It is assumed that basic concepts of OPC UA information modelling are understood in this specification. This specification will use these concepts to describe the ISA-95 Common Object Models. The concepts and terms used to describe the OPC UA Information models are defined in other parts and listed in the following sections. Note that OPC UA terms and terms defined in this standard are italicized.
This standard adopts adding an ISA95 prefix to all ISA-95 defined terms that are used in this standard that are also defined by OPC. The <Term> is the terminology defined by ISA-95. This allows the terminology used in ISA-95 to be easily distinguished from terminology defined in OPC UA.
a concept that categorizes a modelling target defined as a Class in ISA-95 Part2.
Note: It is different than the concept of a Type defined in OPC UA OPC 10000-3, even though the OPC UA Type is also a concept to classify a modelling target and it is similar to a concept of class used in OOAD.
a concept that represents Equipment, Personnel, Physical Assets, and Material defined in ISA-95.
a concept that represents characteristics of a modelling target defined as a Property in ISA-95 Part2.
Note: The semantic of the ISA95Property is similar to Property defined in OPC UA, but the model structure is different since an ISA95Property may have a Reference to an ISA95TestSpecification and an ISA95TestResult and such References are not allowed in an OPC UA Property. An ISA95Property more closely matches an OPC UA Variable, which is allowed to have children.
a concept that represents an attribute of a modelling target defined as attribute in ISA-95.
Note: It is different from a concept of Attribute defined in OPC UA, where Attribute is a concept to represent information of a NodeClass. ISA95Attribute is represented as VariableType in this standard.
UML<Term> is a terminology defined in UML. In this standard, terminologies used in UML are described in this format to distinguish terminology defined in OPC UA and ISA-95.
ACAlarm and Condition
CCTSCore Components Technical Specification (building blocks for data modelling)
CDTCore Data Types
ERPEnterprise Resource Planning
EAMEnterprise Asset Management
LIMSLaboratory Information Management Systems
MES Manufacturing Execution Systems
CMMS Computerized Maintenance Management Systems
MOM Manufacturing Operations Management
SCADA Supervisory Control and Data Acquisition
WMSWarehouse Management Systems
PLCProgrammable Logic Controllers
DCSDistributed Control Systems
OCSOpen Control Systems
This standard uses ModellingRule that are OptionalPlaceholder and MandatoryPlaceholder to define instance declarations, and defines a rule that the BrowseName of instance declarations having an OptionalPlaceholder or MandatoryPlaceholder ModellingRule be enclosed in angle brackets (<>). Originally, this rule is defined in OPC 10000-3 as a recommendation. This naming rule is also used in the description of a table. The BrowseName of a Node that has OptionalPlaceholder or MandatoryPlaceholder ModellingRule are described with angle brackets, which denotes that the name is not fixed. For example BrowseName of Property is described as <PropertyName> in graphical notation and tables results in a Property that can have any name.