MATERIAL HANDLING ACADEMY

Part II. Lesson 5. Think Like the Package.

DRIVING QUESTION What is it like to be the package?
PART II | LESSON 5: THINK LIKE THE PACKAGE

Become the Package

You're not an engineer right now. You're a carton. Somebody just set you down on a conveyor, and you're about to ride it clear across a building you didn't design. What do you feel on the way?

Think like the package, before you draw a single line.

PART II | LESSON 5: THINK LIKE THE PACKAGE

The Package's Journey

  1. How am I getting onto this conveyor? Is something handing me off from another surface, and will I catch an edge on the way?
  2. What's under me right now, and are there enough rollers to hold me up at my length?
  3. Where's my weight sitting?
  4. When the zone in front of me stops, do I slide, rock, or tip?
  5. What's the package behind me doing when I stop?
  6. What does this curve ask of me?
  7. What does this incline ask of me?
  8. And what happens to me if a zone just quits?
PART II | LESSON 5: THINK LIKE THE PACKAGE

Easy Way, Hard Way

EASY WAY

Long dimension forward, running in the direction of travel. You span a lot of rollers at once, sit flat, and ride stable.

HARD WAY

Short dimension forward. Fewer rollers under you, so you can teeter, and your leading edge can dip into the gap before the next roller catches you.

The rule underneath it: at least three rollers in contact with the package at all times.

PART II | LESSON 5: THINK LIKE THE PACKAGE

The Families

PART II | LESSON 5: THINK LIKE THE PACKAGE

The Three W's

WHYA non-standard package, a tote, a polybag, a specialty item, changes technology selection, system architecture, and cost. Catch it in analysis and you design for it. Catch it after install and you rebuild.
WHENDuring product data collection, before any conveyor gets selected. Ask specifically. The customer may not think of their polybag shipments as a conveyor problem. You know they are.
WHEREIn the product analysis, feeding technology selection downstream.
NOT WHENDon't wait for the customer to volunteer it. They ship polybags every day and never think to mention them, because to them it's just product, not a design driver. If you didn't ask, you didn't find out.
FAILURE IF IGNOREDA system gets spec'd for clean rigid cartons, the real mix turns out to be a third polybags nobody asked about, and it starts jamming inside the first month. That's a discovery failure wearing an engineering failure's clothes.
PART II | LESSON 5: THINK LIKE THE PACKAGE
COMMON MISTAKE

Thinking about the conveyor instead of the package. You draw a clean set of lines connecting the entry to the exit, and every line is technically correct, and you never once asked what the product feels going through it. The jams show up later, at the exact points you skipped.

PART II | LESSON 5: THINK LIKE THE PACKAGE
STOP AND THINK

Pick a padded mailer you've gotten in the mail. Put it on a roller conveyor in your head and push it forward. What happens when it reaches a curve? When the zone in front of it stops and the package behind it keeps coming? When it hits a transfer? You just found three reasons a polybag isn't a carton.

PART II | LESSON 5: THINK LIKE THE PACKAGE
FIELD INSIGHT | MICHAEL COLLINS

Tires, polybags, anything that isn't a standard carton, some consideration has to be made, because it can drive the whole solution in a direction you didn't plan for. The question I always ask is what percentage of your volume is this. Five percent or less, you probably don't design the whole system around it, you build an exception path. Twenty percent and you've got a different system entirely.

Michael Collins
PART II | LESSON 5: THINK LIKE THE PACKAGE

Riverside

RIVERSIDE PROJECT
ProductLengthWidthHeightWeight% VolumeProduct Use
Small Case8"6"4"3 lbs4%Packaged food
Standard Case13"9"3"12 lbs78%All clients
Tall Case10"8"14"18 lbs12%Apparel client
Large Case22"15"7"28 lbs6%Housewares

Walk the list as the carton. Which one runs easy, which one is a handling risk, and which one you're flagging and why. Write a one or two sentence behavior read for each, in the package's voice where it helps.

Next: Which products should this system actually be built around?