6 Managing Resource Specifications

Use Resource Specifications in Solution Designer to define your resources and locations. The resources include logical devices, connectivity, custom network address, custom object, device interfaces, flow identifiers, flow interfaces, IPv4Address resource extension, network, telephone number, and so on.

Topics in this document

• About Resource Specifications
• Creating Resource Specifications
• Viewing Resource Specifications
• Updating Resource Specifications
• Cloning Resource Specifications
• Revising Resource Specifications
• Deleting Resource Specifications

About Resource Specifications

Resource specifications are entities that are required to provision a service. Network specialists manage the resource specifications in Solution Designer. Resource specifications are the basis for PSR Models you create in Solution Designer to model your network solution. Table 6-1 shows the different types of specifications and who manages them in Solution Designer:

Table 6-1 Resource Specification Types

Specification	Managed by	Description
Resource	Network Specialist	Resources represent specific objects in the network and inventory that an RFS can consume, reference, or share when the RFS is provisioned. Resources can be physical, such as a port, or logical, such as bandwidth or IP address. See "About Resources" for more information. In the Mobile Service example, the Mobile Identity RFS RFS utilizes the SIM Card resource and TN resource to fulfill the service.
Location	Network Specialist	A physical location for services and resources, such as an office, residence, or city. See "About Locations" for more information.

About Resources

Resources are entities that are required to provision a service. A resource is a specific object in the network and in the inventory that can be consumed, referenced, or shared by a service when provisioning an RFS. Resources can be physical, such as a port, or logical, such as bandwidth. Examples of resources include IP addresses, VoIP phones, and DSLAM ports. In the Mobile Service example, the TN, SIM Card, and UDR are the resources required to fulfill the service.

Resources have associations with other resources. Additionally, you can define resources that you intend to realize in external systems such as supply chain management, activation and so on.

You can define the following types of resources in Solution Designer:

• Connectivity Specification: You use the Connectivity specification to represent the connectivity in your network. 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, JCarrier, 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.

• Custom Network Address Specification: A network address is a name, label, or number identifying a location in storage or a device in a system or network. You use a Custom Network Address specification to define a network address that is not modeled by default in UIM. The network addresses that are modeled by default in the UIM framework are telephone numbers and logical device accounts.

• Custom Object Specification: You use Custom Object specifications to define entities that do not fit into one of the predefined categories in UIM. Custom Object specifications enable you extend the inventory model without having to create a custom schema or redeploy UIM. All of the standard features of specifications, such as characteristics, relationships, and policies are available for custom objects.

• Device Interface Specification: You use Device Interface specification to define the access points into the device. Logical devices often provide device interfaces. These device interfaces may be for connectivity, power, timing, or any other means of interaction with the device.

• Flow Identifier Specification: You use the Flow Identifier specification to model flow identifiers. The various packet connectivity technologies have a variety of ways of identifying network traffic to make it visible to only the appropriate devices. By isolating network traffic in this way, the same physical or infrastructure network can support multiple virtual networks. For example, the Ethernet technology uses VLAN IDs (or tags) for this purpose. Similarly, ATM uses VPI and VCI; Frame Relay uses DLCI; and MPLS uses VPLS IDs. In UIM, you use flow identifiers to represent these various types of network addresses.

• Flow Interface Specification: You use Flow Interface specification to model flow interfaces. Flow interfaces are used with flow identifiers (such as VLAN IDs) to trace the path of services through the device interfaces and connectivities in multipoint and point-to-point service arrangements.

• IPv4Address Resource Extension: You use IPv4 Address Resource Extension specifications to model content for IPv4 address management for IPv4 networks, subnets, and IP addresses.

• IPv6Address Resource Extension: You use IPv6 Address Resource Extension specifications to model content for IPv6 address management for IPv6 networks, subnets, and IP addresses.

• Logical Device Account Specification: You use the Logical Device Account Specification to model special types of network addresses that are hosted or managed by a logical device. For a service provider, a logical device account could be a management account, such as a login name, for configuring a logical device. You use Logical Device Account specifications to define these accounts in your inventory. The information captured in a Logical Device Account specification depends on the account that you are modeling.

