2. What’s New in System Platform 2014 R2 – Part 1
GCS Connect EMEA 2015
DAY 1 – CHANGE DATE FOR DAY 3
April 13, 2015
Eric Enet
Sr. Manager, Wonderware Technical Training Strategy

3. Brand & Industries or Technology:
WW TRN1
What’s New in System Platform 2014 R2 – Part 1
Eric Enet
Brand & Industries or Technology:
Wonderware
All disciplines
Focus of presentation:
This session provides explanations and demonstrations of the main new features in System Platform 2014 and R2. In Part 1 we will cover the unified attribute name space (the new Attributes tab), IO binding, and alarm enhancements.
What you’ll take away:
How to use the Attributes tab.
How to use IO Binding.
What are Alarm Severities.
What is Alarm Shelving and Alarm Plant Modes.
Using the Historian to log alarms and events.
Focus of presentation: what you’ll talk about
Brand & Vertical: Wonderware & Industries or technology
What you’ll take away: 3 or 4 main points audience should remember

4. Agenda The Unified Attribute Name Space
Auto References with IO Binding
Alarm enhancements

5. Requirements and Expectations
Proficient in Application Server
Proficient in InTouch and ArchestrA Graphics

6. Unified Name Space
The new Attributes tab

7. The Attributes Tab Combines the capabilities of:
User-Defined Attributes
Extensions
Field Attributes
It is available in all automation objects in the Galaxy.
User-Defined Attributes + Extensions get automatically converted to the new Attributes.
Field Attributes do get converted automatically. Patch 01 includes a conversion option for Field Attributes.
An analog attribute configured in the new Attributes tab

8. The Power of One… Attribute
Capability
UDA + Extension
Field Attribute
Attribute
Available
All objects
$UserDefined object
Data Types
Boolean
Integer, Float, Double
String
Elapse Time
Time
Internationalized String
Description No
Yes
Category / Writeability 1
Calculated
Calculated Retentive
Object Writeable
User Writeable -
Arrays
Yes 2
Comparison between all three options.
1 The InternationalizedString data type is writeable on configuration time only
2 Not applicable to the InternationalizedString data type

9. The Power of One… Attribute (cont.)
Capability
UDA + Extension
Field Attribute
Attribute
I/O
Yes 1
Yes
Scaling No
Statistics
Boolean
Analog
Historization
Yes 1, 2
Alarming
Log / Event change
Comparison between all three options (cont.).
1 Not applicable to the InternationalizedString data type
2 Not applicable to the Time data type

10. Attribute Features Data Type I/O History State alarm Limit alarm
ROC alarm
Deviation alarm
Bad value alarm
Statistics
Log change
Boolean 
Integer
Float
Double
String
Elapse Time
Time
Internationalized String
Features available per data type.

11. IO Binding
Automatic attribute references

12. Automatic I/O Reference Binding
New IO Devices and IO Device Mapping views allow automatic configuration of I/O references.
Based on naming conventions for objects and attributes names.
Allows overriding references.
It only works with the I/O feature of the new Attributes. Objects with built-in attribute references do not work with auto-binding; for example: $DiscreteDevice, $AnalogDevice, $OperationsCapability, $UtilizationCapability, etc.
The IO Devices and IO Devices Mapping views show automatically generated IO references

13. From the PLC to the Attribute
DIO.Topic1.Mixer100.Level.PV
Mixer100.Level.PV
Object
DIO
DAS
PLC
Address Space
Attribute
Topic
Topic
Item
Alias List (csv)
First: when using “modern” PLC that support a mnemonic namespace.
Second: when using a legacy system with register addresses; aid by the use of an alias list.
The alias list can be loaded in the DAS or the DIO. Loading the alias list it in the DAS:
Reduces performance hit on runtime; the csv content is deployed by with the DIO and the DIO needs to do the translation.
Allows other DIOs and systems to take advantage
DIO.Topic1.Mixer100.Level.PV
Mixer100.Level.PV , 30001
30001

14. Alarm Enhancements
Alarm Severities, Alarm Plant State, Alarm Shelving, Security and Alarm Logging
Alarm Severities: concept, aggregation, attributes, symbols (alarm border and alarm severity), and Alarm Border animation.
Alarm Plant State: concept and attributes.
Alarm Shelving: concept, attributes, and alarm modes/states.
Alarm Permissions: New security permissions.
Alarm and Event Logging: concept and options.

