MISTE_TNM_DO_DRAFT_SOW_PSN.PDF

SOW-2018-055

V1.0, 1 November 2018

DISTRIBUTION STATEMENT A. Approved for public release.

Table of Contents

1. Scope

1.1 Background

2. Applicable Documents

2.1 DOD Specifications

2.2 DOD Standards

2.3 Availability of DOD Standards

2.4 Non-DOD Standards

2.5 Department of Defense Instructions (DoDIs)

2.6 Availability of DoDIs

2.7 Department of Defense Directives

2.8 Other Government Documents, Drawings, and Publications

2.9 Availability of Other Government Documents and Publications

3. Requirements

3.1 General

3.2 Program Management

3.2.1 Integrated Master Schedule (IMS)

3.2.2 Financial Management

3.2.3 Risk Management

3.2.4 Management/Technical Reviews

3.2.4.1 Start of Work Meeting / System Requirement Workshop

3.2.4.2 Site Surveys of Existing EPG Test Network

3.2.4.3 Program Management Reviews

3.2.4.4 Technical Interchange Meetings (TIMs)

3.2.5 Building Facility Infrastructure (HVAC and Electrical Power)

3.3 Risk Management Framework (RMF) Process

3.4 Systems Engineering

3.4.1 Preliminary Network Planning and Design Stage

3.4.2 Detailed Network Design Stage

3.4.3 CHESS Requirement for Hardware/Software Procurement

3.4.4 Requirements Validation

3.4.5 Design Reviews

3.4.5.1 Systems Requirements Review (SRR)

3.4.5.2 Preliminary Design Review (PDR)

3.4.5.3 Critical Design Review

3.4.6 Product Definition Data (PDD)

3.4.7 Anti-Terrorism (AT) Level 1 Awareness Training

3.4.8 Access and General Protection/Security Policy and Procedures. . 12

3.4.9 Threat Awareness and Reporting Program (TARP)

3.4.10 iWATCH Training

3.4.11 OPSEC (Operational Security) Awareness Training

DISTRIBUTION STATEMENT A. Approved for public release.

3.5 Integrated Testing

3.5.1 Integration Readiness Review (IRR)

3.5.2 Test Readiness Review (TRR)

3.5.3 Government Site Acceptance Test and TISN-EN Test Network

Verification Review (TNVR)

3.6 Site Activation

3.6.1 Installation Tools and Test Equipment

3.6.2 Installation Spares

3.7 Training Requirements

3.7.1 Training

3.8 Logistics Requirements

3.8.1 Spare Parts

3.8.2 Equipment Obsolescence Plan

3.8.3 Material Requirements

3.8.3.1 Item Unique Identification (IUID) of Tangible Items

3.8.4 Commercial Off-The-Shelve (COTS) Manuals

APPENDIX A – Design Review Entry and Exit Design Criteria and Data Products ..... A-1 A.1 SRR Entry Criteria ........................................................................ A-1 A.2 Exit Criteria shall include: ............................................................. A-1 A.3 SRR Products .............................................................................. A-2 A.4 PDR Entry Criteria ........................................................................ A-3 A.5 PDR Completion/Exit Criteria ....................................................... A-3 A.6 PDR Products .............................................................................. A-4 A.7 CDR Entry Criteria ....................................................................... A-5 A.8 CDR Completion/Exit Criteria ....................................................... A-6 A.9 CDR Products .............................................................................. A-6 A.10 IRR Entry Criteria ......................................................................... A-7 A.11 IRR Entry Criteria ......................................................................... A-7 A.12 IRR Completion/Exit Criteria ........................................................ A-7 A.13 IRR Products ................................................................................ A-8 A.14 TRR Entry Criteria ........................................................................ A-8 A.15 TRR Completion/Exit Criteria ....................................................... A-8 A.16 TRR Products............................................................................... A-9 A.17 TNVR Entry Criteria ..................................................................... A-9 A.18 TNVR Entry Criteria ..................................................................... A-9 A.19 TNVR Completion/Exit Criteria ..................................................... A-9 A.20 TNVR Products ............................................................................ A-9 APPENDIX B – Acronyms .......................................................................................... B-10

STATEMENT OF WORK

FOR

MODERNIZING INSTRUMENTATION SOLUTIONS FOR TEST AND EVALUATION

(MISTE)

Delivery Order: 0002

ELECTRONIC PROVING GROUND (EPG) TEST NETWORK MODERNIZATION

1. SCOPE.

This Statement of Work (SOW) defines the effort required for designing, procuring, installing, integrating, testing, managing, documenting, training and delivering a Test Network at Electronic Proving Grounds (EPG) in Ft. Huachuca, AZ in support of Testing Instrumentation for the US Army Test and Evaluation Command (ATEC).

1.1 Background.

The U.S. Army Program Executive Office for Simulation, Training and Instrumentation (PEO STRI), Project Manager for Instrumentation, Targets, Threat Simulators and SOF Training Systems (PM ITTS), Instrumentation Management Office (IMO) has a requirement from the U.S. Army Test and Evaluation Command (ATEC), to modernize the Test Instrumentation Networks at all of its test centers as part of the Test Network Modernization Program to support current and future Department of Defense (DoD) customers. The goal of the overarching TNM Program is to establish an enterprise environment for commonality, interchangeability, and interoperability via an approach that will standardize architecture, configuration, hardware and network management tools across ATEC test centers.

