MetaSolv Introduction

Work Management 2-1

Unit 2Preparing the MetaSolvUnit 2Preparing the MetaSolv SolutionSolution

UNIT 2PREPARING THE METASOLV SOLUTION 1

Unit Overview......................................................................................13

SLIDE 1 PREPARING THE METASOLV SOLUTION 13

Why Preparing the MetaSolv Solution is Important.............................13

SLIDE 2 WHY IS THIS UNIT IMPORTANT? 13

1. Introduction to the MetaSolv Solution...............................................15

Overview..............................................................................................15

SLIDE 3 INTRODUCTION TO THE METASOLV SOLUTION15

Lesson 1 Objectives............................................................................15

SLIDE 4 LESSON OBJECTIVES 15

Forty Thousand Foot An Overview of the MetaSolv Solution Subsystems............................................................16

SLIDE 5 FORTY THOUSAND FOOT 16OSS Gateway Management.........................................................................18

SLIDE 6 OSS GATEWAY MANAGEMENT 18Customer Care.............................................................................................19

Proprietary and Confidential Bootcamp

2-2 Unit 2Preparing the TBS SoftwareMetaSolv Solution

SLIDE 7 CUSTOMER CARE 19Network Design............................................................................................20

SLIDE 8 NETWORK DESIGN 20Service Provisioning.....................................................................................21

SLIDE 9 SERVICE PROVISIONING 21Order Management......................................................................................22

SLIDE 10 ORDER MANAGEMENT 22Trouble Management...................................................................................23

SLIDE 11 TROUBLE MANAGEMENT 23Work Management.......................................................................................24

SLIDE 12 WORK MANAGEMENT 24Data Management........................................................................................25

SLIDE 13 DATA MANAGEMENT 25Security.........................................................................................................26

SLIDE 14 SECURITY 26

At the End of this Course.....................................................................27

Bootcamp Roadmap in MetaSolv Solution Software..........................28

SLIDE 15 ROADMAP 28First StopPrepare the MetaSolv Solution..................................................28

SLIDE 16 ADMINISTRATOR HAT 28

MetaSolv Solution 5.0 7/12/2011 D5.0 2001 MetaSolv Software, Inc.

Work Management 2-3

Second StopNetwork Design....................................................................30

SLIDE 17 ENGINEER HAT NETWORK DESIGN 30Third StopCircuit Design...........................................................................30

SLIDE 18 ENGINEER HAT CIRCUIT DESIGN 30Forth StopService Requests.....................................................................31

SLIDE 19 CUSTOMER CARE REPRESENTATIVE HAT 31Fifth StopTrouble Management................................................................32

SLIDE 20 TROUBLE MANAGEMENT HATS 32Final StopWear Everyones Hat................................................................32

SLIDE 21 GRADUATION 32

Log On to the MetaSolv Solution.........................................................33

TogetherNavigate Throughout the Software...................................33

QuickLinks...........................................................................................34

Preferences..................................................................................................34

Default Functionality.....................................................................................34

Customization...............................................................................................36

DEMOQuickLinks......................................................................................36

Help......................................................................................................37

SLIDE 22 HELP 37

Lesson Review....................................................................................38



SLIDE 23 REVIEWINTRODUCTION TO METASOLV SOLUTION 38

2. Infrastructure.....................................................................................39

Overview..............................................................................................39

SLIDE 24 INFRASTRUCTURE 39

Objectives............................................................................................39


Enter Your Information Here................................................................40

The LERG CD......................................................................................41

SLIDE 26 LERG 41

Data Contained In The LERG.............................................................42

States and Cities..........................................................................................43

Operating Companies...................................................................................44

LATAs (Local Access & Transport Area).....................................................45

Central Office (CO) Exchange Areas...........................................................46

NPA/NXX Codes..........................................................................................47

Network Locations........................................................................................48

Manual LERG Load.............................................................................50

Order of Entry......................................................................................50

FYI For Final Obstacle Course............................................................51

Lesson Review....................................................................................52


Work Management 2-5

SLIDE 27 REVIEWINFRASTRUCTURE 52

3. Security.............................................................................................53

Overview..............................................................................................53

SLIDE 28 SECURITY 53

Objectives............................................................................................53


Windows Used.....................................................................................54

MetaSolv Solution Interface.................................................................54

SLIDE 30 POWER BUILDER OBJECTS 54Windows.......................................................................................................54

Window Controls..........................................................................................55

Popup Menus...............................................................................................55

Checkpoints..................................................................................................55

Permissions.........................................................................................55

Default Permissions......................................................................................55

Administrator Capabilities....................................................................56

SLIDE 31 ADMINISTRATOR RIGHTS 56

Basic Steps in a Security Implementation...........................................57

SLIDE 32 SECURITY IMPLEMENTATION FLOWCHART 57

Reports................................................................................................58



Users and Groups...............................................................................58

SLIDE 33 USERS AND GROUPS 58

Passwords...........................................................................................59

Password Requirements..............................................................................59

SLIDE 34 PASSWORD REQUIREMENTS 59Password Expiration Dates..........................................................................60

SLIDE 35 EXPIRATION DATES 60Password Expiration Warnings.....................................................................61

SLIDE 36 CHANGING PASSWORDS 61

Restricting Access...............................................................................61

SLIDE 37 RESTRICTING ACCESS 61Permission Types.........................................................................................62

SLIDE 38 PERMISSION TYPES 62Default Permissions......................................................................................63

User Impact..................................................................................................64

SLIDE 39 PERMISSIONS FLOWCHART 64

SLIDE 40 RULES 64Permissions Group Box................................................................................65

Radio Button Functions................................................................................65

SLIDE 41 RADIO BUTTON FUNCTIONS 65


Work Management 2-7

Restrict Window Access......................................................................66

Checkpoints..................................................................................................66

SLIDE 42 CHECKPOINTS 66Restrict Pop-ups...........................................................................................67

SLIDE 43 POPUP MENUS 67

Lesson Review....................................................................................68

SLIDE 44 REVIEWSECURITY 68

4. Work Management...........................................................................69

Overview..............................................................................................69

SLIDE 45 WORK MANAGEMENT 69

Objectives............................................................................................70


SLIDE 47 LESSON OBJECTIVES (CONTD) 70

Work Management..............................................................................71

SLIDE 48 WORK MANAGEMENT 71

Work Management Puzzle..................................................................72

SLIDE 49 WORK MANAGEMENT PUZZLE 72

Work Queue Set-Up Process Flow.....................................................74

SLIDE 50 WORK QUEUE SETUP PROCESS FLOW 74



Employees...........................................................................................74

SLIDE 51 EMPLOYEES 74

SLIDE 52 EMPLOYEES RULES 74

TogetherCreate a New Employee...................................................76

Work Queues.......................................................................................76

SLIDE 53 WORK QUEUES 76

SLIDE 54 PARENT AND CHILD RELATIONSHIP 76

TogetherView Parent Work Queue..................................................77

TogetherView Child Work Queue....................................................77

Task Types and Checklist Items.........................................................78

Task Types..........................................................................................78

SLIDE 55 TASKS 78Smart Tasks.................................................................................................79

SLIDE 56 SMART TASKS 79

Task Properties....................................................................................80

SLIDE 57 TASK PROPERTIES 80

Task Descriptions................................................................................81

