oracle communications metasolv solution auto-provisioning for

MetaSolv Solution

Auto-Provisioning for Template-Based Services

White Paper

March 2007

Copyright and Trademark Information

2007 Oracle Corporation. All rights reserved. MetaSolv is a trademark registered in the United

States of America by Oracle Corporation. All other trademarks contained herein are property of

their respective owners. Any rights not expressly granted herein are reserved. Information

contained herein is subject to change without notice.

Disclaimer

All references to future incorporation of new or enhanced product functionality, or to future

release dates, are estimates only, and Oracle may change them at any time, without notice.

Information in this document is subject to change without notice and does not represent a

commitment on the part of Oracle Corporation. All references to new or enhanced product

functionality, or to future release dates, are estimates only, and Oracle may change them at any

time, without notice.

The software and/or databases described in this document are furnished under a written license

agreement or nondisclosure agreement. No part of this document, the software and/or databases

may be used, reproduced or transmitted in any form or by any means, electronic or mechanical,

including copying, photocopying, recording, or information storage or retrieval systems, for any

purpose without the written permission of Oracle Corporation, except as specifically allowed in

the written license or nondisclosure agreement. It is against the law to copy the software on any

medium except as specifically allowed in the license or nondisclosure agreement.

Oracle Corporation assumes no responsibility or liability for any errors or inaccuracies that may

appear in this manual. Use of any of this Softwares functionality in a manner inconsistent with

your license grant, whether or not protected by the Product ID, is a breach of the license

agreement between your company and Oracle. A listing of the software options for which you

possess a license may be viewed by navigating to Software Options. This Software contains

sample network system templates ("Templates"). Oracle does not provide, and is not obligated to

provide, Standard Maintenance and Support for the Templates or any modifications made

thereto. The Templates are delivered as is and without warranty of any kind.

Printed in U.S.A.

Oracle Corporation

5556 Tennyson Parkway

Plano, TX 75024 U.S.A

MetaSolv Software, Inc. 1

Table of Contents

About this guide..................................................................................................................................................... 3

Audience........................................................................................................................................................... 3

Additional information and help........................................................................................................................ 3

Global Customer Care...................................................................................................................................... 4

Chapter 1: Overview.............................................................................................................................................. 5

Chapter 2: Infrastructure items.............................................................................................................................. 7

Overview of geographic areas and structured formats ............................................................................... 7

Creating geographic area types.................................................................................................................. 8

Defining the structure format..................................................................................................................... 13

Creating structure format components...................................................................................................... 16

Adding geographic areas to MSS core ..................................................................................................... 24

Adding geographic areas to MSS core ..................................................................................................... 24

Chapter 3: Work Management ............................................................................................................................ 27

System tasks overview.............................................................................................................................. 27

Enhanced system tasks ............................................................................................................................ 28

New system tasks ..................................................................................................................................... 29

Defining a system task .............................................................................................................................. 30

Creating a provisioning plan with the system tasks .................................................................................. 31

Chapter 4: Network templates and design .......................................................................................................... 33

Overview of network templates and network design ................................................................................ 33

Building a network template ...................................................................................................................... 33

Building a network system ........................................................................................................................ 36

Service applications overview................................................................................................................... 39

Equipment assignment template (EAT) overview..................................................................................... 39

Creating service applications and EATs ................................................................................................... 39

Examples of service applications and EATs............................................................................................. 40

Chapter 5: Network areas.................................................................................................................................... 45

Overview of network areas........................................................................................................................ 45


Creating a network area............................................................................................................................ 45

Chapter 6:Product specifications and product catalog........................................................................................ 51

Overview of product specifications ........................................................................................................... 51

Overview of the product catalog ............................................................................................................... 51

Creating product specifications................................................................................................................. 52

Creating the product catalog..................................................................................................................... 58

Creating IP address rules.......................................................................................................................... 59

Chapter 7:End-to-end DSL service scenario....................................................................................................... 63

Overview of end-to-end DSL service scenario.......................................................................................... 63

Entering a PSR ......................................................................................................................................... 64

Assigning a provisioning plan ................................................................................................................... 71

Reviewing the results of the system tasks ................................................................................................ 72

O V E R V I E W


About this guide

This guide contains the procedures and information you need to configure the software to facilitate

auto-provisioning of template-based services.

Audience This guide is for individuals responsible for the configuration and maintenance of Engineering and

PSR Ordering in MetaSolv Solution.

Additional information and help To get information or help for MetaSolv Solution, see the MetaSolv Web site at www.metasolv.com.

