VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Mathematics? | Mean Cumulative Function for Repairable Systems: Recurrent Failures, Risk Sets, Event Counts and Fleet Comparisons

Why mathematics is important becomes concrete when the same machine can fail, be repaired and return to service many times. A first-failure survival curve stops at the first event; the mean cumulative function, or MCF, follows the expected cumulative number or cost of recurrent events as system age increases. It keeps event counts, exposure and censoring on the same time axis.

This guide develops event-history ledgers, risk sets, nonparametric MCF increments, fleet comparisons, uncertainty and operational interpretation. An MCF is a population average, not a promise about one machine. Its shape describes recurrence under the observed repair and operating regime, so changed repair quality, retirement rules or duty cycles can change the curve.

Full chapter index

Chapters 1–5 · Understand the question
  1. Why recurrent failures need their own curve
  2. Build an event-history ledger
  3. The cumulative count process
  4. Population MCF definition
  5. Risk indicator and risk set
Chapters 6–10 · Reproduce the example
  1. Nonparametric MCF increments
  2. A complete fleet calculation
  3. Tied recurrent events
  4. Right censoring and retirement
  5. MCF slope and recurrence rate
Chapters 11–15 · Check assumptions
  1. Mean cumulative cost
  2. Comparing two fleets
  3. Variance and confidence intervals
  4. Within-system dependence
  5. Minimal repair is not required for description
Chapters 16–20 · Explore applications
  1. Repair effectiveness changes interpretation
  2. Terminal events and competing removal
  3. Calendar time versus operating time
  4. Stratification and covariates
  5. Prediction and calibration
Chapters 21–25 · Study and verify
  1. Decision interpretation
  2. Practice activity
  3. Parent and educator guidance
  4. Common misconceptions
  5. Research and next reading

CHAPTER 1 OF 25 · Understand the question

1. Why recurrent failures need their own curve

Back to contents

Repairable systems can contribute several ordered failures, so stopping analysis at the first event discards later operating history. A pump that fails at 200, 500 and 900 hours contributes three cumulative events by 1000 hours. This is the central mathematical mechanism in why recurrent failures need their own curve. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. A recurrence curve does not by itself explain the physical failure mode. Define the recurrent event and restoration rule. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.

Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.

For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.

Contents · Next chapter

CHAPTER 2 OF 25 · Understand the question

2. Build an event-history ledger

Back to contents

Start with the operational question behind build an event-history ledger. For each system, record age or exposure at every event and the last observed age, together with event type and repair information. In the illustrative case, One unit may have events at 120 and 430 hours and be censored at 700 hours. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Calendar time and operating age answer different questions. Choose one exposure scale and preserve both timestamps.

A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.

This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 25 · Understand the question

3. The cumulative count process

Back to contents

Treat the cumulative count process as a model-checking problem rather than a vocabulary exercise. N_i(t) counts how many defined events system i has experienced by age t; its path is a nondecreasing staircase. A history with events at 2, 5 and 8 months has values 0, 1, 2 and 3 across successive intervals. Recompute the example from the raw values and label every unit. Combining unlike event definitions makes the staircase ambiguous. Audit duplicate and reversed timestamps.

The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.

Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 25 · Understand the question

4. Population MCF definition

Back to contents

The mathematics of population mcf definition becomes useful only when its mechanism is explicit. M(t)=E[N(t)] is the population mean cumulative number of recurrent events by age t, or the mean cumulative cost if N is replaced by cumulative cost. Consider the worked illustration: M(1000)=1.4 means 1.4 events per system on average by 1000 hours in the target population. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. The mean need not be an integer and is not the probability of at least one failure. Name the population and response.

There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.

For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.

Primary source: https://doi.org/10.1080/00224065.1988.11979080. Read it for the method and its assumptions; do not transfer its performance claims automatically to another model.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 25 · Understand the question

5. Risk indicator and risk set

Back to contents

Use risk indicator and risk set to practise sensitivity analysis. Y_i(t) indicates that system i is still observed just before t, and Y(t) sums the systems under observation. If 18 of 20 systems remain observed at an event time, the risk set is 18. Before accepting the result, identify the quantity that would change the conclusion most. A unit temporarily down may or may not be exposed depending on the time scale. State when observation and exposure stop.

