WO2001026010A1 - Method and estimator for production scheduling - Google Patents

Abstract

A method for providing a production function for an information technology organization provides the tasks involved in building the production scheduling function. Subgroups or tasks include production scheduling (311), output printing management (312), operations (313), operation architecture management (314), network addressing management (315), storage management (316), restore/back up management (317), archiving (318), event/fault management (319), system performance management (3110), security management (3111), and disaster recovery maintenance and testing (3112).

Description

METHOD AND ESTIMATOR FOR PRODUCTION SCHEDULING 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

Expenditures on information technology have risen over the past twenty years to the point where they are almost always a significant amount in the capital budget of any enterprise. These enterprises include business enterprises, and may also include non-for-profit businesses, charitable institutions, religious institutions, educational establishments, governmental agencies, non-governmental organizations, and other organizations of many types.

The expenditures are not only for computers and their software, but also for many other purposes associated with computers and information technology. These further expenses often include the cost of networking a plurality of computers. Once networks are established, servers of several varieties may be used, as well as other computers and peripherals. As the

Internet and e-commerce have come of age, firewalls, intranets, and web servers are constructed and must be administered. Computer security concerns arise as well.

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 modern 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 a framework needs to be a single framework describing an entire IT capability, whether as functions, systems or tasks. The IT framework should be a framework of 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 the IT framework, there is also a need for production scheduling function that manages the day-to-day operations schedule of activities in the various IT domains and ensures that production activities are performed and controlled as required. Such a production scheduling function maintains the requirements for the execution of scheduled jobs and tasks across the IT enterprise, taking into consideration all dependencies and inter-relationships in the environment. A production scheduling function should coordinate with other function categories to provide input and should aim to continuously improve current IT services and offerings.

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 a production scheduling function that includes planning, designing, building, testing, and deploying a production scheduling function for an IT organization.

In one aspect of the preferred embodiment, the planning step includes developing a business performance model for the production scheduling function. Preferably, the step of developing a business recovery model may further include confirming business architecture; analyzing a plurality of operating constraints; analyzing a current production scheduling capability; identifying a plurality of best practices for the production scheduling; defining a plurality of requirements for the production scheduling; and developing the business performance model.

In another aspect of the preferred embodiment, the designing step includes designing business processes, skills, and user interaction for the production scheduling function. Preferably, the step of designing business processes includes designing a plurality of workflows for processes, activities, and tasks for the production scheduling; identifying physical environment interactions; identifying skill requirements for performing the production scheduling; defining application interactions; identifying performance support requirements; developing a capability interaction model; and developing the business processes, skills, and user interaction.

In another aspect of the preferred embodiment, the designing step includes designing an organization infrastructure for the production scheduling function. Preferably, the step of designing an organization infrastructure includes designing a plurality of roles, jobs, and teams; designing a competency model; designing a performance management infrastructure; determining an organization infrastructure mobilization approach; and developing the organization infrastructure.

In another aspect of the preferred embodiment, the designing step includes designing a performance enhancement infrastructure for the production scheduling function. Preferably, the step of designing a performance enhancement infrastructure includes assessing employee competency and performance for production scheduling; determining performance enhancement needs; designing performance enhancement products; defining a learning test approach; and developing the performance enhancement infrastructure.

In another aspect of the preferred embodiment, the designing step includes designing a technology infrastructure for the production scheduling function. Preferably, the step of designing a technology infrastructure includes preparing a technology infrastructure performance model; analyzing a plurality of technology infrastructure component requirements; assessing a current technology infrastructure; developing a technology infrastructure design; and planning a technology infrastructure product test. In another aspect of the preferred embodiment, the designing step includes designing operations architecture for the production scheduling function. Preferably, the step of designing operations architecture includes identifying operations architecture components; selecting reuse operations architecture components; selecting packaged operations architecture components; designing custom operations architecture components; and designing the operations architecture.

In another aspect of the preferred embodiment the testing step includes validating the technology infrastructure for the production scheduling function. Preferably, the step of validating includes reviewing the technology infrastructure; establishing an environment for validating the technology infrastructure; validating the technology infrastructure; and analyzing an impact of the technology infrastructure.

In another aspect of the preferred embodiment the building step includes acquiring a plurality of technology infrastructure components for the production scheduling function. Preferably, the step of acquiring includes defining acquisition criteria; selecting vendors for the technology infrastructure components; appointing the vendors; evaluating deployment implications of the selecting and appointing; and testing the technology infrastructure components for acceptance.

In another aspect of the preferred embodiment the building act includes building the operations architecture components.

In another aspect of the preferred embodiment the testing act includes testing the operations architecture components; and testing the operations architecture.

In another aspect of the preferred embodiment the building step includes developing policies, procedures, and performance support for the production scheduling function. Preferably, the step of developing includes developing business policies and procedures; developing user procedures; developing reference materials and job aids; and validating the policies, procedures, and reference materials.

In another aspect of the preferred embodiment the building act includes developing learning products for the production scheduling function. Preferably, the step of developing includes developing learning products standards; prototyping the learning products; building the learning products; and testing the learning.

In another aspect of the preferred embodiment the testing step includes testing the technology infrastructure for the production scheduling. Preferably, the step of testing includes preparing a plurality of test models for the technology infrastructure; executing a technology infrastructure product test; executing a technology infrastructure deployment test models; and executing a technology infrastructure configuration test model.

In another aspect of the preferred embodiment the deploying step includes deploying the technology infrastructure for the production scheduling.

Preferably, the step of deploying includes configuring the technology infrastructure; installing the technology infrastructure; and verifying the technology infrastructure.

Another aspect of the present invention is a method for providing an estimate for building a production scheduling 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 production scheduling 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 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 network/systems functions including production scheduling. Figure 2 shows a representation of a method for providing production scheduling according to the presently preferred embodiment of the invention.

Figure 3 shows a representation of the tasks for defining a business performance model for production scheduling. Figure 4 shows a representation of the tasks for designing business processes, skills, and user interaction for production scheduling.

Figure 5 shows a representation of the tasks for designing technology infrastructure requirements for production scheduling.

Figure 6 shows a representation of the tasks for designing an organization infrastructure for production scheduling.

