ATCH_1_CAML_Lite_SOO_15Oct26.pdf

CAML-Lite SOO (Attachment 1 to RFSB) | Page 1 of 14

STATEMENT OF OBJECTIVES (SOO)

Common Autonomous Multi-Domain Launcher (CAML)-Lite Prototype Effort Reference: Attachment 1 to Request for Solutions Brief (RFSB), 15 October 2026 Anticipated Request for Prototype Proposal (RFPP)-Following RFSB Evaluation and Selection Following evaluation, the Government intends to issue an RFPP to selected respondents requesting:

• Phase 1: Prototype Demonstration at Talisman Sabre 2027 (TS-27), with a priced Phase 1 Prototype Acquisition Option for additional prototype units, New Equipment Training (NET), and Contractor Logistics Support (CLS). Proposals due 20 November 2026.

• Phase 2: Prototype Maturation and Common Architecture Integration, with NET and CLS if required. Proposals due as established in the applicable solicitation or request for proposal.

1. PURPOSE

SOO Purpose: This Statement of Objectives (SOO) defines the Government's desired outcomes for the CAML-Lite Prototype Effort: industry demonstration of best available solutions at TS-27;

Government acquisition of selected prototypes for operational experimentation and Soldier feedback; and maturation toward a common CAML architecture.

CAML is a modular launcher platform intended to deliver cross-domain offensive and defensive fires through a system-of-systems Modular Open Systems Approach (MOSA). Autonomous operations increase operational flexibility, mobility, and survivability. Common interfaces and interchangeable modules enable integration of multiple munition families while reducing logistics and training burdens and supporting competition throughout the system's life cycle.

CAML-Lite is a mobile, autonomous launcher capability within the CAML family, intended to support worldwide deployment and cross-domain fires. Its desired capabilities include autonomous munition resupply with minimal human intervention, operations across varied terrain and weather conditions, and integration of current and future munitions and mission systems through modular, open interfaces.

Each Performer shall develop a Statement of Work (SOW) describing the tasks, methods, deliverables, schedule, and verification approach proposed to achieve the objectives applicable to its effort. Following Government review and negotiation, the agreed SOW will be incorporated into the Other Transaction Agreement (OTA) as an attachment. Performers shall use the RFSB and RFPP when preparing their proposed SOW.

2. PROGRAM STRUCTURE

The CAML-Lite prototype effort has two phases. Phase 1 consists of the Phase 1 Demonstration, in which each selected Performer provides one (1) or more complete prototype systems for a Government-sponsored demonstration at TS-27 in August 2027; and the Phase 1 Prototype Acquisition Option, a priced option included in each OTA at award to acquire additional prototype units, with NET and CLS, for Government testing and Soldier experimentation, CAML-Lite SOO (Attachment 1 to RFSB) | Page 2 of 14 including experimentation with the 25th Infantry Division (25th ID). Phase 2 matures selected solutions toward a production-representative configuration and the common CAML architecture.

All Phase 1 systems, including the demonstration system and any units acquired under the option, are prototypes intended to support learning, testing, and experimentation by the U.S.

Government and its international partners. The Government does not expect these systems to be production or production representative systems.

A draft SOW is not required with the Solutions Brief. Each Performer shall submit a draft Phase 1 SOW with its RFPP proposal, separately identifying the demonstration effort and each Phase 1 Prototype Acquisition Option component: additional prototype units, NET, and CLS. Each effort shall identify its scope, deliverables, schedule, configuration, acceptance criteria, assumptions, and dependencies. A Phase 2 SOW shall be submitted separately when requested by the Government.

Phase / Option / Pricing Period of Performance Ends With Phase 1 Demonstration Firm-fixed-price, with two fixed price payments

OTA award through completion of the Government-sponsored demonstration

Government acceptance of demonstration results, required artifacts, and documented system configuration

Phase 1 Option: Additional Prototype Units Firm-fixed-price, tiered unit pricing for one (1) through six

