Platform module · Enterprise Architecture
See what depends on what, and what it is worth.
Capabilities, applications, data and technology in one connected model, each linked to the goals it serves. Architecture stops being a drawing and becomes the map every other module works from.
- Which applications carry this business capability?
- What else goes down if this server or supplier fails?
- Which assets serve no goal at all?
- What reaches end of life next, and what is it worth today?
What it covers
Four layers of architecture, one model.
Each element is an asset in the shared inventory, with an owner, a lifecycle phase and a value score. Relationships between them are first-class records, not lines on a slide.
Capabilities and value streams
What the organisation does, independent of who or what does it. The bridge between goals and systems.
Portfolio and integrations
Every application, its interfaces and its consumers, ready for rationalisation decisions.
Data assets and flows
Which data lives where, who owns it, and which applications create, read and move it.
Infrastructure and standards
Servers, networks and cloud services under the applications, with the standards they should follow.
Security architecture runs across all four, and architecture governance keeps the model honest.
Linked to goals
From a board goal down to the server.
Because every element is linked to the goals above it, criticality flows down the chain. The infrastructure under a critical application inherits why it matters.
Impact before change
Select any element and see everything that depends on it, upwards to goals and downwards to technology, before you approve a change.
Value at stake
The value scores of every dependent asset add up to what an outage would put at risk, so resilience spending follows value.
Orphans and overlaps
Assets that serve no goal score zero. Two applications serving the same capability show up side by side.
Inside the module
What architects work with every day.
Part of one platform
One line on the map, sharing every station.
Enterprise Architecture runs through capabilities, applications, infrastructure and data. Risk, work and service management stop at the same stations, so the model you build here is the one they use.
Risks on real assets
Risks and controls attach to the applications and infrastructure you mapped, with their value already known.
Roadmaps become work
Retirements, migrations and standard changes turn into tracked projects and tasks.
One configuration model
Incidents and changes point to the same elements, and their impact is read from the same dependencies.
Start with Core and Enterprise Architecture.
Map what you have, link it to your goals, and see the value of your landscape in the first weeks.