Figure 7 shows a representation of the tasks for designing a performance enhancement infrastructure for production scheduling.

Figure 8 shows a representation of the tasks for designing operations architecture for production scheduling. Figure 9 shows a representation of the tasks for validating a technology infrastructure for production scheduling.

Figure 10 shows a representation of the tasks for acquiring a technology infrastructure for production scheduling.

Figure 11 shows a representation of the tasks for building and testing operations architecture for production scheduling.

Figure 12 shows a representation of the tasks for developing business policies, procedures, and performance support architecture for production scheduling.

Figure 13 shows a representation of the tasks for developing learning products for production scheduling.

Figure 14 shows a representation of the tasks for testing a technology infrastructure product for production scheduling.

Figure 15 shows a representation of the tasks for deploying a technology infrastructure for production scheduling. Figure 16 shows a flow chart for obtaining an estimate of cost and time allocation for a project.

Figures 17a and 17b show one embodiment of an estimating worksheet for a production scheduling 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 and 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. Within the service delivery function, network/systems management plays an important role. Production Scheduling is a key component of Network/Systems Management. The present invention includes a method for providing a production scheduling function for an information technology organization.

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

Network/systems management is a function within the category of Service Delivery Functions. Service Delivery involves all functions required for the day-to-day operations of the information technology systems. This function category is often referred to as the "IT shop": It 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 information technology enterprise, Service Delivery activities take place in an ongoing manner. Service Delivery includes Network/Systems Management and Applications Management. 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.

Production scheduling 311 manages the day-to-day operations schedule of activities in the various information technology domains and ensures that production activities are performed and controlled as required. Production scheduling maintains the requirements for the execution of scheduled jobs and tasks across the information technology enterprise, taking into consideration all dependencies and inter-relationships in the environment. A job is defined as any activity performed in the environment that requires human intervention, while a task is an activity to the environment that is automated. Production scheduling requirement management manages the changing requirements of the business and associated technology infrastructure for scheduling operations jobs and tasks. This takes into account performance metrics and SLAs/OLAs. Personnel performing these tasks use expertise in technology architecture to extrapolate the scheduling implications of varying requirements, and to add the appropriate supporting functions to the core business capability requirements. This function also maps the business operations and processes to the Production Scheduling function, updating the requirements as new systems and business activities are introduced. Fixed job scheduling defines production schedules and interfaces with System Performance Management functions to validate that the infrastructure environment (network, platforms, storage subsystems, etc.) will support the throughput requirements for the regularly executed schedule of jobs. Ad hoc scheduling assesses the priorities, capacities, and opportunities to add ad hoc jobs and tasks to the normal production schedule. This group prioritizes requests based on established job requirements submitted, and coordinates execution once a schedule is determined. The task is accomplished by weighing considerations, such as other processes running (backup/restoration, software distribution, etc.), before approving and sending the ad hoc order.

Service class definition establishes, maintains, and manages the appropriate service classes to support different classes of jobs and tasks based on requirements. This function determines the scheduling and adds the appropriate supporting functions to the core business capability requirements. Selection criteria may include time, job dependencies, availability of data, and business function priority. Batch process design establishes and maintains the dependency structure, notification approaches, and restart/recovery mechanisms for the production schedule execution. Schedule and job monitoring ensures scheduled jobs and tasks are starting and stopping within the defined schedule window. Schedule and job monitoring revises schedules when execution completes early or extends beyond normal schedule periods. Information from System Performance Management will play a key role in this function.

According to the preferred embodiment of the invention, the method for providing OM production scheduling includes the tasks involved in building that 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, 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 108 includes the step of deploying 7170. In the following description, the details of the tasks within each step are discussed.

Step 2110 - Refining Business Performance Model:

In step 2110, the business requirements for production scheduling are defined, and the scope of the delivery and deployment effort for any upgraded capability are determined. Figure 3 shows a representation of the tasks for carrying out these functions according to the presently preferred embodiment of the invention. These tasks include Confirming Business Architecture 2111 ,

Analyzing Operating Constraints 2113, Analyzing Current Business Capabilities 2115, Identifying Best Operating Practices 2117, Refining Business Capability Requirements 2118, and Updating the Business Performance Model 2119. The products of this step include analyses of scheduling requirements and of scheduling gaps.

Task 2111 : Confirming Business Architecture Task 2111 includes reviewing planning stage documentation; confirming or refining the overall scheduling architecture; and ensuring management commitment to the project. This should help in attaining an understanding of the current production scheduling architecture. The goals and objectives of the project will also be confirmed. Components of the architecture, pre-selected tools, and main interfaces should be refined as a result of the analysis.

The amount of analysis performed in this task depends on the work previously performed in the planning phase of the project. The applications may have some elements of batch processing, and the main crossed dependencies in batch processing between different platforms and systems should be identified. For environments with significant batch processing requirements, production scheduling can be highly complex and may require automated support. Consequently process, technology, organization, and performance issues are included in the analysis. The resulting production scheduling architecture review can then be subjected to further analysis in tasks 2113, 2115, and 2117.

Task 2113: Analyzing Operating Constraints

Task 2113 includes assessment of the organization's culture and its potential impact on the project. The organization, technology, equipment, and facilities are all reviewed to identify any constraints. In identifying the operating constraints and limitations, the potential impact of these constraints on the operations environment can also be assessed.

For example, pre-selected package software may cause constraints such as scheduling and technological limitations. If no batch window is available (i.e., 24x7 on-line uptime) then batch jobs are executed concurrently with on-line activity. The organization's ability to adapt to change should be assessed as part of the constraints analysis.

Task 2115: Analyzing Current Business Capability Task 2115 includes documentation of current activities and procedures documented to establish a performance baseline. Current performance can be measured by using the most representative indicators for volume, elapsed time, number of restarts, and error processing as well as other pertinent factors. Strengths and weaknesses of the current scheduling capability are also assessed.

This analysis provides an accurate picture of the current scheduling elements, their operation, and their performance. The scheduling processes themselves should be identified before looking into how the performances of the processes are measured. This task should be performed to an appropriate level of detail such that the degree of change required to move to the new scheduling capability is fully understood.

Task 2117: Identifying Best Production Scheduling Practices

