Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

North Forge:Hazard: Difference between revisions

From North Forge
No edit summary
No edit summary
 
(14 intermediate revisions by 2 users not shown)
Line 3: Line 3:
Hazards might be identified during [[North Forge:Job Hazard Analysis]], [[Safety Inspection]]s, [[Safety Incident Review]]s or ad-hoc.  
Hazards might be identified during [[North Forge:Job Hazard Analysis]], [[Safety Inspection]]s, [[Safety Incident Review]]s or ad-hoc.  


Hazards feed into the [[Forge:Risk Assessment Matrix]]/[[Risk Assessment Matrix]].  
Hazards feed into the [[North Forge:Risk Assessment Matrix]]/[[Risk Assessment Matrix]].  


{{Discuss |
{{Discuss |
Line 12: Line 12:
* One instance per hazard, so a tool could have zero, 1 or many
* One instance per hazard, so a tool could have zero, 1 or many
* Each includes  
* Each includes  
** type (physical, chemical, etc)
** source (JHA, WHMIS)
** acute vs chronic
** for [[JHA]], type: physical, chemical, biological, muscoloskeletal injury, psychosocial
 
** for [[WHMIS]], 
*** [https://www.ccohs.ca/oshanswers/chemicals/whmis_ghs/hazard_classes.html group, class, category]
** always vs maintenance only
** description, one sentence for things like signs
** description, one sentence for things like signs
***Standardized hazard descriptor
{{Discuss |
* see [[Safety Terminology#General Hazards]]? Alternate standard systems/terms we can use? Should this be encoded? (John)
** Sounds like something we should encode; it's actually what I was aiming for under JHA type above. Your list is different, though. I'd like to settle on a standard. Is there one that applies to JHA and to signage? I only want to include it if it would be useful for something specific, such as [[Safety Signage]], 
}}
** mitigation (separate for PPE?), one sentence, details would be SWP I think
** mitigation (separate for PPE?), one sentence, details would be SWP I think
** PPE
** [[North Forge:Pictograms]] (may be more than one per hazard)
** (or other mitigation pictogram causing data)
** whether it affects at room level
** whether it affects at room level
** whether it affects only at the maintenance level
** [[North Forge:Risk Assessment Matrix]] fields
** [[North Forge:Risk Assessment Matrix]] fields
*** probability
*** probability ("rare", "unlikely", "possible", "likely", "certain")
*** severity
*** severity ("first aid", "medical aid", "lost time", "life altering", "death")
*** frequency
*** frequency
*** # members affected
*** # members affected
** ANSI Z535 signal word: (Danger, Warning, Caution, Notice)
{{Discuss |
{{Discuss |
* Additional fields? [[User:Ttenbergen|Ttenbergen]] ([[User talk:Ttenbergen|talk]]) 22:42, 2024 October 13 (CDT)
* Additional fields? [[User:Ttenbergen|Ttenbergen]] ([[User talk:Ttenbergen|talk]]) 22:42, 2024 October 13 (CDT)
Line 27: Line 41:


* the encoded data will then show as appropriate on all the relevant pages. For example, if an SDS for 3dp resin is a hazard to eyes, then a printer that connects to the SDS will list this hazard, and if it was tagged as room level, then the room will list it as well.  
* the encoded data will then show as appropriate on all the relevant pages. For example, if an SDS for 3dp resin is a hazard to eyes, then a printer that connects to the SDS will list this hazard, and if it was tagged as room level, then the room will list it as well.  
== signage ==
* [https://en.wikipedia.org/wiki/ANSI_Z535 ANSI Z535] sets standards for signage such as colors and other things, but not actually the pictograms
** [https://www.ishn.com/ext/resources/Resources/white-papers/Clarion_ISHN_Whitepaper.pdf ISHN]
** [https://www.vulcaninc.com/files/A%20Handbook%20for%20Effective%20Safety%20Signage%20according%20to%20the%20ANSI%20Standard%20Z535.2-2011.pdf vulcan inc signage]
* [https://en.wikipedia.org/wiki/ISO_7010 ISO 7010] specifies graphical hazard symbols, see [https://commons.wikimedia.org/w/index.php?search=ISO+7010&title=Special:MediaSearch&go=Go&type=image commons]


== follow-ups ==
== follow-ups ==
Line 33: Line 53:
* add to [[North Forge:Job Hazard Analysis]] a query here to show the tools and sdss that have hazards, how many, and when last edited.
* add to [[North Forge:Job Hazard Analysis]] a query here to show the tools and sdss that have hazards, how many, and when last edited.
}}
}}
=== Sign formatting ===
* https://www.ishn.com/ext/resources/Resources/white-papers/Clarion_ISHN_Whitepaper.pdf
* https://www.vulcaninc.com/files/A%20Handbook%20for%20Effective%20Safety%20Signage%20according%20to%20the%20ANSI%20Standard%20Z535.2-2011.pdf


=== Default values ===
=== Default values ===
Line 49: Line 65:
[[Category:Safety]]
[[Category:Safety]]
[[Category:Possible future functionality]]
[[Category:Possible future functionality]]
[[Category:WHMIS]]

Latest revision as of 07:14, 2024 October 29

We are required to document hazards. This documents how the information is stored on the wiki. I am not planning on a "Hazard" page in the actual documentation namespace, the hazards will be displayed on the tool/room/SDS pages where they are relevant.

Hazards might be identified during North Forge:Job Hazard Analysis, Safety Inspections, Safety Incident Reviews or ad-hoc.

Hazards feed into the North Forge:Risk Assessment Matrix/Risk Assessment Matrix.

for all

  • The stuff on this page is not built yet, but I plan to put it together this week, so talk to me ASAP if you don't want it this way. Ttenbergen (talk) 22:42, 2024 October 13 (CDT)
  • Cargo


  • Categories
  • template:Hazard for this that can be included on North Forge:Tool pages, room or North Forge:SDS pages
  • One instance per hazard, so a tool could have zero, 1 or many
  • Each includes
    • source (JHA, WHMIS)
    • for JHA, type: physical, chemical, biological, muscoloskeletal injury, psychosocial
    • for WHMIS,
    • always vs maintenance only
    • description, one sentence for things like signs
      • Standardized hazard descriptor

for all

  • see Safety Terminology#General Hazards? Alternate standard systems/terms we can use? Should this be encoded? (John)
    • Sounds like something we should encode; it's actually what I was aiming for under JHA type above. Your list is different, though. I'd like to settle on a standard. Is there one that applies to JHA and to signage? I only want to include it if it would be useful for something specific, such as Safety Signage,
  • Cargo


  • Categories
    • mitigation (separate for PPE?), one sentence, details would be SWP I think
    • PPE
    • North Forge:Pictograms (may be more than one per hazard)
    • (or other mitigation pictogram causing data)
    • whether it affects at room level
    • whether it affects only at the maintenance level
    • North Forge:Risk Assessment Matrix fields
      • probability ("rare", "unlikely", "possible", "likely", "certain")
      • severity ("first aid", "medical aid", "lost time", "life altering", "death")
      • frequency
      • # members affected
    • ANSI Z535 signal word: (Danger, Warning, Caution, Notice)

for all

  • Cargo


  • Categories
  • the encoded data will then show as appropriate on all the relevant pages. For example, if an SDS for 3dp resin is a hazard to eyes, then a printer that connects to the SDS will list this hazard, and if it was tagged as room level, then the room will list it as well.

signage

follow-ups

for all

Tina
  • Cargo


  • Categories

Default values

for all

  • we could set each tool to list the "Unknown Hazard" hazard that escalates ranking in North Forge:Risk Assessment Matrix. Edit the tool and instead apply the "No associated Hazard" or specific hazard and that gets hidden and de-escalate the RAM placement. Could help motivate updates. Or could disengage. open to thoughts. Ttenbergen (talk) 22:58, 2024 October 13 (CDT)
  • Cargo


  • Categories

Form