W56HZV-22-R-0026_0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0003 2022SEP16

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

DARNELL JENNINGS II

EMAIL: DARNELL.JENNINGS.CIV@ARMY.MIL

W56HZV-22-R-0026

2022JUL01

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 61

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: DARNELL JENNINGS II

Buyer Office Symbol/Telephone Number: CCTA-CBH-B/(586)282-9039

Type of Contract 1: Firm Fixed Price

Kind of Contract: System Acquisition Contracts

*** End of Narrative A0000 ***

1. The purpose of Amendment 0003 to Solicitation W56HZV-22-R-0026 is to incorporate revisions as follows:

a. Section C: _____________

i. C.2.14.1.2 and C.2.14.1.3 are revised in part to fix a typo as follows:

From: "The Contractor shall use 2015 Boundary JACK\'99 Digital Human Models..."

To: "The Contractor shall use 2015 Boundary JACK Digital Human Models..." ____________

ii. C.5.2.16 is revised in part for clarification as follows:

From: "...prototype vehicles in an as-is condition"

To: "...prototype vehicles based on each vehicle's condition at the end of PPT." ___________________________________________________

b. Section E: _____________

i. E.2.1.2 is revised in part for clarification as follows:

From: "At the conclusion of Production Prove Out Testing final acceptance (DD250) of test vehicles shall be performed on each vehicle in as-is condition. The contractor shall provide a PFIR prior to vehicle delivery to the Government that will only document the test vehicles condition."

To: "At the conclusion of Production Prove Out Testing final acceptance (DD250) of test vehicles shall be performed on each vehicle based on each vehicle's condition at the end of PPT. The contractor shall provide an updated PFIR IAW CDRL T017 ___________________________________________________ _________ _____________ prior to vehicle delivery to the Government that will document the test vehicle's condition at the end of PPT." _____________ _ _________________

c. Section J: _____________

i. Attachment 0004, GCIA Sample Task Logical Model, is added with a date of 09-SEP-2022.

ii. Attachment 0008, OMFV Objective Architecture (P-SPEC), date is corrected from 22-AUG-2022 to 24-AUG-2022.

iii. Attachment 0018, Technical Performance Data Instructions, is revised from REV 003 dated 23-AUG-2022 to REV 004 14-SEP-2022.

iv Attachment 0055, Vehicle Vulnerability Data Instructions, dated 29 March 2022 is added.

v. Attachment 0075, OMFV Program Schedule is revised from REV 002 dated 24-JUN-2022 to REV 003 dated 30-AUG-2022.

d. Section L: _____________

i. L.1.8 and L.6.3 are modified in part to replace the "FAR 19.101" reference with "FAR 2.101".

ii. L.4.3 is modified in part to provide clarifications as follows:

From: "The Government will provide a GCIA Sample Task Logical Model with intentionally introduced deviations from GCIA v2.0

(Attachment 0028: GCIA v2.0 SysML Model and Attachment 0102: GCIA v2.0 Data Architecture Model) from the perspective of modularity, interoperability, use of open standards, open interfaces, reduced coupling and increased cohesion as implemented in the GCIA.

The Government will release the GCIA Sample Task Logical Model no later than 45 days prior to the close of the solicitation. All deviations from GCIA v2.0..."

To: "Specific additional Instructions for Factor 2, Subfactor 2: GCIA Sample Task ____________________________________________________________________________

The views in the Government provided GCIA Sample Task Logical Model (Attachment 0004) depict a notional architectural ____________ _________________________________________________ construct with intentionally introduced deviations from GCIA v2.0 (Attachment 0028: GCIA v2.0 SysML Model and Attachment _________

2 61

W56HZV-22-R-0026

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

0102: GCIA v2.0 Data Architecture Model). The deviations are from the perspective of modularity, interoperability, use of __________________ open standards, open interfaces, reduced coupling and increased cohesion as implemented in the GCIA.

All deviations from GCIA v2.0..."

e. Section M: _____________

i. M.1.1 and M.1.1.2 are modified in part to replace the "FAR 19.101" reference with "FAR 2.101".

f. Exhibit A, Contract Data Requirement List (CDRL): ____________________________________________________

i. CDRL T017, Block 16 (REMARKS), is revised in part as follows:

From: "Block 10, 11, 12, and 13: The Contractor shall deliver this data item 60 days prior to first prototype delivery to the

USG."

To: "Block 10, 11, 12, and 13: The Contractor shall deliver this data item 60 days prior to first prototype delivery to the USG and 60 days prior to end of contract." ____________________________________

*** END OF NARRATIVE A0004 ***

3 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 Introduction

This contract is for the Detailed Design and Prototype Build and Test of the Optionally Manned Fighting Vehicle (OMFV). The United

States Government (USG) is implementing a digital acquisition program IAW Attachment 0075 (OMFV Program Schedule). The digital approach is intended to significantly streamline the standalone documents delivered by the Contractor, while providing the USG unparalleled insight to the design, with the goal of improving cost, schedule and performance.

The USG has implemented a Models Based Systems Engineering approach with an OMFV Objective Architecture to better communicate the requirements of the OMFV system in a clear and concise manner. The Contractor will develop the system architecture and design based on

OMFV Objective architecture. The program is requiring Contractors to manage and maintain the system design and requirement compliance status in a model-based environment, the contract requires the implementation and use of the Ground Combat Systems Common Infrastructure

Architecture (GCIA) provided within the OMFV Objective Architecture and DevSecOps software development to enable the USG to quickly upgrade the OMFV in the future in a Government hosted environment.

As referred to in this contract, the number of days refers to calendar days unless stated otherwise.

