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

TechNet Land Forces South 2012CONNECTING JOINT & COALITION PARTNERS FOR THE NEXT FIGHT UNCLASSIFIED

UNCLASSIFIED

Army and Joint Interoperability Certification andCoalition Assessment and Validation Requirements

TechNet Land Forces South

July 2012

Mr. Alan HentemannHQDA CIO/G-6, Cybersecurity Directorate,

System of Systems (SoS) Integration & Interoperability703-545-1418

[email protected]


UNCLASSIFIEDEngagement Theater 1, HQDA CIO/G-6 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

7/11/2012 // Interoperability Certification/Validation Requirements



References


DODI 4630.8All IT and NSS … must be tested for interoperability

before fielding ... and certified by DISA (Joint

Interoperability Test Command (JITC)).

DODD 4630.5IT and NSS interoperability shall be verified early, and with sufficient frequency

throughout a system's life …

DOD 8000 SeriesGIG Policy

DODD 5105.19

DISA shall ensureend-to-end

interoperability.

CJCSI 3170.01Establishes JCIDS w/ NR-

KPP for CRD, CDD and CPD.

DOD 5000 seriesFor IT systems, including NSS, ...

JITC shall provide system interoperability test certification memoranda ... throughout the

system life-cycle and regardless of ACAT.

CJCSI 6212.01FAll IT and NSS must have Joint Staff approved Net Ready – Key Performance Parameter .

(No longer IOP & Supportability)

DOD 4630/5000

DoD CIO Interim GuidanceAll IT and NSS must be

evaluated and certified for Joint interoperability by DISA (JITC).

(To become DoDI 8330.xx)

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.”



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.

http://www.wmin.ac.uk/ielts/images/globe_background.jpg


UNCLASSIFIED 5

Joint Interoperability Guidance Transformation

Overview

7/11/2012 // Interoperability Certification/Validation Requirements Engagement Theater 1, HQDA CIO/G-6


UNCLASSIFIED

Joint Interoperability Considerations

Prior to 2012 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)

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)



UNCLASSIFIED

Joint Interoperability Considerations (Cont.)

Prior to 2012 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

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



UNCLASSIFIED

Interoperability Steering Group (ISG)Interim Certificate To Operate Request

(ANNEX D)Section I: Contact Information: 1. CC/S/A ISG POC: _________________________________________

