A View on Tool Interoperability Solutions at Ford Motor Company

Transcription

1 A View on Tool Interoperability Solutions at Ford Motor Company r. Ahsan Qamar Vehicle Controls & Systems Engineering Research & Advanced Engineering Ford Motor Company

2 Contributors Kurt Osborne (Electrical & Electronics Systems Engineering) Slide Eileen Title avidson (Powertrain Engineering) Bill Bailey (Vehicle System Analysis) George Walley (Vehicle Controls & Systems Engineering) Chris avey (Vehicle Controls & Systems Engineering) Advanced Engineering

3 istributed evelopment Software Engineering Project Management robustness regulatory compliance profit active safety reliability cost geometry production rate Passive safety Systems Engineering Fuel consumption maneuverability mass Powertrain Controls Vehicle Controls Production CA/CAE Advanced Engineering 3

4 Old Landscape Stakeholder/Attribute Requirements Functional Concepts FMEA etailed esign & Analysis Support & Maintenance Production Plan Quality Supply Chain Calibration Advanced Engineering 4

5 Old Landscape Stakeholder/Attribute Requirements Functional Concepts FMEA Some Partial Integration Mostly Information Silos etailed esign & Analysis Support & Maintenance Production Plan Quality Supply Chain Calibration Advanced Engineering 5

6 Current Landscape VSEM Supported Integration SW System evelopment Software Release Software Update 6

7 VSEM Global Feature ictionary Global Features reference hierarchical decomposition of derived Functions The VSEM Feature- Function Architectural Framework supports: Software System Feature development lifecycles that are decoupled from traditional hardware component based engineering. Engineering Work Products to be immediately accessible and re-usable based on Feature mapping. 7

8 VSEM Supported Software elivery Active Safety Powertrain Controls Chassis Controls Production Software EESE Climate Controls Infotainment Advanced Engineering 8

9 Interoperability Goals 9

10 Goal 1: Inform About ependencies Software Engineering Systems Engineering Powertrain Controls Project Management Vehicle Controls Production CA/CAE Advanced Engineering 10

11 Goal 2: Manage Change Across isparate & Heterogeneous Models Slide Software Title Engineering Systems Engineering Powertrain Controls Project Management Vehicle Controls Production CA/CAE Advanced Engineering 11

12 Goal3: Make ecisions Based on Information from Multiple ata Sources Overall fuel Efficiency Changing an ECU Solution to overlapping concerns ecision Maker Requirements coverage System Engineering Analysis Software evelopment CA/CAM Advanced Engineering 12

13 Goal 4: Facilitate ata Exchange About Managed Artifacts Between ifferent Enterprise Systems Calibration Requirements Test Advanced Engineering 13

14 Current State of ata Exchange Standards Limited to exchange of geometric and configuration data STEP AP203 (Mechanical), AP 209 (Structural), AP 210 (Electro-Mechanical), AP 239 (PLCS), JT visualization STEP AP 233 systems engineering > slow uptake Product data exchanged in native file formats, informal communication or document-based Standards mostly focus on how to move data from one place to the other Not (always) necessary to migrate data OSLC web of engineering data -> lightweight Advanced Engineering 14

15 Interoperability With Suppliers 15

16 Powertrain Controls Most of the code done in-house A mix of model-based code generation and hand code Gas powertrain river software (which is hardware dependent) is supplier-developed Interface specifications provided to the supplier (document-based) iesel powertrain Supplier-built software (COTS) Mostly model-based, but also hand code Gasoline Models are not shared with suppliers, but iesel s are Migrating towards AUTOSAR in the near future Interface Spec Gas Engine Powertrain Controls Code Supplier Interface Spec iesel Powertrain Controls Supplier COTS software Advanced Engineering 16

17 Advantages with AUTOSAR Integration of new features on existing ECU s Slide Tier-1 Title application software and OEM owned SW will co-exit on an ECU Transferring SW components between ECUs, supporting flexible architectures A HW independent RTE, based on SW components, with standardized data exchange Application Software Runtime Environment (RTE) Basic SW SW-C 1 SW-C 2 Advanced Engineering 18

