Multi-vendor OLT management. NOC map with live device status. Signal levels inside the customer ticket. OTDR overlays for repair validation. The agent never leaves the ERP to see whether the ONU is healthy.
Most ISP platforms claim "integrated network monitoring." What they mean is: a button that opens the OLT vendor's own console in a new browser tab. The agent leaves the ERP, navigates the vendor UI, copies the relevant data back as a screenshot, pastes it into the ticket. That is not integration. That is two systems pretending to talk to each other through the human in the middle.
Real depth means signal levels live inside the customer record, the ticket, the dispatch packet. The NOC engineer doesn't open a vendor UI; they open the customer's contract and see the ONU's last 24 hours of receive power, the OLT port status, the recent reboot history. The ERP is the network monitoring tool, not a launcher for it.
Nineteen layers of operational network depth. Each shipped because a NOC engineer needed it, not because a roadmap deck listed it.
Vendor-agnostic OLT abstraction layer. Provision ONUs, query signal, manage firmware, control PON ports across vendors from one interface. Per-vendor drivers handle the protocol differences; your team sees one consistent UI.
The customer's ONU signal levels live inside the contract record. Open a ticket, see the last 24 hours of receive power, recent reboot history, OLT port state. Marginal-but-within-spec signal trends get flagged before they degrade to outage.
Aelita recognises when two or more customers in the same neighbourhood drop offline within a short window as a single infrastructure event, not a handful of unrelated tickets. The NOC dispatches a cable team once, with all affected contracts attached to a single incident note.
Upload an OTDR trace file; the system parses it, locates the fault, and overlays it on the GIS map. Compare against the baseline trace to verify a repair actually fixed the issue. Trace-event history per cable section.
IPACCT is the NAS we integrate with most deeply — a robust, Bulgarian-built subscriber-management platform — and ISPCQ drives it straight from the customer's contract. Activate a contract and ISPCQ creates the IPACCT subscriber and provisions its S-VLAN/C-VLAN over IPACCT's IFMGR API; change a plan and the new IPACCT service package follows automatically. The same contract the support agent is reading is the single source of truth for the account on the NAS — no second screen, no re-keying, no drift between billing and the network. Read the NAS deep-dive →
Environmental monitoring at cabinets, manholes, and sites — temperature, humidity, water level, gas detection (methane, H2S), and vibration — with configurable thresholds and Telegram NOC alerts. SNMP integration with Observium / LibreNMS for device discovery and broader infrastructure visibility. Topology auto-sync into the GIS.
What you sold the customer is what they still have nine months later. The Illegal ONUs page surfaces ONUs registered on an OLT that don't map to an active billing record, filterable by OLT and slot/port so the NOC can triage them before they reach the billing path. The dedicated SVLAN provisioned at contract activation survives ONU replace, return, and re-issue cycles — no manual reprovisioning, no "we lost your VLAN during the swap." IPACCT gating prevents the long-tail drift where a service is technically active on the OLT but no billing record carries it.
See exactly what a single customer is doing on the wire, right now. A live sFlow feed sits inside the customer record: real-time bandwidth, top talkers, and a breakdown of how much of their traffic stays local versus crossing a paid peering or transit border. When a customer calls about a slow line, the agent reads the live graph instead of guessing.
Know which PON ports are filling up before a sales order lands on one that can't take it. The capacity view tracks utilisation across every OLT port and raises a warning, then a danger, alert as configurable thresholds are crossed. Planning teams provision ahead of demand instead of reacting to a congested port and angry customers.
The physical ducts that carry your fibre are tracked as first-class infrastructure, not a spreadsheet. Each route breaks into segments with diameter, material, depth, and capacity; nested sub-ducts and the cables routed through them are recorded with live fill rates. A cross-section diagram shows exactly what's inside a duct, with colour-coded congestion warnings — so you know whether the next cable will actually fit before you dig.
An interactive, zoomable graph of how every device connects to every other device — auto-discovered from the network management system and kept current by a background sync. Pick any site, cabinet, or room and the switching scheme draws the port-level and cable-level connections at that location. Save and share scheme views so the next engineer inherits documentation that's actually accurate.
Every rollout phase is a project: code, type, status, contractor, budget, and the infrastructure assigned to it in one place. Wayleave permits are tracked end to end — reference number, municipality, authority, submission and approval dates, conditions, and the approval letters attached. Auto-generate a bill of materials from the assigned infrastructure, and export the whole project to KMZ for Google Earth or a contractor's survey.
When fibre drops, the platform runs the incident end to end. Aelita scans every 20 minutes and files incidents graded Critical, High or Medium by how many customers are affected. Known customers who phone in during an active outage or a planned-maintenance window hear an “we’re aware and working on it” message before they reach an agent. On recovery, a RESTORED alert goes out with total downtime and every related incident note closes automatically.
Router-mode ONUs are handed to a tenant-configurable TR-069 ACS, so customer-premises equipment is configured and managed remotely instead of by a truck roll.
Declare a cable fault and drive it through a clear status pipeline instead of a freeform note. A fault moves from Reported to Under Investigation to Dispatched to Repair Scheduled to Resolved, you assign the technician who handles it, and the system attaches an automatic impact list of exactly which customers sit behind the break — so the team knows who to call and what to expect on site before anyone leaves the depot.
Build the full route from the OLT port to the customer's ONU — cables, cores, splitters, splice points, and ODF patches — and the path carries a calculated loss budget you can validate for continuity and compare against actual OTDR measurements. Then ask the question that matters before a failure happens: pick any cable, splitter, or piece of equipment and see exactly which customers and downstream devices would go dark if it fails.
Drill down through the physical estate — Site to Floor to Room to Cabinet — with a visual rack diagram showing equipment in its slots and patch cables drawn between ports. A port dashboard tracks utilisation and free capacity across the OLTs, and clicking any device opens its full port list with the connected core, the assigned customer, and live ONU data. The whole physical network is navigable down to the individual port.
Planning a new conduit build starts with a question: what's the best path between these two manholes? Pick a start and end manhole from a search dropdown and the system proposes the optimal route, weighing distance against how full the existing conduit already is along the way. Compare up to three candidate routes side by side before a crew ever picks up a shovel.
Every splice where fibre cores are joined — at a manhole or a splice enclosure — gets its own record: the two cables and cores connected, plus the measured splice loss. The splice dashboard gives drill-down to any individual splice, so when a joint starts degrading, the maintenance history is a lookup, not a guess.
The signal. The cluster-detect engine flags four customers on the same OLT PON port whose ONU receive power has degraded by 4 dBm over the past 48 hours. Each individually is still within spec; together, they are a pattern.
The investigation. The NOC engineer opens the GIS map, traces the fibre path from the four customers back through the splitter to the OLT, and notices that the signal degradation correlates with a splice point that was last maintained 14 months ago. She pulls the most recent OTDR baseline for that section and confirms the fault location: a splice closure approximately 1.2km from the OLT.
The result. A maintenance task is created with the exact GPS coordinates and OTDR baseline data attached. The field team is dispatched preventatively, before the splice fully fails. Two days later, the splice closure is re-spliced and the OTDR re-baselined. Two hundred customers downstream of that splitter never lost service. Without the cluster-detect, the first time anyone would have known about it was a wave of "no internet" calls on a Sunday afternoon.