13.3 Project Management Functions in Procurement

Project Management Functions in Procurement

Independent OpenExamPrep teaching for published PSP Domain 3 Task 2 knowledge is that project management (PM) during procurement is how the owner avoids buying a schedule fantasy. The process gates in 13.1 and the diligence in 13.2 can still produce a disaster if nobody owns a scope baseline, a RACI, a risk register that names long-lead cameras and panels, change control that differs before and after award, coordination with IT, facilities, and the authority having jurisdiction (AHJ), and a kickoff that happens before the first crate is promised. The exam-friendly failure sentence is: “We awarded last week; the first device arrives in 26 weeks.”

Exam focus: Freeze scope at award. Name who decides. Put factory lead times on the register before you sign. Addenda change documents before award; change orders change the contract after. Kickoff is a control, not a cake.

Scope baseline

The scope baseline is the awarded definition of the work: issued CDs, specifications, addenda, bid clarifications that were published to all, the bid form quantities, and the contract type from 13.1. PM’s first job is to freeze that package in a revision table. Everything else is a change.

Without a baseline, every hallway request is “already included.” With a baseline, “add six heads on the mezzanine” is either an addendum (if you are still in Chapter 12) or a change order (if you have awarded). Security projects bleed because cameras are easy to point at on a walk-through and hard to license, cable, and store.

Write the baseline in owner language the invoice can match: Door 4 device set, Camera 12 function, license counts, training hours, as-built requirement. Do not freeze a slogan (“world-class video”).

If two documents conflict, the contract’s order-of-precedence clause decides. PM’s job is to find the conflict now, not at commissioning. A baseline review meeting that compares the door schedule to the bid form is cheap. A field fight about whether Door 4 included the homerun is expensive.

RACI during procurement

A RACI (responsible, accountable, consulted, informed) chart stops the “I thought procurement was doing that” gap. For a security buy, typical rows include:

• Requisition and technical attachments — Security designer or owner security PM responsible; budget owner accountable.
• Budget approval — Finance / project controls accountable; security and IT consulted.
• Solicitation documents and addenda — Procurement responsible; security consulted for technical content (Chapter 12).
• Evaluation and diligence — Evaluation committee responsible; procurement officer accountable for process; legal consulted on conflicts.
• Award and contract execution — Procurement or the officer with signature authority accountable.
• Receiving of goods and license entitlements — Owner warehouse or security PM responsible; IT consulted on license registration.
• Invoice approval — Project controls responsible; security PM confirms progress; accounts payable matches the PO.

Accountable means one name, not a department. Two accountables is zero. A RACI that lists “Security” on every cell is a poster, not a control.

IT must be consulted before you solicit a network VMS, not informed after award when the VLAN ticket has a six-week queue. Facilities must be consulted on ceilings, power, and occupied-hour rules. The AHJ is consulted when delayed-egress, maglock release, or a permit path will gate the schedule. Leaving those names off the RACI is how the 26-week camera is joined by a 12-week network change and a permit that was never applied for.

Risk register for long-lead cameras and panels

A risk register during procurement is a living list: the risk, the trigger, the owner, the mitigation, and the residual. For electronic security the repeating stars are long-lead cameras, custom readers, access panels, lock power supplies, and manufacturer training seats.

Factory quotes of 16 to 26 weeks are not folklore. Outdoor multi-sensor heads, specific analytic cameras, and panels tied to a credential format go out of stock. If the owner’s board wants a 30-day cutover after award, and the factory quote in the file is 26 weeks, the PM who signs that schedule has accepted a fiction.

Mitigations you can actually use:

• Ask lead times in the solicitation (Chapter 12.3 timelines) and score schedule realism.
• Early procurement / owner-furnished equipment (OFE) for frozen SKUs after design freeze, with storage and title rules.
• Approved equals in the Chapter 12 window so a second family can ship sooner if performance still holds.
• Do not award a duration that contradicts the factory letter in the file.
• Order immediately after NTP—submittals first if the spec requires approval, or a documented risk-release if the owner accepts the specified SKU.
• Dual-path installation: pull cable and hang boxes while cameras are in the queue, so the 26 weeks are manufacturing, not idle labor.

