<?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: Metro Audit Results</title>
	<atom:link href="http://seattletransitblog.com/2009/09/01/metro-audit-results/feed/" rel="self" type="application/rss+xml" />
	<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/</link>
	<description>Transit in the Greater Seattle Area</description>
	<lastBuildDate>Fri, 25 May 2012 19:00:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Metro Audit Report Complete - Seattle Transit Blog</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-68933</link>
		<dc:creator>Metro Audit Report Complete - Seattle Transit Blog</dc:creator>
		<pubDate>Fri, 18 Sep 2009 12:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-68933</guid>
		<description>[...] Auditor completed their report to the  Council on their full audit of Metro operations.   The first part of the presentation was on September 1, and identified up to $23m in annual savings with little downside, about $60m [...]</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
[...] Auditor completed their report to the  Council on their full audit of Metro operations.   The first part of the presentation was on September 1, and identified up to $23m in annual savings with little downside, about $60m [...]<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernie</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-67129</link>
		<dc:creator>Bernie</dc:creator>
		<pubDate>Thu, 10 Sep 2009 06:56:18 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-67129</guid>
		<description>So if the driver can disable Hush Mode I&#039;m even more confused as to why Metro paid to have it disabled (then enabled) for the two years the tunnel was closed. They couldn&#039;t just tell drivers to not use it?

Eats batteries? Deep discharge does kill batteries and if tunnel operations are indeed eating batteries I don&#039;t think that cost has been fairly factored into Metro&#039;s analysis. 

Even something as lame as GM&#039;s &quot;mild hybrid&quot; technology which shuts of the fossil fuel engine while stopped would seem to be a winner for surface operations. Not if you bought it just for that but if you own it already because it was needed for the tunnel then why not?</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
So if the driver can disable Hush Mode I&#8217;m even more confused as to why Metro paid to have it disabled (then enabled) for the two years the tunnel was closed. They couldn&#8217;t just tell drivers to not use it?</p>
<p>Eats batteries? Deep discharge does kill batteries and if tunnel operations are indeed eating batteries I don&#8217;t think that cost has been fairly factored into Metro&#8217;s analysis. </p>
<p>Even something as lame as GM&#8217;s &#8220;mild hybrid&#8221; technology which shuts of the fossil fuel engine while stopped would seem to be a winner for surface operations. Not if you bought it just for that but if you own it already because it was needed for the tunnel then why not?<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-67125</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Thu, 10 Sep 2009 06:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-67125</guid>
		<description>If it&#039;s the same 255 everyday, than it might just be a driver thing.  The same coach usually isn&#039;t put on the same piece of work everyday.  All the hybrid I drive through the tunnel never have problems with Hush Mode, so I think its probably just a Operater Error, not using it.  Is it always the same driver?</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
If it&#8217;s the same 255 everyday, than it might just be a driver thing.  The same coach usually isn&#8217;t put on the same piece of work everyday.  All the hybrid I drive through the tunnel never have problems with Hush Mode, so I think its probably just a Operater Error, not using it.  Is it always the same driver?<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-67124</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Thu, 10 Sep 2009 06:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-67124</guid>
		<description>In hush mode, the coach is much quieter.  Maybe not when idling, but when the coach takes of in Hush mode, its much quieter.  The name &quot;Huah&quot; wasn&#039;t just givien because of the the noise level, it stand for &quot;Hybrid Ultralow Sound &amp; Hydrocarbons&quot;</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
In hush mode, the coach is much quieter.  Maybe not when idling, but when the coach takes of in Hush mode, its much quieter.  The name &#8220;Huah&#8221; wasn&#8217;t just givien because of the the noise level, it stand for &#8220;Hybrid Ultralow Sound &amp; Hydrocarbons&#8221;<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-67122</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Thu, 10 Sep 2009 06:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-67122</guid>
		<description>You don&#039;t really want to use HUSH mode on streets because they only run at about 90 horsepower.  Not much throttle response.  In the tunnel, after you leave one station, you don&#039;t want to take your foot off the gas until the next stastion or you could lose alot of momentum.  Wouldn&#039;t be great driving them in city traffic.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
