Hazmat Program and Project Management
Hazmat Program and Project Management
This domain tests running a compliant, defensible project: scope, work breakdown structure (WBS), schedule, cost, risk, change control, and stakeholder communication. The technical work fails if the program cannot prove training, records, and contractor oversight.
Core rules
- Define scope, deliverables, assumptions, and acceptance criteria; decompose into a WBS; assign responsibility. Use a critical path method (CPM) schedule and track float. Critical path has zero float; a delay there delays the project.
- Earned value: PV (planned value), EV (earned value), AC (actual cost). CV = EV − AC; SV = EV − PV; CPI = EV/AC; SPI = EV/PV. CPI <1 means over budget; SPI <1 means behind schedule.
- Risk register: probability, impact, owner, trigger, response (avoid, mitigate, transfer, accept). Hold contingency for known risks and management reserve for unknown.
- Compliance program: HASP, training records (HAZWOPER, HazCom, DOT), medical surveillance, audits, waste manifests, and document control. Manage change through written approval before field work.
- Stakeholders: regulators, client, contractors, community. Set reporting cadence and escalation paths.
Worked example
A remediation project has PV = $220,000, EV = $200,000, AC = $250,000. CV = 200,000 − 250,000 = −$50,000 (over budget). SV = 200,000 − 220,000 = −$20,000 (behind schedule). CPI = 200/250 = 0.80; SPI = 200/220 = 0.91. The project is spending more and progressing less than planned. Before approving more field days, check whether the variance is from a scope change, a schedule slip, or unproductive time.
Traps
Do not confuse EV with actual cost. A negative SV does not always mean the team worked slowly-check the baseline. CPI and SPI are ratios, not dollars. “Contingency” is not a slush fund; it is tied to identified risks. Do not let field changes proceed without a change order.