A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.

Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 25 · Reproduce the example

6. Nonparametric MCF increments

Back to contents

Build a small counterexample for nonparametric mcf increments. At an event age t_j, a Nelson-type estimator adds d_j/Y_j, where d_j is the number of recurrent events and Y_j the systems observed just before that age. The initial example is: Two events among 20 observed systems add 0.10 to the estimated MCF. Then create a nearby case where the usual shortcut becomes unreliable. Using total events divided by the original fleet ignores changing observation. Recompute the risk set at every event age.

Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.

When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 25 · Reproduce the example

7. A complete fleet calculation

Back to contents

Connect a complete fleet calculation to a real decision while protecting the boundary between calculation and judgement. With risk sets 4, 4 and 3 and one event at each age, the estimated MCF after the third event is 1/4+1/4+1/3=0.8333. Each increment is a fleet-average contribution. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. The toy fleet is too small for stable operational claims. Show the event-age table and cumulative sum.

The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.

A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 25 · Reproduce the example

8. Tied recurrent events

Back to contents

When several systems have events at the same recorded age, the numerator is the event count at that age and the denominator is the pre-event risk set. Three events among 30 observed systems add 0.10. This is the central mathematical mechanism in tied recurrent events. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. Coarse timestamp rounding can create artificial ties. Preserve measurement resolution. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.

Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.

For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 25 · Reproduce the example

9. Right censoring and retirement

Back to contents

Start with the operational question behind right censoring and retirement. A system contributes its events and exposure until its final observed age; no failure is invented at censoring. In the illustrative case, A machine still running at study cutoff remains event-free only through the cutoff. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Condition-related retirement can make censoring informative. Record every retirement reason.

A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.

This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 25 · Reproduce the example

10. MCF slope and recurrence rate

Back to contents

Treat mcf slope and recurrence rate as a model-checking problem rather than a vocabulary exercise. Where a smooth derivative is meaningful, the slope of M(t) represents the population recurrence rate with respect to the chosen age scale. A steeper late-life curve indicates faster event accumulation. Recompute the example from the raw values and label every unit. Noisy step slopes should not be read as instantaneous physical laws. Use smoothing cautiously and show the step curve.

The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.

Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 25 · Check assumptions

11. Mean cumulative cost

Back to contents

The mathematics of mean cumulative cost becomes useful only when its mechanism is explicit. Replacing unit event increments with repair costs estimates expected cumulative repair cost by age. Consider the worked illustration: A $300 repair among 15 observed systems adds $20 per system to the cost MCF. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. Nominal costs across years may need inflation or discount treatment. Declare currency and valuation date.

There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.

For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 25 · Check assumptions

12. Comparing two fleets

Back to contents

Use comparing two fleets to practise sensitivity analysis. The difference M_A(t)-M_B(t) shows how expected cumulative events or cost separate over age. A difference of 0.4 repairs at 2000 hours is an average fleet gap, not a count for every unit. Before accepting the result, identify the quantity that would change the conclusion most. Different duty cycles or entry rules can confound the comparison. Align age scales and eligibility.

A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.

Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.

A second primary source is https://doi.org/10.1080/00401706.1995.10484299. Compare the problem definition, estimator and validation rather than quoting one result in isolation.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 25 · Check assumptions

13. Variance and confidence intervals

Back to contents

Build a small counterexample for variance and confidence intervals. Recurrence-data variance estimators aggregate between-system variation while accounting for changing risk sets. The initial example is: Uncertainty widens when few long-lived systems remain. Then create a nearby case where the usual shortcut becomes unreliable. Treating every event as independent understates within-system dependence. Use a recurrence-data variance method.

Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.

When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 25 · Check assumptions

14. Within-system dependence

Back to contents

Connect within-system dependence to a real decision while protecting the boundary between calculation and judgement. Events from one system share design, environment and repair history, so they are rarely independent repetitions. A frail machine may contribute several early failures. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. An MCF estimates a mean without specifying all dependence, but prediction may need more structure. Cluster calculations by system.

The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.