(6) units

Option exercise through delivery and Government acceptance, consistent with the delivery lead times in the OTA

Delivery and acceptance of the ordered units

Phase 1 Option: NET Firm-fixed-price per training iteration

As established at exercise to support Government training needs

Completion of NET for Government operators and maintainers

Phase 1 Option: CLS Price per period of support, by number of supported units

As established at exercise to support Government testing and experimentation

Completion of the exercised support period and acceptance of logistics, maintenance, and readiness deliverables

Phase 2 Prototype Maturation Agreement type established in the applicable solicitation

Award or option exercise through final delivery and Government acceptance

Delivery and acceptance of the negotiated quantity of mature prototypes, technical baseline, and verification evidence

Phase 1 Demonstration and Payment The initial award shall support the Performer's provision of its best available solution for TS-27, including the complete demonstration system and the documentation, transportation, checkout, and contractor support required to execute the approved demonstration. If a capability cannot be demonstrated at TS-27 because of security classification, release or export restrictions, host-nation requirements, range limitations, or other reasons acceptable to the Government. The respondent shall identify the affected capability, the reason, and the proposed location and date.

The Government approved alternative demonstration shall be completed no later than 30

CAML-Lite SOO (Attachment 1 to RFSB) | Page 3 of 14

September 2027. The Government will determine whether to approve the alternative; approved alternatives will be established in the OTA.

The Government’s agreed share of the demonstration effort shall be funded at initial award and paid in two installments: an initial payment at award and a final payment upon Government acceptance of the required demonstration deliverables. The negotiated OTA shall establish the amount and conditions of each payment, including required evidence and applicable Performer investment verification. The draft Phase 1 SOW submitted with the RFPP proposal shall identify the proposed outcomes and deliverables supporting the final payment.

The demonstration system remains the property of the Performer and is provided for contractor-supported demonstration activities. Government purchase and formal acceptance of that system are not included unless expressly identified in the negotiated OTA. Completion of the demonstration does not constitute transfer of ownership or acceptance of the system for Government operation. The Performer may propose use of its demonstration system, by loan or bailment, to accelerate NET or experimentation.

Performer Investment The Government has limited funding for the Phase 1 demonstration and does not intend to fund its full cost. Performer investment is required for the demonstration effort.

The draft Phase 1 SOW submitted with the RFPP proposal shall separately identify the Government-funded and Performer-funded demonstration activities; the amount, source, and timing of proposed Performer investment; and its relationship to demonstration tasks and payments. It shall describe the proposed investment reporting and verification approach, including expenditure documentation supporting payment requests. Any voluntary contributions to the Phase 1 Prototype Acquisition Option shall be separately identified.

Investment eligibility shall be governed by the RFSB and negotiated OTA. The negotiated SOW and OTA shall establish the final investment commitments, reporting requirements, verification procedures, and payment conditions. Performer investment in Phase 2 may be proposed when requested but is not required.

Phase 1 Prototype Acquisition Option The draft Phase 1 SOW submitted with the RFPP proposal shall separately address additional prototype units, NET, and CLS consistent with the quantities and planning assumptions established in the RFPP. For additional prototype units, it shall identify the proposed configuration baseline, configuration controls, required support equipment, acceptance testing, warranty terms, and documentation accompanying each unit.

The draft Phase 1 SOW shall identify delivery lead times measured from option exercise, including the lead time to the first unit, delivery intervals for subsequent units, and the time required to deliver the full ordered quantity. It shall describe the process for incorporating Government-approved configuration changes, including changes resulting from the demonstration if the option is exercised before TS-27.

Purchased prototypes shall conform to the configuration baseline established in the negotiated agreement, except for Government-approved changes. Each delivered unit shall include the configuration records, support equipment, and acceptance evidence required by the negotiated

SOW.

CAML-Lite SOO (Attachment 1 to RFSB) | Page 4 of 14

