Part C - Performed Intervention, Functioning, and Return to Use
MNT.9 - Perform and Record the Maintenance Intervention
Type: Method Status: Stable
MNT.9:1 - Problem frame
Use this pattern when a selected maintenance intervention is being performed and later decisions depend on what actually happened. The planned bearing has been replaced, but an interruption, substituted part or changed setting can leave the work record inconsistent with the machine.
Perform the task within its applicable procedure and operative conditions, preserving the material actions and actual resulting configuration. The first result is evidence of the performed intervention, including its incomplete or changed portions. MNT.10 establishes restored functioning and MNT.11 establishes the hand-back result. This pattern does not require physical work to finish a recommendation request.
MNT.9:2 - Problem
A work order describes intended work. Closing its tasks can conceal what was skipped, repeated, changed or performed under different conditions. A subsequent tester may then check the wrong configuration, and a future maintainer may infer that a suspected cause was confirmed.
Unexpected conditions make this worse when the team improvises beyond the permitted scope without revisiting protection, competence or the maintenance choice.
MNT.9:3 - Forces
The practitioner needs enough freedom to respond to the actual machine while preserving the limits that make the response acceptable. Detailed recording can support later diagnosis but distract from protected work if poorly timed. A work interruption can require relief or re-establishment of a condition; simply extending the shift may impair performance.
MNT.9:4 - Solution
Recover the selected task and the operative work conditions before performing it. The applicable equipment procedure supplies the concrete technique, tool use, tolerances and controls. This Method organizes maintenance performance and its usable account; it does not replace that procedure.
Maintain correspondence between work and actual state. Identify the unit, relevant configuration, selected parts and settings. Where the procedure requires a check before an irreversible or consequential step, perform that check at the point where it establishes the needed condition. A later signature cannot recreate an unobserved state that is no longer recoverable.
When the actual condition differs from the expected one, determine what changes. A harmless access detail may remain within the permitted task. Unexpected damage, a different part interface, a lost protection condition or a larger repair can change competence, permission, time and verification. Use the applicable hold or restoration procedure and return the changed maintenance decision rather than silently extending the scope.
Handle interruption explicitly. Preserve a condition that the next practitioner can safely recognize, transfer the relevant unfinished work and protection through the applicable arrangement, and re-establish any condition that no longer has usable support. If fatigue or working conditions impair the task, change allocation, relief or timing. The completion pressure does not supply capability.
Preserve the facts that later users actually need. These commonly include material actions, installed or removed part identities, relevant settings and measurements, deviations from the selected work and unresolved conditions. Use the existing maintenance record when it serves that purpose. Applicable regulatory or organizational retention requirements remain in force; the framework does not create a separate universal bundle.
Keep statements at their supported level. “Bearing installed using the applicable procedure” concerns the intervention. “The required flow is restored” needs functioning evidence. “This recurring failure has been eliminated” needs a different horizon and causal basis. Link those later results when they exist without assigning them to a task-completion entry.
Return the performed work and resulting configuration to the tester, operator or maintenance-history user who needs them. If the work is incomplete, state its actual stopping state and the condition needed for continuation. A truthful partial result is more useful than a closed order that implies unperformed work.
MNT.9:5 - Archetypal Grounding
In the extended constructed PS17 branch, the part return, protected access and permission are in place. The team performs the selected bearing intervention under the applicable equipment procedure.
The removed bearing is identified as R551 and the installed compatible bearing as R607. These are constructed serial-unit identifiers. The resulting installed configuration is identified as C42; it retains the same approved design basis while the actual bearing individual has changed. The maintenance record describes that change; it is not the physical configuration itself.
If unexpected housing damage is found, the original bearing task may no longer answer the condition. The team preserves the supported state and obtains the relevant revised diagnosis and work decision. It does not mark the original plan complete merely because the replacement bearing was available.
In the completed branch, the intervention record supplies the actual configuration and material observations to MNT.10. It does not yet claim restored district-heating service or removal of the unresolved long-horizon recurrence mechanism.
MNT.9:6 - Bias-Annotation
Completion targets reward closed tasks and can discourage reporting deviations or unfinished work. A detailed plan can also make the practitioner expect the machine to match it. Keep actual observations visible where they change the work or later interpretation.
MNT.9:7 - Conformance Checklist
Was the selected work performed within its applicable procedure and operative conditions? Were material deviations, interruptions and changed scope handled by the relevant decision? Can the next user recover the actual installed state and supported work claims? Are incomplete portions and unresolved consequences stated?
The result concerns performed intervention. Functioning and resumed-use claims require their own support only when those are the selected subsequent results.
MNT.9:8 - Common Anti-Patterns and How to Avoid Them
A task is closed because the planned hours were consumed. Record what actually happened and the remaining state. A substituted part is described only as “equivalent” when applicability is material. Preserve the basis that makes it usable in this configuration.
An exhausted specialist is instructed to finish more carefully. Revise relief or timing in response to the actual capability limit.
MNT.9:9 - Consequences
The tester and operator receive an account that corresponds to the intervention, including its limits. Some work returns for a revised decision rather than being completed under an obsolete plan. Recording costs remain focused on useful later claims and operative retention requirements.
MNT.9:10 - Architectural Rationale
Performance and its account are joined because later maintenance decisions rely on that correspondence. The Method does not make the record the work itself. Separating intervention evidence from functioning and release prevents one completion claim from silently taking on several incompatible meanings.
MNT.9:11 - SoTA-Echoing
The practice question is how to preserve reliable continuation when work differs from its plan. This pattern adapts the work-management concern in GFMAM’s maintenance framework and the fatigue-reporting problem in CASA’s 2026 maintenance risk account. Against task-closure-only management, it adds the interruption, actual-state and relief decisions in the Solution. It accepts focused reporting and occasional replanning to avoid concealing incomplete or unsupported work. CASA’s aviation account supplies a relevant failure mechanism, not a universal duty-time threshold. Reopen when a new work variant or observed interruption defeats the continuation arrangement. See GFMAM and CASA’s fatigue account.
MNT.9:12 - Relations
MNT.6 supplies the selected intervention, MNT.5 its support and MNT.8 its operative protection and permission. MNT.7 and MNT.15 handle changed timing or shared work. MNT.10 consumes performed-work and configuration evidence; MNT.12 preserves its useful history. FPF FPF A.13 and FPF A.15.1 govern precise performer and performed-Work claims when those stronger claims are made.
MNT.9:End
MNT.10 - Verify Restored Functioning after Maintenance
Type: Method Status: Stable
MNT.10:1 - Problem frame
Use this pattern when a performed maintenance task is being used to claim that the System can again support its required use. A bearing replacement is complete, but the receiving operator needs evidence about functioning under the relevant configuration and load.
Establish the functioning claim that the available evidence supports, or return its unsupported portion. “Restored” means adequate for the stated use and envelope; it need not mean as-new equipment or absence of every defect. MNT.11 handles the distinct permission and transfer of control for resumed use.
MNT.10:2 - Problem
A completed procedure can leave the original problem unresolved or introduce another fault. An unloaded spin can appear successful while a loaded duty fails. Conversely, repeating every earlier test wastes time when the intervention did not affect those claims and their earlier evidence remains applicable.
The check must be able to reveal the defect that would invalidate the receiving functioning claim.
MNT.10:3 - Forces
Representative testing improves evidence but can consume the outage and create its own controlled exposure. A short test can support an immediate operating claim while leaving long-horizon reliability unresolved. Stronger assurance may require a specialist or independent return; its value and requirements depend on the actual consequence, not the number of signatures collected.
MNT.10:4 - Solution
State the required functioning claim, actual configuration, operating envelope and relevant horizon. Recover the operating and engineering acceptance basis. Select the performance, protection or interaction properties whose failure would change the return-to-use decision.
Relate the intervention to those claims. Identify the functioning it was intended to restore and credible faults it could have introduced. Use current adequate evidence for unaffected claims where its subject, conditions and scope still fit. A component or configuration change that invalidates that evidence reopens the affected check.
Choose checks that can discriminate the relevant success and failure states. Use the applicable equipment procedure, measurement basis and competent providers. Where real operating conditions cannot be represented, state what the test does and does not establish. A measurement needs suitable range, uncertainty and operating context for its acceptance comparison.
Plan the check’s controlled state transitions with MNT.8 and its time with MNT.7. Verification that requires energization or other exposure does not inherit unrestricted permission from the earlier protected repair. The applicable procedure governs how the test state is established and ended.
Compare observed outcomes with the stated basis. Retain the actual subject, load, duration and material limitations. A passing result supports the named claim only at that scope. A failed result returns to the affected diagnosis, intervention or engineering question; unrelated passing tests do not cancel it.
Return qualified functioning evidence. A restricted-use claim may be supportable when unrestricted use is not, provided the relevant acceptance and authority conditions allow that distinction. Certification or an independent check is obtained where the concrete use requires it. Do not impose one on every functioning question, or omit an operative one merely because a task looks routine.
Stop when the receiving functioning question is adequately answered. A recurrence or life-extension claim may remain unresolved without defeating the narrower current-use result. Select further evidence only when its obtainable contribution or operative requirement justifies it.
MNT.10:5 - Archetypal Grounding
For the extended constructed PS17 case, the tested installed configuration is C42, with the bearing replacement recorded in MNT.9. The following values are invented to demonstrate a comparison; they are not pump acceptance limits.
The case’s agreed immediate-duty basis requires at least 20 litres per second at a differential pressure of at least 150 kilopascals during a 30-minute representative run. Its supplied acceptance rule is simple comparison of the reported values with those limits, using an already qualified measurement basis for this range and duty. The premise includes a prior assessment of calibration and measurement uncertainty, with the resulting decision risk accepted for this limited claim; it does not assume zero uncertainty or make simple comparison suitable for every use. Instrument drift or changed measurement conditions that invalidate that assessment reopen the comparison.
Under those supplied conditions, the constructed observation is 20.8 litres per second at 154 kilopascals throughout that run, with the applicable equipment-specific condition checks also satisfied: 20.8 exceeds 20 and 154 exceeds 150 under the stated rule. The 45-minute test allowance in MNT.7 includes this run and its controlled transitions.
Those observations support the stated immediate duty in the tested envelope. They do not establish performance at an untested winter peak, an as-new lifetime or elimination of the long-horizon recurrence mechanism. The operator receives that scope explicitly.
If the loaded test instead reaches only 18 litres per second, the performed bearing replacement can still be correctly recorded while the required functioning claim fails. The team returns to diagnosis or the relevant engineering question. A test record with a completed checkbox cannot convert that result into restored service.
MNT.10:6 - Bias-Annotation
The effort already spent on repair creates pressure to interpret a marginal test as success. A familiar easy-to-measure property can also displace the required operating contribution. State the acceptance basis before reading the outcome where that prevents retrospective adjustment.
MNT.10:7 - Conformance Checklist
Does the evidence concern the actual resulting configuration and required use? Can the selected checks expose the intervention’s relevant failure or introduced fault? Are measurement and test conditions suitable for the claim? Are unchanged evidence and unresolved portions used at their true scope? Are required specialist or independent returns present where applicable?
A supported current-use answer closes this question. It does not claim long-term reliability or authorize resumed use by itself.
MNT.10:8 - Common Anti-Patterns and How to Avoid Them
“Part replaced” is used as evidence of service. Test the functioning the recipient actually needs. “It ran unloaded” becomes permission for full-duty operation. Qualify the operating envelope or obtain the evidence that changes that use.
Every historical test is repeated after a small change. Reopen the claims actually affected, while preserving any concrete requirement for the current verification.
MNT.10:9 - Consequences
The operator receives an applicable functioning result and can distinguish it from completed maintenance work. Some repairs return for further action; some systems support only a narrower use. Verification effort is concentrated on claims and consequences rather than repeated by checklist inertia.
MNT.10:10 - Architectural Rationale
The Method is separate from both intervention and release because their outcomes can differ. A task can be performed correctly without restoring the required contribution, and functioning can be established while control or permission remains unresolved.
Claim-specific checking permits adequate prior evidence to remain useful. It also makes a genuine configuration or load change visible as a reason to reopen the affected conclusion.
MNT.10:11 - SoTA-Echoing
The practice question is what evidence warrants a restored-functioning claim after maintenance. This pattern adapts FPF FPF B.3’s use-specific assurance and FPF C.16’s measurement discipline to intervention-induced failure and operating-envelope checks. Against task-sign-off or indiscriminate retesting, the Method selects checks for the functioning claims and reuses adequate evidence for unaffected claims. The PS17 comparison under load illustrates this reasoning. The trade-off is retaining an explicitly limited immediate-use result instead of claiming lifetime restoration. Equipment procedures supply the concrete acceptance criteria; this synthesis does not establish universal test values. Reopen when configuration, required duty, consequence or the earlier evidence’s applicability changes.
MNT.10:12 - Relations
MNT.1 supplies the required functioning and MNT.9 the performed intervention and resulting state. MNT.8 governs test protection; MNT.7 includes its time. MNT.11 consumes the supported functioning claim for hand-back. MNT.12 retains the useful evidence and MNT.13 addresses later recurrence learning. FPF FPF B.3, FPF A.10 and FPF C.16 support assurance, evidence and measurement.
MNT.10:End
MNT.11 - Hand Back and Authorize Resumed Use after Maintenance, with Certification Where Required
Type: Method Status: Stable
MNT.11:1 - Problem frame
Use this pattern when maintenance control is being returned to operation and the receiving person needs a supported basis to resume use. The work is complete and functioning has been checked, but restrictions, configuration changes or required release authority are still unresolved.
Reconcile the evidence and actual state, obtain certification where the concrete use requires it, transfer control and establish the operative permission for resumed use. The result can be unrestricted use, supported restricted use or the precise missing condition. This pattern is not a prerequisite for completing maintenance advice.
MNT.11:2 - Problem
Task completion, functioning evidence, a certificate and permission to operate can support different claims. Treating them as one “released” status can leave the operator unaware of an outstanding limitation or can imply authority that the signer does not hold.
Hand-back can also fail physically: the expected configuration, controls, access arrangements or temporary restrictions may not match what is actually returned.
MNT.11:3 - Forces
Operation needs a clear timely return, while relevant assurance and protection cannot be inferred from urgency. A restricted use can preserve service but imposes conditions that the receiving people must be able to maintain. Excessive generic sign-offs add delay; missing an applicable release condition can invalidate the intended use.
MNT.11:4 - Solution
Identify the receiving use and its decision holder. Recover what that holder needs to take control: the actual configuration, supported functioning, material unfinished work and restrictions. The receiving use may differ from the original unrestricted plan; make that change explicit.
Reconcile the intervention and verification accounts with the actual returned state. Confirm the relevant temporary arrangements have the disposition required by the applicable procedure. A temporary test configuration is not assumed to be the final operating configuration. Where actual state remains unknown, identify the observation or competent return that can resolve it.
Obtain certification or independent returns when the equipment, contract, rule or consequence requires them. Identify the claim each return supports and the authority of its issuer for that scope. A certificate about a component or specified task does not automatically establish the whole System’s readiness for every use.
Resolve remaining limitations through the applicable decision. Some defects or unfinished work permit a defined restricted use; others prevent the intended operation. The restriction must be technically supported, permitted and practically maintainable by the receiving operation. If no such basis exists, return the unmet condition rather than relabelling the state as temporary permission.
Transfer control so that maintenance and operation know who controls the next state change. Communicate the configuration and conditions that change the receiver’s action, using the existing hand-back arrangement. One person may hold both responsibilities, but the evidence and decisions remain distinguishable.
Record or communicate the resulting permission at the level the actual use and operative requirements need. Do not create a universal release certificate for every machine. Conversely, a framework’s preference for a small useful result cannot cancel a concrete requirement.
Reopen the hand-back result when its configuration, functioning, restrictions or authority basis changes. A completed maintenance recommendation remains usable within its earlier scope even if the proposed intervention’s release is still unavailable.
MNT.11:5 - Archetypal Grounding
In the extended PS17 case, MNT.9 records the bearing intervention and installed configuration C42. MNT.10 supports the stated immediate duty, not an untested winter peak or long-term recurrence claim.
The authorized receiving operator reconciles the returned state with those results. The applicable restoration procedure is completed, relevant temporary test arrangements have their required disposition, and control is transferred. The operating decision then permits the supported resumed use within the case’s conditions. These events are constructed teaching observations, not a real authorization.
In a limited branch, the functioning check is satisfactory but the required receiving authority is unavailable. The functioning evidence remains valid at its scope, while the intended resumed-use decision is outstanding. The team does not treat the technician’s task-completion entry as a substitute.
Aviation illustrates why the distinction matters. EASA’s September 2025 Part-145 guidance distinguishes certification of the specified maintenance from the separate responsibility for an aircraft’s continuing airworthiness. This dated illustration is not a complete current legal basis and is not transferred as a certification requirement for PS17.
MNT.11:6 - Bias-Annotation
“Released” is often a single software status even when several people and claims are involved. Recover its meaning for the receiving use. Operators can also accept an inconvenient restriction in the moment without having the means to maintain it through the next shift.
MNT.11:7 - Conformance Checklist
Can the receiving person identify the actual returned configuration and supported functioning? Are material unfinished work and restrictions resolved for the intended use? Are required certificates or independent returns applicable and issued within their authority? Has control been transferred, and is the resumed-use permission supported?
A qualified restricted-use or missing-condition answer can close the hand-back question. It does not automatically complete the intended unrestricted operation.
MNT.11:8 - Common Anti-Patterns and How to Avoid Them
A component certificate is read as whole-System permission. Recover the certified claim and the still-needed operating decision. A successful test is treated as a physical hand-back while temporary controls remain in the test state. Reconcile actual restoration and control.
A recommendation is withheld until release paperwork exists. Return the adequate advice at its own boundary; obtain release only for the selected actual use.
MNT.11:9 - Consequences
The receiver knows what can be used, under which conditions and who controls the next action. A technically successful repair may still await permission; a supported restricted use may return earlier than an unrestricted one. Communication is focused on action-changing conditions and applicable requirements.
MNT.11:10 - Architectural Rationale
Hand-back joins the evidence and control needed by operation without collapsing their kinds. It remains separate from MNT.10 because “functioning supported” and “use permitted” can truthfully have different outcomes. Certification is a conditional contributor, not the universal definition of maintenance completion.
MNT.11:11 - SoTA-Echoing
The practice question is what a maintenance completion claim permits the receiver to infer. This pattern adapts the bounded certification distinction in EASA’s September 2025 Part-145 guidance, GM1 145.A.50(a). Against a single undifferentiated release status, the Method uses separate reconciliation of functioning, certification, control and permission. It accepts a small amount of explicit hand-back reasoning to prevent an unsupported whole-use claim. The edition notice identifies unincorporated later requirements; live aviation work needs its applicable current legal sources. Reopen when the receiving use, state or permission basis changes.
MNT.11:12 - Relations
MNT.9 supplies performed-work evidence and MNT.10 qualified functioning. MNT.8 supplies the protection and restoration conditions that remain applicable; MNT.12 preserves configuration continuity. MNT.1 identifies the operating control boundary. FPF FPF A.2.8.PER governs permission and FPF B.3 supports claim-specific assurance.