TO 0002-Order-SOW-CDRLs.pdf

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 lot Factory Integration Support Services

CPFF

The contractor shall provide Factory Integration Support Services IAW Basic Contract, CLIN 0010, # SOW-2020-011, Section 3.6.6, and TO 0002 SOW # 2020-011-02.

Year 1

CPFF, Term Form Task Order

78,240 Labor Hours

FOB: Destination

PSC CD: 7010

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

0002 1 lot OPTION Factory Integration Support Services

CPFF

The contractor shall provide Factory Integration Support Services IAW Basic Contract, CLIN 0010, # SOW-2020-011, Section 3.6.6, and TO 0002 SOW # 2020-011-02.

Year 2

CPFF, Term Form Task Order

78,240 Labor Hours

Section B - Supplies or Services and Prices

0003 1 lot OPTION Factory Integration Support Services

CPFF

The contractor shall provide Factory Integration Support Services IAW Basic Contract, CLIN 0010, # SOW-2020-011, Section 3.6.6, and TO 0002 SOW # 2020-011-02.

Year 3

0004 1 lot OPTION Factory Integration Support Services

CPFF

The contractor shall provide Factory Integration Support Services IAW Basic Contract, CLIN 0010, # SOW-2020-011, Section 3.6.6, and TO 0002 SOW # 2020-011-02.

Year 4

0005 1 lot OPTION Factory Integration Support Services

CPFF

The contractor shall provide Factory Integration Support Services IAW Basic Contract, CLIN 0010, # SOW-2020-011, Section 3.6.6, and TO 0002 SOW # 2020-011-02.

Year 5

Section C – Descriptions and Specifications

C1 Order of Precedence

STATEMENT OF WORK

The SOW, under Attachment 1, is incorporated into Section C1 for purposes of FAR Clause 52.215-8, “Order of Precedence”.

Section E – Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 Destination Government Destination Government 0002 Destination Government Destination Government 0003 Destination Government Destination Government 0004 Destination Government Destination Government 0005 Destination Government Destination Government

Section F - Deliveries or Performance

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAC/CAGE

0001 POP 1-SEP-2021 TO N/A N/A

31-AUG-2022 FOB: Destination

0002 POP 1-SEP-2021 TO N/A N/A

31-AUG-2022 FOB: Destination

0003 POP 1-SEP 2022 TO N/A N/A

31-AUG-2023 FOB: Destination

0004 POP 1-SEP- 2022 TO N/A N/A

31-AUG-2023 FOB: Destination

0005 POP 1-SEP 2023 TO N/A N/A

31-AUG-2024 FOB: Destination

Section G – Contract Administration Data

CLAUSES INCORPORATED BY FULL TEXT

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (DEC 2018)

(a) Definitions. As used in this clause—

“Department of Defense Activity Address Code (DoDAAC)” is a six position code that uniquely identifies a unit, activity, or organization.

“Document type” means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

“Local processing office (LPO)” is the office responsible for payment certification when payment certification is done external to the entitlement system.

“Payment request” and “receiving report” are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232- 7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall—

(1) Have a designated electronic business point of contact in the System for

Award Management at https://www.beta.sam.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF

Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1) Document type. The Contractor shall submit payment requests using the following document type(s):

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items—

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

Cost Voucher

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

See (A) above

(Contracting Officer: Insert either “Invoice 2in1” or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv) For performance based payments, submit a performance based payment request.

(v) For commercial item financing, submit a commercial item financing request.

(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF “combo” document type to create some combinations of invoice and receiving report in one step.]

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC To be completed at Contract Award Issue By DoDAAC W900KK Admin DoDAAC** To be completed at Contract Award Inspect By DoDAAC Ship To Code Ship From Code Mark For Code Service Approver (DoDAAC) Service Acceptor (DoDAAC) Accept at Other DoDAAC LPO DoDAAC DCAA Auditor DoDAAC To be completed at Contract Award Other DoDAAC(s)

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert “See Schedule” or “Not applicable.”)

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4) Payment request. The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5) Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

(g) WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity’s WAWF point of contact.

- Ronald Crowder, ronald.j.crowder.civ@mail.mil, ph 407-208-3032, Group Administrator (GAM)

- Thomas Bunch, thomas.j.bunch.civ@mail.mil, ph 407-384-3792, GAM

Officer: Insert applicable information or “Not applicable.”)

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

G2 - Contract Administration Data

Payment Instructions:

https://www.acq.osd.mil/dpap/dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions, G3 AWARD/EXERCISE OF OPTION

The Government may unilaterally exercise any or all CLINs designated as an option in Section B of this task order.

These option CLINs will be exercised at the Government’s discretion to extend the period of performance of the task order up to twelve (12) months, but may be for less time. Such options may be exercised by issuing a contract modification not later than the last day of the current period of performance. The Government shall comply with FAR 52.217-9, “Option to Extend the Term of the Contract” notice requirements.

