STE VSW Industry Day Slides 9.22.26.pdf

Advancing Today’s Training Defeating Tomorrow’s Threats

UNCLASSIFIED

UNCLASSIFIED

Project Manager Simulation (PM SIM)

U.S. Army Capability Program Executive for Simulation, Training, Test and Threat

(CPE ST3)

Synthetic Training Environment (STE) Virtual Software (VSW) Industry

Day

22 September 2026

UNCLASSIFIED 2

Welcome and Opening Comments

COL Natashia Coleman

UNCLASSIFIED 3

STE VSW Industry Day Agenda

• Welcome and Introductions

• Strategic Context and Why We Are Here

• Core Operational Priority Deliverables

• Architecture and Demarcation of Responsibilities

• Acquisition Strategy and Phased Timeline

• Proposal Submission Guidelines and Evaluation

• Next Steps and Q&A

10-Minute Break

• Question and Answer Session

• Closing Comments

UNCLASSIFIED 4

Panel Members

• MAJ Rob Scrip – STE VSW Assistant Product Manager

• MAJ Tyler Valentine – STE VSW Assistant Product Manager

• Mr. Alpesh Patel – PdM CSE Chief Engineer

• Mr. Neal Eskin – STE VSW Lead Engineer

• Mr. Chad Thomas – UnITE Chief Architect

• Mr. Mark A. Muñiz – Army Contracting Command Army Proving Ground – Orlando Division

Contracting/Agreements Officer

• LTC Michael Cuddy – NSC Virtual Training Environment Division Chief

UNCLASSIFIED 5

Administrative Announcements

• Welcome!

• Rules of Engagement

• Please keep sidebars/chatter to a minimum

• Hold questions until end of meeting

• 3x5 Cards

• Microphone Stands

• Fire Protocol / Emergency Exits

• 1x 10-Minute Breaks

• Bathroom Locations

• 1200 (Noon) Cutoff

UNCLASSIFIED 6

Strategic Context and Why We Are Here

MAJ Rob Scrip

UNCLASSIFIED 7

STE Virtual Software – Strategic Context

• A Rapidly Evolving Multi-Domain Battlespace Near-peer threats, dynamic electronic warfare, and modernized combat networks demand more adaptable, rigorous virtual collective training.

• Maintaining Concurrency with the Warfighter Training systems must match the pace of tactical platform modernizations (OFPs, fire control, mission command) in weeks and months, not years.

• Agility Through a Government-as-Integrator Model Adopting a Modular Open Systems Approach (MOSA) with published SDKs to rapidly onboard cutting-edge commercial technology.

UNCLASSIFIED 8

Core Operational Priority Deliverables

1. A Doctrinal TC 3-20.0 Table II Gate to Live

Fire for Ground

2. TC 3-04.3 Table VII & Table X Collective

Gunnery Gate for Air

3. A True Combined Arms Environment

4. Full Mission Command Concurrency

5. Rapid Capability Onboarding and Integration

UNCLASSIFIED 9

STE VSW Architecture and Demarcation of Responsibilities

UNCLASSIFIED 10

STE VSW “Platform and Application” Architecture

5 Capability Lots: "Platform + Apps"

Lot 1: Common Core Software The foundational OS, simulation engine, and data fabric.

Lot 2: Simulation Applications Specialized plug-in modules (CGF, vehicles, sUAS).

Lot 5: Enterprise Integration Support DevSecOps, Software Integration Lab management, and Conformance Testing.

Lot 3: HIL Integration

Physical hardware translation.

Lot 4: AAR Data Layer

Training mgmt & analytics.

• Lot 1 (Core Engine): The "virtual world operating system" (simulation, rendering, data fabric, published SDK).

• Lot 2 (Simulation Apps): The "App Store" modules (vehicle physics, weapon ballistics, tactical plug-ins).

• Lot 3 (HIL Integrator): Physical-to-digital translation (GFE controls to HAPI packets; SIL integration only—no site fielding).

• Lot 4 (AAR & Analytics): Subscribes to message bus for automated TC 3-20.0 scorecards and spatial replays.

• Lot 5 (Enterprise Integrator): The independent "digital motherboard" custodian (SIL operations, DevSecOps pipeline, CTS testing, SBOM analysis).

UNCLASSIFIED 11

Teaming and Lot 5 Structural OCI Rule

• Lots 1–4 Teaming: Multi-vendor teaming and cross-lot subcontractor participation are greatly encouraged.

• Lot 5 Independence: Lot 5 is an independent evaluator/testing authority.

• The Rule: A company/affiliate may bid on Lot 5 and Lot’s 1/2/4 but cannot be awarded or perform on 5 and either Lot 1/2/4. If selected for both, the vendor must elect a single award. Internal corporate firewalls will not be accepted for dual-lot performance.

