[MUSIC] A typical design process requires engineers to make many changes and produce different documents based on information learned during the design process. When the documents reach the manufacturing stage, they can be the cause of delays, inefficiency, and waste because they're subject to misinterpretation by manufacturing workers as they take time to determine the designer's intent. A large percentage of scrap and rework in the manufacturing process is due to inaccuracies in the documents, or misinterpretations resulting from inefficient collaboration between design and manufacturing. The vision of MVE minimizes such problems by adding information required by downstream consumers of the 3D model, including manufacturing, suppliers, and subcontractors. Quality, procurement, maintenance and repair entities. Reusing a single set of engineered data in the model can reduce costs. A well-organized model based enterprise can also reduce the time that engineers spent hunting for design data or recreating analyses for products. Outside of engineering in manufacturing departments, throughout the supply chain, even within service, 3D drawings have yet to become the source of truth, let alone an overall representation of the model. 2D drawings are still often the go to resource for information about a particular product's design. Over recent years, standards have evolved for 3D models to embed other types of non geometric data, product and manufacturing information, PMI, such as geometric dimensions and tolerances, materials, information, and surface finishes, among other items. Examples of data standards that enable the sharing of geometry and/or annotated models are STEP, JT, and 3D PDF. While typically industry would like to keep advances that increase their competitiveness and reduce costs private and protected, Toyota and Boeing have gone on record with claims that an MBE approach can translate into a 50% reduction in costs. The stated sources of savings are the result of efficiencies, and increased accuracy resulted from the 3D product definition. >> INCOSE and systems engineering need to continue and need to continue to expand and connect. The analogy I use for systems engineer is they are the connective tissue on a program. A systems engineer alone brings no value. A systems engineer in the midst of specialists who understand the problem and the solution technologies brings great additive value. The same thing is true for INCOSE. INCOSE focused purely on systems engineering, while we may advance the practice a little bit but we won't solve the great problems of the systems era. INCOSE working in concert with manufacturing organizations, business information modeling, electrical organizations, aerospace organizations, all of those specialists. INCOSE is a connector at that level can bring tremendous value, particularly as we work to scale up to the most complex and scale down to, well there's no simple problem today, but maybe something more on the complicated scale instead. >> A 2014 study on the model based enterprise published by Lifecycle Insights, the study's available in the resources section, found plenty of evidence that model based definitions help companies Save Time, Eliminate Scrap and Promote Reuse. Specifically, the report found that organizations that are heavily committed to using annotated 3D models spend fewer hours per week on engineering documentation, address fewer emergency issues per month, like initiating change orders or re-prioritizing resources. And have to deal with far fewer incidents of figuring out why certain parts didn't end up aligning during the manufacturing and assembly process. Because engineers are devoting fewer hours to creating, clarifying, or fixing documentation, they have more time to spend on generating important design and engineering work. Leading to better products. With this broad overview of the model-based enterprise in mind, the next lesson will focus on how the model-based enterprise connects with the concept of the digital thread.