Skip to main content

​
Overview

The Hazard Tracking Risksheet is a MIL-STD-882E-compliant risk analysis document that captures the complete hazard lifecycle: from identification through mitigation planning to residual risk acceptance. Unlike FMEA risksheets that analyze failure modes at the component level, Hazard Tracking operates at the system level, identifying operational hazards and their mitigation path. Document Type: riskSpecification
Risk Item Type: hazard
Template Location: modules/RiskTemplates/HazardTrackingTemplate/

​
Column Structure

The risksheet organizes 19 columns into 6 functional header groups:

​
System Identification

ColumnTypePurpose
System ElementLinkLinks hazard to system element (parent reference)
Hazard tracking is system-level; each hazard is associated with one system element to establish scope.

​
Hazard Identification

ColumnTypePurpose
CategoryEnumHazard classification (e.g., structural, electrical, operational)
PhaseEnumOperational phase when hazard may occur (e.g., ground operations, cruise, landing)
HazardTextConcise hazard statement
DescriptionLong TextDetailed hazard description and context
CauseLong TextRoot cause of the hazard
ConsequenceLong TextPotential adverse effects if hazard occurs
These columns form the identification block where hazard analysts document what hazard exists, when it may occur, why it occurs, and what effects it produces.

​
Initial Risk Assessment

ColumnTypePurpose
Initial SeverityEnumSeverity category before mitigation (I, II, III, IV)
Initial ProbabilityEnumOccurrence probability before mitigation (A, B, C, D, E)
Initial HRICalculatedHazard Risk Index—auto-calculated from severity × probability
The Initial Risk Assessment columns capture the unmitigated hazard risk. The Hazard Risk Index (HRI) is automatically calculated using the MIL-STD-882E Table II risk matrix.

​
Safety Controls (Mitigations)

ColumnTypePurpose
Risk Control IDLinkLinks to risk control work item (mitigation measure)
Risk Control TitleTextName of mitigation action
Risk Control StatusEnumStatus of mitigation (e.g., open, in-progress, implemented)
ResponsibleUserTeam member assigned to implement mitigation
This block shows the mitigation path: which risk controls address the hazard, their implementation status, and accountability.

​
Residual Risk Assessment

ColumnTypePurpose
Residual SeverityEnumSeverity category after mitigation (I, II, III, IV)
Residual ProbabilityEnumOccurrence probability after mitigation (A, B, C, D, E)
Residual HRICalculatedHazard Risk Index after mitigation
Residual risk columns mirror the Initial Assessment block, allowing side-by-side comparison of risk reduction achieved by mitigation.

​
Risk Acceptance

ColumnTypePurpose
Acceptance AuthorityUserStakeholder with approval authority (e.g., safety officer, certification authority)
Acceptance StatusEnumStatus of risk acceptance decision (e.g., accepted, waived, pending review)
The Acceptance block captures formal approval of residual risk by appropriate authority, completing the hazard lifecycle.

​
Hierarchy Structure

Hazard Tracking uses a 4-level hierarchy: diagram Each level can be expanded or collapsed for focused analysis. Row headers display the hierarchy level with visual indentation.

​
Severity and Probability Classification

​
Severity Categories (Roman Numerals)

CategoryLevelColorDescription
ICatastrophicRedLoss of function and threat to continued safe flight
IICriticalOrangeReduced functional capability or safety margin
IIIMarginalYellowMinor reduction in safety margins or capabilities
IVNegligibleGreenMinimal impact on safety or function

​
Probability Categories (Letters A–E)

CategoryLevelDescription
AFrequentExpected to occur frequently during system lifetime
BProbableWill occur multiple times during system lifetime
COccasionalLikely to occur at least once during system lifetime
DRemoteUnlikely but possible during system lifetime
EImprobableExtremely unlikely to occur during system lifetime

​
Hazard Risk Index (HRI) Auto-Calculation

The Hazard Risk Index is automatically calculated from the MIL-STD-882E Table II risk matrix, which combines severity and probability into a single risk level: HRI Matrix: Severity (I–IV) × Probability (A–E) → Risk Level
ProbabilityCat ICat IICat IIICat IV
A (Frequent)HighHighHighSerious
B (Probable)HighHighSeriousMedium
C (Occasional)HighSeriousMediumMedium
D (Remote)SeriousMediumMediumLow
E (Improbable)MediumMediumLowLow
HRI Color Coding:
HRI LevelColorAction
HighRedUnacceptable — mitigation required
SeriousOrangeMay require mitigation depending on risk tolerance
MediumYellowReview and document acceptance decision
LowGreenAcceptable risk
The formula is applied independently to Initial and Residual risk columns, enabling risk reduction tracking.
The exact JavaScript formulas for HRI calculation and any configurable thresholds should be verified in the application’s Velocity template and risksheet.json configuration.

​
Available Views

The Hazard Tracking Risksheet provides four pre-configured views for different analysis workflows:

​
Full Analysis View

Complete risksheet with all 19 columns and 4-level hierarchy. Used for comprehensive hazard assessment and documentation.

​
Risk Overview View

Side-by-side comparison of Initial and Residual HRI columns, emphasizing risk reduction achieved. Useful for reviewing mitigation effectiveness.

​
Hazard Log View

Focused on hazard identification columns (Category, Phase, Hazard, Description, Cause, Consequence). Used during initial hazard discovery and documentation.

​
Actions View

Shows hazard identification, mitigations, responsible parties, and residual risk. Tracks mitigation task ownership and status. Includes the Responsible assignee column pulled from the linked risk control task.

​
Document Instance Pattern

