Attachment 3 - TO0001 PWS - DRAFT.docx

PERFORMANCE WORK STATEMENT (PWS)

Award

Contract Number:

Task Order Number:

Contractor Name

1. Contracting Officer’s Representative (COR)

a. Primary COR. See Points of Contact in Contract Administration Data

b. Alternate COR. See Points of Contact in Contract Administration Data

2. Task Order Title United States European Command (USEUCOM) Enterprise Multi-site Cutover Design

3. Background USEUCOM is continuing to modernize their systems and networks and make them resilient. USEUCOM will cutover data and services from their primary Special Purpose Processing Node (SPPN) at site A to a secondary SPPN at site C. USEUCOM will require non-personal services to develop the designs and plans to support all USEUCOM sites for the cutover.

Actual site locations will be provided at time of award.

4. Objectives The objective of this task order (TO) is to survey, gather requirements, develop designs, and develop cutover plans to support the cutover of USEUCOM data and services from site A to site C.

5. Scope The contractor shall survey, gather requirements, develop designs, and develop cutover plans for USEUCOM sites D, E, K, and RAS. These USEUCOM sites will be affected during the cutover of data and services from SPPN site A to SPPN site C. The designs and plans shall address the following functional areas but not limited to:

· Data Center Infrastructure

· Cisco Application Centric Infrastructure (ACI) Fabric/Schema

· Network Policy / Cisco ACI Naming Convention

· Core Services and Host Services

· Software Licensing and Software Engineering

· Network Physical / Logical Design

· Cybersecurity

· Virtual Infrastructure

· Database

· Integrated Systems for Knowledge Management (ISKM)

· Service Delivery / Automation

· Command and Control (C2) Infrastructure

· Compute and Storage

6. Performance Requirements

6.1 Task 1: Project Management

6.1.1 TO Kickoff

No later than (NLT) ten (10) business days post TO award, the contractor shall develop and submit a kickoff brief consisting of staffing plan or organizational resource chart, draft schedule, primary objective and scope, issues and risks, and assumptions for review. The contractor shall coordinate with the COR to schedule the kickoff in person or virtual.

6.1.2 Plan of Action and Milestones (POA&M)

The contractor shall develop a POA&M for all tasks and milestones associated with the TO PWS and submit to the COR, NLT ten (10) business days post TO award. The POA&M shall show the completion of all tasks, including review periods for ten (10) business days. It shall utilize a Work Breakdown Structure (WBS) to compartmentalize the effort into definable work efforts and to show assigned resources to each work element and the amount of time in business days necessary to complete each element. The POA&M shall show the interdependencies between all tasks and subtasks. It shall have a Forecasted versus Actual versus Baseline tracking basis and shall identify tasks, dependencies, baseline start dates, baseline finish dates, baseline durations, actual start dates, actual finish dates, actual durations, forecasted start dates, forecasted finish dates, forecasted durations, and percent complete for each task and subtask. It shall be developed in Microsoft Office Project 2016 or later version.

A draft POA&M, baseline POA&M, and monthly POA&M updates shall be submitted. Monthly updates for the POA&M and all other monthly project management artifacts shall be submitted simultaneously prior to the 10th of each month at which time the Government COR has five (5) business days to provide comments and the contractor shall update three (3) business days thereafter. At the discretion of the Government, the contractor shall re-baseline the POA&M and provide weekly schedule updates.

6.1.3 Weekly Meetings

The contractor shall host a weekly web conference and audio teleconference with the COR and other Government stakeholders to discuss the schedule, upcoming activities, action items, risks, and issues with the TO. Prior to the meeting, the contractor shall provide a Weekly Activity Report (WAR) to include a stoplight report including high-level schedule, milestones and deliverables, funding report, list of actions, list of risks/issues. The time of the weekly meeting will be determined with the COR post award of a TO.

The contractor shall develop and deliver meeting reports, which shall include participants, objective, agenda, conclusion, and action items. The contractor shall submit meeting reports to the Government for review within one (1) business day following meetings.

6.1.4 Project Change Requests (PCR)