Task 2117 includes identification of the scheduling areas that benefit from application of "best practices". The optimum best practices required to meet the environment and objectives are researched and identified. These processes define the relevant best practices for production scheduling which meet the organization's requirements.

Opportunities may exist where the organization's present operations underperform standard levels. Examples of underperformance include obsolete basis technology and underperforming groups within the organization. Applying the best practices may require some customization to meet the particular circumstances of the organization.

Task 2118: Refining Business Capability Requirements Task 2118 includes using the assessment of the current capabilities 2115, constraints assessment 2113, and best practice research 2117 to generate the requirements for change. The changes needed to upgrade the scheduling capability are identified and are allocated according to organization and performance improvements, process improvements, and technology improvements. As a result, the scheduling and capability requirements can be defined

The existing service level agreements for batch processing performance and operational requirements should be reviewed. These factors typically relate to timing of outputs and reports and to the availability of updated databases. Capability requirements define what the scheduling system will do. Capability performance requirements define how well it will operate. Assessment of constraints 2113, assessment of the current capabilities 2115, identification of best practices 2117, and refinement of capability requirements 2118 are preferably repeated in an iterative method until the business requirements are fully defined, consolidated, and optimized. These requirements are then used to update the business performance model for production scheduling in task 2119.

Task 2119: Updating Business Performance Model Task 2119 includes creating an understanding of the performance and operational objectives which were previously defined. The metrics and target service levels are aligned with performance provisions for batch scheduling and processing as outlined in the SLA's. This provides for a definition of the metrics and measures that describe the scheduling system's operating performance. The metrics should be kept as simple and straightforward as possible. The suppliers and customers of the scheduling system should be considered in defining the metrics.

The production scheduling performance model defines the overall design requirements for the scheduling capability. These design requirements, metrics, and definitions are delivered to the stakeholders for their concurrence. Upon approval, these parameters guide the design of the production scheduling function in the "capability release design stage".

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

In step 2410, the business processes, skills, and user interaction are taken into account. The new production scheduling processes are designed as are the interactions of the processes with the workforce (skills), the production scheduling software (application interaction), and the physical environment. The main interfaces of production scheduling include monitoring and service control. Figure 4 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiment of the invention. These tasks include Designing Workflows 2411 , Defining Physical Environment Interactions 2412, Identifying Skills Requirements For Performing Scheduling Tasks 2413, Defining Application Interactions 2415, Identifying Performance Support Requirements 2416, Developing A Capability Interaction Model 2417, and Verifying and Validating

Business Processes, Skills and User Interaction 2419. The products of this step include a business process design and a capability interaction model. Task 2411 : Designing Workflows for Processes, Activities and Tasks Task 2411 includes the development of workflow diagrams for the processes and activities. The relationships between core and supporting processes, activities, and tasks are defined. Also, definitions are developed for the metrics and measuring points associated with the processes and activities. These diagrams and definitions allow for definition of the workloads for the production scheduling activities. If packaged software has already been selected for scheduling, the generic business processes implied by the package should be used as the starting point for developing the process elements. The resulting business process design will be used to define and identify key requirements and interactions in tasks 2412, 2413, 2415, and 2416.

Task 2412: Defining Physical Environment Interaction Task 2412 includes identification of the interfaces of the workflow with the physical environment. The facilities, layout, and equipment for scheduling are designed. Also, any distributed scheduling physical requirements and central needs are identified.

The implications of the scheduling processes on the physical environment can include location, layout, and equipment requirements. The interactions identified help define the layout and co-location implications of the scheduling workflows and the physical environment. If facilities or equipment are to be re-used, their condition and adequacy should be confirmed. The resulting physical environment interaction model will be used in task 2417 to develop a capability interaction model.

Task 2413: Identifying Skill Requirements

Task 2413 includes identification of the critical tasks from the workflow designs. The skills needed for the critical tasks are defined. The necessary supporting skills and appropriate behavioral characteristics for performing production scheduling tasks are identified. Where the infrastructure is widely distributed and the production scheduling function cannot be centralized, decisions are made regarding what scheduling tasks are distributed and, therefore, what skills are needed centrally versus at remote sites. The skill definitions and resulting role interaction model will be used in task 2417 to develop a capability interaction model.

Task 2415: Defining Application Interaction

Task 2415 includes identification of required scheduling features that are not supported by the scheduling software. The human-computer interactions needed to meet these requirements are defined.

Packaged software may have pre-defined application interactions. This task will preferably be performed for activities that are not supported by the packaged software. Often, the software permits jobs to be released based on specified events including time of day, day of week/month, and system event, such that a single interaction causes the job to be executed automatically and without intervention until business conditions require a change. The occurrence of abnormal events should be considered so that the interactions appropriate to handle these events, where they are not handled by the package, may be determined. Some events which may not be handled by the package include job failure caused by database time-outs, jobs exceeding threshold execution times, unavailability of required files, and incomplete/invalid parameters supplied for a job. These events should be identified and analyzed on a job-by-job basis. The human-computer interaction model will be used in task 2417 to develop a capability interaction model.

Task 2416: Identification of Performance Support Requirements Task 2416 includes analysis of the critical performance factors for each scheduling task. A mixture of training and support aids is selected to maximize workforce performance in completing each task. These support aids can include scheduling policies and detailed procedures, on-line help screens of various kinds, and checklists.

Anything that has changed from the current processes should be identified as this will help determine the support requirements. The delivery mechanisms should be carefully considered. For example, if a group of support items undergo frequent changes, the support aid containing these items should be accessible on-line so it is more easily maintained. The performance support requirements will be used in task 2417 to develop a capability interaction model.

Task 2417: Developing Capability Interaction Model Task 2417 includes the integration of the physical environment interaction model 2412, skill requirements 2413, human-computer interaction model 2415, and performance support needs 2416 into overall Capability Interaction Models. Capability interaction models should be developed by understanding the interactions within each process for physical environment, skills, application and performance support, so that these models can be unified. The model will illustrate how the process is performed, what roles fulfill the activities involved, and how the roles maintain the scheduling capability.