Option CLINs Description of CLIN Exercise Period CLIN 0002 Factory Integration Support

Services 1 Sep 2022 – 31 Aug 2023

CLIN 0003 Factory Integration Support Services

1 Sep 2022 – 31 Aug 2023

CLIN 0004 Factory Integration Support Services

1 Sep 2023 – 31 Aug 2024 mailto:ronald.j.crowder.civ@mail.mil mailto:thomas.j.bunch.civ@mail.mil http://www.acq.osd.mil/dpap/dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions http://www.acq.osd.mil/dpap/dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions http://www.acq.osd.mil/dpap/dars/pgi/pgi_htm/current/PGI204_71.htm#payment_instructions

CLIN 0005 Factory Integration Support Services

1 Sep 2023 – 31 Aug 2024

Section H - Special Contract Requirements

H1 LEVEL OF EFFORT CLAUSE

(a) The Contractor agrees to provide the total level of effort specified in the next sentence in performance of the work described in Sections B and C of this task order. The total level of effort for the performance of this order shall be 78,240 total man-hours of direct labor, including subcontractor direct labor for those subcontractors specifically identified in the Contractor's proposal as having hours included in the proposed level of effort.

(b) Effort performed in fulfilling the total level of effort obligations specified above shall only include effort performed in direct support of this contract and shall not include time and effort expended on such things as local travel to and from an employee's usual work location.

(c) If the total level of effort specified in paragraph (a) above is not provided by the Contractor during the period of this contract, the Contracting Officer, at its sole discretion, shall either (i) reduce the fee of this contract as follows:

Fee Reduction = Fee x (Required LOE - Expended LOE)

Required LOE or (ii) subject to the provisions of the clause of this contract entitled "LIMITATION OF COST" (FAR 52.232-

20) or "LIMITATION OF COST (FACILITIES)" (FAR 52.232-21), as applicable, require the Contractor to continue to perform the work until the total number of man hours of direct labor specified in paragraph (a) above shall have been expended, at no increase in the fee of this contract.

(d) The Contractor shall provide and maintain an accounting system, acceptable to the Administrative

Contracting Officer and the Defense Contract Audit Agency (DCAA), which collects costs incurred and effort (compensated and uncompensated, if any) provided in fulfillment of the level of effort obligations of this contract.

The Contractor shall indicate on each invoice the total level of effort claimed during the period covered by the invoice, separately identifying compensated effort and uncompensated effort, if any.

(e) Within 45 days after completion of the work under each separately identified period of performance hereunder, the Contractor shall submit the following information in writing to the Contracting Officer with copies to the cognizant Contract Administration Office and to the DCAA office to which vouchers are submitted: (1) the total number of man hours of direct labor expended during the applicable period; (2) a breakdown of this total showing the number of man hours expended in each direct labor classification and associated direct and indirect costs; (3) a breakdown of other costs incurred; and (4) the Contractor's estimate of the total allowable cost incurred under the contract for the period. Within 45 days after completion of the work under the contract, the Contractor shall submit, in addition, in the case of a cost underrun; (5) the amount by which the estimated cost of this contract may be reduced to recover excess funds and, in the case of an underrun in hours specified as the total level of effort; and (6) a calculation of the appropriate fee reduction in accordance with this clause. All submissions shall include subcontractor information.

(f) The Government shall make fee payments to the Contractor, subject to and in accordance with the clause in this contract entitled “FIXED FEE” (FAR 52.216-8). Such payments shall be equal to To Be Completed at Base Contract Award ( %) of the allowable cost of each invoice submitted by and payable to the Contractor pursuant to the clause of this contract entitled “ALLOWABLE COST AND PAYMENT” (FAR 52.216-7), subject to the withholding terms and conditions of the “FIXED FEE” clause (percentage of fee is based on fee dollars divided by estimated cost dollars, including facilities capital cost of money). Total fee(s) paid to the Contractor shall not exceed the fee amount(s) set forth in this contract.

(g) The fee(s) specified in SECTION B, and payment thereof, is subject to adjustment pursuant to paragraph (c), above. If the fee(s) is reduced and the reduced fee(s) is less than the sum of all fee payments made to the Contractor

W900KK-20-F-CT01

under this contract, the Contractor shall repay the excess amount to the Government. If the final adjusted fee exceeds all fee payments made to the contractor under this contract, the Contractor shall be paid the additional amount, subject to the availability of funds. In no event shall the Government be required to pay the Contractor any amount in excess of the funds obligated under this.

(h) Fee(s) withheld pursuant to the terms and conditions of this contract shall not be paid until the contract has been modified to reduce the fee(s) in accordance with the "LEVEL OF EFFORT" special contract requirement, or until the Procuring Contracting Officer has advised the paying office in writing that no fee adjustment is required.

This clause does not supersede the requirements of either FAR 52.232-20 – “LIMITATION OF COST” or FAR

52.232-22 – “LIMITATION OF FUNDS.”