RUNEXE Task.....................................................................................87

SLIDE 58 RUNEXE 87


Work Management 2-9

Checklist Items....................................................................................89

SLIDE 59 CHECKLISTS 89

TogetherCreate Checklist Items......................................................89

Create Provisioning Plans...................................................................90

SLIDE 60 PROVISIONING PLANS 90

Task Properties....................................................................................90

SLIDE 61 TASKS PROPERTIES IN PLAN 90Other Options...............................................................................................91

SLIDE 62 TASK TIMES 92

On-Net and Off-Net Plans...................................................................93

TogetherCreate On-Net Plan...........................................................93

Three Phases of a Provisioning Plan..................................................94

Task Assignment tab...........................................................................94

Task Dependencies Tab......................................................................95

Dating Indicator Field....................................................................................95

Rules for the Dating Indicator Field..............................................................95

Pert Chart............................................................................................96

NPA/NXX Task Assignment................................................................96

Gateway Assignment...........................................................................96

Automatic Plan Selection.....................................................................97



Rules for Automatic Plan Selection..............................................................97

SLIDE 63 AUTOMATIC PROVISIONING PLAN SELECTION97

Rules and Behaviors...........................................................................98

SLIDE 64 RULES/BEHAVIOR 98

Benefits of Rules and Behaviors.........................................................98

SLIDE 65 BENEFITS 98

Example of Using Rules and Behaviors..............................................99

Generate and Modify Tasks..............................................................100

SLIDE 66 GENERATE AND MODIFY TASKS 100

Generating Tasks..............................................................................101

TogetherComplete the Plan Selection Tab....................................102

Work Queues.....................................................................................103

Task Circuits tab.........................................................................................104

PERT Chart Tab.........................................................................................104

Modifying Tasks.................................................................................104

SLIDE 67 MODIFYING TASKS 104Change a Tasks Due Date........................................................................105

APP 09/07/99 105Other Ways to Modify Tasks......................................................................106


Work Management 2-11

TogetherAccess the Work Queue Manager..................................106

Work Queue Manager Map...............................................................107

Work Queue Manager Profiles..........................................................108

SLIDE 68 WORK QUEUE MANAGER 108Tabs at the Bottom of the WQM.................................................................108

Managing Tasks................................................................................109

SLIDE 69 MANAGING TASKS 109

Work Queue Manager Popup Menu..................................................110

Accepting Tasks................................................................................111

TogetherAccept a Task..................................................................111

DemoTransfer a Task....................................................................112

TogetherComplete a Task.............................................................112

Rejecting Tasks.................................................................................112

Why Missed Codes............................................................................113

Jeopardy Codes................................................................................114

SLIDE 70 JEOPARDY CODES AND WHY MISSED CODES114

Entering Escalation Information........................................................116

TogetherEnter Escalation Information...........................................116

Viewing and Entering Notes..............................................................117



Together View and Enter Notes.....................................................117

Gateway Events................................................................................118

SLIDE 71 GATEWAY EVENTS OVERVIEW 118

Benefits of Gateway Events..............................................................118

Lesson Review..................................................................................119

SLIDE 72 REVIEWWORK MANAGEMENT 119

SLIDE 73 REVIEW (CONTD) 119

SLIDE 74 REVIEW (CONTD) 119

Unit Wrap Up.....................................................................................121

SLIDE 75 WRAP UP 121



UNIT OVERVIEWSlide 1 Preparing the MetaSolv Solution

Changing times require new strategies. Its important to stay flexible. At MetaSolv, we recognize that todays converging telecommunications market is challenged with managing a growing number of complex business relationships while supporting a widening variety of new technologies and services. MetaSolvs Solution is designed to help you meet these challenges.

This Unit is designed to provide you with a high-level introduction to the MetaSolv Solution.

WHY PREPARING THE METASOLV SOLUTION IS IMPORTANTSlide 2 Why is this Unit Important?

This class is your first taste of the system. No matter what you will be doing in MetaSolv Solution, it is important that you have a basic understanding of all of its components

This unit is important because once a company decides to purchase the MetaSolv Solution; the first item on the agenda is to load it with specific information geared uniquely to that companys performance.



1. INTRODUCTION TO THE METASOLV SOLUTIONOVERVIEWSlide 3 Introduction to the MetaSolv Solution

The first thing to consider when learning a new software is its basic components, that is, the screens, fields, navigation methods, structure, and so forth. This introduction is designed to teach you the basics.

LESSON 1 OBJECTIVESSlide 4 Lesson Objectives

Given access to the training data base and facilitator led assistance, you will be able to:

Describe the subsystems of the MetaSolv Solution.

Log on to the system.

Describe the various types of MetaSolv Solution windows and fields.

Utilize Help.

Utilize MetaSolv Solution QuickLinks.

Successfully completing the follow up activities will measure your success.



FORTY THOUSAND FOOT AN OVERVIEW OF THE METASOLV SOLUTION SUBSYSTEMSSlide 5 Forty Thousand Foot

Figure 1 Forty Thousand Foot

As you have learned so far, the telecom industry is an exciting and ever changing world. MetaSolv Solution is here today as a result of the wide range of doors that the industry has opened.



The MetaSolv Solution consists of a set of subsystems integrated by a common repository of business data and processes. Each subsystem supports a critical aspect of the telecom industry:

OSS Gateway Management

Customer Care

Network Design

Service Provisioning

Order Management

Trouble Management

Work Management

Data Management

Security

Each subsystem can be extended with add-on modules to tailor it to support unique products and services, such as resale or wholesale-based products that provide local or long distance services. The subsystems can also support network technologies, such as wireless radio or SONET.

This class will be a journey through these subsystems. You will wear many hats throughout the next few days. You will be an engineer, a customer service representative, a problem solver, an administrator, and perhaps, all of these rolled into one!

Before you log on, to MetaSolv Solution lets discuss the subsystems and each role that you will play.



OSS GATEWAY MANAGEMENT

Slide 6 OSS Gateway Management

The MetaSolv Solution is developed on an open architecture that recognizes the need to electronically exchange information with a wide array of systems, such as the managed network, other enterprise systems, and external trading or service partners and their operations support systems.

Figure 2 OSS Gateway Management

This Application Programming Interface (API) architecture enables companies to achieve their goals of flow-through provisioning and interconnection, which helps them take advantage of powerful new opportunities. The integration that the APIs provide forms a solid foundation for revenue assurance activities.



CUSTOMER CARE

Slide 7 Customer Care

One of the key architectural features of MetaSolvs approach is a high degree of integration of customer information.

Figure 3 Customer Care

This Integrated Telecom Information Architecture maintains key relationships between customers and the full scope of their involvement with the business.

This architecture supports the ability to view the customer from the many angles that are important to managing and growing the customer relationship.

In your training, you will access this subsystem to enter basic customer information, work a trouble ticket, and enter a variety of service requests.



NETWORK DESIGN

Slide 8 Network Design

MetaSolv Solution Network Design subsystem is powerful enough to handle large telecom networks and flexible enough to manage a mix of both old and new telecommunications technologies.

Figure 4 Network Design

This subsystem brings together the geographical, physical, electrical, and logical dimensions of the network into a single, cohesive view that is supported by a set of integrated equipment administration and network design modules.