2. APPLICABLE DOCUMENTS.

The following documents of issue form a part of this SOW to the extent specified herein.

In the event of a conflict between documents referenced herein (Section 2) and the contents of this SOW (Section 3.), the contents of the SOW shall be the governing requirement.

For technical and performance specifications, PRF-PT-709 shall be the governing technical requirement as noted in Section 2.8.

2.1 DOD Specifications.

Not applicable.

2.2 DOD Standards.

MIL-STD-130 Identification Marking of U.S. Military Property MIL-STD-31000 Technical Data Packages MIL-STD-40051-2B Page-Based Technical Manuals MIL-HDBK-831 Preparation of Test Reports

2.3 Availability of DOD Standards.

Copies are available on the WWW at URL: https://assist.dla.mil/online/start/

2.4 Non-DOD Standards.

ANSI/EIA-748 American National Standards/Electronic Industry Alliance, Earned Value Management System

2.5 Department of Defense Instructions (DoDIs).

DOD Instruction 5000.02, Operation of the Defense Acquisition System, January 7, 2015; http://www.dtic.mil/whs/directives/corres/pdf/500002p.pdf

2.6 Availability of DoDIs.

Copies are available on the WWW at URL:

https://www.dtic.mil/whs/directives/corres/dir.html

2.7 Department of Defense Directives.

Not applicable.

2.8 Other Government Documents, Drawings, and Publications.

PRF-PT-709 System Performance Specifications for Modernizing

Instrumentation Solutions for Test and Evaluation (MISTE), Delivery Order: 0002, Electronic Proving Ground (EPG) Test Network Modernization, Test Instrumentation Systems Network-Enterprise Network (TISN-EN)

PEO-STRI-2017-W071 Statement of Work for Modernizing Instrumentation

Solutions for Test and Evaluation

2.9 Availability of Other Government Documents and Publications.

Copies of the above documents are available at PEO STRI, PM ITTS-IMO, ATTN:

SFAE-STRI-ITTS-I (Erick Serrano), 12211 Science Drive, Orlando, FL 32826-3276 (erick.s.serrano.civ@mail.mil).

3. REQUIREMENTS.

3.1 General.

The Contractor shall design, procure, install, integrate, test, manage, document, train and deliver an operational Test Network at the Electronic Proving Grounds (EPG) at Ft.

Huachuca, AZ that meets the technical requirements, architecture, and performance specification criteria per PRF-PT-709: System Performance Specifications for https://assist.dla.mil/online/start/ http://www.dtic.mil/whs/directives/corres/pdf/500002p.pdf mailto:michael.a.hickey.civ@mail.mil

Modernizing Instrumentation Solutions for Test and Evaluation (MISTE), Delivery Order:

0002, Electronic Proving Ground (EPG) Test Network Modernization, Test Instrumentation Systems Network-Enterprise Network (TISN-EN) and in accordance with the requirements detailed in this document.

This new modernized test network shall be integrated into the existing operational and live test network in a multi-phased approach so as to minimize down time and operational impact, while maintaining customer testing capability. Associated with this modernized Test Network scope, the Contractor shall provide all IT hardware, software, licensing and any ancillary hardware included but not limited to, cabling (i.e., CAT 6, fiber), cable trays, connectors, IT racks, adaptors, hardware modules required for the successful operation of the new modernized Test Network. Any fiber/cabling runs within the same building shall be the responsibility of this Contractor. Any fiber/cabling runs required from one building to another will be the responsibility of the Government.

The government will be responsible for providing all required mechanical (heating, ventilation and air conditioning (HVAC)), and electrical power upgrades to make new hardware operational as part of this effort.

3.2 Program Management.

The Contractor shall provide the overall management and administrative effort necessary to ensure that the requirements of this contract are accomplished. The Contractor shall plan, implement, and maintain a management process to minimize the life cycle system cost and conduct network hardware/software trade studies, evaluate architectures/configuration, design, procure, install, integrate, test and train users of this modernized Test Network. (DI-MGMT-80227, CONTRACTOR’S PROGRESS, STATUS AND MANAGEMENT REPORT)

3.2.1 Integrated Master Schedule (IMS).

The Contractor shall develop, implement, manage to, update, and maintain the contract IMS. All contract schedule information delivered or presented at program reviews shall originate from the IMS and shall contain all critical events and exit criteria, accomplishments, predecessors and successors’ events, and their dependencies. The IMS shall address total program activities including activities performed by major subcontractors. The Contractor shall develop the logic resource loaded network that accurately portrays the sequence and relationship of activities defining the total development and production program. These network activities shall be keyed to the Contract Work Breakdown Structure (CWBS). The network development activities shall be tracked on a computer based program management control system which utilizes critical path method network analysis, accepts parametric data input, and can be utilized to determine a probabilistic estimate of the program schedules and cost for reporting project progress. The network modernization activities time and cost data shall be updated to reflect accomplished activities and any changes in activity time and cost estimates. The Contractor shall conduct critical path analysis of the tasks and identify problem areas and corrective actions required to eliminate or reduce schedule impacts.

(DI-MGMT-81861, INTEGRATED MASTER SCHEDULE (IMS))

3.2.2 Financial Management.

