Attachment_1_-_Statement_of_Work_(SOW)_-_Amendment_003.pdf

UNCLASSIFIED

FA8808-17-R-0006

Attachment 1. Statement of Work

Att. 1-1 of 163

Protected Tactical Enterprise Service (PTES)

Government Statement of Work (GSOW)

Attachment 1 for

19 March 2018

Att. 1-2 of 163

TABLE OF CONTENTS

SCOPE

Applicable Documents 1 CLIN 0001: Protected Tactical Enterprise Service (PTES) – PTES System/Segment Design

1.1 System Level SEIT/PM and Support Equipment

1.1.1 Systems Engineering

1.1.2 Assembly, Integration and Test

1.1.3 Program Management

1.1.4 Support Equipment and Product Support Planning

1.2 Space Vehicle – N/A

1.3 PTES Ground Operations and Processing Center (GOPC)

1.3.1 SEIT/PM and Support Equipment

1.3.2 PTES Mission Management System (MMS)

1.3.3 PTES Key Management System (KMS) and Key Loading and Initialization Facility (KLIF)

1.4 Ground Terminal (GT)/SATCOM Gateway/PTES ECU (KMS and Joint Hub)/PTES Joint

HUB

1.4.1 SEIT/PM and Support Equipment

1.4.2 Antenna – N/A

1.4.3 Optical Communication Assembly – N/A

1.4.4 RF Electronics – N/A

1.4.5 Timing – N/A

1.4.6 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Baseband-Network

1.4.7 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Hardware

1.4.8 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Software

1.4.9 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Pre-Operations

Maintenance – N/A

1.4.10 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Pre-Operations Mission

Support

1.5 External Network (T-COMM)

1.5.1 SEIT/PM and Support Equipment

1.5.2 Leased Circuits/Data Connectivity

1.5.3 Purchased Circuits

1.6 User Equipment – N/A

1.7 Facilities

1.7.1 SEIT/PM & Support Equipment – TBD

1.7.2 Site Preparation – TBD

1.7.3 Landscape – N/A

1.7.4 Buildings – N/A

Att. 1-3 of 163

UNCLASSIFIED

1.7.5 Equipment and Building Fit Out – N/A

1.7.6 Facility Pre-Ops Maintenance – N/A

1.8 Vehicles and Shelters – N/A

1.9 Insurance – N/A

1.10 Task Orders – N/A

1.11 Orbital Transfer Vehicle (OTV) – N/A

1.12 Launch Vehicle – N/A

1 CLIN 0002 (Option): Protected Tactical Enterprise Service (PTES) – PTES System and

Segment Initial Operational Capability (IOC) Development

1.1 System Level SEIT/PM and Support Equipment

1.1.1 Systems Engineering

1.1.2 Assembly, Integration and Test

1.1.3 Program Management

1.1.4 Support Equipment and Product Support Planning

1.1.5 Pre-Operational Support

1.2 Space Vehicle – N/A

1.3 PTES Ground Operations and Processing Center (GOPC)

1.3.1 SEIT/PM and Support Equipment

1.3.2 PTES Mission Management System (MMS)

1.3.3 PTES Key Management System (KMS) and Key Loading and Initialization Facility (KLIF)

1.4 Ground Terminal (GT)/SATCOM Gateway/PTES ECU (KMS and Joint Hub)/PTES Joint

HUB

1.4.1 SEIT/PM and Support Equipment

1.4.2 Antenna – N/A

1.4.3 Optical Communication Assembly – N/A

1.4.4 RF Electronics – N/A

1.4.5 Timing – N/A

1.4.6 SATCOM Gateway/PTES ECU (for KMS and Joint Hub)/Joint Hub Baseband-Network -

Reserved

1.4.7 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Hardware

1.4.8 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Software

1.4.9 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Pre-Operations

Maintenance – Reserved

1.4.10 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Pre-Operations Mission

Support – Reserved

1.5 External Network (T-COMM)

1.5.1 SEIT/PM and Support Equipment

1.5.2 Leased Circuits/Data Connectivity

1.5.3 Purchased Circuits

Att. 1-4 of 163

UNCLASSIFIED

1.6 User Equipment – N/A

1.7 Facilities

1.7.1 SEIT/PM & Support Equipment

1.7.2 Site Preparation

1.7.3 Landscape – N/A

1.7.4 Buildings – N/A

1.7.5 Equipment and Building Fit Out

1.7.6 Facility Pre-Ops Maintenance – Reserved

1.8 Vehicles and Shelters – N/A

1.9 Insurance N/A

1.10 Task Orders – N/A

1.11 Orbital Transfer Vehicle (OTV) – N/A

1.12 Launch Vehicle – N/A

1 CLIN 0003 (Option): Protected Tactical Enterprise Service (PTES) – PTES System/Segment

Full Operational Capability (FOC) Development

1.1 System Level SEIT/PM and Support Equipment

1.1.1 Systems Engineering

1.1.2 Assembly, Integration and Test

1.1.3 Program Management

1.1.4 Support Equipment and Product Support Planning

1.2 Space Vehicle – N/A

1.3 Ground Operations and Processing Center (GOPC)

1.3.1 SEIT/PM and Support Equipment

1.3.2 PTES Mission Management System (MMS)

1.3.3 PTES Key Management System (KMS) and Key Loading and Initialization Facility (KLIF)

1.4 Ground Terminal (GT)/SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub . 107

1.4.1 SEIT/PM and Support

1.4.2 Antenna – N/A

1.4.3 Optical Communication Assembly – N/A

1.4.4 RF Electronics – N/A

1.4.5 Timing – N/A

1.4.6 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Baseband-Network

1.4.7 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Hardware

1.4.8 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Software

1.4.9 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Pre-Operations

Maintenance – N/A

1.4.10 SATCOM Gateway/PTES ECU (KMS and Joint Hub)/Joint Hub Pre-Operations Mission

Support – N/A

1.5 External Network (T-COMM) – N/A

Att. 1-5 of 163

UNCLASSIFIED

1.6 User Equipment – N/A

1.7 Facilities – N/A