Phase 1 NET and CLS Components The draft Phase 1 SOW shall separately identify the NET and CLS scope, supported quantities and configurations, locations, schedules, Government support dependencies, and deliverables. It shall use the RFPP planning assumptions and identify any deviations and their effects on execution.

NET shall prepare Government operators and maintainers for the authorized testing and experimentation activities. CLS shall provide the support necessary to sustain the prototypes throughout the agreed support period. The draft Phase 1 SOW shall identify whether each activity will be contractor-operated, Government-operated, or conducted with combined support.

Government personnel may operate purchased or loaned prototypes only after completing applicable training and satisfying the safety, cybersecurity, and other approvals required for the intended activity.

CLS deliverables shall include a CLS Plan, recommended spares list, maintenance and readiness reports, and logistics data supporting Government sustainment planning. NET deliverables shall include a NET Plan, programs of instruction, training materials, and course completion records.

Training materials are OMIT data subject to Section 3.4.

Phase 1 Option Completion Completion of each exercised option component shall be based on its negotiated requirements and acceptance criteria. Prototype acquisition requires delivery and Government acceptance of the ordered units and accompanying deliverables. NET and CLS require completion and acceptance of their respective agreed scope and deliverables. Unexercised option components do not create performance obligations.

Phase 2 Prototype Maturation Approach Phase 2 will mature selected solutions through design, development, integration, testing, and delivery of production-representative prototypes, informed by demonstration results, Soldier experimentation, and Government requirements.

When separately requested, the draft Phase 2 SOW shall identify the proposed capability baseline, design improvements, common architecture integration approach, verification strategy, delivery schedule, and supporting assumptions. Phase 2 shall begin with a findings and requirements review establishing the agreed development baseline. The negotiated SOW shall establish configuration and change-control processes.

Phase 2 deliverables shall include a technical data package supporting the matured design, with data rights established in the applicable agreement sufficient to support future competition of the system or its modules.

3. MODULAR OPEN SYSTEMS APPROACH (MOSA) OBJECTIVES

The Performer's SOW shall describe how its technical approach, architecture, and deliverables will support the Government's MOSA objectives throughout Phase 1 and Phase 2. Phase 1 shall document the available solution and identify limitations; Phase 2 shall address maturation toward the required modular architecture and common CAML interfaces. The SOW shall define the tasks and methods for achieving the following objectives.

CAML-Lite SOO (Attachment 1 to RFSB) | Page 5 of 14

3.1 Architecture Severability

The Performer shall design the solution such that individual modules, including the mobility platform, autonomy system, launcher, and resupply subsystem, can be isolated, removed, replaced, or upgraded independently without adversely affecting the functionality of unrelated system elements. For Phase 1, the SOW shall identify existing module boundaries and any limitations on independent replacement or upgrade. For Phase 2, the SOW shall describe how the Performer will establish, refine, and document module boundaries as the design matures.

3.2 Open Interfaces

All external interfaces and major subcomponent interfaces shall use non-proprietary or Government-controlled mechanical, electrical, power, data, and software interfaces. For Phase 1, the Performer shall identify any exceptions in its available solution and describe the proposed path to meeting this objective in Phase 2. The SOW shall describe the Performer's approach to interface standardization and the process by which Interface Control Documents (ICDs) and Interface Design Descriptions (IDDs) will be developed, maintained, and delivered, including interfaces with the CAML architecture.

Phase 1 deliverables shall include electrical, mechanical, and logical (software/firmware) interface documentation reflecting the demonstrated configuration, updated to reflect any Government-approved configuration changes incorporated into purchased prototypes. Finalized ICDs, IDDs, and associated interface requirements shall be Phase 2 deliverables.

3.3 Open System Management Plan

The Performer shall develop an Open System Management Plan (OSMP) describing the MOSA technical approach, module boundaries, interface standards, proprietary dependencies, and strategy for enabling competitive procurement of individual modules. The OSMP is a Phase 1 deliverable subject to Government review and concurrence. It shall identify the demonstrated architecture and the planned approach for addressing MOSA limitations, be updated to reflect approved changes to purchased prototypes, and be further refined during Phase 2 to document the matured architecture.

