초록 ▼

A method and apparatus for component plan analysis under uncertainty is disclosed. A representative implementation of this method begins when a planner captures assumptions about products and components in an entity called a "scenario." A scenario is the parameterization of all the demand, financial

A method and apparatus for component plan analysis under uncertainty is disclosed. A representative implementation of this method begins when a planner captures assumptions about products and components in an entity called a "scenario." A scenario is the parameterization of all the demand, financial, and operational information for a portfolio of products and components across a set of time buckets (planning periods). The planner then specifies a component plan to be analyzed. The component plan identifies the quantities of each resource that will be used or procured during each planning period. The planner then generates a request for analysis including one or more analysis parameters that will be used in order to evaluate the performance and the risks associated with the component plan and scenario. The request for analysis is submitted to an analysis engine for calculation of risk indicators. The analytical engine calculates all the performance indicators and returns the results. The results are then typically stored in a database or other persistent storage system.

대표청구항 ▼

What is claimed is: 1. A computer-implemented method for risk analysis under uncertainty, the method comprising the steps of: capturing assumptions to create a scenario for one or more products for one or more time planning periods; specifying one or more component consumption requirements for one

What is claimed is: 1. A computer-implemented method for risk analysis under uncertainty, the method comprising the steps of: capturing assumptions to create a scenario for one or more products for one or more time planning periods; specifying one or more component consumption requirements for one or more products; specifying a component plan to be analyzed, the component plan identifying the quantities of each component that are positioned for each planning period; submitting a request for analysis to an analytic engine for calculation of risk and performance indicators, wherein the specifying the component plan to be analyzed is performed prior to the submitting the request for analysis, the request for analysis including one or more analysis parameters and identifying the scenario, the one or more component consumption requirements for the one or more products, and component plan; and receiving a risk calculation from the analytic engine in response to the submitting the request for analysis. 2. A method as recited in claim 1 that further comprises the steps of: calculating one or more risk and performance indicators; returning the risk and performance indicators; and storing the risk and performance indicators in a database or other persistent storage system. 3. A method as recited in claim 2 that further comprises the step of presenting the results to the user. 4. A method as recited in claim 3 that further comprises the step of retrieving at least part of the component plan from a database or other persistent storage system. 5. A method as recited in claim 3 that further comprises the step of retrieving at least part of the component plan from an external enterprise resources planning (ERP) systems or supply chain management (SCM) systems. 6. A method as recited in claim 1 that further comprises the steps of: specifying one or more component parameters; specifying one or more product interactions; and specifying one or more product parameters. 7. A method as recited in claim 6 that further comprises the step of storing the one or more component requirements, component parameters, product interactions and product parameters in a database or other persistent storage system. 8. A method as recited in claim 1 that further comprises the steps of: retrieving the scenario and component plan from a database or other persistent storage system; constructing a message including the analysis parameters, the scenario and the component plan; and sending the message to an analytic engine. 9. A method as recited in claim 1 wherein components that are positioned for each planning period comprise non-inventory components. 10. A data storage medium having machine-readable code stored thereon, the machine-readable code comprising instructions executable by one or more processors, the instructions defining a method comprising the steps of: capturing assumptions about products and components to create a scenario, the scenario describing the demand, financial, and operational information for one or more products and components for one or more time planning periods where the components include uninventoried available components; specifying one or more component requirements; specifying a component plan to be analyzed, the component plan identifying the quantities of each component that will be used or procured during each planning period; generating a request for analysis, the request for analysis including the one or more component requirements and one or more analysis parameters and identifying the scenario and component plan; and submitting the request for analysis to an analytic engine for calculation of risk and performance indicators, wherein the specifying the component plan to be analyzed is performed prior to the submitting the request for analysis. 11. A data storage medium as recited in claim 10 wherein the method further comprises the steps of: calculating one or more risk and performance indicators, and returning the risk and performance indicators. 12. A data storage medium as recited in claim 11 wherein the method further comprises the step of storing the risk and performance indicators in a database or other persistent storage system. 13. A data storage medium as recited in claim 10 wherein the method further comprises the steps of: specifying one or more component parameters; specifying one or more product interactions; and specifying one or more product parameters. 14. A data storage medium as recited in claim 13 wherein the method further comprises the step of storing the one or more component requirements, component parameters, product interactions and product parameters in a database or other persistent storage system. 15. A data storage medium as recited in claim 10 wherein the method further comprises the steps of: specifying a component plan; specifying levels for each component included in the component plan; and storing the component plan in a database or other persistent storage system. 16. A data storage medium as recited in claim 10 wherein the method further comprises the steps of: retrieving the scenario and component plan from a database or other persistent storage system; constructing a message including the analysis parameters, the scenario and the component plan; and sending the message to an analytic engine. 17. A system for performing risk analysis under uncertainty, the system comprising: a user interface configured to allow a user to: specify one or more component requirements; capture assumptions about products and components to create a scenario, the scenario describing the demand, financial, and operational information for one or more products and components for one or more time planning periods; and specify a component plan to be analyzed, the component plan identifying the quantities of each component that will be used or procured during each planning period, where the identified quantities of components include at least one uninventoried available component; and an application server configured to: generate a request for analysis, the request for analysis including the one or more component requirements and one or more analysis parameters and identifying the scenario and component plan; and submit the request for analysis to an analytic engine for calculation of risk and performance indicators after the user specifies the component plan to be analyzed. 18. A system as recited in claim 17 wherein the user interface is configured to allow a user to: specify one or more component parameters; specify one or more product interactions; and specify one or more product parameters. 19. A system as recited in claim 18 wherein the application server is configured to store the one or more component requirements, component parameters, product interactions and product parameters in a database or other persistent storage system. 20. A system as recited in claim 17 wherein the user interface is configured to allow a user to: specify a component plan; and specify levels for each component included in the component plan. 21. A system as recited in claim 20 wherein the application server is configured to store the component plan in a database or other persistent storage system. 22. A system as recited in claim 17 wherein the application server is configured to: retrieve the scenario and component plan from a database or other persistent storage system; construct a message including the analysis parameters, the scenario and the component plan; and send the message to an analytic engine.