Commercial security product guide

Nextivity CEL-FI QUATRA EVO and 4000

Nextivity positions CEL-FI QUATRA EVO for supported one- or two-operator solutions and QUATRA 4000/4000i for larger operator-count architectures. These active DAS hybrid systems use network and coverage units with structured cabling and RF distribution, but the exact model, bands, donor source and carrier approvals govern the system engineering.

KSEDCO supplies, installs, configures, maintains, repairs, and supports these systems across Georgia. Discuss a site or service request

Judge the whole system rather than a single feature

Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the system engineering.

Operator architectureOne, two, three or four supported operator paths selected from user and carrier requirements.
Signal sourceOver-the-air donor or other supported source confirmed by carrier, band and quality measurements.
Active transportNetwork and coverage units connected through the approved category-cable and power architecture.
RF distributionCoverage-unit antennas and any passive components system engineeringed for rooms, floors, loss and capacity.

Which QUATRA platform the operators require

Inventory user populations, carriers, critical locations, voice and data problems, building construction and expected changes. Perform an RF survey by carrier, band and area. Decide whether a single- or dual-operator EVO system engineering or a broader QUATRA 4000 architecture matches the actual requirement.

A family name settles little: it does not mean a given carrier and band combination is available at the site. Confirm the exact regional hardware, supported bands, network and coverage units, operator capacity, licensing or service, and the carrier approval path.

Discovery needs to identify protected areas, users, schedules, response procedures, privacy expectations, existing equipment and the party who will administer the finished system. Product claims only become useful after they are translated into measurable coverage, capacity, availability and response requirements.

  • Inventory of users by carrier
  • RF survey per band
  • Where EVO fits against 4000
  • Regional/operator support

Signal source, cabling and coverage-unit system engineering

Measured signal and quality, antenna location, interference and isolation are what the donor source is engineered from. The distribution side is planned against the current Nextivity architecture: category-cable routes, switch or power requirements, distance, intermediate rooms, coverage-unit density and environmental limits.

System Engineering the indoor antenna system from floor plans, wall loss, occupancy and target service. Coordinate pathways, firestopping, grounding, roof work and service access. Separate critical dependencies and document spare ports or units for growth.

Backup power, mounting, pathways, environmental ratings, network addressing, PoE or low-voltage supply and door or camera interfaces need coordinating. Before anything is ordered, check that the exact model and the supported software line up, because two products with near-identical names can differ in capacity, license or integration limits.

  • Isolation and choice of donor source
  • Category-cable architecture
  • Coverage-unit placement
  • Choice of indoor antenna
QUATRA platform engineering assessment
DecisionEVO emphasisQUATRA 4000 emphasis
OperatorsOne or two supported pathsBroader multi-operator system engineering
TransportApproved active hybridApproved active hybrid
CoverageCoverage units and antennasCoverage units and antennas
AcceptancePer-operator RF and servicePer-operator RF and service

Field Installation, functional commissioning and acceptance

Install and label network units, coverage units, cables, donor and indoor antennas by the approved system engineering. Test copper links and RF paths before final functional commissioning. Use the official functional commissioning and management tools and do not mirror software packages on the public site.

Validate each intended operator in representative areas using RF metrics and real voice/data workflows. Review alarms, gain, interference, handoff and uplink behavior. Compare results with the baseline and system engineering criteria and document inaccessible or excluded areas.

Use named administrators, least privilege and multifactor authentication where supported. Establish backup, update, health-monitoring and escalation ownership. Firmware and software needs to come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.

  • Verified copper and RF paths
  • Official functional commissioning tools
  • Per-operator acceptance
  • Checking alarms and the uplink

Ongoing ownership, carrier contact and lifecycle

Deliver unit, antenna, cable and port inventory, RF system engineering, before/after measurements, software and account ownership, alarms, operator status and accepted exceptions. Protect detailed RF and management data in the client repository.

Name the owner for monitoring, subscriptions, firmware, carrier escalation and change control. Coverage is revalidated whenever carrier spectrum, donor, floorplan, cabling or coverage units change, under current regulatory and manufacturer requirements.

Acceptance needs to test normal use, denied or alarm conditions, loss of network or power, notification, audit history and administrator recovery. Deliver protected configuration records, licenses, serials, diagrams, test evidence, support links and clearly owned exceptions.

  • Active units mapped to ports
  • RF records kept protected
  • Named owner for monitoring, firmware
  • Carrier/change coordination

The KSEDCO approach to this work

The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.

Discover

Documentation captures workflows, people, assets, risks and the systems already in place.

System Engineering

A supported architecture is chosen, with devices, licenses and integrations.

Install

Staging, labeling and commissioning happen under change control.

Validate

Operating scenarios get run, then lifecycle records handed over.

Information to gather before system engineering

Good decisions are easier when the security engagement team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.

  • Day-to-day use cases and response
  • Compatibility between devices and software
  • What connects: power, network, physical
  • Licenses, identity and cyber hardening
  • Signoff, support and lifecycle

Common questions

These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.

Does QUATRA work like a passive coax-only booster?

No. The architecture is active DAS hybrid, built from network units, coverage units and an RF antenna system.

Is a carrier survey needed before choosing the platform?

Yes. The choice rests on carrier, band, quality and user requirements.

Does Category cabling remove RF system engineering work?

No. Placement of the donor and indoor antennas, isolation, interference and coverage are still RF engineering work.

What needs to be tested at handoff?

Every operator, in representative areas, with voice and data workflows, RF metrics, alarms, recovery.

Technical files, software and firmware live on the manufacturer’s official site. No firmware copies are hosted here.

Discuss a commercial security engagement

Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and system engineering conversation.

Contact KSEDCO