EXIN SIAM Professional Bridge based on the Scopism SIAM BoK V3 key terms

A management approach that coordinates multiple internal and external service providers so they deliver a single, seamless set of business services to the customer, covering governance, integration, and end-to-end accountability.

The complete network of parties involved in delivering integrated services: the customer organization, the service integrator, internal and external service providers, and supporting governance bodies, all linked by contracts, agreements, and shared processes.

The organizational entity accountable for coordinating service providers, integrating their outputs into end-to-end services, and managing cross-provider processes, performance, and relationships on behalf of the customer.

Any internal or external organization that supplies one or more services or service components within the SIAM ecosystem, operating under agreed contracts and integrated processes defined by the service integrator and customer.

An activity, skill, or control the customer deliberately keeps in-house rather than delegating, typically to preserve strategic direction, governance, commercial leverage, or knowledge over the integrated service landscape.

The part of the customer's own organization that remains after outsourcing decisions, holding retained capabilities and typically owning governance, strategy, demand, and oversight of the SIAM ecosystem.

The set of activities that combine outputs from multiple providers into coherent, end-to-end services, including process integration, data and tooling alignment, cross-provider coordination, and performance management.

A service experienced by the business as a single outcome, delivered through the combined contributions of several providers, with accountability and performance measured across the whole chain rather than per provider.

The principle that one party is answerable for the complete delivery and performance of a service across all contributing providers, removing gaps where responsibility would otherwise fall between organizations.

An individual element of a larger service, such as an application, infrastructure element, or support process, supplied by a provider and combined with other components to form the end-to-end service.

The chosen structural design for a SIAM ecosystem, describing where integration responsibility sits, how many integrators exist, and how providers and the customer relate, for example internally sourced, externally sourced, or hybrid.

A SIAM structure in which integration responsibility is shared between an internal integrator function and one or more external integrators or providers, balancing control and cost against capability and scale.

The collaborative attitude and behaviors required in SIAM, emphasizing shared goals over organizational boundaries, transparency, trust, collective problem-solving, and accountability for customer outcomes rather than individual provider performance.

Working jointly across customer, integrator, and provider boundaries with shared objectives, open communication, and joint decision-making, so that issues are resolved collectively rather than escalated through contractual blame.

A SIAM principle requiring open sharing of performance data, risks, incidents, and decisions among ecosystem parties, so that cooperation is grounded in visible facts rather than concealed information or defensive reporting.

The decision-making structures and mechanisms that set direction, assign authority, define policies, and ensure the SIAM ecosystem meets business objectives, typically owned by the customer's retained organization.

A cross-organizational forum where customer, integrator, and provider representatives make joint decisions on priorities, escalations, policy, and performance, providing the main strategic and tactical oversight mechanism in the ecosystem.

A documented mapping of who does what across the SIAM ecosystem, clarifying ownership of each process, activity, and decision so that accountability is explicit and gaps or overlaps are avoided.

The role accountable for the design, performance, and continual improvement of a single process across all providers, ensuring consistent execution and end-to-end measurement regardless of which organization performs the work.

Aligning processes such as incident, change, and request management across providers so they operate as one coherent flow with common definitions, interfaces, data, and escalation paths.

Connecting the systems used by different ecosystem parties, such as service management platforms and monitoring tools, so data and workflows are shared consistently and a single view of service status is possible.

A repository holding records of configuration items and their relationships, used in SIAM to give all providers a shared, trustworthy view of the infrastructure and services they jointly support.

Any component under configuration control whose state and relationships are recorded, such as hardware, software, documentation, or a service, forming the basis for impact analysis across providers.

A documented commitment between a provider and its customer defining expected service levels, responsibilities, and remedies, which in SIAM must be aligned with the end-to-end service targets.

An internal agreement between teams or providers that supports delivery of an SLA, defining the contributions and targets each party must meet so the end-to-end commitment can be achieved.

A contract with an external supplier that supports delivery of services to the customer, specifying obligations and service levels that must be consistent with the wider SLA commitments.

The practice of negotiating, agreeing, monitoring, and reporting service levels, and in SIAM also reconciling provider-level targets with the end-to-end targets the business actually cares about.

Observing and measuring a service across all providers as one chain, using shared data and integrated tooling, so that degradation is detected and attributed quickly rather than discovered provider by provider.

The defined process for raising an issue to a higher authority or across organizational boundaries when resolution stalls, with clear triggers, paths, and timeframes agreed across the ecosystem.

The practice of restoring normal service as quickly as possible, which in SIAM requires shared priority definitions, cross-provider diagnosis, and a clear owner for end-to-end coordination.

The focused handling of high-impact incidents through a designated coordinator, joint technical bridges, and rapid communication, ensuring multiple providers act as one team under end-to-end leadership.

The practice of assessing, approving, scheduling, and reviewing changes, which in SIAM must coordinate across providers so that one party's change does not disrupt another's service.

Handling routine user requests through a single, consistent entry point, with integrated catalogues and fulfilment workflows spanning whatever providers actually deliver the requested items.

A structured description of services available to users, which in SIAM should present end-to-end services and their underlying providers so demand can be routed correctly and transparently.

Capturing, maintaining, and sharing information across ecosystem parties so that any provider can resolve issues using consistent, current knowledge rather than rediscovering solutions in isolation.

Defining, measuring, reporting, and reviewing service and provider performance against agreed targets, using balanced measures that encourage collaboration rather than narrow local optimization.

A quantified measure chosen to show how well a critical objective is being met, used in SIAM to track both end-to-end service outcomes and individual provider contributions.

Producing regular, consistent information on service performance and issues for governance bodies and the business, integrating data from all providers into a single coherent view.

The ongoing practice of identifying, prioritizing, and implementing enhancements to services and the SIAM ecosystem itself, using measurement, feedback, and joint review across all parties.

A phased plan for moving from the current sourcing and service arrangements to the target SIAM model, covering design, transition, and stabilization stages with defined milestones and risks.

The stage in which services, contracts, processes, and staff are moved into the new SIAM arrangements, requiring careful sequencing, communication, and knowledge transfer to avoid service disruption.