Compliance checklist

Synthetic Training Environment (STE) Virtual Software (VSW) · STE-VSW-26-0006. 79 requirement sentences found in the notice and 6 attachments: every "shall", "must" and "required", quoted as written and sorted into submission requirements (18) and performance / contract clauses (61). Nothing is generated.

Pro

The full checklist is a Pro feature

79 requirement sentences on this RFP. Pro shows every one, grouped by section, with a CSV export, for $39/mo. Below is a preview.

Submission requirements · 18

8effcb8b7afc4e00b4ce75c7fd52ed41.pdf · 1

Offerors proposing a GOTS-based approach must provide in Volume II a clear, detailed technical roadmap and interface design approach demonstrating how they will establish open, published SDKs and modern APIs (e.g., REST, gRPC, HLA/DIS) to expose TSS simulation services, data models, and external interfaces for third-party integration.

8effcb8b7afc4e00b4ce75c7fd52ed41.pdf · Page 1 · 2

Note: Volume II (Technical Concept Submission) remains a blind, narrative evaluation focused on technical approach and architecture, and must remain free of corporate names, logos, or identifying personnel marks.
Lot 1 Offerors must include the labor and engineering costs for participating in the 90-day Phase 4 Sandbox within their Volume IV ROM, explicitly broken out under Milestones 1.1 through 1.4.

Performance / contract clauses · 61

Notice · 1

You must manually check the version dates using the dropdown and select the latest.

8effcb8b7afc4e00b4ce75c7fd52ed41.pdf · 1

Will a live API/SDK Documentation access be required if the vendor selects the GOTS-provided TSS approach for all Lots of this proposoal? No, live public API/SDK documentation is not mandatory for offerors proposing Path A (GOTS-based TSS approach).

Extracted from the notice text and attachments as published. The solicitation governs; read Sections L and M in full before you submit.