Resultat från utveckling i LedsystT, designregler, …sesam.smart-lab.se/seminarier/Hostsem07/PeterT.pdfPlats för projektsymbol Bild 1 Resultat från utveckling i LedsystT, designregler,

Plats för

projektsymbol

Bild

1

Resultat från utveckling i LedsystT,designregler, design och arkitektur förnätverkslösningar.

SESAM 2007-11-08

Peter Thornström Design Partner LedsystT.

[email protected]

Plats för

projektsymbol

Bild

2

Vision

2010

2002 2005 2010

Phase 1 Phase 2 Phase 3

Architecture

Comm

Decision Support

Command Post

Data fusion

Sensors

Air &

Maritime

Ground

Vision

2010

2002 2005 2010

Phase 1 Phase 2 Phase 3

Architecture

Comm

Decision Support

Command Post

Data fusion

Sensors

Air &

Maritime

Ground

Staff & Unitelements

Experiment Experiment ExperimentExperiment

International Co-operation

Techniques

ProceduresOrganisation

M+

O+

P

T

Technical Design Proof of concept info-sec

International Co-operation

Applications Applications Applications Applications

T

RMAThe SAIC Study

DBA

EBO

LedsystT

Changing Society

FOA/Forma

IPT

CD&E

NB

D/N

CW

/NE

C

SOA

Service concept

COTS

OODA

TCP/IP

SitSyst

Design Rule

NCES

NERE FMLS2010

DEMO

MNE-5

NATO

EDA

IDC2

Zon-concept

RDF

CIMIC

Interoperability

Plats för

projektsymbol

Bild

3

0û

10ûW

20ûW

10ûE 20ûE30ûE

40ûE

40ûN

30ûN

50ûN

60ûN

40ûN

30ûN

50ûN

60ûN

50ûE

Batna

Oran

Ouargla

Timimoun

Graz

Gomel

Port Said

El-Minya

Suez

Rovaniemi

Vaasa

PotiSochi

IraklionKhania

Larisa

Ikateq

Pecs

Catania

BanghaziMisratah

Klaipeda

Marrakech

Alta

Kirkenes

Mo

Trondheim

Olsztyn

Coimbra

Arad Braila

Arkhangelsk

Kaluga

Kirov

Murmansk

Novgorod

Orel

Pskov

Smolensk

Syktyvkar

Vorkuta

Voronezh

Malaga

Zaragoza

Gavle

Kiruna

Lulea

Ostersund

Skelleftea

Umea

Gafsa

Medenine

Sfax

Antalya

Lutsk

Simferopol

Inverness

Lerwick

Plymouth

Rijeka

Vologda

Annaba

Constantine

Vejle

Beni Suef

Parnu

Ioannina

Patrai

Gyor

Siglufjordhur

Liepaja

Tangier

Bergen

Hammerfest

Harstad

Severodvinsk

La Coruna

Burgas

Varna

Brno

Torshavn

Bordeaux Lyon

Marseille

Nantes

BonnFrankfurt

Hamburg

Leipzig

Nurnberg

Agrinion

Thessaloniki

Cork

Limerick

FirenzeGenova

Rotterdam

Krakow

Lodz

Poznan

Cluj

Timisoara

Gorkiy

Izhevsk

Kazan

Krasnodar

St. Petersburg

Perm

Saratov

Volgograd

Yaroslavl

Barcelona

CordobaValencia

Valladolid

Goteborg

Geneva

Zurich

Aleppo

Adana

Bursa

Istanbul

Izmir

Donetsk

Frunze

Kharkov

Lvov

Odessa

Voronezh

Edinburgh

LeedsManchester

Sunderland

Alexandria

Bayonne

Strasbourg

Milano

Naples

Palermo

Casablanca

Gdansk

Porto

Rostov

Tol Yatti

Krivoy Rog

Belfast

Birmingham

Glasgow

Liverpool

Tirane

Minsk

SarajevoSofia

Zagreb

Prague

Copenhagen

Helsinki

Paris

Gibraltar Athens

Budapest

