Day 1: May 20
Objective of Meeting
The morning sessions on Information Model Testing, AML, and the Execution Engine Management Feature Set. This was followed by an IOP Report Out and planning session for the IOP in October 2025. The afternoon sessions included planning for the OPAF Quarterly Newsletter and Blog Content, an Executive Session, and presentations on AutomationML. The day concluded with a Networking Reception hosted by The Open Group.
Summary
The session on Information Model Testing and AML focused on the current status and gaps in test case development for the O-PAS™ Standards. Testing exists for OCF-001 through OPC Foundation’s Conformance Test Tool (CTT), but no test cases have been initiated for the O-PAS 6.x parts. AML file testing is partially supported, with key components already testable. The goal is to align an OPC UA Companion Specification with the O-PAS Standard. General differences between the AML files were noted but not covered in detail during this session.
Outputs
Available testing currently includes AutomationML-defined elements, packaging, and certificate signing. Test content and model structure validation are still under development. Key suggestions included contracting the definition and scripting of test cases, hosting test scripts on official sites, and creating a checklist or guide for product certification applicants. The importance of defining testing expectations early and providing clear guidance for the community was emphasized.
Next Steps
Permission is needed from the O-PAS certification working group to begin contracting test suite development and to determine available funding. There is a need to coordinate test case development with the broader O-PAS Standard roadmap, especially considering dependencies among Parts 6.1 through 6.6. A joint IOP with OPC Foundation is proposed for early 2026, and planning for the October 2025 IOP will include finalizing logistics, participant requirements, and content. Additionally, a white paper will clarify the structural differences between UAFX and O-PAS AML implementations.
Links
All presentations are available here:
Day 2: May 21
Objective of Meeting
Morning sessions focused on EAWG Feature Sets and the Feature Set Work Process. The afternoon sessions covered a second Feature Set Working Session, reviewed the OPCF/OPAF MOCA Statement of Work, and discussed Part 5 System Management and Cybersecurity.
Summary
The EAWG session reviewed the role of the Enterprise Architecture Working Group (EAWG) in aligning the O-PAS Standard development through best EA practices. Feature sets, currently at Maturity Level 0, are internal to the forum and not publicly released. The session highlighted the need for traceability via Polarion ALM and the centralized role of feature sets in the O-PAS model. A charter and development alignment strategy were also presented.
Outputs
In working sessions, editors were tasked with deciding alarm facet placements in the specification, and Feature Set ID 41 was confirmed at ML4, needing backfill for ML1. Part 9 System Orchestration first draft is due mid-June, and will then advance to ML4 TWG review. The Feature Set Dashboard was updated and a new prioritization mechanism will be initiated. The MOCA agreement with OPC Foundation was reviewed, and a draft scope of work was generated in the meeting. The draft scope of work needs further review. Necessary O-PAS Standard parts for this work were listed, and IP ownership is to be clearly defined within the collaboration agreement (MOCA).
Next Steps
Weekly Forum meetings will be scheduled to review and prioritize feature sets. Part 4 and 6.3 editors will resolve alarm facet placement. Update and release Part 5 changes for 62443-4-2 compliance in 2025. AML calls rescheduled to resume on June 23rd to deliberate on Feature Sets 13–19.
Links
All presentations are available here:
Day 3: May 22
Objective of Meeting
The day started with sessions on Part 6.2 Basic Configuration and UAFX Integration. In the afternoon, discussions included a Roadmap Review, an outOrchestration Gap Analysis, and topics related to Part 9 Orchestratable Interfaces and System Orchestration.
Summary
The sessions covered several key areas of the O-PAS Standard development. Discussions included updates to Part 6.2, focusing on UAFX integration and basic configuration, a review of the overall roadmap, a system orchestration gap analysis, and progress on Part 9 related to orchestratable interfaces and the System Orchestration user guide, which is out for informal review now, closing Friday May 30. Action items were assigned to various individuals to address specific issues and advance the documentation.
Outputs
The group reached consensus on updating external standard references and the O-PAS Standard references to align with Semantic Versioning in Part 6.2. A new Section 6.7 may be added for the UAFX Connection Manager, and trademarking rules for OPC UA FX and UAFX will be implemented throughout the O-PAS standard. Eight open PRCRs for Part 6.2 need to be closed before the V2.2 publication. The roadmap will remain largely unchanged for now, pending end user feedback. The orchestration gap analysis highlighted the importance of idempotency, noting that it should be a requirement in the standard. An initial draft of the informative Part 9 System Orchestration specification is expected by mid-June, with publication projected by the end of 2025.
Next Steps
A call will be scheduled to review OCFBs and the Connection Manager for Part 6.2. New links are needed for the Part 6.2 XML files on the public GitLab® page. A call will be scheduled calendar for June 9th to review Part 6.1. The updated forum roadmap’s PPTX file needs to be located and forum cochairs should review it. BWG cochairs to lead the BWG in providing direction to the TWG on feature set prioritization. The Part 9 User Guide is currently under review, closing on May 30.
Links
All presentations are available here: