Metasolv Tasks Flashcards by Whaler Band

Application Date task. It identifies the date on which the Customer gives the Access Service Request (ASR) to the Provider. Assign this task to a provisioning plan if you want the APP date on the Confirmation Notice to match the due date of the APP task.

If you want MetaSolv’s software to populate the APP field on the Confirmation Notice, you must include the APP task on your provisioning plan.

If the APP task is not included on your provisioning plan, the APP field on the FOC is blank unless you manually enter information into it. To enter information into this field, access the Confirmation window by first searching for and opening a service request on the Service Request Search window. Then, right-click on the service request and select Confirmation Notice from the pop-up menu.

APP Task

How well did you know this?

Not at all

Perfectly

Appointment task. Double-clicking this task opens the Appointment Selection window in the Work Management subsystem, which allows you to set up appointments. Assign this task to a provisioning plan if the work queue owner needs to schedule an appointment to support the service request.

Note: This is a smart task.

APPT Task

How well did you know this?

Not at all

Perfectly

AUTODSGN TASK

The Automated Design (AUTODSGN) task is a smart task. You can also run the AUTODSGN task as a system task.

Note: The AUTODSGN task ignores Circuit/Line Products that are in the Pending Disconnect status. This allows multiple activities (New, Change, and Disconnect) for similar products that coexist within the same order to be successfully processed by the System Task Server. For orders that disconnect an existing service and start a new service, both of which are designed by the AUTODSGN task, you can now select a provisioning plan containing both the Group Disconnect (GRPDISC) and AUTODSGN tasks. There are no errors in the design tasks because of Pending Disconnect activities. This allows the GRPDISC task to do the necessary work for these products, thus enabling the entire order to be fully automated.

The AUTODSGN task allows you to:

Automate provisioning of facility circuits with rate codes of DS0 and DS1

Automate dedicated plant assignment

AUTODSGN Task Automates Provisioning of Facility Circuits with Rate Codes of DS0 and DS1

This task provides access to the connection design process. Double-clicking the AUTODSGN task opens the Service Request Connections window, which lists all the connections on a service request. Double-clicking a connection on the Service Request Connections window opens the Connection Design window, which allows you to design connections and issue the Design Layout Report (DLR) for the selected service request.

The AUTODSGN task has been automated as a system task for provisioning the facility circuits with rate codes DS0 and DS1 using the assignment information returned by the DS0/DS1 Automated Design extension.

When the DS0/DS1 Automated Design extension is turned on, the AUTODSGN System task does the following:

Reads the assignment information from the extension logic.

Creates the design issues containing the appropriate information from the order.

Makes the assignments as per the information returned by the extension, and then associates to the order.

Builds the design (DLR) blocks representing these assignments.

Changes the status of the circuits on the order to Record Issued.

When the DS0/DS1 Automated Design extension is turned off, the default out-of-the-box functionality is executed, which does the following:

Makes an equipment port assignment at either end of the circuit and makes a “next-available” channel assignment to a parent circuit, which is coterminous with the circuit being auto-provisioned.

Creates the design issues containing the appropriate information from the order

Makes the determined assignments and then associates to the order.

Builds and arrange the design (DLR) blocks representing these assignments.

Changes the status of the circuits on the order to Record Issued.

Notes:

The AUTODSGN task supports only the new assignments and does not support any changes to the connections.

Only the working path and protect path are supported for Network Block Assignments.

See Custom Extensions Developer’s Reference for more information.

AUTODSGN Task Automates Dedicated Plant Assignment for PSR-ordered Circuits

Based on the setting of the AUTODSGN - Make Dedicated Plant Assignment for PSR-ordered Circuits preference, the AUTODSGN task can be automated as a system task to automate the assignment of dedicated plants for non-template based circuits that have either a DS0 or N/A rate code and are ordered on a PSR order as either a Circuit product or a Line product.

To automate the assignment of dedicated plants for non-template based Circuit and Line Products (traditional circuits) using the AUTODSGN task, do the following:

Enable the AUTODSGN - Make Dedicated Plant Assignment for PSR-ordered Circuits preference by setting it to Y under Preferences - Inventory Management - Automation.

Associate Equipment Specifications to Product Specifications.

Associate Equipment Specifications to Product Catalog Items.

Ensure that the existing dedicated plant at the service address supports the ordered service.

How well did you know this?

Not at all

Perfectly

This task automatically creates and saves a new design issue on an order. You can define this system task in provisioning plans that are assigned to Change orders. For all connections on the order, the AUTOSAVE task automatically completes the same actions that are performed by the Group Save option, which you can access from the Service Request Connections window.

After the predecessor task completes, the System Task server picks up the AUTOSAVE task and automatically creates and saves a new design for the connections on the order. For orders that use a provisioning plan with the AUTOSAVE task, you are not required to manually open each connection to create a new design and save it.

If you receive an error when completing the AUTOSAVE task, the task is sent to the exception queue as defined in the Exception Work Queue preference. Clicking the AUTOSAVE task opens the Service Request Connections window, which you use to correct any errors. After you have made the corrections, you can manually complete the the task, or you can transfer the task back to the system work queue to get picked up by the System Task Server.

