| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:01-fdis-ra:01-introduction:01-5-intended-audience:01-5-4-technology-providers-and-integrators:start [2026/07/10 13:26] – nick_dido | dido:01-fdis-ra:01-introduction:01-5-intended-audience:01-5-4-technology-providers-and-integrators:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[dido:01-fdis-ra:01-introduction:01-5-intended-audience:start|Return to 1.5 Intended Audience]] | [[dido:01-fdis-ra:01-introduction:01-5-intended-audience:start|Return to 1.5 Intended Audience]] |
| |
| Commercial and non-commercial solution providers develop platforms, tools, components, and services that support the interpretation and validation of regulated data. These providers include vendors, system integrators, service organisations, and implementation partners operating across regulatory, supervisory, and cross-agency contexts. | Commercial and non-commercial solution providers develop platforms, tools, components, and services that support the interpretation and validation of regulated data. These providers include vendors, system integrators, service organizations, and implementation partners operating across regulatory, supervisory, and cross-agency contexts. |
| |
| This audience includes providers supporting agency-specific implementations of the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:f:FDTA]] joint data standards after the appropriate agency applies those standards to a collection of information. | This audience includes providers supporting agency-specific implementations of the [[dido:99_annexes:annex-b-terms-and-definitions:f:fdta]] joint data standards after the appropriate agency applies those standards to a collection of information. |
| |
| For these stakeholders, the [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:reference_architecture]] provides a structured basis for aligning offerings with defined architectural responsibilities, governed interfaces, lifecycle controls, conformance points, and quality attributes. | For these stakeholders, the [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture]] provides a structured basis for aligning offerings with defined architectural responsibilities, governed interfaces, lifecycle controls, conformance points, and quality attributes. |
| |
| FDIS-RA enables providers and integrators to demonstrate architectural fitness, interoperability, traceability, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:semantic]] governance alignment without prescribing specific technologies, products, platforms, deployment models, or implementation approaches. | FDIS-RA enables providers and integrators to demonstrate architectural fitness, interoperability, traceability, and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic]] governance alignment without prescribing specific technologies, products, platforms, deployment models, or implementation approaches. |
| |
| ---- | ---- |
| |
| <WRAP centeralign> © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. </WRAP> | <WRAP centeralign> © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. </WRAP> |