GLabNetOps is GLab Enterprise’s ISP operations and network management web app. It brings customer and service workflows, broadband information, network maps, fibre planning, device monitoring and staff administration into one operational workspace. ISP teams can use it to organise everyday service work, understand how customers connect to network assets, plan fibre routes and investigate device or service issues.
Public product overview · Private source repository · Updated 5 November 2026
ISP operations
Broadband management
NetVision
GIS & fibre planning
NMS
OLT & ONU visibility
The product
One operational workspace for the ISP side of the network
An ISP works across two closely related areas: the services customers receive and the infrastructure that carries those services. GLabNetOps is designed to give staff useful views of both. Customer and service records support day-to-day administration, while network maps, fibre-planning tools and monitoring views help teams understand the physical network and investigate service conditions.
The application includes a public-facing ISP website and broadband catalogue, authenticated staff workspaces, network-operations tools and administrator controls. It is intended to make information easier to find and operational follow-up easier to organise—not to replace engineering judgement or claim that every task is automated.
Main capabilities
What you can do with GLabNetOps
The following areas describe features present in the application and the work they are intended to support. Some functions need local setup, suitable network data or equipment-specific validation before they can be relied on in an ISP environment.
01 · Public ISP presence
Publish services and broadband plans
Maintain ISP-branded public pages, service information, help content and a publishable broadband-plan catalogue. Plans can describe speeds, prices, billing periods, allowances, installation charges and conditions without inventing offers for the provider.
Public request, request-tracking and receipt-verification pages can support customer contact and follow-up where enabled.
02 · Customer operations
Keep customer and service records organised
Maintain customer profiles, service connections, account references, contact and location details, network assignments and operational history. Staff can work with customer, service and connection records from permission-controlled workspaces.
Receipt records and historical account snapshots help retain operational context; they are not an automated billing ledger.
03 · Day-to-day operations
Coordinate work and operational records
Manage work orders, inventory, service-related records, customer requests, receipts, staff notices and operational follow-up. Searchable staff workspaces provide a place to review and update the information needed to move work forward.
04 · Network visibility
Explore infrastructure with NetVision
View mapped network assets and their physical relationships, including upstream links, points of presence, OLTs, joints, closures, splitters, FAT/FDB access points, fibre segments and customer endpoints. Search and inspect map features to understand where network assets and service endpoints are located.
Permission controls restrict access to customer-identifying details in network views; administrators can also use versioned topology import and export workflows.
05 · GIS and engineering
Plan fibre routes and review optical budgets
Draw and measure network routes, record fibre segments and their characteristics, and estimate route distance and optical loss using mapped cable, splice, connector, splitter and engineering-margin inputs. These calculations help with planning and review before field work.
Route lengths and optical budgets are planning estimates until checked against surveyed routes, actual components and field measurements.
06 · Network monitoring
Review device, OLT and ONU status
Use the monitoring worker, scheduled read-only SNMP polling and a normalized telemetry path to collect supported device information. The application maintains OLT configuration and ONU/ONT records, stores optical samples and exposes device-health and collection-status information for operational review.
Normalization adapters cover Huawei, ZTE, VSOL, C-Data and Syrotech data formats; a vendor name alone does not certify every model or firmware combination.
07 · Fault investigation
Turn selected monitoring events into incident context
For defined groups of ONU loss events on the same OLT and PON, the incident engine can correlate events, show affected devices and linked customers, and use mapped fibre paths to suggest a shared area to inspect. Staff can record the confirmed cause and repair separately from the system’s initial assessment.
This is rule-based decision support, not an AI diagnosis or an automatic repair process.
08 · Staff and administration
Manage access and application settings
Use authenticated staff and administrator areas to manage operational records, public-site content, setup and configuration. Role- and permission-based access keeps internal customer, network, monitoring and administrative information separate from public website pages.
In everyday use
How an ISP team can use it
Customer service
Review a customer or service request
Find the customer and service records, check the recorded connection and location, review related operational information, and record the next action or work order for the appropriate staff member.
Network operations
Investigate a device or access-network issue
Review the latest available device and optical data, check alerts or a correlated incident, then open NetVision to inspect the affected OLT, PON and mapped fibre path. The map and telemetry provide investigation context; staff still verify the fault in the field.
Fibre planning
Prepare a route or network extension
Place or review network assets, connect the planned route, inspect calculated distances and optical-budget estimates, and use the result as an input to a site survey and engineering decision.
ISP administration
Keep public service information current
Update provider pages and publish the broadband plans and service information that customers should see, while staff continue to manage customer and operational records inside the authenticated workspace.
Why it is useful
Practical benefits for ISP operations
Better shared context: customer records, service work, network assets and monitoring information are available through related areas of one application.
Clearer network visibility: staff can connect a service location with mapped access-network infrastructure instead of relying only on free-text notes or separate diagrams.
More informed planning: route-distance and optical-budget estimates make assumptions visible before a fibre job is taken to the field.
More focused fault investigation: device observations and mapped topology can help narrow where staff should inspect, without pretending to replace technician confirmation.
Controlled access: public information is separated from internal operational data, with permissions governing access to staff and customer details.
Configurable operational foundation: the application can be adapted to a provider’s records, network structure and deployment environment, subject to setup and validation.
Find customer and service details, review requests, and coordinate follow-up with operational staff.
NOC and network operators
Review device status, OLT/ONU information, alerts and mapped network context during fault investigation.
Field and fibre-engineering teams
Inspect mapped assets, plan routes, review fibre characteristics and use optical estimates as preparation for site verification.
Clear product boundaries
What is included—and what still needs validation
GLabNetOps is an evolving application. The features above describe capabilities present in the current codebase, but availability in a particular ISP installation depends on configuration, data quality, deployment and testing.
Important things to understand
Monitoring is scheduled: SNMP polling runs on configured intervals. It is not push-based streaming or an instant view of every network change.
Hardware support is specific: OLT/ONU collection must be checked against the exact vendor, model, firmware, OIDs and real equipment. An adapter or simulator test is not universal hardware certification.
Network changes are not automated: monitoring paths are read-only or telemetry-ingestion oriented. GLabNetOps does not automatically provision ONUs, change VLANs, reboot equipment or repair a fault.
Billing is not automated: the broadband catalogue is informational. Automated subscription billing, payment collection and accounting are not current capabilities.
Engineering estimates need field checks: map-based routes and optical budgets depend on the accuracy of entered assets and measurements; they are not a substitute for a physical survey or instrument readings.
Incident support is rule-based: selected bulk-loss patterns can be grouped into explainable incidents, but automatic work-order creation, customer outage messaging and machine-learning fault prediction are not current features.
The purpose of this page is to introduce the product and its practical uses. Deployment steps, API details, data models and hardware-acceptance procedures belong in the separate engineering documentation.