You don&#8217;t really want to use HUSH mode on streets because they only run at about 90 horsepower.  Not much throttle response.  In the tunnel, after you leave one station, you don&#8217;t want to take your foot off the gas until the next stastion or you could lose alot of momentum.  Wouldn&#8217;t be great driving them in city traffic.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-67118</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Thu, 10 Sep 2009 05:54:34 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-67118</guid>
		<description>Metro did shifts some routes around to different bases to save deadheading.  342, used to deadhead from Bell Base to Shoreline P&amp;R, then back from Renton to Bellevue.  The 167 used to Deadhead from Central Base downtown, to Renton.  Run the trip to the U. District then deadhead back to Central.  So last summer I believe, some 342&#039;s and some 167&#039;s went to North Base.  Some stayed at Central and Bellevue Base.  So for example now, AM rush hour.....Coach leaves North base to Shorline P&amp;R (short deadhead), 342 to Renton, 167 from Renton to the UW.  Then a fairly short deadhead back to North Base.  Sucks for us drivers, because I love deadheads, but saves hours and fuel.  But, you can do this completely.  Some areas just need very frequent service in one direction, and not in the other.  Plus deadheading can be much faster than running the trip on the way back.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Metro did shifts some routes around to different bases to save deadheading.  342, used to deadhead from Bell Base to Shoreline P&amp;R, then back from Renton to Bellevue.  The 167 used to Deadhead from Central Base downtown, to Renton.  Run the trip to the U. District then deadhead back to Central.  So last summer I believe, some 342&#8242;s and some 167&#8242;s went to North Base.  Some stayed at Central and Bellevue Base.  So for example now, AM rush hour&#8230;..Coach leaves North base to Shorline P&amp;R (short deadhead), 342 to Renton, 167 from Renton to the UW.  Then a fairly short deadhead back to North Base.  Sucks for us drivers, because I love deadheads, but saves hours and fuel.  But, you can do this completely.  Some areas just need very frequent service in one direction, and not in the other.  Plus deadheading can be much faster than running the trip on the way back.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Welch</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-67030</link>
		<dc:creator>Jeff Welch</dc:creator>
		<pubDate>Thu, 10 Sep 2009 01:16:13 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-67030</guid>
		<description>Bernie,

No.  A part-time driver has to work an AVERAGE of 20 hours per week or more over 6 months to qualify for fully paid medical for the driver only.  Benefits for full-timers include paid (or partially paid) medical, dental, and vision coverage not only for the driver but for dependent family members.

I do not believe that it is cheaper to pay overtime than paying straight time, particularly when you add up the numbers.  Remember, overtime for a driver at top scale (takes about 5 years or less depending) is 41.25 per hour.  That means 10 hours of overtime costs the county $412.50 (more really if you factor in the corresponding increase in pension benefits as well).  The same amount in straight time if paid to a junior part-timer would be $192.50 - a difference of 220.00 for every 10 hours of overtime.

I believe that the contractual restriction against part-timers working eventings and weekends is specifically included in the union&#039;s contract language to protect overtime for full-timers, and has nothing to do with cost savings to the county.  Again - risking having my house burned down by full-timers-of-which-I-hope-to-be-one, I believe that a genuine cost analysis would show a substantial savings if some of that overtime were paid as straight time to willing part-timers.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Bernie,</p>
<p>No.  A part-time driver has to work an AVERAGE of 20 hours per week or more over 6 months to qualify for fully paid medical for the driver only.  Benefits for full-timers include paid (or partially paid) medical, dental, and vision coverage not only for the driver but for dependent family members.</p>
<p>I do not believe that it is cheaper to pay overtime than paying straight time, particularly when you add up the numbers.  Remember, overtime for a driver at top scale (takes about 5 years or less depending) is 41.25 per hour.  That means 10 hours of overtime costs the county $412.50 (more really if you factor in the corresponding increase in pension benefits as well).  The same amount in straight time if paid to a junior part-timer would be $192.50 &#8211; a difference of 220.00 for every 10 hours of overtime.</p>
<p>I believe that the contractual restriction against part-timers working eventings and weekends is specifically included in the union&#8217;s contract language to protect overtime for full-timers, and has nothing to do with cost savings to the county.  Again &#8211; risking having my house burned down by full-timers-of-which-I-hope-to-be-one, I believe that a genuine cost analysis would show a substantial savings if some of that overtime were paid as straight time to willing part-timers.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernie</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66709</link>
		<dc:creator>Bernie</dc:creator>
		<pubDate>Tue, 08 Sep 2009 04:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66709</guid>
		<description>But isn&#039;t the issue that if &quot;part-timers&quot; get more than 20 hours a week then Metro is required to provide full time benefits? That&#039;s why it&#039;s cheaper to pay over time.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
