Technology
›
Telecom, Media & Entertainment
›
Telecom Equipment Sales
Radio Access Network Equipment Sales
Complex platform, content, and network decisions where revenue, rights, and customer experience intersect.
Example organizations in this space:
Ericsson
Nokia
Samsung
CommScope
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Pre-Sales
Qualify and diagnose before investing in a full evaluation cycle.
-
Qualification
Confirm budget envelope, procurement timeline, decision-makers, and high-level rollout constraints before investing in full discovery.
Qualification Questions
Rollout scope and high-level technical constraints
- Roughly how many cell sites are in scope for this program?
- Which representative site archetypes should we include in sample discovery and trials?
- Are there site-level constraints we should know up front (structural load limits, power availability, backhaul types, permitting windows)?
- Will you require explicit interoperability validation with existing baseband or vendor-neutral interfaces for lab/field trials, and will those interfaces be available for testing?
Budget and commercial envelope
- Is there an allocated procurement budget (including expected multi-year license/feature spend) for this program, and which range best fits?
Decision authority and stakeholders
- Who holds final sign-off for a framework procurement of this scale? (role or function is fine)
- Which stakeholders must be involved separately for technical acceptance (lab/field trials) versus commercial sign-off? Select all that apply.
Timeline and decision drivers
- What is your target decision milestone for awarding a framework contract?
-
Outcome Discovery
Map the current RAN footprint, performance baselines, site archetypes, stakeholders, and measurable success signals.
Discovery Questions
A quick network snapshot
- How many active radio sites does your organization manage today, and which site types (macro, small cell, indoor) make up the largest share?
- List the frequency bands you run in production and the approximate traffic share on each (provide band and percent)
- Walk me through the baseline KPIs you report quarterly, including typical downlink per sector, average spectral efficiency, and average site energy use (kWh/site/month)
- Looking at your most recent regional performance review, name the top three metrics that triggered internal concern
- What single current network limitation would cause you to pause or shrink a vendor rollout immediately?
What outcomes leadership really cares about
- If a new radio meets throughput targets but increases per-site energy by 15–25%, would finance and the CTO accept the trade-off or block the award?
- Which internal stakeholders must sign off on technical acceptance, and what concrete authority does each hold (approval, veto, advisory)?
- How do you translate a per-site performance shortfall into business impact (estimate monthly revenue loss, churn risk, or increased OPEX per affected site)?
- Across your portfolio, which site archetype (tower, rooftop, dense urban macro, indoor enterprise) most frequently forces a design change or delay, and why?
- What acceptance threshold in lab or field testing would make your team recommend awarding framework volumes to a vendor without additional pilots?
Where integration usually trips teams up
- Name the interoperability assumption about your baseband, transport, or core that, if false, would force rework across many sites
- How many distinct baseband vendors, software release lines, or split architecture variants exist in the candidate rollout region?
- Who owns firmware, configuration, and test governance for multi-vendor RAN in your organization, and do they have dedicated integration windows?
- Assume a vendor cannot demonstrate over-the-air integration with one key baseband within your required timeline, how likely is that to delay procurement or require design changes?
- Identify a specific connector, API, or physical interface gap that would make a vendor a non-starter for you
Sites, approvals and the hard gates
- Estimate the percentage of planned rollout sites that currently have unresolved structural, power, or access constraints that would block installation within eight weeks
- Who signs civil, tower loading, and power approvals in each region, and what are typical lead times for those approvals?
- Do you have complete site survey, tower loading, and power baseline documentation available for the pilot sites, or are records partial?
- Identify one site-level prerequisite that, if missing at scale, would force you to pause the rollout
How you will judge success in the field
- You may accept better sector throughput at the cost of some cell-edge beam consistency; under what conditions would throughput wins outweigh beam stability concerns for you?
- Provide your target acceptance numbers for key measures: downlink throughput (Mbps/sector), uplink throughput (Mbps/sector), spectral efficiency (bits/s/Hz), and per-site energy (kWh/month)
- What sample size of sites do you require in a pilot to reach statistical confidence, and which archetypes must that sample include?
- Assuming the pilot meets all quantitative criteria, who in your organization can sign the recommendation to proceed within the same week?
The other options on your table
- What would have to be true about your incumbent supplier's price, roadmap, or performance for you to keep them as the primary vendor?
- Which categories of alternatives have you evaluated or are still considering? Select all that apply and add any not listed
- If you were to stay with your current approach, what specific improvements or guarantees would need to be delivered to avoid switching vendors?
- Has anyone on your team proposed solving the gaps internally rather than contracting a vendor, and what would the expected internal timeline be?
- What single competitive factor—price, energy performance, integration ease, or roadmap alignment—would make you choose a new vendor over the incumbent this cycle?
Operational readiness and gating constraints
- Which critical integration dependencies must be in place before a pilot (transport VLANs, OSS/BSS APIs, power upgrades), and who owns each?
- Do you have the internal headcount and specialist skills (RF integration engineers, field test crews) available to support lab validation and pilot rollouts within your target window?
- Is there regulatory or compliance approval that could gate the pilot or national rollout (spectrum, safety, export controls), and what is the expected approval timeline?
- What data or site records are currently missing that would prevent a realistic lab-to-field acceptance plan (e.g., antenna patterns, cabling maps, power draw logs)?
- Which single readiness gap above, if unresolved before pilot start, would cause you to delay the project?
Decision timing and next steps that accelerate things
- What procurement timeline do you expect from final acceptance to framework contract signature (weeks or months)?
- If a pilot validates your targeted improvements, what internal roadblocks remain that could still prevent a quick award?
- What budget or commercial trigger would allow you to commit to a phased rollout immediately after successful pilots?
- Who should be included from your side in a technical workshop next week to finalize pilot scope and acceptance tests?
- What single decision or deliverable, if secured in the next two weeks, would allow this project to move from evaluation to an agreed pilot schedule?
-
-
Solution Experience
Walk through how the proposed hardware, features, and operational workflow deliver the customer's target outcomes across representative site types.
Solution Experience
- Solution Experience Session
- Confirm the current state and its cost to your team
- You confirm the documented acceptance gaps and the cost they impose on the procurement timeline.
- Provide the list of representative site archetypes and your current baseline KPI numbers for each archetype.
- You confirm that the shown per-site evidence workflow would produce the acceptance data you need to sign a framework contract.
- Map proposed solution to your site archetypes
- Run the seller's lab benchmark for the agreed throughput scenario and deliver the raw results and interpretation before the field trial start date.
- Show the evidence workflow for one representative site
- You agree on the remaining lab and field tests and the exact pass/fail metrics that will be used to evaluate results.
- Define the trial site shortlist and schedule the field validation windows for the next 60 days.
- Agree outstanding tests and acceptance criteria
- Validate this maps to your needs
- Solution Experience Session
- Solution Experience Deck
- Solution Brief
- meeting
- slides
- document
-
Technical Evaluation (Lab & Field Trials)
Run lab benchmarks and field trials against precise acceptance criteria (throughput, spectral efficiency, beam performance, energy use, and interoperability) and document pass/fail outcomes.
- current_state
- decision_readiness
- success_criteria
- desired_state
- gaps
- stakeholders
- gaps
- stakeholders
- desired_state
- success_criteria
- decision_readiness
- current_state
- gaps
- current_state
- desired_state
- success_criteria
- stakeholders
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Solution Scope
Define equipment counts by site-type and band, software license entitlements, responsibilities, integration points, and measurable acceptance tests.
Scope Configuration
- Deliver Macro Base Station Hardware
- Deliver Massive MIMO Active Antenna Systems
- Deliver Remote Radio Units
- Deliver Small Cell Hardware
- Provide Standardized Mounting Kits and Structural Certification
- Install and Mechanically Mount Site Equipment
- Commission and Integrate Radios with Baseband and Core
- Preconfigure Site Software Images and Feature Profiles
- Provision Software Feature Licenses per Site
- Activate Energy-Saving Modes and Remote Tilt Control
- Perform Field Drive-Test Validation and RF Tuning
- Supply Spare Parts, Field Repair Kits, and Logistics
- Deliver Firmware and Remote Software Update Service
- Provide Financing Quotes and Incentive Qualification Package
Scope Questions
Deliver Macro Base Station Hardware
- Specify the macro site archetypes to supply (example archetypes: urban rooftop, suburban pole, rural guyed tower) and the estimated unit counts per archetype.
- Which frequency bands must each macro base station unit support? (select all applicable)
- Provide the required transmit/receive port configuration per macro unit (use 4T4R, 8T8R, 32T32R, 64T64R as examples).
- Indicate the maximum acceptable antenna weight and wind-loading limits for rooftop and tower mounts (provide values in kilograms and Newtons/m^2 or upload structural limits).
- Estimate the target per-sector downlink throughput you expect from these macro units under typical load (specify Mbps and percentiles, e.g., 95th percentile).
- Confirm required environmental and regulatory certifications for macro hardware (select all that apply).
Deliver Massive MIMO Active Antenna Systems
- List the massive MIMO antenna panel sizes and port configurations required by site archetype (examples: 32T32R for urban macro, 64T64R for high-capacity sectors).
- Which mid-band and high-band carrier aggregation scenarios must the active antenna support (e.g., 3.5 GHz + 700 MHz, or 3.5 GHz + mmWave)?
- Indicate the acceptable antenna panel front-end power consumption target in watts per sector or kWh per site per day.
- Specify mechanical constraints for antenna placement: maximum panel dimensions (HxW cm), permitted tilt range in degrees, and required connector type (for example 4.3-10).
- Identify required beamforming feature entitlements (examples: wideband beamforming, per-beam power control, MU-MIMO) and whether license gating is expected per feature.
- State any interoperability constraints with existing radios or baseband equipment, naming interfaces such as Common Public Radio Interface (CPRI) or eCPRI and expected fronthaul line rates.
Deliver Remote Radio Units
- Indicate the remote radio unit (RRU) footprints needed by site type (indoor cabinet, outdoor pole-mounted, tower top) and per-site quantities.
- Which RF connector types and IF/fiber interfaces are required on the RRU for your existing split architecture (for example 4.3-10 RF, SFP+/QSFP for fronthaul)?
- Specify ambient operating temperature and enclosure ingress protection targets for RRUs (provide temperature range and IP rating).
- Estimate the expected per-RRU power feed available at sites (options: -48 VDC, 230 VAC single phase, 3-phase 400 VAC) and whether existing UPS is present.
- Identify any fronthaul timing or sync requirements (for example IEEE 1588v2 Precision Time Protocol or SyncE).
- Are there site-level RF exposure / radiation constraints or mandatory exclusion zones that affect RRU placement? Provide the safety standard or distance limits.
Deliver Small Cell Hardware
- Describe small-cell deployment scenarios you require (indoor enterprise, outdoor lamppost, in-building DAS integration) and estimated counts per scenario.
- Select the backhaul connectivity types available at small-cell locations (select all that apply).
- Specify required low-profile antenna mechanical limits for small cells (maximum protrusion, weight, and mounting bracket dimensions).
- Indicate any indoor coverage KPIs to meet (examples: median user throughput in Mbps, voice call drop rate, spectral efficiency bps/Hz).
- State whether small cells must support dynamic spectrum sharing (DSS) between 4G LTE and 5G NR on the same carrier.
- Identify any co-location constraints with third-party equipment in the small-cell mounting location (power sharing, heat dissipation limits).
Provide Standardized Mounting Kits and Structural Certification
- List the mounting kit types required by archetype (rooftop parapet mount, tower cross-arm, pole clamp) and the expected quantities.
- Specify whether a stamped structural engineering letter or a full tower structural analysis is required for each mount type and the jurisdictional licensing standard (for example licensed professional engineer (PE) stamp).
- Indicate the maximum permitted mount point loads and uplift values supplied by the site owner that the mounting kit must stay within.
- Identify required fastener types and corrosion protection class for mounts (for example stainless steel grade, hot-dip galvanized), especially for coastal sites.
- Are third-party structural drawings already available for the inventory of sites? If so, provide the document types available (PDF, AutoCAD, single-line diagram (SLD)).
- State the expected lead time tolerance for custom mounting kits (for example standard kit in 8 weeks, custom in 12-16 weeks).
Install and Mechanically Mount Site Equipment
- Describe whether installation teams will access sites using your field crews, third-party contractors, or a mix, and indicate any site access permit requirements.
- Provide the baseline installation tasks you expect included in scope (examples: mechanical mounting, cable routing, grounding, lightning protection, torque records).
- Identify required safety and certification prerequisites for installation teams at each site (examples: tower climber certification, confined space, lockout/tagout (LOTO)).
- Indicate whether temporary site modifications (scaffolding, crane lifts) are needed and whether permits for heavy-lift operations will be provided by you or must be coordinated.
- What defines mechanical installation acceptance for each site (examples: signed torque logs, antenna azimuth/tilt within ±X degrees, stamped structural certificate)?
- State any exclusion items that are explicitly out of scope for installation (for example tower reinforcement, civil works, power upgrades).
Commission and Integrate Radios with Baseband and Core
- Identify the baseband and core interfaces in use at target sites (examples: vendor-neutral O-RAN split, CPRI/eCPRI fronthaul, S1/X2 or NG interfaces).
- Specify required mobility and neighbor relation integration tasks (examples: automatic neighbor relation (ANR) tuning, X2/NG handover tests, neighbor list updates).
- List performance thresholds that commissioning must demonstrate in the lab or at site for acceptance (examples: per-sector downlink throughput in Mbps, spectral efficiency bps/Hz, acceptable BLER).
- Confirm the fronthaul transport expectations including latency ceiling (ms) and packet loss tolerance for CPRI/eCPRI links.
- Who will provide baseband configuration templates, and do those templates include carrier maps, bandwidth parts, and PRB allocations? Provide document type availability.
- What measurable acceptance criteria will confirm successful integration with baseband and core (examples: sustained downlink throughput ≥ X Mbps at Y percentile, end-to-end latency < Z ms, interop pass on specified test cases)?
Preconfigure Site Software Images and Feature Profiles
- Describe the site profile templates you want preloaded (examples: macro-urban-3-sector, smallcell-indoor, relay-site) and the configuration parameters each template must include.
- Indicate whether preconfiguration should include radio parameter sets for carrier aggregation, MIMO layers, and PRACH configurations per band.
- Specify whether software images must be signed and version-locked to a release train (for example ISO build IDs or semantic versioning).
- State required rollback and recovery behavior for preconfigured images (examples: automatic rollback on boot failure, manual rollback only).
- List the access credentials and tooling endpoints required for image push (for example SFTP server, secure bootstrap API endpoint, site tooling VPN).
- Indicate whether configuration differences must be exported as change logs in a specific format (examples: JSON delta, CSV) after push.
Provision Software Feature Licenses per Site
- Which software feature entitlements do you require per site (examples: carrier aggregation, advanced beamforming, energy-saving modes)? Select all that apply.
- Specify billing model preference for feature licenses: perpetual, annual subscription, or usage-based per GB or per active sector-hour.
- Indicate license activation workflow requirements (examples: bulk activation via license file, per-site activation through portal, offline license token).
- Estimate peak concurrent licensed features per site and whether license pooling across sites is required.
- Provide any regulatory or audit controls required on license keys (examples: license binding to serial number, reporting cadence).
- Identify who will manage license inventory and renewals within your organization (job role or team).
Activate Energy-Saving Modes and Remote Tilt Control
- State target energy consumption reduction goals per site after energy-saving modes are enabled (examples: kWh/day reduction, percent reduction from baseline).
- Which remote electrical tilt (RET) control interfaces are compatible with your OSS tools or radio management platform (examples: NETCONF, REST API, SNMP)?
- Indicate any blackout windows or quality constraints during which energy-saving mode transitions are not permitted (for example peak hours, scheduled traffic events).
- Specify acceptable convergence time when switching RET or energy mode settings (for example tilt change applied and stable within X minutes).
- Are you requesting automated policy scripts for energy modes tied to traffic thresholds (for example enable sleep mode when sector load < Y% for Z minutes)?
- Identify measurement artifacts required to validate energy and tilt activation (examples: power meter logs, RET command traces, before/after KPI snapshots).
-
Mutual Commit
Finalize framework contract modules: pricing bands, lead times, warranty, SLA terms, governance, and rollout milestones.
Agreement Modules
- Framework Supply Agreement
- Purchase Order & Order Confirmation
- Pricing Schedule & Volume Bands
- Delivery & Lead Time Schedule
- Warranty & Hardware Support
- Service Level Agreement (SLA)
- Software Licensing Annex
- Acceptance Tests & Field Trial Criteria
- Rollout Milestones & Delivery Plan
- Governance, Escalation & Change Control
- Payment Terms & Invoicing Schedule
- Site Handover & Acceptance Certificate
- Export Controls & Regulatory Compliance Addendum
- Master Services Agreement (MSA)
- Statement of Work (SOW)
-
Deployment
Lock readiness facts and configuration values before execution begins.
-
Pre-Deployment Readiness
Confirm site access, structural approvals, power availability, civil works status, and scheduled field-validation windows before execution begins.
Pre-Deployment Questions
Environment and site access
- Has the site list for this rollout been finalized and approved by the buyer for deployment planning? (We need a stable site list to allocate materials and crews.)
- Is confirmed, secure physical access arranged for the sites in scope (keys, access permits, on-site contacts or contractor coordination)? (Answer 'Yes' only if access is arranged for all sites.)
- If access is partial or pending, list the site IDs or archetypes needing access coordination and the expected date access will be granted (so we can schedule field teams).
Civil, power and structural readiness
- Have structural/tower approvals and load-bearing assessments been completed for each site? (Needed to confirm antenna weight and mount plans.)
- Is primary power (AC) and backup power (battery/generator) capacity verified per site and sufficient for the planned equipment and energy targets? (This prevents last-minute scope changes on install day.)
- For any sites with outstanding civil or power items, list the site IDs and the outstanding item(s) and target completion date (so we can block resources only after mitigation).
People and ownership
- Who is the buyer's local site owner responsible for granting physical access and approvals? Provide name, role, and single point of contact (email or phone).
- Who is the buyer's technical owner responsible for field-validation and acceptance testing (role and contact)? (This owner will sign off acceptance tests per site.)
Timing and constraints
- Are there regulatory, facility, or seasonal blackout windows or other constraints that will restrict installation dates per site? (If yes, we'll treat these as hard exclusions in the rollout schedule.)
- If field-validation windows are set for prime or representative sites, provide the earliest available start date or date range for those validation activities (so we can confirm lab-to-field sequencing).
-
Configuration Details
Capture per-site configuration values and constraints — antenna mounting specs, power limits, RF parameters, integration endpoints, and tooling credentials.
Configuration Details
Site identity & type
- Enter the site identifier to be used in the deployment build (format: alphanumeric, 3–32 chars). This value is consumed verbatim by inventory and site-config templates.
- Select the site deployment type (this drives default mechanical and RF profiles used by the site build)
Mechanical & structural constraints
- Select the antenna mounting interface at the site (closest match). Consumed by mounting BOM and mechanical drawings.
- Maximum allowable antenna mass at this site (kg). Default is 150 — change if site structural analysis requires a different limit. This value is used by the lift plan and hardware selection.
Power & environment limits
- Available continuous power capacity at the radio location (kW). Default 6.0 kW — supply the exact per-site value consumed by power provisioning and heat-load calculations.
- Is redundant power (A/B feed or equivalent backup) available at this site? This flag controls power-supply selection in the site build.
RF & antenna configuration
- Maximum allowed EIRP per carrier for this site (dBm). Default 61 dBm — provide the regulatory/operational limit consumed by RF parameter generation.
- Preferred antenna downtilt control method (this determines whether remote tilt configuration is enabled in commissioning scripts)
Integration & tooling endpoints
- Primary O&M / management interface type available at this site (choose the single interface the platform will use to push configs and read telemetry). Consumed by integration adapters.
-
Rollout Execution
Coordinate supply, sequencing, field teams, and integration testing across sites with clear owners, milestones, and escalation paths.
-
Go-Live Acceptance
Per-site acceptance checklist verifying installation quality, RF/throughput tests, energy targets, and signed operational handover before declaring sites live.
Checklist items
- Confirm physical installation meets site mechanical checklist
- Obtain structural and safety sign-off for the installed mount
- Execute and document Lockout/Tagout (LOTO) for any energized work
- Receive written Permission to Energize / local authority permit
- Complete initial power-up and equipment health verification
- Pass RF and throughput acceptance tests against agreed criteria
- Validate end-to-end integration with transport and core endpoints
- Verify measured site energy consumption meets target
- Upload as-built configuration and site documentation to shared workspace
- Provide rollback plan and confirm rollback readiness
- Obtain formal per-site acceptance signature and operational handover
-
-
Success
Track network performance against acceptance criteria, manage issues and enhancements, and maintain a shared improvement channel for the rollout.
Success Reviews
- Go-live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- Acceptance Gate Review (around day 90)
- Monthly Operational Review (ongoing, monthly for initial rollout)
- Quarterly Performance Review (ongoing, quarterly)
- Annual Network Performance Review
Issues & Enhancements
- Determine whether downlink throughput per sector and spectral efficiency are trending toward Technical Evaluation targets.
- Publish the acceptance report with pass/fail outcomes, supporting evidence, and the buyer signatory entry.
- If failures exist, open remediation tickets with verification tests and schedule the re-test window.
- If incumbent decommissioning applies, certify archival or migration of legacy data and confirm read-only access controls.
- Performance trend vs Technical Evaluation targets
- Ensure top critical issues are progressing to closure and that corrective actions are reducing gaps in downlink throughput per sector and energy consumption per site.
- Maintain a prioritized list of enhancement requests with committed delivery windows for items that materially affect acceptance metrics.
- Complete remediation work for the top three critical tickets and update verification evidence within the monitoring dashboard.
- Schedule and confirm field validation dates for remediated sites within two weeks.
- Record energy consumption deviations and propose energy-mode adjustments for high-variance sites.
- Quarterly trend analysis
- Confirm whether throughput and beam performance meet rollout trajectory and commit to a prioritized remediation roadmap for the quarter.
- Resolve ownership and timelines for any long-lead or cross-team blockers.
- Publish the prioritized enhancements backlog with expected metric impact and quarter delivery windows.
- Open mitigation plans for long-lead items and schedule escalation checkpoints as required.
- Refresh the improvement channel SLAs and publish the updated governance note.
- Year-to-date performance vs targets
- Validate annual achievement against spectral efficiency and energy consumption targets and document any outstanding gaps requiring program-level action.
- Produce an updated set of runbooks and a defined monitoring cadence for the next 12 months.
- Publish the annual performance report with spectral efficiency and energy consumption analysis and disseminate to the governance forum.
- Update installation and tuning runbooks with lessons learned and circulate for operational adoption.
- Define the ongoing alert thresholds and monitoring dashboards for continuous tracking against Technical Evaluation targets.
- Confirm deployment completion for the sampled sites and that owners are assigned for each acceptance criterion.
- Document all critical open issues with agreed remediation timelines.
- Create and publish the go-live issue register with severity, owner, and due date.
- Schedule targeted field-validation windows for sites with outstanding installation or integration issues.
- Enable monitoring dashboards for sector-up and attach success rates for continuous observation.
- Present first measurement data
- Re-confirm acceptance criteria and owners
- Set a specific remediation plan with milestones and completion dates to resolve the top 3 measured gaps.
- Implement agreed RF parameter adjustments for identified sites and document expected impact per site archetype.
- Schedule focused field trials for the top 5 underperforming sites within the next 14 days.
- Produce a dataset package that maps each measured shortfall to its proposed corrective action and estimated resolution date.
- Restate acceptance criteria and numeric targets
- Capture a formal pass or fail decision for each numeric acceptance criterion recorded in Technical Evaluation (Lab & Field Trials).
- Record the buyer's named signatory acceptance or conditional acceptance and list remediation items with deadlines for any failures.
- Deployment validation and install quality
- Backlog and enhancement prioritization
- Compare results to Technical Evaluation targets
- Operational cost and energy savings review
- Critical incident and ticket burn-down
- Present final outcome data for each criterion
- Persistent blockers and long-lead items
- Enhancement and configuration requests
- Lessons learned and runbook updates
- Root-cause analysis for shortfalls
- Early adoption and usage signals
- Document pass/fail per criterion
- Open issues triage
- Formal acceptance decision and signatory capture
- Improvement channel health
- Agree corrective actions and timeline
- Verification and field-validation scheduling
- Long-term monitoring and escalation cadence
- Remediation plan for any failed criteria
- Immediate remediation agreement
- Incumbent system wind-down status, if applicable