A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 25 · Check assumptions

15. Minimal repair is not required for description

Back to contents

The nonparametric MCF can describe observed recurrent events without assuming every repair restores the system to a particular age. Repairs may be imperfect yet the curve still summarises the observed regime. This is the central mathematical mechanism in minimal repair is not required for description. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. A physical model of repair effectiveness needs additional assumptions. Separate descriptive MCF from renewal modelling. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.

Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.

For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 25 · Explore applications

16. Repair effectiveness changes interpretation

Back to contents

Start with the operational question behind repair effectiveness changes interpretation. Perfect, minimal and imperfect repairs imply different future-risk mechanisms after an event. In the illustrative case, Replacing a failed module may restore only one subsystem. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. The same MCF shape can arise from different mechanisms. Collect repair actions and component identities.

A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.

This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 25 · Explore applications

17. Terminal events and competing removal

Back to contents

Treat terminal events and competing removal as a model-checking problem rather than a vocabulary exercise. Scrapping, catastrophic failure or loss to observation can stop future recurrent events and alter the target process. A unit retired after a severe failure cannot generate later routine repairs. Recompute the example from the raw values and label every unit. Ordinary independent censoring may be implausible for terminal removal. Use joint or multistate methods when removal is informative.

The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.

Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 25 · Explore applications

18. Calendar time versus operating time

Back to contents

The mathematics of calendar time versus operating time becomes useful only when its mechanism is explicit. Calendar age includes idle and repair periods, while operating age measures active exposure. Consider the worked illustration: A standby generator may be ten years old but have only 600 operating hours. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. Mixing the scales distorts denominators and decisions. Report both and choose one estimand.

There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.

For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 25 · Explore applications

19. Stratification and covariates

Back to contents

Use stratification and covariates to practise sensitivity analysis. Fleet MCFs can be plotted by design, environment or maintenance policy before regression modelling. Compare indoor and coastal installations at common operating ages. Before accepting the result, identify the quantity that would change the conclusion most. Small strata produce unstable late curves and multiple comparisons. Predefine important groups.

A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.

Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 25 · Explore applications

20. Prediction and calibration

Back to contents

Build a small counterexample for prediction and calibration. A recurrent-event model can predict future counts, but predictions should be checked against observed MCFs in later cohorts. The initial example is: Compare predicted and observed average repairs by 500, 1000 and 1500 hours. Then create a nearby case where the usual shortcut becomes unreliable. Training fit does not establish transportability. Use temporal or site holdouts.

Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.

When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.

Contents · Previous chapter · Next chapter

CHAPTER 21 OF 25 · Study and verify

21. Decision interpretation

Back to contents

Connect decision interpretation to a real decision while protecting the boundary between calculation and judgement. Translate expected event or cost accumulation into inspection, spares or redesign questions with consequences and uncertainty. A rising cost MCF may motivate investigation before it justifies replacement. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. MCF alone does not optimise a maintenance policy. Combine it with cost and risk thresholds.

The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.

A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.

Contents · Previous chapter · Next chapter

CHAPTER 22 OF 25 · Study and verify

22. Practice activity

Back to contents

Construct four system histories, calculate every d_j/Y_j increment and plot the fleet MCF. Then censor one system earlier and predict which late increments change. This is the central mathematical mechanism in practice activity. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. Toy data cannot support a product claim. Keep the ledger beside the graph. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.

Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.

For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.

Contents · Previous chapter · Next chapter

CHAPTER 23 OF 25 · Study and verify

23. Parent and educator guidance

Back to contents

Start with the operational question behind parent and educator guidance. MCF work connects fractions, cumulative graphs, averages, probability and careful denominators. In the illustrative case, Ask why a second failure still matters after a first repair. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Terminology can obscure a simple cumulative-average idea. Begin with four staircase histories.

A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.

This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.

Contents · Previous chapter · Next chapter

CHAPTER 24 OF 25 · Study and verify

24. Common misconceptions

Back to contents

Treat common misconceptions as a model-checking problem rather than a vocabulary exercise. An MCF is not a survival probability, not the expected time to first failure and not proof that failures form a Poisson process. M(1000)=2 does not mean every system fails exactly twice. Recompute the example from the raw values and label every unit. Reading slope without the age scale creates unit errors. Translate every ordinate into a sentence.

