From Door Schedule to Bill of Quantities: Quantifying an Access Control System Without Missing Items

2026-11-19来源 dev.to PythonEnglish

By Chen Yu — ELV (extra-low-voltage) systems designer since 1998

Ask five estimators to price the access control on the same set of drawings and you will often get five different totals. The card readers are usually right. The differences hide in everything around them: the exit buttons, break-glass units, door contacts, double-leaf locks, controllers that run out of reader inputs, and cable that was measured on the plan but never got a routing allowance.

Over 25+ years designing and pricing ELV systems — access control, CCTV, intrusion alarm, structured cabling and more, for courts, hospitals, schools and public buildings — I have settled on one rule: never count access control hardware off the plan directly. Build a door schedule first, give every door a type, and derive the bill of quantities (BoQ) from the types. This article shows the method and a short Python script that does the derivation, so the BoQ can be re-run every time the architect moves a door.

Step 1: The door schedule

The door schedule is a table with one row per controlled or monitored door. At minimum:

Column Why it matters
Door ID Matches the tag on the CAD layout, so a reviewer can trace every line
Door type code Determines the hardware kit (see Step 2)
Controller area Which controller the door is wired to
Cable distance to controller Drives cable quantities

On a real project you would add leaf count, door material, fire rating, swing direction and the architectural door number, because they all affect which lock can be fitted. But the four columns above are enough to generate a correct BoQ structure.

Step 2: Door types and hardware kits

Most buildings have only a handful of door configurations. Define each one once, as a kit of hardware per door. A typical set:

  • A1 — single leaf, card in, exit button out. Reader, electromagnetic lock, door contact, exit button, emergency break-glass.
  • A2 — single leaf, card in and card out. Two readers (needed for anti-passback or for recording exits), fail-safe electric strike, door contact, break-glass.
  • B1 — double leaf, card in, exit button out. One reader, a double electromagnetic lock, two door contacts (one per leaf), exit button, break-glass.
  • F1 — fire-escape door, monitored only. Door contact and break-glass; no lock on the controlled-access side.

The value of the kit approach shows up on double-leaf doors. Counting by eye, people often take one contact per door; the kit forces two. The same goes for break-glass units on every locked egress door, which are frequently forgotten on the plan but required by fire and life-safety rules in most places. Whether a lock type is acceptable on an escape route, and how it releases on fire alarm, is decided by local codes and the fire authority. Confirm it before fixing the kits.

Step 3: Controllers

Controller quantity is where hand counts are most often wrong, because a controller has two limits: the number of doors it can lock and the number of readers it can accept. A "4-door" controller typically has four reader inputs. One A2 door uses two of them.

So, per controller area:

controllers = max( ceil(readers / reader_inputs), ceil(locked_doors / door_outputs) ) 

Count it per area, not for the whole building: doors wired to different controller locations cannot share spare inputs.

Step 4: Cable

Cable runs follow the devices, not the doors:

  • shielded multi-core for each reader,
  • a power pair for each lock,
  • a signal pair for each door contact,
  • a signal pair for each exit button.

Multiply each run by the routed distance to the controller, then add an allowance for vertical drops, routing around obstacles and terminations. I use 10% when distances are measured along the cable route on the drawings; use more if they are straight-line estimates. Cable designations below use common Chinese specifications (RVVP shielded, RVV sheathed); substitute your local equivalents and check the manufacturer's recommended conductor sizes and maximum distances for readers and locks.

The script

"""Turn an access-control door schedule into a bill of quantities. Usage: python3 door_boq.py doors.csv Each door has a type code; each type maps to a hardware kit per door. """ import csv import math import sys from collections import Counter # Hardware kit per door type (quantities per door). KITS = { # single leaf, card in, exit button out "A1": {"card reader": 1, "electromagnetic lock 280kg": 1, "door contact": 1, "exit button": 1, "emergency break-glass": 1}, # single leaf, card in and card out (anti-passback) "A2": {"card reader": 2, "electric strike (fail-safe)": 1, "door contact": 1, "emergency break-glass": 1}, # double leaf, card in, exit button out "B1": {"card reader": 1, "electromagnetic lock 280kg double": 1, "door contact": 2, "exit button": 1, "emergency break-glass": 1}, # fire-escape door: monitored only (no lock), break-glass for alarm "F1": {"door contact": 1, "emergency break-glass": 1}, } READERS_PER_CONTROLLER = 4 # a 4-reader / 4-door controller DOORS_PER_CONTROLLER = 4 SPARE = 0.10 # 10% cable allowance for routing and terminations def main(path): doors = list(csv.DictReader(open(path, newline=""))) boq = Counter() unknown = [] controllers = 0 cable_m = Counter() for area, group in group_by(doors, "controller_area").items(): readers = sum(KITS[d["type"]].get("card reader", 0) for d in group if d["type"] in KITS) controlled = [d for d in group if d["type"] in KITS and d["type"] != "F1"] controllers += max(math.ceil(readers / READERS_PER_CONTROLLER), math.ceil(len(controlled) / DOORS_PER_CONTROLLER)) for d in doors: kit = KITS.get(d["type"]) if kit is None: unknown.append(d["door_id"]) continue boq.update(kit) dist = float(d["distance_to_controller_m"]) if kit.get("card reader"): cable_m["RVVP 8x0.5 shielded (reader)"] += dist * kit["card reader"] if any(k.startswith(("electromagnetic", "electric strike")) for k in kit): cable_m["RVV 2x1.0 (lock power)"] += dist cable_m["RVV 2x0.5 (contact)"] += dist * kit.get("door contact", 0) if kit.get("exit button"): cable_m["RVV 2x0.5 (exit button)"] += dist boq["4-door access controller"] = controllers print(f"{'item':<36}{'qty':>8} unit") for item, qty in sorted(boq.items()): print(f"{item:<36}{qty:>8} pcs") for item, m in sorted(cable_m.items()): print(f"{item:<36}{math.ceil(m * (1 + SPARE)):>8} m") if unknown: print("\nDoors with no kit defined (fix before pricing):", ", ".join(unknown)) def group_by(rows, key): out = {} for r in rows: out.setdefault(r[key], []).append(r) return out if __name__ == "__main__": main(sys.argv[1]) 

