ASP Fellowship II study plan
ASP Fellowship II · Give each week a clear focus.
8 weeks · About 7 hours per week
Fundamentals of Systems Safety and Risk Analysis & Risk Assessment and Risk Acceptance
Define and distinguish the core vocabulary of system safety (hazard, risk, mishap, severity, likelihood, risk index) and write a one-page glossary in your own words
Derive the risk equation variants used in matrix and index methods, and explain when each is preferred over the other
Work through at least six qualitative risk-matrix scoring exercises and justify each severity and likelihood assignment
Map the relationship between system safety and adjacent disciplines (reliability, quality, logistics, occupational safety) and note where boundaries blur
Build a personal formula sheet covering risk definitions, matrix scoring rules, and acceptance categories
Your checkpoint
A 3-5 page personal reference sheet with glossary, risk equations, a filled example risk matrix, and six worked scoring exercises with justifications
Fundamentals of Systems Safety and Risk Analysis & Hazard Identification, Analysis, and Tracking
Compare and contrast the major hazard analysis techniques (PHA, FMEA/FMECA, FTA, ETA, HAZOP, STPA) by inputs, outputs, and stage of life cycle
Construct a fault tree for a simple system with at least three levels and identify minimal cut sets by hand
Construct an event tree for the same system and compute branch probabilities
Explain the role of preliminary hazard lists and hazard checklists in early design, and draft a starter checklist for a hypothetical system
Describe how hazard logs are structured and how hazard status flows from open to closed
Your checkpoint
A technique comparison table plus one hand-drawn fault tree with computed minimal cut sets and one event tree with quantified branches
Hazard Identification, Analysis, and Tracking & System Safety Program Planning and Management
Draft a system safety program plan outline for a hypothetical acquisition program, covering organization, responsibilities, milestones, and review gates
Identify the hazard tracking workflow, including closure criteria and verification evidence required to close a hazard
Explain how system safety integrates with the broader systems engineering process and configuration management
Describe the role of safety review boards, safety working groups, and independent assessment in program governance
Practice writing hazard closure justifications for three sample hazards
Your checkpoint
A 5-8 page draft system safety program plan outline with an annotated hazard tracking workflow and three sample closure justifications
Risk Assessment and Risk Acceptance
Distinguish risk acceptance criteria types (qualitative, semi-quantitative, quantitative) and explain the ALARP principle and its practical application
Evaluate risk reduction options using the hierarchy of controls and document residual risk for three scenarios
Explain how risk acceptance decisions are documented, who owns them, and how they are revisited as design matures
Analyze the tension between cost, schedule, and risk acceptance, and articulate the safety engineer's role in escalation
Complete a set of practice risk-acceptance scenarios and defend each recommendation in writing
Your checkpoint
A risk acceptance decision memo covering three scenarios, each with hierarchy-of-controls analysis, residual risk statement, and sign-off rationale
Human Factors and Human Error Analysis
Classify human error types (slips, lapses, mistakes, violations) and map each to appropriate analysis techniques
Apply a human error analysis technique (such as THERP-style task decomposition or a human HAZOP) to a maintenance task you can describe in detail
Explain human reliability concepts including performance shaping factors and their effect on error probability
Identify human factors design principles relevant to controls, displays, alarms, and procedures, and critique a real interface against them
Describe how to incorporate human error into fault trees and event trees
Your checkpoint
A human error analysis of one maintenance or operational task, with task steps, error modes, performance shaping factors, and at least two design or procedural recommendations
Software and Complex Electronic Systems Safety
Explain why software and complex electronic systems break traditional hazard analysis assumptions and describe the leading approaches
Describe system-theoretic hazard analysis (STPA) at a conceptual level: control structure, unsafe control actions, loss scenarios
Explain software safety requirements derivation, traceability, and verification evidence expectations
Discuss commercial-off-the-shelf, reused, and configurable software concerns and how they are addressed in a safety case
Describe the role of independence, diverse redundancy, and assurance levels in complex electronic systems
Your checkpoint
A written analysis of a hypothetical software-controlled function, including control structure sketch, unsafe control actions, derived safety requirements, and verification approach
Safety in Design, Operations, and Maintenance & Safety Standards, Regulations, and Compliance
Explain how safety requirements flow into design reviews, test, and acceptance, and identify the safety engineer's role at each gate
Describe operational safety concerns including procedures, training, configuration control, and change management
Describe maintenance-induced hazard mechanisms and controls, including lockout/tagout and return-to-service verification
Map the major standards and regulatory frameworks relevant to your sector and note what each governs without over-claiming specifics
Explain how compliance evidence is assembled and audited, and how to handle a noncompliance finding
Your checkpoint
A standards and compliance map for your sector, plus a design-review safety checklist and a maintenance safety control list
Incident Investigation, Lessons Learned, and Continuous Improvement & System Safety Program Planning and Management & Hazard Identification, Analysis, and Tracking
Describe the phases of incident investigation and the distinction between proximate and root causes
Apply a causal analysis method (such as 5-why, fault tree, or barrier analysis) to a published or hypothetical incident
Explain how lessons learned feed back into hazard analysis, requirements, and training, and how to close the loop
Synthesize the full course into a consolidated one-page summary of concepts, techniques, and cross-domain links
Complete a timed practice assessment across all domains and review every missed item
Your checkpoint
An incident investigation write-up with causal analysis and corrective actions, plus a consolidated one-page course summary and a scored practice assessment with error review
Milestones
Week 2: Can explain the purpose, inputs, and outputs of six hazard analysis techniques without notes, and can build a fault tree and event tree from scratch
Week 4: Can articulate risk acceptance criteria, apply the hierarchy of controls, and write a defensible residual risk statement for a scenario
Week 6: Can explain why software breaks traditional hazard analysis and describe the STPA approach and software safety requirement derivation
Week 8: Scores at or above your target on a timed full-domain practice assessment and has a written review of every missed item