From the home page of the Web site, log on to the customer portal page using your customer ID and

password. On the customer portal page, the following links provide access to additional documents

and Global Customer Care (GCC):

Product Downloads and Documentation

Click this link to view and download documentation for MetaSolv products you have purchased.

The Product Downloads and Documentation page contains documentation for all releases, and

also has a list of frequently asked questions.

Customer Support

Click this link to display the Global Customer Care page. This page contains support information

for individual MetaSolv products and GCC information on available services.

O V E R V I E W


Global Customer Care MetaSolv Global Customer Care helps report, track, and resolve issues relating to the MetaSolv

product line.

E-mail address:[email protected]

Telephone (U.S. and Canada):888-884-7686

Telephone (International):972-403-8400

FTP site:ftp.metasolv.com

Internet access:www.metasolv.com

The preferred method of reporting issues is through the customer portal of the MetaSolv Web site.

When you access the portal, you are prompted for a user logon ID and password. Issues submitted

through the portal are entered directly into MetaSolvs problem management system. When you

submit an issue, you receive an e-mail message that acknowledges the issue and contains the assigned

ticket number. If you do not receive an e-mail confirmation within 15 minutes, contact Global

Customer Care by phone to ensure that your issue was successfully logged.

For Severity 1 Emergency issues that affect production, call Global Customer Care immediately upon

submitting an issue through the customer portal. This step helps avoid delays that can arise with the

electronic transmission of an issue. After normal business hours, call only if after-hours support is

covered by the terms of your Support Contract.


Overview

This document describes setup information that is necessary to facilitate the auto-provisioning process

for template-based services. The document describes how the enhanced functionality can be used

through configuration of the MetaSolv Solution application. The example provided focuses on a

specific DSL service scenario. The chapters describe the different areas of the application that require

set up prior to using this functionality to support a DSL service scenario. It is important to note that

other template-based scenarios are applicable; however, this guide only discusses the DSL service

scenario.

It is important to note that this same functionality can also be supported through customization using

custom extensions. Custom extensions refer to customized code written by you that can be executed

at various defined points within MetaSolv Solution called execution points. For detailed information

on how custom extensions work, refer to the Custom Extensions Developers Reference. For detailed

information on how you could support this DSL service scenario using custom extensions, refer

specifically to Appendix A: Supported Execution Points located in the Custom Extension

Developers Reference. In particular, focus on the execution points Select Component or Element and

Select Port Address.

1


The following is a list of the individual chapter descriptions.

Chapter 1: Overview

Chapter 2: Infrastructure This chapter provides an overview of configuring a new structured format and adding the

appropriate geographic areas to facilitate the automation process.

Chapter 3: Work Management This chapter describes existing system tasks that have been enhanced, as well as new system

tasks, that are used to automate the provisioning process. It also covers the proper set up of a

provisioning plan to ensure all of the tasks are placed in the correct order.

Chapter 4: Network templates and design This chapter describes the necessary steps to configure network templates to define the rules

for network system design.

Chapter 5: Network areas This chapter describes the process for setting up a network area and associating the applicable

network system and network elements/components as well as IP addresses and geographic

areas.

Chapter 6: Product specifications and product catalog This chapter covers the basics of setting up the product specifications and product catalog to

build a product used to order the auto-provisioned service. The process for setting up an IP

address rule to support auto-assigning an IP address to a PSR order is also covered.

Chapter 7: End-to-end process This chapter provides a review of the end-the-end process and show how all of the pieces of

the process fit together to complete the auto-provisioning process for the template-based DSL

service.

I N F R A S T R U C T U R E I T E M S

MetaSolv Software, Inc.

7

Infrastructure items

Overview of geographic areas and structured formats

The MetaSolv Solution (MSS) Utilities application provides the ability to define geographic areas and

structure formats which are used in the auto-provisioning of template-based services included in the

MSS 6.0.11 service pack. geographic areas are defined as either geographic or geographic-political

areas of an address. This data is defined in the MSS Utilities application, while the actual geographic

areas using actual data is defined in the MSS core application.

Structure formats provide a way to enter, define, and store structure and formatting information for

addresses. Since address structures can vary from country to country, the structure formats

functionality uses geographical areas, geographical area types, MetaSolv Solution processes, and

industry versions to provide the flexibility needed in setting up the appropriate structures. This data is

defined in the MSS Utilities application, and then used in the MSS core application.

2



8

Creating geographic area types

The following screenshots show the standard geographic area types (GATs) of country, state, city, and

