1 / 12

Hazard Identification

Hazard Identification. SOFTWARE PROJECT MANAGEMENT. Systematic Processes. What Constitutes a Hazard?. A real or potential condition that, when activated, can transform into a series of interrelated events that result in damage to equipment or property and or injury to people.

kyran
Télécharger la présentation

Hazard Identification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hazard Identification SOFTWARE PROJECT MANAGEMENT

  2. Systematic Processes

  3. What Constitutes a Hazard? A real or potential condition that, when activated, can transform into a series of interrelated events that result in damage to equipment or property and or injury to people.

  4. Safety Managers View • Hazard • An implied threat or danger, a potential condition waiting to become a loss • Stimulus • Required to initiate action from potential to kinetic • May be a: • Component out of tolerance • Maintenance failure • Operator failure • Any combination of other events and conditions

  5. When Do We Look for Hazards? • The 5 Common Phases of a Systems Life Cycle • Conceptual - Research • Design (Validation & Verification) • Development (Full-scale engineering & production) • Operational Deployment • Termination & Disposal

  6. Primary Objective • The first major undertakings of a systematic safety effort must be to identify, analyze and control hazards • Review operational goals, objectives & constraints – “Before the fact” process • Resources (people, time & money) must be considered • Preliminary Hazard List (PHL) developed by experts from multiple areas of expertise

  7. Hazard Severity • A key factor in establishing a common understanding of a safety programs goal • MIL-STD 882 suggests four categories • Cat 1: Catastrophic • Cat 2: Critical • Cat 3: Marginal • Cat 4: Negligible

  8. Category Definitions • Catastrophic • Death or total system loss • Critical • Severe injury, illness or major system damage • Marginal • Minor Injury or system damage • Negligible • Less than minor injury or system damage

  9. Hazard Analysis Methods • Failure Modes & Effects Analysis (FMEA) • Systematic look at hardware piece by piece • Review of how each component could fail • Considers how a failure effects other components, sub-systems and systems as a whole • Risk assessment accomplished (severity & probability) • Risk Assessment Code (RAC) assigned

  10. Hazard Analysis Methods • Fault Tree Analysis (FTA) • Detailed review of a specific undesirable event • Deductive in nature • Top-down effort • Normally reserved for critical failures or mishaps • May be qualitative or quantitative

  11. Hazard Analysis Methods • Operating Hazard Analysis (OHA) • Also known as Operating & Support Hazard Analysis (O&SHA) • “What if” tool brings user into the loop • Integrates people and procedures into the system • Diagrams the flow or sequence of events • Project Evaluation Tree (PET) may be used for OHA accomplishment • Systematic evaluation of man, machine, & procedures

  12. 1. Hazard Identification 6. Follow Through & Review 2. Risk Assessment 5. Implement Risk Controls 3. Analyze Risk Control Measures 4. Risk Controls Hazard ID -- First, Last and Always! (Because what you don’t know can hurt you)

More Related