Skip to content
All articles

Building Networks from a Governed Resource Catalog

Discover how resource roles, specifications, models and properties turn a reusable catalog into guided, dependable telecommunications network design.

7 min read
AS

Arindam Saha

Updated

A telecommunications network contains thousands of resources, but successful network design starts before any individual cabinet, fibre joint, splitter or cable is placed.

It starts with a shared understanding of what those resources are, how they may be used and which details must be captured when they become part of a real network.

Urbbit's Resource Catalog provides that foundation. It organizes resource roles, provider specifications, manufacturer models and properties into reusable knowledge. Network Designer turns that knowledge into guided choices, helping designers create flexible network plans without hardcoded equipment rules or an unrestricted symbol library.

IMAGE PLACEHOLDER 1 - Resource Catalog overview. Suggested screenshot: the Resource Catalog landing page or hierarchy showing Resource Roles, Resource Specifications and Resource Models.

Start with the role: what does this resource do?

A Resource Role describes the function a resource performs in the network. Examples include an Optical Line Terminal, Optical Distribution Frame, Optical Closure, Equipment Rack or Optical Fibre Cable.

The role is deliberately provider-neutral. It gives architecture and design a stable language without embedding one operator's abbreviation, product name or deployment convention.

Different providers can implement the same network function in different ways, while the design platform still understands how each implementation participates in the wider architecture.

Specifications turn a role into usable design behaviour

A Resource Specification is the provider's exact implementation of a role. It defines the terminology and rules that make the resource usable in a design.

  • whether the resource is an element or a cable
  • the network technologies where it applies
  • the properties designers must capture
  • where it may be placed and which resources may contain it
  • whether it can be hosted by civil infrastructure
  • how it participates in a service area
  • which endpoints or resource types it can connect

Two resources with the same general role can therefore behave differently. Two optical closures may share a functional classification while their exact specifications support different positions in the network, containment rules or service-area relationships. The role says what the resource is; the specification says how this provider uses it.

IMAGE PLACEHOLDER 2 - Resource Specification. Suggested screenshot: a specification detail showing its linked Resource Role, applicability, placement or containment policy and defined characteristics.

Models add the manufacturer and product reality

Specifications describe design behaviour without duplicating every commercial product variation. Resource Models add the manufacturer-level facts needed to represent actual equipment and materials.

A Model may provide dimensions, rack-unit height, usable faces, port groups, connector arrangements, cable construction, fibre capacity, splitter geometry or compatible component choices.

A generic cabinet specification can define that the resource acts as an equipment container, while the selected cabinet Model provides its actual capacity. An OLT specification can define its placement and network function, while its Model and selected components determine the ports that can really be connected.

Catalog teams can introduce new manufacturer options without teaching Network Designer a new set of vendor-specific rules.

IMAGE PLACEHOLDER 3 - Resource Model and material structure. Suggested screenshot: a Model showing manufacturer information, physical dimensions, capacity, components or port configuration.

Properties carry catalog knowledge into each network resource

Roles, specifications and models are reusable master data. Properties are where that knowledge becomes specific to one designed resource.

When a designer selects a specification, the platform can present the applicable property sections and characteristic definitions. As the design matures, the resource can be enriched with:

  • identity and lifecycle information
  • specification-defined characteristics
  • manufacturer Model and material configuration
  • location and service-area relationships
  • rack assembly and power information
  • connection and fibre details
  • contacts, references and maintenance information
  • provider-specific additional information

The catalog defines which properties are meaningful and how values are validated. The resource stores the values that belong to the network instance. This avoids both a rigid universal form containing irrelevant fields and unstructured data that cannot be governed or reused.

IMAGE PLACEHOLDER 4 - Catalog-driven resource properties. Suggested screenshot: the Properties navigation for a designed resource together with Characteristics or Material Information generated from its selected specification and Model.

The catalog graph describes what may be built

The catalog is more than a collection of independent records. Roles and specifications participate in a governed architecture graph.

At a high level, this graph describes:

  • which roles may appear at the network root
  • which resources may contain other resources
  • the sequence in which network functions may be introduced
  • which civil hosts are eligible
  • which cable types can connect a selected pair of endpoints
  • which rules become mandatory as the design progresses

These relationships allow the platform to reason about a network design without placing catalog intelligence inside the user interface.

Network Design turns the catalog into guided choices

Network Designer does not ask users to browse every active specification. It resolves candidates from the selected technology, architecture, current network position and existing topology.

At the Network root, the designer sees eligible starting elements. Inside a cabinet, available choices reflect its containment rules. When creating a cable, the selected A-end narrows the possible Z-ends, and the endpoint pair narrows the compatible cable specifications.

This makes the experience feel simple even when the underlying decisions are rich. Designers choose from relevant options rather than remembering compatibility matrices or searching a large catalog manually.

IMAGE PLACEHOLDER 5 - Guided selection in Network Designer. Suggested screenshot: the Add Element dialog or candidate palette showing catalog-qualified resources for the selected network point.

A practical path from cabinet to connectivity

Consider a cabinet-based access network. The architecture admits a telecommunications cabinet role at the appropriate network position. The provider's cabinet specification defines placement and containment behaviour, and the selected cabinet Model supplies its physical capacity and usable faces.

When an OLT or ODF is added, its specification confirms that it may be contained by the cabinet. Its Model supplies the equipment dimensions and termination structure used by assembly and connectivity. When a fibre cable is created, the cable specification validates the endpoint combination and the cable Model provides construction and capacity.

What appears to the designer as a sequence of straightforward selections is a catalog-driven orchestration of multiple related decisions.

Stable catalog identity protects the design over time

When a resource enters a network design, Urbbit retains the exact catalog identity and version used to create it.

Catalog definitions will evolve, products will be retired and new Models will become available. An existing design must remain understandable in the context in which it was created, while new designs should use the current approved catalog.

Pinned catalog identity gives designers and reviewers traceability without preventing the catalog from moving forward.

From design knowledge to physical inventory

Catalog-driven design reduces the gap between planning and inventory. A resource does not begin as a disposable drawing symbol. It begins with a stable identity, selected specification, optional Model and structured properties.

Those foundations can be progressively enriched during detailed design, construction and as-built capture before being reconciled into Physical Resource Inventory.

The result is continuity: less recreation of information, clearer lineage and a stronger relationship between what was approved, what was built and what is operated.

Reusable knowledge, flexible design

The Resource Catalog gives telecommunications teams a controlled way to describe network building blocks without making Network Designer feel rigid.

Roles provide a shared functional language. Specifications define provider behaviour. Models add product reality. Properties capture the details of each network instance. The catalog graph brings those concepts together and guides the choices presented during design.

For the user, the experience remains direct: select an eligible resource, configure what matters and continue building the network. Behind the scenes, the catalog ensures every choice contributes to a network model that is consistent, traceable and ready to continue through its lifecycle.

  • Platform Updates

Want to see it on your network?

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