For BSNL
Built inside a BSNL SSA, for BSNL SSAs.
FNW Flow was built alongside the Akola SSA fibre team. Every workflow exists because a field engineer or a JTO needed it to work that way. It runs on BSNL OLT estates as they actually are — not as a generic OSS imagines.
Origin
Built where the fibre is.
We didn't design this app at a desk. The new-connection wizard, the MOA fault clearance, the OLT pane — every flow came out of a real day on a real SSA. When something didn't fit BSNL's reality, we changed the app, not the process.
Why it fits BSNL
Speaks the network's own language.
- Trilingual core + nine more — every technician on the SSA reads home.
- VSOL · CDATA · OPTILINK — the OLTs SSAs actually run, on one pane.
- New Connection · MOA Fault · Order Clearance — the BSNL flow names, not generic synonyms.
- Every action is logged with role, timestamp, and SSA — auditable from day one.
FAQ
Common questions from BSNL teams.
Is FNW Flow an official BSNL product?
No. FNW Flow is a third-party operator app built by Fiber Network Works alongside an approved pilot in an Akola SSA. It is not endorsed by, affiliated with, or branded by BSNL beyond that specific pilot.
Which OLT vendors does it support?
VSOL, CDATA, and OPTILINK out of the box — the OLT vendors most BSNL SSAs actually run. For an unknown vendor, the AI onboarder learns the login and ONU table itself, so you can operate it without waiting for a driver release.
Does it talk to the actual BSNL provisioning system?
Yes. The new-connection flow submits to BSNL's provisioning endpoint, fault clearance posts to /foa/taskHandle/complete/v1, and the flow names — New Connection, MOA Fault, Order Clearance — match the BSNL workflow names rather than generic OSS synonyms.
What language coverage is there for technicians?
English, Hindi, and Marathi are shipping. Nine more Indian languages are on the roadmap — every technician on the SSA reads home, not in a second language.
How auditable is it for BSNL compliance?
Every action is logged with the operator role, timestamp, and SSA. Lead, fault, and provisioning events are written to an append-only audit log usable from day one.