Developing a C4I Architecture for the Netherlands Armed Forces

Size: px

Start display at page:

Download "Developing a C4I Architecture for the Netherlands Armed Forces"

Dorthy Ellis
6 years ago
Views:

1 Developing a C4I Architecture for the Netherlands Armed Forces Dick Ooms & Tim Grant Netherlands Defence Academy 1 JOINT? COMBINED 2 1

2 Presentation Structure Why a C4I Architecture? Starting point New approach C4I Architecture Products Process Model & Services Model What we learned so far 3 Presentation Structure Why a C4I Architecture? Starting point New approach C4I Architecture Products Process Model & Services Model What we learned so far 4 2

3 Navy C2 systems 5 Army mobile C2 6 3

4 Air Force & Army C2 Combined Air Operations Center (CAOC) Battalion Command Post (CP) in the field 7 Challenge 1: Effective information sharing among dissimilar entities 5/14/09 8 4

5 22 september 2006 Challenge 2: building the C2 chain NL Army suite of C2 systems MOBILE DEPLOYED TITAAN DISMOUNTED TITAAN RADIO NET DECIUS THEMIS XANTHOS AFSIS ISIS PALLAS OSIRIS CYRUS

6 Presentation Structure Why a C4I Architecture? Starting point New approach C4I Architecture Products Process Model & Services Model What we learned so far 11 DIVA Architecture Model conceptueel, direction wat/ composition logisch, implementation waarom RICHTING VORMGEVING hoe BV-Architectuur Goals and Tasks Concept of Operations Organisation Process Models Flow Organisationimplementation Entities, Roles & Activities IV-Architectuur Support Requirements Services Model Systems ICT-Architectuur Requirements for ICT Solutions Components model Building Blocks 12 6

7 DIVA Architecture Hierarchie 5/14/09 Corporate Architecture (HDIO) Sub Architectures C4I: CDS M&F: DMO/DFEZ P&O: HDP management::dio Aspect Architectures Security: BA Networks & Comms: DIO Integration: DIO C4I (sub) Architecture Project Architectures (DMO/IVENT) e.g. TITAAN, OMIS, MS Walrus, ISIS, BMS AFSIS etc. 13 Initial Operational Process Model 14 7

8 Presentation Structure Why a C4I Architecture? Starting point New approach C4I Architecture Products Process Model & Services Model What we learned so far 15 Boyd s OODA loop Cultural Traditions Observations Genetic Heritage Analyses & Synthesis Decision (Hypothesis) Action (Test) New Previous Experience Unfolding Interaction With Unfolding Interaction With Note how orientation shapes observation, shapes decision, shapes action, and in turn is shaped by the feedback and other phenomena coming into our sensing or observing window. From The Essence of Winning and Losing, John R. Boyd, January

Unfolding Interaction With Environme nt Genetic Heritage New Cultural Traditions Previous Experience Unfolding Interaction With Environme nt Unfolding Interaction With Genetic Heritage New Cultural

9 Unfolding Interaction With Environme nt Genetic Heritage New Cultural Traditions Previous Experience Unfolding Interaction With Environme nt Unfolding Interaction With Genetic Heritage New Cultural Traditions Previous Experience Unfolding Interaction With Unfolding Interaction With Genetic Heritage New Cultural Traditions Previous Experience Unfolding Interaction With 22 september 2006 Possible Process Hierarchie Observations Decision (Hypothesis) Action (Test) Joint Air Defence Observations Decision (Hypothesis) Action (Test) Observations Decision (Hypothesis) Action (Test) Common Operational Picture Recognized Air Picture 17 Air Defence Parallel Processes Is everybody informed of my assessment and intentions? What is the current Air Picture? What is the ennemy s most likely course of action? What are my capabilities and possible courses of action? Do I need to adjust the alert state? What about the EMCON Plan? Do I need an adjustment of the Rules of Engagement? What is the actual weapon and fuel state of my fighters? Do I need to reposition my units in view of the threat axis? 18 9

10 Stakeholders & COIs Primary Stakeholders: CDS HDIO DMO CAMS & C2SC Major Operational Commands Predefined COIs: Non-operational: policy&doctrine, planning&budget, requirements, acquisition, R&D, HRM Operational: OPS-planning, -support, -security, C4I-planning & -management, weapon employment, sensor management, ISR/INTEL, education & training 19 Stakeholders, COIs and views 20 10

