Attachment_01-OneSAF_IDIQ_PWS-20241024-TrackChanges.pdf

CUI

Performance Work Statement (PWS) For

One Semi-Automated Forces (OneSAF)

PRODUCTION AND SUPPORT

Indefinite Delivery / Indefinite Quantity

(ID/IQ)

20 Aug24 October 2024

Version 1.3

Prepared by

U.S. Army PEO Simulation, Training, and Instrumentation

(PEO STRI)

12211 Science Drive Orlando, FL 32826-3276

DISTRIBUTION STATEMENT A. Approved for public release: distribution unlimited.

Revision Level

Document Date Summary of Change Pages Affected

1.0 25 September 2023 Initial release of Draft RFP All

1.1 12 February 2024 Update to draft All

1.2 24 June 2024 Update due to SRB comments All

1.3 20 August 2024 Updates f romfrom offerors’ questions

All

1.4 24 October 2024 Updates from offerors’ questions All

Summitted by:

Angela Stacy Assistant Program Manager Angela Stacy

APM

PEO STRI; Program Management Synthetic Environment (PM SE);

Product Directorate Next Generation Constructive (PD NGC)CSS

Controlled by: PEO STRI Controlled by: PM SE, PD NGC CUI Category: Procurement Distribution Dissemination: FEDCON POC: Angela Stacy,407-208-5910, angela.s.stacy.civ@army.mil

Table of Contents

1. SCOPE

1.1. Background

1.2. Development Environment

2. APPLICABLE DOCUME NTS

2.1. Department of Defense (DoD Guidance)

2.2. Other Government Documents, Drawings, and Publications

2.3. Other OneSAF Products

3. REQUIREMENTS

3.1. Program Management

3.1.1. Contract Management

3.1.2. Service Contract ReportingEnterprise-wide Contractor Manpower Reporting Application

(SCReCMRA )

3.1.3. Subcontractor Management

3.1.4. Financial Management

3.1.5. Risk Management

3.1.6. Organizational Process Management

3.1.7. Government Furnished Equipment (GFE) Management

3.1.8. Purchase of Commercial Information Technology (IT) Equipment

3.1.9. Integrated Product Teams (IPT)

3.1.10. Post Award Conference (PAC)

3.1.11. Personnel Requirements

3.1.11.1. Key Personnel

3.1.11.2. Cyberspace Workforce Management

3.1.11.3. Security Clearances

3.2. OneSAF Processes

3.3. Systems Engineering

3.3.1. Systems Integration

3.3.2. Software Engineering and Development

3.3.3. Quality Assurance (QA)

3.3.4. Configuration Management (CM) and Control

3.4. OneSAF Software Product Line Management and Support

3.5. Test Program

3.6. Maintenance and Problem Ticket Report (PTR) Support

3.7. Co-Developer Support

3.8. Cloud Enabled

3.9. OneSAF Software Product Baseline Release… ................................................................................ …. 19

3.10. Tailored OneSAF Software Product Baseline Release

3.11 Capability Development

3.11.1. Concurrency Capability Development

3.11.1.1. Mission Command Adapter (MCA)

3.11.1.2. Standard File Format (SFF)

3.11.1.3. Environmental Runtime Component (ERC)

3.11.1.4. Military Organization and Equipment Representation Currency

3.11.2. P3I Capability Development

3.11.3. Bifrost Maintenance

3.12. Customer Support

3.12.1. Foreign Military Sales (FMS) Support

3.13. OneSAF Help Desk

3.14. Software Distribution

3.15. Traini ng

3.16. OneSAF Integrated Development Environment (IDE) Government Facility & Facilities

3.16.1. Government Furnished Information (GFI)

3.16.2. Government Provided Facility (GFE/GFIPF) Obsolescence/Technology Ref resh

3.16.3. IDEDevelopment Environment Extensions

3.16.4. Government Provided Facility (Development EnvironmentGPF) Documentation

3.17. Transition

3.17.1. Transition-In Plan

3.17.2. Transition-Out Plan

3.18. Cybersecurity

3.18.1. OneSAF Application Cybersecurity

3.18.2. Cybersecurity

3.18.3. Cybersecurity Personnel

3.19. Security

13.19.1. Safeguards

13.19.2. Dissemination Of Export-Controlled Technic al Information and Data

3.20. Operations Security (OPSEC)

3.20.1. Common Access Card (CAC) Protection Policy and Procedures

3.20.2. Performance or Delivery in a Foreign Country

3.20.3. Handling or Access to Classified Information

3.20.4. Army Traini ng Certification Tracking System (ATCTS) Registration

3.20.5. Antiterrorism (AT Level I) Training

3.20.6 AT Awareness Traini ng

3.20.7. OPSEC Training

3.20.8. Threat Awareness Reporting Program (TARP)

3.20.9. Cybersecurity/Information Technology (IT) Traini ng

3.20.10. Cybersecurity/IT Certification

3.20.11. Controlled Unclassified Information (CUI)

3.21. Travel

3.22. Technical Data, Noncommercial Computer Software and Noncommercial Computer Software Documentation

3.23. Data Handling of CUI

3.23.1. Definition

3.23.2. Safeguarding CUI

3.23.2.1. Control Unclassified Information (CUI)

3.23.2.2. During Duty Hours

3.23.2.3. During non-Duty Hours

3.23.2.4. Transmission of CUI Information

3.23.2.5. Termination, Disposal, and Unauthorized Disclosure

3.23.2.5.1. Termination

3.23.2.5.2. Disposal

3.23.2.5.3. Unauthorized Disclosure

3.24. Logistics

3.24.1. Definitions

3.24.2. Accountability

