Bidders Library Interoperability Test and Evaluation - Joint IOP Cert Template.docx

Joint Interoperability Certification Template v 1.0

IN REPLY

REFER TO:

Joint Interoperability Test Command (Choose an office code) dd mmm yyyy

JOINT INTEROPERABILITY CERTIFICATION FOR DISTRIBUTION

SUBJECT: Joint Interoperability Certification of the Program name, System name, JETDS designator Version System version ID

References: (a) Name of requirement document containing JS certified NR KPP and approved architecture information (CPD, CDD in lieu of CPD, or ISP).

(b) Department of Defense Instruction (DoDI) 8330.01, “Interoperability of Information Technology (IT), Including National Security Systems (NSS),” 21 May 2014

(c) through (last reference), see Enclosure 1

1. (Certification with conditions) Certification and Conditions. The System name Version System version ID partially fulfills the interoperability requirements of the Joint Staff-certified Net-Ready Key Performance Parameter (NR KPP) and approved architecture viewpoints contained in Reference (a). The Joint Interoperability Test Command (JITC) certifies System name with conditions described in Table 1. The certification is based on performing all / X of Y joint critical tasks specified in Reference (a). This certification expires upon changes that affect interoperability or no later than 4 years from the date of this memorandum.

Table 1. Conditions

Choose a status

Choose a status

Choose a status

NOTES:

1. Additional test and evaluation is required to remove conditions.

2. ‘Major’ operational impact: A discrepancy or risk that adversely affects an operational or mission-essential capability and an acceptable work-around does not exist.

3. ‘Moderate’ operational impact: A discrepancy or risk that causes a ‘Major’ operational impact if the IT/NSS is deployed and used as designed; however, a mitigating circumstance or acceptable work-around DOES EXIST to reduce the impact (or mitigate risk).

LEGEND:

1. (Certification with no conditions) Certification. The System name Version (System version ID) fulfills/partially fulfills the interoperability requirements of the Joint Staff-certified Net-Ready Key Performance Parameter (NR KPP) and approved architecture viewpoints contained in Reference (a). The Joint Interoperability Test Command (JITC) certifies System name based on performing all / X of Y joint critical tasks specified in Reference (a). This certification expires upon changes that affect interoperability or no later than 4 years from the date of this memorandum.

2. NR KPP Compliance. Table 2 provides the overall NR KPP compliance status.

Table 2. NR KPP Compliance Status

Mission Statement

NOTES:

1. Joint Mission Critical Net Ready Operational Tasks.

2. Attribute Status. Satisfied when all measures related to the NR KPP attribute ‘Met’ their respective threshold criteria.

3. Overall NR KPP Status. Fulfilled when ALL attributes for ALL joint critical tasks have the status of ‘Satisfied’.

LEGEND:

3. Test Details. JITC based this certification on an interoperability evaluation (or name the type of test such as a LUT or OT&E we participated in with other testers) conducted by testers at location(s) from test date to test date. List significant post-test activities along with the completed on (date). (Create a table if needed. Include any other information that is necessary to understand the certification.) Enclosure 2 describes the operational architecture, configurations used during testing, and presents a summary of requirements, results and analysis. Enclosure 3 documents test results in tabular form. The user must verify system interoperability before deployment in an operational environment that varies significantly from the test environment. Additional test and evaluation is needed to clear the Conditions listed in Table 1.

4. Certification Authority. Reference (b) establishes the JITC as the DoD's Joint Interoperability Certification Authority. Reference (c) provides interoperability process guidance, while Reference (d) defines the NR KPP.

5. Additional Information. JITC distributes interoperability information via the JITC Electronic Report Distribution (ERD) system. Interoperability status is available via the JITC System Tracking Program (STP). The STP is accessible by STP account holders at https://stp.fhu.disa.mil/.

6. Point of Contact (POC). The JITC POC is Name; Commercial telephone (xxx) xxx-xxxx;

DSN telephone (xxx) xxx-xxxx; E-mail address firstname.mi.lastname.civ@mail.mil; Mailing address: Joint Interoperability Test Command, ATTN: Choose an office code. Choose an address.

FOR THE COMMANDER:

Distribution (electronic mail):

DoD CIO Joint Staff J-6, JCS

USD(AT&L)

ISG Secretariat, DISA, JT U.S. Strategic Command, J665 US Navy, OPNAV N2/N6FP12 US Army, DA-OSA, CIO/G-6 ASA(ALT), SAIS-IOQ US Air Force, SAF/CIO A6XA US Marine Corps, MARCORSYSCOM, SIAT, A&CE Division US Coast Guard, CG-64

DISA/ISG REP

DIA, Office of the Acquisition Executive NSG Interoperability Assessment Team DOT&E, Netcentric Systems and Naval Warfare Medical Health Systems, JMIS PEO T&IVV COCOMs Program Manager for Program, System Other addressees as requested by the program ERD/STP code

This page intentionally left blank.

JITC Cert, Choose an office code., Joint Interoperability Certification of the Program name System name JETDS designator Version System version ID

ADDITIONAL REFERENCES

(c) Joint Interoperability Test Command, “Interoperability Process Guide,” Version 2.0, 23 March 2015

(d) Chairman of the Joint Chiefs of Staff, “Manual for the Operation of the Joint Capabilities Integration and Development System (JCIDS),” 12 February 2015, including errata as of 18 December 2015

(e) JS NR KPP Certification Memorandum

(f) Others as required

Enclosure 1

1-2

CERTIFICATION SUMMARY

1. SYSTEM AND REQUIREMENTS IDENTIFICATION. Table 2-1 presents the system’s identifying information and requirements sources.

Table 2-1. System and Requirements Identification

System Identification

Increment and/or Version

System Background

