I understand that I may unsubscribe from Nokia at any time. Know, now: Insights without boundaries What are the six trends that communication service providers CSPs need to know about now? Russia's MegaFon has deployed the Comarch Field Service Management system to minimize the cost of service downtime and significantly improve…. Mapcom Systems announced that Conterra Networks has begun the implementation of its M4 Solutions Suite to accelerate the service fulfillment….
The fulfillment process is realized on top of existing technological silos, which allows step by step transformation programs without the need for huge up-front investments. Improve time to market for convergent offers Quickly launch and deliver next-generation convergent offers including digital and content-augmented services regardless of the underlying technology, thanks to the ability to build services from pre-defined components managed in the service catalog. Increase business efficiency and cut costs Lower TCO as a result of automating the service fulfillment process.
Decrease the costs of service launch, delivery and provisioning thanks to service fulfillment automation. Quickly and easily integrate third-party service components, existing legacy systems and service infrastructure by using Comarch Service Inventory as an integration hub.
The Event Manager then publishes the event that the service order request completed successfully. It then creates a notification message with the error information and sends the message to the Notifications utility. The order remains open, but the status is changed to indicate that the order has been suspended.
The Service Fulfillment Manager process can not continue until the error is rectified. To continue processing, you must modify the order via the Notifications utility interface and re-submit the order to the Service Fulfillment Manager process where the error occurred.
Order Service Fulfillment Manager can fail during the Service Fulfillment Manager process due to invalid activation information, or perhaps the unavailability of a needed network element. Oracle Service Fulfillment Manager provides a number of ways to effectively manage the order fallout process through its Notifications utility.
Order fulfillment can fail during the Service Fulfillment Manager process due to the following factors:. Invalid orders: Orders that fail the order validation process may require escalation to the order entry or customer service groups.
In such cases, the Notifications utility serves as a tracking and notification mechanism. Fulfillment action problems: Fulfillment elements may not function properly, or be too busy, or unavailable, so the system rejects the service activation command. Time-outs on orders: The connection session between the application and the fulfillment elements may time-out due to either application or external errors.
Orders that have timed out may have been partially completed prior to the time-out. Network element or service configuration problems: The new service order may conflict with the current subscriber configuration. This may be the result of invalid orders. However, there may be other reasons, such as improper configuration of the customer.
You use the Notifications utility to track, monitor and resolve failed orders. Modify parameters in the failed order and re-send the order down to where the failure occurred, and then continue processing.
Re-send unchanged order down to where the failure occurred in the Service Fulfillment Manager process. Failure may have been due merely to network problems. Notifications are generated by various events and at various stages in the Service Fulfillment Manager process. Example events are:. The workflow produces two distinct types of notifications:.
The system generates these notifications if the Service Delivery Platform system detects a stopped fulfillment element manager process and starts it up automatically. Also, the system generates a notification if an internal problem occurs that requires a system administrator's attention. You use the Resubmission Utility to force the system to re-run an order on a particular fulfillment element. However, only those orders which have either completed, or have been previously submitted, on the fulfillment element in question, can be resubmitted.
This is useful, for example, in the event that a network switch fails or experiences a service disruption, causing a Service Fulfillment Manager order to fail. Through this utility, you specify a particular fulfillment element and the time window during which is was unavailable. After entering the required information, fulfillment elements re-execute the fulfillment actions as scheduled. A Job ID is generated and the progress of the re-submission can be tracked.
If there are no available adapters and the fulfillment element adapter maximum has not been reached, then an error message is generated. Re-submitted fulfillment actions can be identified in the Order Flowthrough window using the Resubmitted check-box. The Event Manager provides a set of APIs that are used by both internal and external systems to register for messages. Incoming messages are frequently a response to a previously initiated message from an external or internal system. Outgoing message are frequently user-defined notifications informing an external or internal system of an event occurrence.
External applications can send request messages to the Event Manager, if they are registered for that message. External applications can also register for response messages. The Event Manager identifies the subscriber and delivers an incoming message to the registered applications. The following sequence of steps is performed automatically. The Service Delivery Platform:. External systems can define their own processing logic at the time when validation and processing logic are defined.
If no application has registered for a message, the application uses the default processing logic after message validation. In Oracle Service Fulfillment Manager, a service order request is often queued in one of the many internal system queues between different stages in its processing.
As the Service Fulfillment Manager of an order progresses, the order moves sequentially through the various system queues as part of the fulfillment process. For example:. Incoming orders are moved to the Orders Pending queue if scheduled for later Service Fulfillment Manager.
The table following describes the queues in use in the Oracle Service Fulfillment Manager system. As an order moves through the system, it progresses from queue to queue in a sequential manner. Typically, this progression moves through the system queues in the following order.
The order stays in the pending queue until the date set for Service Fulfillment Manager. This date can be passed to the Service Delivery Platform as part of the order. If an order does not contain a Service Fulfillment Manager date, the default date becomes the current date and the order is moved immediately to the Order Ready queue.
The Order Ready queue holds orders that are ready to be provisioned immediately. The order is dequeued from the Order Ready queue and the work items generated by the work-plan are placed on the work item queue. The work item queue is used to manage the execution of work items. Determining if the work item is a regular Service Delivery Platform work item or a user-defined workflow. In the case of regular work items, the fulfillment actions are enqueued into the FA Queue in the sequence specified.
For user-defined workflows, the execution of the fulfillment actions is determined by the user-defined workflow. Note: At this point, the Service Delivery Platform does not know which fulfillment elements need to be provisioned.
The FA Queue is used to manage the execution of fulfillment actions for regular on user-defined work items. Checking the configuration to determine to which fulfillment element the fulfillment procedure must be sent. If an adapter is available, then it is immediately used to send the fulfillment element commands specified in the fulfillment procedure. If all adapters for the fulfillment element are busy or none are immediately available, the fulfillment action is put into the Wait for FE channel queue.
When an adapter becomes available, the fulfillment action waiting in the queue is moved to the FE Ready queue. This is a temporary holder for all fulfillment actions that are waiting for a free fulfillment element adapter. As an adapter becomes available, the fulfillment action is immediately dequeued and its fulfillment procedure executed.
The Queue Console provides a set of screens that display specialized information about each internal system queue. It can also be used to track down an order and to take corrective actions to expedite the order fulfillment process. Disabled: The processors are running, but an error condition has occurred. No order is being processed. The Queue Console displays information on the processes that are registered or running for a queue.
Processors Registered: The actual number of processors pulling or processing orders out of a queue. The Queue Console displays information the number and date of the entries in a queue.
A network adapter mediates the communication between Oracle Provisioning and the fulfillment elements. Messages to be sent and received are specified by the fulfillment element and the connection procedures executed by Oracle Provisioning workflow. The Service Fulfillment Manager workflow executes connect procedures for each new fulfillment element connection provided a procedure has been defined for the particular fulfillment element.
The following table lists the ways that adapters are used in the Service Delivery Platform, and describes each:. Only one fulfillment action or fulfillment procedure can be processed through an adapter execution. You pre-define a sequence of commands for the system to perform automatically during the course of the Service Fulfillment Manager process.
This is the most common method of issuing commands to the adapters. You issue adapter commands manually, also through the Connection Manager. However, while possible, this is not likely. You request command , or schedule a request, that an adapter perform one of the following operations:. This command stops the application from sending orders to be provisioned.
It places service orders in a queue until the fulfillment element becomes available. All service order requests that specify this adapter are stored in a job queue until the adapter is re-started. The Connection Manager sets any fulfillment element interfacing to this adapter to either Idle or Busy.
It sets the fulfillment element to Idle , if the job queue is empty for the adapter interfacing at the fulfillment element meaning that no service order requests awaiting Service Fulfillment Manager use this adapter. It set the fulfillment element to Busy , if there is a service order request in the Service Fulfillment Manager queue that uses the adapter interfacing to the fulfillment element. The application continues the Service Fulfillment Manager process, if service order requests are waiting in the job queue.
The next service order request marked for processing continues its Service Fulfillment Manager course. This command is used to close the appropriate connection. It stores the service activation order in a job queue until the connection to the fulfillment element is restored by issuing a connect request.
The Connection Manager places all service order requests that use this adapter into a queue until the adapter is re-connected. The current status of the adapter must be Suspended or Idle for this command to be available. This command is used to establish a connection to a fulfillment element so that is starts, or continues, its normal operation. Service order requests that are stored in a job queue re-start processing. If service order requests are waiting in the job queue, the next service order request due for processing continues its Service Fulfillment Manager course.
The status of the adapter is Busy. If the job queue is empty for that fulfillment element meaning no service order requests are awaiting Service Fulfillment Manager , the status of the adapter is set to Idle. If the Network Element Manager status is Error , then the connection could not be established to the Network Element, the connection procedure failed.
This command is used to close the connection to a fulfillment element by discontinuing adapter operation. Service order requests are stored in a job queue until a new adapter becomes available. The current status of the adapter can not be Shutdown or Reconnecting for this command to be available.
If the status is Busy , the shut down operation does not happen immediately. The application logs a Shutdown request that becomes active upon order completion. This command is used to start up a new adapter and establish a connection to a fulfillment element. If service order requests are waiting in the job queue, then the next service order request continues its Service Fulfillment Manager course. If the job queue is empty for that fulfillment element, then the status of the adapter is set to Idle.
There are three possible states to the Startup Mode:. Adapter operations are disabled unless the adapter mode is changed to either Automatic or Manual. This mode indicates the level of logging for the UNIX executable and the interactive adapter types.
You issue requests commands to the adapters and schedule adapter activities through the Connection Manager. Connect: Establish a connection to the fulfillment element and resume its normal operation. Disconnect: Close the appropriate connection and store the service activation order in a job queue until the connection to the fulfillment element is restored by issuing a connect request.
Start up: Start up a new adapter and establish a connection to the fulfillment element if any. Suspend: Stop Oracle Provisioning from sending any orders to be provisioned and have all service orders placed in a queue until the fulfillment element becomes available. Periodic: The adapter fulfills the request at periodic time intervals based on the supplied period. The Connection Manager provides the means to view, quickly modify, and manage the adapters connected to each fulfillment element.
Adapters maintain connectivity to each fulfillment element during service Service Fulfillment Manager. You can manage each connection for purposes such as load balancing, trouble shooting and maintenance. View the total number of service order requests awaiting activation in the queue for a selected fulfillment element. Note: Fulfillment element types are defined by system experts only. Fulfillment elements in Oracle Service Fulfillment Manager are grouped into logical categories.
A fulfillment element type can be any of the following:. Any service order request provisioned through Oracle Provisioning requires that the type for that specific fulfillment element be defined in the system before the fulfillment element itself is defined.
An attribute defines a property of a fulfillment element type. Attributes are also used to uniquely identify a fulfillment element. Each fulfillment element inherits its attributes from its fulfillment element type. The value of an attribute is the default value defined at the level of the fulfillment element. The attributes of an fulfillment element type defines its properties and behavior.
These include the following:. Note: It is possible to configure multiple software versions generics for each fulfillment element type, each with a specific effective date. Note: Setting a value for an attribute overwrites the default value of that attribute specified at the fulfillment element type level. Oracle Service Fulfillment Manager sets default values for the following attributes:. The adapter retries the command numerous times before it times- out. A failure message is returned and the default value is set to zero retry.
Waiting period in seconds before retrying commands within a fulfillment element. The default value is set to zero seconds. Some fulfillment elements may terminate the session, if there is no processing activity. The Service Delivery Platform allows you to set processing time to execute a command.
This allows the connection between an adapter and the fulfillment element to remain active. The default processing time is set to seconds. The Service Delivery Platform allows you to send commands to a fulfillment element to maintain the active sessions with the adapter.
Note: If you want an carriage return command to be sent, use " " as the attribute value. The default command is " ". Number of times the interactive adapter will try to reconnect automatically if the connection to the fulfillment element is dropped. The default value is zero. In the Oracle Service Delivery Platform, a fulfillment element is a unique physical entity. It has the following characteristics:. You must give each fulfillment element a unique name. This name is registered in the system during the configuration of the fulfillment element.
This helps to identify which particular Cisco router needs to be activated during Service Fulfillment Manager. When configuring a fulfillment element, consider the following:. Attributes assigned to a fulfillment element type are inherited by the newly configured fulfillment element. In Oracle Service Fulfillment Manager, a service is a telecommunication-related product, offered to the customer as an individual item or in bundles.
It is possible to define more than one version of a service in Oracle Service Fulfillment Manager. However, only one version of the service is available to a given customer at one time.
Services provided by the carrier are fulfilled by a set of work items performed in a specific sequence within Oracle Provisioning. A work item, then, is a unit of work which is necessary to fulfil a service action.
You assign to a work item the appropriate parameters, fulfillment actions and fulfillment procedures necessary for the Service Fulfillment Manager process. Fulfillment actions are responsible for the actual Service Fulfillment Manager of services at the fulfillment element level.
As an alternative to work items, users can execute the fulfillment actions conditionally in a user-defined workflow. The workflow is defined according to pre-set conditions in a service order request. The available work item types are:. Static: The list of fulfillment actions and their sequence are defined prior to runtime and do not change. Dynamic: The list of fulfillment actions and their sequence are determined at runtime by executing a shared procedure. User-defined workflow: The list of fulfillment actions and their sequence are determined at runtime by a predefined workflow that executes multiple procedures based on some pre-defined conditions.
Oracle Service Fulfillment Manager comes preseeded with a number of rules for adding, deleting, and modifying work items.
0コメント