3.24.2.1 Property Management System (PMS) Procedures……………………………………………………………39

3.24.3. Other Direct Charges (ODCs), Material Purchases, and Contractor Acquired Property (CAP)…...…...39

4. ACRONYM LIST

Performance Work Statement Forfor One Semi-Automated Forces (OneSAF)

1. SCOPE

This Performance Work Statement (PWS) defines the effort required for providing the capabilities needed to execute the overarching OneSAF program requirements for development, test, integration, interoperability, support, and delivery of software, data, and documentation products to the Assistant Program Manager OneSAF (APM OneSAF); the U.S. Army Modeling and Simulation (M&S) Communities (Acquisition, Analysis, Experimentation, Intelligence, Test and Evaluation, and Training); and the rest of the OneSAF User Community. The OneSAF User Community includes, without limitation, other U.S. Army Program Executive Offices (PEOs) and Program Managers (PMs), Training and Doctrine Command (TRADOC) Battle Labs, Research Development and Engineering Centers (RDECs) and agencies, other Department of Defense Services and Joint agencies, Government civilian organizations and agencies, academic institutions, foreign countries, and other OneSAF Co-Developers. OneSAF supports modeling and simulation of force modernization and transformation from weapons systems. OneSAF supports the Army goal of cloud and web-based software application development in order to reduce hardware and support costs plus to enable rapid training at both home station and distributed locations.

OneSAF is a software product line consisting of a set of interacting components where multiple components utilize common services to satisfy a diverse set of OneSAF use cases. The OneSAF Product Line Architecture Specification (PLAS) defines the System Compositions, Products, and Components within the OneSAF product line. The PLAS defines and describes the overall architecture that governs the products and components within the OneSAF product line and illustrates how the product line can be used to construct systems that meet the OneSAF requirements.

The OneSAF Production & Support effort consists of conceptual modeling, architectural, engineering, and software support required to enhance the OneSAF product line and correct deficiencies identified by the OneSAF Community. With Government concurrence, the OneSAF effort also includes accepting, modifying, integrating, and testing handover packages and new capabilities in support of the requirements of the OneSAF User Community. The effort also provides life cycle sustainment of annual version releases. This life cycle sustainment involves addressing maintenance updates, Problem Ticket Reports (PTRs), and security patches. The effort also entails on-site and remote support and training for the worldwide OneSAF Community. The effort includes final acceptance and test activities required to deliver the annual and tailored version releases and patches to support OneSAF Community requirements.

1.1. Background

OneSAF was formalized as an acquisition program in April 2000 with its designation as an Acquisition Category (ACAT) III program and delegation of the Milestone Decision Authority (MDA) to Commanding General (CG), Army Materiel Command

(AMC). OneSAF was formally chartered on 01 May 2000 by the Army Acquisition Executive (AAE) to manage all OneSAF efforts. On 16 May 2000, the MDA responsibility was delegated to the Commander STRICOM (subsequently re-designated as PEO STRI). In December 2003, Milestones B/C were approved by the MDA and the program moved forward with development of the Full Operational Capability (FOC) baseline. FOC was met in March 2006 and fielding was initiated in September 2006 with the release of OneSAF Version 1.0. Additional versions continue to be fielded with Pre-Planned Product Improvements (P3I) and Co- Developer handovers integrated into the baseline. OneSAF Version 12.0 was released in April 2023; Version 12.1 was released in April 2024 and Version 12.2 is planned for release in November of 2024. OneSAF reached the ACAT II status and is currently in the support phase of the life cycle with ongoing software production and implementation of P3I as approved by the TRADOC Project Office (TPO) OneSAF.

1.2. Development Environment

OneSAF Program has established a development environment that brings together Community/User representatives, Government team members, and Contractor software developers into a single government owned environment. The OneSAF contractor shall maintain the integration, development, and test environment accessible by the OneSAF Community of users; OneSAF Government team; and the OneSAF contractor’s Integrated Product Team (IPT) members. This development environment shall provide a working environment for Contractors with access to all network infrastructure and software needed to promote effective software development. The development environment can be remote and/or in the government provided integrated development environment (IDE) facility performance location. The development environment shall be a Common Access Card (CAC)-enabled, protected network-connected environment that provides for development, integration, and testing of the OneSAF software. This environment provides the ability to share information to all authorized Government organizations, users, and developers simultaneously through CAC enabled Government accessible portals. The development environment allows the contribution of ideas, comments, suggestions, as well as exchanging program information, and collaboration in a distributed environment.

Through these efforts, capability enhancements are continuously being developed and integrated into the baseline, typically resulting in at least an annual version release.

OneSAF has been fielded to multiple Army users within the U.S. Army M&S Communities, as well as other Department of Defense (DoD) agencies and a multitude of industry, Foreign Military Sales (FMS), and academic locations. Concurrent with operations and applicable to future task orders such as: P3I enhancements, base program requirements, Co- Developer integrations, FMS cases, UnITE, customer funded efforts, internal enhancements, enterprise efforts, trade studies, Analysis of Alternatives (AoA), Integrated Development Environment (IDE) IDE efforts, research, pilots, and user feedback; these needs are continuously addressed to assure maximum utilization of the system throughout the growing User Community.

2. APPLICABLE DOCUMENTS

The following documents (or their most current and approved iteration) form a part of this PWS to the extent specified herein. In the event of a conflict between documents referenced herein, the inconsistency shall be resolved by giving precedence in the following order: (1) the contents of this PWS, the contents of the PWS shall be the governing requirement, (2) all remaining documents unless otherwise stated.

2.1. Department of Defense (DoD Guidance)

The following DoD guidance documents are available on the WWW at URL:

https://www.esd.whs.mil/DD/

