Technical Safety Engineering Grounding Session

Transcript:Technical Safety Engineering Grounding Session:
Technical Safety Engineering Grounding Session Michael Banner PEng MSc Disclaimer Background 22 Years as a Technical Safety Professional BSc. Chemical Engineering, MSc Safety, Risk & Reliability Engineering Consultancies (4y), EPC (7y), Operators (11y), Insurance Risk Engineering Lead Technical Safety Eng on Multi $Billion Projects both onshore & offshore Exxon, Chevon, BP, TOTAL, Oil and Gas, LNG, Petrochemical Projects Technical Authority for Mid-sized Operators Conducted dozens of internal/external audits 8 years international overseas Russia, Norway, France, UK, Middle East Half Career on Projects outside of Canada Technical Safety Engineering TEAM Process Safety Engineering P&IDs, Cause and Effect – HAZOPS, HAZIDS, LOPAs etc. Functional Safety Engineering Safety Instrumented Systems (SIL Verification), SRS Loss Prevention Engineers Design of the following systems: F&G, Firewater, Passive Fire, Layouts, LSA, SS, etc. Risk Engineering Specialists Projects VS Operations ▪High Level Greenfield PROJECTS Technical Safety requirements: Finish Line tasks Philosophies developed Layout and design the facility Show ALARP is met Define Safety Critical Elements Operations Technical Safety requirements: Continuously Managing Impairments to SCE KPIs on Health Status of Safety Barriers/SCEs Maintenance on SCE MOC mini projects (brownfield projects) Today’s Presentation talk will focus more on Projects type issues Code Compliance vs Risk Based Most Code Compliance is traditional discipline base Building Code – Civil/Structural Engineering Electrical Code – Electrical Engineering API / ABSA – Process Engineering ASME – Mechanical and/or Piping Engineering BMS codes – Instrumentation Engineering * If you’re spending time doing code compliance issues, you’re in trouble! The disciplines need to know these or you we can’t do your job effectively What Code Compliance is there specific to Technical Safety? NFPA (fire protection mainly) IEC/ISA (Safety Instrumented Systems) Likely there is already a STANDATA or deviation in place for your jurisdiction API 521, API 2218, API 753 – These are helpful CSA Z767 – Best one… However, it doesn’t specifically call out the types of studies that are typically used in Technical Safety Discipline Nor is any RISK criteria normally dictated Typical Studies/Tools used by Technical Safety Initially any Technical Safety teams needs a “GOOD” Risk Matrix What is a “GOOD” Risk Matrix Many Companies in Alberta STILL don’t have a “good” Risk Matrix Key Points Likelihood levels should be “Logarithmic” >1, >0.1, >0.01, >0.001, >1E-4 It facilitates a clear understanding of what safety credits are applied and their effect Segregate the difference between Single Fatality and Multiple Fatalities Ideally, we need to be able