The contractor shall inform the COR and other Government stakeholders for any potential cost, schedule, and performance changes on a TO. The contractor shall provide the analysis and the potential impact into a PCR. The Government will review the PCR, make any necessary changes, perform independent analysis, develop an Independent Government Cost Estimate (IGCE), and formally initiate the PCR with relevant Government stakeholders. Upon approval of the PCR from the Government, the COR will submit a TO modification request to the Contracting Office. Note that until the modification of any changes has been awarded by the Contracting Officer, the contractor is not authorized to proceed to execute any requested changes.

6.1.5 Monthly Status Report

The contractor shall develop and submit a TO status report monthly at least 30 days after TO award on the 10th of each month for those months the TO is active. The contractor shall report on various TO functions, performance, schedule, financial, business relations, and staffing plan/key personnel. The contractor shall develop and deliver, each month, a monthly progress report which shall describe sponsor information, project information, 30-day look back of activities and deliverables, 30-day look ahead of schedule of activities and deliverables, contract history, project status, deliverable status, action items, requests for information, risks/issues, and service requests. All active and completed tasks within the reporting period level of effort tasks shall be identified with a description, completion status, estimated completion date, total amount, and any comments on the status.

The contractor shall also provide a monthly financial report that shall include month-to-month tracking, Contract Line Item Number (CLIN) structure, billed to date, invoicing, funds remaining, invoiced/paid, and details of the Other Direct Cost (ODC) charges (e.g., travel, Housing Overseas Living Allowance (HOLA), Cost of Living Allowance (COLA), materials, subcontracts, etc.). Travel charges shall be broken down to show traveler’s per diem, lodging, air fare, rental car, General and Administrative costs (G&A), and other fees, etc. The HOLA shall be broken up to monthly rent and utilities. The materials shall be broken down to show which materials are ordered, shipped, or delivered, purchase order number, invoice number, shipping costs, G&A, and other fees, etc. The subcontracts shall be broken down to show which services are ongoing, completed, and associated invoices, charges and payments, and any leasing invoices, changes, and payments tied.

6.1.6 TO Closeout Report

The contractor shall develop a TO Closeout Report and submit it no later than 15 days before the TO completion date. The prime contractor shall be responsible for collecting, integrating, and reporting all subcontracting information.

6.1.1

6.2 Task 2: Requirements Development

6.2.1 Site Survey

The Contractor shall conduct a site survey to verify current site conditions, conduct interviews for requirements, and validation of installation design. The contractor shall prepare an in-brief and site survey checklist and submit one (1) week prior to the site survey to the government. The contractor shall prepare an out-brief and submit to the Government one (1) business day prior to the completion of the site survey. The contractor shall develop a detailed 90% site survey report and submit within 2 weeks after the site survey. After review from the government, the contractor shall submit the finalized 100% site survey report. The contractor shall scan and submit survey notes and completed checklists.

6.2.2 Requirements

The Contractor shall develop a Roles and Responsibility Matrix (RRM), Requirements Traceability Matrix (RTM), and System Requirements Matrix (SRM) which will drive questions to further derive requirements and ensure stakeholder acceptance of the requirements. The Contractor shall integrate RRM into the POA&M for each task and subtask.

6.2.1

6.2.1

6.2.1

6.2.2

6.2.2

6.2.2

6.3 Task 3: Design

6.3.1 Installation Design Plan (IDP)

The Contractor shall utilize the results of the surveys and the analysis of the requirements to develop an Installation Design Plan (IDP) that will meet the requirements of the system migration and cutover of data and services for USEUCOM sites D, E, K, and RAS from site A to site C. The Contractor shall develop 30%, 60%, 90%, and 100% iterations of the IDPs utilizing System of Systems engineering approach. The IDPs shall comply with USEUCOM/2nd Sig Brigade standards.

The Contractor shall conduct in-person design reviews with the Government and Government appointed representatives for each engineering deliverable. The Contractor shall also extend invites to the Government for internal Contractor design reviews to support a collaborative and immediate feedback environment. At the major design milestones (30%, 60%, 90%, and 100%), the Contractor shall provide the design artifacts to include a design brief NLT (10) business days prior to the in-person design review. The contractor shall document and consolidate all the review comments received from in-person reviews and virtual submissions. The Contractor shall respond to all Government comments and provide updates to the IDP in the next or current iteration of the design based on customer concurrence. The Contractor shall prepare a design signature page detailing acceptance of the design review for each of the major design milestones (30%, 60%, 90%, and 100%).

