j o i n t
play

J O I N T ? COMBINED 2 1 22 september 2006 Presentation - PDF document

May 23, 2023 •303 likes •500 views

22 september 2006 Developing a C4I Architecture for the Netherlands Armed Forces Dick Ooms & Tim Grant Netherlands Defence Academy 1 J O I N T ? COMBINED 2 1 22 september 2006 Presentation Structure Why a C4I Architecture?

  1. 22 september 2006 Developing a C4I Architecture for the Netherlands Armed Forces Dick Ooms & Tim Grant Netherlands Defence Academy 1 J O I N T ? COMBINED  2 1

  2. 22 september 2006 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. 22 september 2006 Navy C2 systems 5 Army mobile C2 6 3

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

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

  6. 22 september 2006 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 implementation conceptueel, wat/ waarom hoe logisch, direction composition RICHTING RICHTING VORMGEVING BV-Architectuur Goals and Tasks Organisation Organisation- implementation Environment Process Models Entities, Roles & Information Flow Activities Concept of Operations IV-Architectuur Information Information Information Support Services Model Systems Requirements ICT-Architectuur Components Building Blocks Requirements for ICT Solutions model 12 6

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

  8. 22 september 2006 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 Genetic Analyses & Action Heritage Decision Feed Observations Feed Feed Synthesis Forward Forward (Hypothesis) Forward (Test) New Previous Information Experience Unfolding Unfolding Interaction Interaction With With Environment Environment 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 1996. 16 8

  9. 22 september 2006 Possible Process Hierarchie Cultural Traditions Genetic Heritage Action Observations Decision Feed Forward Feed Forward Feed Forward (Hypothesis) (Test) New Information Experience Previous Unfolding Unfolding Interaction Interaction With With Environment Environment Joint Air Defence Cultural Traditions Genetic Heritage Decision Action Observations Feed Forward Forward Feed Forward Feed (Hypothesis) (Test) Information New Previous Experience Unfolding Unfolding Interaction Interaction With With Environment Environment Common Operational Picture Cultural Traditions Action Observations Genetic Decision Heritage Forward Feed Feed Forward (Hypothesis) Feed Forward (Test) Information New Previous Experience Unfolding Unfolding Interaction Interaction With With Environme Environme nt nt Recognized Air Picture 17 Air Defence Parallel Processes What is the What is the What is the What is the current Air current Air ennem ennemy’s mos y’s most t Picture? Picture? likely cour lik ely course of se of action? action? What are my What are m y capabilities and capabilities and Is ever Is e erybody ybody possible courses possible cour ses informed of m inf ormed of my y of action? of action? assessment and assessment and int intentions? entions? What about the What about the Do I need t Do I need to adjus o adjust the t the EMCON Plan? EMCON Plan? alert s aler t stat tate? e? Do I need t Do I need to o reposition m reposition my units y units in vie in view of the threat w of the threat Do I need an Do I need an axis? axis? adjus adjustment of the tment of the Rules of ules of What is the What is the Engagement? Engagement? actual weapon actual w eapon and fuel stat and fuel s tate of e of my f y fight ighter ers? s? 18 9

  10. 22 september 2006 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. 22 september 2006 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. 22 september 2006 C4I Architecture products • C4I Basic Considerations & Principles • C4I Standards & Technologies • Checklist C4I Requirement Process • Technical Requirements & Guidelines • Operational Process Model • Operational Information Services Model 23 C4I Basic Considerations & Principles implementation conceptueel, wat/ waarom hoe logisch, direction composition RICHTING RICHTING VORMGEVING BV-Architectuur Goals and Tasks Organisation Organisation- implementation Environment Process Models Entities, Roles & Information Flow Activities Concept of Operations IV-Architectuur Information Information Information Support Services Model Systems Requirements ICT-Architectuur Components Building Blocks Requirements for ICT Solutions model 24 12

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

  14. 22 september 2006 Development model Version 1.0 Version 1.x Version 0.x D : Using & testing Development first architecture products B1 : Definition (iterative) (iterative) C1 :Development Follow-on development (iterative) Maintenance Evolutional development A : Stakeholder-analysis B2 : Definition (iterative) C2 : Development 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. 22 september 2006 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 implementation conceptueel, wat/ waarom hoe logisch, direction composition RICHTING RICHTING VORMGEVING BV-Architectuur Goals and Tasks Organisation Organisation- implementation Environment Process Models Entities, Roles & Information Flow Activities Concept of Operations IV-Architectuur Information Information Information Support Services Model Systems Requirements ICT-Architectuur Components Building Blocks Requirements for ICT Solutions model 30 15

Recommend

More recommend