WO2001026012A1 - Method and estimator for providing storage management - Google Patents

Abstract

A system and method for storage management of an information technology environment provides the tasks involved in building the storage management function. The tasks include the planning (110), analyzing (3510), designing (2410), building (5550), testing (5590), and deploying (7170) of the storage management function. Each task includes process, organization, and technology infrastructure elements.

Description

METHOD AND ESTIMATOR FOR PROVIDING STORAGE

MANAGEMENT

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application 60/158,259, filed October 6, 1999. This application is related to Application

Serial No. entitled "Organization of Information Technology

Functions," by Dove et al. (Atty. Docket No. 10022/45), filed herewith. These applications are incorporated herein by reference in their entirety.

BACKGROUND OF THE INVENTION

The biggest challenges in Information Technology ("IT") development today are actually not in the technologies, but in the management of those technologies in a complex business environment. From idea conception to capability delivery, and to operation, all IT activities, including strategy development, planning, administration, coordination of project requests, change administration, and managing demand for discretionary and non- discretionary activities and operations, must be collectively managed. A shared understanding and representation of IT management is needed because today's technological and business environment demands it. The new technological management orientation should include ways for planning, assessing, and deploying technology within and across enterprises. Businesses need to balance technological capability with enterprise capability in order to remain modem organizations with a chance of survival.

There is a need, therefore, to construct a complete yet simple IT framework that would quickly convey the entire scope of IT capability in a functional decomposition. Such IT framework has to be a single framework for describing IT such management. The IT framework should be a framework of all functions; a representation of a complete checklist of all relevant activities performed in an IT enterprise. A single IT Framework should represent all functions operative in an IT enterprise.

Within that framework, there is also a need for providing for storage management that addresses the handling of centralized and distributed storage media, such as disk, tape, microfiche, image, optical, CD, and jukeboxes. Such storage management methods should include the monitoring and controlling of each of those types of resources and their usage.

BRIEF SUMMARY OF THE INVENTION

The present invention is defined by the following claims, and nothing in this section should be taken as a limitation on those claims. By way of introduction, one embodiment is a method for providing for storage management that includes planning, designing, building, testing, and deploying the storage management for an enterprise. In another embodiment, the method includes developing a business performance model for the planning phase of the storage management. In another embodiment, the method includes designing business processes, skills, and user interaction for the design phase of providing storage management. The method further includes designing an organizational infrastructure and a performance enhancement infrastructure for providing storage management. Also included are designing for technology infrastructure and operations architecture for storage management.

In another embodiment, the method includes building the technology infrastructure and the operations architecture for the building phase of the storage management. This includes building business policies, procedures, performance support, and learning products for the storage management. In another embodiment, the method includes testing the technology infrastructure and the operations architecture for the testing phase of the storage management. In another embodiment, the method includes deploying the technology infrastructure for information technology in the enterprise.

Another aspect of the present invention is a method for providing an estimate for building a storage management function in an information technology organization. This aspect of the present invention allows an IT consultant to give on site estimations to a client within minutes. The estimator produces a detailed break down of cost and time to complete a project by displaying the costs and time corresponding to each stage of a project along with each task. Another aspect of the present invention is a computer system for allocating time and computing cost for building a storage management function in an information technology organization.

These and other features and advantages of the invention will become apparent upon review of the following detailed description of the presently preferred embodiments of the invention, taken in conjunction with the appended drawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the accompanying figures. In the figures, like reference numbers indicate identical or functionally similar elements. Figure 1 shows a representation of networks/systems functions including storage management.

Figure 2 shows a representation of the method for providing storage management according to the presently preferred embodiment of the invention. Figure 3 shows a representation of a task for defining a business performance model for the storage management of Figure 2.

Figure 4 shows a representation of a task for designing business processes, skills, and user interaction for the storage management of

Figure 2. Figure 5 shows a representation of a task for designing technology infrastructure requirements for the storage management of Figure 2. Figure 6 shows a representation of a task for designing an organization infrastructure for the storage management of Figure 2.

Figure 7 shows a representation of a task for designing a performance enhancement infrastructure for the storage management of Figure 2. Figure 8 shows a representation of a task for designing operations architecture for the storage management of Figure 2.

Figure 9 shows a representation of a task for validating a technology infrastructure for the storage management of Figure 2.

Figure 10 shows a representation of a task for acquiring a technology infrastructure for the storage management of Figure 2.

Figure 11 shows a representation of a task for building and testing operations architecture for the storage management of Figure 2.

Figure 12 shows a representation of a task for developing business policies, procedures, and performance support architecture for the storage management of Figure 2.

Figure 13 shows a representation of a task for developing learning products for the storage management of Figure 2.

Figure 14 shows a representation of a task for testing a technology infrastructure product for the storage management of Figure 2. Figure 15 shows a representation of a task for deploying a technology infrastructure for the storage management of Figure 2.

Figure 16 shows a flow chart for obtaining an estimate of cost and time allocation for a project.

Figures 17a and 17b depict one embodiment of an estimating worksheet for a storage management estimating guide.

DETAILED DESCRIPTION OF THE INVENTION

For the purposes of this invention, an information technology ("IT") enterprise may be considered to be a business organization, charitable organization, government organization, etc. that uses an information technology system with or to support its activities. An IT organization is the group, associated systems and processes within the enterprise that are responsible for the management and delivery of information technology services to users in the enterprise. In a modern IT enterprise, multiple functions may be organized and categorized to provide comprehensive service to the user. Thereby, an information technology framework for understanding the interrelationships of the various functionalities, and for managing the complex IT organization is provided.

The various operations management functionalities within the IT framework include a customer service management function; a service integration function; a service delivery function; a capability development function; a change administration function; a strategy, architecture and planning function; a management and administration function; a human performance management function; and a governance and strategic relationships function. Service Level Management plays an important role within the customer service management function. The present invention includes a method for providing a service level management function and an estimator useful for determining the times and cost to provide such a function. Within the service delivery function, network/systems management and storage management play important roles. The present invention includes a method for providing a storage management function for an information technology organization.

Before describing the method for providing storage management, a brief explanation is in order concerning network/systems management, the storage management function, and its systems, functions and tasks.

Network/systems management 31 encompasses a host of functions or activities. These are the functions that perform the day-to-day execution, administration, and maintenance tasks for the enterprise networks and systems, as shown in FIG. 1. This function set includes all routine maintenance and management activities for all systems and networks, except application maintenance and management. Sub-groups or tasks within network/systems management include production scheduling 311 , output/print management 312, operations 313, operations architecture management 314, network addressing management 315, storage management 316, restore/backup management 317, archiving 318, event/fault management 319, system performance management 3110, security management 3111 , and disaster recovery maintenance and testing 3112.

Storage management contains several functions which address the handling of centralized and distributed storage media, such as disk, tape, microfiche, image, Optical, CD jukeboxes, etc. Storage management includes the monitoring and controlling of each of those types of resources and their usage, to include disk space, data placement, tape management and reporting. Disk space management manages the hierarchy of disk storage types, including cache, high speed disk, mass storage, and optical. Assesses the requirements for disk space and allocates/partitions space to the appropriate pools of storage to fulfill space needs.

Data placement management manages the appropriate classification and placement of data on storage medium relative to the reference profile and business importance. This group's function includes managing 'aging' of data, migrating it across the storage hierarchy as it is referenced or unreferenced over periods of time. The group also addresses the retirement of obsolete and temporary data. Tape management establishes and executes procedures for tape handling, tape rotation, tape cycling, and tape selection. Tape management provides tracking and reporting mechanism for tape usage and location, and manages tape library facilities and vendors for onsite and offsite storage of tapes. Storage management reporting provides a tracking and reporting mechanism for all central and distributed storage management functions (including disk space, data management and location, tape usage and location) to maximize the effectiveness of the enterprise storage management system.