a new fourth level called area. This new geographical area type further defines a specific region inside

a city and can be used to associate to a network area (discussed in Chapter 5) to facilitate the auto-

provisioning for the template-based service. In the following example, the country is United States,

the state is Texas, and the city is Dallas. The areas within Dallas are defined later.

From the MSS Utilities application, select Options>Geographic Area Types from the menu bar. The

Geographical Area Type window opens, as shown below. The GAT country associated is the United

States; this information is located on the GAT Country tab.

On the GAT Relationships tab, the Parent Country United States is associated to the Child GAT

STATE (see bottom portion of window). This builds the relationship so that a state can be defined for

a country.



9

The Geographical Area Type window is shown below for STATE. The GAT country associated is the

United States; this information is located on the GAT Country tab.

On the GAT Relationships tab, the Parent Country United States and Parent GAT STATE is

associated to the Child GAT CITY (see bottom portion of window). This builds the relationship so

that a city can be defined for a state.



10

The Geographical Area Type window is shown below for CITY. The GAT country associated is the

United States; this information is located on the GAT Country tab.

On the GAT Relationships tab, the Parent Country United States and Parent GAT CITY is associated

to the Child GAT AREA. Area is the new level of address definition to further define a region within

a City. This builds the relationship so that an area can be defined for a city.



11

The Geographical Area Type window is shown below for AREA. The GAT Country associated is the

United States.

In the GAT Relationships, nothing further is defined since this is the lowest level defined. The

application allows for further definition, but for the auto-provisioning of the DSL service scenario

described in this document, further definition is not necessary.



12

On the Geographic Area Type window for COUNTRY, you can view the geographical area

hierarchy. As shown below, the hierarchy defined for this scenario is

COUNTRY>STATE>CITY>AREA.



13

Defining the structure format

From the MSS Utilities application, select Options>Structured Formats>Structured Formats from

the menu bar. This is where structure formats are defined and maintained. The following is a sample

of the structure format data that was defined to complete the auto-provisioning of the DSL service

scenario described in this document. When defining a new structure format, it is recommended that

you perform a New From on an existing structure format, and then modify the necessary information.

A sample structured format, CL DSL STRUC FORMAT, was created to show the setup that is

required.



14

The processes below are associated to the structure format for the auto-provisioning of the DSL

service scenario described in this document.

The Country United States is associated to the structure format.



15

The components below are associated to this structure format. Before components can be associated

to the structure format, they must first be created. Refer to the next section, Creating structure format

components, for detailed information on this process.

When the new CL DSL structure format is used, the Data Entry Display tab for a customer address in

MSS looks like the one below. The fields State, City Name and Area are each dependent on its

defined parent.



16

Creating structure format components

From the MSS Utilities application, select Options>Structured Formats>SF Components from the

menu bar. This is where structure format components that are used to create a structure format are

defined and maintained. The address structure format used in this scenario is the CL DSL

STRUCTURED FORMAT TEST.

The structure format data was previously created and is shown here to illustrate how it could be set

up. This is not a best practice for how the structure format should be created (referring to the

components associated) but was used to show how the configuration of the data could be set up for

the auto-provisioning DSL service scenario described in this document.



17

The following screenshots show the structured format components of Country, State, City, and Area.

Below is the Structured Format Component window General tab for Country.

Below is the Structured Format Component window Relationships for Country.



18

Below is the Structured Format Component window Geographical tab for Country.

Below is the Structured Format Component window General tab for State.



19

Below is the Structured Format Component window Relationships tab for State.

Below is the Structured Format Component window Geographical Areas tab for State.



20

Below is the Structured Format Component window General tab for City.

Below is the Structured Format Component window Relationships tab for City.



21

Below is the Structured Format Component window Geographical Areas tab for City.

The new fourth level of geographical area type was an enhancement in the MSS 6.0.11 service pack

that allows for customers to further define a geographic location. The DSL service scenario described

in this document uses this additional level in the address structure, and defines it as Area.

With this enhancement, seven columns on the NA_GA_INSTANCE table are available for use. Based

upon the hierarchy of the Geography Area Types, when the data is saved to the database, the columns

on the na_ga_instance table are populated.

The first GAT is stored in the ga_instance_id_country column.

The second GAT is stored in the ga_instance_id_state column.

The third GAT is stored in the ga_instance_id_city column.

The fourth GAT is stored in the ga_instance_id_addr_gat_comp1 column.

The fifth GAT is stored in the ga_instance_id_addr_gat_comp2 column.

