Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 22:54:38 UTC

MNT.2:4 - Solution

Start from the required function and a failure account sufficient to distinguish policy alternatives. Identify the loss of function, credible mechanisms and consequences. When one policy covers several mechanisms, check each mechanism that could justify a different task. Retain uncertainty where it matters rather than inventing a lifetime distribution from sparse events.

Construct the plausible task alternatives. Use the table to compare when each task family can work and what can defeat it.

Task familyWhat can make it usefulWhat can defeat it
Corrective or deliberate run-to-failureFailure is detectable and its consequence, recovery demand and collateral effects are acceptable for the use.A hidden protection loss, unacceptable exposure or unavailable recovery capability makes waiting untenable.
Age- or usage-based actionFailure behaviour and restoration effectiveness support acting before a relevant age or usage condition.Calendar age is a weak predictor, or replacement repeatedly introduces faults.
Condition-based actionAn observable condition changes early enough to support a useful response.The relevant failure is not detected, the alarm is unreliable, or response lead time exceeds the usable warning.
Failure-findingA task reveals loss of a function that normal operation does not expose, such as a standby protective function.The test misses the relevant failure or creates unacceptable exposure without adequate controls.
Opportunity-based combinationShared access or downtime makes coordinated tasks worthwhile.Bundling consumes useful life, creates interference or overcommits the outage.

For each credible alternative, explain what performing the task changes. Include imperfect repair, task-induced defects and residual failure modes when material. If no acceptable maintenance action addresses a serious failure, return the specific redesign, redundancy or changed-use question to engineering or operation. Adding inspections that cannot reveal or alter the failure is not a substitute.

For condition-based work, reason across the complete response. The usable interval between detectable degradation and unacceptable functioning must accommodate detection delay, interpretation, obtaining support, access and the selected intervention, with uncertainty appropriate to the consequence. This is an applicability question, not a universal formula for a safe interval. A local detection threshold or interval needs the equipment and operating evidence that supports it.

Compare alternatives using the receiving use’s relevant values: loss of service, exposure, labour, material, disturbance, environmental effects and uncertainty. Use comparable operating horizons and state deliberately accepted trade-offs. Existing evidence may settle the choice. Select further investigation only when an attainable answer could change it enough to justify acquisition, interpretation, delay and displaced work.

State the chosen policy in actionable terms. Name the applicable population or configuration, task, trigger or interval basis, relevant support assumptions, response to an out-of-scope condition and the evidence or changed use that would reopen it. Where an operative requirement fixes a task, preserve its current force. A separate merits appraisal may support a request to the authorized rule holder; it does not authorize unilateral relaxation.

MNT.2:4.1 - Turn a task family into a usable policy

Use an adequate existing task and trigger directly. When they are unsettled, construct candidate rules at the resolution needed for the decision. Specify what observation, age, usage or opportunity starts the response, when that information becomes available, what action follows and what functioning is expected afterwards. A condition-based candidate includes its observation schedule and response; a scheduled replacement includes what happens if failure occurs first.

Apply each candidate to the same supported failure and operating account. Follow the relevant histories from functioning through degradation, discovery and response to the resulting state. Include a failure before the planned task and the condition after imperfect repair where those branches matter. Use MNT.3’s failure account and MNT.4’s condition account; obtain an applicable equipment-specific model when projection needs further transition or task-effect evidence. If a consequence needed for the comparison cannot be supported, return that missing contribution rather than assign the desired effect to the task.

Derive the consequences of those histories over a common horizon. Count functioning obtained, losses before detection or restoration, repeated task demand and support constraints. Weight possible histories only where the probability basis supports it; otherwise compare the supported bounds or scenarios. Keep binding requirements and unacceptable consequences visible when comparing burden. Use FPF C.11 with the resulting alternatives and comparison basis to select a policy, retain several alternatives or return the unsettled choice.

For a condition-based candidate, place detection and response on one time basis. Let W be a supported lower bound on the warning from the proposed detectable condition to unacceptable functioning under the intended duty. Let I bound the wait to the next observation and L bound the elapsed time for subsequent interpretation, support, access and intervention, including the selected uncertainty allowance. Where that bounded timing model applies, test I + L <= W. Derive elapsed L from the sequence of tasks and the work that can overlap through MNT.5 and MNT.7. Shorter sampling, an earlier detectable trigger or prepared support are different candidate changes; each needs its own measurement or feasibility basis. A timing fit still needs adequate detection and an effective response.

