Draft:Open Process Automation Standard
This article, Draft:Open Process Automation Standard, has recently been created via the Articles for creation process. Please check to see if the reviewer has accidentally left this template after accepting the draft and take appropriate action as necessary.
Reviewer tools: Preload talk Inform author |
| O-PAS Standard | |
|---|---|
| Open Process Automation Standard | |
| Status | Published |
| First published | 2019 |
| Latest version | 2.1 February 2023 |
| Organization | The Open Group |
| Domain | Industrial Control System Manufacturing |
| License | 90-Day Evaluation License Member License Commercial License Non-commercial License |
| Website | https://publications.opengroup.org/standards/opa |
The Open Process Automation Standard (O-PAS standard) is developed by the Open Process Automation Forum (OPAF) and published by The Open Group.[1] It defines a standards-based, open, secure, and interoperable process control architecture.[2][3] As an open standard it addresses the business problem of proprietary lock-in experienced by companies that use industrial control systems.[4] The standard enables innovation in the process automation market.[5] The scope of the standard currently excludes safety instrumented systems and field devices[6] like instrumentation and actuators.
O-PAS System Attributes
[edit | edit source]The O-PAS standard defines 23 quality attributes[7][8], three of which are foundational quality attributes: safety, reliability, and securability[9]
| Attribute | Description |
|---|---|
| Safety | The expectation that a system or component does not, under defined conditions, lead to a state in which human life, health, property, or the environment is endangered. |
| Reliability | The ability of a system or component to perform its required functions under stated conditions for a specified period of time. |
| Securability | The ability of a system or component to be protected against unauthorized access or modification throughout its lifecycle |
The O-PAS standard Part 1 focuses on an additional four quality attributes that are critical to success: interchangeability, interoperability, portability, and modularity[9][8].
| Foundational |
Safety | ||
| Key |
Interchangeability | ||
| General |
Availability |
Flexibility |
Scalability |
History
[edit | edit source]| Version | Designation | Released | References |
|---|---|---|---|
| 1.0 | Preliminary | February 2019 | [10][11][12] |
| 1.0 | Final | December 2019 | [13] |
| 2.0 | Preliminary | February 2020 | [14][15] |
| 2.1 | Preliminary | May 2021 | [16] |
| 2.1 | Final | February 2023 | [17] |
| 2.1 | Technical Corrigendum 1 | August 2024 | |
| 3.0 | Not yet released | [18] |
Structure of the O-PAS Standard
[edit | edit source]The O-PAS standard is available to the public for download free of charge on the publisher's website.[19] The standard contains 14 different chapters where each part addresses a different topic and a glossary[20][21][22][23]
Part 1 Technical Architecture
- A technical overview of the technology and how the entire standard addresses the goals of the architecture
Part 2 Security
- Provides an overview of how the IEC 62443 standard is integrated into the O-PAS standard
Part 3 Profiles
- Details groupings of features and functions in all parts of the standard where product suppliers are expected to demonstrate conformance. Including how products will be tested and certification be granted
Part 4 Connectivity Framework
- Details how the connectivity framework defined in the O-PAS standard is based on OPC Unified Architecture
Part 5 System Management
- Details how the Redfish standard, published by DMTF, is integrated into the standard.[24] The section explains what information should be exposed by software programs, hardware platforms, and other system components
Part 6 Information & Exchange Models
- Part 6.1 Overview and Interfaces
- Part 6.2 Basic Configuration
- Part 6.3 Alarm and Events Configuration
- Part 6.4 Function Blocks
- Part 6.5 IEC 61499
- Part 6.6 IEC 61131
Part 7 Physical Platform
- Defines how the O-PAS standard approaches integration of the InterEdge standard[25] that is developed and published by PICMG
Part 8 Application Portability
- Details the approach to application portability, which will provide end users the ability to move applications, intellectual property, and control strategies between different systems. This document has not been published
Part 9 System Orchestration
- Published in February 2024, the document is informative and currently available in snapshot form.[26][27] The document publicly communicates the direction and path to defining a standard around system orchestration. Specifically, system orchestration management to automate functions and give systems the ability to rebalance workloads to ensure desired system performance, improve reliability, and improve system resiliency
Reference Implementations
[edit | edit source]The Open Process Automation Forum seems to be aware of the technology life cycle and technology adoption life cycle in efforts to boost industry adoption[28]. A number of reference implementations, proofs of concept, field trials, and test beds have been developed in accordance with the O-PAS™ standard. Publicly announced implementations are listed alphabetically below:
- ExxonMobil Test Bed[29] and Field Trial[30] and Commercial Deployment[31][32]
- Georgia Pacific Demonstration Board[33]
- Petroleum Development Oman Field Pilot[34]
- Petronas Test Bed and Field Trial[35][36]
- Reliance Industries Test Bed[36]
- Saudi Aramco Test Bed[37]
- Shell Test Bed[36]
- Texas A&M University, Department of Nuclear Engineering[38]
Certification and Test Tools
[edit | edit source]O-PAS certification is due to launch in Q4 of 2024.
The certification program requires third party verification for each O-PAS Profile. This must be done by O-PAS Recognized Verification Labs. The exceptions to this rule are for those requirements that involve other certification bodies. The OPC UA Connectivity Profile (OCF-001) and Global Discovery Service (GDS-001) are two profiles that must be verified by the OPC Foundation.
In June 2024, the OPC Foundation announced availability of verification for OCF-001 and GDS-001 O-PAS profiles in the OPC UA Profile Reporting Application.[39][40]
Each Profile requires the SEC-F-001 Security Facet. This facet is derived from the ANSI/ISA-62443-4-2 SL2 security requirements. In order to verify this facet, the supplier must use an ISASecure Lab[41]. In August 2024, the forum selected ISASecure as the exclusive verification provider for security requirements[42].
Academic, Technical, and White Papers
[edit | edit source]- Open Process Automation is Gaining Sustainable Momentum (January 2023)
- Open Process Automation- and Digital Twin-Based Performance Monitoring of a Process Manufacturing System (June 2022)
- Comparison and Alignment of OPAS and MTP Concepts (April 2022)
- Open Process Automation: A standards-based, open, secure, interoperable process control architecture (July 2020)
- Legacy Control System Transition into the IIoT Era (August 2017)
References
[edit | edit source]- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).[non-primary source needed]
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Rahamtallah, M., Abri, A., Abdel Rahman, W., and Q. AlZain. "Building the Next-Generation Process Automation System: An O-PAS Field Pilot Initiative Between Schneider Electric & Petroleum Development Oman." Paper presented at the International Petroleum Technology Conference, Dhahran, Saudi Arabia, February 2024. doi: https://doi.org/10.2523/IPTC-24610-EA
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ url=https://isasecure.org/certification/certify-now
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).