The sixth GAT is stored in the ga_instance_id_addr_gat_comp3 column.

The seventh GAT is stored in the ga_instance_id_addr_gat_comp4 column.

Additionally, the Geographical Areas tab on the Network Area Maintenance window will be modified

to use the additional four columns that are added to the na_ga_instance table. With these

modifications, the Country that the network area is in will drive the User Interface (UI) and the fields

on the Geographical Areas tab. The Geographical Areas tab would show only four fields when a

network area is selected or created for a Country.



22

In order for the new enhancement to support template-based auto-provisioning, users would have to

incorporate the new GATs into an address structure format. They would then use this address

structure format when creating their end user locations on a product service request (PSR).

Below is the Structured Format Component window General tab for Area.

Below is the Structured Format Component window Relationships tab for Area.



23

Below is the Structured Format Component window Geographical Areas tab for Area.



24

Adding geographic areas to MSS core

After the geographical area types have been defined in the MSS Utilities application, you can then

enter the actual geographic areas in the MSS core application.

1. Select Application Setup on the navigation bar.

2. Click the Location and Geography Setup link.

3. Click the Geographic Areas link.

4. Expand the GEO AREAS folder.

The screenshot below shows the available countries.



25

Continue to expand the folders.

5. Expand the COUNTRY United States folder.

6. Expand the STATE Texas folder.

7. Expand the CITY Dallas folder.

The screen shot below shows the state, city and areas associated under the country, United States.

W O R K M A N A G E M E N T


26



27

Work Management

System tasks overview

A system task is a task designated to automatically complete without user intervention. The tasks in

the system queue are polled until predecessor tasks and gateway events are completed and the system

tasks are ready to be completed. Then, the system tasks are worked and automatically completed.

You must designate a task as a system task to send it to the system queue for automatic completion.

You may transfer a task from the system queue to another work queue for manual processing before

the System Task Server completes the task. By transferring the task from the system queue, you do

not remove its system task property. The next time the task is generated, it is sent to the system queue

again unless you change the task type. If for some reason, the task cannot be completed by the system

work queue, it fails and is automatically moved to the exception work queue. After a task is in the

exception work queue, the problem can be fixed and the task moved back to the system work queue or

the task can be manually worked from the exception work queue.

This chapter addresses the new and enhanced system tasks used to complete the auto-provisioning for

template-based services and the DSL service scenario described in this document.

3



28

Enhanced system tasks

Following is a list of the enhanced system tasks:

CKTID-circuit identification

This task is not new or enhanced in 6.0.11 but is included in this chapter because it can be

used in the auto-provisioning scenario. If this task is set as a system task and included in a

provisioning plan, the circuit identifications of the service items ordered on the PSR are

automatically generated and the task completes.

EQ INST-equipment install for customer premise equipment (CPE)

This existing task was enhanced in 6.0.11 to allow for it to be a system task. Prior to this

enhancement, the EQ INST task could be used in a provisioning plan to install CPE that was

ordered on a PSR under a service location. With the new enhancement, CPE ordered is now

automatically installed at the service/end user location if the task is included in a provisioning

plan. Another new enhancement has been added that also affects this task. CPE can now be

added as a child product beneath a network connection (item type) if the connection is a

physical connection and associated to a template type (connection spec). So, with this new

enhancement, a product catalog hierarchy of Product Bundle>Network Connection>CPE

can be created. The equipment installs at the end user location defined in the ordering dialogue

of the PSR.

IPASSIGN-assign an IP address to the PSR

This is not new or enhanced in 6.0.11 but is included in the chapter because it can be used in

the auto-provisioning for DSL service scenario described in this document. If this task is set as

a system task and included in a provisioning plan and the IP address rules have been set up

properly, when IP addresses are ordered in the PSR, an IP address is automatically assigned

and the task completes. For additional details regarding setting up IP address rules, refer to

Chapter 6.



29

New system tasks

Following is a list of the new system tasks:

PCONDES-physical connection design

This system task is new to 6.0.11 and is used to automatically perform the physical connection

design for new connections on a PSR order. More details regarding the setup involved in order

for this task to work as a system task is included in the subsequent chapters of this document.

VONDES-virtual connection design

This system task is new to 6.0.11 and is used to automatically perform the virtual connection

design for new connections on a PSR order. More details regarding the setup involved in order

for this task to work as a system task is included in the subsequent chapters of this document.

AUTO_ISS-automatically record or DLR issue the connections

This system task is new to 6.0.11 and is used in conjunction with the PCONDES and

VCONDES tasks. Auto Issue automatically Records or DLR Issues the physical and virtual

