Interoperability in Aerospace Public Use Case of CRYSTAL project December 3 rd, 2013. Francesco Brunetti, Politecnico di Torino
Summary CRYSTAL Overview; CRYSTAL WP2.08: Public Use Case; Public Use Case, interoperability example; Review and next steps.
1. CRYSTAL Overview CRitical system Engineering AcceLeration More efficient design of safety critical systems; User-driven approach (Users, Bricks, IOS, RTP); 4 critical domains.
2. CRYSTAL WP2.08: Public Use Case Real Design processes definition (entire product life); Engineering Methods definition and allocation over the defined workflow; Preliminary Concepts definition (main sizing, behaviour/functional models); Trade-off underway;
2. CRYSTAL WP2.08: Public Use Case Engineering methods for the Public Use Case: Analyze Requirements Verify Design against requirements Fault-tree generation Heterogeneous Trade Off Analysis Change Impact Analysis Maintain Consistency between multi-viewpoint models Show traceability between all data Provide Process Management Put all data under configuration control Search Data Provide Specification
3. Public Use Case interoperability examples DS Dymola - Request List of available - Get 1 Engineering Method example: Heterogeneous De-icing physical Ontology (e.g. via XML file) for Artefact Definition: Type: Name of : ID: Reference System: Date of creation: Author: Input: Output: Formalism: Author: ID:. 2 Request is send to ontology to determine the information required for an artefact of type simulation model IBM Rhapsody Controller State-based Files Simulink (IOS core + service extensions): Valve In Dymola, launch service Supplier Request list of Purpose: available OEM Engineering Intranet Engineering Intranet The research leading to Type: these Requirement results has received funding from the European Union s Seventh Framework Programme simulation Statement: model
3. Public Use Case interoperability examples Engineering Method example: Heterogeneous DS Dymola - Request List of available - Get De-icing physical A Request is send to all tools connected to the RTP in the sense: Do you have Artifacts of type with this metadata? 3 Ontology (e.g. via XML file) for Artefact Definition: IBM Rhapsody Controller State-based Files Simulink (IOS core + service extensions): Valve Type: Name of : ID: Reference System: Date of creation: Author: Input: Output: Formalism: OEM Engineering Intranet Purpose: Type: Requirement Statement: Author: ID:. Supplier Engineering Intranet
3. Public Use Case interoperability examples Engineering Method example: Heterogeneous DS Dymola De-icing physical IBM Rhapsody Controller State-based Files Simulink Valve - Request List of available - Get OEM Engineering Intranet Type: Name of : xxxx ID: xxxx Reference System: xxxx Date of creation: Author: etc. Input: Output: Formalism: Purpose: Type: (IOS core + service Rhapsody and Simulink do have extensions): (= artifacts of type simulation model ) with the requested set of meta-data. They sent a list back to Dymola The research leading to these results has received Name of : funding from the European Union s Seventh Output: Framework Programme Valve Reaction (FP7/2007-2013) for CRYSTAL Critical System ID: Engineering Acceleration Joint Undertaking under Formalism: grant agreement Simulink n FMU 332830 Reference System: Date of creation: Author: Input: Output: Formalism: Purpose: 4 Type: Name of : Valve ID: VSM 213 Reference System: ATR De-icing System Supplier Author: Mr. X Engineering Intranet Date of creation: November 6, 2013 Input: Temp., Pressure Purpose: Simulate the opening and closing of valve
3. Public Use Case interoperability examples Engineering Method example: Heterogeneous 5 8 In Dymola, after selecting the model from Simulink, launch service Get - Request List of available - Get In Dymola, run combined simulation with simulation model from Simulink DS Dymola De-icing physical OEM Engineering Intranet IBM Rhapsody Controller State-based Request is forwarded to other tools Simulink (IOS core + service extensions): 6 Files Supplier Engineering Intranet Valve 7 In Simulink, send back the requested simulation model
4. Review and next steps First set of realistic data for the de-icing system has been defined Requirements, top-level functions, concept overviews, concept refinement including refined functional views and product breakdown structures + traceability links between all artefacts Preliminary system functional design, as well as Trade off analysis are underway; First list of engineering methods defined and mapped on design processes, Development of demonstrator is ongoing So far, traceability/ change impact analysis engineering method has been partially implemented