WIXLIB

Digitalization, Model-Based X, PLM &the Digital Thread:Where do we go from here?PDT Europe 201718 October 2017—Gothenburg, SWEDENPeter Bilello, PresidentTel: 1.734.668.9922Email: p.bilello@CIMdata.comGlobal Leaders in PLM Consultingwww.CIMdata.comCopyright 2017 by CIMdata, Inc.1Copyright 2017 by CIMdata, Inc.

Our Mission.Strategic management consulting for competitive advantage in global marketsCIMdata is the leading independentglobal strategic management consultingand research authority focusedexclusively on the PLM market.We are dedicated to maximizing ourclients’ ability to design and deliverinnovative products and servicesthrough the application of PLM.Copyright 2017 by CIMdata, Inc.2

Key TakeawaysDigitalization, PLM, MBx, and the Digital Thread: Where do we go from here? Regardless of what we call the process, digitalization andsystems complexity will continue to profoundly affect the waywe do product design, development & sustainment Multiple digital threads will evolve in organizations based onthe business requirements and specific application use cases Product innovation platforms will need to be open andflexible to enable the “digital thread/digital twin” vision Technology is the least important issue – organizationalculture, process change, standards, and people skills will bethe gating factors to successful business adoption andfinancial ROICopyright 2017 by CIMdata, Inc.3

First, A Definition: “Digitalization”Let’s first get a few things straight Digitalization: the administration of digitalis (used to treatcongestive heart failure) until the desired physiologicaladjustment is attained—Merriam-Webster Digitalization: the use of digital technologies to change abusiness model and provide new revenue and valueproducing opportunities; it is the process of moving to adigital business—GartnerI think we should go with the second definition Copyright 2017 by CIMdata, Inc.4

Complexity Risk, Digitalization OpportunityBusiness Success now requires a Model-Based Systems Engineering approach Significant electronics & software content New processes & materials—lighter, stronger, green Consumers demand “mass customized” products with all thelatest technological features Now! Shorter lifecycles continuous product innovation “IoT” environment constant market feedbackComplex market requirements demandmore upfront cross-domain engineeringCopyright 2017 by CIMdata, Inc.5

Model-Based Enables Systems EngineeringDigital collaboration enables high-value information continuity across lifecycle processesMarketAssessmentCross domainsystem conceptmodelsReal world feedbackFeasibility /ConceptExplorationSystemConcept ofOperationsDeploymentandOperationsSystem Validation PlanSystemValidationServiceandMaintenanceEnd of LifecycleDisposition“Digital Twins”System Verification PlanSystemVerificationSystemRequirementsLevel of DetailHigh-LevelDesignSubsystemVerification PlanSubsystemVerificationUnit TestPlanDetailedDesignHigh fidelity virtualprototypes for productfunctional V&VUnit / DeviceTestingStage Gate / ApprovalMechanicalTime LineAssembly & ComponentDefinitionComponent ProcurementElectricalSoftwareAdapted from: US Federal Highway s/seitsguide/“Systems Engineering for Intelligent Transportation Systems”ImplementationCopyright 2017 by CIMdata, Inc.6

Common Model-Based DefinitionsOverlapping and somewhat confusing terminology used by the industry today Model‐Based Systems Engineering (MBSE) – “the formalized application ofmodeling to support system requirements, design, analysis, verification and validationactivities beginning in the conceptual design phase and continuing throughoutdevelopment and later life cycle phases.” Model‐Based Engineering (MBE) – Integrated use of models to define the systemtechnical baseline across the full life cycle, across all disciplines, across all programmembers [models are the authoritative definition of the system] Model‐Based Enterprise (MBE) – “a vision to transform an enterprise’s engineering,manufacturing, and aftermarket services through product data reuse and derivedcontext, rather than interpreting inputs and recreating the models and drawings.” Model-Based Definition (MBD) – The practice of using 3D models (i.e., solid models,3D PMI and associated metadata) within 3D CAD software to define (providespecifications for) individual components and product assemblies. Model-Based Design (MBD) – “A mathematical and visual method of addressingproblems associated with designing complex control, signal processing andcommunication systems as applied in the design of embedded software.”Copyright 2017 by CIMdata, Inc.7

