<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: To Tame Traffic, Go With The Flow</title>
	<atom:link href="https://www.isegoria.net/2010/10/to-tame-traffic-go-with-the-flow/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.isegoria.net/2010/10/to-tame-traffic-go-with-the-flow/</link>
	<description>From the ancient Greek for equality in freedom of speech; an eclectic mix of thoughts, large and small</description>
	<lastBuildDate>Tue, 23 Jun 2026 09:00:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6.1</generator>
	<item>
		<title>By: Isegoria</title>
		<link>https://www.isegoria.net/2010/10/to-tame-traffic-go-with-the-flow/comment-page-1/#comment-41525</link>
		<dc:creator>Isegoria</dc:creator>
		<pubDate>Tue, 02 Nov 2010 18:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.isegoria.net/?p=22313#comment-41525</guid>
		<description><![CDATA[Thanks for the kind words, Michael.  If you&#039;re not the &quot;Herbie&quot; on any of your current projects, you might peruse the archives &#8212; or, at the very least, the &lt;a href=&quot;http://www.isegoria.net/category/theory-of-constraints/&quot;&gt;Theory of Constraints&lt;/a&gt; category.

Anyway, the reason I balked a bit at the &lt;em&gt;drum-buffer-rope&lt;/em&gt; label is that most descriptions emphasize a single constraint as the &lt;em&gt;drum&lt;/em&gt;, in contrast to the situation in a balanced production line, where the current constraint bounces around less predictably &#8212; which is how I see the traffic situation.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the kind words, Michael.  If you&#8217;re not the &#8220;Herbie&#8221; on any of your current projects, you might peruse the archives &mdash; or, at the very least, the <a href="http://www.isegoria.net/category/theory-of-constraints/">Theory of Constraints</a> category.</p>
<p>Anyway, the reason I balked a bit at the <em>drum-buffer-rope</em> label is that most descriptions emphasize a single constraint as the <em>drum</em>, in contrast to the situation in a balanced production line, where the current constraint bounces around less predictably &mdash; which is how I see the traffic situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Clingan</title>
		<link>https://www.isegoria.net/2010/10/to-tame-traffic-go-with-the-flow/comment-page-1/#comment-41483</link>
		<dc:creator>Michael Clingan</dc:creator>
		<pubDate>Tue, 02 Nov 2010 15:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.isegoria.net/?p=22313#comment-41483</guid>
		<description><![CDATA[Hi, great blog. I love your &quot;filter&quot; and take on the world.

The article doesn&#039;t go into the details but does say that &quot;Lights are coordinated with every neighboring light, such that one light alerts the next, &lt;em&gt;Hey, heavy load coming through.&lt;/em&gt;”

From that statement I&#039;m inferring that the drum is not any one light or even every light. The system may not be that smart at all, but it certainly could be tied to a natural bottleneck as you suggest and use that as the drum, or the drum could be non-physical, as is the time of a strategic resource in project management.  This might look like optimizing throughput in a section or to some &quot;safe maximum&quot; rate. 

My guess is that by connecting the &lt;em&gt;in&lt;/em&gt; and &lt;em&gt;out&lt;/em&gt; sensors of a series of lights together that they&#039;ve created an implicit drum. Bohm meets Goldratt!

Another possibly interesting system might use something similar to a TOC inventory dollar days calculation &#8212; incorporating time spent in some road section before a tunnel or bridge and the toll charge for that vehicle. Public transportation and commuter vehicles that might not pay tolls could have a higher pseudo-toll for this calculation, enabling road managers and planners an easy mechanism for lane assignments, signal gating, and such, depending upon their goals (such as getting private cars in and out of suburbia or encouraging mass transit.)]]></description>
		<content:encoded><![CDATA[<p>Hi, great blog. I love your &#8220;filter&#8221; and take on the world.</p>
<p>The article doesn&#8217;t go into the details but does say that &#8220;Lights are coordinated with every neighboring light, such that one light alerts the next, <em>Hey, heavy load coming through.</em>”</p>
<p>From that statement I&#8217;m inferring that the drum is not any one light or even every light. The system may not be that smart at all, but it certainly could be tied to a natural bottleneck as you suggest and use that as the drum, or the drum could be non-physical, as is the time of a strategic resource in project management.  This might look like optimizing throughput in a section or to some &#8220;safe maximum&#8221; rate. </p>
<p>My guess is that by connecting the <em>in</em> and <em>out</em> sensors of a series of lights together that they&#8217;ve created an implicit drum. Bohm meets Goldratt!</p>
<p>Another possibly interesting system might use something similar to a TOC inventory dollar days calculation &mdash; incorporating time spent in some road section before a tunnel or bridge and the toll charge for that vehicle. Public transportation and commuter vehicles that might not pay tolls could have a higher pseudo-toll for this calculation, enabling road managers and planners an easy mechanism for lane assignments, signal gating, and such, depending upon their goals (such as getting private cars in and out of suburbia or encouraging mass transit.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isegoria</title>
		<link>https://www.isegoria.net/2010/10/to-tame-traffic-go-with-the-flow/comment-page-1/#comment-41461</link>
		<dc:creator>Isegoria</dc:creator>
		<pubDate>Tue, 02 Nov 2010 13:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.isegoria.net/?p=22313#comment-41461</guid>
		<description><![CDATA[That&#039;s interesting, Michael, because I was thinking just the opposite: &lt;em&gt;a system of local optima is not an optimal system at all&lt;/em&gt;.  Is it still &lt;em&gt;drum-buffer-rope&lt;/em&gt; if &lt;em&gt;every&lt;/em&gt; traffic light is a &lt;em&gt;drum&lt;/em&gt;?  Or would a canonical &lt;em&gt;drum-buffer-rope&lt;/em&gt; traffic system tie all the lights to the nearby tunnel or bridge?]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s interesting, Michael, because I was thinking just the opposite: <em>a system of local optima is not an optimal system at all</em>.  Is it still <em>drum-buffer-rope</em> if <em>every</em> traffic light is a <em>drum</em>?  Or would a canonical <em>drum-buffer-rope</em> traffic system tie all the lights to the nearby tunnel or bridge?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Clingan</title>
		<link>https://www.isegoria.net/2010/10/to-tame-traffic-go-with-the-flow/comment-page-1/#comment-41293</link>
		<dc:creator>Michael Clingan</dc:creator>
		<pubDate>Tue, 02 Nov 2010 00:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.isegoria.net/?p=22313#comment-41293</guid>
		<description><![CDATA[Great example of a Theory of Constraints Drum-Buffer-Rope application. The 56% reduction in average queue times is typical.

In this case the rope is the communications between traffic signals, the buffer is the &quot;right amount of time&quot; used as the delay and the drum is the rate at which the road can safely handle the traffic demand.

Put another way, the traditional traffic management approach is similar to Lean Manufacturing&#039;s balanced production lines, only with the balance keyed to the clock time to meet average demand. Unfortunately, due to all kinds of variables including accidents, weather, driver behavior and statistical variation, a bottleneck (traffic jam) can easily occur. This bottleneck can occur anywhere so it cannot be managed in advance and the system cannot recover until the load decreases.

Accidents, weather, etc. still affect the new traffic system in the posting but the system&#039;s simple intelligence can restore maximum throughput far more quickly.]]></description>
		<content:encoded><![CDATA[<p>Great example of a Theory of Constraints Drum-Buffer-Rope application. The 56% reduction in average queue times is typical.</p>
<p>In this case the rope is the communications between traffic signals, the buffer is the &#8220;right amount of time&#8221; used as the delay and the drum is the rate at which the road can safely handle the traffic demand.</p>
<p>Put another way, the traditional traffic management approach is similar to Lean Manufacturing&#8217;s balanced production lines, only with the balance keyed to the clock time to meet average demand. Unfortunately, due to all kinds of variables including accidents, weather, driver behavior and statistical variation, a bottleneck (traffic jam) can easily occur. This bottleneck can occur anywhere so it cannot be managed in advance and the system cannot recover until the load decreases.</p>
<p>Accidents, weather, etc. still affect the new traffic system in the posting but the system&#8217;s simple intelligence can restore maximum throughput far more quickly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
