Integrator evaluation should connect proposed capability to documented evidence, delivery responsibility, and support commitments. Compare each proposal against the same enterprise requirements before choosing a preferred supplier.
Part of Enterprise Security Procurement and Bid Evaluation.
Set the evaluation criteria before scoring
Agree on evaluation criteria before reviewing bids. Include the required workflows, relevant project experience, delivery plan, training, documentation, and support commitments. Decide which requirements are mandatory and which can be scored. If weights are used, record them in advance so a low price cannot quietly outweigh a missing essential function.
Compare evidence and unresolved gaps
Ask each bidder to demonstrate the same representative workflow and identify who will deliver and support it. Keep the evidence beside the score: product documentation, a demonstrated result, a relevant reference, or a stated exclusion. Separate verified answers from claims still awaiting confirmation. Give unresolved items an owner and a deadline before selection.
Record the selection and acceptance conditions
Have the responsible stakeholders review the completed matrix and explain material differences between proposals. Record the reasons for selection, remaining conditions, and any follow-up demonstration required. Carry the agreed deliverables and acceptance tests into the final scope. The evaluation record should explain the choice to someone who did not attend the presentations.
Example: compare two proposals on the same basis
This hypothetical scorecard uses invented Proposal A and Proposal B ratings to illustrate the calculation. It does not rate NERSA or another supplier. First confirm that each bid meets mandatory requirements; an unresolved mandatory exclusion should not be hidden by a strong overall score.
For eligible bids, agree the weights before scoring. Use a 0–5 scale: 0 means no adequate response, 3 meets the agreed requirement, and 5 provides documented additional value relevant to the project. Keep the evidence and the reason for each rating beside your working scorecard.
| Criterion | Weight | A rating | B rating |
|---|---|---|---|
| Scope and demonstrated required workflows | 30% | 4 | 3 |
| Delivery, testing and handover plan | 25% | 3 | 4 |
| Support responsibilities and commitments | 20% | 4 | 3 |
| Comparable lifecycle cost | 15% | 3 | 5 |
| Relevant experience and verified references | 10% | 4 | 3 |
| Weighted total out of 100 | 100% | 73 | 71 |
Calculate each contribution as rating divided by 5, multiplied by the criterion weight. For example, A earns 24 points for scope: 4 ÷ 5 × 30. The two-point total difference is a prompt to review the underlying evidence, not an automatic award decision.
Compare costs over the same period and scope, including installation, licenses, subscriptions, maintenance, training and stated exclusions. Ask both bidders to clarify unresolved items through the same procurement process. Record the selection rationale and carry the accepted scope, responsibilities and tests into the contract.
Related planning resources
- NERSA Platform and Manufacturer Experience
- Security Proposal and Scope Development Standards
- Commercial Security Service and Support Standards
Frequently Asked Questions
Should the lowest enterprise security bid be selected automatically?
Compare bids against the same requirements before choosing a supplier. Evaluate supported functions, evidence, delivery responsibility, ownership, ongoing costs, and unresolved gaps alongside price. Different totals can represent different commitments.
When should integrator scoring criteria be agreed?
Set criteria before scoring proposals so each bidder is evaluated on the same basis. Record the selection rationale and acceptance conditions. This connects the procurement decision to demonstrable capability and support commitments.
Let’s talk about your next step
Tell us what you want to improve and which locations are involved. We can help you work through the questions, check what your systems support, and define a practical project scope.
Compliance, Codes & Project Standards
NERSA plans commercial and industrial security work with applicable code, documentation, inspection and authority-having-jurisdiction requirements in mind. Requirements vary by system, property and jurisdiction. These resources support project planning; they do not establish legal compliance, certification or AHJ approval.
Related guidance: Regulatory compliance & inspection readiness · NERSA project standards · Documentation, testing & inspection readiness