GB560 · Unit 3

GB560 Unit 3 current state map example

Designing, Improving, and Implementing Processes Purdue University Global Free custom sample in 24 to 48h

Nine steps appear in the written returns procedure at the composite kitchen-appliance seller; forty returns followed from carrier drop to posted refund passed through seventeen. The GB560 Unit 3 current state map draws the seventeen, along with three loops that send work backward and two batch points where finished items simply wait for a clock.

What this page holds

Seventeen steps observed where the procedure lists nine, with three loops and two batch waits, form this GB560 Unit 3 current state map of an appliance returns center. Searches like "gb 560 unit 3 assignment example", "gb560 unit 3 sample" and "gb560 unit 3 example" land here.

What a finished GB560 Unit 3 current state map looks like

A swimlane map across two pages, then about three pages of notes. Five lanes run across it: dock receiving, the unpacking and matching bench, grading, customer service, and inventory control. Each step box carries touch minutes, and each gap between boxes carries observed waiting hours. The heaviest waits are marked: returns sitting in bulk cartons before unpacking, finished grades held for a 16:00 export, and refunds keyed by customer service the following morning. Three loops appear in heavier lines: returns with no usable authorization routed to a problem cage, disputed grades redone, and refunds corrected after a shopper calls. A comparison strip beneath lists the nine documented steps against the seventeen observed and marks which of the extra eight are workarounds. A method box states that forty returns were followed over two weeks.

How a GB560 Unit 3 example is structured

The map is drawn from observation first and checked against the procedure second, and the paper says so in its opening lines. A method section describes how forty returns were chosen across shifts and product types, and what was timed. The map itself follows, lanes ordered by who touches the item first. Notes are keyed to numbered steps, so each observation, such as a supervisor printing the export by hand, sits next to the box it explains. A section on the extra steps sorts them into three groups: workarounds for missing information, checks added after past errors, and waits created by batching. The loops get their own short section with counts from the forty returns. Closing the paper is a list of questions the map raises for the timing work in Unit 4, without proposing any change yet.

Forty returns, followed

Selection across both shifts and five product families is described, so a reader knows the map reflects ordinary operation rather than one chosen afternoon.

Lanes by first touch

Dock, bench, grading, customer service and inventory control run in the order an item meets them, with every box timed in minutes.

Documented against observed

A strip lists nine written steps beside seventeen observed, and marks the eight additions as workarounds, legacy checks or batch waits.

Loops drawn heavier

Problem-cage routing, re-grades and refund corrections appear as thick return lines, each labeled with how many of the forty returns took it.

Questions, not fixes

The closing list asks where time accumulates and why exports wait for 16:00, leaving the answers to the cycle time unit.

Where marks go in GB560 Unit 3

A map copied from the written procedure is where this assignment most often falls short, since the prompt wants the work as it moves and a procedure records only what was intended. Boxes without times, or times without the waits between them, leave the next unit nothing to analyze. Loops omitted because they seem exceptional hide the paths that consume the most elapsed time. Swimlanes assigned by department rather than by who touches the item can blur handoffs, and handoffs are where waiting collects. Maps with no method statement invite doubt about whether anything was observed at all. Notes that begin proposing improvements move ahead of the course's sequence and are commonly marked as off task. Standard symbols matter to many graders, so decisions drawn as rectangles or waits left unmarked cost small amounts that add up.

Get a GB560 Unit 3 example written to your instructions

Attach whatever you have on the workflow being mapped this term, whether observations, timings or an existing procedure, along with the Unit 3 instructions and rubric. The map returned is built from how the work runs, loops and waits marked, compared with the written steps where they exist. That first custom sample is free, generally back in 24-48h.

GB560 Unit 3 questions, answered

How many cases should a current state map be based on?

Enough to see the paths the work actually takes, which usually means dozens rather than a handful. The sample follows forty returns over two weeks across both shifts. Fewer can work if the process is simple, but the map should state how many were observed and how they were chosen, since graders often ask about exactly that.

Should the loops really go on the main map?

Yes, because they are part of how the process runs, and leaving them off makes the map tidier and less true. In the sample, the problem-cage loop touched a small share of returns but held them for days, which the timing work in Unit 4 later confirms. Heavier lines keep the main path readable while the exceptions stay visible.

What software is used for the map?

Any tool that draws lanes and connectors works, including Visio, Lucidchart, draw.io or the shapes in PowerPoint. Some sections accept a clear hand drawing photographed at high resolution. The sample uses standard flowchart symbols in lanes. What graders check is readability and completeness, so the custom version follows the format your section specifies.