Skip to content

Urbbit Telco · TelBrix

A network is not a drawing. It is a governed system of record.

Building a fibre 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 structurally forces them to agree.

We built the missing middle: a versioned catalog that defines what may be built, and a design surface that can only produce networks the catalog permits.

What fragmentation costs

Physical network delivery is usually spread across catalog spreadsheets, diagramming tools, GIS platforms, project workflows and inventory systems. Each is reasonable on its own. Together they produce the same recurring failures.

We connect these concerns without collapsing them into one oversized record. Each domain keeps clear ownership, while shared identities and governed workflows preserve the relationships between them.

  • Engineers can select equipment that is incompatible with the architecture.
  • Drawings contain topology that cannot be traced back to catalog rules.
  • Sites, serving areas, ducts and equipment are duplicated between systems.
  • Field teams build from mutable or ambiguous design information.
  • Later maintenance teams cannot reliably trace why an asset exists, or how it was approved.

The foundation

A layered catalog, so product detail can change without rewriting the designer

An Optical Line Terminal stays the same functional role even when providers specify different deployment rules and manufacturers supply different chassis. Separating those concerns is what keeps vendor facts out of application code.

LayerBusiness meaning
Resource RoleA shared functional classification describing what a resource does in the network.
Resource SpecificationA provider-owned definition of how that role is deployed, placed, contained and connected.
Network ArchitectureThe valid composition and sequence of roles for a technology and design stage.
Resource ModelManufacturer-specific mechanical, electrical, component, port and capacity behaviour.
Stock Keeping UnitAn orderable commercial variant of a Resource Model.
Stock recordWarehouse quantity, availability and reservation — governed separately from catalog definition.

A Model can change rack height, cards, optics or power choices without turning those facts into frontend code. Supporting a new splitter topology or cable class becomes a published specification — not a software release.

Design that cannot go invalid

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 — found later, during construction or handover, when correction is expensive.

At every add point the designer asks what can come next. The answer reflects the network technology and architecture, the provider’s Resource Graph, exact specification versions, the selected parent or cable endpoints, current topology and design stage. Validation is brought into the journey without reducing design to a rigid wizard.

Progressive cable design

Cable creation starts from valid endpoint candidates. Once the A endpoint is chosen, the platform narrows the Z endpoint and the cable specification. Port and fibre assignment is handled separately, so cable existence stays distinct from detailed termination work.

The natural progression

  1. Establish the Network and its technology.
  2. Place root resources such as cabinets or network handoffs.
  3. Add contained equipment and outside-plant resources.
  4. Connect elements using compatible cable specifications.
  5. Select manufacturer Models and detailed material.
  6. Resolve rack placement, power, ports, fibre and civil routes.
  7. Add Sites and Service Area bindings where required.
  8. Publish a validated, immutable revision.

One network, two purpose-built views

Complementary projections of one governed network — not disconnected drawings that somebody has to keep in step by hand.

Designer CanvasNetwork Map
Editable engineering workspaceRead-only geographic projection
Logical arrangement, containment and connectivitySites, Service Areas, Access Structures and Duct routes
Stores node position, grouping, rotation, annotations, viewportResolves geography from the assets that own it
Collaborative layout changes with canvas historyGeographic discovery and navigation
Does not define Site or geographic truthNo map-level editing; markers do not drag assets

A cable appears on the map through the Duct Segments it occupies. Several cables sharing one pathway reuse the same geographic line rather than stacking overlapping copies, with occupancy visible beneath the shared route.

Assets without resolvable geography stay visible in an unmapped summary. The platform never hides them, and never invents a location from canvas coordinates.

Immutable revisions, and a reason attached to every change

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.

What was approved?

A named revision with a content digest, not “the latest version of the drawing”.

Who changed it, and why?

Every meaningful action records the organization, actor, order, process, timestamp and change. Capability and work assignment are checked on every write — a shared link or a visible object never grants editing authority.

Who can edit it right now?

Independently managed properties use versions, edit leases and audit history, so several disciplines contribute without silently overwriting each other.

An audit stops being an exercise in reconstruction and becomes a read.

One resource, progressively enriched