3.4 Data Rights

The Government desires Unlimited Rights in all interface definitions; form, fit, and function (FFF) data; and operations, maintenance, installation, and training (OMIT) data. The Government desires Government Purpose Rights in technical data defining Major System Interfaces (MSIs); module-level integration documentation; test data generated under this effort;

and technical data and computer software necessary to enable competitive procurement of any deliverable module. The Performer's data rights assertions shall be documented in the Data Rights Assertions attachment to the OTA. The SOW shall not restate data rights but shall reference the OTA, describe how deliverables will be marked consistently with the Data Rights Assertions, and identify the data rights for all deliverables. Performer investment in the demonstration does not reduce the Government's minimum Right to Repair requirements or the rights the Government requires in interface definitions, form, fit, and function data, and OMIT data.

CAML-Lite SOO (Attachment 1 to RFSB) | Page 6 of 14

3.5 Right to Repair

The Government requires sufficient technical data, computer software access, tools, and license rights to enable Government personnel and Government-authorized support providers to inspect, diagnose, maintain, and repair purchased prototypes. The Performer shall identify the documentation, diagnostic tools, software access, licenses, and rights proposed to support these activities and disclose any restrictions or dependencies that could limit their use. The draft Phase 1 SOW submitted with the RFPP proposal shall identify the tasks, documentation, diagnostic tools, software access, and other deliverables proposed to support the Government’s Right to Repair requirements. It shall include delivery milestones and a verification approach demonstrating that Government personnel or Government-authorized support providers can use the delivered resources to perform the required inspection, diagnosis, maintenance, and repair activities. The draft SOW shall reference the proposed license and data-rights terms and identify any dependencies affecting execution.

The RFPP and negotiated OTA will establish the required deliverables and minimum rights, including rights necessary to support future competition for applicable components and support services. Acceptance of the minimum Right to Repair requirements is a condition of award.

4. CAPABILITY OBJECTIVES

The following capability objectives apply to the Phase 1 system and the Phase 2 prototype. A threshold is the minimum acceptable value, subject to the Phase 1 shortfall provisions below; an objective is the desired value. Solutions Briefs shall address each capability objective by number.

For Phase 1, the Performer shall identify, for each capability objective, the value its system will achieve relative to the threshold and objective and the evidence supporting that value. For Phase 2, the SOW shall describe how the prototype will meet the applicable thresholds and objectives expressly incorporated into the negotiated SOW. The negotiated Phase 1 SOW and approved demonstration plan shall establish the required demonstration criteria. Purchased prototypes shall retain the demonstrated capability baseline, except for Government-approved changes.

For Phase 1, the Government may consider solutions with disclosed threshold shortfalls, provided they meet the minimum requirements for consideration in RFSB Section 9.1.

Performers shall identify each shortfall, its effect on demonstration execution and intended Government use, and any proposed mitigation. Selection does not constitute acceptance of an undisclosed shortfall; the negotiated SOW and approved demonstration plan shall establish the required Phase 1 performance baseline.

Capability Objective Threshold Objective OBJ-1 Cross Domain Fires:

The ability to shoot both defensive and offensive munitions

Ability to shoot live munitions. Offensive and Defensive munitions shot in Prototype Demo.

OBJ-2 Reload Operations:

The ability to autonomously load and reload munitions

Ability to reload munitions.

Can include human engagement. All materiel handling equipment must be provided.

Autonomous reload operations without direct human engagement.

Reload requires no external logistic support equipment.

CAML-Lite SOO (Attachment 1 to RFSB) | Page 7 of 14

Capability Objective Threshold Objective OBJ-3 Emplacement and Displacement

Ability to emplace and displace system.

Autonomous emplacement and displacement.

OBJ-4 Autonomous Capability System demonstrates autonomous capabilities.