W900KK-20-F-CT01

Section J - List of Documents, Exhibits and Other Attachments

EXHIBITS AND ATTACHMENTS

Section J - List of Documents, Exhibits and Other Attachments

Type Name Description Attachments Attachment 1 Statement of Work, #2020-011-02 Attachment 2 DD254, DoD Contract Security Classification

Specification (See Basic Contract Attach 14)

Exhibits CDRL A201 Contractors Progress, Status and Management Report DI-MGMT-81928 CDRL A202 Report, Record of Meeting Minutes DI-ADMN-81505 CDRL B201 Platform Development Kit (PDK)n DI-MISC-80711A CDRL B202 System Integration Plan DI-MISC-80711A CDRL B203 Software Version Description (SVD) DI-IPSC-81442A CDRL B205 Consolidated User Feedback Report DI-MISC-80711A CDRL B204 Configuration Management Plan DI-SESS-81875 CDRL B207 DoD Risk Management Framework (RMF) Package

Deliverables

DI-MGMT-82001

CDRL B206 Training Materials Courseware DI-MISC-80711A CDRL B208 Test Procedures DI-NDTI-80603A CDRL B209 Test Procedure Report DI-MISC-80711A CDRL B211 Test Plan DI-NDTI-80566 CDRL B210 Test/Inspection Report DI-NDTI-80809B

SOW-2020-011-02

STATEMENT OF WORK

for the

Cyber Training, Readiness, Integration, Delivery and Enterprise Technology (Cyber TRIDENT)

Task Order Two (2) – Persistent Cyber Training Environment (PCTE) Integration Factory

U.S. Army Program Executive Office for Simulation, Training, and Instrumentation (PEO STRI)

12211 Science Drive Orlando, FL 32826-3276

Revision Number Date Log of Changes Made and Description of

Reason Changes Approved By

Table of Contents

1. SCOPE

1.1 Introduction

1.2 Goals and Objectives

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1 Program Management

3.1.1 Monthly Report

3.1.2 Associate Contractor Agreements (ACAs)

3.1.3 Schedule

3.1.4 Reserved

3.1.5 Reserved

3.1.6 Risk Management

3.1.7 Program Management Reviews (PMRs)

3.1.8 Facilities

3.1.9 Material Acquisition - Computer Hardware, Enterprise Software Solutions

(CHESS) Program

3.2 Development Operations (DEVOPS) Process

3.2.1 Capability Development, Integration, Delivery and Sustainment

3.2.2 Integration Factory

3.2.3 Integration

3.2.3.1 Third Party Onboarding and Orchestration

3.2.3.2 CI/CD Pipeline

3.2.3.3 Agile Systems Engineering

3.2.3.4 Agile Ceremonies

3.2.3.5 Requirements

3.2.3.6 Architecture

3.2.3.7 Test

3.2.3.8 Configuration Management (CM)

3.2.3.9 Release Management

3.2.4 Metrics

3.3 Operations

3.3.1 Event and Exercise Support

3.3.2 End User Outreach

3.3.3 Baseline Management

3.4 Cybersecurity

3.4.1 Security Engineering

3.4.2 Risk Management Framework (RMF)

3.4.3 OPSEC Clauses/COMSEC/Declassification

3.4.3.1 Requirements for OPSEC Training:

3.4.3.2 Anti-Terrorist Training (AT Level 1)

3.4.3.3 Active Shooter Training

3.4.3.4 Access to Government Information Systems

3.4.3.5 Professional Training and Certification

3.4.3.6 Personal Identifiable Information (PII)

3.4.3.7 Security and Access Controls

3.4.3.7.1 General Security

3.4.3.7.2 Security Clearances

3.4.3.7.3 Access and General Protection/Security Policy and Procedures

3.4.3.7.4 Handling or Access to Classified Information

3.4.3.7.5 Disclosure of Information

3.4.3.7.6 Effective Use of Controls

3.4.3.7.7 System Security Plan (SSP)

3.5 Training

3.5.1 Training Packages and Delivery

3.6 Test

3.6.1 CI/CD Testing

3.6.2 Developmental Testing

3.6.3 Operational Testing

3.6.4 Defect Management and Resolution

4. ADDITIONAL CONTRACTOR REQUIREMENTS

4.1 Interaction and/or Disclosure with Foreign Country/Foreign National

Personnel

4.2 The Enterprise-Wide Contractor Manpower Reporting Application

(eCMRA)

Statement of Work

SOW-2020-011-02

Cyber Training, Readiness, Integration, Delivery and Enterprise Technology (Cyber TRIDENT) Task Order Two (2)

1. SCOPE

