W56HZV-22-R-0026.pdf

SOLICITATION, OFFER AND AWARD 1. This Contract Is A Rated Order Under

DPAS (15 CFR 700)

Rating Page of Pages

2. Contract Number 3. Solicitation Number 4. Type of Solicitation 5. Date Issued 6. Requisition/Purchase Number Sealed Bid (IFB)

Negotiated (RFP)

7. Issued By Code 8. Address Offer To (If Other Than Item 7)

NOTE: In sealed bid solicitations ‘offer’ and ‘offeror’ mean ‘bid’ and ‘bidder’.

SOLICITATION

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified in item 8, or if handcarried, in the depository located in until (hour) local time (Date).

Caution - Late Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. For Information A. Name B. Telephone (No Collect Calls) C. E-mail Address

Call: Area Code Number Ext.

11. 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 Attach.

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

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within _____ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. Discount For Prompt Payment 10 Calendar Days (%) 20 Calendar Days (%) 30 Calendar Days (%) Calendar Days (%) (See Section I, Clause No. 52.232-8)

14. Acknowledgment of Amendments (The offeror acknowledges Amendment No. Date Amendment No. Date receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

15A. Name and Code Facility 16. Name and Title of Person Authorized to Sign Offer Address of (Type or Print) Offeror

15B. Telephone Number 15C. Check if Remittance Address is 17. Signature 18. Offer Date Area Code Number Ext. Different From Above – Enter such

Address In Schedule

AWARD (To be completed by Government)

19. Accepted As To Items Numbered 20. Amount 21. Accounting And Appropriation

22. Authority For Using Other Than Full And Open Competition: 23. Submit Invoices To Address Shown In Item

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

24. Administered By (If other than Item 7) Code 25. Payment Will Be Made By Code

26. Name of Contracting Officer (Type or Print) 27. United States Of America 28. Award Date

(Signature of Contracting Officer)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION Standard Form 33 (Rev. 9-97) Previous edition is unusable Prescribed By GSA-FAR (48 CFR) 53.214(c)

W56HZV-22-R-0026

X

2022JUL01

2022NOV0112:00pm

DOA4

2022JUL01 SEE SCHEDULE

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

DARNELL JENNINGS II

(586)282-9039

CCTA-CBH-B

DARNELL.JENNINGS.CIV@ARMY.MIL

1 145

X 1

X 5 X 11

X 45 X 46 X 48

X 53

X 56

X 64

X 103

X 106

X 120

X 138

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

Optionally Manned Fighting Vehicle (OMFV)

Executive Summary

This Executive Summary is provided as an overview of selected points of the solicitation. It is not intended to provide all information included therein. Offerors are responsible to carefully read, understand and comply with the solicitation in its entirety. In the event of any inconsistencies between this Executive Summary and the solicitation, the solicitation shall rule.

A.1 OMFV Program Vision

The Optionally Manned Fighting Vehicle (OMFV) will serve as the Army's Infantry Fighting Vehicle (IFV) tasked to maneuver through the enemy's security zone as part of a combined arms team for the purpose of creating an advantageous position, relative to the enemy, and providing protection and direct fire lethality while manned or remotely operated. In the close fight, the OMFV enables the ability of dismounted elements to maneuver by detecting and destroying targets at a range beyond the enemy's capability.

A.1.1 Transformational Elements

The OMFV will transform how Soldiers and squads accomplish their mission in the following ways.

A.1.1.1 Enable Command and Control

The OMFV will enable command and control at the platoon level and higher by rapidly generating, receiving, and passing information to dismounted elements, other vehicles, and command nodes.

A.1.1.2 Provide Decisive Lethality

The OMFV will be able to detect, engage, and destroy enemy infantry fighting vehicles beyond the range of the enemy's primary weapon system, and rapidly defeat dismounted enemy threats. The OMFV will also enhance formation lethality by providing target acquisition data, shared situational understanding, and the lethal effects required to protect and orient the dismounted element.

A.1.1.3 Enhance Organizational Effectiveness

The OMFV will improve organizational effectiveness by reducing the logistics burden on the Armored Brigade Combat Team (ABCT). This will be achieved through enhanced reliability and on-board diagnostics and prognostics; ease of maintenance with the use of standard, common tools; and reduced burdens on the supply chain in terms of spare parts, fuel, and munitions.

A.1.1.4 Ability to Rapidly Adapt

The OMFV will adopt the latest digital engineering techniques, which will allow rapid adaptation by possessing Growth margins that allow for the insertion and integration of future technologies.

Designed from the beginning using a Modular Open Systems Approach (MOSA) and based on an Army-defined and owned open architecture standard, OMFV provides the Army an affordable pathway to OEM-independent upgrades at the hardware component level. As technology and software evolves, the Army's open architecture standard allows the OMFV to modernize rapidly at a reduced cost. This will also offer more opportunities for increased industry competition and innovation over the OMFV's lifecycle.

This digital approach to delivering OMFV creates a situation where the Army can affordably upgrade at the pace of technological advancement, and reduce the risk posed by strategic unpredictability with respect to the level of capability OMFVs provide the ABCTs.

A.2 Program Overview

A.2.1 Fundamentals

The Army is conducting a five (5) phased acquisition approach to design, prototype, test, and produce the OMFV.

The Army is committed to adopting digital engineering best practices, agile software development using a DevSecOps approach, and a cloud-based infrastructure in support of the OMFV program. The adoption of these principles are key enablers to support the rapid adoption, testing, and integration of future technologies.

OMFV is the U.S. Army's first ground combat vehicle designed using modern digital engineering tools and techniques. OMFV Contractors will develop the OMFV using Models Based System Engineering (MBSE) and within the digital domain to communicate the design's maturity and evolution via a series of interconnected digital models throughout the program lifecycle.

2 145

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

A.2.2 Phase 3: Detailed Design and Phase 4: Prototype Build and Test

The purpose of Phase 3 is to conduct detailed design activities to mature the OMFV designs and will culminate in a critical design review (CDR). Immediately following Phase 3 is Phase 4, Prototype Build and Test. The purpose of Phase 4 is to verify performance against the performance specification. Late in this phase, a Limited User Test will be conducted. In addition to the delivery of prototypes, the Contractor will develop, mature, and deliver a virtual prototype of their design. These phases will be a single contract with up to 3 contracts awarded.

A.2.3 Phase 5: Production and Fielding

The purpose of this phase is to have a single LRIP contract for production, testing and initial fielding. Activities include Pre-

Production Quality Testing (PQT) and Initial Operational Testing and Evaluation (IOT&E). This single contract is planned to be awarded from a competition limited to the Phase 3/4 Contractors. The Army is finalizing the criteria to select the LRIP contract, but are currently exploring performance, MOSA compliance, intellectual property (IP) rights provided, AUMP, end to end digital thread, and manufacturability. The Government intends to require follow-on production of the OMFV to occur in the United States (US).

A.3 OMFV Phase 3/4 Solicitation and Contract

The RFP requires up to 11 prototype vehicles (7 for a contract award and an option for 4 additional vehicles), as well as two Ballistic

Hulls and Turrets, Armor Coupons, digital model twins, and data.

The OMFV Phase 3/4 RFP is a Full and Open Competition. The Army intends to award up to three firm-fixed price contracts with a 54 month period of performance. Formal source selection procedures will be used. See Sections L and M for information required to be submitted in proposals and evaluation of proposals. VATEP (Value Adjusted Total Evaluated Price)will be utilized as part of the overall Price evaluation.

The Army is considering including an Economic Price Adjustment provision for prototype material for the option vehicles. Any such provision will be added by amendment.

A.3.1 Solicitation

This solicitation is for the Detailed Design, Prototype, Build and Test (Phases 3 and 4), and is solicited on a Firm-Fixed-Price basis.

The solicitation requires proposals for a total of 11 prototypes, 7 for a contract award and an option for 4 additional prototypes.

Information in this solicitation takes precedence over any information shared by the Government preceding the solicitation release, including but not limited to, information shared at one-on-one sessions, draft solicitation, or through Q&As released to date.

Assertion of Restrictions: The Offeror shall include in its proposal submission, its Assertion of Restrictions Attachment 0012

(Technical Data and Assertions). Additionally, any proposed special license(s) shall follow the format prescribed within Attachment 0013

(Special License Requirements).

Availability of Funding and Affordability: Contract award(s) will be made subject to the availability of funding. Affordability is addressed at M.3.1.

A.4 Phase 3/4 Proposal Evaluation

The Army will conduct a full and open competition using Best Value Source Selection procedures for the award of up to three contracts during third quarter of Fiscal Year (FY) 23. The Army reserves the right to make fewer than three awards if the value of additional awards up to three would offer only limited benefit (See M.1.1).

A.5 Administrative

Eligibility requirements for award and Rejection Criteria are included in the solicitation. Offerors should carefully review the solicitation to ensure all requirements for award are met.

Access to Classified, Controlled Unclassified Information (CUI), and Export Controlled Documents: All Offerors must have a valid FCL including safeguarding at SECRET level in order to respond to this solicitation. See Attachment 72 (Department of Defense (DD) Form

254,Contract Security Classification Specification) for security requirements. For Export Controlled information, it is the responsibility of the Offeror, not the Government, to obtain the appropriate export licenses, or process the appropriate export license exemption, necessary for authorization to share information with foreign vendors. Offerors who did not recieve CUI under the 17 June

2022 Draft release shall send their request to the general mailbox identified below. Your request shall include the following:

i. Your Company's name and address

ii. Your Name, Title, Office phone number and email address

iii. Copy of the approved DD Form 2345

Points of Contact (POCs):

Michael Chaney, Procuring Contracting Officer

586-282-5057 usarmy.detroit.peo-gcs.mbx.ngcv-omfv-contracting@mail.mil

3 145

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Joe Felice, Contract Specialist

586-282-9450 usarmy.detroit.peo-gcs.mbx.ngcv-omfv-contracting@mail.mil

James Giacchina, Contract Specialist

586-282-4131 usarmy.detroit.peo-gcs.mbx.ngcv-omfv-contracting@mail.mil

A.6 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.7 Public Activity Involvement

Subcontract opportunities under this solicitation and any resulting contracts are open to competition between Department of Defense activities and private firms. In addition, Army Industrial Facilities are available to sell manufactured articles or to perform work at such Facilities on behalf of Offerors, in certain circumstances and as permitted by law. Rock Island Arsenal, Waterlivet Arsenal, Anniston Army Depot, Sierra Army Depot, or Red River Army Depot have expressed interest in securing subcontracting opportunities under this RFP. For information related to the capabilities of these facilities visit the following links:

http://www.amc.army.mil/Portals/9/Documents/AMC%20Publications/AMC%20P3Contact%20Information.pdf?ver=2017-09-18-073343-597 http://www.amc.army.mil/Portals/9/Documents/AMC%20Publications/AMC_0817_RESOURCE-GUIDE.pdf?ver=2017-10-03-110207-990

A.8 Acknowledgement of Amendments

Acknowledge all the amendments received from the Government by identifying the amendment number and its issue date in the box below:

Amendment Number: Date:

A.9 Electronic Contracting

All Army Contracting Command Detroit Arsenal solicitations will be publicized on the System for Award Management website

(https://www.sam.gov ). Any additional attachments, including Technical Data Packages (TDPs) when available electronically, will be separate attachments or links embedded in the solicitation.

Pay close attention to the Issued By block location on the cover page of the solicitation for closing date and time. The closing date and time is based on the local time of the listed location of the Issued By office. In accordance with FAR 15.208(a), offerors are responsible for submitting proposals, and any revisions, and modifications, so as to be received by the Government office designated in the solicitation by the time specified.

It is the responsibility of the Offeror to ensure the proposal/quote is received by the date and time specified on the cover page of this solicitation. In accordance with FAR 15.208, if the proposal/quote was not received at the initial point of entry to the Government infrastructure by the exact date and time specified on the cover page of this solicitation, it will be determined late. Proposal/quote is defined to mean ALL volumes or parts required in the solicitation are included in the submission.

Questions pertaining to this solicitation should be directed to the Contract Specialist identified on the cover page of this solicitation. For technical assistance in doing business with the Government, and doing business electronically, please visit the

Procurement Technical Assistance Center (PTAC) website at http://www.aptac-us.org/ to locate a regional center.

*** END OF NARRATIVE A0001 ***

4 145

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 OMFV DETAILED DESIGN, PROTOTYPE, BUILD AND TEST 1 LO $ $ _______________________________________________ ______________ __________________

SERVICE REQUESTED: OMFV PHASE 3 AND 4 BASE

CLIN CONTRACT TYPE:

Firm Fixed Price

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 3

DEL REL CD QUANTITY DAYS AFTER AWARD __________ ______________ ________________

001 1 1643

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

Packaging and Marking _____________________

All deliverables under this CLIN shall be packaged

5 145

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

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 DAYS AFTER AWARD __________ ______________ ________________

001 1 1126

002 1 1338

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

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

6 145

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

DEL REL CD QUANTITY DAYS AFTER AWARD __________ ______________ ________________

001 2 1126

002 2 1152

003 2 1187

004 1 1218

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

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)

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)

