Professional Documents
Culture Documents
RELEASE 8.1
Release: 8.1
Publication Date: 30 December 2009
Catalog Number:
Information Security: Level 2 – Sensitive
Created: 9/23/2008 12:49:00 PM
Account/FOP:
Author:
Editor:
Last Edited: 11/05/2010 10:53:39 AM
File Name: Task Engine 8.1.0 Product Description.docx
Template: Product.dot
4 Licensing Information..................................................................................................... 11
Task Engine uses Templates to capture the detailed technical design and
assignment Tasks required to fulfill a service order or network capacity
request. When a service or network request is received, Task Engine manages
the assignment of resources in the Amdocs Resource Manager inventory,
generating a DesignRecord for each configuration change. The way in which
resources are assigned is controlled by the automatic application of any
relevant rules and constraints. These are applied for each Task, ensuring that
the resulting design generates a consistent and correct set of DesignRecords for
each execution.
Each Task Engine Template stipulates the Task steps to be executed in order to
fulfill the request. Tasks can be manual or automated; request user input;
assigned to individuals, groups and departments; and sequenced to determine
the order of resource assignment. Typical Tasks would include the checking of
available capacity, port assignments, circuit design, cross-connect cabling and
customer equipment specification.
Task Engine ensures that service orders and network capacity requests are
implemented correctly and consistently each time. Automating the design is the
final step, providing not only consistent designs, but also the capability to
fulfill a high volume of provisioning requests without growing staff numbers.
Process integration
Task Engine is the principle fulfillment design tool within Amdocs OSS 8.1. Its
position in the fulfillment pipeline allows it to integrate with Amdocs Service
Fulfillment Adapter, Amdocs Service Catalog and Amdocs Order Management
Adapter to capture requests for services or network change. Once these
requests have been converted in to a network design by Task Engine, and
presented as DesignRecords, the process flow moves on to Amdocs Delivery
Engine for implementation.
Task Engine may also initiate Amdocs Route Finder to assist with common
circuit routing activities.
Service
Identify Provider Edge Router In this example the service details and
Order Create Customer Edge Router location information are passed in the
Parameters
Create CE-PE Link service order. The Template defines the
Create Bearer steps necessary to design the service
Create SVC/PVC request – identifying the provider edge
Allocate CE Logical IP address (PE) and customer edge (CE) routes,
Allocate PE Logical IP address
and VRF Numbers
specifying the PE to CE connectivity,
Allocate CER Loopback Address
and allocating IP addresses.
Obtain PER Loopback Address
Any number of Templates can exist for
Create Site Topology
each Design Project, for example, to
Specify Connectivity Topology
support the provisioning of gold, silver
Specify VPN Topology
and bronze variants of a service. The
creation of a Task Engine Design Project
and association of the required Template
can be completed automatically through the Service Fulfillment Adapter
(SFA), Order Management Adapter (OMA), through Service Catalog order
decomposition, or manually using the Task Engine Project Wizard.
Views
Task Engine does not introduce any additional Views.
WebReports
The Task Engine WebReports provide information on Design Projects at the
Project, Task and user level. As for all WebReports, filtering options are
provided, as well as context sensitive navigation to other tools and further
analysis of the object and related context in the network.
Wizards
Task Engine Wizards support the processing of Design Templates, undoing
Tasks within a Template, undoing a complete Design Project, and configuring
the user privileges.
Owner Wizard
The Owner Wizard enables configuration of Task ownership within Templates.
Homepages
All Task Engine objects have a dynamically generated HomePage allowing
access to configuration information on the object, and links to other related
objects. Every HomePage has standard attributes for naming, audit trail and
status management purposes.