When you access the Network Design subsystem, you will use it to view, install, delete, and move different types of equipment. You will also create some SONET networks and network routes as well.



SERVICE PROVISIONING

Slide 9 Service Provisioning

The integration of the Service Provisioning subsystem with the Order Management and Network Design subsystems provides an accurate view of what the customer ordered and what your network can support when deciding how to design or provision the service.

Figure 5 Service Provisioning

Because the Network Design subsystem supports network components from a variety of sources, the Service Provisioning subsystem enables you to build the end-to-end circuit design.

You will access this subsystem after you have processed the orders for service. Service Provisioning is the subsystem that is designed to give you a checklist of steps to complete when you design and activate the networks and circuits.



ORDER MANAGEMENT

Slide 10 Order Management

The MetaSolv Solution's Order Management subsystem enables you to manage the end-to-end service delivery process that can often involve more than one type of order or transaction across your organization, as well as with other service providers or network providers.

Figure 6 Order Management

At the core of the MetaSolv Solution Order Management subsystem is flexible service request architecture. This architecture captures the components of todays complex customer requirements and enables you to create and manage multiple types of orders.

Not only will you enter many different types of orders in the Order Management section of this training, but you will also learn about cataloging equipment specifications and designing some ordered circuits.



TROUBLE MANAGEMENT

Slide 11 Trouble Management

MetaSolv Solution Trouble Management subsystem is integrated with Order Management, Service Provisioning, and Network Design, which results in one, comprehensive, consistent view of who the customers are, what services you provide them, and how you provide those services.

When you get into this facet of the training, you will learn how to open, respond to, refer, and close trouble tickets.

Figure 7 Trouble Management



WORK MANAGEMENT

Slide 12 Work Management

The MetaSolv Solution Work Management subsystem brings all of the pieces together, enabling work to flow electronically across the organization, providing visibility to your processes and resource utilization.

Figure 8 Work Management

The Work Management subsystem provides the capability to maintain provisioning plans, which are groups of tasks, needed to manage the flow of work and information.

You can cause provisioning plans for common order types and customize them to add unique tasks to fulfill a specific request.

You will create and select the provisioning plans for the various orders that you enter in MetaSolv Solution.



DATA MANAGEMENT

Slide 13 Data Management

The Data Management component of the MetaSolv Solution maintains reference data about your business, its structure, and other information required to ensure quality and integrity throughout the business process.

Figure 9 Data Management

This central repository of essential reference, or infrastructure data, ensures quality and integrity throughout the business processes that MetaSolv Solution supports.

Later, you will actually go into Infrastructure and create a city, a LATA for that city, an organizational structure, and many more components required to activate a network.



SECURITY

Slide 14 Security

At the outset, all users have permission to access the entire product, except for the security windows that are protected.

Figure 10 Security

Security administration involves adding groups and users and restricting those groups and users from using various parts of the MetaSolv Solution product line.



AT THE END OF THIS COURSEIn a few moments, you will be on a journey through the MetaSolv Solution subsystems. This journey will lead you to your final goal, which will be a Final Bootcamp Obstacle Course, with you as the sole owner of a phone company.

In this final obstacle course you will complete a variety of exercises, from setting up ACTLs to provisioning some orders, from designing networks, to even taking care of some trouble along the way.

So, you have some work ahead of you. For starters, as a company executive, you have chosen to purchase MetaSolv Solution from MetaSolv Software, Inc.

On top of that, you need to learn how to use the MetaSolv Solution to successfully complete the exercises.



BOOTCAMP ROADMAP IN METASOLV SOLUTION SOFTWARESlide 15 Roadmap

Bootcamp is designed to give you a high-level training about the effects of MetaSolv Solution on the telecom world.

This class has been arranged to give you a working knowledge of telecom (as you learned in Unit 1) and how the MetaSolv Solution relates to the industry.

Suppose you are at home and you have decided to form a phone company.

Congratulations! You have made the decision to become a phone company! What is it going to take to be competitive and successful? Well, for starters, you need to purchase MetaSolv Solution.

FIRST STOPPREPARE THE METASOLV SOLUTION

Slide 16 Administrator Hat

Now that you have the software, what are you going to do with it?

INTRODUCTION TO THE METASOLV SOLUTION

Everyone in your company needs to know the basics. You will learn the basics of the software that is, the navigational techniques, various windows and fields, and how to use online help.



INFRASTRUCTURE SUBSYSTEM

Then put on your administrator hat because you need to load your company information, create some office locations, create some city statistics, and LATA information. As an administrator you will be entering all of this data in the Infrastructure subsystem.

SECURITY

Also, as an administrator, since you have so many departments doing different things, you definitely want to ensure that they work only in their perspective areas of the software. If the wrong person ends up manipulating the system in areas in which they dont belong, then this can really cost you some revenue because of the time it takes to recover the lost or changed data. You need some security control!

WORK MANAGEMENT

After you set up your company basics and secured the software the way you like, you are just about finished plugging in your basic information. But, one more thing needs to be done while you still have your administrator hat on. To get the show on the road you must to enter some employee lists, task assignments, and generally assign the responsibilities to the different departments! Work Management is the subsystem to help you do this.



SECOND STOPNETWORK DESIGN

Slide 17 Engineer Hat Network Design

Once you have set up your infrastructure, your security and your work management specifics in MetaSolv Solution, it is time to establish your network.

At this point, you can finally take some orders and design some circuits to ride your networks.

THIRD STOPCIRCUIT DESIGN

Slide 18 Engineer Hat Circuit Design

Orders are coming in! Fortunately your network is designed and your provisioning plans are ready. As a circuit engineer, you have received a task to design an ordered circuit.



FORTH STOPSERVICE REQUESTS

Slide 19 Customer Care Representative Hat

Your company must be able to take some orders, right? How else do you plan to stay afloat?

With that in mind, go ahead and remove the network engineers hat and put on the hat labeled Customer Service Representative.

You will be able to use MetaSolv Solution to enter a variety of service requests.



FIFTH STOPTROUBLE MANAGEMENT

Slide 20 Trouble Management Hats

Uh oh! Something has gone wrong!

After the network is up and running and the circuits are all defined and activated, anything can happen. Everything can be running smoothly and a lightning bolt hits a department store, and suddenly, you have some problems.

Someone calls your office to register the problem. You, as a customer care representative, need to enter a trouble ticket.

As an engineer, you can close a trouble ticket either by locating and fixing the problem or by forwarding it to someone else, if necessary.

Trouble Management accommodates both hats!

FINAL STOPWEAR EVERYONES HAT

Slide 21 Graduation

Since you have changed jobs and hats so often, you decide that you can do them all together!

In the final Bootcamp obstacle course, you will actually juggle the hats of everyone!

So, you have some work ahead of you. First, you must learn the basics of the system.



LOG ON TO THE METASOLV SOLUTIONNow that you have some idea of the different facets of MetaSolv Solution, it is time to log on. At this time, follow the steps that your instructor gives you to open up MetaSolv Solution database.

TOGETHERNAVIGATE THROUGHOUT THE SOFTWAREAt this time, you will learn the different navigational avenues that the system offers. While you are learning these techniques and elements, you will have an opportunity to view some of the subsystems that we just discussed.

Here is what you will learn:

Primary toolbar

Secondary toolbar

Procedures toolbar

Query windows, including