This Statement of Work (SOW) defines the scope of the Project Manager Cyber Test and Training (PM CT2) Product Manager Cyber Resiliency and Training (PdM CRT) Cyber Training, Readiness, Integration, Delivery and Enterprise Technology (Cyber TRIDENT) Task Order Two (2). The Cyber TRIDENT Indefinite Delivery/Indefinite Quantity (IDIQ) is utilized by Department of Defense (DoD) organizations and other non-DoD agencies that have related cyber training needs. The Cyber TRIDENT IDIQ provides the management, integration, maintenance, and evolution for the PCTE platform, and provides total system/subsystem acquisition life cycle support for the PCTE system baseline.

This Task Order Two (2) SOW defines the detailed requirements that PdM CRT requires to have performed under the Cyber TRIDENT IDIQ contract in support of the PCTE Integration Factory.

PM CT2 defines the Integration Factory the PCTE platform under Cyber TRIDENT Task Order Two (2) to include:

• Agile Event Execution

• 3rd Party Integration and Orchestration

• Development Operations (DevOps) Tools and Support

• Agile Reporting and Metrics

• User Feedback/Prioritization

• Release Planning

• Continuous Integration / Continuous Delivery (CI/CD) Pipeline

• Configuration Management

• Training Packages

1.1 Introduction

Task Order Two (2) will provide the necessary contractor support for the Integration Factory of the PCTE capabilities. This covers the integration activities across all PCTE capabilities development to include the conduct of agile events and ceremonies, release planning and management, configuration management, the incorporation and prioritization of user feedback, training package development and delivery, and the overall management of the CI/CD pipeline.

1.2 Goals and Objectives

The objective of Cyber TRIDENT Task Order Two (2) is to provide the Integration Factory for the evolving PCTE capabilities. Cyber TRIDENT Task Order Two (2) will specifically support the integration activities required to support the evolving PCTE capabilities utilizing an agile methodology for the development, testing, training and fielding efforts in compliance with all Army and DoD regulations and policies. The Task Order Two (2) Integration Factory will support PCTE in realizing their agile vision to provide a standardized platform with ecosystem of capabilities to shape, execute and reuse multiple training environments/scenarios.

2. APPLICABLE DOCUMENTS

The applicable documents listed in the Base SOW are applicable to Task Order 2. Reference Section 2 of the Base SOW for full list.

3. REQUIREMENTS

The contractor shall provide an Integration Factory support of the PCTE capabilities. The contractor shall deliver platform capabilities for integration, to include performing testing prior to fielding the platform. This will require such activities that include agile event execution, 3rd party integration and orchestration, DevOps tools and support, agile reporting and metrics, user feedback prioritization, release planning, CI/CD Pipeline management, configuration management, training packages and testing support to ensure compliance with contract requirements and timely delivery of required products. The contractor shall provide engineering, materials, equipment, testing, technical and operations support for the PCTE as described in this Task Order Two (2) SOW.

3.1 Program Management

The contractor shall provide the overall management and administrative effort necessary to ensure that the requirements of this Task Order Two (2) are accomplished. The contractor shall track Task Order (TO) progress, deliverables, and financials utilizing metrics specified by the Government.

3.1.1 Monthly Report

The contractor shall submit a Contractor’s Progress and Status Report that provides information to include but not limited to schedules, accomplishments, metrics, risks, issues, problems, and deficiencies related to this TO’s activities. The monthly report shall include, but not be limited to, status on the below requirements:

• Financial Data

• Agile Event Execution

• 3rd Party Integration and Orchestration

• Development Operations Tools and Support

• Agile Reporting and Metrics

• User Feedback/Prioritization

• Release Planning

• Continuous Integration/Continuous Development Pipeline

• Configuration Management

• Training Packages

• Testing Results

• Status of Risk Management Issues and Resolutions

CDRL Number CDRL Name CDRL A201 Contractor’s Progress and Status Report, DI-MGMT-81928

3.1.2 Associate Contractor Agreements (ACAs)

The contractor shall implement ACAs with other PCTE and third-party contractors as required for exchanging data, accessing and using third party software and equipment, receiving technical support, working interface and integration issues, and DoD Cyber user event planning and execution. The contractor shall ensure that ACAs are maintained to achieve development of the platform and maintain PCTE interoperability and event planning and execution, as applicable.

ACAs shall provide for and permit the complete and unbiased exchange of technical information and data relating to PCTE integration, development and deployment. Agreements shall be structured so that all Cyber TRIDENT and PCTE contractors are obligated to protect proprietary data and classified information from all unauthorized use or disclosure. ACAs shall be submitted to the Government for review prior to execution.

3.1.3 Schedule

The contractor shall plan, execute and deliver contributions within the Government agile scrum processes. The contractor shall align the schedule to trace to the Agile ceremonies and Industry best practices such as sprint duration, release planning, and other appropriate Agile planning processes. The contractor shall deliver in accordance with the government led monthly sprint periods resulting in incremental capability improvement/incorporation leading to six (6)-month formal releases.

3.1.4 Reserved.

3.1.5 Reserved.

3.1.6 Risk Management