Task 2419: Verifying and Validating Business Processes, Skills, and User Interaction Task 2419 includes verification and validation that the process designs and the capability interaction models fulfill the original requirements. The production scheduling requirements are preferably internally consistent. Preferably, it is verified that the capability model. Stakeholders and outside experts as well as the design teams participate in the validation. The design of workflows 2411 , definition of interactions 2412 and 2415, and identification of requirements 2413 and 2416, followed by capability interaction model development 2417 and verification 2419, are preferably repeated in an iterative method until the business requirements are fully met.

Step 2710 - Design Organization Infrastructure: In step 2710, the structures for managing human performance are defined, as are the expectations of the people who participate in the production scheduling function, the required competencies, and the way in which 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. These tasks include Designing Roles, Jobs, and Teams 2711 ; Designing Competency Model 2713; Designing Performance Management Infrastructure 2715; Determining Organization Infrastructure Mobilization Approach 2717; and Verifying and Validating Organization Infrastructure 2719. The products of this step include an organization infrastructure.

Task 2711 : Design Roles, Jobs, and Teams Task 2711 includes confirmation of the production scheduling competency requirements and design of the roles, jobs, and teams. The reporting relationships are determined, and the performance measurement factors are identified. This determines the competencies and the roles required to operate the new capability. Roles may be grouped to fit into teams and jobs.

Production scheduling roles and jobs are based on the breadth of functions assigned. The production scheduling organization structure is designed around the business requirements. A scheduling function may exist in most IT organizations with roles and responsibilities already defined for existing applications. Key issues include the scope of activities to be performed, geographic distribution of the function, the production scheduling software tools selected, and the complexity of the environment.

Factors which could cause major changes to the scheduling function may include migration from a centralized to a distributed (e.g., client/server) environment and the introduction of new scheduling software with significantly different functionality. However, even in these cases, much of the roles are extracted from previous engagements dealing with production scheduling.

Task 2713: Design Competency Model

Task 2713 includes determination of the characteristics required of the individuals/teams that will fill the roles as designed by task 2711. The individual capabilities necessary for success are defined. These capabilities are then organized along a proficiency scale so as to relate them to the jobs and teams. The resulting skill/knowledge/behavior competency model, in combination with the role/job/team design from task 2711 are preferably redesigned in an iterative method until the designs are complete. Task 2715: Design Performance Management Infrastructure Task 2715 includes development of standards for individuals and teams involved in the production scheduling process. Along with the standards, a system to monitor the ability of individuals and teams to perform up to the standards is identified. This then defines how individual performance is measured, developed, and rewarded. The resulting performance management approach and appraisal criteria are organized into a performance management infrastructure.

Task 2717: Determine Organization Infrastructure Mobilization Approach

Task 2717 includes identification of the profiles and number of the ideal candidates for each position as well as the sourcing approaches and timing requirements. The selection and recruiting approaches are determined. This allows for mobilization of the resources required to staff the new production scheduling capability. The size of the organization according to the required profiles and objective SLAs should be determined. All of these considerations become part of a staffing plan.

Task 2719: Verify and Validate Organization Infrastructure Task 2719 includes determination of the approach to be used and participants to be involved. Verification that the organization structure satisfies production scheduling capability requirements is established. The production scheduling organization should also be internally consistent. The organization should be confirmed with subject matter experts to finalize the organization infrastructure.

Step 2750 - Design Performance Enhancement Infrastructure:

In this step, a performance enhancement infrastructure is designed. The training needed for new production scheduling functions is determined, as are 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.

These tasks include Assessing Employee Competency and Performance 2751 , Determining Performance Enhancement Needs 2753, Designing Performance Enhancement Products 2755, Defining a Learning Test Approach 2757, and Verifying and Validating The Performance Enhancement Infrastructure 2759. The products of this step include a performance enhancement infrastructure.

Task 2751 : Assess Employee Competency and Performance

Task 2751 includes assessment of the competency of the current production scheduling staff based on the competency model developed by task 2713. The understanding of the current production scheduling staff's competency proficiency levels and performance levels in specific areas should be refined. Also, the gaps in competencies and performance levels which will drive the design of the performance enhancement infrastructure should be assessed.

Task 2753: Determine Performance Enhancement Needs Task 2753 includes using the employee assessment 2751 to determine the type of performance enhancement required to close the gaps and to reach the desired competency levels. The performance support and training requirements necessary to close the competency and performance gaps in the workforce should be assessed. If a package is used, or re-used, vendor training is available. This is generally the lowest cost approach, although quality of materials may be a concern if the staff is new or unfamiliar with the software and extensive training is required.

Task 2755: Design Performance Enhancement Products Task 2755 includes determination of the delivery approaches for training and performance support. The learning and performance support products are designed, and the support systems for delivering training and performance support are defined. The scope of procedural training depends on the requirements and activities set up for the scheduling function in the prior analysis (2751 ) and design (2753) tasks.

Task 2757: Define Learning Test Approach Task 2757 includes identification of which learning objectives are to be tested and of the data capture methods that are to be used to test those objectives. This helps to develop a comprehensive approach for testing the learning products with respect to achieving each product's learning objectives. The objectives should relate to the Scheduling Performance Model 2419 and Employee Competency Model 2713.

Task 2759: Verify and Validate Performance Enhancement

Infrastructure

Task 2759 includes simulation of the processes and activities performed by the members of the production scheduling team in order to identify performance enhancement weaknesses. Also, the problems are identified, and the appropriate tasks necessary to address the problems are repeated. It should be determined how well the performance enhancement infrastructure and the learning test deliverables fit together to support the new production scheduling capability. These procedures finalize the Performance Enhancement Infrastructure.

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: Analysis of Technology Requirements 3510, Selection And Design of

Operations Architecture 3550, and Validation of Technology Infrastructure 3590. When these steps are performed in conjunction with the design steps 2410, 2710, and 2750, the planning stage 104 of the project will be complete.

Step 3510 - Analyze Technology Infrastructure Requirements: In step 3510, technology infrastructure requirements for production scheduling are analyzed. The goal is to prepare for the selection and design of the technology infrastructure and to establish preliminary plans for technology infrastructure product testing. Figure 5 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiment of the invention. These tasks include Preparing Technology

Infrastructure Performance Model 3511 , Analyzing Technology Infrastructure Requirements 3513, Analyzing Technology Infrastructure Environment 3515, and Planning Infrastructure Technology Test 3517. The products of this step include operations architecture component requirements, a physical model of the operations architecture, and a product test approach and plan.