Hazard Tracking documents follow the naming convention: 
Document Title: <System Name> Hazard Tracking (MIL-STD-882E)
Document ID: <Project Prefix>-HTS-###
Example: MIL-STD-882E-HTS-001
Each document instance is a riskSpecification type linked to a HazardTrackingTemplate containing preconfigured risksheet.json, top panel, and PDF export templates.

​
Metadata Fields

FieldValueNotes
Document TyperiskSpecificationRisk specification (not requirements or design)
TemplateRiskTemplates/HazardTrackingTemplatePre-configured MIME-type template
System ElementSystem-level onlyHazard tracking scoped to whole system, not subsystems
StatusWorkflow-drivenOpen → In Review → Approved
VersionAuto-incrementedSupports revision tracking and PDF export comparison

​
Top Panel and Navigation

The Hazard Tracking top panel displays:
  • MIL-STD-882E Info Banner — Standard description and compliance notice
  • Metadata Row — Document status, version, team, last updated date
  • Risk Matrix — Interactive JavaScript 4×5 risk matrix (same as FMEA) showing acceptable/investigation/unacceptable zones
Unlike FMEA risksheets (DFMEA, SFMEA), Hazard Tracking does not include an embedded JavaScript 5×5 probability × severity risk matrix in the top panel. The HRI calculation is performed entirely by risksheet.json formulas in the columns themselves.

​
Associated Documents

Hazard Tracking documents are typically cross-referenced with:
  • Functional Hazard Assessment (FHA) — System-level failure conditions and classification
  • System Safety Assessment (SSA) — Detailed mitigation planning and risk acceptance
  • Risk Control Plan — Master list of all risk controls across the project
  • Design FMEA (DFMEA) — Component-level failure mode analysis supporting hazard mitigation

​
Risk Control Linking

Each hazard can be linked to one or more risk controls (mitigation measures) via the Risk Control ID and Risk Control Title columns. The link establishes traceability from hazard to implemented mitigation:
  • Risk Control Status tracks implementation progress (e.g., Design Mitigation → Implementation → Testing)
  • Responsible column shows task ownership for accountability
  • Residual Severity/Probability reflects the risk after control is in place
This enables tracking of hazard → mitigation → verification workflows.

​
Verification and Acceptance

The hazard lifecycle concludes with formal acceptance:
  1. Mitigation Status — All mitigating risk controls move to “Implemented” or “Verified”
  2. Residual Risk Assessment — Severity and Probability re-evaluated with mitigations in place, HRI recalculated
  3. Acceptance Authority Review — Designated authority (safety officer, program manager, certification authority) reviews residual risk
  4. Acceptance Decision — Hazard is either:
    • Accepted — Residual risk within acceptable limits
    • Waived — Residual risk accepted despite exceeding limits (with documented justification)
    • Pending — Awaiting additional information or mitigation
The specific acceptance authority roles, waiver justification requirements, and audit trail capabilities should be verified in the application’s workflow configuration and role-based dashboards.

​
Configuration Details

Hazard Tracking configuration details including formulas, cell styling rules, JavaScript calculations, and workflow transitions are defined in the template’s risksheet.json and Velocity templates. Consult the application for exact property names, defaults, and validation rules.

​
Export and Reporting

Hazard Tracking documents support:
  • PDF Export — Multi-section report: cover page, document properties, main hazard records table, mitigation controls table, risk acceptance summary
  • Revision Comparison — Side-by-side comparison of hazard changes between document versions
  • Metrics Export — Risk distribution statistics (High/Serious/Medium/Low HRI counts)
The PDF export template is defined in HazardTrackingTemplate/attachments/risksheetPdfExport.vm and generates a formal deliverable suitable for regulatory compliance demonstration.
Code: modules/RiskTemplates/HazardTrackingTemplate/attachments/risksheet.json (0.71) · modules/RiskTemplates/RiskControlPlanTemplate/attachments/risksheet.json (0.67) · modules/RiskTemplates/PSSATemplate/attachments/risksheet.json (0.65) · modules/Risks/COMPLIANCE-001/module.xml, modules/Risks/MIL-STD-882E-HTS-001/module.xml, modules/Risks/SEC-THREAT-001/module.xml, modules/Risks/SFMEA-SUB-001/module.xml, modules/Risks/SFMEA-SUB-002/module.xml, modules/Risks/SFMEA-SUB-003/module.xml (0.64) · modules/RiskTemplates/FHATemplate/attachments/risksheet.json (0.60) · modules/RiskTemplates/DFMEATemplate/attachments/risksheetTopPanel.vm, SubSystem-FMEATemplate/attachments/risksheetTopPanel.vm, System-FMEATemplate/attachments/risksheetTopPanel.vm, PFMEATemplate/attachments/risksheetTopPanel.vm, HazardTrackingTemplate/attachments/risksheetTopPanel.vm, DFMEATemplate/attachments/risksheetPdfExport.vm, SubSystem-FMEATemplate/attachments/risksheetPdfExport.vm, System-FMEATemplate/attachments/risksheetPdfExport.vm, PFMEATemplate/attachments/risksheetPdfExport.vm (0.60) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.60) · modules/RiskTemplates/CCATemplate/attachments/risksheet.json (0.60) · modules/RiskTemplates/ComplianceTemplate/attachments/risksheet.json (0.59) · modules/RiskTemplates/DFMEATemplate/module.xml, modules/Risks/DFMEA-CMP-PSU/module.xml, modules/_default/WholeRTMSheet/module.xml, modules/Requirements/CUSTOMER-REQS/module.xml (representative of ~50 module.xml files across all spaces and templates) (0.58)