Industry solution

Telecom & Network Operators

One picture of the network, the crews and the subscribers who depend on it

Network inventory, field maintenance, subscriber churn and network security, handled by products designed to hand work to one another.

Products
8
Challenges
6
Concepts
15
Talk to us about TelecomAsk a question
Field technician at a roadside fiber cabinet beneath a cell tower at dusk, with glowing network lines leading to a town.
AdapterCloud(opens AdapterCloud in a new tab)AssetHandler(opens AssetHandler in a new tab)CrewFoundry(opens CrewFoundry in a new tab)FluidGrids(opens FluidGrids in a new tab)Botlit(opens Botlit in a new tab)BigConsole(opens BigConsole in a new tab)Subscriber Bot(opens Subscriber Bot in a new tab)IntelWatchtower(opens IntelWatchtower in a new tab)

The problem

Why running a network is harder than drawing one

Operators run the network, field crews, subscribers and security from systems that do not share a picture, so a fiber cut, a storm or a botnet becomes hours of reconciliation before anyone can act.

Most operators run a layered estate that grew by acquisition and upgrade: fiber and copper access, microwave and fiber backhaul, macro and small cell sites, a routed core and millions of routers in customers' homes. Each layer comes from a different vendor with its own element manager, and the inventory of record is a mix of an older OSS, spreadsheets and as-built drawings that drift from reality after every emergency repair.

The work that keeps the network up happens in the field. Truck rolls are expensive, tower climbs and splicing demand current certificates, storms take out mains power at remote sites, and enterprise contracts attach service-level commitments to every circuit. The people who plan, dispatch and do this work rarely see the same list.

On the other side of the network sit subscribers with a real choice. Competing fiber, cable and fixed-wireless offers make leaving easy, number portability does the same for mobile lines, and a bad month of outages shows up as disconnects and port-outs weeks later. Security threats land in the same place: compromised home routers, abuse reports from transit partners and fraud all hit both the network and the brand, and the teams that see each signal work in separate tools.

Who this is for

  • VP or Director of Network Operations

    Knowing what is down, who it affects and who is fixing it within minutes, across every vendor's element manager.

  • Network Planning and Inventory Lead

    An inventory that matches the network, so ports reserved are really free and stranded capacity gets found and sold.

  • Field Operations Manager

    Fewer repeat truck rolls, the right certified technician on every job, and contractors whose paperwork is current.

  • Head of Retention and Customer Care

    Seeing network-driven churn early, giving agents one consistent outage answer, and aiming save offers at the right accounts.

  • CISO and Security Operations Lead

    Tying abuse reports and threat indicators to real equipment in the field, and containing it before a partner filters traffic.

A day in the life

The story behind the solution

A week at Tessbury Valley Networks: one cut, one storm and one Saturday abuse report

Adaeze runs network operations for a regional operator that grew by stitching together a fiber overbuilder, a fixed-wireless business and a small mobile network. Her NOC watches four element managers, her field teams mix employees and contractors, and her inventory is a system of record in name only. This is one week, told as a sketch of how the pieces could work together.

  1. Monday, 07:10

    The port that was not free

    A turn-up for a cold-storage warehouse fails before it starts: the port the inventory promised on OLT-EAST-03 is lit and carrying a circuit nobody can name. Provisioning lead Marcus Bell spends the morning in spreadsheets while the technician drives back. In the week this page imagines, the port would already have been flagged as not matching the records, with the card and cabinet it lives in one click away.

    How this is solved: Network inventory that matches what is in the ground

  2. Tuesday, 02:14

    A backhoe on County Road 9

    Loss-of-signal alarms on 12 fiber ports across two optical line terminals. On-call engineer Wen Li needs to know which homes, business circuits and cell sites are down, and which rode the protected ring. Instead of rebuilding the answer from a diagram, she opens the trace, confirms twelve enterprise circuits and starts the outage response plan. By 07:00 the care agents are answering from the same notice the network operations center published.

    How this is solved: Knowing who a fiber cut affects before the phones ring

  3. Wednesday, 15:30

    Eleven sites off mains

    A storm takes out mains power across the north district. The power watch ranks the sites, and SITE-NR-114 rises to the top: a generator that failed to start, a battery string already degraded, and three neighboring sites backhauled through it. A portable generator is on the road before the battery runs out.

    How this is solved: Keeping cell sites on air when the grid goes down

  4. Thursday, 06:00

    The climber who could not climb

    The tower realignment would once have gone to the nearest contractor, whose rescue certificate lapsed two weeks ago. This time the board has already blocked him and suggested a technician who holds every certificate the job needs. Field operations manager Rosa Delgado approves the assignment, and the work order updates with the crew and the time on site.

    How this is solved: Sending the right certified technician the first time

  5. Friday, 10:00

    Disconnects climbing in the east district

    The retention review sees disconnect requests rising in the neighborhood Tuesday's cut hit, the same one that lost service twice in August, where many promotional prices end within weeks. Head of retention Imran Siddiqui approves service credits for the highest-risk accounts, and the apology goes out before customers have to call.

    How this is solved: Catching the subscribers an outage is about to cost you

  6. Saturday, 02:40

    An email from the transit partner

    Attack traffic is leaving Tessbury Valley's address ranges, and the partner will filter them if it continues. Security analyst Hannah Berg links the report to a new threat warning and to a cluster of home routers on one old firmware, sees every unit still below the fixed version, and sends Adaeze the plan to fence off the affected routers for her approval.

    How this is solved: Finding compromised home routers before a partner filters you

