Device records drift
OLT, ONU and subscriber records can fall out of sync when inventory and service changes live in separate tools.
Deployment playbook · FTTH
A practical operating model for faster, more consistent FTTH service delivery
See how an FTTH team can connect OLT and ONU operations, subscriber lifecycle, billing and incident response in one controlled workflow.
Illustrative scenario
The operating context
This scenario is designed for an FTTH operator managing subscriber growth across one or more OLT vendors while network, field, support and billing teams need the same service context.
OLT + ONU operations
Provisioning controls
Fiber diagnostics
Subscriber lifecycle
Important: this is a deployment playbook, not a named customer case study. The outcomes below are targets to validate in your environment, not measured customer results.
Before the rollout
Where the operating model breaks down
These are the handoffs the deployment should make visible and repeatable.
Provisioning varies by technician
Manual device steps create avoidable differences between new installations, replacements and plan changes.
Fault evidence arrives late
Support and field teams lose time assembling topology, optical and subscriber history before they can isolate a fault.
Target state
One service record, shared operational context
A subscriber record becomes the shared operational thread: the assigned ONU and OLT, service plan, billing state, location and support history stay available to the teams responsible for the service.
End-to-end workflow
How the target workflow operates
Move each service through a visible lifecycle, with clear ownership from network discovery to ongoing support.
Discover and map
Register OLT and ONU context, then connect network inventory with subscriber and location records.
Apply a controlled setup
Use supported provisioning workflows and repeatable plan settings for activations, replacements and changes.
Align access and billing
Keep subscriber service state and billing actions visible in the same operational flow.
Investigate with context
Review topology, device diagnostics and subscriber history before dispatching or changing the service.
Capability to evidence
What supports the operating model
The playbook is based on these existing ISPbills capabilities. Your exact device actions depend on the supported model and deployment configuration.
OLT and ONU operations
Discover supported devices and manage provisioning tasks from a shared operator console.
GIS service context
Relate subscribers, routers and OLT infrastructure to the places where service is delivered.
Fiber diagnostics
Bring supported device and optical signals into the investigation workflow.
Billing lifecycle
Connect plan, invoice and service status so teams can see commercial and network context together.
Scoped operator access
Limit sensitive actions by role and retain accountability for operational changes.
Support history
Keep incident handling connected to the subscriber and service record.
Rollout and risk controls
Introduce change in verifiable phases
Prove the full service path on controlled records before increasing device, subscriber or team scope.
01 · Baseline
Map the current stack
Document OLT models, ONU inventory, plan rules, subscriber identifiers and team ownership before configuration begins.
02 · Pilot
Prove one service path
Test discovery, activation, plan change, suspension and fault handling on a controlled group before wider use.
03 · Cutover
Move with checkpoints
Reconcile imported records, restrict high-risk permissions and define who approves each production change.
04 · Stabilise
Review exceptions
Track failed actions, mismatched inventory and repeat incidents; refine the runbook before expanding scope.
Validation criteria
Operational outcomes to test
Set a baseline before rollout, define an owner for each target and validate the change with your own operational data.
Target
Repeatable activations
Technicians follow the same verified service path instead of rebuilding each activation from memory.
Target
Earlier fault isolation
Support begins with subscriber, topology and device context already connected.
Target
Cleaner team handoffs
Network, field, support and billing teams work from a shared service record.
Target
Controlled change history
Roles and operational records make sensitive actions easier to review.
Continue your research
Product, integration and planning resources
Scenario FAQ
Questions to resolve before rollout
Is this a real customer case study?
No. It is an illustrative deployment scenario based on ISPbills product capabilities. The outcomes are operational targets, not published customer measurements.
Can every OLT and ONU use the same workflow?
The operating pattern can be consistent, but available discovery, provisioning and diagnostics depend on the supported vendor, model and firmware. Confirm your device stack during deployment planning.
What should an FTTH pilot include?
Include a representative OLT and ONU set, new activation, plan change, suspension, replacement and fault investigation. Reconcile every result before expanding the rollout.
Can billing and network access be introduced in separate phases?
Yes. A staged rollout can reduce risk. Define the source of truth and approval owner for each phase so service and billing state do not drift.
Next step
Turn the scenario into your rollout plan
Bring your device stack, access model, subscriber lifecycle and team responsibilities. ISPbills can help map a controlled pilot around the workflow you run today.
Start running your ISP on a platform your team will actually use
Start a free trial today — no credit card, no commitment.