OMFV RFP W56HZV-22-R-0026_0001.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

0001 2022AUG05

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 77

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 0001 to Solicitation W56HZV-22-R-0026 is to incorporate revisions as follows:

a. Section B: __________

i. CLIN 0003 is updated to delete the delivery date of 1703 days after award.

ii. CLIN 0003 inspection is changed from destination to origin.

b. Section C: __________

i. C.2.4.1 is modified to correct an administrative error. CDRL 041 is changed to CDRL E041.

ii. C.2.12 is modified to update the paint requirement as follows:

From:

C.2.12 Corrosion Prevention and Control

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

To:

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.

iii. Add the word independent in reference to crew sight as follows:

From:

C.3.1 Technology Maturation Planning

If the Contractor's design is equipped with a cannon other than an XM913, and/or 3rd Generation Forward Looking Infrared (3GF)

B-kit components for crew sight, the Contractor shall deliver a technical report IAW CDRL E079.

The report shall contain the following information between the Contractor's system design and the Contractor's design with key technologies integrated (XM913 and/or 3rd Generation Forward Looking Infrared (3GF) B-kit components for crew sight):

a. Performance differences

b. Size differences

c. Non-recurring costs to implement (Engineering and Logistics)

d. Estimated schedule to implement

e. BOM differences of parts that would have to be redesigned, not used, and/or new parts

f. Any additional information critical information related to the integration of these key technologies

To:

C.3.1 Technology Maturation Planning

If the Contractor's design is equipped with a cannon other than an XM913, and/or 3rd Generation Forward Looking Infrared (3GF)

B-kit components for crew independent sight, the Contractor shall deliver a technical report IAW CDRL E079.

2 77

W56HZV-22-R-0026

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The report shall contain the following information between the Contractor's system design and the Contractor's design with key technologies integrated (XM913 and/or 3rd Generation Forward Looking Infrared (3GF) B-kit components for crew independent sight):

a. Performance differences

b. Size differences

c. Non-recurring costs to implement (Engineering and Logistics)

d. Estimated schedule to implement

e. BOM differences of parts that would have to be redesigned, not used, and/or new parts

f. Any additional information critical information related to the integration of these key technologies

iv. Define Ballistic Hull and Turret (BH&T) in C.5.2.4 as follows:

From:

C.5.2.4 Active Protective System (APS) System Testing

If the Contractor's design includes an Active Protective System (APS), the Contractor shall provide one of the two BH&T assets delivered IAW Attachment 0051 (PPT Schedule) be outfitted with a complete, working APS system for APS system testing.

To:

C.5.2.4 Ballistic Hull and Turret (BH&T)

The Contractor shall deliver two BH&T assets IAW Attachment 0051 (PPT Schedule).

C.5.2.4.1 BH&T Definition

A "Ballistic Hull and Turret (BH&T)" is defined as:

1. A basic hull structure that incorporates (when in the design) seats, false floor, spall liners, armor modules, grilles, hatches, access covers, fuel tanks, periscopes, onboard energetics compartmentalization, and structural components required for transportability (e.g., lifting eyes);

2. A basic turret structure that includes the gun mount and gun shield, and incorporates (when in the design) seats, spall liners, armor modules, grilles, hatches, access covers, periscopes, onboard energetics compartmentalization, and structural components required for transportability (e.g., lifting eyes); and

3. CE armor solutions.

C.5.2.4.2 Active Protective System (APS) System Testing

If the Contractor's design includes an Active Protective System (APS), the Contractor shall provide one of the two BH&T assets delivered IAW Attachment 0051 (PPT Schedule) to be outfitted with a complete, working APS system for APS system testing.

c. Section E: __________

i. Paragraph E.2, Final Inspection Record, is revised as follows:

From:

E.2 Final Inspection Record

The contractor shall deliver a Preliminary Final Inspection Record (PFIR) IAW CDRL T017 to be used for prototype vehicle inspection at the contractor's site prior to any shipments and for acceptance at end of contract performance. The PFIR shall be organized to be compatible with assemblies, installation, and end item performance. The PFIR shall contain all examinations and tests that are performed on a single unit during its manufacture and final inspection. The PFIR shall list each vehicle characteristic or function to be inspected from the vehicle specification.

To:

E.2 Final Inspection Record

E.2.1 The contractor shall deliver a Preliminary Final Inspection Record (PFIR) IAW CDRL T017 to be used for prototype vehicle inspection at the contractor's site prior to any shipments and for acceptance at end of contract performance. The PFIR shall be organized to be compatible with assemblies, installation, and end item performance. The PFIR shall contain all examinations and tests that are performed on a single unit during its manufacture and final inspection. The PFIR shall list each vehicle characteristic or function to be inspected from the vehicle specification.

3 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

E.2.1.1 Prior to vehicle shipment at the test site or shipped in place, the contractor shall conduct an inspection utilizing the

PFIR and provide with the vehicle.

E.2.1.2 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.

d. Section H: __________

i. The following paragraphs have been added for the reliability incentive as follows:

H.14 Reliability Incentive

H.14.1 General. The OMFV PSPEC defines the Mean Miles Between Systems Abort (MMBSA) reliability requirement. Attachments 0051

(Production Prove-out Test Schedule) and 0070 (Reliability Growth Planning Model) specify the planned reliability events (PPT1 and

PPT2) and the expected MMBSA performance at conclusion of each event. This provision establishes incentive awards for exceeding expected performance at conclusion of each event.

H.14.2 Applicable conditions. The USG anticipates conducting reliability testing at various locations, timeframes, and planned mileage IAW Attachment 0051 (Production Prove-out Test Schedule). However, the actual vehicles/locations, timeframes, and mileage may differ from anticipated Regardless of any differences, testing conducted prior to the Corrective Action Period (CAP) constitutes PPT1, and testing conducted after the CAP constitutes PPT2.

H.14.3 MMBSA determination. At the conclusion of PPT1 and PPT2, the USG will calculate the demonstrated MMBSA for the Hardware and

Software(HW/SW) values of Test Incident Reports (TIRs) IAW Attachment 0052 (Failure Definition and Scoring Criteria (FDSC)) as calculated below:

H.14.3.1 The USG will make PPT MMBSA determination(s) without regard to any assessment conferences or fix effectiveness factors

(FEFs) related to any corrective actions. The MMBSA will be calculated as a point estimate based on the actual total PPT RAM miles

