Lay out the whole CCTV system on the satellite map

It is where you plan a security camera system before you install it: where each camera goes, what it can see, how it is cabled or linked back to the recorder, how much storage it needs and what it costs. In FieldStacker you lay the CCTV system out on the satellite map of the customer's property, and the same layout becomes the customer's proposal and your estimate.

FieldStacker does not pick a number for you. You place cameras on the map and each one draws its real view and its detail rings (faces identifiable, people recognisable, plates readable, IR night range), so you can see the gaps and add or turn a camera until the areas the customer cares about are covered. The layout counts every camera, switch and recorder for the quote.

From the camera's spec: the published horizontal angle, or a diagonal angle converted to horizontal and marked as estimated. Zoom lenses get a slider, and pan-tilt cameras show their sweep. The detail rings use IEC 62676-4 pixel densities (about 76 pixels per foot to identify a face) and come in closer when the camera is mounted higher, because it looks down at a steeper angle.

Yes. Add a photo of the plans, a PDF page or a DXF drawing (an AutoCAD DWG has to be saved as DXF or printed to PDF first) and it sits under your CCTV layout. A photo taken at an angle is flattened square by dragging the four corners of the sheet. You move, turn and resize it on the map, set the scale from two points you know the distance between, fade it, lock it or hide it, then trace rooms, inside walls and doors over it. A DXF can make the walls for you from its layers. Inside walls stop a camera's view and open doors let it through. A layout holds up to six blueprints, and they never appear on the customer's proposal.

Yes. Each switch or recorder adds up the PoE watts of every camera and radio it powers, from each model's spec sheet. You get a warning past 80% of its PoE budget, an error when the draw is over the budget, and an error when there are more PoE devices than PoE ports.

Yes. Each recorder checks its channel count against the cameras routed to it, and its incoming bandwidth. You set the days to keep, continuous or motion recording and the drive size, and it shows the terabytes needed, the number of drives, how long one drive lasts, and a red warning if the drive size is bigger than the recorder takes per bay or the drives will not fit its bays.

Yes. Draw point-to-point pairs or an access point with several clients. A link that crosses a building or obstruction you traced turns red, and you are warned when it is longer than the radio's rated range or carries too much camera traffic for the radio. It also gives the Fresnel zone clearance at the midpoint. The map cannot see heights, so it always says to check line of sight on site.

Yes. Place a battery backup and the switches and recorders near it plug in automatically; radios follow their switch. It shows the load against the UPS rating, about how many minutes it lasts on battery at night with IR on, and an outage view of which cameras keep recording and which go dark when the power goes out.

Draw each cable run on the map and it measures the length, adds your waste percentage and a service loop, and warns about any Ethernet run over 90 m (about 300 ft). Lengths from the map are estimates until you enter one wall you measured on site, which calibrates the whole drawing. Runs you mark as existing wire are left off the quote.

No. The proposal and the equipment list describe each item in plain words, never the make or model. A shared link shows the layout drawing only, with no prices, model numbers or contact details.

It is on for every company set up as an alarm company in FieldStacker, on Pro ($30/mo), Team ($60/mo) and Team Pro ($250/mo). It is not part of Website & Hosting. For other kinds of companies it is a beta we switch on company by company. Every plan starts with a 14-day free trial with no credit card.