11 Working with Connectivity Specifications

In Oracle Communications Unified Inventory Management, you can represent connectivity in your network with Connectivity entities. Connectivity entities provide built-in support for a variety of technologies and can be customized to suit your business needs.

You can create Connectivity specifications for three types of Connectivity entities:

  • Multiplexed Connectivity entities support technologies such as E-Carrier, T-Carrier, J-Carrier, SDH, and SONET, and WDM.

  • Packet Connectivity entities support technologies such as Ethernet, Frame Relay, ATM, and MPLS.

  • Service Connectivity entities represent the connectivities that delivers services to end customers. Service connectivity consumes other types of connectivity and resources, but cannot be consumed itself.

The specifications for the three connectivity types include different default characteristics. In UIM, you see a different set of tabs in Connectivity Summary pages depending on the connectivity type.

You can also use Pipe entities to model connectivity. For example, pipes are recommended for modeling physical connectivity such as ducts and cables. Because pipe entities do not require end locations and terminations, they can also be useful in situations in which you do not need to model all the details of a connectivity. See "Working with Pipe and Capacity Specifications" for more information.

Pipe entities and Connectivity entities are not mutually exclusive: you can include them both in the same network. For example, pipes can enable channelized connectivity.

When working with Connectivity specifications, see the following topics: