Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method to Combine Separate System's Supply Planning Information into a Single Consolidated view for Processing.

IP.com Disclosure Number: IPCOM000028203D
Original Publication Date: 2004-May-03
Included in the Prior Art Database: 2004-May-03
Document File: 3 page(s) / 66K

Publishing Venue

IBM

Abstract

To support Fulfillment processes globally, multiple fulfillment systems needed to be run concurrently. To reduce expenses, a decision was made to consolidate fulfillment into a single instance. However, only new activity would be run through the consolidated instance; whereas, existing activity remained in the separate legacy systems. In order to support both a single instance with current data, and multiple instances with pre-existing data, a method had to be introduced that would allow for a consolidated view of the information for users and external systems. Supply Planning data is created in multiple scheduling systems which need to be consolidated for further processing. To accomplish this, there is a single master system which creates the consolidated file. The subordinate systems will process then push completed data to a shared directory. Once the data is passed to the shared directory, the subordinate systems record their completion status. The master system reads the completion status and pulls the data from the shared directory, then consolidates for extraction by external system. The data is supply planning information. It is used by external planning systems. It is also can be stored in Information Warehouses for reporting purposes. Advantages. 1. Reduced cost of system consolidation. 2. Reduced risk to revenue and customer impacts based on the need to only focus on a single point of data; the supply planning data. 3. Low development cost. 4. Flexibility to continue to utilize the subordinate systems for handling the remaining processing as long as required. 5. Ease of migration to the single instance. Only new data was entered in the single system.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Method to Combine Separate System's Supply Planning Information into a Single Consolidated view for Processing.

    To support Fulfillment processes globally, multiple fulfillment systems needed to be run concurrently. To reduce expenses, a decision was made to consolidate fulfillment into a single instance. However, only new activity would be run through the consolidated instance; whereas, existing activity remained in the separate legacy systems. In order to support both a single instance with current data, and multiple instances with pre-existing data, a method had to be introduced that would allow for a consolidated view of the information for users and external systems.

    The other known methods did not allow for the continued running of multiple systems as consolidation into a single instance occurred. These methods supported a 'big-bang' approach to migration. All in-process activity would have to be migrated to the single instance. This proved to be both risky and costly. The risk was a negative impact on the revenue flow to the corporation, as well as customer satisfaction (loss of data, improper migration of data). The cost involved purchase and support of additional costly software, which would be utilized only once. Because the decision was made to focus on the Supply Planning Data to support running multiple systems concurrently, the overall risk and cost of the project was greatly reduced from other alternatives.

The invention was implemented in the following manner. Changed program in subordinate system(s); a new program, and a new function module in master system.

  1. Modify program in subordinate system(s) to prevent use of the system's data by the external system.

  The external system can be either a demand/supply planning system, or a business data warehouse.

  (I.e., prevents the automatic extraction and routing of the data to the external system.)

  2. Modify program in subordinate system(s) to write the extract information to the shared directory on the
master system. (Note, in an env...