Resource leveling

Last updated

In project management, resource leveling is defined by A Guide to the Project Management Body of Knowledge (PMBOK Guide) as "A technique in which start and finish dates are adjusted based on resource limitation with the goal of balancing demand for resources with the available supply." [1] Resource leveling problem could be formulated as an optimization problem. [2] The problem could be solved by different optimization algorithms such as exact algorithms or meta-heuristic methods. [2] [3]

Contents

When performing project planning activities, the manager will attempt to schedule certain tasks simultaneously. When more resources such as machines or people are needed than are available, or perhaps a specific person is needed in both tasks, the tasks will have to be rescheduled concurrently or even sequentially to manage the constraint. Project planning resource leveling is the process of resolving these conflicts. It can also be used to balance the workload of primary resources over the course of the project[s], usually at the expense of one of the traditional triple constraints (time, cost, scope).

When using specially designed project software, leveling typically means resolving conflicts or over allocations in the project plan by allowing the software to calculate delays and update tasks automatically. Project management software leveling requires delaying tasks until resources are available. In more complex environments, resources could be allocated across multiple, concurrent projects thus requiring the process of resource leveling to be performed at company level.

In either definition, leveling could result in a later project finish date if the tasks affected are in the critical path.

Resource leveling is also useful in the world of maintenance management. Many organizations have maintenance backlogs. These backlogs consist of work orders. In a "planned state" these work orders have estimates such as 2 electricians for 8 hours. These work orders have other attributes such as report date, priority, asset operational requirements, and safety concerns. These same organizations have a need to create weekly schedules. Resource-leveling can take the "work demand" and balance it against the resource pool availability for the given week. The goal is to create this weekly schedule in advance of performing the work. Without resource-leveling the organization (planner, scheduler, supervisor) is most likely performing subjective selection. For the most part, when it comes to maintenance scheduling, there is less, if any, task interdependence, and therefore less need to calculate critical path and total float.

See also

Related Research Articles

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

Critical path method Method of scheduling activities

The critical path method (CPM), or critical path analysis (CPA), is an algorithm for scheduling a set of project activities. It is commonly used in conjunction with the program evaluation and review technique (PERT). A critical path is determined by identifying the longest stretch of dependent activities and measuring the time required to complete them from start to finish.

Project management software (PMS) has the capacity to help plan, organize, and manage resource tools and develop resource estimates. Depending on the sophistication of the software, it can manage estimation and planning, scheduling, cost control and budget management, resource allocation, collaboration software, communication, decision-making, quality management, time management and documentation or administration systems. Numerous PC and browser-based project management software and contract management software products and services are available.

In a project network, a dependency is a link among a project's terminal elements.

In economics, resource allocation is the assignment of available resources to various uses. In the context of an entire economy, resources can be allocated by various means, such as markets, or planning.

In project management, a schedule is a listing of a project's milestones, activities, and deliverables. Usually dependencies and resources are defined for each task, then start and finish dates are estimated from the resource allocation, budget, task duration, and scheduled events. A schedule is commonly used in the project planning and project portfolio management parts of project management. Elements on a schedule may be closely related to the work breakdown structure (WBS) terminal elements, the Statement of work, or a Contract Data Requirements List.

In organizational studies, resource management is the efficient and effective development of an organization's resources when they are needed. Such resources may include the financial resources, inventory, human skills, production resources, or information technology (IT) and natural resources.

Project portfolio management (PPM) is the centralized management of the processes, methods, and technologies used by project managers and project management offices (PMOs) to analyze and collectively manage current or proposed projects based on numerous key characteristics. The objectives of PPM are to determine the optimal resource mix for delivery and to schedule activities to best achieve an organization’s operational and financial goals, while honouring constraints imposed by customers, strategic objectives, or external real-world factors. Standards for Portfolio Management include Project Management Institute's framework for project portfolio management, Management of Portfolios by Office of Government Commerce and the PfM² Portfolio Management Methodology by the PM² Foundation.