UNCLASSIFIED 12

Operational Requirements and Trade Space

MAJ Tyler Valentine

UNCLASSIFIED 13

Virtual Training Requirements (Ground)

Delivering the TC 3-20 (IWTS) Table II Virtual Gate to Live Fire

Ground fleet initial focus: M1A2 Abrams, M2A3/A4 Bradley & BFIST, Stryker.

• SHOOT (Lethality & Fire Control)

• Full weapon &FCS switchology

• High-fidelity ballistics, time of flight, dispersion, and pH/pK

• Platform battle damage, ammunition loadouts, and doctrinal reload times

• MOVE (Maneuver & Vehicle Dynamics)

• Physics-based tracked/wheeled vehicle dynamics over OWT

• Section- and platoon-level battle drills, combat formations, and actions on contact

• COMMUNICATE (Mission Command Concurrency)

• Integration with operational Mounted Mission Command

• Tactical intercom and multi-echelon radio simulation

• Training under contested conditions: GPS-denied, EW jamming, degraded

C2

UNCLASSIFIED 14

Virtual Training Requirements (Air)

Delivering Aviation collective gunnery: TC 3-04.3 Tables VII and X for AH-64E, UH-60M/V, and CH-47F

Air initial focus: AH-64E, CH-47F, UH-60M/V

• Shoot

• High-fidelity ballistics, time of flight, dispersion & pH/pK

• Full weapon (30mm, Hellfire, Rockets, M240) & sensor (PNVS, TADS, FCR, Link 16) functionality for current platform version

• Move

• Accurate flight modeling of rotary wing physics that depend on the environment, weight and operational systems (fuel, engine, etc.)

• Concurrent & operational aircraft OFP

• Communicate

• Simulation of tactical radios & communication devices by platform (ICS, VHF, UHF, Longbow Net, BFT, Link 16, SATCOM)

• Manned – Unmanned Teaming (MUM-T) capability from other aircraft & UAS (AAG, UR)

• Other

• Mission Planning: AMPS mission planning data ingestion

UNCLASSIFIED 15

RVCT-A Architectural Trade Space

• Call to Industry on Air: Lot 1 and Lot 2 offerors are asked to propose their preferred architectural approach:

• (A) Unified multi-domain simulation engine

• (B) Modular Lot 2 flight physics plugins

• (C) Federated domain-specific engines over standard protocols (DIS/HLA/gRPC)

• (D) Other

UNCLASSIFIED 16

Acquisition Strategy and Phased Timeline

Mr. Mark A. Muñiz

UNCLASSIFIED 17

Phased Solicitation and Award Sequencing

Where are we today, in our anticipated schedule?

Acquisition Events Anticipate Date(s) DRAFT STE VSW CFS posting 27 August 2026

DRAFT STE VSW CFS Q&A 27 August 2026 - 13 September 2026 FINAL STE VSW CFS posting 15 September 2026

STE VSW Industry Day and One on One sessions, Orlando, FL.

22 - 24 September 2026

UNCLASSIFIED 18

Phased Solicitation and Award Sequencing

Phase 1: Solution Brief

• Offerors will submit a high-level summary of their solution, addressing the government’s objectives and requirements. Offerors shall submit a solution structured into the Volumes as noted in Section 6 of the STE VSW CFS. Solutions that fail to adhere to the page limitations or submission requirements will be considered non-compliant and may not be reviewed.

• Detailed solution brief submission requirements for Phase 1 are provided in Section 6 of the STE VSW CFS. Evaluation criteria for Phase 1 are outlined in Section 7 of the STW VSW CFS.

Phase 2: Demonstration Pitch

Selected offerors may be invited to present and discuss their solution in a live or virtual setting.

Phase 3: Revised Solution

The Government shall use the same criteria to evaluate prototype solutions as described for Solution Briefs.

UNCLASSIFIED 19

Phased Solicitation and Award Sequencing

• Immediate Focus (Phase 1): Solicitations open for Lot 1, Lot 3, and Lot 5 (due Tuesday, 29 September 2026). Anticipated award Monday, 13 November 2026.

• Deferred Solicitations (Lots 2 & 4): Formal calls for Lot 2 and Lot 4 will be issued after the initial 90-day sandbox when the Lot 1 SDK is finalized. Approximately 4-months after Lot 1 Phase 3 awards. Lot 2 will have on-ramping opportunities throughout the development phase.

• Approximate Total Project Value: ~$250M ceiling across all Lots.

• Electronic Basket of Vendors: Those selected to have Schedule Narrative, Technical Merit, and Solution Viability Recency, Relevancy, with Low or Moderate overall project risk, but not selected for further consideration, may be selected for basket consideration for up to twenty-four

(24) months.

UNCLASSIFIED 20

