public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-7-rfp-traceability:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-7-rfp-traceability:start [2026/09/12 18:33] – removed - external edit (Unknown date) 127.0.0.1public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:06-4-7-rfp-traceability:start [2026/09/14 18:55] (current) – [Requirements] nick_dido
Line 1: Line 1:
 +====== 6.4.7 RFP Traceability ======
  
 +[[public:00-sip-ra:06-specific-requirements-on-proposals:06-4-required-submission-content:start|Return to Required Submission Content]]
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] establishes an explicit correspondence between the requirements of this RFP and the locations within the Submission where those requirements are addressed.
 +
 +===== Requirements =====
 +
 +^ Requirement ^ Statement ^
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-056-rfp-traceability-map|SIP-056 — RFP Traceability Map]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-056-rfp-traceability-map#Statement&noheader&nofooter&noeditbtn}} |
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-057-requirement-to-specification-traceability|SIP-057 — Requirement-to-Specification Traceability]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-057-requirement-to-specification-traceability#Statement&noheader&nofooter&noeditbtn}} |
 +| [[public:00-sip-ra:99-annexes:annex-c-requirements:sip-058-incomplete-requirement-disclosure|SIP-058 — Incomplete Requirement Disclosure]] | {{section>public:00-sip-ra:99-annexes:annex-c-requirements:sip-058-incomplete-requirement-disclosure#Statement&noheader&nofooter&noeditbtn}} |
 +===== Note =====
 +
 +> Annex C provides the authoritative requirement records for this RFP. Sections 5 and 6 organize those requirements within their applicable context and display their authoritative Statements by transclusion from Annex C.
 +
 +> Identifying an incompletely satisfied mandatory requirement does not make the Submission conformant with that requirement or waive the requirement. Any determination concerning acceptability remains subject to the applicable OMG process.
 +
 +===== Notes for Editors =====
 +
 +The links to SIP-056 through SIP-058 provide temporary access to their individual Annex C requirement pages while those records are being created and reviewed.
 +
 +After those records are complete, replace each locally maintained Statement with a transclusion of its authoritative Statement.
 +
 +Every normative requirement in Sections 5 and 6 should have a corresponding authoritative record in Annex C. Section pages should transclude the Statement from that record rather than maintain a separate copy.
 +
 +SIP-056 requires the traceability-map deliverable. SIP-057 defines its required mappings and satisfaction information. SIP-058 requires transparent identification of requirements that are not fully satisfied.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>