If you did not configure the AUTOSAVE task as a system task during task generation, then you can manually complete the AUTOSAVE task from the Work Queue Manager window.

AUTOSAVE TASK

How well did you know this?

Not at all

Perfectly

This task automatically places the designs on an order in the Record Issued status. You must add this task after the design task in a provisioning plan.

For orders that use a provisioning plan with the AUTO_ISS task, you are not required to issue the designs on the design task (for only Change or Record Activity orders), because after the design task is completed, the System Task Server picks up the AUTO_ISS task and automatically places the designs on the order in the Record Issued status.

If any circuits on the order are not issued for a particular reason, the AUTO_ISS task is sent to the exception queue as defined in the Exception Work Queue preference.

Clicking the AUTO_ISS task opens the Service Request Connections window, which you use to correct any errors. After you have made the corrections, you can manually complete the task, or you can transfer the task back to the system work queue to get picked up by the System Task Server. You can complete the DD task after completing the AUTO_ISS task.

AUTO_ISS Task

How well did you know this?

Not at all

Perfectly

This task sends service request billing data from MetaSolv’s software to a specific billing system or a third-party vendor server, depending upon the billing gateway and API version you are using.

Note: You must set the Billing API Version preference to 4.0 to use the BILLING task.

BILLING TASK

How well did you know this?

Not at all

Perfectly

Carrier Access Billing System (CABS) Acknowledgment Date task. The CAD task is used to indicate that billing information has been successfully entered into the CABS Billing Preparation system.

You must complete the CID task before you can complete the CAD task.

Double-clicking the CAD task opens the CABS Billing Navigator window - ASR Billing Address view. When accessed through the CAD task, the CABS Billing Navigator window is a read-only window. It displays billing information that was either manually or mechanically sent to CABS.

Note: This is a smart task.

CAD Task

How well did you know this?

Not at all

Perfectly

Confirming Design Layout Report Date task.

If you want MetaSolv’s software to populate the CDLRD field on the Confirmation Notice, you must include the CDLRD task on your provisioning plan. Assign this task to a provisioning plan if you want the CDLRD date on the Confirmation Notice to match the due date of the CDLRD task.

If the CDLRD task is not included on your provisioning plan, the CDLRD field on the FOC is blank unless you manually enter information in it. To enter information in this field, access the Confirmation window by first searching for and opening a service request on the Service Request Search window. Then, right-click on the service request and select Confirmation Notice from the pop-up menu.

CDLRD Task

How well did you know this?

Not at all

Perfectly

CABS Issue Date task. Once the task is in “Ready” (Green Light) status, send the order billing information to CABS manually or through an interface.

Double-clicking this task opens the CABS Billing Navigator window - ASR Billing Address view, allowing you to:

Calculate access mileage using the Vertical and Horizontal (V&H) coordinates

Associate the Universal Service Order Codes (USOCs) with the locations on the service request

You must complete this task before you can complete the CAD task.

Note: This is a smart task.

CID Task

How well did you know this?

Not at all

Perfectly

Connection Identification task. It is used for PSR service requests only. It is preloaded for customers who purchase the Product Service Request module.

Double-clicking this task opens the Service Request Connections window, allowing you to:

Create a connection ID for customers that are ordering a new connection.

Retrieve an existing connection ID for customers that are changing or disconnecting their existing connection.

Delete a connection ID.

Update a connection ID.

Automatically create a connection ID for each specific service item associated with the network system.

Manually create a connection ID for each specific service item associated with the network system.

The CKTID task has been automated as a system task for generating the connection ID for the products ordered on a PSR order.

The automated CKTID task generates the connection ID using the input values returned by the ConnectionIdAutomation extension. See Custom Extensions Developer’s Reference for detailed parameter-level information.

When the ConnectionIdAutomation extension is turned off, the default out-of-the-box functionality is executed to generate the connection ID.

The following data from the order is used for generating the connection ID for traditional circuits:

Service Type Category

If the Service Type Category = CLFI, the system builds a CLF circuit

If the Service Type Category is of any other value, the system builds a CLS circuit

Jurisdiction Code

Network Location A

Network Location Z

Service Type Code

Service Type Code is used as Facility Type for CLF

Rate Code

Framing

Line Coding

Framing ANSI Indicator

Partition Group

If the security preference, Use Partition Level Security for Access to Inventory Data is set to Y, the system updates the Partition Group field to All Access.

If the security preference, Use Partition Level Security for Access to Inventory Data is set to N, the system leaves the Partition Group field blank.

For generating the connection ID for template-based circuits, ensure that you select the Auto Id check box in the Managing a Connection Spec window (Inventory Management Setup - Network Templates - Connection Specs).

Notes:

CKTID Task Automation is applicable only to the circuits that are ordered through PSR.

The out-of-the-box algorithm applies the automated circuit id generation to traditional circuits (CIRCUIT and INTRNCKT Item types) and template-based connections (CONNECTOR item types).

The out-of-the-box functionality for traditional circuits generates either CLS or CLF type circuits.

The out-of-the-box functionality for template-based connections uses the current process to generate OTS type circuits.

The only valid connection formats for the custom extension and out-of-the-box functionality are CLS, CLF, OTF, and OTS .

The only valid circuit types are C, F, and S.

If the required information is not populated on the order, the task fails and the service items error out.

