[Example] Configuring a Custom Global Events Library

Scenario: This example shows how to create a customized regional events library with an event schema that uses the 10-category mapping pattern (ten event lamps), two additional custom colors, and a new event category to handle High Risk Gas events.

The new category is created using text group extensions, which is the method used when text group customization is not possible (for example, because different extension modules require changes to text groups at the same library level).

In this example, only the sound files included in the Media library at L1-Headquarter library level are used.

Reference: For background information, see Events Library.

Workflow diagram:

Prerequisites:

You are trained and authorized to work with system libraries at the target customization level. For example, L3-Region.
System Manager is in Engineering mode.
System Browser is in Management View.

Steps:

1 – Create the Customized Events Library

Do this step if a customized events library does not yet exist at the target customization level. For example, L3-Region.

For instructions see Creating a Customized Events Library.

2 – Configure Text Group Extensions

In this step, we will use text group extension to create a new category as follows:

Full text = High Risk Gas (It will extend the category text group, TxG_Category)
Short text = HRG (It will extend the category text group, TxG_CategoryShort)
Seven text group extensions (They will extend the Propagation Summary Status Text Group, TxG_PropagationSummaryStatus):

Management System High Risk Gas
Building Infrastructure High Risk Gas
Building Automation High Risk Gas
Fire High Risk Gas
Security High Risk Gas
Energy Management High Risk Gas
Notification High Risk Gas

It will then be necessary to export and re-import the customized events library for the new text groups to become available.

For instructions, see Configuring Text Group Extensions for Categories.

3 – Add and Configure New Event Colors

In this step, we will configure two custom event colors (Cyan and Bordeaux) in the customized events library, with the gradations indicated in the following table.

For instructions on configuring the custom colors, see Configuring Event Colors in a Library.

Examples of Event Colors Configuration
Property	Cyan	Bordeaux
Text Button Normal	#000000	#000000
Text Button Pressed	#FFFFFF	#FFFFFF
Text Event Selected	#000000	#000000
Text Event Normal	#000000	#000000
Text Event Hover	#000000	#000000
Button Gradient Bright	#00FFFF	#E5326F
Button Gradient Dark	#00CCCC	#DF004C
Button Pressed Gradient Bright	#009999	#B72858
Button Pressed Gradient Dark	#007F7F	#85002D
Button Blinking Bright	#98969A	#98969A
Button Blinking Dark	#5A5D60	#5A5D60
Event Descriptor Selected	#7FFFFF	#E84C81
Event Descriptor Normal	#B2FFFF	#F5B2C9

For color information, refer to specific websites (for example, http://www.color-hex.com/).

4 – Add, Configure, and Apply a New Event Schema

In this step, we will configure a custom event schema (Brazil) that uses the previously configured custom category (High Risk Gas) and custom colors (Cyan and Bordeaux), as indicated in the mapping tables below. Then we will apply the new event schema to the project.

For instructions, see Configuring Event Schemas in a Library.

Example of Category Mapping
ID	Category Text	Event Color Name	Default
01	High Risk Gas	Red Yellow	Y
02	Life Safety	Red	N
03	Danger	Magenta	N
04	Supervisory	Cyan	N
05	Trouble	Yellow	N
06	Isolation	Bordeaux	N
07	Medium	Bordeaux	N
08	Low	Bordeaux	N
09	Fault	Bordeaux	N
10	Status	Cyan	N

Example of Event Mapping
Class	Discipline	Category	Sound File
Access Denied	*	01(High Risk Gas)	CategorySound_01.wav
Access Granted	*	02(Life Safety)	CategorySound_02.wav
Activation	*	03(Danger)	CategorySound_03.wav
Fault	*	09(Fault)	CategorySound_09.wav
Status	*	10(Status)	CategorySound_10.wav
Alarm	*	04(Supervisory)	CategorySound_04.wav
Anomaly	*	05(Trouble)	CategorySound_05.wav
Blocked	*	08(Low)	CategorySound_08.wav
Buffer Full	*	06(Isolation)	CategorySound_06.wav
Burglary	*	07(Medium)	CategorySound_07.wav
Add any additional row to handle all the alarm classes
*	*	08(Low)	CategorySound_08.wav

In a custom event schema, you may either use all the categories and colors defined in Desigo CC (custom categories and custom colors included), or less than ten categories.

5 – Check the Result: Alarms Appearance and Behavior

The following describes the Desigo CC alarms appearance and behavior resulting from the above configuration.

Ten event categories are configured in Desigo CC. Consequently, the Summary bar displays ten event lamps (ID = 01 is the leftmost while ID = 10 is the rightmost).
From left to right text,

Event lamps texts are: High Risk Gas, Life Safety, Danger, Supervisory, Trouble, Isolation, Medium, Low, Fault, and Status.
Event lamps colors are: Red (with yellow text), Red (with white text), Magenta, Cyan, Yellow, Bordeaux, Bordeaux, Bordeaux, Bordeaux, and Cyan.

If you add a new station object without configuring it,

Following the station Object Model, a Fault alarm generates.
Following the custom events library configuration, the Fault event lamp blinks on the Summary bar and has Bordeaux color. The sound played corresponds with CategorySound_09.wav.
In the Operation tab, the Summary Status indicates Management System Fault (the station object belongs to the Management System discipline). Its icon color is Bordeaux.

If you set the Status flag of a BACnet Binary Output object to Fault,

Following the configuration of the BACnet Standard Alarm Table in HQ-BA-Device-BACnet library, a Fault alarm is generated.
Following the custom events library configuration, the Fault event lamp blinks on the Summary bar and has Bordeaux color. The sound played corresponds with CategorySound_09.wav.
In the Operation tab, the Summary Status indicates Building Automation Fault (the Binary Output object belongs to the Building Automation discipline). Its icon color is Bordeaux.

If you set an invalid configuration for the POP3 protocol of the Mail notification device,

As an alarm is configured for the GMSMail_POP3.Status property in the mail object model, a Status event is generated.
Following the custom events library configuration, the Status event lamp blinks on the Summary bar and has Cyan color. The sound played corresponds with CategorySound_10.wav.
In the Operation tab, the Summary Status indicates Management System Status (the Mail object belongs to the Management System discipline). Its icon color is Cyan.

Any other alarm that does not belong to one of the custom Class-Discipline couples, follows the configuration in the last row of the custom event mapping,

The Low event lamp blinks on the Summary bar and has Bordeaux color. The sound played corresponds with CategorySound_08.wav.
In the Operation tab, the Summary Status indicates [Discipline] Low (where [Discipline] indicates the discipline of the alarmed point). Its icon color is Bordeaux.