Query Window Dynamics

List windows

Drop-down menus

Fields (Required and Not Required)

Preferences

User

System

Global



QUICKLINKSMetaSolv Solution QuickLinks is a navigation system that incorporates an HTML page within the MetaSolv Solution application. It is not a true Web-based functionality, but merely a navigational tool on top of the application.

QuickLinks is included as part of the standard MetaSolv Solution application. MetaSolv or another professional service organization performs any desired customization of the HTML page. QuickLinks is optional functionality controlled by MetaSolv Solution preferences.

PREFERENCES

The global and user preferences reference the file location of the HTML page.

The global preference provides that all MetaSolv Solution users access the same HTML page.

The user preference provides a customized HTML page for every specific user.

DEFAULT FUNCTIONALITY

The QuickLinks page makes a variety of functions available:

Enter a New

Query For

Service Requests

Links

ENTER A NEW

QuickLinks supports creating new service requests, displaying recently edited service requests and tasks, plus links from other applications or websites.

You can create a new PSR, ASR, ISR, LSR, or Trouble Ticket from a button on the HTML page.

Without QuickLinks, you would select the Customer Care button, the Service Requests button, and the New button. Both of these navigations take you to the same screen.



QUERY FOR

Several of the common MetaSolv Solution query screens are also accessible from QuickLinks. You will be able to open the query for the following:

Service Requests

SONET/SDH rings

Circuits

DLC configurations

Trunk Groups

SERVICE REQUESTS

A list of service requests and tasks are displayed on the MetaSolv Solution QuickLinks page. The service request list provides a list of the last 10 orders (PSR, ASR, LSR, or ISR) that you modified.

You can open any of these service requests directly from the QuickLinks page.

The tasks list provides a list of tasks assigned to you, and you can open the work queue directly.

LINKS

You can use the Additional Links section to link to Web sites or to open documents that a user or organization requires. For example, you might want to link to Ordering and Billing Forum (OBF) Web sites or link to United States Telephone Association (USTA) or Alternative Local Telephone Service (ALTS) Web sites. You might also want quick access to some documentation or to a spreadsheet.



CUSTOMIZATION

Since QuickLinks is an HTML page within the MetaSolv Solution application, you can customize the screen to meet an individual users specific needs.

The default functionality described above is provided as a base. You can define a default QuickLinks page for all users or for a specific user.

Some common customizations include defining a customer care representative screen and a provisioning order representative screen. The customer care representative may work with PSRs and Trouble Tickets, but not ASRs, LSRs, or ISRs. Neither representatives screen would show the SONET/SDH, circuits, and so forth.

DEMOQUICKLINKS

Watch as your instructor navigates through the QuickLinks basics.



HELPSlide 22 Help

As with any other software that you might have used, online Help is always available for your assistance in MetaSolv Solution.

For each of the subsystems that you learn in class, you will receive a How Guide relating to that subsystem. These are available for MetaSolvs clients and partners and are extremely helpful job aids.

Your instructor will provide you with your How Guide for online Help.

The two facets of Help available are standard Help and Micro Help. At this time, your instructor will walk you through the different avenues for attaining help in MetaSolv Solution.



LESSON REVIEWSlide 23 ReviewIntroduction to MetaSolv Solution

In this lesson you learned the following:

How to log on to MetaSolv Solution

Various types of windows and fields available

How to utilize online Help

How to utilize QuickLinks



2. INFRASTRUCTUREOVERVIEWSlide 24 Infrastructure

Infrastructure covers all components of MetaSolv Solution. It houses all of a companys basic information. The first thing a company does when it purchases MetaSolv Solution is set up shop. They will plug in all data, such as Network Location, addresses, and any other backbone information. Their Infrastructure input is the glue that holds the companys information together.

OBJECTIVESSlide 25 Lesson Objectives

Given an instructor lecture, you will be able to explain the basics for setting up your company Infrastructure, as well as explain the concepts of the Infrastructure preferences.

Follow-up exercises will confirm your success.



ENTER YOUR INFORMATION HERECongratulations! You have decided to purchase MetaSolv Solution from MetaSolv Software, Inc.! So what are you going to do next?

At this time you, as an administrator, need to enter all of your information into the MetaSolv Solution so that you will be able to take some orders and provide some service to clients.

So, where are you going to enter this information? Infrastructure.Because of dependencies, you must enter the information into infrastructure in a certain order. That information comes from three main sources:

Preloaded data from Metasolv and Telcordia

The Local Exchange and Routing Guide, or LERG

Manually entered data

Figure 11 Origin of Infrastructure Data



THE LERG CDSlide 26 LERG

The Location Routing Gateway allows data to be imported from Telcordias Local Exchange Routing Guide (LERG) into the MetaSolv Solution Infrastructure subsystem.

Because the LERG contains such a large volume of data and is very time consuming to load, some MetaSolv Solution customers elect not to load the entire LERG CD.

Regardless of how much of the LERG a company decides to use, it is considered best business practice to utilize the LERG to acquire the necessary data for the MetaSolv Solutions Infrastructure.

When a company does load the LERG CD, the data that the LERG loads is pretty much all or nothing. They can, however, specify or narrow the amount of data that is loaded by selecting specific states to be loaded.



DATA CONTAINED IN THE LERGThe data contained in the LERG is shown in the table below. Notice that the LERG loads the cities and states first, which allows a company to narrow the amount of imported data. The table also denotes whether the data is required or optional in MetaSolv Solution.

TABLE NAME REQUIRED IN METASOLV SOLUTION?

GROUP WITHIN THE COMPANY THAT NEEDS TO BE INVOLVED IN DECISIONS AND INPUT

1.) States and Cities Required Ordering

2.) Operating Companies Required Ordering

3.) LATAs Required Ordering

4.) CO Exchange Areas Required Network

5.) NPA/NXX Codes Required Network

6.) Network Locations Required Network

7.) Tandems Optional Network

8.) ACTLs Required Network

9.) Serving Offices Optional Network

10.) End Offices Optional Network

11.) Switch Details Optional Network

NoteOrder of Entry is Important

Remember that the data is entered in a specific order,

which builds on itself and allows associations to be

made.



STATES AND CITIES

States must exist before you can create cities associated with the states. Cities are used throughout MetaSolv Solution to specify locations within entities, such as primary locations and secondary locations.

Defining City information involves specifying the following:

Valid name for each city

State in which the city is located

Valid Telcordia place code

Figure 12 States and Cities



OPERATING COMPANIES

Operating companies are providers of local telecommunication services (for example, ILECs CLECs, and wireless entities). Each operating company is identified by an operating company number (OCN), which is an industry-wide standard.

Figure 13 Operating Company



LATAS (LOCAL ACCESS & TRANSPORT AREA)

As mentioned earlier, a Local Access and Transport Area (LATA) denotes a geographic area established for the provision and administration of communications service. A LATA encompasses one or more designated exchanges, which are grouped to serve common social, economic, and other purposes.

Figure 14 LATAs



CENTRAL OFFICE (CO) EXCHANGE AREAS

A central office (CO) exchange area is an industry-wide name for a geographic area within which you provide telephone or Internet services for customers and end users. CO exchange area information is required in MetaSolv Solution, regardless of whether your company provides exchange or access information. (CO Exchange areas are prerequisite to several Infrastructure entities.)