Proposal Submission Guidelines and Evaluation

Mr. Mark A. Muñiz

UNCLASSIFIED 21

GFI Baseline Access Procedures

• How to access the TSS GFI baseline (Attachment 06/06a):

1. Sign the STE-IS Software Distribution Agreement (Att 06)

2. Provide all documentation along with a formal request to the Solicitation POCs listed on the sam.gov posting

3. Supply an 8TB external storage drive (schedule appointment to drop off at P IV)

GFI Data Transfer takes approximately 8 hrs. Proposal/Solution submission deadline remains 29 September.

UNCLASSIFIED 22

Phase 1 Submission Requirements

• All solution/proposal submissions shall be submitted using no less than 11 size Arial font, one-inch margins on an 8.5 x 11 standard size page. File size shall be broken up to no larger than 5MB size per email submission. There is no restrictions on file naming. The email solution/proposal submission shall identify specific Lot number.

UNCLASSIFIED 23

Phase 1 Solution Brief Basis of Evaluation

• Volume I (Mandatory Technical Readiness and Compliance): Non-blind. Att 01 Interested Vendor and/or Interested Vendor Form; Attachments: 02 Warranties and Representation; 03 Telecom Reps; Attachment 04 ACA LOI; DD Form 2345; One World Terrain (OWT)/OGC Ingestion & Rendering link or screen capture; OCI dual-submission Acknowledgement Statement; and comprehensive Risk & Mitigation Plan. Master Compliance Matrix (optional).

Ratings will be Acceptable/Not Acceptable

• Volume II (Anonymous Technical Concept Submission): Strictly Anonymous. 5 pages max per Lot (expanded to 8 pages for Lot 1: 5 pages core + 3 pages Air Annex). Up to 2 uncounted diagram pages allowed. Concise technical risk callouts included. Ratings in descending order of importance: (a) Schedule, (b) Technical Merit, and (c) Viability.

• Volume III (Product Demonstration Artifacts): Non-blind. 5-minute video and live API/SDK documentation links.

Evaluated as being Compliant/Non-Compliant based on the verification and validation of the “show, don’t tell” artifacts.

• Volume IV (Rough Order of Magnitude (ROM) and Licensing Model): Non-binding planning ROM for the 9-month prototype effort (including 90-day SIL sprint). ROM is collected for Government planning and market research only;

this volume will NOT be evaluated or scored.

• Volume V (Recent and Relevant Experience): Non-blind. Up to 3 recent contracts within the last 3 years of CFS submission date and relevant experience. Ratings will be Recent/Not Recent and Relevant/Not Relevant.

UNCLASSIFIED 24

Phase 1 Down-Select Evaluation Methodology

• Step 1: Mandatory Technical Readiness and Compliance:

- Mandatory Acceptable/Not Acceptable Readiness application to Volume I.

- If step 1 receives an acceptable rating, then the evaluation moved to Step 2.

• Step 2: Solution Brief Volume II (Anonymous Technical Concept):

- Weighted Evaluation Criteria: Evaluated in descending order of importance:

(a) Schedule, (b) Technical Merit, and (c) Viability.

- Recent and Relevant Experience applicable to Volume V: This volume is going to be assessed as being Recent within will within 3 years of CFS submission date; Recency ratings will be Recent/Not Recent. Relevant to the specific Lot scope, objectives, and requirements.

Ratings will be Relevancy/Not Relevant.

- Overall Project Risk: This subjective overall project risk rating is synthesized from the evaluation findings across Volumes II, and V, reflecting the Government’s confidence in the offeror’s ability to successfully deliver and integrate the proposed STE Virtual Software capabilities without mission failure or critical delay. The Government will utilize the following risk tiers: Low Risk; Moderate Risk; High Risk.

UNCLASSIFIED 25

Phase 1 Down-Select Evaluation Methodology

• Based on the evaluated sections, the Solution submission will be categorized as Selected for Further Consideration or Not Selected for Further Consideration. Those selected to have Schedule Narrative, Technical Merit, Solution Viability, Recency, Relevancy, with Low or Moderate overall project risk, but not selected for further consideration, may be selected for basket consideration for up to twenty-four (24) months.

• The selection of one (1) or more submissions into the next Phase will be based on the criteria listed above and funding availability.

• The Government reserves the right to limit the number of Vendors invited to Phase 2 and/or subsequent Phases. As such, a Vendor’s solution may be evaluated for Schedule Narrative, Technical Merit, Solution Viability, Relevancy, Recency, with Low or Moderate overall project risk but not invited to Phase 2 and/or Subsequent Phases. Solution submissions that are chosen for Phase 2 and/or subsequent Phases will be notified in writing as soon as practicable. The Government reserves the right to bypass Phase 2 into Phase 3 to request a formal proposal should funding be available.