11 Purpose C4I Architecture provide guidance for definition C4I requirements support better scoping of C4I projects provide better cohesion between C4I projects provide guidance for project architectures set standards & technical requirements for C4I projects 21 Presentation Structure Why a C4I Architecture? Starting point New approach C4I Architecture Products Process Model & Services Model Next Steps What we learned so far 22 11

12 C4I Architecture products C4I Basic Considerations & Principles C4I Standards & Technologies Checklist C4I Requirement Process Technical Requirements & Guidelines Operational Process Model Operational Services Model 23 C4I Basic Considerations & Principles conceptueel, direction wat/ composition logisch, implementation waarom RICHTING VORMGEVING hoe BV-Architectuur Goals and Tasks Concept of Operations Organisation Process Models Flow Organisationimplementation Entities, Roles & Activities IV-Architectuur Support Requirements Services Model Systems ICT-Architectuur Requirements for ICT Solutions Components model Building Blocks 24 12

13 C4I Standards & Technologies conceptueel, direction wat/ composition logisch, implementation waarom RICHTING VORMGEVING hoe BV-Architectuur Goals and Tasks Concept of Operations Organisation Process Models Flow Organisationimplementation Entities, Roles & Activities IV-Architectuur Support Requirements Services Model Systems ICT-Architectuur Requirements for ICT Solutions Components model Building Blocks 25 Checklist C4I Requirement Process & Technical Requirements & Guidelines conceptueel, direction wat/ composition logisch, implementation waarom RICHTING VORMGEVING hoe BV-Architectuur Goals and Tasks Concept of Operations Organisation Process Models Flow Organisationimplementation Entities, Roles & Activities IV-Architectuur Support Requirements Services Model Systems ICT-Architectuur Requirements for ICT Solutions Components model Building Blocks 26 13

14 Development model Version 1.0 Version 0.x Version 1.x D: Using & testing Development first architecture products B1: Definition C1:Development (iterative) Follow-on development (iterative) Evolutional development Maintenance (iterative) A: Stakeholder-analysis B2: Definition C2: Development (iterative) Phase 2 (from April 2009) Phase 3 (t.b.d.) Time 27 Presentation Structure Why a C4I Architecture? Starting point New approach C4I Architecture Products Process Model & Services Model What we learned so far 28 14

15 Development Process & Services Models step 1: collect information at school / training center step 2: study material, develop 1st draft process model step 3: collect comments, develop 2nd draft step 4: test model by visits, observation, discussion step 5: correct, refine & amplify step 6: validate with all parties involved 29 Interdependencies conceptueel, direction wat/ composition logisch, implementation waarom RICHTING VORMGEVING hoe BV-Architectuur Goals and Tasks Concept of Operations Organisation Process Models Flow Organisationimplementation Entities, Roles & Activities IV-Architectuur Support Requirements Services Model Systems ICT-Architectuur Requirements for ICT Solutions Components model Building Blocks 30 15

16 Selection of processes to be modelled first Criteria: Joint Combined Imperfect Complementary Processes selected: - Joint Air Defence - Picture Compilation Ground Operations - Close Air Support Next: Peace Support Ops, CIMIC 31 Presentation Structure Why a C4I Architecture? Starting point New approach C4I Architecture Products Process Model & Services Model What we learned so far 32 16

17 What we learned so far involve stakeholders early include non-operational information domains in scope show early, useable results build model bottom-up, using standardised format (e.g. OODA-Loop) model first joint & combined processes not all services are services 33 Further research Suitability of DIVA methods & tools Suitability of C4I Architecture to support NEC transition Suitability of Service-Oriented Architecture to support info exchange between military & civil partners 34 17

18 35 18

Developing a C4I Architecture for the Netherlands Armed Forces

Developing a C4I Architecture for the Netherlands Armed Forces Dick Ooms (POC) & Tim Grant Netherlands Defence Academy (NLDA) P.O. Box 10000, 1780 CA Den Helder, The Netherlands Abstract - The purpose