OPC 10031-4: ISA-95-4 Job Control


Released 1.00

2021-05-12


image001.pngimage002.png

image003.pngOPC UA Companion-Specification

OPC 10031-4

OPC UA for ISA-95 Part 4: Job Control

Release V1.00.0

2021-05-09

Specification Type:

Industry Standard Specification

Comments:

DocumentNumber

OPC 10031-4

Title:

OPC UA for ISA-95 Part 4 :Job Control

Date:

2021-05-09

Version:

Release V1.00.0

Software:

MS-Word

Editors:

Pipero, Costantino

Brandl, Dennis

Source:

OPC 10031-4 - UA Companion Specification for ISA-95 Job Control V1.00.0.docx

Author:

OPEN-SCS

Status:

Release

CONTENTS

Page

Figures i

Tables i

1Scope 1

2Normative References 1

3Terms, abbreviated terms, and conventions 1

3.1Overview 1

3.2OPC UA for ISA-95 Terms 1

3.3Abbreviated terms 1

3.4Conventions used in this document 1

3.4.1Conventions for Node descriptions 1

3.4.2NodeIds and BrowseNames 1

3.4.3Common Attributes 1

4ISA-95 Overview 1

4.1Overview 1

4.2Job Order 1

4.3Job Order Information Model 1

4.4Job Response 1

5Modelling Approach of ISA-95 1

6ISA-95 Data Representation Model 1

6.1General 1

6.2ObjectTypes 1

6.2.1ISA95JobOrderReceiverObjectType 1

6.2.2ISA95JobResponseProviderObjectType 1

6.2.3ISA95JobResponseReceiverObjectType 1

6.3DataTypes 1

6.3.1ISA95EquipmentDataType 1

6.3.2ISA95JobOrderDataType 1

6.3.3ISA95JobResponseDataType 1

6.3.4ISA95MaterialDataType 1

6.3.5ISA95PersonnelDataType 1

6.3.6ISA95PhysicalAssetDataType 1

6.3.7ISA95PropertyDataType 1

6.3.8ISA95ParameterDataType 1

6.3.9ISA95ReturnEnum 1

6.3.10ISA95WorkMasterDataType 1

6.3.11ISA95JobOrderCommandEnum 1

6.3.12ISA95JobOrderStateEnum 1

7Profiles and Conformance Units 1

7.1Conformance Units 1

7.2Profiles 1

7.2.1Profile list 1

7.2.2Server Facets 1

7.2.3Client Facets 1

8Namespaces 1

8.1Namespace Metadata 1

8.2Handling of OPC UA Namespaces 1

Annex A (normative): ISA95 Job Control Namespace and mappings 1

A.1Namespace and identifiers for ISA95 Information Model 1

Annex B OPC UA Method result Codes 1

B.1Method Result Codes (Informative) 1

B.2Job Order Method Return Status Codes 1

Annex C (Informative): Example Job Orders 1

C.1Simple Job Order 1

C.2Job Order with Packaging Master Data 1

Bibliography 1

Figures

Figure 1 – Work Schedule, Work Request, and Job Orders 1

Figure 2 – Job Order Information Model 1

Figure 3 – Job Response Information Model 1

Figure 4 – Job Order Receiver Object Type Methods and Data 1

Figure 5 – ISA95JobResponseProvider Methods 1

Figure 6 – ReceiveJobOrder and RequestJobResponse Transaction Example 1

Figure 7 – ISA95JobResponseReceiverObjectType 1

Figure 8 – ReceiveJobOrder and ReceiveJobResponse Transaction Example 1

Tables

Table 1 – Examples of DataTypes 1

Table 2 – Type Definition Table 1

Table 3 – Examples of Other Characteristics 1

Table 4 – <some>Type Additional References 1

Table 5 – <some>Type Additional Subcomponents 1

Table 6 – <some>Type Attribute values for child Nodes 1

Table 7 – Common Node Attributes 1

Table 8 – Common Object Attributes 1

Table 9 – Common Variable Attributes 1

Table 10 – Common VariableType Attributes 1

Table 11 – Common Method Attributes 1

Table 12 – ISA95JobOrderReceiverObjectType AddressSpace Definition 1

Table 13 – ReceiveJobOrder Method Arguments 1

Table 14 – ReceiveJobOrder Method AddressSpace Definition 1

Table 15 – ISA95JobResponseProviderObjectType AddressSpace Definition 1

