Method and apparatus for reporting the status of work in progress

• US 20030074377A1
• Filed: 12/22/2000
• Published: 04/17/2003
• Est. Priority Date: 12/22/2000
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Maheshwari, Amit, Yenerich, James A., Gupta, Aman
• Application Number:
  US09/747,647
• Publication Number:
  US 20030074377A1
• Time in Patent Office: Days
• US Class Current: 707/203
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

A system and method are disclosed for electronically reporting in real-time the status of work in progress by a computerized system. The invention provides alert notification when a customer requested shipment date falls before the date that a shipment was promised or is scheduled to be fulfilled. The invention further includes notification when the request date for shipment is near, thereby providing a highlighted alert notification to managers. The system is designed to update its data when a request is made, or automatically in real-time or on a regular basis. A proactive alert is provided to alert managers of a correctable problem for that order and a reactive alert is provided to track late shipments to prevent future late shipments.

Claims

1. A method for reporting status of work in progress, comprising the steps of:

periodically querying a database that contains data indicating an order number, a promise date, a request date, a shipment date, and a product category for a plurality of products/services offered;

comparing the promise dates and the request dates;

setting a proactive promise alert if a promise date is later than a request date for a given order; and

displaying the proactive promise alerts with the order number by product category and type of alert.

2. The method of claim 1 further comprising the steps of:

setting a reactive shipment alert if the shipment date exists and the request date is less than a user-defined number of days prior to a current date; and

displaying any reactive shipment alerts with the order number together with the proactive promise alerts.

3. The method of claim 2 wherein the user-defined number of days is equivalent to a number of days required for shipping a product to a customer.

4. The method of claim 1 wherein the querying of the database is conducted automatically at regular time intervals.

5. The method of claim 1 wherein the steps of the method are repeated automatically in real time.

6. The method of claim 1 further comprising repeating the steps of the method every time a request for information is made.

7. The method of claim 2 wherein the proactive promise alert allows for correction of a potential late shipment and the reactive shipment alert provides data to prevent future late shipments.

8. The method of claim 1 further comprising the steps of reacting to a proactive alert by performing one of:

modifying the promise date to coincide with the request date; and

notifying a customer that the request date cannot be fulfilled as desired.

9. A computer-readable medium having stored thereon one or more computer programs that, when executed by one or more computers, causes the one or more computers to:

populate a database with data to include an order number, a promise date, a request date, a shipment date, and a product category for a plurality of orders;

periodically query the database and compare promise dates to request dates;

set a proactive alert if the promise date is later than a request date;

set a reactive alert if the shipment date exists and the request date is less than a user-defined number of days prior to a current date; and

display any promise and shipment alerts by product category and type of alert.

10. The computer-readable medium of claim 9 wherein the user-defined number of days is equivalent to a number of days required for shipping a product to a customer or providing a service to a customer.

11. The computer-readable medium of claim 9 wherein the query of the database is conducted automatically at regular time intervals.

13. The computer-readable medium of claim 9 wherein the one or more computer programs cause the one or more computers to repeat the actions of claim 9 every time a request for information is made.

14. The computer-readable medium of claim 11 wherein the regular time interval is between 0 and 60 seconds.

15. The computer-readable medium of claim 11 wherein the regular time interval is greater than 1 minute.

17. The computer data signal of claim 15 wherein the user-defined number of days is equivalent to a number of days required for shipping a product/service to a customer.

18. The computer data signal of claim 15 wherein the query of the database is conducted automatically at regular time intervals.

19. The computer data signal of claim 15 wherein the computer data signal causes the one or more processors to repeat the actions of claim 15 every time a request for information is made.

20. The computer data signal of claim 17 wherein the regular time interval is between 0 and 60 seconds.

21. The computer data signal of claim 17 wherein the regular time interval is greater than 1 minute.

22. The computer data signal of claim 15 wherein the computer data signal causes the one or more processors to allow user modification of the promise date to coincide with the request date in response to the proactive alert if the product/service is available by the request date.

16. A computer data signal representing a sequence of instructions that, when executed by one of more processors, cause the one or more processors to:

populate a database with an order date indicating a date an order is initially made, a request date indicating a date when a customer requests delivery of the order, a shipment date, when available, indicating a date when actual shipment will occur and a product/service category for each order for a product/service;

query the database and compare promise dates to request dates for each order and check for the entry of a shipment date for each order;

set a proactive alert if any promise date is later than a request date;

set a reactive alert if a shipment date exists for an order and the request date is less than a user-defined number of days prior to a current date; and

display all proactive and reactive alerts by product/service category and type of alert.