Reykjavik

Rome

Amman

Riga

Tripoli

Vaduz

Vilnius

Skopje

Vallelta

Chisinau

Monaco

Amsterdam

Oslo

Warsaw

Bucharest

Moscow

Bratislava

Madrid

Stockholm

Bern

Tunis

Ankara

Kiev

Algers

Vienna

Brussels

Nicosia

Cairo

Tallinn

Berlin

Dublin

Tel Aviv

Beirut

Luxembourg

Rabat

The Hague

Lisbon

Ljubljana

London

Damascus

Belgrade

RUSSIA

FINLAND

AUSTRIA

ITALY

SPAIN

SWEDENNORWAY

GERMANY

FRANCE

PORTUGAL

HUNGARY

ROMANIA

BULGARIA

TURKEY

DENMARK

POLAND BELARUS

UKRAINECZECH

SLOVAKIA

GREECE

CYPRUS

ANDORRA

NETH.

BELGIUM

IRELAND

YUGOSLAVIA

ALBANIA

MOLDOVA

LITHUANIA

LATVIA

ESTONIA

LUX.

BOSNIACROATIA

SLOVENIASWITZERLAND

MACEDONIA

ICELAND

EGYPT

ALGERIA

TUNISIA

LIBYA

MOROCCO

JORDAN

IRAQ

SAUDI ARABIA

ISRAEL

LEBANON

GEORGIA

SYRIA

U. K.

Corsica

Crete

Faroe Islands

Hebrides

Jan MayenKolgujev

LesbosMajorca

Orkney Islands

Peloponnesus

Rhodes

Sardinia

Shetland Islands

Sicily

Dead Sea

Kuybyshev Res.

L. LadogaRybinsk Res.

Danube

Dan

ub

e

Danube

Dnestr

Dnieper

Dnieper

Don

Don

Elbe

Euphrates R.

Garonne

Kama

Loire

Nile

Ob

Po

Rhine

Rho

ne

Rio Douro

Seine

Tagus River

Volga

Volga

VolgaVolga

Adriatic Sea

Aegean Sea

Baltic Sea

Barents Sea

Bay of

Biscay

Black Sea

Greenland Sea

Gulf of Bothnia

Gulf of Finland

Ionian Sea

Mediterranean Sea

Mediterranean Sea

North Sea

Norwegian Sea

Red Sea

Tyrrhenian Sea

White Sea

Denmark Strait

English Channel

Sea of Azov

Strait of Gibraltar

ATLANTIC OCEAN

500KM0

500 Miles0

Parallel scale at 45ûN15ûE

Consider the fact that…

… when the ”NBD journey”

really started in year 1998, the

Area of Interest was Sweden

with surroundings (Baltic Sea

Region)

Plats för

projektsymbol

Bild

4

RUSSIA

RUSSIA

FINLAND

AUSTRIA

ITALY

SPAIN

SWEDEN

NORWAY

GERMANY

FRANCE

PORTUGAL

HUNGARY

ROMANIA

BULGARIA

TURKEY

DENMARK

POLAND

BELARUS

UKRAINECZECHSLOVAKIA

GREECE

CYPRUS

ANDORRA

NETH.

BELGIUM

IRELAND

YUGOSLAVIA

ALBANIA

MOLDOVA

LITHUANIA

LATVIA

ESTONIA

LUX.

BOSNIA

CROATIASLOVENIA

SWITZERLAND

MACEDONIA

GREENLAND

ICELAND

U. S. A.

CANADA

BRAZIL

KENYA

ETHIOPIA

ERITREA

SUDAN

EGYPT

NIGER

MAURITANIA

MALI

NIGERIA

SOMALIA

NAMIBIA

LIBYA

CHAD

SOUTH AFRICA

TANZANIA

CONGO

ANGOLA

ALGERIA

MADAGASCARMOZAMBIQUE

BOTSWANA

ZAMBIA

GABON

CENTRAL AFRICAN REPUBLIC

TUNISIAMOROCCO

UGANDA

SWAZILANDLESOTHO

