Orchestration of automated vehicle functions

Transcription

1 Orchestration of automated vehicle functions Automotive Electronics Systems Conference 2016

2 Overview Orchestration of automated vehicle functions Automation of vehicle functions Use of service oriented architectures for the planning, reconnaissance and decision making of automated vehicle functions The role of supervisory services in automated vehicle functions Trade-off analysis of non-functional requirements for automated vehicle functions

3 Reference levels of automation SAE J3016 Copyright 2014 SAE International

4 Reference levels of automation Automated driving system monitors driving environment Human driver monitors driving environment No automation Driver assistance Partial automation Conditional automation High automation Full automation

5 Automation of Vehicle Functions Planning Reconnaissance Decision making Supervision

6 Supervision in Automated Vehicle Functions

7 System of systems regulators interfaces companies Sat Comms data Cloud services outputs sensors Roadside station Storage people inputs vehicle actuators

8 challenges Projects and programmes are not so independent anymore, they link and overlap Multiple operational, technical and service boundaries are emerging Coherent management of mixed assets and criticality is required

9 Service Oriented architecture Why we need a service approach and what it involves Defining how people, organizations, and systems provide and use services to achieve results High level description of the services and flow of information is between the constituent parts Better view on risk Incorporating human, organisational or technological failure modes Services act as an abstraction layer for different implementations

10 Enterprise Architecture Enterprise architecture provides frameworks, tools, and techniques to assist organizations with the development and maintenance of their SOAs Enterprise architecture in its widest sense includes much more than IT. Business operations, finance, people, and buildings in addition to technology, and it covers technologies other than IT, such as manufacturing or transport. Establishes governance

11 EA Benefits Consistent abstractions of high-level strategies Linking different perspectives to a single business problem Identification of deliverables to support planning and analysis providing a consistent model to address various domains and tests for completeness clear roadmaps to achieve future goals, changes and requirements Traceability links IT and other assets to the business they support Support impact assessment, risk/value analysis, and portfolio management Identified and documented principles, constraints, frameworks, patterns, and standards Governance frameworks processes that ensure appropriate authority for decision-making

12 Enterprise Architecture Frameworks Enterprise architecture supports the whole enterprise, especially the business processes, technologies, and information systems of the enterprise using a skeletal structure that defines suggested architectural artifacts, describes how those artifacts are related to each other, and provides generic definitions for what those artifacts might look like

13 NEC and IoT Network Enabled Capability (NEC), coherent integration of sensors, decision-makers, weapon systems and support capabilities to achieve the desired effect The Internet of Things (IoT), is the network of physical objects that contain embedded technology to communicate and sense or interact with their internal states or the external environment and some of them even work largely without human intervention. The GSMA has highlighted the following two relevant topics under the automotive vertical of IoT Connected and autonomous vehicles Multimodal transport

14 MODAF MODAF is an internationally recognised EAF developed by the MOD to support Defence planning and change management activities. Enables the capture and presentation of information in a way that aids the understanding of complex issues, It is used extensively in Defence acquisition to support systems engineering, particularly in support of Network Enabled Capability (NEC), coherent integration of sensors, decision-makers, weapon systems and support capabilities to achieve the desired effect

15 Modaf- Views MODAF provides a set of templates (called Views ), each MODAF View offers a different perspective on the business to support different stakeholder interests, presented in a format, usually graphical, that aids understanding of how a business operates.

16 MODAF- Viewpoints The Views are divided into seven categories (Viewpoints): Strategic Viewpoint (StV) defines the desired business outcome Operational Viewpoint (OV) defines the processes, information and entities needed to fulfil the capability requirements; Service Orientated Viewpoint (SOV) describes the services, required to support the processes described in the operational Views; Systems Viewpoint (SV) describes the physical implementation of the OV and SOV, thereby, define the solution; Acquisition Viewpoint (AcV) describes the dependencies and timelines of the projects that will of deliver the solution; Technical Viewpoint (TV) defines the standards that are to be applied to the solution; All Viewpoint (AV) provides a description and glossary of the contents of the architecture.

17 Orchestration To yield the most benefit the use of a service oriented approach supported by an enterprise architecture framework is proposed In order to link effectively Technology Business People Process Tech Standards Strategy Operations Solutions Acquisition Holistic planning, reconnaissance and decision making of automated vehicle functions

18 Requirements Trade off Strategy Operations Solutions

19 Requirements Trade off Strategy Operations Tech Standards Solutions Acquisition

20 Tech Standards NHTSA Federal Automated Vehicles Policy Policy released 19SEP16 The Agency will request that manufacturers and other entities voluntarily provide reports regarding how the Guidance has been followed. This reporting process may be refined and made mandatory through a future rulemaking. Submit a Safety Assessment to NHTSA s Office of the Chief Counsel for each HAV system, outlining how they are meeting this Guidance at the time they intend their product to be ready for use (testing or deployment) on public roads. Analyses are required when applicable, the broader transportation system.

21 Conclusions Traditional document based, information sharing approaches may not be sufficient to support the development of automated vehicle functions Rapid changes in business models, capability enablers, user requirements and legal framework require a more orchestrated approach to automation in vehicle functions A richer ecosystem with multiple stakeholders and services involved in the delivery of a highly automated vehicle function requires multiple viewpoints to provide a strong mechanism for governance A standardised architecture framework that all involved stakeholders can share and use may be key to share information and fulfil customer requirements