Deadlines.
Costs. Clarity.

NFPA's public consolidation record identifies the combustible-dust material previously organized through NFPA 652, 61, 654, 655, 484, and 664. NFPA 652 served the common-fundamentals role, while the other documents addressed agricultural and food processes, general particulate solids, sulfur, combustible metals, and wood processing. NFPA 660 coordinates common and material-specific content in one current publication.

That history matters because older DHAs, drawings, specifications, training, and equipment records still cite the legacy documents. Keep those references as evidence of the basis used at the time. For current decisions, map the affected material, process, safeguard, and old citation to the licensed current NFPA 660 edition. DustDHA summarizes the transition and links the official sources; it does not reproduce protected requirements, tables, or figures.

A facility that manufactures, receives, processes, transfers, stores, or collects combustible or potentially combustible particulate should organize an evidence-based screen. Start with the actual material states and process locations, including fines, collected dust, recycled streams, blends, and credible upset conditions. A product name, safety-data-sheet silence, or a visual particle-size judgment is not enough to settle the question.

OSHA's public combustible-dust guidance describes relevant characteristics such as Kst, minimum ignition energy, minimum explosible concentration, and particle size when known, and explains that moisture and other physical conditions can affect behavior. Record what evidence represents the actual process, what has been ruled out on a valid basis, and what remains uncertain. A qualified reviewer decides the technical scope; DustDHA does not classify a material from a web form.

An NFPA consensus standard is not automatically one uniform statute for every U.S. facility. A site's obligations can involve adopted fire or building codes, an authority having jurisdiction, permits, insurer requirements, contracts, OSHA regulations, the General Duty Clause, and the federal or State Plan enforcement context. Those pathways and local editions can differ.

OSHA's revised Combustible Dust National Emphasis Program provides inspection procedures and industry focus; it does not create a simple national NFPA deadline that this site can declare. Confirm the responsible OSHA or State Plan office and the local authority for the actual facility. DustDHA's state pages publish the verified OSHA jurisdiction classification and deliberately avoid inventing fire-code adoption or enforcement claims where a current primary-source record is not stored.

Use two clocks. The first is the applicable periodic revalidation checkpoint, commonly planned from the prior DHA completion date. The second is event-driven: a material, process, equipment, throughput, collector, layout, control, procedure, incident, inspection, or new test result can make an assumption stale earlier. A future calendar date does not excuse an invalidated analysis.

The six-question tracker shows its inputs and uses a five-year planning baseline where that cycle applies. It does not inspect the facility, verify the old report's scope, determine local adoption, or issue a compliance finding. Save the result with the prior report, current standard source, jurisdiction check, and change register. If no applicable prior DHA can be established, organize the first-analysis scope instead of inventing a completion year.

A useful DHA states its boundary: buildings, rooms, materials, process units, transfers, storage, collectors, connected systems, normal operation, startup, shutdown, cleaning, maintenance, and credible upset modes. It identifies the evidence used, assumptions and gaps, hazards or scenarios considered, existing safeguards, and recommendations. The report should be traceable enough for another qualified reviewer to understand what was and was not analyzed.

A checklist can help collect field information but should not conceal technical reasoning. Missing drawings or test data belong in the input register and report. After issue, recommendations need owners, decisions, implementation evidence, and change screening. DustDHA never performs, reviews, or signs that work; it helps a facility prepare a consistent brief for qualified providers.

The dated public anchor used by DustDHA is a vendor-published overall span of $9,000 to $85,000. It is not an independent market average, an NFPA fee schedule, a guaranteed minimum or maximum, or a quote for a particular facility. The breadth is plausible as a scope signal because projects can differ in buildings, process units, materials, records, fieldwork, testing, connected systems, workshops, calculations, travel, and deliverables.

The calculator makes its own low and high model allowances visible line by line. Those allowances are DustDHA planning assumptions and are labeled as such; contextual NFPA or lab links do not turn them into observed prices. Use the output to test scope sensitivity, then replace it with comparable written provider proposals.

Testing is useful when it answers a defined material, hazard-analysis, or protection-design question with a representative sample and appropriate method. Kst describes a normalized rate of pressure rise in a standardized deflagration test context, while Pmax is the maximum pressure measured there. Other characteristics address ignition sensitivity or concentration questions. No one result describes housekeeping, confinement, connected equipment, ignition sources, occupancy, or safeguards.

Document the sampled process location, material or formulation, operating condition, particle and moisture state, preparation, method, units, and chain of custody. Ask a qualified lead to decide whether existing data represents the facility and which new tests are needed. DustDHA does not publish GESTIS-DUST-EX material values because commercial reuse remains license-gated; an unsourced lookup would be worse than an explicit gap.

Compare the proposed people and scope, not a logo or a star score. Ask who leads and technically reviews the work, which relevant materials and processes the team has handled, which edition and methods it will use, and how fieldwork, testing, calculations, recommendations, and draft review are divided. Verify registrations, certifications, or laboratory accreditation with the issuing body when they matter to the task.

Issue the same facility and process inventory to every bidder. Require included areas, site time, owner inputs, tests, workshops, deliverables, exclusions, options, travel, schedule, and change process. DustDHA profiles summarize claims from provider-owned public pages with source links and verification dates. A claimed profile verifies control of the listing; it is not an endorsement or engineering-quality rating.

Prepare a facility and process scope list, material register, current drawing and document index, equipment and collection-system information, available test reports, prior DHAs, open recommendations, closure evidence, incident or near-miss records, known changes, desired deliverable, schedule constraints, and confidentiality needs. Mark each item current, historical, missing, or uncertain.

Share equivalent facts with each prospective provider and let them identify gaps. Keep sensitive formulas, drawings, security details, and trade secrets inside the facility's approved confidentiality process rather than an unnecessary public-form field. DustDHA's RFQ captures enough structure for matching and discloses that a qualified request may be shared with no more than three providers. Detailed engineering records should move under agreed controls.

The complete tracker result appears on screen without an email wall. A user may request a watermarked PDF for their records, then optionally carry the facility profile into the RFQ. The public scoring rubric screens whether the request contains enough fit and intent for provider routing. Qualified contact details can be delivered to no more than three matched firms; the searcher decides whom to contact or hire.

Searchers never pay DustDHA. Participating providers may pay for qualified introductions after the disclosed free period, using published per-delivery or retainer terms. DustDHA remains the information and routing layer, not the engineer, laboratory, authority having jurisdiction, broker of the final contract, or guarantor of a provider's work.

Every canonical content page carries a last-verified date and links its evidence register. Requirements-class claims rely on primary NFPA and OSHA material; incident context relies on CSB; provider facts link to provider-owned sources; and the cost anchor is explicitly labeled vendor-published. Pages are scheduled for review rather than presented as timeless. Unsupported national enforcement dates, invented reviews, customer logos, and material values do not publish. A correction should update the source receipt, visible date, page record, sitemap timestamp, and generated corpus together.

The sitemap, structured data, and llms text expose the same canonical records to search and answer engines. That technical surface does not make a claim true; the source chain does. IndexNow submission and search-console verification still require a live domain and production credentials. Local code can prepare those paths without pretending an external submission occurred. Search-engine inclusion and AI citation remain external outcomes, never guarantees made by this product.