TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Time Values From:"Eric L. Dunn" <edunn -at- TRANSPORT -dot- BOMBARDIER -dot- COM> Date:Mon, 26 Apr 1999 16:37:37 -0400
>>A work-[time unit] is the amount of work a single person gets done in
>>the specified time period (assuming everyone does the same amount of
>>work). There can be many more work hours in a day than real hours,
>>because more than one person can be doing the work. Capiche?
>>
>>Christopher Kowalchuk
This was exactly why I have a problem with the work-month term. I fully
understand the concept of work hours (the value is at the bottom of all our
assembly books for the factory). How can you make the
assumption/calculation of equal work-months? Each country has different
days off and hours per day. As there can be a greater number of worrk-hours
than actual hours how is the work-month defined?
A factory working with a two-shift moving to a three shift would have
horrendous recalculations for work-month. Work-hours I would think is the
only useful term. Unless you can give me a specific example how work-month
is best used.
If work-month is an acceptable value then I can only surmise that it only
applies to a very tightly defined work environment and staffing level.
