An employee expense portal stops accepting sign-ins. The service desk needs to know whether the problem affects that portal alone or a shared sign-in service used by other applications. A platform demonstration should show how quickly an agent can find that information and who can act on it.
That is a more revealing test than a feature list. Two IT service management platforms can both offer configuration records, automated workflows, and self-service while requiring very different amounts of work to make those features useful.
Start with a service your team can test
Choose a service your organization relies on that depends on several components or teams. In the expense portal example, those dependencies might include the application, a shared sign-in service, and an external provider.
When evaluating European ITSM software, including Matrix42, give each vendor the same scenario and ask how its platform connects the relevant records. Decide in advance what an agent should be able to find. For Matrix42, ask which components of the proposed package support those relationships and how the records would be populated from your existing tools.
Starting from a report that employees cannot sign in, can the agent locate the expense portal, identify its dependency on the sign-in service, and find the responsible team? Have a service-desk employee perform the steps rather than relying solely on the vendor’s presentation.
Check how configuration information connects to work
A configuration management database, or CMDB, holds information about components relevant to IT services, often called configuration items. It can also record relationships between them. Those items might include applications, servers, or services.
An asset inventory may tell a team what technology it owns and who is responsible for it. A CMDB can add a view of how components support one another. Their records can overlap, but they serve different purposes.
For the portal test, ask the vendor to show the relationship between the application and the sign-in service from both directions. Check whether an agent can reach that information from the service record without searching several separate systems.
Then introduce an incomplete record. If the sign-in service is shared by several applications, how would the agent recognize a missing relationship? A clear diagram helps, but the team also needs to know which dependencies are confirmed and which still need checking.
Test the work needed to keep records useful
During the demonstration, ask the vendor to change the portal’s support owner. Who can approve the update? When does it take effect? Another agent should be able to see the change history and identify the current owner.
Examine where the records come from. Staff may enter some information, while other fields are imported from existing tools. Ask how often imports run and what happens when two sources give different owners or names for the same component.
Find out how the platform identifies records that have not been reviewed recently. Discovery tools can reduce manual entry, but someone still needs to decide which information matters and check it. Estimate that recurring work with the people who would do it, as well as the procurement team.
Assess workflows, deployment, and support
Use the same scenario to test the wider workflow. Can an agent connect related reports to the affected service? Can a change coordinator see which teams should review a proposed change? On the employee-facing side, check whether users can find the right request and understand its status.
For organizations operating across European locations, examine language coverage in the employee portal, administrator interface, documentation, and support. A translated portal does not necessarily mean administrative tasks and support are available in the same language.
Deployment deserves a separate review. Vendor-managed cloud, private-cloud, and on-premises arrangements can place different responsibilities on the customer for updates, backups, and monitoring. Ask where data is stored, which organizations provide supporting services, and how access is controlled. Hosting location and vendor domicile are distinct questions, so involve the appropriate privacy and legal advisors when reviewing the answers.
Compare the full cost of operating each option
An agent-license quote is the starting point. Ask vendors to identify charges for configuration management, integrations, additional environments, training, and support. Check whether the demonstration used features in the proposed package or separately priced modules.
Account for internal effort too. Someone must configure workflows, maintain integrations, review configuration records, and test upgrades. A lower subscription price may come with greater demands on administrators or outside assistance.
Record each platform’s results against the scenario, including missing capabilities and assumptions about who will maintain the data. Separate requirements that must be met before purchase from improvements that can wait. That comparison gives decision-makers more to work with than a collection of checked feature boxes.