The contractor shall promptly notify the Government of contract performance risks, issues, problems, and deficiencies and shall embed risk management as part of the Agile software development process. In accordance with the contractor’s risk management plan, implement risk detection and identification, assignment of risk categories, risk mitigation planning, mitigation plan implementation, corrective action, tracking of compliance, reporting of status and planning for risk abatement. The contractor shall promptly provide and execute corrective actions plans, in consultation with the Government. The contractor shall include in each Contractor’s Progress and Status Report the status of all outstanding contract performance risks, issues, problems, and deficiencies, as well as corrective actions with respect thereto.

3.1.7 Program Management Reviews (PMRs)

The contractor shall host Program TO Reviews quarterly (per year) to inform the Government of TO risks and issues. The contractor shall conduct Technical Interchange Meetings (TIMs) and In Progress Reviews (IPRs) as directed by the Government. The reviews shall provide a forum for IPT members to clarify the following areas of this TO to include but not limited to:

• Cybersecurity Management and Compliance

• IT Support

• Facilities

• Development RCS, Production RCS

• Logistics

The meetings shall be conducted at the contractor’s facility. PMR shall cover TO program risks and issues that can affect the entire Cyber TRIDENT portfolio, including parallel TOs/DOs-specific issues and risks as appropriate. The contractor shall post agendas and meeting minutes to established web portals or SharePoint sites.

CDRL A202 Report, Record of Meeting/Minutes, DI-ADMN-81505

3.1.8 Facilities

The contractor shall conduct the Government interactions to include the Agile ceremonies such as daily standups, sprint preplanning, and other associated meetings at the contractor’s facility which shall be located no more than ten (10) miles from PEO STRI.

3.1.9 Material Acquisition - Computer Hardware, Enterprise Software Solutions (CHESS) Program The contractor shall procure hardware, software, and licensing to support the TO 2 Integration Factory activities. TO 1 shall track, inventory, and maintain detailed information on procurements made under TO 2. The contractor shall comply with the Army’s CHESS program when making procurements. Under Program Executive Office Enterprise Information Systems (PEO EIS), CHESS is the mandatory source for commercial Information Technology (IT) purchases. CHESS contracts provide IT products and services that comply with U. S. Army Network Enterprise Technology Command (NETCOM), Army and DoD policy and standards.

Purchasers of commercial hardware and software must satisfy IT requirements by utilizing CHESS contracts and DoD Enterprise Software Initiative agreements first, regardless of dollar value. Any purchase made outside of CHESS contracts requires a waiver. A complete list of CHESS contracts and the on-line waiver process can be found at:

https://protectus.mimecast.com/s/yDPLCR6K3OIrGJ7iqywOR?domain=chess.army.mil https://protectus.mimecast.com/s/yDPLCR6K3OIrGJ7iqywOR?domain=chess.army.mil

3.2 Development Operations (DEVOPS) Process

3.2.1 Capability Development, Integration, Delivery and Sustainment

The contractor shall develop and execute the holistic Government led DevOps process for developing, integrating, testing, deploying, and sustaining the PCTE platform. The DevOps process shall cover the stages and feedback loop depicted in Figure 1, the DevOps Infinity. The DevOps process shall also include CMF feedback at each stage of the DevOps Infinity. The DevOps process shall create a culture that emphasizes the collaboration of PCTE vendors, operations, quality assurance, and cyber security teams throughout the PCTE platform lifecycle.

The DevOps processes shall allow teams to work together to optimize both the productivity of PCTE vendors and reliability of operations. The DevOps process shall allow teams to communicate frequently, increase efficiencies, and improve the quality of services provided to the CMF.

Figure 1 DevOps Infinity

The DevOps process shall encompass an Agile System Engineering process which includes but is not limited to concept development, requirements engineering, system architecture, system design and development, system integration, test/test engineering and evaluation, security engineering, and operations and maintenance. The Agile Systems Engineering process shall include Agile ceremonies to develop, refine, and prioritize requirements as well as plan and monitor the development, testing, integration, and deployment of the PCTE platform. The Agile Systems Engineering process shall include traditional Government ceremonies such as but not limited to Systems Requirement Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Integration, Verification and Validation (IV&V), and Test Readiness Review (TRR). The Agile Systems Engineering process shall include a Configuration Management (CM) process to maintain the integrity of the components, services, products, assets, and content throughout the PCTE life cycle. The Agile System Engineering process shall include a process for releasing software to the CMF. The DevOps process shall include a feedback loop from the CMF that includes but is not limited to new features, enhancements, and bugs. The DevOps process shall also include a feedback loop from Technical Operations Staff that includes but is not limited to system performance issues, artifacts regarding bugs, recommendations for improving system performance, and recommendations for improving deployments.

To execute the DevOps process, the contractor shall provide an integration factory which includes but is not limited to a collaborative meeting space, development environment (i.e.

Remote, Compute, and Storage), and tools. The contractor shall onboard PCTE vendors to the development environment which includes but is not limited to account creation, access to infrastructure, access to tools, installing/configuring 3rd party hardware and software, and installing content. The development environment shall include CI/CD pipelines that automate the staged build, test, integration, release, and deployment of all PCTE vendor software and content.

