Skip to main content
A municipal fiber build opens a new subdivision with 64 pre-sold subscribers. The ISP runs the full deployment inside Studio: OLT configuration, splicer dispatch, subscriber records in the BSS, service profiles on the RADIUS server, install tickets auto-issued, and subscriber welcome emails timed to each install. Treat each subscriber activation as a support request with an owner, a provisioning plan, a verified service test, and a welcome response. An agent can coordinate records, appointments, missing information, and completion evidence; operators handle the infrastructure steps that require local access. Define the available actions and handoffs in the support loop.

​
Systems involved

​
Technical playbook

1

Plan the PON tree

Copilot imports the FAT plan: 2 splitters, 1:32 ratio, 64 planned drop fibres. The OLT and PON port are picked from available capacity. The plan becomes a Studio diagram with subscriber IDs at each drop.
2

Order the ONTs and drop cables

The procurement connector orders 64 GPON ONTs and the splice-on-connector drops. The shipment tracking lands in the project channel.
3

Pre-provision the OLT

SSH into the OLT. Copilot stages the PON port config, the splitter entries, and the bandwidth profiles for the service tiers. Stage appears in the staging panel, reviewed, pushed.
4

Splicer dispatch

Schedule the splicer through Google Calendar with the FAT records attached. The splicer is briefed with which subscribers map to which ports and which fibers are reserved.
5

Subscriber records in BSS

Through the Splynx connector, create 64 subscriber records with service product, static IPv4 mapping, IPv6 prefix delegation, and contact details — all from the pre-sale CSV the sales team handed over.
6

RADIUS profiles

The BSS push writes to RADIUS automatically. Copilot spot-checks five subscribers to confirm the bandwidth rate-limit, the static framed-IP, and the session-timeout match the service tier.
7

Install ticket per subscriber

Generate one install ticket per subscriber in the PSA. Each ticket carries the ONT serial, the drop number, the subscriber’s contact, the scheduled window, and the install procedure.
8

Install day

As each install tech activates an ONT, Copilot watches the OLT for the ONT registration, marks the ticket in-progress, and when RADIUS authenticates the session, fires the subscriber’s welcome email through Gmail with login, portal URL, and WiFi default credentials.
9

Close the project

At the end of the go-live week, generate the deployment report: 64 subscribers, first-login rate, install-duration distribution, exceptions. PDF to the project sponsor, and the runbook is saved for the next tree.

​
Support outcome

  • Each subscriber record links the physical install, provisioning result, and service verification.
  • The customer receives go-live information when their service meets the activation criteria.
  • Failed activations remain owned support cases with the installation and test evidence attached.

Hosts and credentials

OLT and per-subscriber ONT inventory with folder structure.

Procedures

New PON tree provisioning with the tree ID as the argument.