None of these moments is exotic; every operator lives some version of this week. The difference imagined here is that the inventory, the work orders, the crews, the subscribers and the threats are seen through products built to pass work along, on one sign-in.

Challenges and how they are solved

6 problems, several products, one connected answer

Each challenge shows the problem as it happens, how the products are designed to hand work to each other, and the concepts that illustrate it. Share any challenge on its own.

Answers are in plain business terms. Choose Technical, or open any technical detail, to see how it works under the hood.

Challenge 1 of 6

Network inventory that matches what is in the ground

AdapterCloud(opens AdapterCloud in a new tab)AssetHandler(opens AssetHandler in a new tab)FluidGrids(opens FluidGrids in a new tab)

The problem

A provisioning engineer reserves port 1/1/14 on OLT-EAST-03 for a new business customer because the inventory says it is free. The technician arrives, finds the port lit and carrying traffic for a circuit nobody can name, and drives back. The records came from a move to a new system years ago, a spreadsheet of splitter assignments and as-built drawings that stopped being updated after the last storm repair. Each vendor's management system for the optical line terminals, routers and microwave links holds its own version of the truth, and none of them know about the cabinets, cards and spares in the field.

What it costs

Every inventory error becomes a wasted truck roll, a missed turn-up date promised to a customer, stranded capacity nobody sells, and ghost circuits that carry traffic without a bill.

How the products work together

AdapterCloud is designed to keep one list of every port, router, link and site, and to flag a port the records call spare that is actually in use. On a schedule, FluidGrids copies what each vendor's equipment system reports into that list, while AssetHandler tracks cabinets, cards and spares and points out devices nobody registered. A technician's tag scan on site corrects the list.

How it works — technical detail

Technical detail

AdapterCloud is designed to be the one logical inventory: network adapters bring OLTs, routers, switches, microwave links and edge sites into one resource list with topology edges between them. A scheduled FluidGrids workflow can read each element manager's export and report it into AdapterCloud, which is designed to record drift wherever the observed state differs from the design record, such as a port in use but recorded as spare. Passive plant, meaning feeder cables, splice closures and splitters, is designed to be imported from the fiber GIS and as-built records through a custom adapter, so a trace can walk it. AssetHandler holds the physical side, cabinets, shelves, cards, batteries and spares, as configuration items, with discovery jobs designed to surface devices nobody registered. A technician's tag scan in AssetHandler is designed to send the corrected card and port to AdapterCloud through a FluidGrids workflow.

The outcome it is designed for

Provisioning is designed to reserve ports that are really free, and the inventory gets more accurate with every automatic network check and field scan instead of drifting further from the network.

The concepts behind it

Challenge 2 of 6

Knowing who a fiber cut affects before the phones ring

AdapterCloud(opens AdapterCloud in a new tab)FluidGrids(opens FluidGrids in a new tab)Botlit(opens Botlit in a new tab)AssetHandler(opens AssetHandler in a new tab)

The problem

At 02:14 an excavator severs a 144-fiber feeder cable on County Road 9. The network operations center (NOC) sees loss-of-signal alarms on 12 fiber ports across two optical line terminals, but not which homes, which business circuits with service-level commitments, or which of the cell sites backhauled over that route are actually down, and which were rerouted over the protected ring. The on-call engineer pieces it together from a network diagram and a circuit spreadsheet. At 07:00 the care queue fills with the same question, is there an outage at my address and when will it be fixed, and agents have nothing consistent to say.

