Control Architect Help Documentation
×
Menu
Index
Block Template Classification
Block Template Classification assigns an Entity Type (Analog or Digital) to each PKS block template. This classification is used throughout the alarm analysis report to separate analog and digital alarm counts and to populate the EntityType column in the Tag Data worksheet.
 
Why Classification Matters
Analog and digital alarms have fundamentally different rationalization approaches under ISA-18.2. Analog alarms (limit-based: PVHI, PVLO, DEVHI, etc.) require setpoint justification, while digital alarms (state-based: ALMOPT, CMDDIS, OFFNORML) require state-change justification. Correct classification ensures the Station Summary counts and Template Breakdown analysis are meaningful.
 
Classification Rules
Entity Type
Typical Template Names
Alarm Characteristics
Analog
PIDTPL, REGCTL, ANAIND
Limit-based alarms: PVHI, PVLO, PVHIHI, PVLOLO, DEVHI, DEVLO, ROCHI
Digital
LOGIC_TPL, DIGIND, DISCNT
State-based alarms: ALMOPT, STATE.ALMENBST, CMDDIS, OFFNORML
 
Managing Classifications
Classifications are managed in the Block Template Editor. See Block Template Editor for instructions on adding and editing template classifications.
Note: Any block template not present in the classification list will result in a darker amber row in the Tag Data worksheet and will not contribute to Analog or Digital counts in the Station Summary.
 
Persistence
Block template classifications are stored in MongoDB and are shared across all report generations within the same Configuration Collection database.
 
See Also