MALAWI

BURUNDI

RWANDA

TOGO

BENIN

GHANA

IVORY COASTLIBERIA

SIERRA LEONE

GUINEA

BURKINA

GAMBIA

CAMEROON

SAO TOME & PRINCIPE

ZIMBABWE

CONGO

EQUATORIAL GUINEA

WESTERN SAHARA

DJIBOUTI

SENEGAL

GUINEA BISSAU

Canary Islands

JORDAN

ISRAEL

LEBANON

ARMENIAAZERBAIJAN

GEORGIA

KYRGYZSTAN

TAJIKISTAN

KUWAIT

QATARU. A. E.

OMAN

YEMEN

SYRIA

IRAQ IRAN

OMAN

SAUDI ARABIA

AFGHANISTAN

PAKISTAN

INDIA

CHINAKAZAKHSTAN

TURKMENISTAN

UZBEKISTANMYANMAR

NEPAL

BHUTAN

SRI LANKA

BANGLADESH

MONGOLIA

U. K.

MALDIVES

ATLANTIC

INDIAN

OCEAN

OCEAN

OCEAN

ARCTIC

Nile

Niger

Gan

ges

Volga

Ob'

Yenisey

Lena

Yangtze

Yukon

MacKenzie

Zambezi

Rhine

Danube

Dnieper

Euphrates

Irtysh

Aldan

Lena

Amur

Huang

Indu

s

Congo

Great Lakes

GreatSlave L.

GreatBear L.

L. Winnipeg

L. Victoria

L. Chad

L. Malawi

L. Balkhash

L. Baykal

ChukchiSea

Beaufort Sea

Hudson BayBaffinBay

NorwegianSea

GreenlandSea

NorthSea

Mediterranean Sea

BalticSea

Black Sea

Aral Sea

Arabian Sea

Bayof

Bengal

Sea ofOkhotsk

Barents Sea

KaraSea

LeptevSea

Caspian Sea

Red Sea

Today…

Plats för

projektsymbol

Bild

5

Plats för

projektsymbol

Bild

6LedsystTFas 0, 0+& 1

LedsystTFas 3 andimplemen-tation

SäkraInformation,delaktighetoch planerautveckling.

Initial definition avförutsättningaroch prod avdesignregler.

Anpassningav förut-sättningar.Design ochdesignregler.

Design ochdesignreglerför säkerhets-lösningen.

Design ochdesignreglerför interoper-ability ochlegacy.

DesignochDR.Inf &komm

Avtal ochStatement of Work

Nytt ram-scenario. BISInternationell samverkan

Förutsättningarinteroperabilitet

Roadmap 1.Verksamhets-utveckling.Skill-Groups.DemoDesign.

Demo Design Demo Design Demo Design POC, S-POC POC, T-POC

Roadmap 2.Scenario NBFKrav. Arkit-ektur. Säkl. Metodansats.DemoDesign.

Roadmap 3.Omvärderingav krav.Arkit-ektur. Säkl. Metodansats.DemoDesign.

Roadmap 4.Arkitektur.Säklösning.Design &designregler. Poc/T-Poc.

Dec 06 >Feb 04 > Nov 04 >Maj 04 > Juni 05 > Juni 06 ? >Nov 03 >

Ett större antal anpassningartill nya (justerade) ramvillkor.

LedsystTTechnicalEnd State.DefinitionBasplatta 2.

Lev-eransoch rapport

Overall process (evolutionary development)

Plats för

projektsymbol

Bild

7

S-O 2 > N

Contract- Delivery of

design rules

Statement ofWork- Process

- Co-oper

- EVM

S-O 1Initial activities

Fixed org

financing

Contract date 1/3-04

Base order, fixed optimised project org financing

1/12-04

> Final delivery

Main task

2006-12-31 Additional task

2007-05-31

> Close Down

(2007-06-15)

2007-12-31

/ /

24/10-0324/10-03

24/10-0324/10-03

17/11-0317/11-03

The “Contract” has been” stable since project start

The “Statement of Work” has been” stable since project start

