The GlassMachineType provides the information of the machine and is formally defined in Table 15. A Machine or system can contain other subsystems (e.g. other machines or devices). Such a complex system can be modelled with the component structure from OPC UA Machinery (see OPC 40000-1 section 11).

This GlassMachine object can be further divided into subtypes using the modular device structure from OPC UA for Machinery.

Table 15 – GlassMachineType Definition

Attribute	Value
BrowseName	GlassMachineType
IsAbstract	False
References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of the 0:BaseObjectType defined in OPC 10000-5
0:HasAddIn	Object	3:Components		3:MachineComponentsType	O
0:HasComponent	Object	ConfigurationRules		ConfigurationRulesType	M
0:HasComponent	Object	0:FileSystem		0:FileDirectoryType	M
0:HasAddIn	Object	2:Identification		GlassMachineIdentificationType	M
0:HasComponent	Object	3:MachineryBuildingBlocks		0:FolderType	M
0:HasComponent	Object	MaintenanceManuals		ManualFolderType	O
0:HasComponent	Object	OperationManuals		ManualFolderType	O
0:HasAddIn	Object	2:OperationCounters		3:MachineryOperationCounterType	M
Conformance Units
FlatGlass_GlassMachineType

3:Components contains components or submachines of the glass machine.

ConfigurationRules contains the properties that describe the machine configuration.

The FileSystem is the root of all file directories of the OPC UA and the underlying machine.

Note: While a direct coupling is not essential, aligning the file paths in both OPC UA 0:FileSystem and actual file systems is recommended (e.g. "/Directory1/FileA" in Unix and "ns=1;i=1001 Directory1/FileA" in OPC UA BrowsePath). Harmonizing OPC UA FileSystem with actual file systems is advised for a more intuitive and efficient work environment.

2:Identification contains the information to identify the glass machine. For more information see GlassMachineIdentificationType and OPC 40001-1(3:MachineIdentificationType).

3:MachineryBuildingBlocks contains all machinery building blocks. See Table 16 for more information.

MaintenanceManuals contains the manuals or the references to the manuals for the maintenance process.

OperationManuals contains the manuals or the references to the manuals for the operation process.

2:OperationCounters provides the information, how long a MachineryItem is turned on and how long it performed an activity

The components of the GlassMachineType have additional references which are defined in Table 16.

Table 16 – GlassMachineType Additional References

SourceBrowsePath	Reference Type	Is Forward	TargetBrowsePath
3:MachineryBuildingBlocks	0:HasAddIn	True	2:OperationCounters

The components of the GlassMachineType have additional subcomponents which are defined in Table 17.

Table 17 – GlassMachineType additional subcomponents

BrowsePath	References	NodeClass	BrowseName	DataType	TypeDefinition	Others
3:MachineryBuildingBlocks	0:HasAddIn	Object	3:MachineryItemState		3:MachineryItemState_StateMachineType	M
3:MachineryBuildingBlocks	0:HasAddIn	Object	3:MachineryOperationMode		3:MachineryOperationModeStateMachineType	M
3:MachineryBuildingBlocks	0:HasAddIn	Object	5:JobManagement		5:JobManagementType	M

OPC 10031-4 defines mechanisms to add job order information using the 2:ISA95JobOrderDataType and mechanisms getting the result or current status of the job order using the 2:ISA95JobResponseDataType. Both DataTypes define arrays of properties of a job order: general, personal, equipment, physical assets, and material. The 2:ISA95JobOrderDataType uses the general properties to describe the job order and the other properties to define the requirements, whereas the 2:ISA95JobResponseDataType uses the general properties to describe the output and the other properties to provide the information what has been used.

OPC UA Machinery Job Management (OPC 40001-3) standardizes some of those parameters, which are application-specific from the view of OPC 10031-4.

The guidelines and extensions specified in this section are designed to complement the foundational models, providing a structured framework for implementation. The Optional element (e.g. fields or parameters) of the OPC 10031-4 or OPC 40001-3 may be used as defined.

The WorkMasterID field of the ISA95JobOrderDataType contains the information about the WorkMaster (e.g. the recipe). The field ID is an identification of the Work Master. This should be used to identify a work master cross different opc ua server and must be unique its scope (e.g. company unique).

This specification use the 0:FileSystem folder to manage(e.g. upload /download files) the work master files on the server. To connect the WorkMasterID with the file additional predefined key-value pairs for 2:ISA95WorkMasterDataType.Parameter are defined in Table 18.

Table 18 – Predefined WorkMaster Parameters

ID	DataType of Value	Description	EngineeringUnits	Subparameters
LocalPath	String	Contains the file path on the OPC UA server. This must be identical with the relative path of the BrowsePath.	-	-
FileNodeId	0:NodeID	Contains the NodeId of the object of the file.	-	-
FileFormat	FileFormatType	Defines the file format of the work master file. This is used to ensure compatibility between the work master and the machine.

Note: Example of the LocalPath could be "/Directory1/FileA" with the corresponding BrowsePath as "{ StartingNode :”ns=1;s=FileSystem”; RelativePath: “Directory1/FileA"}”. It is recommended that the local file system also has a directory “../Directory1/FileA".

Note: A restart may change the nodeid of the file. So it is recommended to check the FildeNodeID before using the file in a WorkMaster. If possible use the LocalPath instead.

Note: The LocalPath must be used in a WorkMaster and the other Parameters are optional.

The following 2:ISA95JobOrderDataType fields shall be used:

• MaterialRequirements
• Priority
• StartTime
• EndTime

The following 2:ISA95JobOrderDataType fields may be used if the relevant information is available:

• JobName

This specification standardizes some of those parameters, which are application-specific from the view of OPC 10031-4.

In Table 19, predefined key-value pairs for 2:JobOrderParameters and 2:JobResponseData is provided. The table indicates, in which data structure the key-value pair is expected to be used. An “X” in “In” indicates it may be used in 2:JobOrderParameters an “X” in “Out” indicates it may be used in 2:JobResponseData.

Table 19 – Predefined JobOrderParameters and JobResponseData

ID	DataType of Value	Description	EngineeringUnits	Subparameters	In	Out
ReasonForSubState	ReasonDescriptionType	Provides an explanation for the current status of the job. This information may be used, for instance, to detail why the server is unable to perform a particular job.	-	-	x	x

The following 2:ISA95JobOrderDataType fields shall be used:

• ActualMaterial
• StartTime
• EndTime

The following 2:ISA95JobOrderDataType fields may be used if the relevant information is available:

• JobName