Upload
others
View
29
Download
1
Embed Size (px)
Citation preview
Control Room ManagementRegulations Implementation
AGA Operations ConferenceMay – 2010
Byron Coy, PEDirector Eastern RegionDirector, Eastern RegionUSDOT/PHMSA/OPS
05‐10‐2010
Project Drivers• PHMSA has been examining Control Room operations for 10 years
– Three Advisory Notices on SCADA & Fatigue (1999, 2003, 2005)– SCADA System Check List Initiated (1998)– T&Q SCADA Training Class Developed (2001)
• Pipeline Safety Improvement Act of 2002 (Section 13b)– CCERT Study of control room operations to enhance pipeline safety (2003‐2006)– Operator Qualification Requirements (2006‐2007)p q ( )– Two CRM Workshops (2006, 2007)– OQ Report to Congress, Section 6 (Dec‐2006)
• National Transportation Safety Board– 10 of 18 Hazardous Liquid accidents have potential CRM involvement (1998‐2005)10 of 18 Hazardous Liquid accidents have potential CRM involvement (1998 2005)– SCADA Safety Study (2005)
• PIPES Act of 2006 (Sections 12, 19, 20) – Establish human factors management plan – Program to assure safe operation of pipelinesProgram to assure safe operation of pipelines– NTSB Recommendations on Displays, Alarms and Training– Accident/incident form changes on Fatigue– Issue Regulations
05‐10‐2010
Control Room Management: Cross References
Enhancement Areas Basis Affiliations and Regulations
PSIA‐2002CCERT Study
Pipes Act2006
NTSBRecommendations
PHMSAAdvisory Bulletins
IndustryRP’s andCCERT Study
Outcomes2006 Recommendations Advisory Bulletins
& Reg.CodesRP s and
Standards ^
Roles & Responsibilities X API RP‐1168**API RP‐1162
Shift Change X API RP‐1168**
Fatigue Awareness & Mitigation
X Section 12 P‐05‐04@, P‐99‐12@
P‐98‐30@ADB‐05‐06 API RP‐1168**
SCADA Displays X Section 19 P‐05‐01@, P‐98‐22@
P‐93‐22@ADB‐99‐03 API RP‐1165
Point Data X
Alarm Management X Section 19 P‐05‐02@
P‐98‐22@API RP‐1167*
AGA White Paper*
Change Management X ADB‐99‐03ADB‐03‐09
API RP‐1168**
Operating Experience& Training
X Section 19 P‐05‐03@
P‐98‐[email protected]
(^) A consortium of Gas Operators are developing a Common Gas Control Manual(*)Under Development (**)New since NPRM (@)Closed Recommendation
05‐10‐2010
Safety Pyramidy ySerious Failure
Significant andMinor Events
Intervention by Controllers
Reportable
Un‐reportableIntervention by Controllers,
other Personnel orSafety Systems
Near Miss, IdentifiedRecorded
Un‐recorded
Near Miss, Undetected
Control Room Management Processes can help assure that developing situations don’tControl Room Management Processes can help assure that developing situations don t climb the pyramid to become Significant Events or Serious Failures
05‐10‐2010
Pipeline CRM Risk Matrix‐‐‐ Risk derived from monitor and control ‐‐‐
Red indicates highest risk, Yellow indicates lower risk
Pipeline ControlRisk Matrix
Hazardous Liquids
Gas Transmission
Gas Distribution
Remote monitor &
RemoteOperation
Remote monitor & remote control
Remote monitor; action by others
‐‐‐ Full Inclusion ‐‐‐y
Individual Field
Station
Local facility with centralized control
panel LimitedStation Operation Individual equip.
with status control and indicators
Inclusion
Matrix coding principally represents the combination of frequency and consequence of pipeline upset conditions and failures, where CRM may be a contributing factor
05‐10‐2010
Operators and ControllersOperator Types Final Rule
Limited* Inclusion,Controllers &
Qualified Supervisors
Full Inclusion,Controllers &
Qualified Supervisors
Master Meters & LPG Excluded
Gas Distribution < 100k services Limited* 1308
Gas Distribution 100k to 250k services Limited* 488
Gas Distribution > 250k services Included 1068
Gas-Trans without compressor station/s Limited* 1307
Gas-Trans with compressor station/s Included 2354
LNG Plants (est. 436 controllers) Excluded
Haz-Liq < 50 pipeline miles Included 308
Haz-Liq 50 to 250 pipeline miles Included 551
Haz-Liq > 250 pipeline miles Included 1108
Estimated Totals 3103 5389
*‐ Limited Inclusion refers to Fatigue Management and Compliance Deviation
05‐10‐2010
Pipeline RegulationsPipeline Regulations
• http://www.phmsa.dot.gov/pipeline/regsp // p g /p p / g• Pipeline Regulations & Applicable Laws• Federal Register
– Vol. 74, No. 231, December 3, 2009– Starting on Page 63310Docket ID PHMSA : 2007 27954– Docket ID PHMSA : 2007–27954
– Amendment Numbers: 192–112 and 195–93– Regulation Identifier Number: 2137–AE28– AGENCY: PHMSA / DOT– ACTION: Final rule
05‐10‐2010
49CFR : 192.631 & 195.44649CFR : 192.631 & 195.446• a) General• b) Roles and Responsibilities• c) Provide Adequate Information• d) Fatigue Mitigation• d) Fatigue Mitigation• e) Alarm Management• f) Change Management) g g• g) Operating Experience• h) Trainingi) C li V lid i• i) Compliance Validation
• j) Compliance and Deviation
05‐10‐2010
Code FootnotesCode Footnotes• Roles, (Authority) & Responsibilities• API ‐ RP1165 (192 ‐ 1, 4, 8, 9, 11.1, 11.3)• API ‐ RP1165, demonstrate not practical• API ‐ RP1168, not referenced in 192• API ‐ RP1167, not published, not referencedT t (A ) B k SCADA S t• Test (Any) Backup SCADA Systems
• Maximum HOS, emergency deviations• Chg Mgt: Control Room Representative• Chg‐Mgt: Control Room Representative• Compliance Deviations
05‐10‐2010
Key Milestones for CRM Regulationsey esto es o C egu at o sImplementation Timetable
• Final Rule Published : Dec‐2009Final Rule Published : Dec 2009• NTSB Recommendation Closures : Feb/Apr‐2010• → Public Workshop : Nov‐2010• Hours of Service Criteria Finalized : 1Q11• Hours of Service Criteria Finalized : 1Q11• Shift Schedules Criteria Finalized: 1Q11 • FAQ’s Finalized : 1Q11• Inspection Enforcement Guidance : 2Q11• Inspection Enforcement Guidance : 2Q11 • Inspector Training Material : 2Q11• Operator Procedures/Programs Established : Aug‐2011• → Program Inspec ons : Sep 2011 to Feb 2013• → Program Inspec ons : Sep‐2011 to Feb‐2013• Operator Procedures/Programs in Service : Feb‐2013• → Implementa on Inspec ons Begin : Mar‐2013
05‐10‐2010
CRM Implementation TeamCRM Implementation Team
• Tewabe Asebe, Regulations, g• Karen Butler, SME• Byron Coy SME (Lead)• Byron Coy, SME (Lead)• Ben Fred, Legal• Max Kieba, Engineering• Wally McGaughey, Trainingy g y, g• NAPSR – State Partners
05‐10‐2010
CRM Public WorkshopCRM Public Workshop
• 1 Full Dayy• November, 2010 … 17th ?• Houston• Houston• Preliminary Inspection Material• FAQ’s, Discussed and Solicited• Stakeholder Participationp
05‐10‐2010
Inspections • PHMSA will be making provisions to inspect and approve
all plans on an orchestrated basisall plans on an orchestrated basis.• We anticipate dedicated initial CRM inspections of every
operator. • The legislation calls for PHMSA (or State partners) to
review and approve operators' plans. • If during an inspection we find an operator’s plan• If during an inspection, we find an operator s plan,
implementation and eventual documentation do not comply with the regulation, or is inadequate, we will certainly take appropriate enforcement action.
05‐10‐2010
Fatigue Management • NTSB has recently accepted our Hours of Service
requirements by closing P 99 12 as acceptable alternativerequirements by closing P‐99‐12 as acceptable ‐ alternative action.
• The NTSB has removed fatigue in the pipeline industry from the Most Wanted list.
• A Gas industry consortium is already drafting guidance material for their operators including scientific analysis formaterial for their operators, including scientific analysis for fatigue management.
• Operators will need to have a technical basis for their shift pschedules and hours of service. This point will be further discussed at the upcoming workshop.
05‐10‐2010
Fatigue Managementg gTechnical Basis
Track history will not be sufficient as a technical basis for shift schedules and hours of service.
• Integrity Management: Pre‐70 ERW Long Seamsg y g g• Operator Qualifications: Work Experience
05‐10‐2010
Compliance Deviations • Deviations could occur for any section of the CRM regulationsregulations.
• There may be infrequent emergencies during which an operator needs to deviate from thewhich an operator needs to deviate from the maximum hour limits it has established.
• Operators will need to document the reasons for pany deviation, and maintain for review during inspections.
• PHMSA shall review the reasonableness of any such deviations.
05‐10‐2010
FrequentlyFrequentlyA k dAsked
QuestionsQ
05‐10‐2010
Control Room ManagementRegulations Implementation
AGA Operations ConferenceMay – 2010
Byron Coy, PEDirector Eastern RegionDirector, Eastern RegionUSDOT/PHMSA/OPS
05‐10‐2010