全部
  • 全部
  • 产品管理
  • 新闻资讯
  • 介绍内容
  • 企业视频
  • 企业图册

CCTV Tender and Bid Guide: Writing Technical Specifications, BOQ, Compliance Matrix and Evaluation Responses for Surveillance Camera Projects


Target readers: system integrators, engineering contractors, vendor pre-sales engineers and bid managers responding to surveillance camera tenders in Europe and Africa, plus security owners, procurement managers and consultants who write the tender documents. Typical projects cover public infrastructure, industrial parks, mining, oil and gas, hotels and retail chains. Core takeaway: surveillance projects are rarely won by the best product alone. They are won by a technical bid that an evaluator can verify line by line. This guide links the URS, technical specification, BOQ, evaluation criteria, compliance matrix, TCO model and FAT/SAT acceptance tests into one reusable bidding workflow: turn vague descriptions into measurable parameters, parameters into clause by clause responses, responses into traceable evidence, and promises into acceptance tests.

TL;DR

  • Tender documents are layered: URS, technical specification, BOQ, evaluation criteria, contract and SLA. Read the scoring method first, then work backwards so effort lands on clauses that actually earn points.
  • Terms such as high definition or clear at night are not verifiable. Convert them into 4MP at 25fps, 0.005 lux, WDR 120 dB or better, IP66 and IK10, H.265, ONVIF Profile S/G/T, and state recognition distance using DORI per EN 62676-4.
  • One unmet Mandatory clause usually means disqualification. The compliance matrix must give Comply, Partially Comply or Non-Comply for every clause and point to a page or certificate number, with no blanks and no hidden negative deviations.
  • BOQ omissions are the most common profit leak. Beyond cameras, include switches and optics, PoE power, poles and foundations, cabinets, cabling and consumables, software licences, installation and commissioning, training, spares and warranty period maintenance.
  • Evaluation is moving from unit price to total cost of ownership. Quantify five year power, disk replacement, licence renewal, on site service and downtime, then show the advantage in one comparison table.
  • The clarification window is the only legitimate chance to correct a biased specification. Ask in writing about exclusionary parameters, single brand references and impossible parameter combinations, and keep the official reply.
  • Winning is not the finish line. Map every bid promise into FAT and SAT test cases with hard acceptance thresholds: online rate 99 percent or better, recording integrity 98 percent or better, analytics accuracy 90 percent or better, and a defined fault response SLA.

Why the Tender Process Decides a Surveillance Project

Surveillance cameras in B2B markets are rarely purchased from a demo. European public bodies and large enterprises use ITT, RFP and framework agreement procedures; large African projects are often funded by the World Bank, the African Development Bank or sovereign funds and require open tendering with eligibility screening. Technical and commercial bids are scored separately, Mandatory clauses act as pass or fail gates, and lowest price awards remain common. A better product does not mean a better bid, because the evaluator only sees what is written down and verifiable.Start with the buying path: 

Tender component

Purpose

Frequent failure point

Eligibility requirements

Qualifications, track record, finance, authorisation chain

Missing manufacturer authorisation, unstamped reference letters, wrong local entity

User requirement specification URS

Business goals and scenario description

Copying the URS as a technical response instead of converting it into measurable parameters

Technical specification

Clause by clause device and system metrics

Writing only compliant, with no model number or datasheet page

BOQ bill of quantities

Pricing and quantity baseline

Omitting consumables and software licences, then absorbing the cost after award

Evaluation criteria

Technical, price and service weights and scoring points

Ignoring weights, so high value clauses get too little coverage

Contract and SLA

Warranty, response, penalties, acceptance

Promising a four hour on site response that cannot be delivered

  • Market differences: European tenders usually require CE, the EN 62676 series, EN 303 645 or IEC 62443 cybersecurity, GDPR readiness and an NDAA supply chain statement. African funded projects often add a local agent, spare parts stock, a training plan and foreign exchange or tax clauses.
  • Timeline: notice, clarification deadline, official replies, bid submission, technical evaluation, clarification defence, commercial opening, award. The clarification window is often only 7 to 14 days, and missing it removes the only chance to challenge a biased clause.

Tip: 

On day one build a one page disqualification risk list covering every Mandatory clause, stamped document, bid bond, format requirement and submission deadline. A technically excellent bid with one missing authorisation letter scores zero.

Reading the Tender: From URS to Evaluation Criteria