• Logical Device Specification: You use the Logical Device Specification to model logical devices. A logical device represents a functional view of a set of resources. The logical device itself is not physical, but it can be supported by one or more physical resources that support it and act together logically to perform one or more functions.

• Media Stream Specification: You use Media Stream specification to model content such as audio or video media delivered over cable, satellite, radio, or streaming IP. Media Stream specifications represent provisional or subscription video services such as tiered services and a la carte packages.

• Network Specification: You use a Network specification to define a network as a whole. In UIM, a network represents a collection of other related entities, such as equipment, logical devices, and other networks.

• Other Resource: You user Other Resource specification to define configurations. A configuration is a hierarchically organized collection of facts (configuration items) in the form of characteristics, resource allocations, and entity references. Configurations can be versioned such that a collective set of facts can be organized, managed and referenced as a unit (version) with its own life cycle. In the PSR model, you add a component for other resource, select Resource component as Type and Config hierarchy as Relationship type. You add the child resource specification that has Other Resource as its type. Any component or resource that you add as a child of the Other Resource specification, is created as a configuration item in UIM run-time environment. Configuration items define the content of the configuration. See "Configurations" in UIM Concepts for more information on configuration and configuration items.

• Pipe Specification: Use the Pipe Specification to define trails and connections, to model layered connectivity, and to model hierarchical relationships of pipes.

• Telephone Number Specification: You use Telephone Number specification to define the types of telephone numbers that your inventory includes and how they are managed in the business process. A Telephone Number specification is a blueprint for the various kinds of telephone numbers you might use.

About Locations

Locations define geographic references that are relevant to services or resources. Locations can be specific places, such as a residence or a business, or more general places, such as a city.

In Solution Designer, two location specification types are supported:

• Place Specifications: You use Place specifications to define entities that represent places that can be located on maps.
• Property Location: You use Property Location specification for geographic locations involved in connectivity scenarios. Unlike Place entities, Property Location entities are all based on a single specification.

In Solution Designer, two locations Customer Site and Service Location are pre-loaded and can be used in the PSR models. Customer Site location is a Place Specifications with the place type as Address. For example, in a Fixed line service, a Customer Premise Equipment (CPE) that is, a telephone instrument must be installed at that customer location. Use Customer Site in the PSR model to represent the customer location where the CPE must be installed.

Service Location is a type of Property Location. For example, in a Carrier Ethernet service, the service is delivered to one or more service locations by a service provider. Use Service Location in the PSR model to represent the location where the service originates or is delivered.

About Place Specifications

You use Place specifications to define geographic entities that can be located on a map, such as a state, city, street, postal address, campus, or building. Place entities answer the business question of where other inventory entities (such as subscribers, services, equipment, service terminations, and so on) are located.

Table 6-2 shows the four different types of Place specification that describe different geographical entities.

Table 6-2 Types of Place Specification

Place Type	Description
Site	Defines a loosely defined place such as a campus, cell site, or VPN site. Unlike a location, a site is not necessarily bound to specific geographic coordinates.
Address	Defines a place using the standard address format to meet your business requirements and national postal standards.
Address Range	Defines a group of addresses as a range, such as an address defined with a low street number and high street number.
Location	Defines a place based on geographic references. It can be a very specific place, such as a residence, or more general places, such as a city or province. You can geocode a location to identify its placement on the face of the earth and to enable geographic visualizations of your network or business. Using geographic coordinates also makes it possible to calculate distances between locations.

About Property Location Specifications

Property Location entities define where resources are located and where connectivity is terminated. Property Location entities are optimized for defining the locations of devices and services in your network. Property Location entities are all based on a single specification. Service Location is pre-loaded in Solution Designer and is a type of Property Location. You can supplement the default data elements of Property Location entities by adding Characteristics. The added characteristics apply to all the instances of the entity in the run-time environment. To add more characteristics to Service Location, revise the service location. See "Revising Resource Specifications" for information on revising locations. You can clone the service location to create a copy of the service location.

About Hard Attributes