Autonomous system, optionally crewed, capable of teleop, waypoint, and convoy modes controlled by leader/follower vehicle(s).

OBJ-5 Air Transportability C-130 transportable without a missile/pod loaded configuration.

C-130 transportable in a loaded missile/pod configuration.

OBJ-6 Self Leveling System can level to support munition requirements.

System can self-level to support entire CAML munition requirements.

OBJ-7 Command and Control (C2)

System can receive fire missions from non-tactical systems.

System can receive fire missions from legacy and modernized DoW systems.

OBJ-8 Mobility Operates on primary and secondary terrain.

Operates on unimproved terrain.

As an all-terrain capable system, CAML variants are engineered to handle challenging, uneven, or loose off-road surfaces such as dirt, mud, sand, gravel, rocks, grass, snow, and shallow water (< three feet) in temperate, arid, and tropic regions; capable of moving from ships into no more than three feet of seawater onto shale or sandy beaches.

OBJ-9 Power External power required for launcher systems.

Self-sustaining onboard power for launcher systems.

5. PHASE 1 OBJECTIVES: DEMONSTRATION AND PROTOTYPE ACQUISITION

The objective of Phase 1 is for each selected Performer to provide one (1) or more complete prototype system representing its best available solution for TS-27 (or an approved alternative demonstration), support a Government-sponsored demonstration assessing the applicable capability objectives in Section 4, and provide sufficient data to inform Government decisions on prototype acquisition, operational experimentation, and follow-on maturation.

Phase 1 also includes the priced Phase 1 Prototype Acquisition Option described in Section 2, whose components may be exercised individually, all together, or not at all, before or after TS-

27. The Performer's SOW shall define the tasks, deliverables, schedule, and acceptance criteria for the demonstration and for each component of the option.

CAML-Lite SOO (Attachment 1 to RFSB) | Page 8 of 14

5.1 Required Phase 1 Outcomes

Demonstration Effort

• Successfully complete a prototype demonstration at TS-27, unless the Government waives this requirement or approves an alternative demonstration.

• Assume full responsibility for transporting the system to Australia, or to an approved alternative location, including all logistics, packaging, and international compliance requirements (for example, customs, biosecurity, export, Australian Border Force, and Australian explosive ordnance licensing).

• Provide all required documentation and support for range safety.

• Provide cybersecurity artifacts to achieve an Interim Authority to Test (IATT).

• Deliver an OSMP; electrical, mechanical, and logical interface documentation reflecting the demonstrated configuration; and reports on Government-funded and Performer-funded expenditures.

• Provide all system operation, field service support, explosive ordnance handling, transportation, system security and repair for the demonstration, as no Soldier support will be provided.

Prototype Acquisition Option (if exercised)

• Deliver the ordered quantity of prototypes in the agreed configuration within the delivery lead times in the OTA.

• Provide configuration records, required support equipment, acceptance evidence, and warranty documentation for each purchased prototype.

• Provide NET before Government personnel undertake activities requiring that training.

• Provide CLS throughout the exercised testing and experimentation period.

• Provide the Right to Repair deliverables established in the OTA (Section 3.5).

• Update applicable interface, safety, cybersecurity, training, and support documentation to reflect approved configuration changes.

• Support Government collection of operational results and Soldier feedback as specified in the negotiated SOW.

5.2 Phase 1 Program Schedule and Reviews

The Performer shall support the following Government reviews and events during Phase 1. The SOW shall describe the data and documentation to be presented and the process for addressing Government feedback and closing critical actions.

Reviews: Kick-Off Review (within 30 days after award), monthly Program Management Reviews (PMRs), Test Planning Integrated Product Teams, Range Safety Working Groups, Design Adaptation Reviews, and a Post-Event After Action Review.

Tentative Demonstration Milestones:

• December 2026: Phase 1 OTA award

• March 2027: System Checkout and Readiness Review

• May 2027: TS-27 Final Planning Conference

• July 2027: OCONUS site preparation and system checkouts

