1 / 26

INTEGRATED DEVELOPMENT ENVIRONMENT (IDE) IFIP July 2008 Hennie Harris Program Integration Manager Defence Institute

INTEGRATED DEVELOPMENT ENVIRONMENT (IDE) IFIP July 2008 Hennie Harris Program Integration Manager Defence Institute. SCOPE. Problem statement Stakeholders IDE Concept IDE Focus Typical Outputs IDE Benefits. PROBLEM WITH CURRENT C 2 SYSTEM.

adamdaniel
Télécharger la présentation

INTEGRATED DEVELOPMENT ENVIRONMENT (IDE) IFIP July 2008 Hennie Harris Program Integration Manager Defence Institute

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INTEGRATED DEVELOPMENT ENVIRONMENT(IDE)IFIP July 2008Hennie HarrisProgram Integration ManagerDefence Institute

  2. SCOPE • Problem statement • Stakeholders • IDE Concept • IDE Focus • Typical Outputs • IDE Benefits

  3. PROBLEM WITH CURRENT C2 SYSTEM • The Joint Command and Control system is highly fragmented at the strategic, operational and tactical control levels and lacks operational flexibility. • It does not allow for easy and cost-effective integration of current, new and improved systems or sub-systems. • Complex nature of specifying interoperability requirements for operational Command and Control capabilities and systems. • Doctrine for the execution of joint operational control needs to be developed and verified. • Integrated full life cycle capability management of Joint Command and Control systems is not executed. • Optimal utilisation of available technologies and development of unique technology requirements.

  4. IDE Stakeholders

  5. Capability Development Portfolios Joint Landward Defence Joint Air Defence Joint Maritime Defence Joint Information Warfare Joint Command and Control and Intelligence Joint Operational Support and Sustainment

  6. Integration of Joint C2 Effort SANDF Joint IO Capability Management (C2 Capability Board) J OPS DIV SUPPORT STRUCTURES AND BOARDS ICT IO STDS CMIS SUPPORT STRUCTURES AND BOARDS • Joint IO Development Env. • (RT and NRT) • - Proves Joint Ops Concepts • Confirms user requirements • Develops/evaluates Interoperability standards • - Develops/evaluates related technologies • Directs acquisition projects • Develop J Ops IO Body of knowledge • Integrates systems • Utilises a technology development platform • (mod approach) • - Tests IO Compliance CAPABILITY MANAGEMENT OPERATIONAL REQUIREMENTS, CONCEPTS AND DOCTRINE TECHNOLOGY AND ACQUISITION PROJECTS SERVICES DAPD SUPPORT STRUCTURES AND BOARDS SPECIALIST SUPPORT INSTITUTES AND INDUSTRY

  7. IDE Concept

  8. INTEGRATED DEVELOPMENT ENVIRONMENT (IDE) The IDE is an integrated planning, experimentation, development and preparation process to examine new concepts in doctrine, organisation and technology required for current and future Joint Command and Control through workshops, symposia, modelling and simulation, demonstrations and field exercises.

  9. IDE Functional Layout Centre of Excellence (CoEx) for JC2 Concept & Doctrine Development (Current and Future) Battle Laboratory (BatLab) for JC2 Systems integration and Procedure Development Interoperability Test and Evaluation Facility for JC2 IDE

  10. SPECIFY CONCEPT ACTIVATE ACTIVATE VERIFY INTEGRATION AND EVALUATION PLATFORM (CMI Responsibility) IMPLEMENTATION STRATEGY OPERATIONAL REQUIREMENTS JOps Responsibility) FUTURE C&C ARCHITECTURE & SYSTEMS “To Be” CURRENT C&C SYSTEM ELEMENTS “As Is” INTEGRATED DEVELOPMENT ENVIRONMENT

  11. DEFINITIONS OF INTEROPERABILITY (IO) “The ability of systems, units or forces to provide services to and accept services from other systems, units or forces and to use the services so exchanged to enable them to operate effectively together.”

  12. FRAMEWORK FOR INTEROPERABILITY MANAGEMENT

  13. JC2 FULL LIFE CYCLE MANAGEMENT P P O O S S T T E E D D F F I I T T PLANNING ACQUISITION EMPLOYMENT DEFINITION PHASE-OUT E1 E1 E2 E2 E2 JC2 E3 E3 E3 JC2 Ops C2 E4 E4 IMPACT STUDIES and EVALUATION E4 E5 E5 DEVELOPMENT E5 E6 E6 CAPABILITY PLAN Ops C2 SYSTEMS MASTER PLAN INTEGRATION PLAN REQUIREMENT DEFINITION PHASE-OUT PLAN SUPPORT and SUSTAINMENT PLAN ARCHITECTURE MANAGEMENT JC2 TEST and EVALUATION PLAN

  14. J1 J2 J3 J4 J5 J6 J7 J8 J9 SITUATIONAL AWARENESS PLANNING TASKING CONTROL IDE CONCEPTUAL LAYOUT Joint Inter-departmental Multi-national (JIM) JOINT COMMANDER JOINT C2 APPLICATIONS ARCHITECTURE MANAGEMENT MODELLING AND SIMULATION MIP DATABASE DATA MAPPING DATA REPLICATION CONNECTIVITY NETWORKS OPERATIONAL C2 SYSTEMS

  15. Architecture Views (The MODAF Framework) Strategic Strategic Viewpoint Viewpoint Documents the strategic picture of how military Documents the strategic picture of how military capability is evolving in order to support capability capability is evolving in order to support capability management and equipment planning. management and equipment planning. Operational Operational Systems Systems Viewpoint Viewpoint Viewpoint Viewpoint Documents the operational processes, Documents the operational processes, Documents the operational processes, Documents the systems processes, relationships and context to support operational relationships and context to support operational relationships and context to support operational relationships and context to support systems analyses and requirements development. analyses and requirements development. analyses and requirements development. analyses and requirements development. Acquisition Acquisition Technical Technical Viewpoint Viewpoint Viewpoint Viewpoint Documents policy, standards, guidance Documents policy, standards, guidance Documents acquisition programme Documents acquisition programme and constraints to specify and assure and constraints to specify and assure dependencies, timelines and DLOD status dependencies, timelines and DLOD status POSTEDFIT status quality expectations. quality expectations. to inform programme management. to inform programme management. All All Views Views Provides summary information for the architecture Provides summary information for the architecture that enables it to be indexed, searched and queried. that enables it to be indexed, searched and queried.

  16. IDE Focus

  17. DECISION SUPERIORITY STRATEGIC LEVEL • Identification of national objectives • Allocation of national resources • Monitoring of departmental execution • Alignment of objectives and resources OPERATIONAL LEVEL • Identification of SANDF objectives • Allocation of SANDF resources • Monitoring of Joint execution • Alignment of objectives and resources CONTROL TASKING SITUATIONAL AWARENESS PLANNING TACTICAL LEVEL • Domain execution of tasked objectives • Allocation of domain resources to tasks • Monitoring of domain and Joint execution • Alignment of objectives and resources HT WEAPON SYSTEM LEVEL • Effector execution of tasked objectives • Allocation of effectors to tasks • Control of effector execution • Effect assesment and reporting LT

  18. Concept Operational JC2 Subprogram in the IDE* JLD J2 Int J3 Ops J5 Plans Sit Awareness Plan Task Sit Awareness Plan Sit Awareness Plan Sit Awareness Plan Control Task Task Task JAD Control Control Control Commander Sit Awareness Plan Plan Sit Awareness Task Task Control Control JMD (IMT) Sit Awareness Plan Task Control JIW Sit Awareness Plan Task Control J Mil Health Ops J4 Log J1 Pers J6 CIS J7 Trg & Doctrine J8 Fin J9 SecDef / CIMIC Plan Sit Awareness Task Control JOSS Sit Awareness Sit Awareness Sit Awareness Sit Awareness Sit Awareness Sit Awareness Sit Awareness Plan Plan Plan Plan Plan Plan Plan Task Task Task Task Task Task Task Control Control Control Control Control Control Control

  19. Typical Outputs

  20. Green Point Stadium 2010 SWC National OV 1 Prov JOC ( Polokwane ) Peter Peter Mokoba Mokoba Stadium Stadium BACSS LASS (Pretoria) ( Hoedspruit ) NAT JOC Prov JOC ( Nelspruit ) (Centurion) Royal Bafokeng Stadium Mbombela Mbombela Stadium Stadium Loftus Versfeld Ellispark Stadium Stadium Soccer City Stadium Free State Stadium Prov JOC Kings Park (Bloemfontein) Stadium Prov JOC (Durban) Nelson Mandela Bay Stadium Prov JOC (Cape Town) Prov JOC (Port Eizabeth )

  21. SAPS DF Malan Air Port Civilian Air Fields Prov JOC NAT JOC NIA GREENPOINT EXERCISE OV 1 Centurion Ghost Squadron Ysterplaat Radars/ Sensors Tygerberg Hospital Green Point Stadium Radars/ Sensors

  22. DF Malan Air Port Civilian Air Fields NL4 NL4 1 Provincial Joint Operations Centre (JOC) 9 Ysterplaat 1.10 JOC Commander NL9 SAPS NL8 1.5 Flight Approval NL1 NL18 1.1 J1 Pers (Support) 1.6 J2 Int 1.3 J3 Ops NL7 NL8 1.2 J4 Log 10 AFCP NL1.3 1.4 Flight Authorisation NL10 NL6 11 Mobile Sector Control Centre (MSCC) Int Community Radars/ Sensors DPSS Environment 1.8 GBADS PROVINCIAL JOINT OPERATIONS CENTRE (JOC) OV 2 Greenpoint

  23. Greenpoint System Integration

  24. IDE JC2 Benefits

  25. IDE JC2 BENEFITS • Evaluate operational efficiency. • Optimal management and sequencing of JC2 capability growth. • Ensure specification and adherence to common JC2 system and integration standards (Technical Reference Model - TRM). • Reduction in development cost and time. • Reduction in maintenance cost. • Reduction in training cost. • Utilisation of current facilities and projects. • Utilise and grow with current technologies.

  26. QUESTIONS

More Related