Friendly Force Friendly Force Friendly Force Friendly Force Friendly Force Friendly Force Friendly Force Friendly Force Information SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation SharingInformation Sharing
Lessons LearnedLessons LearnedLessons LearnedLessons LearnedLessons LearnedLessons LearnedLessons LearnedLessons Learnedandandandandandandandand
way towards NNECway towards NNECway towards NNECway towards NNECway towards NNECway towards NNECway towards NNECway towards NNEC
NATO UNCLASSIFIED
way towards NNECway towards NNECway towards NNECway towards NNECway towards NNECway towards NNECway towards NNECway towards NNEC
7th NATO CIS SymposiumPrague (CZE), 15 October 2008
Roberto [email protected]. +31 (0)70 374-3576
about the difficulty of forecasting IT …about the difficulty of forecasting IT …
Let’s start with two quotesLet’s start with two quotes
“I think there is a world market for maybe five computers “
T.J. Watson, founder of IBM, 1943
… and about successful development methodologies… and about successful development methodologies
NATO UNCLASSIFIED 2
“Make everything as simple as possible, but not sim pler.”Albert Einstein
Presentation OutlinePresentation Outline
�� FFT Interoperability todayFFT Interoperability today�� On going activitiesOn going activities�� Lessons learnedLessons learned�� FFT Services and NNECFFT Services and NNEC�� ChallengesChallenges�� ConclusionsConclusions
NATO UNCLASSIFIED 3
FFT Interoperability todayFFT Interoperability today
ApproachApproach�� Incremental & Incremental & evolutionaryevolutionary process, process, holisticholistic
AchievementsAchievements�� Interoperability Standard interface: NFFIInteroperability Standard interface: NFFI (1)(1)
�� Interoperable NATO and National capabilitiesInteroperable NATO and National capabilities�� ISAF FFT NATOISAF FFT NATO--National Interoperability (NNI) National Interoperability (NNI)
ArchitectureArchitecture
�� SimplestSimplest technical solution to solve 80% of the problemtechnical solution to solve 80% of the problem
NATO UNCLASSIFIED 4
ArchitectureArchitecture
(1) NATO Friendly Force Information
FFT FFT –– Technical Interoperability ConceptTechnical Interoperability Concept
MTF / ADatP-3
OtherNATO C2ISNational CCIS
MIP / JC3IEDM
National CCIS
C2 / Situation AwarenessC2 / Situation AwarenessServices / ApplicationsServices / Applications
NATO LC2ISISAFC2IS
Ver
tical
Inte
rope
rabi
lity C2IS - Horizontal Interoperability
NFFI (NATO FRIENDLY FORCE INFORMATION) – Std FFT Data Exc h. Format & Services
Nat BMS NFFIGWY
NATO NFFI
Force TrackingForce TrackingServicesServicesFTS - Horizontal Interoperability AOCAOC
NOCNOC
NATO C2ISNational CCIS National CCISNFFI
C2IS
Ver
tical
Inte
rope
rabi
lity
NATO UNCLASSIFIED 5
NATOIFTS
NFFIGWY
Other TacOther Tac--platfplatf
FT
S -
NFFI (exp)
FFT Interoperability todayFFT Interoperability todayDevelopment ProcessDevelopment Process
2006 2007 2008 2009 2010 2011
REQ
DEF
REALExtension
NFFI Standard
ISAF-NNI IOC
NATO UNCLASSIFIED 6
USE
Basic FFTBasic FFTInteroperabilityInteroperability
AdaptableAdaptableInteroperabilityInteroperability
Push, XML on IP Smart-Pull WebSvcLand Interop.Svc & Infra
NNEC Core Svc, ...
ExtendedExtended(Land Tactical)(Land Tactical)
Interoperability Standard interface: NFFIInteroperability Standard interface: NFFI
FFT Interoperability todayFFT Interoperability todayAchievementsAchievements
�� Data Exchange Format (XML)Data Exchange Format (XML)�� Multiple sections : core (PLI), add’l info, securit y classif.Multiple sections : core (PLI), add’l info, securit y classif.�� Multiple sections : core (PLI), add’l info, securit y classif.Multiple sections : core (PLI), add’l info, securit y classif.
�� Two profiles for data transfer (IP1, IP2) Two profiles for data transfer (IP1, IP2) –– data pushdata push
NATO UNCLASSIFIED 7
•Definition, standardization and testing• First NFFI def & experiment. (CWID05) June-05• Second experimentation (CWID06) June-06• Consolidated experiment. specs(v 1..3) Aug-06• Pre-operational interop.. test (NC3A) Feb-07
•Specification Status• NFFI v 1.3 interim standard (D-doc) Dec-06• NFFI D-doc as baseline for STANAG-5527 on-going
Data Layering and labelling in NFFI�Different data elements corresponding to different classification�Simple (schema -based) security filtering possible
NFFI Data Model and securityNFFI Data Model and security
�Simple (schema -based) security filtering possible�Section-level labelling
Usually HIGH sec. classification.
Relatively dynamic data.
Usually LOW sec. classification
Dynamic data
Usually HIGH sec. classification.
Relatively static.
For future use(sec. labelling)
FFT Interoperability todayFFT Interoperability todayAchievementsAchievements
Interoperable NATO and National capabilitiesInteroperable NATO and National capabilitiesSAS*
GRATS
BFT*
TBD
FAUSTFisH*
Fleet TrackerBMS*
BMS
FBCB2*MTSFACT SHEETFACT SHEET
• XXX Terminals, XX CmdPosts, XX Control Suite• Report freq: N min or XXX m.• Communication BLOS, SATCOM (L-band)• Interop. Standard NFFI 1.3•IOC March 2007
IFTS SATCOM- Commercial L-band -
ISAF FTS (NATO)
NATO UNCLASSIFIED 9
GRATS BowmanSA*
SiR*Maestro
TBD BFT
TBD
SICIB*
OTS-VR-ONI*
KFTS IFTS
IFTS Terminal- various vehicles -
ISAF FFT NATOISAF FFT NATO--National Interoperability Arch.National Interoperability Arch.
FFT Interoperability todayFFT Interoperability todayAchievementsAchievements
ISAF COP*
(NATO Secret)FACT SHEETFACT SHEETOperational Implementation Status
• NFFI approved as interim standard(*) Dec-06• ISAF Interoperability Experiment (FTEX) Feb-07
ISAF COP*
(ISAF Secret)
(ISAF Restricted)
IFTSControl Center
IFTS
FAUST
FBCB2(OOT**)
Other Command& Control App.
NFFI
NFFI
• ISAF Interoperability Experiment (FTEX) Feb-07• Implementation in the IFTS May-07• Interoperability IOC with (USA) Aug-07• Interoperability with NOR Dec-07• Interoperability with FRA Feb-08•Interoperability with DEU Q3-08
Current activities• Connect more nations on-going• Revise and enhance procedures on-going• Plan next capability improvement on-going
NATO UNCLASSIFIED 10
FAUST
BFTSIR
NFFI
NFFI
NFFI
(*) Common Operational Picture(**) Out of Theatre
FFT Interoperability FFT Interoperability On going activitiesOn going activities
Relevant Activities:Relevant Activities:
�� Specification of Data Exchange (XML) Service Interf aceSpecification of Data Exchange (XML) Service Interf ace�� Specification of Data Exchange (XML) Service Interf aceSpecification of Data Exchange (XML) Service Interf ace
�� Definition of Land Track Interoperability ServicesDefinition of Land Track Interoperability Services
�� Harmonization with nonHarmonization with non--FFT specific standardsFFT specific standards
NATO UNCLASSIFIED 11
FFT Interoperability FFT Interoperability On going activitiesOn going activities
Definition of a Data Exchange (XML) Service Interfa ce Definition of a Data Exchange (XML) Service Interfa ce (SIP3)(SIP3)
�� RequirementRequirement�� Smart data pull Smart data pull functionalityfunctionality�� Complementing the Complementing the data push data push profiles (NFFI IP1, IP2).profiles (NFFI IP1, IP2).�� Same data formatSame data format
�� SolutionSolution�� FFT Service (FTS) abstractionFFT Service (FTS) abstraction�� WebWeb--ServiceService InterfaceInterface technologytechnology
NFFI
IP1
IP2
NATO UNCLASSIFIED 12
�� WebWeb--ServiceService InterfaceInterface technologytechnologyNFFI
NFFI
IP2
SIP3
FFT Interoperability FFT Interoperability On going activitiesOn going activities
Definition of Land Track Interoperability Service ( LTIS)Definition of Land Track Interoperability Service ( LTIS)
�� RequirementRequirement�� RequirementRequirement�� Federation of FTS and C2IS Federation of FTS and C2IS needs more than standard data exchangeneeds more than standard data exchange�� An Interoperability Service Infrastructure is requi red.An Interoperability Service Infrastructure is requi red.�� Independence from the Area of Operation: important operational req.Independence from the Area of Operation: important operational req.
�� SolutionSolution�� FTS Federation Service(s)FTS Federation Service(s)
�� Enabling MidEnabling Mid --Term FFT interoperabilityTerm FFT interoperability
NATO UNCLASSIFIED 13
�� Enabling MidEnabling Mid --Term FFT interoperabilityTerm FFT interoperability�� LongLong--term : NNEC Community Of Interest (COI) Servi cesterm : NNEC Community Of Interest (COI) Services
FFT Interoperability FFT Interoperability On going activitiesOn going activities
LTIS and NNECLTIS and NNEC
NFFI GY
Dissem LTIS
NII Core Svc
LTI CoI
NATO UNCLASSIFIED 14
NFFI GY
NFFI GY
NFFI GY
Augm
Conv
…
LTI CoISvcs
LTI CoI
FFT InteroperabilityFFT InteroperabilityOn going activitiesOn going activities
Harmonization with nonHarmonization with non--FFT specific StandardsFFT specific Standards
Tact. Data Links
FFT(NFFI)
Msg. Text Formats(ADat-P3)
Tact. Data Links(Link-16)
Combat ID(CID STANAGs)
NATO UNCLASSIFIED 15
(NFFI)
C2 Info.Services(MIP / JC3IEDM)
1.1. QuickQuick WinWin == simplesimple technicaltechnical solutionsolution ++operationaloperational focusfocus �������� ButBut enhancingenhancingOperationalOperational InteroperabilityInteroperability needsneeds timetime ..
Lessons Learned: FFT and NNECLessons Learned: FFT and NNEC
OperationalOperational InteroperabilityInteroperability needsneeds timetime ..
2.2. TheThe introductionintroduction ofof servicesservices helpshelpssimplifyingsimplifying thethe interoperabilityinteroperability problemproblem..AndAnd goesgoes towardstowards aa ServiceService OrientedOrientedArchitectureArchitecture (SOA)(SOA)..
NATO UNCLASSIFIED 16
3.3. Interoperability ProfilesInteroperability Profiles �������� flexibility for flexibility for new technologies and different new technologies and different Operational Interoperability Profiles.Operational Interoperability Profiles.
4.4. XMLXML datadata exchangeexchange formatformat technicallytechnicallysimplifiessimplifies thethe introductionintroduction ofof XMLXML--ServicesServices �������� butbut XMLXML--SvcSvc needneed
Lessons Learned: FFT and NNECLessons Learned: FFT and NNEC(continued)(continued)
?
ServicesServices �������� butbut XMLXML--SvcSvc needneedoperationaloperational justificationjustification..
5.5. XML has XML has limitationslimitations for deployment on for deployment on current tactical comm current tactical comm �������� but today’s FFT but today’s FFT requirements don’t need XML on TACOMrequirements don’t need XML on TACOM
XML ?
NATO UNCLASSIFIED 17
6.6. OneOne XMLXML schemaschema withwith multiplemultiple datadatalayerslayers �������� flexibilityflexibility toto supportsupport dualdualsecuritysecurity domaindomain interoperabilityinteroperability
MY ID
MY POS
ChallengesChallenges
�� Coordination and agreement between Coordination and agreement between NATO and the Nations NATO and the Nations �������� an an agreed agreed NATO/National Roadmap NATO/National Roadmap is requiredis requiredNATO/National Roadmap NATO/National Roadmap is requiredis required
�� Proceeding with the Proceeding with the standardization of standardization of
�� Introducing and Introducing and justifying the need for justifying the need for XMLXML--ServicesServices and SOA in Operational and SOA in Operational FFT ArchitecturesFFT Architectures
NATO UNCLASSIFIED 18
�� Proceeding with the Proceeding with the standardization of standardization of NATO/National FFT ServicesNATO/National FFT Services solvingsolving�� E.g.: limitations of formal specifications, E.g.: limitations of formal specifications,
efficient standard. processefficient standard. process
NFFI
ChallengesChallenges(continued)(continued)
�� Integrating and evolving FFT / Land Integrating and evolving FFT / Land Tactical interoperability within a Tactical interoperability within a Service Oriented Architecture. Service Oriented Architecture. Service Oriented Architecture. Service Oriented Architecture.
�� Applying the same approach for Applying the same approach for other similar interoperability other similar interoperability problemsproblems (within the Land Tactical (within the Land Tactical Interoperability domain)Interoperability domain)
NATO UNCLASSIFIED 19
ConclusionsConclusions
We described where we are with FFT We described where we are with FFT … what we learned… what we learned… what we learned… what we learned… and where we could go towards NNEC… and where we could go towards NNEC
Any questions ?Any questions ?
NATO UNCLASSIFIED 20
(For the FFT/LT Community) we recommend to proceed(For the FFT/LT Community) we recommend to proceedwith a NATO/National technical / operational ROADMA Pwith a NATO/National technical / operational ROADMA P
for FFT and Land Tactical Interoperabilityfor FFT and Land Tactical Interoperability
THANKS ! THANKS ! NC3A Brussels
Visiting address:
Bâtiment Z
NC3A The Hague
Visiting address:
Oude Waalsdorperweg 61Bâtiment ZAvenue du Bourget 140B-1110 BrusselsTelephone +32 (0)2 7074111Fax +32 (0)2 7078770
Postal address:NATO C3 AgencyBoulevard Leopold IIIB-1110 Brussels - Belgium
Oude Waalsdorperweg 612597 AK The Hague
Telephone +31 (0)70 3743000Fax +31 (0)70 3743239
Postal address:NATO C3 AgencyP.O. Box 1742501 CD The Hague
NATO UNCLASSIFIED 21
B-1110 Brussels - Belgium 2501 CD The HagueThe Netherlands