Worked warehouse: Camera 40’s specified multi-imager is 26 weeks. The risk register says so before award. The board hears “first picture in 26 weeks plus install” rather than “we awarded last week.” That sentence is the PM function. Hiding the lead time to keep the capital approval is how trust dies at the dock.

Panels have the same pattern: a controller that matches an existing card format may be a special-order. A “we will use whatever is in the van” substitution after award is a Chapter 12 ethics and performance failure, not agility.

Change control before award versus after award

Before award, a scope or specification change that affects price or competition is an addendum issued to every bidder (Chapter 12.1). That is still true if the change is “add long-lead language” or “slide the bid date because the factory just announced 26 weeks.” Hallway promises are not addenda.

After award, the baseline is frozen. The same extra cameras are a change order (or a task order under an MSA) with price, time, and license impact. They are not “already in the lump sum” unless the baseline said so. They are not an addendum; addenda die at bid opening.

PM enforces the split. Designers love to keep sketching. Operations loves to point at new corners. Procurement loves a clean file. The security PM is the person who says “that is a change; here is the form,” instead of letting a superintendent authorize six heads that blow the VMS channel count.

T&M and unit-price contracts still need change control. A unit-price door added after award is a quantity change against the schedule, not a free extra. T&M that exceeds the NTE is a change, not a courtesy.

Coordination with IT, facilities, and the AHJ

Procurement PM is a coordination job as much as a paper job.

IT: VLAN and firewall changes, directory integration, certificates, network time, storage arrays, cloud allow-lists, and who holds admin of the VMS. A purchase that assumes “plug into the nearest switch” will sit in a crate while the enterprise change-advisory board meets. Put IT milestones on the same register as cameras.

Facilities: ceilings, core drills, painting, locksmith cores, roof warranties, infection-control in clinics, dock blackout windows, and escort rules. The integrator cannot receive a panel into a closet facilities has not released.

AHJ: permits, inspections, delayed-egress listings, maglock release on fire alarm, and any local alarm-company license. Awarding without a permit path is a schedule lie. Consult the AHJ during design (Chapter 11) and keep them informed during procurement if the awarded product family affects a listing you already discussed.

The RACI names these people. The risk register dates their queues. Kickoff puts them in one room so the 26-week camera is not the only surprise.

Kickoff

A kickoff happens after award and before the owner believes work has started. It is not a celebratory lunch that replaces the contract. Agenda that actually protects the baseline:

1. Read-through of the scope baseline and order of precedence.
2. Lead times confirmed from current factory letters—not from the sales slide used in the interview.
3. Submittal and RFI calendars, including who approves substitutions now that the Chapter 12 window is closed.
4. Site access, badging, background-screening status for key holders (13.2), safety, and working hours.
5. IT and facilities tickets already opened—or opened that day.
6. Invoice and stored-materials rules from 13.1 so nobody bills 100 percent on a pallet.
7. Names from the RACI, including the single accountable owner PM.

If kickoff is the first time anyone asks “when does the camera ship?”, the PM function already failed. Kickoff confirms the register; it does not discover it.

How PM prevents the 26-week surprise

The surprise is a process failure, not a factory failure. Factories publish lead times. PM’s job is to surface them at the gates that can still change the decision:

1. Requisition / budget (13.1): if the board needs a picture next month, do not requisition a 26-week SKU without an OFE or equal path.
2. Solicitation (Chapter 12): require bidders to state lead times and to score schedule honesty.
3. Diligence (13.2): interview the project manager about their last late panel, not only the programmer about the interface.
4. Award: refuse a 30-day substantial-completion date that contradicts the file.
5. NTP and submittals: order or release fabrication the week you are allowed to, not the week someone remembers.
6. Kickoff: say the date out loud with IT, facilities, and the GC so the rest of the building does not assume cameras appear with the paint.

If the owner still chooses the 26-week camera for performance reasons (identification at a named plane that cheaper in-stock heads cannot meet), that is an accepted risk with a dated residual. The board should hear it. The schedule should show it. The invoice plan should not pretend the device is on the truck.

The diagram below is the PM overlay on the 13.1 gates. Chapter 14 starts when devices can actually be installed and tested—not when a notice of award is still waiting on a factory that nobody called.