SYSTEM AND METHOD FOR CONTINUOUSLY PLANNING MAINTENANCE OF ENTERPRISE EQUIPMENT

• US 20160132804A1
• Filed: 11/07/2014
• Published: 05/12/2016
• Est. Priority Date: 11/07/2014
• Status: Abandoned Application

• Current Assignee: Copperleaf Technologies Inc.
• Original Assignee: Copperleaf Technologies Inc.
• Inventors: CROFT, Lawrence, HORNER, Simon Nesbitt, GNOCATO, Giuseppe, COLEMAN, Stanley Thomas
• Application Number:
  US14/536,585
• Publication Number:
  US 20160132804A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/06313 Resource planning in a project environment
• CPC Class Codes: Y02P 90/80 Management or planning

Abstract

Systems and methods for continuously planning maintenance of enterprise equipment are provided. Draft forecasts relating to projects in an infrastructure are generated by a computer system. A first user (U1) selects a draft forecast and submits it for approval. The computer system adds the submitted forecast to a submitted scenario. A second user (U2) approves or rejects the submitted forecast for inclusion in a master scenario. The second user may modify the submitted forecast. The system permits continuous planning of projects to maintain an enterprise infrastructure.

Claims

1. A method for planning projects for maintaining an infrastructure, the method implemented by a computer system and comprising:

a. receiving a plurality of submissions of new versions of project forecasts, each of the project forecasts associated with a project to replace, upgrade and/or refurbish an infrastructure component, the submissions initiated by one or more first users of the computer system;

b. presenting a user interface that provides a second user with options including;

rejecting the new version of the project forecast and accepting the new version of the project forecast for each of the submitted new versions;

c. incorporating the accepted new versions into a master scenario.

2. The method according to claim 1 comprising, for one or more of the submitted new versions, determining that one or more modifications have been applied to a corresponding current version of the project forecast in the master scenario and, for the one or more of the submitted new versions, providing the second user with the option to incorporate the new project forecast as modified by the one or more modifications in the master scenario in place of the current version of the project forecast.

3. The method according to claim 1 comprising receiving from the second user a modification to one of the accepted new versions, applying the modification to the one of the accepted new versions in the master scenario and automatically notifying the first user of the modification.

4. The method according to claim 1 comprising automatically updating a submitted scenario to include the submitted new versions in place of corresponding current versions of the project forecasts.

5. The method according to claim 4 comprising displaying a comparison of the submitted scenario and the master scenario.

6. The method according to claim 5 wherein the same version of one or more project forecasts are present in both the master scenario and the submitted scenario, the computer system comprises a single copy of the same version, and the submitted scenario and the master scenario each comprise a pointer to the single copy of the same version.

7. The method according to claim 1 comprising automatically notifying the second user on receipt of the submitted new versions.

8. The method according to claim 1 comprising storing a copy of the master scenario as a budget scenario and locking the budget scenario against changes.

9. The method according to claim 1 comprising by the computer system performing an optimization on the master scenario, the optimization yielding modifications to one or more of the project forecasts in the master scenario.

10. The method according to claim 9 comprising automatically notifying the one or more first users of the computer system about any of the modifications applied to project forecasts submitted by the one or more first users of the computer system.

11. The method according to claim 1 wherein one of the plurality of new versions includes a plurality of alternatives, each of the plurality of alternatives specifying a different action to perform on the corresponding infrastructure component, the one of the new versions having a first one of the alternatives selected as an active alternative.

12. The method according to claim 11 comprising receiving from the second user and applying a modification to the one of the plurality of new versions in the master scenario, the modification comprising selecting a second one of the alternatives different from the first one of the alternatives as the active alternative.

13. A method for planning projects for maintaining an infrastructure, the method implemented by a computer system and comprising:

a. receiving submission initiated by a first user of a new version of a project forecast associated with a project to replace, upgrade and/or refurbish an infrastructure component;

b. determining that one or more modifications have been applied to a current version of the project forecast in a master scenario;

c. In response to input from a second user, applying the one or more modifications to the new project forecast and incorporating the new project forecast as modified by the one or more modifications in the master scenario in place of the current version of the project forecast.

14. The method according to claim 13 comprising automatically notifying the second user on receipt of the new version of the project forecast.

15. The method according to claim 13 comprising automatically including the new version of the project forecast in a submitted scenario distinct from the master scenario.

16. The method according to claim 13 comprising storing a copy of the master scenario as a budget scenario.

17. The method according to claim 13 comprising automatically creating in a project management system a project corresponding to the new version of the project forecast.

18. The method according to claim 13 comprising automatically notifying a plurality of users of the received submission.

19. The method according to claim 13 comprising receiving by way of the computer system comments relating to the new version of the project forecast and associating the comments with the new version of the project forecast.

20. The method according to claim 13 comprising presenting a user interface that provides the second user with options including:

rejecting the new version of the project forecast, accepting the new version of the project forecast without modification, and accepting the new version of the project forecast as modified by the one or more modifications.

21. The method according to claim 13 further comprising applying an optimization to the master scenario, the optimization yielding a further modification to the new version of the project forecast, and applying the further modification to the new version of the project forecast.

22. A system useful for planning projects for maintaining an infrastructure, the system comprising a plurality of first user environments in data communication with a database, the database storing records corresponding to each of a plurality of project forecasts, the project forecasts each specifying a project to replace, upgrade and/or refurbish an infrastructure component, the database comprising associations grouping project forecasts into scenarios, the scenarios including at least a master scenario;

a. Each of the first user environments comprising a data processor configured to generate submissions of new versions of the project forecasts;

b. An approval system connected to receive the submissions, the approval system presenting a user interface that provides a second user with options for processing the submissions including;

rejecting the new version of the project forecast and accepting the new version of the project forecast for each of the submitted new versions, the approval system configured to incorporate accepted ones of the new versions into the master scenario.

23. The system according to claim 22 comprising a master scenario editor providing tools for the second user to modify the project forecasts in the master scenario.

24. The system according to claim 22 wherein the scenarios comprise a submitted scenario that is automatically updated by the system to contain a most-recently-submitted version of each one of the project forecasts.

25. The system according to claim 23 comprising a display displaying a comparison of the submitted scenario and the master scenario.