1 / 27

Mr. Alan Hentemann HQDA CIO/G-6, Cybersecurity Directorate,

Army and Joint Interoperability Certification and Coalition Assessment and Validation Requirements TechNet Land Forces South July 2012. Mr. Alan Hentemann HQDA CIO/G-6, Cybersecurity Directorate, System of Systems (SoS) Integration & Interoperability 703-545-1418

xiu
Download Presentation

Mr. Alan Hentemann HQDA CIO/G-6, Cybersecurity Directorate,

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. Army and Joint Interoperability Certification andCoalition Assessment and Validation Requirements TechNet Land Forces SouthJuly 2012 Mr. Alan Hentemann HQDA CIO/G-6, Cybersecurity Directorate, System of Systems (SoS) Integration & Interoperability 703-545-1418 Alan.P.Hentemann.ctr@mail.mil

  2. Agenda • References • HQDA, CIO/G-6, Interoperability Mission • Joint Guidance Transformation • Interoperability Reference Changes • Interoperability Steering Group (ISG) • Change in ISG required documentation • Army Interoperability Certification (AIC) Testing • What is AIC? • AIC Requirements • AIC Determination • Federation of Net-Centric Sites (FaNS) • What is FaNS? • Net-Centric Sites Environment Engagement Theater 1, HQDA CIO/G-6

  3. References DODD 5105.19 DISAshall ensure end-to-end interoperability. DODD 4630.5 IT and NSS interoperability shall be verified early, and with sufficient frequency throughout a system's life … DoD CIO Interim Guidance All IT and NSS must be evaluated and certified for Joint interoperability by DISA(JITC). (To become DoDI 8330.xx) DOD 4630/5000 Interoperability is “the ability to provide and accept data, information, materiel, and services ... ...includes both the technical exchange of information and the end-to-end operational effectiveness of that exchange, as required for mission accomplishment.” CJCSI 6212.01F All IT and NSS must have Joint Staff approved Net Ready – Key Performance Parameter . (No longer IOP & Supportability) DODI 4630.8 All IT and NSS … must be tested for interoperability before fielding ... and certified by DISA (Joint Interoperability Test Command (JITC)). DOD 8000 Series GIG Policy CJCSI 3170.01 Establishes JCIDS w/ NR-KPP for CRD, CDD and CPD. DOD 5000 series For IT systems, including NSS, ... JITCshall provide system interoperability test certification memoranda ... throughout the system life-cycle and regardless of ACAT. Engagement Theater 1, HQDA CIO/G-6

  4. HQDA CIO/G-6 Interoperability Mission To facilitate and ensure Army Net-Centric capabilities by conducting System-of-Systems integration & validation of digital interoperability across all Mission Areas, to include Configuration Management of Certified Baselines, and Software Distribution. Engagement Theater 1, HQDA CIO/G-6

  5. Joint Interoperability Guidance Transformation Overview Engagement Theater 1, HQDA CIO/G-6

  6. Joint Interoperability Considerations Prior to 2012 Since 2012 CJCSI 6212.01F – Net Ready Key Performance Parameter (NR KPP) DoD Memo – Interim Guidance for Interoperability of Information Technology (IT) and National Security Systems (NSS) using DoDD 4630.05 and DoDI 4630.8 DoDI 8330.XX – Interoperability of Information Technology (IT) and National Security Systems (NSS) (Under Development) To incorporate and replace DoDD 4630.05 and DoDI 4630.8 DoD Interoperability Steering Group (ISG) (Interoperability (IOP) Matters Tri-Chair DOD CIO, USD(AT&L), and JS J8 DoD CIO Executive Board (EB) (IOP Policy) • CJCSI 6212.01E – Interoperability and Supportability of Information Techn0ology and National Security Systems • DoDD 4630.05 – Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS) • DoDI 4630.8 – Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS) • USMCEB Interoperability Certification Panel (ICP) (Interoperability (IOP) Matters) • Chair JCS J6 • USMCEB Interoperability Panel (IOP Policy) Engagement Theater 1, HQDA CIO/G-6

  7. Joint Interoperability Considerations (Cont.) Prior to 2012 Since 2012 Interim Certificate to Operate (ICTO) All POR IT/NSS not Joint Certified, urgent need to field and not covered by a JUONS Joint Interoperability Test Waiver Waiver of Policy Operating at Risk List Information Support Plan (ISP) Enhanced ISP Tool Global Information Grid (GIG) Technical Guidance Federation (GTG-F) online portal for ISP review and comment adjudication Service Component and Joint ISP review with Service Component ISP Approval Tailored ISP (TISP) only for legacy programs with no plan for upgrade, non-ACAT programs with limited resources, or programs with near future retirement • Interim Certificate to Operate (ICTO) • All IT/NSS not Joint Certified with urgent need to field • Joint Interoperability Test Exemption • Legacy Waiver (A and B) • Information Technology Watch List • Information Support Plan (ISP) • Enhanced ISP Tool • JCIDS review and comment adjudication • JCS Interoperability and Supportability Certification • Tailored ISP (TISP) for ACAT 2 and below Engagement Theater 1, HQDA CIO/G-6

  8. Interoperability Steering Group (ISG)Interim Certificate To Operate Request (ANNEX D) Section I: Contact Information: • CC/S/A ISG POC: _________________________________________(Refer to the ISG POC list at http://jitc.fhu.disa.mil/cgi/isgsite/poclist.aspx) •  Requesting Organization: _______________________________________ • Program Manager: __________________________________ • Phone (Commercial/DSN) ____________ •  E-Mail Addresses: -- NIPRnet: _________________________________ -- SIPRnet: _________________________________ •  Mailing Address: -- City: _________________________________   -- State: __ -- Zip: ____________ Engagement Theater 1, HQDA CIO/G-6

  9. Interoperability Steering Group (ISG)Interim Certificate To Operate Request (Cont.) Section II: System Information: • Full System Name: _____________________________ • Acronym: _____________________________ • Model/Version: _____________________________ • Provide a short, high level description of what the system is, the function or functions it performs, the level of operation (e.g., tactical, operational, strategic), whether it is intended for single service or Joint usage, and who the system’s customers are._____________________________ • Is the system currently fielded? Yes No (select one) -- If not fielded, what is the estimated fielding date?______________ • What is the impact on program/mission if ICTO is not granted?______________________________________________ REMOVED QUESTIONS ON “CONNECTIONS IAW DODI 8100.3, IA ACTIONS INITIATED TO SUPPORT DSN CONNECTION APPROVAL, AND WHETHER THE SYSTEM IS LEGACY. Section III. Certification Information • Provide a road map on how and when the system plans to complete the Joint Interoperability Certification process.___________________________________ • For systems that do not currently have JS certified requirements documents, please identify all system interfaces that have been assessed by JITC such as a Standard Conformance Certification and/or Interoperability Assessments documents. Include JITC, a matrix diagram of all joint/combined interfaces implemented or planned.Ref to or note attached diagrams: Supplemental Information •   Provide OV-1 and SV-1 diagram •   Summary quad-chart •   For systems, provide a list of all equipment and corresponding software and firmware version numbers of the system, including Joint Interoperability Certification (JIC) status of any component systems (e.g., Voice Grade LAN, VoIP switch) that have JITC certification.  Additional Comments Engagement Theater 1, HQDA CIO/G-6

  10. Program Name and Version (STP#) / Program Manager Name/ JITC AO Name/ ISG Representative Name SYSTEM DESCRIPTION Provide a short, high level description of what the system is, the function(s) it performs, the level of operation (e.g., tactical, operational, strategic), whether it is intended for single service or Joint usage, and who are the system’s customers. ICTO OVERVIEW ICTO Request: __Initial __ Extension Start Date: Expiration Date: Rationale for Request: ICTO History: IOP Certification History: • REQUIREMENTS & TESTING • Requirements derived from: (i.e. ISP, CDD, CPD) • Status of the requirements document: • Date submitted to GTG-F • Where is the document in the review process: • Projected completion date: • Previous Tests and/or Certifications: • SUMMARY • Fielding Date: • ISP Completion Date: • JITC Funding Status: • Projected Joint Testing Start Date(s): • Projected Joint Testing Completion Date: • Projected IOP Certification Date: Engagement Theater 1, HQDA CIO/G-6

  11. Army Interoperability Certification (AIC) Testing Overview Engagement Theater 1, HQDA CIO/G-6

  12. What is AIC? • AIC test process validates: • 1) a system, or groups of systems, successfully performs its digital interoperability and Net-Centric (NC) missions as defined within its interoperability test requirements (mission threads), applicable capabilities or requirements documentation and baselined within its Information Support Plan (ISP); • 2) those systems can securely generate and consume accurate, timely and actionable information/data/services as expected in order to execute specified operational processes; and • 3) a system does not negatively impact the functionality of its expected network environment • * Note- The term ‘System’ encompasses ‘Platforms’, ‘applications’ and ‘services’ and includes the hardware, software and other components. A ‘System’ may be a component of a family-of-systems (FoS) or system-of-systems (SoS). • Bottom Line: The ability of IT/NSS, Units, or Forces to successfully digitally exchange secure and timely data, information, materiel, and services, to enable them to operate effectively and efficiently together, thus achieving information superiority Engagement Theater 1, HQDA CIO/G-6

  13. HQDA CIO/G-6 Policy • CIO/G-6 Policy Signed 28 April 2009: AIC determination is required for all IT/NSS that have a Net-Ready Key Performance Parameter (NR-KPP) and/or have the current capability or requirement to externally generate, utilize, transmit or process Information. All other IT/NSS must attain an AIC Exemption or Waiver, as appropriate. • CJCSI 6212.01E Definition of Interoperability: The ability of systems, units or forces to provide data, information, materiel and services to and accept the same from other systems, units or forces and to use the data, information, materiel and services so exchanged to enable them to operate effectively together. IT and NSS interoperability includes both the technical exchange of information and the operational effectiveness of that exchanged information as required for mission accomplishment. Interoperability is more than just information exchange. It includes systems, processes, procedures, organizations, and missions over the lifecycle and must be balanced with IA. • The USA CIO/G-6 is the AIC Certification Authority (CA) – Title 40 • Test Agent executes AIC on behalf of and under the direction of the USA CIO/G-6 • For MDA/GMD the CTSF will Execute AIC Engagement Theater 1, HQDA CIO/G-6

  14. Overarching AIC Requirements • AIC applies to all Army Information Technology (IT) & National Security Systems (NSS) prior to release to the field, to include: • All Mission Areas/Domains (WMA, BMA, EIEMA, DIMA) • All ACATs • Programs are required to complete the AIC testing process: • Prior to conducting OT events (IOT&E, LUT, LFT&E, etc.) • Prior to or in coordination with Joint Interoperability Certification (JIC) by the Joint Interoperability Test Command (JITC) • Completion of AIC is the way ahead to Joint Interoperability Certification (JIC), either sequentially or in coordination with the JITC, for IT/NSS with Joint interoperability requirements Engagement Theater 1, HQDA CIO/G-6

  15. AIC Determination Options 1 Criteria Through Portfolio Management, conduct analysis of the applicability of Mission Area IT/NSS systems required to undergo the AIC testing process ID Exemption Systems without current or planned interoperability capabilities or requirements Legacy system AIC Test Data FANS-CTSF provides AIC test data to the CIO/G-6 Test Wavier Systems that have Army Interoperability requirements, but cannot currently meet the requirements (i.e., due to the state of the art, requirements blocking, evolutionary acquisition programs, etc.) Categorize Identify type of certification required Determine Test Location(s) CIO/G-6 Disposition Certification Systems that have current interoperability requirements must undergo AIC testing before deployment to the operational User WHERE CERTIFY 3 4 SORT 2 Engagement Theater 1, HQDA CIO/G-6

  16. Federation of Net-Centric Sites(FaNS) Overview Engagement Theater 1, HQDA CIO/G-6

  17. What is FaNS? IS: A federation of existing Army and Joint (when applicable) facilities, network-connected together to execute horizontal integration, AIC testing and Configuration Management ISO applicable Army and Joint Information Technology/National Security Systems (IT/NSS), across all Mission Area’s (MA)/Domains, executed in a predictable and repeatable process. End State: An agile, efficient, flexible and persistent horizontal integration and interoperability testing capability. FANS will allow the Army to grow its integration and interoperability testing capacity, over time, by leveraging existing facilities, both Army and Joint. ADatP-34 Communications Site Criteria MIL-STD 2525 IEEE APFT Event Execution Personnel Information Assurance Standards MIL-SPEC Building codes Configuration Management Ambient air quality Engagement Theater 1, HQDA CIO/G-6

  18. Objective: A federation of existing Army, Joint and Coalition facilities, networked together to execute horizontal and vertical integration, AIC testing and CM ISO applicable Systems IT/NSS, across all Mission Areas/Domains. Net-Centric Sites Environment FaNS Architecture PERSONNEL Battle Command CTSF (TA) WMA SEC MEDCOM COALITION CTE2 The Tactical Logistics Directorate SIL was Accredited on 26 May 2011. 1ST IO COMMAND INSCOM PEO-CGS Warren MI SIM PEO–STRI Orlando Fires Fort Sill, OK AMD Huntsville Fort Bliss/ WSMR FT HOOD JITC Aviation Huntsville, AL FT Belvoir TBD SPAWAR LOGISTICS FT HUACHUCA MCTSSA FINANCIAL TIC EGLIN AFB APC OHIO FT HUACHUCA The Camp Pendleton MCTSSA facility was Accredited on 22 May 2012. The San Diego Enterprise Engineering and Certification (E2C) facility was Accredited on 22 May 2012. (BA Domain) BMA EIEMA JOINT HQDA FaNS Accredited site DIMA Sites in one of the four phases of accreditation. Other Mission Areas report to ACMO for baseline Engagement Theater 1, HQDA CIO/G-6

  19. CONUS FaNS Capability Nodes PEO Ground Combat Warren MICH WPAFB SIMAF / Agile Fires Nellis / AFB Agile Fires APG NAS Patuxent River / Agile Fires INSCOM (Intel) Fort Lee SPAWAR Systems Center, Charleston. MCTSSA / Camp Pendleton SPAWAR Systems Center San Diego Eglin AFB 46th Test Squadron JITC (Joint) ISEC TIC (Infrastructure) PEO STRI(SIM/STIM) CTSF (TBC) Fort Hood Redstone AVN/SMDC APTU (FIRES) Ft. Sill Knox Hall / I-SEE-O-Hall Ft. Bliss/WSMR (FCS) States with FaNS activities Army and JOINT Projected FaNS location JOINT Projected FaNS location Army Current FaNS location Engagement Theater 1, HQDA CIO/G-6

  20. Key AIC/FaNS Take-Aways • CIO/G-6 is Decision Authority for AIC • Test Agent, ICW FaNS, executes AIC on behalf on CIO/G-6 • AIC technically validates the end-to-end flow of information/data • through an operationally representative architecture in a system • of systems environment • We continue to streamline interoperability testing through • partnerships with Joint, DoD and Federal Agencies through • the FaNS Environment Engagement Theater 1, HQDA CIO/G-6

  21. Contact Information Mr. Steven M. Roscoe HQDA CIO/G-6, Cybersecurity Directorate Director; Interoperability, Acquisition and Certification Division Bldg 220, Fort Belvoir, VA (703) 545-1410, DSN: 865-1410 Steven.M.Roscoe2.civ@mail.mil Ms. Jacqueline Zachgo HQDA CIO/G-6, Cybersecurity Directorate Branch Chief; Joint Interoperability and Configuration Management Fort Belvoir, VA (703) 545-1583, DSN: 865-1583 Jacqueline.D.Zachgo.civ@mail.mil Mr. Alan Hentemann HQDA, CIO/G-6, Cybersecurity Directorate Acting Branch Chief; Army Interoperability Certification Fort Belvoir, VA (703) 545-1418, DSN: 865-1418 Alan.P.Hentemann.ctr@mail.mil Mr. David Brumlow HQDA CIO/G-6, Cybersecurity Directorate Liaison Officer (CTSF) / FaNS Coordinator (254) 624-5091 David.G.Brumlow.ctr@mail.mil Engagement Theater 1, HQDA CIO/G-6

  22. Questions Engagement Theater 1, HQDA CIO/G-6

  23. Backups • AIC Test Process & CM AICFB Process • Framework for Army Interoperability Testing • The Integrated Architecture • Program / System Specific Processes Engagement Theater 1, HQDA CIO/G-6

  24. The CIO/G-6 AIC Test Process & CM AICFB Process • AIC certification • Fielding authorization to operational • environment • Materiel Release authorization • Continued Congressional funding • Meets OT/JITC entrance criteria • Supports JTIC Certification Title 40 Products (Output) Title 10 Integration Activities (I2E) SoS ASA (ALT) MATDEV SW Execution Phase Begins Software Under Test CM controlled by ANCMO & executed by ACMO Qtrly BL Rel TTP Validation Change Control managed by Test Agent Baseline Established (G-6) AIC Test (G-6) Test Floor Established (G-6) Backwards Compatibility and Interoperability Testing (G-6) SW/HW Dev (MATDEV) PEO RRT (MATDEVs) IA SoS NVA Entrance Criteria Fielded Software CM under ANCMO control [Software Baseline Change Process Compliance Required] • PM’s AIC Request Memo • Approved ISP • Approved Test Requirements • Funding in Place • IATO/ATO documentation • SUT delivered to Test Agent CM • System Begins IA Scan Process • Systems loaded, config’d & IAVA’s applied • Systems Pass IA Scans • Systems Probed by Test Agent CM • Configuration Control Board (CCB) Verified during the CRR Create & Distribute Baseline Products (G-6) Golden Bricks Approved SW Fielded (MATDEVs/LCMCs) CM Audit of Fielded Software (G6/LCMC) [MaintainsBaseline] Step 1 – Conduct AIC Event Using CTSF and FaNS Test Facilities Engagement Theater 1, HQDA CIO/G-6

  25. Framework for Army Interoperability Testing Entrance Criteria Software Interoperability Testing Architecture Network/Comms Configuration Management Configuration Management Interdependencies Threads PCRs Test Incident Reports DAG ESC Test Schedule CCB/TRR/CRR Subject Matter Experts Learning Curve Technical Expertise Engagement Theater 1, HQDA CIO/G-6

  26. Basic Process Outline for Capability Based Thread Analysis • Start with Desired Operational Capability from the user community • Use baseline architecture (Use Enterprise Approach for ERP Programs.) • Leverage an integrated architecture process that will use the baseline models to deliver the customer desired information sets • Refine and Specialize the required products (as specified in AV1) • Develop OV6c from applied models and associated SV10c product information (ERP Programs Deviation) • Run OV6c and SV10c thru AIMD GOTS application to create an integrated test thread to customer specs (This step is an iterative cycle of Community Review and Architecture Update) • Deliver to CTSF --- Test Threads in CM Status; ‘Sponsor’ of Block responsible for CM until AIC Cert complete ORG UNIT Node The Integrated Architecture Foundational Project Specific Application TV-1 “A Structured Approach” ERP Deviation Feedback / Results Enterprise Approach Warfighting Community Tailored Test Thread to FaNS Specs (Loads StarGen) ISP OV-6c Capability List Developed by the Requirements and Architecture Working Group (RAWG) with the help of the DCD/ TSM 5 7 CADIE Project: SWB III 3 4 2 6 SV-10c OV-3 CTSF OV-5’s Collaborative project between AIMD, NetOps, and ASEO using CADIE portal and tool sets with a common data set. PEO/ PM Community 1 CM OV-4 Scenarios & Test Cases Warfighting Community Modular Force Baseline Models Validated Modular Force Operational Architecture provided the base models to begin the architecture effort. SV-5 SV-4 Engagement Theater 1, HQDA CIO/G-6

  27. FIRE SUPPORT Step 2 – Process Mission. Step 3 – Process Mission to Firing Unit Step 1 - Initiate Call for Fire from an Aerial Observer Step 6 – Receive Message from Fires BN Step 8 – Receive Shot Step 10 – Receive Splash Step 12 – Receive Rounds Complete Step 13 – Send End of Mission GIG Interface GIG Interface SEC at Fort Monmouth, NJ BCT CTSF at Fort Hood, TX Fires BDE SED at Huntsville, AL AV BDE X Fort sill, OK Fires BN/Guns Step 4 – Conduct Firing of the Mission. Step 5 – Send Message to Observer Step 7 – Send Shot Step 9 – Send Splash Step 11 – Send Rounds Complete Step 14 – Receive End of Mission COP Engagement Theater 1, HQDA CIO/G-6 27

More Related