2016 Aras aras com MBSE and the Business

MBSE and the Business of Engineering Pawel Chadzynski Sr. Director, Product Management, Aras Michael

Product complexity is increasing And creating system design challenges Product Complexity Connected Software Electronic Systems of Systems Product as a System 3 D Mechanical Electrical 2 D Mechanical Early Products Smart Connected Products Product as a Service Time © 2016 Aras aras. com

Product vs. Behavior • Are these cars products with lots of parts? • Or is it a system with behavior working with lots of other systems with behaviors? § Is plane a product with lots of parts? § Or is it a system with behavior working with lots of other systems with behavior? © 2016 Aras aras. com

Product vs. Behavior • Are these cars products with lots of parts? • Or is it a system with behavior working with lots of other systems with behaviors? Forces new organizational thinking © 2016 Aras § Is plane a product with lots of parts? § Or is it a system with behavior working with lots of other systems with behavior? aras. com

V-Process supports Systems Engineering Needs System validation Requirements System architecting System integration Sub-system design Component design Sub-system integration Component test Process, manufacture, assembly In theory © 2016 Aras Behavior appears after integration!!! Needs System validation Requirements System architecting System integration Sub-system design Component design M System E S S Component test E M Process, manufacture, assembly In reality aras. com

MBSE spans many tools & data models Behavior part of every design step Domain

MBSE is not MBD or 3 D Mockup MBSE – Model-Based Systems Engineering 1. Structure 3. Requirements MBD – Model Based Drawing/Design 2. Behavior 4. Parametrics All eliminate paper documents/drawings but only MBSE captures system behavior © 2016 Aras aras. com

Connecting System models to Design domains in PLM OK, but how D A MC

§ MCAD – deep IP in PLM ▫ MCAD file = PLM Part/Assembly (BOM) ▫ MCAD files mapped to PLM Parts and part structures are already live in PLM § Electronic/Electrical – no IP in PLM ▫ Schematic block? ▫ Interconnect/layout blocks? § Software – no IP in PLM ▫ IDE files PLM Part/Assembly (BOM) ▫ Build process? Released binary? § System model – TBD in PLM ▫ Requirements? ▫ Block diagrams (functional & logical)? ▫ Models as input, Reports as outputs? © 2015 Aras B com ehavi plex oral ity i s he re Cross-domain link challenge PLM does not understand ECAD structures (manufacturing files and off-shelf BOM is not a structure) PLM does not understand software structures (binary file is not a structure) PLM does not understand or manage RFL at all It will take more finesse than this!

MBSE and PDM Model Rev 1 © 2016 Aras Model Rev 2 Model Rev

MBSE and PLM – today’s target M ec ha nic al System Rev 1

MBSE and PLM – real target Ele c So ftw tro nic M ec

MBSE-PLM use cases Ø The goal is a full traceability between requirements, models, and product details 1 1§ Top/Down – System model first, then detailed Product design 2§ Design everywhere at once – System model 2 is collaborated with on-the-fly 3§ Redesign – Field driven requirements 3 changed © 2016 Aras aras. com

PLM Connectors today A B C Software ALM D E G H I J

That’s why MBSE needs PLM manages post design evolution of physical structures with strong configuration and change management control across life stages A B B © 2016 Aras P 1 C D D D F G F P 2 G H I H J I K L K M O T T T G J J J O L I O Q H S S Q F F K R SN #89 G L R F G J Q SN #89 G T J SN #6 C C F A SN #6 C C E A SN #6 C Q “As Designed” is not a true Digital Twin of the “thing” in the field AA A K K K L L L O I SN #97 O SN #44 H SN #53 Q O SN #44 H SN #71 Q SN #71 R R R S S S R S AS DESIGNED AS ORDERED AS PLANNED AS BUILT AS DELIVERED AS SERVICED aras. com

Add System Model structures in PLM R 1 R 2 R 5 R 6 R 7 R 8 C D D L 4 D D D F F 5 L 5 E F 8 L 6 G L 7 H L 8 J F 9 F 10 F 11 I H I L 10 L K M O Q T T T G J J J O L I O Q R R H R 14 F 14 S S Q R F 16 S AS ORDERED AS PLANNED SN #97 K K K L L L O I F 15 AS DESIGNED F F K F 13 SN #89 G L R 13 F G J Q SN #89 G T J K F 12 P 2 G L 9 L 11 F SN #6 C F 4 F A SN #6 C D Required FUNCTIONAL Logical REQUIRED Functional LOGICAL © 2016 Aras P 1 C Sys. ML tool connector R 12 B A SN #6 C F 7 R 11 B AA A C F 6 R 10 A L 3 F 3 R 4 R 9 L 2 F 2 R 3 A L 1 F 1 O SN #44 H SN #53 Q O SN #44 H SN #71 Q SN #71 R R R S S S AS BUILT SN #44 AS DELIVERED AS SERVICED aras. com

