Expert topic · Ongoing operations

Operate and develop data processes and operational workflows.

In ongoing operations, new requirements can reveal where the target state, operational workflows and system landscape need to be aligned again. FORCE supports implemented data processes and operational workflows, using operational feedback and new requirements to inform continuous development.

Digital operation power. Bundled. Anytime!

After implementation

Ongoing operations are part of the approach.

FORCE describes its approach in four parts: understand and analyse, design, implement and integrate, then operate and optimise. Operation follows implementation.

This includes supporting data processes and operational workflows in context and using operational feedback to guide continuous development. Which requirements matter follows from ongoing operations.

Operating model

From implemented operations to continuous development.

This page separates the ongoing operating phase from initial analysis and design without losing the connection between them.

  1. 01

    Operate the flows

    Implemented data processes and operational workflows are supported in their operational context.

  2. 02

    Consider effect

    Data, processes and operational transparency provide a frame for discussing relationships and requirements.

  3. 03

    Put further development into context

    New requirements are related to the target state, operations and system landscape as part of continuous optimisation.

Operational context

Consider stability and development together.

Support operations

The ongoing relationship between data, systems and processes remains part of the review.

Put effect into context

Operational transparency supports discussion of relationships in operation without promising particular metrics.

Connect further development

New requirements can be related to existing operations, goals and the system landscape.

In focus

Questions for ongoing operations.

This page does not describe service levels, availability values, particular operating tools or security promises. It explains the role of support and further development.

  • How do data processes and operational workflows relate in ongoing operations?
  • Which relationships should operational transparency help consider?
  • How are new requirements put into context with the existing target state?
  • How does continuous optimisation connect with processes and the system landscape?

Frequently asked questions

Put operation and optimisation into context.

The answers describe the fourth phase of the approach without operational guarantees or specific service commitments.

What does operating and optimising mean?

Operating and optimising means supporting data processes and operational workflows in context and using operational feedback and new requirements to guide their continuous development.

How does operation relate to workflow automation?

Workflow automation concerns the modelled and automated operation. In ongoing operations, that flow is supported in context and put into further context when new requirements arise.

What is the role of operational transparency in operation?

The view of data and processes helps discuss relationships in daily operations. It does not replace a particular metric or decision, but provides context for them.

How are new requirements put into context?

New requirements are related to goals, operations and the system landscape. They can then be considered as part of continuous development.

When does continuous development become relevant?

It becomes relevant when new requirements in ongoing operations show that the target state, operational workflows and system landscape need to be aligned again. Operational feedback provides a traceable basis for that development.

Next step

Let us put operation and further development into context together.

An initial conversation can review ongoing data processes, operational workflows, operational questions and new requirements together.