Regional ISPs
One NOC view for several OLTs, with alarms and ONU lists that a small operations team can actually work.
Maram NMS gives internet service providers one console for the optical network and the subscriber router. See OLT and ONU health, authorize new ONTs, and push WAN, VLAN and Wi-Fi settings without sending a technician for every basic change.
An ISP does not fail in one place. The fiber can be bent at a splitter, an OLT port can fill up, or a subscriber router can boot with the wrong VLAN and a default Wi-Fi name. Treating those as separate tools means the NOC sees an alarm in one screen and the customer’s router in another. Maram NMS puts GPON network management and a TR-069 auto-configuration server in the same platform, so the optical path and the customer premises equipment are operated together.
The NMS side watches the OLT: chassis and port state, ONU discovery, authorization, and the optical levels that tell you a link is fading before the subscriber calls. The ACS side speaks TR-069 / CWMP to the ONT or home gateway. It can bind the subscriber account, set the service VLAN, apply Wi-Fi, and run a diagnostic ping without a van roll for work that is only configuration.
This is built for internet service providers, cable broadband operators and the local operators who run a slice of a larger network. It is not an Android device console. Android tablets, signage players and kiosks stay on DCM. NMS is for the fiber plant and the CPE that hangs off it.
A dark ONT is not always a dead router. It can be a PON port, a splitter, a dirty connector or a subscriber who unplugged the power supply. Optical power, grouped as healthy, degraded or critical, plus dying-gasp detection, lets the desk separate a fiber cut that affects a whole tree from one home that lost power. That split is what keeps a truck from leaving for the wrong fault.
Zero-touch provisioning starts when the ONT appears on the PON. The ACS matches the serial number, binds the PPPoE or service account, applies the VLAN and writes the Wi-Fi name and password the subscriber was given. The installer still mounts the hardware. They should not have to log into every router by hand to finish a standard connection.
A large share of “no internet” tickets are Wi-Fi, not fiber. From the ACS an operator can read the connected devices, change a channel, reboot the gateway and confirm the WAN is up. Firmware can go out as a staged campaign with a checksum, instead of a memory stick carried to each building.
NMS fits when subscriber growth has outrun spreadsheets, vendor element managers and truck rolls for routine setup.
One NOC view for several OLTs, with alarms and ONU lists that a small operations team can actually work.
Authorize ONUs and apply line profiles as new buildings come online, without a different login for every OLT brand.
Give a local operator access only to their OLTs, PON ports or VLANs, while the main NOC keeps the full network.
Run more than one OLT family and generic XPON ONTs in the same console instead of a stack of vendor tools.
Separate an optical fault from a Wi-Fi complaint before anyone leaves the office.
Keep the OLT manager you need and add TR-069 provisioning for the gateways you already ship.
The features follow the two jobs: keep the PON healthy, and configure the subscriber device without a visit.
Watch CPU, memory, uplink, temperature and fan state across the OLTs you operate, from one dashboard.
See active ports and how many ONUs sit on each PON, so a full port is visible before it becomes an outage.
Find unconfigured ONTs and apply a line profile and service VLAN instead of leaving them unauthorized on the port.
Group ONUs by signal level and raise a threshold alarm when a link moves from healthy to degraded or critical.
Tell a PON-wide fiber problem apart from a single ONT that lost power.
Read and write WAN, VLAN, DHCP and Wi-Fi parameters on TR-098 and TR-181 devices.
Push firmware in batches and confirm the image before the fleet is marked complete.
Run ping, traceroute and a reboot from the ACS when the ticket is the home network, not the fiber.
Restrict a branch or franchise login to the OLTs and subscribers that team is allowed to see.
The gain is operational: fewer visits for setup, a clearer alarm, and one place to answer whether the fault is optical or in the CPE.
Account binding, VLAN and Wi-Fi can be applied when the ONT first registers, instead of on a second visit.
A falling receive level is visible before subscribers describe it as buffering.
The desk can see whether a complaint is a PON, a single ONT or a Wi-Fi radio.
Operators stop switching element managers every time the OLT vendor changes.
Franchise staff work their own ports without inheriting the whole network.
A new OLT or gateway can be added with an SNMP or TR-069 profile rather than a new operations product.
The published compatible set includes Maram, Huawei SmartAX, ZTE C300 and C320, V-SOL, Syrotech, Netlink and BDCOM. A network that uses another MIB or a proprietary ONT can be profiled rather than replaced.
SNMP, SSH and syslog access for the optical chassis, ports and ONU tables.
CWMP over HTTP or HTTPS for gateways that speak TR-098 or TR-181.
Apply a rule from hardware model, software version or OUI when a device first contacts the ACS.
Maram can write an SNMP OID adapter or a TR-069 parameter map for a fleet you already own.
Signage players and tablets are managed in DCM Console. NMS stays on the access network.
Day-to-day work happens at nms.maramtechnologies.in. This page is the product description. The console is the live system.
The first useful week is a single chassis and the gateway you actually ship, not a slide of every feature.
List OLT models, PON counts, ONU brands and the CPE you provision today.
Bring one OLT and a sample of ONTs into the console and confirm discovery.
Set the line profile, VLAN and Wi-Fi preset for that service.
Authorize a new ONT, raise an optical alarm, and change Wi-Fi without a visit.
Add the next OLT, the franchise roles, and the firmware campaign once that path is boring.
There is no public rate card. The pilot is sized from subscriber count, OLT models and how much of the CPE fleet should be on TR-069.
One brand is a shorter pilot than a plant that mixes several element managers today.
Each new gateway family needs a parameter profile before zero-touch is trustworthy.
A few hundred ONTs and a multi-city fleet do not need the same rollout plan.
Role design takes longer when local operators must see only their own ports.
A proprietary OLT adds engineering time for the adapter. It does not require you to swap hardware first.
Alarm routing, who may push firmware, and how a ticket is closed are part of the pilot, not a later extra.
Tell us the OLT models and how many ONTs you have. We will say what a first console pilot needs to prove.
Contact Maram