No rule per team.
Routing reads the responsible service and team from the object. One rule covers every service, and a new service is a data change.
Free download&w=3840&q=75)
Your service desk needs a brain.
We start from the decisions the process should make alone, not from your inventory. Which questions must never reach a human?
How Assets stay idle
The schema answers one question: what do we own. Objects sit side by side without references, so the model can describe your estate but never decide anything. With no references there is nothing for logic to read. The agent becomes the missing link, doing a lookup from a table in their head. So each case gets its own hardcoded rule. Fifty services, fifty rules, and every new one is a change request against your own tooling. The import ages, the rules drift apart, and the verdict becomes that Assets does not work here. Data quality is not a phase, it is a job.
Logic that scales
No SLA per service.
SLA targets come from object attributes and conditions, so a production service and a test system never share a clock.
No approver list.
Escalation and approval follow the roles stored on the object. The right person is derived, never looked up.
No guessing.
AQL resolves from the reporter to their own objects, so the portal offers only what that person actually has.
&w=3840&q=75)
Why MESKRU?
We sat on your side of the table. Before MESKRU existed, MESKRU founders Manuel Mesmer and Alexander Kruse were the responsible internal Atlassian team of a large European company.
We don't hand you a blank page. Our Asset Scheme Blueprint is a documented JSM use case library.
One rule covers every service. Generic logic reads its parameters from the object, so one rule covers ten services or four hundred.