6.3.2 Systems Migration and Cutover

The Contractor shall develop a draft and final Systems Migration and Cutover Plan. The plan shall contain sufficient detail to address all of the requirements and work activities for systems cutover (e.g., a recovery and fallback contingency plan, schedule, draft Authorized Service Interruption (ASI), and the impacts to the system(s) and/or operation(s) of each stakeholder). The Systems Migration and Cutover Plan shall also be integrated into the IDP detailing which sites, systems, components, and subcomponents will be hot cutover, cold cutover, warm cutover, no cutover required.

The Contractor shall provide a draft System Migration and Cutover Plan NTL (10) business days prior to design review for the major design milestone (90% IDP) and receipt of Government comments. The Contractor shall incorporate the required changes and submit the final Systems Migration and Cutover Plan

6.3.3 List of Materials (LOM)

The Contractor shall develop a List of Materials (LOM) and deliver it along with the 60% IDP. The Contractor shall classify long-lead procurement in the LOM. Additional LOMs can be submitted as the IDP is finalized. The LOM is a separate spreadsheet and shall match parts lists and technical data summary in the IDP. The LOM must include the minimum information: manufacturer, part number, description, quantities, unit of measurement, list price, and extended price, technical data (size, weight, power ratings, heat output, etc.).

6.3.1

6.3.2

6.3.3

6.4 Task 4: System Software Configuration

The Contractor shall develop 60% and 90% System Software Configuration Plan (SSCP) and deliver the plan NLT (30) business days post the development of 60% and 90% IDPs. The plan shall contain changes to configuration settings not documented in the IDPs. This shall include router, switch, firewall, and server operation system and application software configuration settings. The plan may include the development of logical network diagrams with network addressing (e.g., IP addressing) information. The information should include configuration information for the system being installed and configuration information for interfacing systems and equipment whose configurations may need to be changed. If the information is not in the IDPs, the document containing the information shall be identified in the IDP and provided to the Government. The information shall be included in the System Operational Verification Test (SOVT). If the information is classified, the information shall be in separate document that is controlled per the classification requirements.

6.4

60% and 90% System Software Configuration Plan

6.5 Task 5: Cybersecurity

The contractor shall develop Cybersecurity artifacts that are compliant with the relevant DoD and Army Cybersecurity policies and standards including DoD 8500.1, DoD 8510.1//Risk Management Framework (RMF), National Institute of Standard and Technology (NIST) Special Publication (SP) 800-53. All artifacts shall follow the latest version of the RMF Processing Guide. The contractor shall develop the following Cybersecurity RMF artifacts to include but not limited to the following:

· Hardware List

· Firmware List

· Software List

· System Enterprise and Information Security Architecture

· System Authorization Boundary (Defense Information Systems Agency (DISA)-Connection Process Guide (CPG) compliant diagram)

· Information Flows/Paths The Contractor shall ensure that all products recommended and/or procured that impact cybersecurity or IA shall be selected from the National Information Assurance Partnership (NIAP) Validated Products List or other APL with reciprocity. The Contractor shall ensure the products chosen are based on the appropriate Evaluated Assurance Level (EAL) for the network involved and are utilized in accordance with latest Defense Information Systems Agency (DISA) policy at time of order. The Contractor shall store all product information and have it available for Government review at any time.

The Contractor shall ensure any equipment/system installed or integrated into EUCOM platform will meet the cybersecurity requirements as specified under DoDI 8500.01. The Contractor shall ensure that any design change, integration change, configuration change, or installation of hardware and software is in accordance with established DoD/EUCOM/Navy cyber directives and does not violate the terms and conditions of the authorization issued by the appropriate Authorization Official (AO).

6.6 Task 6: Construction Security Plan (CSP)

The Contractor shall develop an addendum to the USEUCOM Special Security Officer (SSO) developed CSP for the procurement, shipping, transportation, and installation of the equipment and materials providing security implementation methodology in accordance with Intelligence Community Directive (ICD) 705 guidance and in compliance. USEUCOM SSO will review and approve/reject the CSP or CSP Addendum. The Contractor shall correct the CSP based on Government’s feedback. The Contractor shall submit a draft copy of the Mitigation Plan with the 60% Installation Design Plan (IDP). A final copy shall be submitted within thirty (30) calendar days after receiving Government comments.