Task 3511 : Preparing Technology Infrastructure Performance Model Task 3511 includes identification of the key performance indicators for production scheduling. Baseline estimates are established, and measurable targets for the performance indicators are set. Functional, physical, and performance models for scheduling are developed. This will preferably involve analysis of the functional, technical, and performance requirements for the production scheduling infrastructure. There are key issues which should be addressed at this step. These issues should be resolved as soon as possible.

If an automated scheduling solution appears to be required, the key business criteria for software selecting should be determined. It may be assumed that custom development of a production scheduling system is not a viable option, although limited modifications to reuse or packaged software may be considered. Therefore, the key technology component of production scheduling requirements may be the actual scheduling software itself.

If the organization has already purchased a production scheduling package, a need for reuse may be strongly indicated. If the business capability requirements suggest a change to other software, a strong business case is needed to support the recommendation.

Task 3513: Analyze Technology Infrastructure Component Requirements Task 3513 includes identification of any constraints imposed by the environment and refinement of functional, physical, and performance requirements developed in the models previously built. The interfaces to other OM components are assessed to avoid redundancy and to ensure consistency and compatibility. This will give a clear representation of production scheduling component requirements.

Since there are several scheduling packages available, all with different features and capabilities, this task focuses, identifies, and prioritizes the factors that are used to analyze, compare, and select the optimum package. Depending on the environment and infrastructure requirements, the scheduler may need to interact with packages that handle backup/restore, performance management, configuration management, software/data distribution, and asset/inventory management.

Task 3515: Assess Technology Infrastructure Current Environment Task 3515 includes documentation and analysis of the current production scheduling technology environment. The areas where gaps exist between the current infrastructure and the new requirements are identified, as are the restrictions or potential conflicts between the new components and the existing infrastructure. Any standards or policies regarding production scheduling technology and any potential areas of reuse of current components are noted. This assessment provides for production scheduling gap analysis. A clear picture of current standards for technology infrastructure should be obtained as a result.

Task 3517: Plan Technology Infrastructure Product Test Task 3517 includes the definition of the test objectives, scope, environment, and test conditions as well as expected results. The deployment plan is developed. The results of this task provide the basis on which the product test 5590 is performed as well as the environment in which it is run, including the test approach, test plan and deployment plan. The product test is a test of the infrastructure. Therefore, the organization and process elements are within the scope of the test.

Step 3550 - Select and Design Operations Architecture: Once the infrastructure requirements have been analyzed, the operations architecture is selected and designed in step 3550. Figure 8 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiments of the invention. These tasks include Identifying Operations Architecture Component Options 3551 , Selecting Reuse Operations Architecture Components 3552, Selecting Packaged

Operations Architecture Components 3553, Designing Custom Operations Architecture Components 3555, Designing and Validating Operations Architecture 3557, and Developing Operations Architecture Component and Assembly, Test Plan and Approach 3558. The products of this step include a production scheduling operations architecture design as well as component and assembly test approaches and plans.

Task 3551 : Identify Operations Architecture Component Options

Task 3551 includes identification of all risks and gaps that exist in the current production scheduling environment. Components that should support the production scheduling architecture are selected, and current software resources, packaged software, and custom software alternatives are considered during this selection process. Specific component options that are needed to support the production environment are preferably identified. If packaged software is part of the solution, RFPs are submitted to vendors for software products that meet basic requirements.

Component options include production scheduling software packages which fit the basic requirements that were established in the prior tasks.

Some packages may be eliminated, based on factors such as lack of fit with the operating system(s), server(s), or other operations architecture components already in place. Comparative analysis should be performed by prioritizing and ranking the requirements based on what is most important to the organization. It may be desirable to assign a numerical rating for how well each component option supports the given requirement, e.g., 0 = does not support, 1 = partially supported, 2 = supported in full. A requirements matrix may then be built for completing this task. Short lists may be created that group component options into reuse, package, and custom categories as applicable. It is desirable to carry forward three or fewer options in each category into the selection process. These options are contained in a production scheduling component summary. For each component, selection tasks 3552, 3553, and 3555 are carried out.

Task 3552: Select Reuse Operations Architecture Components Task 3552 includes evaluation of the reuse component options, determination of possible gaps where the software does not satisfy requirements, and selection of the appropriate reuse components. It should be identified whether there is any opportunity to reuse existing architecture components such that component selection can be finalized. This task can be done in tandem with the package task 3553 and custom task 3555. The select reuse components task may not be required. If the organization already has change-request handling software in place, the organization may undertake only a production scheduling project in order to replace the old system. In this case, reuse is not a possibility. This task is preferred when an organization wants to install new request handling software, but wants to use an existing report writer for production scheduling reporting. The issue then is the compatibility of the report writer with the production scheduling database.

Task 3553: Select Packaged Operations Architecture Components Task 3553 includes evaluation of the packaged component options against the selection criteria. Vendor demonstrations and site visits are conducted. Any gaps where the software will not satisfy requirements are determined so that the appropriate packaged components are selected.

Packaged software is the primary alternative for production scheduling component requirements. Selection of a component is based on how well the options fit the requirements, the level of vendor support and cooperation, and cost factors. Site visits to other organizations using the software components are desirable to verify the vendors' claims of functionality and to obtain independent opinions about vendor support and cooperation. This task as well as task 3552 result in evaluation summaries of components and component gap analysis.

Task 3555: Design Custom Operations Architecture Components

Task 3555 includes design and validation of custom components. Time, cost, and risk associated with custom development are evaluated such that the custom components are selected. A reuse or packaged component may also be customized. Custom design may be needed to extend the capabilities of the packaged software for key requirements. The types of extensions which are encountered in production scheduling may include interfaces which collect, format, and transport data either from the scheduler to another application, or from another application to the scheduler; customized screens used to input scheduling parameters for particular jobs or groups of jobs; and customized reporting of scheduling information, if the scheduler does not provide it.

Task 3557: Design and Validate Operations Architecture