(for all the Contractor's RAM vehicles accumulated from the beginning to end of each PPT), divided by the total HW/SW PPT System

Aborts(SAs) as reported during each PPT. Test Center data shall be the single data source for RAM miles and SAs, as opposed to data or results generated in any digital engineering model, or otherwise. The USGs calculated MMBSA pursuant under this provision will be final.

H.14.4 Award amounts. The incentive award amount for each event is detailed below (Table 1 and Table 2) and is determined using the

USG calculated MMBSA. The award amount for each event will be earned separately and without consideration of the other event. Both events are eligible for incentive awards if the MMBSA values meet the Table conditions. The award amounts are definite for each mileage range and they will not be prorated within a range.

Table #1 (PPT1): USG Calculated MMBSA Range for PPT1 ___________________________________ PPT1 Incentive Award ____________________

MMBSA< 557 miles $0

MMBSA> or = 557 miles, but < 650 miles $2 Million

MMBSA> or = 650 miles $4 Million (Maximum PPT1 Award)

Table #2 (PPT2): USG Calculated MMBSA Range for PPT2 ___________________________________ PPT2 Incentive Award ____________________

MMBSA< 686 miles $0

MMBSA> or = 686 miles, but < 800 miles $2 Million

MMBSA> or = 800 miles $4 Million (Maximum PPT2 Award)

H.14.5 Notification and payment. The Procuring Contracting Officer (PCO) will notify the contractor of the USG's calculated MMBSA results after all TIRs are scored for each event and make payment by unilateral modification promptly thereafter subject to the availability of funds. The parties agree that the USG determinations under this provision are final and are not subject to the

Disputes provision of this contract.

ii. The following paragraphs have been added for the Economic Price Adjustment (EPA) under the Prototype Option (CLIN 0003):

H.15 ECONOMIC PRICE ADJUSTMENT - CLIN 0003

H.15.1 The purpose of this section is to provide for economic price adjustment, upward or downward, for the vehicle prototype option CLIN 0003. Any such price adjustment will be determined by completion of the EPA Table (Attachment 0107). This clause applies only to the prototype option CLIN 0003; no adjustment will be applied to CLIN 0002 BH&T (B001), Base Prototype Vehicles (B002), 4 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Armor Coupons (B003), detailed design of the prototypes, and applicable testing.

H.15.2 Any price adjustment will be determined by completion of the EPA Table (Attachment 0107) located at the end of this provision and is applicable only to prototype vehicles under CLIN 0003.

The Contracting Officer will utilize the most recently published PPI index (even if preliminary) as of 30 September 2024 to calculate the upward or downward price adjustment IAW Attachment 0107. The index and price subject to adjustment are as follows:

Index - PPI Code 33612, Heavy Duty Truck Manufacturing. Published by U.S. Department of Labor Bureau of Labor Statistics in its publication, PPI Detailed Report.

H.15.3 A total of 65 percent (65%) of the contract price for the CLIN 0003 Prototype Option (H.8) is the portion of the Price

Subject to Adjustment, hereinafter referred to as the "PSA", for all adjustments herein.

H.15.4 Under this clause, the maximum increase will be no more than $4,800,000. There will be no limitation on the amount of decrease under this clause.

H.15.5 Economic price adjustment to the contract price will be made against CLIN 0003, IAW Attachment 0107:

H.15.5.1 When the actual index value (Column (4)) is within the non-adjustment band (Column (3)), no adjustment will be made.

H.15.5.2 When the actual index value (Column (4)) is outside the non-adjsutment band (Column (3)), the amount in Column (7) will be the adjustment to contract price for CLIN 0003 (rounded to the nearest dollar) subject to the maximum increase stated in H.15.4.

H.15.6 Any Economic Price Adjustment will be incorporated by a unilateral contract modification prior to 31 December 2024, which will include adjusted contract price to CLIN 0003 only.

H.15.7 In the event any index cited is discontinued or substantially altered by the Bureau of Labor Statistics, the parties shall mutually agree on an appropriate substitute index to be effective as of the date of index discontinuance or alteration.

In the event an index is discontinued or substantially altered, the parties will proceed to mutually establish a replacement index.

If mutual agreement cannot be reached prior to 30 September 2024, the Contracting Officer may make a unilateral index replacement.

Alternatively, the parties may continue to mutually proceed to establish a replacement index. In this case, the Government may exercise the option using the contract price (as a billing price), pending agreement on a replacement index needed to calculate the price adjustment.

H.15.8 The contractor warrants that the prices set forth in this clause do not include allowances for any contingency to the extent covered by this clause.

H.15.9 Regardless of the actual cost during the performance of this contract, economic price adjustments will be made only as provided herein.

H.15.10 The contractor shall certify on a final adjusting invoice that the amounts invoiced under this contract reflect all decreases required by this clause.

H.15.11 Pricing actions pursuant to the "Changes" clause or other provisions within this contract will be priced as though there were no provision for Economic Price Adjustment. All changes made that result in a new contract price under CLIN 0003 prior to option exercise will be reflected in the PSA.

e. Section I: __________

i. Clause 252.232-7015 Performance-Based Payments Representation has been deleted.

f. Section J: __________

i. Exhibit A is revised as follows:

a. The page count for Exhibit A is corrected to reflect 112 in lieu of 138.

b. CDRL T001 Authority block is revised from DI-SESS-81704 to DI-NDTI-80566A.

c. CDRL T002 Authority block is revised from DI-MISC-80508B to DI-NDTI-80809B.

d. CDRL L025 is revised as follows:

From:

5 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Block 12 and 13: If an item was classified as a Special Group Item (SGI) the Contractor shall deliver the SGI's Packaging

Validation Report concurrent with the packaging data deliverable (L029).

To:

Block 12 and 13: If an item was classified as a Special Group Item (SGI) the Contractor shall deliver the SGI's Packaging

Validation Report.

The Contractor shall deliver at least 30% Packaging Validation Report 30 days after the completion of each Provisioning

Conference (PC).

The Contractor shall deliver at least 60% Packaging Validation Report 60 days after the completion of each PC.

The Contractor shall deliver all 100% Packaging Validation Report 90 days after the completion of each PC.

e. CDRL L030 is revised as follows:

From:

Blocks 12 and 13: If an item was classified as a Special Group Item (SGI), the Contractor shall deliver the SGI's Special

Packaging Instructions concurrent with the packaging data deliverable (L029).

To:

Block 12 and 13: If an item was classified as a Special Group Item (SGI), the Contractor shall deliver the SGI's Special

Packaging Instructions.

The Contractor shall deliver at least 30% Special Packaging Instructions 30 days after the completion of each Provisioning

Conference (PC).

The Contractor shall deliver at least 60% Special Packaging Instructions 60 days after the completion of each PC.

The Contractor shall deliver all 100% Special Packaging Instructions 90 days after the completion of each PC.

ii. Attachment 0010 is revised from REV 001 dated 28 Jun 2022 to REV 002 dated 03 Aug 2022.

iii. Attachment 0018 is revised from REV 001 dated 29 Jun 2022 to REV 002 dated 28 July 2022.

iv. Attachment 0020 is revised from REV 001 dated 28 Jun 2022 to REV 002 dated 28 Jul 2022.

v. Attachment 0027 is revised from REV 002 dated 28 Jun 2022 to REV 003 dated 28 Jul 2022.

vi. Attachment 0034 is revised from original dated 29 Mar 2002 to REV 001 dated 03 Aug 2022.

vii. Attachment 0044 is revised from REV 002 dated 23 Jun 2022 to REV 003 dated 22 Jul 2022.

viii. Attachment 0051 is revised from REV 002 dated 16 Jun 2022 to REV 003 dated 19 Jul 2022.

ix. Attachment 0055 is deleted.

x. Attachment 0070 is revised from original dated 21 Jun 2022 to REV 001 dated 28 Jul 2022.

xi. The title for Attachment 0072 is corrected to reflect the Revision Number as 002 in lieu of 004.

xii. Attachment 0091 is revised from REV 001 dated 29 Jun 2022 to REV 002 dated 04 Aug 2022.

xiii. Attachment 0097 is revised from REV 001 dated 29 Jun 2022 to REV 002 dated 04 Aug 2022.

xiii. Attachment 0100 is corrected to reflect the date as "28 Jun 2022" in lieu of "29 Mar 2022".

xiv. Attachment 0102 is revised from original dated 01 Apr 2022 to REV 001 dated 05 Aug 2022.

xiv. Attachment 0107 Economic Price Adjustment Table (CUI) dated 04 Aug 2022.

*See attachment revision logs for specific changes under each attachment.

g. Section L: __________

i. Revise L.3.2.1 to remove reference to Attachment 0055 as follows:

From:

L.3.2.1 Subfactor 1: Survivability

Evaluated item A (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.4.1)

Evaluated item B (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.5.1)

Evaluated item C (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.8.1)

Evaluated item D (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.9.1, 4.1.10.1)

Signature Management (CPSPEC 2.1.1)

Signature Management (CPSPEC 2.2.1)

Specific, additional Instructions for Factor 1, Subfactor 1: Survivability

In addition to the substantiating data required by L.3.1, the Offeror shall provide:

6 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Performance values proposed for the listed PSPECS IAW the instructions provided within

Attachment 0018 (Technical Performance Data Instructions).

Armor Recipe Characteristics (Attachment 0053).

Underbody Analysis Data Instructions (Attachment 0054).

Vehicle Vulnerability Data Instructions (Attachment 0055).

Active Protection Data (Attachment 0057).

To:

L.3.2.1 Subfactor 1: Survivability

Evaluated item A (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.4.1)

Evaluated item B (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.5.1)

Evaluated item C (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.8.1)

Evaluated item D (PSPEC-1090, CPSPEC 4.1, 4.1.1, 4.1.9.1, 4.1.10.1)

Signature Management (CPSPEC 2.1.1)

Signature Management (CPSPEC 2.2.1)

Specific, additional Instructions for Factor 1, Subfactor 1: Survivability

In addition to the substantiating data required by L.3.1, the Offeror shall provide:

Performance values proposed for the listed PSPECS IAW the instructions provided within

Attachment 0018 (Technical Performance Data Instructions).

Armor Recipe Characteristics (Attachment 0053).

Underbody Analysis Data Instructions (Attachment 0054).

Active Protection Data (Attachment 0057).

ii. Revise the SysML format in L.4.3 as follows:

From:

L.4.3 GCIA Sample Task

2 - The offeror shall modify and submit the government provided GCIA Sample Task Logical Model to show compliance with GCIA 2.0, fixing the identified deviations in the model. The Offeror cannot change the requirements in the GCIA Sample Task Logical

Model. The Offeror shall submit the modified GCIA Sample Task Logical Model in the same format as it's delivered (SysML

V1.6) and shall follow the model changing guidelines specified in the model to make the necessary fixes.