Start with the evaluation criteria to see which clauses score points and how much, then read the technical specification for pass or fail gates, and only then return to the URS for business intent. The URS line about recognising faces at the entrance is a goal, the specification line about 4MP and 2.8 mm is a means, and the scoring line about recognition distance and low light performance worth 8 points is where the effort belongs.Read it backwards: 

Layer

Question it answers

Bid action

URS user requirements

Why the system is built and which risk it addresses

Write a solution overview showing business alignment

Technical specification

Which metrics and quantities are required

Build a clause by clause response matrix with evidence references

BOQ

What is priced and in which unit

Reconcile quantities with the camera schedule and add hidden items

Evaluation criteria

How points are awarded and weighted

Sequence chapters and page count by scoring points

Contract and SLA

How the delivery is accepted and enforced

Convert promises into measurable acceptance items

Clarification replies

How ambiguity is officially interpreted

Attach and cite them, since they override the original text

  • Clause classes: Mandatory, Desirable and Optional. Mandatory clauses are usually written with shall or must, and any negative deviation disqualifies; Desirable clauses separate the technical scores.
  • Spotting bias: if only one brand can satisfy a parameter combination, raise it during clarification by citing an equivalent standard such as ONVIF or EN 62676-4 and request that equivalent solutions be accepted.
  • Evidence chain: number every model, datasheet version, test report, certificate validity date and reference contract page, then cite only the index in the compliance matrix.

Practical threshold: 

Give every scored clause at least one verifiable proof item, such as a datasheet page, third party report or measured screenshot. Submit clarification questions at least 48 hours before the deadline to avoid last day channel congestion.

Writing the Technical Specification: Measurable, Repeatable, Acceptable

A clause is useful only if a datasheet, third party report or field test can prove it true or false. High definition cannot be accepted or rejected; 4MP or better at 25fps with H.265 Main Profile, minimum illumination 0.005 lux in colour at F1.2 with AGC on, and WDR 120 dB or better can each be verified during factory acceptance testing. For anything described as clear enough to see, use the DORI levels of EN 62676-4, which are Detect, Observe, Recognise and Identify, and tie pixel density to the scene width.Every parameter must be testable: 

Vague wording

Verifiable wording

Verification method

High definition camera

4MP or better (2560x1440) at 25fps, H.265, main stream 6 Mbps or less

Datasheet plus stream capture

Clear at night

0.005 lux colour and 0.0005 lux monochrome, IR 30 m, WDR 120 dB or better

Dark chamber illumination test plus backlit scene

Can recognise a face

Identify density 250 px/m or better, recognition distance 8 m or more per EN 62676-4

On site measured frame with a scale bar

Suitable for outdoor use

IP66 and IK10, minus 30 to plus 60 C, 6 kV surge, 96 h salt spray

Ingress certificate plus environmental report

Good compatibility

ONVIF Profile S/G/T, RTSP, third party VMS integration proven

ONVIF test tool plus third party platform test

Smart analytics

Person and vehicle classification accuracy 90 percent or better, 5 false alarms per channel per day or fewer, edge NPU

Seven day sample unit statistics

pixel_density_px_per_m = sensor_horizontal_pixels / scene_horizontal_width_m

identify_distance_m = sensor_horizontal_pixels / 250    # EN 62676-4 Identify level

storage_TB = bitrate_Mbps x channels x 3600 x hours_per_day x retention_days / 8 / 1000000

example: 6 Mbps x 64 ch x 24 h x 30 d = 99.5 TB raw; with 1.2 factor for RAID and formatting specify 120 TB

  • Do not over specify: write minimum values with greater than or equal to instead of exact equality, which leaves room for equivalent solutions and avoids locking the bid to one model.
  • List system level metrics separately: end to end latency 300 ms or less, concurrent playback channels, platform user count and RBAC roles, log retention 180 days or more, and network outage buffering with post event upload.
  • Fold compliance into the specification: CE, RoHS and REACH, EN 303 645 or IEC 62443, GDPR readiness with privacy masks and audio off by default, ATEX or IECEx for hazardous areas, and an NDAA supply chain statement.

Common mistake: 

Specifying only device parameters and forgetting system parameters. When the evaluator asks whether 64 channels can play back simultaneously or whether two hours of network loss loses footage, the answer must already exist as a measurable clause, or the system completeness score drops.

Building the BOQ in Four Steps

Step one fixes front end quantities and mounting from the camera schedule. Step two completes transmission, power and back end from the topology. Step three adds software licences, services and spares. Step four reconciles every line of the client BOQ and records differences in a deviation note instead of silently deleting anything. Any silent deletion can be treated as a non responsive bid.The BOQ is the baseline for both price and margin: 

