SEARCH searchBY TOPIC
right_division Green SCM Distribution
Bookmark us
sitemap
SCDigest Logo
distribution

Focus: Distribution/Materials Handling

Feature Article from Our Distribution and Materials Handling Subject Area - See All

From SCDigest's On-Target E-Magazine

- Aug. 7, 2013 -

 
Logistics News: Material Handling Automation Projects - By the Book


Detailed Documentation of a Project from Beginning to End Provides Central Record for All Stakeholders - but is Not Commonly Used

 

 SCDigest Editorial Staff


There are about as many styles of project management for material handling automation as there are consultants, but SCDigest Materials Handling Editor Cliff Holste believes there is one tool that should be common across all of them - development of a "Materials Handling Planning Book."

This is a technique Holste himself has used for many years and involves the creation of a single "binder" that is developed and maintained for all key stakeholders in the project. It becomes the book of record for the project, and thus documents a wide variety of information, from goals and objectives to - critically - all the decisions that are made and why they were made.

"Even after the contract is signed and you think all the details of the system are defined, there are literally dozens of decisions that will still need to be made throughout the life of the project," Holste says. "Far too often, those decisions are not formally documented, or are documented in emails or some other more informal fashion - and that can cause problems later."

It might be weeks or months into the project, and someone questions why a given decision was made - for example, why a specific type of sortation equipment was selected, or specifics of how the interface between the Warehouse Management Systems and Warehouse Control System interface will work - and no one can precisely remember what the details were of that decision, or sometimes even who made it. A Project manager at the company may have made a decision, and senior executives not even be aware that the decision was made.

"Most of the decisions have cost or operational impacts, sometimes significant ones," Holste says. "Organized, detailed documentation is essential to understand how the project is where it is at any given point in the cycle, and most importantly needed to reduce potential conflict between companies, consultants and system vendors over why and by whom decisions were made."

The Planning Book might be updated weekly, with the additions sent to all the stakeholders that have the book. Once the project is in full swing, those updates often come in the form of detailed minutes of any meetings during the past week. Holste says his technique was to first send out the week's documents electronically for any changes or additions, and then bring the physical documents with any of the changes to the next team meeting.

But the book contains a lot more data than just a record of decisions. Holste has used the following general structure for each planning book, though of course there could be variations to this basic format. It represents the structure that might be used say for design and development of a carton sortation system in distribution.

 

Example Materials Handling System Planning Book Structure

 

Section

Table of Contents

Description

1

Glossary of Terms

There are standard industry related terms and specific user terms.  In order to avoid confusion all applicable project related terms will be listed and described.

2

Project Goals

Specific operational and productivity goals will be developed and described.  These will become the yardstick for measuring project success.

3

Assumption & Constraints

Assumptions and constraints will be developed and documented so that they can become a part of the design criteria.

4

Decisions

This is a list of items that are considered to be absolute and not subject to change.

5

WMS & WCS

The keys to successful deployment of these critical software and control systems lie in the development of comprehensive functionality statements.

6

Data Analysis

Item Master, SKU Velocity Reports, On-Hand Inventory Records, Sales Forecasts, etc., will be utilized to develop system operational and flow requirements.

7

Design & Performance Criteria

This is a list of items that are used to drive the system design.

8

Concept Drawings

In the Initialization Phase dimensionally accurate, 11" x 17" layouts of the facility and system arrangement will be developed in color utilizing Microsoft Visio. 

9

Description of Operation

Once the system concept has been developed, an operations plan will be written so the key operational requirements can be identified and described.

10

Planning Report

This is a high level assessment of current warehousing and distribution operations and improvement recommendations.

11

Pricing & Justification

Collaborative pricing formulary and budget pricing.

12

Meeting Minutes Record

Contains minutes of all project team meetings.

 

Source: Cliff Holste

 

A surprising number of projects do not have this level of documentation, leading to misunderstandings and sometimes major conflicts.


(Distribution/Materials Handling Story Continues Below )

CATEGORY SPONSOR: LONGBOW ADVANTAGE - JDA SUPPLY CHAIN CONSULTANTS

Download Longbow Advantage

Business Briefs

 

 

The Keys to WMS Success,

Maximizing JDA WMS

Performance and More

 

 

 

 

 

"You simply can't rely on people's memories," Holste says. "That is a recipe for problems later in the project."

The section on Data Analysis is another key one that almost always proves to be very beneficial down the road.

"It's amazing how often is it useful to refer back to all the data analysis that was used as the basis of the system design and expected throughput," Holste says. "You need to be able to refer back to the data on volumes, handling unit mix, forecasted growth and more when unexpected issues pop up and decisions need to be made."

Why Isn't the Planning Book Approach Used More Often?

Why don't all projects use such a Planning Book? First, developming and especially maintaining such a book is a lot of work, and sometimes companies or consultants just don't want to or can't find the time to keep it up.

Alternatively, often each participant in the process (company, consultant, various vendors) each maintains their own project documentation. Usually, these individual logs are not as detailed as the book Holste recommends, and obviously do not provide a central record that is common to all the stakeholders.

And shippers themselves often come out of the short-end of the stick in this case, Holste says, because when questions arise later, if the vendor has documentation supporting its case, and the company does not, guess who is going to win the battle? Here comes an expensive change order.

 

Operational Flow Diagrams Just One Example of Information in the Planning Book

 




Holste believes shippers should expect their consultant to lead development and maintenance of such a Planning Book, and insist on it as part of the contract terms. But if that isn't going to happen, the shipper is much better off to devote the resources to maintaining the book than to not have it developed at all, or incompletely.

Of course, today there are many electronic options for producing this type of project documentation, but Holste says there is still something to an old-style physical binder.

"If you post the meeting minute updates electronically, is the executive going to read it? Maybe Yes, maybe No," Holste says. "Give him or her a few pages to add to their binders, and they are often more likely to take a look."

Finally, Holste says shippers experiencing this process have often commented that the Planning Book and weekly update cycle had the effect of bringing a strong sense of discipline to the process.

"The Planning Book approach tends to make meetings a lot more focused and effective," he said.

What are your thoughts on the Planning Book approach for materials handling systems? Have you used  a similar approach? Let us know your thoughts at the Feedback section or button (email) below.


Recent Feedback

Great, very good diagram.


ajit vora
general manager
shah forged rolls pvt ltd
Aug, 08 2013

Great 'stuff' – that works, Cliff!  How can someone not take this approach?


John Hill
Director
St. Onge Company
Aug, 08 2013
 
.