MTC OTA Prototype Project Agreement AMD 02.docx

DRAFT

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)

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

PEO GSC OPSEC#: OPSEC-2026-275

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. 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 and execution of operationally relevant fire missions, inclusive of performance, reliability, and operational value.

2.1.2. 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.3. 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.4. Demonstrate a viable path to US Army 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.1.5. In accordance with the statutory discretion regarding the use of competitive procedures to award a follow-on production effort, if multiple prototype solutions are determined to be successful, the Government reserves the right to either pursue a production effort with only one successful contractor, or to solicit proposals from successful contractors for the purpose of selecting an awardee(s) for a follow-on production contract or transaction.

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 be paid a fixed amount for each milestone accomplished in accordance with the tables below. The Contractor shall invoice against the following Milestone Payment Schedules. The Milestone Payment Schedules are effective from the day of agreement execution. The Contractor shall submit invoices for payment in accordance with the Milestone Payment Schedules 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. For table A, delivery after award (days) for Contract Base Milestones are set as days from initial award of the OTA. Delivery after award (days) for Unfunded Milestones (UM) are set as days after the milestone is funded.

3.1. The Contractor shall deliver the prototype hardware identified in section 4.0 in accordance with the tables below. UMs in Table A that are funded on a single amendment will stagger deliveries by 30 days between UMs. The Contractor shall deliver CDRLs A004 and A021, in accordance with paragraph 4.11.5 with each vehicle delivery, to receive payment.

Table A: Prototype MTC system delivery

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

Table C: Ammunition storage cells for Sequential Environmental Testing

Table D: Training System

Table E: Test Ammunition – OPTION

Table F: Service Payment Schedule

System Engineering

Fire Control and Network Integration

Supply Chain

Test & Soldier Evaluation

Training

Prototype Production

Options (Unfunded Milestones)

(a) Fire Control System

(b) Cannon Assembly

(c) Human-Machine Interfaces

(d) Electrical Power Generation Storage and Distribution System

(e) Ammunition Handling System

(f) Cannon Mount and Reoil System

(g) Cannon Pointing System

(h) Wheel and Tire Assembly

(i) Armor

(j) Integrated Fire Suppression System

(k) Climate Control Systems

(a) Fire Control System

(b) Human-Machine Interfaces

(c) Electrical Power Generation, Storage, and Distribution System

(d) Ammunition Handling System

(e) Cannon Pointing System

(f) Climate Control Systems

3.2. Place of Performance

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

3.2.1. Contractor CONUS Location(s) – Vendor Fill In

3.2.2. Contractor OCONUS Location(s) – Vendor Fill In

3.2.3. USG Primary Test Location – See Attachment 021 MFR - Planned Locations for Performance

3.2.4. USG Alternate Test Location – See Attachment 021 MFR - Planned Locations for Performance

3.2.5. USG Soldier Evaluation – See Attachment 021 MFR - Planned Locations for Performance

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 select 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 integration.

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. Obtain delivery of technical data and software to the U.S. Army, with sufficient license rights, 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 agreement to support domestic production in the Follow-On.

4.1.13. Establish Options for the Government to acquire certain technical data and computer software and license rights to enable future Government objectives, such as sustainment of an MTC system selected for follow-on production.

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.1.1. 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.1.2. Make any modifications identified in the initial characterization, testing, and evaluations.

4.2.1.3. Production Verification Testing of the domestically produced MTC.

4.2.1.4. 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.1.5. Obtain U.S. Army Material Release and field the systems to U.S. Army units.

4.3. Applicable Documents

4.4. Hardware Requirements

4.4.1. The Contractor shall deliver six (6) prototype MTC systems. Capabilities of delivered systems will match those capabilities bid in Proposal RPP W912CH26RA017. These systems shall be delivered with modifications as identified in Section 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.

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 vehicle includes an integral or embedded training system. If the system does not include an integral or embedded training system, then system trainers are required. If there are integral or embedded training systems resident in production vehicles, then system trainers are unnecessary. For 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.

