WTCS_DO1_Statement_of_Work_22_NOV_2019.pdf

SOW-2019-045

22 NOV 2019

DISTRIBUTION LIST STATEMENT A:

Approved for public release; distribution is unlimited.

Statement of Work

For

Wideband Training & Certification System (WTCS)

Version 2 (V2)

Delivery Order 0001

U.S. Army Program Executive Office

Simulation, Training, and Instrumentation (PEO STRI)

12211 Science Drive

Orlando, FL 32826-3276

X

Benjamin Little Systems Engineer, PdM VTS

Colleen Matthews Chief Engineer, PdM VTS

Rob Briar Logistics Management Specialist, PdM

VTS

Matthew Brothers, Jr Product Support Manager, PM ST

Lisa Bird Assistant Product Manager, PdM VTS

LTC Edgar O. Santana Product Manager, PdM VTS

Revision Number Date Log of Changes Made and Description of

Reason Changes Approved By

1.0 26 AUG

RPSR Release

2.0 22 NOV 19 Updated paragraph 3.6.2 per ACC-Orlando and PEO STRI Legal Comments

Table of Contents

1. GENERAL INFORMATION

1.1 Scope

1.2 Background

2. APPLICABLE DOCUMENTS

2.1 Department of Defense Specifications

2.2 Department of Defense Standards:

2.3 Department of Defense Directives

2.4 Department of Defense Instructions

2.5 Other Government Documents, Drawings and Publications

2.6 Non-Government Standards and Other Publications

3. REQUIREMENTS

3.1 Specific Requirements

3.1.1 Networking WTCS

3.1.2 Option for WTCS Workstation Production

3.2 General Requirements

3.2.1 Program Management

3.2.1.1 Integrated Master Plan (IMP)

3.2.1.2 Integrated Master Schedule (IMS)

3.2.1.3 Financial Management

3.2.1.3.1 Integrated Baseline Review

3.2.1.4 Organizational Process Management

3.2.1.5 Configuration Management

3.2.1.5.1 Configuration Management Planning and Management

3.2.1.5.2 Configuration Identification

3.2.1.5.3 Technical Data Package

3.2.1.5.4 Drawing Tree

3.2.1.5.5 Configuration Change Management and Reporting

3.2.1.5.6 Configuration Control Documents

3.2.1.5.7 Configuration Status Accounting

3.2.1.5.8 Configuration Validation and Audit

3.2.1.5.9 Contractor Internal Hardware Build-Up Audit

3.2.1.5.10 Physical Configuration Audit (PCA)

3.2.1.5.11 Government Sample Audit to Verify Product Baseline

3.2.1.5.12 Configuration Audit Reporting

3.2.1.5.13 Software Configuration Management

3.2.1.5.14 Software Configuration Control Board

3.2.1.5.15 Software Item Database

3.2.1.5.16 Software Configuration Management Database

3.2.1.5.17 Participation in Satellite Communications (SATCOM) Community Configuration Control Activities 18

3.2.1.5.18 System Engineering Interface

3.2.1.5.19 Engineering Change Proposals (ECP)

3.2.1.5.20 Engineering Change Proposal Review

3.2.1.5.21 Variances

3.2.1.6 Risk Management

3.2.1.7 Management Reviews

3.2.1.7.1 Post Award Conference (PAC)/Start of Work Meeting

3.2.1.7.2 Program Management Reviews

3.2.1.7.3 Technical Interchange Meetings (TIMs)

3.2.1.8 Intellectual Property Rights

3.2.1.9 Government Furnished Information (GFI)

3.2.1.10 Government Furnished Property (GFP)

3.2.1.11 Visitor Support

3.2.2 Systems Engineering

3.2.2.1 System Design

3.2.2.1.1 System Definition Stage

3.2.2.1.2 Preliminary Design Stage

3.2.2.1.3 Detailed Design Stage

3.2.2.1.4 Fabrication, Assembly, Integration and Test Stage

3.2.2.2 Hardware Engineering

3.2.2.3 Software Engineering

3.2.2.3.1 Software Requirements and Architecture Development and Review

3.2.2.3.2 Software Design and Implementation

3.2.2.3.3 Software Development Test

3.2.2.3.4 Software Integrity Certification

3.2.2.3.5 Software Non-Recurring Licensing

3.2.2.3.6 Software Deliverable

3.2.2.4 Hardware and Software Integration

3.2.2.5 Cybersecurity

3.2.2.5.1 Cybersecurity Hardware and Software Purchases

3.2.2.5.2 Cybersecurity Artifacts

3.2.2.5.3 Information Assurance Vulnerability Management Program

3.2.2.5.4 Cybersecurity Process and Controls

3.2.2.5.5 Cybersecurity Control Review/RMF Implementation Plan Review (RIPR)

3.2.2.5.6 Contractor Security Control Assessment (SCA) Event Dry-Run

3.2.2.5.7 SCA Event Readiness Review

3.2.2.5.8 Security Control Assessment (SCA) Event

3.2.2.5.9 Host-Based Security System (HBSS)

3.2.2.5.10 Cybersecurity Contractor Training and Certification

3.2.2.6 Specialty Engineering

3.2.2.6.1 Testability Engineering

3.2.2.6.2 Safety Engineering

3.2.2.6.3 Safety Assessment

3.2.2.6.4 Inspection and Verification