CO exchange areas allow you to group network locations for purposes such as rate setting and calling plans. The CO exchange area usually has the same name as the locality it serves. It is served by one serving wire center (SWC), and can contain multiple NPA/NXXs.

Figure 15 CO Exchange



NPA/NXX CODES

NPA/NXX codes are set up by the North American Numbering Plan (NANP) and are codes that utilize ten digits to identify telephone numbers. The first six digits of the ten-digit number are referred to as the NPA NXX, which is a combination of the three-digit numbering plan area (NPA) code, (the area code), and the three-digit NXX code, (the CO prefix).

Figure 16 NPA/NXXs



NETWORK LOCATIONS

A network location represents the physical points or locations of a building, a point or an inventoried item that your company owns or uses. All network locations are identified by an eight-or-eleven byte Network Location code. For example, the switch where a circuit terminates, or the building that houses a relay rack that you own are both network locations.

Figure 17 Network locations



NETWORK LOCATION EXAMPLES

Below are some examples of network locations:

LOCATION DESCRIPTIONTandem Tandems are switching systems in the network that establish

trunk-to-trunk connections, thereby reducing the number of trunk routes in a concentrated arrangement for subtending ends offices.

ACTL Access Customer Terminal Location (ACTL) is the interLATA facility terminal location of the access customer providing service. The ACTL provides pertinent location information about the service being ordered (the A location).

Serving Office The serving office is a local switching system that connects lines and trunks. It is a facility where subscribers lines are joined to switching equipment for connecting other subscribers to each other, for both local and long distance services. Serving office can also refer to a network location, such as an end office or mobile telephone serving office that provides telephone exchange switching services. Serving offices play a significant role with respect to billing for access services.

End Office The term end office denotes a local telephone company switching system where telephone exchange service customer station loops are terminated for the purposes of interconnection to each other and to trucks. An end office is the central office switch to which a telephone subscriber is connected. The end office delivers dial tone to the subscribers terminal equipment for local POTS (Plain Old Telephone Service).



MANUAL LERG LOADIt is important to understand how to manually enter data from the LERG CD into MetaSolv Solution. Often, to fit its specific needs, a company needs to augment or add to the data that was imported from LERG.

ORDER OF ENTRYAs mentioned before, entering the data into infrastructure is pretty straightforward. Its important to enter the information in the correct order so that all data that is dependent on other data is entered in the proper sequence, which allows associations to be made.

The order of data entry is the same for manual data loading as it is for loading the LERG CD.

Here is a reminder of the order in which this data will be entered, as well as who is responsible for the data entry.

TABLE NAME REQUIRED IN THE METASOLV SOLUTION?

GROUP WITHIN THE COMPANY THAT NEEDS TO BE INVOLVED IN DECISIONS AND INPUT

1.) Cities Required Ordering

2.) Operating Companies Required Ordering

3.) LATAs Required Ordering

4.) CO Exchange Areas Required Network

5.) NPA/NXX Codes Required Network

6.) Network Locations Required Network

7.) Tandems Optional Network

8.) ACTLs Required Network

9.) Serving Offices Optional Network

10.) End Offices Optional Network

11.) Switch Details Optional Network



FYI FOR FINAL OBSTACLE COURSEOrdinarily, in the real world you would actually enter your Infrastructure information to start your business (but not in this lesson).

The final Bootcamp obstacle course will give you the opportunity to enter the data for your company. You will use the data entered for your projects, so you will get that information later.



LESSON REVIEWSlide 27 ReviewInfrastructure

In this lesson, you learned how to enter the basic specifications for setting up your company in Infrastructure.

You also learned the concepts of the Infrastructure preferences.



3. SECURITYOVERVIEWSlide 28 Security

Security is of utmost importance to any organization that stores delicate information. If the wrong person came in and opened up some part of the system and manipulated components within it, recovery time could be costly.

With that in mind, MetaSolv Solution has developed a security system, for the MetaSolv Solution software that allows administrators to secure any screen button, or field. Administrators can set the View Only features (Total Access or All Rights), depending on the type of security that is required.


Given a demonstration of security procedures and reference to those procedures in the How Guide, you will be able to:

Describe administrator capabilities.

Describe various password functions.

Describe available security permissions and restrictions.



WINDOWS USEDA security administrator uses the following windows specifically for security:

Assign Permission

Users and Groups

Security Reports

Secondary windows, such as Add User, are available after you select a main security window.

METASOLV SOLUTION INTERFACESlide 30 Power Builder Objects

Figure 18 Power Builder objects

MetaSolv Solution interface is comprised of objects, such as windows, controls (radio buttons or fields), and menus (including pop-up menus).

WINDOWS

Windows are the principle points of interaction between you and MetaSolv Solution subsystems. They display information, request information from you, and respond to your mouse clicks or keyboard actions.



WINDOW CONTROLS

If you need to protect window controls, such as certain fields or radio buttons on a window, MetaSolv Solution allows you to customize the permissions you set for these objects. Some window controls are pre-loaded, and you can easily scan others into the software to fit the needs of your business.

POPUP MENUS

MetaSolv Solution provides the ability to assign permissions to the pop-up menus and their controls. The Assign Permissions window lists all securable pop-up menus.

CHECKPOINTS

Checkpoints protect the security administration windows and selected functions in the system. The security administrator can establish a special password so that when a user tries to access a particular window or function, a checkpoint window appears. The user must enter the password to gain access to the protected window or function.

PERMISSIONSSecurity administration involves adding groups and users and restricting those groups and users from using various parts of the product line.

If you want to allow users to use some portions of the product line but not others, you can give them permissions that change their access from the default access.

DEFAULT PERMISSIONS

When MetaSolv Solution is installed, all users are members of the Default user group. Everyone in this group can access every part of MetaSolv Solution, except those parts protected by checkpoints, which require direct permission or a password. Default group permissions are set when MetaSolv Solution is installed.



ADMINISTRATOR CAPABILITIESSlide 31 Administrator Rights

A security administrator has the following capabilities:

Departmentalize MetaSolv Solution subsystems.

Hide objects.

Make objects read only.

Require passwords to access specific objects or functions.

Assign and display user permissions and group permissions.

Access security reports.



BASIC STEPS IN A SECURITY IMPLEMENTATIONSlide 32 Security Implementation Flowchart

Figure 19 Security Implementation Flowchart

The basic steps to follow in a first-time security implementation include:

1 Establish the Sec_Admin group.

2 Set up groups and users.

3 Set Global preferences.

4 Assign permissions.

You will learn more about these steps later.



REPORTSSecurity Reports allow you to view or print reports that detail what permissions are assigned to a user or group. One of the most important aspects of the report feature is the new ability to identify any users that are not assigned to the Default group. Running this report periodically helps you locate any users that slip through the cracks.

USERS AND GROUPSSlide 33 Users and Groups

At installation, only the security administrator has access to the Users and Groups window. The security administrator can assign access to groups or users.

Setting up groups in the database allows you to easily grant the same rights and permissions to users with similar responsibilities. If you have to make a change that affects every user in the group, then a single change to the group applies simultaneously to every user in the group.

For example, if you have 500 users in your Engineering group, you can imagine how much easier it is to make a single Engineering group change than to have to make 500 individual changes!

