Cloud& Infrastructure
What it covers
Where should our workloads run, and why there?
We work out with you which applications should run in your own data centre, in a sovereign cloud, in the public cloud or at the edge. The yardsticks are criticality, data sovereignty, cost and energy demand, along with the shared platform your teams need. The result is well-founded placement decisions, a workable operating model for cloud and data centre, and a roadmap for the transition. Enterprise architecture connects business capabilities with applications and technology. IT service management defines services, ownership and operational processes; FinOps establishes transparency and accountability for cloud costs.
When companies bring us in
- Cloud costs are rising, but no one can attribute them to specific applications and owners.
- The use of several cloud providers has grown rather than been planned, and data sovereignty requirements are tightening.
- Your data centre is due for renewal, and AI workloads demand more power and cooling than it was designed for.
From workload to platform
We start with the applications and their requirements, not with a provider. Only once it is clear what belongs where do decisions on platforms, contracts and data centre capacity pay off.
Take stock
We capture applications, data flows, current locations and costs at the level of detail the decision requires. Dependencies between applications become visible along the way.
Set criteria
Together, we weight criticality, data sovereignty, regulatory requirements, cost and energy demand. The result is one set of criteria that applies to every workload.
Place workloads
Each relevant workload is assigned a target location, from your own data centre to the edge. The rationale and exit options are documented.
Design the platform
We define the shared platform, standards and cost accountability your teams need. This becomes the operating model for cloud and data centre.
Plan the transition
Migrations, contract changes and capacity measures are sequenced in waves. The cost and risk of the transition sit alongside the target state.
Services in this area
Explore all servicesEnterprise Architecture Management
Which applications will you actually need?
- Enterprise Architecture Management (EAM)
- Business capability and application maps
- Target architecture with integration and cloud principles
- Application assessment and rationalisation
Cloud Strategy & Cloud 3.0
Which workloads belong in which cloud?
- Cloud strategy and placement criteria
- Workload assessment and target platform recommendations
- FinOps model and cost accountability
- Platform design and cloud operating model
Service Desk & ITSM
How does IT become a dependable service partner?
- ITSM maturity and service-desk assessment
- Service catalogue, ownership and service levels
- Incident, request, problem and change processes
- Knowledge management and self-service
FinOps & Cloud Costs
How do we make cloud costs transparent and manageable?
- Cost allocation to applications and teams
- Budget and forecast model
- Prioritised resource and contract improvements
- FinOps review cycle with metrics and owners
Data Centres & Energy
Own data centre, colocation or cloud?
- Site strategy for data centre, colocation and cloud
- Energy efficiency assessment with metrics such as PUE
- Capacity plan for AI workloads, power and cooling with demand assumptions
- EED reporting readiness and waste-heat concept
