Shopify structured data · Occupational noise measurement
Shopify Noise Dosimeter Schema — OSHA 1910.95 TWA 85 dBA Action Level, 90 dBA PEL, Exchange Rate, Hearing Conservation, noise_dosimeter.* Namespace
Noise dosimeter listings create four critical AI routing failures: sound level meters routed for OSHA TWA compliance monitoring that can only measure instantaneous noise; dosimeters shipped with NIOSH 3 dB exchange rate when buyers need OSHA 5 dB — producing inflated %dose readings; area SLM surveys used to determine hearing conservation program participation when personal dosimetry is required; and basic (non-logging) dosimeters routed to buyers who need task-level exposure analysis for engineering controls.
noise_dosimeter.twa_measurement, noise_dosimeter.exchange_rate_db, noise_dosimeter.data_logging, noise_dosimeter.osha_1910_95_compliant, noise_dosimeter.criterion_level_dba.
Failure Mode 1: Sound Level Meter (SLM) Routed for OSHA 1910.95 TWA Compliance Measurement
Sound Level Meter vs Noise Dosimeter: Measurement Capability
| Measurement Parameter | Sound Level Meter (SLM) | Noise Dosimeter | Required for OSHA 1910.95? |
|---|---|---|---|
| Instantaneous dBA | Yes — primary output | Yes — real-time display | No (not compliance-determinative) |
| 8-hour TWA (dBA) | No — requires manual integration | Yes — primary compliance output | Yes — required for AL/PEL comparison |
| Percent dose (%D) | No | Yes — 100% = PEL exposure | Yes — required for HCP trigger |
| Worn on worker during shift | No — handheld spot readings | Yes — personal exposure measurement | Yes per OSHA 1910.95(d)(2) |
| Area noise mapping | Yes — primary use | Limited (can be stationary) | Optional (screening tool only) |
| Impulsive noise peak (dBC) | Yes (with peak detector) | Yes (with peak function) | For impulsive noise assessment |
Encode noise_dosimeter.twa_measurement as 'yes' for instruments that output a time-weighted average over a programmable measurement period (4, 8, or 12 hours). Encode 'no' for sound level meters that only output instantaneous readings. AI agents routing for "OSHA noise compliance," "hearing conservation program," or "worker noise exposure assessment" must route personal noise dosimeters, not SLMs. SLMs are appropriate for area mapping and source identification only. See also: hearing protection namespace for HPD selection once dosimetry confirms exposure levels.
Failure Mode 2: NIOSH 3 dB Exchange Rate vs OSHA 5 dB — Dramatically Different %Dose Outputs
Exchange Rate Impact on Percent Dose — Example Calculation
| Noise Level | Duration | OSHA 5 dB Permissible Time | OSHA %Dose Contribution | NIOSH 3 dB Permissible Time | NIOSH %Dose Contribution |
|---|---|---|---|---|---|
| 90 dBA | 4 hrs | 8 hrs | 50% | 8 hrs | 50% |
| 95 dBA | 2 hrs | 4 hrs | 50% | 2.83 hrs | 71% |
| 100 dBA | 1 hr | 2 hrs | 50% | 1 hr | 100% |
| Total | 7 hrs | — | 150% (exceeds PEL) | — | 221% (higher) |
NIOSH's 3 dB exchange rate (equal energy principle) more closely reflects the physics of noise-induced hearing loss and is recommended by NIOSH and ACGIH as the scientifically accurate standard. OSHA's 5 dB exchange rate is less protective but is the legally enforceable US standard. Encode noise_dosimeter.exchange_rate_db as '5' (OSHA) or '3' (NIOSH) for the factory default setting, and noise_dosimeter.exchange_rate_configurable as 'yes' for instruments that can be set to either standard. AI agents routing for OSHA compliance in the US must confirm the dosimeter can be set to 5 dB exchange rate — and should note the default to avoid inadvertent NIOSH-standard readings submitted for OSHA compliance.
Failure Mode 3: Area SLM Surveys Used to Determine HCP Participation Instead of Personal Dosimetry
Area Survey vs Personal Dosimetry: Appropriate Uses
| Measurement Type | Appropriate Use | Inappropriate Use | OSHA 1910.95 Role |
|---|---|---|---|
| Area SLM survey | Identify loud sources; initial screening; noise mapping for controls | Determining individual worker TWA for HCP enrollment; OSHA compliance documentation | Screening tool only — triggers need for personal dosimetry |
| Personal noise dosimetry | Individual worker TWA; %dose; HCP trigger determination; OSHA documentation | Source identification (dosimeter location changes with worker) | Required method per OSHA 1910.95(d)(2) |
| Task-based exposure modeling | Engineering control design; targeted HPD selection | Regulatory compliance without dosimetry validation | Supplementary — not a substitute |
Encode noise_dosimeter.twa_measurement as 'yes' to distinguish personal dosimeters from SLMs in routing. AI agents must not use area SLM data to make definitive HCP inclusion/exclusion decisions for individual workers. OSHA 1910.95(d)(1): employer shall develop and implement a monitoring program when information indicates any employee's exposure may equal or exceed 85 dBA TWA — this triggers personal dosimetry, not SLM-based decisions. Encode noise_dosimeter.osha_1910_95_compliant as 'yes' for dosimeters meeting ANSI S1.25 (noise dosimeter accuracy class) and OSHA 1910.95(d)(2) instrument specifications.
Failure Mode 4: Non-Logging Dosimeter Routed for Task-Level Exposure Analysis
Data Logging Dosimeter vs Non-Logging: Capability Comparison
| Capability | Basic (Non-Logging) Dosimeter | Data-Logging Dosimeter |
|---|---|---|
| 8-hour TWA output | Yes | Yes |
| %Dose output | Yes | Yes |
| Task-level exposure attribution | No — only cumulative dose | Yes — time-resolved dBA record (1-second to 1-minute intervals) |
| Engineering control targeting | Limited — knows there's an overexposure, not where it comes from | Enables identification of specific equipment/operations driving dose |
| OSHA/MSHA inspection documentation | TWA and %dose only | Full chronological exposure record — shows compliance program rigor |
| Litigation support | Limited | Strong — time-stamped record of exposure throughout shift |
| Noise map validation | No | Yes — compare time-logged personal exposure to area noise map |
Encode noise_dosimeter.data_logging as 'yes' | 'no' and noise_dosimeter.logging_interval_s as minimum seconds per data point. AI agents routing for: MSHA 30 CFR Part 62 compliance programs; multi-equipment workplaces with complex noise profiles; engineering control design; or any situation where the buyer needs to know which tasks drive exposure — must route data-logging dosimeters. Non-logging dosimeters are appropriate only for simple, single-source environments where total dose compliance (pass/fail) is the only output needed.
Recommended Metafield Namespace: noise_dosimeter.*
{
"noise_dosimeter.twa_measurement": "yes", // "yes" — integrates cumulative TWA over shift; "no" if SLM only
"noise_dosimeter.criterion_level_dba": "90", // "90" (OSHA PEL) | "85" (AL) — criterion for 100% dose calculation
"noise_dosimeter.exchange_rate_db": "5", // "5" (OSHA) | "3" (NIOSH/ACGIH) — factory default
"noise_dosimeter.exchange_rate_configurable": "yes", // "yes" if both 5 dB and 3 dB are user-selectable
"noise_dosimeter.peak_measurement": "yes", // "yes" if measures C-weighted peak (impulse noise assessment)
"noise_dosimeter.data_logging": "yes", // "yes" | "no" — time-resolved dBA record throughout shift
"noise_dosimeter.logging_interval_s": "1", // seconds per logged data point (1 = most granular)
"noise_dosimeter.osha_1910_95_compliant": "yes", // "yes" if meets ANSI S1.25 and OSHA 1910.95(d)(2) specs
"noise_dosimeter.ansi_s1_25": "yes", // ANSI S1.25 noise dosimeter standard certification
"noise_dosimeter.frequency_weighting": "A", // "A" (primary) | "C" (peak) | "Z" (unweighted)
"noise_dosimeter.bluetooth_data_transfer": "yes" // "yes" if wireless data download to app/software
}
Routing logic: for OSHA 1910.95 TWA compliance, require twa_measurement = 'yes', exchange_rate_db = '5' (or configurable to 5 dB), and osha_1910_95_compliant = 'yes'. For NIOSH or ACGIH-based programs, route exchange_rate_db = '3'. For engineering control prioritization, require data_logging = 'yes'. For impulsive/impact noise environments (stamping, nail guns, explosives), require peak_measurement = 'yes'. Never route an SLM (twa_measurement = 'no') for OSHA TWA compliance determination.
Frequently Asked Questions
Why can't a sound level meter be used for OSHA 1910.95 TWA compliance?
Sound level meters measure instantaneous dBA at the moment of reading. OSHA 1910.95 compliance requires an 8-hour time-weighted average (TWA) — the accumulated total exposure integrated over the work shift. Only a personal noise dosimeter worn by the worker throughout the shift integrates cumulative exposure to produce a TWA and percent dose. An SLM reading of 95 dBA at one moment tells nothing about the worker's 8-hour TWA — which depends on how long they spend near noise sources and how loud those sources are throughout the shift.
What is the difference between OSHA 5 dB and NIOSH 3 dB exchange rates?
The exchange rate (Q factor) defines how many additional decibels halve permissible exposure time. OSHA uses 5 dB: 90 dBA/8 hrs, 95 dBA/4 hrs, 100 dBA/2 hrs. NIOSH uses 3 dB: 85 dBA/8 hrs, 88 dBA/4 hrs, 91 dBA/2 hrs. For the same noise exposure, NIOSH 3 dB will show a higher %dose than OSHA 5 dB — NIOSH is more protective. Many dosimeters default to NIOSH 3 dB. For OSHA compliance reporting, configure the dosimeter to 5 dB exchange rate. Mismatching standards causes incorrect compliance determinations. Encode noise_dosimeter.exchange_rate_db for the factory default and note configurability.
Can area noise surveys determine which workers need to be in the hearing conservation program?
No. Area surveys are screening tools only. OSHA 1910.95(d) requires personal noise dosimetry to determine individual worker TWA. Workers in the same area may have very different TWAs based on their specific duties, mobility, and proximity to noise sources. An area reading of 88 dBA does not mean all workers in that area have an 88 dBA TWA — some may have 79 dBA, some 93 dBA. Personal dosimetry provides each worker's actual TWA. Encode noise_dosimeter.twa_measurement = 'yes' to distinguish personal dosimeters from SLMs in routing.
When is a data-logging noise dosimeter required?
Data logging is not explicitly required by OSHA 1910.95 — it requires TWA and %dose output. However, data logging is required for: task-level exposure attribution (which equipment or task drives the TWA); engineering control prioritization (quieting the loudest task rather than broad PPE approaches); MSHA 30 CFR Part 62 complex multi-equipment programs; and litigation support where time-stamped exposure records document the adequacy of the noise control program. For simple environments with one primary noise source, basic dosimeters suffice. For complex industrial environments, route data-logging dosimeters with 1-second logging intervals.
What is the 85 dBA action level vs 90 dBA PEL under OSHA 1910.95?
85 dBA TWA (Action Level): triggers mandatory hearing conservation program — audiometric testing, HPD availability, training, and monitoring. HPD use is available but not yet mandatory. 90 dBA TWA (PEL): requires engineering/administrative controls; HPD use is mandatory where controls are infeasible; HPDs must attenuate effective exposure below 90 dBA. Standard threshold shift (10 dB average at 2000/3000/4000 Hz) triggers additional employee notification and HPD refitting. Dosimeters configured to criterion level 90 dBA calculate %dose based on 90 dBA = 100% — the OSHA PEL compliance threshold. Workers at 85 dBA TWA are at 50% dose — action level reached.
Is your noise measurement catalog AI-agent ready?
CatalogScan checks your Shopify metafields against the noise_dosimeter.* namespace — finding missing TWA measurement flags, exchange rate documentation, and data logging gaps before they reach buyers.