Milestone/Decision supported

Previous certifications

Tracking

System Tracking Program ID

DITPR ID

Requirements Source

WMA, DARS legacy, or other Service source

Remarks

NOTES: Edit as appropriate 1.

2.

LEGEND: Edit as appropriate

2. SYSTEM DESCRIPTION. A brief, high-level description of the SUT’s mission(s) and required functions.

3. OPERATIONAL ARCHITECTURE. Diagram and text of how the SUT fits into its operational architecture. Use an OV-2 or SV-1 if appropriate. See the certification template instructions for more details.

4. SYSTEM CONFIGURATION. Table 2-2 identifies the hardware, software, and firmware versions.

Table 2-2. Hardware/Software/Firmware Versions

NOTE(S): Edit as appropriate

2.

LEGEND:

5. TEST CONFIGURATION. Provide a diagram and text of the test architecture and identify significant differences from the operational architecture (deltas that result in a test limitation or deviation from the test plan that are addressed in paragraph 9 below). Address the cybersecurity (formerly IA) architecture. It must show the SUT, and reflect its interfacing operational nodes and needlines. Include any test equipment used during the test. MUST SHOW THE TEST CONFIGURATION WE USED TO EVALUATE THE SUT. See the certification template instructions for more details.

6. METHODOLOGY. See the certification template instructions for more details.

1. Support Military Operations. Describe the methodology used to evaluate Attribute 1 measures.

2. Enter and Be Managed on the Network. Describe the methodology used to evaluate Attribute 2 measures.

3. Effective Information Exchanges. Describe the methodology used to evaluate Attribute 3 measures.

7. INTEROPERABILITY REQUIREMENTS, RESULTS, AND ANALYSIS

1. Requirements and Results. Table 2-3 summarizes the results for each joint critical task supporting (State the mission here) as described in paragraph 2. The results are presented as a ratio of [(the number of measures of performance (MOPs) ‘Met’)/(the total number of MOPs)]. (If the SUT has multiple missions, add another grouping of paragraphs and a table to encompass the discussion of requirements, results, and analysis associated with each mission. See the template instructions for more details)

Table 2-3. Joint Critical Task Results for Mission #

to the certification

X/Y

LEGEND: Edit as appropriate

2. Analysis. (This section addresses the MOPs ‘Not Met’ or ‘Not Tested’ as indicated by Table 2-3, and describes the analysis used to arrive at that result along with the operational impact and risk. See the template instructions for more details.)

3. Summary Report Data Tables. Enclosure 3 contains the data tables generated for this evaluation. Refer to these tables for the details of the NR KPP Attributes, specific interfaces, and standards/specifications.

8. TEST LIMITATIONS AND DEVIATIONS. Test limitations (anticipated) and deviations (unanticipated) are constraints to testing that may affect the interpretation of the results or the ability to evaluate joint interoperability. Identify any testing limitations or deviations that may affect the interpretation of the results, including use and status of authorized cybersecurity configurations. Provide an assessment of the effect of these limitations and deviations on the ability to evaluate joint interoperability. For any test deviation, provide a recommendation for mitigating the impact. Additional testing may be warranted in cases where the operational architecture is incomplete or numerous configurations are possible. It is appropriate to recommend verifying the interoperability of untested configurations.

9. CONCLUSIONS. (Relate it to the purpose of the joint interoperability test and evaluation. DO NOT use the term ‘full certification’)

The SUT fulfills/partially fulfills the NR KPP and is certified for joint interoperability/certified for joint interoperability with conditions.

OR for a Denial of Certification, The SUT partially fulfills/does not fulfill the NR KPP and certification of SUT is denied.

Enclosure 2 2-4

Certification Summary Data Tables

Table 3-1. Support Military Operations (Attribute 1)

Status Remarks

M1 Mission Name MOE Measure Statement from

NR KPP

T = value

Choose a status

T1 Task Name MOP Measure Statement from

NR KPP

Choose a status

T2

MOP Measure Statement from

NR KPP

Choose a status

T#

MOP Measure Statement from

NR KPP

T = value

Choose a status

M# Mission Name MOE Measure Statement from

NR KPP

Choose a status

T1

MOP Measure Statement from

NR KPP

Choose a status

T2

MOP Measure Statement from

NR KPP

Choose a status

T#

MOP Measure Statement from

NR KPP

T = value

Choose a status

LEGEND:

Enclosure 3 Enclosure 3 3-6

Table 3-2. Enter and Be Managed on the Network (Attribute 2)

Status Remarks

N1 Network Name

MOP Measure Statement from

NR KPP

Choose a status

MOP Measure Statement from

NR KPP

Choose a status

MOP Measure Statement from

Choose a status

MOP Measure Statement from

T = value

Choose a status

N# Network Name

MOP Measure Statement from

NR KPP

Choose a status

MOP Measure Statement from

Choose a status

MOP Measure Statement from

Choose a status

MOP Measure Statement from

T = value

Choose a status

LEGEND:

Enclosure 3 3-5

Table 3-3. Effectively Exchange Information (Attribute 3)

Status Remarks

IE1. IE Name

MOP Measure Statement from NR KPP

Choose a status

IE2. IE Name

MOP Measure Statement from NR KPP

Choose a status

IE3. IE Name

MOP Measure Statement from NR KPP

Choose a status

IE4. IE Name

MOP Measure Statement from NR KPP

Choose a status

IE#. IE Name

MOP Measure Statement from NR KPP

Choose a status

LEGEND:

Table 3-4. Joint Interface Details

I1. Interface Name

Choose a status

I2. Interface Name

Choose a status

I#. Interface Name

Choose a status

LEGEND:

Table 3-5. Key Technical Deficiencies

LEGEND:

image1.jpeg