CAML-Lite SOO (Attachment 1 to RFSB) | Page 9 of 14

• August 2027: TS-27 prototype demonstration System Transportation: The Performer shall propose a transportation schedule supporting required checkout, readiness reviews, and the August 2027 demonstration, accounting for the transportation method, transit time, customs and biosecurity processing, and site preparation. If maritime transportation requires shipment before the planned March 2027 readiness review, the Performer shall identify the required earlier checkout and review dates.

For any exercised option, the SOW shall establish prototype delivery and acceptance milestones, NET completion dates, CLS coverage, and supported Government experimentation events.

5.3 Phase 1 Deliverables

The following are the Government's minimum Phase 1 deliverables, as applicable. The Performer may propose additional deliverables in the SOW. The SOW shall establish the due date, format, and acceptance criteria for each deliverable consistent with the Contract Data Requirements List (CDRLs) attached to the OTA.

Deliverable Description Phase 1 Demonstration System (one (1) complete system)

Performer Investment and Expenditure Report System provided to support all demonstration milestones Airworthiness Certifications or Report Demonstration Report

Program Review Documentation Kickoff Documentation/Slides Demonstration Readiness Review Package PMR Documentation/Slides Meeting Minutes (Test IPTs, Reviews, etc..)

Safety Assessment Report and Supporting Artifacts

Safety Assessment Report (SAR)

FSDP/GSDP

EOD Data Package

Cyber IATT and Supporting Artifacts

CONOP (Cybersecurity Test Plan) DI-SCRE-82140A Vulnerability Scan Compliance (VSC) DI-MGMT-81842 Hardware/Software/Firmware Bill of Material DI-PSSS-81656

MOSA and System Design Details Open System Management Plan Prototype Interface Control Design (ICD) Documentation for Electrical, Mechanical, and logical interfaces

Purchased Phase 1 Prototypes (Option)

Ordered units, required support equipment, configuration records, acceptance evidence, receiving documentation, warranty terms, and Right to Repair deliverables

NET (Option) NET Plan, programs of instruction, training materials, and completion records

CLS (Option) CLS Plan, recommended spares list, maintenance and readiness reports, and logistics data

CAML-Lite SOO (Attachment 1 to RFSB) | Page 10 of 14

5.4 Phase 1 Exit Criteria

The demonstration effort is complete upon written Government determination that the approved demonstration activities have been completed (or halted due to safety or mission constraints) and demonstrated capabilities, limitations, and configuration have been documented. Completion of the demonstration does not constitute Government purchase of the demonstration system, authorization for Soldier operation, or a commitment to exercise any option. Halting the demonstration does not automatically satisfy outstanding deliverables or payment requirements under the OTA. The paragraph would read like this: The demonstration effort is complete upon written Government determination that the approved demonstration activities have been completed or halted due to safety or mission constraints and that demonstrated capabilities, limitations, and configuration have been documented. Halting the demonstration does not automatically satisfy outstanding deliverables or payment requirements under the OTA.

Completion of the demonstration does not constitute Government purchase of the demonstration system, authorization for Soldier operation, or a commitment to exercise any option. Completion of the demonstration by itself, also does not constitute successful performance of a prototype project.

An exercised option shall be completed against the negotiated requirements for each exercised component. Phase 1 closeout shall account for completion of the demonstration and all exercised option components. Unexercised options do not create performance obligations.

6. PHASE 2 OBJECTIVES: PROTOTYPE MATURATION

A draft Phase 2 SOW is not required with the Phase 1 RFPP proposal. When separately requested by the Government, the Performer shall submit a draft Phase 2 SOW that can stand alone for pricing, award, execution, and closeout. Tasks, deliverables, milestones, and costs for Phase 2 shall be separately identified from the Phase 1 demonstration and the Phase 1 option.

