Skip to content

Flagship product

TelBrix

End-to-end telecom OSS and BSS. SaaS, automated, AI-driven.

Building an access network is a construction project that produces a database. Most operators are good at the construction and struggle with the database, because the two happen in different tools and nothing forces them to agree. TelBrix is the missing middle.

  • Quote to Cash
  • Trouble to Repair
  • Monitoring & assurance
  • Network automation

Four ordinary questions most operators cannot answer quickly

None of these are gaps another spreadsheet fixes. They are all the same gap.

“Can we serve this address?”

Someone opens a GIS layer, eyeballs a polygon, then calls the planner who actually knows. The answer takes hours and is a professional opinion, not a fact the system can produce.

“What is actually in that pit?”

Nobody knows until someone drives out and opens it. The design says one thing, the as-built spreadsheet says another, and the photos are in a chat thread from fourteen months ago.

“Which fibre goes where, at this joint?”

A splice schedule exists — as a printed page in a van, a tab in a workbook, or in the head of the technician who did the work. Tracing a path from OLT port to premises means phoning people.

“Who changed this, and why?”

The record of what the network is exists in several places. The record of why it became that exists nowhere.

One continuous thread, from catalog to operations

The design is not a drawing that someone later transcribes into an inventory. It is the inventory, in an earlier state, carrying the same identities forward.

  1. Step 1

    Catalog

    Roles, versioned specifications, architecture graphs, manufacturer models and orderable SKUs. This is the authority every later step is validated against.

  2. Step 2

    Guided design

    The designer asks what can be added next; the platform answers from technology, architecture, the selected parent or endpoints, and current topology. Only valid candidates are offered.

  3. Step 3

    Canvas & map

    One network, two projections: an editable engineering canvas for logical composition, and a geographic map assembled from sites, service areas, access structures and duct routes.

  4. Step 4

    Publish & approve

    Publication creates an immutable revision with a stable identity and content digest. Approval is a deliberate decision over that exact revision — never over a mutable draft.

  5. Step 5

    Inventory & operations

    The same resource carries its identity, catalog context and evidence into the asset register, where lifecycle and operational condition are governed independently.

Civil infrastructure, sites and service areas stay independently governed throughout. Network design links them; it never copies them or takes ownership of them — which is why many networks can reuse one physical pathway and a civil correction appears everywhere it is referenced.

The modules

One platform, ten domains that keep their own ownership. Shared identities and governed workflows preserve the relationships between them without collapsing everything into one oversized record.

Quote to Cash

CPQ through order, activation and billing as one API-driven flow — quoting, inventory, single-touch activation and real-time billing without re-keying an order between systems.

Trouble to Repair

Detection through resolution in one loop: faults raised, triaged, dispatched and closed with service inventory and the field working from the same record.

Monitoring & assurance

Proactive network monitoring over performance and alarms, so degradation is seen and acted on before it becomes a customer-reported outage.

Network automation

Provisioning, assurance and change driven through APIs rather than by hand — the network estate operated by the platform instead of by tickets and tribal knowledge.

Physical network inventory

Design to activate across the whole network. One resource lineage from catalog-guided design through planned and reserved, into an asset register that spans design and installed inventory — with lifecycle and operational condition governed separately.

Resource catalog

Roles, versioned provider specifications, manufacturer models and orderable SKUs. A new architecture becomes a published specification rather than a software release.

Civil infrastructure

Access structures, duct segments and individual ducts as an independently governed domain, with route occupation and enforced duct capacity. Many networks reuse one pathway.

Sites & service areas

Governed locations with addresses, boundaries and floor plans, plus a service-area hierarchy of nested zones where every child boundary stays inside its parent.

Fibre connectivity & splicing

Ports, fibres, terminations and splice schedules as validated inventory with stable identities — not lines on a diagram. Occupancy is authoritative, so a used fibre end cannot be used twice.

Warehouse, SKU & ordering

Orderable variants and warehouse stock — quantity, availability and reservation — governed separately from catalog definition, so stock levels never distort engineering rules.

How it works

Let the catalog decide