The Contractor shall plan, budget, schedule, and control the resources allocated to meet the requirements of the contract. The Contractor shall document and track the status of all appropriated funds associated with the contract to include payments, cancellations and invoices against each contract line item and subline item. The Contractor shall extend the government Program Work Breakdown Structure (PWBS) (incorporated as part of this SOW) to lower levels in the contractor’s CWBS. It defines the lower level components of what is to be procured and includes all the product elements (hardware, software, data, or services), which are defined by the contractor and the contractor’s responsibility. The extended CWBS shall serve as the framework for contract planning, budgeting, and reporting of cost and schedule status. The Contractor shall identify major elements of subcontracted work in the extended CWBS.

The Contractor may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives. The Contractor shall continually update an integrated database during contract performance with pertinent records and data that underlie and support the cost and schedule data reported. The Contractor shall integrate cost, schedule, and performance management information.

The Contractor shall develop, implement, maintain, and use an EVM system that complies with Industry Guidelines ANSI/EIA-748 and meets contractual requirements.

The Contractor shall document the integrated cost and schedule status of work progress on the contract and relate technical performance with cost and schedule accomplishment using procedures for planning work, controlling costs, and measuring performance based on ANSI/EIA-748. (DI-MGMT-81651, CONTRACT INVOICING

AND PAYMENT REPORT), (DI-MGMT-81468, CONTRACT FUNDS STATUS REPORT

(CFSR)), (DI-MGMT-81861, INTEGRATED PROGRAM MANAGEMENT REPORT

(IMPR))

3.2.3 Risk Management.

The Contractor shall prepare, implement, and maintain a risk management process that includes identification, analysis, mitigation planning, mitigation plan implementation, and tracking. The Contractor shall develop and implement Information Assurance (IA) risk management, which will include security safeguards. These safeguards shall include but are not limited to local policy and guidance, identifies threats, problems and requirements, and adequately plan for the required resources. The Contractor’s risk management process shall measure future uncertainties in achieving program goals within defined cost, schedule, and performance constraints. The IA risk shall be addressed across the risk management process and can be addressed in multiple areas. (DI-MGMT-81808, CONTRACTOR’S RISK MANAGEMENT PLAN)

3.2.4 Management/Technical Reviews.

3.2.4.1 Start of Work Meeting / System Requirement Workshop

A Start of Work Meeting/System Requirements Workshop shall be held at EPG Ft.

Huachuca, AZ within 30 calendar days after contract award. The start of work meeting/system requirements workshop shall be a contractor led meeting, expected to occur over a period of three consecutive days and shall review data and discuss but not limited to:

• Introduction of all IPT team members and contract overview.

• IPT structure, membership, and responsibilities.

• Overview of existing operational Test Network at EPG.

• Site survey of existing network locations that comprise the EPG Test Network.

• Discussion and clarification of Government provided TISN-EN System Performance Specification and other contract document requirements.

• Systems Requirements Workshop to ensure requirements are clear, understandable, derivable and achievable.

• Preliminary review of system requirements already incorporated into the DOORS Requirement Management software tool to provide full traceability and documentation that all identified system requirements shall be traced, derived and validated.

• Presentation of an IMS and detailed schedule with status.

• Identify key coordination events, proposed integration/installation timelines and testing events.

• Critical paths within the IMS.

• Systems engineering and technical network design and implementation approach: proposed trade studies to be conducted of network hardware/software solutions that meet the technical and system performance specifications, preliminary installation and integration plans, preliminary testing and validation approach.

• Preliminary training plan for new hardware and software for successful turnover of the modernized Test Network to EPG network representatives.

• Contract Data Requirements List (CDRL) delivery schedule and status.

• Risk Management Plan.

• Action item reporting and status.

• Long lead time item identification and status.

• Metrics collection process, analysis, and reporting.

• Building infrastructure upgrades or modifications required to support the network modernization effort.

• Cybersecurity requirements and impact to the project.

3.2.4.2 Site Surveys of Existing EPG Test Network.

Following the Start of Work/System Requirement Workshop, the Contractor shall conduct three, four day site surveys of the existing EPG Test Network to understand the current network topology, architecture, concept of operations, use cases, component configurations, physical aspects (i.e., IT rack elevations, cable routing, space constraints, etc…) and location of all equipment covered by this contract action throughout EPG. The site surveys will allow insight into day to day operations, customer testing requirements and other existing critical aspects of the network (i.e., minimal downtime, connectivity with other remote sites). In addition, the site surveys shall gather data to provide insight into existing network management system in support of traffic monitoring and to characterize activity throughout a normal workday and typical test events in terms of type of traffic passed, level of traffic, response time of hosts and time to execute file transfers. (DI-MISC-80711A, SCIENTIFIC AND TECHNICAL

REPORT (SITE SURVEY REPORT))

As part of the Site Survey Report, the Contractor shall analyze how the current state of the network and operational requirements will impact the modernization effort to meet the TISN-EN Specifications, installation, integration and testing requirements. Risks and challenges to overcome shall be discussed with proposed solutions to mitigate these risks and challenges shall be presented. Impacts to building infrastructure systems such as HVAC and electrical power shall be identified. A preliminary plan of execution for design, installation, integration and testing shall be included as part of this Site Survey Report.

The findings from the Site Survey shall be presented 20 days after the last site survey, during a corresponding monthly Technical Interchange Meeting (TIM) at EPG in Ft.

