NFPA 660 vs NFPA 652: what changed and what to update

NFPA's committee record identifies content from NFPA 652, 61, 654, 655, 484, and 664 in the consolidation work. NFPA 652 supplied the common fundamentals role, while the other documents addressed agricultural and food processing, general particulate solids, sulfur, combustible metals, and wood processing.

The result is a single current publication with coordinated common and material-specific content. That improves navigation, but it does not mean every old paragraph moved without change. Use the official current edition for exact requirements.

Yes, as evidence of what was assessed at the time. Keep its process scope, material data, scenarios, findings, recommendations, and closure records. Then check whether the facility, material, process, safeguards, authority context, or current standard changed.

A sound revalidation preserves traceability instead of discarding the old work. It also makes gaps visible: equipment omitted from the original scope, tests that no longer represent the process, incomplete findings, and legacy citations that need a current crosswalk.

Start with the scope register. List each affected room, process unit, dust collector, enclosure, transfer, storage point, and material. Connect each to the old report section, current operating condition, open action, and applicable NFPA 660 content.

Next review material evidence and management of change. Supplier, formulation, particle-size, moisture, throughput, equipment, and collection changes can be more important than the document-number change. Finish by documenting who reviewed the crosswalk and what requires new analysis.

No. NFPA's public consolidation record describes a coordinated project that brought content associated with NFPA 652, 61, 654, 655, 484, and 664 into NFPA 660. NFPA 652 had served the fundamentals role, while the other documents addressed different material or industry contexts. A consolidated publication changes how current content is organized and maintained; it is more than a new cover on one legacy document.

DustDHA does not reproduce the new or old text and does not claim that every provision moved unchanged. Use NFPA's official current edition and development records for exact requirements. The practical transition task is to connect the facility's old scope and citations to current applicable content without losing the evidence and decisions already recorded.

Build the crosswalk around facility decisions, not only section numbers. For each old citation or requirement, record the affected material, area, equipment, scenario, safeguard, recommendation, current operating condition, applicable NFPA 660 location, reviewer, and disposition. Mark content that remains relevant, changed, moved, needs confirmation, or no longer applies to the actual scope.

A bare two-column number table can help navigation but cannot show whether the underlying facility facts changed. Keep a link to the licensed standards used for the review and date the crosswalk. If the reviewer cannot verify an exact mapping, preserve the uncertainty and identify the follow-up rather than assigning a convenient new number.

The historical report can preserve valuable evidence: the processes and materials examined, drawings and tests used, field observations, scenario reasoning, identified safeguards, recommendations, closure decisions, and the facility condition at the time. Those records support trend review and prevent the organization from repeating discovery work. Their value does not depend on pretending the standard edition is current.

Retain the original report and attachments unchanged, then issue a dated revalidation or transition record. That record should distinguish editorial citation updates from technical changes. If material, equipment, process, safeguards, or assumptions changed, explain the additional analysis. A document-number substitution should never conceal a missing scope review.

The legacy set carried specialized context for agricultural and food processes, combustible metals, general particulate solids, sulfur, and wood processing. NFPA 660 coordinates common and material-specific content, but a facility still needs to identify which materials, operations, and interfaces apply. A site handling several particulate families may need more than one material-specific path.

Use old specifications and reports to find which legacy documents shaped equipment and controls, then verify the current NFPA 660 scope. Do not infer an exact current chapter solely from a marketing label or this site's industry card. The official standard and a qualified reviewer remain the authority for a mixed or unusual process.

Start with documents that direct future work: corporate standards, project specifications, equipment requirements, design criteria, inspection forms, management-of-change checklists, training references, and procurement templates. Identify legacy citations, confirm their current NFPA 660 counterparts, and retain a revision note explaining the transition. Do not erase old references from records describing work performed under an earlier edition.

Prioritize technical meaning over global search-and-replace. A specification may have quoted an old document number while also embedding assumptions that need review. Route revised controlled documents through the facility's normal technical and document-control process. The goal is a traceable basis for current decisions, not a cosmetically uniform library.

A publication change is a reason to review applicability and gaps, but the scope of work should depend on the facility's actual record. A complete, current, well-scoped analysis with verified safeguards may support a focused crosswalk and revalidation. An old report with omitted systems, stale material data, unclosed recommendations, or substantial changes may require broader work.

Ask the qualified reviewer to state which parts can be relied on, which need confirmation, and which require new analysis. Preserve the rationale. DustDHA cannot turn report age and a document number into that technical decision; its tracker and RFQ intake help organize the facts for the conversation.

Do not close an old recommendation merely because its citation is legacy. Trace it to the hazard or scenario it addressed, verify current facility conditions, identify any corresponding NFPA 660 basis, and review the selected safeguard or disposition. Keep implementation, testing, inspection, and acceptance evidence with the action record.

If a recommendation is revised or replaced during revalidation, document why the new action addresses the underlying issue. If it no longer applies, record the factual and technical basis. This preserves accountability across standard editions and gives future reviewers more than a status field.

Ask whether the engagement includes an old-report scope audit, standards crosswalk, current facility walkdown, material-data review, management-of-change review, open-action assessment, scenario revalidation, and controlled-document recommendations. Request the current edition used, the disciplines involved, deliverable format, assumptions, exclusions, and treatment of areas absent from the old report.

Have providers distinguish a citation refresh from technical revalidation and from a new DHA. Those are different scopes. Issue the same legacy documents and change summary to each bidder so pricing and schedules can be compared on equivalent work.

Store the old report, current crosswalk, revalidation deliverable, source editions, facility scope register, material evidence, change history, open actions, and approvals together. Add a short read-me explaining which document controls current decisions and which remain historical evidence. Assign an owner and review trigger.

Future reviewers should be able to follow a chain from the original scenario through changes, current citations, recommendations, and closure. Visible dates and sources matter because NFPA publications and public authority pages can change. DustDHA shows its own verification date for the same reason and schedules a source review rather than treating web copy as permanent.

Update training references when controlled procedures or facility requirements move to NFPA 660, but preserve the operational meaning employees need. Explain that legacy names may remain on older reports, equipment documents, and drawings, and show workers where the current controlled instruction lives. A document-number lesson alone is not a substitute for material, housekeeping, ignition-control, inspection, or emergency responsibilities.

Record which roles received the change, the effective revision, questions raised, and any field documents that still need correction. If an old label creates a real ambiguity, route it through document control and management of change. The transition succeeds when current decisions are clear and historical evidence remains traceable.