See Custom Extensions Developer’s Reference for more information.

CKTID Task

How well did you know this?

Not at all

Perfectly

Clarification Request task.

Double-clicking this task in the Work Queue Manager window opens the ASR Clarification/Notification request form.

Note: This is a smart task.

CLAREQ Task

How well did you know this?

Not at all

Perfectly

Confirmation task. This task allows you to:

Open the Confirmation Notice (CONF) to issue the Firm Order Confirmation (FOC) to the Customer.

View information received from the Provider on the FOC.

The FOC is the form the Provider submits to the Access Carrier (AC), indicating the date on which the ordered connections are to be installed.

ASRs

If the CONF task is associated with an ASR, double-clicking the task opens the Confirmation Notice window - Header tab. With this window you can:

ISRs

If the CONF is associated with an ISR, double-clicking the task opens the Connection Reference window. With this window, you can:

View connection references.

Associate connection references with an existing connection.

Add, delete, or modify connection references.

Note: This is a smart task.

CONF Task

How well did you know this?

Not at all

Perfectly

Parent Order Coordination task.

Double-clicking the CORD task opens the Service Request Hierarchy window. This window allows you to:

View the status of any associated child service requests.

Associate child service requests to the parent service request.

All parent order provisioning plans should include the CORD task unless you are using the Service Request Worksheet module to create child service requests. If you are using the Service Request Worksheet module, you should use the WORKS task to create child service request and relate them to parent service requests.

Note: This is a smart task.

CORD Task

How well did you know this?

Not at all

Perfectly

Due Date task. You should:

Complete this task after a circuit has been placed “In Service.”

Include this task on all provisioning plans in Work Management, except when you have a parent/child provisioning plan.

Note: If you have a parent/child provisioning plan, you only need the DD task on the child plan.

You should include the DD task on provisioning plans for service requests that involve:

Creating a new circuit ID or telephone number

Disconnecting orders that involve an existing circuit ID

Changing orders that involve an existing circuit ID

Creating designs for telephone number circuits such as Dialtone or POTS (plain old telephone) lines, where a circuit design is created

Change orders for designed Dialtone or POTS lines

Disconnect orders for designed Dialtone or POTS lines

When you complete the DD task the following occurs:

The status of the corresponding order is changed from “Tasks Generated” to “Due Date Completed,” indicating that work on the circuit has been completed.

The status of the circuit is changed from “DLR Issued” to “In Service” or “Disconnected.”

Once you have completed the DD task, you cannot:

Reopen the DD task.

Supplement the service request.

Note: You can complete the DD task in the background if you have the Background Processor software option.

If the Lock Open Orders preference is enabled:

You cannot complete an order’s DD task when another user has the order open.

Another user cannot modify an order when you are in the process of completing the order’s DD task.

Another user cannot modify an order until the Background Processor has completed the DD task when you send the DD task to complete in the Background Processor.

DD Task

How well did you know this?

Not at all

Perfectly

Design Layout Report Date task. This smart task provides access to the connection design process. Double-clicking the DLRD task opens the Service Request Connections window, which lists all connections on a service request. Double-clicking a connection on the Service Request Connections window opens the Connection Design window, which allows you to design connections and issue the Design Layout Report (DLR) for the selected service request.

The DLRD task is recommended for all provisioning plans that are associated with ASRs or LSRs when a connection is provisioned. This task can only be completed if all the connections on the order have been placed in DLR issued status. Because the DLRD task validates that the DLR was issued, you get an error message if you try to complete the DLRD without placing the connection in “DLR Issued” status first.

Any cable pair assignment information you entered while completing the LAM task appears on the Connection Design window - CLR/CLR Design or Schematic Deisign section.

If you use a supplement to cancel a service request, you must cancel service request connection assignments on the Service Request Connections window in the Service Provisioning subsystem before you can complete the DLRD task.

Note: This is a smart task.

DLRD Task

How well did you know this?

Not at all

Perfectly

Directory Service Completion Notice task.

Double-clicking this task opens the Directory Service Confirmation Notice (DSCN) Form window. From this window, you can complete the DSCN form for the order.

Note: This is a smart task.

DSCN Task

How well did you know this?

Not at all

Perfectly

MetaSolv Solution uses the E911 smart task to manage E911 extract data. Since the E911 smart task replaces gateway event functionality, you must manually add the smart task to all provisioning plans that require E911 records. If the task is not present on the provisioning plan, and the Send to E911 checkbox is checked on the Product Catalog window - General tab for any item associated with the order, MetaSolv Solution returns an error during provisioning plan assignment. The E911 smart task is required at task generation when you have an order with an item that requires E911 processing.

The E911 smart task (E911SMRT) allows you to:

Select and send a group of telephone numbers, or individual telephone numbers, to the E911 service provider for processing.

Access the E911 Maintenance window from the TN Records Search window when changes are required or data needs to be resent (without leaving the Work Management module).

Reopen the E911 smart task when supplementing an order.
When you supplement an order, you can reopen the E911 smart task to change values appropriate to your business needs (such as function code changes).

Place the E911 smart task at any point in the provisioning plan (before or after due date, for example). In addition, you are not required to work any of the items associated with the E911 task prior to completing it.

