Annex C: Requirements
This annex contains the authoritative requirement records for the Structured Information Processing Reference Architecture (SIP-RA) Request for Proposals.
Each requirement record provides a stable identifier, short title, normative Statement, requirement level, rationale, evaluation criteria, and backlinks to the sections in which the requirement is referenced.
Requirement Identifiers
The requirement register contains two requirement families:
| Prefix | Requirement Family | Description |
|---|---|---|
| GPR | General Proposal Requirement | Identifies a general OMG proposal requirement or evaluation criterion principally derived from Section 5 |
| SIP | Structured Information Processing Requirement | Identifies a requirement specific to the proposed Structured Information Processing Reference Architecture principally defined in Section 6 |
The numeric portion of each identifier is unique within its requirement family. The identifier remains stable when the requirement is referenced from multiple sections.
The prefix identifies the requirement family. It does not indicate whether the requirement is mandatory, recommended, optional, or conditional.
General Proposal Requirements
General Proposal Requirements govern the general structure, quality, compatibility, security, internationalization, and evaluation of a Submission.
Structured Information Processing Requirements
Structured Information Processing Requirements govern the scope, architectural abstractions, modeling, Governance, integration, conformance, required Submission content, and traceability of the proposed SIP-RA specification.
Notes for Editors
This annex contains the authoritative requirement records. Statements displayed elsewhere in the RFP should be transcluded from the corresponding Annex C pages.
Requirement identifiers remain stable. Do not renumber existing requirements when inserting a related requirement. Use an alphabetic suffix when necessary to preserve established identifiers.
The two Indexmenu statements read the same namespace. Each uses a skipfile+ expression to exclude the other requirement family.
Requirement filenames begin with either gpr- or sip-, followed by the three-digit requirement number and short title.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.