4.8 Proof of Concept [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 4.8 Proof of Concept ======

[[public:00-sip-ra:04-instructions-for-submitters:start|Return to Instructions for Submitters]]

Submissions SHALL include a proof of concept statement explaining how the submitted specifications have been demonstrated to be technically viable.

Technical viability concerns the state of development and maturity of the technology on which a Submission is based. Technical viability differs from commercial availability.

Proof-of-concept statements can contain any information the submitter deems relevant. Examples include:

  * This specification has completed the design phase and is in the process of being prototyped
  * An implementation of this specification has been in beta test for four months
  * A named product with a specified customer base realizes this specification

Submitters SHALL demonstrate the technical viability of their proposal to the satisfaction of the Task Force managing the evaluation process.

OMG favours proposals based on technology for which sufficient relevant experience has been gained.

---

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>