Summary

  • Ericsson confirmed a contract with Instituto Costarricense de Electricidad to deploy a 5G Standalone network for its Kölbi brand.
  • The scope covers a dual-mode 5G core, 4G and 5G radio access, LTE expansion, slicing, cybersecurity, standard interfaces and management capabilities.
  • Ericsson Intelligent Automation Platform will be used across open, multi-vendor and multi-technology network domains.
  • ICE initially plans to trial selected AI-powered anomaly-optimisation rApps; a trial is not evidence of production performance.
  • The core and RAN award, reported at approximately $98 million, survived July appeals, while separate backhaul lots were annulled for renewed analysis.
  • The award was known in April; the August advance is Ericsson’s confirmation and fuller scope, not a completed nationwide rollout or commercial launch.

Winning equipment lots is not operating a network

The procurement reached its award stage in April and Costa Rica’s comptroller maintained the core and RAN result after appeals in July. Ericsson’s new confirmation moves the lifecycle forward by describing what it will supply, rather than creating a new August award.

That distinction matters because a signed scope must still pass design, delivery, integration, acceptance and commercial activation. None of the captured sources supplies a nationwide launch date, coverage map or subscriber migration result.

Core and radio create the Standalone foundation

Ericsson says the package includes its dual-mode 5G core, 4G and 5G RAN products and an LTE radio expansion. A Standalone core can support capabilities such as slicing without depending on a 4G anchor, while LTE expansion preserves the network that existing devices and services still use.

The contract therefore combines transition and destination. Its success cannot be measured by a single 5G site count: coexistence, handover, service continuity and migration all matter.

EIAP extends control beyond one vendor’s equipment

The Ericsson Intelligent Automation Platform is intended to manage open, multi-vendor and multi-technology networks through standardised interfaces. Ericsson calls this the first EIAP deployment in Latin America, a vendor attribution rather than an independently established regional census.

The promise is operational: give ICE one layer from which to observe and optimise heterogeneous domains. The risk is equally operational—data models, permissions, interfaces and responsibility for recommendations must work across vendor boundaries.

The first rApps are experiments with bounded authority

ICE will initially trial selected AI-powered rApps for anomaly detection, optimisation and resilience. “Initially” and “trial” define the state. They do not show that automated actions are running nationwide, that faults are prevented or that performance has improved.

A sound trial should record its network segment, baseline, recommendation accuracy, false positives, human approval rules and rollback. Without those, an AI label says little about operational value.

Slicing and cybersecurity need service evidence

Network slicing and built-in cybersecurity appear in the stated scope. Slicing becomes commercially meaningful only when ICE defines service classes, resource isolation, assurance measures and customers. Security becomes credible through architecture, access controls, testing and incident evidence.

Neither capability should be treated as delivered merely because it is supported by the purchased platform. Contract language describes an available surface; acceptance data shows whether it works in Kölbi’s environment.

The $98 million boundary excludes backhaul

Independent procurement reporting puts the maintained core and RAN award at about $98 million. The comptroller separately annulled backhaul lots for renewed analysis. Combining those lots would distort both scope and price.

Backhaul nevertheless remains a dependency. Radios and a new core cannot produce end-to-end performance if transport capacity, redundancy and timing are unresolved. Its separate procurement path should be monitored without attributing it to this confirmed Ericsson package.

Proof begins at acceptance and continues in service

Useful milestones include delivered equipment, integrated domains, accepted core functions, completed rApp trials, live Standalone traffic and published service performance. Later indicators should cover availability, latency, coverage, migration, slice assurance and security events.

Until those appear, the contract is a technically detailed commitment. It makes ICE’s intended control architecture visible, but not yet its performance.

Sources