What it costs

Slow impact assessment means late notices to business customers, missed escalations for affected cell sites, overloaded care queues and subscribers who hear about the outage from their neighbors first.

How the products work together

AdapterCloud is designed to list every home, business circuit and cell site behind the cut, with rerouted ones shown separately. FluidGrids raises the repair job in AssetHandler, notifies business customers in order of service commitment, and posts an outage notice with an estimated restore time. Botlit's care agents answer from that notice, saying plainly when an address is not affected, and the notice updates when the crew's estimate changes.

How it works — technical detail

Technical detail

AdapterCloud is designed to trace the cut span through its recorded topology, from feeder to splice closure, OLT ports, splitters, service points, enterprise circuits and backhaul links, and to list the affected services with rerouted ones set apart. That list is designed to start a FluidGrids outage workflow through a webhook, which can raise the emergency work order in AssetHandler, notify business customers in SLA order and publish an outage notice, with an estimated restore time, to the Botlit knowledge base the care agents answer from. Botlit agents are designed to answer outage questions on messaging channels, and later on a web chat widget, from that notice, citing it and saying plainly when an address is outside the affected area. When the repair crew updates its estimate, the workflow refreshes the notice.

The outcome it is designed for

The network operations center is designed to see the affected services as soon as the trace runs, business customers hear first, and every care answer comes from the same published notice.

The concepts behind it

Challenge 3 of 6

Keeping cell sites on air when the grid goes down

AssetHandler(opens AssetHandler in a new tab)FluidGrids(opens FluidGrids in a new tab)CrewFoundry(opens CrewFoundry in a new tab)

The problem

At 15:30 a storm takes out mains power across the north district and eleven macro sites switch to batteries or standby generators. The alarm console shows a column of site IDs in red. It does not show that the generator at SITE-NR-114 failed to start, that its battery string was already degraded, or that the site carries backhaul for three neighbors. Refueling runs and portable generators go out in the order people remember, and the first site anyone knows is in real trouble is the one that goes off air.

What it costs

When a hub site drops, the outage cascades to the sites behind it, coverage thins out for emergency calls, and regulators and enterprise customers ask questions nobody can answer quickly.

How the products work together

When grid power fails, FluidGrids is designed to open an emergency work order for each affected site and keep checking battery and fuel levels until power returns. AssetHandler shows one list of sites ranked by battery time left and by how many other sites depend on them, and flags the weak batteries and generators to fix after the storm. CrewFoundry suggests a qualified technician for the dispatcher to approve.

How it works — technical detail

Technical detail

AssetHandler is designed to hold every site's power assets, including rectifiers, battery strings, generators, fuel tanks and cooling, with their maintenance schedules and service history, and to read site power telemetry as connected devices. A FluidGrids workflow triggered by the mains-fail alarm webhook can raise an emergency work order in AssetHandler for each affected site, and a schedule rechecks battery and fuel levels until mains returns. The Cell Site Power Watch is designed to rank sites by battery time left and by what depends on them, while predictive maintenance is designed to flag the battery strings and generators most likely to fail next, so the overdue load test becomes planned work after the storm. Each work order's required skills are designed to pass to CrewFoundry, which is designed to propose an eligible technician for the dispatcher to approve.

The outcome it is designed for

Crews are designed to reach the sites closest to going dark and the ones others depend on first, and weak batteries and generators get fixed on a schedule rather than in a storm.

The concepts behind it

Challenge 4 of 6

Sending the right certified technician the first time

CrewFoundry(opens CrewFoundry in a new tab)AssetHandler(opens AssetHandler in a new tab)

The problem

Thursday's list has a splice closure to rebuild, an antenna to realign on a tall lattice tower and a generator to repair. The dispatcher gives the tower job to the nearest available contractor. On site, the climber's rescue certificate turns out to have lapsed two weeks earlier, so the job stops at the fence. The splicing lead is on leave, and the one other technician with a fusion splicer has the fiber test kit booked out to another van. Every mismatch is another truck roll, and every lapsed certificate is an exposure the company discovers at the base of the tower.

What it costs

Repeat truck rolls, jobs that stall at the site gate, pressure on crews to work outside their qualifications, and no reliable view of which contractors are actually cleared this week.