Traceability gap R 2 R 5 R 6 R 7 F 4 L 4 F 5 L 5 F 6 F 8 R 9 L 6 L 7 F 7 R 8 L 9 F 9 R 10 L 10 F 10 R 11 F 11 R 12 F 12 R 13 F 13 R 14 F 14 B L 3 F 3 R 4 A L 2 F 2 R 3 A L 1 F 1 L 11 Concept/Link Barrier R 1 AA A B P 1 D D D F G P 2 G H I H J I K L K M O Q T T T G J J J K O L I O Q R H S S Q F F L R SN #89 G J Q F G T J SN #89 G I F 15 R F 16 S SN #97 K K K L L L O AS Designed DESIGNED AS ORDERED AS PLANNED REQUIRED FUNCTIONAL LLogical OGICAL <> As © 2016 Aras C C F SN #6 C C F A SN #6 C C E A SN #6 O SN #44 H SN #53 Q O SN #44 H SN #71 Q SN #71 R R R S S S AS BUILT SN #44 AS DELIVERED AS SERVICED aras. com

Add Sys. ML Requirement & Logical structures Software ALM SE Requirements System Model Created

Add Requirements decomposition ALM Requirements Software ALM MCAD Requirements SE Logical Referenced automatically or manually via connectors System Model Mechanical CAD ECAD Requirements Each domain has its own requirements breakdown © 2016 Aras Electronic CAD aras. com

Add Logical to Physical ALM Requirements ALM Structure Software ALM Not really “physical” MCAD Requirements SE Logical MCAD Structure System Model Mechanical CAD ECAD Requirements Linked by connectors or manually within PLM (a diagram-like visual drag/drop process? ) © 2016 Aras ECAD Structure Electronic CAD aras. com

Add multiple models SE Requirements System Model_n © 2016 Aras ALM Structure SE Logical System Model_1 Multiplicity of SE models as part of the same PLM structure ALM Requirements Software ALM MCAD Requirements MCAD Structure Mechanical CAD SE Requirements SE Logical ECAD Requirements ECAD Structure Electronic CAD aras. com

Add “System” properties (data/control flow) SE Requirements ALM Requirements SE Logical System Model_1 Software ALM MCAD Requirements SE Requirements ALM Structure SE Logical MCAD Structure Created/linked by connectors or manually within PLM (a diagram-like ECAD Requirements visual drag/drop process? )ECAD Mechanical CAD Structure System Model_n © 2016 Aras Electronic CAD aras. com

Properties are cross-domain negotiable “Contracts” § Linked between any two structural items Makes Requirements quantifiable and PLM SE structures behavioral § Value, range, enumerated list § Units § Fixed or a target (a budget) § A domain owner § On a structural item or accumulative for an assembly Item A f(x) = y Property x Item B Property y f(y) = x § Transformation function on a property link § Created/linked by connectors or manually (a diagram-like visual drag/drop process within PLM? ) © 2016 Aras aras. com

Add simulation data ALM Structure ALM Requirements n SE Requirements ul SE Logical System Model_1 ti a ul Sim on ta a d io at ta a d Sim Software ALM MCAD Requirements MCAD Structure n io at ta da ul Sim SE Requirements System Model_n SE Logical d ECAD Structure a ul Sim n tio a at ECAD Requirements n tio a ul Sim © 2016 Aras Mechanical CAD ta a d Electronic CAD aras. com

Add Logical to Logical SE Requirements ALM Logical ALM Structure SE Logical System Model_1 Software ALM MCAD Logical MCAD Connectors Structure extract Logical block abstractions per domain Mechanical CAD SE Requirements System Model_n © 2016 Aras SE Logical ECAD Structure Electronic CAD aras. com

Enable Negotiations SE Requirements ALM Logical ALM Structure SE Logical System Model_1 Software ALM MCAD Logical MCAD Structure Space to negotiate “Contracts” on a Logical block level SE Requirements System Model_n © 2016 Aras SE Logical ECAD Logical Mechanical CAD ECAD Structure Electronic CAD aras. com

Result: Complex & Overwhelming System Model_n © 2016 Aras SE Logical ALM Structure s e r tu c u r st l a … c i n ys ith es io. MCAD h Logical P w tur sit s D d A ke ruc po re C E lin st om ctu s / c ru el D … cal e A d st od i t g MC n Lo me are L m a e ftw s. M dat s r i u SE/So Sy n low q SE. Re LLogical M tiple latio ta FECAD c Requirements t e A ul mu Da Logical , … s c M Si rol/ lus o t p V, D n … & Co V , P Q P, P M SE Requirements System Model_1 ALM Logical Software ALM MCAD Structure Mechanical CAD ECAD Structure Electronic CAD aras. com

SE Requirements SE Logical System Model_1 Connectors System Model_n © 2016 Aras SYS Software ALM MCAD Logical SE Requirements ALM Structure SE Logical ECAD Logical SYSmap MCAD Structure Connectors Make PLM “invisible” ALM Logical Reinvent PLM ECAD Structure Traceability driven & Navigation Mechanical CAD Electronic CAD aras. com

Business of Engineering Continuous System & Product design process PLM Digital Twin & Digital

Partnering with § TU Kaiserslautern: Proof of Concept (Magic. Draw) § Airbus/IBM/Aras: OSLC-based ALM/PLM integration § XPLM/No Magic: Magic. Draw integration § Aras/Altium: Bringing ECAD into MBSE © 2016 Aras aras. com