Professional Documents
Culture Documents
Release: 8.1
Publication Date:
Catalog Number:
Information Security: Level 2 – Sensitive
Created: 06/02/11
Account/FOP:
Author: Segev Lev
Editor:
Last Edited: 06/02/11
File Name: Service Fulfillment Adapter 8.1 Product Description.docx
Template: Product.dot
4 Licensing Information............................................................................................... 15
Pre-integrated with the Amdocs OSS 8.1 suite, the Service Fulfilment
Adapter supports the eTOM service configuration and activation lifecycle.
Its pluggable architecture allows fulfilment plug-ins for other third-party or
legacy fulfilment systems to be easily developed and integrated into the
overall fulfilment architecture.
Pluggable Architecture
Service Fulfillment Adapter’s extensible design allows fulfillment plug-ins
for other fulfillment components to be developed, allowing easy integration
of new and legacy components.
Plug-ins for Resource Manager, Task Engine and Delivery Engine are
provided as standard.
Simplified Configuration
Configuration of fulfillment processes is though a single XML-based
configuration file for each high-level service operation. This file-based
approach facilitates simplified configuration management and deployment.
Core features
Unified Fulfillment Interface
The Service Fulfillment Adapter implements the Manage Resource Service
(MRS) capability.
The MRS capability defines the functionality to request the design and
implementation of a service on the network including its characteristics.
CPE Location
Find Free Port
Port No.
Create xSDL
Service Name Connection
DSL Circuit
PVC
Create ATM PVC Project
Project
Implement
Connectivity
Input characteristics
CPE Location
Service Name
Fulfillment processes and the mappings between these
XML-based Configuration
XML-based configuration files are used to specify the detailed fulfillment
steps which must be performed for a particular service specification,
version, operation, order type and method. Such configuration files are
reusable so that for example the same fulfillment steps may be relevant to
multiple service specifications or multiple versions of the same
specification. Such configuration files are easy to maintain and to deploy
and may be configuration managed.
Extensible Architecture
The Service Fulfillment Adapter has been designed to be extensible and to
support the integration with non-Amdocs and legacy fulfillment processes.
This is achieved by creating a fulfillment plug-in which implements a
standard interface and which wraps the fine-grained complexity of the
fulfillment system API.
Resource Manager
The Resource Manager plug-in allows the Service Fulfillment Adapter to
perform Resource Manager API calls. An example of such a call is to
perform a network feasibility check to determine the optimal fulfillment
solution prior to design and implementation of a service.
Task Engine
The Task Engine plug-in automatically creates a Design Project based on
the Template specified in the configuration. It the starts and orchestrates the
Project flow, synchronously processing automatic Tasks for lights-out
operation and asynchronously handling manual Tasks, resuming the process
once manual Task processing has completed.
The plug-in returns the Design Project identifier which may be passed into
the Delivery Engine for implementation project processing.
The Task Engine plug-in supports rollback of Tasks to support order cancel
and amend requests.
Delivery Engine
The Delivery Engine plug-in automatically creates an Implementation
Project based on the Template specified in the configuration. Using the
Delivery Engine API, it then generates Jobs using the Design Records
attached to each of the Design Projects which are passed as input
parameters and then groups and optimizes the Jobs. Jobs can be auto-issued
or processed manually and the plug-in keeps track of the Job status
returning once the Project is complete.
Homepages
Service Fulfillment Orders 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.