The short answer
Most facilities have five realistic options: keep a supported component, repair a bounded fault, integrate usable equipment, phase out a system through a controlled migration, or replace equipment that can't meet the requirement.
A useful assessment explains the evidence for each recommendation, the assumptions still open, and how the finished work will be tested.
Compare the five options
Each option has a different evidence burden and a different way it can fail. Use this comparison as a starting point for a site-specific decision record.
| Option | Best fit | Evidence to require | Common risk |
|---|---|---|---|
| Keep | Meets the requirement and remains supportable | Condition, compatibility, support status, test result, owner | Keeping it without testing dependencies |
| Repair | A specific fault can be corrected | Root cause, repair scope, support availability, retest criteria | Treating symptoms instead of the cause |
| Integrate | Usable equipment can connect to a supported architecture | Interfaces, ownership, compatibility, licensing, support boundary | Creating a mix nobody supports end to end |
| Phase out | A single cutover creates avoidable operational risk | Milestones, coexistence plan, acceptance gates, retirement date | Letting temporary equipment remain indefinitely |
| Replace | The system can't reliably or supportably meet the requirement | Limitation evidence, lifecycle analysis, requirements, acceptance tests | Buying equipment without solving the operating problem |
Start with the business requirement
Define what the facility needs the system to do before comparing products.
Retrieve useful video within an approved process
Administer employee, visitor, contractor, and delivery access
Coordinate doors, gates, alarms, camera views, and infrastructure
Preserve operations during a cutover
Provide auditable configuration, training, and handoff records
When keeping or repairing can be reasonable
Keeping or repairing can fit when the component meets the approved requirement, remains supportable, has known ownership, and can be tested under real operating conditions.
Document exactly what was tested, under what conditions, and what passed.
Identify who holds vendor support, software accounts, and recovery methods.
Retest the corrected fault under real operating conditions before closing it.
Record every remaining unknown and dependency in the decision record.
When integration can preserve useful equipment
Integration can reduce unnecessary replacement when interfaces are documented and responsibility remains clear. A working connection is not automatically a supported integration.
Which functions are officially supported?
Who owns accounts and recovery methods?
What happens when software or licensing changes?
How will the integrated workflow be tested?
When a phased migration is safer
Phasing may fit facilities that can't tolerate one cutover or need to align work with operations, construction, IT changes, budgets, or procurement.
Define the order of work and the milestone that completes each stage.
Plan how legacy and new systems coexist while both are running.
State the temporary functional limits the facility accepts during migration.
Set acceptance gates that must pass before the next stage begins.
Commit to a final retirement date so temporary equipment doesn't become permanent.
When replacement becomes the stronger choice
Replacement may be justified when evidence shows the current system can't reliably or supportably meet the approved requirement. Age alone is not enough.
Vendor support, software updates, or compatible clients are no longer available.
The system fails testing under the conditions the facility actually requires.
Critical accounts or recovery methods are unowned or unrecoverable.
Capacity or compatibility limits block the approved requirement.
Faults recur beyond the scope of any bounded, testable repair.
Compare lifecycle, not only equipment price
Compare equipment, software, subscriptions, infrastructure, migration, training, support, documentation, exclusions, and acceptance testing.
Questions to ask every assessor or bidder
Keep exact facility details in a controlled project record.
What verified requirement does each change solve?
What evidence supports each decision path?
Who accepts reuse and support responsibility?
How will continuity be protected?
How will completion be tested?
What is specifically excluded?
Monitoring and response boundary
Optional monitoring-ready or live-video support may be available through a UL-listed central-station relationship. That is not a universal promise of monitoring, 24/7 response, emergency response, or a particular response time. The written scope must identify the parties, services, schedules, contacts, escalation procedures, and expectations actually included.
Protect sensitive facility information
Keep passwords, codes, exact camera positions, blind spots, door schedules, response procedures, floor plans, public IP addresses, retention settings, and known vulnerabilities in a controlled project record, not a public form or page.
Next step
Request a commercial security assessment to review system ownership, support, compatibility and the operating requirements that need verification.