A few definitions of terms used in providing storage management are included:

Service Delivery: Service delivery involves all functions required for the day-to-day operations of IT functions, including network and/or systems management and application management. This function category encompasses the functions that keep the IT systems running. The functions performed in this section are considered operations and maintenance functions. Regardless of the change events that are scheduled and performed within the IT enterprise, service delivery activities take place in an on-going manner.

Network and/or Systems Management:

Network and/or systems management performs the day-to-day execution, administration, and maintenance tasks for the enterprise networks and systems. This function set includes the maintenance and management activities for all systems and networks, except application maintenance and management.

Storage Management:

Storage management addresses the handling of centralized and distributed storage media, such as disk, tape, microfiche, image, optical discs, compact discs, and jukeboxes. Storage management includes the monitoring and controlling of each of those types of resources and their usage.

Disk-Space Management:

Disk space management manages the hierarchy of disk storage types, including cache, high speed disk, mass storage, and optical storage. Disk space management assesses the requirements for disk space and allocates and/or partitions space to the appropriate pools of storage to fulfill space needs.

Data Placement Management:

Data placement management manages the appropriate classification and placement of data on storage medium relative to the reference profile and business importance. Data placement management manages "aging" of data, and migrates it across the storage hierarchy as it is referenced or unreferenced over periods of time. Also Data placement management addresses the retirement of obsolete and temporary data. Tape Management:

Tape management establishes and executes procedures for tape handling, tape rotation, tape cycling, and tape selection. Tape management provides tracking and reporting mechanism for tape usage and location, and manages tape library facilities and vendors for onsite and offsite storage of tapes.

Storage Management Reporting:

Storage management reporting provides a tracking and reporting mechanism for the central and distributed storage management functions, including disk space, data management and location, and tape usage and location, to maximize the effectiveness of the enterprise storage management system.

METHOD FOR PROVIDING STORAGE MANAGEMENT According to the preferred embodiment of the invention, the method for providing operations management storage management includes the tasks involved in building a particular OM function. These specific tasks are described in reference to the Operations Management Planning Chart ("OMPC") that is shown on Figure 2. This chart provides a methodology for capability delivery, which includes tasks such as planning analysis, design, build & test, and deployment. Each OM function includes process, organization, and technology elements that are addressed throughout the following description of the corresponding OM function.

The method comprises four phases, as described below in connection with Figure 2. The first phase, "plan delivery" 102, or planning, includes the step of defining a business performance model 2110. The second phase, design 104, has a plurality of steps including design of business processes, skills and user interactions 2410, design of organizational infrastructure 2710, design of performance enhancement infrastructure 2750, analyze technology infrastructure requirements 3510, select and design operations architecture

3550, and validate technology infrastructure 3590. A third phase, build and test 106, has a second plurality of steps including acquire technology infrastructure 5510, build and test operations architecture 5550, develop policies, procedures and performance support 6220, develop learning products 6260 and prepare and execute technology infrastructure product tests 5590. The fourth phase, deployment 108, includes the step of deploying

7170. In the following description, the details of the tasks within each step are discussed.

Step 2110 - Refine Business Performance Model:

This step includes defining the business requirements for storage management, and determining the scope of the delivery and deployment effort for any upgraded capability. Figure 3 shows a representation of the tasks for carrying out these functions according to the presently preferred embodiment of the invention. Figure 3 is a more detailed look at the business performance model 2110, which may include the functions of confirming business architecture 2111 , analyzing operating constraints 2113, analyzing current business capabilities 2115, identifying best operating practices 2117, refine business capability requirements 2118, and updating the business performance model 2119.

Task 2111 : Confirm Storage Management Architecture This task includes assessing the current storage management architecture, confirming the goals and objectives, and refining the components of the storage management architecture. Preferably, the task includes reviewing planning stage documentation, confirming or refining the overall storage management architecture, and identifying best practice opportunities. The amount of analysis performed in this task depends on the work previously performed in the planning phase of the project. The scope of storage management includes devices, people, and processes needed for all data storage requirements, including backups, archives, and restores of archived data back to active status. To avoid repetition, the generic terms "Tape" and "Tape Device" are used to represent many forms of storage media and storage handling equipment, including reel tapes, cassettes, cartridges, removable disk packs, disk shadow sets, juke box devices, robots, and CD-ROMs.

Decisions regarding the type, quantity, location, and connectivity requirements for storage devices, and the resources needed to operate them, are based on business, technical, functional and performance requirements.

The analyses performed in the tasks should focus on the following issues:

1. the location of the data - this will help determine if backups need to be executed centrally or at distributed sites;

2. the volume of data to be backed up - this will help determine both the frequency and the type of media needed;

3. the time available for backup - there may be times of the day when the on-line system is shut down; otherwise backup must occur concurrently with on-line processing; and

4. data integrity constraints should be carefully considered.

Task 2113: Analyze Operating Constraints

This task includes identifying the operating constraints and limitations, and assessing their potential impact on the operations environment. Preferably, the task includes assessing the organization's culture and its potential impact on the project, and reviewing organization, technology, equipment, and facilities for the constraints.

Pre-selected package software may cause constraints (introduction of new operating systems, databases and upgrades). The task also includes assessing the organization's ability to adapt to change as part of the constraints analysis.

Task 2115: Analyze Current Storage Management Architecture

