Section 2 Types Suffixes
3BSE042835-600 23
The following suffixes shall be recognized:
Other Naming Issues:
• Several suffixes are allowed but do not use _ (underscore) to separate
abbreviations (occupies one position and may be visually unclear).
• Acronyms should be in capital letters, FBD (Function Block Diagram).
Table 3. Object Name Suffixes
Short Name Remark
Real, Bool, Dint, CC Used as suffix on function blocks that have same or similar
function, but the data type of the main signal parameter
differs. It can also be used to group objects using a main
signal of a certain data type. For example: PidSimpleReal,
PidSimpleCC, SignalInBool, and SignalInReal.
M A control module type that has the same functionality as an
existing function block type shall have the same name as
that function block type plus the suffix “M”.
For example:
AlarmCond (Function block type)
AlarmCondM (Control module type)
D A diagram type that has the same functionality as an
existing function block type or control module type shall have
the same name as that function block type or control module
plus the suffix "D" (for Diagram type). For Example:
RemoteInput Control module type and RemoteInputD
Diagram type
Core Protected core functionality, typically re-used in several
different object types. Functionality that may be subject to
changes should be placed outside the core.
For examples: EquipProcedureCore, UniCore
Template Only for object types that the user must change and rename
before use. For example: EquipProcedureTemplate