C.1.1 OMFV Requirements

The Contractor shall comply with the requirements within Attachment 0008 (OMFV Objective Architecture) and Attachment 0029 (Classified

Specification) in the design of the OMFV.

The Contractor shall research, design, develop, and deliver technical data and computer software as required by the SOW and CDRLs.

C.2 Systems Engineering

The Contractor shall develop and deliver a Digital Engineering Management Plan (DEMP) IAW CDRL E002 and Attachment 0097 (OMFV Digital

Engineering Strategy).

The DEMP shall include the Contractor's configuration management plan for developing and maintaining model-based technical baselines throughout the program lifecycle IAW the technical baseline definitions in EIA-649-1.

The DEMP shall include the Contractor's approach to use Modeling, Simulation, & Analysis (MS&A) in order to reduce risk entering physical test.

C.2.1 OMFV System Architecture Model

The Contractor shall develop an integrated System Architecture Model for the OMFV IAW CDRL E041, Attachment 0067 (CDRL Architecture

Model), and Attachment 0091 (Digital System Model).

The OMFV System Architecture Model (CDRL E041) shall decompose Attachment 0008 (OMFV Objective Architecture) into the requirements and functional, logical, and physical architectural elements that satisfy the USG's Performance Specification (PSPEC) IAW Attachment 0008

(OMFV Objective Architecture) and Attachment 0091 (Digital System Model).

The Contractor shall establish and maintain bi-directional traceability between the OMFV System Architecture Model (CDRL E041) and

Attachment 0008 (OMFV Objective Architecture); including requirements, functional, logical, and physical architecture elements to the lowest replaceable or repairable assembly, subassembly, and repair part, as determined in the LORA, in the Contractor's Bill of

Materials (BOM). The contractor shall ensure all data rights markings IAW DFARS are captured in the System Model (CDRL E041) for all model elements.

C.2.1.1 Specification Tree

The Contractor shall develop, maintain, and deliver a Specification Tree that defines the hierarchical and inter-relationship of the specifications that fully represent the requirements of the OMFV system, including Attachment 0008 (OMFV Objective Architecture) and

Contractor specifications (SSS, SRS, IRS, etc.), IAW CDRL E083, Attachment 0067 (CDRL Architecture Model), and Attachment 0091 (Digital

System Model).

C.2.1.2 System / Sub-system Specifications (SSS)

The Contractor shall develop, maintain, and deliver the SSS for the OMFV IAW CDRL E081 which are identified in the Specification Tree.

C.2.1.3 System / Sub-system Design Descriptions (S/SDD)

The Contractor shall develop, maintain, and deliver the S/SDD for the OMFV IAW CDRL E082 for systems and sub-systems identified in the

Specification Tree (CDRL E083).

C.2.1.4 Requirements Traceability Verification Matrix (RTVM)

The Contractor shall deliver a RTVM IAW CDRL E077 which show the full bi-directional traceability and verification across the requirements contained in the Specification Tree.

C.2.2 Model-Based Design, Simulation, and Test

4 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Contractor shall execute modeling, simulation, and analysis (MS&A) throughout the life of the program to satisfy the use cases of the Attachment 0097 (OMFV Digital Engineering Strategy), and to build the foundation for a digital twin of their design and deliver IAW the DEMP (CDRL E002).

C.2.2.1 Contractor MS&A Deliverables

The Contractor shall deliver the following MS&A in support of system design and the design model specified in the Attachment 0097 (OMFV

Digital Engineering Strategy):

a. The Contractor shall deliver Attachment 0093 (Night Vision - Integrated Performance Model (NV-IPM)) IAW CDRL T023.

b. If the Contractor's design includes Active Protections System (APS) Performance, the Contractor shall deliver APS Performance Data

IAW CDRL E065 and Attachment 0057 (Active Protection Data).

c. The Contractor shall deliver Armor Recipe Characteristics IAW CDRL E066 and Attachment 0053 (Armor Recipe Characteristics).

d. The Contractor shall provide Underbody Analysis IAW CDRL E067 and Attachment 0054 (Underbody Analysis Data Instructions).

e. The Contractor shall deliver modeling and simulation input data as described within Vehicle Vulnerability Analysis MS&A Inputs IAW

CDRL E068 and Attachment 0055 (Vehicle Vulnerability Data Instructions).

f. The Contractor shall deliver a Thermal Signature Analysis IAW CDRL E069 of their vehicle design that demonstrates the predicted system level signature using a root sum squared delta T method in IAW TOP 02-2-812A.

g. The Contractor shall deliver AFES MS&A Inputs IAW CDRL T009 and modeling and simulation input data as described within Attachment

0058 (AFES Analysis Information Request).

h. The Contractor shall fill out the data sheets, and deliver NATO Reference Mobility Model (NRMM) and Dynamics MS&A Inputs IAW CDRL

T010 and Attachment 0059 (NRMM Data Sheet Wheeled and Tracked) for USG to run the model.

i. The Contractor shall deliver Powertrain Data IAW CDRL T011 and Attachment 0060 (Vehicle Data Package for Propulsion System Modeling

& Simulation) and Attachment 0061 (Tracked Vehicle Dynamics Data Sheet).

j. The Contractor shall deliver the Vehicle Interior Noise Analysis Input Datasheet IAW CDRL T032 and Attachment 0101 (Vehicle

Interior Noise Analysis Input Datasheet).

k. The Contractor shall deliver Operational Effectiveness Data IAW CDRL T013 and Attachment 0063 (Operational Effectiveness Template) on their proposed design.

