Selecting 5G customer-premises equipment (CPE) at scale is a multi-year commitment with direct consequences for subscriber experience, support cost, and network reputation. A structured request for proposal (RFP) — backed by disciplined lab testing and field trials — is how operators, MVNOs, and distributors turn a crowded vendor landscape into a defensible, repeatable decision. This guide outlines the criteria, testing, and trial playbook for running a 5G CPE RFP.
Why a Structured RFP Matters
CPE datasheets are optimized to look good; real-world behavior on a specific network is what actually determines success. A structured RFP forces vendors to respond against a consistent, scored set of requirements, making it possible to compare RF performance, security, manageability, and total cost of ownership (TCO) on equal footing. It also creates an auditable record that protects the decision when priorities shift or a chosen device underperforms later. For MVNOs and smaller operators without deep lab resources, the RFP itself becomes a forcing function to define what “good” means before a device ships to subscribers.
Building the Evaluation Criteria
Anchor the RFP on weighted criteria across five domains. Radio and throughput: supported bands, carrier aggregation combinations, antenna and MIMO configuration, and sustained throughput under load. Security: secure boot, signed firmware, VPN and firewall capabilities, and management-plane hardening. Manageability: TR-069 and TR-369 support, zero-touch provisioning, FOTA, and diagnostics. Certification and compliance: CE, FCC, GCF, and any region-specific approvals for the target markets. Lifecycle and TCO: price, warranty, firmware support cadence, spare parts, and end-of-life policy. Weight each domain by business priority before scoring begins, and publish the weights so vendors can respond intelligently.
Lab Testing Methodology
Bring shortlisted devices into a controlled lab before any field work. Test throughput, latency, and jitter across the operator’s actual band and carrier-aggregation configurations, not just theoretical peaks. Stress-test thermal behavior under sustained load, verify failover and reboot recovery, and exercise the full firmware update and rollback path. Run security checks against the management interface and confirm the device behaves correctly under slicing, QoS, and policy changes. A consistent, scripted test harness with pass/fail thresholds turns subjective impressions into comparable numbers.
The Field Trial Playbook
Field trials validate what the lab cannot: real RF environments, installability, and long-term stability. Define clear success metrics — activation success rate, mean throughput at the cell edge, support tickets per device, and uptime. Run trials across a representative mix of locations (urban, suburban, and rural) and, where relevant, across multiple carrier networks. Give installers a defined procedure and capture their feedback on mounting, antenna placement, and cabling. A two-to-four-week trial with telemetry collection usually surfaces the issues that matter most at scale.
Vendor Scoring and Total Cost of Ownership
Combine lab and field results with the weighted RFP scores, then model TCO over three to five years. Include hardware price, logistics, installation, support burden, firmware maintenance, and failure/replacement rates. A device with a higher unit price can easily win on TCO if it generates fewer support tickets and survives longer in the field. Wherever possible, negotiate firmware support commitments, spare-part availability, and a defined end-of-life roadmap into the contract rather than discovering gaps after deployment.
Common Pitfalls to Avoid
The most frequent mistakes are over-weighting theoretical peak throughput, skipping thermal and reboot stress tests, and treating certification as a checkbox instead of verifying it against the exact regulatory regime of each launch market. Equally damaging is ignoring installability — a device that is difficult to mount or provision will erase the savings from a low unit price in support costs. A disciplined RFP, rigorous lab work, and honest field trials are the difference between a CPE fleet that quietly performs and one that becomes a recurring operational burden.