Quick answer: A procurement reviewer accepts documents that name the SKUs on your schedule, not a brand badge. Anabon assembles that evidence as a partner service: per-SKU compliance documentation for the requirement the specification names, the spec sheet for each full SKU and a project-specific written confirmation of which lines are documented. CASE offers NDAA-compliant options for compliance-sensitive projects. Anabon confirms the exact products and provides the official compliance documentation for each project. Ask for it before the pre-bid question deadline, not after award.
Why is compliance documentation a service and not a sentence?
Section 889 of the FY2019 National Defense Authorization Act, the FCC Covered List, grant conditions and state restrictions on covered equipment all attach to equipment: a specific model and what is inside it. In Canada, federal, provincial and municipal tenders set their own supply-chain security clauses case by case; verify each tender. Either way, the reviewer works from your equipment list and looks for a document next to every line. A catalog cover, a website logo or a brand-level letter describes a brand; your bid names models.
The compliance floor also moved in 2026, when screening began to reach the components inside a device rather than only the badge on the housing; FCC Covered List and the 2026 Component Rule covers what changed. The practical consequence is the same for every installer: brand-level assurances protect nobody, and the per-SKU documentation pack is the deliverable. Anabon Security Inc. is a North American B2B distributor of CASE and other professional security brands, and putting that pack together with you is part of what the channel receives.
What does a per-SKU compliance pack contain?
The pack is built for one project and one schedule. Its exact contents depend on the clauses your specification names; the table shows the parts most bids need.
| Part | What it names | What the reviewer does with it |
|---|---|---|
| Per-SKU compliance documentation | The exact model in catalog spelling and the requirement it addresses, such as NDAA Section 889 | Matches it line by line to your camera schedule and bill of materials |
| Spec sheet for each full SKU | The same spelling as the schedule, with the printed rows the specification compares against | Checks the technical clauses and the model identity |
| Project-specific written confirmation | Project, SKU list with quantities, which lines are documented and which need a documented alternative | Confirms the evidence fits this bid, not a generic one |
| Warranty statement by category | The term per product category and how claims flow through the installer | Answers the warranty clause without a blanket number |
| Integration statement | ONVIF profiles per SKU | Answers an interoperability clause in profile language |
| Certificates for Project Series items | Certificate documents per CSP- SKU, such as explosion-proof markings, supplied only after Anabon confirms them in writing for the project | Verifies hazardous-area and similar clauses |
Three statements in the pack are always worded exactly. Warranty: CASE cameras and CASE NVRs carry a 6-year warranty. CASE PTZ cameras carry a 3-year warranty. CASE accessories carry unlimited warranty. Hard drives are supported through back-to-back manufacturer warranty. Integration: ONVIF profiles supported are S, T, and G, with M on pinhole models. Third-party behavior is confirmed per platform and project. Origin: Product documentation is supplied per SKU. For any project with origin, NDAA, or other compliance requirements, Anabon provides the official per-SKU documentation and project-specific confirmation — the document is the answer, so your bid survives a procurement review.
What the pack does not contain
- A brand-wide sentence that every product meets every rule. Not every product carries every documentation type, which is exactly why the pack is per SKU.
- Your own signed representation. On US federal work the offeror’s representation under FAR 52.204-24 is yours; in Canada the tender’s declaration is yours. The pack is what it rests on.
- A legal opinion. Where a clause is unclear, ask the contracting officer or the consultant in writing, and verify with counsel.
- Warranty terms, availability or lead times for CSP- items before Anabon confirms them in writing for the project.
When should you request it?
Earlier than feels necessary. A missing document found at submittal review can cost the bid; the same gap found before the question deadline is a question you can still ask. Anabon does not publish a fixed turnaround; the expected timing is confirmed when your request is received, so build it into the bid calendar.
| Bid stage | What to request | Why then |
|---|---|---|
| Reading the RFP | A first check of which SKUs on your draft schedule are documented for the clauses named | Decides whether to bid and which lines need an alternative |
| Before the pre-bid question deadline | The per-SKU documentation list and any gaps | Gaps can still be raised with the consultant |
| Substitution or “or equal” request | Spec sheets and documentation for each proposed SKU | The approval request needs evidence, not adjectives |
| Bid submission | The project-specific written confirmation for the final schedule | Your representation rests on it |
| After award, at submittals | The pack updated to the approved schedule and quantities | Submittal review checks the same lines again |
| Delivery and closeout | A check that shipped SKUs match the documented SKUs | The O&M binder and the as-built must agree with the pack |
What should your request include?
- Project name, location and buyer type (federal, state or provincial, municipal, school board, grant-funded, private).
- The specification section and the exact clauses: NDAA Section 889, FCC Covered List, TAA, or the Canadian tender’s supply-chain clause.
- The draft camera schedule with every line as a full SKU, for example CS-I8XQ II-2.8mm or CS-N220 P16H-AI, and quantities.
- Accessories and switches on the schedule, because some specifications name switches and network equipment in the same clause.
- Any CSP- items, so certificate documents and written confirmation are requested together.
- The question deadline, the bid date and where the documents will be uploaded.
Send it through Contact Anabon or your business account. The checklist for the rest of the submittal package is in Bid-Ready Documentation Checklist.
How does the pack protect your bid?
- It survives the line-by-line check. The reviewer finds a document for each model on the schedule, in the same spelling.
- It replaces blanket sentences. A sentence a reviewer cannot verify is a reason to reject; a document is a reason to accept.
- It exposes gaps while they are still easy to fix. A line without documentation is swapped for a documented alternative before the bid, not after award.
- It supports your representation. What you sign is backed by per-SKU evidence and a dated written confirmation.
- It carries into closeout. The same pack updates for submittals and the O&M binder, so the system you hand over matches the system you bid.
For the five-document view from the reviewer’s side, see The NDAA Documentation Pack.
What should you never write instead of the pack?
| Avoid | Write instead |
|---|---|
| A sentence that every product is compliant | CASE offers NDAA-compliant options for compliance-sensitive projects. Anabon confirms the exact products and provides the official compliance documentation for each project. |
| “No documentation needed” | Per-SKU documentation is attached for each line on the schedule |
| A verbal statement about where a product comes from | The origin sentence above, with the per-SKU documents |
| “Compatible with any VMS” | ONVIF profiles per SKU; third-party behavior confirmed per platform and project |
| One warranty number for the whole system | The warranty statement by category |
How to use this with your customers
Tell the owner or consultant that compliance is documented per model for their project, and that the documents are attached to your submittal. If they ask whether the brand is compliant, answer with the SKU list and the documents. Keep the pack in the project file; it answers the same question again at closeout and at the next expansion.
FAQ
Are CASE products NDAA compliant?
CASE offers NDAA-compliant options for compliance-sensitive projects. Anabon confirms the exact products and provides the official compliance documentation for each project. Do not write a brand-wide statement in a bid; list the SKUs on your camera schedule and request the per-SKU documentation and project-specific confirmation before you answer the consultant or the procurement officer.
How long does a compliance pack take?
Anabon does not publish a fixed turnaround, because it depends on the number of SKUs, the clauses named and whether CSP- items are involved. The expected timing is confirmed when your request is received. Request it while you read the RFP, before the pre-bid question deadline, so any gap can still be raised with the consultant.
Does the pack cover TAA as well as NDAA?
Only per SKU and per project. TAA is a different rule from NDAA Section 889 and is confirmed for each model separately; never assume that one implies the other. Name the clause in your request, and the project-specific written confirmation states which lines are documented for it and which need a documented alternative.
Can I use one pack for several bids?
Reuse the spec sheets and per-SKU documents as a starting point, but ask for a project-specific written confirmation for each bid. Schedules, quantities, clauses and buyer types differ, and reviewers check that the evidence fits their project. Update the pack again after award so the submittal matches the approved schedule.
Does Anabon talk to the procurement officer or consultant?
No. Anabon is a B2B distributor and supports you behind the scenes. The documents are assembled for your submittal, questions for the buyer are written so you can send them, and the relationship with the owner, the consultant and the procurement officer stays with you as the installer or integrator.
