Method and system for master planning priority assignment

• US 6,981,003 B2
• Filed: 08/03/2001
• Issued: 12/27/2005
• Est. Priority Date: 08/03/2001
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ervolina, Thomas Robert, Harrod, Darrell Lavern, Bundy, Michael Lee, Pauliks, Michael Georg, MacKay, Grant Lindsey, Kanuch, James, Santo, Sarah Elizabeth, Kotecki, Amanda
• Primary Examiner(s): Alam, Shahid
• Assistant Examiner(s): TRUONG, CAM Y T
• Application Number:
  US09/922,058
• Publication Number:
  US 20030028507A1
• Time in Patent Office: 1,607 Days
• Field of Search: 707/1, 707/3, 707/10, 707/6, 707/200, 705/14, 705/27, 705/5, 705/26, 705/1, 705/10, 706/47
• US Class Current: 707/769
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99936 Pattern matching access

Abstract

A method and system for performing master planning priority assignment is presented. The method includes assigning a priority to a demand record that contains at least one demand attribute and a priority field. The assignment includes identifying a database that contains priority assignment rules for demand records and then querying the rule database to find the database record that corresponds to the particular demand record. The corresponding database record is found by matching the data in the attribute fields in the rule database and the demand record. The priority associated with the matching priority database record is assigned to the demand record. Additional embodiments include a system and storage medium for performing master planning priority assignment.

Claims

1. A computer-implemented method for performing master planning priority assignment, the method comprising:

creating at least one rule database that includes fields for specifying attributes relating to customer demand files and related priorities;

assigning a priority to a demand record, said demand record containing a demand record attribute field and a demand record priority field;

said assigning including;

selecting said at least one rule database, said at least one rule database including at least one record, a rule database attribute field that correlates to said demand record attribute field, and a rule database priority field;

querying said at least one rule database for a corresponding rule database record that contains data in said rule database attribute field that matches data in said demand record attribute field, said matching comprising;

querying said at least one rule database for an explicit data match;

if no said explicit data match exists, querying said at least one rule database for a hierarchy value match; and

if no said explicit data match or said hierarchy value data match exists, querying said at least one rule database for a wildcard match; and

based upon said querying, updating data in said demand record priority field with data from said corresponding rule database priority field.

2. The method of claim 1 wherein said data in said corresponding rule database attribute field contains an explicit value operable for specifying a priority to be given to a demand record;

wherein said match occurs if said data in said demand record attribute field is contained within said explicit value.

3. The method of claim 1 wherein said data in said corresponding rule database attribute field contains a hierarchy value operable for specifying a priority to be given to a hierarchy level defined with said rule database attribute field;

wherein said match occurs if said data in said demand record attribute field is contained within said hierarchy value.

4. The method of claim 3 further comprising creating said hierarchy value, said hierarchy value containing a hierarchy level.

5. The method of claim 3 further comprising creating said hierarchy value, said hierarchy value containing said explicit value.

6. The method of claim 1 wherein said data in said corresponding rule database attribute field contains a wildcard value operable for specifying a default priority value to said rule database attribute field;

wherein said data in said demand record attribute field is not used in said matching.

7. The method of claim 1 wherein said demand record attribute field includes due date, customer, and demand type.

8. The method of claim 1 further comprising updating said at least one record in said at least one rule database.

9. A computer-implemented method for master planning priority assignment, the method comprising:

creating at least one rule database;

assigning a priority to a demand record, said demand record containing a demand record attribute field and a demand record priority field, the demand record attribute field includes at least one of a due date, customer, and demand type, said assigning including;

selecting said at least one rule database, said at least one rule database including at least one record, a rule database attribute field that correlates to said demand record attribute field, and a rule database priority field;

querying said at least one rule database for a corresponding rule database record that contains data in said rule database attribute field that matches data in said demand record attribute field, said matching comprising;

querying said at least one rule database for an explicit data match;

if no said explicit data match exists, querying said at least one rule database for a hierarchy value match; and

;

if no said explicit data match or said hierarchy value data match exists, querying said at least one rule database for a wildcard match; and

based upon said querying, updating data in said demand record priority field with data from said corresponding rule database priority field.

10. A system for performing master planning priority assignment, the system comprising:

a storage device storing master planning priority assignment data;

a user system; and

a host system in communication with said storage device and said user system, said host system implementing a process comprising;

creating at least one rule database;

assigning a priority to a demand record, said demand record containing a demand record attribute field and a demand record priority field;

said assigning including;

selecting said at least one rule database, said at least one rule database including at least one record, a rule database attribute field that correlates to said demand record attribute field, and a rule database priority field;

querying said at least one rule database for a corresponding rule database record that contains data in said rule database attribute field that matches data in said demand record attribute field, said matching comprising;

querying said at least one rule database for an explicit data match;

if no said explicit data match exists, querying said at least one rule database for a hierarchy value match; and

if no said explicit data match or said hierarchy value data match exists, querying said at least one rule database for a wildcard match; and

based upon said querying, updating data in said demand record priority field with data from said corresponding rule database priority field.

11. The system of claim 10 wherein said wherein said data in said corresponding rule database attribute field contains an explicit value operable for specifying a priority to be given to a demand record;