6.6

6.7 Task 7: Pre-Installation Test and Check-out (PITCO)

The contractor shall conduct PITCO prior to installation of equipment/systems. This shall include, but is not limited to, installation tests and systems tests for system validation for all system performance requirements. It may require the use of extensive equipment configurations or simulation/emulation tools to model the complete system under stress factors as it is expected to operate in its intended environment. The PITCO may be conducted at Government facilities, contractor facilities, or a project site. The purpose of the PITCO is to provide assurance the procured system and components of a system will be functional prior to installation or integration. The PITCO can be performed in a laboratory or controlled setting but shall simulate the live and operational environment. Due to the nature of operational environments, there are very likely to be several systems with which integration is required that is not available except in the live system. While PITCO provides a level of confidence that the equipment/system that will be delivered for installation is fully operational, it does not for this reason provide a level of confidence that the interfaces between the new and existing (or contractor provided and other provided) systems will be fully operational once installed or integrated.

The contractor shall develop and submit a draft PITCO Plan along with the submission of the 60% IDP. The contractor shall ensure the PITCO Plan that will be used by the contractor and COR to document that the new system/equipment has been properly configured and/or integrated prior to installation, has been tested and is ready for shipment to the installation site. The PITCO Plan shall contain sufficient detailed testing to fully exercise the system or equipment’s capabilities to the extent possible within the PITCO test environment. The Government will require a minimum of the five (5) business days to provide comments. The contractor shall address all the comments and provide an updated PITCO Plan with the corrections within ten (10) business days.

6.7

6.8 Task 8: System Operation Verification Test (SOVT)

The contractor shall develop the draft SOVT and submit along with the 90% IDP. The Government review, provide comments, and/or approval. The contractor shall address all of the comments and resubmit the SOVT with corrections within ten (10) business days.

The SOVT shall contain sufficient detailed testing to fully exercise the system or equipment’s capabilities. The SOVT document shall include the names of the installation and site personnel that participated in the SOVT along with places for signatures/initials that certify that the testing was satisfactorily completed. The SOVT shall be developed IAW referenced NIWC Atlantic Shore Installation Process Handbook (SIPH) and the Space and Naval Warfare (SPAWAR) Preparation and Execution Guide (SPEG). At a minimum, the SOVT will address the following areas:

· A description of the hardware/software configuration installed

· Overall system physical inspection

· Non-operational testing

· Primary power checks

· Equipment testing

· System interface testing

· End-to-end testing

· Equipment/system shutdown procedures

6.9

7. Performance Standards

TASK 1: Project Management (PWS 6.1)

(AQL)

Methods of Calculation

Documents and reports

High level of accuracy

Documents and reports that are complete; have no flawed information, analyses, assumptions, or conclusions.

Minimum Acceptable:

> 95% accuracy of all documents and reports. COR can accept deliverable with comments Calculation:

100% Review from the COR and/or Government Program Manager.

5% or less of error rate.

TASK 2: Requirements (PWS 6.2)

Survey Report

High level of accuracy Reports that are complete; have no flawed information, analyses, assumptions, or conclusions.

Minimum Acceptable:

> 95% accuracy of all reports. COR can accept deliverable with comments Calculation:

100% Review from the COR and/or Government Engineering team.

Less than 5% of error rate.

Requirements Documents

High level of accuracy

Documents that are complete; have no flawed information, analyses, assumptions, or conclusions.

Minimum Acceptable:

> 95% accuracy of all documents. COR can accept deliverable with comments Calculation:

100% Review from the COR and/or Government Engineering team.

5% or less of error rate.

TASK 3: Design (PWS 6.3)

IDP

High level of accuracy IDP packages that are complete; have minor flawed information.

Minimum Acceptable:

> 95% accuracy of all packages. COR can accept deliverable with comments and contractor to correct at next iteration.

Calculation:

100% Review from the COR and/or Government Engineering team.

5% or less of error rate.

Systems Migration and Cutover Plan

High level of accuracy Plan that are complete; have no flawed information, analyses, assumptions, or conclusions.

Minimum Acceptable:

> 95% accuracy of all plans. COR can accept deliverable with comments and contractor to correct at next iteration.

Calculation:

100% Review from the COR and/or Government Engineering team.

5% or less of error rate.

LOM

Absolute accuracy LOM that is complete; have no flawed information.

Minimum Acceptable:

100% accuracy of all LOM.

Calculation:

100% Review from the COR and/or Government Engineering team and compare to the approved design.

0% error rate.

TASK 4: System Software Configuration (PWS 6.4)

System Software Configuration Plan (SSCP)

High level of accuracy Plans that are complete; have no flawed information, analyses, assumptions, or conclusions.

Minimum Acceptable:

> 95% accuracy of all plans. COR can accept deliverable with comments Calculation:

100% Review from the COR and/or Government Engineering team.

5% or less of error rate.

TASK 5: Cybersecurity (PWS 6.5)

Cybersecurity Artifacts

High level of accuracy Artifacts that are complete; have no flawed information, analyses, assumptions, or conclusions.

Minimum Acceptable:

> 95% accuracy of all artifacts. COR can accept deliverable with comments and contractor to make corrections Calculation:

100% Review from the COR and/or Government Cybersecurity team.

5% or less of error rate.

TASK 6: Construction Security Plan (CSP) (PWS 6.6)

CSP Addendum

High level of accuracy Plan that are complete; have no flawed information.

Minimum Acceptable:

> 95% accuracy of all plans. COR can accept deliverable with comments and contractor to correct at next iteration.

Calculation:

100% Review from the COR and/or Government Engineering team.

5% or less of error rate.

TASK 7: Pre-Installation Test and Check-out (PITCO) (PWS 6.7)

PITCO Plan

High level of accuracy Plan that are complete; have no flawed information.

Minimum Acceptable:

> 95% accuracy of all plans. COR can accept deliverable with comments and contractor to correct.

Calculation:

100% Review from the COR and/or Government Engineering team.

5% or less of error rate.

TASK 8: System Operational Verification Test (SOVT) (PWS 6.8)

SOVT Document

Absolute accuracy Documents that are complete; have no flawed information and assumptions.

Minimum Acceptable:

100% accuracy of all documents. COR can accept deliverable when contractor makes the corrections.

Calculation:

100% Review from the COR and/or Government testing team.

0% error rate.

8. Incentives If applicable, the COR will create an annual report on contractor performance (via the Contractor Performance Assessment Reporting System (CPARS) or other annual report). Both positive and negative performance will be documented in past performance reports/database, CPARS, as appropriate, and will be taken into consideration for other task orders or follow-on work. For each item that does not meet acceptable levels, the Government will issue a Contract Discrepancy Report (CDR). CDRs will be forwarded to the Contracting Officer with a copy sent to the contractor. The contractor shall reply in writing within five business days of receipt identifying how future occurrences of the problem will be prevented.

9. Place of Performance

· United States Army Garrison (USAG) Stuttgart, Germany

· Royal Air Force Molesworth, United Kingdom

· Supreme Headquarters Allied Powers Europe (SHAPE) Mons, Belgium

· Shore installations in USEUCOM’s AOR: https://www.eucom.mil/about/the-region

· Site names and locations can be provided via secure methods upon request during solicitation

· Contractor’s Facilities

10. Period of Performance The period of performance of this Task Order: 12 months from date of award

11. Security Requirements Security requirements shall comply with the basic contract DD254.

Work executed and documents developed under this TO may be classified up to Secret. All personnel under this TO will need a Secret clearance. For physical access into Sensitive Compartmented Information (SCI) a Top Secret / Sensitive Compartmented Information (SCI) clearance is required.

11.1 Security References:

· DISA End User Access Agreement, 11 February 2021

· DISA Instruction 240-110-36, Personnel Security

· DISA Instruction 240-110-38, Industrial Security

· DISA Instruction 240-110-43, Insider Threat Program

· DISA Instruction 240-110-8, Information Security

· DISA Instruction 630-230-19, Cybersecurity

· DISA Policy Letter, Unauthorized Connections to Network Devices, 11 September 2013

· AE REG 190-16 Installation Access Control

· AE REG 525-13 Antiterrorism

· AE REG 604-1 Local National Screening Program in Germany

· AR 190-51 Security of Unclassified Army Property

· AR 380-5 Army Information Security Program

· DoD 5200.2-R DoD Regulation – Personnel Security Program