Task 3557 includes combination of the reuse, package, and custom components from tasks 3552, 3553, and 3555, into an integrated design. It is ensured that the architecture meets the production scheduling requirements. Also, the standards and procedures for component build and test are defined. This helps to develop a high-level design of the production scheduling architecture. Prototyping and testing may be considered if there are complex interfaces to the other components of the operations architecture.

Task 3558: Develop Operations Architecture Component And Assembly, Test Approach and Plan Task 3558 includes definition of the approach and test conditions for the production scheduling architecture assembly, component, and component acceptance test approaches and plans. Individual definitions are provided for the following parameters: Objectives, scope, metrics, regression test approaches, and risks associated with each test; Component testing for custom and customized (reuse or package) components; Component acceptance testing for new packaged components; And assembly testing for the components and interfaces.

There are some preferred aspects of production scheduling component and assembly testing. The customized extensions to the software are preferably tested in component and assembly testing. The interfaces of the scheduler to other operations architecture software are preferably tested in assembly testing. The automated features of the scheduler that are used in the production environment are preferably tested during assembly testing. Automated features may include the ability to schedule multiple jobs in succession, dependencies between jobs, auto start of jobs based on such things as dates, times, cycles, specific events. Test cycles should be designed to take these features into account. Step 3590 - Validate Technology Infrastructure:

In step 3590, verification is established that the production scheduling design is integrated, compatible, and consistent with the other components of the Technology Infrastructure Design. The compatibility and consistency of the design with the Business Performance Model and Business Capability

Requirements is also verified. Figure 9 shows a representation of the tasks for carrying out these functions. These tasks include Reviewing and Refining Technology Infrastructure Design Environment 3591 , Establishing Technology Infrastructure Validation Environment 3593, Validating Technology Infrastructure Design 3595, and Analyzing Impact and Revising Plans for

Technology Infrastructure 3597. The products of this step include production scheduling infrastructure design, a product test plan, and deployment test approach and plan.

Task 3591 : Review and Refine Technology Infrastructure Design Task 3591 includes testing that production scheduling is integrated and consistent with the other components of the technology infrastructure. An issue list is developed for design items that conflict with the infrastructure or for items that do not meet performance goals or requirements. The production scheduling infrastructure is refined if needed using the issue list, or "punch list". The strategic direction of technology should be considered, including issues such as company strategy and policies, state of the art, etc.

Task 3593: Establish Technology Infrastructure Validation Environment

Task 3593 includes establishing the validation environment. Participants are selected and trained. The validation is scheduled once it is designed and built for the technology infrastructure. Designers and architects of OM components that interface with Production Scheduling are preferably included in the validation.

Task 3595: Validate Technology Infrastructure Design Task 3595 includes validation of the design and the recording of issues as they arise. Critical gaps between the production scheduling infrastructure design 3591 and the technology infrastructure requirements 3510 are identified and resolved through an iterative process. Action plans are developed for less critical issues.

If a scheduler is installed as part of a larger business capability, it is used as a checkpoint to verify that the most current requirements from the business capability release are being considered. The scheduler may be installed to control all batch processing on a given platform set, and the resulting production scheduling design must also take this into account.

Task 3597: Analyze Impact and Revise Plans for Technology Infrastructure

Task 3597 includes analyzing both the associated scope of work required for modifications and enhancements and the impact of validation outcomes on costs and benefits. Plans for subsequent deployment testing are refined. The appropriate technology infrastructure delivery plans should be updated based on the outcome of the validation process 3595. The result of this task should be a deployment plan, a test approach, and a test plan, as well as an infrastructure design.

Production scheduling itself may only be part of the validation scope. Although it may be deployed in a single release, a different deployment strategy may be appropriate as a result of the validation. All plans should be prepared accordingly with their respective parts such as third party vendors, outsourcers, etc.

To conclude the "capability release design stage" 104 of the project, the project team presents the recommended designs and infrastructure for management and stakeholder approval 112. This action will, in turn, determine the tactics utilized in the development and implementation of the actual production scheduling infrastructure. In the third stage, the "capability release build and test stage" 106, the project may proceed along three lines. One 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 may develop learning products 6260, and other groups or personnel may develop policies, deprocedures 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 5590. With these tasks completed, the remaining step is the deployment 7170 of the new system.

Step 5510 - Acquire Technology Infrastructure:

In step 5510, any Production Scheduling components which must be acquired will be procured. If choices are available, it will be decided who will supply the components and services and how they will be supplied. This task package is preferably utilized if new packaged software is to be procured and installed as part of the project. Figure 10 shows a representation of the tasks for carrying out these functions according to the presently preferred embodiment of the invention. These tasks include Initiating Acquisition of Technology Infrastructure Components 5511 , Selecting and Appointing Vendors 5513, Evaluating Deployment Implications of Vendor Appointments

5515, and Preparing and Executing Acceptance Test of Technology Architecture Components 5517. The products of this step include production scheduling components and component acceptance test models.

Task 5511 : Initiate Acquisition of Technology Infrastructure

Components

Task 5511 includes definition of vendor selection criteria and selection potential vendors. RFP/RFQ documents are prepared and issued to selected vendors. This initiates the process for selecting and obtaining the production scheduling packaged software components. The process is smoothed if component capability and performance requirements are clearly defined in the documentation provided to vendors.

Task 5513: Select and Appoint Vendors Task 5513 includes evaluation of responses to RFP/RFQ documents.

The selected component(s) and desired vendor(s) are identified, and this allows for negotiation of procurement terms. The placement of contracts and orders are managed through component delivery. The selected vendors provide the production scheduling components according to the terms of the procurement. Software training may be negotiated as part of the contractual agreement. If multiple components and multiple vendors are involved, the delivery and installation of the components preferably occur simultaneously so that the component interfaces are tested with vendor representatives on site.

Task 5515: Evaluate Deployment Implications of Vendor Appointments

Task 5515 includes comparisons of procurement costs with project estimates and assessment of the impact on business case and business performance model. Revisions and approvals should be accomplished as necessary. It is preferably ensured that the economics of the transaction is consistent with plans documented in the business case. The business case may be modified as appropriate to reflect the changes.

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

Task 5517 includes building the test scripts, the test drivers, the input data, and the output data in order to complete the technology architecture component acceptance test model. The test is then executed, and any remedies or changes required of the component vendor(s) are documented. This ensures that the production scheduling packaged components meet the technology infrastructure requirements. Software component training may be scheduled and conducted as soon as the new production scheduling components are installed.

