DHA cost calculator: inspect every planning allowance

A small site with one documented process and current material data is a different engagement from a multi-building facility with interconnected systems, several dust families, incomplete drawings, and new testing. Fieldwork, travel, stakeholder workshops, engineering calculations, and deliverable depth also differ.

The broad published range is therefore an anchor, not a tariff. The calculator exposes its complexity allowances so a reader can challenge the assumptions instead of receiving a single unexplained number.

Count distinct process units and dust-collection systems, not only buildings. Identify material samples that need characterization, whether current representative tests exist, operating schedules, access constraints, prior DHA scope, change history, and expected deliverables. Include location and travel assumptions.

Send the same scope summary to each provider. Ask them to state included systems, site time, tests, draft review, final report, exclusions, and optional engineering work. That makes commercial differences visible.

It does not claim that the line-item allowances are published standard rates. They are transparent planning rules around one published market anchor. It does not determine the required testing program, applicable standard scope, professional discipline, or site risk.

Each result displays its method, date, source, and disclaimer. Treat it as a budgeting and RFQ-preparation aid. A provider quote should replace it once the actual scope is known.

The model selects a low and high base allowance from the facility complexity band, then adds low and high allowances for each entered process unit, dust sample, collection system, and optional travel. Every line is shown in the result. The total is the arithmetic sum of those lines, so there is no hidden multiplier or unpublished score.

Only the broad $9,000–$85,000 overall market anchor is attributed to the linked vendor article. The individual dollar allowances are DustDHA planning assumptions calibrated for a budgeting exercise; their source notes say so. NFPA and laboratory links explain technical context, not market prices. This distinction is essential when using the result.

Small, medium, and large are model bands, not regulatory categories or square-foot thresholds. They provide a starting allowance for baseline document and facility review. The selector cannot capture multiple buildings, unusual processes, poor records, access restrictions, or the experience required. Those details belong in the written scope and provider proposal.

Choose the band that best describes the overall planning complexity, then use unit counts to make major drivers visible. If the result will influence a budget request, record why the band was chosen and show decision-makers the model method and uncertainty. Do not relabel the band as a provider estimate.

Count distinct operations or equipment groups that require their own meaningful review rather than every valve or an entire plant as one unit. Examples might include receiving, size reduction, transfer, mixing, drying, finishing, packaging, storage, and reclaim, but the appropriate grouping depends on the actual process and connected systems.

Use the same unit list when requesting proposals. A provider may regroup it after reviewing flow, materials, and scenarios; ask them to explain the change. The model's per-unit allowance is not an NFPA fee schedule or a published provider rate. It is a transparent sensitivity lever.

Enter the number of samples you reasonably expect might require new laboratory work, while preserving uncertainty. Different materials, suppliers, process fractions, moisture states, recycled streams, or collection points may not be represented by one sample. Existing data may reduce new work only when a qualified reviewer accepts that it represents the actual condition and decision.

Zero is valid for an early planning scenario but does not prove that testing is unnecessary. The result's line note tells users to confirm tests and prices directly. Compare a zero-sample scenario with a plausible alternative to understand budget sensitivity, then let the project team define the real program.

Dust collectors and connected transport systems can require dedicated review of configuration, interfaces, operating conditions, safeguards, and documentation. Their work does not necessarily scale in the same way as a general process-unit count. Separating the input helps buyers disclose how many systems they expect the provider to address.

Count distinct systems rather than visible collector labels alone, and note shared ducts, recirculation, indoor or outdoor location, and connected equipment in the RFQ. The model allowance remains an assumption, not a design fee or statement of required protection. A qualified provider must validate the technical scope.

The public form accepts one through forty process units, zero through twenty samples, and zero through twenty collection systems. These limits keep the quick calculator within the kind of planning scenario it can display and reduce accidental or abusive submissions. They do not state that a facility outside the boundary is invalid or exempt.

If a project exceeds a limit, prepare a direct scope inventory and request a tailored proposal instead of splitting the facility into artificial calculator runs and summing them. A provider may find dependencies that make separate arithmetic misleading. Boundary validation is a software control, not an engineering rule.

First inspect the line items and confirm every input. A low result may reflect a simple model scenario, not a guaranteed minimum. A high result may reflect many counted units or samples, not a market ceiling or evidence that all work is necessary. The total can extend beyond the vendor-published overall span because the model does not hide or clamp the entered complexity.

Use an outlying result as a prompt for scope review. Ask providers to identify what can be grouped, what evidence is reusable, what testing is needed, and what work is optional. Do not adjust inputs solely to land inside a preferred range.

Attach a list of facilities, process units, materials, dust-collection systems, existing tests, prior reports, known changes, requested deliverable, target timing, and access constraints. Include the calculator inputs, result, method, source anchor, and date as planning context. State that bidders should validate and replace the assumptions.

Request included systems, site time, tests, workshops, draft review, final report, travel, exclusions, options, and technical team. Sending equivalent information makes responses easier to compare. DustDHA may route one qualified request to no more than three firms; the buyer remains responsible for selection and contract scope.

Refresh the estimate when the process inventory, material set, available test data, collector count, facility boundary, travel assumption, or requested deliverable changes. Also revisit the public source anchor when its review date arrives. Save the old version with its inputs so the budget history remains understandable.

A newer calculator date does not make a model more authoritative than a provider's validated scope. After proposals arrive, compare model assumptions with quoted work and document the reasons for differences. That feedback can improve internal budgeting without converting one project into a universal price claim.

Use the calculator for scope counts and broad facility context; do not place confidential formulas, drawings, security details, trade secrets, or sensitive incident records into fields that do not request them. The optional RFQ collects the information needed for matching and explains that a qualified request may be shared with no more than three providers.

Exchange detailed technical records under the facility's approved confidentiality and procurement process after selecting whom to engage. Save the calculator output according to internal records policy. A planning token and PDF are conveniences, not a secure engineering document repository.