We will have 23 Sub-orders and 4 + Base-orders since project start.

We have 300 identified deliverables and 2000 document (roughly)

24/10-0324/10-03

Contract Model (evolutionary development)

Plats för

projektsymbol

Bild

8

Design Partner LedsystT

Design Rule Project

Saab Ericsson NBD Innovation AB

Contract ”Design of C4ISR Functions”

FMV (Swedish Defence Materiel Administration)

Program management

(Executive and Technical management)Management

group

Project management

Board

of directors President and Vice PresidentS

yste

m E

ng

Team

Production Teams

Part

icip

ant

Board

(R

esourc

es)

Ris

k M

anagem

ent and C

CB

(D

eliv

era

bels

)

Advis

ory

Board

(H

KV

, F

MV

, S

aab, E

ricsson, IB

M, B

oein

g)

Plats för

projektsymbol

Bild

9

• A design rule is a solution to a problem in a specific contextwith the following characteristics:

What is a Formal Design Rule?Definition

Belongs to a

problem domain

Packages knowledge

in a reusable form

Standardize solutions

to design problems

within NBD

Gives value to

the re-user

Plats för

projektsymbol

Bild

10

What is a Formal Design Rule?Design Rule Model

Problem

domain

THE design rule

Referred DR is

mandatory or

recommended

Problem

1..n

Context

1

Solution

1..n 1

0..n

Meta data

1

1

DR product

Version

Date

Status

Identifier

Development Status:[Identified, Draft, Proposal,

Verified, Rejected, Obsolete]

DR Association

Validity = Descriptive

Validity for each referenced DR:

[Normative, Descriptive, Emerging]

0..n

1

0..n+Refers

Analysis DR

1

1

Consequence

0..n

DRP Product

VDD

Domain

DR and DRP references

Status

Identifier

0..n

1+Owner1

0..1

0..n

Each association between DR:s configured in different DRP:s

must also have a corresponding

dependency between the

involved DRP:s.

Requirements

0..n

1

0..n

1

Verification

Method

Result

Plats för

projektsymbol

Bild

11

Technical Design RulesDelivered ”High Level Design Rules”

Focus Areas

Flexibility Mobility Scalability Interoperability Security

Flexibility

Mobility

Scalability

Interoperability

Legacy Integration

Risk Management

Sec. Asp. of Inform.

Sec. Asp. of Flex.

Systems Management

Plats för

projektsymbol

Bild

12

M, A, D, DRFour different types of design rules

• Development methods that supports the life cycle perspective

• Defined structures that supports descriptions of complex relations

• Detailed descriptions of suggested technical solutions

• Long lived and reusable solutions on generic problems

• Prototypes on central NBD functions

Plats för

projektsymbol

Bild

13

Design Governing DocumentsSwAF Goals

High LevelRequirements

SystemRequirements

ComponentRequirements

Require-ments Design

Specifications

130 documents & test environment

Descriptions

9

ReportsReferenceMaterial55

Plats för

projektsymbol

Bild

14

The Overarching Architecture for FMLS 2010Technical System is the highest level of architectureaddressed.

The framework gives

guidelines on how to

elaborate architecture

descriptions

Architecture

FrameworkDesign

Rules

The Overarching

Architecture

describes concepts,

principles and an

overall description of

the entire FMLS

2010 system.

Overarching

ArchitectureReference

Architectures

Reference Architectures,

describe general rules

and patterns for

developers and

architects to use when

creating deployable

instances of a system. Design Rules describe

detailed rules to follow

when designing a system,

according to the

architecture

Target

Architectures

The Target Architectures,

describes rules and

patterns for developers to

use when creating a

specific system instance

Plats för

projektsymbol

Bild

15

COTS (RUPSE)

M1

M2

M3

M4

•Styrning och ledning

•Beslutsprocess

•Konfigurationsledning

•Projektkonfigurering

The Method Package

M5,

M6

FM

LS

2010

*) commercial off-the-shelf

Behov

Lösning

Utveckling

M1=Verksamhets- och kravanalys