connections completed in the PCONDES and VCONDES tasks.



30

Defining a system task

Before a task can be set up as a system task, a system work queue and an exception work queue must

be established. These work queues should be defined in Work Management>Work Queues and

assigned an owner. Then, these work queues should be referenced in Preferences under

Work Management>Work Queue Management.


2. Click the Work Management Setup link.

3. Click the Tasks link.

4. Open one of the tasks with the system task capability.

5. Select the System Task checkbox and populate any other data necessary.

6. Click OK

Note about system tasks: A task that is to work as a system task can only be added to a

provisioning plan as a system task if the System Task checkbox is selected on the Task Type

window. Tasks set as system tasks do not have to be added to a provisioning plan as a system

task but can be set to perform as a smart task instead (double click functionality).



31

Creating a provisioning plan with the system tasks

The following is an example of a provisioning plan using all of the system tasks to complete the auto-

provisioning for DSL service scenario described in this document. The Provisioning Plan window

General Information tab is shown below.

The tasks included in this plan, on the Task Assignment tab, are all shown below as system tasks and

are worked and completed by the system work queue.

The order of the tasks is very important in this DSL service scenario. The CKTID task should be first

to define the circuits for the ordered service items. The EQ INST task should be next to install the

CPE at the customer site prior to the PCONDES task being worked and assignments are made to the

CPE and the network DSLAM. The VCONDES task can then be worked to complete the virtual

connection design, after the physical connection design is complete. The AUTO_ISS task Records or

DLR Issues the connections. The IPASSIGN task automatically assigns an IP address to the PSR

order and the DD task puts all of the ordered services in an In Service status.

N E T W O R K T E M P L A T E S A N D D E S I G N


33

Network templates and design

Overview of network templates and network design

Network templates are included as base data in each of the technology modules. The technology

modules represent different types of technologies within MetaSolv Solution and contain the rules for

how network systems can be built.

Some of the rules that are included are:

The type of network elements/components that can be used in a network system,

The type of connections between network elements/components in a network system; and

The properties of each network element/component and connection within a network system.

Building a network template

The following example shows the network templates built in the unclassified technology module.

Typically, a technology module that represents a customers backbone network would be used.

To access network templates:


2. Click the Inventory Management Setup link.

3. Click the Network Templates link.

4 4



34

The following is an example of a Core Network Template that was created for the DSL service

scenario described in this document and contains two network components, the BRAS and a tier 1

aggregation switch. In our example, an assignable bandwidth link connection spec is associated to the

relationship between the two components. Neither of these network items are represented as a

network element or associated to a network element type.

The following is an example of an Access Network Template that was created for our scenario and

contains one network element, the DSLAM and one network component, the tier 2 GIGE LAN

switch. In this example, a DSL link connection spec is associated to the relationship between the

DSLAM network element and tier 2 GIGE LAN switch network component.



35

The following is an example of a DSL Network Template that was created for our scenario and

contains the core and access network templates as well as the customer site network component. In

our example, a DSL link connection spec is associated to the relationship between the customer site

and the DSLAM and an internet connection spec is associated to the relationship between the

customer site and the BRAS.

When a DSL link is ordered on a PSR, the PCONDES task knows to make an assignment to the CPE

at the customer site and to the equipment associated to the DSLAM. When an internet connection is

ordered on a PSR, the VCONDES task knows to make the appropriate assignments from the customer

site to the DSLAM and then through the network terminating at the BRAS.



36

Building a network system

Once network templates are created and the rules are defined, network systems can be created.

Networks can only be defined with the rules set forth in the network templates.

The following is an example of a Core Network System built using the core network template. As

you can see, there are five BRAS network components and five tier 1 GIGE aggregation switches

included. Only the BRAS and the aggregation switches are connected because that is what the

template rules defined.



37

In the DSL service scenario described in this document, two separate Access Network Systems were

created using different locations for each of the DSLAMs. This process is explained in Chapter 5:

Network areas. In this network system, there are three DSLAMs connected to one tier 2 GIGE

switch. In the network template, we defined that a DSLAM could only be connected to a tier 2 GIGE

switch and that is exactly what is shown here.

In this network system, there are two DSLAMs connected to one tier 2 GIGE switch.



38

In the overall DSL Network System, there are two embedded access network systems and the

embedded core network system. During the provisioning process, depending on information captured

about the end user location, the correct DSLAM is selected automatically and a path is found to the

correct terminating BRAS, located in the core network system.



39

Service applications overview