· DoD 5205.02-M DoD Manual – Operations Security (OPSEC) Program Manual

· DoD 5220.22-M, National Industrial Security Program Operating Manual, February 2006 Incorporating Change 18 May 2016

· IC Tech Spec‐for ICD/ICS 705 Technical Specifications for Construction and Management of Sensitive Compartmented Information Facilities

· ICD 705 Sensitive Compartmented Information Facilities

· ICS 705-1 Physical and Technical Security Standards for Sensitive Compartmented Information Facilities

· ICS 705-2 Standards for the Accreditations and Reciprocal Use of Sensitive Compartmented Information

11.2 Facility Security Clearance

The work to be performed under this contract is up to Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility for some personnel. Therefore, the contractor shall have at the time of contract award and prior to commencement of classified work, a Top Secret Facility Security Clearance (FCL).

11.3 Personnel Clearance

Work executed and documents developed under this TO may be classified up to Secret. All personnel under this TO will need a Secret clearance. For physical access into Sensitive Compartmented Information (SCI) a Top Secret / Sensitive Compartmented Information (SCI) clearance is required.

The personnel security requirements for this contract cover the individuals supporting the Task Areas delineated in the table below. Contractor personnel must possess the interim or final security clearance eligibility delineated in the table below when performance starts.

The following publications, manuals, regulations

11.4 Investigation Requirements

All personnel requiring Top Secret and SCI access under this contract/order shall undergo a favorably adjudicated Tier 5 (T5) investigation (formerly known as a SSBI) as a minimum requirement. All personnel requiring Secret access under this contract/order shall undergo a favorably adjudicated Tier 3 (T3) Investigation formerly known as a National Agency Check, Local Agency Check and Credit Check or Access National Agency Check and Inquiries as a minimum investigation.

11.5 Visit Authorization Letters (VAL)

Visit requests shall be processed and verified through the Defense Information Security System (DISS) to USEUCOM Security Manager Office (SMO) Code W092AA4 for USAG Stuttgart USEUCOM spaces. For the other USEUCOM sites, the SMO codes will be provided to the contractor 30 days prior to site visit. DISS visits for contracts/orders are identified as “Other” or Temporary Assignment Duty (TAD) / Temporary Duty (TDY) and will include the Contract/Order Number and IT-Access level of the contract/order in the Additional Information section. Contractors that do not have access to DISS may submit visit authorizations by e-mail in a password protected .pdf to the COR or Alternate COR specified in Section 1.0.

If DISS is not available, the VAL must contain the following information on company letterhead

· Company name, address, telephone number, assigned Commercial and Government Entity (CAGE) Code, facility security clearance

· CAGE Code

· Contract/Order Number

· Name, Social Security Number, date and place of birth, and citizenship of the employee intending to visit

· Certification of personnel security clearance and any special access authorizations required for the visit (type of investigation & date, adjudication date & agency, and IT access level)

· Name of COR/Alt COR

· Dates or period the VAL is to be valid Top Secret SCI visit requests shall be processed via the US Army Contractor Support Element Army Centralized Contracts and Security (ACCS) Portal to USAG Stuttgart USEUCOM SCI spaces SMO Code W092AA2. For the other USEUCOM SCI sites, the SMO codes will be provided to the contractor 30 days prior to site visit. DISS visits request for task orders are identified as “Other” or “TAD/TDY” and will include the Task Order Number of the contract/order in the Additional Information section.

11.6 Security Contacts

USEUCOM Security Personnel can be contacted for Personnel Security related at:

SSO Non Secure Internet Protocol Router (NIPR): USEUCOM.stuttgart.ecj2.mbx.sso-persec@mail.mil SSO SIPR: USEUCOM.stuttgart.ecj2.mbx.sso-persec@mail.smil.mil Or via mail at:

United States European Command (USEUCOM) ECJ24-SSO Personal Security Unit 30400

APO AE 09131-0400

11.7 Badge Access

Badge access will be provided to the contractor employees who have approved visit requests through DISS and/or ACCS.

12. Government Furnished Property (GFP)/Government-Furnished Equipment (GFE)/ Government-Furnished Information (GFI) N/A

13. Other Pertinent Information or Special Considerations

13.1 Applicable Publications

