VYRCOWhat you will learn
- A maintenance interval needs a documented basis and someone responsible for reviewing it.
- Task completed, acceptable result and equipment released are different states.
- History supports plan reviews when it preserves identity, condition and context.
Who it is for: Planners, mold shops and mold maintenance owners.
Define the asset and plan version
Start with the mold, its revision and the scope: which components the plan covers and which have separate documentation. Give the plan its own version. If two copies list different tasks, people must be able to identify which is current and since when. Retain earlier versions to interpret historical work.
Collect manuals, approved internal instructions, known modifications and intervention records. An incomplete transfer dossier should create visible document gaps; filling them with tasks copied from a similar mold can hide missing information rather than resolve it.
Write tasks that produce a checkable result
“Check mold” is too broad to establish what happened. Describe the component, observation scope, reference procedure and expected record. Do not turn the list into an improvised manual: access, disassembly, cleaning or testing must follow their specific instructions.
Add the acceptance criterion or the reference containing it. If it is undefined, the task remains under review. A photograph may help compare conditions, but a photograph alone does not establish that a function was verified.
| Element | Review question |
|---|---|
| Task | Which component and scope are documented? |
| Criterion | Which reference will be used to evaluate the result? |
| Evidence | Which record will allow execution to be checked? |
| Owner | Who performs, reviews and decides? |
Choose a trigger with a visible rationale
Record whether the task uses calendar time, cycles, condition or another approved criterion. Include the unit, data source and person responsible for updating it. A counter cannot support scheduling reliably if nobody knows when it was reset or which operations it counts. Keep those events alongside the value.
If several triggers apply, state how the combination is interpreted under the applicable procedure. Do not invent a rule or universal interval. If history suggests reviewing an interval, submit a proposal with evidence and distinguish it from an approved change.
Prepare resources and expose blockers
Connect the task to required competence, tooling, spare parts and documentation. The item register helps identify references and status; the reorder-point tool estimates a threshold using user-selected data but does not establish part compatibility. Keep that decision linked to its technical source.
Before scheduling, show what is missing: authorization, a spare part, information, access or time. A blocked job must not appear completed. When tasks are grouped into a shutdown, retain their individual identities and document coordination restrictions defined by the responsible person.
Use execution records to learn
Record date, counter or condition, technician, result and evidence. Separate completed and omitted work and explain deviations. A finding should create a linked action rather than disappear in an unreviewed free-text note. Release remains a separate authorized decision.
During plan review, compare recurring issues, tasks that produce little useful evidence and repeated resource gaps. Maintenance indicators help only when periods and definitions are comparable. Document why a task is retained or changed, who approves and when the decision becomes effective. Make the resulting revision available where work is planned and recorded.
Fictional example: a task without an approved interval
Plan DEMO-M03 includes checking connection identification against drawing revision C. The task has a criterion and expected evidence, but no defined interval. It is marked “under review”, with an owner and date for consulting the manual and history. It is neither automatically scheduled nor assigned an internet-derived interval. Once approved, the plan receives a new revision.
Mistakes to avoid
- Copying another mold’s intervals without an applicable documented rationale.
- Using “OK” to combine execution, acceptance and release.
- Keeping obsolete spares available merely because they remain in the inventory.
Checklist before continuing
- Asset, plan and documents have identities and revisions.
- Each task has a procedure, criterion and expected evidence.
- Triggers have units, sources and owners.
- Missing resources and omitted work remain visible.
- Plan changes retain reason, approval and effective date.
Sources and review
- Husky · Maintenance and Refurbishment
Manufacturer example of inspection, intervention and testing; no general intervals are established.
Accessed: 2026-10-09 - NASA · Configuration Management
Principles for identifying, reviewing and verifying changes. VYRCO formats are original, not NASA forms.
Accessed: 2026-10-10
Original general guidance by VYRCO based on the listed references. Examples are fictional. Editorial review does not validate your process. To correct an item, identify the article, date and source at info@vyrco.com.