Multisite operations

How SaaS Management Platform is set up for you

Distributed teams need a recognizable service name and an owner when an application problem affects more than one location. The service record carries the owner, criticality and status. Asset records add a tag, location and service reference when equipment is involved. Incidents and changes then point to the service without collapsing their different histories into one note.

Start with one service used at a few locations and name its owner. Link representative assets with tags and locations. When a location reports an interruption, open an incident against the service and affected asset, set priority and assign a technician. The technician can record what was checked and when, while the manager sees the current state in the open incident list.

If a configuration change is needed, prepare a separate change with risk, scheduled start and end, and a rollback plan. The Change Approver decides on that planned work. A service incident can stay open while a change is in review, and its response dates remain intact after the change is verified.

Add a subscription for an application supporting the service when renewal and allocation review are needed. Its owner and usage records answer licensing questions; the service and incident records answer operational ones.