This chapter defines the corresponding Conformance Units for the OPC UA Information Model for Pumps and Vacuum Pumps.
Table 152 – Conformance Units for OPC UA for Pumps and Vacuum Pumps
Category |
Title |
Description |
Server |
Base System |
The PumpType is implemented by the server. |
Server |
Historizing |
The Historizing Attribute and the HistoryRead Attribute is True for at least one Quantity. |
Server |
Limit Alarm Status |
The ObjectTypes MeasurementsType, DriveMeasurementsType, InletConnectionMeasurementsType and OutletConnectionMeasurementsType have a 0:GeneratesEvent reference targeting one of the subtypes of the 0:LimitAlarmType. |
Server |
PumpClass Data |
The PumpClass Property of the Design FunctionalGroup is instantiated for all instantiated Pumps and carries a legal value. |
Server |
Pump Connection Port |
At least one of the InletConnectionPortType or the OutletConnectionPortType is implemented by the Server. |
Server |
Pump Control |
At least one of ControlType, ActuationType or one of subtypes of ActuationType is implemented by the Server. |
Server |
Pump Drive Port |
The DrivePortType is implemented by the server. |
Server |
Pump Identification |
Supports the PumpIdentificationType with all its mandatory InstanceDeclarations, and optionally the optional InstanceDeclarations with read access. |
Server |
PumpPumpType Mandatory Nodes |
All nodes declared as mandatory in the PumpType are available in the AdressSpace. |
Server |
Supervision Health Status |
Every instance of a variable of type 0:TwoStateDiscreteType in the subtypes of SupervisionType has a GeneratesEvent reference targeting one of the subtypes of the 2:DeviceHealthDiagnosticAlarmType. |
Table 153 lists all Profiles defined in this document and defines their URIs.
Table 153 – Profile URIs for OPC UA for Pumps and Vacuum Pumps
Profile |
URI |
Pump Base Server Profile |
|
Pump Advanced Server Profile |
The following sections specify the Facets available for Servers that implement the OPC UA for Pumps and Vacuum Pumps companion specification. Each section defines and describes a Facet or Profile.
This Profile defines the elements for a Pump Server which supports basic functionality like the configuration of the Pump, perform various analyses, and provide machine identification.
Table 154 – Pump Base Server Profile
Group |
Conformance Unit / Profile Title |
M / O |
Profile |
0:Embedded 2017 UA Server Profile |
M |
Profile |
0:Data Access Server Facet |
M |
Profile |
0:ComplexType 2017 Server Facet |
M |
Profile |
0:Aggregate Subscription Server Facet http://opcfoundation.org/UA-Profile/Server/AggregateSubscription |
M |
Profile |
3:Machine Identification Writable Server Facet http://opcfoundation.org/UA-Profile/Machinery/Server/MachineIdentificationWritable |
M |
Pump |
Pump PumpType Mandatory Nodes |
M |
Pump |
Base System |
M |
This Profile defines the elements for a Pump Server which supports advanced functionality like the control of the pump, provide health and limit status in the AddressSpace and provide ports.
Table 155 – Pump Advanced Server Profile
Group |
Conformance Unit / Profile Title |
M / O |
Profile |
0:Address Space Notifier Server Facet http://opcfoundation.org/UA-Profile/Server/AddressSpaceNotifier |
M |
Profile |
0:A & C Address Space Instance Server Facet http://opcfoundation.org/UA-Profile/Server/ACAddressSpaceInstance |
M |
Profile |
0:A & C Exclusive Alarming Server Facet http://opcfoundation.org/UA-Profile/Server/ACExclusiveAlarming |
M |
Profile |
0:Base Historical Event Server Facet http://opcfoundation.org/UA-Profile/Server/BaseHistoricalEvent |
M |
Profile |
0:Historical Raw Data Server Facet http://opcfoundation.org/UA-Profile/Server/HistoricalRawData |
M |
Profile |
0:Historical Aggregate Server Facet http://opcfoundation.org/UA-Profile/Server/AggregateHistorical |
M |
Profile |
Pump Base Server Profile |
M |
Pumps |
Historizing |
O |
Pumps |
Limit Alarm Status |
O |
Pumps |
PumpClass Data |
O |
Pumps |
Pump Connection Port |
O |
Pumps |
Pump Control |
O |
Pumps |
Pump Drive Port |
O |
Pumps |
Supervision Health Status |
O |
This version of the specification does not define any Client Facets.