Tech Talk Series

UNDERSTANDING HOW MODEL BASED IMPLEMENTATIONAND DIGITAL TRANSFORMATION WILL AFFECT CDM

IMPLEMENTATION

Interest in model-based engineering approaches and digital transformation has been growing steadily across many different enterprises, extending beyond defense and aerospace. Application vendors are quick to point out benefits of model-based and digital data approaches, but are not always clear how these benefits can impact and change current processes within a realized project. When deploying digital implementation, CDM processes can become obfuscated and the value quickly lost. This presentation willbriefly discuss how model based and digital transformation can affect CDM, and some of the key considerations for successful implementation in real-world projects.

December 14th 2017

Questions?—ACDM Email address

CM supported the traditional Systems Engineering Life-Cycle

Traditional DDT&E Lifecycle

“Typically, Configuration Management supported a linear lifecycle process based on traditional documentation artifacts resulting rom technical processes.”

“That world is changing due to model based implementations”

DESIGN PLAN EXECUTE SUSTAIN

SystemEngineering

SpecsProductionEngineering

DesignDrafting

ProgramRequirements

IndustrialEngineering

KittingandFloorStockManager

Drawing&EBOMDesign

Engineering

ToolClassification

LibrariesandTemplates

MRP

ToolingAsset

Manager

ProductModel/PMI

MBOM,ProductStruct.

OperationMaterial

MachineCodeDataMachineSetupDataToolList

SpecialTooling

WorkInstructionOperationSetupDataProcessDefinitionTestProgram

ProcessControlData

MES

DataCollection

ProcessStructure

Product/TestData

Manuf.Process

EngineeringToolDesign

andCAMDataPreparation

AsMaintainedOperationalDataFRACASData

ProcessStructureandStandards

Prod.Schedule

Prod.Orders

Purch.Orders

OperationBOM

Workflow

CuttingTools

HandTools

SpecialTooling

CollaborativeFeedback

As-

Des

igne

d

As-

Plan

ned

As-

Mai

ntai

ned

As-

Bui

lt

Lifecycle Process ThreadThe digital thread in moves through design, manufacturing, test

CONSIST OF SEVERAL SUB-ELEMENTS (MBX)

• MBSE: System Engineering.

• MBT&E: Testing & Evaluation.• MBI: Inspection/QA.

• MBM: Manufacturing.• MBS: Sustainment. (Operation, Maintenance & Logistics)

• MBDes /EA: Design, Engineering Analysis.

• MBDef: Model Based Definition.

“PART OF DIGITAL TRANSFORMATION”

Model Based Enterprise

DATA MANAGEMENTMBSE as an MBE Framework

7 SysML and MBSE: A Quick-Start Course Copyright © Georgia Tech and InterCAX. All Rights Reserved. 101.02

Beyond Pretty Pictures: Rich Modeling Attributes (Metadata) in each SysML Block

Specification Window

Consistent and comprehensive access to many model aspects (attributes, meta-attributes, ...)

Filters to add/remove detail

Built-in documentation on each model attribute

[MagicDraw: hybrid sport utility vehicle.mdzip]

Hybrid SUV [Appendix B - SysML spec]

Source: SysML 101/201 course material – Russell.Peak@gatech.edu

Page 5 © 2014, 2015, 2016 Rick Steiner/Skygazer Consulting. Unpublished Work.

Basis of MBE: Documents, Diagrams, and Descriptive Models

AirplaneATC Pilot

Request to proceed

Authorize

Power-up

Initiate power-up

Direct taxiway

Report Status

Executed cmds

Initiate Taxi

Document: A primarily textual vehicle, possibly with some embedded graphics.

Diagram (Drawing): A primarily graphical vehicle, possibly with some embedded text.

Can be used to describe, or to express imperatives, for a concept, mission, or system

Model: an organized collection of concepts, obeying certain syntactical and methodological rules, from which documents or diagrams can be expressed.

req

act ibd

par

v :

Page 9 © 2014, 2015, 2016 Rick Steiner/Skygazer Consulting. Unpublished Work.

Model Based Systems Engineering (MBSE) as a Framework for MBE

closed form

discrete event

network

Analysis Models

ExternalRequirements

SystemDocumentation& Specifications

viewpoint

traceabilityrationale

analysisneeds

Model BasedElectrical

Design

Model BasedSoftwareDesign