This task includes assessing the current storage management elements, their operation, processes and policies, and their performance. Preferably, the task includes documenting current activities, procedures and service level indicators (KPI's) to establish a performance baseline, and assessing strengths and weaknesses of the storage management function. The task also includes considering the issues noted in Task 2111 when assessing current capabilities and identifying gaps.

Task 2117: Identify Best Operating Practices This task includes defining the relevant best practices for storage management which meet the organization's requirements. Preferably, the task includes identifying the storage management areas which could benefit from application of best practices, and performing a benchmarking analysis to establish opportunities of improvement.

The task includes considering the issues noted in Task 211 1 when assessing best practice opportunities.

Task 2118: Refine Storage Management Architecture Requirements

This task includes defining storage management architecture requirements, and allocating the requirements across changes to human performance, business process, and technology. Preferably, the task includes using the current assessment, constrains assessment, and best practice research to generate the requirements for change, and identifying the changes needed to upgrade the storage management architecture.

The task also includes allocating the changes according to organization and performance improvements, process improvements, and technology improvements.

The task includes reviewing any existing service level agreements for storage management performance and operational requirements. Functional requirements define what the storage management system will do; performance requirements define how well it will operate.

Task 2119: Update Storage Management Architecture Performance

Model

This task includes defining the metrics and measures that describe the storage management system's operating performance. Preferably, the task includes understanding the performance and operational objectives previously defined, and aligning the metrics and target service levels with performance provisions for the various storage management functions as outlines in SLA's. The storage architecture performance model defines the overall design requirements for the storage management function.

Figure 2 depicts the stages in managing a project 100. After completing a planning phase 102, the project reaches a milestone 110, wherein a decision is made as to whether to proceed to an analysis and design stage 104. Following design 104, a second milestone 112 is reached, wherein a decision is made as to whether the design should be built and tested 106. If the decision is favorable, the project proceeds to build and test 106. The next step in the project is a milestone 114 when the project nears completion, and a decision is made as to whether to proceed to deployment 108. The elements of preparation or performance in the several portions of the project are represented by the blocks contained therein and described in this portion of the description.

Step 2410 - Design Business Processes, Skills, and User Interaction:

This step includes designing the new storage management processes and policies, and designing their interactions with the workforce (skills), the storage management software (application interaction), and physical environment. Figure 3 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiment of the invention.

Task 2411 : Design Workflows for Processes, Activities and Tasks This task includes creating the workflow diagrams and defining the workloads for the storage management activities. Preferably, the task includes developing workflow diagrams for the processes and activities. The task also includes defining the relationships between core and supporting processes, activities and tasks, and defining the metrics associated with the processes and activities.

If packaged software has already been selected for storage management, the method includes using the generic processes implied by the package. These should be the starting point for developing the process elements. The method also considers interfaces with other functions (monitoring, software distribution, and security).

Task 2412: Define Physical Environment Requirements This task includes understanding the implications of the storage management architecture on the physical environment; mainly involving location, layout and equipment requirements. Preferably, the task includes designing the facilities, layout and equipment required for storage management, and identifying distributed storage management physical requirements, if any, as well as central needs.

The interaction includes defining the layout and co-location implications of the storage management processes, devices, and the physical environment. If facilities or equipment are to be re-used, the task should confirm their condition and adequacy. The method further includes considering additional requirements due to contingency, reliability and availability needs (e.g., external service providers, high availability, and contingency between sites).

Task 2413: Identify Skill Requirements

This task includes identifying the skill and behavior requirements for performing storage management tasks. Preferably, the task includes identifying critical tasks from the process designs, and supporting skills needed and appropriate behavioral characteristics.

Also, the task includes defining the skills needed for the critical tasks. Skills may be required in all or many of the following areas: 1. Systems Management/Administration and Capacity Planning;

2. Operations Architecture;

3. Resource Management;

4. Task Planning.

Where the infrastructure is widely distributed or the data volumes are high, the storage management function cannot be centralized and decisions will have to be made regarding what storage management tasks are distributed, and therefore what skills are needed centrally versus at remote sites.

Task 2416: Identify Human Performance Requirements This task includes analyzing the storage management processes and determining how to support human performance within these processes.

Preferably, the task includes analyzing the critical performance factors for each storage management task, and selecting a mixture of training and support aids to maximize workforce performance in completing each task. These can include storage management policies and detailed procedures, on- line help screens of various kinds, and checklists, etc.

The task includes determining what has changed from the current processes, and using this to determine the support requirements. The delivery mechanisms should be carefully considered. For example, if a group of support items undergoes frequent changes, the support aid containing these items should probably be accessible on-line so it can be more easily maintained.

For storage management, typical performance support products could include:

1. applications operating procedures manuals; 2. custom (or packaged) screen_^ prompting for storage management information needed to execute jobs or job streams;

3. phone lists of who to call for different types of problems;

4. operating system on-line help or manual pages;

5. hard copy backups of storage management configuration files or customized scripts;

6. storage management software documentation, both detailed and quick-reference; and

7. business recovery plans. Task 2417: Develop Storage Management Interaction Model This task includes identifying the relationships between the tasks in the process diagrams, the physical location, skills required, human-computer interactions, and per ormance support needs. The task also includes developing storage management interaction models by understanding the interactions within each process for physical environment, skills, application and performance support, and unifying these models. Preferably, the task includes integrating processes, the physical environment models, role and skill definitions, the application interactions, and supporting requirements to develop the capability interaction models.

This model illustrates how the process is performed, what roles fulfill the activities involved, and how the roles are supported to maintain the storage management function.

Task 2419: Verify and Validate Storage Management Processes, Skills, and User Interaction

This task includes verifying and validating that the process designs and the human interaction models meet the storage management requirements and are internally consistent. Preferably, the task includes verifying that the storage management model fulfills the original requirements, and using stakeholders and outside experts as well as the design teams to do the validation. Technical Aspects

While the above sections have dealt with organizational aspects of the invention, it may now be appropriate to consider certain technical aspects. This subject will pertain to the method shown in the lower left portion of Figure 2: studying how to analyze technology requirements 3510, selection and design of operations architecture 3550, and validating the choices for technology 3590. When this portion is completed, the planning stages of the project for the project will be complete. Step 3510 - Analyze Technology Infrastructure Requirements:

For this step, the method of the present invention includes preparing for the selection and design of the technology infrastructure, and establishing preliminary plans for technology infrastructure product testing. The project deliverables here will include operations architecture component requirements, a physical model of the operations architecture, and a product test approach and plan. Other functions shown in Figure 5 include tasks of analyzing technology infrastructure requirements 3511 , analyzing component requirements 3515, and planning their tests 3517.

Task 3511 : Prepare Technology Infrastructure Performance Model

This task includes analyzing the functional, technical, and performance requirements for the storage management infrastructure. Preferably, the task includes identifying the key performance indicators for storage management, and establishing baseline estimates and setting measurable targets for the performance indicators. The task also includes developing the functional and physical models, and the performance model.

Therefore, the key technology requirements are the actual storage ^•-management software components themselves. If the organization has already purchased a storage management package, this is a strong indicator for reuse. If the storage management requirements (functional, technical or performance) suggest a change to other software, a strong business case will be needed to support the recommendation.

Task 3513: Analyze Technology Infrastructure Component Requirements This task includes analyzing and documenting the requirements for storage management components, and defining additional needs. Preferably, the task includes identifying any constraints imposed by the environment, and refining functional, physical, and performance requirements developed in the models previously built. The task includes assessing the interfaces to other OM components to avoid redundancy and ensuring consistency/compatibility. Requirements will vary from business to business, and possibly within different units of the same organization. For example, some backup functions may be considered critical at one site and not required at others.

Hardware Requirements - There may be several factors that determine the hardware requirements of a particular facility. It is critical to identify software that will be compatible with the existing or proposed hardware platform. Furthermore, secondary storage hardware must be compatible with the platform and software solution selected.

Restore Requirements - One of the primary considerations in evaluating restore options and capabilities is flexibility. For example, a file or database may need to be restored to a location other than the original source. Furthermore, options to perform partial or incremental restores during normal business operations may be an important capability to consider. Business and operational requirements will determine the restoration options that will be required.

Media Requirements - The storage management requirements dictate the media selection criteria. Service level agreements mandating specific restoration times in the event of data loss may determine the options available. Within these guidelines, the lowest cost alternative which can satisfy the requirements is normally the one selected.

Error Handling Requirements - A storage management toolset may require comprehensive error handling to ensure full integration with other fault management areas. This does not only require detection but also mitigation of media or catalog faults. Access Requirements - Secured access to backup files and enforcement of permissions are required in any environment. The storage management toolset requires some level of integration with security management controls and facilities. This is dependent upon platforms, architectures, and security policies for any particular implementation. User Interface Requirements - For flexibility in execution, the GUI interface of a storage management toolset should be configurable, with the option of defaulting to a command line interface. Catalog Requirements - The backup catalog is one of the most important features of a storage management toolset.

Scheduling/Monitoring Requirements - Storage scheduling and monitoring requirements may include options for determination of status, automatic notification, reporting capability and time estimating. Furthermore, the toolset should offer flexibility for interfacing with other system management scheduling/monitoring tools.

Other Common Requirements - Other factors may be of significance depending on the environment.

Task 3515: Assess Technology Infrastructure Current Environment

This task includes assessing the ability of the current storage management infrastructure to support the new component requirements, and identifying current standards for technology infrastructure. Preferably, the task includes documenting and analyzing the current storage management technology environment. Also, the task includes identifying the areas where gaps exist between the current infrastructure and the new requirements, and noting any standards/policies regarding storage management technology.

The task also includes using the issues noted in task 3513 to assess the current capability.

Task 3517: Plan Technology Infrastructure Product Test

This task includes planning the product test for the storage management infrastructure. The results of this task provide the basis on which the product test is performed as well as the environment in which it is run. Preferably, the task includes defining the test objectives, scope, environment, test conditions and expected results, and developing the deployment plan.

The product test is a test of the whole infrastructure, not just the storage management technology components. Therefore, the organization and process elements are within the scope of the test. Step 2710 - Design Organization Infrastructure:

In this step, the method of the present invention includes defining the organizational structure required for supporting the storage management function according to the expected service levels (e.g., hours of coverage, weekends, recovery time, and second level support). The method also includes performing an estimation of the number of individuals required for every role, and defining what is expected of people who participate in the storage management function, the required roles, competencies, responsibilities, and how their performance is managed. Figure 6 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiment of the invention. After defining business processes, skills and user interactions, a user may proceed to design an organizational infrastructure 2710. The design may define the structures for managing human performance and also define what is expected of people who participate in the storage management function 2711 , the required competencies 2713, and how performance is managed 2715. Other tasks in this area will include organizational infrastructure mobilization 2717, or hiring, and lastly, to verify and validate 2719 that the organization is meeting storage management needs.

Task 2711 : Design Roles, Jobs, and Teams

This task includes determining the competencies and the roles required to operate the storage management function. The task also includes defining how these roles are grouped to fit into teams and jobs, designing the metrics and service levels expected for the roles, and estimating the resources required for every position. Preferably, the task includes confirming the storage management function organizational requirements. The task also includes designing the roles, jobs and teams, determining the reporting relationships, and identifying the performance measurement factors. The key issues include the scope of activities to be performed, geographic distribution of the function, the storage management software tools selected, and the complexity of the environment. A storage management function will exist in most IT organizations with roles and responsibilities already defined for existing applications. Typical storage management roles/jobs may include Systems Engineer, Application Developer, System Administrator, and Operator.

Task 2713: Design Competency Model

This task includes defining the skills, knowledge, and behavior that people require to accomplish their roles in the storage management process. Preferably, the task includes determining the characteristics required of the individuals/teams that will fill the roles, defines the individual capabilities necessary for success. The task includes organizing the capabilities along a proficiency scale and relating them to the jobs and teams.

The introduction of new tools, platforms or devices requires the creation of new competencies in the Organization.

Task 2715: Design Performance Management Infrastructure This task includes defining how individual performance is measured, developed, and rewarded, and determining a performance management approach and appraisal criteria. Preferably, the task includes developing standards for individuals and teams involved in the storage management process. Along with the standards, the method includes identifying a system to monitor the individuals' and teams' abilities to perform up to the standards.

Task 2717: Determine Organization Structure Mobilization Approach This task includes determining and mobilizing the resources required to staff the new storage management function. Preferably, the task includes identifying profiles of the ideal candidates for each position, identifying the sourcing approaches and timing requirements, and promotion opportunities for current resources.

Also, the task includes determining the selection and recruiting approaches. Task 2719: Verify and Validate Organization Structure This task includes verifying and validating that the storage management organization meets the needs of the storage management function and is internally consistent. Preferably, the task includes determining the approach to be used and participants to be involved, and verifying that the organization structure satisfies storage management function requirements. The task also includes confirming the organization with subject matter experts, and validates the names with sponsors and top management.

Step 2750 - Design Performance Enhancement Infrastructure: This step includes determining the actions required to migrate the human organization dedicated to storage management from the current to the future situation. In this step, a performance enhancement infrastructure is designed. The step includes determining the training needed for new storage management functions, and determining the on-line help text, procedures, job aids, and other information to be used. Figure 7 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiment of the invention. Tasks include employee assessment 2751 , any performance enhancement needs 2753, investigation into performance enhancement products 2755, and verification and validation of the performance 2759.

Task 2751 : Assess Employee Competency and Performance This task includes refining the understanding of the current storage management staff's competency proficiency levels and performance levels in specific areas. The task also includes assessing the gaps in competencies and performance levels which will drive the design of the Performance

Enhancement Infrastructure. Preferably, the task includes assessing the competency of the current storage management staff based on the competency model previously developed. Task 2753: Determine Performance Enhancement Needs This task includes assessing the performance support and training requirements necessary to close the competency and performance gaps in the workforce. Preferably, the task includes using the employee assessment to determine the type of performance enhancement required to close the gaps and reach the desired competency levels.

If a package is used, or re-used, vendor training is likely to be available. This is usually the lowest cost approach. The introduction of new packages, including operating systems, databases, and programming languages, implies the achievement of new technical skills.

Task 2755: Design Performance Enhancement Products

This task includes defining the number and structure of performance support and learning products. Preferably, the task includes determining the delivery approaches for training and performance support, designing the learning and performance support products, and defining the support systems for delivering training and performance support.

The design of the training and performance support items is based on workflows, activities, and skill requirements previously identified.

Task 2757: Define Learning Test Approach This task includes developing a comprehensive approach for testing the learning products with respect to achieving each product's learning objectives. Preferably, the task is to identify which learning objectives are tested, and identify the data capture methods that are used to test those objectives. The task here is to concentrate on learning objectives which focus on knowledge gain and relate directly to the storage management performance model and employee competency model. Task 2759: Verify and Validate Performance Enhancement Infrastructure

The task here is to verify the Performance Enhancement Infrastructure and the learning test deliverables to determine how well they fit together to support the new storage management function. Preferably, the task includes simulating the processes and activities performed by the members of the storage management team in order to identify performance enhancement weaknesses.

The task here is also to identify the problems and repeat the appropriate tasks necessary to address the problems.

Step 3550 - Select and Design Operations Architecture:

After the infrastructure requirements have been analyzed, it is time for the step of selecting and designing operations architecture 3550, Figure 8. In this step, the manager will select and design the components 3551 required to support a high-level storage management architecture, including re-use 3552, packaged 3553, and custom components 3555. After selection and design, the architecture is validated 3557. This is the module where the manager designs an approach to storage management and formulates component and assembly test approaches and plans 3558.

Task 3551 : Identify Storage Management Architecture Component

Options

In this task, a manager identifies specific component options that will be needed to support the production environment. Preferably, the task includes identifying all risks and gaps that exist in the current storage management environment, and selecting components that will support the storage management architecture.

The manager also considers current software resources, packaged software and custom software alternatives during the selection process. If new packaged software is part of the solution, the task includes submitting RFPs to vendors for software products that meet basic requirements. Component options include all storage management software packages which fit the basic requirements that were established in the prior tasks.

Task 3552: Select Reuse Storage Management Architecture Components

This task includes identifying whether there is any opportunity to reuse existing architecture components and, finalizing the component selection.

This task can be done in tandem with the package and custom tasks.

Preferably, the task includes evaluating the reuse component options, determining possible gaps where the software does not satisfy requirements, and selecting the appropriate reuse components.

If the organization already has storage management software in place, it would normally only undertake a storage management project in order to replace the old system, meaning reuse had already been eliminated as a possibility.

Task 3553: Select Packaged Storage Management Architecture Components

In this task, a manager or worker evaluates the packaged component options against the selection criteria in order to determine the best fit. Preferably, the person evaluates the packaged component options, conducts vendor demonstrations and site visits, determines gaps where the software does not satisfy requirements, and selects the appropriate packaged components.

Packaged software is the primary alternative for storage management component requirements. Selection is based on how well the options fit the requirements, the level of vendor support and cooperation, and cost factors.

Task 3555: Design Custom Storage Management Architecture Components

In this task, any custom components that are needed are designed, and the effort required for the implementation is evaluated. Preferably, the task includes designing and validating the custom components. Also included are evaluating time, cost, and risk associated with custom development, and selecting the custom components.

The areas where custom components appear most frequently include: Base Software Design Issues - custom installation scripts system interfaces custom reports External product/protocol requirements network protocols - operations architecture component interfaces application interfaces Base Software Operational Issues file transfer scripts recovery scripts - production control automation scripts

RDBMS scripts for loads/unloads.

Task 3557: Design and Validate Storage Management Architecture This task includes developing a high-level design of the storage management architecture. Preferably, the task includes combining the reuse, package, and custom components into an integrated design, and ensuring that the architecture meets the storage management requirements. The task also includes defining the standards and procedures for component build and test.

Task 3559: Develop Storage Management Architecture Component and Assembly, Test Approach and Plan

This task includes defining the approach and test conditions for the storage management assembly, component, and component acceptance testing. Preferably, the task includes defining objectives, scope, metrics, regression test approaches, and risks associated with each test. Also included are defining component testing for custom and customized (reuse or package) components, component acceptance testing for new packaged components, and assembly testing for all components and all interfaces.

Step 3590 - Validate Technology Infrastructure:

The next block in a technology portion of the method is a step wherein the manager validates the chosen technology infrastructure 3590, as shown in

Figure 9. An analysis is undertaken of the storage management design 3591 , the technology infrastructure is validated 3593, the infrastructure design is validated 3595, and the plans for deploying the system and its test approach are reviewed and revised as necessary 3597. The manager will verify that the storage management design is integrated, compatible, and consistent with the other components of the Technology Infrastructure Design, and meets the Business Performance Model and Business Capability Requirements.

Task 3591 : Review and Refine Technology Infrastructure Design

This task includes ensuring that the storage management infrastructure design is compatible with other elements of the technology infrastructure.

Preferably, the task includes testing that storage management is integrated and consistent with the other components of the technology infrastructure. Also, the task includes developing an issue list for design items that conflict with the infrastructure or items that do not meet performance goals or requirements, and refining the storage management infrastructure if needed.

It may also be prudent to develop an issue list, or "punch list" for design items that conflict with the infrastructure or items that don't meet performance goals or requirements. This "punch list" may be subsequently used to refine the storage management infrastructure if needed.

Task 3593: Establish Technology Infrastructure Validation

Environment

In this task, the organization designs, builds, and implements the validation environment for the technology infrastructure. Preferably, the organization establishes the validation environment, selects and trains participants, and schedules the validation. The task also includes efforts of designers/architects of OM components that interface with storage management in the validation.

Task 3595: Validate Technology Infrastructure Design

In this task, the organization identifies gaps between the storage management infrastructure design and the technology infrastructure requirements defined earlier. Preferably, the task includes validating the design, recording issues as they arise, identifying and resolving critical gaps, iterating through the validation until the critical issues have been resolved, and developing action plans for less critical issues.

If storage management is being installed as part of a larger operations architecture, it is used as a checkpoint to verify that the most current requirements from the Architecture release are being considered. The storage management function is installed to control the environment. The design takes this into account.

Task 3597: Analyze Impact and Revise Plans for Technology Infrastructure

In this task, the organization updates the appropriate technology infrastructure delivery plans based on the outcome of the validation process.

Preferably, the task includes analyzing the associated scope of work required for modifications and enhancements. The task also includes analyzing the impact of validation outcomes on costs and benefits, and refining plans for deployment testing. The project may proceed along three time-lines in the build and test portion 106 of Figure 2. One time-line continues in the technical vein, that is, acquiring the technology infrastructure 5510 and building and testing the selected operations architecture 5550. At the same time, other groups or personnel of the organization may develop learning products 6260, and other groups or personnel may develop policies, procedures and performance support 6220 for the new system. With these tasks completed, the project manager will proceed to prepare and execute a test of the new system, that is, a storage management technology infrastructure product test 5590. With these tasks completed, all that remains is to deploy the new system 7170.

Step 5510 - Acquire Technology Infrastructure: Acquiring the technology infrastructure 5510, Figure 10, is the first step in build and test. Tasks forming a part of this block include planning and executing the acquisition of components 5511 , which suppliers will supply the components and services 5513, and how they will be supplied. This task package is primarily required if new packaged software is to be procured and installed as part of the project or if upgrades in the current devices must be done. The economic impact or implications are evaluated 5515, and the organization prepares and executes acceptance tests 5517 for the new components.

In this step, the method of the present invention includes planning and executing the procurement of storage management components which must be acquired. If choices are available, this is the step in which the organization decides who will supply the components and services and how they will be supplied.

Task 5511 : Initiate Acquisition of Technology Infrastructure Components

In this task, personnel initiate the process for selecting and obtaining the storage management packaged software components. Preferably, the task includes defining vendor selection criteria, selecting potential vendors, preparing RFP/RFQ documents, and issuing request documents to selected vendors. Component capability and performance requirements are clearly defined in the documentation provided to vendors.

Task 5513: Select and Appoint Vendors

In this task, the organization selects the vendor(s) who will provide the storage management components and negotiate the terms of the procurement. Preferably, the organization evaluates responses to RFP/RFQ documents, and determines the selected component(s), and identifies the desired vendor(s). The task also includes negotiating procurement terms, and managing the placement of contracts/orders through component delivery. Software training may be negotiated as part of the contractual agreement. If multiple components and multiple vendors are involved, it is advantageous to arrange to have delivery and installation of the components occur simultaneously so that the component interfaces are tested with vendor representatives on site.

Task 5515: Evaluate Deployment Implications of Vendor Appointments In this task, the organization determines the impact and deployment implications of the software and vendor selection on the project economics and the business case. Preferably, the task includes comparing procurement costs with project estimates, and assessing impact on storage management case and storage management performance model. The task includes making revisions and obtaining approvals as necessary.

Economics of the transaction(s) should be consistent with plans documented in the storage management case, and the storage management business model is modified as appropriate to reflect changes.

Task 5517: Prepare and Execute Acceptance Test of Technology Architecture Components

In this task, personnel ensure that the storage management packaged components meet the technology infrastructure requirements. Preferably, the task includes building the test scripts, the test drivers, the input data, and the output data to complete the technology architecture component acceptance test model. The task also includes executing the test, and documenting any fixes/changes required of the component vendor(s).

Software component training may be scheduled and conducted as soon as the new storage management components are installed. The testing ensures that all critical features and functions operate as advertised by the vendor(s); if multiple components are involved, they should interface correctly. Step 5550 - Build and Test Operations Architecture:

Having acquired the technology, the project now proceeds to a build and test stage 5550, depicted in Figure 11. In this stage, personnel design and program the storage management components. This is also the time to perform component and assembly testing. Major tasks may include detailed design of the operations architecture 5551 , assembly test plan 5552, building of the system 5553, component tests 5555, and assembly and test 5557.

Task 5551 : Perform Storage Management Architecture Detailed Design In this task, the organization defines the requirements and program specifications related to each storage management component. Preferably, the task includes preparing program specifications for custom and customized components, designing the packaged software configuration, and conducting detailed design reviews. Custom components may include interfaces to other OM components and special reporting requirements for storage management.

Additional items to consider include tape naming conventions, service level agreements, disc/tape capacity based on performance modeling and planning, and media retention issues.

Task 5552: Revise Storage Management Architecture Component and Assembly Test Approach and Plan

This task includes updating the storage management test plans to reflect the components' detailed design, and defining revised considerations or changes to the requirements. Preferably, personnel review the test approaches and plans, and revise as needed for new or updated requirements. If other OM components interface with storage management software, the organization plans for testing of these interfaces, either in this task package or in the product test task package.

Task 5553: Build Storage Management Architecture Components In this task, personnel build all custom storage management components and extensions to packaged or reuse components. Preferably, they build the custom components, and the customized extensions to packaged or reuse components, and configure the packaged components. Some packages may have unique or proprietary languages for customizing and/or configuration. Training time may be involved if this is the case.

Task 5555: Prepare and Execute Component Test of Custom Storage

Management Components.

In this task, personnel ensure that each custom storage management component and each customized component meets its requirements. Preferably, the task includes verifying the component test model, setting up the test environment, executing the test, and making component fixes and retests as required.

Task 5557: Prepare and Execute Storage Management Components Assembly Test.

In this task, a full test of all interactions between storage management components is conducted. Preferably, the test verifies the assembly test model, and includes setting up the test environment, executing the test, and making fixes and retests as required. Several test cycles may be needed to test all aspects of the solution, especially where the requirements call for multiple scenarios of partial backup/restore and where multiple sites are involved simultaneously in the process.

Step 6220 - Develop Policies, Procedures, and Performance Support: In this step, the provider produces a finalized, detailed set of new storage management policies, procedures, and reference materials, and conducts a usability test to verify ease of use. Having completed the technical aspects, the project manager now considers some longer-term portions of the project, the policies, procedures and performance support detailed design 6220, as shown in Figure 12, needed for ongoing operation of the service.

The purpose of this step is to produce a finalized, detailed set of new storage management policies, procedures, and reference materials. It is also desirable to conduct a usability test and review to verify ease of use with both scheduling personnel and personnel from the supported enterprise. Upon successful completion of this step, the operating personnel will have storage management policies and procedures and may also have any performance support products that may be necessary or useful. Tasks include writing or performing the policies and procedures 6221 , developing business policies and procedures 6223, user procedures 6225, reference materials and job aids 6227, and validating and testing 6229.

Task 6221 : Perform Policies, Procedures and Performance Support Detailed Design

This task includes providing the product structure for all the new storage management policies, procedures, reference materials, and job aids. It also includes providing prototype templates for each product. Preferably, the task includes designing the structure of the new policies, procedures, and support materials, and templates for product development. The method also desirably includes defining standards for policy and performance support development, and creating prototype products.

Task 6223: Develop Policies and Procedures In this task, the organization develops a complete set of policies and procedures for storage management. Policies describe the rules governing workflows. Procedures describe the sequential sets of tasks to follow based on the policies. Preferably, the organization collects and reviews content information, drafts policies and procedures, and plans for the production of the materials. Procedures are organized according to the functions to be performed by the storage management group. For example, if storage management takes care of backups and restores, the procedures are itemized in separate sections.

Additional items to consider here are: 1. Detailed off-site storage procedures, including pick and delivery during normal business situations and also during emergency conditions, and

2. Storage management inclusion in business recovery plans and business recovery testing schedules.

Task 6225: Develop User Procedures

In this task, the organization drafts a detailed set of storage management user procedures. User procedures provide the details necessary to enable smooth execution of new tasks within a given procedure. Preferably, the organization collects and reviews content information, drafts the procedures, verifies consistency with business policies and procedures, and plans for the production of the materials.

The task includes documenting not only what tasks need to be performed and in what sequence, but also what actions need to be taken when problems or breakdowns occur, and also describe the information flows. Being able to recover quickly from an error condition during backup or restore may be critical if the allotted processing window is limited.

Task 6227: Develop Reference Materials and Job Aids In this task, personnel draft the reference materials and job aids that make a task easier or more efficient. The information provided in the reference materials and job aids is typically difficult to memorize, but is used frequently on the job. Preferably, personnel collect and review content information, and draft the performance support products. These materials should be verified for consistency with policies and procedures, and with plans for the production of the materials. Performance support materials are very desirable in environments where storage management is a decentralized function performed by multiple groups across the organization. This helps provide more consistency in the handling of problem situations. Task 6229: Validate and Test Policies, Procedures, and Performance Support

This task includes confirming that the products meet the requirements of the storage management function and the needs of the personnel who will use them. Preferably, the personnel prepare validation scenarios, and validate content and ease of use of materials. This is also a convenient time for testing on-line support products, and resolving open issues.

Step 6260 - Develop Learning Products:

Though not strictly a part of project hardware building, a successful project will typically include some thought to training its users. Thus, an important step may include development of learning products 6260, as shown in Figure 13. A first task may include defining the needs for learning products and the environment in which they are to be used 6261. Technical training in storage management software components may come from the package vendor or a third party training organization. Procedural training for an organization's procedures is often custom built or tailored for the situation.

After learning these requirements, the next steps are to perform a learning program detailed design 6263 and to make prototypes 6265. Using the prototypes, actual learning products may then be made, and produced 6267. The products should be tested 6269. Testing may take place later in the cycle, as depicted in Figure 13, or earlier, using prototypes, to achieve feedback and ensure the effort is on track and useful to the students or trainees. In this step, the method of the present invention creates a complete, finalized set of learning products.

Task 6261 : Develop Learning Product Standards and Development

Environment

This task includes creating the environment for developing the storage management learning products. Preferably, a manager selects authoring and development tools, defines standards, and designs templates and procedures for product development. Technical training in storage management software components may come from the package vendor or a third party training organization. Procedural training must be custom built.

Task 6263: Perform Learning Program Detailed Design In this task, personnel specify how each learning product identified in the learning product design is developed. Preferably, the task includes defining learning objectives and context, designing the learning activities, and preparing the test plan. The design made by made into modules by separating the storage management activities into separate learning products, integrating use of the storage management software into the learning program, and ensuring that technical software training are complete. It is strongly recommended that formal learning products be developed even if the planned format for delivery of entry-level training is on-the-job (junior operators learning from senior operators).

Task 6265: Prototype Learning Products In this task, personnel complete prototypes and conduct ease-of-use sessions on classroom-based learning components (i.e., activities, support system, instructor guide). Preferably, the same personnel create the prototype components, and conduct and evaluate the prototype.

Task 6267: Create Learning Products In this task, the organization develops the learning materials proposed and prototyped during the design activities. Preferably, they develop activities, content, evaluation and support materials required, as well as the maintenance plan. In this task, the organization trains instructors/facilitators, and arranges for production.

Task 6269: Test Learning Products

In this task, the organization tests each product with the intended audience to ensure that the product meets the stated learning objectives, that the instructors are effective, and that the learning product meets the overall learning objectives for storage management. Preferably, they confirm the test plan, execute any tests, and review and make required modifications. If the target audience is small, this test could serve as the formal training session for the group. Multiple sessions may be appropriate if responsibilities are split and all personnel are not responsible for knowing all activities.

Step 5590 - Prepare and Execute Technical Infrastructure Product Test.

At this point, much of the project work has been completed, and the product is ready for testing in a realistic environment 5590 to insure it is ready for deployment. A series of storage management tests is depicted in Figure 14. The test and its design or model are first prepared 5591 , with expected results. The test is then performed 5593, by executing the tests prepared earlier. The tests should simulate actual working conditions, including any related manuals, policies and procedures produced earlier. An objective of the test should be to notice any deficiencies and make changes as required. Following these tests, a deployment test should be executed 5595, to ensure that the storage management infrastructure can be gainfully deployed within the enterprise or organization. If this test is successful, the last stage of testing may then be executed, the technology infrastructure configuration test 5597. This test will ensure that the performance of the technology infrastructure, including storage management, will be consistent with the Technology Infrastructure Performance Model after the infrastructure has been deployed. The test should be made with an eye to risk assessment of the integration of the new system within the enterprise, and the risk assessment should be updated as needed.

Task 5591 : Prepare Technology Infrastructure Test Model In this task, personnel create the storage management infrastructure test model. Preferably, they create the test data and expected results, and the testing scripts for production, deployment, and configuration tests. Also, they conduct the storage management training not yet completed, and review and approve the test model. If a complete set of functions is being deployed, this is a comprehensive test with storage management being one piece. Storage management may be implemented as an independent function designed to support all other applications. The product test should occur in a production- ready environment and include all hardware and software to be used in production. If storage management is being implemented independently, then all or a portion of the production environment is used as the "test" application.

The task includes verifying that the interfaces to other operations components, such as capacity planning and system monitoring, are included in the test plan.

Task 5593: Execute Technology Infrastructure Product Test This task includes verifying that the technology infrastructure successfully supports the requirements outlined in the storage management architecture design stage. Preferably, the task includes executing the test scripts, verifying the results, and making changes as required. The test should simulate the actual storage management working conditions, including related manuals and procedures.

Task 5595: Execute Technology Infrastructure Deployment Test In this task, the new storage management infrastructure can be correctly deployed within the organization. Preferably, the deployment test includes executing the test scripts, verifying the results, and making changes as required.

Task 5597: Execute Technology Infrastructure Configuration Test In this task, personnel ensure that the performance of the technology infrastructure, including storage management, is consistent with the technology infrastructure performance model after the infrastructure has been deployed. Preferably, they execute the test scripts, verify the results and make changes as required. They also update the risk assessment.

After completing the build and test phase 106, a milestone 114 for authorizing deployment is reached. At this point, the organization or a manager decides whether the project should be implemented or deployed. If the decision is favorable, the deployment stage 108 is reached and the new or improved storage management function is implemented.

Step 7170 - Deploy Technology Infrastructure.

Following successful testing, the storage management infrastructure may be deployed online 7170, Figure 15. At this point, the tasks remaining include configuring the technology infrastructure 7171 to prepare for any new business capability components.

If the configuration is complete, the technology infrastructure may then be installed 7173. In addition to the scheduling software, all documentation, performance support tools and training must be completed and in place prior to the deployment. A final task may be to verify the technology infrastructure 7179 and address any issues raised as a result of the testing or the deployment. Customers and storage management personnel, as well as enterprise management, should be kept abreast of developments, successful and less successful, so all issues can be resolved quickly. This task should require minimal effort if storage management is being installed independently.

Task 7171 : Configure Technology Infrastructure In this task, personnel customize the deployment unit's technology infrastructure to prepare for the new storage management components. Preferably, they review the customization requirements, perform the customization, and verify the infrastructure configuration. This task may be required if the storage management function is being deployed at more than one site. In these cases, variances in the configurations may determine any customization required.

Task 7173: Install Technology Infrastructure

In this task, personnel install the technology infrastructure for storage management. Preferably, they prepare the installation environment, install the storage management infrastructure, and verify the installation. In addition to the method for providing the storage management function, as described above, the present invention also includes a method and apparatus for providing an estimate for building a storage management function in an information technology system. The method and apparatus generate a preliminary work estimate (time by task) and financial estimate

(dollars by classification) based on input of a set of estimating factors that identify the scope and difficulty of key aspects to the system.

Previous estimators only gave a bottom line cost figures and were directed to business rather than OM functions. It would take days or weeks before the IT consultant produced these figures for the client. If the project came in either above or below cost, there was no way of telling who or what was responsible. Therefore, a need exists for an improved estimator

Fig. 16 is a flow chart of one embodiment a method for providing an estimate of the time and cost to build a service level management in an information technology system. In Fig. 16, a provider of a storage management system, such as an IT consultant, for example, Andersen Consulting, obtains estimating factors from the client 202. This is a combined effort with the provider adding expertise and knowledge to help in determining the quantity and difficulty of each factor. Estimating factors represent key business drivers for a given operations management OM function. Table 1 lists and defines the factors to be considered along with examples of a quantity and difficulty rating for each factor.

For example, as an illustration of the method of the invention, the provider, with the help of the client, will determine an estimating factor for the number of service level agreements ("SLA") 202. Next comes the determination of the difficulty rating 204. Each of these determinations depends on the previous experience of the consultant. The provider or consultant with a high level of experience will have a greater opportunity to determine the correct number and difficulty. The number and difficulty rating are input into a computer program. In the preferred embodiment, the computer program is a spreadsheet, such as EXCEL, by Microsoft Corp. of Redmond, Washington, USA. The consultant and the client will continue determining the number and difficulty rating for each of the remaining estimating factors 206.

After the difficulty rating has been determined for all of the estimating factors, this information is transferred to an assumption sheet 208, and the assumptions for each factor are defined. The assumption sheet 208 allows the consultant to enter in comments relating to each estimating factor, and to document the underlying reasoning for a specific estimating factor.

Table 1

Next, an estimating worksheet is generated and reviewed 210 by the consultant, client, or both. An example of a worksheet is shown in Figs 17a and 17b. The default estimates of the time required for each task will populate the worksheet, with time estimates based on the number factors and difficulty rating previously assigned to the estimating factors that correspond to each task. The amount of time per task is based on a predetermined time per unit required for the estimating factor multiplied by a factor corresponding to the level of difficulty.

Each task listed on the worksheet is described above in connection with details of the method for providing the storage management function. The same numbers in the description of the method above correspond to the same steps, tasks, and task packages of activities shown on the worksheet of

Figs. 17a and 17b. The worksheet is reviewed 210 by the provider and the client for accuracy. Adjustments can be made to task level estimates by either returning to the factors sheet and adjusting the units 212 or by entering an override estimate in the 'Used' column 214 on the worksheet. This override may be used when the estimating factor produces a task estimate that is not appropriate for the task, for example, when a task is not required on a particular project.

Next, the provider and the client review and adjust, if necessary, the personnel time staffing factors for allocations 216 for the seniority levels of personnel needed for the project. Referring to Figs. 17a and 17b, these columns are designated as Partner - "Ptnr", Manager - "Mgr", Consultant - "Cnslt", and Analyst - "Anlst", respectively. These allocations are adjusted to meet project requirements and are typically based on experience with delivering various stages of a project. It should be noted that the staffing factors should add up to 1.

The consultant or provider and the client now review the workplan 218, and may optionally include labor to be provided by the client. In one embodiment, the workplan contains the total time required in days per stage and per task required to complete the project. Tasks may be aggregated into a "task package" of subtasks or activities for convenience. A worksheet, as shown in FIG. 17a and 17b, may be used, also for convenience. This worksheet may be used to adjust tasks or times as desired, from the experience of the provider, the customer, or both.

Finally, a financial estimate is generated in which the provider and client enter the agreed upon billing rates for Ptnr, Mgr, Cnslt, and Anlst 220. The total estimated payroll cost for the project will then be computed and displayed, generating final estimates. At this point, a determination of out-of- pocket expenses 222 may be applied to the final estimates to determine a final project cost 224. Preferably, the provider will then review the final estimates with an internal functional expert 226.

Other costs may also be added to the project, such as hardware and software purchase costs, project management costs, and the like. Typically, project management costs for managing the provider's work are included in the estimator. These are task dependant and usually run between 10 and 15% of the tasks being managed, depending on the level of difficulty. These management allocations may appear on the worksheet and work plan. The time allocations for planning and managing a project are typically broken down for each of a plurality of task packages where the task packages are planning project execution 920, organizing project resources 940, controlling project work 960, and completing project 990, as shown in FIG. 17a. It will be appreciated that a wide range of changes and modifications to the method as described are contemplated. Accordingly, while preferred embodiments have been shown and described in detail by way of examples, further modifications and embodiments are possible without departing from the scope of the invention as defined by the examples set forth. It is therefore intended that the invention be defined by the appended claims and all legal equivalents.

While this invention has been shown and described in connection with the embodiments described, it is apparent that certain changes and modifications, in addition to those mentioned above may be made from the basic features of this invention. Many types of organizations may benefit from the use of this invention, e.g., any organization wishing to use a storage management system within an information technology system. In addition, there are many different types of computer systems, and computer software and hardware, that may be utilized in practicing the invention, and the invention is not limited to the examples given above. Accordingly, it is the intention of the applicants to protect all variations and modifications within the valid scope of the present invention. It is intended that the invention be defined by the following claims, including all equivalents.

Claims

1. A method for providing storage management for an IT organization, the method, comprising:

(a) planning for said storage management; (b) designing said storage management;

(c) building said storage management;

(d) testing said storage management; and

(e) deploying said storage management.

2. The method of claim 1 wherein said planning act includes: (f) developing a business performance model for said storage management.

3. The method of claim 2 wherein said developing act includes: (g) confirming business architecture;

(h) analyzing a plurality of operating constraints; (i) analyzing a current storage management capability;

(j) identifying a plurality of best practices for said storage management;

(k) defining a plurality of requirements for said storage management; and (I) developing said business performance model.

4. The method of claim 1 wherein said designing act includes:

(f) designing business processes, skills, and user interaction for said storage management.

5. The method of claim 4 wherein said step (f) includes: (g) designing a plurality of workflows for processes, activities, and tasks for said storage management;

(h) identifying physical environment interactions;

(i) identifying skill requirements for performing said storage management; (j) defining application interactions;

(k) identifying performance support requirements;

(I) developing a capability interaction model; and

(m) developing said business processes, skills, and user interaction.

6. The method of claim 1 wherein said designing act includes: (f) designing an organization infrastructure for said storage management.

7. The method of claim 6 wherein said step (f) includes: (g) designing a plurality of roles, jobs, and teams; (h) designing a competency model;

(i) designing a performance management infrastructure; (j) determining an organization infrastructure mobilization approach; and

(k) developing said organization infrastructure.

8. The method of claim 1 wherein said designing act includes:

(f) designing a performance enhancement infrastructure for said storage management.

9. The method of claim 8 wherein said step (f) includes:

(g) assessing employee competency and performance for a current storage management;

(h) determining performance enhancement needs;

(i) designing performance enhancement products;

(j) defining a learning test approach; and

(k) developing said performance enhancement infrastructure.

10. The method of claim 1 wherein said designing act includes: (f) designing a technology infrastructure for said storage management.

11. The method of claim 10 wherein said step (f) includes:

(g) preparing a technology infrastructure performance model; (h) analyzing a plurality of technology infrastructure component requirements; (i) assessing a current technology infrastructure;

(j) developing a technology infrastructure design; and (k) planning a technology infrastructure product test.

12. The method of claim 1 wherein said designing act includes:

(f) designing operations architecture for said storage management.

13. The method of claim 12 wherein said step (f) includes:

(g) identifying operations architecture components;

(h) selecting reuse operations architecture components;

(i) selecting packaged operations architecture components; (j) designing custom operations architecture components; and

(k) designing the operations architecture.

14. The method of claim 10 wherein said testing act includes:

(g) validating said technology infrastructure for said storage management.

15. The method of claim 14 wherein said validating act includes: (h) reviewing said technology infrastructure;

(i) establishing an environment for validating said technology infrastructure; (j) validating said technology infrastructure; and

(k) analyzing an impact of said technology infrastructure.

16. The method of claim 14 wherein said building act includes: (h) acquiring a plurality of technology infrastructure components for said technology infrastructures.

17. The method of claim 16 wherein said acquiring act includes: (i) defining acquisition criteria;

(j) selecting vendors for said technology infrastructure components;

(k) appointing said vendors;

(I) evaluating deployment implications of said selecting and appointing; and

(m) testing said technology infrastructure components for acceptance.

18. The method of claim 13 wherein said building act includes: (I) building said operations architecture components.

19. The method of claim 18 wherein said testing act includes: (m) testing said operations architecture components; and (n) testing said operations architecture.

20. The method of claim 1 wherein said building act includes: (f) developing policies, procedures, and performance support for said storage management.

21. The method of claim 20 wherein said developing act includes:

(g) developing business policies and procedures;

(h) developing user procedures;

(i) developing reference materials and job aids; and

(j) validating said policies, procedures, and reference materials.

22. The method of claim 1 wherein said building act includes:

(f) developing learning products for said storage management.

23. The method of claim 22 wherein said developing act includes:

(g) developing learning products standards; (h) prototyping said learning products; (i) building said learning products; and (j) testing said learning.

24. The method of claim 16 wherein said testing act includes: (i) testing said technology infrastructure for said storage management.

25. The method of claim 24 wherein said step (i) includes:

(j) preparing a plurality of test models for said technology infrastructure; (k) executing a technology infrastructure product test;

(I) executing a technology infrastructure deployment test models; and

(m) executing a technology infrastructure configuration test model.

26. The method of claim 24 wherein said deploying act includes:

(j) deploying said technology infrastructure for said production services.

27. The method of claim 26 wherein said step (j) includes: (k) configuring said technology infrastructure; (I) installing said technology infrastructure; and

(m) verifying said technology infrastructure.

28. A method for providing an estimate for building a storage management function in an information technology system, the method comprising: (a) obtaining a plurality of estimating factors;

(b) determining a difficulty rating for each of said estimating factors;

(c) generating a time allocation for building said storage management based on said estimating factor and said difficulty rating; and (d) generating a cost for building said storage management based on said time allocation.

29. The method as recited in claim 28, wherein obtaining said estimating factor further includes receiving said estimating factors from a client.

30. The method as recited in claim 28, wherein said estimating factors include the number of at least one of platforms, service level agreements, storage management activities, applications, databases, storage management components, storage management roles, number of users, and business units.

31. The method as recited in claim 28, wherein said difficulty rating is selected from the group of simple, moderate, or complex.

32. The method as recited in claim 28, wherein said time allocation includes time allocated for a plurality of individual team members where said individual team members include at least one of partner, manager, consultant, and analyst.

33. The method as recited in claim 28, wherein said cost depends on said time allocation and a billing rate for said individual team member.

34. The method as recited in claim 28, wherein said cost is broken down for each of a plurality of stages for building said storage management where said stages include at least one of plan and manage, capability analysis, capability release design, capability release build and test, and deployment stages.

35. The method as recited in claim 28, wherein said time allocation is used to generate a project work plan.

36. The method as recited in claim 28, wherein said billing rate generates a financial summary of said cost.

37. The method as recited in claim 35, wherein said work plan is broken down for each of a plurality of stages for building said storage management where said stages are plan and manage, capability analysis and design release, capability release build and test, and deployment.

38. The method as recited in claim 37, wherein said plan and manage stage is broken down for each of a plurality of task packages where said task packages are plan project execution, organize project resources, control project work, and project complete.

39. A computer system for allocating time and computing cost for building a storage management function in an information technology system, comprising:

(a) a processor;

(b) a software program for receiving a plurality of estimating factors and difficulty rating for each of said estimating factors and generating a time allocation and cost for building said storage management; and

(c) a memory that stores said time allocation and cost under control of said processor.