How the products work together

Each AssetHandler work order is designed to list the site, checklist, parts, test kit and certificates the job needs. CrewFoundry matches it against each employee's and contractor's certificates and expiry dates, ranks who can go, blocks anyone with a lapsed certificate, and offers it to outside crews when nobody inside fits. The approved technician goes on the work order, and anyone nearing expiry can be enrolled in a renewal course.

How it works — technical detail

Technical detail

Each AssetHandler work order is designed to carry a job pack: the asset and its location, the checklist, parts and test equipment, and the qualifications the work requires. CrewFoundry is designed to match those requirements against its skills graph, which is designed to hold every employee's and contractor's climb, rescue, RF awareness, splicing and electrical certificates with expiry dates, alongside leave, and, as shift rosters and location-aware dispatch arrive on its roadmap, shifts and home base. The Tower and Splicing Crew Qualification Board is designed to rank eligible technicians, block anyone whose certificate has lapsed, and offer the job to contract crews from the talent marketplace when nobody internal fits. The approved assignment is designed to flow back onto the AssetHandler work order, and technicians close to expiry can be enrolled in a renewal learning path.

The outcome it is designed for

Jobs are designed to go to people whose recorded certificates cover the work, first-time fixes become the habit, and lapsing certificates surface weeks before a site visit.

The concepts behind it

Challenge 5 of 6

Catching the subscribers an outage is about to cost you

Subscriber Bot(opens Subscriber Bot in a new tab)BigConsole(opens BigConsole in a new tab)FluidGrids(opens FluidGrids in a new tab)Botlit(opens Botlit in a new tab)

The problem

The Friday retention review opens with a familiar surprise: disconnect requests from the east district are climbing. Nobody has connected them to Tuesday's fiber cut, the two outages in the same neighborhood in August, or the promotional price that ends for many of those households within weeks. Network data sits with the network operations center, promotion dates with billing, contact reasons in the care platform, and the churn model, where there is one, runs monthly on last month's data. By the time the save desk calls, the household has already booked a competitor's install.

What it costs

Churn caused by the network gets treated as a marketing problem, save offers go to the wrong accounts, and the lifetime value of loyal subscribers leaks away one disconnect at a time.

How the products work together

FluidGrids is designed to bring outage minutes, speed tests and customer contact reasons into BigConsole, which shows repeat outages and complaint hot spots by neighborhood. Subscriber Bot's planned churn scoring would flag at-risk accounts from outages, promotions ending and disconnect requests, and show why. The save desk approves every credit or apology before FluidGrids sends it, and Botlit care agents can look up recent outages in a caller's district.

How it works — technical detail

Technical detail

FluidGrids workflows are designed to push outage minutes by service area, speed-test results and care-contact reasons into BigConsole data sinks, where a network-experience console shows repeat outages and complaint hot spots by district, down to the neighborhood. Subscriber Bot's provider-side churn scoring is on its roadmap; operator data would reach it through FluidGrids and BigConsole by design. The scoring is designed to combine that signal with plan, promotion roll-off, disconnect requests and, for bundled mobile lines, transfer-PIN requests into a risk score per account, showing the drivers that moved it. Which signals may drive retention offers is set with the operator's own compliance team. The save desk approves each proposed credit, plan change or apology, and approved offers are designed to go out through a FluidGrids workflow. When a customer calls, Botlit care agents can query the console for the district's recent outages.

The outcome it is designed for

Retention teams are designed to see network-driven churn while there is still time to act, and offers reach the subscribers whose experience actually warrants them.

The concepts behind it

Challenge 6 of 6

Finding compromised home routers before a partner filters you

IntelWatchtower(opens IntelWatchtower in a new tab)AdapterCloud(opens AdapterCloud in a new tab)FluidGrids(opens FluidGrids in a new tab)Botlit(opens Botlit in a new tab)

The problem

At 02:40 on Saturday an upstream transit partner sends an abuse report: attack traffic is leaving the operator's address ranges, and the partner will block those ranges if it continues. The on-call security analyst has traffic alerts in one tool, a threat-intelligence list in another naming a new web address the attackers use to control infected devices, and no quick way to know which subscriber routers are infected. Router models and firmware versions live in the provisioning system, and nobody can say how many units still run the firmware with the known flaw. The abuse mailbox fills, and care has no script for customers whose internet is suddenly slow.