Model BasedMechanical

Design

Model BasedTesting

performanceestimates

System Model (SysML)

Model Level Linkage

req

actibd

par

Structure Behavior

Requirements Parametrics

Model Based Systems Engineering

Copyright 2014, Rick Steiner/Skygazer Consulting. Unpublished Work © 2015 Elsevier

ARRM System-of-Systems Block Diagram (EEIS)“Views vs. Language”

OverviewMBSE Cloud-Based Enterprise Architecture Configuration Management

MBSE Planning Considerations

1. Enterprise Information and Configuration Management (ICM) must be addressed initially and continuously– Authoritative Architecture.

2. Information, App Architecture, versions, and interconnections must be identified, controlled, released, and accounted for using standardized ICM processes for information, and applications software.

3. These processes are typically managed by the CIO and Engineering.

4. Proper communication of release changes and software PR’s is essential to avoid issues with critical data control.

5. The need for disciplined cloud/application ICM increases with information system complexity.

Overview MBSE Product Configuration Management

Product CM Considerations – Identification/Decomposition of SysML Models

Level I

Level II

Level III

Level IV

Level V

o Unique models can be created for each system element and assigned a UUID. UUIDs are included as part of model block diagrams and maturity state properties and are also captured with each released model version as the identifier.

o The configuration baselines will generally be maintained in a PLM/PDM system such as Windchill that includes functional, allocated, and product baselines (Product Definition Data)

o The snapshot versions are released as part of a defined release process into a model library(Team Center) within the defined IM architecture.

o The PLM system will be used to maintain versioning and access to all baseline artifacts regardless of format. Linkage between system can be provided within the PLM tool.

o Model snapshots are captured when data packages are needed for technical events or defined maturity state criteria are met.

o Synching and pedigree of controlled ICM artifacts must be continuously maintained by the Information and Configuration Management functions.

o Model Views and Reports (Data Exports) are identified and controlled as part of the CM process. Use cases for these artifacts must be defined along with key model meta-data.

o A framework of maturity states is used to define suitability for engineering usage within predefined activities. (Design Reviews, TIMs, Design, etc.

OverviewMBSE ICM Road Map and Implementation Outline

Change Management (Initial Approach)

Europa Project Change Process/ J. Reiz

• CCB approval is used for baselined maturity state.

• Developmental CM processes used for earlier maturity states (Sprints/Developmental Release)

• ECR content is managed external to the model.

• Model changes can be captured as predefined view snapshots or exports. Model structure changes (Diff Comparisons) can be included with the MCR content.

• Information architecture changes are addressed through a common change board or as a stand alone Architecture Control Board.

• The various ECR related change artifacts (Doors, Documents, Other Model Exports) are captured and integrated into a ECR CCB integrated decision package.

Functional Baseline

Notional Configuration Management (CM) Data Artifacts within the Architecture

Views/Reports

Model Release

Requirements

Archive/Reference

Product Design PDD)

Developmental

Pink shaded blocks depict where CM artifacts are created that are part of the model based configuration information

Developmental CM Processes(Non Baselined Maturity State)

PLMProduct Baseline

CONFIGURAITON MANAGEMENTInformation and Application Architectures

Cloud-based w/ multi-center access

PLM/PDMProduct Baseline

Model Developmental Configuration Management (CM)

Archive/Reference

Functional and Product Baselines

Developmental CDM Processes(Non-Baselined Maturity State)

Views/Reports

Developmental Model Release(Diff Comparisons/Synchs/Commits/Pushes)

Pink shaded blocks depict where CM artifacts are created that are part of the model based configuration information

CONFIGURATION MANAGEMENTDevelopmental Environment

ModelValidation

TIM 1

TIM 2

TIM X

Tech Review

Maturity C

riteria

CM

Release

Metadata Pedigree

Digital TraceabilityData Structures and Baseline Instances

Digital TraceabilityThe Thread and the Twin

Digital ThreadUse of Interoperability Data Standards to Exchange Data

Digital ThreadUse of Interoperability Data Standards to Exchange Data

PDES Inc Digital ThreadUse of Interoperability Data Standards to Exchange Data

API Digital ThreadUse of Interoperability Data Standards to Exchange Data

Technical Data Packages

MIL-STD-31000 Revision Project / J. Windham

MIL-STD-31000 Revision Project / J. Windham

Technical Data PackagesA Use Case Example