W56HZV-23-C-0026.pdf

AWARD/CONTRACT 1. This Contract Is A Rated Order Under DPAS (15 CFR 700)

Rating Page Of Pages

2. Contract (Proc. Inst. Ident.) No. 3. Effective Date 4. Requisition/Purchase Request/Project No.

5. Issued By Code 6. Administered By (If Other Than Item 5) Code e-mail address:

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

FOB Origin Other (See Below)

9. Discount For Prompt Payment

10. Submit Invoices Item (4 Copies Unless Otherwise Specified)

Code Facility Code To The Address Shown In:

11. Ship To/Mark For Code 12. Payment Will Be Made By Code

13. Authority For Using Other Than Full And Open Competition: 14. Accounting And Appropriation Data

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( )

15A. Item No. 15B. Supplies/Services 15C. Quantity 15D. Unit 15E. Unit Price 15F. Amount

15G. Total Amount Of Contract

16. Table Of Contents

(X) Sec. Description Page(s) (X) Sec. Description Page(s)

Part I - The Schedule Part II - Contract Clauses A Solicitation/Contract Form I Contract Clauses

B Supplies or Services and Prices/Costs Part III - List Of Documents, Exhibits, And Other Attachments

C Description/Specs./Work Statement J List of Attachments

D Packaging and Marking Part IV - Representations And Instructions

E Inspection and Acceptance K Representations, Certifications, and F Deliveries or Performance Other Statements of Offerors G Contract Administration Data L Instrs., Conds., and Notices to Offerors

H Special Contract Requirements M Evaluation Factors for Award Contracting Officer Will Complete Item 17 (Sealed-Bid or Negotiated Procurement) Or 18 (Sealed-Bid Procurement) As Applicable

17. Contractor’s Negotiated Agreement (Contractor is required to sign this document and return copies to issuing office.) Contractor agrees to furnish and deliver all items or perform all the services set forth or otherwise identified above and on any continuation sheets for the consideration stated herein. The rights and obligations of the parties to this contract shall be subject to and governed by the following documents: (a) this award/contract, (b) the solicitation, if any, and (c) such provisions, representations, certifications, and specifications, as are attached or incorporated by reference herein. (Attachments are listed herein.)

18. Sealed-Bid Award (Contractor is not required to sign this document.) Your bid on Solicitation Number , including the additions or changes made by you which additions or changes are set forth in full above, is hereby accepted as to the items listed above and on any continuation sheets. This award consummates the contract which consists of the following documents: (a) the Government’s solicitation and your bid, and (b) this award/contract. No further contractual document is necessary. (Block 18 should be checked only when awarding a sealed-bid contract.)

19A. Name And Title Of Signer (Type Or Print) 20A. Name Of Contracting Officer

19B. Name of Contractor 19c. Date Signed 20B. United States Of America 20C. Date Signed

By By

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

AUTHORIZED FOR LOCAL REPRODUCTION Standard Form 26 (Rev. 5/2011) Previous edition is NOT usable Prescribed By GSA - FAR (48 CFR) 53.214(a)

DOA4

W56HZV-23-C-0026 2023JUN26

SIGNED REPRINT

SEE SCHEDULE

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

JOSEPH FELICE

JOSEPH.A.FELICE5.CIV@ARMY.MIL

S2305A

DCMA DETROIT

35803 MOUND ROAD

STERLING HEIGHTS MI 48310

8B3G4

AMERICAN RHEINMETALL VEHICLES , LLC

35875 MOUND RD

STERLING HEIGHTS, MI 48310-4777

X

SEE SCHEDULE

HQ0337

DFAS-COLUMBUS CENTER

NORTH ENTITLEMENT OPERATIONS

P.O. BOX 182317

COLUMBUS OH 43218-2317

SEE SECTION G

SEE SCHEDULE

$107,912,944.00

X

2 signed

JAMES J. GIACCHINA

JAMES.J.GIACCHINA.CIV@ARMY.MIL (586)282-4131

2023JUN26

2023JUN26SIGNED REPRINT

1 102

X 1

X 3

X 9

X 45

X 46

X 48

X 53

X 56

X 66

X 100

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: JOSEPH FELICE

Buyer Office Symbol/Telephone Number: CCTA-ALH-C/(571)588-9093

Type of Contract 1: Firm Fixed Price

Kind of Contract: System Acquisition Contracts

Type of Business: Large Business Performing in U.S.

Surveillance Criticality Designator: A

Weapon System: No Identified Army Weapons Systems

*** End of Narrative A0000 ***

A.1 Army Contracting Command - Detroit Aresnal (DTA) Ombudsperson

Information regarding the Ombudsperson for this contract is located at the following website: http://acc.army.mil/contractingcenters/acc-wrn/CompMgmtOffice.html

A.2 ACCEPTANCE APPENDIX