Category

Typical line items

Quantity source and unit

Front end devices

IPC bullet, dome and PTZ, explosion proof, cellular units, lenses, brackets, housings

Camera schedule, pieces or sets

Transmission

Access and aggregation switches, PoE switches, optical modules, fibre, wireless bridges, 4G/5G SIM and data plans

Topology drawing, pieces, km, SIMs, months

Power and civil works

UPS, solar kits, poles and foundations, cabinets, surge and grounding, cables and trays

Site survey, sets, metres, items

Back end and storage

NVR or server, enterprise disks, RAID, decoders, video wall, backup NAS

Channel count and retention formula, units, disks, TB

Platform software

VMS base package, channel licences, AI algorithm licences, mobile client, SDK integration

Channel count and concurrency, sets, channels, years

Installation and services

Cabling, mounting, commissioning, system integration, project management, training, as built drawings

Points and schedule, points, person days, items

Spares and maintenance

5 to 10 percent spare units, spare disks, warranty inspections, SLA response, annual maintenance

Device count times factor, units, years

  1. Fix quantities from the stamped camera schedule and check model, mounting height, power method and whether explosion proof or solar supply is needed at each point.
  2. Complete the chain by walking from each camera to the NVR, so every port, fibre run and power source has an owner.
  3. Size storage with the formula in section three, then add RAID and formatting overhead so capacity is not 20 percent short at acceptance.
  4. When the client BOQ lacks items, quote them separately as recommended additions with a rationale, which preserves responsiveness and avoids absorbing cost after award.

Experience value: 

Consumables, installation and services typically represent 25 to 40 percent of project value. Spares run at 5 to 10 percent of device count. Software licences and annual maintenance are the two most frequently omitted lines and the two most often questioned during evaluation.

The Compliance Matrix: Where Bids Are Won

Split every clause of the technical specification into one row with the clause number, the requirement, the actual response value, the compliance judgement, the model and the evidence page. Use only three judgements: Comply, Partially Comply and Non-Comply. A Non-Comply on a Mandatory clause normally disqualifies. A Partially Comply must state the gap and the compensating measure, and must never be hidden behind the word compliant.This is the only document the evaluator reads line by line: 

Clause

Requirement

Response value

Judgement

Evidence index

TS-3.2.1

Resolution 4MP or better

2560x1440 at 25fps, model X4

C

DS-X4 p.3, report R-221

TS-3.2.5

Minimum illumination 0.005 lux or lower

0.005 lux colour, 0.0005 lux monochrome

C

DS-X4 p.5

TS-3.4.2

IP66 and IK10

IP66 and IK10, 96 h salt spray

C

Certificates C-118 and C-119

TS-4.1.7

Third party VMS support

ONVIF Profile S/G/T plus RTSP, tested with two platforms

C

ONVIF report O-087

TS-6.3.1

Local spare parts warehouse

Regional hub with 48 hour dispatch, no permanent local stock

PC

Service plan S-12, letter of commitment

  • Respond with values, not with the word yes. Each compliant must be followed by a number and a model, otherwise the evaluator has nothing to verify and often awards no points.
  • Manage negative deviations openly: for a genuine gap, offer an equivalent solution, compensating measures and a risk statement, and confirm the clause is not Mandatory. A concealed Non-Comply is far more damaging than a declared one.
  • Make evidence traceable: each datasheet, certificate and report carries an index and a page number, and the matrix matches the annex index so a reviewer can check everything within two hours.
  • Use an alternative bid where allowed: attach a better performance or lower TCO option, but keep the main bid fully responsive so it is not ruled non compliant.

Reminder: 

Clause numbers in the matrix must match the tender document exactly. Never renumber or merge clauses. Merged responses are a leading cause of disqualification because the evaluator cannot confirm that a clause was answered.

Decoding the Scoring Method and Bid Strategy

A typical open tender uses 60 percent technical, 30 percent price and 10 percent service and track record, while government or funded projects may use 70 percent technical and 30 percent price. List every scoring point first, then decide how many pages go to the technical solution, drawings, references and test reports. Price points are not won by cutting the unit price but by proving with TCO evidence that the higher priced option costs less overall.Allocate page count by weight: 

Scoring dimension

Typical weight

What earns points

Technical parameter response

25 to 35 percent

Clause level response values, third party reports, DORI and low light measurements

System architecture and completeness

15 to 20 percent

Topology, bandwidth and storage calculation, redundancy, outage buffering, cybersecurity

Implementation and project management

10 to 15 percent

Phased cutover, Gantt chart, no shutdown migration, risk management

