12.3 SOW, Timelines, Costs, Personnel & Documentation

SOW, Timelines, Costs, Personnel, and Documentation

The bid package is the pile of files that turns Domain 2 requirements into a price. Independent OpenExamPrep teaching for published PSP Domain 3 Task 1 knowledge is that incomplete scope of work (SOW) is the number-one change-order machine in physical security. Integrators cannot mind-read device counts, software license tiers, training hours, spare parts, or as-built duties. If it is not in the package, it is either a guess in the bid or an extra after award. Section 12.1 made bidders look at the same site. This section makes them price the same deliverables.

Exam focus: Name what belongs in the SOW. Separate lump sum, allowances, and unit prices. Treat named people as commitments. Missing forms make a cheap bid non-responsive.

Detailed scope of work

A security SOW is not “install a camera system.” It is a buildable description of what will exist at acceptance:

• Devices: each opening and each scene—reader, lock, door position switch, request-to-exit, camera, intercom, duress, panel, power supply—with counts, locations, and the performance sentences from Domain 2 (identification versus detection, fail state, report time).
• Software: VMS and ACS license tiers, client seats, analytic channels, failover, the cybersecurity hardening the owner actually wants, and whether existing servers are reused or replaced. Annual subscription years included in the bid must be stated, or year-two licensing will arrive as a surprise invoice.
• Pathway and integration: who provides conduit, cable, network drops, fire-alarm release, elevator interface, and the HR termination feed. Division 28 versus 26/27 must be explicit, as 12.1 required in the pre-bid.
• Training: who is trained (operators, administrators, security supervisors), how many hours, whether a recorded session is required, and whether a follow-up visit after thirty days is included.
• Spare parts: cards or credentials, lock hardware, a spare switch, a spare camera of each type—named quantities, not “as needed.” Spare parts are how a failed head does not wait on a factory boat during residual-risk hours.
• As-builts and closeout: record drawings, device addresses, password turnover, recommended-spares list, warranty start, and operation-and-maintenance manuals. An as-built is a record of the installed condition, not permission to ignore the spec.
• Phasing and occupied operations: which doors stay live, temporary measures, escort rules, and infection-control barriers.

If any of those bullets is a shrug, the low bidder will omit it and the high bidder will include it. You will award to the shrug and then pay the high bidder’s number as a change order. That is not contractor greed as a first cause. It is an owner document that never required the work.

Worked hospital: “Upgrade pharmacy access control” without a door schedule is how you discover at submittal that the anteroom interlock, the narcotics cabinet, and the after-hours dual-control rule were never priced. The change order is not a surprise. It is the SOW you refused to write. Worked warehouse: “Provide dock cameras” without naming identification versus detection, licenses, mounts, cable, switch capacity, and training produces four incompatible numbers. The silent bidder from 12.1 and the thin SOW are the same failure wearing two hats.

Owner-furnished equipment belongs in the SOW too. If the owner will supply servers or credentials, say when they arrive and who configures them. If the contractor must furnish them, say that. Split responsibility with no sentence is another extras factory.

Project timelines

The package should state substantial-completion and final-acceptance targets, phasing, long-lead items, owner-furnished equipment dates, and blackout dates (census, holidays, board meetings, receiving waves). A timeline that says “ninety days after award” with no allowance for factory lead times on electrified hardware will produce either a false bid or a later delay claim.

Security projects die on other people’s clocks: badging for airport work, infection-control permits, IT change windows, and authority-having-jurisdiction inspections. Put those as milestones with owners. Bidders price overtime if the pharmacy can only be cut over on weekends; they cannot price it if you hide the constraint in a hallway comment that never became an addendum.

A Gantt chart in an RFP is a communication tool. Contractual time is the agreement, including liquidated damages if you use them. Do not put a pretty chart in a marketing appendix and a contradictory paragraph in the general conditions. If liquidated damages apply, state the daily amount and when the clock starts. If they do not, do not bluff.

Phasing is part of time. A campus that must keep Door 4 detecting while Door 5 is in pieces needs a temporary measure in the SOW and a date on the timeline. “Means and methods” does not excuse a dead detect path you never mentioned.

Costs, allowances, and unit prices

Lump sum prices the defined SOW. It is clean when the SOW is complete. It is a weapon when the SOW is vague: the contractor priced a thin job and will not donate the missing training.

Allowances are owner-directed pots of money inside the contract for work that is known in kind but not in quantity or selection (a finish-hardware allowance, a spare-cable allowance, an extra-device pool the AHJ may require). Allowances are not contractor profit and not a substitute for design. Unused allowance typically returns to the owner; overruns need a written process. An allowance stuffed to hide an unfinished door schedule is still an incomplete SOW.

Unit prices state a price per extra reader, extra camera, extra foot of pathway, extra training hour. They are how you add a door during construction without inventing a rate under pressure. They only help if the unit definition matches the real extra (a camera with license, mount, cable, configuration, and as-built update—not a bare camera body). Publish the estimated extra quantities if you expect them, so bonding and crew size are honest.

Alternates let the owner buy or decline a package (analytic licenses, a second site, a higher identification-grade lobby camera) without re-bidding. Unit prices and alternates belong on the bid form, not in a cover letter that evaluators might miss.

Cost breakdowns (labor, material, software, tax, bond) help evaluation and later changes. A single number with no breakdown is hard to negotiate and hard to audit. On IFB work the breakdown may be informational; on RFP work it often supports best-value discussion. Either way, do not let “allowance” and “unit price” become synonyms. They are different tools.

Key personnel and resumes

RFP and RFQ packages typically demand a project manager, a field superintendent, and manufacturer-certified technicians for the ACS, VMS, or intrusion brands in the spec. Those names are bid commitments. Silent substitution of uncertified labor after award is how a listed delayed-egress device is miswired and how a database is migrated by someone who has never seen that software.

Resumes should show relevant work—hospital pharmacies, live cutovers, occupied schools—not a generic “twenty years in low voltage.” The owner should have a contractual right to reject a replacement who is weaker than the person who won the score. If the certified tech is 80 percent allocated to three other jobs, the resume is bait. Ask for current workload or a letter that the named person will be on this site for cutover weeks.

Guard-service packages have the same idea with account manager, field supervisor, and post-training lead. A cheap wage with no named supervisor is how posts go dark.

Required documentation

Responsive bids typically include: bid form, acknowledgment of addenda, bid security (bid bond or check), insurance certificates or a statement of ability to insure, licenses, proposed deviations list, technical compliance matrix (12.4), manufacturer authorization letters, and sometimes a sample commissioning or training outline. Missing a required form is how a cheap bid dies as non-responsive. Do not “fix it after opening” on a public IFB unless the statute truly treats that item as a minor informality. Most missing bonds are not minor.

After award, the same package should already have pointed to submittals: cut sheets, shop drawings, programming matrices, and test plans. Those are not bid-day forms, but the SOW should say they are required before devices ship. A bid package that never mentions as-builts will not grow as-builts at closeout out of courtesy.

Write the SOW as if the winning firm will be a stranger who only does what is written. That stranger is exactly who will show up. Section 12.4 scores the offers and keeps ethics in the file.