SYSTEM AND METHOD FOR MANAGING MANUFACTURING INFORMATION

Information

  • Patent Application
  • 20070192128
  • Publication Number
    20070192128
  • Date Filed
    February 16, 2007
    18 years ago
  • Date Published
    August 16, 2007
    17 years ago
Abstract
A system for managing data within an organization that is intended to provide tactical and/or role-based data. The system includes a data acquisition module, a data processing module and an output module. The data acquisition module acquires operational data and financial data related to the operational data. The data processing module is configured to: analyze the operational data to identify a variance in the operational data; determine a financial impact of the variance based on the financial data; generate an event based on the variance in the operational data; and prioritize the event based on the financial impact. The output module then outputs the event, preferably in accordance with priority. In a particular case, the event may also be categorized as relating to a particular role with the organization.
Description

BRIEF DESCRIPTION OF THE FIGURES

For a better understanding of the exemplary embodiments, and to show more clearly how they may be carried into effect, reference will now be made, by way of example, to the accompanying drawings which aid in understanding and in which:



FIG. 1 is a block diagram of a system according to an embodiment;



FIG. 2 is a tree diagram illustrating an exemplary data structure in accordance with an embodiment;



FIG. 3 is a tree diagram illustrating an exemplary data structure similar to that of FIG. 2 together with exemplary data stored by each node;



FIG. 4 is a block diagram showing exemplary modules of management software for the system of FIG. 1;



FIG. 5 is a block diagram of the hardware components of an MMD;



FIG. 6 is a logical flow diagram of the software modules of the MMD.



FIG. 7 is a flowchart of a method for operating the MMD.



FIG. 8 is a flowchart of the configuration step of FIG. 7.



FIG. 9 is a flowchart of the monitoring step of FIG. 7.



FIG. 10 is a flowchart of the reporting step of FIG. 7 for automated reports.



FIG. 11 is a flowchart of the reporting step of FIG. 7 for user requested web page reports.



FIG. 12 illustrates an exemplary user-interface for reports;



FIG. 13 illustrates an exemplary inventory report;



FIG. 14 illustrates an exemplary role-based user interface;



FIG. 15 illustrates exemplary rules used by a rules processing module;



FIG. 16 illustrates exemplary events listed as a hot list;



FIG. 17 illustrates two machines operating at different levels of efficiency with assigned jobs of differing value;



FIG. 18 is a flowchart illustrating a method by which management software collects and stores data;



FIG. 19 is a flowchart illustrating a method by which the management software processes data into tactical role specific information;



FIG. 20 is a flowchart illustrating a method by which the management software outputs information on the user interface.


Claims
  • 1. A system for managing data within an organization, the system comprising: a data acquisition module for acquiring: operational data; andfinancial data related to the operational data;a data processing module configured to: analyze the operational data to identify a variance in the operational data;determine a financial impact of the variance based on the financial data;generate an event based on the variance in the operational data; andprioritize the event based on the financial impact; andan output module for outputting the event.
  • 2. A system according to claim 1, wherein the financial data is data relating to opportunity costs.
  • 3. A system according to claim 1, wherein the financial data is data relating to margins.
  • 4. A system according to claim 1, wherein the financial impact is determined by applying the financial data to the operational data and calculating a value attributable to the variance in the operational data.
  • 5. A system according to claim 1, wherein the data acquisition module acquires financial data for a task at the time the task is scheduled.
  • 6. A system according to claim 1, wherein the output module outputs the event in accordance with the prioritization.
  • 7. A system according to claim 1, wherein the operational data is real-time operational data and the data processing module operates on the real-time operational data.
  • 8. A system according to claim 1, wherein the data processing module is further configured to categorize the event as relating to a role within the organization.
  • 9. A system according to claim 1, wherein the data processing module comprises a rules processing module for applying rules to the operational data and financial data to identify the variances and to determine the financial impact.
  • 10. A system according to claim 9, further comprising a configuration module for entry of the rules.
  • 11. A system according to claim 9, wherein the rules comprise information relating to roles within the organization.
  • 12. A method for managing data within an organization, the method comprising: acquiring operational data relating to operations of the organization;acquiring financial data related to the operational data;automatically analyzing the operational data and the financial data to: identify a variance in the operational data;generate an event based on the variance;determine a financial impact of the variance based on the variance and the financial data; andprioritize the event based on the financial impact; andoutputting the events.
  • 13. A method according to claim 12, wherein the analyzing further comprises categorizing the event as relating to a role within the organization.
  • 14. A method according to claim 12, wherein the analyzing comprises applying rules to the operational data and financial data to identify the variance and to determine the financial impact.
  • 15. A method according to claim 14, wherein the rules comprise information relating to the roles within the organization and the event is categorized as being related to a role within the organization.
  • 16. A method according to claim 14, further comprising entering configuration data, comprising the rules.
  • 17. A graphical user interface for role-based information, the user interface comprising a plurality of icons each representing a role within an organization, wherein each icon is selectable to provide additional information relating to events relating to the role.
  • 18. The graphical user interface of claim 17, wherein each icon also indicates a status for the represented role based on priority of the events for the represented role.
  • 19. The graphical user interface of claim 17, wherein the additional information comprises a list of events ranked according to a financial impact of the event on the organization.
  • 20. A graphical user interface for viewing reports comprising: a main window;two or more secondary windows within the main window, each secondary window showing a single report variable, wherein each secondary window comprises a means for moving the secondary window within the main window, allowing a first secondary window to be overlaid on a second secondary window in order to compare report variables.
Provisional Applications (1)
Number Date Country
60773646 Feb 2006 US