M2 = Design och designregler

M3 = Information hantering

M4 = Integration, Verifiering och

Validering

M5 = Verktyg

M6 = MSI

utveckla

Plats för

projektsymbol

Bild

16

Design Rules, Governing Design, Architecture andMethods.

Focus Areas

Flexibility Mobility Scalability Interoperability Security

Flexibility

Mobility

Scalability

Interoperability

Legacy Integration

Risk Management

Sec. Asp. of Inform.

Sec. Asp. of Flex.

Systems Management

A ”technical base” that makes it

possible to start specification work

for development of NBD.

Sveden: In interaction with method

development results (LedsystM) and

demonstration experinces.

International: At least 80% of al pre-

study objectives has been adressed.

Interoperability with legacy system is

structured.

Plats för

projektsymbol

Bild

17

A new generationLevel of complexity

BeforeOne configurationOne level of powerEasy understandablePower??Comfort??Short service intervalsA new chassie for every model

AfterReconfigurable in runtimeSeveral levels of powerMaybe not that understandablePower!!!Comfort!Long service intervalsOne chassie many models

Plats för

projektsymbol

Bild

18

Components and it´s relations

Plats för

projektsymbol

Bild

19

Storing structures

Assembly lines

and methods

Plats för

projektsymbol

Bild

20

Standards

Plats för

projektsymbol

Bild

21

Focus on the chassie

Plats för

projektsymbol

Bild

22

Three different ”road” conditions

Plats för

projektsymbol

Bild

23

LedsystT Design principles

• All IP vision – IP convergence layer

• Service Orientation

– NCES – Standardised service types and interfaces

– NERE – Lookup, authorization and com. support

– Encapsulation

• Common system management model

• Common security model

• Policy control

• Interoperability and legacy integration bridges

• Autonomous mode operation

• Open standards and modularity

• Use of standardized interfaces between and within system

Plats för

projektsymbol

Bild

24

Technology changes,

New major requirements

System

Assembly

Service

Assembly

Operate/Maintain

Capability

Operational

changes

Add/Update

System/Module/

Services

New missions,

New organizations

Updated

capabilities

needed

Change Architecture

System

Assembly

Service

Assembly

Operate/Maintain

Capability

Operational

changesUpdated

capabilities

needed

Time Minutes/SecondsYears/Months

Developmental Flexibility Operational Flexibility

LedsystT Main driver- Flexibility

Changes

RequiredSystemChange orAction

Plats för

projektsymbol

Bild

25

LedsystT Technical Security solution

• Must support in flexibility in network and service orientation• Must meet security requirements

– KSF

– Security targets

• Major information technology parts

– Multi-layered security

– High assurance information zones

– End to end authentication and encryption

– Logically centralized distributed authorization

– Separation between users and sensitive data and sensitivefunctionality

– Use of SwAF security mechanisms (TAK, Kryappar, Färist …).

Plats för

projektsymbol

Bild

26

Security Concept

Transport (trafikskydd)

Network (IPSEC)

TLS (sessionbased)

Ap

pli

cati

on

Message-

orientented sec

4 -Transport

3 -Network

2 -Data link

1 -Physical

securi

ty

7 – Applicationincl:

- Presentation

- Session

Acc

ess-

con

trol

Risk Management Security in depth Accreditation

Plats för

projektsymbol

Bild

27

Command post example security

VPN-1

VPN-3

Internet

VPN-4

Information

stair

Information

stair

VPN-2

Informationscell-1

Informationscell-2

Informationscell-4

Informationscell-3

Informationscell-5

Plats för

projektsymbol

Bild

28

System of system management: SituationAdapted System Configurations

FMIP

FMLS Systems

System configuration for

RDF

System configuration

for

CIMIC

System configuration

for

?

Systems of

external

partners

Plats för

projektsymbol

Bild

29

H d d kt Stöd d ktH d d kt Stöd d kt

Generic design _ Applied Design_ Prototype

FMLS 2010

Underlag

MethodsArchitectural

FrameworkTDRDesign

Systems

ManagementApplications

