(U) SDN-B MOC CRM.xlsx
XLSX spreadsheet 17 KB Posted
- Solicitation number
- SDNMOC002
About this file
This is a Comment Resolution Matrix (CRM) document that tracks and manages industry feedback on draft solicitation materials for the Space Data Network Backbone (SDN-B) Mission Operations Center (MOC) procurement. The matrix serves as a template and instructional document defining three types of comments—Critical (C), Substantive (S), and Administrative (A)—along with corresponding decision categories: Accept (A), Reject (R), and Partially Accept (P). Critical comments address violations of law or policy, safety risks, waste of appropriations, unreasonable resource burdens, or concerns that would cause reviewer non-concurrence. Substantive comments identify unnecessary, misleading, confusing, or inconsistent sections, or disagreements with proposed responsibilities, requirements, or procedures. Administrative comments address non-substantive aspects such as dates, organizational symbols, formatting, and grammar.
The underlying procurement context involves the Space Systems Command Spectrum Warfare Division planning to award a single-award, Firm Fixed Price (FFP) Indefinite Delivery/Indefinite Quantity (IDIQ) contract for SDN-B MOC operations. The government released draft Statement of Work (SOW) and Technical Requirements Document (TRD) documents containing Controlled Unclassified Information (CUI) for industry feedback prior to the Commercial Solutions Opening (CSO) solicitation anticipated for release on April 30, 2026. Industry feedback was solicited through an Industry Day held on April 22, 2026, and interested parties could request CUI materials through a formal security vetting process managed by the Space Force security team, requiring submission of company information, CAGE codes, UEI, and compliance with NIST SP 800-171 and DFARS 252.204-7012 requirements for protecting CUI.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| MOC Industry Day Instructions - Amendment 2.docx | DOCX document | |
| MOC Industry Day Instructions - Amendment 1.docx | DOCX document | |
| (U) MOC Industry Day Announcement Final - updated 17 APR 26.docx | DOCX document | |
| (U) MOC Industry Day Announcement Final - updated 15 APR 26.docx | DOCX document | |
| (U) MOC Industry Day Announcement Final.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SDN-B MOC CRM
| POC | Type | ||||
| (C/S/A) | Document | Section, Page, Line | Comment/Question | Rationale | Decision |
(A/R/P) (Gov Use) Response (Gov Use)
Definitions
| Type | ||
| C | Critical | Critical comments MUST identify (1) violations of law or contradictions of Executive Branch, DoD, or Air Force/Space Force policy; (2) unnecessary risks to safety, life, limb, or DoD materiel; (3) waste or abuse of DoD appropriations; (4) imposition of an unreasonable burden on a Component’s resources; or (5) a concern that, if unresolved, will cause the reviewer to non-concur. |
| S | Substantive | Make a substantive comment if a part of the issuance seems unnecessary, misleading, confusing, or inconsistent with other sections, or if you disagree with the proposed responsibilities, requirements, or procedures. |
| A | Administrative | An administrative comment concerns non-substantive aspects of an issuance, such as dates of reference, organizational symbols, format, and grammar. |
| Decision | ||
| A | Accept | |
| R | Reject | |
| P | Partially Accept |
File details come from the government source that posted it. Updated .