Service and SLA

8 to 12 percent

Local service presence, spares, response times, training plan

Track record and qualifications

5 to 10 percent

Comparable scale references, acceptance certificates, CE and ISO, manufacturer authorisation

Price including TCO

20 to 40 percent

Five year total cost, energy, disk replacement, licence renewal

  • TCO model: five year TCO equals hardware plus installation plus licence times five plus power times five plus disk replacement plus maintenance times five plus a downtime estimate.
  • Price score formula: lowest responsive bid divided by our bid, multiplied by the price weight. An 8 percent higher bid with a 14 percent lower five year TCO should be shown in a comparison table in the commercial volume, not only described in the technical volume.
  • Ask during clarification about exclusionary parameters, single brand references, contradictory metrics and certificates that cannot be obtained within the schedule. Every question needs a written reply that can be cited later.
  • If a factory acceptance test or sample demonstration is part of the process, prepare scripts tied to scoring points: backlight, night scene, recognition distance, false alarm rate and outage recovery, each with time stamped screenshots.
  • Bundle compliance into a standalone chapter: GDPR readiness, EN 303 645, ATEX for hazardous areas and an NDAA statement are often hidden scoring points or gates in European and funded projects.

Strategy thresholds: 

Target 100 percent coverage of technical scoring points with at least one verifiable proof item each. Submit 100 percent of clarification questions before the deadline and keep every official reply. The commercial volume must include a five year TCO comparison table.

Submission Checklist and FAT / SAT Acceptance Thresholds

Check every item before submission:

  1. Eligibility documents: business registration, manufacturer authorisation, reference projects, financial and tax records, bid bond, authorised signatures and format compliance.
  2. Technical volume: solution overview, system topology, camera schedule, clause by clause compliance matrix, datasheets and certificates, calculation sheets for bandwidth, storage, power and DORI.
  3. Commercial volume: priced BOQ, unit rates, five year TCO comparison, delivery schedule, payment and warranty terms, deviation statement.
  4. Implementation volume: project organisation, schedule, phased cutover and no shutdown plan, risk management, training and document list.
  5. Service volume: SLA response times, spare parts list, local service capability, warranty and annual maintenance pricing.
  6. Compliance annex: CE and RoHS, EN 62676, EN 303 645 or IEC 62443, GDPR readiness statement, ATEX or IECEx where applicable, NDAA declaration.
  7. Attach all clarification replies and addenda, and confirm the latest tender template version is used.

Convert bid promises into measurable acceptance items:

  • System online rate 99 percent or better over 30 days, with single point failure alarm within 60 seconds.
  • Recording integrity 98 percent or better, full backfill after a two hour network outage, no timeline gaps in a SAT sample of 7 days by 10 channels.
  • Analytics accuracy 90 percent or better for recognition use cases, with 5 false alarms per channel per day or fewer over a seven day sample test.
  • DORI compliance at critical scenes: measured frames at the stated distance per EN 62676-4, Identify density 250 px/m or better.
  • End to end latency 300 ms or less, 64 channel concurrent playback without dropped frames, NTP synchronised across all devices, log retention 180 days or more.
  • Grounding resistance 4 ohm or less, with hazardous areas following ATEX requirements; PoE port power headroom 20 percent or more.
  • Complete documentation: as built drawings, camera schedule, configuration backup, administrator handover, training attendance and FAT/SAT reports signed by both parties.

A technical bid is not a one off document; it is the master for the contract, the implementation and the acceptance test. Number every promise and map it to a test case, an owner and an evidence file, then reuse it directly as the acceptance checklist after award. After each tender, feed the scoring result and the lost points back into a parameter library, an evidence library and a compliance matrix template, and the marginal cost of the next bid drops noticeably.Wrap up: 

FAQ

Q: Can the compliance matrix simply say fully compliant?

A: It is not recommended. The evaluator needs verifiable values and evidence indexes. A bare fully compliant is usually treated as insufficient information and rarely earns full points on a scored clause. Give the response value, model, datasheet page and judgement for each clause.

Q: What if the tender is clearly written around one brand?

A: Raise it in writing during the clarification window. Cite equivalent standards such as ONVIF, EN 62676-4 and IEC 62443 to show that several vendors can meet the requirement, and request that equivalent solutions be accepted or that the exclusionary wording be removed. Verbal discussions leave no evidence, so obtain a written reply and attach it.

Q: One Mandatory clause cannot be met. Should we still bid?

