Maintenance Plans
What should be done, how often, and measured how — by calendar, by running hours, by cycles, or by a condition somebody is monitoring. The three are different strategies with different costs.
Where to find it
- Module: Manufacturing
- Group: Maintain
- Section: Maintenance
- Screen: Maintenance Plans
Address in the console: /mfg/maintenance-plans
List · 14 columns · 23 fields on its form · 2 of them required · 2 actions
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Plan | Code | plan_no |
| Name | Text | name |
| Machine | Code | equipment_no |
| Criticality | Status | criticality |
| Type | Status | maintenance_type |
| Trigger | Status | trigger_type |
| Every (days) | Number | interval_days |
| Every (meter) | Number | interval_meter |
| Lead | Number | lead_days |
| Next due | Date | next_due_date |
| Days | Number | days_to_due |
| Tasks | Number | task_count |
| Shutdown | Text | requires_shutdown |
| Active | Text | is_active |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Name required | Text | ||
| Description | Long text | ||
| Machine | Choice | Looked up from existing records | |
| Equipment class | Choice | Configuration list | |
| Work center | Choice | Looked up from existing records | |
| Type | Choice | preventive, predictive, condition_based, inspection, lubrication, calibration, statutory, autonomous | |
| Triggered by required | Choice | calendar, meter, condition, event, manual | |
| Interval (days) | Number | ||
| Meter | Choice | running_hours, cycles, units_produced, distance, starts | |
| Interval (meter units) | Number | ||
| Condition rule | Choice | Looked up from existing records | |
| Raise the order (days ahead) | Number | A plan that raises its order on the due date is a plan that is always late. | |
| The machine has to stop | Yes or no | ||
| Estimated hours | Number | ||
| Estimated cost | Number | ||
| Crew size | Number | ||
| Trade | Choice | Configuration list | |
| Failure mode it prevents | Choice | Looked up from existing records | |
| Procedure | Choice | Looked up from existing records | |
| Next due | Date | ||
| Next due at meter | Number | ||
| Active | Yes or no | ||
| Notes | Long text |
What you can do here
Generate due work primary
Asks for confirmation: Raise orders for everything due inside its lead time? A plan that already has an open order for this cycle is skipped, so a re-run does not double up.
Task list
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.