Hard attributes are the data elements that are added by default as characteristics in the resource specifications. The hard attributes are added based on the resource type. For example, the hard attributes for logical device specification are id, name, description, deviceIdentifier, and networkLocationEntityCode. Hard attributes are associated with the initiative UIM Configuration in the Data Elements application. Based on the resource type, some of the hard attributes are required and some of them are optional. In general, id and name are the hard attributes added for all the resource types. You cannot edit, clone, revise, or delete the hard attributes.

The hard attributes are displayed with Type as Hard Attribute in Resource Specifications. At run time, all these hard attributes are available for all the instances of the specification as required or optional based on the resource type.

Creating Resource Specifications

A network specialist creates and manages the resource specifications. You create the resource specifications using the Resource Specifications application or in the Build Model step, when creating PSR Models in the guided mode. See "About Solution Designer Applications" for more information on Solution Designer applications and "Creating PSR Models using Guided Process" for more information on the guided process.

To create the resource specifications:

• To create resources, see "Creating Resources".
• To create locations, see "Creating Locations"

Note:

Two locations Customer Site and Service Location are pre-loaded in Solution Designer.

Creating Resources

Network specialists create and manage the resources. You can relate a resource to a location, another resource, or RFSs.

For creating and configuring a resource specification, you must have the following in Solution Designer:

• An initiative. See "Creating Initiatives" for more details.
• Domains. See "Creating Domains" for more details.
• Resources or Locations. To configure a resource, you must create the child resources, or have locations within the same initiative so they are available for the resource to build the hierarchical relationship between them.

To create a resource using the Resource Specifications application:

1. In the Solution Designer landing page, click the Resource Specifications application.

2. In the Resource Specifications application, click Create Resource from the Actions drop-down list.

   The Create resource specification dialog opens.

3. Select the type of resource specification that you would like to create. See "About Resources" for more information on the types of resources supported.

4. Enter the following fields. Table 6-3 describes the fields in creating resources.

   Table 6-3 New Resource Fields

   Name	Required or Optional	Description
   Name	Required	Unique name of the resource. In the Mobile Service example, TN, SIM Card, and UDR are the resources.
   ID	Required	Unique Id of a resource.
   Start Date	Optional	The starting date of a resource.
   End Date	Optional	The ending date of a resource.
   Primary Domain	Required	The primary service domain or the technology domain. Only one primary domain can be selected for a resource.
   Secondary Domains	Optional	The secondary domains that are associated with the resource. Multiple secondary domains can be associated with the resource. The secondary domains must have the same domain type as that of the selected primary domain.
   Delivery Action Target	Optional	Select the check box to mark a resource to be the delivery action target for the delivery policies. Only those resources that have delivery action target selected are available for the delivery policies. See "Defining Delivery Policies" for more information on how to define delivery policies.
   Description	Optional	The description of the resource.
   Initiative	Required	The initiative that the resource belongs to. This resource is available only for the selected initiative across the application until the initiative is released. Specifications from the released initiative are available system-wide.

   Note:

   The resource must have a unique ID and follow the naming rules. See "About Naming Rules" for more information on naming rules.

5. Click Create and Continue.

   The Resource editor page opens.

6. You can use the following tabs that are displayed based on the resource type to define the resources:

   • General Information: Displays the general information of the specification. You can add advanced policy implementation assets to a specification. See "Adding Advanced Policy Implementation Assets" for information on how to add advanced policy implementation assets.

   • Configurations: Configure the relationship between a resource and the other entities such as resources and locations. This builds a hierarchy between resources and locations. The Configurations tab is displayed only for the following resource types:

     • Logical Device Account

     • Logical Device

     • Flow Interface

     • Network

     • Other Resource

     See "Configuring Relationships between Specifications" for details on how to configure the relationships between specifications.

   • Design Parameters: Configure the design parameters for the resource using the existing data elements or create new data elements. Design parameters are carried from the upstream order management systems and you define them in the resource. See "Defining Design Parameters" for details on how to define design parameters.

   • Characteristics: Configure the characteristics for the resource using the existing data elements or create new data elements. Data elements are added as characteristics to realize them in UIM run-time environment. See "Defining Characteristics" for details on how to define entity characteristics.

   • Parameter Mapping:Configure the parameter mapping of the design parameters to the characteristics of the specification and also to the design parameters of its child specification. See "Mapping Design Parameters" for details on parameter mapping.

   • Design Policies: Configure the design policies to provision the services in UIM. UIM provisions the service based on the defined design policies. See "Defining Design Policies" for details on defining design policies.

   • Delivery Policies: Configure the delivery policies which are requests to downstream delivery systems such as activation, supply chain management, and so on, to make changes in the network. See "Defining Delivery Policies" for details on defining delivery policies.

   • Used by: Lists all the PSR Models and specifications that use the specification.

   Note:

   Resources of type Other Resource do not support Design Parameters, Characteristics, Parameter Mapping, Design Policies, and Delivery Policies.