To save time when entering groups and users in the Users and Groups window, use the Continuous Add checkbox to add a number of groups or users.



PASSWORDSUsers are required to have passwords to log on to the MetaSolv Solution and to access windows protected by checkpoints. When new users are added, the password automatically defaults to the user ID. The system administrator can assign a permanent password or change the Security Preference so that users can change their own passwords when they log on for the first time.

PASSWORD REQUIREMENTS

Slide 34 Password Requirements

Passwords are a necessary part of securing the database. Users are required to have passwords to:

Log on to the MetaSolv Solution.

Access windows or functions protected by checkpoints.

Logon passwords like the user ID must be:

Four - eight characters long

Start with a letter

Include only letters and numbers.

Note Are passwords case sensitive?No! Currently, Oracle does not support case sensitivity.



PASSWORD EXPIRATION DATES

Slide 35 Expiration Dates

SERVER DATES

The log on and expiration dates validate against the server date instead of the date on your personal computer. Using the server date allows for more consistency and accuracy because fewer people have access to the server.

PASSWORD EXPIRATION

The password will expire on the date displayed in the Edit User window. The system default is ninety days from the setup date.

Note No preference currently exists to change the default.

NO EXPIRATION DATE

If you leave the Password Expires On field blank. You can make this field blank the password will never expire by highlighting the date and pressing the key.

Warning

Password Expires On FieldFor security reasons, we do not recommend that you leave the Password Expires On field blank.



PASSWORD EXPIRATION WARNINGS

Slide 36 Changing Passwords

The MetaSolv Solution warns users that their password is about to expire six days prior to expiration. When the user receives the warning, they may change their password in the User Information folder in Preferences before it expires.

If a user does not change their password or access the MetaSolv Solution during the time that the warning appears, then the password expires. Users are then forced to change their password the next time they login to the MetaSolv Solution.

RESTRICTING ACCESSSlide 37 Restricting Access

If you want to allow users to use some portions of the product line, but not others, give them permissions that change their access from the default access. The best way to handle this task is to divide users into groups based on job functionality.

Lets say you want a manager to have the ability to make changes through a certain window, but you do not want to give that permission to a temporary office worker. You create a group named "Clerical" and put temporary office workers into that group. But first, you need to restrict access for that group.

Security Administration provides an easy way to view the permissions associated with an individual user.



PERMISSION TYPES

Slide 38 Permission Types

The following permissions are available for objects in the product line. The object type determines the permission that you assign to the object. You can assign a checkpoint to some windows and functions, which requires a user to enter a password for access to those windows and functions.

PERMISSION DEFINESDisabled What you can see but you cannot use because the

object is grayed out.

Full Access That the selected group or user is specifically permitted to use the selected object.

Invisible When you cannot see an object on a window.

No Access When you cannot see or use a window or checkpoint.

Not Set When you can use a window or menu by default. (The default for checkpoints is No Access.)

Password When you must enter a password to access the checkpoint.

Read Only When you can see and access the object but cannot make changes to the selected object.

NoteRead-Only WindowsIf a user enters data on a read-only window, no notice appears to notify the user that the data has not been accepted. Therefore, use the Read Only permission sparingly.

These permissions are available for every object in the product line. For windows or functions that require checkpoint access, you must assign a password so that authorized users can gain full access.



DEFAULT PERMISSIONS

With default access, you can access everything but Security. The following table shows the default permissions:

TOPIC DESCRIPTIONInitial Permissions Not Set is the access default value for every

object in MetaSolv Solution. However, users do not have default access to functions that have checkpoints, such as Work Management changes or security administration.

Groups Once associated with a group, the user inherits the groups permissions. In cases of conflict between a users permissions and a groups permissions, the least restrictive permissions apply unless the user is directly granted permission such as Enabled or No Access. Directly granted user permissions override other permissions, which allows the security administrator to override a permission obtained through group membership.

Checkpoints The default permission for a checkpoint is No Access, which means that you must assign the user permission to pass a checkpoint and access the protected object or function.

Not Set versus Enabled

An object that does not have an assigned permission is Not Set. Therefore, you get the default permission for the object or checkpoint, which can include a restriction.

The Enabled permission gives the user explicit permission to access an object. When a user has Enabled permission, more restrictive group permission cannot override it.



USER IMPACT

The access that a user has to the software depends on two variables:

Are specific user permissions assigned?

Does the user belong to one or more groups?

Slide 39 Permissions Flowchart

Figure 20 Permissions Flowchart

Slide 40 Rules

Rules governing permissions include:

Users are given the LEAST RESTRICTIVE access available.

Specific user permissions override group permissions.

Not Set allows access to windows as a default, but it is ignored as a determining factor when you set group permissions.



PERMISSIONS GROUP BOX

A user or group can have different levels of permissions, depending on group memberships and individual permissions. Use the radio buttons on the Assign Permissions window to specify permission types.

If you select an individual user or group from the User/Group drop-down, you can use these radio buttons to display the information. We will look at user permissions after we have set them up.

RADIO BUTTON FUNCTIONS

Slide 41 Radio Button Functions

Radio buttons have the following functions:

RADIO BUTTON FUNCTIONEffective Displays the permissions in effect for a selected

object. The object name is displayed in the left pane, and you can determine the object name of any window by using the hot-key combination. MetaSolv Solution grants the individual user either the least restrictive permission level or the permission directly assigned to the user, whether those permissions belong to a group that the user is a member of or to the individual.

User Displays the permissions directly assigned to the user.

All Displays all user permissions and all group memberships. MetaSolv Solution sorts the permissions in order of highest priority, from those directly assigned to the user to the least restrictive permissions obtained from the group.



RESTRICT WINDOW ACCESSYou can secure a window in several ways, from making the window invisible to making it Read-Only. You can even secure controls on the window so that a user can perform some functions but not others.

To assign permissions to window controls, you need to assign permissions to objects on windows (fields, radio buttons, and so on).

On the Assign Permissions window, all windows are listed, but not all of the controls for the windows are listed. You must scan in controls that are not listed. When you scan in window controls, these controls are added to the database.

CHECKPOINTS

Slide 42 Checkpoints

For a new installation, the Security Administration group has "Access" permissions for all security checkpoints. After installation, the security administrator decides which functions should require password protection.

Currently, the MetaSolv Solution has six areas that use checkpoints:

Equipment Install Module

Order Management

Security

System Settings

Trouble Management

Work Management



RESTRICT POP-UPS

Slide 43 Popup Menus

Figure 21 Popup Menus

Pop-up menus are used throughout the product family. You can access additional functionality by right-clicking any item and selecting an item from the pop-up menu. When you cannot find what you are looking for, right-click and see what functionality is available from the pop-up menu, which will have different menu items, depending on the item that you selected.

Pop-up menus include add, delete, move, and assign functions. Through the Assign Permissions window, you can determine the pop-up menu functions for specific groups or users.



LESSON REVIEWSlide 44 ReviewSecurity

In this lesson, you were able to do the following:

Describe administrator capabilities.

Describe the various passwords functions.

Describe the permissions and restrictions available.



4. WORK MANAGEMENTOVERVIEWSlide 45 Work Management

You can use the Work Management subsystem to complete service requests that you receive from your customers. The business process usually consists of the following steps:

Receive and enter an order.

Generate tasks.

Manage the tasks.

