LAVOSAR Functional & Technical Architecture · LAVOSAR – Functional & Technical Architecture ......

© Rheinmetall Defence 2013

LAVOSAR – Functional & Technical Architecture LAVOSAR Industry Workshop (Brussels, 25th June 2013)

Dr. Oliver Prenzel Rheinmetall Defence Electronics ( phone: +49 421 457-4507 fax: +49 421 457- 1759 * e-mail: [email protected]

1

LAVOSAR – Functional & Technical Architecture (First Results)

© Rheinmetall Defence 2013 Dr. Oliver Prenzel, VEAT

Overview

• Basic Considerations for Architecture Development

• Identification of Suitable Architectural Structures

• Development of Architectural Views

2

Identify Suitable Architectural StructuresIdentify Suitable Architectural Structures

Modular Decomposition

Areas of Innovation and Competition

Stable or Slowly Evolving Aspects

Scalability and Extendability

Decouple Different Innovation Speeds

Safety and Security

Develop Architectural ViewsDevelop Architectural Views

Functional View

Network and Computer View

Operating System and Middleware View

Computer Program View


© Rheinmetall Defence 2013 Dr. Oliver Prenzel, VEAT 3

Considerations for Development of LAVOSAR Architecture

Not only Interface Standardization & Design Constraints

but: Comprehensive Open Reference Architecture

Electronic & Information Technological 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, Certification & Accreditation

Verification & Validation

Roadmap, Transition for Existing System



Open Architecture: Technical Principles

4

[E.M. Nelson, “Open Architecture – Principles and Guidelines“, IBM, 2008]



@ RTI, Realtime Innovations

Levels of Conceptual Interoperability



Modularization

Motivation

Decoupling (Space, Time, Flow, Platform, Multiplicity)

Separation of Interface & Implementation

Reuse

Evolutionary Enhancements

“SOLID” Principle [R.C. Martin, 2002]

Single Responsibility (Separation of Concerns)

Open/Closed Modules

Liskov’s Substitution Principle

Interface Segregation

Dependency Inversion

6



Architectural Structures - Decoupling different Innovation Speeds

7

Innovation Cycles, e.g.

0.5 – 1 year

2-3 years

5-10 years

Mechanical

StructuresMechanical

Interfaces

Electronic

Structures Plugs

IT

Structures

Cabling

Services

Plug-ins

Networking

Infrastructure

Middleware

…

OS,

Hypervisors, ...

cPCI, VPX,

...

…



Development of Architectural Views

8



Architectural Views - Functional View: Overview

9

Monitoring Services

Mission System Services

Effector

Services

Sensor

Services

Common Crew

Station

UI_SvcPlugins

Plugin Manager

UI_SvcPluginsUser Interface

Service Plugins

Common

ServicesVehicle

Services

Resource

Management

Gateway

Services

Safety

MonitoringSecurity

Monitoring



Architectural Views - Service View

Monitoring Services

Mission System Services

Effector ServicesSensor Services

Common Services

Time Sync

Recording &

Replay

Map &

Navigation

Object

Detection

Acoustic Sniper

Detection

Object Tracking

Target

Classification

Video Display

Augmented

Reality

Obscuring

System

Change

Detection

Laser WarningBlue Force

Tracking

RadarCBRNE

Sensing

Electronic Support

Measures

Remote Controlled

Weapon Station

Laser Effector

Acoustic

Effector

Electronic Counter

Measures

Target

Designator

Message &

Chat

Vehicle Services

HUMS

Battle

Management

Logistics &

Maintenance

Simulation &

Training

Resource

Management

Safety

Monitoring

Security

Monitoring

Gateway Services

Authentification

Encryption

Secure Links

Cross Domain

Links

Mediation &

Transformation



Achitectural Views - Layer Overview

Mechanics Layer

(Common Mechanical Adaptation Schemes)

Electronics Layer

(Plugs, Cabling, Power Mgmt, Electronics/Networking Infrastructure)

IT Layer

(Information & Communication)



Achitectural Views - Detailed Layer View

Middleware

(Data Distribution Service)

Service Layer

(Decentralized/Publish-Subcribe Services,

Definition & Orchestration)

Common Data Model

(PIM >> PSMs)

(QoS)

Physical

(Ethernet, IP)

Application Layer

(Service Subscription Plugins)

Mechanics Layer

(Common Mechanical Adaptation Schemes)

Electronics Layer

(Plugs, Cabling, Power Mgmt, Electronics/Networking Infrastructure)



Development of Architectural Views

- Further Examples and First Ideas -

13



Architectural View Example - Logical Data Model View

Common Data Model

Mission SystemsVehicle Subsystems

Crew Station

Engine

Fuel

Brake

Transmission

HUMS

Navigation

Vehicle Platform

Power

Sensors

Acoustics

ESM

LRF

Met

Tracker

CBNRE

RadarEO/IR

C4I

Effectors

Acoustic Effector

ECM

LTD

Machine Gun

Laser Effector

Missile

RCWS

General Components

PT Platform

Video Processing

Laser Warner

IFF

Obscuring

PlugIn Registration

HMI Config

Fragment Control

Input Device Command



Architectural View Example - Mission System Elements View

15

Roles„Driver“ „Gunner“ „Commander“ „Info Officer“ „Squad Leader“

Vehicle Control Weapons C4I Communication Command Posts

Internal Vehicle Communication

Com

munic

ations /

Radio

s

Sensors Effectors / Weapons

Gate

way to E

xte

rn

Other InformationProcessing



Architectural View Example - Communication Domain View

16



Thank you for your attention

Questions?

Discussion!

17

LAVOSAR Functional & Technical Architecture · LAVOSAR – Functional & Technical Architecture ......

Documents

Transcript of LAVOSAR Functional & Technical Architecture · LAVOSAR – Functional & Technical Architecture ......