To learn more, contact:
Any A&D PLM Action Group Member or:
Our stated mission is to:
The Aerospace & Defense PLM Action Group is working on several strategic projects and has developed a series of position papers and other publications that are freely available for downloading. For the full list of publications that are available to please visit our publications page.
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.
An Aerospace & Defense PLM Action Group (AD PAG) sponsored project team proposed validating their recently defined Multiple-view Bill of Materials (Multi-view BOM) requirements by benchmarking use cases using commercially available PLM software. Domain experts from eight AD PAG member companies and one Tier 1 supplier engaged with four leading software providers to execute the benchmarks. Results were consolidated, analyzed, and configured to enable each of the participating software providers to have visibility to the benchmark scores for their solution, while publicly reported results were generalized to mask specific solution performance. This report documents the definition of use cases that encapsulate requirements for Multi-view BOM management within an aerospace OEM, and the findings and conclusions from evaluating the capability of commercially available PLM software to fulfill those requirements. The report concludes that the use cases are valid, and that commercial technology has matured to a level where implementation of Multi-view BOM management within an aerospace OEM is a practical possibility, albeit with caveats.
The terminology used within the aerospace and defense (A&D) industry for product lifecycle management (PLM) concepts, processes, and artifacts is extensive and complex. When the A&D PLM Action Group (AD PAG) was founded in 2014 with the mission to identify and remediate common PLM-related pain points, one of the first problems that the members confronted was the communication barrier posed by inconsistent use of language. Over the years, AD PAG project teams have published reports and position papers on a range of topics. In this document, the AD PAG project teams have collaborated to create a comprehensive, common glossary that applies across all of their projects’ work products. This glossary of acronyms and terms draws from industry standard publications such as EIA-649, EIA-836, ATA Specification 2000, and the CIMdata PLM Glossary. This “living” document will continue to be updated to meet the needs of the AD PAG members and is published for the benefit of the aerospace and defense industry as a whole.
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.
This intent of this paper is to explore the need to enable frictionless operation between OEMs and their suppliers. Process analysis by the A&D PLM Action Group (AD PAG) project team has shown that many different data formats, PLM software systems, and enabling infrastructure technologies exist across the OEMs and their supply base. This position paper, in its first release, presents the problem statement, including use cases, and the project team’s go forward plan. Future releases will include a statement of business performance improvement objectives, a description of the desired future state, and requirements by which that future state can be achieved.
This document states a joint position of major aerospace and defense companies on the topic of Multiple View Bill of Materials (multi-view BOM). Its purpose is to provide the basis for a dialogue between the Aerospace and Defense industry and the PLM providers. The document introduces the problem statement of the dichotomy between single BOM and multi-view BOM approaches and all their pros and cons. It introduces a set of concepts that form the basis of any BOM solution, as well as a set of use cases that any PLM system must support. Finally, it introduces a solution concept to address the pain points identified throughout the document. While the discussions presented herein focus heavily on the engineering and manufacturing views of the BOM, the concepts apply to any additional upstream and downstream views of the BOM, such as Sales and Configuration BOM and Support and Services BOM.
A major barrier that emerged immediately during the first Aerospace & Defense PLM Action Group (AD PAG) multi-view BOM workshop was the inability of the assembled experts from the member companies to effectively communicate due to their use of different terms for similar concepts (or sometimes even use of the same term for contradictory concepts). This glossary is a list of agreed upon terms with precise definitions, the source (if directly adopted or based on an industry publication), and a list of synonyms. The goal of the glossary is to support effective communication throughout the aerospace and defense industry and to promote incorporation of common language within future PLM solution provider offerings and documentation.
This technical Appendix, which is most appropriate for Subject Matter Experts (SMEs), provides a walkthrough example and a list of use cases to illustrate BOM Restructuring and Accountability requirements. This Appendix explains best practices used with multi-view BOM: EBOM, MBOM. It addresses the capability of managing instance and assembly information between EBOM and MBOM after split. Walkthrough change examples of multi-view BOM management include the following: establishing an engineering baseline, applying an engineering change to the baseline, and introducing a manufacturing change post engineering change. This document provides use case examples for each of the above.
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.