32CFR, Part 117 National Industrial Security Program Operating

Manual (NISPOM) DoDD 8140.01 CYBERSPACE WORKFORCE MANAGEMENT

DoDI 8140.02 IDENTIFICATION, TRACKING, AND REPORTING

OF CYBERSPACE WORKFORCE

REQUIREMENTS

DoD-M 8140.03 CYBERSPACE WORKFORCE QUALIFICATION

AND MANAGEMENT PROGRAM

DoDI 5000.02 Operation of the Defense Acquisition System

DoDI 5000.64 Accountability and Management of DoD Equipment and Other Accountable Property

DoDI 8500.01 Cybersecurity DoDI 8510.01 Risk Management Framework (RMF) for DoD

Information Technology (IT)

DoDI 5200.46 DoD Investigative and Adjudicative Guidance for Issuing Common Access Cards (CAC)

DoDM 5200.48 DoD Instruction Controlled Unclassified Information

(CUI)

The following DoD guidance documents are available on the WWW at URL:

https://www.acquisition.gov/

DFARS 252.225-7043 Antiterrorism/Force Protection for Defense Contractors

Outside the US

FAR 31.205-46 Travel Costs FAR 52.216-7 Allowable Cost and Payment

2.2. Other Government Documents, Drawings, and Publications

The following are available on the WWW at URL:

http://csrc.nist.gov/publications/PubsSPs.html

NIST SP 800-53 Assessing the Security Controls in Federal Information Systems and Organizations

NIST SP 800-171 Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations

The following are available on the WWW at URL https://armypubs.army.mil/

Army Regulation (AR) 25-1

Army Information Technology

AR 25-2 Army Cybersecurity

AR 380-5 Department of the Army Information Security Program

AR 380-10 Foreign Disclosure and Contact with Foreign Representatives

AR 380-49 Industrial Security Program

AR 380-67 Personnel Security Program

AR 381-12 Military Intelligence

AR 525-13 Antiterrorism

AR 530-1 Operations Security (OPSEC)

AR 710–2 Inventory Management

AR 710-4 Property Accountability Policies

The following are provided with the applicable web link:

https://assist.dla.mil/online/start/

MIL-STD-961E Unique Data Item Descriptions (UDIDs) MIL-STD-963C Data Item Descriptions (DIDs)

Joint Travel Regulation https://www.travel.dod.mil/Policy-Regulations/

Army Cloud Plan https://api.army.mil/e2/c/downloads/2022/10/14/106b220e/army-cloud-plan- 2022.pdf

2.3. Other OneSAF Products

The following Technical Data Package artifacts shall be provided:

OneSAF v12.0 Accreditation Documentation OneSAF v12.0 application software, documentation, and training materials OneSAF v12.0 RIB Items OneSAF v12.0 Use Cases

OneSAF Distribution Agreement (DA) OneSAF Electronic Process Guide (EPG) OneSAF Product Line Requirement Specification (PLRS) OneSAF Product Line Architecture Framework (PLAF) OneSAF Product Line Architecture Specification (PLAS) OneSAF System Integration Plan (SIP), Revision 17 January 2023

The table below Exhibit A – List of CDRLs contains the potential deliverable items, not all inclusive, that may be identified at the Task Order (TO) level, throughout the life of this contract. Additional deliverable items shall may be identified on each individual TO as required per the requirements.

CDRL # DID CDRL Title CDRL Subtitle Due to Gov

Preliminary/ Final

Days for Gov

Review

Days to Incorp.

Comments

A001 DI-MGMT- 80227

Contractor's Progress, Status and Management

Report

CPSMR

SHALL BE DUE 30

DAYS AFTER

CONTRACT AWARD.

SHALL CONTINUE

MONTHLY

THROUGH THE

LIFE OF THE

CONTRACT.

20 10

A002 DI-MISC- 80711A

Scientif ic and

Technical Reports

Process Report

SHALL BE DUE 120

DAYS AFTER PAC.

SHALL BE DUE

THREE TIMES

ANNUALLY

THROUGH END OF

CONTRACT.

30 20

A003 DI-MGMT- 81334

Contract Work

Breakdown Structure

SHALL BE DUE 30

DAYS AFTER

CONTRACT AWARD.

REVISIONS SHALL

CONTINUE AS

REQUIRED

THROUGH THE

LIFE OF THE

CONTRACT.

20 10

A004 DI-MGMT- 80259

Physical Inventory Reports

SHALL BE UPDATED

AFTER THE FIRST

SUBMISSION AS

REQUIRED BY

INVENTORY

CHANGES,

SUBMISSIONS

REQUIRING

APROVAL

SHALL BE

PROVIDED FORTY-

FIVE (45) DAYS

PRIOR TO

COMPLETION OF

EACH OPTION YEAR

ON AN ANNUAL

BASIS.

10 5

A005 DI-IPSC- 81429A

SOFTWARE

TRANSITION

PLAN (STrP)

DRAFT SUBMISSION

SHALL BE DUE

TWELVE (12)

MONTHS PRIOR TO

THE END OF THE

CONTRACT. FINAL

SUBMISSION

SHALL BE DUE SIX

(6) MONTHS PRIOR

TO THE END OF THE

CONTRACT.

30 15

A006 DI-MISC- 80711A

Scientific and

Technical Reports

Technical Report

SHALL BE DUE AS

REQUIRED BY THE

GOVERNMENT 30

DAYS FOLLOWING

COMPLETION OF A

SIGNIFICANT EVENT

OR DEVELOPMENT,

INTEGRATION AND

TEST ACTIVITY.

TECHNICAL

REPORT SHALL BE

DUE 90 DAYS PRIOR

