4.8 Proof of Concept

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 prototypedAn implementation of this specification has been in beta test for four monthsA named product with a specified customer base realizes this specificationSubmitters 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.

—

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.