3.2.2.6.5 SAR Updates

3.2.2.6.6 Hazards Tracking and Risk Resolution

3.2.2.6.7 Health Hazard Assessment

3.2.2.6.8 Producibility Engineering

3.2.2.6.9 Quality Engineering

3.2.2.6.10 Human Factors Engineering

3.2.2.6.11 Electromagnetic Environmental Effects (E3)

3.2.2.7 Hardware (HW) Standardization

3.2.2.7.1 Obsolescence Management

3.2.2.7.2 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.2.2.8 Design Reviews

3.2.2.8.1 System Requirements Review (SRR)

3.2.2.8.2 Preliminary Design Review (PDR)

3.2.2.8.3 Critical Design Review (CDR)

3.2.2.9 Product Definition Data (PDD)

3.2.3 Logistics

3.2.3.1 Logistics and Supportability Integrated Project Team (IPT)

3.2.3.2 Logistics and O&S Cost Reduction Reviews

3.2.3.3 Considerations for Tradeoffs

3.2.3.4 Maintenance Concept

3.2.3.5 Logistics Product Data (LPD) and LPD Reports

3.2.3.6 Recommended Spares

3.2.3.7 Technical Publications (TPs)

3.2.3.7.1 Technical Publications Technical Interchange Meetings (TIMs)

3.2.3.7.2 Electronic Technical Manuals (ETM)

3.2.3.7.3 Commercial-Off-the-Shelf Manuals (COTS)

3.2.3.7.4 ETM 40% In Process Review (IPR)

3.2.3.7.5 ETM 80% In Process Review (IPR)

3.2.3.7.6 ETM and COTS Manual Validation

3.2.3.7.7 ETM and COTS Manual 100% Verification

3.2.3.8 Item Unique Identification (IUID)

3.2.3.9 Development Software Support Environment

3.2.3.10 Training Products

3.2.3.10.1 Interactive Multimedia Instruction (IMI)

3.2.3.10.2 Training Technical Interchange Meetings (TIMs)

3.2.3.10.3 New Equipment Training (NET)

3.2.3.11 Refresher Training

3.2.3.12 Warranties and Licenses

3.2.4 Interim Contractor Support (ICS)

3.2.4.1 Cybersecurity ICS

3.2.4.2 On-Call Telephone Support

3.2.4.3 ICS Hardware and Software Shipments

3.2.4.4 ICS Software Support

3.2.4.5 Additional Engineering Support

3.2.4.6 Transition of GFP and CAP

3.2.5 Integrated Testing

3.2.5.1 Contractor Dry-Run Testing

3.2.5.2 Test Readiness Review (TRR)

3.2.5.3 Cybersecurity Compliance for Testing

3.2.5.4 First Article Test (FAT)

3.2.5.5 In-Plant Acceptance Test (IPAT)

3.2.5.6 System Readiness Testing (SRT)

3.2.5.7 Site Acceptance Test (SAT)

3.2.5.8 Test Discrepancies

3.2.5.8.1 Discrepancy Processing

3.2.5.8.2 Test Discrepancy Severity

3.2.6 Site Installation

3.2.6.1 Site Survey

3.2.6.2 Site Preparation

3.2.6.3 Packing, Handling, Storage, and Transportation (PHST)

3.2.6.4 WTCS Installation

3.2.6.5 Removal of Equipment

3.2.7 WTCS Support

3.2.8 Security and General Protection

3.2.8.1 Access and General Protection Policy and Procedures

3.2.8.1.1 Common Access Card (CAC)

3.2.8.1.2 Non-Credentialing

3.2.8.2 Security Clearance

3.2.8.3 Security Training Requirements

3.2.8.3.1 Anti-Terrorism (AT) Level 1 Training

3.2.8.3.2 iWATCH Training

3.2.8.3.3 OPSEC Training

3.2.8.3.4 Information Assurance/Information Technology Certification

3.2.8.3.5 Threat Awareness Reporting Program (TARP) Training

3.2.8.4 Handling/Access to Classified Information

3.2.8.5 OCONUS Travel Security Requirements

APPENDIX A - Review Entry and Exit Criteria and Data Products

A.1 SRR Entry Criteria

A.2 SRR Completion/Exit Criteria

A.3 SRR Products

A.4 PDR Entry Criteria

A.5 PDR Completion/Exit Criteria

A.6 PDR Products

A.7 CDR Entry Criteria

A.8 CDR Completion/Exit Criteria

A.9 CDR Products

A.10 TRR Entry Criteria

A.11 TRR Exit Criteria

Statement of Work

For Wideband Training & Certification System (WTCS)

Version 2 (V2) Delivery Order 01

1. GENERAL INFORMATION

1.1 Scope

This Delivery Order (DO) Statement of Work (SOW) establishes responsibilities for performance of the tasks related to the design, integration, production, testing, management, documentation, delivery, installation, and sustainment for Wideband Training and Certification System (WTCS) Version 2 (V2).

The general tasks that Project Manager Soldier Training (PM ST) desires to have performed under WTCS

V2 DO 01:

• Networking WTCS workstations between sites

• Options for production of WTCS workstations

• Architecture Evolution

• Software Integration

• Hardware Integration

• Production

• Testing

• Fielding

• Installation

• Refresher Training

• Interim Contractor Support (ICS)

