Phase 1 of 6
Scoping & Energy-SLA Constraints
Define the energy-saving levers in scope, the network KPI envelope optimization must not breach, and the ESG and grid constraints that frame every downstream architectural decision.
0/9
Phase Progress
Required Recommended Optional Open-Source Proprietary Trinidy
Optimization Levers & Site Portfolio
Identify energy-saving levers in scope
Why This Matters
Each lever has a distinct actuation interface, safety envelope, and payoff profile — a model that bundles them into one reward function tends to over-optimize the easy levers and leave the high-value ones untouched. 3GPP Release 17 and Release 18 introduced the symbol-, channel-, carrier-, and cell-level sleep primitives that most AI energy systems now actuate, but operators frequently enable only the conservative subset. The scope decision should be explicit, not an emergent property of whichever lever the vendor integrates first.
Note prompts — click to add
+ Which levers are actuator-ready today (API/CLI available from the RAN or site controller) versus gated on a vendor upgrade?+ Have we modeled the per-lever expected saving so we can prioritize integration sequencing?+ Are sleep-mode levers scoped per 3GPP Release 17 or Release 18 capability of the installed base?Confirm which per-site optimization levers the model(s) will actuate.
Select all that apply
Define site archetypes in the deployment portfolio
Why This Matters
Industry benchmarks put a typical macro site at roughly 15–30 MWh/year, but diesel-hybrid and off-grid sites can run 2–5x that with generator fuel dominating the cost structure — and the optimization math flips: fuel scheduling dominates sleep-mode gains. Small cells and rooftops have negligible cooling load and different MIMO profiles, so a single-model approach trained on macro data will underperform on them. Archetype segmentation is a first-order decision because it drives how many distinct models you will train and operate.
Note prompts — click to add
+ What is our site-count distribution across archetypes and which bucket contributes the most OpEx?+ Do we have separate labeled datasets per archetype or only a portfolio-wide pool?+ Are diesel-hybrid sites handled by the same team and toolchain as grid-connected ones?Different site types have entirely different thermal, power, and traffic profiles — model architecture depends on which mix is in scope.
Select all that apply
Establish network-KPI guardrails (no-degradation envelope)
Why This Matters
Every published operator deployment — Vodafone/Ericsson, DT/Nokia, MTN/Huawei — emphasizes that measured energy savings are only acceptable at zero or near-zero KPI degradation, and that the KPI envelope must be hard-enforced in the optimization loop rather than treated as a soft reward penalty. Without explicit guardrails, a model will happily trade 2% throughput for 5% energy because the reward function told it to. The guardrails also anchor A/B test success criteria — you cannot evaluate an experiment without them.
Note prompts — click to add
+ Which KPI breaches trigger immediate rollback of the optimization action vs. passive logging?+ Have network operations, not just the energy team, signed off on the guardrail set?+ Are guardrails the same at 3 AM and at the busy hour, or do they need time-of-day variation?Energy optimization must not breach service KPIs — set the envelope before the model is trained.
Select all that apply
Define target energy-saving range and baseline
Why This Matters
GSMA Intelligence reports a median 15% per-site saving across member operators, with an outer band of 20–25% on diesel-heavy portfolios where generator dispatch and solar integration dominate — targets should be anchored to your portfolio mix, not the headline number. Without a locked baseline window (typically 30–90 days of pre-deployment metering at the same site, same season), you cannot defend the saving to finance or ESG reporting. Setting the target before the baseline is one of the most common causes of stalled ROI reporting.
Note prompts — click to add
+ What is our formal baseline window definition — calendar, methodology, and normalization factors?+ Do we normalize savings by traffic volume, weather, and season, or report absolute kWh?+ Who signs off on the baseline methodology — finance, ESG, or network ops?Set the saving target against a measurable baseline period — without a baseline, savings are unfalsifiable.
Single choice
Establish inference latency envelope per lever
Why This Matters
Latency budgets for RAN energy actions are fundamentally constrained by 3GPP signaling timescales — symbol and channel shutdown operate at sub-second granularity, cell DTX at seconds, and cooling or generator dispatch at minutes. A single cloud-hosted inference loop cannot serve the faster tiers without round-trip variance wiping out the savings. Operators that collapse everything into a 5-minute cadence typically achieve only the cooling and generator share of savings and leave sleep-mode gains on the table.
Note prompts — click to add
+ Which levers in our scope require sub-second or seconds-scale inference, and does our planned topology meet that?+ Are we willing to run multi-tier inference (on-node fast path plus centralized slow path) or only one cadence?+ What is our measured end-to-end latency today from metric ingestion to actuator response?Select the dominant latency tier — different levers need different inference cadences.
Single choice
Trinidy — Cooling and generator decisions tolerate minute-scale latency, but RAN sleep-mode actuation on Release 18 cell DTX must respond within seconds of traffic drop-off. Trinidy runs the full model stack on-node, eliminating cloud round-trip variance that otherwise prevents aggressive sleep-mode policies.
Map ESG and carbon-accounting scope
Why This Matters
The GHG Protocol splits tower-operator emissions across Scope 1 (on-site diesel), Scope 2 (grid electricity), and Scope 3 (leased space at tower-co sites) — and the same kWh saving lands in different scopes depending on site ownership structure, which materially changes how it is reported. SBTi-aligned operators have committed to absolute reduction targets and need AI-saving data wired into their inventory, not just dashboards. ISO 50001 certification adds an auditable management-system overlay on top of the measurement.
Note prompts — click to add
+ Have we mapped each site archetype to the correct scope category?+ Is our ISO 50001 energy review up to date, and is the AI system included in the energy performance indicators?+ Does our SBTi or CSRD submission pathway accept AI-verified savings, and what evidence does it require?Confirm which sustainability frameworks the saving must be reported against.
Select all that apply
Identify grid and critical-infrastructure constraints
Why This Matters
NERC CIP-002 through CIP-014 cover cyber and physical security for Bulk Electric System assets, and any automated load-dispatch system that interacts with BES-registered sites can be drawn into scope — a distinction many telco teams discover only at audit. FERC Order 2222 opens wholesale participation to distributed energy resources, which creates an optionality most tower portfolios have never monetized. Mapping these constraints before architecture is locked avoids a rework cycle later.
Note prompts — click to add
+ Do any of our sites host or interface with BES-registered equipment, triggering NERC CIP scope?+ Have we evaluated FERC Order 2222 monetization of battery and generator assets?+ Does our utility offer interruptible tariffs the AI could opportunistically serve?Where sites are on-grid or co-located with bulk-power assets, NERC and FERC rules can apply to load-control decisions.
Select all that apply
Confirm data residency and network-sovereignty constraints
Where are site telemetry, RAN configuration, and energy data allowed to flow?
Select all that apply
Trinidy — RAN configuration and energy telemetry often fall under national-infrastructure residency rules. Trinidy runs the full optimization loop on-site or in-country, keeping telemetry, model state, and actuation commands entirely within the operator's perimeter.
Select deployment topology
Physical location of the inference runtime.
Single choice
Trinidy — For sub-second RAN sleep-mode actuation and zero cloud dependency during backhaul outages, on-site inference is the only viable topology. Trinidy nodes run at under 50W — the inference substrate does not consume the savings it produces.