7. Click Go to Resource Specifications on the top left to return to the Resource Specifications page.

Creating Locations

You can create the location in Solution Designer. Two locations Customer Site and Service Location are pre-loaded in Solution Designer and can be used in PSR Models.

To create locations using the Resource Specifications application, do the following:

1. In the Resource Specifications application, click Create Location from the Actions drop-down list.

   The Create Location Specification page opens.

2. Enter the following fields:

   Table 6-4 New location Fields

   Name	Required or Optional	Description
   Name	Required	Unique name of the location.
   ID	Required	Unique Id of the location.
   Start Date	Optional	The starting date of the location.
   End Date	Optional	The ending date of the location.
   Type	Required	The type of the location and defaulted to Place Specification and can't be modified.
   Place Type	Required	The types of place specification. Site defines a place that does not have a single, precise location. Address defines ways to locate places based on textual information. Address Range define a place using groups of related addresses. Location defines a place based on geographic references.
   Description	Optional	The description of a location.
   Initiative	Required	The initiative that the location belongs to. This location is available only for the selected initiative across the application until the initiative is released.

   Note:

   The location must have a unique name and ID.

3. Click Create and Continue.

   The Location editor page opens.

4. You use the following tabs to define characteristics on locations:
   • General Information: Displays the general information of the location.
   • Characteristics: Defines the characteristics for the locations along with the hard attributes that are added by default. You can use the existing data elements or create a new data element. Data elements are added as characteristics to realize them in UIM. See "Defining Characteristics" for on how to define entity characteristics.
   • Used by: Lists all the PSR Models and specifications that use the location.
5. Click Go to Resources Specifications at the top left, to return to the Resource Specifications page.

Viewing Resource Specifications

You can view the resource specifications from the Resource Specifications application or from the Initiative Items tab in the Initiatives application.

To view the resource specifications:

1. In the Solution Designer landing page, click the application that you want to work with.

2. Do one of the following:

   • In the Resource Specifications application, search for a specification using the following criteria:

     • Specification name
     • Status
     • Initiatives
     • Domain
     • Type
     • Resource Type
     • Last Updated
     The resources specification result is filtered based on the search criteria.

     Note:

     In the resource specifications results page, click View Errors to view the validation errors if any.

   • In the Initiatives application, search for an initiative and click the Initiative Items tab in the initiative editor page.

3. Select a resource specification to view the details.

   The resource specification editor page opens.

4. You can view the resource specification details such as configuration, design parameters, characteristics, design policies, delivery policies, used by, and general information for the respective specifications in different tabs.
5. Do one of the following:

   • Click the Go to Resources Specifications link on the top left to return to the Resource Specifications page.

   • Click the Go to previous page link on the top left to return to the Initiatives Items tab in the initiatives editor page.

Updating Resource Specifications

You can update the configuration, design parameters, characteristics, parameter mapping, design policies, delivery policies and general information. You can update the primary domain and the secondary domains if the specification does not have any components or any child specifications associated with it.

Note:

You can update a resource specification only if the associated initiative is in Definition and Advanced Configuration status.

To update a resource specification:

1. In the Solution Designer landing page, click the application that you want to work with.

2. Do one of the following:

   • In the Resource Specifications application, search for a resource specification and open the resource specification.

   • In the Initiatives application, search for an initiative and click the Initiative Items tab in the initiatives editor page. Select a specification to update the details.

   The specifications editor page opens.

