13.07.2015 Views

Minutes October 2013 - BC Safety Authority

Minutes October 2013 - BC Safety Authority

Minutes October 2013 - BC Safety Authority

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Doppelmayr DSSeries Grip Jawsongoing /completeSome ski areas are not doing 100% immediate replacement of grip jaws; areminder will be sent to these ski areas to submit information to <strong>BC</strong>SA.2.1.4PassengerRopeway andConveyorGuarding updateJason Gill updated the committee on the status of the passenger ropeway andconveyor guarding issue, with the following key points: WorkSafe<strong>BC</strong> called <strong>BC</strong>SA after Mt Washington had sent in variance requestfrom the requirements for machine guarding. WorkSafe<strong>BC</strong> is aware that Z98code vs WorkSafe<strong>BC</strong> regulations may conflict in terms of lockout procedures.WorkSafe<strong>BC</strong>’s plan was to review Z98 requirements and create guidelines,and avoid having all ski areas apply for a variance. Best practices manual issued by CWSAA in 2007 had some incorrectprocedures.George Trousdell added the following points: Mt Washington is installing polycarbonate guarding in terminal.DiscussionhighlightsMembers discussed the following: According to CSA Z432 lockout procedures standards: Cannot haveinadvertent contact with machinery. Lift must be completely de-energized.OHS and WorkSafe<strong>BC</strong> use this standard. CWSAA developed a best practices / safe work procedures manual,including how to operate work basket and references Z432. The proceduresneed revising; WorkSafe<strong>BC</strong> had been involved in making this document andis aware that some procedures are not correct.Outcome Jason Gill will put forward the issue of the incorrect best practices manual atthe CWSAA meeting.2.1.5PassengerRopeways RiskAssessmentProgram toolupdateJason Gill updated the committee on the passenger ropeways risk assessmentprogram tool, with the following key points: Last meeting, discussed preliminary RAP tool. <strong>Safety</strong> Officers have recentlycompleted scoring risk evaluation on each ropeway, considering variousfactors, such as type of installation (operational incidents for that type ofinstallation); modifications; safety culture; training and competency. Added new factor: Hours. May also ask areas to give information onmodifications that were not originally in file. Will also add: As-foundconditions; last inspection date. As-found conditions look at worst possible non-compliance as per past COIs,not just comparison to code as, sometimes codes do not address particularhazards. EL and GA use this to allocate SO resources. Will eventually try to implementthis in PR, maybe apply to contractor later.In response to questions, Jason Gill provided the following clarifications: Whether the original manufacturer still exists is not yet a factor in calculatingthe RAP score.Outcome Update at next meetingPassenger Ropeways Technology Advisory Committee <strong>Minutes</strong> – FINAL VERSION p. 4 of 10<strong>October</strong> 7, <strong>2013</strong>


2.2 SAFETY RISK ISSUES2.2.1Incidentsummary reportJason Gill provided an overview of the incident summary report, with the followingkey points: Data has not changed much since last meeting. Some incidents were related to competency of ski area operations andmaintenance workers: One area allowed a carrier to run with gripcompromised while passengers were riding the lift, and the carrier continuedto slide backwards on the rope. Monetary penalty issued; restrictions wereput on the contractor licence; they have since hired additional staff andrestrictions have been relaxed. May point to the importance of mechaniccertification. They had not followed the <strong>Safety</strong> Order regarding gripinstallation checking procedures, although had signed that they hadcompleted it.In response to questions, Jason Gill provided the following clarifications: Power outages should no longer be included in incidents report as there islittle data to be learned from these reports; only if the evacuation drive failswhen engaged during a power outage. If industry has a compelling reason toinclude power outages as incidents, it would be reconsidered.SupportingmaterialLink distributed via email in agenda: Incident Summary Report on <strong>BC</strong>SA website2.2.2Risk registrysummaryJason Gill provided an overview of the risk registry summary, with the following keypoints: Axle adjustment bolt failure: Put on “watch” status Mechanic certification: High riskSee Item 2.3.2SupportingmaterialDistributed via email: Risk registry (July 15, <strong>2013</strong>)2.3 WORKING GROUPS2.3.1Aging PassengerRopewaysWorking GroupWayne Wiltse updated the committee on the status of the Aging PassengerRopeways Working Group, with the following key points: Not much work has been done since last meeting. Bruno Mannsberger and Dave Looney discussed this issue briefly but moreneeds to be done before possible review in mid-November.Outcome Working Group meeting to be held in conjunction with Certification ofPassenger Ropeway Maintenance Personnel Working Group meeting inJanuary 2014.2.3.2Certification ofPassengerRopewayMaintenanceJason Gill updated the committee on the status of the Certification of PassengerRopeway Maintenance Personnel Working Group, with the following key points: Need to meet with Working Group in January 2014 to discuss possibleoptions. Issue to resolve: Small- to medium-sized ski areas are having trouble withPassenger Ropeways Technology Advisory Committee <strong>Minutes</strong> – FINAL VERSION p. 5 of 10<strong>October</strong> 7, <strong>2013</strong>


PersonnelWorking Groupsuccession planning; knowledgeable industry personnel are retiring ormoving to other areas, leaving <strong>BC</strong>SA <strong>Safety</strong> Officers to conduct qualitycontrol, load tests, etc.Certification of maintenance personnel would include having a set of criteriato determine an individual to be qualified / competent in certain areas ofwork, and have received training specific to industry/code.In response to questions, Jason Gill provided the following clarifications: No regulatory requirements for having a competent or qualified person toapply for a contractor licence. Passenger ropeway <strong>Safety</strong> Management Plans intended to address thesame issue. SMPs came from a recommendation from the PassengerRopeways, Amusement Rides and Recreational Rail Technology AdvisoryCommittee, but this proved not to be a viable option. Passenger Ropeways<strong>Safety</strong> Officers had been expected to conduct audits on all the ski areas withlittle training and no adjustment to existing work practice to create time foraudits. The Province of <strong>BC</strong> rejected the idea of certification of passenger ropewaysmaintenance personnel in the past because of Trade, Investment and LabourMobility Agreement issues – could do this through other means such aslicences. Possible to certify only one person at the area, or implement a Field <strong>Safety</strong>Representative approach in which one individual is responsible for signoff ofall work. Possible examples to follow/consider: <strong>BC</strong>SA’s elevating devices mechaniccertification, Europe’s passenger ropeways mechanic certification courses. Implementation will not go forward until thorough consultation is done. It is not likely that ITA would entertain the administration of the certificationbecause the number of certified individuals is very low. Mechanic certification aligns with 10-year strategy in making sure that peoplehave the skills and abilities to do the work, and is mentioned in <strong>BC</strong>SA’s 3-year business plan. The Working Group should include people from CWSAA and Selkirk College.DiscussionhighlightsMembers discussed the following: This seems to be an arduous endeavour with little rationale. Millwrights havethe training required to work in the passenger ropeways industry; however,not all areas are hiring millwrights. For smaller areas, <strong>BC</strong>SA could require particularcompetencies/training/experience on particular equipment or else need tocontract work. It was asked what the approximate percentage is of ski areas that do nothave well-trained personnel to operate and maintain the passengerropeways. Other jurisdictions: USA does not have certification for their passengerropeway maintenance personnel. TSSA’s program may not be achievingwhat was intended; signoffs on competencies and who can sign off is notclear. The idea was met with much resistance.Outcome Working Group meeting to be held January 22, 2014 (location TBD) Jason Gill may discuss the issue of mechanic certification at the CWSAAmeeting.Passenger Ropeways Technology Advisory Committee <strong>Minutes</strong> – FINAL VERSION p. 6 of 10<strong>October</strong> 7, <strong>2013</strong>