l. The Contractor shall deliver C5ISR CoSite Inputs IAW CDRL T026 and Attachment 0090 (CoSite Data Instructions).

m. The Contractor shall deliver a Process SimulateTM Model Concept IAW CDRL T014 and Attachment 0064 (Process SimulateTM).

n. The Contractor shall deliver SoSAT Data Inputs IAW CDRL T019 and Attachment 0106 (SoSAT Data Inputs).

The Contractor shall deliver MS&A artifacts developed to meet the use cases and model specifications included in the Attachment 0097

(OMFV Digital Engineering Strategy) IAW CDRL E076 and the Contractor's DEMP (CDRL E002).

C.2.2.2 Technical Baseline and System Model Data Rights

The Contractor shall deliver all system model data and computer software which supports the development, operation and sustainment, configuration management, maintenance, repair, overhaul, replacement of components and parts of the OMFV System as well as documented and digital data representations IAW CDRLs and H.9. For all OMFV system non-commercial Technical Baseline and System Model data and non-commercial computer software developed exclusively at Government expense, the Contractor shall grant Unlimited Rights to the Government.

C.2.3 OMFV Digital Environments

C.2.3.1 USG Digital Acquisition Environment (DAE)

The USG will utilize a DAE in order to manage the scope of this contract. The USG DAE will be separate from the Contractor Integrated

Digital Engineering Enviornment (IDEE).

The Contractor shall acquire access to the DAE by submitting a Digital Access Point Request IAW Attachment 0006 (Digital Access Point

Request). This access will serve as the connection between the DAE and the Contractor IDEE.

The Contractor shall be responsible for ensuring all Contractor IDEE connections/trace links/etc. are maintained when transferred from the Contractor IDEE to the USG DAE.

5 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.3.2 Contractor IDEE

The Contractor shall establish and utilize an IDEE in order to develop and manage the OMFV system data. The Contractor shall abide by the data repository requirements IAW DFARS 227.7108 Contractor data repositories.

The Contractor shall update the USG at the Program Coordination Meeting's (PCM) for any deviations from DFARS 227.7108, as well as the current software used in their IDEE.

C.2.4 OMFV Product Baseline and Bills of Material (BOM)

C.2.4.1 OMFV Product Baseline

The Contractor shall ensure that the OMFV vehicle product baseline, as defined by EIA-649-1, accurately traces and is linked to the OMFV system architecture model IAW CDRL E041, the Contractor's configuration status accounting system information, all BOM data, data from its suppliers, and CSDR CWBS elements IAW B008.

C.2.4.2 OMFV Bill of Materials (BOM)

The Contractor shall ensure the BOM is derived from the product baseline and delivered IAW CDRL B008 and Attachment 0088 (OMFV Bill of

Materials).

C.2.4.3 Prototype Vehicle BOM

The Contractor shall deliver an As-Built Configuration Baseline Bill of Materials (ABC-BOM) for each prototype vehicle IAW CDRL E029.

C.2.5 Configuration and Data Management

C.2.5.1 Request for Variance (RFV)

The Contractor shall deliver a RFV IAW CDRL E042 at any time the Contractor intends to deviate from the requirements of this contract.

C.2.5.2 Specification Change Notice (SCN)

For proposed changes to USG Specifications, the Contractor shall deliver a SCN IAW CDRL E046 and MIL-STD-961E.

C.2.5.3 Technical Data Package (TDP)

The Contractor shall identify Key Characteristics IAW AS9103 and identification of these features shall be included within engineering drawings and the TDP.

C.2.5.3.1 Developmental Level TDP

The Contractor shall prepare and deliver a Government-format, Model-based definition developmental level TDP IAW CDRL E003, MIL-STD-

31000B, and Attachment 0011 (Developmental Level TDP Instructions).

C.2.5.3.2 Product Level TDP

The Contractor shall prepare and deliver a Government-format, Model-based definition product-level TDP IAW CDRL E080,MIL-STD-31000B, and

Attachment 0087 (Product Level TDP Instructions).

C.2.5.3.3 TDP In-Process Reviews (IPRs)

The Contractor shall participate in TDP IPRs, during scheduled PCMs, to receive feedback on E003 and/or E080 submission deficiencies.

Rather than reject entire submissions, the USG intends to give incremental feedback for the Contractor to resubmit portions of TDP that aren't meeting contractual requirements. The Contractor shall resubmit TDP CDRLs and/or portions of TDP CDRL submissions according to the TDP IPRs.

C.2.5.4 Technical Data Package supporting Assertions of Restrictions

The Contractor shall submit a conceptual, developmental or product level TDP for any items the Contractor Asserts Restrictions IAW E011.

The Contractor shall prepare and deliver the configuration baseline data and design information for the OMFV released, to date, by the contractor (i.e. development configuration baseline, design release baseline) IAW E003 and Attachment 0011 (Developmental TDP).

C.2.5.5 Data Accession List (DAL)

The Contractor shall deliver the DAL IAW CDRL E040. The Contractor shall flow down the DAL requirements to its Subcontractors.

C.2.6 Technical Performance Measures and Metrics

The Contractor shall develop and deliver Technical Performance Measures (TPMs) Report IAW CDRL E001 and Attachment 0010 (Technical

Performance Measures).

C.2.7 Use of Modular Open Systems Approach (MOSA)

The Contractor shall develop and employ a MOSA for the OMFV design using Attachment 0007 (Program Executive Office (PEO) Ground Combat

Systems (GCS) MOSA Implementation Guide v1.0) as a guide.