Step 5550 - Build and Test Operations Architecture:

Having acquired the technology, step 5550 proceeds to design and program the production scheduling components, including extensions to reused and packaged items. This is also the time to perform component and assembly testing. Figure 11 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiments of the invention.. These tasks include Performing Operations Architecture Detailed Design 5551 , Revising Operations Architecture Component and Assembly

Test Approach and Plan 5552, Building Operatiohs Architecture Components 5553, Preparing and Executing Component Tests of Custom Operations Components 5555, and Preparing and Executing Operations Assembly Test

5557. The products of this step include production scheduling software components, and test models for components and assembly.

Task 5551 : Perform Operations Architecture Detailed Design Task 5551 includes preparing program specifications for custom and customized components, designing the packaged software configuration, and conducting detailed design reviews. This allows for definition of the requirements and program specifications related to each production scheduling component. Custom components may include interfaces to other OM components and special reporting requirements for production scheduling. If data needs to be transferred between the scheduler and other programs, the transfer files and custom programs to facilitate the transfer are designed. It is also appropriate to consider reporting needs which have arisen since the design phase.

Task 5552: Revise Operations Architecture Component and Assembly

Test Approach and Plan

Task 5552 includes reviewing the test approaches and plans and revising for new or updated requirements as needed. In this manner, the production scheduling test plans are updated to reflect the components' detailed design. Revised considerations or changes to the requirements are defined. If other OM components interface with production scheduling software, these interfaces should be tested, either in this step or in the product test step 5590.

Task 5553: Build Operations Architecture Components Task 5553 includes building the custom components as well as the extensions to packaged or reuse components. The packaged components are then configured. Some packages may have unique or proprietary languages for customizing and/or configuration. In these cases, training time may be necessary, and this may be subcontracted. Task 5555: Prepare and Execute Component Test of Custom Operations Components

Task 5555 includes preparation and execution of tests of the custom operations components that have been built. This testing will ensure that each custom production scheduling component and each customized component meets its requirements. This task verifies the component test model, sets up the test environment, and executes the test. Component fixes and subsequent retests are performed as required. Tests should confirm component performance as well as their functionality. System performance should not be compromised by the amount of customization. These tests are not limited to this stage, but may proceed in subsequent testing tasks.

Task 5557: Prepare and Execute Operations Assembly Test

Task 5557, then, includes the preparation and execution of a test on the entire operations assembly. A full test should be performed of all interactions between production scheduling components. This task verifies the assembly test model, sets up a test environment, and executes the test. Again, fixes and retests are performed as needed, preferably in an iterative fashion. Shell programs or stub programs may be needed to perform the assembly test. If shell programs are used, it is important to test not only successful completion, but to build in the error conditions which would cause abnormal endings or problems. It should be verified that all interfaces to other components are tested and operate correctly for successful, predictable outcomes and for error conditions.

Step 6220 - Develop Policies, Procedures, and Performance Support:

In step 6220, a finalized, detailed set of new production scheduling policies, procedures, and reference materials is produced. It is 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 task, the operating personnel will have Production Scheduling Policies & Procedures and may also have any performance support products that may be necessary or useful. Figure 12 shows a representation of the tasks for carrying out these functions. These tasks include Performing Policies, Procedures and Performance Support Detailed Design 6221 , Developing Business Policies and Procedures 6223, Developing User Procedures 6225, Developing Reference Materials and Job Aids 6227, and Validating and Testing Policies, Procedures, and Performance

Support 6229.

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

Task 6221 includes designing the structure of the new policies, procedures, and support materials, as well as templates for product development. Standards for policy and performance support development are defined, and prototype products are created. These processes lead to standards and templates for production scheduling policy and procedures.

Task 6223: Develop Business Policies and Procedures Task 6223 includes collecting and reviewing content information.

Policies and procedures are drafted, and plans are made for the production of the materials. This provides for a complete set of business policies and procedures for production scheduling. Business policies describe the business rules governing workflows. Business procedures describe the sequential sets of tasks to follow based on the policies. Procedures should generally be organized according to the functions to be performed by the scheduling group. For example, if scheduling takes care of backups and restores, these items should be documented as a separate section.

Task 6225: Develop User Procedures Task 6225 includes collecting and reviewing content information and drafting the user procedures. Consistency of these user procedures with business policies and procedures is verified, and plans are made for the production of the materials. The production scheduling user procedures should be detailed as they provide the steps necessary to enable smooth execution of new tasks within a given business procedure. Documentation of the appropriate actions in response to problems or breakdowns should be provided. The ability to recover quickly is critical when the batch processing window is short or when batch work overlaps with on-line activity and needs to be completed rapidly to avoid degrading on-line response.

Task 6227: Develop Reference Materials and Job Aids Task 6227 includes collecting and reviewing content information, drafting the performance support products, verification of consistency with policies and procedures, and planning for the production of the materials. The reference materials and job aids that make a task easier or more efficient should be drafted. The information provided in the reference materials and job aids is typically difficult to memorize, but is used frequently on the job. Performance support materials are used in environments where production scheduling 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

Task 6229 includes preparation of validation scenarios and validation of content and of the ease of use of materials. On-line support products are tested, and any open issues should be resolved. The products that have been developed should meet the requirements of the production scheduling capability and the needs of the personnel who will use them.

Step 6260 - Develop Learning Products:

In step 6260, a complete, finalized set of learning products are created. Though not strictly a part of project hardware building, a successful project will typically include some thought to training its users. Technical training in Production scheduling 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. Figure 13 shows a representation of the tasks for carrying out these functions, according to the presently preferred embodiment of the invention. These tasks include Developing Learning Product Standards and Development

Environment 6261 , Performing Learning Program Detailed Design 6263, Prototyping Learning Products 6265, Creating Learning Products 6267, and Testing Learning Products 6269.

Task 6261 : Develop Learning Product Standards and Development Environment Task 6261 includes selecting tools for authoring and development, defining standards, and designing templates and procedures for product development. This helps to create the environment for developing the production scheduling learning products. Technical training in production scheduling software components may come from the package vendor or a third party training organization. Procedural training aids are preferably custom built.