What it costs

Compromised customer equipment can get an operator's internet addresses filtered or blocklisted, degrades service in the neighborhoods where it sits, and erodes trust when customers learn about it last.

How the products work together

IntelWatchtower is designed to pull the partner's abuse report, traffic alerts and threat warnings into one case and group infected home routers by model and firmware. AdapterCloud then shows every router on the flawed firmware, not only the ones causing trouble. Once a named approver signs off, FluidGrids limits the infected routers' internet access and schedules the firmware update, and Botlit's care agents answer affected customers from the published notice.

How it works — technical detail

Technical detail

IntelWatchtower is designed to take the abuse report, flow alerts and threat indicators in as feeds, correlate them into clusters of compromised routers, tracked as network-node entities with confidence and threat score, and run the response as a case. AdapterCloud is designed to hold the router inventory by model and firmware, imported from the provisioning system through an adapter, with a firmware baseline policy raising a violation for every unit below the fixed version. Escalating a cluster is designed to call a FluidGrids webhook with the affected lines, and the workflow looks up the matching routers in AdapterCloud, exposing the whole vulnerable population. The workflow is designed to wait until a named approver signs off, then apply a walled-garden policy through the BNG and RADIUS policy system and schedule the firmware push through the CPE auto-configuration server. Botlit care agents are designed to answer affected customers from the published notice.

The outcome it is designed for

The security team is designed to answer the partner quickly with scope, fix and timeline, and to close the exposure across every vulnerable router rather than only the noisy ones.

The concepts behind it

How it fits together

From a fiber cut alarm to a subscriber who stays

One incident, followed across the products: a feeder cut at night becomes a traced impact, a response plan, a job pack, a qualified crew, consistent answers for customers and, a few days later, save offers for the households the outage hurt most.

  1. To FluidGrids: Who is affected, by service commitment, with rerouted services marked

  2. To AssetHandler: A repair request naming the cut cable, splice point and priority

  3. To CrewFoundry: The certificates needed, the location and the priority

  4. To AssetHandler: Approved crew and arrival time, added to work order and notice

  5. To FluidGrids: The reasons customers got in touch about the outage

  6. To BigConsole: Outage, speed-test and customer-contact figures by service area

  7. To Subscriber Bot: Areas hit by repeated outages this quarter

Step 1 of 8: Trace the impact

How each hand-off works — technical detail

Technical detail

  1. 1. AdapterCloud — Trace the impact: Finds everything downstream of the cut span and separates what rerouted from what is down.Hands to FluidGrids: The affected-services list, with SLA tiers and rerouted services marked, starts the outage workflow.
  2. 2. FluidGrids — Run the outage runbook: Starts from a webhook, notifies business customers in SLA order, publishes the outage notice to Botlit and requests an emergency work order.Hands to AssetHandler: An emergency work order request naming the span, the splice closure and the priority.
  3. 3. AssetHandler — Build the job pack: Raises the work order with the closure location, checklist, spares and test equipment, and the certificates the repair requires.Hands to CrewFoundry: Required certificates, location and priority for the crew match.
  4. 4. CrewFoundry — Send a qualified crew: Ranks eligible splicing technicians and contract crews by certificate, expiry and distance, and proposes the best match for the field operations manager to approve.Hands to AssetHandler: The approved crew and estimated time on site, written back to the work order and the outage notice.
  5. 5. Botlit — Answer customers: Care agents are designed to answer outage questions from the published notice, cite it, and log why each customer got in touch.Hands to FluidGrids: Outage-related contact reasons, picked up by a FluidGrids workflow.
  6. 6. FluidGrids — Land the experience data: Pushes outage minutes, speed tests and care-contact reasons into BigConsole data sinks on a schedule.Hands to BigConsole: Keyed datasets that feed the network-experience console.
  7. 7. BigConsole — Show network experience: A network-experience console shows outage minutes, repeat outages and care contacts by district, drilling down to the neighborhood.Hands to Subscriber Bot: Service areas with repeat outage exposure this quarter.
  8. 8. Subscriber Bot — Protect the relationship: Scores churn risk from outage exposure, promotion roll-off and disconnect requests, and queues save offers that go out through FluidGrids once a person approves.

Products in this solution

