A median return spent 3.34 days elapsed and 11.4 minutes handled, and GB560's Unit 4 cycle time analysis traces the difference to queues, batches and loops. Searches like "gb 560 unit 4 assignment example", "gb560 unit 4 sample" and "gb560 unit 4 example" land here.
What a finished GB560 Unit 4 cycle time analysis looks like
The paper spans about five pages: a histogram, a segment table and a path comparison. The histogram shows 120 returns timed from scan data over two weeks, skewed to the right: median 3.34 days, mean 4.10, standard deviation 2.34, 90th percentile 7.05, longest 14.9. Handling on the standard path totals 11.4 minutes, 12.4 on average once loops are included, so process cycle efficiency is about 0.24 percent of clock time. The segment table ranks waits by their share of mean elapsed time: bulk cartons before unpacking 35.6 percent, the overnight refund-keying queue 21.4, the wait for the 16:00 export 13.3 and the grading queue 9.7. Fourteen returns with no usable authorization took a median of 8.94 days against 3.21 for the rest. First pass yield is 80.0 percent.
How a GB560 Unit 4 example is structured
Definitions come first, because cycle time means different things to different readers: here it is elapsed calendar time from the dock scan to the refund posting, and touch time is minutes of hands-on work. A data section describes the 120 returns, the timestamps used and two gaps in the scan records. The distribution section reports center and spread together and explains why the mean exceeds the median. Segment analysis follows, each wait measured separately and ranked by its share of elapsed time, which shows batching and queues outweighing all handling combined. A path comparison splits matched from unmatched returns and reports first pass yield. Against the three-business-day requirement from Unit 2, a short section counts 63.3 percent of returns past a 72-hour mark, a conservative stand-in. Two waits a redesign would have to remove are named at the close.
Two clocks defined
Elapsed time runs from dock scan to posted refund; touch time counts only minutes of handling, and the analysis never mixes the two.
Center with spread
A median of 3.34 days sits beside a standard deviation of 2.34 and a 90th percentile of 7.05, so the long tail stays in view.
Waits ranked
Bulk cartons, overnight keying, the 16:00 export and the grading queue together account for about 80 percent of mean elapsed time.
Two paths compared
Returns lacking an authorization take a median of 8.94 days, nearly three times the matched path's 3.21, and they make up 11.7 percent of the sample.
Against the requirement
Seventy-six of 120 returns pass 72 hours, a strict proxy for the Unit 2 limit, which turns a timing study into a statement of the gap.
Where marks go in GB560 Unit 4
A mean reported without its spread is the figure that costs cycle time papers most, because the returns shoppers complain about live in the tail. Reporting touch and elapsed time as one number, or leaving cycle time undefined, makes every later comparison unreliable. Segment waits estimated rather than taken from timestamps weaken the analysis for most graders, and a paper should say which figures were observed. Exception paths averaged into the whole hide the fact that one group of returns behaves differently. Efficiency ratios quoted without stating whether clock hours or working hours sit in the denominator can mislead by a factor of three or more. Analyses that end with general advice to speed things up, rather than naming the specific waits to remove, leave the design unit starting from scratch.
Get a GB560 Unit 4 example written to your instructions
Upload your timing data or observations, the requirement your process is measured against and the Unit 4 prompt with its rubric. The analysis separates elapsed from touch time, reports the spread alongside the center and ranks every wait by its share of the total. There is no charge for an initial custom sample, normally ready in 24-48h.
GB560 Unit 4 questions, answered
Why is the median lower than the mean?
Because a few returns take far longer than the rest and pull the mean upward. In the sample, returns stuck in the problem cage for over a week lift the mean to 4.10 days while the median stays at 3.34. Reporting both, with a percentile for the tail, tells a reader how the process behaves for typical and unlucky cases alike.
What is process cycle efficiency?
The share of elapsed time spent actually working on an item, touch time divided by total time. In the sample, 11.4 minutes of handling within a median of 3.34 days gives about 0.24 percent measured in clock hours. Very low figures are common in service and administrative work, which is why the ratio is useful for showing where waiting dominates.
How much data is enough?
Enough to show the distribution's shape and the main paths, which usually means dozens of items at minimum. The sample uses 120 returns over two weeks to cover weekday variation. If your process runs slowly, fewer cases may be all you can collect; state the number and the period, and avoid claiming more precision than the sample supports.