3. You can update the specification configurations, design parameters, characteristics, parameter mappings, design policies, delivery policies, and general information for the respective specifications. See "Configuring Service and Resource Specifications" for more information on updating the resource specifications.
4. Do one of the following:

   • Click the Go to Resource Specifications link on the top left to return to the Resource Specifications page.

   • Click the Go to previous page link on the top left to return to the Initiatives Items tab in the initiatives editor page or the parent specification page from where this specification is opened.

Cloning Resource Specifications

You can clone an existing resource specification and update the details as necessary. Cloning the resource specification copies the specification and its details such as the configuration, design parameters, entity characteristics, and general information. The parameter mapping, design policies, and delivery policies are not copied when cloning a specification. The cloning process creates a new copy of the specification with the same name appended with - Copy. You can update the specification name and its details such as the configuration, design parameters, entity characteristics, and general information.

To clone a resource specification:

1. In the Solution Designer landing page, click the application that you want to work with.

2. Do one of the following:

   • In the Resource Specifications application, search for a specification.

     In the specifications result list page, click Clone.

     The Clone Specification pop-up appears. Specification includes resource and location.

   • In the Resource Specifications application, search and open the specification.

     The specifications editor page opens. Click the Clone in the specifications editor page.

     The Clone Specification pop-up appears. Specification includes resource and location.

   • In the Initiatives application, search and select an initiative. Click the specification in the Initiative Items tab in the initiatives editor page.

     In the specifications editor page, click Clone.

     The Clone Specification pop-up appears. Specification includes resource and location.

3. Update the name, ID, and description as necessary. See "About Naming Rules" for more information on naming rules for ID.

   Note:

   • You can't select a new initiative when you clone a specification in the Definition and the Advanced Configuration status.
   • You must select a new initiative that is in Definition status when you clone a specification in Released status.

4. Click Continue.

   The specification editor page opens with all the details.

   You can update the configuration, design parameters, entity characteristics, and general information. You may configure parameter mapping, design policies, and delivery policies after cloning, as those are not copied when cloning a specification.

Revising Resource Specifications

A service specialist or a network specialist revises a resource specification in the Released status. A network specialist revises a resource or location specification. When you revise a specification, you create a revision of the specification that you attach to an initiative in Definition status. The original specification definition, which is attached to an initiative in Released status, does not change. You can update the details of the revised specification such as the configuration, design parameters, characteristics, parameter mappings, design policies, delivery policies, and general information. When you delete a revised specification, only the current revision is deleted and the specification is reverted to the previously released version.

To revise a resource specification:

1. In the Solution Designer landing page, click the application that you want to work with.

2. Do one of the following:

   • In the Resource Specifications application, search a specification.

     The specification is listed in the results section.

   • In the Resource Specifications application, search and open a specification.

   • In the Initiatives application, search for an initiative and click the Initiative Items tab in the initiatives editor page. Select a specification.

     The specification editor page opens.

3. Click Revise.

   The Revise Specification dialog box opens. Specification includes resources and locations.

4. Select an initiative that is in the Definition status and click Continue.

   The corresponding specification editor page opens.

5. The configuration, design parameters, entity characteristics, parameter mapping, design policies, delivery policies, and general information can be modified for the revised specification. See "Updating Resource Specifications" for more information on modifying specification details.

Deleting Resource Specifications

You can delete a specification from the Specifications application or from the Initiative Items tab in the initiatives editor page in the Initiatives application.

To delete a resource specification:

1. In the Solution Designer landing page, click the application that you want to work with.

2. Do one of the following:

   • In the Resource Specifications application, search for a specification.

     The specification is listed in the results section.

   • In the Resource Specifications application, search for and open a specification.

     The specification editor page opens.

   • In the Initiatives application, search for an initiative and click the Initiative Items tab in the initiatives editor page. Open a specification.

     The specification editor page opens.

3. Click Delete.

   A confirmation dialog box appears.

4. Click Delete in the confirmation dialog box.

   The specification is deleted if it is not associated with any other specifications or PSR models. If you are deleting a revised specification, only the current revision is deleted and the specification reverts to the previously released version.

Note:

You can't delete a resource specification after you complete the Advanced Configuration phase of the associated initiative.