(DRAFT2) Prototype Project Agreement (PDF Version).pdf

Distribution Statement A. Approved for public release: distribution is unlimited.

PEO GCS OPSEC# OPSEC-2026-232

PROTOTYPE PROJECT AGREEMENT

Concerning

Mobile Tactical Cannon (MTC)

Other Transaction Prototype Project under 10

U.S.C. §4022

BETWEEN

{Vendor Name}

{Vendor Address}

{Vendor CAGE Code}

AND

The Government:

United States Army Contracting Command – Detroit Arsenal

(ACC-DTA)

SECTION 1: GENERAL INFORMATION

1.0. This Fixed Price Prototype Project Agreement (PPA) results from a competitive solicitation, evaluation, and selection process. Under this PPA, the identified Contractor shall serve as a collaborative partner with the Government.

1.1. This bi-laterally executed PPA is between the Contractor and the Government. This PPA, to include all attachments and appendices, describes the rights, duties, obligations, and privity of contract between the parties created by this PPA. The Contractor shall be responsible for performance of the work set forth in the PPA and associated attachments and appendices, as agreed upon by the Government and the

Contractor. The Government’s designated Agreements Officer Representative (AOR) for the specific project will serve as the Government technical point of contact.

1.2. By executing this PPA, the Contractor, and the Government (referred to collectively as “Parties”) hereby agree that the Parties shall adhere to all terms and conditions described herein and in the associated attachments and appendices to the PPA, to include the non-negotiable general terms and conditions listed in Appendix A – Project Articles (entirety), and Appendix B – Project Other Terms and

Conditions .

SECTION 2: PRODUCTION FOLLOW-ON ACTIVITIES

2.0. Pursuant to 10 USC §4022(f),“a follow-on production contract or transaction may be awarded to the participants of the transaction without the use of competitive procedures…..if A) competitive procedures were used for selection of the parties for participation in the transactions; and B) the participants in the transaction successfully completed the prototype project provided for in the transaction.”

2.1. Prototype Success Metrics:

The prototype will be deemed successful by the Government if it meets the metrics below. The prototype will be evaluated by the Government using information collected throughout performance of the PPA.

2.1.1. Soldier Evaluation.

The prototype will be deemed successful if the Mobile Tactical Cannon (MTC) demonstrates mission viability with US Army Soldiers through Evaluation events, inclusive of performance, reliability, and operational value.

2.1.2. Operationally Useful Integration into US Army Fires Network.

The prototype will be deemed successful if US Army Soldiers, without intervention from USG or

Contractor personnel, can execute operationally relevant digital fire missions.

2.1.3. Demonstration of Cyber Resilience.

The prototype effort will be deemed successful if the Contractor can provide evidence that, with minimal modifications, the prototype could achieve Authority to Operate (ATO) under the US Army

Risk Management Framework (RMF) with a medium or lower risk rating.

2.1.4. Demonstration of a viable path to US Army supportability

The prototyping effort will be deemed successful if the Contractor can provide a plan that shows how the US Army will be able to support the prototype during long-term production, with special emphasis on crucial software, technical data, and manufacturing and supply of critical components.

The plan must also address configuration management, obsolescence management, supply chain risk management and how the US Army will be able to oversee these activities.

2.1.5. Demonstrate a viable path to US Army Full Material Release

The prototyping effort will be deemed successful if the system does not demonstrate any deficiencies in safety, suitability, or supportability that would preclude the system from achieving Full Material

Release (FMR).

2.2. The Government shall be solely responsible for documenting whether competitive procedures were utilized and whether prototype projects were successfully completed. Any follow-on production effort will be pursued outside of this agreement and will be entered into by the Government and the follow-on production Contractor(s). The potential follow-on production effort is primarily intended to procure systems to replace M777 towed howitzers within the Army. The potential follow-on production effort may include ancillary services and ancillary items such as spare parts, technical manuals, etc. Note that the information provided within this section is for planning purposes only and is an estimate that is subject to change based on the progression of the prototype project, funding, schedule and other considerations.

Also note that if a Contractor is selected for a production follow-on effort, the Contractor will be required to demonstrate the ability to satisfy one of the conditions at 10 USC §4022(d) prior to follow-on production award.

SECTION 3: DELIVERY AND PRICING/INVOICING

3.0. Invoice Instructions / Payments

The Contractor shall invoice against the following Milestone Payment Schedules. The Milestone Payment

Schedule is effective from the day of agreement execution. The Contractor shall submit invoices for payment in accordance with the Milestone Payment Schedule and the terms of Appendix B, Project Terms and Conditions. The Contractor shall submit all invoices through the Wide Area Work Flow (WAWF) system. Inspection and acceptance of invoices within WAWF is the responsibility of the Agreements

Officer Representative (AOR). The tables are broken out into major hardware deliveries and service milestones.

3.1. The Contractor shall deliver the prototype hardware identified in section 4.0 in accordance with the tables below. Grouped Unfunded Milestones (UM) will stagger deliveries by 30 days. The Contractor shall deliver a BOM IAW CDRL A007 with each vehicle delivery, to receive payment.

{DRAFT RELEASE NOTE: The Government is seeking feedback on feasibility of all below timelines inclusive of ammunition availability timelines}

Prototype MTC system delivery

Vehicle Qty Delivery after award (days)

Delivery

Location

Contract Base /

Unfunded

Milestone (UM)

Fixed Price Funded

1 60 CONUS Base

2 360 CONUS Base

2 390 CONUS Base

1 420 CONUS Base

3 450 CONUS UM

3 450 CONUS UM

3 450 CONUS UM

3 450 CONUS UM

Cannon/Breech Assemblies for Proof Gun Stand (USG PGS)