Service applications are user-defined classifications for connections that allow connections to be

designed on a consistent basis. The purpose of service applications is to assist you in categorizing the

connections in your network. Service applications also classify and select paths and equipment

assignment templates used in auto-provisioning the connections. Each service application defines a

service offered and the connection spec for which the service is intended.

Service applications in the auto-provisioning of template-based services are used by the PCONDES

task to determine a specific equipment spec or equipment type for port assignments on the physical

connection. The connection type of the connection along with the product specification of the ordered

product is used to find the correct service application.

Equipment assignment template (EAT) overview

An equipment assignment template (EAT) is a list of all the equipment needed to auto-provision a

circuit for a particular type of service, such as internet dedicated access. The template contains

specifics regarding rate codes, equipment specifications, and service applications. You can define an

EAT to support multiple rate codes or service applications.

Each EAT must be given a unique, user-defined name. EATs allow you to designate generic

equipment types, such as a DACS card, or designate a specific brand or model of equipment through

the use of an equipment specification.

At auto-provisioning time, equipment specifications included in an EAT are used to find installed

equipment in a network location and make the necessary assignments. EATs are applied only at the

terminating points of the design.

In the auto-provisioning of template-based services, the service application is used to determine the

equipment assignment template (EAT). This is an optional process that allows the user to select

between two cards on one component/element, for example in the case where both an ADSL card and

an SDSL card exists. If no equipment assignment template is defined, the process finds the first

available port on any card matching the rate code of the connection being designed.

Creating service applications and EATs

Service applications and EATs are found on the Inventory Management Setup page, in the Connection

Design section.



40

Examples of service applications and EATs

In the DSL service scenario described in this document, two separate service applications (DSL and

ADSL) have been defined and they are associated to different EATs. This is done to distinguish

between two different types of service offered from one DSLAM. The service applications are built

the same but each EAT is associated to a different service application and designates a different card

to be used for equipment port assignments. Below is the service application that is built to support

standard DSL service.

On the Service Application window Definition tab, a connection type and product specification are

associated. The connection type is the same as the connection spec that is defined in the network

template. The physical connection product specification is also associated to the same connection

spec. More information regarding product specifications can be found in Chapter 6.



41

Below is the first Equipment Assignment Template (EAT) page for standard DSL service. The two

checkboxes on this window for port assignments enforce that, during the provisioning process, an

equipment port assignment is made at the CPE installed at the end user location and an equipment

port assignment is made to the DSLAM.

On the Details tab, a rate code and service application are associated.

On the Specifications, Types and Options tab, equipment specifications are associated. In this case,

the equipment specification is the card at the DSLAM that supports standard DSL service.



42

Below is the Service Application window which shows the service application that is built to support

ADSL service.

On the Service Application window Definition tab, a connection type and product specification are

associated.



43

Below is the EAT defined for ADSL service. The two checkboxes on this window for port

assignments enforce that, during the provisioning process, an equipment port assignment is made at

the CPE installed at the end user location and an equipment port assignment is made to the DSLAM.

On the Details tab, a rate code and service application are associated.

On the Specifications, Types and Options tab, equipment specifications are associated. In this case,

the equipment specification is the card at the DSLAM that supports ADSL service.



44

N E T W O R K A R E A S


45

Network areas

Overview of network areas

A network area is a user-defined feature. It can be defined as a single floor in a building, a building

complex, an entire city, or an even larger geographical area. It is a grouping of network items and end

user locations than can be defined to support local calling areas, rate centers, telephone number areas,

serving areas, or a unique business need.

A network area can include:

End user and network locations

Number inventories, for example IP addresses

Network items, for example, switches and DSLAMS

Geographic areas

For the auto-provisioning for template-based services to work, there are certain items that need to be

set up correctly in the network area. The following processes show the details of the setup.

Creating a network area


2. Click the Inventory Management Setup link.

3. Click the Network Areas link located under the Network Areas section.

4. Complete the required fields.

4

5



46

In the DSL service scenario described in this document, there is one network area configured

per DSLAM and associated to the network area is one geographic area. By associating just

one DSLAM and one geographic area, when a PSR order is submitted with an end user

location associated to a specific geographic area, the correct network area is found and an

assignment is made to a port on the DSLAM. If more than one DSLAM is associated, an

assignment to the first available port, regardless of the DSLAM, is made.

5. Select the Network Items tab.

6. The network system that includes the DSLAM should be associated first and then the actual DSLAM in the network system be associated. If more than one DSLAM is to be associated, it

would be done here too.



47