Table 16 – RequestJobResponse Method Arguments 1

Table 17 – RequestJobResponse Method AddressSpace Definition 1

Table 18 – ISA95JobResponseReceiverObjectType AddressSpace Definition 1

Table 19 – ReceiveJobResponse Method Arguments 1

Table 20 – ReceiveJobResponse Method AddressSpace Definition 1

Table 21 – ISA95EquipmentDataType Structure 1

Table 22 – ISA95EquipmentDataType AddressSpace Definition 1

Table 23 – ISA95JobOrderDataType Structure 1

Table 24 – ISA95JobOrderDataType AddressSpace Definition 1

Table 25 – ISA95JobResponseDataType Structure 1

Table 26 – ISA95JobResponseDataType AddressSpace Definition 1

Table 27 – ISA95MaterialDataType Structure 1

Table 28 – ISA95MaterialDataType AddressSpace Definition 1

Table 29 – ISA95PersonnelDataType Structure 1

Table 30 – ISA95PersonnelDataType AddressSpace Definition 1

Table 31 – ISA95PhysicalAssetDataType Structure 1

Table 32 – ISA95PhysicalAssetDataType AddressSpace Definition 1

Table 33 – ISA95PropertyDataType Structure 1

Table 34 – ISA95PropertyDataType AddressSpace Definition 1

Table 35 – ISA95ParameterDataType Structure 1

Table 36 – ISA95ParameterDataType AddressSpace Definition 1

Table 37 – ISA95ReturnEnum values 1

Table 38 – ISA95WorkMasterDataType Structure 1

Table 39 – ISA95WorkMasterDataType AddressSpace Definition 1

Table 40 – ISA95JobOrderCommandEnum values 1

Table 41 – ISA95JobOrderStateEnum values 1

Table 42 – Conformance Units for OPC 30261 ISA-95 Job Orders 1

Table 43 – Profile URIs for OPC 30261 ISA-95 Job Orders 1

Table 44 – Profile Overview 1

Table 45 – ISA-95 Job Control Base Server Profile 1

Table 46 – ISA-95 Job Order Receiver Server Profile 1

Table 47 – ISA-95 Job Response Provider Server Profile 1

Table 48 – ISA-95 Job Response Receiver Server Profile 1

Table 49 – ISA-95 Job Control Base Server Profile 1

Table 50 – Job Order Receiver Client Profile Definition 1

Table 51 – Job Order Response Provider Client Profile Definition 1

Table 52 – Job Order Response Receiver Client Profile Definition 1

Table 53 – NamespaceMetadata Object for this Specification 1

Table 54 – Namespaces used in an ISA 95 Job Control Server 1

Table 55 – Namespaces used in this document 1

Table 56 – OPC UA Method Result Codes 1

Table 57 – ISA-95 Methods Return Status Codes 1

OPC FOUNDATION

____________

UNIFIED ARCHITECTURE

FOREWORD

This specification is the specification for developers of OPC UA applications. The specification is a result of an analysis and design process completed by the OPC Foundation member organizations to develop a standard interface to facilitate the development of applications by multiple vendors that shall inter-operate seamlessly together.

Copyright © 2006-2021, OPC Foundation, Inc.

AGREEMENT OF USE

COPYRIGHT RESTRICTIONS

This document is provided "as is" by the OPC Foundation.

Right of use for this specification is restricted to this specification and does not grant rights of use for referred documents.

Right of use for this specification will be granted without cost.

This document may be distributed through computer systems, printed or copied as long as the content remains unchanged and the document is not modified.

OPC Foundation does not guarantee usability for any purpose and shall not be made liable for any case using the content of this document.

The user of the document agrees to indemnify OPC Foundation and their officers, directors and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this specification.

The document shall not be used in conjunction with company advertising, shall not be sold or licensed to any party.

The intellectual property and copyright is solely owned by the OPC Foundation.

OPC Foundation members and any non-members are prohibited from copying and redistributing this specification. All copies must be obtained on an individual basis, directly from the OPC Foundation Web site http://www.opcfoundation.org.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC specifications may require use of an invention covered by patent rights. OPC shall not be responsible for identifying patents for which a license may be required by any OPC specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you.

RESTRICTED RIGHTS LEGEND

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer is the OPC Foundation,. 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830

COMPLIANCE

The OPC Foundation shall at all times be the only entities that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials. Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

TRADEMARKS

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of the State of Minnesota, excluding its choice or law rules.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.