To:

L.4.3 GCIA Sample Task

2 - The offeror shall modify and submit the government provided GCIA Sample Task Logical Model to show compliance with GCIA 2.0, fixing the identified deviations in the model. The Offeror cannot change the requirements in the GCIA Sample Task Logical

Model. The Offeror shall submit the modified GCIA Sample Task Logical Model in SysML 1.4 or newer 1.x (not SysML 2.x), which is compatible with MagicDraw 2021. The offeror shall follow the model changing guidelines specified in the model to make the necessary fixes.

iii. Paragraph L.7.14 is added as follows: The Offeror shall consolidate and identify, in Volume 5, all GFP it proposes to use for performance under the resultant contract based on the list of GFP offered by the Government within Attachment 0044 (GFM List).

iv. Paragraph L.7.15 is added as follows: List all the programming languages, as well as the tools and build process, planned to be used in the development of the OMFV software.

h. Section M: __________

i. The Funding Schedule Table in Paragraph M.3.1.1 as follows:

From:

Funding Period Basic Award Amount ($M) _______________________________________________

Award - Dec 31, 2023 $ 108.5

Jan 01, 2024 - Dec 31, 2024 $ 286.1

Jan 01, 2025 - Dec 31, 2025 $ 208.7

Jan 01, 2026 - Dec 31, 2026 $ 143.0

