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.
Ericsson
Nokia
Samsung
CommScope
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles (CTO, VP Network, CFO, board), timeline, risk tolerance, and what ‘good’ looks like for each stakeholder.
Alignment Questions
Opening: Your Network Ambitions
- What is the single most important objective for this RAN program right now?
- Who is driving the technical evaluation and who owns the final capital approval?
- What is your target timeline from RFI to framework contract execution and first site rollout?
- How would each stakeholder (CTO, VP Network, CFO, board) describe ‘good’ for this program — in one sentence each?
- Which past procurement wins or regrets are influencing how you want to run this program?
If We Keep Doing What We Do Today, How Much Will That Cost You?
- How is your current vendor split structured across the footprint today?
- Tell us about a time vendor lock-in or a long migration path caused measurable pain—what happened and what were the consequences?
- How do you currently preserve competitive tension while avoiding risky churn?
- Practically, how long (months) and what activities would a full technology/vendor switch require for a typical region?
- How tolerant are your executives to migration risk vs. potential price savings—describe the mood and decision posture.
What Keeps Your Network Engineers Awake at Night?
- Which technical KPIs worry you most right now?
- Please provide current baseline numbers or ranges for the KPIs you just selected.
- Which site classes historically underperform or cause the most operational overhead?
- Share a concrete incident where performance or energy surprised you—what were the root causes and business impact?
- How do you currently measure and validate per-site energy consumption and RF performance?
What Would 'Unquestionable' Performance Look Like?
- If someone said your RAN delivered ‘unquestionable’ performance, what three concrete outcomes would they cite?
- For each stakeholder (CTO, VP Network, CFO, board), what single measurable target would win their confident approval?
- Which matters more for your program: peak site performance (best-in-class throughput) or predictable, lower TCO per site? Pick where you’d invest first.
- Imagine a 3-year stretch where rollout pace and performance both accelerate—what would change operationally and culturally inside your teams?
- If you could remove one procurement or deployment constraint immediately, which would it be and why?
Show Me the Evidence — How Will You Validate Claims?
- What trial evidence would make you comfortable awarding a large framework: lab benchmarks, interoperability tests, short field pilots, or long-duration trials?
- What pass/fail criteria do you require for a field trial to be considered successful?
- Which site types must be included as mandatory in any trial to be representative?
- Who on your team will own trial evaluation and final sign-off (names/roles preferred)?
- Approximately how many sites, hours of testing or throughput samples do you expect before you’ll consider results statistically meaningful?
What Are the Hidden Costs Nobody Talks About?
- Which non-hardware line items drive unexpected cost when you deploy new radios?
- Do you have validated tower structural assessments and mounting constraints for your prioritized site classes?
- What supply chain or lead-time risks keep you from committing to a multi-year framework today?
- Which software license model would best align with your budget and operational goals?
- How would you prefer spare parts, warranties, and software updates be bundled to reduce surprises?
Who Really Needs to Be Comfortable Before You Sign?
- Which stakeholder(s) have historically been the deal blockers on large RAN buys?
- For each blocker you've selected, what is their primary concern (cost, risk, interoperability, vendor lock-in, SLA)?
- What commercial protections would make the CFO comfortable (e.g., exit clauses, performance credits, volume flex)?
- What kind of executive-level assurance (metrics, dashboards, escalation) helps the board feel confident in multi-year frameworks?
- What evidence or demos would move skeptics to ‘support’ rather than ‘observe’ during procurement?
If We Start Tomorrow, What Would True Readiness Look Like?
- Do you currently have site access permissions, permits, and structural clearances for the priority rollout areas?
- How complete is your inventory of integration points (BBU versions, transport interfaces, cloud/core compatibility)?
- What logistics or regulatory bottlenecks typically delay deployment in your regions (permit, customs, tower access, workforce)?
- Who should be the named owners for deployment readiness tasks (site access, integration inventory, structural fixes, logistics)?
- How would you like rollout sequencing prioritized if resources are constrained?
How Will You Know We Delivered?
- Which acceptance tests are non-negotiable for sign-off on a site?
- What format and level of evidence do you require for per-site sign-off (e.g., formatted test report, raw logs, signed forms)?
- What SLA levels (availability %, response times) are required for the framework and where are you willing to trade strict SLAs for pricing?
- Who will own long-term support, escalation, and continuous improvement after rollout?
- How would you like post-deployment lessons learned and enhancement requests captured and prioritized?
-
Current State Mapping
Document existing RAN topology, vendor splits, site classes, supply chain constraints, and failure modes that drive requirements.
Current State
Setting the Stage: A Quick, Useful Snapshot
- Who will be our primary technical and commercial contacts for this RAN evaluation (name + role)?
- Which operator account, country/region, and network cluster does this project cover?
- What stage of the procurement are you in today?
- Approximately how many sites are in-scope for the initial framework?
- Which decision roles must sign off on vendor selection and the capital envelope?
- What is your target timeline to begin physical rollout of the first tranche of sites?
- Anything else about organizational context or competing initiatives we should understand up front (regulatory, JV partners, national rollout vs urban pilot)?
If You Could Fix One Thing About Today’s Network, What Would It Be?
- If you had to name the single biggest regret about your current RAN setup, what is it and why?
- How is your current vendor split across this geography?
- Which frequency bands and radio families are currently deployed across the sites in scope?
- How would you classify the site types in scope?
- What baseband/core platforms are these sites integrated with today (vendor + generation)?
- How old is the installed RAN equipment (by percentage of sites)?
- Which supply chain constraints are most limiting your deployment plans today?
- Which failure modes drive your most urgent requirements (select all that apply and list examples below)?
- How frequently do you experience service-impacting RAN failures in the scoped footprint?
- Please describe one recent failure that influenced procurement or design choices (what happened, impact, who owned remediation).
Where Performance Promises Often Fall Short — Let’s Be Brutally Clear
- Where do current vendor choices actively limit your ability to meet strategic goals (coverage, capacity, energy, speed of rollout)?
- Which measurable KPIs are monitored today and reported to execs?
- For the KPIs you selected, what are the target numbers and current baselines? (list KPI → baseline → target)
- How do you currently validate RAN interoperability with your baseband/core (lab interop, vendor test suites, field integration sites)?
- Have you run cross-vendor performance benchmarks (e.g., MIMO beam tests) in the last 12 months? If yes, what was the scope and conclusion?
- How confident are your technical leads that the current RAN vendors can meet the next-band performance and energy targets?
- Which site classes should be treated as highest priority for performance validation (select up to three)?
- Tell us about a trial or benchmark that surprised you—what did you learn and how did it change your approach?
Which Assumptions Are Quietly Steering This Program?
- Which of these beliefs best describes your procurement stance today?
- How entrenched is dual-sourcing as a strategy—non-negotiable, preferred, or open to change?
- To what extent are you willing to trade higher hardware cost for lower operating cost (energy + installation + licensing)?
- How important is software licensing model predictability (per-site perpetual vs feature-subscription vs usage-based) for your forecast?
- Which long-held assumptions might be worth testing in a small experiment (e.g., heavier upfront hardware for energy savings, software-enabled features to replace hardware layers, or Open RAN interoperability)?
- Which stakeholders or committees typically push back on challenging these assumptions (and why)?
- Give one concrete example of an assumption that, if proven false, would change your procurement approach dramatically.
If This Program Succeeds, What Will People Celebrate?
- Describe the network in three measurable ways that would make the CTO and CFO both say “we did the right thing.”
- What are your target ranges for these priority KPIs?
- Which cost-per-site levers will have the biggest influence on your procurement decision?
- Who are the internal champions and who are the skeptics for this program—and what will win each group over (metric or evidence)?
- What pass/fail criteria would you set for a small field trial to prove the offering reduces TCO per site?
- How would you like trial results packaged for executives (one-page scorecard, full KPI dataset, live demo, or site visit)?
- If we deliver a proof that meets these targets, what procurement outcome do you expect (preferred vendor slot, framework volume, phased award)?
What Could Break This Plan Before It Starts?
- Which of the following risks worries you most right now?
- Tell us about a logistics or rollout problem from the past 18 months that delayed delivery—what exactly happened and how was it resolved?
- How confident are you that site-specific structural assessments and permits can be completed within your planned rollout window?
- Which integration dependencies are non-negotiable before we deploy radios at scale?
- What contingency budget or schedule buffer do you typically allocate for unexpected technical rework?
- How do you currently manage third-party installers and contractors—centralized program vs regional procurement?
- Which approvals or sign-offs typically take the longest and why (technical, legal, finance, board)?
- What practical steps have worked in prior rollouts to reduce schedule risk (e.g., pre-staging sites, parallel approvals, vendor-managed logistics)?
Ready to Run a Small, High-Impact Experiment?
- What’s one small pilot (site class and scope) that would give you a decisive answer within 8–12 weeks?
- Which KPIs must the pilot prove for you to greenlight a scaled rollout?
- Who will be the project owner(s) for the pilot and what internal resources can you commit (lab access, RF engineers, drive-test teams)?
- What budget range is available for an initial pilot/trial (hardware + integration + test)?
- What is an acceptable timeline to decide go/no-go after a pilot completes?
- If the pilot shows mixed results, what shaped remediation would you accept (software patch, hardware tweak, extended trial)?
- Finally, what would make you say yes to starting a pilot with us this quarter? (single most important condition)
-
-
Outcome Discovery
Define measurable success signals (throughput per sector, spectral efficiency, energy per site, rollout cadence) and business constraints for the procurement.
Discovery Questions
Quick Grounding: Your Outcome Priorities
- Which of these outcome signals would you rank as highest priority for the upcoming RAN procurement?
- What’s the single most important business reason you’ll judge a vendor as ‘successful’ after rollout?
- How soon do you expect the chosen equipment to start delivering measurable gains versus today’s baseline?
- Briefly describe one recent example where a vendor delivered (or failed to deliver) an outcome you cared about.
- Which internal metric or dashboard does your leadership actually look at when assessing network performance?
If We Don’t Raise The Bar, What Breaks First?
- What are the consequences if your next-generation sites deliver only incremental—not step-change—improvements?
- Which customer or commercial outcomes feel most at risk (ARPU, churn, enterprise contracts, brand perception)?
- How long has the team been tolerating current performance limitations, and what has been tried already to mitigate them?
- Tell us about a recent capacity shortfall or site energy issue—what happened, who felt the impact, and how did you respond?
- If we fail to meet your targeted throughput or spectral efficiency, what internal escalation or commercial remedy would you expect?
How Do You Quantify 'Good'—Numbers That Actually Matter
- What specific numeric targets do you expect for these signals: downlink per-sector throughput, spectral efficiency (bps/Hz), energy per site (kWh/day), and rollout cadence?
- Which of the following KPIs will be used as pass/fail thresholds in trials or acceptance testing?
- For each KPI you select above, what is the minimum acceptable performance (provide numbers or ranges)?
- How frequently do you need KPI reporting to feel confident (real-time dashboards, daily, weekly, monthly)?
- What measurement tools and methods do you trust most for these KPIs (drive test, OTDR, lab emulation, operator probes, 3rd-party analytics)?
- Who in your organization will own the KPI gate during trials and who signs acceptance when thresholds are met?
What Would You Be Willing To Trade For Those Gains?
- If a supplier could deliver 20–30% better spectral efficiency but site energy rose slightly, how would you weigh that trade-off?
- Would you accept a phased performance ramp (best performance on new sites first) or require uniform performance across all site classes from day one?
- Which cost model do you prefer when balancing CapEx vs. recurring software/feature licenses?
- How important is minimizing installer time and tower climbs relative to raw hardware price when calculating TCO?
- Are you open to vendor-funded pilots where the vendor assumes trial risk in exchange for preferred rollout rights if targets are met?
- Which outcome would justify accepting a higher initial hardware cost?
Dependencies and Deal‑Breakers We Must Unblock
- What non-technical constraints could block selection even if performance is excellent (budget windows, single-vendor mandates, warranty language, import restrictions)?
- Do you have a fixed procurement window or capital approval date we must hit to be considered in this round?
- How will dual‑sourcing requirements be expressed in the framework (equal splits, preferred vendor share, geographic carve-outs)?
- Which contractual terms are immediate deal-breakers for you (short warranty, restrictive IP, onerous SLA credits, limited software access)?
- Are there supply‑chain or manufacturing constraints (local assembly, lead times, preferred OEMs) that will shape acceptable proposals?
- What level of pricing transparency or breakdown (HW, SW, services, logistics) do you require for internal approval?
Who Holds the Keys — Decision Roles, Influence, and Risk Appetite
- If we map this decision from technical recommendation to CFO/Board sign-off, who are the essential people and what does each care about most?
- What is the board/CFO’s tolerance for new architectures (e.g., Open RAN) versus proven monolithic vendor solutions?
- How much technical uncertainty (measured as probability of integration issues or rework) will you tolerate before the CFO says ‘no’?
- Which internal team will operate the field trials and who authorizes changes identified during trial remediation?
- Who needs to be present and convinced during the final executive demo or KPI readout for sign-off?
- How do stakeholders prefer evidence—raw test data, normalized dashboards, vendor-led presentations, or independent third-party validation?
How Will We Prove It — Trials, KPIs, and Acceptance
- What would make a trial result incontrovertible to you—statistical significance, representative site mix, or multi-vendor comparison?
- For field trials, which site classes must be included (urban macro, suburban macro, rural macro, dense urban small cell, indoor enterprise)?
- What sample size and duration do you consider sufficient per site class to accept performance claims?
- Which pass/fail criteria are non-negotiable (e.g., ≥X% of UEs meet target speeds, energy below Y kWh/site)? Please specify required thresholds.
- Who pays for trials, and are you open to split-cost models where vendors cover lab validation and operator covers field logistics?
- How will trial data be shared and protected — do you require anonymization, data escrow, or live dashboards?
Commercial Gates: Terms, Volumes, and What ‘Mutual Commit’ Really Means
- What commercial structure best aligns incentives for both parties—framework with volume bands, outcome-linked rebates, or standard per-unit pricing?
- What minimum framework volume or geographic scope would you commit to if performance and trials meet targets?
- Which software license model do you prefer for advanced features: perpetual, perpetual + maintenance, site-based subscription, or per-feature subscription?
- Which warranty and SLA elements are necessary for executive approval (MTTR, spare pool commitments, software patch cadence)?
- What commercial levers would you use to offset technology risk (price discounts, performance credits, extended warranty, pilot refund)?
- What would be a clear sign, from a commercial standpoint, that your executive team is ready to sign a framework agreement?
Practical Next Steps — What We Need From You to Move Forward
- What immediate artifacts or data can you share to accelerate baseline modeling (current RAN inventory, site classes, historical KPIs, energy bills)?
- Who is the single point of contact for coordinating trials, logistics, and approvals on your side?
- What timeline constraints should we be aware of for scheduling lab benchmarks, interoperability tests, and field pilots?
- How would you prefer to structure an initial pilot contract (fixed scope, time-boxed, or outcomes-conditioned)?
- What internal approvals or NDAs do we need in place before you can share sensitive baseline data or allow on‑site trials?
- If we deliver a draft trial plan within two weeks, when could your team realistically review and give feedback?
-
Solution Experience
Walk through realistic operator scenarios (capacity growth, densification, multi-band rollout) to show how the offering meets target outcomes and reduces TCO per site.
Experience Meetings
- Scenario Alignment & Current State Confirmation
- Capacity Growth Scenario — Simulation & Proof
- Densification & Small‑Cell Integration Scenario
- Multi‑Band Rollout & Interoperability Scenario
- Consolidated Validation & Executive Decision Workshop
- Seller to provide interoperability test scripts and a lab runbook mapped to pass/fail criteria.
- Confirm Site Classes & Constraints
- Agree densification phasing and show how it meets rollout cadence targets.
- Quantify installation time, structural constraints, and per-site incremental costs for small cells.
- Confirm energy and opex implications and acceptance KPIs for densified sites.
- Identify integration impacts and agree owners for addressing OSS/BSS changes.
- Seller to deliver site-by-site Gantt skeleton for densification (by site class) and a structural assessment checklist.
- Operator to provide access policies and permitting timelines for prioritized densification areas.
- Joint team to estimate required backhaul and power upgrades for the selected pilot area.
- Confirm Target Bands & BBUs
- Validate that multi‑band configurations meet the operator's KPI targets in lab/simulated conditions.
- Agree a concrete interoperability test list with pass/fail thresholds for each band and BBU type.
- Confirm field trial sites, KPIs, and decision triggers to scale to rollout.
- Ensure structural and energy impacts are quantified and owned for follow-up assessments.
- Introductions & Objectives
- Operator to nominate trial sites and provide BBU models and software release levels for interoperability testing.
- Joint team to schedule lab windows and tentative field trial dates, identifying required permits.
- Joint team to finalize trial SOW, dates, and sign the lab/field trial MoU.
- Executive One‑sentence Current State & Consequence
- Executive alignment to proceed (or not) based on the consolidated proof tied to the future-state outcome.
- Formal sign-off of KPIs, acceptance criteria, trial SOW and budget threshold to move forward.
- Assign clear owners and timelines for trial execution, lab verification and commercial negotiations.
- Agree communication cadence for status updates to CFO and board-level stakeholders.
- Seller to produce an executive summary pack (1–2 pages) mapping proofs to KPIs for board review.
- Operator to issue budget approval or a conditional budget trigger to start field trials.
- Assign named owners for each trial site, lab run, and commercial negotiation with target completion dates.
- Produce a single-sentence current-state diagnosis agreed by technical and commercial stakeholders.
- Quantify the consequence of the current state in operational and financial terms (high-level $/site, schedule risk).
- Agree a one-sentence future-state outcome and the success signals/KPIs to validate it.
- Identify data gaps and assign owners to deliver required inputs for scenario modeling.
- Operator to deliver anonymized site inventory, traffic forecasts, vendor split, and energy baseline files.
- Seller to produce initial baseline TCO model and example KPI dashboard template.
- Schedule Scenario #1 (Capacity Growth) workshop with RF planners and finance.
- Recap Current/Future State and KPIs
- Demonstrate measurable throughput and spectral-efficiency improvements for representative site types.
- Agree the quantified per-site TCO reduction and its sensitivity to core assumptions.
- Obtain operator validation of assumptions or capture required changes for re-run.
- Define immediate next steps: lab tests and candidate trial sites for capacity verification.
- Seller to deliver full simulation report with raw outputs and a TCO sensitivity table.
- Operator to confirm or correct traffic-growth and interference assumptions in the model.
- Jointly select 2–3 candidate sites for capacity field trials and schedule trial windows.
- One-sentence Current State
- Densification Sequencing & Rollout Cadence
- Scenario Assumptions & Inputs
- Proof Pack Summary
- Interoperability Constraints & Pass/Fail Criteria
- Multi‑Band RF Performance Mapping
- Installation Feasibility — Weight & Structure
- Simulation Walkthrough — Throughput & SE
- Consequence Quantification
- KPI Sign-off & Acceptance Criteria
- TCO Per-site Modeling & Sensitivity
- Energy & Opex Impact
- Structural & Energy Proof Points
- Commercial Roadmap & High‑level Volume Sensitivity
- One-sentence Future State
- Field Trial Scope & KPIs
- Tie Outcomes to Operator Problems
- Integration & OSS/BSS Impact
- Success Signals & KPI Agreement
-
Technical Evaluation & Trials
Plan and document lab benchmarks, interoperability tests, and field trials with clear KPIs, site types, and pass/fail criteria.
Evaluation Meetings
- Trials Kickoff & Success Criteria Alignment
- Lab Benchmark & Test Case Design
- Interoperability & Field Trial Integration
- Site Selection, Logistics & Safety Planning
- Trial Readout, Analysis & Go/No-Go Decision
- Introductions & Meeting Objectives
- Operator to provide baseline network counters and representative site inventory by class within 5 business days.
- Vendor to draft preliminary lab and field test timelines and resource needs for review.
- Assign workstream leads for Lab, Interop, Field and Analysis and circulate contact list.
- Recap KPIs & Acceptance Criteria
- Finalize a complete lab test catalogue where each test maps to one or more KPIs and acceptance thresholds.
- Agree measurement methods and instrumentation to guarantee repeatable, auditable results.
- Define the pilot run timeline and data/reporting templates for trial readouts.
- Vendor to deliver the detailed Lab Test Plan with test scripts and equipment list within 7 business days.
- Operator to confirm available lab resources (BBU licenses, SIMs, transport loops) and version constraints.
- Procure or allocate measurement instrumentation and reserve lab time slots for pilot and full runs.
- Prepare the reporting dashboard skeleton and agree reporting cadence.
- Current Interop Baseline (one-sentence)
- Approve an interop test matrix tied to KPI impact and identify owners for each scenario.
- Confirm required OSS/core interfaces, data feeds and monitoring points for field validation.
- Agree field configuration, change windows and rollback procedures to protect live traffic.
- Produce an Interop Test Matrix document with detailed steps and expected counters for each scenario.
- Operator to expose required OSS/core test interfaces and enable read-only counters for the trial period.
- Create site-wise configuration templates and rollback scripts for the field team.
- Nominate on-call triage contacts and escalation rota for the trial window.
- Recap Site Classes & Sample Targets
- Finalize the list of trial sites and confirm structural/power eligibility for each.
- Approve logistics, installation sequence and safety controls to minimize delays and incidents.
- Agree the exact sign-off evidence required per site class to prove acceptance.
- Operator to deliver final site access permissions and any local contact info for each candidate site.
- Field team to complete detailed site survey reports including structural calculations where needed.
- Order/confirm required mounting kits, cabling and backup power equipment for the first wave.
- Publish the site sign-off checklist template and train field engineers on evidence capture standards.
- Executive Summary of Trial Objectives & Future-State Target
- Arrive at a formal, documented go/no-go decision against the trial pass/fail criteria.
- Provide a clear remediation plan for any partial failures with owners and timelines.
- Produce the trial report and executive summary required for commercial and procurement teams.
- Publish the Final Trial Report including raw data, analysis scripts, and an executive one-page summary.
- If go: prepare technical annexes required for framework contract (site classes, licensing model, acceptance tests).
- If partial/no-go: create a prioritized remediation backlog with owners, test plan updates and re-test schedule.
- Schedule an executive briefing to present the outcome and recommended commercial approach.
- Create a shared, one-sentence current-state, consequence, and future-state that all parties accept.
- Agree on primary KPIs, site classes, pass/fail thresholds, timeline and decision gate owners.
- Assign owners for trial workstreams (lab, interop, field, analysis) and schedule the next detailed design meetings.
- Publish a one-page Trial Charter including current-state sentence, consequence, future-state sentence, KPIs and pass/fail thresholds.
- Lab Environment & Baseline Configuration
- Lab Benchmark Results vs KPIs
- Interop Test Scenarios & Matrix
- Candidate Site Reviews
- Current State (one-sentence)
- Test Case Catalogue Mapping to KPIs
- Consequence Statement & Business Impact
- Field Trial Results vs KPIs and Evidence
- Structural, Weight & Wind Load Constraints
- Core/OSS Integration Checklist
- Interoperability Incidents & Root Cause Summary
- Logistics: Equipment, Transport & Installation Steps
- Traffic Emulation & Subscriber Profiles
- Measurement Methodology & Instrumentation
- Future State & Success Signals (one-sentence + KPIs)
- Interoperability Scenarios in Lab
- Site Configuration Templates & Rollback Plan
- Trial Scope & Site Class Mapping
- Operational & TCO Implications
- Site Access, Permits & Stakeholder Notifications
-
Solution Scope
Define hardware modules, per-site licensing, integration responsibilities, acceptance tests, and rollout phasing across site classes.
Scope Configuration
- Deliver macro active antenna systems
- Install and mount antenna-radio units
- Terminate fiber and power connections
- Integrate radios with operator baseband
- Perform OTA beam calibration and tuning
- Activate carrier aggregation and beamforming licenses
- Enable per-site energy-saving modes
- Configure remote electrical tilt
- Commission sites and hand over to operator
- Collect drive-test RF KPI data
- Install small cells for densification
- Deploy millimeter-wave radio modules
- Supply mechanical reinforcement kits
- Provide spare parts and field replacement kits
Scope Questions
Deliver macro active antenna systems
- Do you require delivery of macro active antenna systems (AAS) as part of this rollout?
- Estimated number of macro AAS units required (total and by site class)
- Which antenna configurations are required?
- Which frequency bands will the macro AAS need to support?
- Are there delivery constraints (warehouse staging, customs, delivery windows, special packaging)? If yes, describe.
- Who is responsible for logistics and customs clearance for macro AAS deliveries?
Install and mount antenna-radio units
- Do you require installation and mechanical mounting services for antenna-radio units (ARUs)?
- What site classes will need ARU installation (e.g., rooftop, tower, pole, indoor)?
- Are there specific mounting interfaces or legacy mounts to accommodate (provide part numbers or drawings if available)?
- Do sites require single-person lift access, crane, or rope access for mounting?
- Are mechanical installation crews and safety certifications required to be vendor-approved/certified?
- Desired installation acceptance checklist items (mechanical torque, cable routing, grounding, labeling) or leave blank for standard checklist
Terminate fiber and power connections
- Do you require fiber termination and testing at each site?
- What types of fiber interfaces and connector types are present/required?
- Are there existing power feed characteristics (AC voltage, phase, backup UPS, diesel generator) to be used or modified?
- Should fiber links be OTDR tested and documented per site? If yes, specify acceptable loss/reflectance thresholds.
- Who owns fiber/power change coordination with local utilities (operator, vendor, third party)?
- Any site-specific power constraints (max draw per cabinet, generator run-hour limits, fuel logistics) to note?
Integrate radios with operator baseband
- Is integration with the operator's existing baseband and transport required?
- Which baseband vendors and versions are in scope for interoperability testing?
- Preferred backhaul interface (eCPRI, CPRI, Ethernet) and transport latency/bandwidth requirements?
- Do you require lab integration, vendor-provided integration engineering, or field integration support?
- Define success criteria for integration (S1 throughput, uplink/downlink KPI thresholds, connection stability duration)
- Are there security or network segmentation constraints for integration (VPNs, management VLANs, firewall rules)?
Perform OTA beam calibration and tuning
- Do you require over-the-air (OTA) beam calibration and tuning services for deployed AAS?
- Which site types require OTA tuning (macro urban, macro suburban, small cell indoor, small cell outdoor)?
- What KPIs define a successful beam calibration (per-sector throughput, SINR, coverage radius, handover success)?
- Should beam tuning be performed remotely, during a scheduled on-site window, or both?
- Do you require preservation of historical calibration profiles and rollback capability?
- Are there field measurement tools or operator-provided drive-test data we must use during tuning?
Activate carrier aggregation and beamforming licenses
- Will carrier aggregation and beamforming features be enabled via per-site licenses?
- Which features require licensing (carrier aggregation, advanced beamforming, MU-MIMO, dynamic spectrum sharing)?
- How should licenses be billed/assigned (per-site, per-sector, per-feature, pooled annual license)?
- Do you require trial or temporary feature activation windows for field validation?
- Are there governance requirements for license activation (approval flows, change windows, executive signoff)?
- Who will manage license keys and software entitlement (operator, seller, third-party license manager)?
Enable per-site energy-saving modes
- Do you want per-site energy-saving modes enabled (sleep modes, carrier shutdown, adaptive power control)?
- Which energy-saving strategies are of interest?
- Are there regulatory or service-level constraints preventing energy-saving measures at certain sites?
- What metrics should be tracked to measure energy savings (kWh per site, CO2 reduction, cost savings)?
- Should energy modes be centrally orchestrated or locally configured per site?
- Any dependencies on hardware or software versions for energy features (list versions if known)?
Configure remote electrical tilt
- Is remote electrical tilt (RET) required for the deployed antenna systems?
- Which sites/classes should have RET enabled (macro urban, suburban, rural)?
- Do you require scheduled tilt profiles (time-of-day, load-based) or manual control only?
- Who will be the change approver for tilt adjustments (RAN planner, field ops, vendor)?
- Should tilt changes be logged and auditable with rollback capability?
- Are there integration requirements between RET and OSS/NMS systems (provide system names/interfaces)?
Commission sites and hand over to operator
- Do you require full site commissioning and formal handover to the operator?
- What acceptance criteria must be met for handover (list KPIs, coverage, capacity targets, drive-test thresholds)?
- Which documents/evidence are required at handover (as-built drawings, test reports, certificates)?
- Who signs the acceptance certificate (operator RAN lead, project manager, vendor engineer)?
- Is there a warranty/defect liability period post-handover and what duration is expected?
- Are there phased handovers (per-site, per-cluster, per-region) or single bulk handover?
Collect drive-test RF KPI data
- Is drive-test RF KPI data collection required for acceptance and validation?
- Which KPIs must be collected during drive tests (throughput, RSRP, RSRQ, SINR, handover success)?
- Do you have preferred drive-test tools and formats (e.g., TEMS, Nemo, vendor tool) or should the vendor provide?
- Are static/crowd-sourced measurements (e.g., UE logs, MDT) required in addition to drive tests?
- What geographic coverage and measurement density are required (route km, number of samples per cell)?
- How should drive-test results be delivered and visualized (raw files, KPI dashboards, PDF reports)?
-
Mutual Commit
Resolve commercial terms, framework volumes, SLAs, warranty and software license models, and confirm executive sign-off criteria.
Agreement Modules
- Framework Agreement
- Volume Commitment & Ordering Schedule
- Statement of Work (SOW)
- Pricing Discounts & Escalation Schedule
- Service Level Agreement (SLA) & Performance Guarantees
- Warranty Spare Parts & Maintenance Agreement
- Software Licensing & Feature Activation
- Acceptance Criteria & Site Sign-off Protocol
- Field Trial & Pilot Agreement
- Logistics Delivery & Lead Time Commitments
- Installation Integration & Commissioning Responsibilities
- Change Order & Variation Process
- Governance Escalation & Executive Sign-off Criteria
- Payment Terms Invoicing & Financing
- Termination Exit & Decommissioning Plan
- Data Protection Security & IP Commitments
- Regulatory Compliance & Certification Commitments
- Insurance Indemnity & Liability
- Transition to Volume Rollout Handover
- Training Knowledge Transfer & Support Onboarding
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Confirm site access, structural assessments, integration inventories (BBU/core), logistics, and risk controls for the rollout start.
Readiness Questions
Opening: Who’s in the Room and How Quickly Must We Move?
- Which stakeholders will be actively involved in the RAN procurement and technical evaluation?
- Who ultimately approves the capital envelope and what is their primary decision driver?
- What is your target timeline from RFI to framework execution (select closest)?
- How would you describe your organization’s risk tolerance for adopting new RAN products or architectures?
- If there’s one timing constraint we must know about (regulatory deadline, spectrum award, seasonal window), briefly describe it.
Is Your Current Strategy Putting You at Risk?
- If we fast-forward six months, which single vendor decision today would force the most painful rework or cost escalation for your rollout?
- How is your current radio vendor split structured today?
- Which site classes make up the majority of your estate (select all that apply)?
- What supply-chain constraints are most likely to delay your rollout (select up to three)?
- How long have the supply or vendor-split issues been affecting your deployment planning?
What Keeps the Network Team Up at Night?
- Which single failure mode today would cause the biggest SLA hit or customer churn if it occurred at scale?
- Which technical areas are you most concerned about when evaluating radios?
- Please pick the top three technical KPIs that will decide vendor selection for you.
- Tell us about a recent incident where a site class underperformed — what happened, what was the operational impact, and how did your team react?
- How concerned are you about long-term vendor lock-in vs. short-term cost savings?
What If You Could Stop Worrying About This?
- Imagine the first 100 sites deploy with no integration rework and meet KPIs—what would that free your team to do next quarter?
- Which measurable outcomes would make you call the deployment a clear success?
- For each outcome you selected, what is the minimum acceptable threshold (percent improvement, absolute value, or timeframe)? Please list them.
- How should procurement trade off lower hardware price versus higher recurring software/license costs?
- How would achieving these outcomes change conversations with your CFO/board?
Where the Cost and Complexity Live
- What was the single 'hidden' cost in your last large RAN rollout that surprised external vendors?
- Which factors currently drive the largest share of site-level TCO for you?
- Which site types contribute disproportionately to your cost or risk profile?
- Describe an example where a site required unexpected structural or regulatory work — how long did it take, and what was the cost impact?
- How flexible are you to adjust mount or antenna specifications to accept a vendor’s integrated antenna-radio design?
Trials, Tests, and Tipping Points
- Would you be comfortable awarding a framework without field trials—what would give you that confidence, or why not?
- Which trial and test types are mandatory before you will sign a framework agreement?
- For live field trials, which site classes must be included (pick up to three)?
- What specific pass/fail criteria (KPIs with thresholds and durations) will you require for a trial to be considered successful?
- Who in your org will own trial orchestration, and which roles must sign off on trial results?
Decision Moments: When and How Will You Pull the Trigger?
- What is the single non-negotiable that would stop your team from moving forward with a vendor—even if performance targets were met?
- What level of executive sign-off is required to commit to framework volumes and multi-year rollouts?
- Which commercial terms matter most in final selection (rank by importance in your head and then select up to three)?
- How do you prefer to phase rollout across site classes?
- Are there procurement rules, local content requirements, or vendor qualification lists that could invalidate a vendor bid? Please specify.
What Would Success Look Like After Year One?
- If you could measure one headline metric after 12 months to prove the rollout was a success, what would it be?
- Which success signals will you report to executives (select all that apply)?
- What long-term support model do you expect from your chosen vendor after deployment?
- How would you like to maintain an ongoing, shared channel for issues and enhancements (choose preferred methods)?
- What would make you confident to continue expanding scope with a vendor into year two and beyond?
-
Deployment Enablement
Schedule site-by-site execution with Gantt sequencing, owners, installation steps, and escalation paths for multi-year rollout.
-
Validation Checklist
Execute acceptance tests, drive-test validation, energy and RF measurements, and capture sign-off evidence per site class.
Validation Questions
Starting Line: Who owns acceptance for this program?
- What's the deployment program name and who is the primary acceptance owner on your side (name, title, team)?
- Which teams will have a formal sign-off role during site acceptance?
- Do you already have an operator acceptance checklist template we should align to?
- What format does your program expect for sign-off evidence (pick all that apply)?
- Are there hard deadlines for acceptance after site build (e.g., within 7 / 14 / 30 days)? If yes, please specify.
If paper tests looked brilliant but customers still complained, what then?
- How confident are you that your current acceptance tests reflect real user experience and not just lab numbers?
- Which user-experience metrics matter most to your execs and subscribers (select top 3)?
- Tell us about a recent case where acceptance passed but the field experience was poor—what happened and why did it stick with you?
- How often do post-acceptance complaints trigger retrofits, re-optimization, or SLA disputes?
- What single change to acceptance testing would increase your confidence the most (e.g., longer trial windows, different KPIs, third-party verification)?
What does 'pass' actually mean — and who gets to define it?
- Do your pass/fail criteria favor headline KPIs, site‑class specifics, or do you use a blended approach?
- List the top three KPIs and numeric thresholds we must meet for acceptance (e.g., DL throughput per sector = X Mbps).
- How do acceptance tests differ by site class (macro urban, suburban, rural, rooftop, indoor, small cell)? Please describe differences or attach examples.
- Which of these tests are mandatory vs. advisory for a pass (choose all that are mandatory)?
- Who finalizes margin rules for marginal failures (e.g., 5% below target): operator, vendor, or joint agreement?
When tests disagree, whose numbers settle it?
- If lab benchmarks and field measurements conflict, which data source carries contractual weight for you?
- Do you require signed, timestamped raw data (traces, CSVs, PCAPs) to be uploaded for every acceptance event?
- Which file formats and tools must deliverables support (select all that apply)?
- Who is the defined neutral arbiter for disputed results today (name/role or 'none')?
- How long must raw test data and reports be retained for audit purposes?
Can we validate without breaking your live service?
- Will acceptance tests run in isolated test slices/labs or in the live network where there is user impact?
- Which sites or site classes can be isolated for stress tests (pick all that apply)?
- What blackout or peak windows must we avoid when scheduling validation drive tests or stress events?
- Do you require detailed rollback procedures and a contact for rapid remediation during any validation test?
- Who will own traffic steering, core changes, and subscriber experience during trials (roles and on-call contacts)?
Are energy and RF measurements binding contractual facts or nice-to-knows?
- Are energy-per-site and RF emission thresholds contractually enforced or advisory in your acceptance policy?
- What energy-per-site targets do you expect by site class (kWh/day, average power, or other unit)? Please specify for the main site classes.
- What RF exposure, EMC, or regulatory sweep checks must be included in acceptance?
- How should measurement uncertainty and instrument tolerance be treated when assessing pass/fail (e.g., ±x%)?
Who runs the tests and what do they need to succeed?
- Do you expect vendor test teams to execute validation, or will operator teams lead with vendor support?
- List required equipment, access rights and permissions for validation (e.g., drive vehicles, power meters, spectrum analyzers, remote SSH/BBU access).
- Will we need remote access to BBU logs, OSS/KPI dashboards, and core interfaces for root-cause analysis?
- What training, runbooks or shadowing do you require to hand over acceptance procedures to your operations team?
- Do you want a 'shadow acceptance' period where vendor continues to support accepted sites for a limited time?
If you only had one piece of evidence per site, which would convince your execs?
- Which of the following evidence bundles do you expect as the standard per-site deliverable?
- What level of photo/video documentation is required for mechanical and RF evidence (mast, cable routing, connector labels)?
- Do you require geo-tagged evidence and chain-of-custody records for hardware serial numbers and installation crews?
- Who will be the final signatory (title) for site acceptance in each region?
- What is your preferred artifact storage and access model for acceptance evidence (cloud repository, SFTP, operator OSS)?
Can you realistically validate hundreds of sites at the pace your rollout assumes?
- Do you have the crew, vehicles, and instrumentation to validate at your planned sites-per-week rate, or will you need vendor augmentation?
- What's your planned validation throughput (initial ramp vs. peak) in sites per week?
- Do you prefer sequential regional cutovers (one region validated then moved) or parallel validation across regions?
- If systemic issues are uncovered during bulk validation, what escalation path and SLA for root-cause do you require?
- What acceptance velocity would trigger commercial remedies or pause further rollout (e.g., >X% failures over Y days)?
Once a site is accepted, how long should we guard against surprises?
- Is acceptance permanent, or do you require a probation period (early-life performance window) after which acceptance is confirmed?
- What post-acceptance monitoring cadence and report format do you expect (daily, weekly, monthly)?
- If early-life failures occur, do you expect vendor SLA credits, remediation windows, or rolling fixes? Please specify preferred remedy model.
- Who owns long-term optimization, tuning, and software updates after acceptance (operator, vendor, or joint)?
- How should lessons learned during validation be captured and fed back into the rollout plan (format, cadence, owners)?
-
-
Success
Review delivery against success signals, confirm long‑term support model, and maintain a shared channel for issues and enhancements.
Success Reviews
- Success Review & KPI Reconciliation
- Long‑Term Support, Warranty & Commercial Ongoing Model
- Operational Escalation, Runbooks & War‑Room Playbook
- Enhancement Backlog, Roadmap & Shared Channel Governance
- Lessons Learned, Training & Continuous Improvement Plan
Issues & Enhancements
- Confirm release windows and change control process to avoid disruptions to live rollouts.
- Create a software license schedule (sites, features, renewal dates) and confirm pricing triggers.
- Escalation Matrix Review
- Ensure all operational teams can execute the runbooks and meet SLA response/repair targets.
- Configure monitoring thresholds and alert routing to avoid missed incidents or alert noise.
- Validate war‑room readiness and a repeatable post-incident improvement process.
- Update and publish final runbooks with named owners and escalation contacts in the shared channel.
- Implement agreed monitoring thresholds and alert routing in NOC tools and verify during next 72 hours.
- Schedule quarterly incident simulation exercises and assign facilitators.
- Shared Channel & Tooling Setup
- Create a single prioritized backlog in the shared channel with clear owners and SLAs for response.
- Agree quantitative prioritization criteria that link enhancements to operator success signals and rollout phases.
- Welcome & Objectives
- Administrator to provision shared workspace, import existing tickets, and assign initial access rights.
- Joint team to score and publish the top 20 backlog items with owners and target delivery windows.
- Schedule recurring monthly backlog governance meeting and circulate calendar invites.
- Retrospective: What Worked / What Didn’t
- Capture actionable lessons that materially reduce risk and cost for remaining rollout phases.
- Agree and schedule training deliverables to transfer operational knowledge to the operator team.
- Define measurable continuous‑improvement KPIs and reporting cadence tied to the operator's success signals.
- Produce and publish a Lessons Learned report with recommended process changes and owners.
- Develop a training schedule and materials for NOC and field teams with dates and trainers.
- Add continuous improvement KPIs to the QBR template and assign reporting owner.
- Establish clear pass/fail status against each agreed success signal for all representative site classes.
- Agree remediation plan, owners, and retest schedule for any unmet targets.
- Capture formal acceptance actions and timeline to move into long‑term support.
- Seller to deliver final consolidated KPI report with site-level evidence and annotated variances within 3 business days.
- Owner(s) to open remediation tickets for each failed KPI with target resolution dates.
- Schedule drive-test retest windows and responsible teams for any sites requiring re-validation.
- Support Model Overview
- Finalize and document the SLA and support tier that will apply to the live sites.
- Agree the physical spares strategy and RMA logistics that meet the operator's rollout risk tolerance.
- Confirm software licensing model, renewal cadence, and lifecycle commitments to avoid future commercial disputes.
- Produce a finalized SLA appendix and support statement of work for signature.
- Seller to provide spares inventory proposal and logistics lead times mapped to operator regions.
- Identify Process Improvements
- Backlog Review & Classification
- SLA Details & Performance Credits
- Package of Evidence Review
- Runbook Walkthroughs
- Prioritization Framework
- KPI Reconciliation by Site Class
- Monitoring & Alerting Configuration
- Warranty, Spares & Logistics
- Training & Knowledge Transfer Plan
- Root Cause & Impact Discussion
- War‑Room Simulation
- Release & Change Control Calendar
- Continuous Improvement KPIs
- Software Licensing & Feature Entitlements
- Continuous Improvement Loop
- Financial & Contractual Consequence
- Security & Lifecycle Policy
- Cadence & Roles for Backlog Governance
- Closeout Actions & Archive
- Governance & Executive Sign-off
- Decision & Next Steps