EDA LAVOSAR Workshop #2 "Industry Workshop" (Brussels, 25Th June 2013) Dr

EDA LAVOSAR Workshop #2 "Industry Workshop" (Brussels, 25Th June 2013) Dr

EDA LAVOSAR Workshop #2 "Industry Workshop" (Brussels, 25th June 2013) Dr. Norbert Härle Rheinmetall Defence Electronics - Head of Technology Strategies ( phone: +49 421 457-1503 fax: +49 421 457- 4415 mobile: +49 151 14805589 * e-mail: [email protected] © Rheinmetall Defence 2013 1 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Land Vehicle with Open System Architecture (LAVOSAR) - Agenda - 10:30 – 10:45 Introduction by the EDA 10:45 – 11:30 LAVOSAR Study presentation 11:30 – 12:45 Requirements, Standardisation and Business Case 12:45 – 13:30 Lunch break 13:30 – 15:30 Computing and Communication Environment 15:30 – 16:30 Functional and Technical Architecture 16:30 – 17:00 Concluding Remarks and Way Ahead Dr. Norbert Härle, VET © Rheinmetall Defence 2013 2 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) LAVOSAR Project Participants . EDA . Thales SA (FR) – Marek Kalbarczyk (Project Officer) – Benoit Senechal . Fraunhofer FKIE (DE) . Thales Communications and – Daniel Ota Security (FR) – Ralph Erdt – Olivier Schmidt . Rheinmetall Defence . Thales Optronics Limited (UK) Electronics GmbH (DE) – David Kempton – Norbert Härle . VRC (UK) – Oliver Prenzel – Aditya Deshpande . Selex ES (UK) – Elias Stipidis – Edouard Mouchel – George Valsamakis – Guy Davies Dr. Norbert Härle, VET © Rheinmetall Defence 2013 3 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Visting Participants (status 20 June 2013) Christopher HUGHES, AnCoast Ltd. Maximilian SCHOEPPNER, Krauss-Maffei Kristoffer BIEL, BAE Systems Bofors Wegmann GmbH & Co. KG Ian NICHOLSON, BAE Systems Combat Vehicles Helge Eduard WERNER, Matrium GmbH Uwe MUENCH, BAAINBw K1.2 Florian WALZ, MBDA Germany Maximilian Bornefeld-Ettmann, BORNEFELD- Jens KARLSSON, MilDef AB ETTMANN CAUSA GmbH & Co. KG Marian GILCEAVA, National Company ROMARM Martin SCHOESSLER, CAUSA GmbH & Co. KG Lorenzo ABAD MENOR, Navantia Sistemas Andre GOOSEN, Cassidian, EADS Deutschland Jose DOMINGO SALVANY, NEXTER Electronics GmbH Julia LOPEZ DE LA TORRE LUCHA, NTGS Francois PRENOT-GUINARD, Cassidian Teemu ALAKOSKI, Patria Land Systems Oy Jürgen DEBUSMANN, Causa Consulting William CATHERINE, Renault Trucks Defense Olivier VOISIN, DGA Catherine WILLIAM, Renault Trucks Reinhard SCHMIEDL, Diehl Defence Holding John STRETTON, Ricardo plc GmbH Marco MANSO, RINICOM Jean Albert EPITALON, French Land Defense Garik MARKARIAN, Rinicom Ltd Industry Association GICAT Petter GARDIN, Saab AB Kees-Jan HERMANS, FOX-IT Mario CIAVATTA, Iveco Piergiorgio FOTI, Selex ES Mauro MARCHISOTTI, Iveco Defence Vehicles Louisa DUBOIS, Steria Stefano PIOVAN, Iveco Defence Vehicles Joachim STRAY, Thales Norway Mariusz WIŚNIEWSKI, WB ELECTRONICS S.A. Dr. Norbert Härle, VET © Rheinmetall Defence 2013 4 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Background . EDA contracted the study Land Vehicles with Open System Architecture LAVOSAR (EDA Contract 12.R&T.OP.336 with 345K€) . Study execution between 1 Feb. 2013 and 30 Nov. 2013 by – Rheinmetall Defence Electronics GmbH with subcontractors – Fraunhofer FKIE, – Selex ES, – Thales Communications and Security, – Thales Optronics Ltd., and – Vetronics Research Centre . Objective is – to define an electronic and information reference architecture for military land vehicles – to be published and proposed as Land Vehicle Open Architecture for Mission Systems – architecture • shall serve as a reference solution for developing and implementing mission systems for vehicles • is for integrating the mission subsystems into a completely networked vehicle capability configurable depending on the vehicle or mission requirement. Study will make recommendations for an EU standard as well as influence the NATO Generic Vehicle Architecture. Dr. Norbert Härle, VET © Rheinmetall Defence 2013 5 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Workshop #2 "Industry Workshop Objective is involvement of stakeholders . Workshop #1 with government officials at the 23 April 2013 (feedback from procurement and maintenance side) . Workshop #2 with Industry (feedback about state of the art and potential future technology) APPROACH . inform industrial stakeholders about the current status and the current results. Feedback and refinement to the intermediate project results (WP1) – normative framework, – best practices and standards, and the – business case and roadmap . as well as (WP2) – computing and communication technologies, – mission system technologies, – current architectural structures, – forecasts . Feedback about current and potential future architectures (WP3) Dr. Norbert Härle, VET © Rheinmetall Defence 2013 6 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Terminology Open Reference Architecture . Comprehensive best practice architecture with all necessary views from which a target architecture for a specific system can be derived and which is maintained by an open, public consensus process of an open forum. There are no barriers to implementation by a third party: – No Secrets: MUST include all details necessary for implementation. – Availability: MUST be freely and publicly available (e.g., from a stable web site) under royalty-free terms. – Patents: All patents essential to implementation MUST: • be licensed under royalty-free terms for unrestricted use, or • be covered by a promise of non-assertion when practiced – No Agreements: There MUST NOT be any requirement for execution of a license agreement, NDA, grant, click-through, or any other form of paperwork, to deploy conforming implementations. – No Incompatible Dependencies: Implementation MUST NOT require any other technology that fails to meet the criteria above. Dr. Norbert Härle, VET © Rheinmetall Defence 2013 7 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Terminology Modular Architecture . designed in such a way as to allow the replacement or addition of sub-systems and upgrades as required without any undesirable emerging properties. Military Land Vehicle . Manned or unmanned mobile machine that performs a mission (surveillance, reconnaisance,, combat, transport, etc.). It is subdivided into – a Vehicle Platform, – a Vehicle Mission System, – the Mounted User(s), and – Stores Item(s) . Each vehicle carries only one missions system at a time. The mission system might be changed by replacing, adding, or taking away one or several subsystems which will again build the single mission system. Vehicle Platform . The platform for the mission system which comprises all primary automotive subsystems and controls (incl. passive protection) and which is approved for driving on public roads Vehicle Mission System . Vehicle equipment which is not needed for the primary automotive function, but is needed to perform a certain mission such as surveillance, reconnaissance, combat, communication, etc. Dr. Norbert Härle, VET © Rheinmetall Defence 2013 8 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Open System Architecture Principles and Advantages ©LEGO [1] Open Architecture (OA) is Key to Cost Efficient Vehicle Life Cycle Advantages: Characteristics: •Reduce Vendor Lock-in •Open, publicly available specifications, • Larger Market, Enhanced Competition •Well-defined, Widely used • Continuous Innovation Non-proprietary (Standard) Interfaces, • Independent Upgrade of Subsystems Services and Formats with minimal Impact on Overall System • Durable Component Interfaces • Decrease Costs for System Engineering, (stable or slowly evolving) Integration, Verification & Validation • Decoupled Mechanical, Hardware, • Reduce Training Software Interfaces • Facilitate Equipment Sharing [1] Definitions based on: Capt. T.J. Strei, United States Navy, “Open Architecture in Naval Combat System Computing of the 21st Century”, 2003 Dr. Norbert Härle, VET © Rheinmetall Defence 2013 9 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Introduction & Background: DefStan 23-09, Generic Vehicle Architecture Approach: Interface Standardization & Interfaces & Boundaries Design Constraints, e.g. IP-Networked Vehicle . Data Distribution Service (DDS) as Data Exchange Mechanism . Land Data Model . Electrical Interfaces & Plugs . Power Supply . Common Crew Station . IP-based Video Distribution (DefStan 00-82) • Issue 1: 20 August 2010 Objective: • Issue 2: October 2011 . Improved Operational Effectiveness • Issue 3: to be expected . Reduced Integration Risks . Part 0 – GVA Approach Introduction . Part 1 – GVA Infrastructure . Reduced Cost of Ownership . Part 2 – GVA Human Machine Interfaces (HMI) . Part 3 – GVA Health Usage Monitoring System (HUMS) . Part 4 – GVA Physical Interfaces Dr. Norbert Härle, VET © Rheinmetall Defence 2013 1010 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Dr. Norbert Härle, VET © Rheinmetall Defence 2013 11 EDA LAVOSAR Workshop #2 - "Industry Workshop" (Brussels, 25th June 2013) Beyond DefStan 23-09 Not only Interface Standardization & Design Constraints but: Comprehensive Open Reference Architecture . Electronic & Information Technological Reference Architecture . Consideration of Full Life Cycle of Vehicle . Interoperability (Mechanics, Electronics, Software) . Plug-and-Play . Scalability & Extensibility . Flexible & Modular Building Blocks . Service Definitions & Orchestration (Common & Mission System Services) . Standardized Gateways (e.g. to Soldiers, other Vehicles, C4I) . Security & Safety Considerations

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    21 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us