7 145

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: Destination ACCEPTANCE: Destination

Deliveries or Performance _________________________

DOC SUPPL

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

001 3

DEL REL CD QUANTITY DAYS AFTER AWARD __________ ______________ ________________

001 1 1004

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 $ $ ________________ ______________ __________________

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: Destination ACCEPTANCE: Destination

8 145

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

Deliveries or Performance _________________________

DOC SUPPL

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

001 3

DEL REL CD QUANTITY DAYS AFTER AWARD __________ ______________ ________________

001 1 1703

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

0004 CONTRACT DATA REQUIREMENTS LIST (CDRL) ______________________________________

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

SERVICE REQUESTED: CDRL'S

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

DEL REL CD QUANTITY DAYS AFTER AWARD __________ ______________ ________________

001 1 1643

9 145

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 $XXX*

Jan 01, 2024 - Dec 31, 2024 $XXX*

Jan 01, 2025 - Dec 31, 2025 $XXX*

Jan 01, 2026 - Dec 31, 2026 $XXX*

Jan 01, 2027 - End of contract $XXX*_____________________________________________

Total $XXX*

*To be Proposed by the Contractor. Not to Exceed the amounts stated in M.3.1.1.

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 $XXX*

Jan 01, 2026 - Dec 31, 2026 $XXX*