For a hidden protective function, relate the test interval to the period during which the failed function could remain undiscovered and the consequences of a demand during that period. The test’s coverage, any exposure it creates and the relevant failure-and-demand account determine whether the interval is acceptable. Continuing normal production supplies no observation of that protective function.

MNT.2:4.1.1 - Build and improve a predictive maintenance option

Use this branch to develop a maintenance policy whose response depends on a forecast or other conditional estimate. An adequate existing estimate and decision rule can be used directly. A competent practitioner’s condition assessment can supply the estimate; fitting a statistical model is one possible means.

Start with the decisions the estimate should improve. Determine the available interventions and windows, what continued operation may lose, and what an earlier intervention consumes or disrupts. Connect observations available at the decision time to an estimate of the relevant failure or functioning, then to an intervention rule. This makes the forecast useful through the action it permits and the functioning that action can obtain.

Apply each candidate rule to the supported histories described above. Compare the resulting functioning and burden, including early interventions, missed failures and delays. Examine which differences between estimates change the chosen response. A smaller prediction error that leaves every consequential action unchanged may add little maintenance value; an error near an action boundary can reverse the choice. Keep the required service and other binding conditions in that comparison.

Construct a better response where an obtainable support change makes it possible. Use MNT.5 to establish how the needed part, provider and preparation can be obtained, and MNT.7 to construct a feasible window and service arrangement. Bring the required lead times, commitments and burdens back into the candidate. Advance preparation can shorten the delay between warning and intervention; another window can make a previously unusable warning actionable. Compare this complete arrangement with the current one, including preparation and recurring support. Recalculate the response rule when those returned conditions change.

When the forecasting or response rule itself needs development, use FPF C.40:4.7. Supply the permitted variations, the observations each variant may use, its feasible interventions and the maintenance consequences by which its use will be judged. Use the consequences to identify estimate errors that change a useful action, then vary the relevant assessment, trigger or response rule. Compare those revisions through the maintenance consequences of their selected actions. Return the forecasting or assessment rule together with its response rule and support conditions. A small comparison of expert assessments or rules can suffice.

If model fitting is useful, one implementation tunes the prognostic model using a loss derived from the interventions selected by a chosen policy. Keep that policy’s windows and consequences with the fitted model. Such tuning can improve maintenance decisions while worsening a prediction score; any required probability calibration claim still needs its own support. Use MNT.3 for a supported failure and task-effect account, including lifetimes censored by replacement. Keep consequences estimated through that account distinct from outcomes observed in maintenance.

Select a feasible change when the current observations, applicable model or reasoned expert estimate make its expected benefit worth its complete burden under the relevant uncertainty. Use ranges, scenarios or a qualitative comparison when they are sufficient. Return the policy and the next executable preparation or intervention decision, with the assumptions whose change could reverse the choice. New data or a trial are needed only when their attainable contribution warrants the burden; a reasonable estimate can justify acting before an improvement has been observed.

MNT.2:4.2 - Compare recurring age-replacement costs when that model fits

Suppose replacement restores the component to an as-new state, successive lifetimes X are independent with the same distribution, intervention duration is negligible, expected cycle duration is positive and finite, and costs cover the relevant consequences. For replacement at age a or earlier failure, derive the two possible endings from the lifetime model, counting a failure at age a as corrective:

  • the cycle’s operating duration is min(X,a);
  • corrective cost Cc applies when X <= a, and planned cost Cp otherwise.

The long-run cost per operating-time unit is

g(a) = [Cc * P(X <= a) + Cp * P(X > a)] / E[min(X,a)].

Compare feasible ages, including continued operation to failure where admissible. This calculation includes how often replacement recurs. Use another model when downtime, imperfect restoration, changing duty or coupled components invalidate these assumptions; a finite service horizon also needs its own end condition. See Arts and colleagues, §2.2.1 for the renewal-reward basis and its limits.