STATE3 Enterprise / ITSM

IT Service Management.

It is 2am and SQL cluster 02 is down. Monitoring tells you which server. STATE3 shows you that payroll runs on it, and who needs to know.

One server down, and what it reaches Four layers from bottom to top: infrastructure, applications, services and people. SQL cluster 02 is down. Finance ERP and Payroll Cloud run on it, so the Month-end close and Payroll run services are affected, and Finance Systems and the Payroll team need to be told. App server 04, File store 01, the HR Portal, the CRM, Leave requests, Rates billing, People and Culture and the Contact centre are not affected. PEOPLE SERVICES APPLICATIONS INFRASTRUCTURE Finance Systems Payroll team People & Culture Contact centre Month-end close Payroll run Leave requests Rates billing Finance ERP Payroll Cloud HR Portal CRM SQL cluster 02DOWN App server 03 App server 04 File store 01
  • SQL cluster 02Down
  • Finance ERPApplication
  • Payroll CloudApplication
  • Month-end closeService
  • Payroll runService
  • Finance SystemsTell
  • Payroll teamTell
Failed Affected Who to tell Not affected Illustrative estate
When something breaks

What an outage means for the business.

  • What is affectedThe applications and services on the failed server.
  • Who to tellThe owners recorded against each one.
  • What was already openRisks and changes in progress on the same record.
  • Who to callThe support contract and the vendor contact.

Where you already run a service desk, STATE3 supplies this context beside it. Where you don't, STATE3 handles the requests as well. The same connections read from the operational end are in organisational context for IT operations.

Example · Microsoft 365 Copilot → STATE3 via MCP
SQL cluster 02 is down. What does it affect?
lookingfollowing what runs on it, up to the services…
ServicesPayroll run · Month-end close ApplicationsPayroll Cloud · Finance ERP OwnersFinance Systems · Payroll team Risks1 open · treatment in progress Request1 upgrade in review Contracts1 support contract · vendor contact linked

An illustrative question and answer. In STATE3 it comes from your own records, in the app or through an AI assistant over MCP.

What ITSM does

The catalogue, the impact and the requests.

Catalogue One service catalogue

Business services, applications, infrastructure and integrations in one catalogue, with an owner on each.

  • Business services linked to the applications and infrastructure that deliver them
  • Technology, process and business ownership assigned
  • On-prem, cloud and hybrid sources brought in by the STATE3 ingestion engine
  • Lifecycle dates on the technology each service runs on

Impact Read an event as the services it affects

Start from the server or application that has a problem and follow the links up.

  • Infrastructure Map: relationships between servers and supporting infrastructure
  • Technology Map: how applications connect and depend on each other
  • Impact reports across 14+ entity types, followed from one report into the next
  • Open risks and changes in progress shown against the same record

Requests Request handling without a separate service desk

Where there is no service desk to route requests to, raise and track them in STATE3.

  • Service requests tracked from intake to close
  • A workflow with approvers for each step
  • Change requests and your own request types are covered by Request Management

Current-state and future-state models, what-if scenarios and capability maps are covered under enterprise architecture.

Use STATE3 Enterprise ITSM for…

Incident impact

See which services and owners an outage reaches before you send the first update.

Service catalogue management

One catalogue across infrastructure, applications and integrations.

Operational reporting

Reports that reflect today's state, not last quarter's snapshot.

Service requests

Raise and track requests in STATE3 where there is no separate service desk to route them to.

Explore other capabilities

Modules that read the same model.

See your own services this way.

Book a 30-minute discovery call and we'll walk through ITSM with you.