Table 29 defines the namespace metadata for this document. The Object is used to provide version information for the namespace and an indication about static Nodes. Static Nodes are identical for all Attributes in all Servers, including the Value Attribute. See OPC 10000-5 for more details.
The information is provided as Object of type NamespaceMetadataType. This Object is a component of the Namespaces Object that is part of the Server Object. The NamespaceMetadataType ObjectType and its Properties are defined in OPC 10000-5.
The version information is also provided as part of the ModelTableEntry in the UANodeSet XML file. The UANodeSet XML schema is defined in OPC 10000-6.
Table 29 – NamespaceMetadata Object for this Document
|
Attribute |
Value |
||
|
BrowseName |
|||
|
Property |
DataType |
Value |
|
|
NamespaceUri |
String |
||
|
NamespaceVersion |
String |
1.0.0 |
|
|
NamespacePublicationDate |
DateTime |
2022-09-01 |
|
|
IsNamespaceSubset |
Boolean |
False |
|
|
StaticNodeIdTypes |
IdType [] |
System.Int32[] |
|
|
StaticNumericNodeIdRange |
NumericRange [] |
|
|
|
StaticStringNodeIdPattern |
String |
|
|
Note: The IsNamespaceSubset Property is set to False as the UaNodeSet XML file contains the complete Namespace. Servers only exposing a subset of the Namespace need to change the value to True.
Namespaces are used by OPC UA to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId. Unlike NodeIds, the BrowseName cannot be used to unambiguously identify a Node. Different Nodes may have the same BrowseName. They are used to build a browse path between two Nodes or to define a standard Property.
Servers may often choose to use the same namespace for the NodeId and the BrowseName. However, if they want to provide a standard Property, its BrowseName shall have the namespace of the standards body although the namespace of the NodeId reflects something else, for example the EngineeringUnits Property. All NodeIds of Nodes not defined in this document shall not use the standard namespaces.
Table 30 provides a list of mandatory and optional namespaces used in an OPC 40560 OPC UA Server.
Table 30 – Namespaces used in an OPC 40560 Server
|
NamespaceURI |
Description |
Use |
|
Namespace for NodeIds and BrowseNames defined in the OPC UA specification. This namespace shall have namespace index 0. |
Mandatory |
|
|
Local Server URI |
Namespace for nodes defined in the local server. This namespace shall have namespace index 1. |
Mandatory |
|
Namespace for NodeIds and BrowseNames defined in OPC 10000-100OPC 10000-100. The namespace index is Server specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames defined in OPC 40001-1. The namespace index is Server specific. |
Mandatory |
|
|
Namespace for NodeIds and BrowseNames defined in this document. The namespace index is Server specific. |
Mandatory |
|
|
Vendor specific types |
A Server may provide vendor-specific types like types derived from ObjectTypes defined in this document in a vendor-specific namespace. |
Optional |
|
Vendor specific instances |
A Server provides vendor-specific instances of the standard types or vendor-specific instances of vendor-specific types in a vendor-specific namespace. It is recommended to separate vendor specific types and vendor specific instances into two or more namespaces. |
Mandatory |
Table 31 provides a list of namespaces and their indices used for BrowseNames in this document. The default namespace of this document is not listed since all BrowseNames without prefix use this default namespace.
Table 31 – Namespaces used in this document
|
NamespaceURI |
Namespace Index |
Example |
|
0 |
0:EngineeringUnits |
|
|
2 |
2:DeviceRevision |
|
|
3 |
3:MachineComponentsType |
(normative) OPC 40560 Namespace and mappings
Namespace and identifiers for OPC 40560 Information Model
This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this document. The identifiers are specified in a CSV file with the following syntax:
<SymbolName>, <Identifier>, <NodeClass>
Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId.
The BrowsePath for an Instance Node is constructed by appending the BrowseName of the instance Node to the BrowseName for the containing instance or type. An underscore character is used to separate each BrowseName in the path. Let’s take for example, the MiningEquipmentType ObjectType Node which has the add-in Identification object. The Name for the Identification InstanceDeclaration within the MiningEquipmentType declaration is: MiningEquipmentType_Identification.
The NamespaceUri for all NodeIds defined here is:
– http://opcfoundation.org/UA/Mining/General/
The CSV released with this version of the specification can be found here:
– http://opcfoundation.org/UA/schemas/Mining/General//1.0.0/NodeIds.csv
NOTE The latest CSV that is compatible with this version of the specification can be found here:
– http://opcfoundation.org/UA/schemas/Mining/General/NodeIds.csv
A computer processible version of the complete Information Model defined in this document is also provided. It follows the XML Information Model schema syntax defined in OPC 10000-6.
The Information Model Schema for this version of the specification (including any revisions, amendments or errata) can be found here:
– http://opcfoundation.org/UA/schemas/Mining/General/1.0.0/opc.ua.minig.general.nodeset2.xml
NOTE The latest Information Model schema that is compatible with this version of the document can be found here:
– http://opcfoundation.org/UA/schemas/Mining/General/opc.ua.minig.general.nodeset2.xml
(informative)Subdocuments of the OPC UA Companion Specification Mining
This appendix gives an overview of the constituent documents of the OPC UA Companion Specification Mining. The OPC UA Companion Specification Mining follows a multi-level document structure in Figure 1 and Figure 2 and explained in Chapter 4.2.
Extraction Equipment
Table 32 – Subdocuments of OPC 40561 Extraction Equipment
|
Document Name |
Document Number |
Description |
|
General |
OPC 40561-1 |
General Information about Extraction Equipment |
|
Shearer Loader |
OPC 40561-2 |
Machine specific information about the Shearer Loader machine |
Loading Equipment
Table 33 – Subdocuments of OPC 40562 Loading Equipment
|
Document Name |
Number |
Description |
|
General |
OPC 40562-1 |
General Information about Loading Equipment |
|
Hydraulic Excavator |
OPC 40562-2 |
Machine specific information about the Hydraulic Excavator machine |
Transport and Dumping Equipment
Table 34 – Subdocuments of OPC 40563 Transport and Dumping Equipment
|
Document Name |
Number |
Description |
|
General |
OPC 40563-1 |
General Information about Dumping Equipment |
|
Armored Face Conveyor |
OPC 40563-2 |
Machine specific information about the Armored Face Conveyor machine |
|
Rear Dump Truck |
OPC 40563-3 |
Machine specific information about Rear Dump Truck machine |
Mineral Processing Equipment
Table 35 – Subdocuments of OPC 40564 Mineral Processing Equipment
|
Document Name |
Number |
Description |
|
General |
OPC 40564-1 |
General Information about Mineral Processing Equipment |
|
Rock Crusher |
OPC 40564-2
|
Machine specific information about Rock Crusher machine |
Development and Support Equipment
Table 36 – Subdocuments of OPC 40565 Development and Support Equipment
|
Document Name |
Number |
Description |
|
General |
OPC 40565-1 |
General Information about Development and Support Equipment |
|
Roof Support System |
OPC 40565-2 |
Machine specific information about Roof Support System |
|
Dozer |
OPC 40565-3 |
Machine specific information about the Dozer machine |
Monitoring and Supervision Services
Table 37 – Subdocuments of OPC 40566 M&S Services
|
Document Name |
Number |
Description |
|
General |
OPC 40566-1 |
General Information about Monitoring and Supervision Services |
Planning, Execution, Logistics and Operation (PELO) Services
Table 38 – Subdocuments of OPC 40567 PELO Services
|
Document Name |
Number |
Description |
|
General |
OPC 40567-1 |
General Information about PELO Services |
|
Face Alignment System |
OPC 40567-2 |
System specific information about the Face Alignment System |
External Standards
Table 39 – Subdocuments of OPC 40568 External Standards
|
Document Name |
Number |
Description |
|
IREDES |
OPC 40568-1 |
Model description of the IREDES Compatibility Standard |
Companion Specification Mining: Application and Use Cases
Table 40 – Subdocuments of OPC 40569 Application and Use Cases
|
Document Name |
Number |
Description |
|
Longwall Operation |
OPC 40569-1 |
Description of Application and Use Cases for Longwall Operation |
|
Discontinuous Loading |
OPC 40569-2 |
Description of Application and Use Cases for Discontinuous Loading operations as part of the Load-and-Haul-Cycle |
|
Discontinuous Unloading |
OPC 40569-3 |
Description of Application and Use Cases for Discontinuous Unloading operations as part of the Load-and-Haul-Cycle |
|
Dozing |
OPC 40569-4 |
Description of Application and Use Cases for Dozing operations as part of the Load-and-Haul-Cycle |
___________