Huachuca, AZ.

3.2.4.3 Program Management Reviews.

The Contractor shall conduct formal Program Management Reviews once every quarter throughout the life of the contract. Contract period of performance is not to exceed three years. The Program Management Review shall provide a project overview and a detailed discussion of pre-selected topics. Program Reviews shall be one day, conducted at PEO STRI’s facility in Orlando, Florida.

3.2.4.4 Technical Interchange Meetings (TIMs).

Subsequent to the Start of Work Meeting/System Requirement Workshop, the Contractor shall lead, conduct, and participate in TIMs every four weeks as a minimum throughout the entire duration of the contract. These meetings will be conducted via teleconferences (expected to last two hours) with the exception of three, one day TIMs to occur at EPG in Ft. Huachuca, AZ. The meetings shall be co-chaired by a Government and contractor representative. The Contractor shall explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of tasks required by the contract. The Contractor shall prepare drawings and other data, as required, to aid in teleconferences. The Contractor shall prepare meeting agendas and document meeting minutes.

3.2.5 Building Facility Infrastructure (HVAC and Electrical Power).

The Government will provide new HVAC and electrical power as required to support the installation of new hardware based on timely identification of system requirements.

Any fiber runs required from one building to another shall be the responsibility of the Government. Any fiber or cabling (ie, CAT 6) and installation within the confines of a building, shall be the responsibility of this Contractor’s scope of work.

3.3 Risk Management Framework (RMF) Process

ATEC’s Cyber Security Office will be have the responsibility of performing Risk Management Framework (RMF) procedures to permit the system to acquire an Authority to Operate (ATO). The Cyber Security requirements for DoD information technologies will be consistent with the principles established in NIST Special Publication (SP) 800-37 in accordance with DoD 8510.01 Risk Management Framework (RMF) for DoD Information Technology (IT).

However, the Contractor under this scope of work, shall provide the following RMF documentation required to implement the RMF Controls for Confidentiality, Integrity and Availability Levels:

a. Security Plan

b. Hardware / Software List

c. Continuity of Operations Plan / Contingency Plan

d. Compliance Deviation Report

The Government Cyber Security team will provide this Contractor with samples and templates of these documents. The Government will work with this Contractor to ensure that the security requirements and procedures are met in accordance with all required DoD and Army regulations per the Mission Assurance Category and Confidentiality levels agreed upon for the system. CYBERSECURITY ARTIFACTS (DI-MISC-80711A)

3.4 Systems Engineering.

The Contractor shall implement a systems engineering process to produce the detailed design and implement an integrated Test and Evaluation process for verification and validation of the TISN_EN Network per the System Performance Specifications.

The Contractor shall, as part of the systems engineering effort, create and maintain the Systems Engineering Management Plan (SEMP) as a living document. (DI-SESS-

81785, SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP))

3.4.1 Preliminary Network Planning and Design Stage.

The Contractor shall translate the basic operational needs, requirements, objectives, interface and other network architectural design constraints including cost, into preliminary verifiable functional requirements.

Network planning and design shall be an iterative process, encompassing topological design, network-synthesis, and network-realization, and shall be aimed at ensuring the new modernized network meets the needs of EPG Test Center while aligned with the TISN-EN architecture.

The Contractor shall conduct cost-benefit trades to support the requirements. The Contractor shall provide an analysis of alternatives of network technical designs and hardware that will meet the performance requirements with the most effective life cycle cost benefit to the Government. The system network design shall be balanced with respect to performance, cost, schedule, and risk and verified it meets the network system performance requirements.

For this stage, Network Engineering reviews shall be completed at 50% of preliminary design for Government visibility and concurrence. The final 100% preliminary network design review will be the Preliminary Design Review (as outlined below) culminating in final government concurrence prior to proceeding into the Detailed Network Design Stage.

The purpose of these reviews shall be to ensure that:

a. An Analysis of Alternatives (AoA) has been developed and complete to achieve the best network performance vs. total-cost-of-ownership to the Government.

The AoA must consider the entire life cycle of the networking environment.

a. Equipment hardware and software costs

b. Performance trade-off costs

c. Installation costs

d. Expansion costs

e. Support costs

f. Cost of downtime

g. Opportunity costs

b. Workload modeling of the proposed new TISN-EN environment has been performed for optimization based on the parameters of the existing Test Network’s characterization of traffic during normal workday and typical test events.

c. Equipment rack elevations are being developed.

d. Building infrastructure improvement requirements (i.e., HVAC, electrical) are being identified.

e. Preliminary network topology, designs and configurations have been developed to meet the architecture and specification criteria. Architecture to comply with the TISN-EN Specifications.

f. A phased installation and integration plan with ongoing coordination with EPG network representatives.

g. Test plans for each IT device and network layer are being developed.

h. Test plans for the enterprise network operation are being developed.

i. Security engineering processes are being integrated into the network design to achieve an integrated secure solution.

j. All system requirements are tracked in DOORS.

3.4.2 Detailed Network Design Stage.

The Contractor shall complete the network system design down to the lowest network level and addressing all components in the network. Detail designs, physical and logical topology drawings, IT hardware and software bill of materials, installation plans and network testing plans shall be finalized. For this stage, network engineering reviews shall be scheduled and completed at 50% of detailed design for Government visibility and concurrence. The final 100% detailed network design review will be the Critical Design Review (as outlined below) culminating in final government concurrence prior to IT hardware/software procurement and installation/integration/testing phase.