Complete E911 processing one of two ways: manually, or by using the system queue.

Related Concepts

List of Task Types
Smart Tasks
Task Types

Related FAQs

Can I have multiple E911 smart tasks on the same provisioning plan?

E911 Task

How well did you know this?

Not at all

Perfectly

Equipment Install task.

Double-clicking this task opens the Service Request Equipment window that lists all of the end-user locations and associated equipment specifications that have been ordered. If one of the locations listed in the Service Request Equipment window already has installed equipment, a checkmark appears in the Installed checkbox.

Double-clicking one of the rows in the Service Request Equipment window opens the Equipment Inventory window which allows you to verify what equipment is installed at the end-user location and install equipment ordered for the end-user location on the product service request (PSR).

This task is available for any order containing equipment at a location.

Note: This is a smart task.

EQ INST Task

How well did you know this?

Not at all

Perfectly

End User Billing Acknowledgement Date task.

Double-clicking the EUAD task opens the End User Bill Prep window, which acknowledges that End-User (EU) billing has been set up in the billing system. This task is used for customer interfaces with EU billing systems.

You must complete the EUID task before you can complete the EUAD task.

Note: This is a smart task.

EUAD Task

How well did you know this?

Not at all

Perfectly

End User Billing Issue Date task.

Double-clicking the EUID task opens the End User Bill Prep window, allowing you to enter the appropriate change code and finish preparations for EU billing. You can only complete the EUID task when it is in green light status with a bill status of “E” or nothing by the task.

This task is a prerequisite to the EUAD task.

Note: This is a smart task used for customer interfaces with EU billing systems.

EUID Task

How well did you know this?

Not at all

Perfectly

Facility Confirming Design Layout Report Date task.

If you want MetaSolv’s software to populate the FCDLRD field on the FOC, you must include the FCDLRD task on your provisioning plan. The Facility Confirming Design Layout Report Date field identifies the date the Confirming Design Layout Report (CDLR) is received at the Provider design control office.

If this task is not included on your provisioning plan, the FCDLRD field on the FOC is blank unless you manually enter information in this field. To manually enter information in this field, access the Confirmation window by first searching for and opening a service request on the Service Request Search window. Then, right-click on the service request and select Confirmation Notice from the pop-up menu.

FCDLRD Task

How well did you know this?

Not at all

Perfectly

Facility Due Date task. Assign this task to a provisioning plan if you want the FDD date on the Confirmation Notice to match the due date of the FDD task.

If you want MetaSolv’s software to populate the FDD field section on the FOC, you must include the FDD task on your provisioning plan.

If this task is not included on your provisioning plan, the FDD field on the FOC is blank unless you manually enter information in this field. To manually enter information in this field, access the Confirmation window by first searching for and opening a service request on the Service Request Search window. Then, right-click on the service request and select Confirmation Notice from the pop-up menu.

Study These Flashcards

FDD Task

Facility Design Layout Report Date task. Assign this task to a provisioning plan if you want the FDLRD date on the Confirmation Notice to match the due date of the FDLRD task.

If you want to populate the FDLRD field on the FOC, you must include the FDLRD task on your provisioning plan.

If this task is not included on your provisioning plan, the FDLRD field on the FOC is blank unless you manually enter information in the field. To manually enter information in this field, access the Confirmation window by first searching for and opening a service request on the Service Request Search window. Then, right-click on the service request and select Confirmation Notice from the pop-up menu.

Study These Flashcards

FDLRD Task

Fiber Network Identification task.

Double-clicking this task opens the Fiber Network Identifier window so you can enter the FNI to support a ring circuit service request.

Any of the following methods allow you to have an FNI task in the provisioning plan:

Assigning it to a provisioning plan dedicated to ring circuit service requests.

Dynamically adding an FNI task to the provisioning plan during task generation by establishing a rule and behavior in the rules and behaviors functionality.

Manually inserting or adding the FNI task during task generation.

If you decide to use the rules and behaviors functionality to automatically insert the FNI task, the ideal situation is to insert the FNI task when:

The service request contains a value of “N” New in the FNI field.

The provisioning plan chosen contains a CONF task.

The provisioning plan does not already contain a FNI task.

MetaSolv’s software can automatically insert the FNI task between the predecessor of the CONF task and the CONF task. However, you must manually establish all of these relationships on the Rules and Behaviors window before MetaSolv’s software can automatically insert the FNI task.

Note: This is a smart task.

Study These Flashcards

FNI Task

Facility Plant Test Date task. Assign this task to a provisioning plan if you want the FPTD date on the Confirmation Notice to match the due date of the FPTD task. If you want MetaSolv’s software to populate the FPTD field on the FOC, you must include the FPTD task on your provisioning plan. If this task is not included on your provisioning plan, the FPTD field on the FOC is blank unless you manually enter information in the field. To manually enter information in this field, access the Confirmation window by first searching for and opening a service request on the Service Request Search window. Then, right-click on the service request and select Confirmation Notice from the pop-up menu.

FPTD Task

Facility Record Issue Date task. This task indicates the date all the circuits on the order were placed in “Record Issued” status.

FRID Task

Facility Wired and Office Tested task. This task indicates the scheduled date for internal wiring and testing of the service.

FWOT Task