1.8 Vehicles and Shelters – N/A

1.9 Insurance – N/A

1.10 Task Orders – N/A

1.11 Orbital Transfer Vehicle (OTV) – N/A

1.12 Launch Vehicle – N/A

1 CLIN 0004 (Option): Protected Tactical Enterprise Service (PTES) – PTES Joint Hub End

Cryptographic Unit (ECU)/Joint Hub Procurement Full Operational Capability (FOC)

1.1 System Level SEIT/PM and Support Equipment

1.1.1 System Engineering – N/A

1.1.2 Assembly, Integration and Test – N/A

1.1.3 Program Management – N/A

1.1.4 Support Equipment and Product Support Planning

1.1.5 Pre-Operational Support – N/A

1.2 Space Vehicle – N/A

1.3 PTES Ground Operations and Processing Center (GOPC) – N/A

1.4 Ground Terminal (GT)/SATCOM Gateway/PTES Joint Hub ECU/PTES Joint HUB

1.4.1 SEIT/PM and Support Equipment

1.4.2 Antenna – N/A

1.4.3 Optical Communication Assembly – N/A

1.4.4 RF Electronics – N/A

1.4.5 Timing – N/A

1.4.6 SATCOM Gateway/PTES Joint Hub ECU/Joint Hub Baseband-Network – N/A

1.4.7 SATCOM Gateway/PTES Joint Hub ECU/Joint Hub Hardware

1.4.8 SATCOM Gateway/PTES Joint Hub ECU/Joint Hub Software

1.4.9 SATCOM Gateway/PTES Joint Hub ECU/Joint Hub Pre-Operations Maintenance – N/A 114

1.4.10 SATCOM Gateway/PTES Joint Hub ECU/Joint Hub Pre-Operations Mission Support – N/A

1.5 External Network (T-COMM) – N/A

1.6 User Equipment – N/A

1.7 Facilities – N/A

1.8 Vehicles and Shelters – N/A

1.9 Insurance – N/A

1.10 Task Orders – N/A

1.11 Orbital Transfer Vehicle (OTV) – N/A

1.12 Launch Vehicle – N/A