Digital/Model-Based Engineering “As Is”Overlapping and somewhat confusing terminology used by the industry todaySystemArchitecture &RequirementsTest/V&VModeling &SimulationProductReqs.MBSEMechanicalDesign PDMElectronicsDesignIn Service(SLM)SPDMModelBasedDesignDesignFor ProcurementBOMs, Reqs, Configurations,Portfolio, Change Mgmt Copyright 2017 by CIMdata, Inc.8

Model-Based – What is the Business Challenge?Disciplines are approaching digital design & development from different perspectivesSystemsEngineering(RFLP)All areas are supported by a number of overlapping solutionsCopyright 2017 by CIMdata, Inc.9

So, Which Model is Correct?Many competing, complimentary viewsSome andnone all Copyright 2017 by CIMdata, Inc.10

“Sewing the Digital Thread”Copyright 2017 by CIMdata, Inc.11

Digital Thread & Digital Twin (DoD/USAF)The thread that binds the product and systems world Digital Thread is the creation and use of cross-domain commondigital surrogates of a system to allow dynamic, real-timeassessment of the system’s current and future capabilities toinform decisions throughout the entire life cycle Digital surrogate (i.e., the digital twin) is a physics-baseddescription of the system resulting from the generation,management, and application of data, models, and informationfrom authoritative sources across the system’s lifecycleDigital thread is enabled and supported by arobust systems model and MBSE processesExtracted from: irForce/Cleared DT for Website.pdfAlso see: and-digital-twindefinition.htmlCopyright 2017 by CIMdata, Inc.12

Defense Systems Have Unique RequirementsReliability & Sustainability drives the need for a Systems Engineering approach Must design, build and operate “systems of systems” Rapidly changing threats & operational requirements Rapidly changing electronics & S/W technologies Extremely long lifecycles requiring continuous system &subsystem upgrades (LOTAR) Cyber security threats to sensitive IP Shrinking DoD R&D & procurement budgets (since 2008)“The Digital Thread Puts EngineeringBack Into Systems Engineering1”1 Dr. Ed Kraft, USAF AEDC/CZ; Presented to the NIST MBE Summit December 18, 2013Copyright 2017 by CIMdata, Inc.13

Relationship of Digital Initiatives (“As Is”)Key domains in model-based are typically managed partially or totally in silos For MfgALMIoT/Digital TwinsModeling &SimulationProductReqs.MechanicalDesign nMgmt.InventoryIn ncePhysicalBOMs, Reqs, Configurations,Portfolio, Change Mgmt Copyright 2017 by CIMdata, Inc.14

Sewing the MBSE Digital Thread (“To Be”)Conceptual Systems Engineering across domains; connections to PLM/M&S for V&VTest/V&VSystemArchitecture &RequirementsProductReqs.MechanicalDesign PDMElectronicsDesignSoftwareDesign ALMModeling &SimulationModelBasedDesignMBSE Use Case:Conceptual Design,Optimization and ValidationOf Cyber-Physical SystemsSPDMVirtualMBSEBOMs, Reqs, Configurations,Portfolio, Change Mgmt Copyright 2017 by CIMdata, Inc.The thread needs to connectinformation across domains:* Systems Architecture& Requirements* Software/ALM* EDA/ECAD/EBOM* MDA/MCAD/PDM* M&S/CAE/SPDM* Test/V&V/TDM15