NEW BUSINESS3.1 ROUNDTABLEConsultants: Clauses in Z98 Code for contactor requirements are written very genericallyand it is not clear how to apply them. This will be brought up at Z98 Codemeetings.Contractors: Concerns expressed about resources for two <strong>BC</strong>SA <strong>Safety</strong> Officersconducting inspections on one site in the days leading up to the CWSAAmeetings.3.1.1ITTAB - updatefrom meeting ofropewaysauthoritiesJason Gill provided an overview of the annual ITTAB conference for ropewaysauthorities worldwide, with the following key points: At the annual ITTAB conference, all passenger ropeways authorities cometogether and review incidents and accidents over the past year. According to the summary conducted by Austria, 1 minor injury per 11 milliontransports; 1 severe injury for 42 million transports; 1 fatality per 1.7 billiontransports worldwide. France did presentation on a fatal incident: The welding was found to beinadequate on sheave assembly and caused a car to fall. Switzerland presented a summary of their 25-year operating permit review.The results can be discussed at the Aging Ropeways Working Groupmeeting.3.1.2Z98 Code –update on neweditionJason Gill provided an overview of the upcoming new edition of the CSA Z98 Code,with the following key points: Danny Cox, Warren Sparks and Jason Gill have been reviewing draft codethat had been put out for next edition, which will likely be Z98 2014. 82changes in total. CSA Z98 Code lost national standard status last edition; signage needs to bein English and French as per Canadian Standards Council (CSC). ASTM wasrecognized as a standards-making body in Canada; <strong>BC</strong>SA can adopt andrecognize multiple codes and standards that do not have national standardstatus from CSC. <strong>BC</strong> usually adopts the Z98 Code as-is with no deviations. <strong>BC</strong>SA will reviewthe edition and determine if any design requirements need to beimplemented retroactively but it is not anticipated that this will be required.Most of the changes in the new edition affect 3S and Reversible ropewaysystems that are not built very often in Canada.Passenger Ropeways Technology Advisory Committee <strong>Minutes</strong> – FINAL VERSION p. 7 of 10<strong>October</strong> 7, <strong>2013</strong>


EVALUATION & ADJOURNMENT4.1 MEETING EVALUATIONThe meeting evaluation was distributed and collected via email.4.2 NEXT MEETING DATESWednesday, February 26, 2014 or Wednesday, March 5, 2014<strong>BC</strong> <strong>Safety</strong> <strong>Authority</strong> New Westminster office4.3 MEETING ADJOURNMENTThe meeting was adjourned at approximately 4:15pm.Passenger Ropeways Technology Advisory Committee <strong>Minutes</strong> – FINAL VERSION p. 8 of 10<strong>October</strong> 7, <strong>2013</strong>


PASSENGER ROPEWAYS TECHNOLOGY ADVISORY COMMITTEE ACTION LOGFollowing <strong>October</strong> 7, <strong>2013</strong> meetingTECHNICAL SAFETY AND REGULATORY OPERATIONSHeight restrictions on chairlifts <strong>Minutes</strong> reference 2.1.1Action item (s) Responsible Target date Status UpdatePut forward height restriction issue at CWSAArisk management meetingJason Gill, SueDixon, et al09-Oct-13 Open As of <strong>October</strong> 7 PRTAC meeting,CWSAA risk management meetinghad not happened.Send any examples of best practices, heightrestriction signage, particularly if different forsummer and winter operations, to Jason GillDraft Information Bulletin on height restrictionsand send draft to all PRTAC members forcommentAll members 25-Oct-13 Open No examples have been received.Jason Gill 31-Oct-13 Pending Pending best practice informationsubmitted by members, anddiscussions at CWSAA.WORKING GROUP STATUS REPORTSAging Passenger Ropeways Working Group <strong>Minutes</strong> reference 2.3.1Action item (s) Responsible Target date Status UpdateDetermine scope of Working Group Wayne Wiltse 22-Jan-14 Open Meeting to be called January 22, 2014Review AEDARSA aging ropeways checklist inpreparation for PRTAC meeting and CWSAAmeeting in <strong>October</strong>BrunoMannsberger andDave Looney22-Jan-14 OpenCertification of Passenger Ropeway Maintenance Personnel Working Group <strong>Minutes</strong> reference 2.3.2Action item (s) Responsible Target date Status UpdateComplete a Request for Formation of a WorkingGroup form for the passenger ropewaycertification of maintenance personnelJason Gill 01-Oct-13 Complete First meeting to be called January 22,2014Passenger Ropeways Technology Advisory Committee minutes – FINAL VERSION p.9 of 10<strong>October</strong> 7, <strong>2013</strong> meeting


ADMINISTRATIVE ISSUESRecruitment / Membership / Alternates <strong>Minutes</strong> reference 1.2.2Action item (s) Responsible Target date Status UpdateDesignate alternates and submit membership All members N/A In progress This item was not discussedforms to MerylInvite Hildur Fossberg, Ken Derpak, Mike Barker(small ski areas), and David Lynn (CWSAA) tojoin the Passenger Ropeways TechnologyAdvisory CommitteeFrank Do, JasonGill01-Oct-13 In progress Invitations to join the PRTAC havebeen sent to industry; individuals canbe asked to join committee.Passenger Ropeways Technology Advisory Committee minutes – FINAL VERSION p.10 of 10<strong>October</strong> 7, <strong>2013</strong> meeting

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!