Issue Loop Assignment and Makeup task. This task allows you to complete the issue and print the Loop Assignment and Makeup (LAM) request form. Double-clicking this task opens the Loop Assignment and Makeup Circuit Listing window. The ILAM task is applicable to all order types except Product Service Request (PSR) and Local Service Request (LSR) order types. If the ILAM task is associated to a PSR order or an LSR order, double-clicking this task opens the Service Request Search window. Note: This is a smart task.

ILAM Task

IP Assignment task. This task allows you to assign IP address blocks during provisioning rather than during PSR entry. Double-clicking this task opens the IP Address Assignment window. You can automatically or manually assign an IP address. You can only assign IP address blocks if you have purchased the IP Address Management module. You can set this task as a system task so it is automatically completed by the System Queue. Note: This is a smart task.

IPASSIGN Task

Loop Assignment and Makeup task. This task allows you to enter local loop and cable pair information for the connection. Double-clicking this task opens the Service Request Connections window. Double-clicking a circuit on the Service Request Connections window opens the Cable Pair Connection Assignment window, which allows you to enter local loop and cable pair information for the connection. Any cable pair assignment information that you enter on the Cable Pair Connection Assignment window displays on the Connection Design window - CLR/DLR section when you begin working on the DLRD task or RID task. Use this task to add cable pair assignment information to the connection design lines once the connection is in “Record Issued/DLR Issued” or “In Progress” status. Complete the cable pair connection assignment using the LAM task before you design the connection using the DLRD or RID task. Note: This is a smart task.

LAM Task

Double-clicking this task will invoke the PSR to ASR mapping process allowing you to choose PSR items to map to an ASR order. Note: This is a smart task.

MAPASR Task

Network Design task. This is a smart task. Double-clicking this task opens the Graphic Canvas, allowing you to: Render the drawing of the Network System. Make associations of equipment, connections, etc. to the network system. Note: Ordered systems and elements do not have to be 'In Service' before the NET DSGN task is completed. The status will be changed from Pending to In Service when the Due Date (DD) task is completed. The Net Design task has been automated as a System task for both the PSR ordered and non-ordered network systems. The automated Net Design task performs the following: Copies the network system and its attributes from the ordering tables to the Inventory tables. The Net Design task assumes that the network system (VPN) is actually on the order as a network system product catalog item type that is associated with a network template. Adds the ordered customer edge (network element) to the network. The Net Design task assumes that the customer edge component is actually on the order as a component product catalog item type that is associated with a network template. Associates any equipment on the order with the customer edge network element. The Net Design task assumes that the equipment has been ordered and is associated with the network element on the order. Associates the customer edge with the provider edge. The Net Design task uses the network area concept to determine which provider edge (network element) to choose, similar to the current PCONDES logic. For change orders, only the following activities are supported: Adding new last mile connections. Updating customer edges (CE), network systems, and physical connection custom attributes. When custom extensions are turned off, use the network area mapping to specify endpoint (provider edge component and provider network) details for each last mile connection. Note: The automated Net Design task is not applicable for virtual connections and supplement change orders involving any disconnect/cancel activities. See Custom Extensions Developer’s Reference for more information.

NET DSGN Task

Pick Child Provisioning Plan task. Double-clicking this task opens the Task window. You can then select specific child plans you would like to associate with the parent plan you have selected. When a NEWTASK (or a smart task with NEWTASK behavior) is worked from Queue Manager, the follower task is based on the due date of the NEWTASK. This keeps the integrity of the parent/child relationship between the NEWTASK on the parent plan and its follower task on the child plan. If you have the Allow Completion of NEWTASK Without Picking Child Plan preference disabled and you attempt to complete this task without associating a child plan(s) with it, a message box appears, asking you if you would like to associate child plan(s). If this preference is enabled, you must associate a child plan before you can complete this task. Note: This is a smart task.

NEWTASK Task

Order Hierarchy task. Double-clicking this task opens the Service Request Hierarchy window. This window allows you to: View the status of any associated child service requests. Associate child service requests to the parent service request. All parent order provisioning plans should include either the ORDHEIR task or the CORD task unless you are using the Service Request Worksheet module to create child service requests. If you are using the Service Request Worksheet module, you should use the WORKS task to create child service request and relate them to parent service requests. Note: This is a smart task.

ORDHEIR Task