What each product brings

  • AdapterCloud

    Network inventory, connections and policy

    AdapterCloud is designed to bring different vendors' equipment into one inventory that shows how it connects, where records and reality disagree, and which units break your rules, such as outdated firmware. Tracing a cut across several links and automatic rule checks are on its roadmap.

    Technical detail

    Technical detail

    Its adapter model is designed to bring network, edge and IoT systems into one resource inventory with topology edges, drift records and policy violations, the records that outage tracing and firmware exposure checks rely on. Multi-hop tracing and automatic policy evaluation are on its roadmap.

    Visit AdapterCloudAll concepts

  • AssetHandler

    Site assets, work orders and maintenance

    Cell-site power gear, cabinets, spares and test equipment need one register with maintenance schedules and one queue of work orders. AssetHandler provides both and is designed to add warnings about equipment likely to fail and live readings from connected site equipment.

    Technical detail

    Technical detail

    Cell-site power gear, cabinets, spares and test equipment need a registry with preventive schedules and one work-order queue. AssetHandler provides those and is designed to add predictive maintenance and connected-device telemetry.

    Visit AssetHandlerAll concepts

  • CrewFoundry

    Certified field crews and contractors

    Field work depends on current certificates, shifts and contractors. CrewFoundry is designed to keep the skills and certificates of employees and contractors in one place, offer training courses and find outside crews when needed.

    Technical detail

    Technical detail

    Field work runs on current certificates, shifts and contractors. CrewFoundry's skills graph, learning paths and talent marketplace are designed for employees, contractors and field crews alike.

    Visit CrewFoundryAll concepts

  • FluidGrids

    Outage, power and response workflows

    FluidGrids is designed to turn your response plans into repeatable steps that start when an alarm arrives or on a schedule, and pause until a person signs off. It also passes outage and customer-care figures to BigConsole.

    Technical detail

    Technical detail

    Alarm webhooks, schedules and wait steps that resume on a person's sign-off are designed to turn runbooks into repeatable workflows, and its data sink step feeds BigConsole consoles with outage and care data.

    Visit FluidGridsAll concepts

  • Botlit

    Care agents that answer from outage notices

    Botlit's care agents are designed to answer customers on messaging channels from published content such as outage notices, show their source, admit when they do not know, and look up figures or start a follow-up task when a customer needs more.

    Technical detail

    Technical detail

    Agents are designed to answer from cited knowledge on messaging channels, say so when they do not know, and query consoles or trigger workflows when a customer needs more.

    Visit BotlitAll concepts

  • BigConsole

    Network-experience and retention consoles

    BigConsole is designed to give network operations, retention and finance teams the same outage and customer-experience numbers, filtered by date and area and broken down from district to neighborhood.

    Technical detail

    Technical detail

    Governed consoles with filters and drill-down let the NOC, retention and finance read the same outage and experience numbers by district and neighborhood.

    Visit BigConsoleAll concepts

  • Subscriber Bot

    Churn risk and the save desk

    Subscriber Bot's planned Provider Success Platform, for providers who connect their systems, is designed to score each subscriber's risk of leaving, show the reasons behind each score, and queue save offers that go out once a person approves them.

    Technical detail

    Technical detail

    Its planned Provider Success Platform, which covers churn analytics and retention automation for providers who integrate, is designed to score subscriber risk with explainable drivers and route approved save offers.

    Visit Subscriber BotAll concepts

  • IntelWatchtower

    Abuse, botnet and threat casework

    IntelWatchtower is designed to give the security team one sorted queue of alerts and threat warnings, a record of each affected device, and a case file that tracks who did what, from the first abuse report until the infected routers are contained.

    Technical detail

    Technical detail

    Feeds, indicators, network-node entities, alert triage and cases give a security team one accountable picture from abuse report to contained botnet.

    Visit IntelWatchtowerAll concepts

One platform underneath: Burdenoff Workspaces

All eight products run on Burdenoff Workspaces, so a NOC engineer, a field technician, a retention lead and a security analyst sign in once and see only what their role allows, with one audit trail of who approved what and one bill across the products.

Concept gallery

Every concept in this solution

15 concepts from 8 products. Each one links to its own page on the product's website, and every view has a link you can share.

Pitch kit

The Telecom solution in one minute