• Technical Documentation Updates

• Cybersecurity

1.2 Background

The U.S. Army Program Executive Office for Simulation Training and Instrumentation (PEO STRI), Project Manager Soldier Training (PM ST) and Product Manager Virtual Training Systems (PdM VTS) have a requirement to modernize the existing WTCS. The WTCS is an interactive training system to train military and/or civilian operators on the Wideband Satellite Operational Management System (WSOMS) and its associated management, payload control, and planning subsystems. The WSOMS is built around a fast moving, constantly changing, set of requirements, therefore modularity is paramount in the architecture of the WTCS in order to provide the flexibility to expeditiously pursue required training modifications when sufficient data associated with each change is available. The WTCS must be kept up-to-date to support training in the dynamic environment of satellite control.

The WTCS is used to support the Army's Military Occupational Specialty (MOS) 25S with the Additional Skill Identifier (ASI) 1C.

2. APPLICABLE DOCUMENTS

2.1 Department of Defense Specifications

Copies are available on the WWW at URL: http://quicksearch.dla.mil.

2.2 Department of Defense Standards:

MIL-STD-130N Change 1, 16 November 2012, Identification Marking of U.S. Military Property

MIL-STD-31000B, 31 October 2018, Technical Data Packages

MIL-STD-40051-2C, 15 December 2015, Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)

Copies are available on the WWW at URL: http://quicksearch.dla.mil.

2.3 Department of Defense Directives

Copies are available on the WWW at URL: https://www.esd.whs.mil/dd/

2.4 Department of Defense Instructions

DoDI 5000.2, 31 August 2018 (Change 4), Operation of the Defense Acquisition System

DoDI 8500.01, 14 March 2014, Cybersecurity

DoDI 8510.01, 28 July 2017 (Change 2), Risk Management Framework (RMF) for DoD Information Technology (IT)

DoDI 8582.01, 6 June 2012, Security of Unclassified DoD Information on Non-DoD Information systems.

Copies are available on the WWW at URL: https://www.esd.whs.mil/DD/

2.5 Other Government Documents, Drawings and Publications

DAG, Defense Acquisition Guidebook: https://dag.dau.mil/Pages/Default.aspx

DISR, Department of Defense (DoD) Information Technology Standards Registry.

Copies are available on the WWW at URL http://www.dsp.dla.mil/Specs-Standards/List-of-DISR-documents/

CNSSP 11, 1 June 2015, Acquisition of Information Assurance (IA) and IA-Enabled Information Technology (IT) Products.

Copies are available on the WWW at URL https://www.cnss.gov/CNSS/openDoc.cfm?uwnVIG2JEfxsFnYW43qdhw== AR 380-5, 29 September 2000, Department of the Army Information Security Program.

Copies are available on the WWW at URL https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/r380_5.pdf http://quicksearch.dla.mil/ http://quicksearch.dla.mil/ https://www.esd.whs.mil/dd/ https://www.esd.whs.mil/DD/ https://dag.dau.mil/Pages/Default.aspx http://www.dsp.dla.mil/Specs-Standards/List-of-DISR-documents/ http://www.dsp.dla.mil/Specs-Standards/List-of-DISR-documents/ https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/r380_5.pdf

AR 25-2, 4 April 2019, Army Cybersecurity .

Copies are available on the WWW at URL https://armypubs.army.mil/ProductMaps/PubForm/Details.aspx?PUB_ID=1002626

AR 200–1, 13 December 2007, Environmental Protection and Enhancement Copies are available on the WWW at URL https://armypubs.army.mil/ProductMaps/PubForm/AR.aspx

AR 602-2, 27 January 2015, Human Systems Integration in the System Acquisition Process.

Copies are available on the WWW at URL https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/r602_2.pdf

AR 750-1, 3 August 2017, Army Materiel Maintenance Policy Copies are available on the WWW at URL https://armypubs.army.mil/ProductMaps/PubForm/AR.aspx

TRADOC PAM 350-70-12, 3 May 2013, The Army Distributed Learning (DL) Guide, https://www.tradoc.army.mil/Publications-Resources/

TRADOC Pamphlets.

Copies are available on the WWW at URL http://www.tradoc.army.mil/tpubs/pamndx.htm

DA PAM 25-1-2, 6 June 2012, Information Technology Contingency Planning.

Copies are available on the WWW at URL https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/PAM%2025-1-2.pdf

DoD 8570.01-M, 10 November 2015 (Change 4), Information Assurance Workforce Improvement Program Copies are available on the WWW at URL https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/857001m.pdf

DoD 5220-22-M, 18 May 2006, National Industrial Security Program Operating Manual Copies are available on the WWW at URL https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/522022M.pdf

WTCS Instructional Media Development Plan (IMDP) v2.1

WTCS Interface Design Description (IDD), Rev 3, 31 August 2017

WTCS System Subsystem Specification (SSS) v7

WTCS Database Design Description (DBDD), Rev 3, 31 August 2017

WTCS Software Design Description (SDD), Rev 3, 31 August 2017

WTCS Logistics Product Data (LPD), Rev 2

WTCS Safety Assessment Report (SAR), Rev 3, 1 November 2017

