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 deployment design.
Select the complete system, not one headline feature
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the deployment design.
Operator needs and QUATRA platform selection
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 deployment design or a broader QUATRA 4000 architecture matches the actual requirement.
Confirm the exact regional hardware, supported bands, network units, coverage units, operator capacity, licensing or service and carrier approval path. Product-family names do not guarantee that every carrier and band combination is available at a site.
Discovery must 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.
- Carrier and user inventory
- Band-by-band RF survey
- EVO versus 4000 role
- Regional/operator support
Signal source, cabling and coverage-unit deployment design
Engineer the donor source from measured signal and quality, antenna location, interference and isolation. Plan category-cable routes, switch or power requirements, distance, intermediate rooms, coverage-unit density and environmental limits using the current Nextivity architecture.
Deployment Design 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.
Coordinate network addressing, PoE or low-voltage power, pathways, environmental ratings, mounting, door or camera interfaces and backup power. Verify exact model compatibility and supported software before ordering; similar product names can conceal different capacity, license or integration limits.
- Donor source and isolation
- Category-cable architecture
- Coverage-unit placement
- Indoor antenna model
| Decision | EVO emphasis | QUATRA 4000 emphasis |
|---|---|---|
| Operators | One or two supported paths | Broader multi-operator deployment design |
| Transport | Approved active hybrid | Approved active hybrid |
| Coverage | Coverage units and antennas | Coverage units and antennas |
| Acceptance | Per-operator RF and service | Per-operator RF and service |
On-Site Installation, operational acceptance and acceptance
Install and label network units, coverage units, cables, donor and indoor antennas by the approved deployment design. Test copper links and RF paths before final operational acceptance. Use the official operational acceptance 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 deployment design 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 must come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.
- Cable and RF verification
- Official operational acceptance tools
- Per-operator acceptance
- Alarm and uplink review
Management, carrier coordination and lifecycle
Deliver unit, antenna, cable and port inventory, RF deployment design, before/after measurements, software and account ownership, alarms, operator status and accepted exceptions. Protect detailed RF and management data in the client repository.
Assign monitoring, subscription, firmware, carrier-escalation and change ownership. Revalidate coverage after carrier spectrum, donor, floorplan, cabling or coverage-unit changes and follow current regulatory and manufacturer requirements.
Acceptance must 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-unit and port map
- Protected RF documentation
- Monitoring and firmware owner
- Carrier/change coordination
How we plan and deliver the work
The final deployment design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Document people, assets, workflows, risks and existing systems.
Deployment Design
Select the supported architecture, devices, licenses and integrations.
Install
Stage, label and commission through controlled changes.
Validate
Exercise operating scenarios and deliver lifecycle records.
Information to gather before deployment design
Good decisions are easier when the site program team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Operational use cases and response
- Device and software compatibility
- Power, network and physical interfaces
- Licensing, identity and cybersecurity
- Acceptance, support and lifecycle
Frequently asked questions
These are common deployment planning questions. A site-specific answer must be confirmed during discovery and deployment design.
Is QUATRA the same as a passive coax-only booster?
No. It is an active DAS hybrid architecture with network and coverage units plus an RF antenna system.
Can the platform be selected without a carrier survey?
No. Carrier, band, quality and user requirements are essential inputs.
Does Category cabling remove RF deployment design work?
No. Donor and indoor antenna placement, isolation, interference and coverage still require RF engineering.
What must be tested at handoff?
Each operator, representative areas, voice/data workflows, RF metrics, alarms and recovery.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Discuss a commercial security site program
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and deployment design conversation.