But isn&#8217;t the issue that if &#8220;part-timers&#8221; get more than 20 hours a week then Metro is required to provide full time benefits? That&#8217;s why it&#8217;s cheaper to pay over time.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Welch</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66701</link>
		<dc:creator>Jeff Welch</dc:creator>
		<pubDate>Tue, 08 Sep 2009 04:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66701</guid>
		<description>VB,

Two issues being confused here.  My point is that as a part-timer scrounding for more than the 3.5 hours a day of regular work that I have, I - an EXISTING employee - am not permitted to work evenings or weekends.  Someone calls in sick on a piece that runs after 8pm?  I can&#039;t work it.  Someone has an RDO that doesn&#039;t include weekends?  I can&#039;t work their Saturday or Sunday piece.  Under the current contract, the County HAS to pay full-timers overtime - even though there are a hell of a lot of part-timers out there willing to do the same work for straight-time.

Again - hoping nobody burns down my house for pointing this out.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
VB,</p>
<p>Two issues being confused here.  My point is that as a part-timer scrounding for more than the 3.5 hours a day of regular work that I have, I &#8211; an EXISTING employee &#8211; am not permitted to work evenings or weekends.  Someone calls in sick on a piece that runs after 8pm?  I can&#8217;t work it.  Someone has an RDO that doesn&#8217;t include weekends?  I can&#8217;t work their Saturday or Sunday piece.  Under the current contract, the County HAS to pay full-timers overtime &#8211; even though there are a hell of a lot of part-timers out there willing to do the same work for straight-time.</p>
<p>Again &#8211; hoping nobody burns down my house for pointing this out.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VeloBusDriver</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66206</link>
		<dc:creator>VeloBusDriver</dc:creator>
		<pubDate>Fri, 04 Sep 2009 18:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66206</guid>
		<description>There are other costs associated with having employees on the books.  Training, uniform allowance, health insurance, facilities, etc...  Paying overtime, even on a regular basis, sometimes will be less expensive than hiring a new employee and figuring out how to get them into the schedule so you don&#039;t have to pay the 2 or 3 hours in overtime.  This is especially true for weekend runs and the remainder of a 4/40 work schedule where you are only paying OT for 1 or 2 days a week.

The Machinists at Boeing were still complaining about getting TOO MUCH overtime as part of their 2008 contract.  Boeing shoves all that OT down the Machinists throats because they have determined it is less expensive than hiring new employees.  In many cases, I&#039;m sure Metro management and planners have come to the same conclusion.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
There are other costs associated with having employees on the books.  Training, uniform allowance, health insurance, facilities, etc&#8230;  Paying overtime, even on a regular basis, sometimes will be less expensive than hiring a new employee and figuring out how to get them into the schedule so you don&#8217;t have to pay the 2 or 3 hours in overtime.  This is especially true for weekend runs and the remainder of a 4/40 work schedule where you are only paying OT for 1 or 2 days a week.</p>
<p>The Machinists at Boeing were still complaining about getting TOO MUCH overtime as part of their 2008 contract.  Boeing shoves all that OT down the Machinists throats because they have determined it is less expensive than hiring new employees.  In many cases, I&#8217;m sure Metro management and planners have come to the same conclusion.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2Tall</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66187</link>
		<dc:creator>2Tall</dc:creator>
		<pubDate>Fri, 04 Sep 2009 15:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66187</guid>
		<description>Riding the bus is not the way to look at the real running time.  It&#039;s a one-time snapshot which isn&#039;t representative.  Looking at the on-time data on multiple trips is representative.  