WTCS Product Drawings, Rev 3, 6 October 2017 https://armypubs.army.mil/ProductMaps/PubForm/Details.aspx?PUB_ID=1002626 https://armypubs.army.mil/ProductMaps/PubForm/AR.aspx https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/r602_2.pdf https://armypubs.army.mil/ProductMaps/PubForm/AR.aspx https://www.tradoc.army.mil/Publications-Resources/ http://www.tradoc.army.mil/tpubs/pamndx.htm https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/PAM%2025-1-2.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/857001m.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/522022M.pdf

WTCS Instructor/Maintainer Training Course Materials/Products Rev 3, 13 July 2018

WTCS Operator Training Course Materials/Products Rev 3, 13 July 2018

MIL-PRF-32216A, 7 June 2016, Evaluation of Commercial Off-the-Shelf (COTS) Manuals and Preparation of Supplemental Data

Request for copies shall be addressed to Army Contracting Command (ACC) Orlando, ACC-ORL-OPA, 12211 Science Drive, Orlando, FL 32826-3224.

2.6 Non-Government Standards and Other Publications

ANSI/EIA-748C-2013, Earned Value Management System

ANSI/EIA-649, National Consensus Standard for Configuration Management

SAE GEIA-STD-0007-B, May 2013, Logistics Product Data

SAE GEIA-HB-0007-B, February 2014, Logistics Product Data Handbook

SAE TA-HB-0007-1, May 2013, Logistics Product Data Reports Handbook

Copies are available on the WWW at URL: https://www.ansi.org/

3. REQUIREMENTS

3.1 Specific Requirements

This section defines the specific requirements for the tasks governed by this WTCS Delivery Order.

3.1.1 Networking WTCS

The Contractor shall modify the WTCS baseline to provide network connectivity between the WTCS located at the Wideband SATCOM Operations Centers (WSOC) and Headquarters (53rd Signal Battalion/1st Space Brigade). The Contractor’s networking solution shall be IAW the WTCS System Requirements Document (SRD). The Contractor shall deliver the Government approved WTCS networking solution IAW Section F of the Delivery Order.

3.1.2 Option for WTCS Workstation Production

The Contractor shall provide the system engineering, materials, equipment, facilities, testing, technical management, cybersecurity, logistics, manufacturing, and clerical support for configuration, integration, production, testing, and installation of WTCS workstations IAW the WTCS Product Drawings . The Contractor shall deliver the WTCS workstations IAW Section F of the Delivery Order.

3.2 General Requirements

3.2.1 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 track program progress utilizing metrics. The Contractor shall plan, implement, and maintain a life cycle cost (LCC) management process https://www.ansi.org/ to minimize the system cost and use LCC to conduct trade studies, evaluate design and support alternatives, and select the resource support requirements. The Contractor shall define and monitor metrics to evaluate the performance of each critical technical and management process and conformance of the evolving products with contract requirements and objectives including cost requirements and objectives.

(DI-MGMT-80227) Contractor’s Progress, Status and Management Report

3.2.1.1 Integrated Master Plan (IMP)

The Contractor shall implement, manage to, update, and maintain the contract IMP. The Contractor shall develop the system IAW the IMP. The Contractor shall use the IMP throughout the contract as a management tool to assess progress and determine success in achieving program requirements. The Contractor shall report on work in progress IAW the IMP at each program review, at selected technical reviews and at Government discretion. The IMP shall depict the contract work breakdown structure.

3.2.1.2 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, shall be traceable to the IMP, and shall contain all critical events and exit criteria, accomplishments, predecessors and successors events, and their dependencies. The Contractor shall document the planning and scheduling effort, related Government responsibilities, and the interaction for the efforts required for development and delivery of the training products. The Contractor shall integrate contract deliverables and dates that the Contractor needs support from the Government Subject Matter Experts (SMEs) into the IMS. The IMS shall address total program activities including activities performed by major sub-contractors. The Contractor shall construct the IMS to ensure that milestones and deliveries meet contractual requirements. 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. The Contractor shall key these network activities to the Contract Work Breakdown Structure (CWBS). The network shall be implemented 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 Contractor shall update the network activities time and cost data 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. The Contractor shall deliver the IMS IAW Exhibit A of the Delivery Order.

(DI-MGMT-81861) Integrated Program Management Report (IPMR) Integrated Master Schedule (IMS) Format 6 (DI-MGMT-81861) Integrated Program Management Report (IPMR) Work Breakdown Structure Format 1

3.2.1.3 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 provide a detailed Program Work Breakdown Structure (PWBS) to define the lower level components of items to be procured and include all the product elements (hardware, software, data, or services).

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.

(DI-MGMT-81468) Contract Funds Status Report (CFSR) (DI-MGMT-81651) Contract Invoicing and Payment Report (DI-MGMT-81861A) Integrated Program Management Report (IPMR) Work Breakdown Structure Format 1

3.2.1.3.1 Integrated Baseline Review

The Contractor shall participate with the Government in the assessment of program risk and the degree to which the following are established:

a. Technical scope of work is fully included and is consistent with authorizing documents.

b. Project schedule key milestones are identified and supporting schedules reflect a logical flow to accomplish the work.

c. Resources (budget, facilities, personnel, skills, etc.) are available and are adequate for the assigned tasks.

d. Tasks are planned and can be measured objectively relative to the technical progress.

e. Rationales underlying the review are reasonable.

f. Management processes support successful execution of the project.

3.2.1.4 Organizational Process Management