15. Alarm Severities
Provides a mechanism to categorize alarms in four distinct groups based on the criticality (priority) of the alarm.
Severities can be aggregated from the attributes all the way up to the Area.
Display capabilities in the form of Alarm Border and Alarm Severity Symbol.
Severity number logged on User1 column. User1 column not previously used by Application Server alarm logging.
The Alarms and Events Configuration dialog box

16. Alarm Severities Aggregation
Attribute
Object (Contained)
Object (Container)
Sub-Area
Area
Alarm Severity aggregated counts:
AlarmCntsBySeverity » Integer[4]
Most Urgent Alarm information:
AlarmMostUrgentSeverity » Integer
AlarmMostUrgentInAlarm » Boolean
AlarmMostUrgentAcked » Boolean
AlarmMostUrgentMode » Enum
AlarmMostUrgentShelved » Boolean
All attributes are read-only.
From bottom-left to top-right:
All alarms in a single attribute (Alarms in a Temperature attribute: Hi, ROC, etc.)
All attributes in an object (Attributes in a tank object: Level, Temperature, etc.)
All contained objects (Objects contained in a Mixer: Valve, Pump, etc.)
All objects in an Area (Objects hosted in Line 1: Mixer100, Mixer200, etc.)
All areas in an Area (Areas in Production: Line 1, Line 2, etc.)
Alarm Severity attributes available at:
Areas (includes all objects and sub-areas)
Objects (includes contained objects)
Attributes (includes all alarms in the field attribute)

17. Alarm Plant State
Provides context when setting the Alarm Mode (Enable, Disable, Silence) for an area.
Plant State attributes:
PlantState » String R/W
PlantStateAlarmMode » Enum R-O
Attributes at the Area object only.
This is 2-fold:
- Allows context when setting the alarm mode for an entire area.
- Allows restriction through security (more on this later) by providing different permissions for the Plant State and the Alarm Mode.
The Alarms and Events Configuration dialog box

18. Alarm Shelving
Provides a mechanism to suppress reporting alarms to Alarm Clients for a specified period of time.
Shelving attributes:
AlarmShelveCmd » String R/W
AlarmShelved » Boolean R-O
AlarmShelveNode » String R-O
AlarmShelveReason » String R-O
AlarmShelveStartTime » Time R-O
AlarmShelveEndTime » Time R-O
AlarmShelveUser » String R-O
Alarm Shelving is set at the object level through the Alarm Client of an attribute.
Duration and reason for shelving is mandatory.
The Alarms and Events Configuration dialog box

19. Alarm States Logging alarms with Historian Server.
View
Trigger
Alarm Condition
Inhibited
Disabled
Silenced
Shelved
Log
Logging alarms with Alarm DB Logger.
View
Trigger
Alarm Condition
Inhibited
Disabled
Silenced
Shelved
The alarm trigger represent the expression/rule for the alarm (for example, Level > 70).
The alarm condition is the actual alarm being raised (InAlarm attribute set to true).
Inhibiting an alarm sets the Alarm Mode to Disable.
Log

20. Alarm Permissions
New security permissions for new and existing alarm management capabilities.
Operational permissions:
Can Acknowledge Alarms
Can Shelve Alarms
Can Modify Alarm Modes
Can Modify Plant States
Permissions:
Can Acknowledge Alarms (previously available)
Can Shelve Alarms (new permission for new capability)
Can Modify Alarm Modes (new permission for existing capability)
Can Modify Plant States (new permission for new capability)
The Security configuration dialog box

21. Alarm and Event Logging
Alarm and Events from Application Server logged by Historian Server.
Log to:
Traditional SQL Server database (A2ALMDB), or
History Blocks
The A2ALMDB database has the same structure as the traditional WWALMDB database; it cannot be renamed.
Alarm Client enhanced to read the alarm and event log from the SQL database or from history blocks.
The Configurator utility

22. Alarm and Event Logging
Alarm logging by severity.
Event logging by type.
Alarm DB Logger is still an option.
The Alarms and Events Configuration dialog box

23. DAY 1 – HIDE FOR DAY 3 PRESENTATION

24. DAY 3 – HIDE FOR DAY 1 PRESENTATION