Working with Profiles

The Profile is the foundation that everything within Connect is built upon, therefore the most important component! A profile is a set of objects and the data type those objects present. Accurate profiles will present trouble free results. Inaccurate profiles will produce inaccurate results and possible communications (COMM) issues. 

A common misconception is that all devices of the same type contain the same objects and data types. At times, all devices of the same type will not contain the same set of objects, names, or data types. A person may assume that all the Fan Coils or Variable Air Volume Terminals will contain the exact same set of objects using the exact same data types. But in reality many times a small group will contain a small difference. 

For example:

• An exhaust fan start stop and status is added to a small number of Fan Coils or Variable Air Volume Terminals.
• A small set of devices have a CO2 or humidity sensor while the others do not.
• Different controls technicians or contractors were used during different project stages and the same brand and model of devices contain different object sets, names or data type conversions.

Devices with different object sets must have different profiles. Identifying these differences requires some investigation. 

Correct and trouble-free Profiles require careful attention through multiple actions.

Clean Profiles help:

• Produce lower Average Load %.
• Prevent Comm Errors.

Clean Profiles provide:

• Quicker scan times.
• Higher Points per minute values.
• Better performance overall.

A Profile is required for each device that contains a unique object set.

High Level Step Overview

1. Create a Profile name for each individual device object set.
2. In at least one device of each Profile type, perform an Object scan.

3. Select any object that does not return an invalid value such as NaN or a blank value. 

   One method to assure clean profiles is to use the Dynamic Explorer and scroll through each device, watching the Dynamic Grid for occurrences of blank, NaN or BadUri values.
4. The user may desire to apply in a Dynamic Explorer scan.
5. Save the selected objects.
6. Select Occupancy and Output objects returning Text values and apply the correct Point Conversions. You may wish to apply conversions to all objects returning Text values.
7. Select all objects where trending is desired and then assign a Trend Interval.
8. Select a Profile, open the Properties window, and then assign a Device Class.
9. Perform the Object Mapping.
10. Save and review. 
11. Perform any troubleshooting, if needed.
12. Restart the Agent.