An employee loses access to a business application. The service desk logs the issue, but one provider manages the application and another looks after its infrastructure. Both have a part to play, and the desk needs to keep track of their work.
For an organization choosing an IT service management (ITSM) platform, this is a useful test. Can the people involved share information and coordinate an incident across organizational boundaries?
What service integration and management means
Service integration and management, or SIAM, is an approach to coordinating services delivered by multiple internal and external providers. A service integrator oversees how those parties work together and keeps sight of the service as a whole. An internal team, an external organization or a combination of both can take on that role.
SIAM is an operating approach, not a software product. The organization must agree on responsibilities and escalation, while Service management software can help teams track incident records and handoffs across providers.
Start with one shared incident
Ask each shortlisted vendor to demonstrate the application outage from start to finish. The service desk creates an incident, sends work to the application provider and brings in the infrastructure provider when further investigation is needed.
Give every vendor the same starting information: the affected service, symptoms, provider responsibilities and the systems each party uses. Leave the cause unresolved. The demonstration should show how the providers collaborate when the service desk does not yet know where the fault lies.
Matrix42 Service Management includes incident management. As with other candidates, its fit for the organization’s provider arrangements should be assessed through the same scenario.
Follow the record across providers
Start by checking what each party receives. Can the application provider see the affected service, symptoms and relevant diagnostic details without the service desk copying them into an email? If providers use separate systems, ask the vendor to show how records are linked and which fields, comments and attachments pass between them.
Next, have the application provider add a finding and ask the infrastructure provider to investigate. Can the coordinating team see that the request was sent and accepted? An “assigned” status tells the desk little if it cannot see whether the receiving team has picked up the work.
Test an exception, too. Ask what happens if an update fails to reach a provider’s system. Look for an alert, a way to identify the affected record and a practical recovery process. Establish who would investigate the failure and how the teams would coordinate while the connection is unavailable.
Check ownership, progress and access
During the demonstration, identify the person or team accountable for the overall incident and the provider responsible for each action. Ask how those responsibilities appear when both providers are investigating at once. Passing a task to a supplier should leave the coordinating team with a clear view of who is doing what.
The service desk also needs more detail than a single “in progress” label. It should be able to see what each provider has done, what it is waiting for and when it last updated the record. Ask to view the history of assignments and changes, with enough context to reconstruct a disputed handoff.
Access deserves a separate test. Sign in, or ask the vendor to demonstrate the view, as each provider. Can the application provider see the relevant incident while unrelated tickets remain private? Can sensitive notes and attachments be restricted while operational updates remain available to the people who need them?
Ask how access is removed when a provider’s employee leaves or the contract ends. The answer should cover both shared platform accounts and any connections to the provider’s own system.
Examine European operating requirements
For an organization operating across Europe, several parties may view or process the incident record. Ask where data and backups are stored and processed, which providers or subcontractors can access them, and where support staff are located. Check those arrangements against the deployment being quoted, including any integrations.
Confirm the languages, support hours and escalation channels available to your teams and providers. If work crosses time zones, ask how the service desk will identify the next contact when one provider’s shift ends.
Compare the evidence
Record what each vendor demonstrated, what requires configuration or a separate integration, and what still needs proof. Ask who would build and maintain connections between provider systems, and include that work in the cost assessment.
A shared ticket is a starting point. The stronger evidence is whether the right people can act on it, see the next step and recover when an update fails to arrive.