Quick answer: A bid-ready documentation package for a camera project has six parts: a spec sheet for every full SKU on the schedule, compliance documentation per SKU for the project, a warranty statement by product category, a software statement that lists only what is supported today, an ONVIF profile statement, and the drawings and schedule the reviewer checks the rest against. Assemble it before the bid is due, in the order Division 01 asks for, and the reviewer has nothing to bounce.
What goes into a submittal package for a camera bid?
Division 01 (01 33 00 Submittal Procedures in CSI MasterFormat, used in the US and Canada) sets the format, the portal or copies, and the sequence; Division 28 Part 1 names the documents it wants for video surveillance. Packages bounce for three reasons: a model number that does not match the schedule, a missing document the spec named, or a blanket claim the reviewer cannot verify. How to Read a Video Surveillance RFP shows where these clauses sit.
| Item | What it contains | Source | Why packages bounce |
|---|---|---|---|
| Product data (spec sheets) | One sheet per full SKU, revision date, relevant rows marked | Current CASE spec sheet per SKU, from Anabon | Partial SKU; stale revision |
| Compliance documentation | Per-SKU documents the spec names (NDAA Section 889, FCC Covered List, TAA, listings) | Anabon, per SKU and per project | Brand-level letter instead of per-SKU documents |
| Warranty statement | Term by product category, how claims flow | The exact CASE wording below | “6-year on everything”; wrong PTZ term; a term stated for a CSP- item |
| Software statement | What is supported today for app, desktop and remote access | CASE Connect wording below; capability confirmed per model and firmware | Future features; integration promised without a test |
| ONVIF statement | Profiles per SKU, third-party behavior per platform | SKU spec sheet | “ONVIF compatible” with no profile named |
| Drawings and schedule | Camera schedule, shop drawings, riser, network and power plan | Your design, cross-checked with Anabon’s project review | Count differs from drawings |
| Qualifications and closeout | Licenses, references, training plan, O&M and as-built commitments | Your company file | Training hours not stated |
How do you prepare the spec sheets per SKU?
Write the full SKU, every time
A CASE SKU carries a series letter that changes housing, specs and sometimes the AI list: write CS-I8XQ II-2.8mm, never a shortened model name or “8MP turret”. The schedule, the bill of materials, the spec sheet header and the compliance document must all show the same spelling. Legacy models no longer offered never appear in a package; ask Anabon when a spec names a model you do not recognize.
Mark the rows the spec asks for
Reviewers look for the numbered requirement, not the whole sheet; list the rows that answer each Part 2 paragraph. For the CS-I8XQ II-2.8mm the printed rows include 8MP / 2.8mm Fixed, 3840×2160@30fps, Max. IR Distance 164 ft (50 m), White Light Distance 98 ft (30 m), 120dB True WDR (TWDR), IP66, Metal housing, a 1 TB memory slot and built-in mic and speaker. Some catalog pages print a reduced row set; that page prints no operating temperature or compression row, so those values come from the SKU spec sheet, never from a similar model. The order of authority is spec sheet, then catalog, then website copy; Or Equal Substitution Security Camera Guide shows how to turn the rows into a compliance table.
Check the revision date and the accessory sheets
Submit the current revision with its date on the cover sheet, and add the sheets for mounts, junction boxes and the PoE switch, because reviewers check that the mounting and power path exists. The CS-POE33024PF, for example, prints 24×10/100/1000M RJ45 PoE ports, IEEE 802.3af/at, 30W max per port, a 400W / 600W total PoE budget and 2×1000M SFP fiber uplinks; those rows answer the network paragraph without a separate letter.
What is the exact warranty statement?
Warranty clauses are pass or fail and reviewers compare them word for word. Use this wording, by category, and never a blanket figure:
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.
| Category on the schedule | Term to write | Note for the reviewer |
|---|---|---|
| CASE cameras (fixed, panoramic, special) | 6-year | Exceeds a 3- or 5-year clause |
| CASE NVRs | 6-year | Recorder line items |
| CASE PTZ cameras / speed domes | 3-year | A stated deviation against a 5-year clause; cover with a contractor warranty line if you choose |
| CASE accessories (mounts, boxes, PoE) | Unlimited | Mounts, junction boxes, switches, injector, splitter |
| Hard drives | Back-to-back manufacturer warranty | Not a CASE term; the drive vendor’s term applies |
| CASE Project Series (CSP- prefix) | No term stated | Confirmed in writing per project, with availability, certificates and lead time |
Add one sentence on process: warranty support goes through the installer, dealer or approved business account that supplied the system, with Anabon supporting that partner; the owner contacts you, not Anabon. If an end user reads your package: for warranty and service, please contact the installer or company that supplied your system. Details in CASE Warranty by Category.
What does the software statement say?
Write only what is supported today, and tie every capability to a model and version. The approved wording: CASE Connect is the official app experience for CASE systems. App features and remote access options should be confirmed by model, software version, and project configuration. A reviewer who asks for a desktop client gets a technical answer that names CASE Station, the desktop VMS, with features confirmed per version; a reviewer who asks about remote configuration gets CASE Cloud described as remote NVR configuration over P2P, never as cloud recording. Where the spec lists analytics, name them from the printed AI row of the exact SKU, confirmed per model, firmware, software version and project configuration. The CS-N220 P16H-AI, for example, prints AI by NVR (Face Detection, Face Recognition, Tripwire, Double Tripwire, Perimeter, Smart Motion Detection) and VCA Search; face functions are discussed only after the use case, region and legal requirements are confirmed. No sentence in the statement describes a future release.
The ONVIF line
ONVIF profiles supported are S, T, and G, with M on pinhole models. Third-party behavior is confirmed per platform and project. If the owner keeps an existing VMS, attach a bench-test record or written confirmation rather than the word “compatible”.
How do you document compliance per SKU?
Compliance is a document per SKU, never a sentence per brand. The wording: CASE offers NDAA-compliant options for compliance-sensitive projects. Anabon confirms the exact products and provides the official compliance documentation for each project. In the US the clause usually cites NDAA Section 889 and the FCC Covered List; in Canada public buyers set compliance requirements case by case in their own documents, so read the clause and ask for exactly what it names. TAA and domestic-preference requirements are confirmed per SKU and project with documentation, never assumed. Listings are answered from printed rows and listed accessories: UL (ULC in Canada) for power supplies and enclosures, FCC Part 15 (ICES-003 in Canada) for emissions, the electrical code for the installation (NEC in the US, CEC in Canada). A listing the sheet does not print is a stated deviation, not a gap to hope past. Read The NDAA Documentation Pack: What to Ask Your Distributor Before a Bid.
Which drawings and closeout documents belong in the package?
- Camera schedule: tag, location, full SKU, lens, mount, box, PoE class, cable route, NVR channel; the same table later becomes the as-built. Format in Writing a Camera Schedule and Bill of Materials.
- Shop drawings: device locations on the floor plans, mounting heights in ft (m), fields of view where the spec asks, head-end rack elevation.
- Riser and network plan: switch ports, PoE budget per switch, uplinks, VLAN or separate network, NVR incoming bandwidth with analytics on.
- Power plan: circuits, UPS runtime, PoE class per device, bt-class PTZs on their own supply or injector.
- Closeout commitments: as-built format, O&M manuals, credential handover method, training hours and attendees, spare parts list.
The checklist (copy it into your job folder)
Copy this table into your own spreadsheet, one column per bid; items marked “per SKU” repeat for every full SKU on the schedule.
| # | Item | Scope | Source | Done |
|---|---|---|---|---|
| 1 | Spec sheet, current revision, rows marked | Per SKU | Anabon | |
| 2 | Accessory sheets: mount, box, switch, injector | Per SKU | Anabon | |
| 3 | Compliance documents named in the spec | Per SKU, per project | Anabon | |
| 4 | Warranty statement by category, exact wording | Per package | This article | |
| 5 | Software statement, supported today, per model and version | Per package | This article; Anabon confirms | |
| 6 | ONVIF profile statement | Per SKU | SKU spec sheet | |
| 7 | Camera schedule and bill of materials, full SKUs | Per project | Your design | |
| 8 | Shop drawings, riser, network and power plan | Per project | Your design, reviewed with Anabon | |
| 9 | Project Series items: written confirmation of availability, certificates, lead time | Per CSP- item | Anabon, in writing | |
| 10 | Qualifications: licenses, references, insurance, training certificates | Per package | Your file | |
| 11 | Closeout commitments: as-built, O&M, training, credentials, spares | Per package | Your proposal | |
| 12 | Cover sheet: project, section, addenda, revision dates, contact | Per package | Your file |
What to tell your customer
“Every model on the schedule is listed by its full part number with its current specification sheet attached, and the compliance documents your specification names are supplied per model for your file. Warranty is stated by product category, software is described as supported today for the exact models and versions, and the drawings match the schedule line by line.”
FAQ
What is a product data submittal for security cameras?
It is the package of spec sheets, statements and drawings that proves each scheduled product meets the specification, submitted under Division 01 before ordering. For cameras it holds one spec sheet per full SKU, the compliance documents the spec names, a warranty statement by category, a software statement and the camera schedule; the reviewer approves it, approves it as noted, or returns it.
Can I attach one compliance letter for the whole brand?
No. Reviewers verify compliance per model, and a brand-level sentence is a blanket claim they cannot check. 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 the per-SKU documents as soon as the schedule is drafted, because they take time to assemble per SKU.
What warranty wording do I put in a security camera bid?
Use the category wording exactly: 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. For CASE Project Series items with the CSP- prefix, state no term until Anabon confirms it in writing for the project.
Where do I get the spec sheets and documents?
From Anabon, per SKU, through your approved business account or a direct request with the project name and the schedule. Ask for the current revision and the accessory sheets at the same time, and send the specification section so the compliance documents match what the clause actually names. Anabon supports you behind the scenes; the submission stays yours.
