Acceptance Testing Under Schedule Pressure
A new 12-floor headquarters for 1,800 employees is two weeks from occupancy. The security package - 140 card readers, 96 IP cameras, 22 intrusion zones, 6 intercoms - was installed by the general contractor's low-voltage subcontractor. Acceptance testing this week found: 18 readers drop offline for about six minutes when the primary server fails over; measured video retention is 19 days against a 30-day specification; and four intrusion zones report 'ready' during a walk test while the door is standing open. The integrator calls these punch-list items and has submitted a request for substantial completion and 90% payment. The move date is contractual and already booked with the movers.
1. Quantify the video retention shortfall so it can be argued commercially rather than emotionally.
Read the worked answer
Baseline calculation at the specified 4 Mbps, 24/7:
- One camera per day: 4,000,000 bits/s × 86,400 s = 345.6 Gb ≈ 43.2 GB/day
- 96 cameras: 96 × 43.2 GB = 4,147 GB/day ≈ 4.05 TB/day
- 30 days: 4.05 TB × 30 = ≈121.5 TB usable video
- With RAID-6 overhead (say 10 data + 2 parity, ×1.2) and 10% headroom: ≈160 TB raw
What is actually installed: 19 days at the same rate ≈ 77 TB usable. The shortfall is roughly 45 TB usable, 55–60 TB raw.
Before you use that number, check the bitrate. If the integrator 'made the math work' by dropping the configured bitrate, retention is being bought by degrading image quality, which is a second specification failure wearing the first one's clothes. Require the configured stream settings in writing and reconcile them against the design.
Do not accept extrapolation as proof of the fix. After storage is added, validate with a seven-day recorded sample and confirm the projected 30-day figure from actual disk consumption, not from a calculator.
Commercial framing: this has a clean remedy - add storage, or accept a reduced-retention scope with a written credit and a re-baselined retention policy the business signs. Lead with the remedy, not the accusation; it is the one defect on the list that money can close in a week.
2. Which findings do you refuse to accept, which are genuine punch list, and how do you handle the schedule and payment pressure without becoming the reason the move slips?
Read the worked answer
Reject - these are functional failures, not punch list:
- Reader failover, 18 readers offline for six minutes. Failover is a stated requirement. Six minutes of dead readers on 18 doors at a 1,800-person building is an availability failure, not cosmetics.
- Intrusion zones reporting 'ready' while the door stands open. Safety-critical, and it indicates miswiring, a missing or wrong resistor, or programming error. Demand a documented 100% walk test of all 22 zones with a result recorded per zone.
- 19 days versus 30 days retention. Measurable, and fixable commercially.
Genuine punch list: cable management, labeling, camera aim and focus, door hardware adjustment, intercom audio levels, operator-documentation formatting.
Handling the pressure. Refusing to let people move is a losing position and makes you the villain of a booked move. Defining the conditions of moving is a winning one:
- Issue a written non-conformance list with severity, remedy and date per item.
- Withhold payment per contract for the rejected items; do not sign substantial completion.
- Offer a beneficial occupancy agreement: the owner takes the building, the contractor retains a defined retainage (e.g., 10%) and a 30-day closeout window, with agreed daily escalation after that and a named escalation contact on both sides.
- Keep the general contractor's contract administrator copied on everything, because your leverage is the GC's payment to the subcontractor, not your relationship with the integrator.
What you are protecting: six minutes of dead readers during a fire alarm or a security incident is the exact moment the system gets tested for real. The building opening on time with documented interim mitigations - manual door control and posted staff - is a defensible outcome. The building opening with a silent failover defect is not.
3. What must be delivered before the first employee badges in, beyond the non-conformance items?
Read the worked answer
Technical handover
- As-builts and a full IP/network schedule; cameras and controllers on their own VLAN, not reachable from the flat corporate network.
- Default credentials removed, firmware current, admin accounts transferred to the owner - with the integrator's accounts disabled.
- Every zone, door and camera labeled to match the physical space, and the label list handed over.
Operational readiness
- A written alarm response matrix: which alarm goes where, how fast, and what the responder does.
- Operator training on the PACS, video export and alarm acknowledgement, with an attendance record - untrained operators are the most common cause of 'the system doesn't work.'
- A mass credential issuance test: badge 50 people from HR data and verify access rights match their role, before you attempt 1,800.
- Key control and cabinet keys, signed for.
Commercial
- Warranty start date documented, spare parts list, and a 30-day hypercare period with the integrator on site.
- Test evidence on file: door-prop alarms, failover, verified retention, all 22 zones walked, all 6 intercoms audited.
The test that matters most: badge a stranger in at 0700 on day one and see whether the system, the operator and the response plan behave the way the paper says they will.