wherein said match occurs if said data in said demand record attribute field is contained within said explicit value.

12. The system of claim 10 wherein said data in said corresponding rule database attribute field contains a hierarchy value operable for specifying a priority to be given to a hierarchy level defined within said rule database attribute field;

wherein said match occurs if said data in said demand record attribute field is contained within said hierarchy value.

13. The system of claim 12 wherein said host system implementing a process further comprises creating said hierarchy value, said hierarchy value containing a hierarchy level.

14. The system of claim 12 wherein said host system implementing a process further comprises creating said hierarchy value, said hierarchy value containing said explicit value.

15. The system of claim 10 wherein said data in said corresponding rule database attribute field contains a wildcard value operable for specifying a default priority value to said rule database attribute field;

wherein said data in said demand record attribute field is not used in said matching.

16. The system of claim 10 wherein said demand record attribute field includes due date, customer, and demand type.

17. The system of claim 10 wherein said host system implementing a process further comprises updating said at least one record in said at least one rule database.

18. The system of claim 10 further comprising a network providing communication between the host system and the user system.

19. The system of claim 10 further comprising a network providing communication between the storage device and the host system.

20. A system for performing master planning priority assignment, the system comprising:

at least one rule database that includes fields for specifying attributes relating to customer demand files and related priorities;

a storage device storing master planning priority assignment data associated with said at least one rule database;

a user system; and

a host system in communication with said storage device and said user system, said host system implementing a process comprising;

creating said at least one rule database;

assigning a priority to a demand record, said demand record containing a demand record attribute field and a demand record priority field, the demand record attribute field includes at least one of a due date, customer, and demand type, said assigning including;

selecting said at least one rule database, said at least one rule database including at least one record, a rule database attribute field that correlates to said demand record attribute field, and a rule database priority field;

querying said at least one rule database for a corresponding rule database record that contains data in said rule database attribute field that matches data in said demand record attribute field, said matching comprising;

querying said at least one rule database for an explicit data match;

if no said explicit data match exists, querying said at least one rule database for a hierarchy value match; and

if no said explicit data match or said hierarchy value data match exists, querying said at least one rule database for a wildcard match; and

based upon said querying, updating data in said demand record priority field with data from said corresponding rule database priority field.

21. A storage medium encoded with machine-readable computer program code for performing master planning priority assignment, the storage medium storing instructions for causing a host system to implement a method comprising:

creating at least one rule database that includes fields for specifying attributes relating to customer demand files and related priorities;

assigning a priority to a demand record, said demand record containing a demand record attribute field and a demand record priority field;

said assigning including;

selecting said at least one rule database, said at least one rule database including at least one record, a rule database attribute field that correlates to said demand record attribute field, and a rule database priority field;

querying said at least one rule database for a corresponding rule database record that contains data in said rule database attribute field that matches data in said demand record attribute field, said matching comprising;

querying said at least one rule database for an explicit data match;

if no said explicit data match exists, querying said at least one rule database for a hierarchy value match; and

if no said explicit data match or said hierarchy value data match exists, querying said at least one rule database for a wildcard match; and

based upon said querying, updating data in said demand record priority field with data from said corresponding rule database priority field.

22. The storage medium of claim 21 wherein said data in said corresponding rule database attribute field contains an explicit value operable for specifying a priority to be given to a demand record;

wherein said match occurs if said data in said demand record attribute field is contained within said explicit value.

23. The storage medium of claim 21 wherein said data in said corresponding rule database attribute field contains a hierarchy value operable for specifying a priority to be given to a hierarchy level defined within said rule database attribute field;

wherein said match occurs if said data in said demand record attribute field is contained within said hierarchy value.

24. The storage medium of claim 23 further comprising creating said hierarchy value, said hierarchy value containing a hierarchy level.

25. The storage medium of claim 23 further comprising creating said hierarchy value, said hierarchy value containing an explicit value.

26. The storage medium of claim 21 wherein said data in said corresponding rule database attribute field contains a wildcard value operable for specifying a default priority value to said rule database attribute field;

wherein said data in said demand record attribute field is not used in said matching.

27. The storage medium of claim 21 wherein said demand record attribute field includes due date, customer, and demand type.

28. The storage medium of claim 21 further comprising updating said at least one record in said at least one rule database.

29. A storage medium encoded with machine-readable computer program code for performing master planning priority assignment, the storage medium storing instructions for causing a host system to implement a method comprising:

creating at least one rule database;

assigning a priority to a demand record, said demand record containing a demand record attribute field and a demand record priority field, the demand record attribute field includes at least one of a due date, customer, and demand type, said assigning including;

selecting said at least one rule database, said at least one rule database including at least one record, a rule database attribute field that correlates to said demand record attribute field, and a rule database priority field;

querying said at least one rule database for a corresponding rule database record that contains data in said rule database attribute field that matches data in said demand record attribute field, said matching comprising;

querying said at least one rule database for an explicit data match;

if no said explicit data match exists, querying said at least one rule database for a hierarchy value match; and

;

if no said explicit data match or said hierarchy value data match exists, querying said at least one rule database for a wildcard match; and

based upon said querying, updating data in said demand record priority field with data from said corresponding rule database priority field.