The Physical Connection Design (PCONDES) task is applicable only to the template-based physical connections. The PCONDES task is a smart task. You can also run the PCONDES task as a system task. Note: The PCONDES task ignores physical connections that are in the Pending Disconnect status. This allows multiple activities (New, Change, and Disconnect) for similar products that coexist within the same order to be successfully processed by the System Task Server. For orders that disconnect an existing service and start a new service, both of which are designed by the PCONDES task, you can now select a provisioning plan containing both the Group Disconnect (GRPDISC) and PCONDES tasks. There are no errors in the design tasks because of Pending Disconnect activities. This allows the GRPDISC task to do the necessary work for these products, thus enabling the entire order to be fully automated. The PCONDES task allows you to: Automatically design physical connections Automate dedicated plant assignment PCONDES Task Automatically Designs Physical Connections The PCONDES task plays an important role in the service provisioning process by providing the ability to automatically design physical connections. Using this task, you have the ability to use Equipment Assignment Templates to select a specific Card Type or Card Specification. Notes: The PCONDES task must be processed prior to the VCONDES task and the provisioning plan should be configured accordingly. The custom attributes must be populated on the PSR order. The custom attributes cannot be updated or entered during the processing of the PCONDES task. When you manually open the PCONDES task, only the Bandwidth NGN Connections are displayed in the Service Request Connections window. The options that are available for this task are: Auto Provision and Group Print. The assumption for the automation of the PCONDES task is that the connection must be “new” or "change" activity. For PSR orders containing new, change, disconnect connections, or a combination of these, only the new and change connections are processed by the PCONDES task. You can extend the PCONDES task logic using extension points when the PCONDES task is run automatically from the System Task Server. There are two extension points for the PCONDES task. One extension point runs before the component is selected and the other extension point runs before the port is selected.The extension points enable you to do the following in the order listed: Select the appropriate component or element to use in the physical design of the connection. Select the appropriate port address to use in the physical design of the connection. The extension point is triggered before the port address is selected by the PCONDES autoprovisioning process. If a port address is successfully selected by the extension logic, the existing PCONDES autoprovisioning logic is bypassed. If a port address is not selected by the extension logic, the existing PCONDES autoprovisioning logic still executes. For example, you can enter a PSR order and assign a provisioning plan that defines the PCONDES task as a system task. The PCONDES task is used to automatically design physical connections. When the status of the PCONDES task becomes Ready, the System Task Server processes the task. The extension logic executes and, based on the selection logic in the extension and the information on the order, the appropriate port address is selected for the design of the physical connection. See Custom Extensions Developer’s Reference for more information. The physical connection design process using the PCONDES task consists of the following steps: The connection specification for the ordered connection is used to determine the component type inside the network system. For example, Digital Subscriber Line Access Multiplexer (DSLAM). If the extension is not utilized, the component type and the geographical area construct of the end user location address are used to find the correct network areas and components by default. The connection on the order can have only one end user location; otherwise, the system task fails and it is moved to the exception queue. A new issue is created and the custom attributes are copied to the new issue. The network system is associated to the connection and the locations are updated on the circuit. Note: Network Template Setup is used here. Use the product specification and the connection specification to find the appropriate service application and equipment assignment templates (EAT). View all the equipment specifications for the end user locations. If the End User Location Assignment Required check box is selected, a port assignment is required at the end user location. If the Network Location Assignment Required check box is selected, a port assignment is required at the network location for the specific network component. When determining the equipment that must be assigned to the physical connection, you must consider the following: If the equipment specification ordered through the EQINST task is installed, use this equipment specification if it has available ports of the correct rate code. If the equipment specification has not been installed or if it does not have available ports of the correct rate code, determine whether an EAT is configured. If so, match its rate codes to that of the connection. If they match, find an unassigned port for the installed equipment that matches with the associated equipment specifications. If no equipment specifications are associated or no available ports are found, perform the same check using the associated equipment types. If no available ports are found or the rate code of the circuit is not associated in the EAT, search for available ports on any piece of equipment installed at the location. If no available ports are found, a port assignment is not made. Note: For assignments to the network component, the equipment must be associated to the network component in network systems. PCONDES Task Automates Dedicated Plant Assignment for PSR-ordered Connections Based on the setting of the PCONDES - Make Dedicated Plant Assignment for PSR-ordered Connections preference, the PCONDES task can be automated as a system task to automate the assignment of dedicated plants for template-based connections that are ordered on a PSR order and build the dedicated plant design block. To automate the assignment of dedicated plants for template-based connections using the PCONDES task, do the following: Enable the PCONDES - Make Dedicated Plant Assignment for PSR-ordered Connections preference by setting it to Y under Preferences - Inventory Management - Automation. Associate Equipment Specifications to Product Specifications. Associate Equipment Specifications to Product Catalog Items. Ensure that the existing dedicated plant at the service address supports the ordered service. Related Concepts Smart Tasks Task Types

PCONDES Task

Product Service Request/Local Service Request task. This task allows you to auto-generate child LSRs and DSRs for a PSR. Double-clicking this task opens the PSR to LSR Mapping window if either of the following conditions apply: The Perform PSR/LSR Mapping Outside the PSR Order preference is enabled, and the PSR contains portability, loop service, loop service with number portability, or directory service request information. The Perform PSR/LSR Mapping Outside the PSR Order preference is disabled, but you did not perform PSR to LSR/DSR mapping on the service request. Warning! If this preference is disabled after you click the Finish button for a PSR, the software does not force you to perform PSR to LSR/DSR mapping on the PSR/LSR smart task. Note: Double-clicking the PSR/LSR task does not open the PSR to LSR Mapping window if the PSR does not have portability, loop service, loop service with portability, or directory service request information. You must complete the PSR to LSR Mapping window before the MetaSolv Solution allows you to complete this task. When you complete the window, the MetaSolv Solution automatically generates child LSRs and DSRs directly from the parent PSR. The MetaSolv Solution requires you to select a provisioning plan with the PSR/LSR smart task when you generate tasks if both the following conditions apply: The PSR contains portability, loop service, loop service with number portability, or directory service request information. The Perform PSR/LSR Mapping Outside the PSR Order preference is enabled. Note: This is a smart task. Related Concepts PSR to LSR/DSR Mapping Related FAQs What types of LSRs/DSRs can I map? When are child LSRs/DSRs required? Why can't I use the PSR to LSR mapping function?