Assemblies Delivery after award (days)

Delivery

Location

Contract Base /

Unfunded

Milestone (UM)

Fixed Price Funded

1 120 CONUS Base

1 150 CONUS Base

3 300 CONUS Base

Ammunition storage cells for Sequential Environmental Testing

Type Delivery after award (days)

Delivery

Location

Contract Base /

Unfunded

Milestone (UM)

Fixed Price Funded

Howitzer

Projectile 300 CONUS Base

Howitzer

Propellant 300 CONUS Base

Training System

Training System

Delivery after award

(days)

Delivery

Location

Contract Base /

Unfunded

Milestone (UM)

Fixed Price Funded

2 420

CONUS U.S.

Army Installation Base

2 270 Fort Sill, Oklahoma

UM

Test Ammunition – OPTION

Ammunition Delivery after award

(days)

Delivery

Location

Contract Base

/ Unfunded

Milestone

(UM)

Fixed

Price Funded

Increment 1 HE

Projectiles

TBD, with first vehicle delivery?

CONUS UM

Increment 2 HE

Projectiles

TBD, with 6th vehicle delivery?

CONUS UM

Increment 3 HE

Projectiles

TBD, with 18th vehicle delivery?

CONUS UM

Increment 1

Training

Projectiles

300 CONUS UM

Increment 1

Primers

TBD, with first vehicle delivery?

TBD, CONUS

U.S. Army

Location

UM

Increment 2

Primers

TBD, with 6th vehicle delivery?

TBD, CONUS

U.S. Army

Location

UM

Increment 3

Primers

TBD, with 18th vehicle delivery?

TBD, CONUS

U.S. Army

Location

UM

Increment 1

Propelling Charges

TBD, with first vehicle delivery?

TBD, CONUS

U.S. Army

Location

UM

Increment 2

Propelling Charges

TBD, with 6th vehicle delivery?

TBD, CONUS

U.S. Army

Location

UM

Increment 3

Propelling Charges

TBD, with 18th vehicle delivery?

TBD, CONUS

U.S. Army

Location

UM

Service Payment Schedule

Milestone Name Delivery after award

(days)

Scope

Reference

Contract Base

/ Unfunded

Fixed

Price Funded

Milestone

(UM)

Completion of

Start of Work

Meeting

14 4.6.5.2

Ballistic Kernel data for US FDC

(CDRL A002),

IMS (CDRL

A022)

4.6.3.7

Complete PMR 1 TBD 4.5.6

Complete PMR 2 TBD 4.5.6

Integration &

Technical

Support

(monthly)

4.6

System

Engineering

Delivery of System

Design Review

(A001)

45 4.6.2

Fire Control and

Network

Integration

(a) Completion of

Tactical Radio

Integration

TBD 4.6.3.2

(b) Completion of

Position/Navigatio n/Timing Device

TBD 4.6.3.3

(c)Fire Mission

Data Processing integration 300 (prior to delivery of system 2) 4.6.3.4

(d) Completion of

Command and

Control

Applications

Integration

TBD 4.6.3.5

(e)Development of

Vehicle Fire

Control Emulator

TBD 4.6.3.6

(f) Submit

Graphical Human

Machine Interface

TBD 4.6.3.7

Deliver

Ammunition transportability

Report (CDRL

0051)

TBD

Supply Chain

CDRLS

overarching

4.6.6

Delivery of EDFP

(A037) TBD

4.7.3

Delivery of OMIT

Data (CDRL

A010)

TBD

4.7.4

Test & Soldier

Evaluation

Test Support

Services (Monthly) 4.8.1-4.8.10.6

MTC Soldier

Evaluation Support

(Monthly)

4.9-4.9.7

Training

Complete 1st

Operation and

Crew Level training

4.10.1

Complete 2nd

Operation and

Crew Level training

Complete 3rd

Crew Level training

Complete 4th

Crew Level

Training

Completion of 1st

Cannon/Breech/M uzzle Brake

Assembly training

4.10.2

Completion of 2nd

Cannon/Breech/M uzzle Brake

Assembly training

4.10.2

Completion of 1st

Operator and Field

Maintainer training

4.10.3

Completion of 2nd

Maintainer training

Completion of 3rd

Maintainer training

Complete 1st vehicle familiarization training event

4.10.4

Complete 2nd vehicle familiarization training event

4.10.4

Prototype

Production

Submit Production

Capability Plan TBD

Options

(Unfunded

Milestones)

Option 1:

Technical Data-

Key Interface Data

Option 2:

Technical Data -

Lightweight CAD

Model

TBD 4.7.5

Option 3:

Technical Data -

Target Subsystems

TBD 4.7.6

(a) Fire Control

(b) Cannon

Assembly

(c) Human-

Machine Interfaces

(d) Electrical

Power Generation

Storage and

Distribution

(e) Ammunition

Handling System

(f) Canon Mount and Reoil System

(g) Cannon

Pointing System

(h) Wheel and Tire

Assembly

(i) Armor

(j) Integrated Fire

Suppression

(k) Climate

Control Systems

3.2. Place of Performance