Here&#039;s what I would do:

Pull the OTP data and look what the 95th percentile running time is.  Next, I would look to see how the real running time relates to the scheduled runnig time and determine what the &quot;real&quot; recovery time is.    

Next, I would see if it were possible to reduce recovery time by 15 minutes (Route 70 has mostly 15-minute headways, and thus you&#039;d need to reduce recovery by a minimum of 15 minutes to pull a bus out of the schedule and maintain existing service levels).
 
If you can&#039;t reduce recovery by 15 minutes and have maintain some recovery time, then you wouldn&#039;t do it.

Where you put the layover is not so important - it&#039;s a short route.  It could be 5 minutes on one end and 20 on the other, or 10 and 15 on either end.  The key being is that you&#039;d put a minimum of 5 at one end.

Let me be clear that recovery/layover is necessary for schedule reliability and operator health/comfort.  The key question is how much layover/recovery is necessary.  30 pecent of time spent in recovery/layover is unquestionably high.

I strongly suspect that the real running time data would show that you can reduce recovery time by a total of 15 minutes and pull a bus out of Route 70 schedule during weekday morning/middays.  This still leaves an operator with over 25 minutes of recovery time every round trip, which is not unreasonable.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Riding the bus is not the way to look at the real running time.  It&#8217;s a one-time snapshot which isn&#8217;t representative.  Looking at the on-time data on multiple trips is representative.  </p>
<p>Here&#8217;s what I would do:</p>
<p>Pull the OTP data and look what the 95th percentile running time is.  Next, I would look to see how the real running time relates to the scheduled runnig time and determine what the &#8220;real&#8221; recovery time is.    </p>
<p>Next, I would see if it were possible to reduce recovery time by 15 minutes (Route 70 has mostly 15-minute headways, and thus you&#8217;d need to reduce recovery by a minimum of 15 minutes to pull a bus out of the schedule and maintain existing service levels).</p>
<p>If you can&#8217;t reduce recovery by 15 minutes and have maintain some recovery time, then you wouldn&#8217;t do it.</p>
<p>Where you put the layover is not so important &#8211; it&#8217;s a short route.  It could be 5 minutes on one end and 20 on the other, or 10 and 15 on either end.  The key being is that you&#8217;d put a minimum of 5 at one end.</p>
<p>Let me be clear that recovery/layover is necessary for schedule reliability and operator health/comfort.  The key question is how much layover/recovery is necessary.  30 pecent of time spent in recovery/layover is unquestionably high.</p>
<p>I strongly suspect that the real running time data would show that you can reduce recovery time by a total of 15 minutes and pull a bus out of Route 70 schedule during weekday morning/middays.  This still leaves an operator with over 25 minutes of recovery time every round trip, which is not unreasonable.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Welch</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66142</link>
		<dc:creator>Jeff Welch</dc:creator>
		<pubDate>Fri, 04 Sep 2009 04:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66142</guid>
		<description>Buses yes, wires no.

You do realize that ETB&#039;s rely on a network of thousands of miles of overhead wiring and a dozen or so power relay stations, right?</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Buses yes, wires no.</p>
<p>You do realize that ETB&#8217;s rely on a network of thousands of miles of overhead wiring and a dozen or so power relay stations, right?<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66124</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 04 Sep 2009 00:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66124</guid>
		<description>Yes, check it Fridays.  I think the diesels on weekdays are only there for fill in, but you&#039;d know better than me.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Yes, check it Fridays.  I think the diesels on weekdays are only there for fill in, but you&#8217;d know better than me.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Welch</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66096</link>
		<dc:creator>Jeff Welch</dc:creator>
		<pubDate>Thu, 03 Sep 2009 20:55:07 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66096</guid>
		<description>2Tall,

Let&#039;s take a closer look at that run card data:

The total shift time (not counting the 10 minute sign-in/inspection time) is 5 hours and 26 minutes - or 326 minutes.

The 070/02 VT (CMBO210-1) has the following layovers/recovery times:

6:43-6:51 am - 8 minutes (at Brooklyn/NE 50th St.)

7:28-7:53 am - 25 minutes (3rd S. and S. Main)

8:30-8:51 am - 21 minutes (Brooklyn and NE 50th St.)

9:29-9:53 am - 24 minutes (3rd S. and S. Main)

10:28-10:51 am - 23 minutes (Brooklyn and NE 50th St.)

Total cumulative recovery time:  101 minutes

So yes - your math is pretty spot on.

Now - this is a WEEKDAY run.

Guess what happens during weekdays?  Traffic.  That means that this recovery time is dang near always used for - wait for it - RECOVERY.

I challenge you to actually RIDE that run, and you&#039;ll see how much time is actually spent &quot;in-service&quot;.  On some morings if not most, I guarantee you that driver gets maybe half that time, if at all.

So given that you&#039;ve pulled this rush-hour weekday example - how would YOU make it more &quot;efficient&quot; (assuming that having the bus parked for more than 30 seconds is in your view somehow &quot;inefficient&quot;?

You&#039;ve got the run - card - show us what YOUR schedule would look like.  Would you cut the recovery time at either Harvard or Main in half?  More?

Do tell.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
2Tall,</p>
<p>Let&#8217;s take a closer look at that run card data:</p>
<p>The total shift time (not counting the 10 minute sign-in/inspection time) is 5 hours and 26 minutes &#8211; or 326 minutes.</p>
<p>The 070/02 VT (CMBO210-1) has the following layovers/recovery times:</p>
<p>6:43-6:51 am &#8211; 8 minutes (at Brooklyn/NE 50th St.)</p>
<p>7:28-7:53 am &#8211; 25 minutes (3rd S. and S. Main)</p>
<p>8:30-8:51 am &#8211; 21 minutes (Brooklyn and NE 50th St.)</p>
<p>9:29-9:53 am &#8211; 24 minutes (3rd S. and S. Main)</p>
<p>10:28-10:51 am &#8211; 23 minutes (Brooklyn and NE 50th St.)</p>
<p>Total cumulative recovery time:  101 minutes</p>
<p>So yes &#8211; your math is pretty spot on.</p>
<p>Now &#8211; this is a WEEKDAY run.</p>
<p>Guess what happens during weekdays?  Traffic.  That means that this recovery time is dang near always used for &#8211; wait for it &#8211; RECOVERY.</p>
<p>I challenge you to actually RIDE that run, and you&#8217;ll see how much time is actually spent &#8220;in-service&#8221;.  On some morings if not most, I guarantee you that driver gets maybe half that time, if at all.</p>
<p>So given that you&#8217;ve pulled this rush-hour weekday example &#8211; how would YOU make it more &#8220;efficient&#8221; (assuming that having the bus parked for more than 30 seconds is in your view somehow &#8220;inefficient&#8221;?</p>
<p>You&#8217;ve got the run &#8211; card &#8211; show us what YOUR schedule would look like.  Would you cut the recovery time at either Harvard or Main in half?  More?</p>
<p>Do tell.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Welch</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66088</link>
		<dc:creator>Jeff Welch</dc:creator>
		<pubDate>Thu, 03 Sep 2009 20:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66088</guid>
		<description>Nathanial,

&lt;b&gt;This means that the only possible reason for trolleybuses “costing more” over the lifecycle is a shortage of trolleybus manufacturers, causing the prices to go up.&lt;/b&gt;

No, the reason that trolleys cost more to run is that you not only have to factor the cost of the equipment that&#039;s driven in - but the cost of thousands of miles of overhead wiring to feed them power.

It&#039;s the maintenance of the overhead wiring that drives up the cost of running ETB&#039;s.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Nathanial,</p>
<p><b>This means that the only possible reason for trolleybuses “costing more” over the lifecycle is a shortage of trolleybus manufacturers, causing the prices to go up.</b></p>
<p>No, the reason that trolleys cost more to run is that you not only have to factor the cost of the equipment that&#8217;s driven in &#8211; but the cost of thousands of miles of overhead wiring to feed them power.</p>
<p>It&#8217;s the maintenance of the overhead wiring that drives up the cost of running ETB&#8217;s.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2Tall</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66040</link>
		<dc:creator>2Tall</dc:creator>
		<pubDate>Thu, 03 Sep 2009 17:19:31 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66040</guid>
		<description>Here&#039;s your route.  (Thanks Oran)

Route 70

37/38 minute one-way run time with over 20 minutes of layover.  In each direction during a.m. and midday.  

Specifically, on 070/02VT CMBO 210-1 (Atlantic Base), the operator between 6:07 a.m. and 11:28 a.m. has 101 minutes of recovery/layover and that operator is &quot;in service&quot; for 320 minutes.  31 percent of time is spent on recover/layover.  I hope my math is right.
 
It would appear that Route 70 during certain times can be operated with less layover and one less bus.  Even with bridge lifts.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Here&#8217;s your route.  (Thanks Oran)</p>
<p>Route 70</p>
<p>37/38 minute one-way run time with over 20 minutes of layover.  In each direction during a.m. and midday.  </p>
<p>Specifically, on 070/02VT CMBO 210-1 (Atlantic Base), the operator between 6:07 a.m. and 11:28 a.m. has 101 minutes of recovery/layover and that operator is &#8220;in service&#8221; for 320 minutes.  31 percent of time is spent on recover/layover.  I hope my math is right.</p>
<p>It would appear that Route 70 during certain times can be operated with less layover and one less bus.  Even with bridge lifts.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: "Bus fan"</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66027</link>
		<dc:creator>"Bus fan"</dc:creator>
		<pubDate>Thu, 03 Sep 2009 16:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66027</guid>
		<description>I&#039;ve noticed that there&#039;s always this one 255 bus that runs in diesel mode in the tunnel - its this one specific purple hybrid bus that has this problem. I&#039;ve never really bothered to remember the fleet number, though.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I&#8217;ve noticed that there&#8217;s always this one 255 bus that runs in diesel mode in the tunnel &#8211; its this one specific purple hybrid bus that has this problem. I&#8217;ve never really bothered to remember the fleet number, though.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oran Viriyincy</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66026</link>
		<dc:creator>Oran Viriyincy</dc:creator>
		<pubDate>Thu, 03 Sep 2009 16:30:54 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66026</guid>
		<description>KC Metro Work assignments and run cards are publicly available at

http://www.atu587.com/about-divisions-kcmto.html</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
KC Metro Work assignments and run cards are publicly available at</p>
<p><a href="http://www.atu587.com/about-divisions-kcmto.html" rel="nofollow">http://www.atu587.com/about-divisions-kcmto.html</a><!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2Tall</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66006</link>
		<dc:creator>2Tall</dc:creator>
		<pubDate>Thu, 03 Sep 2009 15:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66006</guid>
		<description>Jeff,

Thank you for going and looking this up.  

Specific routes that have warrants for less layover?  

I&#039;m going to have to pull some schedules and give you some examples. (I do not have access to the run cards like you do).</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Jeff,</p>
<p>Thank you for going and looking this up.  </p>
<p>Specific routes that have warrants for less layover?  </p>
<p>I&#8217;m going to have to pull some schedules and give you some examples. (I do not have access to the run cards like you do).<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael</title>
		<link>http://seattletransitblog.com/2009/09/01/metro-audit-results/#comment-66004</link>
		<dc:creator>Nathanael</dc:creator>
		<pubDate>Thu, 03 Sep 2009 15:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7684#comment-66004</guid>
		<description>OK, so others are saying the savings are illusory, and are due to assuming that all trolleybuses are as bad as the Breda&#039;s currently in use.  When in fact most trolleybuses are substantially more efficient and lower maintenance.  :-/</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
OK, so others are saying the savings are illusory, and are due to assuming that all trolleybuses are as bad as the Breda&#8217;s currently in use.  When in fact most trolleybuses are substantially more efficient and lower maintenance.  :-/<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Database Caching 2/4 queries in 0.001 seconds using disk
Object Caching 424/428 objects using disk

Served from: seattletransitblog.com @ 2012-05-25 12:39:45 -->
