IT Financial Management (ITFM)
See what a system costs across licences, infrastructure and vendor contracts, who owns that spend, and which renewals are due in the next quarter.
IT financial management
STATE3 Enterprise
One graph. Many lenses.
Application portfolio, risk, cost, change and service management are usually five tools holding five versions of the same organisation. In STATE3 Enterprise they are five views of one model. The risk you record against an application sits on the same application the cost is attached to, and the same one the change board is about to touch. The architecture is the model itself rather than a diagram kept beside it.
One organisation. Many ways to understand it.Enterprise architecture · one connected model
Choose a lens
Every view draws on the same records and relationships
Select a lens to follow its connections.
Your AI assistant can query this model through MCP →
The capabilities
Many lenses on the same graph.
Each one answers a different kind of question. They share one model, so an answer from one is usable in another. Two audiences have their own way in: organisational context for IT operations and technology intelligence for CIOs.
Request Management
Requests of every type, tracked from intake to close. Before a change is approved, see what it touches: the applications, services, processes, people and risks connected to it.
request and change management
Application Portfolio Management (APM)
See what an application costs, who owns it, which business capabilities it supports, what depends on it, and whether something else already does the same job.
application portfolio management
Risk Management
Attach a risk to the application, vendor, service or business activity it sits on. Record the owner and treatment, then see what else is exposed through those connections.
technology risk management
IT Service Management (ITSM)
Link services to the applications and infrastructure beneath them, so an incident on a server reads as the business services it affects. Where there is no separate service desk, STATE3 handles the requests too.
IT service managementThe AI layer
Every view above is queryable through MCP. An authorised AI client puts the question to STATE3, and STATE3 answers within the permissions that user already has.
See the MCP interface
Why one platform
Because the answers live between the silos.
Most tools hold either the business view or the technology view. The questions that hold up a decision sit across the join. Which business process depends on this server. What an application costs once the contract is included. Who has to sign off if it changes. Answering those means one model, not two well-integrated ones.
Two routes in
Automated feeds and ingestion-hub imports are staged and reconciled before they're written to the model. Entity-specific imports, direct edits and MCP writes are validated and written straight to the graph. How STATE3 stays current.
Impact assessments across 14+ entities
Trace what a change touches before committing to it, and follow the link from one impact report into the next.
Enterprise architecture views
Technology maps, infrastructure dependency diagrams, application-to-capability views, and current-versus-future-state scenarios, all drawn from the same model.
Enterprise architecture
Enterprise architecture in business language
STATE3 describes your organisation in words the business already uses: applications, services, capabilities, business activities, owners and costs. There is no framework notation to learn, so the architecture team, a finance manager and a service owner can read the same model and talk about the same thing. We keep it simple on purpose, because a model only helps when the people making decisions can read it.
How the model is organised
Workspaces
Each workspace is a model of the organisation kept for one purpose: the current state, a future state you're designing, a what-if to test an idea, or the changes in one request. Compare a future workspace with the current one side by side, and deploy it once the change is made. A what-if merges back if you decide to keep it.
The Library
Your organisation's master list. Technologies, capabilities, business activities, roles, business units and people are defined once in the Library and used in any workspace. A workspace item linked to the Library shows the Library's values, so a correction made once appears wherever that item is used. Request types can read from the Library too.
Consolidation
Combines several workspaces into one read-only view of the whole organisation and removes the duplicates. Items are matched by the Library entry they're linked to, so a technology recorded by five departments appears once. The view is rebuilt on a daily, weekly or monthly schedule, with current and future states consolidated separately.
The modules and tools that support it
Application Portfolio Management
Applications linked to the business and technology capabilities they support, with their owners, costs and overlaps.
Application portfolio management
IT Financial Management
What each application and service costs, from licences, infrastructure and contracts.
IT financial management
Risk Management
Architecture principles are recorded as the source of risk, and the findings of an architecture assessment are recorded as risks with an owner.
Technology risk management
Request Management
Architecture assessments and change requests run as requests, and a change's impact is visible before it's approved.
Request and change management
IT Service Management
Business services linked to the applications and infrastructure beneath them.
IT service managementAlso in the platform
Business and technology capability hierarchies, diagrams (including BPMN, flowcharts and org charts), a data map, a business glossary and dependency analysis.
Working with your framework
If your team works with TOGAF, ArchiMate or ITIL, STATE3 models the same things in the business's own words, so the architecture can be shared well beyond the architecture team.
TOGAF
Your baseline and target architectures become current and future workspaces. Compare them to see the gap, and deploy the target once the change is made. Architecture principles drive architecture assessments, and their findings are tracked as risks.
How STATE3 supports TOGAFArchiMate
Business, application and technology layers in one connected model: business units, roles and activities, linked to the applications they use and the infrastructure those run on, drawn in plain shapes anyone can read.
ITIL
Business services are linked to the applications and infrastructure that deliver them, so an incident reads as the services it affects. Change requests come with an impact assessment before anyone approves them.
Capability models
Business and technology capabilities in a hierarchy as deep as you need, each linked to the applications and business activities that deliver it.
Process models
Business activities and process flows record who does what, with which systems, how often and at what cost. Draw them as BPMN when you need the detail.
Data governance
A business glossary gives each term one agreed meaning and an owner, linked to the data that holds it. The data map and CRUD matrix show how data relates and which systems change it.
See STATE3 drawn as ArchiMate, TOGAF and Zachman →
STATE3 is not certified against these frameworks.
See it on your own estate.
A tailored demo runs on data shaped like yours, so you can judge it against an environment you recognise rather than a sample one.