For a distributor or integrator, a lower quoted device cost can be offset by door preparation, unclear wiring scope, repeat site visits, unavailable spares or an unresolved platform dependency. TCO turns those risks into review items before the quotation becomes a commitment.
What belongs in video intercom TCO?
| Cost area | What to compare | Evidence to request |
|---|---|---|
| Supply scope | Door stations, monitors, power, release hardware, accessories, firmware and licenses. | Itemized bill of materials and exclusions. |
| Installation | Cable route, mounting, door release interface, network work and site access. | Wiring diagram, mounting dimensions and field assumptions. |
| Commissioning | Device provisioning, calling route, release operation, user setup and acceptance test. | Named workflow and commissioning checklist. |
| After-sales | Diagnostic ownership, firmware path, RMA process, spares and response route. | Written support scope for the selected model. |
| Lifecycle | Subscription, server or cloud responsibility, change control and future replacement path. | Current terms, account owner and documented fallback. |
Start with the installed system, not the catalogue
Two door stations with similar specifications can lead to different operating cost because their complete systems differ. The comparison should name the power method, lock interface, indoor or mobile answer route, network owner and maintenance owner. Without that boundary, “includes app” or “supports SIP” does not show what work remains on site.
Where projects usually absorb avoidable cost
Unresolved retrofit assumptions
Existing cable does not automatically establish a viable reuse route. Verify conductor condition, distance, topology, power and the devices that must stay in service. A sample test can be less costly than discovering a cable or release limitation after equipment arrives.
Interfaces described only by protocol names
SIP, ONVIF and API references should be translated into an acceptance action: call routing, video display, door release, event delivery or account administration. Then identify the client system, firmware and party responsible for the test.
Support transferred without records
A support team cannot isolate a fault without the model, hardware and firmware revision, site topology, observed symptom and basic field evidence. Define that intake record before rollout, along with who approves parts, replacement and commercial disposition.
How to use the framework in a quotation review
- Normalize all quotations to one itemized hardware and service scope.
- List every assumption that changes installation labor or accessories.
- Assign each support activity to the distributor, installer, operator or manufacturer.
- Run a representative sample and record pass criteria before volume release.
- Set a spare-parts and replacement route for the installed configuration.
This does not create a universal cost figure. It produces a defensible comparison and shows which assumptions must be closed before a commercial decision.