Complete the order.

You should still have your Administrator hat on because you are about to set up shop to prepare for this business process.




Given facilitator assistance, access to the Work Management subsystem, and a Work Management How Guide, you will be able to:

Identify key elements of The Work Management subsystem.

Describe the function of adding new employees.

Describe the function of adding parent and child work queues.

Describe how the organizational calendar is associated with work queues.

Describe the function of the different task types and check list items.

Set up the Auto Plan Selection feature.

Slide 47 Lesson Objectives (contd)

Select a provisioning plan.

Select a work queue for each task.

Modify tasks, due dates, and work queues.

Identify the key fields and values on the Work Queue Manager.

Accept, transfer, and complete tasks and all checklist items.

Enter notes, why missed codes and jeopardy codes in tasks.

Throughout this lesson, practices will support what you have learned.



WORK MANAGEMENTSlide 48 Work Management

Figure 22 Work Management

The work management function ensures that work is not assigned on holidays and not assigned to personnel on vacation. Work Management holds the work plans and the departments that customer representatives can select to fulfill an order.

With Work Managements Work Queue Manager, engineers, field services, and other personnel can complete tasks for orders to track their workloads and actually perform work.



WORK MANAGEMENT PUZZLESlide 49 Work Management Puzzle

Figure 23 Work Management Puzzle

Lets look at the pieces of the puzzle that make up the Work Management process flow: EmployeesNot all employees own a work queue. Only those employees that complete tasks for orders own work queues.

Work QueueWork Queues contain the tasks that are generated during the order entry process. The work group queue usually receives the tasks first and then distributes them to the individual work queues that are associated with it. As an example, a task is sent to the Engineering work group and then assigned to an engineer.

TasksTasks are the steps you take to process an order. They are the building blocks that you use to create provisioning plans. They are, in fact, to-do items.

Checklist ItemsChecklist items are associated with individual tasks. An example of a checklist item might be to do a credit check on a customer when a service request is submitted.

Provisioning PlansProvisioning plans allow you to define in the MetaSolv Solution how you complete service requests in your organization. They are a collection of to-do items or tasks.

After you set up all of these puzzle pieces, you are ready to receive service requests. A provisioning plan is generated for a request, but the tasks on the plan can have multiple circuits. The tasks for that request



are then assigned to work queues. These are the main pieces of the Work Management subsystem.



WORK QUEUE SET-UP PROCESS FLOWSlide 50 Work Queue Setup Process Flow

To set up employee work queues so that they can receive tasks, use the following process:

1 Add the employee to the Security database, if not already entered.

2 Add the employee to the Work Management database.

3 Create parent and child work queues.

EMPLOYEESSlide 51 Employees

Employees are the first piece of the Work Management puzzle. Not all employees own a work queue. Only those employees that complete tasks own work queues. To own a work queue, you must be entered as an employee in the Work Management subsystem. Only employees who will be performing tasks to fill a service request need a work queue.

Slide 52 Employees Rules

Before employees can log on to the MetaSolv Solution and use the Work Management functions, the following rules apply:

An organization must be set up in Infrastructure.

The employee must be entered in MetaSolvs Security database with a valid logon ID.

The employee must be entered in the Work Management subsystem.

Remember that you can set up employees with a MetaSolv Solution log on ID and not set them up as employees in the Work Management subsystem. If you do so, however, they will not be able to access any tasks in the MetaSolv Solution.



When you add an employee to Work Management, the new ID should be the same as the MetaSolv Solution log on ID. When an employee logs on to the MetaSolv Solution, the log on ID determines which work queues the employee can access. You can enter employees who do not have MetaSolv Solution log on IDs in Work Management, but they wont be able to log on to the MetaSolv Solution without a MetaSolv Solution log on ID.

When you create an Employee ID, the system validates that the MetaSolv Solution log on ID has direct access to the Employee IDs work queues.

Note PasswordsSecurity passwords must begin with a letter and be between four and eight characters long.

Some companies create a generic logon for all of their contractors. If the security administrator locks down all systems for this logon, except the Work Queue Manager, then contractors can view only their work queues.



TOGETHERCREATE A NEW EMPLOYEEYour supervisor at NewTel has asked you to add a new employee to the Work Management database. His name is Ronnie Wood (RWOODXX), and he has already been set up in Security.

WORK QUEUESSlide 53 Work Queues

In work queues you store and organize tasks generated during the order entry process so that individuals or groups of individuals can access and work on their assigned tasks.

The parent, or work group, work queue receives the tasks first and then distributes them to the child work queues that are associated with the parent. Therefore, a task would go to the Engineering work queue (the parent queue) and then will be sent to an individual engineer (to the child queue of the engineering parent queue).

Slide 54 Parent and Child Relationship

Parent Work Queue AParent Work Queue A

(child)TONI(owner)

(child)GERRI(owner)

(child)JAMES

(owner)

(child)TOM

(owner)

(child)MARIA(owner)

(child)

SUSIE(owner)

(child)JOHN(owner)

Lara (owner)Lara (owner)

(child)BILL(owner)

(child)JOHN(owner)

(child)

SUSIE(owner)

Parent Work Queue BMike (owner)


(child)LARA(owner) (child)

MIKE(owner)

Parent Work Queue AParent Work Queue A

(child)TONI(owner)

(child)GERRI(owner)

(child)JAMES

(owner)

(child)TOM

(owner)

(child)MARIA(owner)

(child)

SUSIE(owner)

(child)JOHN(owner)

Lara (owner)Lara (owner)

(child)BILL(owner)

(child)JOHN(owner)

(child)

SUSIE(owner)



(child)LARA(owner) (child)

MIKE(owner)

Figure 24 Parent and child relationship

You must set up the parent work queue first. You typically set up the child, or individual, work queue for one person. You typically set up the parent, or group, work queue for a group or a department or for an individual who is responsible for managing task assignments.



TOGETHERVIEW PARENT WORK QUEUEThe CUSTCARE work queue is a departmental or parent work queue for the Customer Service Department. Your supervisor wants you to access this work queue and ensure that all tasks placed in the parent work queue are assigned automatically.

TOGETHERVIEW CHILD WORK QUEUEThe USERXXEN work queue is a child work queue of the ENGINEER parent queue. Access and view the USERXXEN queue online.



TASK TYPES AND CHECKLIST ITEMSNext, you will learn about the different types of tasks, that you can send to work queues.

Tasks are the steps that you take to process an order, such as confirming the order, designing the circuit, or preparing billing. The MetaSolv Solution includes detailed reporting that identifies which users completed tasks on time and which users completed tasks late.

TASK TYPESSlide 55 Tasks

The Work Management Task Types section allows you to create and maintain task types associated with provisioning plans. Task types are pre-loaded when the MetaSolv Solution is installed, and they trigger specific pre-programmed processes within the system.



SMART TASKS

Slide 56 SMART Tasks

The highlighted tasks are SMART tasks. A SMART task drives information in the system. It has a double-click function that takes you to wherever you want to go in the MetaSolv Solution to accomplish a task.

When you double-click a SMART task in the Work Management subsystem, a window specific to that task opens. For example, when you double-click the DLRD task, the Design Layout Record window opens.

When you double-click any task that is not a SMART task, then the system defaults to the Service Request Query window.



TASK PROPERTIESSlide 57 Task Properties

