Table 133 defines the corresponding ConformanceUnits for the OPC UA Information Model for LADS
Table 133 – Conformance Units for LADS
|
Category |
Title |
Description |
|
Server |
LADS ActiveProgramType |
The server supports nodes that conform to (subtypes of) the ActiveProgramType. The ActiveProgramType node itself is available in the AddressSpace. Every instance of (subtypes of) the ActiveProgramType must include all mandatory components of the ActiveProgramType and may include the optional components. |
|
Server |
LADS AnalogArraySensorFunctionType |
The server supports nodes that conform to (subtypes of) the AnalogArraySensorFunctionType. The AnalogArraySensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogArraySensorFunctionType must include all mandatory components of the AnalogArraySensorFunctionType and may include the optional components. |
|
Server |
LADS AnalogControlFunctionType |
The server supports nodes that conform to (subtypes of) the AnalogControlFunctionType. The AnalogControlFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogControlFunctionType must include all mandatory components of the AnalogControlFunctionType and may include the optional components. |
|
Server |
LADS AnalogControlFunctionWithComposedTargetValueType |
The server supports nodes that conform to (subtypes of) the AnalogControlFunctionWithComposedTargetValueType. The AnalogControlFunctionWithComposedTargetValueType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogControlFunctionWithComposedTargetValueType must include all mandatory components of the AnalogControlFunctionWithComposedTargetValueType and may include the optional components. |
|
Server |
LADS AnalogControlFunctionWithRelativeTargetValueType |
The server supports nodes that conform to (subtypes of) the AnalogControlFunctionWithRelativeTargetValueType. The AnalogControlFunctionWithRelativeTargetValueType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogControlFunctionWithRelativeTargetValueType must include all mandatory components of the AnalogControlFunctionWithRelativeTargetValueType and may include the optional components. |
|
Server |
LADS AnalogControlFunctionWithTotalizerType |
The server supports nodes that conform to (subtypes of) the AnalogControlFunctionWithTotalizerType. The AnalogControlFunctionWithTotalizerType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogControlFunctionWithTotalizerType must include all mandatory components of the AnalogControlFunctionWithTotalizerType and may include the optional components. |
|
Server |
LADS AnalogSensorFunctionType |
The server supports nodes that conform to (subtypes of) the AnalogSensorFunctionType. The AnalogSensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogSensorFunctionType must include all mandatory components of the AnalogSensorFunctionType and may include the optional components. |
|
Server |
LADS AnalogScalarSensorFunctionType |
The server supports nodes that conform to (subtypes of) the AnalogScalarSensorFunctionType. The AnalogScalarSensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogScalarSensorFunctionType must include all mandatory components of the AnalogScalarSensorFunctionType and may include the optional components. |
|
Server |
LADS AnalogScalarSensorFunctionWithCompensationType |
The server supports nodes that conform to (subtypes of) the AnalogScalarSensorFunctionWithCompensationType. The AnalogScalarSensorFunctionWithCompensationType node itself is available in the AddressSpace. Every instance of (subtypes of) the AnalogScalarSensorFunctionWithCompensationType must include all mandatory components of the AnalogScalarSensorFunctionWithCompensationType and may include the optional components. |
|
Server |
LADS BaseControlFunctionType |
The server supports nodes that conform to (subtypes of) the BaseControlFunctionType. The BaseControlFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the BaseControlFunctionType must include all mandatory components of the BaseControlFunctionType and may include the optional components. |
|
Server |
LADS BaseSensorFunctionType |
The server supports nodes that conform to (subtypes of) the BaseSensorFunctionType. The BaseSensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the BaseSensorFunctionType must include all mandatory components of the BaseSensorFunctionType and may include the optional components. |
|
Server |
LADS ControlFunctionStateMachineType |
The server supports nodes that conform to (subtypes of) the ControlFunctionStateMachineType. The ControlFunctionStateMachineType node itself is available in the AddressSpace. Every instance of (subtypes of) the ControlFunctionStateMachineType must include all mandatory components of the ControlFunctionStateMachineType and may include the optional components. The ControlFunctionStateMachineType state machine is implemented correctly by the server. This means the succession of states adheres to the transitions defined in this specification and the 0:HasCause and 0:HasEffect references are implemented correctly. |
|
Server |
LADS ControlFunctionStateMachineType Start method |
Supports the handling of the Start method of the ControlFunctionStateMachineType as described in this specification. |
|
Server |
LADS ControllerParameterSetType |
The server supports nodes that conform to (subtypes of) the ControllerParameterSetType. The ControllerParameterSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the ControllerParameterSetType must include all mandatory components of the ControllerParameterSetType and may include the optional components. |
|
Server |
LADS ControllerParameterType |
The server supports nodes that conform to (subtypes of) the ControllerParameterType. The ControllerParameterType node itself is available in the AddressSpace. Every instance of (subtypes of) the ControllerParameterType must include all mandatory components of the ControllerParameterType and may include the optional components. |
|
Server |
LADS ControllerTuningParameterType |
The server supports nodes that conform to (subtypes of) the ControllerTuningParameterType. The ControllerTuningParameterType node itself is available in the AddressSpace. Every instance of (subtypes of) the ControllerTuningParameterType must include all mandatory components of the ControllerTuningParameterType and may include the optional components. |
|
Server |
LADS CoverFunctionType |
The server supports nodes that conform to (subtypes of) the CoverFunctionType. The CoverFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the CoverFunctionType must include all mandatory components of the CoverFunctionType and may include the optional components. |
|
Server |
LADS CoverStateMachineType |
The server supports nodes that conform to (subtypes of) the CoverStateMachineType. The CoverStateMachineType node itself is available in the AddressSpace. Every instance of (subtypes of) the CoverStateMachineType must include all mandatory components of the CoverStateMachineType and may include the optional components. The CoverStateMachineType state machine is implemented correctly by the server. This means the succession of states adheres to the transitions defined in this specification and the 0:HasCause and 0:HasEffect references are implemented correctly.
|
|
Server |
LADS CoverStateMachineType Close method |
Supports the handling of the Close method of the CoverStateMachineType as described in this specification. |
|
Server |
LADS CoverStateMachineType Lock method |
Supports the handling of the Lock method of the CoverStateMachineType as described in this specification. |
|
Server |
LADS CoverStateMachineType Open method |
Supports the handling of the Open method of the CoverStateMachineType as described in this specification. |
|
Server |
LADS CoverStateMachineType Reset method |
Supports the handling of the Reset method of the CoverStateMachineType as described in this specification. |
|
Server |
LADS CoverStateMachineType Unlock method |
Supports the handling of the Unlock method of the CoverStateMachineType as described in this specification. |
|
Server |
LADS DiscreteControlFunctionType |
The server supports nodes that conform to (subtypes of) the DiscreteControlFunctionType. The DiscreteControlFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the DiscreteControlFunctionType must include all mandatory components of the DiscreteControlFunctionType and may include the optional components. |
|
Server |
LADS DiscreteSensorFunctionType |
The server supports nodes that conform to (subtypes of) the DiscreteSensorFunctionType. The DiscreteSensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the DiscreteSensorFunctionType must include all mandatory components of the DiscreteSensorFunctionType and may include the optional components. |
|
Server |
LADS FunctionalStateMachineType |
The server supports nodes that conform to (subtypes of) the FunctionalStateMachineType. The FunctionalStateMachineType node itself is available in the AddressSpace. Every instance of (subtypes of) the FunctionalStateMachineType must include all mandatory components of the FunctionalStateMachineType and may include the optional components. The FunctionalStateMachineType state machine is implemented correctly by the server. This means the succession of states adheres to the transitions defined in this specification and the hasCause and hasEffect references are implemented correctly. |
|
Server |
LADS FunctionalStateMachineType Abort method |
Supports the handling of the Abort method of the FunctionalStateMachineType as described in this specification. |
|
Server |
LADS FunctionalStateMachineType Clear method |
Supports the handling of the Clear method of the FunctionalStateMachineType as described in this specification. |
|
Server |
LADS FunctionalStateMachineType Stop method |
Supports the handling of the Stop method of the FunctionalStateMachineType as described in this specification. |
|
Server |
LADS FunctionalUnitSetType |
The server supports nodes that conform to (subtypes of) the FunctionalUnitSetType. The FunctionalUnitSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the FunctionalUnitSetType must include all mandatory components of the FunctionalUnitSetType and may include the optional components. |
|
Server |
LADS FunctionalUnitStateMachineType |
The server supports nodes that conform to (subtypes of) the FunctionalUnitStateMachineType. The FunctionalUnitStateMachineType node itself is available in the AddressSpace. Every instance of (subtypes of) the FunctionalUnitStateMachineType must include all mandatory components of the FunctionalUnitStateMachineType and may include the optional components. The FunctionalUnitStateMachineType state machine is implemented correctly by the server. This means the succession of states adheres to the transitions defined in this specification and the hasCause and hasEffect references are implemented correctly. |
|
Server |
LADS FunctionalUnitStateMachineType Start method |
Supports the handling of the Start method of the FunctionalUnitStateMachineType as described in this specification. |
|
Server |
LADS FunctionalUnitStateMachineType StartProgram method |
Supports the handling of the StartProgram method of the FunctionalUnitStateMachineType as described in this specification. |
|
Server |
LADS FunctionalUnitType |
The server supports nodes that conform to (subtypes of) the FunctionalUnitType. The FunctionalUnitType node itself is available in the AddressSpace. Every instance of (subtypes of) the FunctionalUnitType must include all mandatory components of the FunctionalUnitType and may include the optional components. |
|
Server |
LADS FunctionSetType |
The server supports nodes that conform to (subtypes of) the FunctionSetType. The FunctionSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the FunctionSetType must include all mandatory components of the FunctionSetType and may include the optional components. |
|
Server |
LADS FunctionType |
The server supports nodes that conform to (subtypes of) the FunctionType. The FunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the FunctionType must include all mandatory components of the FunctionType and may include the optional components. |
|
Server |
LADS KeyValueType |
Exposes the KeyValueType and all its supertypes in the AddressSpace. |
|
Server |
LADS LADSComponentType |
The server supports nodes that conform to (subtypes of) the LADSComponentType. The LADSComponentType node itself is available in the AddressSpace. Every instance of (subtypes of) the LADSComponentType must include all mandatory components of the LADSComponentType and may include the optional components. |
|
Server |
LADS LADSDeviceStateMachineType |
The server supports nodes that conform to (subtypes of) the LADSDeviceStateMachineType. The LADSDeviceStateMachineType node itself is available in the AddressSpace. Every instance of (subtypes of) the LADSDeviceStateMachineType must include all mandatory components of the LADSDeviceStateMachineType and may include the optional components. |
|
Server |
LADS LADSDeviceStateMachineType GotoMaintenance method |
Supports the handling of the GotoMaintenance method of the LADSDeviceStateMachineType as described in this specification. |
|
Server |
LADS LADSDeviceStateMachineType GotoOperating method |
Supports the handling of the GotoOperating method of the LADSDeviceStateMachineType as described in this specification. |
|
Server |
LADS LADSDeviceStateMachineType GotoShutdown method |
Supports the handling of the GotoShutdown method of the LADSDeviceStateMachineType as described in this specification. |
|
Server |
LADS LADSDeviceStateMachineType GotoSleep method |
Supports the handling of the GotoSleep method of the LADSDeviceStateMachineType as described in this specification. |
|
Server |
LADS LADSDeviceType |
The server supports nodes that conform to (subtypes of) the LADSDeviceType. The LADSDeviceType node itself is available in the AddressSpace. Every instance of (subtypes of) the LADSDeviceType must include all mandatory components of the LADSDeviceType and may include the optional components. |
|
Server |
LADS LADSMaintenanceSetType |
The server supports nodes that conform to (subtypes of) the LADSMaintenanceSetType. The LADSMaintenanceSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the LADSMaintenanceSetType must include all mandatory components of the LADSMaintenanceSetType and may include the optional components. |
|
Server |
LADS LADSOperationCountersType |
The server supports nodes that conform to (subtypes of) the LADSOperationCountersType. The LADSOperationCountersType node itself is available in the AddressSpace. Every instance of (subtypes of) the LADSOperationCountersType must include all mandatory components of the LADSOperationCountersType and may include the optional components. |
|
Server |
LADS LADSOperationModeStateMachineType |
The server supports nodes that conform to (subtypes of) the LADSOperationModeStateMachineType. The LADSOperationModeStateMachineType node itself is available in the AddressSpace. Every instance of (subtypes of) the LADSOperationModeStateMachineType must include all mandatory components of the LADSOperationModeStateMachineType and may include the optional components. |
|
Server |
LADS MaintenanceTaskResultEnum |
Exposes the MaintenanceTaskResultEnum and all its supertypes in the AddressSpace. |
|
Server |
LADS MaintenanceTaskType |
The MaintenanceType node is available in the AddressSpace. The server supports nodes that conform to (subtypes of) the MaintenanceType. The instance(s) of (subtypes of) the MaintenanceType is/are available in the AddressSpace. Events of (subtypes of) the MaintenanceType are generated by the server. |
|
Server |
LADS MaintenanceTaskType ResetTask method |
Supports the handling of the ResetTask method of the MaintenanceTaskType as described in this specification. |
|
Server |
LADS MaintenanceTaskType Start method |
Supports the handling of the Start method of the MaintenanceTaskType as described in this specification. |
|
Server |
LADS MaintenanceTaskType Stop method |
Supports the handling of the Stop method of the MaintenanceTaskType as described in this specification. |
|
Server |
LADS MaintenanceType Historical Events |
The EventNotifier of the instance of a LADSMaintenanceTaskSetType is set to HistoryRead and SubscribeToEvent and Events are stored on the server for HistoryRead. |
|
Server |
LADS MultiSensorFunctionType |
The server supports nodes that conform to (subtypes of) the MultiSensorFunctionType. The MultiSensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the MultiSensorFunctionType must include all mandatory components of the MultiSensorFunctionType and may include the optional components. |
|
Server |
LADS MultiModeAnalogControlFunctionType |
The server supports nodes that conform to (subtypes of) the MultiModeAnalogControlFunctionType. The MultiModeAnalogControlFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the MultiModeAnalogControlFunctionType must include all mandatory components of the MultiModeAnalogControlFunctionType and may include the optional components. |
|
Server |
LADS MultiStateDiscreteControlFunctionType |
The server supports nodes that conform to (subtypes of) the MultiStateDiscreteControlFunctionType. The MultiStateDiscreteControlFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the MultiStateDiscreteControlFunctionType must include all mandatory components of the MultiStateDiscreteControlFunctionType and may include the optional components. |
|
Server |
LADS MultiStateDiscreteSensorFunctionType |
The server supports nodes that conform to (subtypes of) the MultiStateDiscreteSensorFunctionType. The MultiStateDiscreteSensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the MultiStateDiscreteSensorFunctionType must include all mandatory components of the MultiStateDiscreteSensorFunctionType and may include the optional components. |
|
Server |
LADS PidControllerParameterType |
The server supports nodes that conform to (subtypes of) the PidControllerParameterType. The PidControllerParameterType node itself is available in the AddressSpace. Every instance of (subtypes of) the PidControllerParameterType must include all mandatory components of the PidControllerParameterType and may include the optional components. |
|
Server |
LADS ProgramManagerType |
The server supports nodes that conform to (subtypes of) the ProgramManagerType. The ProgramManagerType node itself is available in the AddressSpace. Every instance of (subtypes of) the ProgramManagerType must include all mandatory components of the ProgramManagerType and may include the optional components. |
|
Server |
LADS ProgramManagerType Download method |
Supports the handling of the Download method of the ProgramManagerType as described in this specification. |
|
Server |
LADS ProgramManagerType Remove method |
Supports the handling of the Remove method of the ProgramManagerType as described in this specification. |
|
Server |
LADS ProgramManagerType Upload method |
Supports the handling of the Upload method of the ProgramManagerType as described in this specification. |
|
Server |
LADS ProgramTemplateSetType |
The server supports nodes that conform to (subtypes of) the ProgramTemplateSetType. The ProgramTemplateSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the ProgramTemplateSetType must include all mandatory components of the ProgramTemplateSetType and may include the optional components. |
|
Server |
LADS ProgramTemplateType |
The server supports nodes that conform to (subtypes of) the ProgramTemplateType. The ProgramTemplateType node itself is available in the AddressSpace. Every instance of (subtypes of) the ProgramTemplateType must include all mandatory components of the ProgramTemplateType and may include the optional components. |
|
Server |
LADS RatebasedAccumulatingControlFunctionType |
The server supports nodes that conform to (subtypes of) the RatebasedAccumulatingControlFunctionType. The RatebasedAccumulatingControlFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the RatebasedAccumulatingControlFunctionType must include all mandatory components of the RatebasedAccumulatingControlFunctionType and may include the optional components. |
|
Server |
LADS ResultFileSetType |
The server supports nodes that conform to (subtypes of) the ResultFileSetType. The ResultFileSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the ResultFileSetType must include all mandatory components of the ResultFileSetType and may include the optional components. |
|
Server |
LADS ResultFileType |
The server supports nodes that conform to (subtypes of) the ResultFileType. The ResultFileType node itself is available in the AddressSpace. Every instance of (subtypes of) the ResultFileType must include all mandatory components of the ResultFileType and may include the optional components. |
|
Server |
LADS ResultSetType |
The server supports nodes that conform to (subtypes of) the ResultSetType. The ResultSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the ResultSetType must include all mandatory components of the ResultSetType and may include the optional components. |
|
Server |
LADS ResultType |
The server supports nodes that conform to (subtypes of) the ResultType. The ResultType node itself is available in the AddressSpace. Every instance of (subtypes of) the ResultType must include all mandatory components of the ResultType and may include the optional components. |
|
Server |
LADS RunningStateMachineType |
The server supports nodes that conform to (subtypes of) the RunningStateMachineType. The RunningStateMachineType node itself is available in the AddressSpace. Every instance of (subtypes of) the RunningStateMachineType must include all mandatory components of the RunningStateMachineType and may include the optional components. |
|
Server |
LADS RunningStateMachineType Hold method |
Supports the handling of the Hold method of the RunningStateMachineType as described in this specification. |
|
Server |
LADS RunningStateMachineType Reset method |
Supports the handling of the Reset method of the RunningStateMachineType as described in this specification. |
|
Server |
LADS RunningStateMachineType Suspend method |
Supports the handling of the Suspend method of the RunningStateMachineType as described in this specification. |
|
Server |
LADS RunningStateMachineType ToComplete method |
Supports the handling of the ToComplete method of the RunningStateMachineType as described in this specification. |
|
Server |
LADS RunningStateMachineType Unhold method |
Supports the handling of the Unhold method of the RunningStateMachineType as described in this specification. |
|
Server |
LADS RunningStateMachineType Unsuspend method |
Supports the handling of the Unsuspend method of the RunningStateMachineType as described in this specification. |
|
Server |
LADS SampleInfoType |
Exposes the SampleInfoType and all its supertypes in the AddressSpace. |
|
Server |
LADS SensorValueSetType |
The server supports nodes that conform to (subtypes of) the SensorValueSetType. The SensorValueSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the SensorValueSetType must include all mandatory components of the SensorValueSetType and may include the optional components. |
|
Server |
LADS SetType |
The server supports nodes that conform to (subtypes of) the SetType. The SetType node itself is available in the AddressSpace. Every instance of (subtypes of) the SetType must include all mandatory components of the SetType and may include the optional components. |
|
Server |
LADS SupportedPropertiesSetType |
The server supports nodes that conform to (subtypes of) the SupportedPropertiesSetType. The SupportedPropertiesSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the SupportedPropertiesSetType must include all mandatory components of the SupportedPropertiesSetType and may include the optional components. |
|
Server |
LADS SupportedPropertyType |
The server supports nodes that conform to (subtypes of) the SupportedPropertyType. The SupportedPropertyType node itself is available in the AddressSpace. Every instance of (subtypes of) the SupportedPropertyType must include all mandatory components of the SupportedPropertyType and may include the optional components. |
|
Server |
LADS TimerFunctionType |
The server supports nodes that conform to (subtypes of) the TimerFunctionType. The TimerFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the TimerFunctionType must include all mandatory components of the TimerFunctionType and may include the optional components. |
|
Server |
LADS TwoStateDiscreteControlFunctionType |
The server supports nodes that conform to (subtypes of) the TwoStateDiscreteControlFunctionType. The TwoStateDiscreteControlFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the TwoStateDiscreteControlFunctionType must include all mandatory components of the TwoStateDiscreteControlFunctionType and may include the optional components. |
|
Server |
LADS TwoStateDiscreteSensorFunctionType |
The server supports nodes that conform to (subtypes of) the TwoStateDiscreteSensorFunctionType. The TwoStateDiscreteSensorFunctionType node itself is available in the AddressSpace. Every instance of (subtypes of) the TwoStateDiscreteSensorFunctionType must include all mandatory components of the TwoStateDiscreteSensorFunctionType and may include the optional components. |
|
Server |
LADS VariableSetType |
The server supports nodes that conform to (subtypes of) the VariableSetType. The VariableSetType node itself is available in the AddressSpace. Every instance of (subtypes of) the VariableSetType must include all mandatory components of the VariableSetType and may include the optional components. |
The structure of the Companion Specification Profile and its Facets is interdependent, as depicted in Figure 20. Implementations of the Companion Specification are required to fulfil the LADS BaseServer Server Profile. Additionally, up to three optional Facets - Maintenance, ProgramManager, and ExtendedFunctionalUnit (blue) - can be implemented.
The Maintenance Facet encompasses all necessary nodes for maintenance use cases. The ProgramManager Facet includes all nodes for read-only Program Management, which can be expanded with management methods in the ExtendedProgramManager.
The ExtendedFunctionalUnit Profile mandates the optional methods of the FunctionalUnit, enabling control of a functional unit and a program. This structure provides a comprehensive and flexible framework for implementing the LADS Companion Specification.
In addition, at least one Facet function (grey) needs to be implemented. For the CoverFunction and the ControllerFunction, there is a base Profile (read-only) and an extended Profile with method and write implementation.
Figure 20 – Overview of the Profiles
Table 134 lists all Profiles defined in this document and defines their URIs.
Table 134 – Profile URIs for LADS
|
Profile |
URI |
|
LADS BaseServer Server Profile |
http://opcfoundation.org/UA-Profile/LADS/Server/BaseServer |
|
LADS Maintenance Server Facet |
http://opcfoundation.org/UA-Profile/LADS/Server/Maintenance |
|
LADS ProgramManager Server Facet |
http://opcfoundation.org/UA-Profile/LADS/Server/ProgramManager |
|
LADS ExtendedProgramManager |
http://opcfoundation.org/UA-Profile/LADS/Server/ExtendedProgramManager |
|
LADS ExtendedFunctionalUnit Server Facet |
http://opcfoundation.org/UA-Profile/LADS/Server/ExtendedFunctionalUnit |
|
LADS CoverFunction Server Facet |
http://opcfoundation.org/UA-Profile/LADS/Server/CoverFunction |
|
LADS SensorFunction Server Facet |
http://opcfoundation.org/UA-Profile/LADS/Server/SensorFunction |
|
LADS ControllerFunction Server Facet |
http://opcfoundation.org/UA-Profile/LADS/Server/ControllerFunction |
|
LADS ExtendedControllerFunction Server Facet |
http://opcfoundation.org/UA-Profile/LADS/Server/ExtendedControllerFunction |
The following sections specify the Facets available for Servers that implement the LADS companion specification. Each section defines and describes a Facet or Profile.
Table 135 defines a Profile that describes a basic LADS OPC UA Server.
Table 135 – LADS BaseServer Server Profile
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
Profile |
0:Core 2022 Server Facethttp://opcfoundation.org/UA-Profile/Server/Core2022Facet |
|
|
Profile |
0:Nano Embedded Device 2022 Server Profilehttp://opcfoundation.org/UA-Profile/Server/NanoEmbeddedDevice2022 |
|
|
Profile |
0:UA-TCP UA-SC UA Binaryhttp://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary |
|
|
Profile |
0:Data Access Server Facethttp://opcfoundation.org/UA-Profile/Server/DataAccess |
|
|
Base Information |
0:Base Info Custom Type System |
M |
|
Base Information |
0:Base Info Engineering Units |
M |
|
Base Information |
0:Base Info Placeholder Modelling Rules |
M |
|
AMB |
3:AMB Configurable Asset Identification |
M |
|
AMB |
3:AMB Hierarchical Location Property |
O |
|
AMB |
3:AMB Operational Location Property |
O |
|
DI |
2:DI DeviceSet |
M |
|
DI |
2:DI DeviceType |
M |
|
DI |
2:DI DeviceHealth |
O |
|
DI |
2:DI Locking |
O |
|
Machinery |
4:Machinery Component Identification |
O |
|
Machinery |
4:Machinery Building Block Organization |
O |
|
Machinery |
4:Machinery MachineryItem State |
O |
|
Machinery |
4:Machinery Operation Mode |
O |
|
Machinery |
4:Machinery Operation Counter |
O |
|
Machinery |
4:Machinery Lifetime Counter |
O |
|
LADS |
LADS ComponentSetType |
M |
|
LADS |
LADS FunctionalStateMachineType |
M |
|
LADS |
LADS FunctionalUnitSetType |
M |
|
LADS |
LADS FunctionalUnitStateMachineType |
M |
|
LADS |
LADS FunctionalUnitType |
M |
|
LADS |
LADS FunctionSetType |
M |
|
LADS |
LADS FunctionType |
M |
|
LADS |
LADS LADSComponentType |
M |
|
LADS |
LADS LADSDeviceStateMachineType |
M |
|
LADS |
LADS LADSDeviceStateMachineType GotoMaintenance Method |
O |
|
LADS |
LADS LADSDeviceStateMachineType GotoOperating Method |
O |
|
LADS |
LADS LADSDeviceStateMachineType GotoShuttingDown method |
O |
|
LADS |
LADS LADSDeviceStateMachineType GotoSleep Method |
O |
|
LADS |
LADS LADSDeviceType |
M |
|
LADS |
LADS LADSMaintenanceSetType |
O |
|
LADS |
LADS LADSOperationCountersType |
M |
|
LADS |
LADS RunningStateMachineType |
M |
|
LADS |
LADS SensorValueSetType |
M |
|
LADS |
LADS SetType |
M |
|
LADS |
LADS SupportedPropertiesSetType |
M |
|
LADS |
LADS SupportedPropertyType |
M |
|
LADS |
LADS VariableSetType |
M |
|
LADS |
LADS FunctionalStateMachineType |
M |
|
LADS |
LADS FunctionalUnitSetType |
M |
|
LADS |
LADS FunctionalUnitStateMachineType |
M |
|
LADS |
LADS FunctionalUnitType |
M |
|
LADS |
LADS FunctionSetType |
M |
Table 136 defines a Profile that contains all necessary conformance units for maintenance tasks.
Table 136 – LADS Maintenance Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
AMB |
AMB Asset Health Status Base |
M |
|
AMB |
AMB Asset Health Status Alarms |
O |
|
AMB |
AMB Asset Health Tracking Overall Asset Status |
O |
|
AMB |
AMB Asset Health Tracking Events |
O |
|
AMB |
AMB Client Asset Health Status |
O |
|
LADS |
LADS MaintenanceTaskType |
M |
|
LADS |
LADS MaintenanceTaskType ResetTask Method |
O |
|
LADS |
LADS MaintenanceTaskType Start Method |
O |
Table 137 defines a Profile that contains all necessary conformance units for program monitoring.
Table 137 – LADS ProgramManager Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS ActiveProgramType |
M |
|
LADS |
LADS ProgramManagerType |
M |
|
LADS |
LADS ProgramTemplateSetType |
M |
|
LADS |
LADS ProgramTemplateType |
M |
|
LADS |
LADS ResultFileSetType |
O |
|
LADS |
LADS ResultFileType |
O |
|
LADS |
LADS ResultSetType |
O |
|
LADS |
LADS ResultType |
O |
Table 138 defines a Profile that contains all necessary conformance units for complete program management, including up- and download of program templates.
Table 138 – LADS ExtendedProgramManager Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS ProgramManager Server Facet |
M |
|
LADS |
LADS ProgramManagerType Download method |
M |
|
LADS |
LADS ProgramManagerType Remove method |
M |
|
LADS |
LADS ProgramManagerType Upload method |
M |
Table 139 defines a Profile that contains all conformance units which extend a Functional Unit with Methods.
Table 139 – LADS ExtendedFunctionalUnit Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS FunctionalStateMachineType Abort Method |
M |
|
LADS |
LADS FunctionalStateMachineType Clear Method |
M |
|
LADS |
LADS FunctionalStateMachineType Stop Method |
M |
|
LADS |
LADS FunctionalUnitStateMachineType Start Method |
M |
|
LADS |
LADS FunctionalUnitStateMachineType StartProgram Method |
O |
|
LADS |
LADS RunningStateMachineType Hold Method |
O |
|
LADS |
LADS RunningStateMachineType Reset Method |
O |
|
LADS |
LADS RunningStateMachineType Suspend Method |
O |
|
LADS |
LADS RunningStateMachineType ToComplete Method |
O |
|
LADS |
LADS RunningStateMachineType Unhold Method |
O |
|
LADS |
LADS RunningStateMachineType Unsuspend Method |
O |
Table 140 defines a Profile which contains all conformance units for implementing a cover function.
Table 140 – LADS CoverFunction Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS CoverFunctionType |
M |
|
LADS |
LADS CoverStateMachineType |
M |
Table 141 defines a Profile which contains all conformance units for implementing a cover function and extending the CoverFunction with Methods.
Table 141 – LADS ExtendedCoverFunction Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS CoverFunction Server Facet |
|
|
LADS |
LADS CoverStateMachineType Close Method |
M |
|
LADS |
LADS CoverStateMachineType Lock Method |
M |
|
LADS |
LADS CoverStateMachineType Open Method |
M |
|
LADS |
LADS CoverStateMachineType Reset Method |
O |
|
LADS |
LADS CoverStateMachineType Unlock Method |
M |
|
LADS |
LADS CoverStateMachineType Close Method |
M |
Table 142 defines a Profile that a Server can provide if a Sensor is used in the model. At least one of the optional conformance units must also be implemented.
Table 142 – LADS SensorFunction Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS AnalogArraySensorFunctionType |
O |
|
LADS |
LADS AnalogSensorFunctionType |
O |
|
LADS |
LADS AnalogScalarSensorFunctionType |
O |
|
LADS |
LADS AnalogScalarSensorFunctionWithCompensationType |
O |
|
LADS |
LADS BaseSensorFunctionType |
M |
|
LADS |
LADS DiscreteSensorFunctionType |
O |
|
LADS |
LADS MultiSensorFunctionType |
O |
|
LADS |
LADS MultiStateDiscreteSensorFunctionType |
O |
|
LADS |
LADS TwoStateDiscreteSensorFunctionType |
O |
Table 143 defines a Profile that a Server can provide if a Controller system is used in the model. At least one of the optional conformance units must also be implemented.
Table 143 – LADS ControllerFunction Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS AnalogControlFunctionType |
O |
|
LADS |
LADS AnalogControlFunctionWithComposedTargetValueType |
O |
|
LADS |
LADS AnalogControlFunctionWithTotalizerType |
O |
|
LADS |
LADS BaseControlFunctionType |
M |
|
LADS |
LADS ControlFunctionStateMachineType |
O |
|
LADS |
LADS ControllerParameterSetType |
O |
|
LADS |
LADS ControllerParameterType |
O |
|
LADS |
LADS ControllerTuningParameterType |
M |
|
LADS |
LADS DiscreteControlFunctionType |
O |
|
LADS |
LADS MultiModeAnalogControlFunctionType |
O |
|
LADS |
LADS MultiStateDiscreteControlFunctionType |
O |
|
LADS |
LADS PidControllerParameterType |
O |
|
LADS |
LADS RatebasedAccumulatingControlFunctionType |
O |
|
LADS |
LADS TimerFunctionType |
O |
|
LADS |
LADS TwoStateDiscreteControlFunctionType |
O |
Table 144 defines a Profile which extends the ControllerFunction Server Facet with method calls.
Table 144 – LADS ExtendedControllerFunction Server Facet
|
Group |
Conformance Unit/Profile Title |
Mandatory/Optional |
|
LADS |
LADS ControllerFunction Server Facet |
|
|
LADS |
LADS ControlFunctionStateMachineType Start Method |
M |
|
LADS |
LADS RunningStateMachineType Hold Method |
O |
|
LADS |
LADS RunningStateMachineType Reset Method |
O |
|
LADS |
LADS RunningStateMachineType Suspend Method |
O |
|
LADS |
LADS RunningStateMachineType ToComplete Method |
O |
|
LADS |
LADS RunningStateMachineType Unhold Method |
O |
|
LADS |
LADS RunningStateMachineType Unsuspend Method |
O |
|
LADS |
LADS FunctionalStateMachineType Abort Method |
M |
|
LADS |
LADS FunctionalStateMachineType Clear Method |
M |
|
LADS |
LADS FunctionalStateMachineType Stop Method |
M |