The MUSING platform will feature many SOA principles at different levels, both for their desirability in designing such a distributed, large-scale system, and for the specific requirement that some of the components involved in the delivery of MUSING-based services be intimately immersed in a company's business process or workflow.

At the foundation level, the organisations responsible for the development of key technical components are exploiting their expertise and know-how, and are tackling the relative problems by modular steps, each producing components (either delivered as actual services, or software elements) whose functionality is extremely well defined, as widely acknowledged in literature, including the most cutting-edge solutions.

This ensures an extremely flexible composability of those elements, for their functional characteristics are formally defined, even when those components are to interact with each other.

At the service level, the MUSING platform foresees, within each of its vertical streams, the integration with the final user service deliverer, and it therefore becomes a necessity to keep the functionalities loose-coupled and based on stable standards of communication. This ensures ease in the setting up of a new MUSING service without low-level adjustments.

Technically, the transport for the service invocation is WebServices, whereas data communication is based upon acknowledged representation standards (such as XBRL for business reporting). The extensive use of carefully crafted, and standard abiding ontologies within MUSING guarantees wide applicability and enforces the multi-industry requirement of the initiative, by providing several possibilities concerning semantic interoperability.