(a) Contract Number W56HZV-23-C-0026 is awarded to AMERICAN RHEINMETALL VEHICLES LLC.

(b) The contractor, in its proposal, provided data for various solicitation clauses, and that data has been added in this contract.

(c) Any attachments not included within this document will be provided by ACC-DTA directly to the administrative contracting officer

(ACO) via e-mail as required. Technical data packages that are only available on CD-ROM will be mailed by ACC-DTA to the ACO. Within one week of this award, any office not able to obtain these attachments from System for Award Management (SAM) at beta.sam.gov and still requiring a copy, can send an e-mail request to the buyer listed on the front page of this contract.

(d) The following Amendment(s) to the solicitation are incorporated into this contract: 0001, 0002, 0003, 0004, 0005, 0006, and 0007.

*** END OF NARRATIVE A0001 ***

2 102

W56HZV-23-C-0026 REPRINT

AMERICAN RHEINMETALL VEHICLES , LLC

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

0001 PH 3 & 4 Detailed De

0001AA OMFV DETAILED DESIGN, PROTOTYPE, BUILD AND TEST 1 LO $ ** N/A ** $ 107,912,944.00 _______________________________________________ ______________ __________________

SERVICE REQUESTED: PH 3 & 4 Detailed De

CLIN CONTRACT TYPE:

Firm Fixed Price

PRON: 733009MC72 PRON AMD: 02 ACRN: AA

CLIN 0001 is for design, development, Prototype build, and test for 7 Prototype deliverables. The

Prototypes shall be delivered IAW Attachment 0051

(PPT Schedule).

(End of narrative B001)

Packaging and Marking _____________________

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

DOC SUPPL

REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____

001 000000 3

DEL REL CD QUANTITY DEL DATE __________ ______________ ___________

001 1 25-DEC-2027

FOB POINT: Destination

SHIP TO:

(W56HZV) XU W4GG HQ US ARMY TACOM

6501 EAST 11 MILE ROAD

ARMY CONTRACTING COMMAND WARREN

DETROIT ARSENAL,MI,48397-5000

0002 HARDWARE DELIVERABLES _____________________

B001 BALLISTIC HULL & TURRET 2 EA $ ** NSP ** $ ** NSP ** _______________________ ______________ __________________

COMMODITY NAME: HULL & TURRET

CLIN CONTRACT TYPE:

Firm Fixed Price

3 102

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

PSC: 1010

Packaging and Marking _____________________

All deliverables under this CLIN shall be packaged and marked IAW the requirements detailed in Section

D.

(End of narrative D001)

Inspection and Acceptance _________________________

INSPECTION: Origin ACCEPTANCE: Destination

Deliveries or Performance _________________________

DOC SUPPL

REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____

001 3

DEL REL CD QUANTITY DEL DATE __________ ______________ ___________

001 1 26-JUL-2026

002 1 23-FEB-2027

FOB POINT: Destination

SHIP TO:

(W56HZV) XU W4GG HQ US ARMY TACOM

6501 EAST 11 MILE ROAD

ARMY CONTRACTING COMMAND WARREN

DETROIT ARSENAL,MI,48397-5000

BH&T shall be shipped to Aberdeen Proving Ground IAW

Attachment 0051 (Production Prove-Out Test Schedule).

(End of narrative F001)

B002 PROTOTYPE VEHICLES 7 EA $ ** NSP ** $ ** NSP ** __________________ ______________ __________________

COMMODITY NAME: PROTOTYPES

CLIN CONTRACT TYPE:

Firm Fixed Price

PSC: 2350

Packaging and Marking _____________________

All deliverables under this CLIN shall be packaged and marked IAW the requirements detailed in Section

D.

(End of narrative D001)

4 102

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

Inspection and Acceptance _________________________

INSPECTION: Origin ACCEPTANCE: Destination

Deliveries or Performance _________________________

DOC SUPPL

REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____

001 3

DEL REL CD QUANTITY DEL DATE __________ ______________ ___________

001 2 26-JUL-2026

002 2 21-AUG-2026

003 2 25-SEP-2026

004 1 26-OCT-2026

FOB POINT: Destination

SHIP TO:

(W56HZV) XU W4GG HQ US ARMY TACOM

6501 EAST 11 MILE ROAD

ARMY CONTRACTING COMMAND WARREN

DETROIT ARSENAL,MI,48397-5000

Prototype Vehicles (PV) shall be shipped to the following locations IAW Attachment 0051 (Production

Prove-Out Test Schedule):

Location SHIP TO DoDAAC ________________________ ______________

PV1-2: Aberdeen Proving Ground W81C5M

PV3-4: Yuma Proving Ground (YPG) W905MY

PV5: Aberdeen Proving Ground W81C5M

PV6: White Sands Missile Range/YPG W81C39/W905MY