4.4.4. Deliver five (5) complete cannon assemblies (including tube/barrel, breech mechanism assembly, bore evacuator, and muzzle brake), modified for testing with up to 5 pressure measurement locations and up to 2 temperature measurement locations based on proposed cannon assembly design to be clarified at the Start of Work Meeting, and any associated equipment to conduct ammunition compatibility testing utilizing a United States Government (USG) Proof Gun Stand (PGS).

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 quantities of optimized foreign ammunition identified in sections 4.4.6-4.4.9. In the event foreign ammunition is required, the contractor is solely responsible for importing that foreign ammunition into the U.S., including full compliance with all foreign and U.S. import and export control laws. 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 (as defined in Table C: Ammunition storage cells), in a quantity sufficient for at least twenty (20) projectiles and twenty (20) full propelling charges, along with associated mounting equipment. The USG intends to use the provided hardware for system level simulation of the shock and vibration environment that the ammunition will experience while the MTC is performing its missions. This does not require any automation and/or robotics but does require the cells to transfer the laboratory induced shock and vibration to the ammunition.

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 topics provided by USG upon contract award. 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 an Integrated Master Schedule (IMS) IAW CDRL A019.

4.5.4. The Contractor shall hold weekly programmatic meetings that will focus on cost, schedule, and programmatic risks and issues, with Read Ahead (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 shall 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, software/cyber status, financial status, action items, risks, issues, and problem resolutions.

4.5.7. The contractor shall deliver a Data Accessions List (DAL) IAW CDRL A033

4.5.8. The contractor shall support USG development of a Total Cost of Ownership assessment.

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 deliver a System Overview IAW CDRL A001 and present the overview 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 90 days after contract 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 seven (7) business days before the event, and meeting minutes provided within 2 business days after completion. |

4.6.2.2. Systems Engineering Model Development: The contractor shall provide an overview of the contractor’s existing systems engineering and digital engineering capabilities with focus on how these capabilities are implemented on the system offered and the artifacts that currently exist for the system. The contractor shall also collaborate with the USG on incorporation of existing content/methodologies and deliverables within this contract into the USG’s emerging digital acquisition strategy.

4.6.2.3. Key Interfaces: The Contractor shall support discussion and review of the information provided in Section 4.8.1 as requested by the USG.

4.6.2.4. System Transportability: The Contractor shall prepare and deliver a Transportability Report for the proposed system IAW CDRL A024 – Transportability Report. This report shall include Attachment 013 ATTLA Universal Data Sheet as described in CDRL A024.

4.6.2.5. Petroleum, Oils, and Lubricants: The Contractor shall prepare and deliver a report defining any Petroleum, Oils, and Lubricants (POLs) used in the operation and maintenance of the proposed system, IAW CDRL A025 - Petroleum, Oils, and Lubricants List.

4.6.2.6. System Performance Data: The Contractor shall prepare and deliver a report defining the system mobility and power capabilities IAW CDRL A020 – Power and Mobility Capabilities Report. This report shall include Attachment 007 Mobility Analysis Tool-Computer Edition (MATCE) as described in CDRL A020.

4.6.2.7. System and Force Protection: The Contractor shall prepare and deliver a report defining system and force protection capabilities of the system IAW CDRL A026 – Armor Suitability Report.

4.6.2.8. Configuration Management and Standardization: The Contractor shall provide a briefing and support a discussion detailing their current Configuration Management processes, for both hardware and software, explaining 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. The Contractor shall provide RAHs 24 hours in advance, and meeting minutes provided within 2 business days following.

4.6.2.8.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.8.2. Variance Definitions

4.6.2.8.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.8.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.8.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.8.3. Variances are for the benefit of the Contractor. Under no circumstances shall submission of a Variance be the basis for a contract price increase.

4.6.2.8.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. All Requests for Variance shall be submitted in accordance with CDRL A042 – Request for Variance Supporting Data.

4.6.2.8.5. Effectivity Certification: Variances incorporated into the proposed MTC configuration 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. The Contractor shall assume financial responsibility for all retrofit activities in their entirety. Configuration updates resulting from Variances shall be incorporated as an update to the MTC IBOM in accordance with CDRL A003 - IBOM.

4.6.2.8.6. Configuration Change Notification: The Contractor will notify the USG of any changes to the technical baseline as provided by CDRL A003 - IBOM, 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. Technical Reviews for Modifications: The contractor shall prepare a technical review for all modifications made to the system to accommodate changes requested by the USG or resulting from USG needs in accordance with CDRL A043 – Configuration Change Design Review. The format and cadence of the review or reviews shall be at the discretion of the Contractor, so long as it addresses the purposes stated here. The purpose of the review is to capture the essential systems engineering activities to review the design requirements, interfaces, preliminary design, and final design prior to fabrication or prototype integration. The technical review must be completed prior to implementation of modifications into the prototype vehicles. Entry requirements for the technical reviews shall include a description of which requirements and/or vehicle capabilities are affected, impacts on producibility, impact on cyber security, impact on system safety, and changes to form, fit, or function of modified configuration item. The only exit criteria is that the USG must agree that the technical solution is adequate to address the USG needs.

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

4.6.2.11. System thermal management data: The Contractor shall provide access to 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 temperature monitoring and cooling systems.

4.6.2.12. Armament Performance Data: The Contractor shall make provide access to 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.13. Hazardous Materials Report: The Contractor shall prepare and deliver 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 A013 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.13.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.13.2. Products listed under "Priming" and "Topcoating" in MIL-DTL-53072, Table I

4.6.2.13.3. Lead-acid batteries

4.6.2.13.4. Lead in engine bearings

4.6.2.13.5. Leaded battery terminal adaptors/clamps

4.6.2.13.6. Steel containing up to 0.35 % lead by weight

4.6.2.13.7. Aluminum containing up to 0.4 % lead by weight

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

4.6.2.13.9. Beryllium and Beryllium alloys used in electrical components

4.6.2.13.10. Mercury containing components compliant with European Union (EU) Directive 2011/65/EC (RoHS2)

4.6.2.13.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. For any software that needs to be developed in order to facilitate the scope herein, the Contractor shall deliver a Software Development Plan IAW CDRL A008 – Software Development Plan.

4.6.3.2. Tactical Radios: The Contractor shall integrate Government Furnished Equipment (GFE) 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 Mounted Assured Positioning, Navigation and Timing System (MAPS) Gen II system and modify their system such that it only uses this device and it’s y-code output for position and navigation data, exclusive of any Inertial Navigation Unit (INU) integrated into the system as a baseline. The Contractor shall prepare a plan for integration of the m-code implementation of the MAPS Gen II. The unit and antenna will be provided as GFE. 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 and Attachment 022 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 system, comprised of Government furnished software and hardware, to be clarified at the time of award. This task shall be completed prior to delivery of the second prototype.

4.6.3.6. Vehicle Fire Control Emulator: The Contractor shall prepare and provide access to the USG a combination of hardware and software to allow the USG to conduct battalion level (18 systems) 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 integrated on the vehicle in task 4.6.3.4. 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 provide access to and present evidence in the form of verification test results showing the emulator matches vehicle behavior and performance. This task shall be completed no later than 30 prior to delivery of the prototype MTC vehicle number 2.

4.6.3.7. Graphical Human Machine Interface (HMI) Adjustments: The contractor shall provide a graphical HMI in English. This task shall be completed prior to delivery of the second prototype.

4.6.3.8. 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 to achieve an Interim Authority to Test.

4.6.4.1. Software Bill of Materials: The Contractor shall prepare and deliver a Software Bill of Materials (SBOM) IAW CDRL A006 – Software Bill of Materials.

4.6.4.2. The Contractor shall deliver the system software source code with access rights for the purpose of the USG conducting a 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. The first vulnerability assessment will take place no later than 30 days after delivery of the first MTC prototype.

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 Cyber RMF Artifacts IAW CDRL A031. This shall include Contractor executed scans of vehicle software and electronics using the Assured Compliance Assessment Solution (ACAS) scanner.

4.6.5. U.S. Ammunition Integration

4.6.5.1. Assessment of Compatibility: The Contractor will evaluate compatibility of U.S. fielded and developmental 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 and/or ammunition solutions to any ammunition incompatibilities, to include scope and estimated cost and schedule. The Contractor shall participate in working group meeting focused on ammunition compatibility to convey findings and collaborate with the USG.

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 009. Instrumentation will be defined at the Start of Work meeting.

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 Interfaces Report IAW CDRL A028 – US Ammunition Interfaces Report. 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 seeks a Special Negotiated License for the delivered technical data package. The specific deliverables shall be of the same design as the delivered system and the resupply system, if applicable.

4.6.5.5. If non-US ammunition is purchased as an option, then the Contractor shall prepare and deliver to the Government a Foreign Ammunition Safety and Reliability Report IAW CDRL A027 - Foreign Ammunition Safety and Reliability Report no later than 30 days before the ammunition due date.

4.6.6. Supply Chain

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

4.6.6.1. Indentured Bill of Materials (IBOM): The Contractor shall provide an IBOM IAW CDRL A003. 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. The Contractor shall provide SME support for discussions to characterize how the Contractor conducts supply chain risk management.

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. Any report provided by the contractor shall be IAW CDRL A032 - Availability Assessment.

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. The completed checklist shall be delivered IAW CDRL A034 - Supply Chain Market Checklist.

4.7. Technical Data and Computer Software Base Requirements

The Contractor shall prepare and deliver the following system technical data and software as requested within the below sections. All documentation shall be provided in the English language.

4.7.1. Engineering Data for Provisioning (EDFP): The contractor shall prepare and deliver EDFP for the comprehensive weapon system IAW CDRL A029. The EDFP 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 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. EDFP containing only form, fit, and function data shall be delivered to the Government with Unlimited or Unrestricted Rights.

4.7.2. Data Necessary for Operation, Maintenance, Installation, and 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. This data shall be delivered IAW CDRL A009.

4.8. Technical Data and Computer Software Options

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. Upon determination of exercise of an option, the AO will notify the Contractor of the Government’s desire to exercise the option. Thereafter, the Government and the Contractor shall determine a mutually agreeable time and duration to examine the technical data and/or computer software to be delivered under the proposed exercised option. The Government shall have sole discretion on exercising the option.

4.8.1. Modular System Interfaces: To establish a Modular, Open System Approach (MOSA) foundation that enables rapid modernization and allows for competitive or Government-led modification for experimentation, the Government requires detailed architectural and interface data. The Contractor shall deliver comprehensive systems engineering information that defines the system's functional and physical architecture. This includes detailed descriptions of interfaces between all major system components. Major system components of interest include, if applicable to the system: the Cannon/breech/muzzle brake; Gun Mount and Recoil System; Fire Control; Position Navigation and Timing (PNT); Human-Machine-Interfaces; Cannon Pointing Systems; Ammunition handling systems; Automated diagnostics systems; Cameras or other situational awareness systems; Data networks internal to the vehicle (Ethernet networks, Controller Area Networks (CAN), etc.); Wheel Assemblies; Powertrain; Armor Kits; Towing/Tie-Down/Recovery Interfaces; Electrical Power Distribution; and any Secondary Weapon System. The Government is seeking specifically negotiated license rights, with mutually beneficial terms, for the data delivered under CDRL A022 – Interface Control Document to enable the Government to use that data internally without restriction and to release that data outside the Government for another contractor to use for future modification and upgrades (e.g., Government-purpose-like rights with an extended protection period, etc.). These modular system interfaces shall be delivered IAW CDRL A022 – Interface Control Document.

4.8.2. Lightweight Computer-Aided Design (CAD) Model: The Contractor shall deliver lightweight CAD model of the system, as detailed in CDRL A010 and Attachment 010 “TDP Option Worksheet CAD”. 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 allow for review of 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.8.3. 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.