3.2.2 Integration Factory

The contractor shall perform integration factory activities to include recommending improvements to the current integration factory development environment to increase the quality of the software and release frequency. The contractor shall maintain and enhance the current implementation of the development environment documented in the PCTE PDK. The development environment shall be remotely accessible to all PCTE team members at any time except for during maintenance windows. The development environment shall be remotely accessible from anywhere. The development environment shall include but not limited to the following zones: development, testing, quality assurance, staging, and production. The contractor shall be able to automate the creation of new zones when directed by the Government.

The zones shall provide sandboxes for the PCTE vendors that protect their intellectual property (IP). The contractor shall be able to automate the creation new sandboxes when onboarding new vendors, supporting canary releases, supporting operational tests, or whenever directed by the Government. The contractor shall automate the creation of the development environment, maintain it, and evolve it as directed by the Government. The development environment shall allow for the creation of CI/CD pipelines that automate the staged build, test, and integration of all PCTE vendor software and content described in section 3.2.3.2. The development environment shall be integrated with the integration factory tooling to support CI/CD activities.

The contractor shall document the development environment design using the integration factory tooling and in the PCTE PDK as directed by the Government. The contractor shall maintain and enhance the development environment as directed by Government.

The contractor shall recommend improvements to the current integration factory tooling to increase the quality of the software and release frequency. The contractor shall maintain and enhance the current integration factory tooling documented in the PCTE PDK as directed by the Government. The integration factory shall include but not be limited to the following tools:

• Requirements management tools

• Collaborative wiki

• Chat

• Video and audio teleconferencing tools

• Software version control tool

• Configuration management tools

• Software Artifact Repository

• Automation server

• License management tools

• Test case management tools

• Static code analysis tools

• Testing Tools (Supports the type of testing described in section 3.2.3.7)

• Security Tools (Supports security activities described in section 3.4)

The contractor shall develop a Continuity of Operations Plan (COOP) and implementation ensuring that critical integration factory functions continue when the development environment and/or tooling experiences issues. The contractor shall develop and implement a data backup and recovery plan in the event of a storage failure.

CDRL B201

Platform Development Kit (PDK), DI-MISC-80711A

3.2.3 Integration

The contractor shall manage, execute, and integrate products developed by current and future PCTE training capability vendors into a unified system of systems. The contractor shall integrate third party vendor contributions into an overall PCTE integration package to include documentation. The contractor shall package the comprehensive PCTE system in a manner that is rapidly deployable to PCTE RCS nodes to enable iterative assessment by CMF operators. The contractor shall manage, execute and support the acceptance modification and test of future capabilities into the PCTE platform. As a result of the PM’s release schedule and strategic vision, the contractor shall establish an integration schedule, strategy and environment that provides an online, interactive, and collaborative environment, which is protected with access control. The Government and contractor/subcontractor team members shall be able to exchange information and collaborate in a distributed environment. The contractor shall provide an integration schedule and strategy that addresses integrating all the work efforts identified as ready to be integrated into the PCTE production system. The contractor shall monitor the development process and work to ensure each vendor is aware of the scheduled updates into the existing system(s). The contractor shall manage the integration process and identify any issues or potential problems any vendors will have with other existing assets and identify what will be used as the baseline to build upon and which resources will be reused as part of the legacy assets.

The contractor shall provide documentation which describes each vendor will interface with the development system using Agile methodology. The contractor shall ensure each vendor provides updates to the documentation for each component of the system. The integration environment, shall be based on processes and standards construct that supports data and requirements management, stores collaborative artifacts, software, tools, PDK, and architecture products. The contractor's integration and testing processes shall ensure that new provided capabilities, handover packages, change sets, and bug fixes are fully implemented and satisfy their requirements and respective Use Cases without impacting existing capability prior to integration into the main PCTE baseline.

CDRL B202 System Integration Plan, DI-MISC-80711A

3.2.3.1 Third Party Onboarding and Orchestration

The contractor shall manage, execute and host as well as participate in third party vendors interaction and handover meetings. The contractor shall work with other industry partners and users of the system to identify and develop capabilities that support cross-developer interactions, and service-specific uses of system. The contractor shall monitor the system capabilities that are developed/integrated by third party vendors, and keep the Government informed on the progress of such efforts. The contractor shall provide the architectural, and engineering support required to support the third-party vendors in product deliveries. The contractor shall analyze proposed handovers for impact on the baseline configuration and provide recommendations for inclusion.

With Government concurrence, the contractor shall accept, modify, integrate, and test handover packages, new capabilities, change sets, and PTR/Discrepancy Report (DR) fixes from vendors following established processes. These capabilities shall become part of the formally managed software baseline

3.2.3.2 CI/CD Pipeline