Phase 2 runs from award or option exercise through design, development, integration, verification, acceptance testing, and formal Government acceptance of the required prototypes and deliverables. The objective of Phase 2 is to mature the selected CAML-Lite solution, incorporating applicable Phase 1 demonstration results, available Soldier experimentation feedback, and Government direction, into a production-representative prototype that meets the applicable thresholds and negotiated objectives in Section 4 and advances integration with the common CAML architecture.

6.1 Required Phase 2 Outcomes

• Deliver Production-Representative Prototypes: Deliver the specified quantity of

CAML-Lite prototypes that meet the applicable Section 4 thresholds and objectives expressly incorporated into the negotiated SOW, are representative of the production design, and are ready for Government testing.

• Finalize and Document the System Design: Establish the complete technical baseline by delivering a finalized Technical Data Package (TDP), As-Built Configuration Lists (ABCL), and supporting digital engineering models (MBSE, M&S), with rights sufficient to support future competition as established in the Phase 2 agreement.

• Establish a Complete MOSA-Compliant Architecture: Deliver finalized ICDs and an updated OSMP that fully document the system's modular, open architecture and ease of component replacement.

CAML-Lite SOO (Attachment 1 to RFSB) | Page 11 of 14

• Verify and Validate System Performance: Complete all required design reviews and qualification testing to provide objective, verifiable evidence that the final prototype design meets the applicable Section 4 thresholds and objectives expressly incorporated into the negotiated SOW.

• Provide Program Management Data: Deliver the program management artifacts required to demonstrate disciplined execution and progress against cost, schedule, and performance milestones.

6.2 Phase 2 Program Milestones and Reviews

During Phase 2, the Performer shall execute a structured series of formal reviews, including Program Kick-Off, System Requirements, Preliminary and Critical Design, Test Readiness, and Configuration Audits, supplemented by recurring PMRs and technical working groups. In parallel with or following critical design reviews, milestones shall include prototype fabrication, integration, testing, verification, delivery, and formal Government acceptance, as established in the negotiated SOW. Any NET or CLS required for Phase 2 prototypes shall be separately identified and priced.

6.3 Phase 2 Deliverables

The following are the Government's minimum Phase 2 deliverables. The Performer may propose additional deliverables in the SOW.

Deliverable Purpose Phase 2 Prototype(s) Prototype(s) meeting the applicable Section 4 thresholds and objectives expressly incorporated into the negotiated SOW for Government testing

Finalized ICDs Establishes complete and final interface definitions Updated Open System Management Plan (OSMP)

Documents the final MOSA architecture and module strategy

Model Based Systems Engineering Models and Artifacts

Support requirements, design, analysis, verification, and validation associated with the development of the prototype systems.

Modeling and Simulation Models and Artifacts

Supportive digital model of the prototype systems that represents the physical model in which real world conditions are applied and tested

Configuration Management Document to define how vendor will identify, control, track, and manage changes to a product or system throughout its design/ lifecycle.

Objective Evidence for Design Reviews

Objective Evidence provided by the vendor to meet entrance and exit criteria for SRR, PDR, CDR and VAL/VER

Technical Data Package (TDP) Technical Data Package List

(TDPL)

Models, drawings, specifications, and related documentation that fully defines an item.

CAML-Lite SOO (Attachment 1 to RFSB) | Page 12 of 14

Deliverable Purpose As-Built Configuration List (ABCL) at delivery and Government Acceptance (DD250) of each Production Prototype.

Records every part, component, and configuration detail of an assembled end item, including part numbers, revisions, serial/lot numbers

Program Management Artifacts Deliverables that show progress to program milestones, risk management, and cost performance/metrics.

6.4 Phase 2 Exit Criteria

Phase 2 is successfully completed upon written Government determination that all of the following have been satisfied:

• Prototype Acceptance: Government inspection, testing, and formal acceptance of all delivered production-representative prototype units.

• Technical Baseline Delivery: Receipt and Government approval of the finalized TDP, ABCL, and digital engineering/MBSE models.

