LAVOSAR Industry Workshop WP1 Standardisation and Business ...eda.europa.eu › docs › ... ›...
Transcript of LAVOSAR Industry Workshop WP1 Standardisation and Business ...eda.europa.eu › docs › ... ›...
LAVOSAR Industry Workshop
Guy Davies, Edi Mouchel, Selex ES Ltd
EDA Brussels, 25 June 2013
WP1 Standardisation and Business Case
This is an unpublished work created in 2013, the copyright in which vests in Selex ES Ltd. All rights reserved.
The information contained herein is the property of Selex ES Ltd and is supplied without liability for errors or
omissions. No part may be reproduced, disclosed or used except as authorised by contract or other written
permission. The copyright and the foregoing restriction on reproduction, disclosure and use extend to all media
in which the information may be embodied.
This is a working document. It remains subject to project team review and is not a formal deliverable of the
LAVOSAR contract.
Work Package 1
(complete)
Candidate Standards
Normative Framework
Business Case
Host Vehicles
Vetronics Infrastructure
(Physical, Middleware,
Storage, Power)
Sensor SystemsEffector / Weapon
Systems
Display and Control Systems
Off-
board
Comms
Service
Applications
(eg BMS)
Management
Applications
On
board
Comms
BMS / C4I
Infrastructure
Vehicle Types
Operating
Environment
Army Fleet Size
& EvolutionMissions &
CONEMP
Automotive
Interfaces
Infrastructure
Constraints
Security
Constraints
Information
Exchange
Requirements
Comms Legacy
Constraints
Supportability
Concepts
Training
Constraints
Actors, Use
Cases
Which Vehicle Types?
EDA Future Land Systems Expert Group identified opportunities
Vehicle Type Short Term Prospect
Long Term Prospect (>5 years)
Combat Contact Vehicle Some Legacy Upgrade Tactical Differences
Combat Multi-Role Vehicle Opportunity for Collaboration Opportunity for Collaboration
Combat Support Vehicle Specialist Mission Systems Specialist Mission Systems
Logistics Vehicles Vehicle Competition Preferred Vehicle Competition Preferred
Unmanned Vehicles Immature Concepts Opportunity for Collaboration
Mission System Context class Vehicle System Domain
Dismounted
User
Support User
«system»
LAVOSAR MissionSystem
«actor»
Vehicle Platform
notes
= GVA "Base Vehicle"«actor»
StoresItem
Operational Group
Vehicle
notes
= GVA "Operational System"
Mounted User
«actor»
Legacy Subsystem
LAVOSAR Subsystem
«actor»
OtherUnit
SupportEnv ironment
LAVOSAR
InfrastructureElement
«actor»
MissionCommandNet
0..*
«flow»
1
0..* 0..*
1
Mission System Users
class User Specialisation
Commander Driv er Gunner
Maintainer Instructor
Mounted User Dismounted
User
Support User
PassengerCrew Member
VehicleUserType
Civ ilian Gov ernmentAgent
SoldierMachine
notes
eg Simulator / AI
MissionSystem
UserRole
Logistics UserGroup Commander
i tsVehicleUserType
Standards
Aim of identifying small set of precise standards to bound the architecture
Previous lists of standards (CEN 10) - insufficient focus
Nominations were invited for Mission System electronic architecture
standards. Additional request to vehicle providers, remains open.
Nominations received based on best practice within the team.
Loosely grouped into categories, tabulated, reviewed and developed.
Some “Guidance” standards are included. Aim to compress list to most
architecturally relevant.
Candidate Standards (highlights)
Crewstation
• Human Machine Interface - UK GVA Def Stan 23-09
• Detailed guidance from Def Stan 00-250, MIL STD 1472
Physical Infrastructure
• Ethernet IEEE 802…
• 28 Vdc – STANAG 2601 + Def Stan 61-5
• Including connectors – Def Stan 23-09
Data Infrastructure
• Middleware - Data Distribution Service (DDS)
• On-board Video RTP/SNMP (STANAG 4697 / Def Stan 00-82)
• Off-board Video STANAG 4609
Data Model
• On-board - GVA Data Model
• Off-board - NATO STANAG 5525 – MIP (JC3IEDM)
Applicable Standards Discussion
Input invited on
• Safety infrastructure
• Security infrastructure
• Software defined radio, secure comms
• Separation of software and hardware
• Extensibility of middleware
• 28 Vdc vs Higher voltage, and over what time
Normative Framework
Government Questionnaire
Mission System Features
Use Cases
Identify major system elements
Government Stakeholder Questionnaire
EDA Participating Member Country:
General Characteristics
Number of land vehicles with Mission System expected to be upgraded
or procured up until 2023
Anticipated Year of Initial Operating Capability
Anticipated Year of Full Operating Capability
Mission System acquisition / procurement concept
Support Concept
Training Concept
Mission System Features
User Interface
Single, intuitive multi-function standard HMI display per crew station
Flexible operator role (eg gnr, cmdr) assignment to any crew station
Onboard Crew Communication Voice intercom
Crew aids for collaboration / on board (Text, Graphics, Cues, Alerts)
Head-out operation of mission system
Crew aids for collaboration / task share between vehicles in own troop
Other (please specify)
Sensors
Optical Sensors (any band) - Close Indirect Vision (driver or 360deg)
Optical Sensors (any band) - Reconnaissance, Surveillance
Optical Sensors (any band) - Target Acquisiton and Aiming (inc LRF)
Navigation - Own vehicle geo location measurement / GPS)
Acoustic (eg Sniper) Detection Sensors
Meteorological Sensors
CBRN Sensors
Other (please specify)
Effectors
Modular Weapon Subsystems (self-defence, direct or indirect fire )
Optical Effector (eg Laser Designator, pointer)
Acoustic (eg Public Address, countermeasures etc)
ECM effectors
Defensive Aids Launch (eg obscurant, smoke)
Other (please specify)
Applications (Operational, Training, Maintenance)
RSTA Automated Information Development (detect, track, recognise)
Fire Control Computation Aids
Precision Target Geo-Location
Navigation (Digital Maps)
Blue Force Tracking (awareness of own force locations)
Battlefield Information Management
HUMS, diagnostics, prognostics information development
Power Management
Integrated Electronic Test & Maintenance Manuals
Battlefield scenario simulation & training
Other (please specify)
Mission System Infrastructure
HF/VHF Voice
Data Radio
Off-board Personal Role Radio (to dismount troop)
SATCOM
Mass Storage of Mission data (audio, video, location etc)
Multiple Independent Layers of (information) Security on board vehicle
Ability to add / remove elements / re-role mission system in Theatre
Other (please specify)
Number of users per vehicle operating Mission System simultaneously
User Security Access Control to Mission System
Information & Power Exchange Requirements
Vo
ice
LS
Da
ta
HS
Da
ta
Po
we
r
Vo
ice
LS
Da
ta
HS
Da
ta
Po
we
r
Vo
ice
LS
Da
ta
HS
Da
ta
Po
we
r
Vo
ice
LS
Da
ta
HS
Da
ta
Po
we
r
Vo
ice
LS
Da
ta
HS
Da
ta
Po
we
r
Own Vehicle - Dismounted Soldier
Own Vehicle - Troop Vehicle
Own Vehicle - Command Network
Own Vehicle - Maintainer
Own Vehicle - Training Equipment / Training Environment
Own Vehicle - Dismounted Equipment
Own Vehicle - UAV/UGV (eg video downlink)
Own Vehicle - Internet
Own Vehicle - Removable Storage Media
Own Vehicle - Key material
Other (please specify)
Fixed Legacy Interface Types
Recce
mm 2013
APCMBT
LAVOSAR Study:
Vehicle Mission System Stakeholder Data Input
Notes
Date:
IFV Truck
Vehicle Type
dd
Host Vehicles
Vetronics Infrastructure(Physical, Middleware,
Storage, Power)
Sensor SystemsEffector / Weapon
Systems
Display and Control Systems
Off-board
Comms
Service
Applications(eg BMS)
Management
Applications
On
board Comms
BMS / C4I
Infrastructure
Vehicle Types
Operating
Environment
Army Fleet Size
& EvolutionMissions &
CONEMP
Automotive
Interfaces
Infrastructure
Constraints
Security
Constraints
Information
Exchange
Requirements
Comms Legacy
Constraints
Supportability
Concepts
Training
Constraints
Actors, Use
Cases
Input Needed
Known
Input NeededInput Needed
Input
Desirable
OK
OK
OK
OK
Prioritisation
Input
Desirable
Input Needed
Input Needed
OK
Host Vehicles
Vetronics Infrastructure(Physical, Middleware,
Storage, Power)
Sensor SystemsEffector / Weapon
Systems
Display and Control Systems
Off-board
Comms
Service
Applications(eg BMS)
Management
Applications
On
board Comms
BMS / C4I
Infrastructure
Vehicle Types
Operating
Environment
Army Fleet Size
& EvolutionMissions &
CONEMP
Automotive
Interfaces
Infrastructure
Constraints
Security
Constraints
Information
Exchange
Requirements
Comms Legacy
Constraints
Supportability
Concepts
Training
Constraints
Actors, Use
Cases
Input Needed
Known
Input NeededInput Needed
Input
Desirable
OK
OK
OK
OK
Prioritisation
Input
Desirable
Input Needed
Input Needed
OK
Mission System Feature Priorities
Based upon average response, top five functions for the Combat Multi
Role platform:
• HF/VHF Voice Communication
• Navigation (Digital maps)
• Battle Management
• Blue Force Tracking
• Data Radio
• Expected government priority - concerning Battle information related
Of remaining features, the following were rated important
• Crew Voice Intercom
• Close Indirect Vision
• Defensive Aids Launch
• Precision Target Location
• Off-board Personal Radio
These concern Local situational awareness
Use Cases - Command uc Commander View
Mission System
Dev elop Local
Situation Picture
Dev elop Battlespace
Situation Picture
Acquire Target
Manage
Defensiv e Aids
Manage Power
Plan & Manage
Mission
Record & Report
Situation
Dev elop Briefing
and Orders
Access and
Initialise Mission
System
Manage Vehicle
Health &
Maintenance
Commander
«actor»
Automotiv eSystem
Engage Target
«actor»
MissionCommandNet
BattlespaceDatabase
LogisticsDatabase
Dismounted User
Manage Stores
Group Commander
Mission System - Composition
class Mission System Composition
«system»
LAVOSAR MissionSystem
MissionSystem
Manager
CrewInterface
Sensor SpecialToRole
Subsystem
Mount
LAVOSAR
InfrastructureElement
CommsInterface InformationServ ice
Effector
LAVOSAR Subsystem
0..* 0..*
Sensor
class Sensor Specialisation
Camera
AcousticSensor
LaserRangefinder
OpticalSensor
InternalSensor
MetSensor
Sensor
CBRNESensor
LaserWarner
AttitudeSensor HeadingSensor
InertialSensor
Any sensor may
include its dedicated
local processing.
And/or processing may
be within an
InformationService
ExternalSensor
GeneralTransducer
Surv eillanceRadarGPS_Interface
Effector
class Lethal effector Specialisation
Mortar Gun
Lethal Effector
Cannon Missile
class NonLethal EffectorSpecialization
Non-Lethal Effector
LaserDesignator
ElectronicCountermeasure
LaserPointer
Loudspeaker
ObscurantLauncher FireExtinguisherSystem
Searchlight PaintMarker
Floodlight
Crew Interface
class Crew Interface Composition
CrewInterface
Headset DisplayScreen Keyboard
Pointer
notes
eg Touchscreen,
Thumbstick,
Bezel Key
Cursor
HandgripSwitch
DiscreteIndicator
VisualPresentationInterface
Normative Framework – Discuss
Host Vehicles
Vetronics Infrastructure
(Physical, Middleware,
Storage, Power)
Sensor SystemsEffector / Weapon
Systems
Display and Control Systems
Off-
board
Comms
Service
Applications
(eg BMS)
Management
Applications
On
board
Comms
BMS / C4I
Infrastructure
Vehicle Types
Operating
Environment
Army Fleet Size
& EvolutionMissions &
CONEMP
Automotive
Interfaces
Infrastructure
Constraints
Security
Constraints
Information
Exchange
Requirements
Comms Legacy
Constraints
Supportability
Concepts
Training
Constraints
Actors, Use
Cases
Open Radio
Interface
Definitions
New Technology Input
eg BMS Application SW
Vehicle Platform
Interface
Roadmap
Security Technology
Roadmap
OS-Middleware-
Hardware Roadmaps
Business Case - Background
Evolving operational threats.
Frequent variation in theatre of operation and mission requirements.
Shrinking procurement, fewer developments of new vehicles.
Procurement of generic base vehicle platforms without a full concept of use for the
mission systems they may ultimately carry.
Buyer aversion to the single source prime “vehicle provider is mission system
integrator” approach.
Increasing vetronics sophistication - Mission system integration skills needed
Buyer expectation of a COTS-like ‘plug-and-play’ continuous technology progression
with all associated benefits. (vs market volume)
Increasing software capability expected and possible … giving operational
improvements (with associated complexity and risk).
Government recognition of above, leading to accelerated initiatives in standardisation.
Business Case - Perspectives
“Tier 0” Government and Military
• User
• Procurement Agency
“Tier 1” Industry Prime Contractor and Mission System Integrator
• (inc C4I Network Technical Authority)
“Tier 2” Industrial Supply Base.
Business Case - Benefits
“Tier 0” Government and Military
• User
– Reduced Workload
– Improved task effectiveness
– Modular flexibility
– Training simplified
– Maintainability
• Procurement Agency (eg fleet 5000 vehicles)
– Specification simplification
– Initial Acquisition (~10% potential saving)
– Support
– Training
– Whole life – potential saving initial estimate ~25%
Business Case - Benefits
“Tier 1” Industry Prime and Mission System Integrator
• Initial Specification effort reduced
• Maintain architecture cost reduced
• Acquire Infrastructure and subsystems – from Tier 2 reductions
• Integrate, Test, Certify, Deliver – Risk reduction
• COTS infrastructure support base (eg test equipment)
“Tier 2” Supply Base
• Develop Infrastructure saving (roadmap, open standards)
• Manufacture of Infrastructure - scale
• Develop subsystem – software/hardware reuse, tool reuse
Outline Roadmap
2014 2015 2016 2017 2018 2019 2020 2021 2022 2023
Vehicle Upgrade Programme 1 (TBC)
Vehicle Replacement Programme 2
Vehicle Upgrade Programme 3 (TBC)
Vehicle Refit Programme 4
Other EU programmes ?????
TE
CH
NO
LO
GY
MA
RK
ET
PR
OD
UC
T
National Vehicle Primes
Competitive LAVOSAR Supply Base
2000x APC
2000x APC 1000+ APC?
2000x APC
100 x APC
LAVOSAR
Mission
System 1
LAVOSAR
Subsystems
Vendor X
LAVOSAR
Infrastructure Elements
LAVOSAR Standards Maintenance Board LAVOSAR Reference
Architecture
Definition v A
LAVOSAR Mission
System 2
LAVOSAR
TDPLAVOSAR
Subsystems
Vendor Y
LAVOSAR Mission
System n
LAVOSAR Reference
Architecture Definition
v 1.0
STANAG
LAVOSAR
Subsystems
Vendor Z
Standards
Business Case – Discussion
Work should continue to quantify
• Fleet sizes
• Acquisition model
• Capability introduction schedules
• Software cost model
Comments invited on assumptions:
• Funded EU body maintains LAVOSAR Reference Architecture
Definition..
• EU free-market procurement policy for LAVOSAR Subsystems.
• Vehicle Prime organisations continue, as design authorities, to
underwrite the installed performance. (not Tier 0 “plug and play”)
• Scope for Tier 1 Mission System Integrator v Vehicle Provider