TO THE

END OF THE

CONTRACT.

30 20

A007 DI-SESS- 80639D

Engineering

Change Proposal (ECP)

DAYS AFTER

IDENTIFYING A

CHANGE TO ANY

ESTABLISHED

BASELINE.

10 10

A008 DI-MISC- 80711A

Scientific and

Technical Reports

Integrated Development Environment

UBSEQUENT

SUBMISSIONS DUE

ANNUALLY FOR THE

LENGTH OF

THE CONTRACT.

FINAL SUBMISSION

SHALL BE DUE 60

DAYS PRIOR TO THE

END OF CONTRACT.

30 20

B001 DI-MCCR- 80700

Computer Software

Product End Items (CSPEI)

OneSAF and Bif rost/ Software

Version Release

SHALL BE DUE FOR

EACH RELEASE OF

THE SOFTWARE

THROUGH THE LIFE

OF THE DELIVERY

ORDER.

20 10

B002 DI-MISC- 80711A

Scientific and

Technical Reports

OneSAF Bif rost/ Product Line Architecture

Specification

SHALL BE DUE AT

EVERY DOMESTIC

SOFTWARE

RELEASE.

REVISIONS AS

REQUIRED

THROUGH LIFE

OF THE CONTRACT.

30 30

B003 DI-MISC- 80711A

Scientif ic and

Technical Reports

OneSAF Bif rost/ Product

Line Requirement Specification

SHALL BE DUE AT

EVERY DOMESTIC

SOFTWARE

RELEASE.

REVISIONS AS

REQUIRED

THROUGH LIFE OF

THE

CONTRACT.

30 30

B004 DI-MISC- 80711A

Scientif ic and

Technical Reports

OneSAF Bifrost System

Integration Plan

INITIAL SUBMISSION

DUE 30 DAYS AFTER

CONTRACT AWARD.

SUBSEQUENT

SUBMISSIONS

SHALL OCCUR

ANNUALLY

THROUGH THE LIFE

OF THE

CONTRACT.

B005

DI-MGMT-

82001A OneSAF RMF

Package

SHALL BE DUE 60

DAYS PRIOR TO A

PRODUCT VERSION

RELEASE AND 60

DAYS PRIOR TO AN

ACCREDIDATION

EVENT.

4. REVISIONS AS

NEEDED

THROUGHOUT

CONTRACT PERIOD

OF

PERFORMANCE.

30 15

B006 DI-IPSC- 80603A

Software Test Plan

DAYS AFTER INITIAL

PLANNING

CONFERENCE FOR

EACH SOFTWARE

VERSION RELEASE.

SHALL BE DUE FOR

EACH RELEASE OF

THE SOFTWARE

THROUGH THE LIFE

OF THE CONTRACT.

GOVERNMENT

APPROVAL SHALL

BE REQUIRED

PRIOR TO THE

START OF ANNUAL

RELEASE

TESTING.

10 5

C001 DI-MISC- 80711A

Scientif ic and

Technical Reports

OneSAF and Bif rost Operator

Manual

REVISIONS AS

REQUIRED WITH

EACH B001

SOFTWARE

DELIVERY AND

SHALL INCLUDE

UPDATES TO THE

OPERATOR

MANUAL

20 10

C002 DI-MISC- 80711A

Scientif ic and

Technical Reports

OneSAF and Bif rost Maintenance

Manual

SHALL BE DUE

WITH EACH B001

SOFTWARE

DELIVERY AND

SHALL INCLUDE

INCORPORATE

UPDATES TO THE

MAINTENANCE

MANUAL

REVISIONS AS

REQUIRED WITH

EACH B001

SOFTWARE

DELIVERY

C003 DI-IPSC- 81442A

Software Version

Description

(SVD)

OneSAF and Bif rost Version Description Document

SHALL BE DUE

WITH EACH B001

SOFTWARE

DELIVERY AND

SHALL INCLUDE

UPDATES TO THE

VERSION

DESCRIPTION

DOCUMENT.

REVISIONS AS

REQUIRED WITH

EACH B001

SOFTWARE

DELIVERY.

20 10

C004 DI-MISC- 80711A

Scientif ic and

Technical Reports

OneSAF and Bif rost User Training

Manual

SHALL BE DUE 30

DAYS AFTER B001

SOFTWARE

DELIVERY AND

SHALL INCLUDE

UPDATES TO THE

TRAINING

MATERIALS.

REVISIONS AS

REQUIRED, 30 DAYS

AFTER EACH B001

SOFTWARE

DELIVERY.

TRAINING

MATERIALS FOR

TRAINING

SESSIONS SHALL

BE DELIVERED 15

DAYS PRIOR TO

CONDUCT OF THE

TRAINING.

5 5

C005 DI-MISC- 80711A

Scientif ic and

Technical Reports

OneSAF and Bif rost Developer

Training Manual

SHALL BE DUE 30

DAYS AFTER B001

SOFTWARE

DELIVERY AND

SHALL INCLUDE

UPDATES TO THE

TRAINING

MATERIALS

REVISIONS AS

REQUIRED, 30 DAYS

AFTER EACH B001

SOFTWARE

DELIVERY.

TRAINING

MATERIALS FOR

TRAINING

SESSIONS SHALL

BE DELIVERED 15

DAYS PRIOR TO

CONDUCT OF THE

TRAINING.

5 5

Table 1. Contract Data Requirements List (CDRL) Table

The Government’s potentially essential deliverables are reflected in the table. The Government reserves the ability to change the deliverables, per the unique requirements established for each TO.

3. REQUIREMENTS