A resource begins as design intent and gains detail as it becomes known. The same conceptual profile is retained throughout, so empty early-stage sections are meaningful placeholders rather than missing records.

  1. concept
  2. draft
  3. planned
  4. reserved
  5. commissioned
  6. in operation
  7. retired
  8. decommissioned

Lifecycle is not condition

Operational condition is tracked separately. A resource can be normal, faulty, damaged, under maintenance or unavailable without pretending that a fault is a lifecycle stage.

Authority is not uniform

Designers can progress a resource through planning and allocation. They cannot declare it commissioned or operational — that authority sits with the operational workflow.

Configuration comes from the catalog, not from code

  • A cabinet Model determines rack capacity, accessible faces and dimensions.
  • Child Models determine rack height and face occupancy.
  • Power policies determine supplies, feeds, loads and capacity checks.
  • Material configuration determines cards, optics, connectors and ports.

The pathway is an asset, not a line on a cable drawing

If every cable owns its own copied path, shared infrastructure becomes invisible and geographic records drift. Civil Infrastructure is its own governed domain, planned and approved by civil planners and then referenced by network designers.

Civil objectPurpose
Access StructureA pit, handhole, manhole or jointing chamber giving physical access to underground plant.
Duct SegmentOne pathway section between two Access Structures, owning its own geographic route.
Duct or subductAn individually identifiable, capacity-bearing channel inside a Duct Segment.
Route OccupationThe ordered Duct Segments and ducts occupied by a cable.

Different networks reuse the same physical pathway.

Deleting a draft network never deletes shared civil assets.

Ownership and access conditions stay attached to the pathway.

A civil correction appears everywhere the object is referenced.

Each duct has a stable identity and an occupancy limit. Cables select an ordered route, and the platform validates continuity, prevents duplicate segment or duct use within a route, and enforces available capacity. A long route is a chain of Duct Segments — because that is how ownership, damage and maintenance are handled in the field: section by section, between access points.

Sites and service areas

A Site is a governed location, not a network asset — it owns its address, boundary and floor plans. Equipment inside a Site-bound cabinet uses the cabinet as its context rather than copying the Site relationship into every child.

Hierarchical zones

A Service Area is the level-zero serving boundary, with descendant zones forming a hierarchy. Every child boundary must stay inside its immediate parent, and parent changes are checked against existing children. The backend stays authoritative for geometry — map drawing tools provide interaction, not a second source of spatial truth.

For downstream resources the platform can follow topology to the nearest upstream resource with a serving-area binding and offer only the appropriate child zones. If that upstream relationship is incomplete, the selection pauses rather than skipping to an unrelated branch.

Fibre connectivity and splicing

Connectivity is catalog-driven inventory, not lines drawn between symbols. Ports come from the specification and the manufacturer Model: a fixed chassis exposes built-in port groups, a modular chassis derives ports from selected cards and optics, a passive frame exposes mirrored front and rear terminations.

Occupancy is authoritative

A port or fibre end already carrying an active connection is unavailable to another. Compatibility, media, connector, same-container and capacity rules are revalidated when a connection is saved — so port reuse is caught in design, not during fault investigation.

Splice-capable joints own a Fibre Splicing Schedule recording continuity between cable spans and the splices for branches. It is independently viewable, lockable and auditable, and validates fibre-mode compatibility, one active use per fibre end, closure capacity and tray placement.

AI in practice

AI sits where the platform already has the model

A governed catalog, live network state and a complete audit trail are what make automated decisions defensible rather than merely fast.

From signed agreement to priced service

Upload the master service agreement and AI derives the offer catalog for that customer. Select a premise address and a 100 Mb service, and the MSA supplies the agreed price — the charge follows the service once delivered, rather than being hand-built per customer.

Proactive fault handling

AI watches performance and alarms continuously, correlates them to a root cause rather than a symptom, then either rectifies through the automation platform where that is safe, or raises a trigger with the diagnosis already attached.

More on how this fits the wider product family at urbbit.com/telbrix.

Bring us a network

Tell us what your current records cannot tell you. We will be straight with you about whether this is the right platform for it.

Talk to an Expert
Hours
Mon–Fri 8:30am–6:30pm (Australian Time)
Address
Melbourne, Australia, 3038