<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Warehousing Insights &#124; Material Handling Systems &#187; advanced shipping notice</title>
	<atom:link href="http://www.cisco-eagle.com/blog/index.php/tag/advanced-shipping-notice/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cisco-eagle.com/blog</link>
	<description>Warehousing Insights By Cisco-Eagle. Information on the products and techniques to better store, handle, and move products in your facility.</description>
	<lastBuildDate>Tue, 17 Aug 2010 15:11:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Cross Docking: A retailer improves supply chain</title>
		<link>http://www.cisco-eagle.com/blog/index.php/2008/03/14/cross-docking-a-retailer-improves-supply-chain/</link>
		<comments>http://www.cisco-eagle.com/blog/index.php/2008/03/14/cross-docking-a-retailer-improves-supply-chain/#comments</comments>
		<pubDate>Fri, 14 Mar 2008 16:05:28 +0000</pubDate>
		<dc:creator>chris.doyle</dc:creator>
				<category><![CDATA[Automation]]></category>
		<category><![CDATA[Conveyor]]></category>
		<category><![CDATA[Cross Docking]]></category>
		<category><![CDATA[Material Handling]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[advanced shipping notice]]></category>
		<category><![CDATA[asn]]></category>
		<category><![CDATA[cross dock]]></category>
		<category><![CDATA[order fulfillment]]></category>
		<category><![CDATA[sortation]]></category>

		<guid isPermaLink="false">http://www.cisco-eagle.com/blog/index.php/2008/03/14/cross-docking-a-retailer-improves-supply-chain/</guid>
		<description><![CDATA[This is the fourth in a series of briefs on cross docking A recent project for a large retailer in the Southwest provided a good example of how an element of cross-docking might be deployed to reduce the footprint of distribution space required, reduce order fulfillment touchpoints, and shorten the logical pathway for fulfilling orders. [...]]]></description>
			<content:encoded><![CDATA[<p><em>This is the fourth in a series of briefs on cross docking </em></p>
<p>A recent project for a large retailer in the Southwest provided a good example of how an element of cross-docking might be deployed to reduce the footprint of distribution space  required, reduce order fulfillment touchpoints, and shorten the logical pathway for fulfilling orders.</p>
<p>Incoming shipments are anticipated through the use of advanced shipping notices (ASN&#8217;s).  Stretch-wrapped pallet loads arrive via truck throughout the day.  They arrive at doors designated for cross-docking.  These doors were selected based upon proximity to the material handling system which takes advantage of the facility layout.  Pallets are unloaded by fork truck, the stretch wrap removed, and cases manually inducted into one of several conveyor staging lanes.  Each lane represents a &#8220;wave&#8221; of orders which will be processed either that day, or a specific day later in the week.  When a wave is released, it moves downstream, and the individual cases are sorted to a specific shipping lane whose products are destined for a particular store.  Other products from static storage positions and non-conveyables destined for the same store are consolidated at this point.<span id="more-48"></span></p>
<p>As waves are released, the staging lane becomes immediately available for a subsequent wave.  Multiple waves are processed daily.  Pallets arrive at the receiving docks with man-readable labels indicating the destination store and day to ship.  The individual cases on each pallet are pre-labeled (pre-distribution) with a unique identifier that corresponds to the ultimate destination retail store, the SKU number, and the quantity.  When the case label is scanned for the identifier, a lookup into a warehouse control system database occurs, which provides the routing instructions, ie, the correct shipping door.  Again, orders can be comprised of cases that are cross-docked from the staging lanes, product stored in static storage positions, and/or non-conveyables.  The sortation management system routes all conveyables in the current wave directly to the correct shipping lane.</p>
<p>Order fulfillment occurs in waves, due to a limited number of shipping doors.  Most shipping doors are dedicated to a specific destination store, while a handful of other doors will each serve a number of smaller retail stores.  This distribution center demonstrates how cross-docking products that are good candidates, can be integrated with order fulfillment of inventoried products to enhance overall distribution performance.</p>
<p><em>Next month we will look at a scalable, &#8220;out-of-the-box&#8221; cross docking system, its layout, and cost to purchase and implement.  It will include conveyors, controls, and software to support a basic cross docking system.  We have taken a modular approach to a systems solution that can truly be modularized.  Join us.</em></p>
 <div class=’series_links’><a href='http://www.cisco-eagle.com/blog/index.php/2008/01/25/cross-docking-what-are-the-facility-layout-considerations/' title='Cross Docking: What are the facility layout considerations?'>Previous in series</a> </div><div class=’series_toc’><hr />This article is part of a series of articles on<b> Cross Docking</b>. Click on a link below to view one of the other articles.<ol><li style="margin-left:4px"><a href='http://www.cisco-eagle.com/blog/index.php/2007/12/05/brief-1-cross-docking-is-it-right-for-me/' title='Cross Docking: Is it right for me?'>Cross Docking: Is it right for me?</a></li><li style="margin-left:4px"><a href='http://www.cisco-eagle.com/blog/index.php/2007/12/19/am-i-wasting-time-is-cross-docking-a-viable-consideration-for-my-company/' title='Am I wasting time: is cross-docking a viable consideration for my company?'>Am I wasting time: is cross-docking a viable consideration for my company?</a></li><li style="margin-left:4px"><a href='http://www.cisco-eagle.com/blog/index.php/2008/01/25/cross-docking-what-are-the-facility-layout-considerations/' title='Cross Docking: What are the facility layout considerations?'>Cross Docking: What are the facility layout considerations?</a></li><li style="font-weight:bold; margin-left:4px">Cross Docking: A retailer improves supply chain</li></ol><hr /></div> ]]></content:encoded>
			<wfw:commentRss>http://www.cisco-eagle.com/blog/index.php/2008/03/14/cross-docking-a-retailer-improves-supply-chain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cross Docking: What are the facility layout considerations?</title>
		<link>http://www.cisco-eagle.com/blog/index.php/2008/01/25/cross-docking-what-are-the-facility-layout-considerations/</link>
		<comments>http://www.cisco-eagle.com/blog/index.php/2008/01/25/cross-docking-what-are-the-facility-layout-considerations/#comments</comments>
		<pubDate>Fri, 25 Jan 2008 22:01:19 +0000</pubDate>
		<dc:creator>chris.doyle</dc:creator>
				<category><![CDATA[Automation]]></category>
		<category><![CDATA[Conveyor]]></category>
		<category><![CDATA[Cross Docking]]></category>
		<category><![CDATA[Material Handling]]></category>
		<category><![CDATA[Supply Chain]]></category>
		<category><![CDATA[Warehousing]]></category>
		<category><![CDATA[advanced shipping notice]]></category>
		<category><![CDATA[conveyor systems]]></category>
		<category><![CDATA[cross dock]]></category>
		<category><![CDATA[dock layout]]></category>
		<category><![CDATA[order fulfillment]]></category>

		<guid isPermaLink="false">http://www.cisco-eagle.com/blog/index.php/2008/01/25/cross-docking-what-are-the-facility-layout-considerations/</guid>
		<description><![CDATA[This is the third in a series of articles on cross docking If you started from scratch, many might simply build a cross dock facility with a much shallower depth than most warehouses. A depth of a hundred feet or so, with incoming product on one side that can be easily moved a short distance [...]]]></description>
			<content:encoded><![CDATA[<p><em>This is the third in a series of articles on cross docking </em></p>
<p style="text-align: center"><img src="http://www.cisco-eagle.com/order-fulfillment/CrossDockImages/Cross-DockDrawing.jpg" alt="Cross dock facility rendering" height="197" hspace="1" width="360" /></p>
<p>If you started from scratch, many might simply build a cross dock facility with a much shallower depth than most warehouses. A depth of a hundred feet or so, with incoming product on one side that can be easily moved a short distance and loaded on the other side to an outbound truck. Most of us however, must deal with an existing facility, many times a large square box which is not generally the preferred layout. However, as long as the existing facility has a sufficient quantity of dock doors, yard space, and an adequate footprint, you may be fine&#8230;</p>
<p><span id="more-32"></span></p>
<p>Simply having a lot of dock doors does little for efficiency if the doors are located on opposite walls at a great distance from one another. Conveyor companies might love this, but there are better alternatives. Some recommend all the doors on one wall, or even at 90 degrees to one another. High speed movers would then travel between incoming and outgoing doors in closest proximity to one another. Proximity of high traffic incoming and outgoing doors is key. Distance equals costs. Many consider dedicating only a portion of their facility for cross dock duties as an acceptable workaround.</p>
<p>Pallet handling versus case handling create separate requirements. Congestion in dock areas will be a killer. Sufficient dock space is key to moving products quickly and safely. This is particularly true if the company is growing or deals with seasonal products. Ample space must be available for any pallet staging activities near shipping doors. If aisles are part of your logical pathways, then oversize them in high traffic areas.</p>
<p>One of the more complete reviews of cross dock design is by John Bartholdi and Kevin Gue in <em>Transportation Science</em>. They provide an analysis of the impact of &#8220;shape&#8221; on the performance of a cross dock operation. They considered a wide variety of designs and freight flow patterns, and offered the following summary:</p>
<p>&#8220;Shape matters. Freight must be moved across the dock and total distance traveled is a good estimate of labor costs. The best shape for small to mid-sized cross docks is a narrow rectangle or I-shape, which gets maximum use of its most central doors. For larger docks, alternative shapes are more attractive. The best shapes for larger docks will have piers branching out from a central area. These designs have more corners, for which they pay a cost. However, they achieve greater centrality, and so more distant doors are closer to other doors. For example, the T-shape is best for dock sizes between about 150 to 200 doors. For larger than 200 doors, the X-shape is best. Despite having four inside corners near the center of the dock, the worst doors are not far from the center. When freight flows are concentrated among few destinations, the point will be deferred at which a more complicated design becomes attractive. This is because the labor will be concentrated on a subset of the dock, and so the dock is, in effect, a smaller dock.&#8221;</p>
<p>Layouts designed on solid principles will address the &#8220;layout issue&#8221;. Although we have been focusing on the internal logistics of cross docking, we do need to make note of another obvious area of interest&#8230;. the &#8220;trailer spotting&#8221; issue. A poor spotting process defeats a quality layout. They work in concert. There are many issues you deal with in creating an optimum design for cross docking. In the next brief, we will take a look at cross docking in actual practice. This will include a couple of applications that deal with the issues we have discussed, and others. One application is complex, the other is a simple scalable system (actually including system costs).</p>
 <div class=’series_links’><a href='http://www.cisco-eagle.com/blog/index.php/2007/12/19/am-i-wasting-time-is-cross-docking-a-viable-consideration-for-my-company/' title='Am I wasting time: is cross-docking a viable consideration for my company?'>Previous in series</a> <a href='http://www.cisco-eagle.com/blog/index.php/2008/03/14/cross-docking-a-retailer-improves-supply-chain/' title='Cross Docking: A retailer improves supply chain'>Next in series</a></div><div class=’series_toc’><hr />This article is part of a series of articles on<b> Cross Docking</b>. Click on a link below to view one of the other articles.<ol><li style="margin-left:4px"><a href='http://www.cisco-eagle.com/blog/index.php/2007/12/05/brief-1-cross-docking-is-it-right-for-me/' title='Cross Docking: Is it right for me?'>Cross Docking: Is it right for me?</a></li><li style="margin-left:4px"><a href='http://www.cisco-eagle.com/blog/index.php/2007/12/19/am-i-wasting-time-is-cross-docking-a-viable-consideration-for-my-company/' title='Am I wasting time: is cross-docking a viable consideration for my company?'>Am I wasting time: is cross-docking a viable consideration for my company?</a></li><li style="font-weight:bold; margin-left:4px">Cross Docking: What are the facility layout considerations?</li><li style="margin-left:4px"><a href='http://www.cisco-eagle.com/blog/index.php/2008/03/14/cross-docking-a-retailer-improves-supply-chain/' title='Cross Docking: A retailer improves supply chain'>Cross Docking: A retailer improves supply chain</a></li></ol><hr /></div> ]]></content:encoded>
			<wfw:commentRss>http://www.cisco-eagle.com/blog/index.php/2008/01/25/cross-docking-what-are-the-facility-layout-considerations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
