Expert topic · Approach

Analyse the system landscape and define a target state.

When goals, existing systems and handovers are assessed separately, it can be harder to compare solution options in context. A structured analysis considers processes and the system landscape together, providing a basis for a target state and solution approach before implementation and ongoing operations are planned.

Digital operation power. Bundled. Anytime!

Structured starting point

Do not start with a premature tooling decision.

The system landscape is more than a list of involved systems. It describes how goals, processes, data and handovers work together in the current information flow.

The analysis provides a basis for defining a target state and solution approach. Only then are implementation, integration, operation and optimisation considered in concrete terms.

Approach model

From understanding to a target state.

The approach separates clarification of the starting point from later delivery so that requirements do not arise from a single technical perspective alone.

  1. 01

    Understand goals and operations

    Goals, processes and existing information flows are captured and put into context together.

  2. 02

    Analyse the system landscape

    Involved systems, input channels, metadata, target systems and handovers are considered in their relationship.

  3. 03

    Define the target state and concept

    The findings inform a target state and solution approach aligned with the operation for later delivery.

Functional context

A shared foundation for the next steps.

Understand the starting point

Goals, processes and the system landscape are considered in their relationship rather than separately.

Design relationships

A target state connects requirements from data, processes and the involved systems.

Put next steps into context

The solution approach provides orientation for the implementation and integration that follow.

In focus

Questions for the starting point.

This page describes a structured beginning. It does not contain fixed timelines or a specific tooling or architecture decision.

  • Which goals and processes need to be understood?
  • Which systems, input channels and target systems are involved?
  • Where are relevant data flows and handovers?
  • Which requirements should a target state and solution approach bring together?

Frequently asked questions

Put the system landscape and target state into context.

The answers describe how collaboration begins and the roles of analysis, target state and solution approach.

What belongs to a system landscape?

The system landscape includes systems, input channels, target systems, data flows and handovers that matter to the processes under consideration.

What is analysed at the start?

Goals, processes and the system landscape are reviewed in a structured way. For integration questions, this also includes input data, metadata and the requirements of receiving systems.

What is a target state?

A target state describes the intended functional direction based on the analysis. It provides the basis for a solution approach aligned with the operation.

What follows the target state and solution approach?

Implementation and integration are then delivered iteratively. Operation, effect and continuous development can be considered afterwards.

When does a shared target state become relevant?

It becomes relevant when goals, existing systems and handovers are assessed separately, making solution options harder to compare in context. A shared target state connects operational requirements, processes and the system landscape before a tooling decision is made.

Next step

Let us review your starting point in a structured way.

A no-obligation initial conversation can put goals, processes and the system landscape into context and establish the frame for a target state.