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