The requirements defined herein shall form the basis for all work that shall be performed as part of this TO contract and all subsequent TOs the Government shall issue under thise OneSAF Production & Support Single Award ID/IQ contract for the design, development, integration, testing, customer support, and sustainment of the OneSAF Product Line.

3.1. Program Management

The Contractor shall provide the overall management and administrative effort necessary to ensure that the requirements in this PWS are accomplished. The management activities of the OneSAF Production and Support effort requiring face to face engagements (i.e.g. meetings) with the government shall be performed in the GPFGovernmentperformance locationfacility government provided facility unless pre-approved in writing by the Contracting Officer’s Representative (COR) and/or Contracting Officer. The program management associated with this effort shall include technical and administrative planning, organization, coordination, resource allocation, development environment management/maintenance, and risk management. The Contractor shall plan, implement, and maintain a Life Cycle Cost (LCC) management process to minimize the cost of support. The Contractor shall use LCC to evaluate design and support alternatives and select the resource support requirements. The Contractor shall track program progress utilizing metrics and share the metrics and related data with the Government. The Contractor shall conduct Technical Interchange Meetings (TIMs), create an Integrated Master Integrated Master Schedule (IMS) to include but not limited to Program Management Reviews (PMRs), In Progress Reviews (IPRs), and others as directed by the Government. The Contractor shall post agendas and meeting minutes to the established web portals.

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

3.1.1. Contract Management

The Contractor shall plan, budget, schedule, and control resources allocated to meet requirements of the contract. The Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The Contractor shall prepare, implement, and utilize the Contract Work Breakdown Structure (CWBS) and based on the ID/IQ performance-based Government PWS to define the work required for the proposed effort. The Contractor shall identify elements of subcontracted work in the extended CWBS and may propose changes to the CWBS to enhance its effectiveness in satisfying program objectives.

CDRL A003 (DI-MGMT-81334C) Contract Work Breakdown Structure (CWBS)

3.1.2. Enterprise-wide Contractor Manpower Reporting Application (eCMRA)Service

Contract Reporting

The Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for PEO STRI (W6ECAA) via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address:

http://sam.gov/. Reporting inputs shall be for the labor executed during the Period of Performance (PoP) during each Government fiscal year, which runs October 1 through September 30. While inputs may be reported any time during the fiscal year, all data shall be reported no later than October 31 of each calendar year, beginning with year of award. Contractors may direct questions to the help desk at “http://sam.gov/”.For each Order awarded, the Contractor shall report the following information required via the internet at www.sam.gov:

(1) Contract number and order number.

(2) The total dollar amount invoiced for services performed during the previous Government fiscal year under the order.

(3) The number of Contractor direct labor hours expended on the services performed during the previous Government fiscal year.

(4) Data reported by subcontractors under paragraph (f) of this clause.

The Contractor shall require each first-tier subcontractor providing services under this contract, with subcontract(s) each valued at or above the thresholds set forth in FAR 4.1703(a)(2), to provide the following detailed information to the Contractor in sufficient time to submit the report

(i) Subcontract number (including subcontractor name and unique entity identifier), and

(ii) The number of first-tier subcontractor direct-labor hours expended on the services performed during the previous Government fiscal year.

Reporting inputs will be for labor executed during the period of performance for each Government Fiscal Year (FY) which runs 1 October through 30 September.

While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors can find User Guides and may direct question to the help desk at www.SAM.gov.

3.1.3. Subcontractor Management

The Contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime Contractor shall manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. The Contractor shall integrate subcontractors into program Integrated Product Teams (IPTs) and program management and tracking systems.

3.1.4. Financial Management

The Contractor shall maintain a detailed cost and schedule status of work progress on the contract and procedures for planning work, controlling costs, measuring performance, and generating timely and reliable information. The Contractor shall document and track the expenditure of all appropriated funds associated with the contract against each contract line item and sub-line item. The Contractor shall maintain integrated cost and schedule information on those subcontracts that, based on risk, schedule criticality, or dollar value, have the potential to impede the successful completion of the contract.

3.1.5. Risk Management

The Contractor shall prepare, implement, and maintain a risk management process that addresses the identification, analysis, mitigation planning, mitigation plan implementation, and tracking he uncertainty in the project’s ability to meet cost, schedule and performance objectives. The Contractor shall provide Government insight into the Contractor’s tools, assessment, mitigation, and control techniques.

The Contractor shall document risk management as part of the Contractor Progress, Status, and Management Report.

3.1.6. Organizational Process Management

The Contractor shall manage the overarching OneSAF processes and procedures established in the EPG. The Contractor shall recommend changes and improvements where appropriate, aimed at increasing the effectiveness and efficiency in the execution of those processes while maintaining the integrity of the product line. The Contractor shall provide process reports covering topics such as Project Planning, Requirements Management, Requirements Development, Technology Solutions, and Verification. Initial process report topics shall be finalized at the Post Award Conference (PAC) by the Government and Contractor.

Topics shall be revised as required throughout the contract PoP.

CDRL A002 (DI-MISC-80711A) Scientific and Technical Report (Process Reports)

3.1.7. Government Furnished Equipment (GFE) Management

The Contractor shall maintain accountability of all major end-items provided by the Government Furnished Equipment (GFE)/ Government Furnished Property (GFP) or purchased for use under this contract (Contractor-Acquired Property (CAP)).

The Contractor shall maintain and update a property spreadsheet as needed with newly purchased items and remove items that have been properly returned to Government accountability. Inventories shall be conducted by the Contractor and the Government at the beginning of the contract period, once annually thereafter, and once at the conclusion of the contract unless the most recent inventory has been completed within 45 days of the end of the contracted period of performance. The Contractor shall submit the results of the inventory through contracts in accordance with (IAW) Property Accountability Policies (AR 710-4).