PV7: Aberdeen Proving Ground W81C5M

(End of narrative F001)

B003 ARMOR COUPONS 1 EA $ ** NSP ** $ ** NSP ** _____________ ______________ __________________

COMMODITY NAME: VEHICLE ARMOR

CLIN CONTRACT TYPE:

Firm Fixed Price

PSC: 9515

Armor Coupons shall be IAW Attachment 0069 (Armor

Coupons).

All deliverables under this CLIN shall be IAW the requirements detailed in Section F and inspection shall be IAW the requirements detailed in Section E.

(End of narrative B001)

5 102

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

Packaging and Marking _____________________

All deliverables under this CLIN shall packaged and marked in accordance with the requirements detailed in Section D.

(End of narrative D001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

DOC SUPPL

REL CD MILSTRIP ADDR SIG CD MARK FOR TP CD ______ ________ ______ ______ ________ _____

001 3

DEL REL CD QUANTITY DEL DATE __________ ______________ ___________

001 1 26-MAR-2026

FOB POINT: Destination

SHIP TO:

(W56HZV) XU W4GG HQ US ARMY TACOM

6501 EAST 11 MILE ROAD

ARMY CONTRACTING COMMAND WARREN

DETROIT ARSENAL,MI,48397-5000

Armor Coupons shall be shipped to Aberdeen Proving

Ground IAW Attachment 0051 (Production Prove-Out Test

Schedule).

(End of narrative F001)

0003 PROTOTYPE OPTION 1 LO $ ** N/A ** $ 66,807,958.00 ________________ ______________ __________________

SERVICE REQUESTED: OPTION VEHICLES

CLIN CONTRACT TYPE:

Firm Fixed Price

Prototype Vehicles (Section C.11), all Option

Prototype vehicle work under this CLIN shall be performed in accordance with Section C, Statement of

Work. This CLIN will be incrementally funded in accordance with B.1. The vehicle(s) shall be shipped to the location specified IAW H.8 and Attachment 0051

(PPT Schedule).

The USG reserves the unilateral right to incrementally exercise and incrementally fund the option. This may result in additional CLINs needed to

6 102

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

track the unexercised portion of the option and allow for multiple funding lines.

(End of narrative B001)

Packaging and Marking _____________________

Inspection and Acceptance _________________________

INSPECTION: Origin ACCEPTANCE: Destination

0004 CONTRACT DATA REQUIREMENTS LIST (CDRL) ______________________________________

A001 CONTRACT DATA REQUIREMENTS LIST 1 LO $ ** NSP ** _______________________________ __________________

SERVICE REQUESTED: CDRL'S

CLIN CONTRACT TYPE:

Firm Fixed Price

Technical Data as set forth in Contract Data

Requirements List (CDRL) DD form 1423, in Section J hereinafter referred to as Exhibit A.

Each CDRL listed in Exhibit A of Section J is set forth in the Exhibit Line Items below.

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

Period of Performance

Start Date: 26-JUN-2023

End Date: 25-DEC-2027

DLVR SCH PERF COMPL

REL CD QUANTITY DATE ________ ______________ __________

001 1 25-DEC-2027

7 102

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

B.1 Incremental Funding

B.1.1 CLIN 0001

The Government will provide funds under CLIN 0001 on an incremental basis IAW Defense Acquisition Regulation Supplement (DFARS) 252.232-

7007. It is estimated that the amounts shown are sufficient for the performance of the work in each of the cited funding periods.

The following is the Incremental Funding Schedule for the CLIN 0001:

Funding Period Amount

Award - Dec 31, 2023 $107,912,944

Jan 01, 2024 - Dec 31, 2024 $282,966,188

Jan 01, 2025 - Dec 31, 2025 $171,277,691

Jan 01, 2026 - Dec 31, 2026 $111,784,543

Jan 01, 2027 - End of contract $_71,826,399____________________________________________________

Total $745,767,765

B.1.2 CLIN 0003 Prototype Option

If the Option is exercised, (ref. C.11 & H.8), CLIN 0003 will be funded on an incremental basis IAW Defense Acquisition Regulation

Supplement (DFARS) 252.232-7007. The following is the Incremental Funding Schedule for CLIN 0003:

Funding Period Amount

Award - Dec 31, 2025 $37,945,931

Jan 01, 2026 - Dec 31, 2026 $26,474,350

Jan 01, 2027 - End of contract $ 2,387,677___________________________________________________

Total $66,807,958

*** END OF NARRATIVE B0001 ***

8 102

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

9 102

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 Environment (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.

10 102

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.

11 102

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.1 IAW Attachment 0028 (GCIA v2.1 SysML Model) and Attachment 0102 (GCIA v2.1 Data Architecture

Model). Attachment 0030 (GCIA v2.1 Architecture Description Document) and Attachment 0081 (GCIA v2.1 Data Architecture Definition) may

12 102

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

be used to provide further context.

At a component level, the contractors implementation of its Common Infrastructure Capability shall allow the Government to execute the following actions: maintain, exchange, update, upgrade, or change technology anytime. The contractors implementation shall allow these actions without modifying its common infrastructure capability, without modifying its existing interfaces, and without requiring any approval from the original developer.

The term original developer" means a prime contractor, system integrator, subcontractor, or a product vendor who designed, developed, implemented, modified, or sold components of a Contractors Common Infrastructure Capability.

The Contractor shall deliver the system architecture of the Common Infrastructure Capabilities and GCIA v2.1 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.1 SysML Model).

The Contractor shall utilize instantiations of the Common Infrastructure Capability IAW GCIA v2.1 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.1 Attachment 0028 (GCIA v2.1 SysML model).

The Contractor shall always utilize GCIA 2.1-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.1 SysML Model) and Attachment 0102 (GCIA v2.1 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.1.

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.1 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.1 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.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.1 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.

13 102

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

For other modular system interfaces not encompassed by the GCIA interfaces in section 2.4 of Attachment 0030 (GCIA v2.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

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, and all of its subcontractors, shall use the USG provided DevSecOps environment in Platform One for creating new software and modification of existing software for application to OMFV, to include firmware. Throughout section C.2.8 the mention of software includes firmware. The contractor shall conduct system level software integration testing, including all software and predictive models (which includes Artificial Intelligence and Machine Learning Models in this document) if using (see C.2.8.15) at every level which will be integrated into the OMFV platform, using the USG provided DevSecOps environment.

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 software created or modified within the USG provided 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)

For any software not created or modified within the USG provided DevSecOps environment the contractor shall provide CDRLs E007, E008, E012, E013, E015, E045, E085, E114, and E004.

C.2.8.3 Source Code & Executable

(Paragraph Deleted)

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.

14 102

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

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.8.15 Predictive Models

If the contractor creates predictive models as part of the contractors software solution, the contractor shall provide the predictive models and all predictive model workflows surrounding the predictive models to the USG. All predictive models and predictive model

15 102

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

workflows shall be open, modifiable, replicable, exportable, and interchangeable, and shall include the elements in Section C.2.8.15.1.

Predictive models and predictive model workflows shall be uploaded by the Contractor into the USG provided DevSecOps environment. The contractor shall use the predictive models and workflows in the USG DevSecOps environment for conducting software test.

The USG may provide Machine Learning Operations (MLOps) tools in the DevSecOps environment to aid with the development of predictive model elements. The USG may also provide access to Government hosted datasets for developing and maintaining autonomous capabilities.

The Contractor, and its subcontractors, may use additional MLOps tools and environments as long as all necessary deliverables defined in section C.2.8.15.2 are integrated into the USG provided DevSecOps environment and delivered to the Government IAW the CDRLs specified in

C.2.8.15.2. The Contractor shall submit requests for outside use of USG provided data to the Contracting Officer for approval. Requests shall be sent electronically via email. The contractor shall ensure that the USG retains the capability to train, validate, test, and maintain any models the contractor has created for OMFV with 3rd party data.

C.2.8.15.1 Predictive Model Elements

Any predictive model or predictive model workflow created for OMFV shall include the following elements:

a. Data exploration, preprocessing code, queries

b. Metadata describing datasets version

c. Feature definitions and stored features

d. Data labels

e. Data quality tests, including all code to run data quality tests

f. Any exploratory hosted notebooks and development code

g. Machine learning models in an open format (such as ONNX, PyTorch, TensorFlow) along with metadata on model versioning and deployment.

h. Experiment data to include training and validation logs, logged images/graphics, etc.

i. Model optimization and hyperparameter search results

j. The results of any model generated via AutoML techniques as defined by bullets f, g, and h, and i.

k. All training statistics, model weights, and training procedures in acceptable open formats as well as supporting code.

l. All evaluation set metadata and evaluation code.

m. Explainability and/or interpretability metrics for insights into the models

n. Any user-provided compliance and auditing workflows

o. Model serving configurations in open formats. Any containers used as part of model serving must be unencrypted or have the encryption keys well documented and provided to the government.

C.2.8.15.2 Predictive Model Documentation

For any predictive models created for OMFV, the following must be maintained current and viewable to the USG within the USG provided

DevSecOps environment and delivered IAW the associated CDRL. This information shall be included within the following CDRL deliveries required in C.2.8.2:

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

a. Includes all individual elements listed in C.2.8.15.1

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. Software Test Description (CDRL E085)

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

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

For any other predictive models not created for OMFV and used for the OMFV program, the contractor shall deliver CDRLs E007, E008, E012, E013, E015, E085, E114, and E004.

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.

16 102

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.10.1.1 Inherited CT and CPI

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.