“Is our architecture work connected to the money and the roadmap?”
Every phase of the ADM, from Preliminary through Phase H and Requirements Management, plus the content metamodel, the Enterprise Continuum and the architecture repository — run on the model your strategy, budgets and portfolio already use. The baseline is read from the live estate. Transition and target architectures are priced from the ledger. Work packages become funded initiatives. Tailor the ADM and the metamodel as the standard intends; when The Open Group revises it, your repository is remapped, not re-imported. And BIZBOK, APQC and app rationalization share the same capabilities and applications.
The pressure
Architecture vision, baseline, target and roadmap are written into a repository the budget never reads. The Phase F work packages are re-typed into the portfolio tool. The price of the target is a spreadsheet estimate. Phase G reviews happen in a meeting that leaves no record. By the time Phase H fires, the baseline the cycle started from is already out of date.
What it looks like today
Full coverage
Each phase, artifact and repository area is kept as live records rather than documents, alongside strategy, cost and the portfolio.
Built for the TOGAF Standard, 10th Edition
Preliminary, Phase A and the requirements at the center.
Phases B, C and D, read from the live estate.
Phases E and F, priced.
Phases G and H, dated and attributed.
The metamodel and what it produces.
Where architecture knowledge lives.
What changes
ADM deliverables written once per cycle
ADM outputs kept as records the next cycle starts from
A target architecture as a picture
Baseline, transition and target, each with a price
Work packages handed off and lost
Work packages as funded initiatives, still linked to the gaps they close
Architecture governance as a meeting
Conformance, waivers and decisions dated on the record, beside the change they govern
Phases G and H, on live records
Start from a work package or a change request, and Dotwork follows the model out to the capabilities, applications, teams, controls, contracts and earlier decisions it touches, each with the cost it carries. The impact assessment the architecture board reads and the architecture contract delivery signs up to come from the same records — so Phase G and Phase H start from facts, not a fresh round of interviews.
Where other tools stop
EA repositories hold the models. The cost, the contracts and the controls live in other tools, so every impact assessment is assembled by hand before every board.
Flexed to how you run
The standard expects every organization to adapt the ADM and the metamodel. Dotwork keeps the TOGAF structure underneath and lets you shape the rest without losing the mapping.
Your metamodel, TOGAF underneath
Shape the objects and relationships in Ontology Studio. Each one keeps a declared mapping to TOGAF — exact, broader, narrower or partial — so nobody assumes a closer fit than exists.
Full cycle or short loop
Run the full cycle for an enterprise strategy, a short loop for one segment, or phases in parallel beside agile delivery — all on the same records.
Your plateaus and work packages
Label plateaus, work packages and domains the way your architects already do. TOGAF’s structure is kept beside them for reporting and comparison.
Start where it hurts
Begin with an assessed baseline or with a priced target, and add governance, the continuum and capability-based planning as the practice grows.
From 9.2 to the 10th Edition
When The Open Group revises the standard, the reference mapping is updated first, and your records move only where you approve it. Past ADM cycles keep the structure they were run under.
One large document split into Fundamental Content and TOGAF Series Guides
The reference mapping follows the new structure — your records do not move
Series Guides on business capabilities, value streams and capability-based planning brought into the standard
Capabilities and value streams are already first-class records; capability-based planning runs in the portfolio
Architecture states made explicit — candidate, current, transition and target
Mapped to scenarios and to baseline, interim and target plateaus, each priced
Content metamodel reworked as the enterprise metamodel
Your model re-crosswalked, with every change in fidelity shown for approval
More guidance for agile and digital ways of working
Short ADM loops on the same records as agile delivery and the portfolio
Every framework, one model
Architects rarely run TOGAF alone. Business architects use BIZBOK, finance uses TBM, delivery uses SAFe and resilience teams answer to regulators. Here they work from one repository instead of five.
Capability and process maps
Phase B reads the same capability map, value streams and processes business architects keep.
Explore BIZBOK & APQCTIME model · 7 Rs
TIME decisions show up in Phase E as the gaps a transition has to close.
Explore App RationalizationStandards and review for every architecture component
Phase G runs on the same standards, waivers and review decisions.
Explore Solution GovernanceIT spend taxonomy
Plateaus are priced from TBM’s allocated cost, so the roadmap and the ledger agree.
Explore TBMScaled Agile’s operating model for AI
Architectural runway and enablers sit beside the epics and trains they unlock.
Explore AI-Native SAFeEU DORA · NIS2 · UK op-res
Dependencies and recovery objectives from Phase C and D feed important business services.
Explore Operational ResilienceAI-native TOGAF
The work that eats an architecture team’s cycle — rebuilding the baseline, listing the gaps, pricing the roadmap, preparing the board — is drafted from the model. Every proposal stops at the architect or board that owns the decision, and every change is logged.
Assembles the baseline from the live estate — capabilities, applications, data and technology — with the as-of date of every assessment. Unknown stays unknown, never zero.
Compares baseline and target and lists every arriving, retiring, retained and changed element by gap type — capability, data, integration, technology, resilience, compliance and cost.
Prices each transition and the target against the baseline, and shows the run-rate each initiative disturbs.
Keeps each work package linked to the gaps it closes and the initiative that funds it, and flags target elements no initiative is moving.
Walks from a proposed change to the capabilities, applications, controls, contracts and decisions it touches, with the cost involved.
Drafts each project’s compliance review from its conformance verdicts, open waivers and the standards it touches.
Reads the revised standard against your metamodel and proposes renames and remaps, flagging any change in fidelity.
Answers questions about the architecture from the live model, with the assessment date behind each fact.
Where it runs in Dotwork
Dotwork does not ask you to adopt a new method. The framework becomes a view over the same model these solutions already read and write.
How it compares
EA repositories model the ADM and its artifacts. Slides and diagrams carry the rest to the people who fund it. TOGAF on Dotwork covers the whole method and connects every phase to the strategy, budgets and portfolio it is meant to change.
| Capability | EA repositories | Office & diagramming tools | TOGAF on Dotwork |
|---|---|---|---|
| Every ADM phase and Requirements Management | Partly | ||
| A metamodel shaped to your organization | |||
| Baseline, transition and target architectures | Partly | ||
| Each transition priced from the ledger | Partly | ||
| Work packages funded and tracked in the portfolio | Partly | ||
| Change impact across capabilities, contracts and controls | Partly | ||
| Compliance reviews, waivers and decisions kept and dated | Partly | Partly | |
| A new TOGAF edition without re-importing the repository | Partly | ||
| Capabilities and applications shared with BIZBOK, APQC and app rationalization | Partly | ||
| Wired to strategy, budgets, the portfolio and cost |
Who it is for
“What does the target cost, and which transition do we fund first?
“Is the baseline I’m working from still true today?
“How does my design move us toward the target architecture?
“Is our architecture work changing what we fund?
“Which initiatives close which gaps in the target architecture?
“What run-rate does the roadmap release, and when?
Before you buy
How to get a number instead of a pitch.
1
Good answer · Each plateau priced from the same ledger finance closes on.
Bad answer · A rough estimate on a roadmap slide.
2
Good answer · Into the portfolio as funded initiatives, linked to the gaps they close.
Bad answer · Exported to the project office’s tool and never seen again.
3
Good answer · No. The reference mapping is updated and you approve each move; history stays.
Bad answer · A new metamodel, a re-import and a migration project.
More in Architecture
Architecture
The maps of what the business does and the technology that supports it.
The model underneath
Steer, Fund & Optimize and Govern & Deliver all read and write the same Enterprise Operating Model. The first module you license builds the model. Every module after it adds context instead of another silo — and Dotwork AI reads all of it, stopping where the decision is yours.
See the Enterprise Operating Model© 2025-2026 Dotwork, Inc. All rights reserved.