The Contractor's property spreadsheet shall be provided to the Government for use during the inventory no later than five (5) business days before the inventory is scheduled to begin. The GFE/GFP is identified on Section 4 – List of Attachments, the contract Attachment 18,- GFE/GFP lList.

CDRL A004 (DI-MGMT-80259) Physical Inventories Report

3.1.8. Purchase of Commercial Information Technology (IT) Equipment

The Contractor shall use the Army's Computer Hardware, Enterprise Software Solutions (CHESS) program, under PEO Enterprise Information Systems (EIS), as the mandatory source for commercial IT purchases. CHESS contracts provide IT products and services that comply with Network Enterprise Technology Command

(NETCOM), Army and Department of Defense (DoD) policy and standards.

Purchasers of commercial hardware and software must satisfy their 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://chess.army.mil.

3.1.9. Integrated Product Teams (IPT)

The Contractor shall utilize an IPT environment as defined by the OneSAF processes. IPT activities shall include the OneSAF Contractors, users, Co- Developers and Government Agency representatives. Associate Contractor Agreements (ACA) shall be implemented and utilized with all OneSAF Contractors where required (i.e. , programs within PM SESTE, JLCCTC, LVC-IA, NGC). The Contractor shall support and provide status during the weekly IPTs. The weekly IPT meeting shall provide an overview and status of all activities and a discussion of technical and/or programmatic topics. The Contractor shall participate in Program Management meetings, Government-led meetings, and third party IPT meetings as directed by the Government. The Contractor shall provide minutes and/or slides reports for all meetings to the development environment portal as directed by the Government.

3.1.10. Post Award Conference (PAC)

The Contractor shall schedule and conduct a PAC within 30 days after contract award. The conference shall introduce key participants with emphasis on top level management of the program, identify points of contact and discuss both parties’ understanding of the requirements to be performed, agree on metrics that shall be used as management indicators, identify any partnering approach, and other contract issues. The Contractor shall post the conference materials and minutes to the OneSAF development environment within 5 business days after the PAC.

3.1.11. Personnel Requirements

3.1.11.1. Key Personnel

The Contractor shall provide staff to support the OneSAF requirements. The following personnel employed under this contract shall be subjected to approval by the Contracting Officer and shall be dedicated at 100% to the program throughout the length of the contract. Key personnel labor category criteria identified in the RFP (Section J, Attachment 7)contract Attachment Cost Price Workbook are required to remain in that role for the first year of the contract. The contractor agrees to assign to any effort requiring non-key personnel, only personnel who meet or exceed the applicable labor category descriptions. No substitution or addition of personnel shall be made except in accordance with this instruction.

a. Program Manager

b. Lead Software Engineer

c. Lead Systems Engineer

d. Lead Integration Engineer

e. Lead Software Architect

f. Lead Cybersecurity Specialist/Analyst

If Key Personnel for whatever reason become unavailable for work under the contract for a continuous period exceeding thirty (30) working days or are expected to devote substantially less effort to the work than indicated in the proposal, the Contractor shall propose a substitution to such personnel. The contractor agrees that during the term of each Order, no Key Personnel substitutions or additions will be made unless necessitated by compelling reasons including, but not limited to an individual’s illness, death, termination of employment, declining an offer of employment (for those individuals proposed as contingent hires), or family leave. In such an event, the contractor must provide the information required below for approval prior to the substitution or addition of Key Personnel.

