8 Resource Entity Management

This chapter explains how you use the resource management features in Oracle Communications Unified Inventory Management (UIM). UIM includes several different types of entities that you use to manage resources in various ways:

Inventory Groups

You use inventory groups to organize and correlate entities in your inventory. You can define inventory groups to organize entities based on criteria such as:

  • Geographic area, such as country, district, community, or location on a machine room floor

  • Resource pools

  • Serving area

  • Billing area

  • Service types offered by serving area

  • Resources identified for a particular purpose

You can write rulesets to control the behavior of entities in inventory groups. See UIM Developer's Guide for information about rulesets and extending the product.

The following entity types can be included in inventory groups:

  • Custom Network Addresses

  • Custom Object

  • Equipment

  • Flow Identifier

  • IPv4 Address

  • IPv4 Subnet

  • IPv6 Address

  • IPv6 Subnet

  • Logical Device

  • Logical Device Account

  • Party

  • Physical Device

  • Pipe

  • Pipe Termination Point

  • Property Location

  • Service Specification

  • Telephone Number

You are not required to define an Inventory Group specification to create inventory groups in UIM. You can define Inventory Group specifications to include characteristics or to associate specific entities with specific inventory groups in UIM.

About Inventory Group Types and Resource Pools

In Design Studio, you can optionally associate Inventory Group specifications with Inventory Group Type specifications. Inventory group types define specific entities or groups of entities that can or must be included in the inventory group. Inventory groups with inventory group type associations are called resource pools. They are used to manage the assignment of resources in UIM.

For example, you can create a Telephone Number Resource Pool Inventory Group Type specification in Design Studio, define that only Telephone Number entities can be included, and specify that these entities are required. You can then associate the Inventory Group Type specification with appropriate Inventory Group specifications to define telephone number resource pools. In UIM, you add telephone numbers to these resource pools and use them to manage assignments.

Two Inventory Group Type specifications are included in the Base Specifications base cartridge:

  • IP Resource Pool

  • Flow Identifier Resource Pool

Creating Inventory Groups in UIM

In UIM, you can build inventory groups and add entities to it in two ways: you can create an inventory group and add entities to it, or start with an entity and add it to an inventory group.

About Inventory Group Hierarchies

You can form hierarchies of inventory groups in UIM. For example, you can use inventory groups to manage resources for large serving areas and include child inventory groups in the hierarchy for smaller, included serving areas.

Network Address Domains

Network address domains define a context for the uniqueness of network addresses. For example, in the public domain, an IP address must be unique among all IP addresses on the Internet. In contrast, an address can exist in more than one private routing domains. You can use network address domains to define those private routing domains. When you search for an IP address, you can use the network address domain as a search criterion to ensure that you select from the correct addresses.

In UIM, you can use network address domains with the following entities:

  • Flow identifiers

  • IPv4 addresses

  • IPv6 addresses

  • IP subnets

  • Telephone numbers

Network address domain entities are based on specifications that you define in Design Studio. Predefined specifications are included in some sample cartridges, such as the Carrier Ethernet cartridge.

See Design Studio Help for information about defining Network Address Domain specifications. See "IP Address Management" and "About Flow Identifiers" for information about how you use network address domains in those contexts.