The contractor shall leverage the integration factory tooling to design, implement, and support the execution of Continuous Integration (CI) pipelines for all PCTE vendor software and content in accordance with the contractor’s Agile system engineering process. The contractor shall implement CI pipelines that automate the staged build, test, and integration of PCTE vendor software and content. The contactor shall implement CI pipelines with the required stages to automate functional and nonfunctional gates to progress software and content across but not limited to Development, Test, Quality Assurance, Security, Scalability. The contractor shall implement CI pipelines that automate the promotion of software and content between stages via human in the loop or when automated testing passes.

The contractor shall extend the CI pipelines to form Continuous Delivery (CD) pipelines to deploy the software and content as well as release it in production. The contractor shall implement CD pipelines that rapidly and safely deploy and test software as well as content in a production-like environment and releases the software and content in production. The contractor shall implement stages in the pipelines that allow software and content to go through automated testing in a production-like environment. The contractor shall implement CD pipelines that allow the organization to make the decision on whether to release the software and content in production when the software passes automated testing. Using the CD pipelines, the contractor shall release new features to the CMF and ensure those releases are stable. The contractor shall continually monitor the PCTE platform’s health and security once the updates are deployed.

After deploying to production, if issues are encountered, the contractor shall execute automated procedures for rolling back to a healthy PCTE platform state.

The contractor shall provide the PCTE vendors a visualization of the execution status of their CI/CD pipelines. The contractor shall provide the Government a visualization of the execution status of all CI/CD pipelines. The contractor shall automate the reporting of issues that are discovered during the execution of each CI/CD pipeline to the PCTE vendors and Government.

The contractor shall maintain and resolve issues with visualization of CI/CD pipelines and automated issue reporting.

The contractor shall maintain and resolve issues with the CI/CD pipelines. The contractor shall collaborate with PCTE vendors to resolve vendor software and content issues that are discovered during the execution of all CI/CD pipelines as directed by the Government. The contractor shall Analyze production system performance and errors and collaborate with PCTE vendors to mitigate problems in the system design stage.

The contractor shall recommend improvements to the current CI/CD pipelines to increase the quality of the software and release frequency. The contractor shall maintain and enhance the current implementation of the CI/CD pipelines documented in the PCTE Platform Development Kit (PDK).

3.2.3.3 Agile Systems Engineering

The contractor shall manage, execute, and apply agile methodologies based on industry best practices for all PCTE development efforts. The contractor shall work with the Government, vendors, sub-contractors in identifying the necessary and sufficient fundamental concepts for the process to be agile. The contractor shall ensure all work is defined and planned using the agile sprint methodology, using a defined product backlog, sprint review and planning cycle with the goal of having a shippable product at the end of each sprint. The contractor's agile process shall achieve results through continuous iterative development of capability enhancements for the PCTE platform. The contractor shall provide a prompt response to emerging needs, demonstrated reliability, on reoccurring release cycles. The contractor shall plan, schedule, and execute all agile ceremonies, including sprint planning and review sessions, daily sprint standups, sprint retrospectives and sprint demonstrations. The contractor shall provide the requisite technical and programmatic support to complete the required tasks for each vendor associated with the PCTE engineering and management. These tasks shall encompass the efforts associated with the development, dissemination, engineering, management, and maintenance of the PCTE architecture, components, and documentation. These tasks shall also include the work efforts associated with the engineering, management, and tracking of PCTE fielded products, PCTE services and platform. The contractor shall identify an agile means of developing, integrating, testing and releasing the PCTE platform consisting of various contributions through an agile methodology facilitating CMF user feedback.

3.2.3.4 Agile Ceremonies

The contractor shall plan, schedule, lead, and facilitate all Agile ceremonies. The contractor shall recommend improvements to existing Agile process and ceremonies documented in the PCTE PDK to improve velocity, increase transparency of vendor progress, reduce meetings, and make best use of the participants time. The contractor shall recommend new agile methodologies or processes to increase efficiencies. The contractor shall execute the agile ceremonies in the collaborative environment described in section 3.2.2. The contractor shall execute the Agile ceremonies across all PCTE vendors and provide the Government with regular visibility into the status of PCTE platform development. The contractor shall manage the Product Backlog, as directed by the Government Product Owner. Product Backlog management includes but is not limited to creating, refining, removing and Prioritizing requirements. The contractor shall maintain configuration management over the Product Backlog and ensure that the state of the Product Backlog aligns with actual development such as but not limited to video and audio teleconferencing tools, requirements management tool, collaborative wiki, and chat. The contractor shall recommend agile metrics to provide the Government visibility into the status of the PCTE platform development and vendor performance. The contractor shall leverage the integration factory to capture and report agile metrics such as but not limited to burn down, burn up, velocity.

3.2.3.5 Requirements

The contractor shall manage, execute, and provide overarching support for the capabilities needed to support the PCTE program requirements for development, test, integration, interoperability, support, and delivery of software, data, and documentation to the Government.