Jan 01, 2027 - End of contract $XXX*_____________________________________________

Total $XXX*

*To be Proposed by the Contractor. Not to Exceed the amounts stated in M.3.1.1.

*** END OF NARRATIVE B0001 ***

10 145

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

11 145

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

12 145

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

13 145

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.

14 145

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

15 145

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.8.1 DevSecOps

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

C.2.8.1.1 Platform One

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

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

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

System IAW CDRL E024.

C.2.8.2 Software Design Documentation

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

IAW the associated CDRL:

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

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

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

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

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

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

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

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

i. Software Test Report (CDRL E015)

j. GCIA Test Report (CDRL E045)

k. Software Test Description (CDRL E085)

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

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

C.2.8.3 Source Code & Executable

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

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

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

C.2.8.4 Software Version Description (SVD)

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

CDRL E012.

C.2.8.5 Software Architecture Document

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

C.2.8.6 OMFV System and Support Systems Software Licenses

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

C.2.8.7 Software Transition Plan

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

C.2.8.8 Software Qualification Testing (SQT)

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

(SQTR) IAW CDRL E015.

C.2.8.9 Software Quality Assurance

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

16 145

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.8.10 Software Assurance

The Contractor shall ensure that protection and assurance activities aimed at mitigating attacks against the operational system throughout the system life cycle and those that address threats to the development environment that are documented, implemented, and delivered in…