kopik
Créer
Industrie & mécaniqueVérifiée par Kopik: Sources officielles relues et réponses testées par Kopik

Awareness barriers and chains: when OSHA accepts them as machine guarding

Many shops wonder whether a chain, a railing or a warning sign can stand in for a physical guard. OSHA has answered this in an interpretation letter and in a directive specific to metal-cutting shears.

Posez votre question

Compte gratuit requis

Chaque question est indépendante · 1 offertes par mois, puis avec l'abonnement.

Les réponses sont rédigées par un modèle de langage à partir des seuls documents de cette base, avec leurs sources numérotées. Elles peuvent être inexactes et ne constituent pas un conseil juridique, médical ou financier : vérifiez les sources avant toute décision importante.

Why a chain is generally not a guard

In a May 28, 1996 letter, OSHA explained that machine guarding standards contemplate a physical means of preventing contact with moving parts. An awareness barrier such as a chain depends largely on human behavior, so it would not provide the necessary protection.

The letter notes one exception: where there is no reasonably foreseeable reason for an employee to enter the area. The employer must consider every possible reason for entry, including oiling and cleaning, and foreseeable misconduct such as "sneaking a smoke". The page notes this letter is an archive document that may no longer represent OSHA policy.

The specific case of metal-cutting shears

OSHA Instruction STD 01-12-025 (July 12, 1994) tells compliance officers to accept properly applied awareness barrier safeguarding, as specified by ANSI B11.4-1993, as point-of-operation safeguarding on metal-cutting shears.

This applies only where it is impossible to use a fixed guard or a point-of-operation device because of the diversity of operations on the shear. It is a narrow exception, not a general alternative to guarding.

Questions fréquentes

Does a locked gate remove the need for other guarding?

OSHA said a locked gate that prevents entry into the danger zone would negate the need for additional guarding. It only works if employees can get the key and enter when the moving-part hazards are not present, because the standards do not create a class of "authorized" employees who may be exposed.

What about an interlocked gate on a machine that coasts to a stop?

An interlocked gate is not acceptable if an employee can reach the danger zone before the machine stops. OSHA recommends a time delay so the gate cannot open until moving parts have fully stopped.

Does lockout/tagout also apply when entering a guarded area?

If the purpose of entering is servicing or maintenance, OSHA notes that 1910.147, the control of hazardous energy (lockout/tagout) standard, may apply.

Pour les développeurs et les agents

Intégrer / API / MCP

Branchez cette base à Claude, Cursor, ChatGPT ou votre propre application. Chaque requête API ou MCP coûte 0,10 €, débitée de votre crédit Kopik (non facturée si rien n'est trouvé). Il vous faut une clé API : créez-la depuis votre tableau de bord.

MCP pour vos agents

Adresse du serveur MCP de cette base (outils ask_base et search_base) :

URL MCP
https://kopik.io/api/mcp?base=us-osha-machine-guarding-amputation
Claude Code, Cursor et autres clients
Claude Code
claude mcp add --transport http kopik-us-osha-machine-guarding-amputation "https://kopik.io/api/mcp?base=us-osha-machine-guarding-amputation" --header "Authorization: Bearer kpk_…"
Configuration JSON (mcpServers)
{
  "mcpServers": {
    "kopik-us-osha-machine-guarding-amputation": {
      "url": "https://kopik.io/api/mcp?base=us-osha-machine-guarding-amputation",
      "headers": {
        "Authorization": "Bearer kpk_…"
      }
    }
  }
}

API REST pour vos applications

mode vaut "answer" (réponse rédigée + sources) ou "passages" (passages bruts seulement). Ajoutez un maxPriceCents facultatif pour plafonner le prix : si la base coûte plus cher, l'appel est refusé sans rien débiter.

curl
curl -X POST https://kopik.io/api/v1/bases/us-osha-machine-guarding-amputation/query \
  -H "Authorization: Bearer kpk_…" \
  -H "Content-Type: application/json" \
  -d '{"question": "Votre question ici", "mode": "answer"}'

Pour commencer

  1. Créez une clé dans votre tableau de bord et rechargez votre crédit.
  2. Remplacez kpk_… par votre clé.
  3. Tout le détail (réponses, erreurs, exemples JS et Python) : documentation développeurs.