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.

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.

Since the start of 2017 the A&D PLM Action Group’s Multi-view BOM project team has been working to produce an understandable set of common high-level requirements for managing the multi-view BOM in PLM solutions.This presentation will describe the operating model that has been put in place and the topics identified by the team that need to be addressed.

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.