PSR/LSR Task

Plant Test Date task. If you want MetaSolv’s software to populate the PTD field on the FOC, you must include the PTD task on your provisioning plan. If the PTD task is not included on your provisioning plan, the PTD field on the FOC is blank unless you manually enter information in it. To manually enter information in this field, access the Confirmation window by first searching for and opening a service request on the Service Request Search window. Then, right-click on the service request and select Confirmation Notice from the pop-up menu.

PTD Task

Response Confirmation Notice task. Double-clicking the RCONF task opens the Confirmation Notice window for the appropriate order type. ASRs If the RCONF is associated with an ASR, double-clicking the task opens the Confirmation Notice window. If the CONF was electronically received, you can: View Confirmation Notice information. Click the Tasks button to open the Tasks window - Plan Selection tab. This window allows you to view information about all the tasks associated with the service request including: Task due dates Task predecessors and followers Task checklist items Gateway events associated with the tasks Task connections The work queue for each task Click the CLR button to open the Service Request Connections list window. With this window you can view connections for the service request. If the CONF was not electronically received, you can: Manually enter data relevant to the Confirmation Notice you received. Click the Tasks button on the to open the Tasks window - Plan Selection tab and view information about the tasks associated with the order. Click the CLR button to open the Service Request Connections list window. Click the CKT X-Ref button on the Confirmation Notice window to open the Connection Reference -Child Order window. On this window, you can: Associate connection references for child orders with a parent order's connections. View connection information for parent and child orders. Add, modify, or delete connection references. Click the Validate button to validate the information you manually entered on the Confirmation Notice window. LSRs If the RCONF is associated with an LSR, double-clicking the task opens the Local Service Request window - Local Service Request Confirmation (LSC) form. With this window you can: Enter data relevant to the Confirmation Notice you received. Validate the data entered on the Confirmation Notice. View service detail records. Print the Confirmation Notice. ISRs If the RCONF is associated with an ISR, double-clicking the task opens the Connection Reference window. With this window, you can: View connection references, Associate connection references with an existing connection, Add, delete, or modify connection references, Note: This is a smart task. Related Concepts Smart Tasks Task Types

RCONF Task

Record Issue Date task. This task provides access to the connection design process in the Service Provisioning subsystem. Double-clicking the RID task opens the Service Request Connections window in the Service Provisioning subsystem. Double-clicking a connection on the Service Request Connections window opens the Connection Design window, which allows you to design connections and issue the Design Layout Report (DLR) for the selected service request. The RID task is recommended for all provisioning plans that are associated with PSRs or ISRs when a connection is provisioned. This task can only be completed if all the connections on the order have been placed in “Record Issued” status. Because the RID task validates that the record on the connection was issued, you receive an error message if you try to complete the RID task without placing the connection in record issued status. Any cable pair information you entered while completing the LAM task appears on the CLR/DLR Design section on Connection Design window. If you use a supplement to cancel a service request, you must cancel service request connection assignments on the Service Request Connections window in the Service Provisioning subsystem before you can complete the RID task. Note: This is a smart task.

RID Task

Run Executable task. This task allows you to use the Work Queue Manager window to: Launch any executable file installed on your computer. Although the RUNEXE task is preloaded, you must define the RUNEXE task to launch a specific executable file. You must set up a RUNEXE task on the Task Type window before you can use the double-click action of this task. Open a saved document in another application. The following example opens a specific Microsoft Word document: c:\Program Files\Microsoft Office\Office\WINWORD.EXE "c:\graphical design lines.doc" Use quotes around the file name if it or it's directory path contains spaces. If the file name and path do not contain spaces, you do not need to include the quotes. For example: c:\progam~1\micros~2\Office\winword.exe c:\sample.doc Launch the double-click action of another task. Instead of opening an executable or specific file, you can assign the RUNEXE task to perform the action of another work management task

RUNEXE Task

Scheduled Issue Date task. This task indicates the scheduled date that the company will issue a firm service order.

SID Task

The Suspend task supports Product Service Request (PSR) suspend service requests. The provisioning plan you use for a suspend service request should have a Suspend task. Any of the following methods allow you to have a Suspend task in the provisioning plan: Creating a provisioning plan for suspend service requests and assigning the Suspend task to the provisioning plan. Dynamically adding a Suspend task to the provisioning plan during task generation by establishing a rule and behavior in the rules and behaviors functionality. Manually inserting or adding the Suspend task during task generation. There are several things you must do before the suspend task can work correctly including: Creating the Suspend task on the Task Type window Note: Although the Suspend task is a smart task, it is not preloaded. Defining a grace period and queue days for the suspend task on the Suspension Period window. Although a Suspend task might be assigned to your work queue, it may not appear in your work queue immediately after tasks are generated. This is because Suspend task can be set to not show up in your work queue until an appointed time. The length of time before the Suspend task displays in your work queue and other criteria regarding the Suspend task is determined in Application Setup on the Suspension Period window. For example, if you set the Suspend Grace Period field for 30 days, and the Suspend Queue Days field for 5 days, the Suspend task shows up in your work queue 25 days after the suspension period begins (so, five days before service should be suspended). In another example, if the suspend grace period is 30 days, and the suspend queue days is also 30 days, the Suspend task shows up in your work queue immediately. Once the Suspend task appears in your work queue, you can double-click it to open the Restore/Disconnect Products window to disconnect or restore service. Related Concepts Rules and Behaviors Task Types

