WO2001025876A2 - Technique et estimateur pour la modelisation et la planification de la capacite - Google Patents

Technique et estimateur pour la modelisation et la planification de la capacite Download PDF

Info

Publication number
WO2001025876A2
WO2001025876A2 PCT/US2000/027795 US0027795W WO0125876A2 WO 2001025876 A2 WO2001025876 A2 WO 2001025876A2 US 0027795 W US0027795 W US 0027795W WO 0125876 A2 WO0125876 A2 WO 0125876A2
Authority
WO
WIPO (PCT)
Prior art keywords
planning
capacity
modeling
capacity modeling
designing
Prior art date
Application number
PCT/US2000/027795
Other languages
English (en)
Other versions
WO2001025876A3 (fr
Inventor
William C. Bond
Original Assignee
Accenture Llp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Accenture Llp filed Critical Accenture Llp
Priority to AU80017/00A priority Critical patent/AU8001700A/en
Publication of WO2001025876A2 publication Critical patent/WO2001025876A2/fr
Publication of WO2001025876A3 publication Critical patent/WO2001025876A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/80—Management or planning

Definitions

  • IT Information Technology
  • a major challenge in Information Technology (“IT”) development is not the technologies, but rather the management of those technologies in a complex business environment. IT activities must be managed collectively and include idea conception, strategy development, capability delivery, planning, administration, operation, coordination of project requests, change administration, and managing demand for discretionary and non-discretionary activities and operations.
  • the technological and business environment demands a shared understanding and representation of IT management.
  • a technological management orientation needs ways to plan, assess, and deploy technology within and across enterprises. Business needs to balance technological capability with enterprise capability in order to become or stay a competitive organization.
  • the IT framework must be a single framework for describing IT management.
  • the IT framework also needs to be a framework of all functions, representing a complete checklist of all relevant activities performed in an IT enterprise.
  • a single IT Framework should represent all functions operative in an IT enterp ⁇ se.
  • one embodiment of the invention is a method for providing capacity modeling and planning that includes planning, designing, building, testing, and deploying a capacity modeling and planning function for an IT organization.
  • the planning step preferably includes developing a business performance model.
  • the designing step preferably includes designing business processes, skills, and user interaction, and may also include designing an organization infrastructure, designing a performance enhancement infrastructure, and designing technology infrastructure and operations architecture.
  • the building step preferably includes building the technology infrastructure, building the operations architecture, business policies, procedures, performance support, and developing learning products for the capacity modeling and planning.
  • the testing step preferably includes testing the technology infrastructure, and testing the operations architecture for capacity modeling and planning.
  • the developing step includes deploying the technology infrastructure for the IT enterprise.
  • Another aspect of the present invention is a method for providing an estimate for building a capacity modeling and planning 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 capacity modeling and planning function in an information technology organization.
  • Figure 1 shows a representation of the steps in a method for providing a capacity modeling and planning function according to the presently preferred embodiment of the invention.
  • Figure 2 shows a representation of the tasks for selecting delivery options for the method represented in Figure 1.
  • Figure 3 shows a representation of the tasks for surveying packaged software candidates for the method represented in Figure 1.
  • Figure 4 shows a representation of the tasks for developing a capacity modeling and planning Request for Proposal for the method represented in Figure 1.
  • Figure 5 shows a representation of the tasks for selecting packaged software for the method represented in Figure 1.
  • Figure 6 shows a representation of the tasks for developing capacity modeling and planning methods design for the method represented Figure 1.
  • Figure 7 shows a representation of the tasks for designing capacity modeling and planning organization for the method represented in Figure 1.
  • Figure 8 shows a representation of the task for designing capacity modeling and planning performance enhancement for the method represented in Figure 1.
  • Figure 9 shows a representation of the tasks for developing a target process design for the method represented in Figure 1.
  • Figure 10 shows a representation of the tasks for building and testing target processes for the method represented in Figure 1.
  • Figure 11 shows a representation of the tasks for deploying technology infrastructure for the method represented in Figure 1.
  • Figure 12 shows a flow chart for obtaining an estimate of cost and time allocation for a project.
  • Figures 13a and 13b show one embodiment of an estimating worksheet for an Operations Management Capacity Modeling and Planning Estimating Guide.
  • an IT enterprise may be a business, charitable, government, another organization, and the like that uses an information technology system with or to support its activities.
  • An IT organization is the group, associated systems, and processes within the enterprise that are responsible for the management and delivery of information technology services to users in the enterprise.
  • the IT enterprise has an IT framework for understanding the interrelationships of the various functionalities and for managing a complex IT organization.
  • the IT framework may include various operations management functionalities such as (1) a customer service management system function, (2) a service integration system, (3) a service delivery function, (4) a capability development function, (5) a change administration function, (6) a strategy, architecture, and planning function, (7) a management and administration function, (8) a human performance management function, and (9) a governance and strategic relationships function.
  • capacity modeling and planning plays an important role.
  • the invention is directed toward a method and estimator for providing a capacity modeling and planning function in an IT framework.
  • the strategy, architecture, and planning function creates a strategy and plan that outlines the overall IT capability direction, initiatives, and common IT processes, organizations, applications, and technology architecture required to support desired business capabilities with optimal efficiency.
  • the strategy and plan are accomplished by working with the enterprise and business unit strategy teams and by analyzing technology industry trends.
  • the strategy, architecture, and planning function provides technology guidance to the broader enterprise through the definition of common application and technology architecture blueprints.
  • the application and technology architecture blueprints include the IT organization, IT process architectures, application architectures, and delivery vehicle architectures (development, execution, operations and physical network, and computing environments) required to enable the business capabilities.
  • the strategy, architecture, and planning function aligns the IT enterprise with the business and increases the value, interoperability, and reuse of IT initiatives. Additionally, the strategy, architecture, and planning function evaluates, prioritizes, and plans for the recovery of critical business systems through a risk management function.
  • the strategy, architecture, and planning function focuses on planning and balancing long-term, strategic initiatives with quick-win business opportunities. Day-to-day operational and administrative tasks are addressed within the service delivery and the management and administration functions.
  • the strategy, architecture, and planning function includes strategic planning, capability planning, and risk management.
  • Strategic planning provides a long-term strategic direction for the IT enterprise and may be for a term of three to five years.
  • Capability planning defines application and technology architectures and key business continuity and protection plans needed to deliver and enable the core business capabilities.
  • Risk management encompasses functions aimed at identifying and securing enterprise assets against various forms of business interruption or loss.
  • Capability planning works with the strategic planning and quality management functions to ensure people and processes are in place to facilitate the interoperability of business capability IT solutions and to ensure consistent IT strategy implementation. Capability planning further ensures the technologies used by the enterprise also enable the pursuit of business objectives and capabilities. Capability planning also ensures the employment of sound operations and security practices. Capability planning includes several functions or tasks such as process planning, organization planning, application architecture planning, data architecture planning, technology architecture planning, capacity modeling and planning, and architecture standards and compliance. Process planning defines the key IT processes and related performance requirements required to implement the overall IT function. Organization planning defines the organization required to support information technology processes. Application architecture planning defines applications, application requirements, the performance model, and application distribution approach needed to enable the business capabilities.
  • Data architecture planning defines the data, data definitions, a performance model, and data distribution approach needed to enable the business capabilities.
  • Technology architecture planning defines the technology architecture blueprints and performance model required to enable application blueprints to deliver business capabilities. Capacity modeling and planning ensures appropriate system resources are available to handle business workloads and enable business capabilities and that service level targets are reached.
  • Architecture standards and compliance establishes the standards and guidelines for technology and architecture related items in the IT enterprise, including software, hardware, and configurations.
  • Capacity modeling and planning ensures appropriate system resources are available to handle the business workloads and enable business capabilities.
  • the appropriate system may include computing, networking, and a combination or combinations.
  • Capacity modeling and planning also ensures service level targets are reached. This function ensures enough physical facility is available to house resources and enough people are available to manage those resources.
  • Capacity modeling and planning may include a business definition and requirements planning task, a resource data gathering task, a capacity modeling task, a capacity plan development task, and a plan implementation and maintenance task.
  • the business definition and requirement planning task defines key business requirements and business drivers to determine what IT resources are needed for a specific application during a given time frame.
  • the resource data gathering task collects key data for building a capacity model and performing capacity planning.
  • the information for data gathering comes from a variety of sources, both manual and automated. Historical and current data are gathered to understand resource utilization trends, identify peak process periods, and plan for future processing demands. Accuracy is one of the most important aspects of data gathering. The accuracy of data directly impacts the accuracy of the capacity model and the quality of the capacity plan.
  • the capacity modeling task uses automated tools to build a model of the application and identify the system on which the application is running.
  • the capacity modeling tool identifies the optimal hardware, software, and communications configuration needed to meet desired service levels for expected workloads.
  • the capacity plan development task summarizes the configuration strategies of the capacity modeling efforts and creates the capacity plan report.
  • the capacity plan documents the capacity requirements and resource upgrades required for the coming year.
  • the plan documents are used on an ongoing basis to track actual capacity consumption.
  • the capacity plan implementation and maintenance task presents the results of the capacity plan for a given planning period to management. Once approved, a capacity planning team works with other teams to execute the capacity plan. The team or function continually monitors the actual usage in the business environment and IT production environment. Business workload volumes, levels of performance, and resource utilization are monitored and compared against planned projections to determine variances. The results are reported on a periodic basis to management.
  • Figure 1 is a representation of the task packages that may be included in one embodiment of a method for providing a capacity modeling and planning function.
  • the task packages are shown in essentially a time sequence for a project having a managing phase and a delivery phase. However, the invention is not limited to carrying out these tasks in the particular sequence shown.
  • the managing phase includes plan project evaluation, organize project resources, control project work, and complete project.
  • the delivering phase includes capability analysis stage 102, a capability release design stage 104, a capability release build and test stage 106, and a deployment stage 108.
  • the project may have milestones including plan delivery approval 110, authorization to build and test 112, and authorization for deployment 114.
  • the method for providing an operations management (OM) capacity modeling and planning function includes steps involved in building, but not running this particular OM function.
  • OM specific tasks are extensions of a business integration methodology, and provide additional detail to the steps required to build the OM specific function.
  • the business integration methodology includes task packages covering analysis, design, build & test, and deployment. Each OM function is made up of process, organization, and technology elements that are addressed through the OM methods by appropriate task packages and tasks to create a comprehensive solution.
  • Figure 2 is a representation of the task package to select delivery options 2210.
  • This task package includes the following tasks: assemble standard capacity modeling and planning methods 2211 , refine requirements 2213, create a strawman framework 2215, finalize delivery requirements 2217, and develop an overall capacity modeling and planning framework 2218.
  • This task package defines the scope and direction of the development effort related to deployment of a capacity modeling and planning framework within an IT organization.
  • the framework outlines the approach used for future workload forecasting efforts aimed at projecting capacity requirements.
  • the goal of this task package is to deliver a capacity management framework.
  • the major activities required for a capacity modeling and planning project may be summarized in the following steps:
  • Steps 1 through 4 are performed to establish the methodology and capabilities needed to develop and maintain capacity models. These steps may be completed only once for a given organization. Steps 5 through 8 are generally repeated for each key business activity until all activities are addressed and the organization has a complete set of models for its entire workload.
  • a modeling tool may be selected that fits the technology environment. The functions and capabilities of the tool then drive the design of modeling approaches to be employed.
  • Some commonly used modeling techniques include trend analysis, analytical modeling, simulation, and benchmarking.
  • Trend analysis uses historical trends to predict future utilization. It is one of the simplest but normally is one of the least flexible and least accurate approaches.
  • Analytical modeling uses mathematical techniques to model system capacity. It . generally provides reasonable results and provides 'what-if capabilities, but with somewhat more effort.
  • the simulation approach models discrete events, frequently allows 'what-if scenarios, and is most accurate for sizing new applications, although it can be very costly and time consuming.
  • the benchmarking approach uses live data and resources to model the workload and develop projections. It is most accurate for comprehensive modeling. However, simulation usually requires an organization's production system to be shutdown during the benchmark, which may not be acceptable.
  • the modeling environment may be simplified if the organization accepts a recommended modeling software and standard methodology.
  • a "strawman" framework would require fairly limited modifications. However, considerable work effort may be needed to establish the environment if the organization requires modifications or selects another software option.
  • Net-centric considerations may affect the development of a capacity management framework. Issues such as global accessibility, 24X7 availability (available 24 hours per day, 7 days per week), unpredictability of users actions, and net-centric data types add unique considerations to capacity planning. These considerations may be technology-specific and not process- related. However, they may affect tools, processes, and scope of the capacity planning process.
  • Net-centric or “network centric” includes various means of reaching others (customers, clients, and the like) with computing systems over a communications structure, such as an intranet, extranet, or internet connection.
  • the types of applications required by a net-centric computing system may be described by a framework.
  • Application logic may be packaged into components and distributed from a server to a client over a network connection between the client and server.
  • the client may have standardized interfaces.
  • An application may execute with a client that can run on multiple operating systems and hardware platforms.
  • Net-centric frameworks may support a style of computing where processes on different machines communicate using messages.
  • client processes delegate business functions or other tasks (such as data manipulation logic) to one or more server processes.
  • Server processes respond to messages from clients.
  • Business logic can reside on both the client and server.
  • Clients typically are personal computers and workstations with a graphical user interface running a web browser.
  • Servers may be implemented on UNIX, NT, or mainframe machines.
  • “fatter” clients often result from new technologies such as Java and ActiveX.
  • technology, people, and processes may be distributed across global boundaries. Business functions and systems may involve multiple organizations. This generally adds complexity to the systems.
  • Net-centric considerations include net centric data types, fat servers, thin clients, and push software distribution.
  • Net-centric data types may increase from the introduction of net-centric technologies.
  • Sites may contain images, audio and video clips, Java Applets or ActiveX controls, all of which must be part of traditional backup and restore plans and part of network capacity models.
  • Storage and network capacity planning should allow for the increased size of these file types.
  • Fat servers occur when file access is granted to the broader Internet community. Performance degradation becomes an issue as large numbers of users download files. This is also a consideration as servers deliver full-blown applications to networks of users. Frequent file transfers may cause performance bottlenecks within server hardware, server applications, network pipes, or client access interfaces. Proper capacity planning across all these components should be performed.
  • Figure 3 is a representation of the task package to survey packaged software candidates 2250.
  • This task package includes the following tasks: assess the software market 2251 , define software screening criteria 2252, and select software finalists 2253.
  • This task package selects two or three packaged software vendors as finalists for detailed evaluation. The goals are to provide software selection criteria and to identify the potential vendors having the ability to satisfy key capacity planning requirements with their packaged software products.
  • modeling software is required, the modeling approach selected dictates what the component options are.
  • the modeling approach may be analytic, simulation, and benchmarking.
  • Modeling tools include BEST/1 , Snapshot, DEC Capacity Planner, WinRunner, LoadRunner, SES, and the like. Each modeling tool has unique features and characteristics. However, none of the modeling tools meets all the given sets of requirements and all environments. Also, the scope of the project, whether it be enterprise wide modeling or specific application performance analysis, dictates the options available. Considerable care should be used in identifying the most appropriate options for further analysis.
  • tools are also available which provide for the collection of data to be used in the modeling process.
  • the screening criteria used to select qualifying vendors are those key requirements that are critical to the organization and must be accommodated in the final solution. Vendors not satisfying these criteria need not be considered.
  • FIG 4 is a representation of the task package to develop a capacity modeling and planning request for proposal 2270.
  • This task package includes the following tasks: finalize packaged software selection criteria 2271 , define business scenarios 2272, and prepare and distribute a Request for Proposal ("RFP") 2273.
  • RFP Request for Proposal
  • This task package creates the RFP that is distributed to the packaged software finalists.
  • the completed RFP is used to select the one or more software packages and one or more vendors. There may be more than one RFP.
  • the goal is to provide the RFP.
  • the selection criteria in a distributed client and server environment are aimed at determining what resources are needed, where these resources are located, and what data transmission requirements are between the various locations.
  • the resources may include CPU and memory for the host, clients, and servers, DASD and other storage, LAN and WAN communications, print, and the like.
  • the analysis also considers batch processing separate from on- line processing, including the size of the batch processing window. In some environments, on-line processing may be required on a 24-hour basis, meaning the analysis must consider simultaneous on-line and batch processing, storage, and communications.
  • the approach and toolset employed typically must be capable of satisfying the following requirements, where M is a mandatory requirement and D is a desirable requirement.
  • Database definitions - DB name, number of records, record length, overhead (D).
  • Report simulation results and predictions graphically (D).
  • Business scenarios are a series of short narratives explaining critical packaged software requirements. The business scenarios focus on how a package works, as opposed to what features and functions it contains. Vendors respond to the scenarios by describing how their product meets the requirements. Business scenarios are used to differentiate the vendors' solutions based on functional fit, ease of use, and efficiency.
  • a Request for Proposal may not be required if there are limited choices or time constraints, if there is no desire for a formal evaluation, or if the specifications are understood. If an RFP is required, every effort should be made to define requirements clearly and accurately so responses will be consistent and may be compared on a common basis. Vendors will invariably try to play up key features of their software. Accordingly, it is important to insist on strict adherence to the basic requirements format and the use of supplements or appendices to cover special features. There are several network management considerations of the RFP.
  • the capacity modeling and planning offerings of the network service provider should be reviewed.
  • Some service providers may offer customer access to carrier databases and support facilities that provide an enterprise-wide view of the network.
  • Options for capacity modeling and simulation of the network should be considered, especially if the client is short on resources or skills to perform and maintain the modeling solution and plan.
  • When selecting a tool consider the application architecture may impact the complexity of simulating network traffic. For example, Oracle databases may generate different traffic types depending on how the application is accessed (e.g., x-windows vs. client server vs. emulation). In the product selection, look for tools that use auto-discovery to facilitate creating the initial model of the network. Tools may also have a library of models from which one can be customized to resemble the actual environment.
  • Figure 5 is a representation of the task package to select packaged software 2280 task package.
  • This task package includes the following tasks: evaluate RFP responses 2281 , conduct vendor demonstrations 2282, select finalist and negotiate 2283, confirm costs and benefits 2284, finalize packaged software selection 2285, obtain and install software 2286, document resource utilization measurement requirements 2287, arrange and attend software training 2289, and install and adjust measurement tools 2288.
  • This task package gathers additional information about the packaged software finalists, allowing the evaluation and comparison of the capabilities and functionality of each finalist.
  • a packaged software finalist is selected for each required component and contract terms are negotiated with the one or more vendor. The goal is to provide a packaged software selection and software training.
  • Figure 6 is a representation of the task package to develop capacity modeling and planning methods design 2410.
  • This task package includes the following tasks: design process flows 2411 , develop process descriptions 2412, prepare functional specifications 2413, design data gathering forms 2415, develop detailed flows, procedures, and forms 2417, customize software components 2418, and assemble capacity planning binder 2419.
  • This task package designs capacity modeling and planning processes, functional specifications, and the forms needed for data collection and modeling. The goal is to provide capacity modeling methodology design elements and a capacity planning binder.
  • the approach and documentation are based on the BEST/1 software suite.
  • the approach and documentation includes data collection agents, analysis, and prediction tools.
  • the approach and documentation may be based on other software.
  • a decision to use other software or methods to support capacity planning may entail significant efforts to revise the documentation and standard processes.
  • environmental characteristics and the makeup of the workload may impact the approach to data collection and analysis. It is important to note that in client and server environments, where processing occurs at many nodes, the transmission of data resulting from that processing, commonly known as the Network Traffic, is the most difficult element to define and size.
  • benchmarks may be built and tested for as many of the possible variations as is practical. It may also be possible to circumvent problem cases caused by this situation. Messages greater than a particular size may be intercepted and restricted to overnight delivery. The size may be 5 MB.
  • Capacity modeling and planning design involves analyzing the workloads and workload volumes and developing a modeling approach that best mirrors the production environment in order to produce reasonable projections. In many cases, this is not as simple as input-process-output.
  • An example is where an on-line monitor is used for on-line activity and a DBMS handles the input and output.
  • the set of sub-models or mini-models may include one for the monitor, one for the DBMS, and one for the application itself. This mini-model approach can be used to handle other similar situations as well.
  • Custom components for the capacity modeling and planning may be needed in the following scenarios: the organization requires customized reports (this may be necessary in the majority of cases) multiple tools are selected, and interfaces must be developed; there are essential requirements that cannot be satisfactorily met by either reuse or packaged software; and the decision is made to go with a manual or spreadsheet type of approach (this approach is generally of little value in today's complex environments). Since custom design and development of software is time consuming and expensive, any such decision needs to be carefully evaluated.
  • Form and process design also may be more complex if the solution involves use of more than one tool for capacity modeling and planning. This may occur in large, complex environments where effective planning may produce significant hardware cost savings. This also may occur when the computing and networking components require different tools, which is very common in client and server environments. In these situations, the interfaces between the components must be verified and the overall high level design validated against technology requirements. Prototyping is not required. The capacity modeling and planning software is actually a prototyping tool in itself in many respects, rather than a complex architecture that may need to be simulated before proceeding.
  • Extranet Partners - workflows, activities, and tasks may span multiple organizations for capacity planning;
  • More Frequent Activities - capacity planning activities i.e., update processes, communication processes, reporting processes
  • New Events - in a net-centric environment new events such as push/pull software distribution and content management may influence capacity planning (these new events should be properly integrated into capacity planning processes to ensure they will not have adverse effects on the system).
  • Figure 7 is a representation of the task package to design capacity modeling and planning organization 2710.
  • This task package includes the following tasks: design capacity modeling and planning roles 2711 and document roles and responsibilities 2713.
  • This task package defines what is expected of people who participate in the capacity modeling and planning function, the required competencies for people to perform the function, and how their performance is managed and sustained. The goal is to provide capacity modeling and planning roles and responsibilities.
  • required skills are identified and grouped by workflow processes into the key capacity modeling and planning roles. These roles would normally include overall management of the function, execution of the modeling software, analysis and interpretation of results, and activity reporting and communication.
  • the key jobs normally involved in on-going modeling and monitoring activities include the Capacity Planner, or Planning Manager, and the Planning Analyst.
  • the latter may be individuals or teams, depending on the size of the organization and scope of responsibilities.
  • the role of the capacity planning function is to maintain overall control of the modeling tools and the capacity modeling and planning process. This would include on-going scheduling and execution of capacity modeling and planning activities, control of reporting and monitoring functions, and communicating with IT management regarding capacity issues and problems.
  • the role of the Planning Analyst is to assist application development personnel with capacity modeling and planning issues as new applications or maintenance enhancements are designed, coded, tested, and deployed. Personnel with responsibility for on-going capacity modeling and planning activity need a combination of business management and technology skills.
  • Technology skills include in-depth knowledge of: capacity planning and modeling concepts and techniques; elements making up the environment (Servers, Clients, DASD, communications, etc.); all modeling tools used, and the configuration of the tools at all sites; performance management software in use, and performance reporting; the capacity modeling and planning process and the SLA's in place; and business capability requirements and how they translate to application requirements and then into technology infrastructure processing volumes and system utilization.
  • capacity modeling and planning personnel need common business administration and business management skills, such as the ability to read and interpret the performance reports, analyze and evaluate trends, work effectively with others involved in the process, document problems and issues for resolution, and communicate ideas and recommendations to senior IT and enterprise management.
  • Organizational infrastructure considerations are typically minimal when introducing a capacity modeling and planning function because of the small size and specialized skills of the group.
  • Additional considerations for designing roles, jobs, and teams for Capacity Planning in a net-centric environment include: (1) extranet partners - capacity planning teams may span multiple organizations; and
  • New interaction methods and the large number of potential users may challenge existing capacity planning models.
  • the network service provider may be included on the capacity modeling and planning team.
  • the service provider may often provide tools and experience that can assist in development and maintenance of the physical network plan.
  • Performance enhancement design for capacity modeling and planning may be minimal for the technical modeling and planning staff. Training may almost always be most economical when purchased from the vendors supplying the modeling software, or from other outside firms specializing in this type of training. The same is true for the systems software skills that are needed. For application knowledge, capacity modeling and planning staff will normally receive on-the-job training from application development or maintenance personnel when assigned to a given project. Likewise, desktop aids and other performance support are typically not applicable, as this is a highly analytical function that does not lend itself to quick-reference lookups. The primary training required, therefore, is focused on the methodology used to collect data and develop capacity models for business activities and applications.
  • Network modeling tools typically require significant training to understand the complexities of the tool. Often, vendors offer hands-on workshops with their products. Ensure that there is client buy- in and ownership due to the significant training investment required to operate and maintain modeling tools.
  • Figure 9 is a representation of the task package to develop target process design 6260.
  • This task package includes the following tasks: identify target business activities 6221, define business driver 6222, determine business workloads 6223, establish service level targets 6224, develop target user team training 6227, and confirm target process design 6229.
  • This task package creates the detailed framework for the specific business activities to be modeled. The development of the actual plan document may begin at this point. The goal is to provide capacity planning policies & procedures and capacity plan component drafts.
  • the actual modeling process begins with establishing and agreeing on the overall scope and objectives and the key business functions to be included in the "target" or "pilot' project, the business units involved, and key users and responsibilities within the business unit. It is desirable to express the key functions in business terms rather than system terms. This facilitates communication with the user community and prepares for identification of business drivers using similar terminology. Linking functions with business units and users sets the stage for forecasting, which occurs in subsequent tasks.
  • the business drivers are defined for all functions. The business drivers are the keys to projecting and reporting future growth in utilization. Some typical drivers might include: the number of customers for order entry applications; the number and growth in personnel for human resource systems; and the number of programmers for systems development or application maintenance.
  • drivers are factors used in the modeling process to project capacity requirements. They also may be used in on-going reporting to management. The purpose of this is to relate capacity needs to business factors that may be easily understood and analyzed. The drivers need to be validated to confirm they are good predictors of processing workloads.
  • Target process design also involves determining business workloads.
  • a workload is defined as the transactions performed by a user and the transactions performed by the supporting application(s) to accomplish a business function.
  • Workloads are a key link in translating business function and business driver volume into actual system resource utilization. Accurate and complete mapping of workloads is essential to the modeling and planning process. It can be very time consuming, and typically requires extensive support from users, application developers, and even hardware/software vendors.
  • Capacity modeling and planning may be undertaken to ensure that service levels can be met at the lowest reasonable cost.
  • An understanding of what service levels are included in the scope is critical. The impact of service levels on performance, and therefore on capacity, may be felt in many ways.
  • some form of the 80/20 rule applies - 20% of the applications or transactions generate 80% of the workload volume. Here, it may be appropriate to focus solely on that 20% as being sufficient for modeling.
  • the severity of penalties for failure to meet SL 's (or rewards for over-achievement) influences the portions of the workload to be modeled. This may also influence desired capacity and utilization levels of the production environment (e.g., a 'no down-time' requirement may dictate close to 100% redundancy in the hardware configuration).
  • Net-Centric Service Providers and Service Control Given potential changes in incident frequencies, volumes, interaction methods, and the times they are reported, net-centric service providers and Service Control should readdress support team staffing and forecasting models to ensure that customers are receiving the proper level of support. New interaction methods and the large number of potential users may challenge existing capacity planning models.
  • Figure 10 is a representation of the task package to build and test target processes 5550.
  • This task package includes the following tasks: train capacity planning team 5551 , complete data gathering procedures 5552, develop baseline model 5553, model capacity demand 5555, and prepare capacity planning document 5557.
  • This task package designs and programs the capacity modeling & planning components that make up the base models, including extensions to reused and packaged items, and then to perform the workload characterization, model calibration, and verification. Multiple iterations of this task package may be required to align all components.
  • the goal is to provide capacity models and a capacity management plan. Training for users involved in the forecasting process may be appropriate, but this will typically be a small group of people and forecasting will represent only a minor portion of their workload.
  • the recommended approach is to forecast the changes to key business drivers for each function, and then translate these into changes expected in workload volumes. Forecasts may be projected for any time period and may depend on specific requirements of the sponsoring organization.
  • a common method is to develop an initial 12-month forecast, and then update it each quarter with an additional 3 month projection based on actual and expected results. This may be referred to as a rolling 12-month forecasting process.
  • Application development and maintenance workloads may need to be factored in along with production workloads if they comprise a significant portion of total utilization.
  • the workload characterization process consists of taking the business functions and application business drivers and decomposing them into system transactions.
  • the transactions that relate to a given business driver are grouped together to create a workload.
  • the resources that are consumed by each transaction are accumulated to determine the resource usage for the total workload.
  • transactions may not be as easy to isolate as in a mainframe environment.
  • a transaction usually must be created by grouping the processes or threads and is initiated by the occurrence of a business driver event.
  • the processes and threads that consume the majority of the resources are the ones that should be included in the transaction. For example, a user in the client server environment might initiate a series of processes on a client machine, one of which is a request for customer credit information.
  • This request is sent to a server in the form of a query.
  • the activity performed to satisfy the query represents the processing performed. Capturing activity by process and grouping the processes permits identification, and subsequently analysis, of resource utilization by 'transaction,' and thereby relates utilization back to business drivers.
  • Resource utilization data is normally gathered by Collection Agents. These Agents are simply programs that reside in servers and capture process activity for specified time periods. This data is then passed to the analysis modules of the modeling software to create the base models.
  • base model data should be collected during peak periods of random or on-line processing activity for target applications.
  • base model data must be generated through manual input, benchmarking, or some other technique.
  • the base model Once the base model has been created, it must be calibrated in order to ensure that the model is a true representation of the actual system. Calibration involves verifying that the model's projections accurately reflect business conditions, then adjusting the assumptions and parameters used to correct any problems.
  • the model's utilization projections are analyzed and resource configuration alternatives that satisfy the capacity requirements are developed.
  • the ongoing capacity modeling and planning team as well as the key business users who will be involved in capacity planning in the future should be heavily involved in executing the product test.
  • the cost of each viable alternative is determined.
  • the benefits are documented.
  • the most desirable configuration strategy is presented to the management of the organization for review and approval.
  • the capacity plan should also be completed in conjunction with this task package.
  • the development of the capacity plan includes: summarization of configuration strategies; collection of cost data for alternative configurations; analyses of costs and benefits for alternatives; policies and procedures for modeling and capacity management; and creation of a Capacity Planning Project Report.
  • the plan should cover the scope and objectives of the project, results realized as outlined above, procedures for on-going execution, procedures for maintenance of the planning process, and other issues that may be significant to the sponsoring organization.
  • the plan typically defines the resource requirements by type, and estimates changes in the requirements, either up or down, over a period of time.
  • a plan may be based on six-month increments, showing the projected capacity requirements by resource type for each six month period over a total time frame of three to five years. It may be appropriate to recommend firm follow-up if the capacity modeling and planning process is new to the organization.
  • On-going management attention to the plan should also be arranged to ensure the project is not treated as just a one-time exercise and then discarded.
  • FIG 11 is a representation of the task package to deploy technology infrastructure 7170.
  • This task package includes the following tasks: finalize capacity planning binder 7171 , prepare and present management report 7173, and support post-deployment planning cycle 7175.
  • the capacity modeling and planning infrastructure is implemented within the deployment unit.
  • the capacity plan is finalized and published.
  • the policies and procedures are activated for on-going forecasting, data collection, and reporting.
  • the goal is to provide a capacity plan and a capacity modeling and planning infrastructure.
  • the model should be run on a periodic basis as additional production data and new user forecasts are collected and entered into the database. This will verify that the model is still forecasting utilization and capacity needs correctly, or will indicate that changes are required.
  • the model developed through this process should be a reliable tool to support the on-going performance management, modeling, & planning processes.
  • the invention provides a method and apparatus for providing an estimate for building a capacity modeling and planning function in an information technology organization.
  • 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.
  • Figure 12 is a flow chart of one embodiment a method 200 for providing an estimate of the time and cost to build a capacity modeling and planning in an information technology organization.
  • a provider of a capacity modeling and planning such as an IT consultant (e.g., Andersen Consulting) obtains estimating factors from the client 202.
  • IT consultant e.g., Andersen Consulting
  • the provider determines an estimating factor 202, such as for the number of business procedures.
  • the determination of the difficulty rating is determined 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.
  • the computer program is a spreadsheet, such as EXCEL, by Microsoft Corp. of Redmond, Washington, USA.
  • the consultant and the client continue determining the number and difficulty rating for each of the remaining estimating factors 206.
  • this information is transferred to an assumption sheet 208.
  • the assumptions for each factor are defined.
  • the assumption sheet 208 allows the consultant to enter comments relating to each estimating factor, and to document the underlying reasoning for a specific estimating factor.
  • an estimating worksheet is generated and reviewed 210 by the consultant, client, or both.
  • An example of a worksheet is shown in Figures 13a and 13b.
  • the default estimates of the time required for each task 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 capacity modeling and planning 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 Figures 13a and 13b.
  • the worksheet is reviewed 210 by the provider and the client for accuracy.
  • Adjustments may be made to task level estimates by both returning to the factors sheet and adjusting the units 212 or by entering an override estimate in the 'Used' column 214 on the worksheet.
  • This override may be used when the estimating factor produces a task estimate that is not appropriate for the task, for example, when a task is not required on a particular project.
  • 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.
  • 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.
  • the staffing factors should add up to 1.
  • the consultant or provider and the client now review the workplan 218, and optionally may include labor to be provided by the client.
  • 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 Figures 13a and 13b 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.
  • 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 is then computed and displayed, generating final estimates.
  • a determination of out-of- pocket expenses 222 may be applied to the final estimates to determine a final project cost 224.
  • the provider reviews the final estimates with an internal functional expert 226.
  • project management costs for managing the providers work are included in the estimator. These are task dependant and may 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 Figure 13a.

Abstract

Cette invention concerne une technique permettant d'assurer ou de créer une fonction de modélisation et de planification de la capacité dans une organisation spécialisée dans les technologies de l'information, technique qui passe par l'exécution de taches en rapport avec la mise en place de ladite fonction. Ces tâches consistent à ordonnancer, analyser, concevoir, tester et déployer la fonction de modélisation et de la planification de la capacité. Chacune de ces tâches se subdivise en éléments sous-jacents concernant les processus, l'organisation et la technologie.
PCT/US2000/027795 1999-10-06 2000-10-06 Technique et estimateur pour la modelisation et la planification de la capacite WO2001025876A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU80017/00A AU8001700A (en) 1999-10-06 2000-10-06 Method and estimator for providing capacity modeling and planning

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US15825999P 1999-10-06 1999-10-06
US60/158,259 1999-10-06

Publications (2)

Publication Number Publication Date
WO2001025876A2 true WO2001025876A2 (fr) 2001-04-12
WO2001025876A3 WO2001025876A3 (fr) 2001-08-30

Family

ID=22567316

Family Applications (12)

Application Number Title Priority Date Filing Date
PCT/US2000/027593 WO2001026028A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur de gestion du changement
PCT/US2000/027803 WO2001026013A1 (fr) 1999-10-06 2000-10-06 Technique et estimateur pour gestion des niveaux de service
PCT/US2000/027856 WO2001025970A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur pour l'evaluation de modeles de maturite d'operations
PCT/US2000/027795 WO2001025876A2 (fr) 1999-10-06 2000-10-06 Technique et estimateur pour la modelisation et la planification de la capacite
PCT/US2000/027518 WO2001026005A1 (fr) 1999-10-06 2000-10-06 Procede de determination du cout total de la propriete
PCT/US2000/027801 WO2001026011A1 (fr) 1999-10-06 2000-10-06 Technique et estimateur pour la planification strategique de la gestion des operations
PCT/US2000/027629 WO2001026008A1 (fr) 1999-10-06 2000-10-06 Procede de surveillance d'evenements/defaillances et dispositif d'estimation associe
PCT/US2000/027804 WO2001026014A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur destines a la mise en oeuvre d'une commande de services
PCT/US2000/027802 WO2001026012A1 (fr) 1999-10-06 2000-10-06 Technique et estimateur pour la gestion des moyens de stockage
PCT/US2000/027857 WO2001025877A2 (fr) 1999-10-06 2000-10-06 Organisation de fonctions de technologie de l'information
PCT/US2000/027796 WO2001026010A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur pour l'ordonnancement de la production
PCT/US2000/027592 WO2001026007A1 (fr) 1999-10-06 2000-10-06 Methode et estimateur destines a la planification antisinistre d'une affaire

Family Applications Before (3)

Application Number Title Priority Date Filing Date
PCT/US2000/027593 WO2001026028A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur de gestion du changement
PCT/US2000/027803 WO2001026013A1 (fr) 1999-10-06 2000-10-06 Technique et estimateur pour gestion des niveaux de service
PCT/US2000/027856 WO2001025970A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur pour l'evaluation de modeles de maturite d'operations

Family Applications After (8)

Application Number Title Priority Date Filing Date
PCT/US2000/027518 WO2001026005A1 (fr) 1999-10-06 2000-10-06 Procede de determination du cout total de la propriete
PCT/US2000/027801 WO2001026011A1 (fr) 1999-10-06 2000-10-06 Technique et estimateur pour la planification strategique de la gestion des operations
PCT/US2000/027629 WO2001026008A1 (fr) 1999-10-06 2000-10-06 Procede de surveillance d'evenements/defaillances et dispositif d'estimation associe
PCT/US2000/027804 WO2001026014A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur destines a la mise en oeuvre d'une commande de services
PCT/US2000/027802 WO2001026012A1 (fr) 1999-10-06 2000-10-06 Technique et estimateur pour la gestion des moyens de stockage
PCT/US2000/027857 WO2001025877A2 (fr) 1999-10-06 2000-10-06 Organisation de fonctions de technologie de l'information
PCT/US2000/027796 WO2001026010A1 (fr) 1999-10-06 2000-10-06 Procede et estimateur pour l'ordonnancement de la production
PCT/US2000/027592 WO2001026007A1 (fr) 1999-10-06 2000-10-06 Methode et estimateur destines a la planification antisinistre d'une affaire

Country Status (4)

Country Link
EP (2) EP1226523A4 (fr)
AU (12) AU7996000A (fr)
CA (1) CA2386788A1 (fr)
WO (12) WO2001026028A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8355938B2 (en) 2006-01-05 2013-01-15 Wells Fargo Bank, N.A. Capacity management index system and method
US9984044B2 (en) 2014-11-16 2018-05-29 International Business Machines Corporation Predicting performance regression of a computer system with a complex queuing network model
US10044786B2 (en) 2014-11-16 2018-08-07 International Business Machines Corporation Predicting performance by analytically solving a queueing network model
CN110096423A (zh) * 2019-05-14 2019-08-06 深圳供电局有限公司 一种基于大数据分析的服务器存储容量分析预测方法
WO2019232434A1 (fr) * 2018-06-01 2019-12-05 Walmart Apollo, Llc Système et procédé de modification de capacité pour de nouvelles installations
US11693385B2 (en) 2018-06-01 2023-07-04 Walmart Apollo, Llc Automated slot adjustment tool

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2002256550A1 (en) * 2000-12-11 2002-06-24 Skill Development Associates Ltd Integrated business management system
US7937281B2 (en) 2001-12-07 2011-05-03 Accenture Global Services Limited Accelerated process improvement framework
US7035809B2 (en) * 2001-12-07 2006-04-25 Accenture Global Services Gmbh Accelerated process improvement framework
WO2004040409A2 (fr) 2002-10-25 2004-05-13 Science Applications International Corporation Systeme et procede destines a determiner des capacites de niveau de performance selon des criteres de modeles predetermines
DE10331207A1 (de) 2003-07-10 2005-01-27 Daimlerchrysler Ag Verfahren und Vorrichtung zur Vorhersage einer Ausfall-Häufigkeit
US8572003B2 (en) * 2003-07-18 2013-10-29 Sap Ag Standardized computer system total cost of ownership assessments and benchmarking
US8566147B2 (en) * 2005-10-25 2013-10-22 International Business Machines Corporation Determining the progress of adoption and alignment of information technology capabilities and on-demand capabilities by an organization
EP1808803A1 (fr) * 2005-12-15 2007-07-18 International Business Machines Corporation Système et procédé de sélection automatique d'une ou plusieurs mesures pour la réalisation d'une évaluation CMMI
US8457297B2 (en) 2005-12-30 2013-06-04 Aspect Software, Inc. Distributing transactions among transaction processing systems
US7523082B2 (en) * 2006-05-08 2009-04-21 Aspect Software Inc Escalating online expert help
WO2008105825A1 (fr) * 2007-02-26 2008-09-04 Unisys Corporation Procédé pour des services fondés sur une technologie de diversification
US20100312612A1 (en) * 2007-10-25 2010-12-09 Hugh Carr Modification of service delivery infrastructure in communication networks
US8326660B2 (en) 2008-01-07 2012-12-04 International Business Machines Corporation Automated derivation of response time service level objectives
US8320246B2 (en) * 2009-02-19 2012-11-27 Bridgewater Systems Corp. Adaptive window size for network fair usage controls
US8200188B2 (en) 2009-02-20 2012-06-12 Bridgewater Systems Corp. System and method for adaptive fair usage controls in wireless networks
US8577329B2 (en) 2009-05-04 2013-11-05 Bridgewater Systems Corp. System and methods for carrier-centric mobile device data communications cost monitoring and control
US9203629B2 (en) 2009-05-04 2015-12-01 Bridgewater Systems Corp. System and methods for user-centric mobile device-based data communications cost monitoring and control
US20110066476A1 (en) * 2009-09-15 2011-03-17 Joseph Fernard Lewis Business management assessment and consulting assistance system and associated method
US20110231229A1 (en) * 2010-03-22 2011-09-22 Computer Associates Think, Inc. Hybrid Software Component and Service Catalog
US20130219163A1 (en) * 2010-10-27 2013-08-22 Yaniv Sayers Systems and methods for scheduling changes
US11172022B2 (en) 2014-02-21 2021-11-09 Hewlett Packard Enterprise Development Lp Migrating cloud resources
US10148757B2 (en) 2014-02-21 2018-12-04 Hewlett Packard Enterprise Development Lp Migrating cloud resources
US20170032297A1 (en) * 2014-04-03 2017-02-02 Dale Chalfant Systems and Methods for Increasing Capability of Systems of Business Through Maturity Evolution
US10460272B2 (en) * 2016-02-25 2019-10-29 Accenture Global Solutions Limited Client services reporting
CN106682385B (zh) * 2016-09-30 2020-02-11 广州英康唯尔互联网服务有限公司 健康信息交互系统
EP3782021A4 (fr) * 2018-04-16 2022-01-05 Ingram Micro, Inc. Système et procédé d'appariement de flux de revenus dans une plateforme de courtage de services en nuage
US11483350B2 (en) 2019-03-29 2022-10-25 Amazon Technologies, Inc. Intent-based governance service
US11119877B2 (en) 2019-09-16 2021-09-14 Dell Products L.P. Component life cycle test categorization and optimization
EP4058958A4 (fr) * 2019-11-11 2023-11-29 Snapit Solutions LLC Système de production et de distribution de services et de produits de technologie de l'information
US11288150B2 (en) 2019-11-18 2022-03-29 Sungard Availability Services, Lp Recovery maturity index (RMI)-based control of disaster recovery
US20210160143A1 (en) 2019-11-27 2021-05-27 Vmware, Inc. Information technology (it) toplogy solutions according to operational goals
US11501237B2 (en) 2020-08-04 2022-11-15 International Business Machines Corporation Optimized estimates for support characteristics for operational systems
US11329896B1 (en) 2021-02-11 2022-05-10 Kyndryl, Inc. Cognitive data protection and disaster recovery policy management

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5630069A (en) * 1993-01-15 1997-05-13 Action Technologies, Inc. Method and apparatus for creating workflow maps of business processes
US5953707A (en) * 1995-10-26 1999-09-14 Philips Electronics North America Corporation Decision support system for the management of an agile supply chain

Family Cites Families (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4827423A (en) * 1987-01-20 1989-05-02 R. J. Reynolds Tobacco Company Computer integrated manufacturing system
JPH03111969A (ja) * 1989-09-27 1991-05-13 Hitachi Ltd 計画作成支援方法
US5233513A (en) * 1989-12-28 1993-08-03 Doyle William P Business modeling, software engineering and prototyping method and apparatus
WO1993012488A1 (fr) * 1991-12-13 1993-06-24 White Leonard R Systeme et procede de logiciel pour analyse de mesures
US5701419A (en) * 1992-03-06 1997-12-23 Bell Atlantic Network Services, Inc. Telecommunications service creation apparatus and method
US5586021A (en) * 1992-03-24 1996-12-17 Texas Instruments Incorporated Method and system for production planning
US5646049A (en) * 1992-03-27 1997-07-08 Abbott Laboratories Scheduling operation of an automated analytical system
US5978811A (en) * 1992-07-29 1999-11-02 Texas Instruments Incorporated Information repository system and method for modeling data
US5819270A (en) * 1993-02-25 1998-10-06 Massachusetts Institute Of Technology Computer system for displaying representations of processes
CA2118885C (fr) * 1993-04-29 2005-05-24 Conrad K. Teran Systeme de commande de processus
WO1994029804A1 (fr) * 1993-06-16 1994-12-22 Electronic Data Systems Corporation Systeme de gestion des processus
US5485574A (en) * 1993-11-04 1996-01-16 Microsoft Corporation Operating system based performance monitoring of programs
US5724262A (en) * 1994-05-31 1998-03-03 Paradyne Corporation Method for measuring the usability of a system and for task analysis and re-engineering
US5563951A (en) * 1994-07-25 1996-10-08 Interval Research Corporation Audio interface garment and communication system for use therewith
US5745880A (en) * 1994-10-03 1998-04-28 The Sabre Group, Inc. System to predict optimum computer platform
JP3315844B2 (ja) * 1994-12-09 2002-08-19 株式会社東芝 スケジューリング装置及びスケジューリング方法
JPH08320855A (ja) * 1995-05-24 1996-12-03 Hitachi Ltd システム導入効果評価方法およびシステム
US5875431A (en) * 1996-03-15 1999-02-23 Heckman; Frank Legal strategic analysis planning and evaluation control system and method
US5960417A (en) * 1996-03-19 1999-09-28 Vanguard International Semiconductor Corporation IC manufacturing costing control system and process
US5793632A (en) * 1996-03-26 1998-08-11 Lockheed Martin Corporation Cost estimating system using parametric estimating and providing a split of labor and material costs
US5960200A (en) * 1996-05-03 1999-09-28 I-Cube System to transition an enterprise to a distributed infrastructure
US5673382A (en) * 1996-05-30 1997-09-30 International Business Machines Corporation Automated management of off-site storage volumes for disaster recovery
US5864483A (en) * 1996-08-01 1999-01-26 Electronic Data Systems Corporation Monitoring of service delivery or product manufacturing
US5974395A (en) * 1996-08-21 1999-10-26 I2 Technologies, Inc. System and method for extended enterprise planning across a supply chain
US5930762A (en) * 1996-09-24 1999-07-27 Rco Software Limited Computer aided risk management in multiple-parameter physical systems
US6044354A (en) * 1996-12-19 2000-03-28 Sprint Communications Company, L.P. Computer-based product planning system
US5903478A (en) * 1997-03-10 1999-05-11 Ncr Corporation Method for displaying an IT (Information Technology) architecture visual model in a symbol-based decision rational table
US6028602A (en) * 1997-05-30 2000-02-22 Telefonaktiebolaget Lm Ericsson Method for managing contents of a hierarchical data model
US6106569A (en) * 1997-08-14 2000-08-22 International Business Machines Corporation Method of developing a software system using object oriented technology
US6092047A (en) * 1997-10-07 2000-07-18 Benefits Technologies, Inc. Apparatus and method of composing a plan of flexible benefits
US6131099A (en) * 1997-11-03 2000-10-10 Moore U.S.A. Inc. Print and mail business recovery configuration method and system
US6119097A (en) * 1997-11-26 2000-09-12 Executing The Numbers, Inc. System and method for quantification of human performance factors
US6157916A (en) * 1998-06-17 2000-12-05 The Hoffman Group Method and apparatus to control the operating speed of a papermaking facility

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5630069A (en) * 1993-01-15 1997-05-13 Action Technologies, Inc. Method and apparatus for creating workflow maps of business processes
US5953707A (en) * 1995-10-26 1999-09-14 Philips Electronics North America Corporation Decision support system for the management of an agile supply chain

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8355938B2 (en) 2006-01-05 2013-01-15 Wells Fargo Bank, N.A. Capacity management index system and method
US8818840B2 (en) 2006-01-05 2014-08-26 Brian M. Gilpin Capacity management index system and method
US9984044B2 (en) 2014-11-16 2018-05-29 International Business Machines Corporation Predicting performance regression of a computer system with a complex queuing network model
US10044786B2 (en) 2014-11-16 2018-08-07 International Business Machines Corporation Predicting performance by analytically solving a queueing network model
WO2019232434A1 (fr) * 2018-06-01 2019-12-05 Walmart Apollo, Llc Système et procédé de modification de capacité pour de nouvelles installations
US11481711B2 (en) 2018-06-01 2022-10-25 Walmart Apollo, Llc System and method for modifying capacity for new facilities
US11693385B2 (en) 2018-06-01 2023-07-04 Walmart Apollo, Llc Automated slot adjustment tool
CN110096423A (zh) * 2019-05-14 2019-08-06 深圳供电局有限公司 一种基于大数据分析的服务器存储容量分析预测方法

Also Published As

Publication number Publication date
WO2001025877A3 (fr) 2001-09-07
AU8001800A (en) 2001-05-10
AU7861800A (en) 2001-05-10
WO2001026007A1 (fr) 2001-04-12
EP1222510A4 (fr) 2007-10-31
EP1222510A2 (fr) 2002-07-17
WO2001026010A1 (fr) 2001-04-12
AU8001700A (en) 2001-05-10
WO2001026014A1 (fr) 2001-04-12
WO2001026013A1 (fr) 2001-04-12
AU7866600A (en) 2001-05-10
WO2001025877A2 (fr) 2001-04-12
WO2001026011A1 (fr) 2001-04-12
WO2001026008A1 (fr) 2001-04-12
AU7996000A (en) 2001-05-10
AU1193601A (en) 2001-05-10
AU1431801A (en) 2001-05-10
WO2001025970A1 (fr) 2001-04-12
AU1193801A (en) 2001-05-10
EP1226523A4 (fr) 2003-02-19
EP1226523A1 (fr) 2002-07-31
WO2001026012A1 (fr) 2001-04-12
WO2001025876A3 (fr) 2001-08-30
WO2001026005A1 (fr) 2001-04-12
AU1431701A (en) 2001-05-10
AU1653901A (en) 2001-05-10
AU7996100A (en) 2001-05-10
WO2001025970A8 (fr) 2001-09-27
WO2001026028A8 (fr) 2001-07-26
WO2001026028A1 (fr) 2001-04-12
CA2386788A1 (fr) 2001-04-12
AU7756600A (en) 2001-05-10

Similar Documents

Publication Publication Date Title
US6738736B1 (en) Method and estimator for providing capacacity modeling and planning
WO2001025876A2 (fr) Technique et estimateur pour la modelisation et la planification de la capacite
US8200527B1 (en) Method for prioritizing and presenting recommendations regarding organizaion's customer care capabilities
US20060161884A1 (en) Methods for managing capacity
US20050049911A1 (en) Transformation opportunity indicator
US20060161883A1 (en) Methods for capacity management
US20080016490A1 (en) Enhanced Statistical Measurement Analysis and Reporting
US20020091994A1 (en) Systems and methods for software evaluation and performance measurement
US6968312B1 (en) System and method for measuring and managing performance in an information technology organization
US20090288061A1 (en) Emerging trends lifecycle management
Haley et al. Raytheon Electronic Systems experience in software process improvement
Arekete et al. Project Time and Cost Management
Hajnić et al. Integration of the Decision Support System with the Human Resources Management and Identity and Access Management Systems in an Enterprise
Engelen et al. Towards Improved Decision-Making through the Integration of Financial Information in BPMN Models
Olson Quantitative Tools of Project Management
Carper et al. Computer capacity planning: strategy and methodologies
Singh downloaded from the King’s Research Portal at https://kclpure. kcl. ac. uk/portal
WO2001008004A2 (fr) Systeme, procede et article manufacture pour determiner les niveaux de capacite d'une zone de processus de surveillance a des fins d'evaluation de processus dans une etude de maturite operationnelle
Holt et al. Cost-benefit evaluation of interactive transaction processing systems
WO2001008035A2 (fr) Systeme, procede et article manufacture de verification d'un processus a maturite operationnelle par determination du niveau d'aptitude dans un domaine de processus traitement d'administration utilisateur
Baleevskaia Optimising of ERP System Support
Marquis A Study Guide to Service Catalogue from the Principles of ITIL V3
Burnett et al. Project initiation
Bajaj et al. Linking Systems Analysis Outputs to Capital Budgeting Measures: A Framework and Case Study Validation.
Clapp et al. A guide to conducting independent technical assessments

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP