Quick answer: Security system design support at Anabon starts with one rule: bring us the opportunity before you say no. Send the drawing, site notes and the requirement for any job that is larger, more specialized or more compliance-sensitive than your usual work; we check it against the printed rows of each full CASE SKU and return a corrected schedule, sizing, a SKU and accessory list, a documentation list and the open questions. You decide whether and how to bid, and the end-user relationship stays with you.
Which opportunities should you bring before you say no?
Most installers turn down work for the same handful of reasons: the job is bigger than the usual recorder, it names a technology the team has not installed, it carries a compliance clause nobody wants to sign, or the deadline leaves no time to research. Those are exactly the jobs a distribution and channel partner is for. Anabon Security Inc. is a North American B2B distributor of CASE and other professional security brands, and project review is part of what the channel receives. Not every project should be accepted blindly; the point is to decide with facts instead of declining on instinct.
| Opportunity type | Signal you see | Why a review helps |
|---|---|---|
| Larger than your usual job | More cameras than your standard recorder, two buildings, a phase two | Channel count, bandwidth, PoE layout and storage are sized before you commit to a number |
| Specialty technology | Thermal, explosion-proof, long-range or laser PTZ, radar perimeter, off-grid solar | Candidates are identified; CASE Project Series items are confirmed per project in writing |
| Compliance-sensitive | Section 889, FCC Covered List or TAA clauses (US); supply-chain clauses in Canadian public tenders | Documentation is requested per SKU before you answer the consultant |
| Integration-dependent | An existing VMS, a gate or access control system, an ONVIF clause | Profiles and third-party behavior are checked per platform instead of assumed |
| Analytics requests | Facial recognition, plate search, people counting, safety-helmet detection | Use case, model, firmware and legal requirements are confirmed before anything is promised |
| Short bid window | An “or equal” clause, a substitution deadline, a pre-bid walk next week | The equivalence work and the document list start the same day you send the file |
Small jobs qualify too. A five-camera site with one awkward 400 ft (about 120 m) run or a gate camera at the edge of the network is a fair reason to ask.
What should you send with the request?
Send what you have and say what is missing; the first four items are enough to start.
- A drawing, site plan or aerial image with one known dimension for scale.
- Site notes and photos: mounting positions, wall and ceiling types, telecom rooms, existing network and power.
- A draft camera schedule: tag, location, purpose (overview, identification, plate), preferred form factor.
- Owner requirements: retention days, users and viewing locations, remote viewing, areas to exclude for privacy.
- The specification section and addenda if it is a bid, with the question and substitution deadlines.
- Constraints: phasing, cold or hazardous areas, long runs, existing equipment that must stay.
The full intake list, with the reason behind each item, is in Project Design Review: What Anabon Checks Before You Quote.
What does the review check?
Every check is made against the printed row of the exact SKU, never a similar model or a series name. One letter in a CASE SKU can change the series, housing and specs, so the review starts by writing every line in full catalog spelling.
- Coverage: lens and resolution against the purpose of each position; IR and white-light rows against the darkest position; IP and IK ratings and the operating temperature against the site.
- PoE and network: the PoE class of each device against the switch budget; every copper run against 328 ft (100 m); bt-class PTZs on their own supply; uplinks between buildings.
- Storage and bandwidth: retention days and bitrate against drive bays; total incoming bitrate against the recorder row with AI on.
- Channel headroom: today’s device count plus the next phase against the channel count.
- Compliance: which clauses the specification names and which per-SKU documents answer them.
- Software scope: what the owner expects from mobile, desktop and remote access against what is supported today for that model and version.
- Accessories and spelling: a mount and junction box per camera; no legacy model anywhere on the schedule.
- Project Series flags: any item with the CSP- prefix is marked as project-quoted until availability, certificates, lead time and warranty term are confirmed in writing.
Three wording checks ride along with every review, because a proposal is your document and your customer’s contract reference. Warranty by category: 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. Compliance per SKU: CASE offers NDAA-compliant options for compliance-sensitive projects. Anabon confirms the exact products and provides the official compliance documentation for each project. Integration as profiles: ONVIF profiles supported are S, T, and G, with M on pinhole models. Third-party behavior is confirmed per platform and project.
What do you get back?
| Deliverable | What it contains | How you use it |
|---|---|---|
| Corrected camera schedule | Your tags and positions with full SKUs, lens, mount and box per line | The core of your proposal and your bill of materials |
| Sizing summary | Channels, incoming bandwidth, PoE budget per switch, storage against retention | Defends your numbers when a consultant asks |
| SKU and accessory list | Every line in catalog spelling, including switches, injectors, mounts and boxes | Order list; nothing waits on site for a bracket |
| Documentation list | Spec sheet per SKU, compliance documents the specification asks for, warranty wording by category | Your submittal package checklist |
| Open questions | Items only the owner or engineer can decide, written so you can forward them | Your next call with the customer |
| Project Series notes | Which CSP- candidates were found and what still needs written confirmation | Keeps unconfirmed items out of the proposal |
Timing depends on the size of the project and how complete the file is, so we tell you the expected timing when we confirm receipt rather than publishing a fixed figure. Private pricing for the result comes through your approved business account or a direct quote, and the customer only ever sees the number you decide to quote.
An anonymized example: the yard that nearly went unbid
The scenario below is illustrative. It combines requirements that come up often; it is not one customer’s project, and no site or partner is described.
A regional installer who usually quotes 8 to 16-camera retail jobs is invited to bid a public-works yard: about 30 cameras across a vehicle garage, an office and a fenced yard, after-hours deterrence on the fence line, coverage near a fuel dispensing area, 30-day retention, and a grant condition that asks for Section 889 documentation. The fuel area, the compliance clause and the size each looked like a reason to decline. The installer sent the site plan, photos and the specification section instead.
- Recorder: 30 cameras plus a phase two pointed to the CS-N440 P16H-AI, printed as 40CH with 16 PoE ports, 400Mbps / 400Mbps bandwidth (AI on: 200Mbps / 200Mbps) and 4x10TB HDD. The review sized the camera bitrates against the AI-on incoming row, not the headline figure.
- Second building: the garage sat beyond 328 ft (100 m) of copper, so its cameras went on a CS-POE33024PF (24 Gigabit PoE ports, 30W per port, 400W / 600W total budget, 2×1000M SFP fiber uplinks) with a fiber link back to the office.
- Fence-line deterrence: a CS-P88 44X on a pole: 8MP, 44X zoom, 984 ft (300 m) IR and a laser up to 1,640 ft (500 m) as printed. EW and AEW are deterrence features. Availability is confirmed per SKU. The laser is a deterrent, not an illuminator, and is offered on selected models only. Its power row is DC36V or PoE++ (IEEE 802.3bt), so it was given its own supply rather than a port on the af/at switch.
- Fuel area: the hazardous-location classification is set by the owner’s engineer and the authority having jurisdiction under the NEC (in Canada, the CEC); verify the local code. The review listed two options for that decision: a standard camera placed outside the classified area looking in, or an explosion-proof candidate such as the CSP-I8PS EX-I-2.7-13.5mm, project-quoted, with availability, certificates and lead time confirmed in writing before it appears in a proposal.
- Documents: a per-SKU documentation list for every line on the schedule, the warranty wording by category, and the software statement limited to what is supported today.
The installer went to the pre-bid meeting with a schedule, a sizing summary and three written questions for the engineer. Whether a bid like this wins depends on the owner; what changed is that the decision to bid was made on facts. For more on site types like this one, see Municipal Yards and Public Works.
How to use this with your customers
Tell the customer what is true: your company designs, installs and services the system, and your distributor reviews the design and supplies per-SKU documentation behind the scenes. If the owner asks who supports the hardware, the answer is you, with Anabon supporting you through the approved warranty process. Keep open items open in writing; a question listed in the proposal is better than a promise you cannot pass through.
FAQ
How fast does a project review come back?
It depends on the size of the project and how complete the file is, so Anabon tells you the expected timing when receipt is confirmed instead of publishing a fixed figure. A scaled drawing, site photos, a draft schedule and the owner’s retention and user requirements move fastest. Anything missing is listed back to you in that first reply.
Does Anabon contact my customer during the review?
No. Anabon is a B2B distributor and supports you as the installer, integrator or dealer. Questions for the owner or the engineer are written so you can forward them yourself, and warranty and service for your customer run through you. Anabon stays behind the scenes, so the customer relationship and the proposal remain yours.
Is my project too small to ask for a review?
No. A five-camera job with an unusual run, a gate camera at the edge of the network or a first PTZ is a fair reason to ask. The sales line applies to every size of job: bring us the opportunity before you say no. Smaller files are usually quicker to check because there are fewer open items.
Can the review include thermal, explosion-proof or radar items?
Yes, as a project conversation. CASE Project Series items with the CSP- prefix are project-quoted. The review identifies candidates, but availability, certificates, lead time and warranty term are stated only after Anabon confirms them in writing for that project, so nothing unconfirmed goes into your proposal.
What if the review says the job should not be bid as written?
That is still a useful result. The review may suggest reshaping the scope, splitting a phase, asking the consultant a clarifying question or using a documented alternative for one line. Sometimes it shows the job is not a fit. Either way you decide with written facts instead of declining on instinct or bidding blind.
