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
Line 37: Line 37:
== signage ==
== 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://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
** [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
** [https://www.vulcaninc.com/files/A%20Handbook%20for%20Effective%20Safety%20Signage%20according%20to%20the%20ANSI%20Standard%20Z535.2-2011.pdf vulcanic]
* [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]
* [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]



Revision as of 13:53, 2024 October 15

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
    • mitigation (separate for PPE?), one sentence, details would be SWP I think
    • PPE (or other mitigation pictogram causing data)
    • whether it affects at room level
    • North Forge:Risk Assessment Matrix fields
      • probability
      • severity
        • This is similar to the signal word concept for ANSI Z535 signage, should we use the same? (Danger, warning, caution, notice)
      • frequency
      • # members affected

for all

  • Additional fields? Ttenbergen (talk) 22:42, 2024 October 13 (CDT)
  • WHMIS details such as class would be stored on the SDS, but the hazard should be stored via template:hazard
  • 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