The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.

Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.

Continue with the Mathematics Learning Hub, the eduKate Mathematics Learning System, the approach to learning mathematics, the Singapore Mathematics curriculum overview, the cross-subject learning approach and the previous reliability article. Each destination has its own role: subject navigation, learning method, school-to-advanced progression, or continuity with the latest reliability mechanism.

Contents · Previous chapter · Next chapter

CHAPTER 25 OF 25 · Study and verify

25. Research and next reading

Back to contents

The mathematics of research and next reading becomes useful only when its mechanism is explicit. Nelson introduced graphical repair-data analysis and later confidence limits for censored recurrence data. Consider the worked illustration: Reproduce the nonparametric increment table before using specialised software. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. The papers support estimation, not a universal repair mechanism. Read assumptions beside the event ledger.

There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.

For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.

Quick answers

What should I calculate first? Start with the estimand or failure event, then a simple baseline.

Does the advanced method guarantee accuracy? No. It needs input, numerical and model checks.

Which school mathematics matters? Algebra, graphs, probability, functions and careful units all contribute.

How can a student practise safely? Use fictional or open benchmark data and preserve every intermediate value.

What makes a career claim responsible? Describe how the mathematics is used without promising admission, salary or employment.

Contents · Previous chapter · Mathematics Learning Hub

Extended practice laboratory

Practice case 1: Why recurrent failures need their own curve

Setup: Use this chapter’s illustrative case: A pump that fails at 200, 500 and 900 hours contributes three cumulative events by 1000 hours.

Task: Define the recurrent event and restoration rule.

Checking target: A recurrence curve does not by itself explain the physical failure mode.

Practice case 2: Build an event-history ledger

Setup: Use this chapter’s illustrative case: One unit may have events at 120 and 430 hours and be censored at 700 hours.

Task: Choose one exposure scale and preserve both timestamps.

Checking target: Calendar time and operating age answer different questions.

Practice case 3: The cumulative count process

Setup: Use this chapter’s illustrative case: A history with events at 2, 5 and 8 months has values 0, 1, 2 and 3 across successive intervals.

Task: Audit duplicate and reversed timestamps.

Checking target: Combining unlike event definitions makes the staircase ambiguous.

Practice case 4: Population MCF definition

Setup: Use this chapter’s illustrative case: M(1000)=1.4 means 1.4 events per system on average by 1000 hours in the target population.

Task: Name the population and response.

Checking target: The mean need not be an integer and is not the probability of at least one failure.

Practice case 5: Risk indicator and risk set

Setup: Use this chapter’s illustrative case: If 18 of 20 systems remain observed at an event time, the risk set is 18.

Task: State when observation and exposure stop.

Checking target: A unit temporarily down may or may not be exposed depending on the time scale.

Practice case 6: Nonparametric MCF increments

Setup: Use this chapter’s illustrative case: Two events among 20 observed systems add 0.10 to the estimated MCF.

Task: Recompute the risk set at every event age.

Checking target: Using total events divided by the original fleet ignores changing observation.

Practice case 7: A complete fleet calculation

Setup: Use this chapter’s illustrative case: Each increment is a fleet-average contribution.

Task: Show the event-age table and cumulative sum.

Checking target: The toy fleet is too small for stable operational claims.

Practice case 8: Tied recurrent events

Setup: Use this chapter’s illustrative case: Three events among 30 observed systems add 0.10.

Task: Preserve measurement resolution.

Checking target: Coarse timestamp rounding can create artificial ties.

Practice case 9: Right censoring and retirement

Setup: Use this chapter’s illustrative case: A machine still running at study cutoff remains event-free only through the cutoff.

Task: Record every retirement reason.

Checking target: Condition-related retirement can make censoring informative.

Practice case 10: MCF slope and recurrence rate

Setup: Use this chapter’s illustrative case: A steeper late-life curve indicates faster event accumulation.

Task: Use smoothing cautiously and show the step curve.

Checking target: Noisy step slopes should not be read as instantaneous physical laws.