SUSPEND Task

Translation task. This task allows you to use the Work Queue Manager to view and enter translation information for switched circuit service requests. The TRANS task replaces the older XL10, XL100, XL5ESS and XLDC0 tasks. For PSR orders, double-clicking the TRANS task opens the Product Service Request window, from which you select a product or service on the order and view or print the Tech Translation Sheet for that product or service. For other types of orders, double-clicking the TRANS task opens the Translations window, from which you can: Enter translation information. View or delete circuit routing information. Enter or change contact information. Print the trunk circuit order. View the End Office Detail Form. View trunk group information. View the Trunk Circuit Order report. Since the TRANS task must be associated with a service request that uses the Translation Questionnaire (TQ), the TRANS task is for switched circuits service requests. Note: This is a smart task.

TRANS Task

The Virtual Connection Design (VCONDES) task plays an important role in the service provisioning process by providing the ability to automatically design virtual connections through the VCONDES task. Notes: The PCONDES task must be processed prior to the VCONDES task and the provisioning plan should be configured accordingly. The custom attributes must be populated on the PSR order. The custom attributes cannot be updated or entered during the processing of the VCONDES task. When you manually open the VCONDES task, only virtual connections are displayed in the Service Request Connections window. The options that are available for this task are: Auto Provision and Group Print. The assumption for the automation of the VCONDES task is that the connection must be “new” or "change" activity. For PSR orders containing new, change, disconnect connections, or a combination of these, only the new and change connections are processed by the VCONDES system task. You can extend the VCONDES task logic using execution points when the VCONDES task is run automatically from the System Task Server. The extension point for VCONDES enables you to provide the network component to use for the design. The default network component is used based on network areas. For example, you can enter a PSR order and assign a provisioning plan that defines the VCONDES task as a system task. The VCONDES task is used to automatically design virtual connections. When the status of the VCONDES task becomes Ready, the System Task Server processes the task. The extension logic executes, and based on the selection logic in the extension and the information on the order, the appropriate component or element is selected for the design of the virtual connection. See Custom Extensions Developer’s Reference for more information. The virtual connection design process using the VCONDES task consists of the following steps: The connection specification for the ordered connection is used to determine the component type inside the network system. For example, the connection specification may indicate the component type should be a Broadband Remote Access Server (BRAS). If the extension is not utilized, the component type and the geographical area construct of the end user location address are used to find the correct network areas and components. The connection on the order can have only one end user location; otherwise, the system task fails and it is moved to the exception queue. The ordered connection specification must have only one component marked as a network extension; otherwise, the system task fails and it is moved to the exception queue. A new issue is created and the custom attributes are copied to the new issue. Allocations are made between the virtual and the physical connection. Note: You can define the VCONDES task as either a smart task or a system task. Related Concepts Smart Tasks Task Types

VCONDES Task

Worksheet task. You can assign this task to your provisioning plan only if you purchased the Service Request Worksheet module. This task is typically assigned to a provisioning plan for parent service requests. Ideally, it is one of the first tasks performed and it comes before the DLRD task. Double-clicking the WORKS task opens the Worksheet window which allows you to: See a graphical representative of a network Enter information on worksheets that apply to the service request Relate child service requests to parent service requests with the Service Request Hierarchy view Create child service requests and automatically relate them to parent service requests Access templates for child service requests To open the Service Request Worksheet, the WORKS task must be associated with an ASR or ISR with a circuit ID. Note: This is a smart task.

WORKS Task

Wired and Office Tested task. This task indicates the scheduled date that the company internally wires and tests the service

WOT Task

is used if a task has the potential of being late.

Jeopardy

are used to explain why a task is completed late

Why Missed

If a system task has a jeopardy code, and the jeopardy code is not closed when the task is ready to be completed, the task is sent to the

Exception Queue

(True or False) A smart task cannot be a system task since it usually requires some user intervention. Therefore, it cannot be completed automatically. In addition, a system task cannot have any associated checklist items since they require manual processing

True

(True or False) You must designate a task as a system task to send it to the system queue for automatic completion. You can transfer the task from the system queue to another work queue for manual processing before the task completes. By transferring the task from the system queue, you do not remove its system task property. The next time the task is generated, it is sent to the system queue again unless you change the task type

True

(True or False) If a system task requires a why missed code, MetaSolv Solution determines if the task’s predecessor required a why missed code. If it did, the same why missed code is automatically associated with the system task, and the task can automatically complete.

True

(True or False) If the predecessor does not have a why missed code, MetaSolv Solution determines the setting of the System Queue Default Why Missed Code preference. This preference tells MetaSolv Solution to either add a default why missed code to the system task or send the task to the exception queue. Regardless, the system task can automatically complete in the system queue.

True

Metasolv Tasks Flashcards

(53 cards)