Preventive
Scheduled services that reduce breakdowns and extend useful life.
Community maintenance
Every service happens when it should.
Onzane turns the recurring needs of every asset and facility into traceable plans, inspections, readings and work. The community gets ahead of due dates and retains the complete history.
A continuous cycle
Plan. Generate. Execute. Record.
Maintenance no longer relies on personal reminders and becomes a shared, verifiable process.
-
01
Plan
Define what must be done, how often, for which asset and under which instructions.
-
02
Generate
Onzane creates the work on time, without duplicates and in line with the expected schedule.
-
03
Execute
The responsible party completes steps, readings, notes, photographs and evidence from their tool.
-
04
Record
The outcome remains linked to the asset, supplier, contract and community history.
Maintenance plans
From a recurring obligation to a controlled schedule.
Every plan brings together scope, frequency, priority, instructions, owner, supplier, contract and asset. The community knows what is due and what has been completed.
Corrective
Interventions arising from an anomaly, incident or non-conforming result.
Inspections
Structured checks with required steps, answers and evidence.
Readings
Periodic recording of pressure, temperature, consumption, flow or other values.
Automatic generation
The plan triggers the work before it is due.
Recurrence can be calculated from a fixed date or the last valid execution. Onzane prevents duplicate work, keeps the cadence and alerts the responsible people.
- 01Flexible frequency
Daily, weekly, monthly, yearly or through a custom rule.
- 02No duplicates
A new execution is not generated when an equivalent one is already pending.
- 03Clear ownership
Assign staff, supplier, contract, priority and instructions from the outset.
- 04Alerts and escalation
Notify upcoming due dates and flag delays that require attention.
Structured inspections
Ticking a task as done is not enough.
Templates turn a service into verifiable steps. They can require answers, values, comments, photographs or documents before the work is completed.
01Reusable checklists
Define the procedure once and use it for every plan execution.
02Required evidence
Request photographs, documents or comments at critical points.
03Non-conforming results
An incorrect response can trigger an alert or corrective action.
04Subsequent validation
The responsible person reviews the result before accepting it.
Readings and thresholds
Values also tell the story of an asset.
Record manual or device readings and compare them with expected ranges. A deviation can trigger alerts and corrective work.
- Pressure, temperature, consumption, flow, operating hours or other values
- Unit and expected range defined for each asset
- Chronological evolution and comparison with earlier readings
- Automatic alerts when a value falls outside its range
Operational history
Every execution improves the next decision.
The asset retains when it was serviced, who intervened, what they found, which evidence they supplied and the outcome. The community can assess recurrence and compliance.
Preventive
Compliant
Monthly service completed
Correct pressure, no leaks and evidence attached.
Corrective
Resolved
Valve replacement
Work linked to an out-of-range reading.
Reading
Reviewed
Pressure deviation detected
The value exceeded the threshold and triggered an automatic alert.
Inspection
Compliant
Checklist validated
Five steps completed by the responsible supplier.
Frequently asked questions
Community maintenance with Onzane.
How recurring work is planned, executed and retained.
01What is the difference between a plan and a work order?
The plan defines the recurring need, frequency, instructions and responsible parties. Each execution creates the specific work that must be completed and validated by a given date.
02Can Onzane generate work automatically?
Yes. A rule can create work before it is due, prevent duplicates, assign responsible parties and send alerts according to the configured priority and schedule.
03Can maintenance be linked to a specific asset?
Yes. A plan can be related to an asset, facility or location, as well as the relevant contract, supplier and responsible parties.
04What can an inspection include?
Ordered steps, yes-or-no answers, numerical values, comments, photographs, documents and conditions that determine whether the result is compliant.
05What happens when a reading is outside its range?
Onzane can mark the reading as anomalous, alert those responsible and trigger corrective work to inspect the asset.
06Can an external company carry out the maintenance?
Yes. The plan can be linked to a supplier and its contract. Execution can be shared with the supplier while retaining instructions, evidence, timing and validation.
07Does the history remain when the supplier changes?
Yes. Plans, executions, readings, inspections and evidence belong to the community’s operational context and remain available to newly authorised responsible parties.
Prevention with context
Make maintenance happen before the problem.
We help you organise assets, import plans and define an operational schedule that can be sustained over time.