Necessary use of multiple software tools to create and consume model-based definition (MBD) data in different, often proprietary, formats results in substantial non-value-added integration costs for the aerospace and defense (A&D) industry. An open, vendor-neutral standard format as the common language is critical. Multi-company members of the Aerospace & Defense PLM Action Group (AD PAG) tested ISO 10303-242 (STEP AP242) and commercial translation tools that support data exchange and interoperability requirements for existing MBD design processes. This paper presents MBD element descriptions and support-level results. The AD PAG concluded that identified gaps in the standard and translation tools limit MBD adoption. Therefore, it’s imperative that standards communities and PLM software providers work with the A&D industry to bridge the gaps, ensuring protection of A&D legacy data and processes.

Minimum Model-Based Definition (MBD) for Type Design Certification is important to the Aerospace and Defense industry because multiple and ever-changing engineering and manufacturing software tools used to design and produce a product add time and cost by requiring data representation changes to maintain a current definition of the product.

This position paper captures the list of minimum data items required for standard MBD for Type Design Certification. The paper identifies the necessary Part Types and data items within each that are needed to develop, build, and certify the product. The paper first presents use cases As Is today without model-based definition support, including the business impact. The paper then lists To Be (desired state) use cases once minimum MBD requirements are met, including the business benefits. This latest release of the paper identifies specifics of the minimum required list of data items necessary for minimum MBD support. Terms in this paper are defined in a common AD PAG Glossary on the AD PAG web site (www.ad-pag.com).

Note: There are CAD models support this paper. The models will be available on this website in the future.

Members of an A&D multi-company project team are defining the minimum data content in MBD-type design required to meet manufacture, inspection, and regulatory certification requirements. The Group has focused on ISO 10303-242 (STEP AP242), ISO 14306 (JT), and ISO 32000/14739 (PRC for 3D PDF), and commercial translation tools that support data exchange and interoperability requirements for existing MBD design processes. This presentation will describe the status of their work, and their plan to present detailed requirements, promote adoption, and achieve compliance within the PLM ecosystem.

This presentation will share work undertaken by members of the A&D PLM Action Group to define the minimum data content in MBD type design that is required to meet regulatory requirements, and evaluate existing standards and tools to provide an industry standard data delivery process to regulatory agencies.

The A&D PLM Action Group has taken steps to examine the digital thread and explore the art of the possible for certifying commercial aircraft designs in an industry consistent manner. This presentation will examine the elements of the digital thread and the group’s thoughts on a consistent approach to certification relevant data.

The intent of this document is to provide the basis for productive dialogue within the A&D PLM community. Initial distribution will be to a select set of PLM solution providers with a request for response and support. However, this is only the first in what will be a series of position papers that address the topic in ever increasing detail, ultimately resulting in a detailed requirements statement. Through this progression, it is the intent of the A&D PAG members to engage the broader PLM community in dialogue.

Phase 3 of the Model-Based Systems Engineering (MBSE) interoperability project evaluates the business context and tool alternatives for exchanging requirements and architecture representations depicting systems and system components. It attempts to identify the minimum content that must be exchanged based on popular authoring technologies. The project distinguishes the use cases that describe the exchange scenarios and the most appropriate technical data needed for interoperability. A mapping between two major modelling languages, SysML and ARCADIA, is defined for each use case. The outcome was a scoring of capabilities needed to implement a full-scale solution across a multi-tier supply chain. The project was based on the following problem statement and objective.

The intent of this document is to convey the current state of data interoperability in the industry, to identify an interim solution, and to influence future solutions and best practices for MBSE model interchange that enable model-based collaboration across the A&D supply chain. This position paper reviews the various alternatives considered by the group and makes initial recommendations on the most promising approaches to enable OEM–supply chain design collaboration based on both short- and long-term MBSE standards.