OAGi Working Groups

Welcome to the OAGi Working Groups page. The best way to engage with OAGi is to participate and/or lead a Working Group.

If you are interested in joining any of these Working Groups, or in starting a new Working Group, please write to us.

OAGi has a specific, repeatable development process that all of these Working Groups follow. It contains four phases:

  1. Project Definition
  2. Construction
  3. Review and Approval
  4. Publication

You can learn more about or development methodology.

Participation on Working Groups is a privilege of membership. If you are not already an OAGi member, you can learn more.

AIA and EBO Harmonization Working Group

The Chair for this Working Group is Scott Nieman from Land O’Lakes. The companies that are the members of this Working Group include:

  • Land O’Lakes
  • Oracle
  • National Institute of Standards and Technology
  • Archer Daniels Midland
  • Boeing
  • iBASEt

The Scope of this Working Group includes:

  • Provide an intake, review and migration process for Oracle submission of Application Integration Architecture Enterprise Object Library common XSDs
  • Identify overlaps with existing OAGIS capabilities
  • Identify capabilities that would benefit OAGIS
  • Prioritize work effort based on actual industry use
  • Import into Semantic Refinement staging tables for conversion
  • Selectively convert to 10.x
  • Provide generalized mappings from AIA to OAGIS for migration; review of submitted subsets of actual used EBO XML nodes

Quality Content Working Group

Quality Content Working Group is now in hiatus, and will convene for maintenance requests. The working group uplifted noun submissions by Infor to the 10.x platform, creating new OAGIS Nouns for quality and test related activities and integrations. Integrations may be between a Product Lifecycle Management system, Laboratory Information Management System, ERPs, Quality Management systems, and external Third Party Laboratories that perform testing services. Corrective Action resolution capabilities based on repeated Item instance nonconformance were added to the scope of work to complete the lifecycle. Future nouns may evolve over time. Topics of interest include Sampling Protocol, Sampling Plan, and Equipment Maintenance, which will draw upon research completed by the Smart Manufacturing Working Group.

OAGIS NounReleasedScope
TestMethodReleased 10.2.1
TestSpecificationReleased 10.2.1
InspectionOrderReleased 10.2.1
Changed in 10.4
Added Geospatial capabilities in 10.3
Added status inquiry capabilities in 10.4
TestResultsReleased 10.2.1
Changed in 10.3
CorrectiveActionRequestReleased in 10.3
CorrectiveActionPlanReleased in 10.3
CorrectiveActionReleased in 10.3
ItemNonconformanceReleased in 10.0

Semantic Refinement Working Group

The Working Group Chair for the Semantic Refinement WG is Serm Kulvatunyou from NIST. It plans to do this by developing an RDMS design to support the OAGIS Data Model so that OAGi can better:

  • Allow for import of OAGIS developer schemas
  • Allow for precise content contextualization
  • Implement a prototype, open source tool, which in addition to above requirements:
    • Allow for export of OAGIS contextualized standalone schema
    • Allow for import of OAGIS contextualized standalone schema

The database has been designed and OAGIS has been loaded in and is being debugged. The expression generation software is under construction. IT is planned to support expression generation from context drivers defined in the tool.

Smart Manufacturing Working Group

This Working Group is Co-Chaired by Nenad Ivezic of NIST and Conrad Leiva from iBASEt.

Scope: To Develop a multi-tiered supply chain collaboration guideline and standard for engineered components to improve cost, quality, agility and more.

Mobile, Cloud, and JSON Working Group

This Working Group is Chaired by Mike Rowell from Oracle.

The purpose of this Working Group is to explore ways that the OAGIS Specification and deliverables need to be updated to more fully enable Mobile Business, Cloud Computing, and support for JSON based instance expressions of the current Business Object Documents.

The Working Group may include but is not limited to the following:

  • JSON based instances of the OAGIS BODs
  • A JSON tool converter
  • JSON Naming and Design Rules similar to the current OAGIS XSD Naming and Design Rules
  • REST processing guide for OAGIS
  • Changes to the OAGIS BOD architecture to provide improved support for cloud-based processing. For example, in the BOD Application Area. This could include additions from the current UN/CEFACT Business Data Header project
  • Mobile Business Case Studies as examples
  • Working with Solution Providers to support OAGIS JSON based apps on mobile devices
  • OAGIS Apps for mobile devices from OAGi and its members