1. Alternativ 1 – Core services

2. LedsystT Focus Areas and Structure
FMLS 2010 Technical System
Application domain
Systems & Security Management
Legacy &
Weapon systems
Training &
Simulation
Network Centric Enabling Services (NCES)
Communication Infrastructure
This slide shows the first level of breakdown structure for the Technical System and Enabling system, which are the main scope for this End-state presentation
The Enabling system is illustrated with an increasing scope over time, while the technical system is of more constant scope (but of course the content will constantly be developed)
Description
Frameworks
Methods
Technical Design Rules
FMLS Enabling System

3. Focus Area Description NCES
Frameworks
FMLS enabling system C2
Intelligence
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Interfaces
Network Enabling Runtime Environment (NERE)
This slide is just an introduction to the NCES description and it shows that NCES is divided in two parts:
Interfaces towards technical systems that supports the operations
Runtime Environment (NERE) which is the central mechanisms executing in the FMLS2010 systems of systems in order to achieve NBD.

4. Focus Area Description NCES
Frameworks
FMLS enabling system C2
Intelligence
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Interfaces
Network Enabling Runtime Environment (NERE)
Application domain
Mgmnt
Legacy & Weapon
Train/Sim
Alternativ till bild 2 och 3
This slide is just an introduction to the NCES description and it shows that NCES is divided in two parts:
Interfaces towards technical systems that supports the operations
Runtime Environment (NERE) which is the central mechanisms executing in the FMLS2010 systems of systems in order to achieve NBD.

5. Focus Area Description NCES
Frameworks
FMLS enabling system C2
Intelligencel
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Interfaces
NERE
The Network Centric Enabling Services will:
Enable FMLS 2010 to be a system of independent cooperating systems.
Be based on a service oriented architecture with loosely coupled systems.
Use open industrial standards
Be as lean as possible
This slide shows the general functions and characteristics for NCES

6. Focus Area Description NCES Interfaces
Frameworks
FMLS enabling system C2
Intelligencel
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Focus Area Description NCES Interfaces
Interfaces
NERE
NCES Interfaces to Technical systems and the areas they support in the Operational Systems
Technical interfaces to
Information C2
Intelligence
Logistics
Collaboration tools
Administrative tools
System Management
Security Management
Legacy systems
Weapon systems
Training&Simulation systems
Communication infrastructure
Supporting Operational areas
(To be synchronized with LedsystM)
Command Control
Collaboration
Situational awareness
Interoperability
Service Management
Training & Simulation management
System Management
Information Management
This slide shows the correlation between the technical interfaces of NCES (they corresponds to the technical focus areas) and the operational areas they are to support. The operational areas is the highest level of operational structure as seen from a LedsystM perspective.

7. Focus Area Description NERE
Frameworks
FMLS enabling system C2
Intelligencel
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Focus Area Description NERE
Interfaces
NERE
NERE Characteristics
Included services in NERE
Looking up services and systems
The registry information is NATO standards extended for SwAF. Web Service (WS) interface
Looking up individual users
E.g. SIP DNS names to establish voice, video or message communication. A presence service maintains log on information. Web Service Interface
Setting up and changing organizations and roles
Connect roles to users
Notifies on organization change. Web Service interface
NERE is a distributed system
With one instance on every locality in the FMLS 2010, operating in static, semi static and mobile domain
NERE uses industry standards
To enable the combination of SwAF specific security mechanisms with COTS software and hardware
This slide is a more detailed description NCES, its functions and its underlying technology
Abbreviations: SIP= Session Initiation Protocol
DNS=Distributed Name Server

8. Focus Area Description NERE
Frameworks
FMLS enabling system C2
Intelligencel
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Interfaces
NERE
NERE will consist of:
Distributed systems providing catalog and authorization services
A fast distributed name server implementation
Key server for the distribution of symmetric keys
Set of code modules implementing secure multicast messaging and session based communication
Encryption units and encryption key stores for both symmetric and asymmetric keys
This slide shows the general functions and characteristics for NERE

9. Focus Area Description NERE
Frameworks
FMLS enabling system C2
Intelligencel
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Interfaces
Possible approach of standard utilization
in NERE:
DNS protocols
The DNS implementation uses standard DNS
protocols and is totally transparent. It will be
used along with other (hierarchical) DNS
implementations
JMS interface and a proprietary provider interface
The SRMM uses both an industry standard JMS
interface and a native core interface. The JMS inter-
face is for message communication e.g. SOAP, Adat-P3).
It gets keys from either key stores or the key server to
do SwAF specific encryption/decryption.
Security standards APIs
PKCS#11 PKCS#12
Web services interoperability
WSI 1.1
The TLS module acts as a TLS wrapper for all TCP communication and uses SwAF specific encryption mechanisms and key stores (e.g. TAK)
NERE
This slide is a more detailed description NERE, its functions and its underlying technology
Abbreviations: Adat-P3=Allied Data Publishing 3 (Formatted messages)
JMS=Java Message Service
SOAP=Simple Object Access Protocol
PKCS=Public key cryptographic standard
TAK=Totalförsvarets aktiva kort

10. Focus Area Description – NCES Artifacts
Service Descriptions
Reference Architecture
X nn
Description
Frameworks
FMLS enabling system C2
Intelligencel
Logistics
Collaboration tools
Information
Administrative tools
FMLS 2010 Technical System
NCES
Communication Infrastructure
Training & Simulation
Systems mgmt
Security mgmt
Legacy
Weapon
system
Methods
Technical
Design Rules
Interface Descriptions
Interfaces
NERE
Design Rules
Target Architecture
A. Scenario XXX
This slide shows the main artifacts that will be produced within LedsystT (sub project 1).
This type of artifacts are generic and do belong in FMLS2010 Technical system:
Reference Architecture
Service descriptions
Interface descriptions
Design Rules
This type of artifacts are related to a certain mission in a certain scenario performed with certain equipment and do not belong in FMLS2010 Technical system:
Target Architecture
SwAF HQ
Scenario
Target Architecture
B. Scenario YYY

11. Alternativ 2 – Core services

12. Application services

13. Application support services

14. NERE – Network Enabling Runtime Environment