Network Operations · Project case study
Noney BSNL Broadband NMS
An independently developed broadband operations platform that centralized customer service, network monitoring, infrastructure planning, mapping, and administrative workflows for a rural BSNL franchise.
Status · Completed · production retired
Context
Software shaped by day-to-day rural broadband operations.
The platform grew from practical challenges in a newly established broadband franchise with limited infrastructure, operational support, and dedicated software. Manual customer, fault, planning, and documentation processes were brought into one web-based system.
Platform
One operational workspace across service and infrastructure.
- Customer information, requests, notices, and public service delivery
- Administrative records, complaints, reporting, configuration, and audit logs
- Broadband latency, connectivity, and network-health monitoring
- GPON/OLT and fiber-infrastructure documentation
- Geo mapping, route measurement, topology visualization, and installation planning
Deployment
A stable public gateway to a local operational system.
The production Python application ran on a local office server connected to the operational broadband environment. GitHub Pages provided a permanent public gateway, while JSON configuration and status checks selected a dynamic tunnel or maintenance state.
This architecture allowed a stable public entry point without exposing the office server directly as a permanent public endpoint.
Architecture
Public gateway, local application, and operational infrastructure.
- GitHub Pages supplied a stable public entry point and maintenance experience
- redirect-config.json described prioritized endpoints, retries, delays, and status messages
- A dynamic tunnel connected the public gateway to the locally hosted Python application when available
- The application centralized customer services, administration, network monitoring, infrastructure documentation, and reporting
- Geo mapping and NetVision represented fiber routes, splitters, endpoints, cable lengths, service areas, and network hierarchy
- Private source, credentials, customer records, topology, OLT configuration, and internal deployment details remained outside the public portfolio repository
Validation
Portfolio verification without reconnecting the retired production environment.
- Serve the repository locally and verify the gateway, maintenance state, error page, icons, messages, and screenshots
- Validate redirect-config.json and ensure public builds contain demonstration-safe endpoints only
- Review desktop and mobile presentation
- Confirm documentation consistently identifies the production server as retired
- Check that customer records, credentials, internal topology, OLT configuration, private server code, and deployment secrets are absent
Outcome
Completed, production-tested, and preserved as a portfolio system.
The documented production deployment is now retired. The public repository preserves the gateway, screenshots, demonstration material, architectural description, and workflow evidence while deliberately excluding customer data, credentials, internal topology, server configuration, and private production source.
Public documentation demonstrates the system without exposing production data or sensitive infrastructure details.
Publication note
Static, crawlable case study.
This page contains the substantive project description directly in HTML. The existing GLab project catalogue and JavaScript interface can continue to operate independently.