ANSI Z359 package logic
Why harness, connector, anchorage, and rescue planning must be documented as a system.
Request PDF
OSHA 1910 / 1926ANSI Z89.1 · Z359EN 397 · EN 12492 · EN 361NFPA 1983 references
Standards index
Filter by PPE type, task, and jurisdiction before writing the specification
The table below is not a substitute for legal or competent-person review. It is a working index for technical buyers who need to understand which standard family is relevant to each product decision.
| Standard | Scope | Where it appears in Petzl reviews | Notes |
|---|---|---|---|
| ANSI Z89.1-2014 | Industrial head protection | Safety helmet class, impact, and electrical references | Use with accessory and chin-strap compatibility review. |
| EN 397 / EN 12492 | Industrial and mountaineering-style helmets | Helmet selection for vertical work and rescue teams | Check product marking and intended-use instructions. |
| ANSI Z359 family | Fall protection and fall arrest systems | Harness, lanyard, connector, and rescue planning | Do not evaluate a single item outside the full system. |
| OSHA 1926.502 | Construction fall protection workplace rule | Program and jobsite compliance review | OSHA compliance is a workplace responsibility, not a product approval. |
| EN 361 / EN 358 / EN 813 | Harness and positioning references | Work positioning and rope access package review | Match task and regional requirement before substitution. |
Whitepapers
Technical topics safety teams ask about before rollout
Helmet accessory compatibility
How chin straps, face protection, headlamps, and hearing protection affect helmet selection.
Request PDFSuspension trauma planning
Program notes for rescue timing, equipment staging, and supervisor responsibilities.
Request PDFInspection record structure
Fields that help competent persons track condition, incidents, and retirement triggers.
Request PDFEN and ANSI language comparison
A practical guide to avoiding one-to-one standard assumptions across regions.
Request PDFProcurement substitution control
How to define approved alternatives without eroding the safety basis of the original package.
Request PDF
Datasheets
Datasheet requests should include the task, standard, and accessory stack.
For head protection, tell us whether the crew needs chin strap retention, face protection, hearing protection, headlamp mounting, dielectric considerations, or cold-weather liners. For fall protection, include anchorage assumptions, free-fall distance, rescue plan, lanyard or SRL preference, user size range, and the work positioning method. Those details make the datasheet package more useful than a generic file bundle.
Typical TDS package
- Product specification sheet
- Applicable standards and scope notes
- Inspection checklist template
- Compatibility considerations
- Retirement and storage guidance
Evidence index
Keep approval, conformity, and workplace compliance language separate
Petzl documentation distinguishes product evidence from employer obligations. Product conformity files can support a purchasing decision, but they do not replace hazard assessment, training, rescue planning, inspection, or local workplace compliance review. This separation prevents wording that wrongly implies OSHA grants product-level approval for PPE.
Spec help
Questions that usually change the recommendation
Is the worker climbing, positioning, or only exposed near an edge?
The access method affects harness attachment points, lanyard style, and rescue assumptions.
Does the helmet need accessories?
Face shields, hearing protection, lights, and communication devices can change compatibility and comfort.
Who owns inspection records?
A program fails when inspection responsibility is split informally between the user, supervisor, and warehouse.
What happens after a fall event?
Rescue planning, equipment quarantine, incident review, and replacement decisions must be written before deployment.
Engineering review
Send a standards question with the product family and task context.
We will route the request toward the right technical documentation and identify the assumptions that need field validation.