Seventeen actual steps against nine documented ones, drawn in swimlanes across six roles, with touch time and waiting time logged: GM504 Unit 3's process map for a contractor delivery order. Searches like "gm 504 unit 3 assignment example", "gm504 unit 3 sample" and "gm504 unit 3 example" land here.
What a finished GM504 Unit 3 process map looks like
A two-page map, printed wide across facing pages, followed by about four pages of narrative. Lanes run for inside sales, the credit desk, dispatch, yard pickers, loaders and drivers, and each step box carries two numbers, minutes of work and minutes waiting before the next step starts. Beneath the map sits a summary strip in the style of a value stream map: total lead time from order entry to truck departure of about nineteen hours, of which roughly forty minutes is anyone touching the order. Red flags mark the eight steps missing from the written procedure, among them a 6:00 a.m. print run of every next-day ticket regardless of credit status and a dock-side substitution when a bin comes up empty. The narrative walks the map lane by lane and classifies each unwritten step.
How a GM504 Unit 3 example is structured
The map comes before any interpretation, and the paper explains how it was built: fifteen composite orders followed from entry to delivery over two weeks, with the elapsed time at each handover noted by the writer rather than taken from the system. That method matters, because the enterprise system records only order entry, invoicing and proof of delivery, and everything between them is invisible to it. After the map, a section compares actual against documented steps and sorts the eight extra steps into three groups: workarounds for a system limitation, rework caused by an earlier step, and informal decisions nobody authorized. Lean's categories of waste label each non-value-added step, with waiting and motion dominating. Last comes a short list of the three points where errors most plausibly enter the order, which sets up the cause analysis without claiming to have done it.
Fifteen orders, followed on foot
The method paragraph names how the orders were chosen, why they include two peak Mondays and a slow midweek day, and how times were recorded at each handover, so the map's reliability can be judged before the map itself.
Six lanes, seventeen boxes
The map itself, each box labeled with work minutes and wait minutes. Unwritten steps are flagged in a contrasting color, and a legend explains the symbols for decisions, delays and hand-carried paper.
Nine written, eight not
The written procedure is set beside the map. The eight missing steps are sorted into workarounds, rework and unauthorized decisions, with the early ticket print and the dock substitution treated at length because both change what ends up on the truck.
Waste by type
Each non-value-added step is labeled with a Lean waste category. Waiting accounts for most of the nineteen-hour lead time, and motion accounts for most of the pickers' day, since overflow stock sits two aisles from its recorded bin.
Where errors enter
Three candidate entry points close the paper: the unrecorded overflow locations, the verbal substitutions and the handwritten add-ons phoned in after tickets print. They are offered as hypotheses for later cause analysis, not as conclusions.
Where marks go in GM504 Unit 3
Process maps in this course most often lose marks for being drawn from the procedure manual. A tidy diagram of how orders are supposed to move shows no failure points, so nothing downstream can connect to it. Maps also fall short when every box looks alike: without time data or a distinction between work and waiting, there is no way to see where the nineteen hours go. Rubrics commonly reward evidence of direct observation, a stated method, and unwritten steps named plainly rather than smoothed over. Another frequent deduction comes from a narrative that simply repeats the map in sentences. The better-marked versions interpret it, classifying the gap between documented and actual work, and they stop short of proposing fixes, since a map that already contains a solution has usually been drawn to fit one.
Get a GM504 Unit 3 example written to your instructions
Describe the process your Unit 3 map has to cover, from the first trigger to the finished output, and say who touches it along the way. If you have timings or a written procedure, include them with the prompt and rubric. Your first map and narrative are free, built to that assignment and returned in 24-48h.
GM504 Unit 3 questions, answered
Which mapping format does the Unit 3 assignment expect?
Instructions vary. Many sections accept a swimlane flowchart, a SIPOC diagram followed by a detailed flow, or a value stream map, and some specify one. The example here uses swimlanes with a value stream summary strip, because the roles and the waiting time both mattered. Whatever format is used, it should show who does each step and where work sits idle.
Can I map a process I do not work in myself?
Yes, if you can observe it or interview the people who do. Mapping from the outside often catches steps that insiders no longer notice, since habits stop looking like steps. The weakness is timing: without watching the work, estimates tend to reflect the procedure rather than reality. Say how each figure was obtained, and mark estimates as estimates.
How detailed should the map be?
Detailed enough that a stranger could follow a single order through it and predict where it might go wrong. A map with five boxes usually hides the handovers where errors enter; one with sixty becomes unreadable. The example settles at seventeen steps because each one changes who holds the order or what is on it. Steps that change neither are merged.