12.4 Evaluation Criteria, Technical Compliance & Contracting Ethics

Evaluation Criteria, Technical Compliance, and Contracting Ethics

Independent OpenExamPrep teaching for published PSP Domain 3 Task 1 knowledge is that award is a documented decision, not a vibe. You publish evaluation criteria, you score technical compliance, and you keep ethics in the file: gifts, bid-rigging, incumbency bias, hidden OEM specifications, and the conflict when the designer also bids. Public and private procurement use different statutes; both still punish a crooked process. Sections 12.1 through 12.3 built a fair package. This section decides a winner without lighting a protest or a kickback.

Exam focus: Cost is one RFP criterion, not the only one. Matrices catch exceptions. Ethics failures void trust and often void awards. Private owners are not “anything goes.”

Evaluation criteria you will actually use

Typical published factors:

• Cost / price. Lowest among responsive, responsible bidders on a true IFB. Weighted on an RFP. Software subscriptions, spare parts, and monitoring can sit in the cost model if you said so up front. Changing the cost formula after envelopes are open is how protests are won.
• Experience. Similar occupancy, similar systems, similar live cutovers—not “we do electrical” and not a warehouse resume offered as hospital-pharmacy proof.
• Scheduling. Realistic phasing, factory lead times, and staff loading. A thirty-day campus promise with sixteen-week hardware lead times is a fiction. Score the schedule against the constraints the walk and the SOW already disclosed.
• Certification. Manufacturer-certified technicians, company-level factory authorization, and any required low-voltage or alarm licenses. A cheap bid that cannot obtain the factory credential will fail commissioning and may void a listing. Ask for certificates, not a marketing sentence.
• Resources and bonding. Crew depth, supervision ratio, local warehouse, and bid, performance, and payment bonds at the stated capacity. Bonding is not a personality test. It is evidence a surety will stand behind the work. A firm that cannot bond a hospital pharmacy ACS is not “agile.” It is under-resourced.

Weight the criteria before you see prices. An evaluation committee and a procurement officer with separate jobs help: technical people score compliance and method; procurement guards the process. Do not let a single enthusiast own both the spec and the score sheet without review.

On IFB work, resist the urge to invent extra “best value” after you dislike the low number. If you needed best value, you needed an RFP. The ethical repair is to reject non-responsive bids or to cancel and re-solicit with a legal justification—not to reweight in the hallway.

Technical compliance matrices

A compliance matrix is a table: each shall-statement, drawing note, and specification paragraph versus complies / does not comply / complies with exception. Exceptions must describe the alternative. This is how you catch a bidder who priced detection-grade cameras where identification was specified, or who took exception to as-builts, weekend pharmacy work, and the HR feed.

IFB culture sometimes pretends matrices are unnecessary because “the spec is the spec.” In security, exceptions still arrive as cover letters and footnotes. Read them. A low bid that excepts training, spare parts, and after-hours cutover is not low. It is a different job. Treat material exceptions as non-responsive when the IFB forbade them, or as scored deficiencies when the RFP allowed alternatives.

Use the matrix in evaluation meetings. Do not score “nice brochure” or a live demo in a dark conference room as technical compliance. A demo is not a field test of Door 4. Manufacturer letters that say the bidder is “authorized” belong next to the matrix, not in a leftover email.

Worked matrix row: “Camera 12 shall support identification at the badge-desk plane.” Firm A complies and names a lens and lighting assumption. Firm B complies with exception: “parking-lot camera reused for the desk.” That exception is a Domain 2 performance miss. It should lose technical score on an RFP and may be a reject on an IFB that forbade substitutions after the 12.1 window closed.

Ethics in contracting

Gifts. A meal, tickets, or a “factory tour” that is really a resort during the solicitation freeze is a conflict. Many public owners forbid any gift from a bidder. Private codes vary; the professional standard is still do not let a personal benefit steer an award. If a sample camera must be tested, log it as owner property or return it. Do not take it home.

Bid-rigging. Competitors agree who will win, who will submit a complementary high bid, or who will stay home. That is a crime in many jurisdictions, not a networking tactic. Rotating public security winners among friends is a classic pattern. Oddly similar high bids, identical exceptions, and a market where nobody new ever wins are warning signs. Independent estimates help you see a rigged number.

Incumbency bias. The current integrator has keys, passwords, and tribal knowledge. That can be a legitimate transition-cost factor if you published it as a scored task (password turnover, shadowing, dual operation for two weeks). It is not legitimate to ignore a better technical score because “they already know the panel.” Write transition so incumbents compete on a fair extra, not on a secret veto. Taking extra site photos only the incumbent is allowed to take is a 12.1 fairness failure as well as an ethics failure.

Designing a spec around one OEM without disclosure. Naming a camera family with unique mounts, unique analytics licenses, and unique reader protocols, then pretending the spec is open, steers the bid. If the owner truly needs that OEM for compatibility, say so and use sole-source or a disclosed proprietary specification. If the owner wants competition, write performance shall-language (identification at a plane, supervised encrypted reader traffic, listed delayed egress) and allow or-equals in the 12.1 window. Copying a single cut sheet into Division 28 and calling it performance is the usual tell.

Designer also bids. The firm that wrote Division 28 has information and influence no competitor has. Many public owners forbid that firm from bidding the install, or require a firewall, disclosure, and an independent reviewer. Even in private work, the conflict is obvious: the designer can write a spec only they can meet, then win the install. Recuse, disclose, or split design and build. “We know the drawings best” is not an ethics defense. It is the conflict statement.

A communications blackout (sometimes called a cone of silence) during evaluation stops bidders from lobbying individual committee members. All questions go to the named procurement contact. That rule is process and ethics together.

Public versus private procurement (high level)

Public owners (cities, school districts, many authorities) live under statutes: advertising periods, sealed bids or published RFP rules, bid-opening rituals, protest periods, open-records exposure, and strict gift rules. IFB lowest responsive responsible is common for construction-like work. RFP is available where the statute allows best value. Sole source needs a record. Violations create protests and sometimes voided contracts. A protest is not an insult. It is the system checking the file.

Private owners (many corporations, some hospitals and universities depending on funding) can often negotiate, down-select, and even sole-source under board policy instead of a procurement statute. They still have internal audit, lender, insurer, and fiduciary expectations. Ethics problems—kickbacks, rigged specs, undisclosed conflicts—remain firing offenses and civil claims. Do not tell an exam stem that private means “anything goes.” A private RFP can keep prices confidential; it should not keep a gift quiet.

Federal, state, and local rules differ in detail. PSP-style items ask for the idea: more formality and protest rights on the public side; more negotiation flexibility on the private side; the same expectation that the people who score bids are not for sale.

Award the firm that met the published criteria and the matrix. Document why, including why a lower price lost on an RFP. Then Domain 3 can install what was actually bought, instead of litigating what the hallway meant.