1 CLIN 0005 (Option): Protected Tactical Enterprise Service (PTES) –- PTES Joint Hub (w/End

Cryptographic Unit (ECU) Installation and Deployment (Full Operational Capability (FOC)) .115

1.1 System Level SEIT/PM and Support Equipment

Att. 1-6 of 163

UNCLASSIFIED

1.1.1 Support Equipment and Product Support Planning

1.2 Space Vehicle – N/A

1.3 PTES Ground Operations and Processing Center (GOPC) – N/A

1.4 Ground Terminal/SATCOM Gateway/PTES Joint Hub (w/ECU)

1.4.1 SEIT/PM and Support Equipment

1.4.2 Antenna – N/A

1.4.3 Optical Communication Assembly – N/A

1.4.4 RF Electronics – N/A

1.4.5 Timing – N/A

1.4.6 SATCOM Gateway/PTES Joint Hub Baseband-Network

1.4.7 SATCOM Gateway/ECU/PTES Joint Hub Installation Hardware

1.4.8 SATCOM Gateway/PTES Joint Hub Software – N/A

1.4.9 SATCOM Gateway/PTES Joint Hub Pre-Operations Maintenance – N/A

1.4.10 SATCOM Gateway/PTES Joint Hub Pre-Operations Mission Support – Reserved

1.5 External Network (T-COMM)

1.5.1 SEIT/PM and Support Equipment

1.5.2 Leased Circuits/Data Connectivity

1.5.3 Purchased Circuits

1.6 User Equipment – N/A

1.7 Facilities

1.7.1 SEIT/PM & Support Equipment

1.7.2 Site Preparation

1.7.3 Landscape – N/A

1.7.4 Buildings – N/A

1.7.5 Equipment and Building Fit Out – N/A

1.8 Vehicles and Shelters – N/A

1.9 Insurance – N/A

1.10 Task Orders – N/A

1.11 Orbital Transfer Vehicle (OTV) – N/A

1.12 Launch Vehicle – N/A

1 CLIN 0006 (Reserved): Protected Tactical Enterprise Service (PTES) – Initial Spares/Support

Equipment/Interim Contractor Support

1.1 System Level SEIT/PM and Support Equipment

1.1.1 Systems Engineering

1.2 Spares

1 CLIN 0007 (Option): Protected Tactical Enterprise Service (PTES) – Priced Training and

Technical Orders Option

1.1 Training

1.2 Technical Orders (TOs)

1 CLIN 0008 (Option): Protected Tactical Enterprise (PTES) –- Special Studies

Attachment 1. Statement of Work

Att. 1-7 of 163

UNCLASSIFIED

1.1 Special Study Requirements

Appendix A – Agile Product Management Appendix B – Key Personnel Substitution Appendix C – SMC--Enabling Clause For Government Program Contracts Requiring Interface With

Aerospace Federally Funded Research and Development Center (FFRDC) Contract Support

(NOV 2017)

Appendix D – Rework, Replacement, or Correction Due to CAT 1 Emergency and CAT 1 Urgent Defects (Applicable To CLINS 0002, 0003, 0004, and 0005) (May 2018)

Appendix E – Acronym List

LIST OF TABLES

Table 1-1. PTES Internal System ICDs Led by PTES Contractor Table 1-2. PTES External System ICDs Supported by PTES Contractor Table 1-3. Criticality Definitions Table 1-4. Software Assurance (Development Process) Table 1-5. Software Assurance (Operational Process) Table 1-6. Software Assurance (Development Environment) Table 1-7. System Test Events Led by PTES Contractor Table 1-8. System Test Events Supported by PTES Contractor Table 1-1. System Test Events Led by PTES Contractor Table 1-2. System Test Events Supported by PTES Contractor Table 1-1. System Test Events Led by PTES Contractor Table 1-2. System Test Events Supported by PTES Contractor Table A-1. Government PTES Program Office (or Designee) Participation at Agile Meetings Table A-2. User Story Definition of Ready Criteria Table A-3. User Story Definition of Done Table A-4. Sprint Definition of Done Table A-5. Feature Definition of Done Table A-6. Build Definition of Done Table A-7. Release Definition of Done Table A-8. Build Decision Review Entrance/Exit Criteria

1395812781A Highlight

Att. 1-8 of 163

UNCLASSIFIED

SCOPE

The Protected Tactical Enterprise Service (PTES) will provide an anti-jam Satellite Communications (SATCOM) capability for the tactical warfighter via Wideband Global SATCOM (WGS) satellites.

PTES includes a Mission Management System (MMS), a Key Management System (KMS) and Key Loading and Initialization Facility (KLIF), and provides Joint Hubs to plan the global communication services via WGS satellites. The PTES Initial Operational Capability (IOC) provides regional service utilizing one (1) WGS satellite and the Full Operational Capability (FOC) provides a worldwide service utilizing up to ten (10) WGS satellites.

The PTES MMS, KMS and KLIF will be deployed at Defense Information Systems Agency (DISA) Core Data Centers (CDC), which is a Joint Integration Environment (JIE) CDC. The PTES Joint Hubs will be deployed at existing SATCOM Gateway sites. PTES will be operated by personnel at Schriever AFB. The MMS, KMS and KLIF software will be developed using the Agile Product Management process as specified in this document. For the Joint Hub and End Cryptographic Unit (ECU) the PTES Contractor may choose to use the Agile Product development process or another development lifecycle (e.g., waterfall, incremental).

There are eight Contract Line Item Numbers (CLIN) covering design, development, testing, and fielding. The CLIN structure provides three (3) System Engineering, Integration and Test, Program Management, and Support Equipment CLINs (0001, 0002 and 0003) that covers different periods of performance from Effective Contract Date (ECD) through FOC. CLIN 0001 provides for the design of the hardware (Joint Hub and ECU), Architectural Development of the MMS, KMS, and KLIF (Build 0), and the development, test, and delivery of the MMS, KMS, and KLIF software Builds 1 and 2. CLIN 0002 provides for the development and fielding of the PTES IOC capability to include the ECU, Joint Hub, and MMS, KMS, and KLIF Release 1 (Builds 3 and 4). CLIN 0003 provides for the development of the MMS, KMS, and KLIF FOC Release 2 (Builds 5 through 8) and any required upgrades to the ECU and Joint Hub. CLIN 0004 covers ECU (for the KMS and Joint Hub) and Joint Hub production for FOC. CLIN 0005 provides for the installation of ECUs and Joint Hubs for FOC. CLIN 0006 covers interim contractor support and sparing to support the transition period between IOC and FOC. CLIN 0006 is “Reserved.” The Government intends to modify the contract at a later date to include this work.

CLIN 0007 provides additional training and documentation requirements for military personnel in the event military personnel are required to operate the PTES system. CLIN 0008 covers special studies.

The technical requirements for PTES have been flowed down from the PTES Capabilities Development Document (CDD) and are defined in the PTES System Technical Requirements Document (TRD) (PTES-8000). The PTES CDD includes fifteen (15) Key Performance Parameters (KPP). The CDD also includes twenty five (25) Key System Attributes (KSA) and sixteen (16) Additional Performance Attributes (APA).

This Government Statement of Work (GSOW) defines the tasks required to develop, build, integrate, test, field, and conduct interim contractor operations of the PTES system. Note that days mentioned in the GSOW, unless otherwise specified, refer to calendar days (CD). The Contractor Statement of Work (CSOW) shall be consistent with the structure, content, and numbering of the GSOW, and shall only add lower level tasks.

The GSOW contains eight CLINs of which seven CLINs contain Contract Data Requirement Lists (CDRL). Additionally, specified requirements in CLIN 0001 that are also applicable to CLINs 0002 and 0003 are referred to in their respective sections. CDRLs contained in CLIN 0001 that are also applicable to CLINs 0002 and 0003 will be identified in CLIN 0001 and submitted as stated below.

Att. 1-9 of 163

UNCLASSIFIED

With the exception of A054 (Integrated Program Management Report (IPMR)) and A055 (Contract Funds Status Reports (CFSR)), CDRLs for each CLIN shall be identified as follows:

“A” series CDRLs apply only to CLIN 0001, [AXXX] "B" series CDRLs apply only to CLIN 0002, [BXXX] "C" series CDRLs apply only to CLIN 0003, [CXXX] "D" series CDRLs apply only to CLIN 0004, [DXXX] "E" series CDRLs apply only to CLIN 0005, [EXXX] "F" series CDRLs are “Reserved,” and apply only to CLIN 0006, [FXXX] "G" series CDRLs apply only to CLIN 0007, [GXXX]

CDRLs A054 (IPMR) and A055 (CFSR) will run the length of the contract and updated/submitted as indicated on their respective DD Form 1423.

Applicable Documents All Compliance and Reference documents to include Standards, Handbooks, instructions, policy guidance, operations, etc., are contained in Attachment 2, Compliance and Reference Documents. The PTES Contractor shall comply with Table 1 of Attachment 2 (Compliance and Reference Documents) as defined in this GSOW and the documents in the PTES Technical Baseline unless specifically exempted or tailored by the Government. The PTES Contractor shall notify the Government for resolution in the event a conflict exists between a compliance document and this GSOW. For the purpose of this contract, this GSOW takes precedence over compliance documents except for higher-level Department of Defense (DoD)/DFARS clauses. The words “in accordance with (IAW)” and “in compliance with” will be used when referring to requirements in Compliance documents. The words “consistent with” and “per” will be used when referring to requirements in Reference documents.

Att. 1-10 of 163

UNCLASSIFIED

Requirements

1 CLIN 0001: Protected Tactical Enterprise Service (PTES) – PTES System/Segment Design CLIN 0001 includes all activities required to design and develop PTES from Effective Contract Date (ECD) through completion of System Critical Design Review (CDR) and CDR closeout actions. All requirements and nomenclature under this section also apply to CLINs 0002 and 0003 except where expressly stated otherwise.

1.1 System Level SEIT/PM and Support Equipment

The system level System Engineering, Integration and Test (SEIT) and Program Management (PM) and Support Equipment includes all PTES system and segments, overall program planning and controls to guide and execute program objectives. This section includes system engineering, integration, testing, program management, and support equipment efforts across system level activities, intersegment level activities and interfaces with external systems and organizations.

1.1.1 Systems Engineering

1.1.1.1 General Planning

The PTES Contractor shall conduct planning to design, build, and deliver a ground system that meets all PTES functional and performance requirements as defined in Government approved PTES specifications, Interface Control Documents (ICD), Cybersecurity Controls, compliance documents (Attachment 2, Compliance and Reference Documents) and the Operational Concept Description (OCD) for Initial Operational Capability (IOC) and Full Operational Capability (FOC).

a. The PTES Contractor shall plan to manage and execute the PTES system engineering effort compliant with ISO/IEC/IEEE 15288 (Systems Lifecycle Processes) (as tailored by IEEE 15288.1), IEEE 15288.1 (Application of Systems Engineering on Defense Programs) (as tailored by SMC-T-005 (Risk Management Supplement To IEEE-15288.1 and Attachment 2 (Compliance and Reference Documents)) and SMC-T-006 (Specialty Engineering Supplement to IEEE 15288.1) and in accordance with (IAW) the Government PTES Program Office approved Systems Engineering Management Plan (SEMP).

1. The PTES Contractor shall prepare and maintain a SEMP that complies with IEEE 15288.1

(Application of Systems Engineering on Defense Programs) (tailored), is consistent with the Government PTES System Engineering Plan (SEP) and documents the contractor’s processes for planning, controlling and conducting a fully integrated engineering effort for PTES.

[A001], [B001], [C001]

i. The PTES Contractor shall include an annex in the SEMP that provides a trace of the

IEEE 15288.1 Process Outputs for each process to the Contract Data Requirement List (CDRL). For those Process Outputs that do not trace to a CDRL, the PTES Contractor shall provide a recommended tailoring.

2. The PTES Contractor shall establish and maintain a PTES engineering change process IAW with Section 1.1.1.10 below.

b. The PTES Contractor shall deposit all technical and management data that are required deliverables and work products identified in the Software Development Plan (SDP) and SEMP, including: processes, procedures, work instructions, interim CDRLs, and required work products

Att. 1-11 of 163

UNCLASSIFIED

identified for the Data Accession List (DAL) in the Contractor’s secure Integrated Digital Environment (IDE) (see 1.1.1.11 Data Management) within three (3) business days of being updated, and update the DAL. (DAL submission) [A004], [B004], [C004]

c. The PTES Contractor shall prepare and maintain an OCD consistent with the PTES Capabilities Development Document (CDD), Protected Anti-Jam Tactical SATCOM (PATS) Concept of Operations (CONOPS), and PTES System TRD (PTES-8000). [A002], [B002], [C002]

d. The PTES Contractor shall use a disciplined Systems Engineering approach IAW the Government PTES Program Office approved SEMP to define requirements, control changes, verify the PTES product, and achieve Government PTES Program Office acceptance. [A001], [B001], [C001]

e. The PTES Contractor shall request Government Furnished Property (GFP) items listed in Attachment 6: Government Furnished Property (GFP) and coordinate the delivery dates established by the Government PTES Program Office.

f. The PTES Contractor shall conduct Technical Interchange Meetings (TIM) and engineering tag-up teleconferences with the Government. (assume two per month)

g. The PTES Contractor shall produce meeting minutes with action items. (DAL submission) [A004], [B004], [C004]

h. All PTES segment markings shall be IAW MIL-STD-130N (Identification Marking of U.S.

Military Property).

i. The PTES Contractor shall ensure the system and segment design complies with Department of Defense (DoD) Information Technology Standards Registry (DISR) standards to be tailored in coordination with the Government PTES Program Office.

(https://gtg.csd.disa.mil/disr/dashboard.html)

1. The PTES Contractor shall provide data to support the Government PTES Program Office in completing the DISR questionnaire and profile. (DAL submission) [A004], [B004], [C004]

j. The PTES Contractor shall develop system and segment level systems engineering plans and perform system engineering for the integration of PTES segments and integration of PTES with external systems and organizations.

1. The PTES Contractor shall develop and maintain a System Integration and Test Plan (SITP) that is consistent with the Government SITP (PTES-8950). [A005], [B005], [C005]

k. The PTES Contractor shall provide personnel with network and system administration experiences to manage DISA assets belonging to PTES during development.

1. The PTES Contractor shall be, at a minimum, Information Assurance Technical (IAT) Level

1 certified.

2. The PTES Contractor shall meet the background investigation requirements IAW DoDI

8500.01, "Cybersecurity," March 14, 2014."

l. The PTES Contractor shall comply with DISA Terms and Conditions (latest version), section on

System Technology for hardware and software to be installed at the DISA CDC.

https://gtg.csd.disa.mil/disr/dashboard.html

Att. 1-12 of 163

UNCLASSIFIED

m. The PTES Contractor shall provide adequate cleared personnel up to and including Top Secret/Sensitive Compartmented Information (TS/SCI) in order to process realistic threat scenarios for testing of the PTES system. (See DD Form 254 for more details)

1.1.1.1.1 Support to the Government PTES Program Office

a. The PTES Contractor shall support the Integrated Product Teams (IPT) listed in the PTES SEP.

Support shall include, but not be limited to:

1. Participating in meetings and IPTs with the Government PTES Program Office. (Assume ten

(10) (one (1) hour) separate IPT bi-weekly (every two weeks) meetings by teleconference)

2. Providing technical inputs and developing material for IPT products.

3. Providing status on PTES Contractor activities related to the IPT.

b. The PTES Contractor shall provide the data derived from PTES analyses, demonstrations and modeling and simulation (M&S) activities as inputs for Government PTES Program Office M&S activities associated with system design trades and requirements verification. (DAL submission) [A004], [B004], [C004]

c. The PTES Contractor shall facilitate meetings for unanticipated events as requested by the Government PTES Program Office. (Assume four one-day meetings per year, held at the Contractor’s facility with 25 attendees)

d. The PTES Contractor shall participate in the Government PTES Program Office Engineering Review Board (ERB), Risk Management Board (RMB) and Configuration Control Board (CCB) processes as documented in the PTES SEP. (Assume teleconference every two (2) weeks)

e. The PTES Contractor shall support the MILSATCOM Control Board (MCB) as requested by the Government PTES Program Office (assume quarterly).

f. The PTES Contractor shall support planning and execution of the Government testing and assessments as outlined in the Government SITP (PTES-8950):

g. The PTES Contractor shall participate in the PTES Schedule Management Review (SMR) processes, as documented in the PTES SEP.

1. The PTES Contractor shall provide Contractor schedule status and updates to the

Government PTES Program Office for incorporation into the Government PTES Program Office Integrated Master Schedule (IMS).

2. The PTES Contractor shall attend scheduling meetings to review baseline schedule changes and schedule disconnects, and to review near term activities, progress and late tasks.

(Assume teleconference every two (2) weeks)

h. The PTES Contractor shall support the Government PTES Program Office working groups for PTES future extensibility to support the Protected Anti-jam Tactical Satellite Communications (PATS) phases. (Assume one (1) teleconference every month)

1. The PTES Contractor shall support technical discussions with PATS programs’ contractors and provide technical input to the working group to define requirements, interfaces, and operations concepts for the extension of PTES functionality to support all PATS phases.

Att. 1-13 of 163

UNCLASSIFIED

2. The PTES Contractor shall provide comments on technical material provided by other PATS programs’ contractors through the working group.

i. The PTES Contractor shall provide status information for Government PTES Program Office reviews, executive reviews, independent program reviews and assessments, inspections, milestone events, budget excursions and user conferences. (DAL submission. [A004], [B004], [C004]

j. The PTES Contractor shall support the Government PTES Program Office in the generation and execution of the Program Office’s giver/receiver lists.

k. The PTES Contractor shall provide dedicated office spaces for:

1. Three Government PTES Program Office personnel at the primary Contractor software development facility and two Government PTES Program Office personnel at up to two other software development facilities. As a minimum, the office space shall be a lockable room and include a desk(s), phone(s), and unclassified computer hookups with access to the internet. The Government PTES Program Office personnel shall also be provided a hot desk and access to the PTES Contractor software development environments and secure IDE.

2. Two Government PTES Program Office personnel at the primary Contractor hardware development facility and one Government PTES Program Office personnel at up to two other hardware development facilities. As a minimum, the office space shall be a lockable room and include a desk(s), phone(s), and unclassified computer hookups with access to the internet. The Government PTES Program Office personnel shall also be provided a hot desk and access to the PTES Contractor secure IDE.

l. The PTES Contractor shall support the Government PTES Program Office in developing and updating, when necessary, the Defense Information Systems Agency (DISA) Service Request Form (SRF).

1. The PTES Contractor shall support a TIM with the Government PTES Program Office to finalize the initial SRF within 14 calendar days (CD) of ECD.

2. The PTES Contractor shall support monthly TIMs to update the SRF and to discuss issues with DISA environments.

3. The PTES Contractor shall participate in technical meetings and IPTs with DISA. (Assume daily (one (1) hour) technical discussion and separate weekly (one (1) hour) IPT meetings by teleconference)

1.1.1.1.2 Support to External Organizations

a. The PTES Contractor shall support and provide technical inputs to certifications listed in the

Government PTES SITP (PTES-8950) to include, but not be limited to: certification for operation over Wideband Global SATCOM (WGS) system, National Security Agency (NSA) certifications, DISA Core Data Centers (CDC), SATCOM Gateways and DoD Risk Management Framework (RMF).

b. The PTES Contractor shall participate in meetings, technical discussions, reviews, etc., with external organizations such as the Office of the Secretary of Defense (OSD), DISA, United States Strategic Command (USSTRATCOM), Headquarters (HQ) Air Force Space Command

Att. 1-14 of 163

UNCLASSIFIED

(AFSPC), Army Forces Strategic Command (ARSTRAT), NSA and terminal Program Offices.

(Assume only one (1) external organization teleconference per week)

c. The PTES Contractor shall coordinate with DISA to:

1. Incorporate Cybersecurity requirements on PTES hardware and software deployed at DISA

CDCs.

2. Provide full detailed documentation for performance issues, fixes and change requests recommended to improve the performance or security.

d. The PTES Contractor shall integrate and collaborate with Government identified Cybersecurity

Service Provider (CSSP) to integrate monitoring tools that the CSSP requires to operate based on the level of service (degree of monitoring) of the CSSP.

Note: A CSSP is an organization that provides one or more cybersecurity services to implement and protect the Department of Defense Information Networks (DoDIN). CSSP will:

- Offer and provide cybersecurity services in accordance with DoD O-8530.01-M.

- Execute cybersecurity responsibilities and authorities in accordance with DoD

Component policy, MOAs, contracts, or support agreements.

- Comply with directives and orders of USSTRATCOM and supported DoD Component

NOSC and organizations.

- Document all supported entities and associated systems in accordance with DoD

Component policy, MOAs, contracts, or support agreements.

1.1.1.2 PTES System Level Design

a. The PTES Contractor shall design and develop a system that:

1. Meets all requirements (software & hardware) required by the GSOW to include Contractor developed PTES specifications, TRDs, ICDs, other applicable specifications and compliance documents (Attachment 2, Compliance and Reference Documents, Table 1).

2. Meets evolving Risk Management Framework (RMF) per DoDI 8510.01 (Risk Management Framework (RMF) for DoD Information Technology (IT)) (latest version) and NIST 800-53 (latest version) controls tailored for PTES as specified in the Government PTES-8000 System TRD and including DISA Security Technical Implementation Guide (STIG) requirements.

b. The PTES Contractor shall develop and maintain a Model Based Systems Engineering (MBSE) Solution Architecture (as delineated in the SEP). The Solution Architecture design shall ensure reuse of information, architecture artifacts, models and viewpoints that can be shared with common understanding in Commercial-Off-The-Shelf (COTS) SysML-compliant tools. The Solution Architecture shall be included as a model and documented in the PTES System/Subsystem Design Description (SSDD), with supporting rationale that meets all PTES requirements. [A006], [B006], [C006]

1. The PTES Contractor shall develop and maintain the SSDD and ensure Solution Architecture alignment with the PTES GRA. [A006], [B006], [C006]

Att. 1-15 of 163

UNCLASSIFIED

2. The PTES Contractor shall document PTES Dynamic Resource Allocation (DRA) algorithm and Mission Management System (MMS) demodulation packing solution in the SSDD.

[A006], [B006], [C006]

3. The PTES Contractor shall deliver the MBSE products to include the Solution Architecture model as part of the SSDD. [A006], [B006], [C006]

4. The PTES Contractor shall provide to designated Government Program Office personnel access to the products and models within the Contractor’s integrated MBSE environment.

5. The PTES Contractor shall allow designated Government Program Office personnel to participate in the Configuration Management processes related to the Contractor’s MBSE environment.

c. The PTES Contractor shall ensure the MBSE Solution Architecture Model supports:

1. Applicable products to meet entrance and exit criteria for design reviews are delineated in the

SEMP. [A001], [B001], [C001]

2. Requirements development, requirements analysis and interface definition.

3. Integration, test, verification, planning and execution.

4. Updates to Government Department of Defense Architecture Framework (DoDAF) views documenting the end-to-end PTES system architecture, technical baseline changes, and PTES evolving capabilities.

5. Refinement of the understanding of the PTES operations and maintenance.

d. The PTES Contractor shall use a Modular Open System Approach (MOSA) for the design and development of the PTES system (reference Defense Acquisition Guidebook CH 3-2.4.1).

1. The PTES Contractor shall design an architecture meeting MOSA principles that allows severable components at the appropriate level to be iteratively added, removed, or replaced throughout the lifecycle of PTES to enable opportunities for technical upgrades, increased interoperability, sustainment benefits, costs savings and schedule reductions.

i. The PTES Contractor shall provide a design and develop a system that includes system interfaces that utilize Government-approved ICDs between the PTES system and external systems, between PTES segments, and between subsystems.

2. As part of the MOSA design architecture and development, the PTES Contractor shall use the following four segments including: the MMS, Key Management System (KMS), Key Loading and Initialization Facility (KLIF) and Joint Hub.

i. For MMS, the PTES Contractor shall use a minimum of ten (10) subsystems which include Database Management, WGS Mission Planning, External Input/Output Manager, and Classified Portal Manager, Unclassified Portal Manager, and additional contractor-defined subsystems.

ii. For each KMS, KLIF and Joint Hub segments, the PTES Contractor shall use a minimum of six subsystems which include an Input/Output Manager and contractor-defined subsystems.

Att. 1-16 of 163

UNCLASSIFIED

iii. The PTES Contractor shall ensure that the size Source Lines of Code (SLOC) of a subsystem does not exceed 25% of its segment size (SLOC).

iv. The PTES Contractor shall provide a design and develop a system such that interfaces between subsystems within a segment use only a common set of industry standard application layer protocols for data exchanges between subsystems.

e. The PTES Contractor shall demonstrate that the MMS software design meets extensibility requirements (IAW the PTES System TRD) to plan for and manage PATS Terminals, Contingency Hubs, Joint Hubs, and Hub-in-space for the operations for future PATS phases.

f. The PTES Contractor shall document technical decisions and trades, including trade studies requested by the Government PTES Program Office and present the findings to the Government PTES Program Office as requested. (DAL submission) [A004], [B004], [C004]

1. The PTES Contractor shall conduct a systems engineering trade-off analysis showing how cost and capability vary as a function of the major design parameters prior to the PTES System Preliminary Design Review (PDR). The analysis will support the Government Program Manager’s assessment of refined Key Performance Parameters/Key System Attributes/Additional Performance Attributes (KPPs/KSAs/APAs) and Government validation of the CDD. For planning purposes, anticipate three technical interchange meetings (TIMs) with the Government Program Office to refine the study parameters and brief the results. [A004] (This subparagraph only applies to CLIN 0001)

2. The PTES Contractor shall conduct a system engineering trade-off analysis on the selection of the integration, test, demonstration, and training environment, and operational environment for the PTES MMS, KMS, and KLIF segments prior to PTES System Functional Review (SFR). The analysis will show how life-cycle factors and risk vary as a function of, but not limited to, cost, performance, integration, test, cybersecurity certification, and sustainment. At a minimum, environments analyzed will include DISA CDCs, DISA milCloud 2.0, and a dedicated hardware/software system collocated with the operators. The analysis will support the Government Program Manager’s assessment of the operational computational environment. For planning purposes, anticipate three technical interchange meetings (TIMs) with the Government Program Office to refine the study parameters and brief the results. [A004](This subparagraph only applies to CLIN 0001)

g. The PTES Contractor shall employ M&S capabilities for the development, test and validation of the PTES system and provide a minimum of Government Purpose Rights for all M&S capabilities developed for this purpose.

h. The PTES Contractor shall develop and deliver a Design Review Information Package (DRIP) that addresses Technical Review and Audit requirements contained in IEEE 15288.2 (Technical Reviews and Audits on Defense Programs) (tailored) for the PTES System Requirements Review (SRR). [A008] (This subparagraph only applies to CLIN 0001)

1. The PTES Contractor shall coordinate with the Government PTES Program Office to agree on the content, format, and acceptance criteria of the SRR, including tailoring of specific criteria specified in IEEE 15288.2 (Technical Reviews and Audits on Defense Systems) (tailored). Note: SRR criteria related to software for segments using Agile software development will be tailored to be consistent with Agile processes.

Att. 1-17 of 163

UNCLASSIFIED

i. The PTES Contractor shall develop and deliver a DRIP that addresses Technical Review and Audits requirement contained in IEEE 15288.2 (Technical Reviews and Audits on Defense Programs) (tailored) for the PTES SFR. [A008] (This subparagraph only applies to CLIN 0001)

1. The PTES Contractor shall coordinate with the Government PTES Program Office to agree on the content, format, and acceptance criteria of the SFR, including tailoring of specific criteria specified in IEEE 15288.2 (Technical Reviews and Audits on Defense Systems) (tailored). Note: SFR criteria related to software for segments using Agile software development will be tailored to be consistent with Agile processes.

j. The PTES Contractor shall develop and deliver a DRIP that addresses Technical Review and Audit requirements contained in IEEE 15288.2 (Technical Reviews and Audits on Defense Programs) (tailored) for the PTES System PDR. [A008] (This subparagraph only applies to

CLIN 0001)

1. The PTES Contractor shall coordinate with the Government PTES Program Office to agree on the content, format, and acceptance criteria of the System PDR, including tailoring of specific criteria specified in IEEE 15288.2 (Technical Reviews and Audits on Defense Systems) (tailored). Note: System PDR criteria related to software for segments using Agile software development will be tailored to be consistent with Agile processes.

2. The PTES Contractor shall also include in the System PDR DRIP a Reliability and Maintainability Predictions Report (see MIL-HDBK-217F).

k. The PTES Contractor shall develop and deliver a DRIP that addresses Technical Review and Audit requirements contained in IEEE 15288.2 (Technical Reviews and Audits on Defense Programs) (tailored) for the PTES System CDR. [A008] (This subparagraph only applies to

CLIN 0001)

1. The PTES Contractor shall coordinate with the Government PTES Program Office to agree on the content, format, and acceptance criteria of the System CDR, including tailoring of specific criteria specified in IEEE 15288.2 (Technical Reviews and Audits on Defense Systems) (tailored). Note: System CDR criteria related to software for segments using Agile software development will be tailored to be consistent with Agile processes.

2. The PTES Contractor shall also include in the System CDR DRIP a Reliability and Maintainability Predictions Report (see MIL-HDBK-217F).

l. The PTES Contractor shall conduct the following PTES system reviews in compliance with the tailored IEEE 15288.2 (Technical Reviews and Audits on Defense Programs) (tailored) entry and exit criteria: System Requirements Review (SRR), System Functional Review (SFR), System Preliminary Design Review (PDR), and System CDR. (This subparagraph only applies to CLIN 0001)

m. The PTES Contractor shall perform the following for System SRR, SFR, System PDR, and System CDR: (This subparagraph only applies to CLIN 0001)

1. Conduct an Entry Criteria review meeting with the Government PTES Program Office prior to each design review for Government PTES Program Office assessment of entry criteria sufficiency and readiness to hold the review.

Att. 1-18 of 163

UNCLASSIFIED

2. Conduct dry-run presentations with Government PTES Program Office participation no later than fourteen (14) CD prior to the review.

3. Develop post-review minutes and respond to post-review action item no later than fourteen

(14) CD following the review. (DAL submission) [A004], [B004], [C004]

4. Submit proposed closure of action items and liens for Government PTES Program Office approval no later than fourteen (14) CD following the review. (DAL submission) [A004], [B004], [C004]

5. Obtain Government PTES Program Office concurrence that acceptance criteria have been met.

1.1.1.3 Software Development

a. The PTES Contractor shall use an Agile Project Management approach as outlined in Appendix

A (Agile Product Management) for the development of the MMS, KMS and KLIF. For the KMS ECU, Joint Hub ECU and Joint Hub software development, the PTES Contractor may choose to use the Agile Product development process or another development lifecycle (e.g., waterfall, incremental). (Note: Regardless of ECU development approach selected, all ECU CDRLs shall be delivered IAW their respective DD 1423 instructions.)

b. The PTES Contractor shall plan and execute a set of defined management, engineering and support processes for software development:

1. That are mature, capable, and process interfaces are integrated across the entire team, including subcontractors to ensure work products transition across organization boundaries efficiently.

2. That leverage organization and industry best practices (e.g., Software Engineering Institute (SEI) Capability Maturity Model-Integrated for Development (CMMI-DEV®), SAE AS9100 Rev D (Quality Management Systems - Requirements for Aviation, Space and Defense Organizations) and ISO 9001 (Quality Management Systems – Requirements)).

3. That are compliant with evolving program Cybersecurity controls as described in section 1.1.1.14.

4. That are identified in the SEMP and Software Development Plan (SDP) and accessible in the

IDE. [A001], [B001], [C001], [A010], [B010], [C010]

c. The PTES Contractor shall develop, implement and manage software and associated products IAW SMC-S-012 (SMC Software Development for Space Systems) (as tailored by Attachment 2, Compliance and Reference Documents):

1. Software Architecture Description (SAD) [A011], [B011], [C011]

2. Database Design Description (DBDD) [A012], [B012], [C012]

3. Software Requirements Specification (SRS) (only for Joint Hub if using non-agile software development methods) [A013], [B013], [C013]

4. Software Development Plan (SDP) [A010], [B010], [C010]

5. Software Test Plan (STP) [A014], [B014], [C014]

6. Software Test Description (STD) [A015], [B015], [C015]

Att. 1-19 of 163

UNCLASSIFIED

7. Software Test Reports (STR) [A016], [B016], [C016]

8. Software User Manual (SUM) [A017], [B017], [C017]

9. Software Product Specification (SPS) [A018], [B018], [C018]

10. Software Version Description (SVD) [A019], [B019], [C019]

11. Software Resources Data Reporting: Development and Maintenance Reports and Data

Dictionary [A020], [B020], [C020]

12. Software and System Measurement Report (SSMR) [A021], [B021], [C021]

13. Firmware Support Manual [A022], [B022], [C022]

14. Software Transition Plan (STrP) [A023], [B023], [C023]

15. Agile Product Backlog/Product Roadmap [A024], [B024], [C024]

d. The PTES Contractor shall ensure the team’s software development environment is consistent with the Government approved DISA CDC Integration, Demonstration & Test, and Training environment; and Operational environment.

e. The PTES Contractor shall use secure coding standards identified in the SDP for all PTES software. [A010], [B010], [C010]

1. The PTES Contractor shall conduct training in secure coding based on the standards identified in the SDP for the PTES development team. [A010], [B010], [C010]

f. The PTES Contractor shall use automated analysis tools to ensure conformance to secure coding standards identified in the SDP. [A010], [B010], [C010]

1. The PTES Contractor shall ensure software, scripts and data developed to support the automated analysis are deposited into the Contractor's IDE and entered into the DAL.

[A004], [B004], [C004]

g. The PTES Contractor shall ensure interim versions of software work products are available in the Contractor’s secure IDE, and update the DAL. [A004], [B004], [C004]

h. The PTES Contractor shall identify and receive Government PTES Program Office concurrence for use of proposed Non-Developmental Items (NDI) (see Appendix A (Agile Product Management) Glossary definition), including updates, in the PTES system and for development, support and maintenance.

1. The PTES Contractor shall ensure that the selected PTES NDI complies with SMC-S-012

(SMC Software Development for Space Systems) Appendix B (tailored) and can be maintained, verified, tested, and sustained.

2. The PTES Contractor shall conduct NDI pedigree analysis and vulnerability assessments and provide the results to the Government PTES Program Office. (DAL submission) [A004], [B004], [C004]

3. The PTES Contractor shall use automated analysis and test tools on all NDI to demonstrate functionality, and for integration, regression, and requirement testing.

4. The PTES Contractor shall annually review changes to NDI product versions, including operating systems, infrastructure and platform software.

Att. 1-20 of 163

UNCLASSIFIED

5. The PTES Contractor shall identify risks and propose mitigations for use of NDI, present the proposed approach to the Government PTES Program Office.

6. The PTES Contractor shall maintain configuration identification and control of all NDI software used in development, support, or maintenance of PTES. (DAL submission) [A004], [B004], [C004]

i. The PTES Contractor shall ensure configuration identification includes: developer name

(project name for NDI), product name, version, country of origin, summary of general purpose, where used (e.g., development environment, test environment, end unit) and a website reference.

ii. The PTES Contractor shall provide Software Product Specification (SPS) for reuse code.

[A018], [B018], [C018]

i. The PTES Contractor shall identify and minimize the existence of dead or unused code

1. The PTES Contractor shall use static code analysis to identify dead or unused code

2. The PTES Contractor shall assess and mitigate the cybersecurity and system performance risks of dead or unused code

3. The PTES Contractor shall track risks associated with dead or unused code in Risk

Management process per paragraph 1.1.1.7 and obtain Government PTES Program Office approval for risk mitigation approach.

j. The PTES Contractor shall ensure that software provides independence from the GFE operating system and virtualization infrastructure to minimize impact on PTES software from upgrades or changes to the operating system over time.

k. The PTES Contractor shall deliver a complete list of licenses and warranties for all software used within the system for development, testing and operations. [A025], [B025], [C025]

1. The PTES Contractor shall maintain the current/active licenses and warranties until turnover

(DD Form 250) of the system to the Government.

2. The PTES Contractor shall formally transfer all equipment software licenses and warranties required to test, operate and maintain the installed system at system turnover (DD Form 250).

[A025], [B025], [C025]

3. The PTES Contractor shall ensure software licenses do not contain requirements that restrict or obligate the Government's use of the source codes, such as requirements to provide software updates back to the owner, limits on the type of use or user, inability to pass the license on to others, or includes other embedded licenses that are not equally available or disclosed.

4. The PTES Contractor shall ensure software licenses do not have expirations dates (e.g., stops working after 31 December 2050).

5. The PTES Contractor shall ensure maintenance fees ($$ each YY) are negotiated and agreed to by the Government.

Att. 1-21 of 163

UNCLASSIFIED

1.1.1.4 Requirements and Interfaces

a. The PTES Contractor shall develop, deliver, and maintain the PTES System Specification and ensure that it is compliant with the PTES System TRD (PTES-8000). [A026], [B026], [C026]

b. The PTES Contractor shall document and maintain bi-directional requirements traceability between the Government PTES Program Office controlled TRDs and ICDs, PTES CDD, PATSCONOPS, and PTES Contractor developed specifications and ICDs in a Requirements Traceability Matrix (RTM) using a DOORSv9 compatible database data, as the requirement flow-down management system. The PTES Contractor’s DOORS version shall be coordinated with the Government PTES Program Office prior to incorporation. [A027], [B027], [C027]

1. The PTES Contractor shall provide all PTES requirements documents and RTMs, e.g.

system, segments and ICDs to the Government PTES Program Office as DOORS modules.

[A027], [B027], [C027]

2. The PTES Contractor shall provide DOORS files in the following format. If the DOORS file(s) contains links to other modules, then the archive file shall be a DOORS project archive (.dpa) file. If there are no links, then the archive shall be a DOORS module archive (.dma) file.

- All DOORS module archives shall use the following naming convention:

COMPANYNAME_CDRL NUMBER_PROJECT NAME_ARCHIVEDATE.dma.

- All DOORS project archives shall use the following naming convention:

COMPANYNAME_CDRL NUMBER_PROJECT NAME_ARCHIVEDATE.dpa.

3. The PTES Contractor shall coordinate with the Government PTES Program Office to deliver a project archive that contains the appropriate link schematic. The project archive shall correctly employ the use of link modules and link sets.

4. The PTES Contractor shall ensure DOORS database delivery is in synchronization with the approved version of the specifications (Word document).

5. The PTES Contractor shall provide trace views coordinated with the Government PTES Program Office to ensure proper bi-directional requirements traceability between the Government PTES Program Office controlled TRDs and ICDs, PTES CDD, PATS CONOPS, and PTES Contractor developed specifications and ICDs.

c. The PTES Contractor shall plan and conduct monthly meetings that involve the Government PTES Program Office to mature requirements and concepts of operation. Government PTES Program Office involvement includes: attendance at the monthly meetings, review of Contractor developed operational concepts, requirements and design details associated with operations as they mature, opening issues and agreeing on closure plans.

d. The PTES Contractor shall participate in activities to assess and incorporate new or modified system requirements. This includes, but not limited to:

1. Supporting changes to PTES requirement documents and ICDs…