Man-hour
A man-hour is the amount of work performed by the average worker in one hour.[1][2] It is used in written "estimates" for estimation of the total amount of uninterrupted labour required to perform a task. For example, researching and writing a college paper might require twenty man-hours. Preparing a family banquet from scratch might require ten man-hours.
Man-hours do not take account of the breaks that people generally require from work, e.g. for rest, eating, and other bodily functions. They only count pure labour. Managers count the man-hours and add break time to estimate the amount of time a task will actually take to complete. Thus, while one college course's written paper might require twenty man-hours to carry out, it almost certainly will not get done in twenty consecutive hours. Its progress will be interrupted by work for other courses, meals, sleep, and other distractions.
Contents
Real-world applications
The advantage of the man-hour concept is that it can be used to estimate the impact of staff changes on the amount of time required for a task. This is done by dividing the number of man-hours by the number of workers available.
This is, of course, appropriate to certain types of activities. It is of most use when considering 'piece-work', where the activity being managed consists of discrete activities having simple dependencies, and where other factors can be neglected. Therefore, adding another person to a packaging team will increase the output of that team in a predictable manner. In transport industry, this concept is superseded by passenger-mile and tonne-mile for better costing accuracy.
In reality, other factors intervene to reduce the simplicity of this model. If some elements of the task have a natural timespan, adding more staff will have a reduced effect: although having two chefs will double the speed of some elements of food preparation, they roast a chicken no faster than one chef. Some tasks also have a natural number of staff associated with them: the time to chop the vegetables will be halved with the addition of the second chef, but the time to carve the chicken will remain the same.
Another example is the adage, "Just because a woman can make a baby in nine months, it does not follow that nine women can make a baby in one month." This adage is often cited in systems development to justify the belief that adding more staff to a project does not guarantee it will get done quicker.
Another problem with this model, as Fred Brooks noted, is that organization, training, and co-ordination activities could more than outweigh the potential benefits of adding extra staff to work on a task, especially if considered only over a shorter time period.
Similar units
The similar concept of a man-day, man-week, man-month, or man-year[3][4] is used on large projects. Recently, in some organizations the gender-neutral terms effort-hour, effort-day (ED), effort-week, effort-month, effort-year (EY) are also used. It is the amount of work performed by an average worker during one day, week, month, or year, respectively. The number of hours worked by an individual during a year varies greatly according to cultural norms and economics. The average annual hours actually worked per person in employment as reported by OECD countries in 2007, for example, ranged from a minimum of 1,389 hours (in the Netherlands) to a maximum of 2,316 hours (in South Korea).[5]
Productive system hours
The concept of productive system hours (PSH) has been used in forestry in Austria and by extension to other work. It includes time for breaks and can be used to calculate how long a task may take to be done including required recovery times from physically strenuous work as well as legally required breaks or other human interactions. If it includes 15 min breaks it is written as (PSH15).
A related concept is productive machine hours (PMH).[6]
See also
- Henry Gantt
- Frank Bunker Gilbreth
- Labour
- Mechanization
- Productivity
- Scientific management
- Surplus value
- Taylorism
- The Mythical Man-Month, Fred Brooks's classic book on software engineering
- Time and motion study
- Frederick Winslow Taylor
References
- ↑ Definition from the Merriam-Webster Online Dictionary
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Infoplease.com
- ↑ SFAF.org
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://www.wabo.boku.ac.at/uploads/media/raupe_pnw99_e.pdf More details in the paper INFLUENCE OF TERRAIN CONDITIONS AND THINNING REGIMES ON PRODUCTIVITY OF A TRACK-BASED STEEP SLOPE HARVESTER
- The Principles of Scientific Management F.W.Taylor, 1911, online
- Shop Management, F.W.Taylor, 1911, online
- A Selection from Frederick Taylor's Essays, online
External links
Man-years:
- Man-year defined as 2000 hours: http://www.onr.navy.mil/02/matoc/05_09/solicitations/docs/05-0002-02.pdf (Solicitation Number 05-0002-02: Support Services for the Office of Naval Research for the Legislative Affairs Office (United States Navy Office of Naval Research: Arlington, Virginia, USA, 2004)
- Man-year defined as 2087 man-hours: Report 5, International Federation Of Professional And Technical Engineers Local 32: San Diego, California, 2000(counting 311 "Non-available/Nonproductive" man-hours)