Application

SupportSecurity Infrastructure

Resource

Management

Security

Management

Resource

Provisioning

Management

Resource

Trouble

Management

Resource

Performance

Management

Data

Collection &

Processing

Change

Management

Service Level

Management

Release

Management

Availability

Management

Service

Continuity

Management

Audit

Management

Alert

Management

Response

Management

Decision

Support

Policy

Management

Common

Operating

Picture Syst.

Sensor

Management

Order

Management

Remote

Command

and Control

Geographic

InformationServices Communic.

IT

Infrastructure

Information

Zones

Comm.

Security

Key

ManagementPlatform Services

Authentic. in

WSData Diode

VPN

Multi-zone

platform

Walls

Link level

Intrusion

Protection

Certificate

Common

Keys

Protocol

Analysis

Key

Distribution

Session

Based

Security

SSO Single

Sign-On

Authorization

Management

Security in

ESB

Information

Management

Service

Metadata

Basic

Services

Web

Services

Application

QoS

Middleware

User

Services

Radio

Link Layer

Network

Layer

Routing

Mobility IP

QoS IP

GPRS/3G

typDRP

FMLS 2010

generic design

Combat vehicleSoldierRecipient

Urban areaOrder/requestStreaming

video/response

OPIL/TK

BG HQ

6000 km

200 km200 km

50 km

50 km

5 km

0 km/hr (fixed network)

0 km/hr (transportable/fixed network)

Units70 km/hr

(mobile node)

units70 km/hr

(mobile node)

Year: 2010

Sverige

x

MCP

MCP

Soldiers5 km/hr

FHQxxx

0 km/hr (transportable/fixed network)

xxx

Computer Computer ComputerServer

Bridge

PDA

Computer Computer Computer

PDA PDA

Server

Bridge

Plats för

projektsymbol

Bild

30

LT

XO

EY

Y-N

NN

N -

Utg

. 1

.02

00

6-1

1-0

8F

örf

att

are

Focus has been on the Enabling System and

design of a System Proof of Concept

FMLS 2010 deployed system

Technical SystemOperational system

FMLS enabling system – continuously evolving

Methods: How to design using Design Rules and an architectural framework.

Description frameworks

High-level technical design rules in the areas flexibility, security and interoperability

Technical infrastructurethat should provide the means

for the collaboration of systemsin all communication domains

while fulfilling the security

requirements and taking cost

effectiveness into account.

Systems managementFlexibility, security and costeffectiveness

Coverage of focus areasCoverage of focus areas

Description

Frameworks

FMLS Enabling System

C2 Intelligence LogisticsCollaboration

toolsInformation

Administrativetools

FMLS 2010 Technical System

Network Centric Enabling Services (NCES)

Communication Infrastructure

Training&

Simulation

Systemsmgmt

Securitymgmt

LegacyWeapon system

Methods Technical

Design Rules

Plats för

projektsymbol

Bild

32

The SysPoC design is one of many activities in the

LedsystT project

2004 2005 2006

Demo Design DSG2

Targeted DesignSecurity

Infrastructure and telecom

System management

Utilization ofCOTS

Research

FMLS 2010 Overall Design

Experiments TPOC TPOC

Sys POC

Sec POC

Plats för

projektsymbol

Bild

33

On the web

www.fmv.se

Plats för

projektsymbol

Bild

34

Released documents

•Overarching documents•Methods

– Design Method

– Information Management Method

– Integration, Verification and ValidationMethods

•Framework– System Framework

– Services Framework

– Information Management Framework

– Technical Design Rules Framework

•Technical Design Rules– Security Technical Design Rules

– Applications Technical Design Rules

– System Configuration Technical Design Rules

•Generic Design– System Management Design

– Security Design

– Business Applications Design

– Application Support Design

– Infrastructure Design

•Applied Design

– Configured System

– Rapid Deployment Force OperationalScenario

– Civil Military Collaboration OperationalScenario


– Design Method











– Security Design




•Applied Design




16 October 2006 4 May 2007

Plats för

projektsymbol