Workforce management (WFM) is an institutional process that maximizes performance levels and competency for an organization. The process includes all the activities needed to maintain a productive workforce, such as field service management, human resource management, performance and training management, data collection, recruiting, budgeting, forecasting, scheduling and analytics.

Scheduling is the process of arranging, controlling and optimizing work and workloads in a production process or manufacturing process. Scheduling is used to allocate plant and machinery resources, plan human resources, plan production processes and purchase materials.

Database tuning describes a group of activities used to optimize and homogenize the performance of a database. It usually overlaps with query tuning, but refers to design of the database files, selection of the database management system (DBMS) application, and configuration of the database's environment.

Schedule Planning of tasks and events

A schedule or a timetable, as a basic time-management tool, consists of a list of times at which possible tasks, events, or actions are intended to take place, or of a sequence of events in the chronological order in which such things are intended to take place. The process of creating a schedule — deciding how to order these tasks and how to commit resources between the variety of possible tasks — is called scheduling, and a person responsible for making a particular schedule may be called a scheduler. Making and following schedules is an ancient human activity.

TaskJuggler

TaskJuggler is GPL-licensed project management software that runs under the Linux and Unix operating systems and is programmed in C++ using the Qt toolkit and KDE libraries. The TaskJuggler Project was started in 2001 by Chris Schläger. Early releases provided a command line tool that generated HTML reports. From August 2005 to July 2010, the package also provided a graphical user interface based on the KDE libraries.

A glossary of terms relating to project management and consulting.

Project management triangle Model of the constraints of project management

The project management triangle is a model of the constraints of project management. While its origins are unclear, it has been used since at least the 1950s. It contends that:

  1. The quality of work is constrained by the project's budget, deadlines and scope (features).
  2. The project manager can trade between constraints.
  3. Changes in one constraint necessitate changes in others to compensate or quality will suffer.

Service chain optimization is the application of processes and tools that embrace all functions for improving the efficiency, productivity and, eventually, the profitability of service organizations. In this regard, profitability of a service organization is measured by the revenue generated from service demand, and by the costs due to activity of the enterprise's human resources. Service chains consider the full life-cycle of service demand from early stages of forecasting, through planning, scheduling, dispatch, execution and post-analysis.

LibrePlan

LibrePlan is a free software web application for project management, developed by the Fundación para o Fomento da Calidade Industrial e Desenvolvemento Tecnolóxico de Galicia, dependent of the Ministry of Industry of the Xunta de Galicia. It counted with the collaboration of ACLUNAGA and the financing of the Ministry of Industry, tourism and Commerce and the regional Government of Galicia. The headquarters are located in A Coruña, Spain.

The following outline is provided as an overview of and topical guide to project management:

Spider Project Project management software

Spider Project is a project management software, developed by a Russian company, Spider Project Team.

In project management, resource smoothing is defined by A Guide to the Project Management Body of Knowledge as a "resource optimization technique in which free and total float are used without affecting the critical path" of a project. Resource smoothing as a resource optimization technique has only been introduced in the Sixth Edition of the PMBOK Guide and did not exist in its previous revisions. It is posed as an alternative and a distinct resource optimization technique beside resource leveling.

References

  1. ↑ "6.6.2.4 Resource Optimization Techniques". A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (5th ed.). Project Management Institute. 2013. p. 179. ISBN   978-1-935589-67-9.
  2. 1 2 "Piryonesi, S. M., Nasseri, M., & Ramezani, A. (2018). Resource leveling in construction projects with activity splitting and resource constraints: a simulated annealing optimization. Canadian Journal of Civil Engineering, 46(999), 81-86". doi:10.1139/cjce-2017-0670. hdl: 1807/93364 . S2CID   116480238.{{cite journal}}: Cite journal requires |journal= (help)
  3. ↑ "Rieck, J., Zimmermann, J., & Gather, T. (2012). Mixed-integer linear programming for resource leveling problems. European Journal of Operational Research, 221(1), 27-37".
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.