One wave plan
Workloads, dependencies, and sequence held together with the rollback position for each wave.
The EAX Product Suite™
EAX CloudBlueprint™
Cloud modernization planning workspace: migration planning, architecture guidance, and the business roadmap in one place.
Concept
Executive overview
Cloud migrations are usually planned twice: once technically and once financially, in documents that never quite agree.
CloudBlueprint is being designed as a single workspace for wave planning, architecture decisions, and the business roadmap, so that a migration wave, its guardrails, and its expected commercial effect are described in one record.
Current availability
In concept. Interface material is illustrative. Scope is being shaped with infrastructure and platform leaders.
EAX CloudBlueprintMigration plan
Workloads catalogued
214
with dependencies
Waves planned
6
rollback stated per wave
Guardrail gates
11
prerequisite to wave start
- Wave 1: low dependencyReadyGuardrail gates met
- Wave 2: shared servicesBlockedIdentity prerequisite outstanding
- Wave 3: regulated workloadsPlanningResidency constraint under review
- Run-cost baselineDraftPending architecture decision 07
The business problem
What this removes
The conditions that make the work expensive, slow, or hard to defend.
Wave plans change faster than the documents describing them.
Architecture decisions are made in meetings and lost in inboxes.
The run-cost expectation is set before the architecture is settled.
Business value
What changes for the accountable executive
Decisions with reasons
Architecture decisions recorded with alternatives considered and the constraint that decided it.
Guardrails as prerequisites
Landing-zone conditions treated as gates before a wave proceeds.
Roadmap alignment
The business roadmap derived from the same wave plan the delivery team holds.
Target organizations
- Enterprises mid-migration with mixed estates
- Organizations consolidating datacentres under a compliance obligation
- Businesses whose cloud run cost has outpaced the plan
Illustrative workflow
How the work would move through the platform
A representative sequence. Steps beyond the stated availability describe intended design rather than released behaviour.
Catalogue workloads
Applications, dependencies, and the constraints attached to each.
Set landing-zone conditions
Guardrails and policies that must exist before any wave proceeds.
Plan the waves
Sequence workloads with a stated rollback position per wave.
Record architecture decisions
Capture the decision, the alternatives, and the deciding constraint.
Publish the roadmap
A business-facing sequence derived from the same plan.
Future roadmap
Released, in build, and intended
Items outside the first column are direction rather than commitment. They may change or be withdrawn.
Now
Current state
- Concept definition
- Scope conversations with platform leaders
Next
Subject to validation
- Workload catalogue and wave planning
- Architecture decision record
Later
Direction, not commitment
- Guardrail gate tracking
- Business roadmap output
Questions
Answered plainly
- Is CloudBlueprint available?
- No. It is a concept, and the interface material shown is illustrative.
- Does it perform migrations?
- No. It is a planning workspace. Execution is carried out by delivery teams using the platform tooling appropriate to the estate.
- How does it relate to an advisory engagement?
- It would hold the plan an engagement produces, so the record stays current after the advisors step back.
Request access
Discuss EAX CloudBlueprint™ with an advisor
Tell us the obligation or decision you are working against. If the product is not ready for your situation, we will say so and describe the advisory route instead.