6 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Contractor's approach for the MOSA shall enable refreshment and upgrade of technologies at a component level, through modular designs for severable end item components of all subsystems/system-of-systems by using open standards for the modular system interfaces of the OMFV system. The Contractor shall deliver interface control documents for all major system component, Modular System Interfaces, and key interfaces at the component level of all subsystems/system-of-systems IAW CDRL E041.

The term "component level" means a configuration item (e.g. severable modules of a fire control system), which encapsulates a subset of the system's functionality/data, with a defined interface.

The term "major system component"

(A) means a high-level subsystem or assembly, including hardware, software, or an integrated assembly of both, that can be mounted or installed on a major system platform through modular system interfaces; and

(B) Includes a subsystem or assembly that is likely to have additional capability requirements, is likely to change because of evolving technology or threat, is needed for interoperability, facilitates incremental deployment of capabilities, or is expected to be replaced by another major system component.

The term "Modular System Interface" means a shared boundary between major systems, major system components, or modular systems, defined by various physical, logical, and functional characteristics, such as electrical, mechanical, fluidic, optical, radio frequency, data, networking, or software elements.

Examples of modular system interfaces include, but are not limited to, the following:

- Hull and Turret

- Hull and System Survivability

- Turret and System Survivability

- Hull and Suspension

- Hull and Power Pack

- Hull and Drive Train

- Turret and Armament

- Turret and Automatic Ammunition Handling

- Fire Control and Armament

- APS and Turret/Hull

Key Interfaces are subsets of Modular System Interfaces, and are interfaces which support or enable:

- Rapid changes in technology

- Rapid changes in threat systems

- Interfaces existing between systems

- Multiple, long term, viable sources or where COTS exist

- Mission Critical Functions

- Isolates US-only systems

- Connections to GFE, GFP, and USG Information Systems

- Software capability insertion

Some examples Key Interfaces include:

- A Modular Radio Interface Unit that allow the integrations of multiple different radios (power, signals, waveforms and data).

- Power Control Units which allow updating channel outputs enabling system changes without hardware updates.

- A standardized message set for software (SW) communication to enable third party software (SW) insertion such as a standardized message set for software communication to enable third party software insertion (e.g. Artificial Intelligence and Fire Control).

- VICTORY enabled interfaces which facilitate information availability via standardized messages.

- Data bus standards, e.g. SAE-J1939 CAN, gigabit Ethernet.

- Vetronics computer backplanes and cards, e.g. 3UVPX.

- Interface and ports for USG equipment and devices, e.g. maintenance equipment, software loading, prognostics/diagnostics, and embedded training.

- The interface between the general-purpose processor and higher-level software abstraction layers

- The interface between business logic software and communication services

- The interface between hardware device drivers and higher-level software abstraction layers

The Contractor shall apply standards according to the order of importance below:

a. Standards as specified within the contract (including all the attachments)

b. Commercial standards

c. Widely supported, adopted, and consensus-based standards in the market place

d. Standards developed by US industry standards bodies that have been widely adopted by industry

C.2.7.1 Common Infrastructure Capability

The Contractor shall implement a reusable, modular, and severable Common Infrastructure Capability that complies with the PEO GCS Common

Infrastructure Architecture (GCIA) v2.0 IAW Attachment 0028 (GCIA v2.0 SysML Model) and Attachment 0102 (GCIA v2.0 Data Architecture

Model). Attachment 0030 (GCIA v2.0 Architecture Description Document (ADD) Rev2.1) and Attachment 0081 (GCIA v2.0 Data Architecture

7 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Definition (DAD) Rev2.1) may be used to provide further context.

The Contractor shall deliver the system architecture of the Common Infrastructure Capabilities and GCIA v2.0 interfaces within the OMFV

System Architecture Model IAW CDRL E041.

The Contractor shall extend the Common Infrastructure Capability instead of creating duplicate capability for implementing additional functions related to the Common Infrastructure Capability not specified IAW Attachment 0028 (GCIA v2.0 SysML Model).

The Contractor shall utilize instantiations of the Common Infrastructure Capability IAW GCIA v2.0 for the integration of subsystem capabilities.

The Contractor shall utilize the services available through the Common Infrastructure Capability to refrain from duplication of resources across subsystems.

The Contractor shall ensure that all subsystem integrations comply with GCIA v2.0 Attachment 0028 (GCIA v2.0 SysML model).

The Contractor shall always utilize GCIA 2.0-compliant software or hardware interfaces for accessing and providing data within the GCIA in-vehicle network.

All data used by the OMFV platform shall be open, visible, accessible, understandable, trusted, interoperable, and secure (VAUTIS) within the Common Infrastructure Capability.

The Contractor shall develop, extend, and deliver OMFV Data Model Artifacts IAW CDRL E103, Attachment 0099 (Data Architecture Artifacts

One Time DID), Attachment 0028 (GCIA v2.0 SysML Model) and Attachment 0102 (GCIA v2.0 Data Architecture Model).

The Contractor shall develop and deliver a GCIA Test Plan IAW CDRL E044. The Contractor shall deliver a GCIA Test Report IAW CDRL E045.

C.2.7.2 MOSA/Common Infrastructure Capability Exceptions

The Contractor shall deliver a Request for Variance IAW CDRL E042 to obtain USG approval prior to using software and/or hardware that does not comply with the PEO GCS Common Infrastructure Architecture (GCIA) v2.0.

C.2.7.3 MOSA and Other Reference Architecture Interfaces Data Rights

The Government intends to retain ownership of its GCIA infrastructure provided in Attachment 0028 (GCIA v2.0 SysML Model) to re-compete capabilities to meet future government requirements without being vendor locked. The Government also intends to modify the interfaces and infrastructure without any approval from the original developer as GCIA matures. The Government intends to reuse the interfaces for follow on Phases or on other GCS platforms.

