Support operations
The ongoing relationship between data, systems and processes remains part of the review.
Expert topic · Ongoing operations
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, data processes and operational workflows form part of ongoing operational work.
Data, processes and operational transparency help put effect in the operation into context.
New requirements can be taken into continuous optimisation in a structured way.
After implementation
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
This page separates the ongoing operating phase from initial analysis and design without losing the connection between them.
Implemented data processes and operational workflows are supported in their operational context.
Data, processes and operational transparency provide a frame for discussing relationships and requirements.
New requirements are related to the target state, operations and system landscape as part of continuous optimisation.
Operational context
The ongoing relationship between data, systems and processes remains part of the review.
Operational transparency supports discussion of relationships in operation without promising particular metrics.
New requirements can be related to existing operations, goals and the system landscape.
In focus
This page does not describe service levels, availability values, particular operating tools or security promises. It explains the role of support and further development.
Frequently asked questions
The answers describe the fourth phase of the approach without operational guarantees or specific service commitments.
Operating and optimising means supporting data processes and operational workflows in context and using operational feedback and new requirements to guide their continuous development.
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.
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.
New requirements are related to goals, operations and the system landscape. They can then be considered as part of continuous development.
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
An initial conversation can review ongoing data processes, operational workflows, operational questions and new requirements together.