Embed Size (px)
Citation preview
NATO Nations Deepen Operation's Field
Cooperation With Business Processes
Kurt Veum NCIA Principal Scientist
Marc Fiammante IBM Distinguished Engineer
NATO UNCLASSIFIED
Agenda
• About NATO Communications & Information Agency
• Coalition Intelligence, Surveillance & Reconnaissance (ISR)
• Model Driven Architecture Development
• ISR Architecture
• Summary
NATO Communications & Information Agency
Connects forces, NATO and Nations, where and when required by providing interoperable Communications and Information Systems and services.
Provider of NATO-wide IT services and state-of-the-art C4ISR capabilitiesby applying industry best practices and providing a full life-cycle approach
Key pillar of NATO Secretary General’s Smart Defence and Connected Forces initiatives.
• Fully Customer Funded.
• Independent design authority for NATO enterprise.
• Full life-cycle perspective.
• Live and breathwith our customers.
• Unique blend of multinational technical and operational expertise.
NATO UNCLASSIFIED 4
Our value
The JISR Service Line
NATO UNCLASSIFIED 5
• The JISR SL focus = facilitating global interoperability within the JISR COI internal to NATO but also with external COI’s
• The JISR SL will be responsible to its customers for planning and executing all lifecycle management activities in support of the JISR Cycle and associated services, including:
• Strategy & Policy• Standardisation• Requirements Analysis • CD&E• Design & Development • Processes• Acquisition• Implementation• Transition • Service Operations (O&M)
• Overview
– 9 NATO Nations
– NCIA (Technical Management, Subject Matter Expertise and Support)
– NATO organisations (ACO, ACT, NAEW&C)
– More than 150 C2ISR systems
– Active industry involvement
• Process
– National Funding
– NATO and National Staffs from Government
and Industry
– Standards based Interoperability
MAJIIC2 in a nutshell
NATO UNCLASSIFIED 6
Multi- intelligence All-source Joint Intelligence Surveillance And Reconnaissance (ISR) Interoperability Coalition (MAJIIC 2)
MAJIIC2 The Challenges
NATO UNCLASSIFIED
• No means for sharing, sensor data, information and
intelligence
between coalition partners
– Duplication of collection effort
– Inability to fulfil information
requirements
• Single partner lacks required number
and mix of assets
• Incompatible processes and procedures
• Inflexible to change in process and information
models
JISR Services in Support of
Operations
IntelligenceIntelligenceIntelligenceIntelligence
CycleCycleCycleCycle
ISR Products(1st , 2nd and 3rd Order
Exploitation)
ISRtask /
request
Joint ISRJoint ISRJoint ISRJoint ISR
ProcessProcessProcessProcess
Multi-national, multi-service, multi-echelon processes
OperationsOperationsOperationsOperations
CycleCycleCycleCycle
ISRtask /
request
Information Requests
Intelligence Products
ISR Products(1st Order
Exploitation)
Imp
lem
en
t
ati
on
s
Mo
de
l D
rive
n A
rch
ite
ctu
re
Web Service Stack
Op
era
tio
ns
WSDL XSD WS-*
SoaML Model
Service Interfaces Participants
Service Contracts
Bindings
Messages
UML ModelInformation Models
Use Case Narrative
Functions and Tasks
CONOPs/TTPs/ SOPs Lessons Learned
Doctrine Operations Exercises
Experimentation
Interface between Operations and ArchitectureInterface between Operations and Architecture
BPMN ModelProcess Models Choreography
Events
IERs
Executables/ Binaries/Applications/ Services
Platforms.Net/ Java/ Native
Test Suites/ Harnesses Data
Interface between Design Time and Run TimeInterface between Design Time and Run Time
Fe
ed
ba
ck L
oo
p
MAJIIC 2 Model Driven Architecture
NATO UNCLASSIFIED
Computationally Independent Model
Platform Independent Model
Platform Specific Model
• There must be consistency & traceability between choreography, service and
information models.
Method & Model Coherency
NATO UNCLASSIFIED
Business process choreography models Information models
Service & Event models
Tasks & Messages
• A central process (which can be another service) takes control of the involved services and coordinates the execution of different operations on the services involved in the operation.
• The involved services do not "know" (and do not need to know) that they are involved in a composition process and that they are taking part in a higher-level business process.
• Only the central coordinator of the orchestration is aware of this goal, so the orchestration is centralized with explicit definitions of operations and the order of invocation of services.
Orchestration
NATO UNCLASSIFIED
� Choreography, in contrast, does not rely on a central coordinator.
� Rather, each service involved or notified in the choreography knows exactly when to execute its operations and with whom to interact.
� Choreography is a collaborative effort focusing on the exchange of messages in public business processes.
� All participants in the choreography need to be aware of the business process, operations to execute, messages to exchange, and the timing of message exchanges.
Orchestration Coordinator
Service
Service
Service
Service
Service
Service
Service
Service
Choreography
Choreography – what?
versus
MAJIIC 2 CIM Information ModelsMAJIIC 2 CIM Information ModelsMAJIIC 2 CIM Information ModelsMAJIIC 2 CIM Information Models
NATO UNCLASSIFIED
MAJIIC 2 CIM Choreography ModelMAJIIC 2 CIM Choreography ModelMAJIIC 2 CIM Choreography ModelMAJIIC 2 CIM Choreography Model
NATO UNCLASSIFIED
• SOAML provides support for design process from business processes to service interfaces.
• It defines a UML profile with stereotypes allowing automatic transformation from models to
WSDLs
Service oriented architecture Modeling Language (SoaML) for service modeling http://www.omg.org/spec/SoaML/
NATO UNCLASSIFIED
MAJIIC 2 PIM Service Model (SOAML)MAJIIC 2 PIM Service Model (SOAML)MAJIIC 2 PIM Service Model (SOAML)MAJIIC 2 PIM Service Model (SOAML)
NATO UNCLASSIFIED
• Service Specifications are Compact
• Contract First Development (CFD)
• Specifications:– Information
– Interface
– Behavioural/ Business Rules
– Exceptional
– NFR/ SLA
• E.g.: SPS++ replication – 50 concurrent connections, 5 messages per second,
average message size 20KB;
Service Specification/ Contract First Development
NATO UNCLASSIFIED
NATO UNCLASSIFIED
MAJIIC 2 The Challenges
Operational lessons learned:
– Coalition is the norm
– Come as you are
– Bring what you got
– Plug and play (pray)
Coalition Context:
– Limited High Value Assets (Sensors)
– Limit Duplication of effort
– Provide Burden Sharing
– Coordinate processes across Nations, Services, and Echelons
Federation of autonomous partners engaged in a cooperative effort
Multi-national, multi-service, multi-echelon processes
• Product/ Metadata library supporting Discovery, Search, Archiving
and Retrieval to support near-real-time and forensic analysis
• Distributed choreographed workflows for requesting information,
assigning tasks to sensors and analysts
• Distributed, shared structured information
• Streaming Data (GMTI, Tactical Data, Video)
MAJIIC 2 data types
NATO UNCLASSIFIED
MAJIIC 2 Objectives
Change quickly to meet new requirements
• New Units, Sensors, Systems, Processes
Integrate with legacy and evolving capabilities
• Disadvantage Units, Legacy Units, Evolutionary Capabilities (AMN)
Share data with other Communities of Interest (COI)
• Operations, Plans, Logistics
NATO UNCLASSIFIED
Fallacies of Distributed Computing (1994)
NATO UNCLASSIFIED 20
The fallacies are summarized as follows:
1.The network is reliable.
2.Latency is zero.
3.Bandwidth is infinite.
4.The network is secure.
5.Topology doesn't change.
6.There is one administrator.
7.Transport cost is zero.
8.The network is homogeneous.
- http://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
– National Sovereignty of Implementation/ Technology Choice
– Re-use
– Observe Standards
– Federation
– Service Oriented & Event Driven/ Loose Coupling/ Message Orientation
– No Vendor Lock In
– Specification Driven/ Wire Protocol/ Contract First Development
– Design for Unreliability
– Minimum Mission Footprint vs Autonomy
– Location Independence
– Continuous Development and Test (Environment)
Architectural Principles
NATO UNCLASSIFIED
� Employ Hybrid (Opportunistic) Data Replication
� Multi Master Distributed Write Scheme
� Asynchronous Propagation
� Multi Version Concurrency Control
� Query & Update fine-grained MAJIIC 2 Data
� SPARQL & RDF Store
� UML model for MAJIIC 2
� Event Driven Architecture
� Entity Representation
� Layered Architecture
Architectural Decisions
NATO UNCLASSIFIED
MAJIIC2 Service Stack
NATO UNCLASSIFIED 23
COI Enabling Layer
Core Enterprise Service Layer
SPS++
Pub Sub
NRS3 E2RSCore GIS Collaboration
MAJIIC 2 User Facing Capabilities
IRM&CMExploitation SensorC2
JISR COI Specific LayerOrganization Request
CSD Query
Task
CSD PubCSD Stream
ATO/ACO
Target List
Requirement
4559
CORBA CSD
Entity
Validation
Entity
CRUDAggregationPre-Canned
Queries
MAJIIC 2 in context of NATO Enterprise Architecture(C3 Classification Taxonomy)
NATO UNCLASSIFIED
MAJIIC 2 User Facing CapabilitiesMAJIIC 2 User Facing CapabilitiesMAJIIC 2 User Facing CapabilitiesMAJIIC 2 User Facing Capabilities
Enterprise Support ServicesEnterprise Support ServicesEnterprise Support ServicesEnterprise Support Services
SOA Platform ServicesSOA Platform ServicesSOA Platform ServicesSOA Platform Services
Replicating PersistenceReplicating PersistenceReplicating PersistenceReplicating Persistence
COI Specific ServicesCOI Specific ServicesCOI Specific ServicesCOI Specific Services
Infrastructure Storage ServicesInfrastructure Storage ServicesInfrastructure Storage ServicesInfrastructure Storage Services
MAJIIC 2 User Facing Capabilities
Enterprise Support Services
SOA Platform Services
Replicating Persistence
COI Specific Services
Infrastructure Storage Services
Distribution of Nodes (Federation of Service Stacks)Distribution of Nodes (Federation of Service Stacks)Distribution of Nodes (Federation of Service Stacks)Distribution of Nodes (Federation of Service Stacks)
NATO UNCLASSIFIED 25
Plug and Play
NATO UNCLASSIFIED 26
Mission Composable Plug and Play Architecture
Core Enterprise Services
Core Enterprise Services
Communications Services
Community of Interest Services
Community of Interest Services
User Applications
User Applications
A new replication mechanism required for MAJIIC 2 it should be:
• Basically Available, Soft State and Eventually Consistent (BASE
not ACID)
• Partition Tolerant, Available and Eventually Consistent (CAP)
• Asynchronous, queued & message oriented
• Multi-Master Write
• Low write latency/ non blocking
• Realise a distributed shared information space
• Support Choreographed Distributed Process
• Introduces the concept of Storage-as-a-Service
Replication
NATO UNCLASSIFIED
• C3 Classification Taxonomy for Information Products
• Subscribe to trees of echelons or types– xmlns:topns=“urn:int:nato:C3ClassificationTaxonomy”
– topns:Information_Products/Resource_Status/SystemStatusUpdate/MCC
– topns:Information_Products/Resource_Status/Organization/SystemStatusUpdate/*
– topns:Information_Products/Requests_And_Responses/Request_for_Information_RFI
– topns:Information_Products/Resource_Status/Organization/SPSPlusPlus
• State transitions
• Enterprise Event Relay
• MAJIIC 2 Notification Envelope– Meets minimum metadata standards
– Enforces cross domain mandatory metadata
Event Driven Architecture
NATO UNCLASSIFIED
• Not vapour-ware!
• Scenarios Evolved Verified and Validated
– MAJEX 12
– TEI13 - MAJEX13
– TIE14-A - UV14 - TIE14-B
• Interoperability across combinations of
– Organisational Structures/ Echelons
– COI
– NATO, Nations (9) and Industries (30+)
– Implementations (upto 5)
– Platforms
– Layers
Plug and Play in Practice
NATO UNCLASSIFIED
Service Provision at UV14
NATO UNCLASSIFIED
MAJIIC 2 Stack OptionsMAJIIC 2 Stack OptionsMAJIIC 2 Stack OptionsMAJIIC 2 Stack Options
26.02.2015 NATO UNCLASSIFIED 31
WAN
CE
S S
OA
P
Full StackTo Full Stack
Full StackTo Full Stack
Partial StackCOI to remote CES
Partial StackCOI to remote CES
Partial StackUA to remote COI
Partial StackUA to remote COI
E2R
S
Bu
sin
ess S
OA
P
Web Client toremote COI
Web Client toremote COI
Web
cli
en
t H
TT
P
Rep
licati
on
CE
S E
ven
tin
g
Bu
sin
ess E
ven
tin
g
Runtime Choreography Monitoring
NATO UNCLASSIFIED
KPI: Choreography adherence
Choreography KPIs
NATO UNCLASSIFIED
KPI: Task choreography adherence Message frequency
System operational status
Air 1
Maritime
Land 1
Land 2 Air 2IRM CM
Exploitation system
IRM CMGroundControl
IRM CM
RFI
Task
SSU
SSU
Task
FW
On
OnAccpt
IA
Prod
Prod
Acm
Acm
Cmplt
RC
RC
RC
RC
Ack
Ack
RFI Task (to Sensor)
FF MotionImagery
Choreography Monitoring Conceptual
NATO UNCLASSIFIED
1. Model Driven Architecture development
2. Service Contract First Development
3. Combination of SOA/ ROA/ EDA
4. Storage-as-a-Service
5. Working Methodology and Framework as well as an ISR
solution
6. Evolutionary & Agile
7. Extensibility by design
8. Continuous Regression Test Environment
Summary
NATO UNCLASSIFIED