The list below (to be posted (TBP)) includes all places of performance. Any changes to the place of performance must be approved in writing by the Agreements Officer (AO). (DRAFT RELEASE NOTE:

primary places of performance will include Army testing facilities managed by US Army Test and

Evaluation Command (ATEC). A detailed list of locations will be included in final release but will include facilities listed on the ATEC website https://atec.army.mil/)

3.3. Period of Performance

Up to 48 months after date of award.

SECTION 4: STATEMENT OF WORK (SOW)

4.0. Background

4.0.1. Army formations require enhanced mobility, survivability, sustainability, maintainability, reliability and long-range lethal cannon artillery fires during Large Scale Combat Operations (LSCO).

4.0.2. To achieve this, the Army is seeking a Mobile Tactical Cannon (MTC) system to replace select artillery systems currently in use by the United States Army (U.S. Army). The initial focus is to replace the M777 towed howitzer in Stryker Brigade Combat Teams (SBCT), Infantry Brigade

Combat Teams (IBCT), and Mobile Brigade Combat Teams (MBCT) formations.

4.1. Near-Term Objectives (Within period of performance)

The following represents the U.S. Army’s objectives that are expected to be achieved while executing this

PPA with the Contractor. They do not reflect discrete scope for the Contractor.

4.1.1. Acquire systems and cannon assemblies to support the objectives below.

4.1.2. Execute preliminary U.S. Army familiarization and safety assessment at the Contractor facility and/or country of origin prior to the delivery of the MTC systems.

4.1.3. Ensure all material delivered is fully supported, such that each system is fully mission capable, throughout the characterization, test, and soldier evaluation efforts through use of Contractor

Logistics Support (CLS) and technical support from the manufacturer.

4.1.4. Train all required U.S. Army personnel and support Contractors for safe and effective use of the systems procured.

4.1.5. Assess the MTCs interoperability within the current and future U.S. fires network.

4.1.6. Conduct U.S. ammunition compatibility assessments.

4.1.7. Execute characterization, formal testing, and Soldier Evaluation events within the United States

(U.S.).

4.1.8. Achieve Interim Authority to Test (IATT).

4.1.9. Issue the MTC to U.S. Army artillery units for evaluation.

4.1.10. Identify recommended modifications (hardware/software) in support of long-term U.S. Army operations.

4.1.11. Transfer technical data and software to the U.S. Army to support the purposes stated herein.

4.1.12. Begin the transition of the MTC system’s supply chain, production and assembly to a facility or facilities located in the United States (“onshoring”) with onshoring complete within two (2) years of initial award of this contract.

4.2. Long-Term Objectives

4.2.1. The following represents the U.S. Army’s objectives that will follow the execution of this effort and which some PPA tasks support. They do not reflect discrete scope for the Contractor.

4.2.2. If success criteria are achieved, award a long-term production contract. *Note: Decision is predicated on Army Senior Leader (ASL) decisions, available funding, and Army requirements.

4.2.3. Make any modifications identified in the initial characterization, testing, and evaluations.

4.2.4. Production Verification Testing of the domestically produced MTC.

4.2.5. Achieve Authorization to Operate (ATO) as defined by DoD Instruction 8510.01, which requires the residual cybersecurity risk to be at or reduced to an acceptable level (no unmitigated high-risk items remain).

4.2.6. Obtain U.S. Army Material Release and field the systems to U.S. Army units.

4.3. Applicable Documents (TBP)

Document Title

Attachment 001 Contract Data Requirements Lists (CDRLs)

Attachment 002 Cyber Control Compliance Description

Attachment 003 Supply Chain Market Checklist

Attachment 004 Assertion of Restrictions

Attachment 005 As Built Configuration Template

Attachment 006 Indentured Bill of Materials (I-BOM) Sample

Attachment 007 Mobility Analysis Tool-Computer Edition (MATCE)

Input Datasheet Wheeled Vehicles

Attachment 008 Memorandum For Record – MIL-STD-6017 Initial

Integration for MTC (CUI)

Attachment 009 Proof Gun System Overview Distro A

Attachment 010 TDP Option Worksheet CAD

Attachment 011 TDP Option Worksheet

Attachment 012 MTC Test Schedule Breakdown

4.4. Hardware Requirements

4.4.1. The Contractor shall deliver six (6) prototype MTC systems with record showing the vehicle is fully mission capable within the system’s designed capabilities. Capabilities of delivered systems will match those capabilities bid in Proposal RPP XXXXX. These systems shall be delivered with modifications as identified in Sections 4.6 with the exception of first delivery. The first delivery shall have modifications incorporated as available or no later than 300 days after award.

{DRAFT RELEASE NOTE: The USG is interested in industry feedback regarding the feasibility of delivery of inga a prototype MTC within 60 days of contract award.}

4.4.2. Deliver up to 12 additional prototype MTC systems as option. These systems shall be delivered with modifications as identified in Sections 4.6.

4.4.3. The Contractor shall deliver up to four (4) system trainers. This requirement is dependent on whether the production vehicles include an integral training system. If they do not, then system trainers are desired. If there are integral training systems resident in production vehicles then system trainers are unnecessary. For the purpose of this effort, a system trainer is defined as a training device that replicates the system’s core operational functions, enabling a crew to achieve and sustain at least preliminary gunnery and crew drill qualification. Additionally, system trainers may also replicate up to deport-level maintenance of the system.

4.4.4. Deliver five (5) complete cannon assemblies (including tube/barrel, breech mechanism assembly, bore evacuator, and muzzle brake) modified for testing as directed at award, and any associated equipment to conduct ammunition compatibility testing utilizing a United States

Attachment 013 ATTLA Universal Data Sheet

Attachment 014 Petroleum Oils and Lubricants (POL) Guide

Attachment 015 Key Characteristics Description (Draft)

Attachment 016 MTC Sample Special License Agreement (SLA)

Attachment 017 US Army 155mm Artillery Ammunition Interfaces for Compatibility Evaluation (DRAFT)

AR 530-1 Operations Security (OPSEC)

AR 70-12 TBD

AR 750-1 Army Materiel Maintenance Policy

MIL-STD-6017 Variable Message Format (VMF)

Department of Defense Cyber Tabel Top Guide

Version 2.0, 16 Sept 2021

Test Schedule and Support Requirements

Government (USG) Proof Gun Stand (PGS).

{DRAFT RELEASE NOTE: The USG is interested in industry feedback regarding the feasibility of delivery of a Contractor designed live-fire gun stand within 120 days of contract award.}

4.4.5. The USG intends to maximize the use of US Ammunition that is compatible with the

Contractor’s system. If foreign optimized ammunition is necessary to meet USG objectives, the USG reserves the right to procure the following quantities of optimized foreign ammunition. All US

Ammunition will be provided by the U.S. Army.

4.4.6. Deliver conventional projectiles that are qualified for the MTC system. The projectile shall be of an unassisted, high explosive type. The U.S. Army’s equivalent would be the M795.

4.4.6.1. Increment 1: 1,000 projectiles

4.4.6.2. Increment 2: 2,000 projectiles

4.4.6.3. Increment 3: 2,000 projectiles

4.4.7. Deliver inert projectiles that are qualified for the MTC system. The projectile performance shall be sufficient to allow for payload, demonstration, experimentation, and training in non-combat environments. The U.S. Army’s equivalent would be the inert wax filled M795.

4.4.7.1. Increment 1: 500 projectiles

4.4.8. Deliver primers qualified for the MTC system that are compatible with the propelling charges.

4.4.8.1. Increment 1: 1,150 primers

4.4.8.2. Increment 2: 2,200 primers

4.4.8.3. Increment 3: 2,200 primers

4.4.9. Deliver propelling charges qualified for the MTC system. The propelling charges’ performance shall allow for the full range capability of the MTC armament.

4.4.9.1. Increment 1: 5,004 charge increments

4.4.9.2. Increment 2: 6,600 charge increments

4.4.9.3. Increment 3: 11,004 charge increments

4.4.10. The Contractor shall deliver hardware representing the vehicle's ammunition stowage interface, in a quantity sufficient for at least twenty (20) projectiles and twenty (20) charges, along with associated mounting equipment.

4.5. Program Management

4.5.1. Start of Work Meeting: The Contractor shall host a contract Start of Work Meeting (SOWM) with the government no later than 14 days after contract award. The start of work meeting should include the following topics for discussion: XX, YY, ZZ. The Contractor shall provide readaheads

(RAH) 2 days prior to the Start of Work Meeting and provide meeting minutes within 2 days after completion.

4.5.2. The Contractor shall maintain a program management team with technical SME support for the duration of the agreement. The Contractor shall provide presentation materials, meeting minutes, and action items as requested by the USG.

4.5.3. The Contractor shall develop, maintain, and submit a project schedule IAW CDRL A022.

4.5.4. The Contractor shall hold weekly programmatic meetings that will focus on cost, schedule, and programmatic risks and issues, with RAHs provided 24 hours in advance, and meeting minutes provided within 2 business days following. Examples topics for programmatic meetings are build/parts status, schedule, risk, onshoring progress, and test results.

4.5.5. The contactor shall hold weekly technical meetings that will focus on the technical aspects of the program, with RAH provided 24 hours in advance, and meeting minutes provided within 2 business days following. Example topics for technical meetings are technical briefings on the system, technical issues, technical risks/issues, software and/or cyber.

4.5.6. The Contractor will conduct a Program Management Review (PMR) twice yearly. The

Contractor shall report at a minimum current program schedules, onshoring status, integration and/or modification status, financial status, action items, risks, issues, and problem resolutions.

4.6. Integration and Technical Support

4.6.1. Technical Support

The Contractor shall provide access to subject matter experts and documentation as required for the purposes of addressing items related to safety, general vehicle operation, correction of vehicle deficiencies arising during test or evaluation, and planning of future US modifications.

4.6.2. Systems Engineering

4.6.2.1. System Design Review: The Contractor shall prepare and present a System Overview

IAW CDRL A001, and present at a one-time design review. The purpose of this design review is to achieve the following for the system in its design state at the time of the event: familiarize the

US Army with the system, verify both Contractor and US Army assumptions about performance/integration, provide the US Army with insight to enable future modifications for US

Army needs, and provide the US Army with understanding of previously completed verification and validation activities. This overview is intended to be analogous to a tailored Critical Design

Review. Execution of the System Overview must be completed no later than 60 days after award.

The System Overview must be completed CONUS with options for both in-person and virtual attendance. It is expected to be a multiple-day event, with RAHs provided five (5) business days before the event, and meeting minutes provided within 2 business days after completion. |

4.6.2.2. Key Interfaces: The Contractor shall support discussion and review of the information provided in Section 4.7.5 as requested by the USG. Further, the Contractor shall develop and deliver an Open Systems Management Plan (OSMP) IAW CDRL A001 – System Overview. The

OSMP shall contain details of the Contractor’s MOSA approach, including MOSA design, implementation, and documentation required to demonstrate MOSA benefits.

4.6.2.3. System Transportability: The Contractor shall prepare and deliver a Transportability

Report for the proposed system IAW CDRL A030 – Transportability Report.

4.6.2.4. Petroleum, Oils, and Lubricants: The Contractor shall prepare and deliver a report defining any Petroleum, Oils, and Lubricants (POL) used in the operation and maintenance of the proposed system, IAW CDRL A031, MTC Petroleum, Oils, and Lubricants List, conformance with AR 70-12 and Attachment 014, U.S. ARMY POL Products Guide for Ground Vehicle and

Equipment Materiel Systems.

4.6.2.5. System Performance Data: The Contractor shall complete the data fields in Attachment

007 – MATCE Input Datasheet Wheeled Vehicles and submit IAW CDRL A023 – Power and

Mobility Capabilities Report, in addition to requested system technical data regarding braking, fuel compatibility, volume, and consumption, self-recovery features, tire information, energy storage features, and key external system dimensions.

4.6.2.6. System and Force Protection: The Contractor shall prepare and deliver a report defining system and force protection capabilities of the proposed system, IAW CDRL A032 – Armor

Suitability Report.

4.6.2.7. Configuration Management and Standardization: The Contractor shall provide a detailed summary of their current Configuration Management processes, for both hardware and software, and explain how the system produced for this contract will be managed. The Contractor shall also provide a detailed summary of the Technical Data Package’s ability to meet International or

Industry standards.

4.6.2.7.1. Notification of System Variances: From the time of contract award, if the

Contractor finds it necessary to deviate from the proposed MTC configuration, the Contractor shall submit written documentation detailing the variance and discuss these variances during the weekly Technical Review meetings, see 4.5.

4.6.2.7.2. Variance Definitions

4.6.2.7.2.1. Critical. Critical variances are not allowed. A critical variance is a departure from proposed MTC configuration affecting one or more of the following: (1) Safety, (2)

Human health, (3) Environment, (4) Security (local program or national)

4.6.2.7.2.2. Major. A major variance is a departure from proposed MTC configuration affecting one or more of the following: (1) Performance or operational limits, (2)

Interchangeability, reliability, survivability, maintainability, or durability of the item or its repair parts, (3) Structural strength, (4) Effective use or operation, (5) Weight, moment, center of gravity, (6) Appearance, (7) Limits on product use or operation, (8) Temporary use of alternate items

4.6.2.7.2.3. Minor. A minor variance is a departure which does not involve any of the factors listed for critical or major.

4.6.2.7.3. Variances are for the benefit of the Contractor. Under no circumstances shall submission of submission of a Variance be the basis for a contract price increase.

4.6.2.7.4. Supporting Data: Variances shall contain marked up copies of affected drawings and 3D models as well as impact statements and any other supporting data necessary to fully understand the Variance.

4.6.2.7.5. Effectivity Certification: Variances incorporated into the proposed MTC configuration shall be applied to all vehicles delivered, with the Contractor assuming financial responsibility for all retrofit activities in their entirety. The change shall be annotated by the Contractor to reflect the anticipated effectivity point by product serial/registration number and date. The Contractor shall maintain the original effectivity point certification on file. Configuration updates resulting from Variances shall be incorporated as an update to the MTC As-Built Configuration IBOM in accordance with

CDRL A003 (IBOM) and shall be delivered to the government 14 days after Variance submittal.

4.6.2.8. Technical Review for Modifications: The Contractor will notify the USG of any changes to the technical baseline as provided by CDRL A004, Bill of Materials (BOM), delivered in section 4.6.6.1. The notification shall be provided as part of the Weekly Technical Review meeting presentation, and must include the driving requirements, impacts to the system, the technical solution, and an updated IBOM.

4.6.2.9. Failure Modes, Effects, Critical Analysis (FMECA): The Contractor shall provide the system level FMECAs (functional and design level) IAW CDRL A026. The purpose of this delivery is to allow for USG familiarization, test support, and preparation for future modification planning.

4.6.2.10. System thermal management data: The Contractor shall make available information regarding the architecture, physical behavior, and performance of all thermal management

(“Cooling”) systems on the vehicle to allow USG modeling and simulation as requested by the

USG. These include but are not limited to engine, transmission, electronics, climate control, and armament cooling systems.

4.6.2.11. Armament Performance Data: The Contractor shall make available information regarding the architecture, physical behavior, and performance of the 155mm armament and associated systems on the vehicle to allow modeling and simulation as requested by the USG.

These include, but are not limited to, interior ballistics, muzzle brake efficiency, gun mount stress capabilities, and recoil system performance, including recoiling mass, fluids, pressures, fluid-throttling profiles, thermal limits (fluid, seals, ability to compensate for fluid expansion), and embedded sensors.

4.6.2.12. Hazardous Materials Report: The Contractor shall prepare a report outlining use of the following materials at any point through the system lifecycle and identify any ongoing or proposed efforts to remove those materials from the system in accordance with CDRL A016.

Hazardous materials: The following are prohibited materials: asbestos, beryllium, Class I and

Class II Ozone Depleting Substances (ODS), hexavalent chromium, cadmium, mercury, lead, radioactive materials, and other Group 1 Agents classified as "carcinogenic to humans" by the

International Agency for Research on Cancer (IARC) Monographs. The following exceptions are allowed without prior approval from the Government:

4.6.2.12.1. Cadmium and hexavalent chromium on electrical connectors and back shells used to mate with cadmium electrical connectors on Government Furnished Equipment (GFE)

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

4.6.2.12.3. Lead-acid batteries

4.6.2.12.4. Lead in engine bearings

4.6.2.12.5. Leaded battery terminal adaptors/clamps

4.6.2.12.6. Steel containing up to 0.35 % lead by weight

4.6.2.12.7. Aluminum containing up to 0.4 % lead by weight

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

4.6.2.12.9. Beryllium and Beryllium alloys used in electrical components

4.6.2.12.10. Mercury containing components compliant with European Union (EU) Directive

2011/65/EC (RoHS2)

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

4.6.3. US Fire Control and Network Integration

4.6.3.1. The Contractor shall participate in a Network Interoperability working group meeting to convey status and collaborate with the USG throughout the period of performance.

4.6.3.2. Tactical Radios: The Contractor shall integrate Government Furnished Material (GFM) tactical radios systems, to be determined at contract award. The Contractor shall install/integrate all radios and demonstrate that they maintain the performance in accordance with USG defined test procedures. This task shall be completed prior to delivery of the second prototype.

4.6.3.3. Position/Navigation/Timing Device: The Contractor shall integrate the US Army’s

Modular Active Protection System (MAPS) Gen II system and modify their system such that it only uses this device for position and navigation data, exclusive of any Inertial Navigation Unit

(INU) integrated into the system as a baseline. The unit and antenna will be provided as GFM.

This task shall be completed prior to delivery of the second prototype.

4.6.3.4. Fire Mission Data Processing: The Contractor shall modify their system to receive and transmit fire mission data as defined in Attachment 008 MFR - MIL-STD-6017. This task shall be completed prior to delivery of the second prototype.

4.6.3.5. Command and Control Applications: The Contractor shall integrate a Command and

Control Applications, comprised of GFM software and hardware, to be identified at the time of award. For any software that needs to be developed in order toto facilitate this, the Contractor shall deliver a Software Development Plan IAW CDRL A009 – Software Development Plan.

This task shall be completed prior to delivery of the second prototype.

4.6.3.6. Vehicle Fire Control Emulator: The Contractor shall prepare a combination of hardware and software to allow the USG to conduct battalion level fire mission processing simulation. The emulator shall receive VMF 6017 messages, emulate the performance of the vehicle, and then transmit appropriate end-of-mission VMF messages, as described in Attachment 008 MFR - MIL-

STD-6017. The emulator will provide an accurate representation of user displays and system behaviors of the tactical fire control software for integration and verification testing. The

Contractor shall present evidence in the form of verification test results showing the emulator matches vehicle behavior and performance. This task shall be completed prior to delivery of the second prototype.

4.6.3.7. Ammunition Ballistics: The Contractor shall provide the data necessary to produce a ballistic kernel for US Army Fire Direction Center (FDC) computations IAW CDRL A002.

4.6.4. Cybersecurity Assessments

The purpose of the cybersecurity assessments is to allow the USG to validate the cyber survivability of the system and allow the system on US Army networks.

4.6.4.1. Software Bill of Materials: The Contractor shall provide a Software Bill of Materials

(SBOM) IAW CDRL A007 – Software Bill of Materials.

4.6.4.2. The Contractor shall provide software source code IAW CDRL A008 – Software Source

Code as required to perform a USG lead vulnerability assessment of the vehicle software and electronics using the Software Assurance Tool (SWAT). The Contractor shall provide vehicle access to support two separate Government led cyber penetration test events. As part of each of those events, the Contractor shall provide on-vehicle access to special connectors and subject matter expert support to answer questions and provide connectivity to electronic components and networks within the vehicle. This task shall be completed no later than 30 days after award.

4.6.4.3. The Contractor shall support cyber tabletop exercises as described by The Department of

Defense Cyber Tabel Top Guide Version 2.0, 16 Sept 2021 (https://ac.cto.mil/wp-content/uploads/2021/09/DoD-Cyber-Table-Top-Guide-v2.pdf)

4.6.4.4. The Contractor shall develop solutions that mitigate cybersecurity vulnerabilities through the period of performance.

4.6.4.5. The Contractor shall provide a Hardware/Software List that includes all system-level and application-level components (CDRL A028).

4.6.4.6. The Contractor shall identify and provide completed Security Technical Implementation

Guides (STIGs) for all applicable hardware, software, and electronic components utilized in the system. The Contractor shall document the system's compliance status against each applicable

STIG (CDRL A030 – Security Technical Implementation Guides). Evidence of compliance/non-compliance will be required during review/evaluation of STIG deliveries.

(https://www.cyber.mil/stigs/downloads).

4.6.5. Ammo Compatibility

4.6.5.1. Assessment of Compatibility: The Contractor will evaluate compatibility of U.S.

ammunition, as requested, and provide feedback as to the compatibility of that ammunition in the

Contractor system. Compatibility assessments should include, but are not limited to, assessments on the interior ballistics of the cannon-ammunition combination, considerations for the ammunition handling system, safety, and ammunition storage environment. The assessment shall also include potential PLATFORM/AMMUNITION solutions to any ammunition incompatibilities, to include scope and estimated cost and schedule. The Contractor shall participate in an Ammunition Compatibility working group meeting to convey findings and collaborate with the USG. The Contractor shall provide support to USG for required US

Ammunition Compatibility updates to Contractor system Fire Control software, Firing tables/Ballistic Kernels/Ballistic Library, and USG Battle Management System.

4.6.5.2. Cannons for Ammunition Assessments: The Contractor shall collaborate with the USG on the USG led integration of the delivered cannon/breech/muzzle brake assemblies into a USG

Proof Gun Stand (PGS) and shall be responsible for modification of the cannon for USG required instrumentation. An overview of the PGS is provided in Attachment A009. Instrumentation will be defined at the Start of Work meeting. (DRAFT RELEASE NOTE: for proposal purposes:

assume 3-5 pressure measurements locations throughout the assembly and 3 temperature measurement locations. Final details are dependent on subsystem design.) Alternately, if modifications cannot be completed by the Contractor, the Contractor shall make available all technical information required for the USG to make the modifications for instrumentation.

4.6.5.3. The Contractor shall assess integration of US Army fuze setter systems with the intent of enabling maximum system and US ammunition capability.

4.6.5.4. The Contractor shall prepare and deliver to the Government an Ammunition

Transportability Report IAW CDRL A036, Ammunition Transportability Report.

4.6.5.5. If non-US ammunition is purchased as an option, then the Contractor shall provide the following CDRLs. These CDRLs shall be provided no later than 30 days before the ammunition due date.

4.6.5.5.1. The Contractor shall prepare and deliver to the Government a Foreign Ammunition

Safety and Reliability Report IAW CDRL A034, Foreign Ammunition Safety and Reliability

Report.

4.6.5.5.2. The Contractor shall prepare and deliver to the Government a Foreign Ammunition

Design Maturity Report IAW CDRL A034.

4.6.5.5.3. The Contractor shall prepare and deliver to the Government a Foreign Ammunition

Performance Report IAW CDRL A035.

4.6.6. Supply Chain

For all subsections, the supply chain referenced is the current supply chain for the system as currently designed, before onshoring.

4.6.6.1. Indentured Bill of Materials (IBOM): The Contractor shall provide an IBOM IAW CDRL

A005. The data will be used by the Government to perform a Diminishing Manufacturing

Sources and Material Shortages (DMSMS) assessment and examination for items common to other US Army systems. The IBOM shall also identify components that contain “specialty metals” as defined by DFARS 225.7003. If no materials fitting this category exist in any of the platform components the Contractor shall furnish to the Government a declaration stating that no such materials exist within the configuration of the platforms being provided.

4.6.6.2. Supply Chain Supportability Assessment: The Contractor shall provide a Supply Chain

Risk Management (SCRM) Plan IAW CDRL A005. The purpose of receiving this plan is for the

USG to gain insight into the supply chain management of the system provided. This task shall be completed no later than 60 days after award.

4.6.6.3. Supply Availability Assessments: The Contractor shall provide support for Government

SME discussions to characterize how the Contractor supports their system with respect to spare repairable and consumable parts. The intent of this scope is to demonstrate to the Government how system sustainment can be accomplished.

4.6.6.4. The Contractor shall provide a completed Supply Chain Market Checklist (Attachment

003) to assess commonality with US Military, NATO supply systems, and Commercial off The

Shelf (COTS) parts.

4.7. Technical Data and Software

The USG will have the option to procure system technical data and software, in whole or in part, as requested within the below sections. All documentation shall be provided in the English language.

{DRAFT RELEASE NOTE: The request that follows is the USG’s preferred data deliverables and associated rights with purposes stated. The USG would appreciate feedback on the clarity of the proposed deliverables and the technical feasibility of their delivery.}

4.7.1. The Contractor shall maintain configuration control of the technical baseline but shall provide the Government access, insight, and approval authority for all modifications completed during the period of performance.

4.7.2. The Contractor shall collaborate with the Government on the Government’s adoption of a common digital environment to achieve the Government’s Digital Acquisition goals.

4.7.3. Engineering Data for Provisioning (EDFP): To ensure the comprehensive provisioning of the weapon system as delivered, enable the competitive procurement of future spare parts, and secure additional sources for consumable items, the Contractor shall provide Engineering Data for

Provisioning (EDFP). This data package must be adequate to allow the Government to identify, catalogue, and procure each individual part of the end item and to fully understand the relationship and assembly of all parts within the system. This requirement shall include all Commercial-Off-The-

Shelf (COTS) items, for which the Contractor shall furnish sufficient form, fit, and function data

(such as Vendor Item Control Drawings per ASME Y14.24), to support the identification of alternative sources. The Government shall be granted Unlimited Rights for all EDFP data. This data shall be delivered IAW CDRL A037.

4.7.4. Operation Maintenance Installation Training (OMIT): The Contractor shall provide comprehensive Operations, Maintenance, Installation, and Training (OMIT) data to allow the US

Army to organically conduct field and depot level maintenance, and to use the submitted technical data for any other Government programs. The Contractor shall provide all OMIT data with no less information or detail than industry standards, nor less than the Contractor typically requires, to perform such maintenance activities, and shall include any additional information necessary for the stated US Government purposes. Examples of OMIT data include, but are not limited to, Operator's and Maintenance Manuals, Repair Parts and Special Tools Lists (RPSTLs), Maintenance Allocation

Charts (MACs), troubleshooting guides, software installation guides, and all training materials. The

Government shall be granted Unlimited and Unrestricted Rights for all OMIT data and associated software. This data shall be delivered IAW CDRL A010.

4.7.5. Lightweight Computer-Aided Design (CAD) Model: The Contractor shall deliver lightweight

CAD model of each proposed vehicle design, as detailed in CDRL A011. This model is required for

Government use in the visualization of the system for administrative purposes, including presentations and program overviews, and to conduct Government-mandated analyses, such as transportability assessments with third-party Government teams. The model shall include, at a minimum, all exterior surfaces, interior crew and maintenance surfaces, and overall mass properties, and shall be structured to allow for the selection of individual components or assemblies as designated in the indentured Bill of Materials (BOM). The Government shall be granted a Special

Purpose License, equivalent to Government Purpose Rights, for all data delivered under this requirement; these rights shall not convert to Unlimited Rights.

4.7.6. Technical Data Packages for Targeted Subsystems: The Contractor shall provide a complete

Technical Data Package (TDP) containing all technical data, to include mechanical, electrical, communication, and software documentation information. The purpose of this data is to enable the

Government to procure, as well as modify, the targeted subsystems for sustainment and experimentation purposes without the need for additional development or reverse engineering. To achieve these objectives, the Government shall receive a Special Negotiated License for the purposes stated herein. This Technical Data Package shall be delivered in accordance with CDRL A006

[Product Level TDP]. The TDP shall include the following subsystems:

4.7.6.1. Fire Control system, defined as all hardware, software and firmware that is required to receive an offboard fire command and translate that command into pointing, loading, and firing of the cannon.

4.7.6.2. Cannon Assembly, defined as the recoiling mass of the main cannon artillery armament, and any associated consumable components of the breech, including but not limited to tube/barrel, breech mechanism assembly, bore evacuator assembly, and muzzle brake, sealing rings, obturator pads, etc. depending on design.

4.7.6.3. Human-Machine Interfaces for all armament related functions, defined as any component, software element, or subsystem which is directly interfaced by the operating soldier during normal vehicle operations.

4.7.6.4. Electrical Power Generation, Storage, and Distribution System, defined as all components or subsystems involved in the generation, storage, or distribution of electrical power from the vehicle’s main energy conversion source (e.g. diesel engine) to the point of final electrical power conversion or consumption.

4.7.6.5. Ammunition Handling System, defined as all components or subsystems onboard the system that prepare, store, move, or load any element of artillery ammunition (i.e. fuzes, propelling charges, projectiles, and primers).

4.7.6.6. Cannon Mount and Recoil System, defined as all components or subsystems that constrain the cannon assembly to the turret, cab, or chassis (as applicable) and provide resistance and damping forces between the cannon assembly and structure.

4.7.6.7. Cannon Pointing System, defined as all components or subsystems required to traverse or elevate the cannon to the desired aim location, exclusive of chassis, cab, or turret structural features.

4.7.6.8. Wheel and Tire Assembly, defined as the rotating mass which spins the tire and interfaces to the vehicle driveline, hub, or axle.

4.7.6.9. Armor, defined as all pieces of the system which provide protection of the crew or system against kinetic threats.

4.7.6.10. Integrated Fire Suppression System, defined as all systems and components associated with the extinguishing, mitigating, and prevention of fires on or within the vehicle during operation.

4.7.6.11. Climate Control Systems, defined as any heating, ventilation, or cooling system components or subsystems involved in the control of the temperature, air quality, and humidity of any enclosed volume on the system.

4.7.7. The Contractor shall provide a complete software package, to include all source code, build scripts, operating systems, and associated documentation, which can be verifiably compiled in a

Government designated software development environment and made ready for deployment on the system. The purpose of this deliverable is to enable the Government to modify or maintain the targeted subsystems for sustainment and experimentation purposes without the need for additional development or reverse engineering. To achieve these objectives, the Government shall be granted a

Special Negotiated License for the purposes stated herein. This software package shall be delivered in accordance with CDRL A008 – Software Source Code, to include an update applicable to this delivery to CDRL A007 – Software Bill of Materials. The software package shall address the software components of the following subsystems:

4.7.7.1. Fire Control system, defined as all hardware, software and firmware that is required to receive an offboard fire command and translate that command into pointing, loading, and firing of the cannon.

4.7.7.2. Human-Machine Interfaces for all armament related functions, defined as any component, software element, or subsystem which is directly interfaced by the operating soldier during normal vehicle operations.

4.7.7.3. Electrical Power Generation, Storage, and Distribution System, defined as all components or subsystems involved in the generation, storage, or distribution of electrical power from the vehicle’s main energy conversion source (e.g. diesel engine) to the point of final electrical power conversion or consumption.

4.7.7.4. Ammunition Handling System, defined as all components or subsystems onboard the system that prepare, store, move, or load any element of artillery ammunition (i.e. fuzes, propelling charges, projectiles, and primers).

4.7.7.5. Cannon Pointing System, defined as all components or subsystems required to traverse or elevate the cannon to the desired aim location, exclusive of chassis, cab, or turret structural features.

4.7.7.6. Climate Control Systems, defined as any heating, ventilation, or cooling system components or subsystems involved in the control of the temperature, air quality, and humidity of any enclosed volume on the system.

4.7.8. The Contractor shall deliver a technical data package for the vehicle's ammunition stowage interfaces. The purpose of these deliverables is to enable U.S. Government (USG) led shock, vibration, and live-fire testing at Government test facilities to validate system integration and performance. To facilitate this testing and future integration efforts, the Government shall be granted a Special Negotiated License for the delivered technical data package. All data shall be delivered in accordance with CDRL A036 – Ammunition Transportability report. The specific deliverables shall be of the same design as the delivered system and the resupply system, if applicable.

4.8. Test

4.8.1. The Contractor shall provide a Bill of Materials (BOM) IAW CDRL A004 with each vehicle delivered which represents the configuration of the vehicle delivered for test.

4.8.2. The Contractor shall support Government testing and evaluation of the MTCs. For planning purposes, the Contractor shall assume: the evaluation will begin with delivery of the first prototype as outlined in section 3.1 and consist of scope and schedule of events in Attachment 012 Test Schedule

Breakdown. The USG will provide facilities at the test sites for secured storage, required daily maintenance, and required intermediate maintenance for the system. The USG will be present during all maintenance activities. The USG will provide test ranges, and common USG consumable items such as fuel (JP-8/F-24) and nitrogen. The USG will provide personnel for operation of the vehicle after completing training as specified in Section 4.1.

4.8.3. The Contractor shall provide and manage the System Support Package (SSP) (e.g.: Special

Tools, Test/Diagnostic Equipment, Maintenance Significant Components, spare parts and consumption items) to maintain, recover, and keep the MTC in a state of operational readiness during the duration of the testing. The Contractor is responsible for managing the inventory of the SSP, including ordering additional spares, delivery, and return parts to the SSP. The Contractor is responsible for managing the transportation of their SSP to and from the test site and/or CONUS soldier evaluation sites.

4.8.4. The Contractor shall be responsible for supporting vehicle operations, maintenance, repair and parts supply, inspection, testing, installation, calibration, troubleshooting and repair to make equipment fully operational. Additionally, the Contractor shall conduct on site field testing and provide technical guidance to test site test personnel. The Contractor shall identify technical problems and take initiative to resolve issues immediately.