Portamus GmbH is an independent enterprise architecture consultancy based in Oberhausen, Germany, serving large enterprises, mid-market companies and public administrations across the German-speaking region and internationally. Founded in 2011, the firm is vendor-neutral and delivers digital transformation architecture with TOGAF®- and ArchiMate®-certified senior architects.

What role does enterprise architecture play in digital transformation?

Enterprise architecture provides the connective tissue a transformation programme needs: a documented baseline of the current landscape, an agreed target state across business, application, data and technology layers, a sequence of transition states between the two, and the governance that checks each workstream's design against that target. Without it, transformation programmes make platform commitments in individual workstreams that later have to be undone — which is where most cost overruns originate.

When should architecture work start in a transformation programme?

Before the workstreams select platforms. A four-week architecture baseline ahead of the programme design phase is usually enough to establish current-state constraints, and it is far cheaper than reversing an integration decision in year two. Where a programme is already running, we start with a baseline and a target-state reconciliation of the commitments already made.

Which framework do you use for transformation architecture?

We work on TOGAF® ADM, model in ArchiMate® and document architecture descriptions in line with ISO/IEC 42010. The ADM is tailored to the programme rather than run in full: the emphasis is on Phases A to D for the target state and Phases E and F for the transition roadmap, with architecture governance from Phases G and H running alongside delivery.

How is this different from what a large systems integrator offers?

Two differences matter. First, we sell no platforms and take no licence or implementation commission, so the target architecture is not shaped by what we would later implement. Second, delivery is by senior architects throughout rather than a large blended team, and the architecture function is deliberately handed to your people at the end of the programme.

How do you measure whether the transformation architecture worked?

Through transition states, not through model completeness. Each transition state carries measurable criteria — applications decommissioned, interfaces consolidated, capability coverage reached, end-of-life risk cleared. If a transition state cannot be given such criteria, it is usually a sign the sequencing is wrong rather than the measurement.

Digital Transformation

Enterprise Architecture for Digital Transformation

Q: Do you also support delivery, not just the plan?

Yes. Beyond the target architecture and roadmap we run design reviews against the target state, arbitrate architecture conflicts between workstreams and keep the roadmap current as the programme learns. Where an organisation has no standing architecture capacity, this can be retained continuously as Enterprise Architecture as a Service.

Enterprise architecture consulting for digital transformation: we turn a transformation strategy into a target architecture, a sequenced roadmap and an architecture governance that keeps the programme from drifting — delivered by TOGAF®-certified senior architects.

Overview

Understanding This Service

A target architecture the programme can build on

Transformation programmes fail on architecture, not on ambition. We define the target state across business, application, data and technology layers before the workstreams start committing to tooling.

Sequencing, not a wish list

We order the transformation by dependency, risk and value — which capabilities have to exist before which others can be built, and where the early, provable wins are.

Governance that survives the programme

Principles, review criteria and an architecture board that assess each workstream's design against the target state — so the landscape after transformation is the one that was agreed.

Common Challenges

Why Clients Request This Service

Transformation strategy exists, but no architecture behind it

Workstreams commit to platforms before the target state is agreed

Legacy core systems block the transformation roadmap

No architecture authority to arbitrate between programme workstreams

What's Included

Scope of Testing

Our enterprise architecture work in digital transformation programmes typically includes:

Architecture baseline

An assessment of the current landscape, its capability coverage, integration debt and end-of-life exposure — the honest starting point a transformation plan has to assume.

Target architecture

The digital target state across all four layers, modelled in ArchiMate® and traced back to the business capabilities the transformation is meant to change.

Transformation roadmap

A sequenced plan of transition states with dependencies, decision points and measurable milestones, aligned to the programme's funding cycle.

Architecture governance for the programme

Principles, a design-review process and an architecture board so each workstream's solution design is checked against the target state before build.

Our Approach

How We Run This Engagement

1. Baseline

Map the current landscape, capability coverage and integration debt; surface the constraints the transformation plan has to work within.

2. Target architecture

Define the digital target state across business, application, data and technology layers and trace it to the capabilities the transformation is meant to change.

3. Transition states & roadmap

Break the distance between baseline and target into transition states that each deliver value, and sequence them by dependency and risk.

4. Governance & delivery support

Run design reviews against the target state, arbitrate between workstreams and keep the roadmap current as the programme learns.

Deliverables

What You Walk Away With

Architecture baseline report

Current-state assessment with capability coverage, integration debt, end-of-life exposure and the resulting constraints on the transformation plan.

Target architecture model

Documented digital target state across all four layers, modelled in ArchiMate® and summarised for the programme board.

Transition roadmap

Sequenced transition states with dependencies, decision points, measurable milestones and funding-cycle alignment.

Architecture governance pack

Architecture principles, design-review criteria and the terms of reference for the programme's architecture board.

Related Frameworks

This service commonly supports requirements under:

TOGAF®ArchiMate®Enterprise Architecture Consulting Digital Maturity Assessment Cloud Architecture & Migration

Why Our Approach

What Makes Our Testing Different

Senior architects deliver — no junior pyramid

Vendor-neutral: no platform or licence commission

Enablement: the architecture function stays with your team

Measurable transition states instead of a multi-year wish list

The Portamus Difference

Portamus GmbH is an independent enterprise architecture consultancy based in Oberhausen, Germany, that supports digital transformation programmes with the architecture they are built on. We produce three things: an honest baseline of the current landscape, an agreed target architecture across business, application, data and technology layers, and a sequence of transition states that each deliver measurable value — plus the governance that keeps workstream designs aligned to the target.

Transformation programmes fail on architecture, not ambition

The strategy is rarely the problem. The problem appears when several workstreams start delivering in parallel, each choosing a platform that is locally reasonable and collectively incoherent. Two years later the integration layer is the programme’s largest cost item and the target state exists only in a slide deck.

Architecture prevents that by making the target state explicit and binding before the commitments are made, and by giving the programme an authority that can arbitrate between workstreams. That is the work we do — described in more depth in our articles on enterprise architecture management and EA governance.

Baseline, target state, transition states

We start with a baseline: capability coverage, integration debt, end-of-life exposure. We then define the target architecture and — the step most often skipped — break the distance between the two into transition states. Each transition state is a landscape the organisation could live in, with criteria that can be verified: applications decommissioned, interfaces consolidated, capabilities delivered. A roadmap without such states is a wish list with dates on it.

Where the trigger is a core-system replacement or a move to cloud, this connects directly to our cloud architecture and migration work; where the starting point is unclear, a digital maturity assessment establishes it in weeks.

Vendor-neutral by construction

We sell no platforms, implement no products and take no licence or implementation commission. A target architecture drawn by a party that would later implement it is not an independent target architecture. Our references — for example the enterprise architecture modernisation of a tax authority and an SAP BTP architecture in medtech — show how that plays out in delivery.

Getting started

Initial conversation with a senior architect about the transformation trigger, scope and the decisions already committed.
Four-week architecture baseline with current-state constraints and a first target-state outline.
Target architecture, roadmap and governance — followed by delivery support for as long as the programme needs it, or continuous support via Enterprise Architecture as a Service.

See also our enterprise architecture consulting overview.

FAQs

Questions About Enterprise Architecture for Digital Transformation

Don't see your question here? Our team is happy to walk through the specifics of your environment.

Ask Our Team