Metasolv Introduction PDF
Metasolv Introduction PDF
SLIDE 14 SECURITY 26
At the End of this Course.....................................................................27
Bootcamp Roadmap in MetaSolv Solution Software..........................28
SLIDE 15 ROADMAP 28
First Stop—Prepare the MetaSolv Solution..................................................28
SLIDE 21 GRADUATION 32
Log On to the MetaSolv Solution.........................................................33
Together—Navigate Throughout the Software...................................33
QuickLinks...........................................................................................34
Preferences..................................................................................................34
Default Functionality.....................................................................................34
Customization...............................................................................................36
DEMO—QuickLinks......................................................................................36
Help......................................................................................................37
SLIDE 22 HELP 37
Lesson Review....................................................................................38
SLIDE 24 INFRASTRUCTURE 39
Objectives............................................................................................39
SLIDE 26 LERG 41
Data Contained In The LERG.............................................................42
States and Cities..........................................................................................43
Operating Companies...................................................................................44
NPA/NXX Codes..........................................................................................47
Network Locations........................................................................................48
SLIDE 27 REVIEW—INFRASTRUCTURE 52
3. Security.............................................................................................53
Overview..............................................................................................53
SLIDE 28 SECURITY 53
Objectives............................................................................................53
Window Controls..........................................................................................55
Popup Menus...............................................................................................55
Checkpoints..................................................................................................55
Permissions.........................................................................................55
Default Permissions......................................................................................55
Administrator Capabilities....................................................................56
User Impact..................................................................................................64
SLIDE 42 CHECKPOINTS 66
Restrict Pop-ups...........................................................................................67
SLIDE 44 REVIEW—SECURITY 68
4. Work Management...........................................................................69
Overview..............................................................................................69
Employees...........................................................................................74
SLIDE 51 EMPLOYEES 74
SLIDE 52 EMPLOYEES RULES 74
Together—Create a New Employee...................................................76
Work Queues.......................................................................................76
SLIDE 55 TASKS 78
Smart Tasks.................................................................................................79
SLIDE 58 RUNEXE 87
Checklist Items....................................................................................89
SLIDE 59 CHECKLISTS 89
Together—Create Checklist Items......................................................89
Create Provisioning Plans...................................................................90
Pert Chart............................................................................................96
NPA/NXX Task Assignment................................................................96
Gateway Assignment...........................................................................96
Automatic Plan Selection.....................................................................97
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
Modifying Tasks.................................................................................104
Managing Tasks................................................................................109
UNIT OVERVIEW
Slide 1 Preparing the MetaSolv Solution
Changing times require new strategies. It’s important to stay flexible.
At MetaSolv, we recognize that today’s converging telecommunications
market is challenged with managing a growing number of complex
business relationships while supporting a widening variety of new
technologies and services. MetaSolv’s 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.
LESSON 1 OBJECTIVES
Slide 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.
CUSTOMER CARE
NETWORK DESIGN
SERVICE PROVISIONING
ORDER MANAGEMENT
TROUBLE MANAGEMENT
WORK MANAGEMENT
DATA MANAGEMENT
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.
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 don’t 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.
At this point, you can finally take some orders and design some circuits
to ride your networks.
With that in mind, go ahead and remove the network engineer’s 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.
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….
QUICKLINKS
MetaSolv 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
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
DEMO—QUICKLINKS
HELP
Slide 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
MetaSolv’s 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 REVIEW
Slide 23 Review—Introduction 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. INFRASTRUCTURE
OVERVIEW
Slide 24 Infrastructure
Infrastructure covers all components of MetaSolv Solution. It houses all
of a company’s 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
company’s information together.
OBJECTIVES
Slide 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.
•
Figure 11 Origin of Infrastructure Data
THE LERG CD
Slide 26 LERG
The Location Routing Gateway allows data to be imported from
Telcordia’s 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 Solution’s 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.
SOLUTION? TO BE INVOLVED IN
Note
Order of Entry is Important
made.
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
OPERATING COMPANIES
Figure 14 LATAs
Figure 15 CO Exchange
NPA/NXX CODES
Figure 16 NPA/NXX’s
NETWORK LOCATIONS
LOCATION DESCRIPTION
Tandem 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 subscriber’s terminal equipment for local
POTS (Plain Old Telephone Service).
ORDER OF ENTRY
As mentioned before, entering the data into infrastructure is pretty
straightforward. It’s 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.
INPUT
LESSON REVIEW
Slide 27 Review—Infrastructure
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. SECURITY
OVERVIEW
Slide 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.
OBJECTIVES
Slide 29 Lesson Objectives
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 USED
A 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.
WINDOWS
WINDOW CONTROLS
POPUP MENUS
CHECKPOINTS
PERMISSIONS
Security 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
ADMINISTRATOR CAPABILITIES
Slide 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.
REPORTS
Security 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.”
PASSWORDS
Users 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
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.
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 <Delete> key.
Warning
Password Expires On Field
For security reasons, we do not recommend that you
leave the Password Expires On field blank.
RESTRICTING ACCESS
Slide 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.
Let’s 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
PERMISSION DEFINES
Disabled 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.
Note
Read-Only Windows
If 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 DESCRIPTION
Initial 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 group’s permissions. In cases of conflict
between a user’s permissions and a group’s
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 An object that does not have an assigned
Enabled 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?
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
LESSON REVIEW
Slide 44 Review—Security
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 MANAGEMENT
OVERVIEW
Slide 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.
OBJECTIVES
Slide 46 Lesson Objectives
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 (cont’d)
• 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 MANAGEMENT
Slide 48 Work Management
are then assigned to work queues. These are the main pieces of the Work
Management subsystem.
EMPLOYEES
Slide 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 MetaSolv’s 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.
Note Passwords
Security 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.
WORK QUEUES
Slide 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
(child)
(child)
TONI
(owner)
JOHN (child)
(owner)
(child)
JOHN
(owner)
TOM
(child) (owner) (child)
(child)
SUSIE SUSIE
(owner) JAMES (owner)
(owner) (child)
(child) BILL
(owner)
LARA (child)
(owner) (child)
MARIA MIKE
(owner) (owner)
(child)
GERRI
(owner)
TASK TYPES
Slide 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
TASK PROPERTIES
Slide 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
TASK DESCRIPTIONS
Items that appear below with a gray background are smart tasks.
*Tasks proceeded by asterisk run background validations and should not be renamed.
In the Executable Path field, you type the path name to the program that
you want to run. Then you can use the RUNEXE task, for example, to
open Word and send a letter to your customer.
Note
RUNEXE Double-click
You can create a SMART task with the double-click
action of RUNEXE (and you can rename it, if you like).
On the Task Type – New window, the Browse button
next to the Executable Path field allows you to select
one of several executable programs.
CHECKLIST ITEMS
Slide 59 Checklists
Checklist items remind you to complete certain aspects of a task.
Each checklist item is user-defined, based on your business
practice, and is associated with a task on a provisioning plan.
When you add a checklist item to a task, it shows up only for new
tasks generated. It does not apply to tasks that are already in work
queues.
Let’s say that for the APP task, you want to define two subtasks:
one to send a welcome letter when you complete the APP task and
the other to check the customer’s credit to make sure they can pay
you. You can set up both of these subtasks as checklist items.
Again, a checklist item is a reminder for the person completing the
task. In this example, you must complete both checklist items
before you can complete the APP task.
The MetaSolv Solution doesn’t hold you to completing your checklist
items in any specific order, except that you must complete them
before you complete the task. Your business process dictates the
recommended order of completion.
TASK PROPERTIES
Slide 61 Tasks Properties in Plan
You must consider two additional properties when you add tasks
to a provisioning plan:
• A work queue is the group
of individuals or the department responsible for completing the
tasks. The group might be customer service representatives,
engineers, or field services.
• The interval is the length
of time (in 15-minute increments) that you can complete a task
and is on time.
OTHER OPTIONS
TOPIC TIME
Start of Business 8:00 a.m.
Close of Business 5:00 p.m.
Lunch 12:00 – 1:00 p.m.
On the Task Assignment tab, you can perform the following functions:
• Assign a default work queue for
each task.
• Associate tasks with the
provisioning plan.
• Make tasks auto completeable by
checking the Auto Comp checkbox.
• Specify the interval, or number
of workdays, required to complete each task.
In most cases, all tasks are forward dated, except the Due Date task,
which is usually backdated. Sometimes, you backdate other tasks
when an order is not due for a long time.
For example, a customer orders a T1 line in January but doesn’t want
it turned on until May 1st. If a standard order takes six weeks, the
installation of the T1 would take place way ahead of schedule.
Therefore, you would probably complete the application and credit
check and then backdate the remaining tasks from the Due Date. After
a gap of no work from January to March, the work would begin in
March and be completed by May 1.
You can also forward date the Due Date. For example, if you make a
sale for a product that takes two weeks to produce and the due date is
in one week, all the tasks would have earlier due dates that you most
likely cannot meet. In a realistic work schedule, the Due Date would
be forward dated and would fall in line with the task intervals.
PERT CHART
The PERT chart is a graphical representation of the tasks listed on the
Task Dependencies tab.
GATEWAY ASSIGNMENT
A gateway event is the process of linking a third party vendor to
the MetaSolv Solution. You use the Gateway Assignment tab to
add a gateway event to a task in a provisioning plan.
GENERATING TASKS
Before generating tasks, an appropriate provisioning plan must exist
in the database.
You’ve already set up a plan through the MetaSolv Solution Work
Management subsystem. You have identified the following:
• Base set of tasks
• Workdays needed to complete
each task
• Dependencies between tasks
• Default assignments for each task
Now, you are ready to generate tasks for the order.
The Plan Selection tab on the Tasks window allows you to select
a provisioning plan, plus NPA NXX scheduling information (if
the preference is set up). The MetaSolv Solution uses this
information to generate work queue assignments.
WORK QUEUES
You can select work queues automatically or manually (if the Allow
Manual Queue Scheduling at Task Generation preference is turned on).
For both methods, the type of work queue and employee availability
affect, which work queues, you can select.
Note
Unidentified Work Queues
Question marks (????????) indicate that the
MetaSolv Solution inserted or added a task after
executing rules and behaviors. (Only tasks that come
from a provisioning plan have associated work
queues.) You must select work queues for these
unidentified work queues manually.
When tasks go to work queues, they adjust to the local time zone
for the queue owner automatically, based on the Windows
settings. If the Database Server Time Zone preference is set,
however, then whenever the local time zone differs from the
database server time zone, the MetaSolv Solution displays a
message at logon that allows you to select the appropriate time
zone. (You can verify the setting of the database server time zone
by checking Preferences>System Information>Database Server
Time Zone.)
The Task Circuits tab allows you to view all circuits on the order
after you click OK or Apply to send tasks to work queues. You
can also add circuit notes and add Jeopardy status on this tab.
MODIFYING TASKS
Slide 67 Modifying Tasks
You start task generation with a provisioning plan, which provides
consistent provisioning across orders. If your tasks don’t meet the
needs of the current order, then you can customize them.
If you ever have to modify some tasks, then you can do any of the
following:
• Change task due dates. (You
must have a security clearance to change the dates.)
• Add and delete tasks from the
task list.
• Override default work queues.
To change the due date, go to either the Task Gantt tab or the Task
List tab. Then select the task and type in a new due date.
On the Plan Selection window, if the Automatically Adjust Dates
of Followers Tasks checkbox is checked, then if you change the
date of one task, the dates of the follower tasks adjust automatically.
You cannot move the APP task to 9/8 because the due date is fixed at
9/9 and cannot be changed by changing the due date of the APP task.
You can, however, change the DD task to be due on 10/10/99. Then
the DLRD and APP tasks would be adjusted automatically to be due
10/9/99 and 10/8/99 respectively.
In addition to changing task due dates, you can delete, not require,
insert, or add tasks. Earlier, you learned about the difference between
inserting and adding a child task in a provisioning plan. You can also
modify a task from the Task Gantt window or from the Task List
window. After you select a task on either of these windows, right-
click it to access the pop-up menu, which provides several options for
modifying the task.
Specifically, you can make the following changes to a task:
• Insert a sibling task.
You can insert any task that has been set up through Work
Management (except the DD task). You can also set the
workdays for an inserted sibling task.
• Insert a child task.
• Add a child task.
• Add a jeopardy status.
• Make a task not required.
• Delete a task.
WORK QUEUE
You can click the “Personal”radio
button to see work queues that YOU
own, or you can click the “Work Group”
radio button to see all other work
queues in your work group.
JEOPARDY STATUS
The jeopardy icon appears if a task
has a J eopardy Code.
TYPE OF ORDER
Identifies if the order is an ASR,
*
PSR, or LSR.
Bitmap profiles have icons: White
book=ASR, Green book=ISR, box=
PSR, and house=LSR.
ACT
Identifies the activity Indicator for
the order. “N”=NewInstallation. To
interpret the different letters, right- CCNA
click, select Service Request Detail. Shows the Customer Carrier
The activity Indicator is in lower half Name Abbreviation.
of window. To close the window and POTENTIALLY LATE INDICATOR :
return to Work Queue Manager, RED: Identifies that the due date has
click the close button. passed.
YELLOW: Identifies that the task is in
SUP: Identifies the supplement jeopardy of beinglate.
number, if an order has been
CircuitID: Identifies the circuit
supplemented.
number that your company assigned
or that the Other Exchange Company
*The legend in the middle of this (OEC) provided on the order. This
BILL: Identifies the status of billing records.
windowidentifies the SUP numbers. number should followTelcordia
(Bellcore) standards for circuit ID
format. However, it can also be in
telephone #format or freeform.
The Work Queue Manager has the following tabs at the bottom of the
window:
• Task DetailProvides more
detailed information about the task, including who assigned the
task.
• PredecessorsDisplays all of
the tasks that you must complete before you can complete the
selected task.
• FollowersDisplays the tasks
that you cannot complete until you complete the selected task.
• ChecklistDisplays any
checklist items associated with a task. You must complete all
checklist items before you can complete the associated task.
• CircuitsDisplays circuits
related to a task.
• GatewayDisplays any gateway
event and its status associated with the task.
MANAGING TASKS
Slide 69 Managing Tasks
Managing tasks is what you have to do to complete your work in the
Work Management subsystem, thereby completing the service requests
that you receive.
When a task is first assigned to a work queue, it has a status of “New.”
When you accept it, the task’s status changes, and it no longer shows
“New” in the Status column on the Work Queue Manager window.
The action of accepting tasks organizes your work queue so that
you can quickly see which tasks are new, which are changed, and
which have a changed gateway event status.
When a task appears in your queue that someone else should work, you
can transfer the task to the appropriate queue for completion.
After you have finished the work and checklist items associated with
a task, the task should have a status of “Ready,” and you can
complete it. (Completing the task removes it from the work queue.)
ACCEPTING TASKS
When a task is first assigned to a work queue, it has a status of
“NEW.” When you accept it, the task’s status changes so that it no
longer shows “NEW” in the Status column on the Work Queue
Manager window, as illustrated below.
TOGETHER—ACCEPT A TASK
Along with your instructor, accept any two tasks in the work queue
whose status is “New.”
DEMO—TRANSFER A TASK
When a task appears in your queue that should be worked by someone
else, you can transfer the task to the appropriate queue for completion.
Watch as your instructor demonstrates this procedure.
TOGETHER—COMPLETE A TASK
After you have finished the work and checklist items associated with
a task, the task should have a status of “Ready,” and you can
complete it. (Completing the task removes it from the work queue.)
With your instructor, complete a task.
REJECTING TASKS
You can reject a task if it has a predecessor task that is incomplete or
inaccurate, such as when you have entered design lines incorrectly.
When you reject a task in your queue, the rejection action actually goes
against the predecessor task in the queue from which the predecessor
task originated. The task in your queue must be in “Ready” status
before you can reject a task.
Again, when you reject a task, you are really rejecting the predecessor
task. MetaSolv Solution allows you to choose the incomplete
predecessor task, which can be the last task before your task, or it can be
the first completed task that would, in turn, reject all tasks after it.
Whenever you reject a task, you should also enter a reject reason in the
Service Request Note area.
After you reject a task, it (along with any follower tasks) goes back to
“New,” with a “Pending” status. The task that you rejected goes to
“Rejected” status to be worked again. As soon as it is completed, your
task goes to “Ready,” or green light, as usual.
Note
Grace Days
The grace interval that you select for a task affects that
JEOPARDY CODES
Slide 70 Jeopardy Codes and Why Missed Codes
If you know that a task is in jeopardy of being completed late, you can
add a jeopardy code to the task. A jeopardy code associates a reason for
the potential lateness with the task and changes the status of the task so
that a quick glance at the queue indicates the jeopardy condition.
You do not have to go to the Task Type window to see which tasks are
critical. Instead, you can access the WQM window and select the task.
Then, at the bottom of the Task Detail tab window, you can see if a task
is critical.
Since jeopardy codes are a proactive way of tracking the reasons why a
critical task might be late, you should enter them prior to completion of
the task.
An example of the Task Jeopardy Codes window appears below:
Bomb icon
Note
Bomb Icon inherent
The “bomb” icon indicates that a jeopardy code has been
entered for the task.
GATEWAY EVENTS
Slide 71 Gateway Events Overview
A gateway event is the process of linking a third party vendor to
MetaSolv Solution. You can have inbound or outbound events, which
means that MetaSolv Solution can send information to the vendor, or
the vendor can send information to MetaSolv Solution electronically.
LESSON REVIEW
Slide 72 Review—Work Management
In this lesson, you have learned how to:
• Identify key elements of Work
Management subsystem.
• Describe the function of adding
new employees, parent work queues, and child work queues.
• Describe how the organization
calendar is associated with work queues.
• Describe the function of the
different task types and checklist items.
• Create a provisioning plan and
insert different tasks in the plan.
Slide 73 Review (cont’d)
• Set up the Auto Plan Selection
feature.
• 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 window.
• Accept, transfer, and complete
tasks and all checklist items.
Slide 74 Review (cont’d)
• Enter notes, why missed codes
and jeopardy codes in tasks.
• View gateway events.
• Describe the functions of
Gateway preferences.
• Describe the association between
gateway events and tasks.
UNIT WRAP UP
Slide 75 Wrap Up