# US 2008/0313595 A1 · Method and system for estimating project plans for packaged software applications

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0313595 A1
- Document ID: US20080313595A1
- Status: Published application
- Kind: A1
- Application number: 11/762,113
- Filed: 2007-06-13
- Published: 2008-12-18
- Earliest claimed: 2007-06-13
- Assignees: International Business Machines Corporation
- Inventors: Paul R. Boulineau; John D. Cann; Rajat Dugar; Jed Kreamer; Juhnyoung Lee; Rakesh Mohan; Andrew Raymond; Thomas D. Rosinski; Vikas J. Shivpuriya; Gerhard Sigl; Annette Simonato
- Web page: https://patentgrep.com/patent/US20080313595A1

## CPC

- G06F 8/20: Software design
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 10/06312: {Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling}
- G06Q 10/06313: {Resource planning in a project environment}
- G06Q 10/0635: Risk analysis of enterprise or organisation activities
- G06Q 10/06375: {Prediction of business process outcome or impact based on a proposed change}
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A system for estimating and generating project plans for implementing packaged software applications, the system includes: a view layer configured to act as a user interface for user inputs and system outputs; a model and control layer configured to implement rules based on a series of estimation and implementation models, and to perform calculations of project plan details and project plan schedules; an estimation knowledge base layer configured to hold and derive the series of estimation and implementation models; and wherein the system for estimating and generating multi-dimensional project plans for implementing packaged software applications is carried out over networks comprising: the Internet, intranets, local area networks (LAN), and wireless local area networks (WLAN).

## Claims

### Claim 1

A method for estimating and generating multi-dimensional project plans for implementing packaged software applications, the method comprising:
generating one or more project plans based on a series of user inputs;
inputting a user selected project plan from the one or more project plans and the user inputs to a rule based duration estimator to determine a series of project phases and their estimated durations;
generating staffing, resource allocation, project cost, and project value estimations based on a project schedule estimation and one or more estimation models; and
wherein the project schedule estimation is based on the series of project phases and their estimated durations.

### Claim 2 (depends on 1)

The method of claim 1 further comprising: scoring the series of project plans based on the user inputs and a project plan scorer with a series of scoring rules and parameters;
ranking the series of project plans based on their scores;
listing the series of project plans in a plan list based on their rank; and
wherein the user selects one or more implementation project plans from the list.

### Claim 3 (depends on 2)

The method of claim 2, wherein the series of rules and parameters for scoring the series of project plans are externalized in one or more data storage systems to facilitate user understanding and adjustments of the scoring calculation.

### Claim 4 (depends on 1)

The method of claim 1, wherein the rules and parameters for estimating project phase durations are externalized in one or more data storage systems to facilitate user understanding and adjustments of the phase duration estimation.

### Claim 5 (depends on 1)

The method of claim 1, wherein the estimation models are at least one of the following: normative and constructive;
wherein the normative estimation model is a generic model that supports one or more of the following: various packaged software applications, various clients, evolving situations, and parameter externalization in ontology and autonomic configuration; and
wherein the constructive estimation model is an intuative model for estimation that provides insights and understanding to the estimation, as well as, interactive decision support using what-if analysis and sensitivity analysis.

### Claim 6 (depends on 1)

The method of claim 1, wherein the estimation models are stored within one or more estimation knowledge bases.

### Claim 7 (depends on 1)

The method of claim 1, wherein the user inputs are externalized to facilitate user adjustments.

### Claim 8 (depends on 1)

The method of claim 1, wherein the user inputs are divided by subject into basic information, plan dimensions, and system information;
wherein the basic information comprises one or more of: scenario information, user information, project information, and customer information;
wherein the system information user input provides system details that will be taken into account in the packaged application project to be estimated; and
wherein the plan dimensions define the scope of the project plan.

### Claim 9 (depends on 8)

The method of claim 8, wherein various combinations and permutations of plan dimensions provide a plurality of multi-dimensional implementation project plans.

### Claim 10 (depends on 8)

The method of claim 8, wherein the plan dimensions that are taken into account in structuring packaged application implementation projects comprise one or more of: sector and industry, geography by continent, country, business unit, and business scenario; and
wherein various combinations and permutations of plan dimensions provide a plurality of multi-dimensional implementation project plans.

### Claim 11 (depends on 1)

The method of claim 1, wherein the project schedule estimation is rendered in one or more project plan representation schemes including but not limited to a Gantt chart.