All proposed substitutions shall be submitted, in writing, to the PCO and COR at least fifteen (15) days (thirty (30) days if a security clearance must be obtained) prior to the proposed substitution. Each request shall provide a detailed explanation of the circumstances necessitating the proposed substitution, a complete resume for the proposed substitute, information regarding the full financial impact of the change, and any other information required by the PCO to approve or disapprove the proposed substitution. All proposed substitutes (no matter when they are proposed during the performance.

3.1.11.2. Cyberspace Workforce Management

IAW DoDD 8140.01 Cyberspace Workforce Management, DoDI 8140.02

IDENTIFICATION, TRACKING, AND REPORTING OF CYBERSPACE

WORKFORCE REQUIREMENTS, DoD-M 8140.03 CYBERSPACE WORKFORCE QUALIFICATION AND MANAGEMENT PROGRAM, personnel whose required duties include government information assurance/ cybersecurity requirements shall have at least one approved security-related certification.

3.1.11.3. Security Clearances

DoD Secret level Personnel Security Clearances (PSC) are required for all personnel working on the program. Key Personnel as defined in this PWS shall possess a final DoD security clearance at the start of the Task Order. An active DoD security clearance is required for 100% of all contractor and subcontractor employees that are required to access to any GPFgovernment facilities in support of the contract. The Contractor, at its own expense, shall be responsible for providing and maintaining personnel with the appropriate security clearances to ensure compliance with Government security regulations, as specified in the Task Order. The contractor shall have qualifications that are equal to or higher than the qualifications of the person being replaced. See further security requirements in section 3.18 and 3.19.

3.2. OneSAF Processes

The Contractor shall execute and maintain the overarching OneSAF processes and procedures established in the EPG. The Contractor shall recommend changes and improvements where appropriate, aimed at increasing the effectiveness and efficiency in the execution of those processes while maintaining the integrity of the product line to include the use of UnITE.

3.3. Systems Engineering

The Contractor shall establish and maintain an effective systems engineering program throughout the requirements, design, testing, and integration processes in order to deliver the OneSAF capabilities in an efficient, effective and innovative, (i.e.e.g. agile manner). The Contractor shall provide the management and execution of all engineering elements of the contract. The Contractor shall leverage new and evolving technologies and leverage and reuse existing products to the fullest extent practicable with the goal of reducing overall life cycle costs.

The Contractor shall use an open systems approach as the design strategy to:

(1) Choose commercially supported specifications and standards for selected system interfaces (external, internal, functional and physical), products, practices and tools

(2) Integrate cloud-based technology in support of the Army’s goals including data discovery, enrichment, and reuse. The cloud computing capability shall utilize and leverage commercial technology and commodity, non-proprietary components to the maximum extent possible

(3) Build open system architectures as the primary foundation in developing the proposed system and its elements

(4) Identify the means for ensuring conformance to open systems standards and profiles throughout the development process.

The Contractor shall evolve the OneSAF product line 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 PLAS and Product Line Requirements Specification (PLRS).

CDRL B002 (DI-MISC-80711A) Scientific and Technical Report (OneSAF Product Line Architecture Specification) CDRL B003 (DI-MISC-80711A) Scientific and Technical Report (OneSAF Product Line Requirement Specification)

3.3.1. Systems Integration

The Contractor shall develop and implement applicable program-level specifications and design documents for the OneSAF Product Line with consideration for critical software items, data rights and interfaces sufficient to support verification & validation, operations, maintenance, and modifications of OneSAF. The Contractor shall provide updates to the System Integration Plan (SIP), including hardware and software development/integration plans, to achieve an optimal system design, production software item, and documentation package.

CDRL B004 (DI-MISC-80711A) Scientific and Technical Report (OneSAF System

Integration Plan)

3.3.2. Software Engineering and Development

The contractor shall establish a robust and comprehensive capability to provide holistic rigor and process across conceptual modeling, knowledge acquisition and engineering; requirements analysis, code design, development, and unit tests; and software integration and test phases in support of activities across a diverse, broad OneSAF community user base and stakeholders. For all software development activities, the contractor shall apply robust, repeatable, and industry align software-intensive processes, tooling, methodologies that align to Capability Maturity Model Integration for Development (CMMI-DEV) and supportive of iterative agile software development frameworks, modular open system approach (MOSA) tenets, and cloud-enabled technologies supporting continuous integration/delivery (CI/CD).

The Contractor shall develop the system software to meet the incremental baseline requirements for new functionality. The Contractor shall ensure the software design is based upon a common infrastructure and common infrastructure services; that interoperability and security are built-in; and that information made available is trusted and interoperable. The Contractor shall analyze requirements concerning computer resource utilization and allocate computer resources among the software items, continuously monitor the utilization and reallocate or identify the need for additional resources. The Contractor shall conduct testing that demonstrates that the new capabilities, change sets, PTR/DR fixes, and handover packages integrated meet the requirements and their respective Use Cases as provided by the Government.

3.3.2.1. Software Processes

The Contractor shall use an innovative process, i.e. agile software development methodology, where each capability is developed during a series of sprints. The

Contractor can propose tailoring as required with Government approval. The build typically consists of the Knowledge Acquisition/Knowledge Engineering (KA/KE) phase followed by subsequent sprints that consist of the Requirement Analysis (RA), Design, Code and Unit Test (CUT), and Software Integration and Test (SWIT) phases. The Contractor shall perform software capability evaluations and stakeholder peer reviews at appropriate phases of the OneSAF development process to ensure that designs are supportable, testable, and conform to the OneSAF architectural specifications.

3.3.2.2. Software Integration

The Contractor shall continuously support the acceptance, modification, integration, and test of internally developed and Co-Developer capabilities daily, in order to deliver the OneSAF software, data, and documentation products. The Contractor shall support complete integration through automation and automated tests and regression testing of the product baseline utilizing supported software configurations and in supported interoperability configurations. The Contractor’s integration and testing processes shall ensure that new capabilities, handover packages, change sets, and PTR/DR fixes are fully implemented and satisfy their requirements and respective Use Cases without impacting existing capability prior to integration into the main OneSAF Software Product Line.

3.3.3. Quality Assurance (QA)

The Contractor shall implement and maintain a QA program using industry-accepted best practices and subject to Government program approval. The Contractor shall establish the QA process with full Government insight. The Contractor shall maintain records of quality conformance and shall make these records available for Government review upon request.

The Contractor shall maintain a structured quality control process on the project that ensures the prompt detection of deficiencies and initiation of necessary corrective actions for any software artifacts or deliverables found non-compliant with this PWS or the Contractor’s internal practices. The Contractor shall introduce appropriate quality controls and establish measurement points that shall provide maximum visibility into new and prior processes to assure contractual requirements are being met. The Contractor shall select the proper methods to analyze these processes to continuously improve the system. Metrics shall be developed to assist management visibility into an adequate process control system. The Contractor shall utilize a discrepancy tracking system with the ability to produce complete permanent records of all discrepancies. The Contractor shall establish a suspense system to ensure timeliness of analysis and corrective action for discrepancies and risk reduction items. The Contractor shall make all data exportable in a readable/manipulatable acceptable format for Government use.

The Government shall monitor the Contractor’s performance under this contract in accordance with the Government’s Quality Assurance Surveillance Plan

(QASP).

3.3.4. Configuration Management (CM) and Control

The Contractor shall identify and manage the software product baseline configuration items and adopt and expand the established OneSAF CM process to ensure that the OneSAF product conforms to the product requirements and is identified and documented in sufficient detail to support its life cycle. The Contractor shall follow the established OneSAF processes, contained in the EPG, to maintain system requirements, system configuration information, and all relevant information about the system. The CM process shall address the evolving production configuration and support environments (engineering, implementation, and test) used to generate and test the product line. The Contractor shall exercise the CM control on all configuration baselines. The Contractor shall establish and maintain a program-level Configuration Control Board (CCB) and submit Contractor Change Proposals (CCP) or Engineering Change Proposals (ECP) for any recommended change, deviation, or waiver In Accordance With (IAW) the established CM process for Government concurrence. The Contractor shall maintain the current CM processes, evaluating them and recommending improvements. The Contractor shall document, and the Government shall review all changes to established baselines. The Contractor shall maintain and manage system requirements in a Government approved industry standard application that provides import/export of data in a commercia standard format.

CDRL A007 (DI-SESS-80639DDI-CMAN-80639C) Engineering Change Proposal

3.4. OneSAF Software Product Line Management and Support

The Contractor shall maintain and enhance the established OneSAF software product line within the OneSAF development environment. The Contractor shall develop, enhance, maintain, and integrate capabilities (developed internally or from external users/customers) and provide version release delivery acceptable to the Community.

The Contractor shall maintain, support, develop, and enhance the tools, models, behaviors, compositions, and/or services of the OneSAF Product Line that meet the various System Compositions extracted from the product line for a particular use. The Contractor shall maintain CM over all daily builds as well as all delivered baselines.

The Contractor shall continuously execute the handover acceptance, modification, integration, and test of developed products to include those from Co-Developers across the Modeling and Simulation Communities, in order to deliver the OneSAF software, data, and documentation products. The contractor shall document significant events related to development and/or testing activities.

CDRL A006 (DI-MISC-80711A) Technical Report

3.5. Test Program

The Contractor shall develop, implement, manage, and maintain an innovative integrated test program that includes plans and test procedures designed to verify the OneSAF product line (including the various configurations) meets all requirements as well as verify fixes related to integration, issue resolution, new development, or enhanced capability including mission command stimulation. The Contractor shall implement methodologies to automate tests using a well-designed framework to increase both the speed and accuracy of testing by providing a reliable structure that reduces dependence on subject matter experts while offering early baseline health indicators and informative report summaries. The Contractor shall collect metrics indicative of testing trends, performance, and baseline stability throughout and report the result to the Government during the weekly IPT meetings.

3.6. Maintenance and Problem Ticket Report (PTR) Support

The Contractor shall perform recurring PTR resolution in conjunction with a prioritized list as established by the Government PTR review board in order to maintain the quality of the software product baseline.

3.7. Co-Developer Support

The Contractor shall host and participate in Co-Developer interaction and handover meetings with OneSAF users. The Contractor shall work with other Army Contractor partners and users of the OneSAF product line to identify and develop reusable software components that support cross-developer interactions, and service-specific uses of OneSAF. The Contractor shall monitor OneSAF system capabilities that are developed by Co-Developers, and keep the Government informed on the progress of such efforts. The Contractor shall provide the conceptual modeling, architectural, and engineering support required to support the Co-Developer’s OneSAF software product deliveries. The Contractor shall analyze proposed handovers for impact on the OneSAF product line 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 Co- Developers following established processes. This software shall become part of the formally managed software baseline.

3.8. Cloud Enabled

In support of the Army’s M&S Communities, the Contractor shall execute the systems engineering process and perform requirement analysis, conceptual modeling, engineering design, development, production, test, and integration to incrementally permit OneSAF to be cloud enabled, Common Operating Environment (COE) compliant and optimized for all identified use cases. This capability could provide services for user locations as well as test and development environments and look to reduce OneSAF recurring sustainment cost over time. The Contractor shall ensure that any cloud services are implemented in accordance with Defense Information Systems Agency (DISA) provided Cloud Computing Security Requirements Guidance and IAW established Army objectives, memorandums and directives as outlined in the Army Cloud Plan. The contractor shall migrate OneSAF virtual machines and containers, conduct DevSecOps, and optimize OneSAF deployment in a Government approved or designated cloud by the Army. The contractor shall ensure this aligns to MOSA, microservices-based architecture, digital engineering, and data-centric principles that support tailoring for cloud-enabled technologies.

3.9 OneSAF Software Product Baseline Release

The Contractor shall facilitate the final user acceptance testing to demonstrate that all changes made to the OneSAF Software Product Line Baseline meet the applicable requirements and their respective Use Cases without impacting existing capability. The Contractor shall prepare and deliver one annual version release. The Contractor shall maintain and update OneSAF version deliverable support documentation for each release.

The Contractor shall coordinate with the Government to identify and prioritize test areas, test threads, test scenarios, vignettes; and any other special test needed to evaluate the functionality and stability of the OneSAF software release baseline. The Contractor shall participate in planning conferences with the TPO and M&S Communities to finalize the Release Test Plan. In preparation to the final acceptance, the Contractor shall dry-run all identified threads, vignettes, large scale exercises, and bi-directional interoperability with live Mission Command (MC) devices with user involvement. The Contractor shall collect metrics throughout the dry-runs and report the results back to the Government during the weekly IPT meeting. The Contractor shall ensure that the OneSAF software baseline under test meets the requirements as identified in ORD, PLRS, and P3I lists as well as any specific additional requirements identified in the Release Test Plan prior to the final acceptance test. The Contractor shall capture all data required to measure the capability and stability of the OneSAF baseline and shall support the Government during the final acceptance test. When appropriate, the Contractor shall ensure the developed capability is adequately tested to meet the appropriate live, virtual, constructive, and gaming simulation requirements. The Contractor shall identify and provide all the test requirements needed, including test plans and resources, to assess the newly developed functionality and its impact on the stability of the software product line baseline. The final acceptance test shall be performed by the Government in an operationally relevant environment prior to all annual software product line baseline releases.

The Contractor shall facilitate the final user acceptance testing to demonstrate that all changes made…