WIP at Risk
The WIP at risk report makes problem jobs float to the surface. Catch a job as and when it goes off the rails, not weeks later.
Highlights
- Breakdown of % used vs planned for completed items
- Breakdown of % used vs planned for items in play
- Details of Extra Hours Tracked
List of jobs at risk
In this report wayahead analyses all WIP and only displays the jobs that need your attention, because they are potentially at risk. This could be because they are already over serviced as a whole, but also because they are partially overserviced or because they have extra hours tracked.
Catch a job going off the rails early
The idea behind this report is to catch jobs being over serviced as early on as possible in the process. You may have a job that runs for 6 months, broken down in 20 individual items. By the time you’ve completed the first 4 items, you’ve already used 10% more time that you were allowed on those 4. That is a problem. Even though the job will not look over serviced in Streamtime, given that you’ve only completed 20% of the job and you’ve only used up say 25% of all available time.
wayahead adds up the estimated time against all complete items and compares it against used time against the same items to tell you where you stand so far. In the example above it would show 4⁄20 completed, 10% over serviced.
Extra Hours Tracked
Another risk category this report flags is extra hours tracked. Generally speaking there is no reason to book hours on a job outside the scope of the planned items. Usually this happens because the user can’t be bothered to pick the right item for the todo they’re logging. By not selecting an item, other people working on the job might think they can still spend more time, risking to over service on the item and the job. wayahead shows the amount of extra hours tracked against each job.
