Overview

The abridged version of the development process specifies the steps necessary to create ontologies based on an agile, iterative process. The process begins with collecting epics from working groups, users, and domain experts to guide development.

...

Technical Oversight Board

...

Epics

Working groups create or add Epics to the TOB and MAY add an Epic to the Working Group to organize user scenarios for each area of concern. The TOB checks cross-cutting concerns with each working group. The working group WG MUST link Epics to the TOB Epics.

...

• The high-level topics and concerns the working groups need to address.

• Known dependencies on this Epic by other groups and if other Epics are blocked.

• An estimate of the complexity of the Epic.

• The necessary stakeholders in each domain to create use cases.

Examples

• Title: Supply chain resistance. The manufacturing supply chain needs to reduce the dependency on a single source of parts because of areas of vulnerability that prevent a surge in production or incur delays due to a lack of available capabilities. To address this problem, standards are needed to provide capability-based agile manufacturing support for dynamic just-in-time sourcing, planning, scheduling, and executing from the supply chain, engineering, and manufacturing processes across the industrial base.

• Title: Lifecycle product data. The current manufacturing information systems cannot capture the lifecycle of products and all their parts to support the archival and retrieval of products across their complex mereological structure. To address this, the industry requires information across the entire product and lifecycle, including design, manufacturing, maintenance, and end-of-life, to understand how something was made and the provenance of the parts.

...