North Forge:Hazard

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.

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 tool, room or North Forge:SDS pages
• One instance per hazard, so a tool could have zero, 1 or many
• Each includes
  • type (physical, chemical, etc)
  • description, one sentence for things like signs
  • mitigation (separate for PPE?), one sentence, details would be SWP I think
  • whether it affects at room level
  • North Forge:Risk Assessment Matrix fields
    • probability
    • severity
    • frequency
    • # members affected

for all

Additional fields? Ttenbergen (talk) 22:42, 2024 October 13 (CDT)

• 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.

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

• suggest to use Hierarchy of Controls for mitigation portion