You can edit the existing task types or create new task types that are specific to your company. For each task entered you can:

Create the number of grace days, hours, and minutes, which allows users additional time after the due date before a why missed code is required.

Create the potentially late notification days, hours, and minutes, which gives users advance notice that a task has the potential for being late.

Determine if the task is critical.

Create a double-click action if the task is not already a SMART task. For example, if you select DLRD as the double-click action for a new task called PRECLR (pre-circuit layout record), then when you double-click the PRECLR task, it also opens the Design Layout Record window. You can make any new task work like an existing SMART task.

Warning

SMART Tasks with Background Validations

In your task handout, notice that a few tasks have an asterisk beside them. These SMART tasks have some background validations and should not be renamed or used for another task.



TASK DESCRIPTIONSItems that appear below with a gray background are smart tasks.

*Tasks proceeded by asterisk run background validations and should not be renamed.


TASK TYPE TASK DESCRIPTIONAPP The Application Date task identifies the date

when the access customer gives the ASR to the access provider. This task populates the Firm Order Confirmation.

APPT Double-clicking the Appointment task opens the Appointment Selection window.

BILLING The Billing task acts as an interface between MetaSolv Solution and billing systems.

*CAD Double-clicking the CABS Acknowledgment Date task opens the Carrier Access Billing System (CABS) window. You cannot complete this task until you enter billing information and complete the CID task. You use this task only with the interface to the CABS billing system.

CDLRD The Confirming Design Layout Report Date task populates the CDLRD field on the Firm Order Confirmation.

*CID Double-clicking the CABS Issue Date task opens the CABS window. With this task, you can use coordinates to determine the mileage between endpoints in a circuit. It also allows you to associate Universal Service Order codes with locations on a service request. (You must complete this task before you can complete the CAD task.)

TASK TYPE TASK DESCRIPTIONCKTID Double-clicking the Circuit ID task opens the

Service Request Circuits window. You use this task to add, delete, or update circuits for PSRs only.

CONF Double-clicking the Confirmation task opens the Firm Order Confirmation window and allows you to issue a confirmation to the access customer.

CORD Double-clicking the Parent Order Coordination task opens the Service Request Hierarchy window in the Worksheet module. This task allows you to view the status of associated child tasks and to associate parent and child orders with tasks. All parent provisioning plans should include this task.

*DD You should include the Due Date task on all plans. If, however, there is a parent/child plan, then the DD should be on the child plan only. The Due Date task involves building the circuits on an order and changing the status of ordered items to In Service, Suspended, or Disconnected. Completion of this task implies that the work on a circuit is complete, including attaching telephone numbers and circuit IDs to the order.

*DLRD Double-clicking the Design Layout Report Date task opens the Service Request Circuits window, which lists all circuits on a service request. Double-clicking a circuit on this window allows you to design circuits and issue the Design Layout Record.

This task is recommended for all plans that have a provisioned circuit. You can complete the DLRD only if all of the circuits are in DLR-issued status.

DSCN Double-clicking the Directory Service Completion Notice task opens the DSCN form, which allows you to track requests for directory services. You can complete this task only after the service is complete.

TASK TYPE TASK DESCRIPTIONEQ INST Double-clicking the EQ INST task opens the

Equipment Install window, from which you can install equipment from an order at an end user location.

*EUAD Double-clicking the End User Acknowledge Date task opens the End User Bill Prep window, which acknowledges that End User billing is in effect. This task is only for customer interfaces with EU billing systems. You must complete the EUID task before the EUAD.

*EUID Double-clicking the End User Billing Issue Date task opens the End User Bill Prep window, which allows you to enter appropriate change codes and complete preparations for EU billing. You must complete this task before you complete the EUAD.

FCDLRD The Facility Confirming DLR Date task populates the FCDLRD field on the Firm Order Confirmation form (FOC).

FDD The Facility Due Date task populates the FDD field on the FOC form.

FDLRD The Facility Design Layout Report Date task populates the FDLRD field on the FOC form.

FNI Double-clicking the Fiber Network Identification task opens the FNI window so that you can enter an FNI to identify a ring circuit service request.

Note: This task is not pre-loaded, and you must create it manually.

FPTD The Facility Plant Test Date task populates the FPTD field on the FOC form.

FRID The Facility Record Issue Date task indicates the date that the facility record was issued.



TASK TYPE TASK DESCRIPTIONFWOT The Facility Wired and Office Tested Date task

indicates the date when the wiring and testing must be completed.

ILAM Double-clicking the Issue Loop Assignment and Makeup task opens the Loop Assignment and Makeup Circuit Listing window, which allows you to issue and print the LAM form.

LAM Double-clicking the Loop Assignment and Makeup task opens the Service Request Circuits window and allows you to enter local loop and cable pair information in the Plant Administration module.

NEWTASK Double-clicking the New Task opens the Task Generation window, which allows you to select specific child plans to associate with parent plans. If you enable the NEWTASK preference, then you must associate a child plan before you can complete this task. (If this preference is not enabled, then a warning message appears.)

ORDHEIR Double-clicking the Order Hierarchy task allows you to view associated child orders and to associate a child order with a parent order.

PSR/LSR Double-click the PSR/LSR task to perform PSR- to-LSR/DSR mapping. The Generate Local Service Requests and Directory Service Requests window opens. (You must first enable the Perform PSR/LSR Mapping Outside the PSR Order preference.)

PTD The Plant Test Date task populates the PTD field on the FOC form.

RCONF Double-clicking the Response Confirmation Notice task opens the Circuit Reference window for the appropriate order type.

RID Double-clicking the Record Issue Date task opens the Service Request Circuits window, which allows you to access the circuit design process in the Engineering subsystem and to print the Circuit Layout Report.


RUNEXE TASKSlide 58 RUNEXE

The RUNEXE task is not one of the pre-loaded tasks, so you have to create it. (MetaSolv doesnt pre-load this task because not everyone wants to run the same application.)


TASK TYPE TASK DESCRIPTIONRUNEXE Double-clicking the Run Executable task opens

a program file. You must set up the program file (executable) prior to attempting to double-click the RUNEXE task.

SID The Scheduled Issue Date task indicates the scheduled date for issuing a firm service order.

SUSPEND Double-clicking the SUSPEND task opens the Restore/Disconnect Products window so that you can disconnect or restore service for a customer whose service had been suspended.

TRANS Double-clicking the TRANS task opens the Translation window. You can enter translation information, view or delete circuit routing information, enter or change contact information, print trunk circuit orders, view end-office detail forms, view trunk group information, and view the trunk circuit order report.

You must associate this task with a service request that uses the Translation Questionnaire for switched access service requests. This task also opens the Product Service Request window for PSR orders so that you can view the Tech Translation sheet for services and products.

VPN DSGN Double-click the VPN DSGN task to access the Network Systems drawing canvas to build a graphical representation of the Virtual Private Network (VPN).

WORKS Double-clicking the WORKS task opens the Worksheet, which allows you to see a graphical representation of a network and to enter additional information about the service request.

WOT The Wired and Office Tested Date task indicates the scheduled date for internal wiring and testing of the service.


In the Executable Path field, you type the path name to the program that you want to run. Then you can use the RUNEXE ta

MetaSolv Introduction

Documents

Transcript of MetaSolv Introduction