The Contractor shall use organizational processes equivalent to Capability Maturity Model Integration (CMMI) level 3 or higher. The Contractor shall present an overview of their organizational processes at the Post Award Conference/Start of Work Meeting.

3.2.1.5 Configuration Management

The Contractor shall use ANSI/EIA-649 to establish processes and tools to establish and maintain consistency between system requirements, system configuration information, and all relevant information about the system. The consistency established through the Configuration Management process shall ensure that the system conforms to the requirements. The Contractor shall identify and document the system in sufficient detail to support the system life cycle. This shall ensure component interchangeability, accurate system information, and safety of system operation & maintenance. The Contractor shall define the performance, functional, and physical attributes in configuration documentation. As the configuration information becomes more detailed and definitive as the life cycle progresses, the Contractor shall define configuration baselines. The Contractor shall archive the defined attributes in the baseline in an integrated database. Both the system and its information shall be verified for consistency. The Contractor shall identify and evaluate the impact of all proposed changes through the configuration change management process, including the verification that the system and all associated component information have been updated and continue to be consistent. The Contractor shall plan implementation of the Configuration Management functions for the context and environment in which they are to be performed and then manage in accordance with the planning.

3.2.1.5.1 Configuration Management Planning and Management

The Contractor shall establish processes and tools to establish and maintain hardware and software configuration baselines prior to acceptance of the Product Baseline (PBL) by the Government.

The Contractor shall maintain all current and all historical release information for all configuration items and their component parts. The engineering release system shall interrelate with the Contractor’s internal system of controls to assure the incorporation of all approved Class I engineering changes as specified. The configuration identification for the PBL shall be as established by data specified in the WTCS technical data package (TDP).

After successful completion of formal qualification test and acceptance activities and a Physical Configuration Audit (PCA), the control of the PBL shall transition to Life Cycle Contractor Support (LCCS). Thereafter, the Contractor must receive approval from the Configuration Manager prior to making any changes to the PBL.

(DI-SESS-82019) Product Baseline Index (PBLI)

3.2.1.5.2 Configuration Identification

The Contractor shall identify unique identifiers for selected system attributes, system information and components to be used as the basis for configuration management. The Contractor shall:

a. Define the functional, performance, interface and physical attributes of the system and components.

b. Determine the systems composition using its product definition information.

c. Assign unique identifiers to configuration items so that they can be distinguished from other items, one configuration of the system can be distinguished from another, the source of a component can be determined, and the correct system definition information can be retrieved.

d. Assign unique unit identifiers to individual components of the system.

e. Update component identifiers when a system is modified reflecting the new configuration without altering the system identifier and model identifier.

f. Uniquely identify information so that it can be correctly associated with the applicable configuration of the system.

g. Apply information identification rules to maintain representation and version relationships.

h. Maintain relationships between information, information requirements, and the related system configuration to ensure accurate information retrieval.

i. Establish complete, valid, and suitable for use agreed-to descriptions of the attributes of the system and components at a point in time and provide a known configuration to which changes can be addressed.

j. Identify interfaces and establish mutually agreed-to control of common attributes for system or component boundaries that interface to the system or within the system.

The Contractor's configuration management system shall meet the minimum information content requirements as specified below:

a. Elements of data required for hardware items. The Contractor's engineering release records for hardware items shall contain the following information.

i. Configuration Item (CI) elements:

(a) CI identifier

(b) Delivered CI serial numbers

(c) Top assembly drawing number

(d) CI specification identification number.

ii. Drawing elements:

(a) Drawing number

(b) Drawing title

(c) CAGE number

(d) Number of sheets

(e) Date of release

(f) All released change letters

(g) Date of each change letter release

(h) Each effecting change document numbers.

iii. Part number elements:

(a) Controlling drawing number

(b) Component part numbers released.

b. Elements of data required for software items. The Contractor's engineering release records shall reference the software configuration item in the Software Version Description (SVD).

3.2.1.5.3 Technical Data Package

The Contractor shall prepare and deliver all product related technical data such as product drawings (either specification control or source control drawings) and associated lists, and commercial/product component parts information adequate to reproduce/manufacture the final delivered and accepted WTCS as a TDP. Acceptance and/or inspection data as well as any supplementary quality assurance provisions shall be provided. The Contractor is responsible for the updating and revision of all product related technical data as a result of engineering changes during the production of the first articles. In process reviews of TDP data will be conducted by the Government in conjunction with formal implementation reviews and/or audits. The Contractor shall prepare and submit the WTCS TDP to the Government IAW Exhibit A.

(DI-SESS-80776A) Technical Data Package

3.2.1.5.4 Drawing Tree

The Contractor shall prepare and submit a Drawing Tree to the Government as an attachment to the TDP IAW Exhibit A. The drawing tree will be prepared in Top down/Breakdown format and will include Functional Group Codes.

(DI-DRPR-81961) Engineering Drawing Tree

3.2.1.5.5 Configuration Change Management and Reporting