C.2.7.3.1 GCIA Interfaces

For the design of the Common Infrastructure Capability, modular system interfaces of the OMFV system, and the interfaces between the subsystem capabilities and the GCIA v2.0 compliant Common Infrastructure Capability, the Contractor shall deliver the SysML models, ICDs, IDDs, form, fit & function, and all corresponding specifications/requirements documents IAW CDRLs E006, E007, E008, E009, E010, and E041. Reference C.2.8.2 and C.2.8.1.1. The definition of GCIA modular system interfaces, and a listing of them, can be found in

Attachment 0030 (GCIA v2.0 ADD Rev2.1).

C.2.7.3.2 GCIA Components (Implementation of Infrastructure)

For all GCIA Components, the Contractor shall deliver SysML models, data architecture model, data architecture model library, and artifacts, source code for the software infrastructure implementation (including configuration files), executables, and all corresponding design/specification/requirements documents as it relates to GCIA implementation (software and hardware components) IAW

CDRLs E006, E007, E008, E009, E010, E041, and E103. Reference C.2.8.2 and C.2.8.1.1. A GCIA component is a severable module

/configuration item that is developed IAW with the GCIA 2.0 specifications, which encapsulates its associated GCIA functionality/data, with a GCIA defined/identified open standards based interface.

C.2.7.3.3 Other OMFV Platform Modular System Interfaces

In addition to GCIA, the Government intends to upgrade and re-compete capabilities that fall outside the boundary of GCIA. The

Government wants to reuse interfaces for follow on Phases or on other GCS Platforms. It is critical that the government obtain rights to the modular interfaces on OMFV, to enable a MOSA.

For other modular system interfaces not encompassed by the GCIA interfaces in section 2.4 of Attachment 0030 (GCIA v2.0 ADD Rev2.1), the

Contractor shall deliver the SysML models, ICDs, IDDs, and all corresponding specifications/requirements documents IAW CDRLs E006 E007, E008, E009, E010, E041,and E103. Reference C.2.8.2 and C.2.8.1.1. These modular system interfaces are defined as Shared boundaries between major systems, major system components, or modular systems, defined by various physical, logical, and functional characteristics, such as electrical, mechanical, fluidic, and radio.

C.2.8 Software Development

8 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.8.1 DevSecOps

The Contractor shall use the USG provided DevSecOps Environment IAW Attachment 0009 (DevSecOps Overview) NLT six months after contract award and provide read-only access to the USG.

C.2.8.1.1 Platform One

The Contractor shall use this environment for development of OMFV software, to include firmware. Throughout section C.2.8. the mention of software includes firmware. The Contractor shall have all sub-Contractors develop software within Platform One. The Contractor shall import all previously developed software into Platform One. The Contractor shall include all software integrated into Platform One for system level qualification testing.

The Contractor shall deliver OMFV System Architecture Model IAW CDRL E041. The Contractor shall continually update their backlog within their DevSecOps environment and make their backlog viewable by the USG.

The Contractor shall identify and track all software system risks (IAW MIL-STD-882E section 4.4 and sub-sections) in the Hazard Tracking

System IAW CDRL E024.

C.2.8.2 Software Design Documentation

For all OMFV software within the DevSecOps environment, the following must be maintained current and viewable to the USG and delivered

IAW the associated CDRL:

a. Software Design Description (SDD) (CDRL E005)

b. Software Requirements Specification (SRS) (CDRL E006)

c. Interface Requirements Specification (IRS) (CDRL E007)

d. Interface Control Document (ICD) (CDRL E008)

e. Interface Design Document (IDD) (CDRL E009)

f. Software Product Specification (SPS) (CDRL E010)

g. Software Version Description (SVD) (CDRL E012)

h. Software License Requirements List (SLRL) (CDRL E013)

i. Software Test Report (CDRL E015)

j. GCIA Test Report (CDRL E045)

k. Software Test Description (CDRL E085)

l. Software Systems Integration Laboratory (SIL) Test Report (CDRL E114)

m. Software Bill of Materials (SBOM) (CDRL E004)

C.2.8.3 Source Code & Executable

For all OMFV software, the Contractor shall deliver a software product specification (SPS) including all source code, header files, implementation files, configuration files, object files, statically and dynamically linked libraries, binaries, executables, and configuration files IAW CDRL E010.

For uploading software updates to the OMFV system, the Contractor shall implement and use a secure software updating process to ensure that the code has not been corrupted or altered. The design shall be detailed in block diagram, activity, behavior views within the

System Architecture Model IAW CDRL E041, which includes all software source code, executables, and libraries.

C.2.8.4 Software Version Description (SVD)

The Contractor shall develop and deliver a Software Version Description (SVD) to describe each computer software version release IAW

CDRL E012.

C.2.8.5 Software Architecture Document

The Contractor shall develop and deliver a Software Architecture Document (SAD) IAW CDRL E084.

C.2.8.6 OMFV System and Support Systems Software Licenses

The Contractor shall deliver all Software Licenses IAW CDRL E013 for all software utilized on the OMFV systems, including commercial software licenses, required for compiling, building, installing, and maintaining all software utilized on the OMFV system, as well as all software licenses required for operation and maintenance of the OMFV system.

C.2.8.7 Software Transition Plan

The Contractor shall develop and deliver a Software Transition Plan (STrP) IAW CDRL E014.

C.2.8.8 Software Qualification Testing (SQT)

The Contractor shall conduct software qualification testing of each Software Configuration Item and deliver Software Quality Test Report

