Zero-touch provisioning that actually works.
Ship an ONT to a subscriber. When they plug it in, NOS provisions it, binds it to their record, and lights up their plan — without a technician touching a config file.
Any operator scaling install volume or replacing an old ACS.
Provisioning is where most ISP toolchains go quietly wrong. ONTs get bound to the wrong subscribers, plans arrive out of sync, and the technician on the pole ends up SSHing into an OLT to fix it.
NOS ships a first-class TR-069 / TR-369 ACS inside the operating system. New devices phone home, are recognised against your inventory, matched to the correct subscriber, and configured against the plan they bought.
The Field Engineer App closes the loop on the physical side — signal readings, install photos and sign-offs land in the subscriber record before the technician has driven away.
Zero-touch provisioning is the outcome everyone claims and few deliver. The industry vocabulary — TR-069, TR-369, OMCI, RADIUS — is not the hard part; the hard part is that ZTP requires the ACS, the OLT, the AAA layer and the plan catalogue to reference the same subscriber identity. Without shared identity, ZTP is a scripting exercise.
Netxol collapses the identity problem. A CPE shipped to a subscriber phones home to the bundled ACS on first power-up; the ACS reads the subscriber plan from CRM; the OLT sees the ONT authorised via NMM; the RADIUS layer applies the correct policy. All four references resolve to the same identity because they share the graph.
The commercial payoff is truck-roll elimination on standard installs. Read the study at /blog/tr-369-usp-adoption-2026 for the technical detail and /solutions/tr-069-acs for the ACS-focused framing. Netxol NMM ships the ACS; Netxol Core X5 is the recommended tier for operators serious about ZTP at scale.
Firmware campaigns extend the pattern. Staged rollout (canary → 1% → 100%) with automated rollback on health regression converts firmware changes from a source of outages into a routine background activity. Every step writes to an immutable audit trail.
Four moves.
Native ACS in NOS
TR-069 and TR-369, protocol-complete, tuned for GPON and XGS-PON.
Inventory-first onboarding
ONTs are pre-bound at receipt — no field mismatches.
Plan-driven configuration
The plan the subscriber bought is the configuration they get. No scripts.
Field Engineer App
Signal tests, sign-offs and stock reconciliation from the pole.
Stage firmware campaigns
Canary → 1% → 100% rollout with automatic rollback on health regression.
Unify identity across ACS + OLT + RADIUS
Same subscriber, same ONT, same plan, same RADIUS policy — because they share the graph.
Everything you get with this playbook.
Operators already running this play.
Questions we get on the first call.
How long does it take to go live?
Small deployments complete in under a week from unboxing the Core to first paying subscriber; larger rollouts scoped in weeks not months.
Do we need to change our existing hardware?
No. NOS ships adapters for every mainstream OLT and router. You keep the gear you own; we replace the tooling above it.
What happens to our data?
Everything stays on your Core appliance by default. Backups go to your object store of choice. No subscriber data leaves your rack unless you turn on an opt-in telemetry channel.
Can we migrate from another platform?
Yes — we run a scoped migration project with matching data mappings and cut-over windows. Standard editions include the first migration.
Other stories in this shape.
Dispatch, route and close jobs from one screen — with GPS, signal tests and stock reconciliation built in. The Field Engineer App is the phone-side of NOS.
ReadOutcomeMost of what a NOC does at 3 a.m. is small, boring and repeatable. NOS is built to notice those patterns, act on them safely, and keep humans in the loop for anything that isn’t routine.
Read