Managing plan problems across planning cycles
View Patent ↗A method for managing plan problems across planning cycles includes accessing a first plan generated in a first planning session of a first planning cycle, identifying one or more first plan problems reflected in the first plan, and storing and persisting plan problem data associated with the one or more first plan problems for access in one or more successive planning cycles. The method includes accessing a second plan generated in a second planning session of a second planning cycle subsequent to the first planning cycle, identifying one or more second plan problems reflected in the second plan, and comparing the one or more first plan problems identified for the first planning cycle with the one or more second plan problems identified for the second planning cycle. The method includes determining whether the second plan problem corresponds to any first plan problem identified for the first planning cycle.
1. A system, comprising:
a computer, comprising a processor and a memory, the computer configured to:
access execution data of an execution system, the execution data describing conditions within an execution domain;
detect whether the execution data exceeds a predetermined plan problem threshold;
when the execution data exceeds the predetermined plan problem threshold, create one or more plan problem records based, at least in part, on the execution data;
store the plan problem records from the execution data at a location accessible to both a planning domain and the execution domain until at least one successive planning cycle;
determine a root cause of one or more plan problems associated with the one or more plan problem records; and
store root cause data at the location accessible to both the planning domain and the execution domain until the at least one successive planning cycle, the root cause data identifying one or more plan problems according to the determined root cause.
2. The system of claim 1 , wherein the computer is further configured to:
detect whether a magnitude of a change between the one or more plan problem records and a plan problem record from the at least one successive planning cycle exceeds a predetermined plan problem record threshold; and
when the magnitude of the change exceeds the predetermined plan problem record threshold, update the plan problem record.
3. The system of claim 1 , wherein the computer is further configured to:
identify a constraint causing the execution data to exceed the predetermined plan problem threshold by comparing the one or more plan problem records and a plan problem record from the at least one successive planning cycle, wherein the at least one successive planning cycle comprises generating an unconstrained plan.
4. The system of claim 1 , wherein the execution system comprises at least one of the following:
a manufacturing execution system;
an enterprise resource planning system;
an order management system; and
an accounting system.
5. The system of claim 1 , wherein the execution data comprises at least one of the following:
a status of a demand of an item; and
an availability of resources needed to meet the demand of the item.
6. The system of claim 5 , wherein the root cause data comprises a constraint quantity and an identification of the item.
7. The system of claim 6 , wherein the item is lated or shorted.
8. A computer-implemented method, comprising:
accessing execution data of an execution system, the execution data describing conditions within an execution domain;
detecting whether the execution data exceeds a predetermined plan problem threshold;
when the execution data exceeds the predetermined plan problem threshold, creating one or more plan problem records based, at least in part, on the execution data;
storing the plan problem records from the execution data at a location accessible to both a planning domain and the execution domain until at least one successive planning cycle;
determining a root cause of one or more plan problems associated with the one or more plan problem records; and
storing root cause data at the location accessible to both the planning domain and the execution domain until the at least one successive planning cycle, the root cause data identifying one or more plan problems according to the determined root cause.
9. The computer-implemented method of claim 8 , further comprising:
detecting whether a magnitude of a change between the one or more plan problem records and a plan problem record from the at least one successive planning cycle exceeds a predetermined plan problem record threshold; and
when the magnitude of the change exceeds the predetermined plan problem record threshold, updating the plan problem record.
10. The computer-implemented method of claim 8 , further comprising:
identifying a constraint causing the execution data to exceed the predetermined plan problem threshold by comparing the one or more plan problem records and a plan problem record from the at least one successive planning cycle, wherein the at least one successive planning cycle comprises generating an unconstrained plan.
11. The computer-implemented method of claim 8 , wherein the execution system comprises at least one of the following:
a manufacturing execution system;
an enterprise resource planning system;
an order management system; and
an accounting system.
12. The computer-implemented method of claim 8 , wherein the execution data comprises at least one of the following:
a status of a demand of an item; and
an availability of resources needed to meet the demand of the item.
13. The computer-implemented method of claim 12 , wherein the root cause data comprises a constraint quantity and an identification of the item.
14. The computer-implemented method of claim 13 , wherein the item is lated or shorted.
15. A non-transitory computer-readable medium embodied with software, the software when executed:
accesses execution data of an execution system, the execution data describing conditions within an execution domain;
detects whether the execution data exceeds a predetermined plan problem threshold;
when the execution data exceeds the predetermined plan problem threshold, creates one or more plan problem records based, at least in part, on the execution data;
stores the plan problem records from the execution data at a location accessible to both a planning domain and the execution domain until at least one successive planning cycle;
determines a root cause of one or more plan problems associated with the one or more plan problem records; and
stores root cause data at the location accessible to both the planning domain and the execution domain until the at least one successive planning cycle, the root cause data identifying one or more plan problems according to the determined root cause.
16. The non-transitory computer-readable medium of claim 15 , wherein the software when executed further:
detects whether a magnitude of a change between the one or more plan problem records and a plan problem record from the at least one successive planning cycle exceeds a predetermined plan problem record threshold; and
when the magnitude of the change exceeds the predetermined plan problem record threshold, updates the plan problem record.
17. The non-transitory computer-readable medium of claim 15 , wherein the software when executed further:
identifies a constraint causing the execution data to exceed the predetermined plan problem threshold by comparing the one or more plan problem records and a plan problem record from the at least one successive planning cycle, wherein the at least one successive planning cycle comprises generating an unconstrained plan.
18. The non-transitory computer-readable medium of claim 15 , wherein the execution system comprises at least one of the following:
a manufacturing execution system;
an enterprise resource planning system;
an order management system; and
an accounting system.
19. The non-transitory computer-readable medium of claim 18 , wherein the execution data comprises at least one of the following:
a status of a demand of an item; and
an availability of resources needed to meet the demand of the item.
20. The non-transitory computer-readable medium of claim 19 , wherein the root cause data comprises a constraint quantity and an identification of the item.