(SQTR) IAW CDRL E015.

C.2.8.9 Software Quality Assurance

The Contractor shall prepare and deliver a Software Quality Assurance Report (SQAR) IAW CDRL E016.

9 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.8.10 Software Assurance

The Contractor shall ensure that protection and assurance activities aimed at mitigating attacks against the operational system throughout the system life cycle and those that address threats to the development environment that are documented, implemented, and delivered in a Software Assurance Plan IAW CDRL E070.

C.2.8.11 Software/Systems Integration Lab

The Contractor shall conduct system qualification tests, including cybersecurity and safety tests, utilizing an environment that most closely represents the actual OMFV design: i.e. verified software integrated on actual hardware-in-the-loop, including vehicle harnesses to the maximum extent that is to fully represent vehicle's parameters. The Contractor shall develop and deliver the Software/Systems

Integration Laboratory (SIL) Test Plan IAW CDRL E034. The Contractor shall deliver the Software/SIL Test Report IAW CDRL E114.

C.2.8.12 System Software Safety Program

The Contractor shall conduct a System Software Safety Program IAW Attachment 0084 (Joint Software System Safety Engineering Handbook

(JSSSEH) Implementation Guide) paragraph C.

The Contractor shall conduct a System Software Safety Assessment to define, evaluate, and test the safety-significant functionality associated with the integration of the Contractor-generated, NDI, COTS, reuse, and Government-furnished computer software; and discuss the assessment during the ESOH WG. Any hazards contributed by software will be documented in the Hazard Tracking System and delivered

IAW CDRL E024.

The Contractor shall conduct Level of Rigor (LOR) activities to ensure that the software will perform as specified in the SRS and IRS, without contributing to hazards.

All LOR tasks for all SwCI (Software Criticality Index) level 1-3 shall be completed no later than Test Readiness Review 1 IAW MIL-STD-

882E. These results and mitigations shall be delivered IAW CDRL E015. If all LOR tasks are not completed or the LOR tasks are unspecified the SW Safety contribution to a system level risk will be documented as a Medium, Serious, or High risk depending on the

SwCI level.

The Contractor shall conduct System Software Safety -specific testing and deliver the the results IAW CDRL E015 to verify that the design and implementation of the computer software mitigates all of the identified computer software related hazards.

C.2.8.13 Software Bill of Materials (SBOM)

The Contractor shall develop and deliver a Software Bill of Materials (SBOM) IAW CDRL E004. The SBOM is a formal record containing the details and supply chain relationships of various components used in building software, and tracks version of all code; including firmware, third party developed software (to include dependent libraries), and previously developed software. International Standard

ISO/IEC 5962 (as of 202108) can be used as a guide.

For each software component, the SBOM shall include the following and be delivered IAW CDRL E004:

a. Software name

b. Name of developer, distributor or location acquired (repository, website, disc delivery, etc),

c. Associated hash codes

d. Hash code algorithms

e. Version identifiers

f. Identification is the software has privileged access (ex: Administrator or Root)

g. Identification of allocation to the OMFV (LRCs or Circuit Cards)

C.2.8.14 Source Code & Executables Data and License Rights

For any non-commercial computer software the Contractor intends to deliver with less than Government Purpose Rights, the Contractor agrees to negotiate with the Government for specifically negotiated license rights to that computer software to meet the Government's needs.

C.2.9 Vetronics Infrastructure

The Contractor shall prepare and deliver a Vehicle Electronics Infrastructure Report IAW CDRL E104 and Attachment 0092 (Vehicle

Electronics Infrastructure Architecture One Time DID).

C.2.10 Program Protection

C.2.10.1 Critical Technologies (CT) and Critical Program Information (CPI)

The Contractor shall identify all Critical Technologies (CT) and Critical Program Information on the OMFV and document results in the

Program Protection Implementation Plan (PPIP) IAW CDRL E018 and Attachment 0026 (Inherited Critical Technologies and Potential

Countermeasures). The Contractor shall document trusted system design countermeasures in the OMFV System Architecture Model IAW CDRL

E041.

C.2.10.1.1 Inherited CT and CPI

10 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Contractor shall include any CT and CPI inherited from GFE IAW Attachment 0026 (Inherited Critical Technologies and Potential

Countermeasures).

C.2.10.2 Program Protection Implementation Plan (PPIP)

The Contractor shall develop, implement, and deliver a PPIP IAW CDRL E018 that describes the Contractor's process for managing risks to technology and mission-critical system functionality from foreign collection, design vulnerability, supply chain exploitation, and battlefield loss throughout the acquisition lifecycle IAW DoDI 5200.44.

C.2.10.2.1 Program Protection Criticality Analysis

The Contractor shall develop and deliver a Program Protection Criticality Analysis IAW CDRL E019 and Attachment 0014 (Program

Criticality Analysis Template).

C.2.10.2.2 Critical Component SubContractors

The Contractor shall take steps to ensure that products purchased or obtained shall not be identified as being destined for inclusion in a USG system.

C.2.10.2.3 Risk Mitigation of Critical Components

The Contractor shall develop risk mitigation strategies for all Critical Components (CCs) identified from the Program Protection

Criticality Analysis IAW CDRL E019.

C.2.10.3 Critical Component Control

The Contractor shall certify that the underlying computer software, firmware, and hardware, which in totality, constitute the managed service, have been controlled, evaluated, and tested to ensure that the service delivers what it is designed to deliver and nothing more.

