Getting Started with Maintenance

The maintenance flow at a glance

Maintenance in P4 is designed as a controlled, traceable workflow.

Instead of treating maintenance as a stream of urgent tasks, phone calls, and ad-hoc fixes, P4 separates:

• issue detection,

• decision and approval,

• planning and assignment,

• execution,

• monitoring and evaluation.

This guide walks you through the complete maintenance flow, step by step, using the same logic you would follow in real maintenance operations.

You do not need to configure everything or understand all details to get started.
You only need to understand how the pieces fit together.

1. The maintenance flow at a glance

Maintenance in P4 follows a clear sequence:

Issue detected
→ Maintenance Notification
→ Maintenance Order
→ Planning & Assignment
→ Execution
→ Monitoring & Reporting

Each step builds on the previous one.

Skipping a step usually leads to:

• unclear responsibilities,

• overloaded technicians,

• distorted KPIs,

• maintenance that feels chaotic instead of controlled.

2. How maintenance is structured in P4

P4 intentionally separates maintenance into distinct layers:

Asset layer
Equipment represents physical assets that require maintenance.

Detection layer
Maintenance Notifications and Measuring Points capture potential issues.

Decision layer
Notifications are evaluated and converted into Maintenance Orders.

Execution layer
Maintenance Orders are assigned, executed, and logged by technicians.

Insight layer
Monitoring and reporting turn execution into measurable results.

This structure allows you to:

• react quickly to problems,

• prioritize what really matters,

• keep full traceability from issue detection to resolution,

• improve maintenance based on real data.

3. Who this guide is for

This Getting Started guide is intended for:

• maintenance planners and managers,

• technicians and team leaders,

• key users responsible for maintenance setup,

• anyone who needs to understand how maintenance works end-to-end.

It is not:

• a configuration manual,

• a complete reference of all features,

• a troubleshooting handbook.

Its goal is simple:

Help you understand maintenance well enough to start using it confidently.

4. How to use this guide

You can follow this guide in two ways.

4.1 Step-by-step (recommended)

Start at the first page and follow the maintenance flow in order.

This builds a clear mental model of:

• how issues enter the system,

• how work is approved and executed,

• how results are evaluated.

4.2 Jump to your role

If you already know parts of the system, you can jump directly to:

• notifications and orders,

• planning and execution,

• preventive maintenance,

• reporting and KPIs.

Each page stands on its own, but works best as part of the full story.

5. What this guide does not cover

To keep Getting Started focused, this guide does not cover:

• detailed parametrization of maintenance processes,

• advanced preventive maintenance setup,

• measuring point configuration and integrations,

• detailed KPI formulas and report configuration.

These topics are covered in dedicated documentation once the basics are clear.

6. Ready to start?

If you are new to maintenance in P4, start here:

Detecting Issues: Maintenance Notifications

This is where every maintenance process begins —
with noticing that something might not be right.