Browse Prior Art Database

On Demand Fulfillment of Ordered Components Requiring Conditional Routing of Order Approvals/Rejections

IP.com Disclosure Number: IPCOM000031209D
Original Publication Date: 2004-Sep-17
Included in the Prior Art Database: 2004-Sep-17
Document File: 2 page(s) / 47K

Publishing Venue

IBM

Abstract

A method is described for differential routing of on-demand requests for upgrade components as part of an IT migration project. The method utilizes routing tables that are based on a set of criteria such as department or division and that allow an employee's request to be either rejected automatically, sent to the manager for approval, or if required, sent to a second level for approval.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

On Demand Fulfillment of Ordered Components Requiring Conditional Routing of Order Approvals/Rejections

During an IT migration project that requires distribution of workstation upgrade components to employees, such as Ethernet components, some individuals might need to acquire their components outside of the normally scheduled process. Because of the cost associated with the components, an approval may be required. A process didn't exist whereby:

Some requests could automatically be routed through two levels of approval for designated employee groups
Some requests could automatically be rejected for designated employee groups Some requests could automatically be routed to the employee's manager for approval

In order to allow employee On Demand requests for hardware upgrade components to be processed/approved correctly, a set of routing tables was created. The routing tables, based on a set of criteria such as department or division, would allow an employee's request to be either rejected automatically, sent to the manager for approval, or if required, sent to a second level for approval. By using the routing tables, a project member didn't have to review each request and determine who would need to approve the request. The use of routing tables also cut down the time to approve requests and reduced the number of errors.

For I/T migration projects which involve the distribution of hardware upgrade components, management approval is usually a requirement because of the costs involved. Also, because some user groups might have financial constraints, the approval process of one user group might be different than other user groups. To handle these requirements, a set of routing tables may be created to customize the routing of an individual's request. The routing table can use requestor profile information such as the employee's department or division to determine how the request should be handled. As the request comes into the processing function, the application can take the employee's division/department and look for a corresponding entry in the routing table. The routing table can specify if the employee's request should automatically be rejected for cases where the user group has no funding for this type of request requires multiple levels of approval and how to route the request should take the default process of having one level of management approval

As part of the corporate token ring to Ethernet migration, this process was put to use. The Adapter By Exception (ABE) process was...