20 ProductionDatasetManagementType

20.1 General

Production datasets are used for the configuration of machines. They are stored in files which can be exchanged over the network (e.g. between a machine and MES). This chapter defines methods and events for the exchange of lists of available production datasets and for the transfer of the files themselves.

NOTE: Transferred production datasets are always complete and consistent (includes data for the core machine and connected peripheral equipment, e.g. robot). As the production dataset files themselves are not standardized, a set of metadata is included in the ProductionDatasetInformationType (see 20.4.4).

20.2 ProductionDatasetManagementType Definition

This ObjectType is a container for the functionalities related to the listing and exchange of production datasets. It is formally defined in Table 102.

20.3 ProductionDatasetStatusType

20.3.1 ActiveProductionDatasetStatus, ProductionDatasetInPreparationStatus

This Object represents the status of the production dataset which is active in the control system of the machine or in preparation (in analogy to ActiveJob and JobInPreparation). The ProductionDatasetStatusType is formally defined in Table 103.

NOTE: Production datasets are manufacturer specific files which contain settings of production parameters for the machine and for connected peripheral devices.

20.3.2 Information

The Information Property represents a set of information on the production dataset.

20.3.3 Modified

The Modified Property informs if the production dataset has been changed after the last storage.

NOTE: This information is only valid for the machine directly connected to the client. If the dataset also includes parameters for peripheral devices to that machine, changes in the peripheral devices might not be recognized.

20.3.4 Frozen

The Frozen Property indicates whether changes in the production dataset are not allowed. If TRUE, no changes on the machine in the production dataset (change of process parameters) are allowed.

NOTE: This information is only valid for the machine directly connected to the client. If the dataset also includes parameters for peripheral devices to that machine, changes in the peripheral devices might still be possible.

20.3.5 Load

The Method Load loads a production dataset from the file system of the machine to the control of the machine. As production datasets can contain parameter settings not only for the machine itself but also for peripheral equipment (e.g. robots/handling devices), the parts of the production dataset which shall be activated can be chosen.

Signature

	Load (
		[in]	0:String	Name
		[in]	0:UInt16[]	Components);

20.3.6 Save

The Method Save stores a production dataset from the control of the machine to the file system of the machine.

Signature

	Save (
		[in]	0:String	Name);

20.4 ProductionDatasetLists

The Object ProductionDatasetLists is used to exchange information on the available production datasets on client and server.

The Object ProductionDatasetLists can fire an Event RequestProductionDatasetList to initiate a call of SendProductionDataList by the MES.

20.4.1 GetProductionDatasetList

This Method is used to read a list from the server which production datasets are available on the machine's file system (e.g. for a check before an activation or transfer of a production dataset is initiated). The NameFilter and MouldId can be used to reduce the length of the list or for a targeted search.

Signature

	GetProductionDatasetList ( 
		[in]	0:String	NameFilter
		[in]	0:String	MouldId
		[out]	ProductionDatasetInformationType[]	ProductionDatasetList);

20.4.2 SendProductionDatasetList

This Method is used to send a list of production datasets available on the client to the server.

Signature

	SendProductionDatasetList ( 
		[in]	ProductionDatasetInformationType[]	ProductionDatasetList);

It is possible to call the Method without an InputArgument (length of the array ProductionDatasetList is zero) as an answer to the Event RequestProductionDatasetList (see below) if no production dataset which fits the NameFilter and/or MouldId transferred with the event is available.

20.4.3 RequestProductionDatasetList

The Object ProductionDatasetLists can fire an Event RequestProductionDatasetListEventType to initiate a call of SendProductionDatasetList by the client. This can for example be triggered by an operator who wants to load a production dataset not existing on the server.

The MouldFilter and MouldId parameters which can be used to reduce the length of the list or for a targeted search is used in the same way as in the Method GetProductionDatasetList defined in 20.4.1.

20.4.4 ProductionDatasetInformationType

This structure provides information on a production dataset. It does not contain the production dataset file itself.

NOTE: This meta data shall also be included in the production dataset file itself.

NOTE: The list will be extended when further OPC UA models for other machine types are developed.

20.5 ProductionDatasetTransfer

20.5.1 General

OPC UA Part 5 defines a TemporaryFileTransferType for the representation of file transfers. This Type is used for the transfer of production datasets.

20.5.2 GenerateOptions in GenerateFileForRead

For the GenerateOptions in the Method GenerateFileForRead the DataType ProductionDatasetReadOptionsType as defined below shall be used.

20.5.3 GenerateOptions in GenerateFileForWrite

For the GenerateOptions in the Method GenerateFileForWrite the DataType ProductionDatasetWriteOptionsType as defined below shall be used.

This Enumeration is defined as a Mask. With this, writing to several destinations with one Method call is possible (e.g. StorageEnumeration = 6 writes the production dataset to the file system and the preparation layer of the control system.

NOTE: It is possible that the machine does not support all storage options (e.g. only writing to file system allowed). In this case, the server will return the StatusCode Bad_InvalidArgument when calling the GenerateFileForWrite Method with a not supported value for Storage.

20.6 Events for ProductionDatasetTransfer

RequestProductionDatasetRead and RequestProductionDatasetWrite are Events to trigger a file transfer by the machine/server (e.g. initiated by the operator).

Storage: Indication from where the dataset is read. Although StorageEnumeration is defined as a Mask, here only the values 1, 2 and 4 are allowed (no combination).

Name: Name of the production dataset that should be transferred from the server to the client. This parameter is only relevant, if Storage is 4 (FILE_SYSTEM).

Name: Name of the production dataset that should be transferred from the client to the server.

Storage: Indication where the dataset is written to.

Components: Array which indicates which parts of the production dataset shall be activated in the machine control after writing. Only valid if Storage is CONTROL_SYSTEM_1 or FILE_AND_CONTROL_SYSTEM_2. Array of UInt16. See possible values in Table 115. If Components has the array length 0 then complete production dataset is activated.

20.7 GetProductionDatasetInformation

This Method allows reading the description of a production dataset during the file transfer from the server to the client with ProductionDatasetTransfer. It may only be called between receiving the fileHandle generated by GenerateFileForRead and closing the file.

Signature

	GetProductionDatasetInformation (
		[in]	0:UInt32	fileHandle
		[out]	ProductionDatasetInformationType	Information);

20.8 SendProductionDatasetInformation

This Method allows sending of the description of a production dataset during the file transfer from the client to the server with ProductionDatasetTransfer. It may only be called between receiving the fileHandle generated by GenerateFileForWrite and closing the file.

Signature

	SendProductionDatasetInformation (
		[in]	0:UInt32	fileHandle
		[in]	ProductionDatasetInformationType	Information);