Skip to content

Zero-touch provisioning for radio network devices

New sites go from installation to carrying traffic without a manual configuration step. x101 reads the plan, generates the device configuration from approved vendor templates, validates it against the live network, and commissions it under approval.

Example scenario · Telecom

Function
Network rollout and commissioning
Systems
Planning, inventory, element managers, ticketing
Deployment
On-premises or private cloud
Human control
Approval before anything reaches a live device

Last updated: 22 September 2026

The challenge

Rolling out radio sites at scale is limited less by hardware than by the configuration work around it. Every device needs settings derived from the plan, matched to its vendor and generation, checked against the live network, and recorded, and today most of that is careful manual work under time pressure.

  • Configuration written by hand, site by site

    Engineers derive parameters from planning documents for every device, which is slow and produces variation between sites that should be identical.

  • Every vendor does it differently

    A multi-vendor estate means multiple command sets, templates and conventions, and the knowledge of each lives with a handful of specialists.

  • Errors found after the crew has left

    Mistakes surface during commissioning or after go-live, when fixing them means another visit and another maintenance window.

  • Records assembled after the fact

    What was configured, by whom and against which plan version is reconstructed later, which makes rollout audits slow.

What x101 does

The same platform capabilities that run in production elsewhere, applied to this work. Each step below is standard platform behaviour, not custom development.

  1. The plan, read directly

    x101 reads the design and planning output alongside inventory and the current network state, so the intended configuration and the live reality sit in one picture.

  2. The configuration, generated

    Device settings are drafted from approved vendor templates and past commissioned sites, with every value traceable to the plan or the standard it came from.

  3. Validated before it ships

    Parameter conflicts, neighbour relationships, capacity assumptions and policy rules are each checked against the live network state before anything is sent to a device.

  4. Commissioned under approval

    The approved configuration is applied through the operator's own automation, inside blast-radius limits, with every action logged and reversible.

  5. Verified on air

    Post-commissioning checks confirm the site behaves as designed; anything outside tolerance is raised as an exception with evidence.

  6. Each site teaches the next

    Corrections, overrides and commissioning outcomes feed the templates, so the generated configuration improves with every rollout.

Governance runs across every step. Each request carries the permissions of the person asking, actions follow the policies you set, high-impact steps wait for human approval, and every decision is written to a signed, replayable record.

What gets measured

These are the measures a deployment of this scenario is held to. Figures are published on this page once a live deployment has produced them.

Baseline and target

Agreed before the first week

  • Elapsed time from installation to carrying live traffic
  • Share of sites commissioned without a repeat visit
  • Configuration errors caught before they reach a device
  • Engineer hours per commissioned site

How rollout works

A first use case live in weeks

  • Inside your perimeter. Your cloud, your access controls and your data, from day one.
  • Works with what you run. x101 reads the systems you already have, as they are today.
  • Paired with a solutions engineer. Someone who has deployed this before works alongside your team.
  • Measured against your baseline. The numbers that matter are agreed up front and reported against.

The parts of x101 this uses

Every capability below already runs in production. This scenario applies them to a different kind of work.

  • Unify

    Planning output, inventory, element managers and the live network state read as one picture.

    Explore Unify
  • Company Knowledge

    Vendor manuals, approved templates and past commissioned sites ground every configuration.

    Explore Company Knowledge
  • From Answer to Action

    The configuration is not only drafted, it is validated, applied and verified in the same flow.

    Explore From Answer to Action
  • AI Explainability

    Every parameter traces back to the plan or standard behind it, with the full trail preserved.

    Explore AI Explainability
  • Governed by Design

    Approval gates before anything touches a live device, and a signed record of every step.

    Explore Governed by Design
  • No Vendor Lock-in

    Runs on the operator's own premises, with models that never leave the estate.

    Explore No Vendor Lock-in

Bring zero-touch rollout to your network.

Plan-to-live commissioning with generated configuration, live validation, governed execution and a complete record, deployable entirely on your premises.