The Contractor shall establish a systematic and measurable configuration change management process for managing product configuration changes and variances. Once the system requirements have been approved by an authorized management activity, the Contractor shall effect changes to the baseline requirements only after the proposed change has been approved using the change process. The Contractor shall report to the Government during meetings and reviews conducted IAW this effort, information describing proposed changes to identified internal hardware and software configuration baselines, and identify when and how those changes were implemented or otherwise dispositioned. The Contractor shall maintain a record of any changes made to individual quantitative requirements from the values stated in the System Specification that occur as internal baselines are developed and revisions are made to those baselines. The Contractor shall cross-reference those changes to specific activities and events in which the need for such changes was discovered and the change approved. This data shall be discussed at reviews and Technical Interchange Meetings (TIM), and delivered as part of the approved PB. The Contractor shall:

a. Document and uniquely identify each change.

b. Classify requested changes to aid in determining the levels of review and approval.

c. Clearly and completely document request for change.

d. Consider the technical, support, schedule, and cost impacts of a requested change before making a judgment to approve the change for implementation and incorporation in the system and its documentation.

e. Determine potential effects of a change and coordinate impacts with the impacted areas of responsibility.

f. Determine the effectivity for each change and identify which units of the system are to be changed, the point of production break-in, and which units will be included in a retrofit.

g. Verify implementation of a change to ensure consistency between the system, its documentation, and its support elements.

h. Document variances, when authorized by the appropriate level of authority.

3.2.1.5.6 Configuration Control Documents

The Contractor shall prepare and submit Configuration Control Documents (CCDs) to the Government IAW Exhibit A for approval when the Contractor determines that a change to the Functional Baseline (FB) or the Government approved PB is necessary. The Contractor shall not implement changes without the receipt of a formal approval from the Government. Such approval may modify the requested change(s).

(DI-MISC-80711A) Scientific and Technical Reports (Configuration Control Documents)

3.2.1.5.7 Configuration Status Accounting

The Contractor shall provide access to accurate, timely information about the system and its documentation. The Contractor shall correlate, store, maintain, and provide readily available views and information of system configuration information including pending, current and historical data. The Contractor shall:

a. Systematically record, safeguard, validate, and disseminate system information.

b. Establish methods, processes and procedures to provide controlled access to system information.

c. Capture configuration information as it evolves.

3.2.1.5.8 Configuration Validation and Audit

The Contractor shall verify and audit the system configuration information to ensure that requirement attributes are met and accurately documented. The Contractor shall:

a. Validate the system attributes through a systematic comparison with the associated results of system tests, analyses, inspections, demonstrations or simulation models.

b. Maintain surveillance over the configuration management process to ensure it is being followed and remains in compliance with requirements.

c. Assist the Government during the Physical Configuration Audit (PCA).

3.2.1.5.9 Contractor Internal Hardware Build-Up Audit

Concurrent with manufacture of piece parts and incoming inspection of procured parts, a 100% audit shall be conducted by personnel approved by the QA Manager to verify the as-built configuration matches the design documentation prior to use of each part in production. During this process each product definition document will also be examined for proper format (compliance with ANSI Y14 series standards), completeness, and currency of material references, accuracy of piece part identification, and adequacy of manufacturing instructions and any other information critical to acquire a like part. A record of each product attribute verified shall be maintained and available through the IDE.

3.2.1.5.10 Physical Configuration Audit (PCA)

The Contractor and Government shall jointly conduct a PCA in the Contractor’s plant or the Wideband Integration Center (WIC) at the completion of all security compliance and system performance verification activities. The PCA shall ensure that the physical configuration items evaluated for delivery to the Government are in agreement with all of the configuration identification documents and media intended to be delivered, and all such documents are IAW the objectives of this contract as described in the SRD. The Contractor shall conduct an audit of the system wiring to verify accuracy to system wiring diagrams and a physical inspection and inventory of system components to verify the accuracy of system drawings. The audit shall be conducted NLT 15 business days after the acceptance by the Government of all verification testing results. The Government’s prerequisites to the conduct of the PCA are described below. These conditions must be met NLT 30 business days prior to the conduct of the PCA.

a. Engineering drawings, associated lists, and vendor item/control specifications made available for Government review.

b. Isolation of the item(s) (specific serial numbers) to be reviewed established.

c. Unencumbered access provided to the facilities to be used for inspection, fabrication, production, assembly, testing.

d. Access provided to all documents referenced by engineering drawings, inspection reports, process sheets and other applicable data.

Acceptance of the WTCS and any of the associated system documentation will not occur until the PCA is approved by the Government.

3.2.1.5.11 Government Sample Audit to Verify Product Baseline

After completion of acceptance testing and any required design modifications, but prior to formal acceptance, the Government will verify final product baseline by reviewing a representative number of drawings, associated technical manuals, logistics management information and manufacturing instructions to determine their accuracy IAW the final product configuration design. Based on comments from the Government during this review, the Contractor shall update documentation and drawings in order to ensure they are IAW the final product configuration design.

3.2.1.5.12 Configuration Audit Reporting

The Contractor shall produce and deliver a Configuration Audit Summary Report on all of the CI that are to be delivered to the Government or individual Configuration Audit reports for each configuration item to be delivered.

3.2.1.5.13 Software Configuration Management

The Contractor shall establish and document a software configuration management process. The Contractor’s software configuration management plan may be incorporated into the software development process plans or may be a separate configuration management plan.

3.2.1.5.14 Software Configuration Control Board

The Contractor shall establish and maintain a software configuration control board or equivalent responsible for configuration control of its software configuration items and related software products.

