SlideShare a Scribd company logo

CapellaDays2022 | ThermoFisher - ESI TNO | A method for quantitative evaluation of functional chains supported by a Capella add-on

•
•
Obeo
Obeo

Development of high-tech systems is a complex task done by diverse specialists distributed across the globe. Reference architectures including a clear functional breakdowns can support them and support their decisions. This presentation proposes an approach to improve the development of advanced electron microscopes by using Capella as an authoritative source of information. To support design decisions, a Capella AddOn has been developed to obtain quantitative information, such as throughput numbers, for a particular workflow. First, we will illustrate how functional and system decompositions can be captured and serve as company-wide architecting assets to inform design decisions. Next, we will outline how simulating Capella models can bring valuable insights to modelers. During a demo, we’ll simulate Capella’s Functional chains using the open-source simulation tool POOSL (https://github.com/eclipse/poosl) , and visualize results using the freely available TRACE4CPS tool (https://www.eclipse.org/trace4cps/). Re-using functions from the reference architecture allows us reason about design aspects such as the relation between throughput and design choices about function allocation and parallelism. *** The open-source code of the solution is available at https://github.com/TNO/capella-workflow-dse

1 of 32
Download to read offline
A method for quantitative evaluation of functional chains supported by a Capella add-on TNO-ESI: Alexandr Vasenev Jacques Verriet Koen Kanters Jozef Hooman Thermo Fisher Scientific: Joost Dierkse Olivier Rainaut Jamie McCormack
Outline 2 Intro to workflows • Joost • 15 min Method • Alexandr • 20 min Conclusions • Joost • 5 min Q&A • All  • 10 min
Introduction to workflows (Joost, 15 min) 3
Thermo Fisher Scientific 4  Material and Structural Analysis >40B$ Revenue
System Scope 5 Transmission Electron Microscope  Dimensions: 1.6m x 1.6m x 3.0-4.3m  Weight: > 1600kg  Resolution: 50pm  Cost: 1M$ – 15M$ Applications  Life Sciences • Virus and cell structure research  Material Sciences • Chemical and material investigations  Semiconductor • Process analysis / control
Background 6  15 active commercials TEM products  More than 20 customer-facing applications  More than 400 Modules  1 TEM Server Software Stack  1000+ active configurations  Distributed Development
Reference Architecture Overview 7
Workflow Analysis 8  Identify Customer Value  Identify Critical To Quality (CTQ) Parameters (KPIs)  Allocate CTQ Parameters to Features
Functional Decomposition / System Decomposition 9  Decompose System into Functions • Decompose CTQ parameters • Cover hardware and software  Decompose System into Modules • Allocate Functions to Modules and Owners (Hardware and Software) • Logical grouping of functions • Define transfer functions for Modules (based on Function CTQ Parameters)
Logical Architecture / Compatibility 10  Identify interfaces between Modules • Critical for compatibility • Used for risk management (FMEA) • Component naming aligned though Taxonomy  Define technical compatibility • Map Module compatibility to Systems • Include Non-Standard Requests • Include Backward Compatibility
MBSE – Evolving Reference Architecture 11  Tool to support Reference Architecture • Guarantee consistency • Ease maintainability • Increase automation opportunities  Process to ensure maintainability • System-of-Systems approach • Separate models for System versions
MBSE – Modeling Structure 12 150% 100% System System of Systems Logical Architecture Logical Architecture Logical Architecture Physical Architecture Physical Architecture
MBSE – Transition 13  Transfer Reference Architecture to Capella • Functional Decomposition • System Decomposition • Interface Specifications TITLE: NODE: NO.: 2 F0 External functions diagram for operational mode (Owner = Jamie McCormack) Transmission Electron Microscope System Building Post-processing, archiving and reporting system (including e.g. 3D reconstruction) Operator (human, or virtual operator/ external software application/robot) Specimen Preparation System F1 Execute TEM microscopy application TEM workflow procedure Environment (air temperature, acoustic, magnetic) F2 Analyze, archive and report results Application result F3 Operate tool (externally) Tool control F4 Provide environment F5 Prepare And Handle TEM specimen Prepared specimen for TEM loading F6 Provide infrastructure Power, water, N2, compressed dry air Customer workflow procedure Application and system status information Specimen preparation procedure Sample Grid power, grid water, stock N2 Emergency messages Microscopy analysis workflow procedure Changed environment (air temperature, acoustic, magnetic) Heated water Report Processed specimen Processed specimen Existing application result (processed) specimen Note: F5 is intended to cover the sample to specimen preparation outside of the microscope tool itself but in the scope of TFS tool flow. F5 is such that it keeps open the option for customer facilities outside the devices of TFS.
MBSE – Maximizing Benefits 14  CTQ / KPI Calculation • Attribute model with CTQ parameters • Extract performance based on configuration • Reliability prediction model • Define Customer Value at design time
Method for quantitative evaluations of functional chains (Alexandr, 20 min) 15
ESI at a glance 16 Synopsis  Foundation ESI started in 2002  ESI acquired by TNO per January 2013  ~60 staff members, many with extensive industrial experience  7 Part-time Professors  Working at industry locations Synopsis  Foundation ESI started in 2002  ESI acquired by TNO per January 2013  ~60 staff members, many with extensive industrial experience  7 Part-time Professors  Working at industry locations Partners Partners Focus Focus Managing complexity of high-tech systems through • system architecting, • system reasoning and • model-driven engineering delivering • methodologies validated in cutting-edge industrial practice
What do we want to achieve? 17 Conclusion: we need simulation Approach: Simulate functional chains in Capella • Why: Natural fit to ‘precedes’ relation, Iteration/OR/AND nodes • To do: Specify meaning of nodes, add properties
Intro to Functional Chains 18 Functional Chain: a specific path among all possible paths (using certain Functions and Functional Exchanges). * A lead to functional modeling: Functional flow block diagram - Wikipedia Example of a functional chain: is described by involves Note: Sequence links (‘precedes’ relation)
A method in a nutshell 19 End goal: To get quantified results of functional chains, for instance: * Note additional property values: ResourceID and Duration 1 2 Time saved 0 7.4 s 0 4.1 s
A method in a nutshell 20 1. Create a ‘simulatable’ functional chain (with specific property values) 2. Export and run the chain 3. Visualize result Steps: Overall architecture: Functional chain (incl. property values) + rule checker Capella add-on Formal export (Petri net) Simulation- ready Export (POOSL) Used constructs: Extra parameters: Simulator (POOSL) Visualization (TRACE4CPS)
Demo: construct a 3D model out of 2D images 21 Highlights: - A library of functional chains - Generated graph Functions: Overview:
Behind the scenes 22 Property values definition (PVMT add-on) A CONS (n) IT IT GEN (n) Transformations from a functional chain via Petri-net formalism to a simulation … Formalized model
POOSL https://www.poosl.org/ 23 Functionality highlights: - simulation of parallel processes, - well-defined semantics
TRACE4CPS https://www.eclipse.org/trace4cps/ 24 Functionality highlights: - critical path analysis, - customization of visualization using user-defined attributes (grouping, coloring, filtering)
Experiences 25 It’s easy to: - explain the model to other stakeholders due to clear traceability - quickly explore new options - relate to Arcadia constructs (Functions, Functional chains, Components) It’s good to remember that: - complexity can grow quickly, e.g., • adding extra information • when re-using a sub-FC several times in the higher-level FC • potential links between Arcadia layers (e.g., to Configuration Items) - modelers should agree on and carefully follow a modeling convention - as with any toolchain, one shall pay attention to versioning and exceptions - there is an entry bar to such a project: Arcadia and Capella knowledge, programming skills We’ve validate the approach through interviews and an industrial case with: ꟷ 12 Functional chains ꟷ 4 levels of nesting ꟷ 3 levels of functions + set of re-usabes functions ꟷ ~35 functions (most used 2+ times)
Work in progress 26 Design Space Exploration - The user can vary timing parameters - min-max durations - iteration numbers - weights of conditional arcs - Allocate functions to resources - Defining duration as a function of involved components Quantifying other properties (e.g., cost, reliability) - Specifying parameters - Exporting components for analysis using other techniques Early example
Summary 27 To note: - We’ll write a generic report - We consider releasing the code, subject to discussions: - On licensing - Vision of project stakeholders 1. Create a ‘simulatable’ Functional chain 2. Export and run the chain in POOSL 3. Visualize result (TRACE4CPS) ꟷ Interested in POOSL-TRACE4CPS native integration? Check TRANSACT project (https://transact-ecsel.eu/). We created a way to simulate Functional Chains with steps: ꟷ Interested about MBSE and high-tech industry? Check ESI report ‘MBSE in the high-tech equipment industry’ https://esi.nl/news/blogs/mbse-tno-report-2022 Some leads:
Conclusions (Joost, 5 min) 28
Conclusions – Solution Space 29  Proof of Concept delivered  Simulation of Workflows  Capella Integration  Systems Engineering Goal  Prevention of double recording of Information  Customer Value Maximization through design space exploration
Conclusions & Next Steps 30  Collaboration with ESI  Short develop-review cycles  Regular checks on the deliverables and goals  Applying scientific methods in industry on specific cases  Next Steps  Capella Model as authoritative source of truth  Tools that use Capella Model as input Capella POOSL JAMA DSE …
Q&A (10 min) 31
Your questions and thoughts? 32 Your experience on: 1. Quantitative analysis of any Capella diagram, not just functional chains 2. Simulation/analysis of functional chains in general

More Related Content

CapellaDays2022 | ThermoFisher - ESI TNO | A method for quantitative evaluation of functional chains supported by a Capella add-on

  • 1. A method for quantitative evaluation of functional chains supported by a Capella add-on TNO-ESI: Alexandr Vasenev Jacques Verriet Koen Kanters Jozef Hooman Thermo Fisher Scientific: Joost Dierkse Olivier Rainaut Jamie McCormack
  • 2. Outline 2 Intro to workflows • Joost • 15 min Method • Alexandr • 20 min Conclusions • Joost • 5 min Q&A • All  • 10 min
  • 4. Thermo Fisher Scientific 4  Material and Structural Analysis >40B$ Revenue
  • 5. System Scope 5 Transmission Electron Microscope  Dimensions: 1.6m x 1.6m x 3.0-4.3m  Weight: > 1600kg  Resolution: 50pm  Cost: 1M$ – 15M$ Applications  Life Sciences • Virus and cell structure research  Material Sciences • Chemical and material investigations  Semiconductor • Process analysis / control
  • 6. Background 6  15 active commercials TEM products  More than 20 customer-facing applications  More than 400 Modules  1 TEM Server Software Stack  1000+ active configurations  Distributed Development
  • 8. Workflow Analysis 8  Identify Customer Value  Identify Critical To Quality (CTQ) Parameters (KPIs)  Allocate CTQ Parameters to Features
  • 9. Functional Decomposition / System Decomposition 9  Decompose System into Functions • Decompose CTQ parameters • Cover hardware and software  Decompose System into Modules • Allocate Functions to Modules and Owners (Hardware and Software) • Logical grouping of functions • Define transfer functions for Modules (based on Function CTQ Parameters)
  • 10. Logical Architecture / Compatibility 10  Identify interfaces between Modules • Critical for compatibility • Used for risk management (FMEA) • Component naming aligned though Taxonomy  Define technical compatibility • Map Module compatibility to Systems • Include Non-Standard Requests • Include Backward Compatibility
  • 11. MBSE – Evolving Reference Architecture 11  Tool to support Reference Architecture • Guarantee consistency • Ease maintainability • Increase automation opportunities  Process to ensure maintainability • System-of-Systems approach • Separate models for System versions
  • 12. MBSE – Modeling Structure 12 150% 100% System System of Systems Logical Architecture Logical Architecture Logical Architecture Physical Architecture Physical Architecture
  • 13. MBSE – Transition 13  Transfer Reference Architecture to Capella • Functional Decomposition • System Decomposition • Interface Specifications TITLE: NODE: NO.: 2 F0 External functions diagram for operational mode (Owner = Jamie McCormack) Transmission Electron Microscope System Building Post-processing, archiving and reporting system (including e.g. 3D reconstruction) Operator (human, or virtual operator/ external software application/robot) Specimen Preparation System F1 Execute TEM microscopy application TEM workflow procedure Environment (air temperature, acoustic, magnetic) F2 Analyze, archive and report results Application result F3 Operate tool (externally) Tool control F4 Provide environment F5 Prepare And Handle TEM specimen Prepared specimen for TEM loading F6 Provide infrastructure Power, water, N2, compressed dry air Customer workflow procedure Application and system status information Specimen preparation procedure Sample Grid power, grid water, stock N2 Emergency messages Microscopy analysis workflow procedure Changed environment (air temperature, acoustic, magnetic) Heated water Report Processed specimen Processed specimen Existing application result (processed) specimen Note: F5 is intended to cover the sample to specimen preparation outside of the microscope tool itself but in the scope of TFS tool flow. F5 is such that it keeps open the option for customer facilities outside the devices of TFS.
  • 14. MBSE – Maximizing Benefits 14  CTQ / KPI Calculation • Attribute model with CTQ parameters • Extract performance based on configuration • Reliability prediction model • Define Customer Value at design time
  • 15. Method for quantitative evaluations of functional chains (Alexandr, 20 min) 15
  • 16. ESI at a glance 16 Synopsis  Foundation ESI started in 2002  ESI acquired by TNO per January 2013  ~60 staff members, many with extensive industrial experience  7 Part-time Professors  Working at industry locations Synopsis  Foundation ESI started in 2002  ESI acquired by TNO per January 2013  ~60 staff members, many with extensive industrial experience  7 Part-time Professors  Working at industry locations Partners Partners Focus Focus Managing complexity of high-tech systems through • system architecting, • system reasoning and • model-driven engineering delivering • methodologies validated in cutting-edge industrial practice
  • 17. What do we want to achieve? 17 Conclusion: we need simulation Approach: Simulate functional chains in Capella • Why: Natural fit to ‘precedes’ relation, Iteration/OR/AND nodes • To do: Specify meaning of nodes, add properties
  • 18. Intro to Functional Chains 18 Functional Chain: a specific path among all possible paths (using certain Functions and Functional Exchanges). * A lead to functional modeling: Functional flow block diagram - Wikipedia Example of a functional chain: is described by involves Note: Sequence links (‘precedes’ relation)
  • 19. A method in a nutshell 19 End goal: To get quantified results of functional chains, for instance: * Note additional property values: ResourceID and Duration 1 2 Time saved 0 7.4 s 0 4.1 s
  • 20. A method in a nutshell 20 1. Create a ‘simulatable’ functional chain (with specific property values) 2. Export and run the chain 3. Visualize result Steps: Overall architecture: Functional chain (incl. property values) + rule checker Capella add-on Formal export (Petri net) Simulation- ready Export (POOSL) Used constructs: Extra parameters: Simulator (POOSL) Visualization (TRACE4CPS)
  • 21. Demo: construct a 3D model out of 2D images 21 Highlights: - A library of functional chains - Generated graph Functions: Overview:
  • 22. Behind the scenes 22 Property values definition (PVMT add-on) A CONS (n) IT IT GEN (n) Transformations from a functional chain via Petri-net formalism to a simulation … Formalized model
  • 23. POOSL https://www.poosl.org/ 23 Functionality highlights: - simulation of parallel processes, - well-defined semantics
  • 24. TRACE4CPS https://www.eclipse.org/trace4cps/ 24 Functionality highlights: - critical path analysis, - customization of visualization using user-defined attributes (grouping, coloring, filtering)
  • 25. Experiences 25 It’s easy to: - explain the model to other stakeholders due to clear traceability - quickly explore new options - relate to Arcadia constructs (Functions, Functional chains, Components) It’s good to remember that: - complexity can grow quickly, e.g., • adding extra information • when re-using a sub-FC several times in the higher-level FC • potential links between Arcadia layers (e.g., to Configuration Items) - modelers should agree on and carefully follow a modeling convention - as with any toolchain, one shall pay attention to versioning and exceptions - there is an entry bar to such a project: Arcadia and Capella knowledge, programming skills We’ve validate the approach through interviews and an industrial case with: ꟷ 12 Functional chains ꟷ 4 levels of nesting ꟷ 3 levels of functions + set of re-usabes functions ꟷ ~35 functions (most used 2+ times)
  • 26. Work in progress 26 Design Space Exploration - The user can vary timing parameters - min-max durations - iteration numbers - weights of conditional arcs - Allocate functions to resources - Defining duration as a function of involved components Quantifying other properties (e.g., cost, reliability) - Specifying parameters - Exporting components for analysis using other techniques Early example
  • 27. Summary 27 To note: - We’ll write a generic report - We consider releasing the code, subject to discussions: - On licensing - Vision of project stakeholders 1. Create a ‘simulatable’ Functional chain 2. Export and run the chain in POOSL 3. Visualize result (TRACE4CPS) ꟷ Interested in POOSL-TRACE4CPS native integration? Check TRANSACT project (https://transact-ecsel.eu/). We created a way to simulate Functional Chains with steps: ꟷ Interested about MBSE and high-tech industry? Check ESI report ‘MBSE in the high-tech equipment industry’ https://esi.nl/news/blogs/mbse-tno-report-2022 Some leads:
  • 29. Conclusions – Solution Space 29  Proof of Concept delivered  Simulation of Workflows  Capella Integration  Systems Engineering Goal  Prevention of double recording of Information  Customer Value Maximization through design space exploration
  • 30. Conclusions & Next Steps 30  Collaboration with ESI  Short develop-review cycles  Regular checks on the deliverables and goals  Applying scientific methods in industry on specific cases  Next Steps  Capella Model as authoritative source of truth  Tools that use Capella Model as input Capella POOSL JAMA DSE …
  • 32. Your questions and thoughts? 32 Your experience on: 1. Quantitative analysis of any Capella diagram, not just functional chains 2. Simulation/analysis of functional chains in general