Skip to content
All articles

Introducing TelBrix: One Continuous Thread for the Telecom Network Lifecycle

Urbbit introduces TelBrix, connecting catalog-driven network design, civil infrastructure, fibre detail and physical inventory through one governed telecom lifecycle.

7 min read
AS

Arindam Saha

Updated

Urbbit is introducing TelBrix, our telecom platform for connecting the decisions made during network planning with the physical network that is designed, built and operated.

Building an access network is a construction project that also produces a database. Operators are often strong at delivering the construction, but the design, field evidence and inventory are maintained in different tools. A drawing says one thing, a spreadsheet says another, and the reason behind a change may live only in a task, an email or someone's memory.

TelBrix is being built to close that gap. The network design is not treated as a disposable drawing that must later be transcribed into inventory. It is an earlier state of the same governed network, carrying stable identity, catalog context, relationships and evidence forward.

IMAGE PLACEHOLDER 1 - TelBrix launch overview Suggested image: A TelBrix product banner or a composite showing Resource Catalog, Network Designer, Network Map and Physical Resource Inventory.

Why telecom needs one continuous thread

Many operational questions sound simple:

  • Can this address be served?
  • What equipment is installed at this location?
  • Which fibre connects these two network points?
  • What occupies this duct or termination point?
  • Who changed the network, under which work item, and why?

The difficulty is rarely a lack of data. It is that topology, geography, equipment, civil infrastructure, work context and inventory are stored as separate records without dependable relationships.

TelBrix establishes those relationships from the beginning. Instead of trying to reconcile disconnected systems after construction, the platform validates the design as it is created and retains the context required to carry it through approval, build and operation.

The Resource Catalog defines what may be built

The implemented TelBrix journey begins with a governed Resource Catalog.

Resource Roles provide a shared language for what a network element does. Provider-owned Resource Specifications describe how that role is implemented, including its properties, placement, containment and connection behaviour. Manufacturer Models add physical and commercial reality such as dimensions, rack-unit height, ports, connectors, cable construction, capacity and component choices.

Architecture and resource graphs connect these definitions. They describe which elements can start a network, what may be placed inside a cabinet, which cable can connect a selected pair of endpoints and which rules must be satisfied as a design matures.

This means a new network architecture can increasingly be expressed through published catalog knowledge rather than a new collection of frontend conditionals.

IMAGE PLACEHOLDER 2 - TelBrix Resource Catalog Suggested screenshot: Resource Roles, Specifications and Models together, ideally including a specification's properties or architecture relationship.

Guided physical network design

TelBrix turns the catalog into a guided Physical Network Inventory design experience.

The designer does not browse every catalog record or place unrestricted symbols. At each step, the platform resolves what can be added next from the selected technology, architecture, parent resource, cable endpoints and current topology.

On the canvas, engineers can drag, position and group network elements in a way that makes the design understandable. Visual layout remains separate from physical topology: moving a box improves presentation without silently changing its site, containment or connection.

The same network is also available as a geographic map. Sites, service areas, access structures, duct routes and resolved resource positions provide the geographic projection, while resources without final geography remain visible rather than being assigned an invented location.

IMAGE PLACEHOLDER 3 - Network canvas and map Suggested screenshot: A designed PNI topology on the canvas beside the same network projected on the geographic map.

Civil infrastructure remains independently governed

Telecommunications networks depend on civil pathways, but a network design should not take ownership of the infrastructure it reuses.

TelBrix manages access structures, duct segments and individual ducts as independently governed civil assets. Network resources can reference those assets for hosting and routing while the civil record remains authoritative.

This allows multiple networks or cables to reuse one physical pathway. Corrections to an access structure or duct become visible wherever that civil asset is referenced, without copying geometry into every network design. Route occupation and capacity can therefore be governed as relationships, not inferred from lines drawn on a map.

IMAGE PLACEHOLDER 4 - Civil infrastructure and duct route Suggested screenshot: Access structures and duct segments on the map, with a fibre cable following an ordered civil route.