(Refer to the ISG POC list at http://jitc.fhu.disa.mil/cgi/isgsite/poclist.aspx)2. Requesting Organization: _______________________________________3. Program Manager: __________________________________4. Phone (Commercial/DSN) ____________5. E-Mail Addresses:

-- NIPRnet: _________________________________-- SIPRnet: _________________________________

6. Mailing Address:-- City: _________________________________

-- State: __-- Zip: ____________


http://jitc.fhu.disa.mil/cgi/isgsite/poclist.aspx


UNCLASSIFIED

Interoperability Steering Group (ISG)Interim Certificate To Operate Request (Cont.)

Section II: System Information:1. Full System Name: _____________________________2. Acronym: _____________________________3. Model/Version: _____________________________4. 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._____________________________

5. Is the system currently fielded? Yes No (select one)-- If not fielded, what is the estimated fielding date?______________

6. 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

7. Provide a road map on how and when the system plans to complete the Joint Interoperability Certification process.___________________________________

8. 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




Program Name and Version (STP#) / Program Manager Name/ JITC AO Name/ ISG Representative Name


SUMMARY– Fielding Date:

– ISP Completion Date:

– JITC Funding Status:

– Projected Joint Testing Start Date(s):

– Projected Joint Testing Completion Date:

– Projected IOP Certification Date:

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:

ICTO OVERVIEWICTO Request: __ Initial __ Extension

Start Date: Expiration Date:

Rationale for Request:

ICTO History:

IOP Certification History:

SYSTEM DESCRIPTIONProvide 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.


UNCLASSIFIED 11

Army Interoperability Certification (AIC) Testing

Overview




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



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



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




AIC Determination Options


CriteriaThrough Portfolio Management,

conduct analysis of the applicability of Mission Area IT/NSS systems required to

undergo the AIC testing process

Categorize

Identify type of certification required

ExemptionSystems without current

or planned interoperability capabilities

or requirementsLegacy system

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.)

CertificationSystems that have current

interoperability requirements must undergo AIC

testing before deployment tothe operational User

AIC Test DataFANS-CTSF provides AICtest data to the CIO/G-6

CIO/G-6 DispositionDetermine

TestLocation(s)

Test

ID

SORT

WHERE

4

1

2

CERTIFY3


UNCLASSIFIED 16

Federation of Net-Centric Sites(FaNS)Overview



UNCLASSIFIED

APFTMIL-STD 2525

MIL-SPECIEEE

AMBIENT AIR QUALITY

ADatP-34

STANDARDSConfiguration Management

Information Assurance

Site CriteriaEvent Execution Personnel

Communications

Building codes

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.

7/11/2012 // Interoperability Certification/Validation Requirements 17Engagement Theater 1, HQDA CIO/G-6

http://ep.yimg.com/ca/I/priorservice_2156_224126110

http://www.google.com/imgres?imgurl=http://www.clipartheaven.com/clipart/occupations/cartoons_(a_-_l)/construction_worker_1.gif&imgrefurl=http://www.clipartheaven.com/show/clipart/occupations/cartoons_(a_-_l)/construction_worker_1-gif.html&h=588&w=351&sz=10&tbnid=q3L46gBI0oCAUM:&tbnh=135&tbnw=81&prev=/search?q=clip+art+construction+worker&tbm=isch&tbo=u&zoom=1&q=clip+art+construction+worker&hl=en&usg=__h6AkxPYR0U3jtlbvRTgMyTHfQgg=&sa=X&ei=bVTuTYnqA5P1gAfx3dCUDw&ved=0CCQQ9QEwBQ


UNCLASSIFIED

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.

HQDA FaNS Accredited site

Battle CommandCTSF (TA)

WMA

SIMPEO–STRI

Orlando

AviationHuntsville,

AL

FiresFort Sill,

OK

PEO-CGSWarren

MIFort Bliss/

WSMR

AMDHuntsville

DIMA

INSCOM

FT HOOD

FT HUACHUCA

1ST IOCOMMAND

SPAWARJITC

EGLIN AFB

JOINT

TBD

EIEMA

FT HUACHUCA

APCOHIO

FT Belvoir

FINANCIALLOGISTICS

BMA

SEC

MEDCOM

MCTSSA

(BA Domain)

COALITION CTE2 The Tactical Logistics

Directorate SIL was Accredited on 26 May

2011.

TIC

Sites in one of the four phases of accreditation.

Other Mission Areas report to ACMO for baseline

PERSONNEL

The San Diego Enterprise Engineering and Certification (E2C) facility was Accredited

on 22 May 2012.

The Camp Pendleton MCTSSA facility was

Accredited on 22 May 2012.

Net-Centric Sites EnvironmentFaNS

Architecture

7/11/2012 // Interoperability Certification/Validation Requirements Engagement Theater 1, HQDA CIO/G-6 18

http://upload.wikimedia.org/wikipedia/commons/6/69/USAF_logo.png

http://upload.wikimedia.org/wikipedia/commons/7/7c/MCTSSA_Logo.gif


UNCLASSIFIED

SPAWAR Systems Center, Charleston.

INSCOM(Intel)

APG

PEO Ground CombatWarren MICH

JITC(Joint)ISEC TIC(Infrastructure)

PEOSTRI(SIM/STIM)

Eglin AFB46th Test Squadron

RedstoneAVN/SMDCAPTU(FIRES) Ft. Sill

Knox Hall / I-SEE-O-Hall

CTSF(TBC)Fort HoodFt. Bliss/WSMR

(FCS)

Fort Lee

WPAFB SIMAF / Agile Fires

Nellis / AFB Agile Fires

NAS Patuxent River / Agile Fires

SPAWAR Systems Center San Diego

MCTSSA / Camp Pendleton

Projected FaNS location JOINTCurrent FaNS location

Projected FaNS location ArmyStates with FaNS activities Army and JOINT

CONUS FaNS Capability Nodes





http://www.navy.mil/

http://upload.wikimedia.org/wikipedia/commons/7/7c/MCTSSA_Logo.gif

http://www.navy.mil/

http://commons.wikimedia.org/wiki/File:US-MarineCorps-Seal.svg



UNCLASSIFIED

Key AIC/FaNS Take-Aways

20

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



UNCLASSIFIED

Contact Information

21

Mr. David BrumlowHQDA CIO/G-6, Cybersecurity DirectorateLiaison Officer (CTSF) / FaNS Coordinator(254) [email protected]

Mr. Steven M. RoscoeHQDA CIO/G-6, Cybersecurity DirectorateDirector; Interoperability, Acquisition and Certification DivisionBldg 220, Fort Belvoir, VA(703) 545-1410, DSN: [email protected]

Ms. Jacqueline ZachgoHQDA CIO/G-6, Cybersecurity DirectorateBranch Chief; Joint Interoperability and Configuration Management Fort Belvoir, VA(703) 545-1583, DSN: [email protected]

Mr. Alan HentemannHQDA, CIO/G-6, Cybersecurity DirectorateActing Branch Chief; Army Interoperability CertificationFort Belvoir, VA(703) 545-1418, DSN: [email protected]



UNCLASSIFIED7/11/2012 // Interoperability Certification/Validation Requirements Engagement Theater 1, HQDA CIO/G-6 22

Questions


UNCLASSIFIED

Backups

AIC Test Process & CM AICFB Process Framework for Army Interoperability Testing The Integrated Architecture Program / System Specific Processes




SW Execution PhaseBegins

SW/HW Dev(MATDEV)

PEO RRT(MATDEVs)

Create & DistributeBaseline Products

(G-6)Golden Bricks

AIC Test(G-6)

CM Auditof Fielded Software

(G6/LCMC)

Software Under Test CM controlled by ANCMO & executed by ACMO

Change Control managed by Test Agent

Baseline Established

(G-6)

Fielded Software CM under ANCMO control[Software Baseline Change Process Compliance Required]

Approved SWFielded

(MATDEVs/LCMCs)

Test FloorEstablished

(G-6)

• AIC certification• Fielding authorization to operational

environment• Materiel Release authorization• Continued Congressional funding• Meets OT/JITC entrance criteria• Supports JTIC Certification

• 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)

