====== 15.1 Overview ======
[[fxdemo:03-part:15-relationship-to-implementation-profiles-psm:start | Go To Relationship to Implementation Profiles / PSM ]]

An Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] maps the FX Demo Logical Profile to selected implementation technologies, data representations, communication mechanisms, runtime packaging approaches, and implementation artefacts.

This part defines the platform-independent FX logical profile. An Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] defines how a selected implementation realises that profile. The implementation profile preserves the FX logical meaning of FX logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Nodes]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node_role|Node Roles]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], information structures, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], interaction patterns, governance relationships, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships.

An Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|PSM]] does not redefine the Part 1 Conceptual Architecture, the Part 2 Logical Architecture / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]], or the FX Demo Logical Profile. It provides technology-specific mappings from FX logical elements to implementation artefacts.

----

<WRAP centeralign>

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

</WRAP>