Before you replace anything
The applicable requirement depends on the contract, the funding source and the buyer. This page is general information, not legal advice. Verify the current rule and the exact model before purchasing or removing equipment.
Dahua equipment reaches a procurement limit through a contract, a funding condition or the FCC Covered List, not through a sudden defect. Read the requirement and who enforces it, collect model-level documentation, then replace by role: cameras, recording and video management, access control and intercom. Existing equipment can often stay while a phased migration is planned.
A Dahua installation rarely fails all at once. What changes is the paperwork around it: a new federal contract, a grant approval, a lease requirement or a policy update from a parent organization, any of which turns an ordinary camera replacement into a compliance question.
This page separates the federal procurement rule from the FCC equipment rule, sets out what to verify before accepting a replacement, and describes a phased migration that keeps coverage and door control working. It is general information, not legal advice; confirm your obligations with counsel and your procurement contact.
When a Dahua system turns into a procurement question
A Dahua deployment usually becomes a question through a document rather than a fault. Section 889, carried into contracts by FAR Subpart 4.21, restricts federal agencies and their contractors from buying covered telecommunications and video surveillance equipment or using it in a covered system. The obligation follows the work being performed, not the invoice that paid for the cameras, which is why a private owner can inherit it with a single subcontract and no change to the equipment itself. Contract language, not the model list, usually decides the answer. Two sites with identical cameras can therefore carry different obligations, and only the contract paperwork separates them.
The FCC Covered List is a separate mechanism that governs new equipment authorization and marketing, so it changes what can be bought rather than what is already bolted to a wall. Funding conditions, state procurement rules and insurer questionnaires frequently layer on top of both. A risk review may name the platform for reasons of its own, and that is a management decision for the owner rather than a determination an integrator can make. Treating any single one of these as the whole requirement is how projects overrun. The answer for one building is rarely transferable to the next one, even on the same campus with the same owner.
Documents that answer the compliance question
Start with the requirement itself: the contract clause, the purchase order, the grant term or the customer standard. Write down which rule applies and who enforces it, then ask the manufacturer for a statement covering the exact model and part number. A component-level bill of materials, an FCC ID where authorization applies, and country-of-origin information belong in the same project file so a later reviewer starts from evidence rather than from a vendor's assurance. Give the same packet to every vendor who quotes, so the proposals compare on documents rather than on confidence.
Check the FCC ID against the Commission equipment authorization records rather than a reseller listing, and keep a copy with the system documentation. Detail at the model level matters because a documented product family can still ship a variant with a different radio module or firmware source. A blanket "NDAA compliant" statement about a product line is not evidence for the part number in your quote, and it is not a substitute for a review by counsel or your contracting officer. Date the file, because the answer changes when the contract, the model or the rules change.
Replacement options for each system role
For cameras, Axis, Hanwha Vision, Avigilon, Bosch, Pelco, i-PRO and VIVOTEK are the manufacturers that appear most often in commercial specifications. Selection turns on the view to be covered, the light available at night and whether analytics have to run locally. For recording and video management, Milestone and Genetec are open platforms that keep camera choice flexible; a recorder-native system is simpler to start with and harder to leave later, and that trade belongs in the plan rather than in the sales conversation. Vendor concentration is the real trade there: an open platform spreads the decision across manufacturers, while a recorder-native one keeps it with the recorder supplier.
Access control follows the door schedule rather than the camera plan, and Brivo and LenelS2 are the two platforms most common in commercial buildings. Intercom stations sit at entrances and should be chosen together with the credential system, because a station that cannot release the door or share badges creates a second directory to maintain. Every one of these choices still needs model-level documentation before it is specified into a restricted project or written into a proposal. Badge format and door release are the two details that most often break an intercom upgrade after the hardware arrives.
Migrating in phases while the site stays covered
Removing a working system in a single weekend is rarely funded and rarely necessary. Private ownership is not automatically unlawful, so the deadline usually comes from a contract, a funding condition or an insurer rather than the brand. Where a federal obligation touches the site, the equipment has to leave that path, and the plan should say which views and doors leave first and which can wait for the next budget cycle or the next tenant improvement package. Say what happens to a camera that fails mid-migration before it fails, not after the truck is booked. The date belongs in the file next to the clause that produced it.
Inventory cameras, recorders, controllers and entry stations by location and role, group them into phases, and segment the old system on a restricted network zone while the new one comes online on separate addressing. Replace the recorder and the highest-risk views first, then move outward by zone. After each phase, confirm live view, recording, retention and door release, update the asset list with what was removed, and keep the dated record with the contract file. Two short visits per zone are usually better than one rushed cutover that leaves retention untested.
Sources
Frequently asked questions
Does the FCC Covered List make an installed Dahua system illegal?
No. The list governs new equipment authorization and marketing. Equipment that was lawfully authorized and installed is not invalidated by a later listing, though contract terms, funding conditions and insurance requirements can still prohibit it on a specific site.
What should I collect before requesting a replacement quote?
The contract or funding condition, a model and serial list, manufacturer statements for the proposed models, FCC IDs, and country-of-origin information. Keep them together so the next review starts from evidence instead of a sales claim, and give the same packet to every vendor who quotes.
Can a Dahua recorder stay while the cameras are replaced?
It can, if it supports the new cameras over ONVIF or another documented protocol and its storage and retention fit the new stream profiles. Keeping a restricted recorder inside a federally funded path does not resolve the restriction, so the recorder often moves in the first phase.
Last reviewed: