This guide treats how to investigate repeated availability losses as a technical subject with observable inputs, especially event timeline, contributing factors and corrective action.
Planning connects technical limits with operational decisions. Record capacity, assumptions, owners and review dates so a proposal can be checked again when equipment or conditions change.
Event Timeline
The role of event timeline is best understood through a controlled comparison. Hold unrelated inputs constant, change one relevant condition and observe the response. Then check whether contributing factors moved in the expected direction. A mismatch is a prompt to inspect the model, not to hide the data.
- Evidence: a dated record for event timeline.
- Cross-check: compare it with contributing factors.
- Review trigger: repeat the check after a material change affecting event timeline.
Contributing Factors
Normalize contributing factors before using it in a table or calculation. Convert units, align the time period and retain the original value. If corrective action comes from a different source, document that source separately so readers can reproduce both sides of the comparison.
- Evidence: a dated record for contributing factors.
- Cross-check: compare it with corrective action.
- Review trigger: repeat the check after a material change affecting contributing factors.
Corrective Action
Use corrective action as a testable input, not a general description. Record what produced the value, the interval it covers and any exclusions. Compare the record with event timeline only after both use compatible boundaries; otherwise the apparent difference may come from definitions rather than performance.
- Evidence: a dated record for corrective action.
- Cross-check: compare it with event timeline.
- Review trigger: repeat the check after a material change affecting corrective action.
How to investigate repeated availability losses: evaluation sequence
- Write the exact decision involving event timeline.
- Collect contributing factors using the same observation period.
- Test how the conclusion changes when corrective action moves.
- Save the source values, conversions and date of review.
Reference for Mining Planning
Verify the underlying context with NIST Cybersecurity Framework. For values that change over time, use a current source and record its retrieval date.