The Contractor shall test all Critical Component code against the top 25 Common Weakness Enumerator (http://cwe.mitre.org

The Contractor shall deliver details in tab SwA Table' of the Program Protection Criticality Analysis IAW CDRL E019. All Contractor-developed source code shall be provided for independent system assurance testing within the DevSecOps environment.

C.2.10.4 Supply Chain Risk Management (SCRM)

The Contractor shall submit a Supplier Performance Risk System (SPRS) Certification IAW CDRL E020.

The Contractor shall develop, implement, and deliver a Counterfeit Parts Prevention Program Plan IAW CDRL E021.

C.2.11 Cybersecurity

C.2.11.1 Cybersecurity Test Events

For all Cybersecurity Test Events, the Contractor shall participate in a pre-test event and post-test event review. The pre-test and post-test events cannot exceed six hours in length.

For all pre-test event reviews, the Contractor shall generate briefing materials in support of the review IAW CDRL P002. All pre-test reviews shall occur five (5) to twenty-one (21) days prior to the test event.

For all post-test event reviews, the Contractor shall generate briefing materials in support of the review IAW CDRL P002. All post-test reviews shall occur five (5) to twenty-one (21) days after the test event.

All Cyber Testing events, Cyber Tabletop Exercise, Cooperative Vulnerability Identification, Adversarial Cyber Development Testing, and

Cooperative Vulnerability Penetration Assessment shall be events, pre-test reviews, and post-test reviews shall be classified events.

The Contractor shall work with the PCO to identify a location for these events.

C.2.11.1.1 Cyber Tabletop Exercise

The Contractor shall participate in a Cyber Tabletop Exercise (CTT) IAW Attachment 0015 (Cybersecurity Test Events).

C.2.11.1.2 Cooperative Vulnerability Identification (CVI)

The Contractor shall participate in a Cooperative Vulnerability Identification (CVI) event IAW Attachment 0015 (Cybersecurity Test

Events).

C.2.11.1.3 Adversarial Cyber Developmental Testing (ACDT)

The Contractor shall participate in an ACDT event IAW Attachment 0015 (Cybersecurity Test Events).

C.2.11.1.4 Cooperative Vulnerability Penetration Assessment (CVPA)

The Contractor shall participate in a CVPA event IAW Attachment 0015 (Cybersecurity Test Events).

11 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.11.2 Attack Surface Characterization

The Contractor shall generate and deliver an Attack Surface Characterization Report IAW CDRL E022. The Contractor shall include all potential entry and exit points to the platform (Ex: software download, training devices, removable hardware, etc.).

C.2.11.3 Cyber Risk Management Framework

The Contractor shall deliver DoD Risk Management Framework (RMF) Package Deliverables IAW CDRL E017 and IAW Attachment 0024 (Risk

Management Framework Package Deliverables Instructions).

C.2.11.4 Supporting Artifacts

The Contractor shall deliver the RMF Package Deliverables IAW CDRL E017 and Attachment 0024 (Risk Management Framework Package

Deliverables Instructions).

a. Authority to Operate (ATO) Requests

b. Assessment and Authorization (A&A) Project Plan

c. A&A Tasks and Milestones

d. System Security Implementation Plan

e. RMF Implementation Plan (RIP) IAW Attachment 0020

f. Software Code Vulnerability Scans

g. Operating System Vulnerability Scans

h. Software/Firmware Information Assurance Vulnerability Management (IAVM) Plan

i. Key and Certificate Management Plan

j. Plan of Action and Milestones

k. Cyber Security Waiver

C.2.11.5 Design for Security

C.2.11.5.1 Cryptographic Processes and Key Management Plan (KCMP)

The Contractor shall follow policy provided by the Committee on National Security Systems Policy (CNSSP) 15, Use of Public Standards for

Secure Information Sharing, to determine algorithms for assessing integrity and ensuring confidentiality.

CNSSP is available at:

https://www.cnss.gov/CNSS/issuances/Policies.cfm

The Contractor shall develop a copy of all encryption and signing keys / certificates assigned to each platform and deliver

Cryptographic Encryption Keys IAW CDRL E075.

C.2.11.5.2 Cross Domain Solution

The Contractor shall include Cross Domain Solution Key Interfaces IAW Attachment 0062 (OMFV Key Interfaces for Cross Domain Solutions);

if a communication between domains is required, the platform shall separate the domains IAW DoDD 8540.01.

C.2.12 Corrosion Prevention and Control

C.2.12.1 The Contractor shall develop, deliver, maintain, and comply with a Corrosion Prevention and Control Plan (CPCP) IAW CDRL E031 and Attachment 0082 (Chemical Agent Resistant Coating Drawing).

C.2.12.2 The interior of the prototype vehicles and BH&Ts shall be painted Gloss White Chip No. 17925 of SAE AMS-STD-595 in accordance with Attachment 0082. The USG will specify the exterior color of prototype vehicles and BH&Ts NLT PDR.C.2.13 Environment, Safety and

Occupational Health (ESOH).

C.2.13.1 ESOH Program

The Contractor shall develop, implement, and maintain an ESOH program in accordance with MIL-STD-882E.

C.2.13.2 Prohibited Material

The Contractor's OMFV design shall not have prohibited materials (including alloys containing prohibited materials) present in or on any delivered systems or support equipment, required for operation and sustainment or provisioning of the system, or used in final manufacture and assembly processes.

The following are prohibited materials: asbestos, beryllium, Class I and Class II Ozone Depleting Substances (ODS), hydrofluorocarbons

(HFCs), hexavalent chromium, cadmium, mercury, lead, radioactive materials, and other Group 1 Agents classified as "carcinogenic to humans" by the International Agency for Research on Cancer (IARC) Monographs.

The following exceptions are allowed without prior approval from the USG:

a. Cadmium and hexavalent chromium on electrical connectors and back shells used to mate with cadmium electrical connectors on

Government Furnished Equipment (GFE) or used in an Automatic Fire Extinguishing System (AFES)

b. Products listed under "Priming" and "Topcoating" in MIL-DTL-53072, Table I

12 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

c. Lead-acid batteries

d. Lead solder

e. Leaded battery terminal adaptors/clamps

f. Silica used in adhesives and sealants

g. Fuels specified for use in the requirements of this contract

h. Steel containing up to 0.35% lead by weight

i. Aluminum containing up to 0.4% lead by weight

j. Copper and Brass alloys containing up to 4% lead by weight

k. Beryllium and Beryllium alloys used in electrical components

l. Mercury containing components compliant with European Union (EU) Directive 2011/65/EU (RoHS 2)

m. Trace amounts of identified restricted materials contained in base materials and/or alloys. For the purposes of this contract trace amounts are defined as <0.1% by weight for carcinogens and <1% by weight for all other materials

n. R134a in ground vehicle air conditioning systems

o. HFCs in fire extinguishing systems in crew-occupied spaces

C.2.13.3 Prohibited Materials Waivers

The Contractor shall submit Requests for Variance (RV) IAW CDRL E042 and Attachment 0017 (Request for Use of Prohibited Materials).

C.2.13.4 Hazard Tracking System (HTS)

The Contractor shall conduct Subsystem Hazard Analysis IAW MIL-STD-882E Task 204, System Hazard Analysis IAW MIL-STD-882E Task 205, Health Hazard Analysis MIL-STD-882E Task 207, Functional Hazard Analysis IAW MIL-STD-882E Task 208, and Environmental Hazard Analysis

IAW MIL-STD-882E Task 210.

The Contractor shall include assessments of software's contribution to system risk (IAW MIL-STD-882E section 4.4 and sub-sections) in the System Hazard Analysis and Functional Hazard Analysis.

The Contractor shall use these analyses to create the HTS IAW MIL-STD-882E Task 106, and deliver the HTS Status IAW CDRL E024.

The Contractor shall document and track all hazards in the HTS IAW MIL-STD-882E Risk definitions.

The Contractor shall identify all Safety Critical Items (SCI), as defined by MIL-STD-882E paragraph 3.2.33. The Contractor shall track the status of all SCI within the HTS regardless of risk levels. The Contractor shall only eliminate an SCI from the HTS if that item was removed from the vehicle design.

C.2.13.5 Safety Assessment Report (SAR)

The Contractor shall develop and deliver a SAR IAW CDRL E025 and MIL-STD-882E Task 301.

C.2.13.6 Hazardous Materials Management Report (HMMR)

The Contractor shall develop and deliver a HMMR IAW CDRL E043 and Attachment 0025 (HMMR Template).

C.2.13.7 Built-In-Test (BIT)/Built-In-Test Equipment (BITE) Fault Tree

The Contractor shall develop and deliver a BIT/BITE Fault Tree IAW CDRL L041.

C.2.14 Human Systems Integration (HSI)

The Contractor shall develop a HSI program IAW AR 602-2 and document and deliver the HSI Program Plan (HSIPP) IAW CDRL E035.

C.2.14.1 HSI Documentation Requirements

C.2.14.1.1 Human Engineering Systems Analysis Report (HESAR)

The Contractor shall deliver a Human Engineering Systems Analysis Report (HESAR) IAW CDRL T015.

C.2.14.1.2 Human Engineering Design Approach Document-Operator (HEDAD-O)

The Contractor shall deliver a Human Factors Engineering Design Approach Operator (HEDAD-O) IAW CDRL T021 and Attachment 0104

(Additional Instructions for Human Engineering Design Approach Document-Operator).

The Contractor shall use 2015 Boundary JACK Digital Human Models (DHMs) IAW Attachment 0065 (JACK ARL 2015 Dismounted Boundary Manikins

Sets) and Attachment 0066 (JACK ARL 2015 Mounted Boundary Manikins Sets) for the analysis of physical operator interfaces.

C.2.14.1.3 Human Engineering Design Approach Document-Maintainer (HEDAD-M)

The Contractor shall deliver a Human Factors Engineering Design Approach Maintainer (HEDAD-M) IAW CDRL T022.

The Contractor shall use 2015 Boundary JACK Digital Human Models (DHMs) IAW Attachment 0065 (JACK ARL 2015 Dismounted Boundary Manikins

Sets) and Attachment 0066 (JACK ARL 2015 Mounted Boundary Manikins Sets) for the analysis of physical maintainer interfaces.

C.2.14.1.4 HSI Issue Database

13 61

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Contractor shall develop and maintain a Human Systems Integration (HSI) Issue Database IAW AR 602-2. The Contractor shall document and track all HSI issues regardless of risk levels. The Contractor may only eliminate an HSI issue from the HSI Issue Database if that item was removed from the vehicle design.

C.2.14.1.5 HSI Report (HSIR)

The Contractor shall develop and deliver a HSIR IAW CDRL E047.

C.2.14.1.6 Soldier Touchpoint Support

The Contractor shall provide personnel support for Soldier Touchpoints for up to a total of 8 weeks at Detroit Arsenal to provide HSI feedback. Contractors may bring any components to showcase any design attributes for feedback. During Soldier Touchpoint periods, Contractors may have the opportunity to host an event at their local location for feedback.

C.2.14.2 Soldier Workload Analysis

The Contractor shall deliver a Soldier Workload analysis which assesses the 2-person crew workload of the OMFV IAW CDRL E088.

The Contractor shall utilize…