Example door schedule (illustrative, not a real project). Note door 2F-04 has a type code that does not exist yet — on real jobs this happens all the time when the architect adds a door:

door_id,type,controller_area,distance_to_controller_m 1F-01,B1,1F-East,18 1F-02,A1,1F-East,12 1F-03,A1,1F-East,9 1F-04,A2,1F-East,22 1F-05,F1,1F-East,30 1F-06,A1,1F-West,15 1F-07,A1,1F-West,11 1F-08,A1,1F-West,26 2F-01,A2,2F,14 2F-02,A2,2F,19 2F-03,A1,2F,8 2F-04,X9,2F,10 

Output:

item qty unit 4-door access controller 5 pcs card reader 13 pcs door contact 12 pcs electric strike (fail-safe) 3 pcs electromagnetic lock 280kg 6 pcs electromagnetic lock 280kg double 1 pcs emergency break-glass 11 pcs exit button 7 pcs RVV 2x0.5 (contact) 223 m RVV 2x0.5 (exit button) 109 m RVV 2x1.0 (lock power) 170 m RVVP 8x0.5 shielded (reader) 230 m Doors with no kit defined (fix before pricing): 2F-04 

What the output tells you

  • Controllers: 5, not 3. There are 11 doors with a known type, of which 10 are locked or monitored by a reader. A naive "10 doors ÷ 4 per controller" gives 3. But 1F-East has five readers (the A2 door uses two), and so does 2F. Each of those areas needs two controllers. This is the single most common under-count I see in access control BoQs.
  • Door contacts: 12 for 11 doors, because of the double leaf on 1F-01.
  • Break-glass: 11, one for every door that has a known kit, including the fire-escape door.
  • Unknown type flagged. Door 2F-04 does not silently disappear from the BoQ. The script lists it, and nothing should be priced until it has a type.

Making it part of the drawing workflow

The method works best when the door schedule lives next to the CAD layout and both use the same door IDs. When the layout changes, update the schedule, re-run, and compare the new BoQ to the previous one. The differences are the variation, and you can explain every line of it.

From there it is a short step to pricing: map each BoQ item to a unit rate and installation labour, and keep separate lines for the items that are often supplied by others, such as the door hardware fitted by the door contractor. Agree at the start of the job who supplies the locks; that boundary is a frequent source of claims.

Checklist

  1. Tag every controlled door on the layout and build the schedule from the tags.
  2. Define a small set of door types with a complete hardware kit for each.
  3. Count controllers per area against both the reader and the door limits.
  4. Derive cable from devices and routed distances, with a stated allowance.
  5. Fail loudly on any door without a type.
  6. Re-run on every layout revision and diff the result.

None of this requires special software. A door schedule and a short script remove most of the gaps that make access control quotes disagree.

Chen Yu has worked in ELV and intelligent-building design since 1998, delivering or supervising 200+ projects for courts, public-security organs, hospitals, schools, metro lines and industrial parks, and producing more than 30,000 CAD drawings, BoQs and tender documents with Grade-A design institutes in China. Portfolio: https://leoa81761-ops.github.io/

Free tools: if you want this as a ready-made spreadsheet instead of a script, I put a door schedule to BoQ calculator for access control online, plus a free ELV quick calculator (CCTV storage, PoE budget, DC voltage drop). The full set of my ELV estimating sheets is here.

原文:https://www.a8q9.cn/en/article/from-door-schedule-to-bill-of-quantities-quantifying-an-access-control-system-wi-baffa3.html

相关文章