The results of design reviews shall be documented.

The purpose of these reviews shall be to ensure that:

a. Each IT hardware device specification will meet its respective performance criteria.

b. Equipment rack elevations are complete and properly documented.

c. Building infrastructure improvements (to be performed by the Government) have been identified.

d. Network topology, designs and configurations have been finalized to meet the network function and performance criteria.

e. A phased installation and integration plan is complete and has been fully coordinated and approved by EPG network representatives.

f. Trade-study data verifies network solution is the most effective life cycle cost benefit to the Government.

g. Test plans for each IT device and network layer have been developed and approved by Government EPG Test Center Representatives and PEO-STRI

IMO.

h. Test plans for enterprise network centric operations have been developed and approved by Government EPG Test Center Representatives and PEO-STRI

IMO.

i. Security engineering processes are integrated into the network design to achieve an integrated secure solution.

j. All system requirements are tracked in DOORS.

3.4.3 CHESS Requirement for Hardware/Software Procurement

Contractor shall procure all IT hardware and software through the US Army Common Hardware Enterprise Software and Solutions (CHESS) contract vehicle unless deviations authorized by the Government.

All IT Hardware procured shall be Information Assurance approved products that are NIAP-validated or on the DoD Unified Capability (UC) Approved Products List (APL) (https://aplits.disa.mil/processAPList.do).

All IT software procured shall have a Certificate of Networthiness (CoN) accreditation issued from the US Army Network Enterprise Technology Command (NETCOM).

3.4.4 Requirements Validation.

The Contractor shall perform and document an analysis to verify all requirements from the System Performance Specifications are met and are traceable. The Contractor shall use IBM® Rational® DOORS® for requirements management.

The Contractor shall ensure there is forward and backward traceability between all requirements (i.e. specifications, test procedures, and associated design documentation).

3.4.5 Design Reviews

The Systems Requirements Review (SRR) (as outlined below) shall be conducted 15 days after completion of the TIM of the Site Survey findings. Successful completion of the SRR will allow the contractor to proceed into the Preliminary Network Planning and Design Stage. The SRR shall occur at EPG during a not to exceed two day period.

As outlined above, for the Preliminary Network Planning and Design Stage, network engineering reviews shall be completed at 50% for Government visibility and concurrence. The final 100% preliminary network design review will be the Preliminary Design Review (as outlined below) culminating in final government concurrence prior to proceeding into the Detailed Network Design Stage. The 50% PDR will occur at EPG during a not to exceed two day period. The 100% PDR will occur at the Contractor’s facility during a not to exceed two day period.

As outlined above, for the Detailed Network Design Stage, Network Engineering reviews shall be completed at 50% of detailed design for Government visibility and concurrence. The final 100% detailed network design review will be the Critical Design Review (as outlined below) culminating in final government concurrence prior to IT hardware/software procurement and installation/integration/configuration/testing phase.

The 50% CDR will occur at EPG over a period of two days. The 100% CDR will occur at the Contractor’s facility over a period of two days.

3.4.5.1 Systems Requirements Review (SRR)

The SRR is a multi-disciplined product and process assessment to ensure the Network Performance requirements, as captured in the TISN-EN System Performance Specifications, are consistent with the Test Network solution and available technologies.

Of critical importance to this review is the understanding of program technical risk https://aplits.disa.mil/processAPList.do inherent in the system performance specification. Acceptable level of risk is key to a successful review. All requirements shall be captured and tracked in DOORS.

See Appendix A for Entry and Exit Criteria and SRR Products.

3.4.5.2 Preliminary Design Review (PDR)

The Preliminary Design Review (PDR) is a multi-disciplined product and process assessment to ensure that the Test Network can proceed into detailed design, and can meet the stated performance requirements within cost, schedule, risk, availability, reliability and maintainability and other system constraints.

See Appendix A for Entry and Exit Criteria and PDR Products.

3.4.5.3 Critical Design Review

The Critical Design Review (CDR) is a multi-disciplined product and process assessment to ensure that the Test Network can proceed into the IT hardware/software procurement and installation/integration/configuration/testing phase.

See Appendix A for Entry and Exit Criteria and CDR Products.

3.4.6 Product Definition Data (PDD).

During the systems engineering and design, and in accordance with MIL-STD-31000, the Contractor shall develop, produce, and maintain product definition data (PDD) that accurately depicts the final TISN-EN Design and validation & verification compliance.

The PDD is the technical description of items adequate for supporting an acquisition strategy, procurement, engineering, and logistics support. The PDD shall disclose complete network design, topology, diagrams, rack elevations, architecture, logistics, and the means of measuring compliance with the requirements. Hardware/Software information (equipment, drawings, software & associated licenses, computer aided design files and metadata) and associated lists shall provide design and engineering requirements. (DI-IPSC-81431A w/NOT 1, SYSTEM/SUBSYSTEM SPECIFICATION

(SSS)), (DI-IPSC-81432A, SYSTEM/SUBSYSTEM DESIGN DESCRIPTION (SSDD)),

(DI-SESS-81003E, COMMERCIAL DRAWINGS/MODELS AND ASSOCIATED LISTS),

(DI-SESS-81000E, PRODUCT DRAWINGS MODELS AND ASSOCIATED LISTS), (DI-

SESS-81704, TEST PLANS/TEST PROCEDURES)

3.4.7 Anti-Terrorism (AT) Level 1 Awareness Training.

All Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, and controlled access areas shall complete AT Level 1 Awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected Contractor, to the

Contracting Officer’s Representative (COR) or to the contracting officer. Training is available at the following website: https://atlevel1.dtic.mil/at/.

(DI-MISC-80711A, SCIENTIFIC AND TECHNICAL REPORT (AT TRAINING))

3.4.8 Access and General Protection/Security Policy and Procedures.

The Contractor shall ensure that all employees, including subcontractor employees, shall provide all information required for background checks to meet installation access requirements as directed by the installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, Head Quarters Department of the Army (HqDA), and/or local policy. The Contractor shall comply with agency personal identity verification procedures identified in the contract that implement Homeland Security Presidential Directive-1 (HSPD-12), Office of Management and Budget (OMB) guidance M-05-24, and Federal Information Processing Standards Publication (FIPS PUB) Number 201.

Contractor will require access to Controlled Unclassified Information (CUI), Technical Information/Documents and For Official Use Only (FOUO) information. The Contractor shall ensure that employees performing under this contract have the appropriate SECRET clearance for requirements supported and identified in the DD254.

3.4.9 Threat Awareness and Reporting Program (TARP).

All Contractor employees with security clearances must receive annual TARP training by a counterintelligence agent or other trainer as specified in AR 381-12, Threat Awareness and Reporting Program, Paragraph 2-4b. TARP training shall be completed within 30 calendar days of contract award and within 15 calendar days of new employees commencing performance. The Contractor shall submit certificates of completion for each affected Contractor, to the Contracting Officer’s Representative (COR) or to the contracting officer.

(DI-MISC-80711A, SCIENTIFIC AND TECHNICAL REPORT – TARP TRAINING)

If the contractor is meeting the TARP requirement, there is no need for IWATCH!

3.4.10 iWATCH Training.

The Contractor and all associated subcontractors shall brief employees on the local iWATCH program training standards provided by the requiring authority. Using the iWATCH program, the Contractor workforce shall recognize suspicious activities and the proper method of reporting. iWATCH training shall be completed within 30 calendar days of contract award and within 15 calendar days of new employees commencing work. Results shall be reported to the COR after completion of training. (DI-MISC-

80711A, SCIENTIFIC AND TECHNICAL REPORT (AT TRAINING))

https://atlevel1.dtic.mil/at/

3.4.11 OPSEC (Operational Security) Awareness Training.

Contractor employees and all associated subcontractors requiring access to Government installations, facilities, and controlled access areas shall complete Level I OPSEC Awareness training within 30 calendar days after the contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable, and annually thereafter. New employees shall be trained within 30 calendar days of their reporting for duty and annually thereafter. OPSEC Awareness training is available at the following website: http://cdsetrain.dtic.mil/opsec.

. (DI-MISC-80711A, SCIENTIFIC AND TECHNICAL REPORT (OPSEC TRAINING))

3.5 Integrated Testing.

The Contractor shall plan, coordinate, establish, and implement a comprehensive Network Testing program to verify performance, stability, availability, reliability and optimization at both a component level and a complete network centric level. The Network Testing program will ensure the network meets the technical and operational requirements, as stated in the System Performance Specifications.

(DI-SESS-81704, TEST PLANS/TEST PROCEDURES)

3.5.1 Integration Readiness Review (IRR).

The IRR is a multi-disciplined product and process assessment to ensure the network hardware/software is ready for shipment and integration into the EPG Test Network.

The IRR is anticipated to be two days in duration at EPG Ft. Huachuca, AZ. Key consideration and criticality of importance is that this new modernized test network shall be integrated into the existing operational and live test network in a multi-phased approach so as to minimize down time while maintaining customer testing capability.

See Appendix A for Entry and Exit Criteria and IRR Products.

3.5.2 Test Readiness Review (TRR).

The TRR is a multi-disciplined product and process assessment that the modernized Test Network System at EPG has demonstrated and achieved performance requirements. The TRR is anticipated to be two days in duration at EPG Ft. Huachuca, AZ. After requirements validation through testing have been demonstrated by the Contractor, the Government will proceed towards Government Acceptance Testing.

The TRR verifies the traceability of test plans to program and performance specification requirements. Documentation from DOORS and all related back-up material will be reviewed to verify traceability has been successfully accomplished. The Contractor shall address the following key issues at the system engineering TRR prior to the start of formal Government acceptance testing:

http://cdsetrain.dtic.mil/opsec

a. Test procedures comply with plans and descriptions are adequate to accomplish test verification requirements.

b. New or modified test equipment and procedure manuals required to accomplish planned test and evaluation, are available and satisfy requirements.

c. Testing results correlate to Test Procedures and Plans.

d. DOORS documentation is current and up to date for verification and full traceability that every requirement in the TISN-EN System Performance Specifications has been satisfied.

See Appendix A for Entry and Exit Criteria and TRR Products.

3.5.3 Government Site Acceptance Test and TISN-EN Test Network Verification Review (TNVR)

The TNVR is a multi-disciplined assessment to ensure the system has met performance, cost, schedule, and risk requirements prior to formal acceptance by the Government. Both the Contractor’s final approved test reports and the Government’s final approved test reports will be reviewed. The TNVR is anticipated to be two days in duration at EPG, Ft. Huachuca, AZ. In addition, the complete PDD shall be submitted to the government for review and acceptance.

See Appendix A for Entry and Exit Criteria and SVR Products.

3.6 Site Activation

The Contractor shall conduct a final installation survey at least six months prior to the commencement of the IT hardware installation.

During the survey, the Contractor shall review and confirm:

(1) The status of the building or location where the IT hardware will be installed.

(2) Confirm the required positions of equipment, assemblies, cableways, access ways, and any other unique feature, and measure to insure clearance during the installation.

(3) Review and confirm the proposed location of power outlets, cabling (CAT 6, fiber) are in place and ready to accept the new IT hardware.

(4) Determine the availability of required services.

(5) Review and confirm arrangements for hours of work, access to work areas, delivery routes, and on-site personnel participation.

(6) Discuss and resolve any outstanding issues pertaining to the installation phase.

3.6.1 Installation Tools and Test Equipment.

The Contractor’s installation team shall be equipped with all tools required for the network system installation. Any special tools shall remain at the site and become property of the Government.

3.6.2 Installation Spares.

The Contractor’s installation team shall be equipped with an installation spares package of common items (i.e., cabling, connectors, connector kits, etc.) as required to perform on-site testing and Government acceptance testing. The installation spares packages shall remain at the site and become property of the Government.

3.7 Training Requirements.

3.7.1 Training.

The Contractor shall develop and execute a comprehensive training plan for EPG network engineering personnel that includes classroom (outside of EPG), on-site (at EPG) and over the shoulder training (at EPG) for all new hardware/software installed as part of the TISN-EN network. (DI-ILSS-80872, TRAINING MATERIALS)

3.8 Logistics Requirements.

3.8.1 Spare Parts.

The Contractor shall provide the following Spare Parts as part of this effort:

a. (1) One L2BS device (Layer 2 Bridging Switch)

b. (1) One ACS device (Area Core Switch)

c. (1) One ADS device (Area Distribution Switch)

d. (3) Three EAS devices (Edge Access Switch).

e. (1) One 1,000’ SMF fiber reel.

f. (1) One 1,000’ CAT 6 fiber reel.

g. (15%) of all connector types utilized

h. (1) One fiber connector kit

3.8.2 Equipment Obsolescence Plan.

The Contractor shall develop an Equipment Obsolescence Plan for all IT hardware and software procured and installed as part of this network modernization effort. This plan shall identify all IT equipment, cost, end-of-sale, end-of-life, end-of-service and end of APL list approval. This plan shall also contain all software costs, licensing information coupled with costs of yearly sustainment and Certificate of Networthiness (CoN) expirations. This information will be utilized by ATEC Headquarters for sustainment purposes for future out years’ budget planning and replacement. (DI-MISC-80711A , SCIENTIFIC AND TECHNICAL REPORT (EQUIPMENT OBSOLESCENCE REPORT))

3.8.3 Material Requirements.

3.8.3.1 Item Unique Identification (IUID) of Tangible Items.

The Contractor shall implement an IUID of tangible items in accordance with MIL-STD- 130N w/Change 1. IUID means a set of data marked on items that is globally unique, unambiguous, and robust enough to ensure data information quality throughout the system’s life. These requirements apply to developed and commercial items. The Contractor shall coordinate among the IPT members and identify Unique Identification (UID) type, the UID to be used, and items requiring unique identification including embedded subassemblies, components, and parts. The Contractor shall provide IUID, or a DOD-recognized unique identification equivalent, for all identified items delivered.

The Contractor shall submit this data to the DOD IUID central registry. UID marking of items shall be both machine-readable and human-readable. (DI-MGMT-81804A, ITEM

UNIQUE IDENTIFICATION (IUID) MARKING ACTIVITY, VALIDATION AND

VERIFICATION REPORT)

3.8.4 Commercial Off-The-Shelve (COTS) Manuals.

The contractor shall deliver Commercial Off-the-Shelf (COTS) technical publications for all commercial equipment and software delivered with the TISN-EN network. The COTS documentation shall be obtained in electronic media or scanned into indexed electronic media (i.e., portable document format) for delivery to the Government and be sufficient to support the operation and maintenance of all COTS components per MIL- PRF-32216. The contractor shall review the COTS documentation and identify deficiencies or deviations in the manuals. If the COTS document is not sufficient to support the operation and maintenance and the contractor is unable to retrieve the required data from the vendor, the contractor shall develop supplementary data for inclusion in the main text of the Technical Manual ensuring that all required data for the COTS item is presented. (DI-TMSS-80527C, COMMERCIAL OFF THE SHELF

MANUALS & ASSOCIATED SUPPLEMENTAL DATA)

A-1

APPENDIX A – Design Review Entry and Exit Design Criteria and Data Products

SRR:

A.1 SRR Entry Criteria The SRR is a multi-disciplined product and process assessment to ensure the System Performance Specifications requirements are consistent with the TISN-EN solution and available technologies. Of critical importance to this review is the understanding of program technical risk inherent in the system performance specification and coupled with the overall life cycle cost benefit to the government with the available solutions. All requirements shall be captured and tracked in DOORS and presented during this SRR.

a. A preliminary agenda has been coordinated (nominally) 15 days prior to the SRR.

b. SRR technical products for hardware and software configuration item have been made available to the cognizant SRR participants prior to the review:

(1) All requirements have been incorporated in the DOORS requirements management tool with backwards traceability means

(2) Conceptual topology and architecture of the proposed modernized network solution. Architecture to meet the TISN-EN System Performance Specifications.

(3) A comprehensive risk assessment with emphasis on the installation/integration approach to minimize existing operational network downtime. Contractor to present multiple approaches for completing the integration phase that minimizes network down time.

(4) A proposed testing approach to meet the network availability requirements

(5) Top level approach to the proposed Testing Program

(6) Top level approach to the proposed Training Program

(7) Cybersecurity impacts to the TISN-EN Network

A.2 Exit Criteria shall include:

(1) Are the system requirements and specifications sufficiently detailed and understood proceed forward to Preliminary Planning and Network Design Stage?

(2) Can the requirements be met given the technology available in COTS hardware and software solutions?

(3) Are adequate processes and metrics in place for the program to succeed?

(4) Are the risks known and manageable?

(5) Is the program schedule executable (technical/cost risks)?

(6) Is the program properly staffed?

(7) Is the program executable within the existing budget?

(8) Have preliminary architectures and configurations been presented to meet the modernized network at EPG?

A-2

(9) Have installation and integration challenges been understood and solutions presented to minimize test network downtime?

(10) Have preliminary testing approaches been identified and presented to best meet the modernization efforts of the EPG TISN-EN Network?

(11) Have physical, power and space concerns been identified to be able to install new hardware in existing or new IT racks?

(12) Has a preliminary training approach been presented to provide EPG network engineering users with the ability to configure and manage the new modernized Test Network?

(13) Have Cybersecurity impacts been identified and are clear on how they impact the project? And does the Contractor understand his roles and responsibility of the RMF process?

A.3 SRR Products

a. Completion of the SRR shall provide the following:

(1) An approval of all network system performance requirements identified in

DOORS.

(2) A preliminary identification of all potential hardware/software components (support, deliverable, non-deliverable, etc.)

(3) Identification of all new IT hardware locations to be installed throughout the entire EPG Network.

(4) Identification of IT Rack space availability throughout the entire EPG Network.

(5) Preliminary identification of building infrastructure (HVAC, electrical, etc.), upgrades required to support new modernization effort.

(6) Preliminary identification of cabling (i.e., CAT 6 and Fiber) runs from building to buildings proposed for new EPG Test Network modernization.

(7) Preliminary installation/integration approaches to minimize network downtime.

(8) Preliminary identification of cost-effective network testing approaches to meet the requirements of the network performance specification requirements.

(9) Preliminary training approaches to provide EPG network engineering users with the ability to configure and manage the new modernized Test Network

(10) A comprehensive risk assessment

(11) An approved SEMP that addresses cost and critical path drivers

b. Email each attendee the following documents:

(1) List of attendees, to include; name, functional area represented, phone number, and email address,

(2) Meeting minutes

(3) Recommendation as to the technical readiness of the program to enter the next stage of design: Preliminary Network Planning and Design Stage

A-3

PDR:

A.4 PDR Entry Criteria Multi-disciplined product and process assessment to ensure the system can proceed to detailed design, can meet performance, cost, schedule, and risk requirements.

a. A preliminary agenda has been coordinated (nominally) 15 days prior to the PDR.

b. PDR technical products for each system hardware and software configuration item have been made available to the cognizant PDR participants prior to the review:

(1) Refined System Performance Specifications

(2) Network System Performance Requirements tracking in DOORS with traceability of proposed validation method.

(3) A completed Analysis of Alternatives (AoA) to achieve the best network performance vs. total-cost-of-ownership to the Government. The AoA must consider the entire life cycle of the networking environment.

(a) Equipment hardware and software costs

(b) Performance trade-off costs

(c) Installation costs

(d) Expansion costs

(e) Support costs

(f) Cost of downtime

(g) Opportunity costs

(h) Sunken costs.

(4) Preliminary Network topology, configurations have been developed to meet the performance criteria and overall EPG Test Network. Architecture to meet TISN-EN Specifications.

(5) Logistics documentation of all equipment/software proposed.

(6) Workload modeling of the proposed new Test Network for optimization based on the parameters of the existing Test Network’s characterization of traffic during normal workday and typical test events.

(7) Updated IT equipment rack elevations.

(8) Updated building infrastructure improvements (i.e., HVAC, electrical)

(9) Refined phased installation and integration plans to minimize network downtime.

(10) Refined Test Plans for the new modernized EPG Test Network to address component testing and network centric wide testing.

(11) Security engineering (Cybersecurity) implementation approach to integrate a secure solution into the new modernized EPG Test Network.

(12) Updated risk assessment

A.5 PDR Completion/Exit Criteria

a. The PDR is considered complete when all draft Request for Actions (RFAs) are signed off, and an acceptable level of program risk is ascertained.

A-4

b. Typical Exit Criteria include:

(1) Can the preliminary design, as disclosed, satisfy the system performance requirements?

(2) Are the system requirements and specifications sufficiently detailed and understood proceed forward to Detailed…