7 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Jan 01, 2027 - End of contract $ 65.2 ____________________________________________

Total $ 811.4

Funding Period Option Amount ($M) _______________________________________________

Award - Dec 31, 2025 $ 71.8

Jan 01, 2026 - Dec 31, 2026 $ 1.6

Jan 01, 2027 - End of contract $ 1.3 ____________________________________________

Total $ 74.3

To:

Funding Period Basic Award Amount ($M) _______________________________________________

Award - Dec 31, 2023 $ 108.5

Jan 01, 2024 - Dec 31, 2024 $ 286.0

Jan 01, 2025 - Dec 31, 2025 $ 208.7

Jan 01, 2026 - Dec 31, 2026 $ 143.0

Jan 01, 2027 - End of contract $ 65.2 ____________________________________________

Total $ 811.4

Funding Period Option Amount ($M) _______________________________________________

Award - Dec 31, 2025 $ 71.8

Jan 01, 2026 - Dec 31, 2026 $ 1.6

Jan 01, 2027 - End of contract $ 1.4 ____________________________________________

Total $ 74.8

*** END OF NARRATIVE A0002 ***

8 77

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

0003 PROTOTYPE OPTION 1 LO $ $ ________________ ______________ __________________

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

Deliveries or Performance _________________________

DOC SUPPL

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

001 3

DEL REL CD QUANTITY DEL DATE __________ ______________ ___________

001 DELETED

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

9 77

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 level component 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

The Contractor shall execute modeling, simulation, and analysis (MS&A) throughout the life of the program to satisfy the use cases of

10 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

C.2.3.2 Contractor IDEE

11 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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.

The Contractor's approach for the MOSA shall enable refreshment and upgrade of technologies at a component level, through modular

12 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

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

13 77

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

14 77

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…