Task 6263: Perform Learning Program Detailed Design Task 6263 includes definition of learning objectives and context, design of the learning activities, and preparation of the test plan. It should be specified how each learning product identified in the learning product design is to be developed. The design may be modularized by separating the production scheduling activities into separate learning products. Integration of the use of the production scheduling software into the learning program may be accomplished, preferably after technical software training is complete.

Task 6265: Prototype Learning Products

Task 6265 includes the actual creation of prototype components combined with an evaluation of the prototype. Ease-of-use sessions should be conducted on classroom-based learning components, i.e., activities, support systems, instructor guides.

Task 6267: Create Learning Products

Task 6267 includes development of activities, content, evaluation and support materials required as well as a maintenance plan. Instructors and facilitators are trained, and arrangements are made for production. This develops the learning materials proposed and prototyped during the design activities. Task 6269: Test Learning Products

Task 6269 includes confirmation and execution of the learning test. Any required modifications are assessed, reviewed, and carried out. Each product should be tested 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 production scheduling. If the target production scheduling audience is small enough, 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 the 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 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 production scheduling 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 production scheduling, 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

Task 5591 includes creation of the test data and expected results as well as testing scripts for production, deployment, and configuration tests. The production scheduling training not yet completed is conducted. The production scheduling infrastructure test model is then reviewed and approved. If a complete business capability is being deployed, the test should be comprehensive with production scheduling being one piece. The product test should occur in a production-ready environment and should include the hardware and software to be used in production. If production scheduling is being implemented independently, then all or a portion of the production environment can be used as the 'test' application.

Task 5593: Execute Technology Infrastructure Product Test Task 5593 includes executing the test scripts, verifying the results, and making changes as required. This helps to verify that the technology infrastructure successfully supports the requirements outlined in the business capability design stage. It is preferable to simulate the actual production scheduling working conditions, including related manuals and procedures.

Task 5595: Execute Technology Infrastructure Deployment Test

Task 5595 includes execution of the test scripts and verification of the results. Changes are made as required. The new production scheduling infrastructure should be correctly deployed within the organization.

Deployment testing and configuration testing 5597 are usually minimal for production scheduling, since it is a behind-the-scenes application with limited visibility to the majority of the organization.

Task 5597: Execute Technology Infrastructure Configuration Test Task 5597 includes execution of the test scripts and verification of the results. Changes are made as required, as are updates to the risk assessment. The performance of the technology infrastructure, including production scheduling, should be consistent with the technology infrastructure performance model after the infrastructure has been deployed.

To conclude the "capability release build and test stage" 106 of the project, the test findings and recommendations are presented to the stakeholders for their approval 114. This task is very desirable for maintaining management awareness of and commitment to production scheduling efforts. ln the fourth stage, the "deployment stage" 108, the technology infrastructure is deployed by function 7170.

Step 7170 - Deploy Technology Infrastructure:

Following successful testing, the production scheduling 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 production scheduling members, 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 production scheduling is being installed independently.

Task 7171 : Configure Technology Infrastructure Task 7171 includes reviewing the customization requirements and performing any necessary customization. The resulting infrastructure configuration is verified. Customization of the deployment unit's technology infrastructure prepares for the new business capability components. This task is generally required if the production scheduling capability is being deployed at more than one site. In these cases, variances in the existing configurations determine any customization required.

Task 7173: Install Technology Infrastructure

Task 7173 includes preparation of the installation environment, installation of production scheduling infrastructure, and verification of the installation. In addition to the production scheduling software, the documentation, performance support tools and training are completed and put in place prior to the deployment. Since production scheduling is a behind-the- scenes capability, the deployment may occur without the fanfare of a more highly visible capability. This does not diminish the importance of executing the deployment properly, with adherence to applicable standards and procedures in place within the sponsoring organization.

Task 7179: Verify Technology Infrastructure

Task 7179 includes performing the infrastructure verification, making changes as required, and notifying stakeholders. This verifies the new technology infrastructure environment and addresses the issues raised as a result of the testing. This task requires minimal effort if production scheduling is being installed independently.

In addition to the method for providing the production scheduling function, as described above, the present invention also includes a method and apparatus for providing an estimate for building a production scheduling 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 production scheduling in an information technology system. In Fig. 16, a provider of a production scheduling 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.

Table 1

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.

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 production scheduling 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 or 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 Figures 17a-b.

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 enterprises may benefit from the use of this invention, e.g., any enterprises wishing to use a production scheduling function within an information technology organization. In addition, there are many different types of computer systems, and computer software and hardware, which 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 a production scheduling function in an IT organization comprising:

(a) planning for said production scheduling function; (b) designing said production scheduling function;

(c) building said production scheduling function;

(d) testing said production scheduling function; and

(e) deploying said production scheduling function.

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

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 production scheduling capability;

(j) identifying a plurality of best practices for said production scheduling;

(k) defining a plurality of requirements for said production scheduling; 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 production scheduling function.

5. The method of claim 4 wherein said designing act includes: (g) designing a plurality of workflows for processes, activities, and tasks for said production scheduling;

(h) identifying physical environment interactions; (i) identifying skill requirements for performing said production scheduling; (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 production scheduling function.

7. The method of claim 6 wherein said designing act 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 production scheduling function.

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

(g) assessing employee competency and performance for production scheduling;

(h) determining performance enhancement needs;

(i) designing performance enhancement products;

0^') 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 production scheduling function.

11. The method of claim 10 wherein said designing act 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 production scheduling function.

13. The method of claim 12 wherein said designing act 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 production scheduling function.

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 production scheduling function.

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 production scheduling function.

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 production scheduling function.

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 production scheduling.

25. The method of claim 24 wherein said testing act 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 scheduling.

27. The method of claim 26 wherein said deploying act 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 production scheduling function in an information technology organization, the method comprising:

(a) obtaining a plurality of estimating factors;

(b) determining a difficulty rating for each of said estimating factors; generating a time allocation for building said production scheduling based on said estimating factor and said difficulty rating; and generating a cost for building said production scheduling 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 business units, job streams, platforms, scheduling groups, total users, software components, and organizational readiness for change.

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 production scheduling 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 production scheduling 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 production scheduling 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 production scheduling; and

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