UNCLASSIFIED 26

Phase 2 Demonstration Pitch

• Live Demonstrations: Down-selected offerors will be invited to conduct a one-hour, live or virtual technical demonstration of their submitted software solution to the Government evaluation team.

• Evaluation: criteria will remain the same as in Phase 1 for Lots 1,2, and 4. Lots 3 & 5 evaluations will be identified upon selection.

UNCLASSIFIED 27

Phase 3 Revised Solution Submission

• Phase 3 Revised Solution Submission: submission requirements and evaluation criteria will be outlined in the invitation to this phase.

UNCLASSIFIED 28

POCs for Questions and Solution/Proposal Submission

Contract POCs:

Ruth Torres, Contract/Agreements Specialist: ruth.e.torres10.civ@army.mil

Kimberly Skinner, Contract/Agreements Specialist: kimberly.c.skinner.civ@army.mil

Dave Hagler, Contracting/Agreements Officer: david.a.hagler.civ@army.mil

Sean J. Johnson, Contracting/Agreements Officer: sean.j.johnson2.civ@army.mil

Mark A. Muñiz, Contracting/Agreements Officer: mark.a.muniz6.civ@army.mil mailto:ruth.e.torres10.civ@army.mil mailto:kimberly.c.skinner.civ@army.mil mailto:david.a.hagler.civ@army.mil mailto:sean.j.johnson2.civ@army.mil mailto:mark.a.muniz6.civ@army.mil

UNCLASSIFIED 29

Next Steps

• 25 September 2026: Q&A Cutoff

• 29 September 2026: Submission Deadline

• 02 October 2026: Anticipated Down-Select Notifications

• 09 October 2026: RVCT Platforms available in the TIF for experimentation

• 20-22 October 2026: Lots 1, 3, & 5 Demonstration Pitch

UNCLASSIFIED 30

10 Minute Break Before Questions and Open Discussion

UNCLASSIFIED 31

Most Frequently Asked Questions

UNCLASSIFIED 32

Most Frequently Asked Questions

1. Volume IV Pricing Scope, Enterprise Licensing Models & ROM Metrics

• Government Position: Volume IV is non-binding and collected for planning/market research only – it is not evaluated or scored in Phase 1. The baseline preference is a flat STE-program-wide enterprise license across the 22 planned fielded RVCT sites.

2. Volume III Demonstration Artifacts, Live Portals, and TRL 8/9 Maturity Gates

• Government Position: Volume III is an objective Compliant/Not Compliant technical readiness gate and is exempt from anonymity. Password-protected or credentialed portals are acceptable provided immediate, self-service access credentials are included in Volume I. Lot 5 vendors may demonstrate operational pipelines from other defense or commercial enterprise programs as proof of TRL 8/9 capability.

3. SIL Physical Facility, Real Estate, Networks & Infrastructure Responsibility

• Government Position: As formalized in Amendment 001, the Government will not provide physical real estate. Lot 5 is solely responsible for leasing, securing, accrediting, and operating the brick-and-mortar SIL facility in the greater Orlando, FL area, along with internal simulation and development LANs. Lot 5 acts as physical custodian (receiving, rigging, placing GFE cabs), while Lot 3 acts strictly as the technical integration tenant.

UNCLASSIFIED 33

Most Frequently Asked Questions

4. Lot 2 and Lot 4 Submission Deferrals, Milestones, and Deadlines

• Government Position: The 29 September 2026 deadline is unchanged and applies to Lots 1, 3, and 5.

Formal Phase 1 submissions and Phase 2 demonstrations for Lots 2 and 4 are fully deferred until after the winning Lot 1 Common Core platform is selected and its SDK is published.

5. Organizational Conflict of Interest (OCI) and Lot 5 Firewall Restrictions

• Government Position: Under FAR Subpart 9.5 and OT principles, the Lot 5 firewall is a strict structural exclusion applying across the entire corporate family—corporate firewall mitigation plans will not be accepted between Lot 5 and Lots 1, 2, or 4. Companies may submit bids on multiple Lots, but in the event of dual selection, they must elect a single award. Cross-lot teaming is permitted across Lots 1–4, and Lot 3/Lot 5 dual-proposals are evaluated for impaired objectivity on a case-by-case basis.

6. Cybersecurity Compliance, Risk Management Framework (RMF) & Authority to Operate (ATO) Responsibilities

• Government Position: Shared Responsibility Model – Lots 1 through 4 are responsible for delivering component-level security artifacts. Lot 5 acts as the centralized pipeline aggregator and lab custodian, automating security testing and maintaining the integrated security package under direct Government Program Office oversight.

UNCLASSIFIED 34

Q&A and Open Discussion

UNCLASSIFIED 35

Closing Comments

COL Natashia Coleman