A: Under most evaluation rules it means disqualification. Two options remain: request equivalence recognition during clarification, or keep the main bid fully responsive while submitting an alternative offer. Never conceal a negative deviation in the main bid, since discovery is usually treated as a material non response and can affect future eligibility.

Q: The client BOQ omits software licences and consumables. Should we add them?

A: Do not silently edit the client BOQ. Respond to every line as issued, then attach a separate recommended additions list with pricing and rationale. That preserves responsiveness and puts the cost and risk on record instead of absorbing them after award.

Q: How different are qualification requirements in Europe and Africa?

A: European tenders emphasise CE, EN 62676, EN 303 645 or IEC 62443, GDPR and NDAA supply chain statements. African funded projects often add a local agent or registered entity, spare parts stock, a training plan and World Bank or AfDB eligibility and anti corruption clauses. In both cases make compliance a standalone chapter.

Q: Must we be the lowest bidder to win the price score?

A: Not necessarily. A common formula is lowest responsive bid divided by our bid multiplied by the price weight, but the technical gate must be passed first. A five year TCO comparison quantifying power, disk replacement, licence renewal and maintenance, combined with a technical score advantage, is more durable than simply cutting price.

Q: What if we cannot deliver a parameter promised in the bid after award?

A: Map every promise to a FAT and SAT test case with a measurable threshold before submission, and confirm that the supply chain and schedule can deliver it. Over promising leads to failed acceptance, penalties and a damaged performance record. A declared Partially Comply with compensating measures and clear boundaries is better than an unverifiable number.

Prev:

Related News

CCTV Tender and Bid Guide: Writing Technical Specifications, BOQ, Compliance Matrix and Evaluation Responses for Surveillance Camera Projects

Target readers: system integrators, engineering contractors, vendor pre-sales engineers and bid managers responding to surveillance camera tenders in Europe and Africa, plus security owners, procurement managers and consultants who write the tender documents. Typical projects cover public infrastructure, industrial parks, mining, oil and gas, hotels and retail chains. Core takeaway: surveillance projects are rarely won by the best product alone. They are won by a technical bid that an evaluator can verify line by line. This guide links the URS, technical specification, BOQ, evaluation criteria, compliance matrix, TCO model and FAT/SAT acceptance tests into one reusable bidding workflow: turn vague descriptions into measurable parameters, parameters into clause by clause responses, responses into traceable evidence, and promises into acceptance tests.

Nov 15,2026

GDPR Compliant Surveillance Camera Guide: Video Surveillance Data Protection and Technical Deployment in Europe and Africa

Target readers: security owners, data protection officers (DPO), system integrators, and procurement managers deploying surveillance cameras across European and African sites, retail chains, hotels, warehouses, and industrial parks. Core takeaway: video footage showing identifiable people is personal data. Under GDPR a camera project is not just an engineering job but a compliance one. This guide maps legal basis, DPIA, data minimisation, retention, access control, subject rights, and vendor acceptance onto concrete camera and NVR settings, giving one reusable delivery framework.

Nov 15,2026

Explosion Proof Surveillance Camera Guide: Selection and Installation for Gas Stations, Oil Depots, Chemical Plants, Mining

Target readers: security owners, system integrators, and EHS engineers for petrochemical, oil and gas, pharmaceutical, powder processing, and coal mining sites where explosive gas or combustible dust exists. Core takeaway: a normal camera is itself an ignition source in flammable environments. You must use explosion proof cameras certified to ATEX, IECEx, or China Ex, selected by hazard zone, installed with proper grounding, and documented for compliance. This guide gives a reusable selection, install, and acceptance workflow.

Nov 08,2026

4G 5G Cellular Surveillance Camera Guide: Remote Video without Broadband

Target readers: security owners and integrators for farms, orchards, fisheries, construction, oil and mining sites, vehicle fleets, and remote African villages where broadband is scarce. Core takeaway: when there is no fiber, no broadband, and frequent power loss, a SIM card cellular camera is the easiest and most scalable remote video option. This guide gives a reusable architecture covering power, data, backhaul, AI, and compliant deployment.

Nov 08,2026

Analog CCTV Upgrade Guide: Coax HD Reuse vs Full IP Rebuild, Cost and Timeline Compared

Factory, campus and retail chains running analog surveillance for five or six years face the same wall: blurry images, unretrievable footage, and no path to AI analytics on legacy hardware. This guide breaks down pre-upgrade system inventory, compares the coax-HD reuse route against a full IP rebuild, gives bandwidth and storage recalculation formulas, and lays out a zoned, non-disruptive cutover plan with a selection checklist.

Oct 31,2026