The software configuration control board will be responsible for COTS (including open source) management including product and version identification. The Contractor shall obtain approval of the system Integrated Product Team (IPT) prior to committing to use any version of any COTS product. The Contractor shall ensure that all COTS products included in the system deliverable configuration are commercially supported.

3.2.1.5.15 Software Item Database

The Contractor shall capture software design data in an integrated database and shall provide a shared data source for the exchange and reuse of technical information. The Contractor shall develop software item data to populate the software database. The Contractor shall provide the capability to establish, modify, make available, and maintain the integrity of the database. The Contractor shall maintain the system software item database until transition.

(DI-ADMN-80925A) Revisions to Existing Government Documents (Database Design Description (DBDD))

3.2.1.5.16 Software Configuration Management Database

The Contractor shall establish and maintain a software configuration management database IAW the software development process plan. A schema shall be developed for identification of software items and their versions. The Contractor shall perform the following: identification and recording of change request, analysis and evaluation of the changes; approval or disapproval of the request, and implementation, verification, and release of the modified software item. The database shall contain an audit trail whereby each modification, the reason for the modification, and authorization of the modification can be traced.

3.2.1.5.17 Participation in Satellite Communications (SATCOM) Community Configuration Control Activities

The Assistant Product Manager (APM) will coordinate participation of the Contractor in the configuration control activities of the SATCOM community. The WTCS is functioning as a component of a System of Systems (SoS), the WSOMS, and can possibly have a technical and programmatic impact to other components in the various SATCOM communities when changing its baseline configuration. The WTCS as well, can be impacted technically and programmatically by changes to other elements in the SATCOM community. If applicable to the WSOMS Configuration Control Board (CCB), the Contractor shall support the Government participating in the activities of the SATCOM communities of the following organizations:

a. U.S. Army

b. U.S. Air Force

c. U.S. Navy

d. Defense Information Systems Agency (DISA)

e. Austrailian Devense Force

f. Other Government Agencies and International Partners

The Contractor shall review all proposed change requests as well as all approved for implementation change requests regardless of source and advise the APM of any possible impacts to the WTCS. This support shall begin upon contract award and continue throughout the delivery schedule of this contract.

Once the Government has approved the WTCS production configuration baseline, the Contractor shall assist the Government with the preparation of any configuration control documents. The Contractor shall support the Government in the presentation of those documents and rendering technical assistance at CCB meetings in support of any Government presented change requests. The Contractor shall submit change control documents prepared IAW the respective configuration control authority procedures. The Contractor shall submit reports on their CCB activities or reviews of documents IAW Exhibit A.

(DI-MISC-80711A) Scientific and Technical Reports (Configuration Control Reports)

3.2.1.5.18 System Engineering Interface

The process shall allow simultaneous access to the common product data model coupled with the ability to coordinate and update immediate changes to the product definition data. The configuration management system must handle all levels of product and process integration to build and support the product as well as manage the sequence of significant events. The information architecture must permit capture of change information and notify affected team members.

3.2.1.5.19 Engineering Change Proposals (ECP)

The Contractor shall document and the IPT shall review all changes to established baselines and all changes to the requirements (other than the functional baseline), including changes to the statement of work, contract data requirements list (CDRL), the contract schedule, and the general provisions of the contract.

(DI-SAFT-80103C) Engineering Change Proposal System Safety Report (DI-SESS-80639D) Engineering Change Proposal (ECP) (DI-ADMN-81505) Report, Record of Meeting/Minutes (DI-SESS-80642D) Notice of Revision (NOR)

3.2.1.5.20 Engineering Change Proposal Review

In coordination with the Government, the Contractor shall hold a requirements review on all proposed changes prior to the submittal of the engineering change proposal in order to clarify requirements, format, and content. Depending upon the criticality of the proposed changes, this review may take the form of a teleconference, a video-teleconference, a formal meeting at PEO STRI, or a formal meeting at the Contractor’s facility. All appropriate parties shall be in attendance in order to conduct a thorough, effective review. Minutes shall be a historical record to allay any miscommunications.

3.2.1.5.21 Variances

The Contractor shall document the rationale and the potential impact of any variance. The Contractor shall obtain approval before varying from any Government-controlled baseline.

(DI-SESS-80640D) Request for Variance (RFV)

3.2.1.6 Risk Management

The Contractor shall conduct risk management to systematically control uncertainty in the project’s ability to meet cost, schedule, and performance objectives. 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 Cybersecurity 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 Contractor shall address Cybersecurity risk in multiple areas across the risk management process. The Contractor shall use their internal risk management tools to perform risk management. The Contractor shall document risk management as part of Contractor’s Progress, Status and Management Report IAW Exhibit A of the Delivery Order.

(DI-MGMT-80227) Contractor’s Progress, Status and Management Report

3.2.1.7 Management Reviews

3.2.1.7.1 Post Award Conference (PAC)/Start of Work Meeting

As specified for each DO, the Contractor shall conduct a combined PAC/Start of Work Meeting held at the Contractor’s facility, at mutually agreed upon date with the Government, within 20 business days after contract award. The purpose of the conference shall be to establish the framework of the Contractor and Government interaction during the performance period of the contract. The meeting shall include the Contractor’s key team members identified in the proposal with emphasis on top level management of the program. The Contractor shall present the preliminary program schedule, Integrated Product Team (IPT) structure, management concept, organizational structure, points of contact followed by a discussion of both parties understanding of the scope of the effort and other contract issues. The Contractor shall provide presentation slides to the Government no less than one business day prior to the scheduled PAC/Start of Work Meeting date. The Contractor shall be responsible for generating minutes of the meetings and provide them to the Government for approval. The Contractor shall document action items, due dates, and coordinate resolution and track action items until closure. Action item closure shall require contractor and Government approval.