Bild

35

Released documents


– Design Method











– Security Design




•Applied Design





– Design Method











– Security Design




•Applied Design




16 October 2006 4 May 2007

Plats för

projektsymbol

Bild

36

Main content in each area


– Design Method











– Security Design




•Applied Design




•Systems Engineering Vision•Technical End State 2006•Achievements towards the vision

•Operational Scenarios•Overarching Architecture (OA) forFMLS 2010 Technical System

•Requirements– High level

– System requirements

– Security requirements

– Component requirements

4 May 2007

= Newly released material

= Updated material

Plats för

projektsymbol

Bild

37



– Design Method











– Security Design




•Applied Design




•Methodology for FMLS MethodDevelopment•Method for Approval of Design Rules

•Design Method– In Swedish

• Information Management Method– In Swedish

• Integration, Verification and ValidationMethods

– Mainly in Swedish


= Updated material

Plats för

projektsymbol

Bild

38



– Design Method











– Security Design




•Applied Design




•SOA for NBD: Principles andConsiderations

•Architecture Description Framework•Architecture Templates

– Reference Architecture Template

– Target Architecture Template

• Integrated Dictionary for FMLS 2010Technical Systems


= Updated material

Plats för

projektsymbol

Bild

39



– Design Method











– Security Design




•Applied Design




•Framework for System Description•Design Target Architecture Template

•Framework for Service Description•Definition of Service Template

• Information Management Framework– Information Exchange Models

– Common Information ExchangeStandards

– Information Models

– Information objects

– Metadata

– Information exchangerequirements

•Framework for Design Rules•Design Rule Package Template•Design Rule Template


= Updated material

Plats för

projektsymbol

Bild

40



– Design Method











– Security Design




•Applied Design




•Security Design Rules– Security Aspects on Flexibility

– Security Aspects on Information

– Risk Management

– System Management

•Application Design Rules– Data Incest Prevention

•System Configuration Design Rules– Flexibility

– Mobility

• Reports on HIP, Mobile IPv4/v6, DNS etc.

– Scalability

– Interoperability

– Legacy Integration


= Updated material

Plats för

projektsymbol

Bild

41



– Design Method











– Security Design




•Applied Design




•Design Overview

•Reference Architecture NetworkCapabilities Enabling Services (RANCES)•NCES Standard protocols, formats andAPIs

•Target Architecture System Proof-of-concept (TA SysPoC)


= Updated material

Plats för

projektsymbol

Bild

42



– Design Method











– Security Design




•Applied Design




•Management Architecture Overview•Technical Management Architecture

•Design Target Architectures (DTA)– SysPOC Systems Management

System

– SitSyst Builder

– Distributed Policy ConfigurationProvider

– DTAs for Managed Systems andNetworks

•Service Definitions (SD)– Policy, Log, SW and Data

Distribution, Action, Monitoring,Configuration

– Simulation Ground TruthPlatforms, Simulation Mgmt

•Management Information Data models


= Updated material

Plats för

projektsymbol

Bild

43



– Design Method











– Security Design




•Applied Design




•Security Architecture Overview•Next Generation Security Architecture

– Overview, Secure Networking,Security Management, SecureComputing

•Operational Assurance concepts

•Authority Management– Use cases for Authorization Mgmt

• Information Zones– DTA and SD for Information stair

and data diode

•Key Management– TA for Key server architecture

and protocol

•Platform security– Design Report Platform Security

•Services security– DTAs for Session Security Profile,

Security Libraries, JMS


= Updated material

Plats för

projektsymbol

Bild

44



– Design Method











– Security Design




•Applied Design




•Common Operation Picture System– COPS Overview

– COPS Information model

– COPS Internal Requirements

– DTA COPS

– SDs for Access COP Information,Provide Streaming Data, SupportCOPS, Process Intelligence,Provide Report

•Mission Management– DTA Mission Handling

– Definition of Service MissionHandling

•Remote Command and Control– TA Distributed Staff Support

Portal (DSSP)

– SD Portal Framework

– SD Presence Indication


