Model Based Development Approach AUTOSAR Functional Safety - MATLAB EXPO
Model Based Development Approach –AUTOSAR Functional Safety AspiceNishant TholiyaAVP & Business Leader – Automotive Product Engineering Services
KPIT Industry Focused SolutionsAutomotive &TransportationManufacturingEnergy & UtilitiesKPIT Product Engineering & Enterprise ITEmbedded Software Product & Engineering Design IT Platforms & SolutionsProcess modernization using IT Cloud & Big Data Analytics PLM Digital Transformation Infrastructure Management Solutions24/24/2017 KPIT Technologies Limited
Automotive and Allied Engineering - Snapshot10SSEP2013Product Engineering to make mobility Smarter, greener, safer & affordableProduct Engineering Solutions AcrossAUTOSAR &In VehicleNetworksBodyElectronicsChassis , Autonomusand Driver AssistanceEngineeringDesignFunctional SafetyISO 26262InfotainmentToolsProducts Business PortfolioK-SARAUTOSAR SuiteWorlds’ FIRST AUTOSAR R 4.0.3SolutionProductsRTE Basic SoftwareStack MCAL3ODX Designer OTX Suite Diagnostic IDE/RTEBMSKIVIBattery Management SystemsKPIT In VehicleInfotainment PlatformAutomotive Stationary Applications4/24/2017 KPIT Technologies LimitedPlug In Parallel Hybrid SolutionInstrument ClustersPowertrainVehicle DiagnosticsPeople withpassion forTechnologyOEMs & Tier 1swho benefitfrom ourtechnology4500 85 VehicleProductionProgramsimpacted by usTotal number ofprojectsexecuted350 2000
The Global Automotive Industry is in a Transformational phase .Electrification &Fuel EfficiencyElectric vehicles to be 35% of global new car sales by 2040Various Geos offers imperatives and constraints for Electric vehicle adoptionsConnectivity89% of new cars sold worldwide will have embedded connectivity by 2024Autonomous Driving10 Million Self-Driving Cars Will Be On The Road By 2020Consumer ExperienceVehicle customization, ride sharing, personalization, multi modaltransport considered game changers by Automotive industryWe are moving towards the world of Autonomous, Connected, Fuel Efficient, Lightweight vehicleswith personalized Consumer Experience44/24/2017 KPIT Technologies Limited
Functional SafetyModel based systemand softwareengineeringIncrease in AutomotiveControls SystemComplexityAutosar PlatformapproachPlatform strategiesIntegrated modelbased developmentenvironment54/24/2017 KPIT Technologies Limited22DEC2014Future trends imposing technical need of standard compliance and change indevelopment workflowDevelopment NeedsTechnical Needs
KPIT’ Feature Development MBD workflow: Focus on ‘Continuous Verification’Compliant to ISO26262, ASPICE and Autosar standardsKey Differentiators:-System EngineeringBest PracticesConceptProduction1. FeatureRequirements10. Acceptance Testing/Calibration TuningV12. System-Functional Safety AssessmentsRequirements- Use Case ScenariosDevelopment/- Requirements ManagementModeling-Rapid Prototyping3.1. RCP(MIL/PIL/HIL/Real Plant)3. ConceptDevelopment- Extensive tool suite experiencein Rhapsody & Matlab/Simulink- Leader in AUTOSAR9. HIL Testing / - Extensive tool suitePlant Modelexperience inDevelopment Industry toolsArchitectureGuidelinesSystemArchitecture- Completely automated verification ofMatlab models to comply with leadingindustry standardsModelingGuidelines- An adaptive & integrated solution forModel Based Engineering5. SoftwareArchitecture Design7. MIL/SIL Testing6. Auto code Generation64/24/2017 KPIT Technologies Limited8. Software IntegrationTesting4.1. MILModel BasedCalibrationModelDevelopment4. ExecutableSpecificationDevelopmentV2- Extensive tool suite experienceUsing Real Time Workshop & TargetLinkauto-coder
Functional Safety Lifecycle – KPIT InvolvementItem Definition System / SW Safety DevelopmentAlignmentIn-house System / SWSafety DevelopmentConceptKPIT involvementOEMSupplier Hazard Analysis AndRisk AssessmentKPIT experiences spans across theentire Functional Safety LifecyclePart 3 4/24/2017 KPIT Technologies LimitedFunctional Safety Assessment Functional Safety ConceptPart 4Technical Safety ConceptSafety requirementsSafe ArchitectureSafety Validation System Architecture Item Integration & TestingH Part 5Performed byOEMSafety verificationHW LifecycletestingPart 6 SW development using Model BasedIntegrationworkflowUnit design & code7Release for ProductionSW LifecyclePart 6 Unit testing
ISO26262: Part 6 : REQUIREMENTS & METHODSSoftware Safety RequirementDerivationHARASafetyGoalFSC1. RequirementsRequirements based testing ontarget – Reuse MIL test vectorTSCHSICDIA2. Fault injection testingISO 26262-6: Software Safety Requirment VerificationASIL Level AssignedSoftware Safety RequirementsSystem Testing3.MIL-SIL-HILClause 10: ISO 26262-6Integration Testing RequirementsClause 10 : Req-10.4.6: of ISO26262-6 Integration TestingMethods4. Interfaces validationFormal ArchitectureDesign ToolsClause 7 of ISO 26262-6Architectural Design RequirementsDesign Patterns (sensor – actuator,Diagnostics, Functionalsafety etc.)2. Component size3. Component partition4. Cohesion andClause 7: Req-7.4.18 of ISO 26262-6CouplingArchitectural Design Verification Methods5. Variant Management6. Architecture Views andReport generation7. Architecture evaluationcriteriaIntegrationTesting1.84/24/2017 KPIT Technologies tation1. Textual requirements validation –Executable specificationClause 8 of ISO 26262-6Unit Design & Implementation RequirementsClause 8: Req-8.4.5 of ISO 26262-6Unit Design Verification Methods2. Functional validation – MIL5. Memory optimization manualanalysisClause 9: ISO 26262-6Unit Testing RequirementsClause 9: Req -9.4.3 of ISO 26262-6Unit Testing Methods1. Functional validation – MIL2. Back to back testing – Model andCode (MIL – SIL)Clause 9: Req -9.4.4 of ISO 26262-6Unit Testcase Generation MethodsClause 9: Req -9.4.5 of ISO 26262-6Test Coverage Matrix Methods3. Coverage testing using Auto testcase generated from Design Verifier.Measures for unintendedfunctionality
Motivation & Implications of migrating to AUTOSARMain motivation to migrate from the legacy software is to manage the increasing complexityof the increasing electronics and software complexity and at the same time: Improve quality Reduce cost Reduce time to marketTypical challenges when migrating from the legacy software to AUTOSAR Software migration & complexity Variants management Configurator vs. implementer New technologies94/24/2017 KPIT Technologies Limited
SW-CApplicationDiagnosticServiceManagementPlatform specificSWBootloaderSoftware migration & complexitySW-CSW-CSW-CMCAL 10Application MigrationApplication integration with BSWBSW License – delivered pre-integrated with MCALDiagnostics integration and configuration4/24/2017 KPIT Technologies Limited BSW configuration Most services are available in AUTOSARProject specific complex drivers and I/O abstractionBootloader integrationSWC unit testing and Rapid Prototyping
Workflow of AUTOSAR Application Migration using MBD1. SystemRequirementDevelopment10. Vehicle testingand calibrationTest Cases For Testing Functional Test Cases Integration Test Cases2. s Document8. SoftwareIntegration andtesting4. Architecture &Design ModelSWC/RunnableInterface/DataType9. HIL TestingApplication (SWC.arxml)3. SoftwareRequirement Communication MatrixAnalysisAUTOSAR I/FConfigurationRte.exe5. Modeldevelopment.c/.h7. MIL/SIL TestingEmbedded CoderAUTOSAR Block setTest ReportECU-Extract/dbcBSW Platform &RTE ConfigIntegration &TestInterface TestService ComponentIoHwAb ComponentK-SARAUTOSARSuiteAUTOSARConfiguration ToolsCompliance6. Auto code GenerationAUTOSAR ACG c/.hAtomic SW-C.arxml KPIT Technologies LimitedKPIT Tools
Round trip approach –AUTOSAR Compliant Development1 Create AUTOSAR Architecture2 Import ARXML & Create Frame Model3 Update Detail logic7 Merge ARXML6 Generate ARXML124/24/2017 KPIT Technologies Limited5 Generate Code & Preform SIL4 Perform MIL Validation
Automotive Spice – Software Quality Assurance StandardMAN.3 – Project ManagementMAN 5 – RiskManagementENG 1 – RequirementElicitationENG 10 – SystemtestingENG 2 – SystemRequirement AnalysisENG 9 – Systemintegration testENG 3 – SystemArchitectural DesignENG 8 – SoftwaretestingENG 4 – SoftwareRequirement AnalysisENG 5 – SoftwareDesignSUP 1 – QualityAssurance134/24/2017 KPIT Technologies LimitedSUP 8 – ConfigurationManagementENG 7 – Softwareintegration testNeed integratedenvironmentto managerequirementsENG 6 – SoftwareConstructionSUP 9 – Problemresolution mgmtSUP 10 – ChangeRequest management
KPIT approach : Integrated tools environment for ASPICE compliantworkflowRequirementsManagement ToolArchitectureModeling ToolSystems and ControlsModeling ToolAuto-code ToolMIL/SIL/HIL TestingToolEngineering WorkflowSystemsControlsSoftwareV&VObjective: Allows management of product lifecycledevelopment based on PLA principles Allows traceability throughout productdevelopment lifecycle Allows impact analysis across product linesand engineering artifacts Allows management visibility of the wholeprocess Enable global collaboration Process and standards compliance (CMMI,AutoSpice, SAE, ISO 26262)Integrated InfrastructureConfigurationManagement ToolChange/IssueManagement ToolData DictionaryWorkflowManagementToolALM Environment144/24/2017 KPIT Technologies LimitedTest ManagementBuild and ReleaseManagement
Summary 154/24/2017Model based development is way forward to develop Automotive controlssoftwareModel based development is well suited to develop controls software compliantto Automotive standards ISO26262 ASPICE AutosarIncreasing electronics content in Automotive is increasing system complexity,needs many engineers with expertise in Model based development. KPIT Technologies Limited
Our approach to meet demand - ECoDe – developing right talentto cater to customer demandsKPIT Learning ModelECoDe KAIZEN -Continuous Up gradation and Certificationsacross all the experience levelsOn goingGENESISFreshEntrantsFresh Engineers Induction ProgramEngineering AcademiesPACEBeforeJoiningKPITInitiative to bridge the gap betweenAcademia & Industry needs Credit BasedFramework toTrain and CertifyemployeesPACE: Program for Academic Collaboration and Engagement KPIT Technologies LimitedCopyright KPITELEVATE LIFT ASPIRE SOFTSKILLSLeadership Development Programs tomentor Emerging & Existing Leaders40-40-20Academy SME KPIT SME VendorPartners ModelCollaborative Education ModelGuest LecturesFaculty EnablementKPIT offered electivesInternships & ProjectsStudent ContestsIndustryReadiness16 Automotive ElectronicsTechnologies andDomains CompetencyFrameworkaligned to Roles& Career StreamsCollaborations with InternalStake holders and ExternalPartnersStrongBaseCurrent &RelevantGENESIS (6-8 weeks)Every Campus recruited engineer trained& ready for customer projects
Program for Academic Collaboration & Engagement (PACE) & GENESISUnique Initiative of KPITProgramme objectives1“PACE” Programme partnership kit for academicinstitutions2MOUs with 20 Partner Institutions aligned to SBUneeds3Standard education artifacts in partnership with SBUs &Academies and repositories4KPIT created courses approved by Academic boardsand taught as part of Curriculum5Through “Train the Trainer” Faculty enablementprogrammes & exchange programmes 60 facultytrained6Joint partnership for deployment & support institutionsSBU Aligned fresher induction and deployment7PACE linked to Campus hire, Internships andprospective employee engagementFaculty Development through collaborations8Induction to SBUs and Accounts –additions skill gaptrainings as per needsBuild KPIT Brand in Universities / Institutions to attract theright talentHire the Right motivated talent for each practiceQuicker deployment on projects / reduce internal trainingtime / costs /effortsRepresentation on Academic boards of Institutions Toinfluence education SystemWork to create Industry ready niche resources17 KPIT Technologies LimitedCopyright KPIT
Thank Youwww.kpit.com184/24/2017 KPIT Technologies Limited
Product Engineering to make mobility Smarter, greener, safer & affordable AUTOSAR & In Vehicle Networks Body Electronics Chassis , Autonomus and Driver Assistance Engineering Design Functional Safety ISO 26262 Infotainment Instrument Clusters Powertrain Vehicle Diagnostics Product Engineering Solutions Across AUTOSAR Suite K-SAR
AUTOSAR 3.x AUTOSAR 4.x AUTOSAR 3.x is used in serial production projects by: Audi / Volkswagen / Porsche Daimler Fiat / Chrysler Volvo Trucks (incl. Construction Machines) AUTOSAR 4.x is used in serial production projects by: BMW GM Toyota Volvo Cars AUTOSAR 4.x is generally announced by Ford PSA
2 Introduction to AUTOSAR Simulink approach to AUTOSAR Overview of Modeling SWCs & Modeling Styles AUTOSAR Design Workflows Bottom Up, Top Down & Round Trip Advanced Topics –Top 5 Startup, Reset, and Shutdown Modeling Basic Software (BSW) Access J-MAAB Type B Architectu
Adaptive Environment - The AUTOSAR Adaptive environment for adaptive design AUTOSAR Builder is based on Eclipse and uses Artop. Artop is an open AUTOSAR tool environment that is available for free. It enables you to build your own tools and integrate from other tool vendors. For more details, see the AUTOSAR Builder Overview document. 1.
Simon Fürst, BMW Group Safetronic 2011 8 Nov. 2011, Sheraton Arabellapark Hotel, Munich. 2 8 Nov. 2011 AUTOSAR and Functional Safety . Basic aspects of AUTOSAR architecture and methodology Safety mechanisms supported by AUTOSAR Technical safety concepts supported by AUTOSAR Relationship to ISO 26262 and Conclusion
AUTOSAR User Group, i.e. the Artop User Group . –It is a group of AUTOSAR members and partners, i.e. users of AUTOSAR, with a special interest in AUTOSAR tools. –Was launched in October 2008 and the members currently are: –Continental –Geensys –Peugeot Citroën (PSA)–BMW Car IT –New members are welcome to join the User Group.
Both, Releases 2.0 and 2.1, are in use by several AUTOSAR members for series produc-tions. 2.2. Overview on AUTOSAR Phase II Three releases had been planned for AUTOSAR Phase II, providing a continuous improve-ment of the specifications and introducing new concepts. Release 3.0 was published early 2008 on the AUTOSAR web site [1]. It included a .
the AUTOSAR architecture with a message-based NoC and to evaluate the impact of the hardware choices (e.g. multi-core topology, NoC configurations) on the AUTOSAR software. The contribution of this paper is a co-simulation framework supporting the simulation of time-triggered message-based multi-core processors hosting AUTOSAR-based software that
AUTOSAR Methodology at BMW Page 2. OVERVIEW. AUTOSAR Versions and Roadmap Configuration Process until Generation 2015 Vision Generation 2021 and Current Status Generation 2018 Tool Architecture Tool Development ECU Configuration Flow AUTOSAR Tool Requirements for the Future