### Claim 12 (depends on 1)

The method of claim 1, wherein the user inputs are obtained from a series of questionnaires.

### Claim 13 (depends on 12)

The method of claim 12, wherein the questionnaires are dynamically generated based on user responses in previous questionnaires within the series of questionnaires; and
wherein the user may iteratively return to the questionnaires to adjust their recorded responses.

### Claim 14 (depends on 12)

The method of claim 12, wherein the questionnaires are form-based.

### Claim 15 (depends on 12)

The method of claim 12, wherein the questionnaires are rendered in a graphical user interface (GUI) format with user selectable header tabs to navigate between questionnaires.

### Claim 16 (depends on 12)

The method of claim 12, wherein the series of questionnaires are divided by subject into basic information, plan dimensions, and system information.

### Claim 17 (depends on 12)

The method of claim 12, wherein the user responses to the series of questionnaires are externalized to facilitate user adjustments.

### Claim 18 (depends on 1)

The method of claim 1, wherein the user may adjust the generated project schedule to overlap two or more of the project phases by changing one or more of: the starting date of the phases and the length of the phases;
wherein the user may adjust the generated project schedule to grouping by synchronization two or more of the project phases by changing the starting date of one or more phases; and
wherein a GUI is configured to adjust the project phases.

### Claim 19 (depends on 1)

The method of claim 1, wherein the user may adjust a plurality of rollouts of the implementation project plans, to overlap two or more of the rollouts, by changing one or more starting dates of the rollouts;
wherein the user may group by synchronization the starting date of a plurality of rollouts of the implementation project plans; and
wherein a GUI is configured to adjust the starting dates of the implementation project plan rollouts.

### Claim 20 (depends on 1)

The method of claim 1, wherein estimating and generating multi-dimensional implementation project plans for packaged software applications is carried out over networks comprising: the Internet, intranets, local area networks (LAN), and wireless local area networks (WLAN).

### Claim 21

A method for estimating and generating multi-dimensional project plans for implementing packaged software applications, the method comprising:
recording user responses to a series of form-based questionnaires;
scoring a series of project plans for a packaged software application based on the recorded user responses and a project plan scorer with a series of scoring rules;
ranking the series of project plans based on their scores;
listing the series of project plans in a plan list based on their rank;
recording the user's project plan selection from the plan list;
inputting the project plan selection and the user responses to a rule based duration estimator to determine a series of project phases and their estimated durations;
generating a project schedule estimation in terms of a series of one or more project phases based on the rule based duration estimator;
generating staffing, resource allocation, project cost, and project value estimations based on the project schedule estimation and normative and constructive models stored within an estimation knowledge base;
wherein the form-based questionnaires are dynamically generated based on user responses in previous form-based questionnaires within the series of form-based questionnaires;
wherein the user may iteratively return to the form-based questionnaires to adjust their recorded responses;
wherein the recorded user responses are externalized to facilitate user adjustments;
wherein the series of rules and parameters for scoring the series of project plans are externalized in one or more data storage systems to facilitate user understanding and adjustments of the scoring parameters;
wherein the rules and parameters for estimating phase duration are externalized in one or more data storage systems to facilitate user understanding and adjustments of the phase duration parameters;
wherein the user may adjust the generated project schedule to overlap two or more of the project phases by changing one or more of: the starting date of the phases and the length of the phases;
wherein the user may adjust the generated project schedule to group by synchronization two or more of the project phases by changing the starting date of one or more phases;
wherein the user may adjust a plurality of rollouts of the implementation project plans, to overlap two or more of the rollouts, by changing one or more starting dates of the rollouts;
wherein the user may group by synchronization the starting date of the plurality of rollouts of the implementation project plans;
wherein a series of plan dimensions are taken into account in estimating and generating multi-dimensional implementation project plans;
wherein various combinations and permutations of plan dimensions provide a plurality of multi-dimensional implementation project plans; and
wherein the estimating and generating multi-dimensional implementation project plans for packaged software applications is carried out over networks comprising: the Internet, intranets, local area networks (LAN), and wireless local area networks (WLAN).

### Claim 22 (depends on 21)

The method of claim 21, wherein the plan dimensions that are taken into account in structuring packaged application implementation projects comprise one or more of: sector and industry, geography by continent, country, business unit, and business scenario.

### Claim 23

