A control profile is a group of settings which define how the building will work while the profile is running.
A typical building would have a number of profiles, which may be " Normal Hours", "After Hours" and "Emergency Mode".
A controller can have up to 7 control profiles which an installer can name dependent on the use.
A control profile is typically global, and will operate across all controllers, however it is possible to have localised profiles to achieve more complex tasks.
Control profiles use a scheduler which lets the system know when the profile will become active. This allows profiles to run differently on different days, weekend or holidays.
A control profile can be called multiple times during the day. The profile can be called, whilst in the same profile. The only effect that will be seen is that the profile entry sequences will be triggered. If there are no such sequences set up, there will be no effect to changing the profile to the same profile.
It is also possible to activate a control profile from a switch or other input device.
A typical use case for control profiles is to change the behaviour of sensors or switches at different times during the day, but can be used to change almost all settings.
Control profiles can have one of four priorities (in order of priority): Scheduled, Medium, High, Emergency.
Scheduled profiles are profiles that are set to be changed to at certain times of the day. All other profile change levels are to facilitate diversions from the regular schedule (ie, events, emergency, etc)
Once in an elevated profile, the user can only change to a profile if it has a priority equal or above to the current profile. During this elevated priority, scheduled profile changes will not change the current profile. In this situation, the schedule profile change still becomes the last scheduled profile that the system has seen.
The most common way to exit profiles above scheduled priority is to use the return to scheduled instruction via sequence and button press actions which do use the last scheduled profile seen.
For example: the user may have a button that sends the system into "Event" mode, which is a medium priority profile. Their regular scheduled profile changes are then only noted, not executed. An emergency occurs and the system goes into its Emergency profile. From this, user intervention would be required to use the return to scheduled feature to get back out of the emergency profile.
Important Note about Emergency Profiles:
To get out of the emergency profile, the most common action is to return to scheduled profile. If the controller has no schedules (for instance, if it only has one normal profile), it is still recommended to have a schedule for that single profile, so that the controller knows which profile to return to. The system allows profile changes to occur whilst still in the same profile.
Alternatively, if there is a single profile on the control system, the action "Go to Profile (Ignore Priority)" can be used.
Comments
0 comments
Article is closed for comments.