3.2.1.7.2 Program Management Reviews

The Contractor shall conduct program management reviews on a quarterly basis IAW the IMS. The first PMR shall be no more than 90 calendar days after the combined PAC/Start of Work Meeting. The Procuring Contracting Officer (PCO) and the Contractor shall mutually agree upon the location of the PMRs. The Contractor shall coordinate and provide all facilities and infrastructure for Government- Contractor meetings and separate breakout rooms for Government only meetings during the PMR. The PMR shall provide a program overview and shall include as a minimum:

a. Hardware and software design status

b. Risk and problem identification

c. Subcontract management/progress

d. Data collection and modeling

e. Government Furnished Property (GFP) Status

f. Test planning

g. Schedule status

h. Logistics CDRL Status

i. Pre-selected topics of interest

j. Cybersecurity

k. Human Factors Engineering

Status and information at the review shall reflect currency since the previous review. When possible, other program reviews such as technical reviews, technical manual reviews, etc. shall combine into the PMR. The Contractor shall provide presentation slides to the Government no less than one business day prior to the scheduled PMR date. The Contractor shall be responsible for generating minutes of the meetings and provide them to the Government for approval. The Contractor shall document action items, due dates, coordinate resolution, and tracking of action items until closure. Action item closure shall require contractor and Government approval.

3.2.1.7.3 Technical Interchange Meetings (TIMs)

The Contractor shall conduct and participate in TIMs as required and/or by the request of the Government to address, but not be limited to, requirements, performance, schedule, interfaces, testing and logistics.

The specific locations, dates, and duration of the meetings shall be as specified in the Integrated Master Schedule (IMS). The meetings shall be co-chaired by a Government and Contractor representative. The Contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The Contractor shall prepare drawings and other data, as required, to aid in the presentations.

The Contractor shall have all the required personnel and resources present. The Contractor shall make available facilities for Government only meetings. These Government meeting facilities shall include direct internet access for Government personnel laptops. The Contractor shall provide presentation slides to the Government no less than one business day prior to the scheduled TIM date. The Contractor shall be responsible for generating minutes of the meetings and provide them to the Government for approval. The Contractor shall document action items, due dates, coordinate resolution, and tracking of action items until closure. Except where noted herein, meetings shall be considered fulfilled when all of the following items are completed:

a. A formal review meeting has been conducted.

b. The Contractor has documented and submitted all action items (including a responsible individual(s) and a suspense date for each).

c. The Contractor has submitted TIM minutes to the Government for review.

3.2.1.8 Intellectual Property Rights

At a minimum, Government Purpose Rights and/or a perpetual, royalty free, worldwide, nonexclusive, irrevocable license is required for all technical data, computer software, and computer software documentation deliverable under this contract. The Contractor shall not claim rights to any documentation provided for updates or developed under this contract using Government funds.

3.2.1.9 Government Furnished Information (GFI)

The Government will provide agreed upon technical data necessary to accomplish the objectives of this contract upon contractor request, or at the earliest possible opportunity. In the event that technical data required to accomplish the objectives of this contract cannot be provided on a timely manner, the Contractor shall secure alternate Government approved data collection or generation methods. The Contractor shall be responsible to secure, protect and maintain the data provided as GFI.

3.2.1.10 Government Furnished Property (GFP)

The Government will provide the property listed in the GFP List Attachment necessary to accomplish the objectives of this contract at an agreed upon need-by date.

All GFP transactions from/to the Government and to/from the Contractor shall be processed throught the Wide Area Workflow (WAWF) GFP Module at https://wawf.eb.mil/ for the duration of this contract.

The Government will conduct bi-annual inventories and inspections of all GFP and Contractor Acquired Property (CAP).

(DI-MGMT-80441C) Government Property Inventory Report

3.2.1.11 Visitor Support

The Contractor shall host very important person visits and arrange for and provide demonstrations of system performance, program progress, and other system characteristics when notified by the Procurement Contractor Officer (PCO).

3.2.2 Systems Engineering

The Contractor shall translate the basic operational needs, requirements, and objectives and interface and other design constraints including cost, into preliminary verifiable functional requirements and objectives and conduct cost-benefit trades to support refinement of the preliminary functional requirements. The Contractor shall employ well-defined security policy models, structured, disciplined, and rigorous hardware and software development techniques, and sound system/security engineering principles throughout all facets of the design and development of the WTCS. The Contractor shall complete the WTCS design (balanced with respect to performance, cost, schedule, and risk) and verify that it meets the systems requirements. The Contractor shall assess proposed changes in the evolving functional https://wawf.eb.mil/ architecture, physical hierarchy, and baselines and objectively trade alternatives to balance performance, cost, schedule, and risk prior to approval. As part of the system design and component selection process, Cybersecurity shall be considered as a requirement for all systems used to enter, process, store, display, or transmit information. The Contractor shall develop and complete all planned integrated master schedule (IMS) tasks for each milestone.