7. On the Geographic Areas tab is where the geographic areas are associated. Allowing an association to a fourth level of the geographic area is part of the enhancement made to geographic

areas described in Chapter 2. The fourth level in this example is the geographic area Area.



48

The following example shows the network area used to associate the BRAS (terminating element for

the internet connection) and IP address inventory as well as geographic areas.

8. In order to associate IP addresses to a network area, the network area type of IP Area must be associated on the General tab.

9. On the Number Inventory tab, associate existing IP address inventory with this network area.



49

10. The network system that includes the BRAS should be associated first and then the actual BRAS in the network system be associated.

11. On the Geographic Areas tab is where the geographic areas are associated. As you can see, a network area can be associated to more than geographic area.

P R O D U C T S P E C I F I C A T I O N S A N D P R O D U C T C A T A L O G


51

Product specifications and

product catalog

Overview of product specifications

Product specifications are items used to create a template for the products your company offers. The

product specification function lets you:

Define the products you offer to your customers.

Define related items offered with each product.

Indicate how the product specification can be used in the product catalog.

Overview of the product catalog

The product catalog defines the products, features, and options your company offers. The product

catalog lets you:

Define items (products and services) offered to your customers.

Set up a hierarchy of related products

Define default values

4

6



52

Creating product specifications

The DSL service scenario described in this document requires several product specifications to be

created in order to support the ordering of the products to be auto-provisioned. Following are

screenshots and a description of the all of the product specifications built to support the process.

To create a product specification:


2. Click the Order Management Setup link.

3. Click the Product Specifications link located under the PSR section.

4. The first product specification is for Customer Premise Equipment (CPE) and the Item Type Customer Premise Equipment/Equipment is used to build this product specification.



53

5. On the Equipment Spec tab, it is necessary to associate an equipment spec. Only equipment that does not occupy mounting positions and that is marked as CPE Capable (on the Equipment Spec)

can be associated. More than one equipment spec can be associated to the product specification.

For the EQ INST system task to work, the CPE cannot occupy mounting positions in other

equipment.

6. The product bundle is the level 1 product specification that is created. When you first create the

product bundle, there are no available items to associate as they have not been created yet.



54

7. The Network Connection/Connector for the physical connection is created next using an item type of network connection. The connector is the product specification that represents the ordered

DSL link from the customer premise to the DSLAM.

8. A network template type (or connection spec) is then associated to the physical connection. The

connection spec is the same one that is associated in the network templates that were defined at

the beginning of the process.



55

9. The Network Connection/Connector for the virtual connection is then created, also using the item type of network connection. This connector is the product specificaiton that represents the

ordered internet connection from the customer premise to the BRAS or other terminating

component.



56

10. A network template type (or connection spec) is then associated to the virtual connection. The connection spec is the same one that is associated in the network templates that were defined at

the beginning of the process.

11. In this DSL service scenario, we also order an IP address on the PSR order. Below is the product

specificaiton created to order an IP address.



57

12. After all of the individual product specifications are created, it is necessary to associate the product specifications to the product bundle product specification. Below shows the different

product specifications associated to the product bundle.

New item type relationship: In 6.0.11, it is a new enhancement to be able to associate the

customer premise equipment product specification to the network connection product

specification. In order to make the association, the network connection must be associated to a

physical connection specification on the Network Template Type tab. With this enhancement,

customers are now able to order the CPE in the PSR ordering dialogue along with the

template-based connections and take advantage of using the EQ INST system task. In order

for the EQ INST task to work though, only one end user location/service location can be

added in the ordering dialogue. If more locations exist, the system cannot determine which

location the CPE should be installed and therefore, the system task would fail and move to the

exception work queue.



58

Creating the product catalog

To create a product catalog item:


2. Click the Order Management Setup link.

3. Click the Product Catalog link located under the PSR section.

The available product specifications from which to select are presented and the product catalog items

can be built.

Below is a screenshot of the DSL product bundle built for the DSL service scenario described in this

document. When the product catalog item for the product bundle is added, a Service Category and

Offering Type must be specified.



59

Creating IP address rules

You can auto-assign an IP address to a PSR based on assignment rules you define in the inventory. If an IP address is not available to be assigned based on the rule, you can choose to auto-create the address and have it assigned to the order. This feature allows you to limit the amount of IP address inventory you must manually create because you can automatically subnet your inventory as needed.

To create an IP address rule:

1. Select Inventory Management on the navigation bar.

2. Click the IP Address Rules link.

3. Click the Add New link.