· DISA Approved Products List https://aplits.disa.mil/processAPList.action

· 2nd Theater Signal Brigade Cabling Distribution System (CDS/ICDS) Guide June 2017

· AE REG 25-1 Army in Europe Information Technology

· AE REG 25-13 Army in Europe Telecommunications and Unified Capabilities

· AE REG 25-2 Army in Europe Information Assurance

· BICSI Information Technology Systems Installation Methods Manual (ITSIMM) 8th Edition

· BICSI Telecommunications Distribution Methods Manual (TDMM), 14th Edition

· CNSSAM TEMPEST/1-13 Red Black Installation Guidance, 17 January 2014

· CNSSI No. 7003 Protected Distribution Systems (PDS) (September 2015)

· DoD 8100.04 DoD Instruction Unified Capabilities

· DOD DIRECTIVE 8140.01 Cyberspace Workforce Management, October 5, 2020

· DOD MANUAL 8140.03 Cyberspace Workforce Qualification and Management Program, February 15, 2023

· DoD 8570.01-M Information Assurance Workforce Improvement Program

· DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March 2020

· DoDD 5205.02E DoD Directive – Operations Security (OPSEC) Program, August 20, 2020

· DoDD 8570.01 DoD Directive – Information Assurance Training, Certification, and Workforce Management, November 10, 2015

· DoDI 8500.01 DoD Instruction – Cybersecurity, October 7, 2019

· DoDI 8510.01 DoD Instruction – Risk Management Framework (RMF) for DoD Systems, July 19, 2022

· EIA 310-D Cabinets, Racks, Panels, and Associated Equipment

· IC Tech Spec‐for ICD/ICS 705 Technical Specifications for Construction and Management of Sensitive Compartmented Information Facilities

· ICD 705 Sensitive Compartmented Information Facilities

· ICS 705-1 Physical and Technical Security Standards for Sensitive Compartmented Information Facilities

· ICS 705-2 Standards for the Accreditations and Reciprocal Use of Sensitive Compartmented Information

· IEEE 142-2007 Recommended Practice for Grounding of Industrial and Commercial Power Systems

· IEEE C2-2023 National Electrical Safety Code

· IEEE/ISO/IEC 12207-2008 International Standard - Systems and software engineering -- Software life cycle processes

· Installation and Campus Area Network (ICAN) Design Guide (June 2012)

· ISO 9001 (ANSI/ASQ Q9001) International Organization for Standardization (American National Standard Institute/American Society for Quality) – Quality Management Systems, Requirements

· ISO/IEC 12207 International Organization for Standardization/ International Electrotechnical Commission: Systems and Software Engineering – Software Life Cycle Processes

· ISO/IEC 15288 International Organization for Standardization/ International Electrotechnical Commission: Systems and Software Engineering – System Life Cycle Processes

· National Institute of Standards and Technology (NIST), Framework for Improving Critical Infrastructure Cybersecurity. Version 1.1

· SIPH v4.1 Shore Installation Process Handbook (SIPH), Version 4.1

· SPEG v1.8 System Operational Verification Test (SOVT) Preparation and Execution Guide (SPEG) for Ship, Shore, and Submarine Installations

· TIA/EIA 568 Commercial Building Telecommunications Cabling Standard

· TIA/EIA 569 Telecommunications Pathways and Spaces

· TIA-942/TIA-942-A-1 Telecommunications Infrastructure Standard for Data Centers

· UFC 3-580-01 Telecommunications Building Cabling Systems Planning and Design, June 1, 2016

· USACE ECB 2007-22 Army Installation Information Infrastructure Architecture (I3A) Guide

· USAISEC I3A Technical Criteria for the Installation Information Infrastructure Architecture

14. Section 508 Accessibility Standards The following Section 508 Accessibility Standard(s) are applicable to this acquisition.

Functional Performance Criteria:

· 301.1 Scope - The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

· 302.1 Without Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

· 302.2 With Limited Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

· 302.3 Without Perception of Color - Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

· 302.4 Without Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

· 302.5 With Limited Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

· 302.6 Without Speech - Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

· 302.7 With Limited Manipulation - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

· 302.8 With Limited Reach and Strength - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

· 302.9 With Limited Language, Cognitive, and Learning Abilities - ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

Page 1 of 37 Pages

Page 2 of 37 Pages