A system for estimating and generating multi-dimensional project plans for implementing packaged software applications, the system comprising:
a view layer configured to act as a user interface for user inputs and system outputs;
a model and control layer configured to implement rules based on a series of estimation and implementation models, and to perform calculations of implementation project plan details and project plan schedules;
an estimation knowledge base layer configured to hold and derive the series of estimation and implementation models; and
wherein the system for estimating and generating multi-dimensional project plans for implementing packaged software applications is carried out over networks comprising: the internet, intranets, local area networks (LAN), and wireless local area networks (WLAN).

### Claim 24 (depends on 23)

The system of claim 23, wherein the view layer comprises an estimation template, and an output generating component;
wherein the estimation template is dynamically formed and based on a business product software program including, but not limited to, a spreadsheet, a word processor, presentation applications, and project planning applications; and
wherein the estimation template is configured to provide basic user interface functions and estimation features.

### Claim 25 (depends on 24)

The system of claim 24, wherein the estimation template provides a series of questionnaires;
wherein the series of questionnaires are configured to provide inputs to the system;
wherein the series of questionnaires are dynamically generated based on user responses in previous questionnaires within the series of questionnaires; and
wherein the questionnaires are rendered with user selectable header tabs to navigate between questionnaires.

### Claim 26 (depends on 25)

The system of claim 25, wherein the series of questionnaires are divided by subject into basic information, plan dimensions, and system information;
wherein the basic information comprises one or more of: scenario information, user information, project information, and customer information;
wherein the plan dimensions define the scope of the project plan; and
wherein the system information user input provides system details that will be taken into account in the packaged application project to be estimated.

### Claim 27 (depends on 26)

The system of claim 26, wherein various combinations and permutations of plan dimensions provide a plurality of multi-dimensional project plans.

### Claim 28 (depends on 26)

The system of claim 26, wherein the plan dimensions that are taken into account in structuring packaged application implementation projects comprise one or more of: sector and industry, geography by continent, country, business unit, and business scenario; and
wherein various combinations and permutations of plan dimensions provide a plurality of multi-dimensional project plans.

### Claim 29 (depends on 23)

The system of claim 23, wherein the model and control layer comprises one or more rules engines that are configured to support rule-based estimation of project phase durations, and the automation of business rules, and one or more object controllers that manage the series of estimation and implementation models held in one or more estimation knowledge bases within the estimation knowledge base layer, as well as, providing estimation and implementation outputs to the view layer, and accepting user input that has been received in the view layer;
wherein the estimation knowledge base layer comprises one or more estimation knowledge discoverers and collectors in signal communication with one or more model refiners;
wherein the estimation knowledge discoverers and collectors are in signal communication with information sources comprising: empirical data from the system output, prior internal cases stored in a knowledge repository, and collected knowledge and data from external sources related to project plans for implementing packaged software applications;
wherein the collected knowledge and data is culled and analyzed by one or more model refiners for validation;
wherein validated knowledge and data is learned by one or more model refiners;
wherein the model refiners convey the newly found validated knowledge and data to the estimation and implementation models as parameters that are represented in the estimation knowledge base.

### Claim 30 (depends on 29)

The system of claim 29, wherein the estimation knowledge base externalizes knowledge and information parameters related to the project estimation, and facilitates the updating of parameter values that are used by the series of estimation and implementation models.

### Claim 31 (depends on 29)

The system of claim 29, wherein data from external sources comprise one or more of: the Internet, one or more enterprise networks, information from one or more packaged application software vendors (ISV) and service providers, and information from existing packaged application software installations.

### Claim 32 (depends on 23)

The system of claim 23, wherein the system is configured based on a model-view-controller (MVC) architecture.

### Claim 33 (depends on 23)

The system of claim 23, wherein the project schedule estimation is rendered in one or more project plan representation schemes including but not limited to a Gantt chart.

### Claim 34 (depends on 23)

The system of claim 23, wherein the user may adjust the generated project schedule to overlap two or more of the project phases by changing one or more of: the starting date of the phases and the length of the phases;
wherein the user may adjust the generated project schedule to group by synchronization two or more of the project phases by changing the starting date of one or more phases; and
wherein a GUI is configured to adjust the project phases.

### Claim 35 (depends on 23)

The system of claim 23, wherein the user may adjust a plurality of rollouts of the implementation project plans, to overlap two or more of the rollouts, by changing one or more starting dates of the rollouts;
wherein the user may group by synchronization the starting date of a plurality of rollouts of the project plans; and
wherein a GUI is configured to adjust the starting dates of the project plan rollouts.