Operators run the network, field crews, subscribers and security from systems that rarely talk to each other. Burdenoff brings together an up-to-date network inventory, site assets and work orders, certified crews, workflows, care agents, consoles, churn risk and threat casework on one sign-in and one audit trail, so a fiber cut, a storm or a botnet can be handled end to end. The products are designed to:

  • Trace a fiber cut to every affected circuit, cell site and home, and start the outage response plan from the same view.
  • Rank cell sites off mains by battery time left and by what depends on them, with emergency work orders raised as the alarm arrives.
  • Match every field job to a technician whose climb, rescue or splicing certificate is current.
  • Show network-driven churn by district and queue save offers for approval before subscribers disconnect.
  • Tie abuse reports and threat warnings to the exact router models and firmware in your inventory.
Email it

Questions

Frequently asked

Do we have to replace our OSS, element managers or billing system?

No. The products are designed to work alongside your current network, billing and customer-care systems, reading the alarms and records they already produce. They add shared views of inventory, jobs, crews and subscribers on top. Which of your systems to connect depends on your setup and is worked out during scoping.

Technical detail

Technical detail

No. The design is to sit alongside what you run today. FluidGrids workflows are designed to receive alarm webhooks and read element manager, billing and care exports through HTTP, database or custom nodes, and AdapterCloud custom adapters are designed to import them. The products then add the shared inventory, work, crew and subscriber views on top. Which connections make sense depends on your estate and is worked out during scoping.

Is this solution available today?

No. The products are early and pre-launch, and this page describes a concept: how they are designed to work together. Some parts, such as tracing a cut across several links, equipment failure prediction, crew dispatch, website chat answers and churn scoring, are still on roadmaps. We are glad to show what exists now and what is planned.

Technical detail

Technical detail

The products are early and pre-launch, and this page describes a solution concept: how they are designed to work together for an operator. Some capabilities shown, such as multi-hop impact tracing, predictive maintenance, crew dispatch, grounded answers on web chat and provider-side churn scoring, are on product roadmaps rather than generally available. We are glad to walk through what exists now and what is planned.

Can we start with one problem, such as field maintenance?

Yes. Each product works on its own, so you can start where the pain is sharpest, for example AssetHandler and CrewFoundry for site maintenance and crews. Network inventory, churn or security can be added later, with the same sign-in, the same roles and one record of who did what.

Technical detail

Technical detail

Yes. Each product works on its own, so most teams would start where the pain is sharpest, for example AssetHandler and CrewFoundry for site maintenance and crews, and add network inventory, churn or security later on the same workspace, with the same sign-in, roles and audit trail.

How is subscriber and employee data protected?

Every product runs on Burdenoff Workspaces, so a technician, a care agent and a retention analyst each see only what their role allows, and there is one shared record of who did what. Rules on where data may be kept, for how long, and on licensing vary by country, so review them with your compliance team. We claim no certifications.

Technical detail

Technical detail

Every product runs on Burdenoff Workspaces with role-based access and a shared audit trail, so a technician, a care agent and a retention analyst each see only what their role allows. Data residency, retention and licensing obligations vary by country and should be reviewed with your own compliance team; we do not claim certifications.

Does this fit mobile, cable and fixed-wireless operators, not only fiber?

Yes, in principle. The ideas here, namely inventory, how the network connects, sites, work orders, crews, subscribers and threats, apply across network types. A cable operator's nodes and amplifiers or a mobile operator's radio sites would be tracked the same way, with the details shaped during scoping.

Technical detail

Technical detail

Yes, in principle. The concepts rest on shared ideas, namely inventory, topology, sites, work orders, crews, subscribers and threats, that apply across access technologies. A cable operator's nodes and amplifiers or a mobile operator's radio sites become resources and assets in the same model; the details are shaped during scoping.

Can the AI agents change things on their own?

Only within limits you set. Botlit's agents are designed to answer from published content and show their source. Save offers and actions that restrict infected routers wait for a named approver, every action goes into one record of who did what, and each product's settings decide what may run without a person's sign-off.

Technical detail

Technical detail

The design keeps people in charge. Botlit agents are designed to answer from published, cited content; save offers and walled-garden actions wait for a named approver; every action is recorded in the audit trail, and each product's agent and workflow policies set what may run without a person's approval.

Related domains

Where these products also work together

All domains

Want to explore this for your organization?

Tell us about your setup. We will walk you through the products involved and scope a pilot around the challenge that hurts most.

Talk to usBrowse every domain

This is a solution concept: it shows how Burdenoff products are designed to work together in this industry. The images are illustrations of the concepts, not screenshots of the actual products, and every name and figure in them is sample data.