The contractor shall evolve the PCTE architecture over time to address new requirements and to keep pace with the advancing technical environment through the system engineering process.

The contractor shall provide updates to the Platform Development Kit as well as update the Government on the capability enhancements to ensure new requirements for PCTE is continuously being developed and integrated into the baseline resulting in multiple version releases each year. The contractor shall record, maintain, analyze customer requirements, and user feedback, needed to continuously ensure maximum utilization of the system throughout the development.

3.2.3.6 Architecture

The contractor shall develop and execute governance processes, ceremonies, and use the integration factory tooling to develop PCTE system requirements and architecture in accordance with the contractor’s Agile system engineering process. The contractor shall develop processes, ceremonies, and use the integration factory tooling to govern the PCTE architecture including but not limited to implementing a system of controls over the creation and monitoring of all architectural components and activities, implementing a system to ensure compliance with internal and external standards, developing practices that ensure accountability to a clearly identified stakeholder community, both inside and outside the organization. The governance processes and ceremonies shall ensure that all updates to the PCTE Architecture are approved by the Government prior to implementation. The governance processes and ceremonies shall ensure the PCTE Architecture is highly cohesive, loosely coupled, and have severable components to have an open systems architecture capable of procuring at the component level. When developing the PCTE architecture, the contractor shall consider the entire lifecycle of the system including but not limited to development, maintenance and deployment. The governance processes and ceremonies shall ensure architecture is designed for extensibility, scalability, maintainability, availability, usability and security using an approach that is based on open system standards, products and patterns. The contractor shall define and record the PCTE operational concept for the system, architectural design of the system (identifying the components of the system, their interfaces, and a concept of execution among them), and the traceability between the system components and system requirements. The contractor shall research and evaluate the existing PCTE architecture documented in the PCTE PDK and recommend and implement modifications which enable the Government’s ability to continually integrate new vendor products. The contractor shall ensure the analysis and results of the governance processes and ceremonies are documented using the integration factory tooling and in the PCTE PDK as directed by Government. The contractor shall maintain and update the PCTE PDK which includes the PCTE architecture, platform integration points, and Government Owned Application Programming Interfaces (APIs). The contractor shall leverage and improve the existing PCTE Architecture Working Group (AWG) to implement governance processes.

The contractor shall use the Agile ceremonies to document and prioritize PCTE system requirements as directed by the Government Product Owner. The contractor is encouraged to suggest revisions to Government requirements where such revisions would result in cost or schedule reduction or performance improvements. The contractor shall evaluate the PCTE cybersecurity requirements to assess any impacts on developed capability and provide potential solutions, if applicable. In addition, the contractor shall determine if existing open source products are capable of meeting any operational capabilities, perform a detailed product reuse evaluation, and document the results of the analysis. The contractor shall conduct architecture evaluations, including stakeholders external to the contractor’s organization, for each iteration of PCTE. The contractor shall use the Enterprise Initiatives and technologies to evolve the PCTE architecture based on changes to technology, threat, and tactics, techniques and procedures.

The contractor shall support the PCTE PM Office as DoD Enterprise Initiatives are assessed to understand and define the impact to PCTE. The contractor, along with the Government staff, shall introduce stewardship and management of the Enterprise Initiatives policies and process.

The contractor shall use the Enterprise Initiative process to evolve changes based on technology, threat, and tactics, techniques and procedures. Enterprise Initiatives bring value to the organization as more lines of business participate thus ensuring the collaboration and participation across the entire enterprise drives system and component development. The contractor shall use Enterprise Initiatives as a means of incorporating new/updates to system components through analysis and registration, developing "rules of engagement" for collaboration, defining quality expectations and rules, monitoring and managing quality of the system, and changes to needs of the users through offerings and research.

3.2.3.7 Test

The contractor shall support the continuum of PCTE platform testing across the agile development lifecycle in accordance with Section 3.6.

3.2.3.8 Configuration Management (CM)

The contractor shall initially sustain and mature the current CM methodology to establish and maintain the integrity of the components, services, products, and assets throughout the PCTE life cycle. CM shall be implemented throughout the entire period of execution for all components, services, products, and assets of the PCTE system. CM shall be a proactive activity within the

PCTE system. CM shall identify, track, and document configuration items, control the configuration items and changes to them, and record and report status, and change activities to these configuration items. CM shall function as a multidimensional version of a typical CM process (multi-phased, multi-program, multi-tiered, multi-instantiated, and multi-baseline), binding the PCTE products and activities. CM shall support parallel development, distribution, and build releases. CM shall address use by all developers, products, and vendors.

The contractor’s CM efforts shall:

a) Identify the configuration items, components, and related work products that will be placed under configuration management

b) Establish and maintain a configuration management and change management system for controlling work products

c) Create or release baselines for internal use and for delivery to the customer

d) Track change requests for the configuration items

e) Control changes in the content of configuration items

f) Establish and maintain records describing configuration items, and

g)…