• Performance Verification: Successful completion of all required development and qualification testing, demonstrating that the system meets the applicable Section 4 thresholds and objectives expressly incorporated into the negotiated SOW.

• Certifications Obtained: Receipt of a cybersecurity Authority to Operate (ATO), system safety hazard clearance, and all required transportation and airworthiness certifications.

• Closeout: Unless otherwise determined, Closeout will occur after completion of all required SOW tasks, review milestones, deliverables, and financial reporting.

Verification of Performer investment applies only if expressly included in the Phase 2 agreement.

7. PROGRAM SCHEDULE

The Performer's SOW shall reflect the applicable milestones below and identify schedule risks, dependencies, and mitigation approaches. The Performer shall notify the Agreements Officer's Representative in writing as soon as practicable upon identifying a condition that could affect a milestone.

Key Milestone Date RFSB Issuance 15 October 2026 Request for Invitation for Q&A 19 October 2026, COB

Virtual Q&A Event 20 October 2026, Time TBD

Solutions Briefs Due 23 October 2026, 1600 CT RFPP Issuance to Selected Respondents 6 November 2026 RFPP Proposals Due 20 November 2026, 1600 CT Phase 1 OTA Awards, Including the Priced Phase 1 Prototype Acquisition Option

Expected 18 December 2026

CAML-Lite SOO (Attachment 1 to RFSB) | Page 13 of 14

Key Milestone Date System Checkout and Readiness Review March 2027, or earlier as required by the

Performer's transportation schedule Phase 1 Demonstration at TS-27 (or approved alternative)

August 2027

Government Phase 1 Demonstration Report Government-established date following the demonstration

Updated Pricing Request for the Phase 1 Option (downward only)

Following TS-27, on the common date at the Government's request

Phase 1 Option Exercise Window From award through 90 days after issuance of the Government's demonstration report

Prototype Deliveries, NET, and CLS In accordance with the delivery lead times and schedules in the OTA

Phase 2 Proposals and Award As established in the applicable solicitation or request for proposal

8. SECURITY

The prototype OTA is anticipated to be classified at the SECRET level. The Performer shall address security requirements in the SOW consistent with the DD Form 254 attached to the OTA and applicable OPSEC requirements, identify the system classification level and handling, and describe its approach to managing classified information, facility clearance requirements, and personnel security throughout all periods of performance. This SOO is unclassified.

9. GOVERNMENT-FURNISHED PROPERTY AND INFORMATION

Government-furnished property, information, and equipment shall be identified and documented for the demonstration effort, the Phase 1 option, and Phase 2, as applicable. The SOW shall include the complete list of Government-furnished items required for each effort, including munitions, interface documentation, common CAML components, and test assets where applicable, with required availability dates and dependencies affecting execution.

Each Performer shall identify the munition types and quantities required for its proposed demonstration and whether they will be Performer-provided or requested as Government-furnished items. The negotiated SOW shall establish responsibility for munition sourcing, integration, transportation, handling, and associated safety documentation. The Performer shall not assume availability of any Government-furnished item unless expressly identified and agreed to in the applicable agreement. Property management requirements shall be governed by that agreement.

10. APPLICABLE DOCUMENTS

• CAML-Lite Request for Solutions Brief (RFSB), [Solicitation Number], 16 October

2026: program background, capability gap, program structure, and acquisition strategy

CAML-Lite SOO (Attachment 1 to RFSB) | Page 14 of 14

• CAML-Lite Request for Prototype Proposal (RFPP), 3 November 2026: proposal and SOW requirements, option pricing instructions and planning assumptions, and OTA terms and conditions

• Prototype OTA attachments, to be identified in the RFPP: Contract Data Requirements List (CDRLs); DD Form 254, DoD Contract Security Classification Specification; and Data Rights Assertions

• 10 U.S.C. § 4022: Other Transaction Authority for Prototype Projects

• 10 U.S.C. §§ 4401 through 4403: Modular Open Systems Approach Requirements

• CAML Concept of Employment (CONEMP) [Draft]