18 Electrical & Electronic Systems Engineering (EESE) Climate Control Model-based design -> can leverage AUTOSAR components Infotainment UML/SysML modeling is employed with Rational Rhapsody UML model shared with the supplier -> code generated from UML to C Supplier is provided both models and documents providing interface specifications Advanced Engineering 19

19 Tool Integration / Interoperability Examples 20

20 Comparison of Integration Approaches Common Vocabulary omain Vocabulary point-to-point single shared meta-model Hybrid Advanced Engineering 21

21 Example 1: Failure Mode Avoidance (FMA) FMA work is time consuming with Slide specifications Title duplicated to FMA tools FMA tools disconnected from core design tools Mandatory FMA Rubric is needed Interoperability with FMA tools Automatic import, export, and document generation Advanced Engineering 22

22 Solution Failure Mode Avoidance Work MBSE System Modeling Tool (SysML) Lean Failure Mode Avoidance (LFMA) Process iagram (P-iag) Failure Modes Effects Analysis (FMEA) Reliability & Robustness Checklist (RCL) Contributors: Walley, G., Meinhart, M., Corral, M., Nefcy, B., avison, M., Stanek, J. Advanced Engineering 23

23 Interoperability Supported Through SysML P-iagrams FMEAs RCLs Boundary iagram SysML Models LFMA VSEM - Teamcenter Advanced Engineering 24

24 Example 2: Integrated Vehicle Analysis Vehicle Model composed of various HW and Controller domain models Modelica for HW models Simulink for controller models Powertrain Eng Trn ln Exh Fuel H-ware Control Coupled data & analysis interface Addresses top of Vee Cross-omain Chassis Veh Ste Brk Susp H-ware Control Whl Integrated Vehicle Function & Attribute Analysis (IVA) Capability Veh Sys Control Arch Alg Control Comfort rivability ynamics Cross-Attribute / Cross-Function NVH Performance Energy Emissions Safety Electrical Supply Loads ist H-ware Control omain HMI Climate A/C Heat Cabin H-ware Control Sub-domain Thermal - Aero Cool Front End Underhood Model architectures, models, data H-ware Control Contributor: Bailey, W. Advanced Engineering 25

25 Integrated Vehicle Analysis - Process omain model developers then add content to the model From Finally, templates this Add models architecture, analysis-specific are integrated use custom I/O Start from a common model into a and transformations vehicle model model content and to to generate used Vehicle Reference model to perform create templates a If I/O Specialized system-level with predefined Architecture changes are in required, SysML interfaces analysis they Analysis must in Simulink come Architecture from and the Modelica. shared SysML model Advanced Engineering 26

26 Example 3 : Hybrid Approach - Models as Graphs Implict (inferable) Pattern x u y v Variable Bindings Cross-Model Relations Physical Architecture Requirements CA Geometry Model Advanced Engineering Herzig, S., Qamar, A., Paredis, C., Inconsistency Management in MBSE, GPIS 2014

27 Mediation Between Multiple Vocabularies Language Voc. #2 Language Voc. #1 omain Voc. #2 e.g., Rule 1 omain Voc. #1 e.g., SysML Language Voc. #3 e.g., Rule 2 omain Voc. #3 Base Vocabulary omain Voc. #n Language Voc. #4 e.g., OORS e.g., Requirements Language Voc. #m Inference Paths Advanced Engineering Herzig, S., Qamar, A., Paredis, C., Inconsistency Management in MBSE, GPIS 2014

28 Key Takeaways ata exchange standards have limited uptake Moving data Vs creating information traces Tool interoperability supporting product lifecycle and system engineering work is vital Reasoning over distributed sources with traceability Scalability of point-to-point vs single shared meta-model vs hybrid integration approaches Advanced Engineering 29