= Updated material

Plats för

projektsymbol

Bild

45



– Design Method











– Security Design




•Applied Design




• Infrastructure Overview•Design Target Architecture NERE

•DTAs and SDs for:– User, System, Service and

Organization Registries (lookupand admin)

– AccessControl, Revocationinformation, Authorization

– Network Time synchronization,TimeStamp, DNS, SIP endpointsand servers

– Communication broker, NERESubscription

– Enterprise Service Bus, SW &Data distribution

•NERE metadata specifications•Design description of Data Distribution•Technical and software systemdeployment approval process


= Updated material

Plats för

projektsymbol

Bild

46



– Design Method











– Security Design




•Applied Design




•Communication InfrastructureOverview

•Report on FMLS transmission systems•Report about voice communication inbattle group scenarios•Utilization of Civilian TelecomTechnologies

•DTA Communication Infrastructure•Definition of protocol-set forConvergence Plane

•Report on SIP based collaborationinfrastructure•Design Target ArchitectureCollaboration


= Updated material

Plats för

projektsymbol

Bild

47



– Design Method











– Security Design




•Applied Design




•Design Target Architectures– CETRIS, Strics, UndE23, UAV,

IT-Soldier

•Rapid Force Deployment (RDF)Scenario•Target Architecture Rapid DeploymentForce (RDF)•Operational Examples

– Autonomy and reconnection,System reconfiguration,Interoperability RDF, Insider,Outsider, COP etc

•Civil and Military Co-operationScenario•Target Architecture Civil and MilitaryCo-operation•Operational Examples

– Interoperability CIMIC


= Updated material

Plats för

projektsymbol

Bild

48

Planer avs fortsatt stöd till FMV:LedsystT

Sett från Designpartnerns pespektiv

Plats för

projektsymbol

Bild

49

Verksamhet 2007

Avtalets giltlighetstidförlängd.

DesignpartnerLedsystT

Fas 2/3SO22SO23

SO19SO20SO21

4

SAAB ERICSSON NBD INNOVATION

Peter Thornström

Designpartnern

Statusanalys Historik

LedsystTFas 0, 0+& 1

LedsystTFas 3 ?


Initial definition avförutsättningaroch prodavdesignregler.









Demo Design Demo Design Demo Design POC, S -POC POC, T-POC





Ett större antal anpassningar till nya (justerade) ramvillkor.

LedsystTTechnicalEnd State.DefinitionBasplatta2.


Säkrakontinuitet

3

15/6-2007 2008 >>1/4-200831/12-2007

Kompletterande och stödjande

verksamhet utgående från

genomförd leverans.

Avtalets giltlighetstid

förlängt till 2007-12-31

Plats för

projektsymbol

Bild

50

Verksamhet 2008.

Avtalets giltlighetstidförlängd.

DesignpartnerLedsystT

Fas 2/3SO22SO23

SO19SO20SO21

4

SAAB ERICSSON NBD INNOVATION

Peter Thornström

Designpartnern

Statusanalys Historik

LedsystTFas 0, 0+& 1

LedsystTFas 3 ?


Initial definition avförutsättningaroch prodavdesignregler.









Demo Design Demo Design Demo Design POC, S -POC POC, T-POC





Ett större antal anpassningar till nya (justerade) ramvillkor.

LedsystTTechnicalEnd State.DefinitionBasplatta2.


Säkrakontinuitet

3

15/6-2007 2008 >>1/4-2008

UtvecklingspartnerLedsystTFas 3

31/12-2007

En upphandling av

Utvecklingspartner

pågår.

Starttidpunkt osäker.

Sannolikt förlängs avtalet

med Designpartnern till

Utvecklingspartner utsetts.

Plats för

projektsymbol

Bild

51RevolutionRevolution

EvolutionEvolutionEvolution

Previous vision

Platform-centric,service embedded,

large conflict,well established C2

New vision

Network-centric,interoperable,

joint, integrated,flexible

Existing structureExisting structure Future structureFuture structureFuture structure

IT´S ABOUT TRANSFORMATION