Sites, service areas and the real geography of rollout

Sites and Service Areas provide two different but connected views of location.

Sites represent governed places, addresses, boundaries and floor plans. Service Areas represent the rollout footprint and its hierarchy of zones. Resource Specifications decide when a network element requires one of these relationships and which level is appropriate.

Designers select existing governed records rather than typing a location or serving area into a free-text field. The platform can then validate that a resource belongs where the architecture expects it, while keeping geographic ownership outside the network drawing.

From equipment placement to fibre-level connectivity

The current implementation moves beyond high-level boxes and lines.

Catalog-selected Models can supply rack dimensions, usable faces, equipment height, power choices and stable termination groups. Cabinet Assembly can place eligible equipment in front or rear rack units while checking capacity and overlap. Material Information progressively resolves manufacturer Models, components, connectors and ports.

Cables are first-class network resources. Compatible endpoints and cable specifications are validated during design. Detailed Connection and Fibre Splicing Schedule views can then represent ports, cable ends, tubes, fibres, fusion splices and pass-through continuity using stable identities.

A used termination point or fibre end is authoritative occupancy state. It cannot simply be selected again because another drawing appears to have space.

IMAGE PLACEHOLDER 5 - Assembly and fibre connectivity Suggested screenshot: A cabinet rack elevation or Fibre Splicing Schedule showing equipment, ports, fibres and validated connectivity.

Publish, approve and understand every change

A draft network needs room to evolve. An approved network needs a dependable reference point.

TelBrix supports versioned design and publication. Publishing validates the complete current graph and creates an immutable revision with a stable identity. Approval can then refer to that exact revision instead of a mutable canvas.

Design and property activity carries user, time and work context. Layout changes can be audited separately from physical topology changes, so a visual rearrangement is not confused with an engineering modification. This makes the question who changed this, and why? answerable from the platform rather than reconstructed after the event.

The design continues into Physical Resource Inventory

The same resource lineage can continue from planned design into the Asset Register and installed Physical Resource Inventory.

A resource begins with catalog identity and structured lifecycle sections. It can be progressively enriched with characteristics, material configuration, location, service area, assembly, connectivity, contacts, maintenance information, references and field evidence.

As-built capture and reconciliation do not require the network to be recreated from scratch. The physical resource can retain the design and catalog context that explains what it is, how it was approved and how it participates in the network.

IMAGE PLACEHOLDER 6 - Physical Resource Inventory Suggested screenshot: The Asset Register or a Physical Resource detail showing catalog identity, lifecycle status and its managed property sections.

What TelBrix includes today

The launch foundation implemented so far brings together:

  • governed Resource Roles, Specifications, Models and properties
  • provider architecture and catalog graphs
  • guided PNI element and cable design
  • an editable engineering canvas and geographic Network Map
  • Sites, Service Areas and floor-plan relationships
  • Civil Access Structures, duct segments, ducts and route occupation
  • manufacturer material configuration and rack assembly
  • port, fibre, connection and splicing detail
  • versioned publication, approval context, locks and audit history; and
  • continuity into the Asset Register and Physical Resource Inventory

These capabilities form the physical-network foundation for the wider TelBrix OSS/BSS vision. They create the governed identities, topology, geography, capacity and evidence that future serviceability, fulfilment, assurance, automation and AI-assisted operations can depend on.

A telecom platform built around the network's truth

TelBrix is not intended to be another place where operators redraw the network or maintain a second copy of inventory.

Its purpose is to make the network's design, physical relationships and lifecycle understandable as one connected model. The catalog guides what may be built. The designer captures what is planned. Civil and geographic domains retain their authority. Detailed connectivity protects physical integrity. Publication creates a stable decision point, and inventory carries the result forward.

This is the foundation Urbbit has implemented for TelBrix so far: a practical, governed path from network knowledge to network design, and from design to the physical estate that operators need to trust.

  • Industry News
  • Platform Updates

Want to see it on your systems?

We will walk you through the platform with your own processes, and be straight with you about the fit.