Security camera as-built drawings that stay current

A security camera as-built drawing is the record of what was actually installed: every camera’s position on the floor plan, its model, where it points, and how it is set, as the system stood at handover. The design is what the bid proposed. The as-built is what the crew put on the wall after the ducts, the distributor’s stock, and the client’s last-minute changes had their say. It is the document everyone reaches for later, and the one that goes out of date soonest.

What belongs in a camera as-built

A useful as-built answers the questions people ask years after the install, without anyone climbing a ladder:

• A camera number and name that match the recording system, so the camera on the drawing is the camera in the video.
• Its position on a scaled floor plan.
• The model, as installed, not as bid.
• The lens setting. The field of view the camera is set to, which on a varifocal model is not on the datasheet.
• The aim, drawn as a direction and a reach.
• Mounting height and tilt, which set the dead zone under the camera.
• What it is for: the detail level its area needs, such as identify at a door or detect across a lot.
• Photos of the mount and of the view on the day it was accepted.
• A camera schedule: the same facts as a table, one row per camera.

Network details such as address, switch port, and cable label usually live in a separate schedule. The drawing’s job is where and what.

Why it goes stale

Every change to a camera system is small, and none of them updates the PDF. A camera is swapped for a different model because the original was out of stock. One is moved two feet to clear a duct. A dome is re-aimed around a new sign. Two cameras are added at the loading dock in year three. One comes down in a renovation and is never replaced. Each change makes sense to the person doing it, and each one moves the drawing further from the building.

Five years in, the as-built describes a building that no longer exists, and that shows at the worst moments: the investigator asking which camera covered the side door, the service tech looking for camera 14, the auditor asking for evidence of coverage at the entrances, the next integrator bidding the refresh. What auditors ask about camera systems covers what that third conversation looks like.

Keeping a static as-built honest

If the as-built is a file, keeping it true is a manual routine:

1. File the as-built, not the bid. After commissioning, update the drawing to the real positions, models, and aims before it goes into the client’s records.
2. Give it one owner. A drawing anyone may edit tends to be a drawing nobody updates.
3. Update it on every work order. A swap, a move, or a re-aim is closed when the drawing changes, not when the camera is back online.
4. Walk it once a year. Compare the drawing to the ceiling, camera by camera, and fix what drifted.

The routine holds while the person who owns it stays and the fleet stays small. It is the first thing dropped in a busy quarter. AXIS Site Designer covers the same routine for an Axis design project.

An as-built that keeps up on its own

The MentatNOC camera coverage map is an as-built made from the cameras themselves. Each pin is a camera the platform is already watching, carrying its model, field of view, mount height, tilt, and reach level, so the drawing and the device are one record. It notices change three ways. A camera that goes offline or is pulled goes dark on the drawing. A camera that no longer sees what it was installed to see reads as a tamper event. A camera in the fleet that is not on the drawing sits in the list of cameras not yet placed until someone puts it there. When a camera is physically moved, drag its pin to the new spot, and everything else on the pin follows the device.

The rest of the as-built comes with it:

• Stable camera numbers. Every pin gets a number when it is placed, and numbers are never reused, so camera 07 stays 07 on the map, the schedule, and the plan sheet for the life of the plan.
• Design to as-built without redrawing. Planned cameras are drawn on the same plan. When one is installed, it is promoted to the real device and keeps its position and aim.
• Handover as a revision. Save a named revision of the plan at handover. Later, compare it with the plan today to see what moved, turned, or disappeared.
• Photos on the pin. Install and context photos sit on each pin, and hovering a pin shows its newest install photo with the camera’s name and health. Location data is stripped from every photo on upload.
• An audit trail. Every edit to the plan lands in the audit log with who changed what.
• Exports. The plan sheet PDF puts the calibrated drawing on the first page and the camera schedule on the pages after it. The schedule also downloads as a CSV, with the camera number in the first column.

Doing this across 500 cameras

An integrator looking after 500 cameras across a dozen client sites has a dozen as-builts, each owned by whoever last touched it, and each out of date in its own way. Keeping them true by hand is a standing job that loses to every service call. On the coverage map, the as-built stops being a handover deliverable and becomes a live record: the same drawing at handover and in year five, current both times because it reports what the cameras report. It monitors device health, not video.

MentatNOC is a white-label managed services toolkit for security integrators, added to the service contract and bundled with the monitoring they already sell. When a camera on the drawing goes offline, freezes, or reports tamper, a classified ticket lands in the integrator’s own ticketing system under their own SLA, naming the camera and the site. Dispatch knows where the device is and what failed before the truck leaves the shop, the tech brings the right part when the alert calls for one, and the integrator calls the customer before the customer finds the gap. See it running against a 500-camera fleet on the interactive demo.