Entrance Criteria

Products (Output)

[Maintains Baseline]

Title 10 Title 40

Backwards Compatibility and Interoperability

Testing (G-6)

IntegrationActivities

(I2E)

SoS

ASA (ALT)MATDEV

IA SoS NVA

Qtrly BL RelTTP

Validation

Verif

ied

durin

g th

e C

RR

Step 1 – Conduct AIC Event Using CTSF and FaNS Test Facilities

The CIO/G-6 AIC Test Process & CM AICFB Process




Framework for Army Interoperability Testing


Interoperability Testing

Learning Curve

Technical Expertise

DAG ESC

Entrance Criteria

Software

Threads

Architecture

Network/Comms

Subject Matter Experts

Test Incident Reports Test Schedule CCB/TRR/CRR

PCRs

Inte

rdep

ende

ncie

s

Confi

gura

tion

Man

agem

ent

Confi

gura

tion

Man

agem

ent



The Integrated Architecture


Capability ListDeveloped by the Requirements and Architecture Working Group (RAWG) with the help of the DCD/ TSM

Modular Force Baseline Models

Validated Modular Force Operational Architecture provided the base models to begin the architecture effort.

CADIE Project:SWB III

OV-6c

SV-10cCollaborative project between AIMD, NetOps, and ASEO using CADIE portal and tool sets with a common data set.

Tailored Test Thread to FaNS Specs

(Loads StarGen)

CTSF

1. Start with Desired Operational Capability from the user community2. Use baseline architecture (Use Enterprise Approach for ERP Programs.)3. Leverage an integrated architecture process that will use the baseline models to deliver the customer desired information sets4. Refine and Specialize the required products (as specified in AV1)5. Develop OV6c from applied models and associated SV10c product information (ERP Programs Deviation)6. 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)7. Deliver to CTSF --- Test Threads in CM Status; ‘Sponsor’ of Block responsible for CM until AIC Cert complete

Basic Process Outline for Capability Based Thread Analysis

OV-5’s

Foundational Project Specific Application

ORG UNIT

Node

CMOV-4

Warfighting Community

Warfighting Community

PEO/ PM Community

OV-3

SV-5

SV-4

Feedback / ResultsTV-1

ISP

Scenarios&

Test Cases

“A Structured Approach” ERP Deviation

EnterpriseApproach

1

2 3 4 56

7


UNCLASSIFIED 27

FIRE SUPPORT

X

COP

GIGInterface

GIGInterface

Step 4 – Conduct Firing of the Mission.Step 5 – Send Message to ObserverStep 7 – Send ShotStep 9 – Send SplashStep 11 – Send Rounds CompleteStep 14 – Receive End of Mission

Step 3 – Process Mission to Firing Unit Step 2 – Process Mission.

SEC at Fort Monmouth, NJBCT

CTSF at Fort Hood, TXFires BDE

Fort sill, OKFires BN/Guns

Step 1 - Initiate Call for Fire from an Aerial ObserverStep 6 – Receive Message from Fires BNStep 8 – Receive ShotStep 10 – Receive SplashStep 12 – Receive Rounds CompleteStep 13 – Send End of Mission

SED at Huntsville, ALAV BDE


Documents

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