4. On the IP Rule Information tab, enter the required fields.



60

5. Click the IP Rule Criteria tab.

6. If IP addresses already exist in IP inventory and have a use group/use code assigned, it is best to also associate those here to narrow the criteria. The network area and network item can also

be associated.

7. Select a Type of address to Auto Assign from the drop-down in the Auto Assign Criteria section.



61

8. Click the IP Rule Association tab, and select the product catalog IP address item to associate to this rule. This tells the system that when the IPASSIGN system task is used and this

particular product has been ordered, the rules set here are followed.

If items occur more than once in the list below, it is because the product specification has been

used more than one time to build product catalog items. Hovering over the item with the

mouse shows the Item Hierarchy (product catalog item) that this product is associated to.

E N D - T O - E N D D S L S E R V I C E S C E N A R I O


62



63

End-to-end DSL service scenario

Overview of end-to-end DSL service scenario

The auto-provisioning of the DSL service scenario described in this document follows the flow

outlined below:

Enter a PSR order with a new customer account and assign a provisioning plan.

Review the system tasks that were automatically completed and the functionality that was completed behind the scenes. The system tasks included are as follows:

o CKTID-connection identification

o EQ INST-equipment install

o PCONDES-physical connection design

o VCONDES-virtual connection design

o AUTO_ISS-auto issue

o IPASSIGN-IP address assignment

4

7



64

Entering a PSR

To enter a PSR:

1. Select Order Management on the navigation bar.

2. Click the New Product Service Request link.

3. Click the Address icon.

In this DSL service scenario, a service category of residential is selected because that is how our

product catalog item is built. Also, in order for auto-provisioning to work correctly, the correct

structure format on the Address Maintenance window must be selected and the correct geographic

area (Area) that is associated to one of the previously defined network area must also be selected.

4. Click OK on the Address Maintenance window.

5. Click OK on the Create or Select a Customer for a New Product Service Request window.



65

6. Enter the required information on the Order Info tab.

7. Click the Services link.

8. Select the Global icon, right click and select Add New Item from the pop-up menu.



66

9. Select the DSL product and click Yes to configure the product.

10. The IP address product was the first item in the ordering dialogue to display. If this product is

desired, click the check box next to it and select the Next button.



67

11. On the New Location page, click the use the customer primary billing address link to default the end user location address information. In this DSL service scenario, only one end

user location address is allowed (in order for the EQ INST system task to work).

12. Click the Next button.

13. Click the Next button again.



68

14. Select the available connectivity cell to represent where connections can be added and click the Next button.

15. Select the applicable checkbox and click the Add button to add a connection.

16. If the CPE product is a child of the physical connection, it displays as an option on the window after the Add button is selected on the above window. Select the check box and click the Next

button to order the equipment too; otherwise, just select the Next button.

17. Select the virtual connection from the Connection Type dropdown and select the applicable checkbox and click the Add button to add a connection.



69

18. Click the Next button.

19. Enter the necessary Custom Attributes for the first connection. The rate code is necessary in this scenario to correctly find the port at the end user location and DSLAM, as shown when

the EAT was configured.

20. Click the Next Connection button.

21. Enter the necessary Custom Attributes for the second connection.

22. Click the Next Connection button if there are additional connections, or click the Done button if this is the last one.



70

23. From the PSR Services view, expand the product and select the CPE product. Select the applicable Equipment Spec from the drop-down. Click a different product and select to save

the changes when prompted.



71

Assigning a provisioning plan

1. Continuing from the steps above, click the Finish Order link.

2. Select a provisioning plan on the Plan Selection tab.

3. All of the tasks in the provisioning plan are assigned to the system work queue. Assign any remaining tasks to the appropriate work queue and click OK.



72

Reviewing the results of the system tasks

The CKTID task completed automatically and assigned the CKTIDs to the ordered connections.

Below, the PCONDES, VCONDES and AUTO_ISS tasks have all been completed by the System

Task Server.

This is the network system information automatically associated based on the network area

configuration and the association to the geographic area Area.

Here are the port assignments that were made to the installed CPE at the Customer site and the

DSLAM.



73



74

This is the network system associations for the virtual connection.



75

And here, the VCONDES task automatically found a path through the different networks and created

the schematic design.



76

Here the IPASSIGN task has automatically made an IP Assignment to the PSR order.


77

ContentsOverviewInfrastructure itemsWork ManagementNetwork templates and designNetwork areasProduct specifications and product catalogEnd-to-end DSL service scenario

oracle communications metasolv solution auto-provisioning for

Documents