Set up maintenance
Configure reusable instructions and recurring plans in Operations Studio → Maintenance. Daily work orders belong in Maintenance; technicians use a published execution App.
Before you begin
Select the intended site and environment. Confirm that the machine exists and the author can read the asset and manage maintenance. Releasing an instruction requires the corresponding approval permission. Use your organization's actual instructions and technical limits.
Create and release an instruction
- Select Procedures → New instruction and give the task a clear name.
- Add accessible source documents and useful revision labels.
- Save the draft, inspect it and release the saved revision. Choose whether the released instruction should be active.
- Build the technician's questions, checks, measurements, conditions and evidence flow in the execution App's ordinary source. Publish the reviewed App separately.
The instruction remains reusable task context. It is not a second input editor. There are no published Forms to attach or platform-defined checklist requirements to configure. New orders retain their released instruction snapshot; App-defined inputs and conditions are maintained through App authoring. Existing historical records remain separate from a new App draft.
Create a recurring plan
Choose Maintenance plans → New maintenance plan. Select the machine, linked instruction when applicable, priority and review/return-to-service settings. Then choose a trigger.
| Trigger | Configure | Check before activation |
|---|---|---|
| Date | Day interval, next due date and time zone | The intended first instant and local recurrence time. |
| Operating hours / counter | Metric, unit, interval and next due value | Readings use the same metric and unit as the plan. |
| Condition | Metric, unit, comparison and threshold | The threshold comes from an approved maintenance rule. |
Next due date (UTC) sets an instant. Time zone controls local calendar-day recurrence, including daylight-saving changes. Do not treat the UTC field as a local time. Counter plans use cumulative readings; condition plans trigger on a crossing and require recovery before another crossing. Configuring a plan does not connect a sensor or manufacture a reading. Connected readings need a configured, trusted integration.
Keep Active when released off while checking the first due date, instruction and access. Save and release the inactive plan. When the configuration is ready, turn Active when released on, save and release that revision. The active plan can then generate preventive work. If an instruction is linked, it must be released and active. A plan without an instruction does not inherit a checklist.
The plan's scheduling authority belongs to the author in that site/environment. Removing their required management or asset-read access can stop new automatic work. If generation stops, check the plan's active released state, current readings or due date, and the author's current access before recreating the plan.
Change a released definition
Editing and saving creates a draft. The current released instruction or plan continues to apply until the draft is released. To stop future automatic work, release the plan with activation turned off; an inactive draft alone does not change the active release.
Use History to inspect earlier definitions. Restoring a version prepares a draft for review; it does not immediately replace the release. Release that draft separately when it should take effect.
App input changes follow App editing and publication. Review their effect on ongoing work and saved drafts before publishing.
Verify the setup
Before activating a recurring plan, create one authorized test order from its released instruction. Check the machine, instruction, App inputs, saved-state behavior and review settings. Confirm actual recording as the intended technician and review by a different authorized person where required.
If saving or release fails, inspect access, scope and the current saved revision. Reload after a conflict and resolve an uncertain save with the same request identity. Do not recreate a definition just because a response was interrupted.