Sewing the MBSE Digital Thread (“As Is”)Significant collaboration efforts underway to integrate data and processesEvolving standards for cross-domain data linking & interoperability SysML v2.0 – Next generation MBSE systems modeling language UPDM – Unified systems modeling standard for DoD and MoD STEP AP 233/239/242 & 209 – New unified data architecture OSLC – Open Services for Lifecycle Collaboration (www.oasis.org) PDES Requirements Traceability Project – Connect requirementsinformation across the domains of MBSE, PLM/MCAD & ECAD viaopen source Eclipse resources (ReqIF Studio, Lyo/OSLC, Papyrus) Modelica & FMI/FMU – Functional Mockup Interface/Mockup Unit MoSSEC – Modeling & Simulation information in a collaborativeSystems Engineering Context. See http://www.mossec.org/Copyright 2017 by CIMdata, Inc.16

Sewing the MBSE Digital Thread (“As Is”)Significant collaboration efforts underway to integrate data and processesSample of commercial solution offerings from MBSE providers Reqs and ALM/PLM integration using OSLC – IBM Rational and Aras Integration of sys design arch & req in Magic Draw (SysML) withPLM & Product Line Engineering tools – No Magic OSLC integration of req (IBM Doors & The Reuse Company) withphysics-based systems modeling simulation via FMI (Modelon) SysML data for use with automation of physics-based systemsmodeling and simulation – Phoenix Integration MBSE Pak Integration of MBSE system engineering data with PLM, CAD andCAE applications – InterCAX Syndeia, ParaMagic, ParaSolver MOSSEC implementation at CFMS/Airbus & Model Integration inthe SAVI consortia work with Rockwell Collins - EurostepCopyright 2017 by CIMdata, Inc.17

Sewing the MBEnt Digital Thread (“To Be”)Use of 3D model-based design information in manufacturing; Connections to PLM, ERPSystemArchitecture &RequirementsMBEnterprise Use Case:Move from 2D drawings and docs to3D Models PMI on the shop floorPLMProductReqs.MechanicalDesign terpriseModelBasedDesignDesignFor ventoryProcurementERPBOMs, Reqs, Configurations,Portfolio, Change Mgmt Copyright 2017 by CIMdata, Inc.18

Sewing the MBEnt Digital Thread (“As Is”)The MB Enterprise journey is still at its beginnings—early adopter successes (1 of 2) Aerospace and automotive have 20 years of PLM experience MBEnterprise is supported as part of PLM strategies (maturity levels growing) Early adopters: Boeing, Gulfstream, GM, Ford, Airbus Commercial aerospace OEMS proactive in getting FAA to accept electronicTechnical Data Packages for flight certification signoffs and design approvals Gulfstream’s maturity level is very advanced Model-Based is now the basis for their FAA certification Using embedded PMI with 3D directly to factory instead of 2D drawings & paperBoeing: demonstrates massive use of 3D for 777 (mostly 3D) and 787 (all 3D) CIMdata’s A&D PLM Action Group actively researching what is needed to fullydefine PMI (manufacturing data such as GD&T embedded in models)—manyunresolved issues being addressed by joint industry & DoD/govt. activities NIST, DMDII/UI Labs, Air Force Research Labs(AFRL), NAVAIR, etc. active in this area 3D data interoperability solution providers such as ITI and Anark partnershipCopyright 2017 by CIMdata, Inc.19

Sewing the MBEnt Digital Thread (“As Is”)The MB Enterprise journey is still at its beginnings—early adopter successes (2 of 2) DLA (Defense Logistics), NAVAIR, Army and others working onMBE-based TDPs (still relatively low maturity levels) Standardize the acquisition and sustainment of TDPs Provide work force with the tools, training, infrastructure, and processesrequired to be successful Army prototyping a 3D TDP for gunbarrel (with Army Materiel Command) U.S. Army & Boeing A-10 wingreplacementA-10 Wing replacement metrics—results ofusing model data vs. paper drawings Significant reduction in NSN errors andmissing information (standard parts) Elimination of non-described NSNsNSN National Stock NumberSource: http://www.nist.gov/el/msid/upload/D1 2 yright 2017 by CIMdata, Inc.20