A traditional diagram tool lets almost any symbol be placed or connected. The drawing looks complete while hiding incompatible equipment, invalid containment, missing capacity or impossible cable endpoints — problems found later, during construction or inventory handover, when they cost far more to fix.

TelBrix moves that validation into the design itself. At every add point the designer asks what can come next, and the platform answers from the catalog. The engineer is guided by the model rather than expected to remember every rule.

  • Selecting a cabinet exposes only the equipment it may contain.
  • Selecting two elements exposes only cable specifications that can connect them.
  • Selecting a manufacturer model determines rack height, power choices and available ports.
  • Selecting a cable model determines construction and fibre capacity.
  • A used port or fibre end is unavailable to anything else — occupancy is authoritative.
  • The same rules are revalidated on save and again on publication.

Designer Canvas

An editable engineering workspace showing logical composition, containment and connectivity. Layout is versioned separately from topology, so moving or grouping nodes never alters the physical design.

Network Map

A read-only geographic projection of the same network, composed from sites, service areas, access structures and duct routes. Assets without resolvable geography stay visible in an unmapped summary — never hidden, never given an invented location.

AI in practice

Where AI does the work nobody enjoys

Not a chat box bolted to a dashboard. AI sits where the platform already has the model, the state and the audit trail to act on.

From signed agreement to priced service

Bring your customer contract. The platform builds the commercial model around it.

Upload the master service agreement and AI derives the offer catalog for that customer. When they select a service — a premise address, a 100 Mb connection — the MSA supplies the agreed price, and the charge follows the service once it is delivered. Quoting and billing are configured from the agreement rather than hand-built per customer.

Proactive fault handling

The fault is found, diagnosed and acted on before anyone reports it.

AI watches network performance and alarms continuously, correlates them to a root cause rather than a symptom, and decides what to do: rectify through the automation platform where the fix is safe to automate, or raise a trigger with the diagnosis attached so a human is not starting from a blank alarm list.

And across the rest of the platform

Serviceability as an answer, not an opinion

Ask whether an address can be served and get a fact read from live network state, capacity and service-area boundaries — instead of a planner reconciling three tools by hand.

Design review before it reaches the field

AI reads a draft against catalog rules and comparable published designs, and flags the choices that are technically valid but operationally regrettable — capacity too tight, a route that will be hard to maintain.

Route and duct-capacity planning

Given two endpoints, propose routes over existing duct capacity and rank them by spare capacity, civil reuse and access constraints, rather than defaulting to a new build.

Splice-schedule generation

Produce a proposed fibre splice schedule for a joint from the cable models and the design intent, for an engineer to approve — a first draft instead of a blank grid.

Stock and demand alignment

Read the pipeline of approved designs against warehouse stock and reservations, and surface the SKUs that will run short before the rollout stalls on them.

Audit answered by query

Every physical change already carries the work that authorized it, who made it, and their evidence. AI turns that trail into a plain answer to "who changed this, and why".

What changes

Serviceability becomes a query

Coverage and capacity are read from live network state, not assembled by a planner from three tools.

Handover stops being a spreadsheet

Commissioning evidence is captured once, at the point of work, attached to the asset that will be operated.

A new architecture is a catalog change

Support a different splitter topology, a rack-mounted variant, a new cable class — publish a specification. Not a release.

An audit is a read

Every physical change already carries the work that authorized it, the person who made it, and the evidence they captured.

The vocabulary

TelBrix uses precise names for things that are usually left vague. These are the ones worth knowing.

Resource Role
Shared vocabulary for what a network element does.
Resource Specification
One operator’s exact versioned implementation of a role, including its assembly and placement rules.
Service Area
The footprint of one rollout, divided into zones.
Network Design
A versioned plan made of first-class elements and cables.
Access Structure
A pit, handhole, manhole, or jointing chamber.
Duct Segment
One physical pathway run between two access structures.
Network Handoff
A modelled boundary to another network, so one design need not contain the entire estate.
Resource Inventory
The installed asset and its maintenance profile.

Bring us a network

Tell us what you are trying to build, or what your current records will not tell you. We will be straight with you about whether TelBrix is the right fit.