This page contains a single entry from the blog posted on November 9, 2010 6:46 AM.
The previous post in this blog was Pot can make you stupid.
The next post in this blog is Showdown in Seattle.
Many more can be found on the main index page or by looking through the archives.
New Portland city computer system officially pronounced a fiasco
When the city auditor, who usually plays patty-cake with politicians and bureaucrats alike, tells you you've screwed up, then you've really screwed up. She reports:
Instead of a $14 million, 14-month implementation as planned, the reported project costs exceeded $47 million and took over 30 months to implement. These significant increases to the originally planned costs and schedule were made worse because some of the planned system functions are not complete and other functions were eliminated as the project developed. In addition, the City’s intent to eliminate secondary or "shadow" systems remains incomplete....
Moreover, the City did not appear to heed some of the warnings from its experience with prior City projects. As it was beginning the process to select and implement the new system, the City compiled a listing of lessons learned from past City projects. The City also recognized the opportunity to learn from problems experienced during this project and issued a "Lessons Learned" document in April 2010. However, we noted concerns in the April report that were similar to concerns in the previous report.
That sounds like an apt new motto for the city: "We Never Learn."
As it continues to increase its knowledge of how to operate and maintain the system, the City may incur up to $4.4 million for consultants to provide operating and maintenance services. Further, the long-term maintenance and support costs of the new software are expected to be higher than the costs of the old software. Because the new SAP software is highly complex, the City anticipates it will need additional staff and training to properly maintain and operate the software. In the City’s FY 2010-11 budget, Council approved additional personnel to maintain and operate the SAP software and to support SAP users. These new positions are also expected to help implement additional SAP software functions, some of which were originally planned to be available once the software went live. City bureaus using the new software will pay for these additional costs through increased fees.
BFD - I'd like to see an action plan or some heads on a stick. Isn't this the 26th computer system CoP has screwed up?
"The outside firm hired by the City to provide quality assurance
services repeatedly warned the City about concerns around project
governance and management."
Maybe if Samdy's proteges would stop spending time making PowerPoints telling the world how smart they are, they might have time to focus on stuff like this.
Lesson learned - NEVER ever vote for any CoP bond, it'll just get all p!ssed away.
I wonder what kind of sales job the City got from vendors? If you recall the water bureaus' computer fiasco, as well as the many similar stories from cities across the country, I am sure that government is precieved to be 'easy marks'.
If IT costs were 300% over budget in the private sector, heads would roll. If rollout was so far off the mark, somebody would be called to account.
At the same time, I do have to give props to the Auditor. I have been watching her since she took office and she is not one in the limelight, but she always speaks truth to power. Shes a keeper, the 'other' member of a pretty forgettable city council.
I think Dave Lister wrote about this awhile back in The O. He pointed out that it's not the software itself that's the problem necessarily, it's the bungled business processes the software is supposed to support. Garbage in, garbage out, as the programmers used to say. And I'll go further and say that it's our bungled up, multi-bureau, commission form of government that creates the bungled processes that creates the bungled software implementations. If all the bureaus could agree to a common set of standards for payroll, billing, timeclock, ERP, CRM and other back-office processes, the software could almost write itself.
Others have pointed out there are some huge drawbacks to the strong-mayor model -- namely, we shudder at the thought of Sam or Randy with unlimited power -- but if we are going to continue our decentralized, devolved system of competing commissioners with their feuding fiefdoms in the bureaus, we have to be willing to accept this waste of taxpayer money on inefficiencies and redundancies as all but a fact of life.
SAP software is notoriously rigid and they are very transparent about the need to adapt your business practices to the software, rather than trying to customize it.
I'm shocked and dismayed they will pass these cost overruns on to Portlanders who had no say in the matter. Ditto for the Sellwood Bridge registration fees, the leaf pickup fees, the doubling of parking meter rates and parking/traffic fines, and a 50% increase in water/sewer rates.
Portland's voters can't say they haven't been punished over and over again for returning the same incumbents to office term after term.
After watching the Wate Bureau software debacle this comes as no surprise. They just circle the wagons and support each other's decisions, with a promotion or two thrown in. What idiots we are to put up with this.
SAP software is notoriously rigid and they are very transparent about the need to adapt your business practices to the software, rather than trying to customize it.
I don't doubt that's true, although Oracle has other shackles (namely on pricing) it forces its customers into as well. While customization is of course inevitable (and maybe SAP was the wrong choice for this for that reason, as you point out), the city still needs to standardize and integrate its processes. I mean, 200 different systems or applications are in use across all the offices and bureaus??!!
If that is true of SAP, Mr. Tee, then why are we in this mess? There is nothing left about a rigid system that doesn't do the job, except to quit or to start over, which apparently they did and we are paying the engineering costs.
And it does signal the end of the American dream. I don’t agree with everything in the Der Spiegel piece, but the overarching theme is correct – Americans were taught that they could have it better than their parents, through hard work and initiative. And that’s not necessarily true anymore. We have an economic system tilted to the benefit of a several-block radius in Lower Manhattan known as Wall Street. We have a political system bought and paid for by those corporate interests. We have a legal system where power and influence can buy justice. And we have a culture of accountability that’s in tatters. So out of all of that, you get scam artists making fake courtrooms and stealing from people, basically assuming the robes of justice themselves in the absence of any competition.
It’s inequality, not just income inequality but inequality of opportunity, upward mobility and justice that drives this. In these times, it couldn’t be more important for community groups to band together, work with their neighbors and build a collective voice. It’s almost the only hope left.
Eric,
Yes, I did write about it in May of 2008 when the problems first began to emerge. The other thing I've written, both on the SAP system and the Water Billing is that the city's own RFP (request for proposal) processes help ensure failure. You can probably find my piece on the water billing by googling "Dripping Dollars". It was in Brainstorm NW magazine back in July 2003.
Dave
If you look into a thing like this, what you're likely to find is that most of the problems come from customization. And most of the pressure for customization comes from — wait for it — the customer. People in the city's administration start with the view that their idiosyncratic ways are necessary, or better, or both, than the ways provided in the standard package. As far as I am concerned, they should be able to run the city on Excel. Or maybe Quicken.
Allan L., so you think that "pressure for customization comes from-...the customer.???
Think of how many customers call or come down to all the bureaus and ask for more customizing of the computer programs-most of us don't even know how to even ask, don't care, or that we can for more diversity in all the 300 city programs. The lady trying to pay her water bill isn't interested in how many gallons she used 10 years ago-only the bureaucrats do.
It's like when I went down to BDS last week to review possible sewer hook up on an undeveloped city lot. The staff person brought up a sewer street plan that showed the information, but then he said that he could use another program that would highlight in color the sewer lines. How many programs can the commoner afford? He can't.
Might add, not only does the faucet have to be tightened, but the line has to be shut off.
Similar to what the water bureau does to customers who aren't able to pay.
It appears that the City adopted a number of guiding principles at the outset of the SAP implementation that may have helped it to stay closer to schedule and to control costs, then proceeded to violate most of those principles. The City may have tried to do too much in one step, but it seemed to lack an effective overall plan and the ability to make timely decisions to modify the plan when things went south. When Bureaus were faced with the need to change their diverse, outdated business practices to conform to a common set of accepted business practices embodied in SAP, many Bureaus resisted the change, and the City often caved in to those Bureaus. This led to many customizations and interfaces and greatly increased project costs. Responsibility for poor planning and decision making lies with City leaders and management, not the consultants.
SAP may not have been the right system for the City but it has invested more than $47 million in SAP, so it will be around for quite a while. The City that mis-managed the implementation will continue to struggle with SAP unless it finds the ability to standardize the way it does business, requires Bureaus to use SAP rather than their home grown systems and finds more employees with the ability to operate and maintain SAP. Look for ever increasing costs for consultants and contractors to operate and maintain the system. These costs will consume more of your taxes and be relected in increased utility rates and more user fees like the leaf pickup fee.
lw -- I'm pretty sure that when Allan was talking about customer demands, he was referring to the city's role as the customer purchasing the software.
I'm inclined to agree with his other point; couldn't something like 85 percent of the city's business be taken care of via Word, Excel, Access Outlook and their equivalents?
Roger, you're probably right in interpreting Allan. But I was making the point that the customer is not CoP but us.
Do we need three or four programs to display a map? Is that what the true customer, us, needs? For example, does a retail paint store have numerous, duplicating programs to handle the customer buying a can of paint? If they do, paid the price for the numerous programs, then they'll eventually be out of business. Same for this city.
Can't believe nobody (quite) said "Opie lives." Will real people, and real little people, pay for these terrible mistakes as they did with the Water Department fiasco?
Charamba, Douro 2008
Horse Heaven Hills, Cabernet 2010
Lorelle, Horse Heaven Hills Pinot Grigio 2011
Avignonesi, Montepulciano 2004
Lorelle, Willamette Valley Pinot Noir 2011
Villa Antinori, Toscana 2007
Mercedes Eguren, Cabernet Sauvignon 2009
Lorelle, Columbia Valley Cabernet 2011
Purple Moon, Merlot 2011
Purple Moon, Chardonnnay 2011
Abacela, Vintner's Blend No. 12
Opula Red Blend 2010
Liberte, Pinot Noir 2010
Chateau Ste. Michelle, Indian Wells Red Blend 2010
Woodbridge, Chardonnay 2011
King Estate, Pinot Noir 2011
Famille Perrin, Cotes du Rhone Villages 2010
Columbia Crest, Les Chevaux Red 2010
14 Hands, Hot to Trot White Blend
Familia Bianchi, Malbec 2009
Terrapin Cellars, Pinot Gris 2011
Columbia Crest, Walter Clore Private Reserve 2009
Campo Viejo, Rioja, Termpranillo 2010
Ravenswood, Cabernet Sauvignon 2009
Quinta das Amoras, Vinho Tinto 2010
Waterbrook, Reserve Merlot 2009
Lorelle, Horse Heaven Hills, Pinot Grigio 2011
Tarantas, Rose
Chateau Lajarre, Bordeaux 2009
La Vielle Ferme, Rose 2011
Benvolio, Pinot Grigio 2011
Nobilo Icon, Pinot Noir 2009
Lello, Douro Tinto 2009
Quinson Fils, Cotes de Provence Rose 2011
Anindor, Pinot Gris 2010
Buenas Ondas, Syrah Rose 2010
Les Fiefs d'Anglars, Malbec 2009
14 Hands, Pinot Gris 2011
Conundrum 2012
Condes de Albarei, Albariño 2011
Columbia Crest, Walter Clore Private Reserve 2007
Penelope Sanchez, Garnacha Syrah 2010
Canoe Ridge, Merlot 2007
Atalaya do Mar, Godello 2010
Vega Montan, Mencia
Benvolio, Pinot Grigio
Nobilo Icon, Pinot Noir, Marlborough 2009
Portuga, Rose 2011
Revelation, Chardonnay, Pays d'Oc 2010
Beaulieu, Cabernet, Rutherford 2005
Monte Alto, Tinto Reserva 2005
Chateau Ste. Michelle, Cabernet, Indian Wells 2009
Espiral, Vinho Rose
Vin-Koru, Pinot Gris 2011
14 Hands, Hot to Trot Red 2009
Rodney Strong, Cabernet, Sonoma 2009
Abacela, Vintner's Blend #11
Portuga, White 2010
La Bourgeoisie, Red 2009
Januik, Red 2009
Three Rivers, River's Red 2008
Kirkland, Alexander Valley Merlot 2008
Muga, Rioja Rose 2010
Quinta das Amoras, Vinho Tinto 2009
Mauro Molino, Barbera d'Alba 2009
Garda Chiaretto Rose
Columbia Crest, Two Vines Vineyard 10 White
Chateau Ste. Michelle, Pinot Gris, Columbia Valley 2009
L'Hortus, Rose de Saignee 2010
Maculan, Pino & Toi 2008
McKinley Springs, Bombing Range Red 2008
Trader Joe's Pinot Gris 2009
Montes Alpha, Cabernet 2007
Gran Sasso, Sangiovese, Terre di Chieti 2009
Garda, Classico Chiaretto Rose
Beaulieu, Cabernet, Rutherford 1999
Picos del Montgo, Tempranillo 2008
Chateau de Montmirail, Vacqueyras 2008
La Granja 360, Syrah 2009
Montgras, Carmenere Reserva 2009
Lange, Pinot Gris 2009
Columbia Crest, Horse Heaven Hills Cabernet 2008
Kirkland, Pinot Grigio 2010
Trader Joe's Coastal Syrah 2009
Columbia Crest, Horse Heaven Hills Merlot 2008
Trader Joe's Coastal Chardonnay 2009
Vieux Papes Red
Domaine de l'Aujardiere, Chardonnay 2009
Santa Rita, Cabernet, Medalla Real 2007
Penfold's, Koonunga Hill Shiraz Cabernet 2008
Guild, Red, Lot #02 2008
Dievole, Dievolino Sangiovese 2008
Laforet, Burgogne Chardonnay 2009
Columbia Winery, Merlot 2007
Bonterra, Cabernet 2008
Elk Cove, Pinot Gris 2009
Maquis Lien 2006
Scott Paul, Pinot Noir, Le Paulee 2007
The Occasional Book
Neil Young - Waging Heavy Peace
Mark Bego - Aretha Franklin, the Queen of Soul (2012 ed.)
Jenny Lawson - Let's Pretend This Never Happened
J.D. Salinger - Franny and Zooey
Charles Dickens - A Christmas Carol
Timothy Egan - The Big Burn
Deborah Eisenberg - Transactions in a Foreign Currency
Kurt Vonnegut Jr. - Slaughterhouse Five
Kathryn Lance - Pandora's Genes
Cheryl Strayed - Wild
Fyodor Dostoyevsky - The Brothers Karamazov
Jack London - The House of Pride, and Other Tales of Hawaii
Jack Walker - The Extraordinary Rendition of Vincent Dellamaria
Colum McCann - Let the Great World Spin
Niccolò Machiavelli - The Prince
Harper Lee - To Kill a Mockingbird
Emma McLaughlin & Nicola Kraus - The Nanny Diaries
Brian Selznick - The Invention of Hugo Cabret
Sharon Creech - Walk Two Moons
Keith Richards - Life
F. Sionil Jose - Dusk
Natalie Babbitt - Tuck Everlasting
Justin Halpern - S#*t My Dad Says
Mark Herrmann - The Curmudgeon's Guide to Practicing Law
Barry Glassner - The Gospel of Food
Phil Stanford - The Peyton-Allan Files
Jesse Katz - The Opposite Field
Evelyn Waugh - Brideshead Revisited
J.K. Rowling - Harry Potter and the Sorcerer's Stone
David Sedaris - Holidays on Ice
Donald Miller - A Million Miles in a Thousand Years
Mitch Albom - Have a Little Faith
C.S. Lewis - The Magician's Nephew
F. Scott Fitzgerald - The Great Gatsby
William Shakespeare - A Midsummer Night's Dream
Ivan Doig - Bucking the Sun
Penda Diakité - I Lost My Tooth in Africa
Grace Lin - The Year of the Rat
Oscar Hijuelos - Mr. Ives' Christmas
Madeline L'Engle - A Wrinkle in Time
Steven Hart - The Last Three Miles
David Sedaris - Me Talk Pretty One Day
Karen Armstrong - The Spiral Staircase
Charles Larson - The Portland Murders
Adrian Wojnarowski - The Miracle of St. Anthony
William H. Colby - Long Goodbye
Steven D. Stark - Meet the Beatles
Phil Stanford - Portland Confidential
Rick Moody - Garden State
Jonathan Schwartz - All in Good Time
David Sedaris - Dress Your Family in Corduroy and Denim
Anthony Holden - Big Deal
Robert J. Spitzer - The Spirit of Leadership
James McManus - Positively Fifth Street
Jeff Noon - Vurt
Road Work
Miles run year to date: 21
At this date last year: 52
Total run in 2012: 129
In 2011: 113
In 2010: 125
In 2009: 67
In 2008: 28
In 2007: 113
In 2006: 100
In 2005: 149
In 2004: 204
In 2003: 269
Comments (31)
"We Never Learn." Indeed. SAP software? Oh, that's too on the nose!
Posted by Bill Barstad | November 9, 2010 7:01 AM
Nothing to worry about. The central system in this project -- the firewall that separates authority from accountability -- is up and running.
Posted by Allan L. | November 9, 2010 7:05 AM
Its not their money. They dont care.
Posted by mk | November 9, 2010 7:16 AM
The comic strip Dilbert comes to mind.
Posted by Michelle | November 9, 2010 7:19 AM
I love page 7, the Oregonian will report that the city "saved" $2.1M on the project.
Posted by reeves | November 9, 2010 7:48 AM
"Overall, the City did not meet its goals"
BFD - I'd like to see an action plan or some heads on a stick. Isn't this the 26th computer system CoP has screwed up?
"The outside firm hired by the City to provide quality assurance
services repeatedly warned the City about concerns around project
governance and management."
Maybe if Samdy's proteges would stop spending time making PowerPoints telling the world how smart they are, they might have time to focus on stuff like this.
Lesson learned - NEVER ever vote for any CoP bond, it'll just get all p!ssed away.
Posted by Steve | November 9, 2010 7:53 AM
"City bureaus using the new software will pay for these additional costs through increased fees."
Translation - City bureaus means us.
Posted by Steve | November 9, 2010 7:55 AM
Pretty good reason why the city can no longer maintain eroding streets or pick up leaves.
I just looked at my property tax and pondered my own involunatry financial support for all these fiascos.
Posted by Peucellier | November 9, 2010 7:57 AM
Renminds me of the design and production of the perfect car: "The Homer"
Posted by dhughes609 | November 9, 2010 8:10 AM
I wonder what kind of sales job the City got from vendors? If you recall the water bureaus' computer fiasco, as well as the many similar stories from cities across the country, I am sure that government is precieved to be 'easy marks'.
If IT costs were 300% over budget in the private sector, heads would roll. If rollout was so far off the mark, somebody would be called to account.
At the same time, I do have to give props to the Auditor. I have been watching her since she took office and she is not one in the limelight, but she always speaks truth to power. Shes a keeper, the 'other' member of a pretty forgettable city council.
Posted by Grumpy ol' Joe | November 9, 2010 8:22 AM
Grumpy,
I don't think it's call a "sales job" that Sam got from the vendors, but the second word in the quoted IS correct.
Posted by phil | November 9, 2010 8:29 AM
I think Dave Lister wrote about this awhile back in The O. He pointed out that it's not the software itself that's the problem necessarily, it's the bungled business processes the software is supposed to support. Garbage in, garbage out, as the programmers used to say. And I'll go further and say that it's our bungled up, multi-bureau, commission form of government that creates the bungled processes that creates the bungled software implementations. If all the bureaus could agree to a common set of standards for payroll, billing, timeclock, ERP, CRM and other back-office processes, the software could almost write itself.
Others have pointed out there are some huge drawbacks to the strong-mayor model -- namely, we shudder at the thought of Sam or Randy with unlimited power -- but if we are going to continue our decentralized, devolved system of competing commissioners with their feuding fiefdoms in the bureaus, we have to be willing to accept this waste of taxpayer money on inefficiencies and redundancies as all but a fact of life.
Posted by Eric | November 9, 2010 9:32 AM
I googled SAP and found this:
http://www.bloomberg.com/news/2010-11-09/lazard-s-fishbein-says-oracle-is-must-own-stock-video.html
Posted by Starbuck | November 9, 2010 9:35 AM
The Riches of a City are the taxpaying citizens.
SAP software is notoriously rigid and they are very transparent about the need to adapt your business practices to the software, rather than trying to customize it.
I'm shocked and dismayed they will pass these cost overruns on to Portlanders who had no say in the matter. Ditto for the Sellwood Bridge registration fees, the leaf pickup fees, the doubling of parking meter rates and parking/traffic fines, and a 50% increase in water/sewer rates.
Portland's voters can't say they haven't been punished over and over again for returning the same incumbents to office term after term.
Posted by Mister Tee | November 9, 2010 9:39 AM
After watching the Wate Bureau software debacle this comes as no surprise. They just circle the wagons and support each other's decisions, with a promotion or two thrown in. What idiots we are to put up with this.
Posted by kimberly | November 9, 2010 9:46 AM
SAP software is notoriously rigid and they are very transparent about the need to adapt your business practices to the software, rather than trying to customize it.
I don't doubt that's true, although Oracle has other shackles (namely on pricing) it forces its customers into as well. While customization is of course inevitable (and maybe SAP was the wrong choice for this for that reason, as you point out), the city still needs to standardize and integrate its processes. I mean, 200 different systems or applications are in use across all the offices and bureaus??!!
Posted by Eric | November 9, 2010 10:02 AM
If that is true of SAP, Mr. Tee, then why are we in this mess? There is nothing left about a rigid system that doesn't do the job, except to quit or to start over, which apparently they did and we are paying the engineering costs.
Great opportunity for SAP, wouldn't you say?
Posted by Starbuck | November 9, 2010 10:07 AM
The story is about another matter, however, when I read this sentence in the article below, I thought of our city -
. . And we have a culture of accountability that’s in tatters. .
http://news.firedoglake.com/2010/11/08/the-american-nightmare-debt-collector-thieves-create-fake-courtrooms-to-steal-from-consumers/
And it does signal the end of the American dream. I don’t agree with everything in the Der Spiegel piece, but the overarching theme is correct – Americans were taught that they could have it better than their parents, through hard work and initiative. And that’s not necessarily true anymore. We have an economic system tilted to the benefit of a several-block radius in Lower Manhattan known as Wall Street. We have a political system bought and paid for by those corporate interests. We have a legal system where power and influence can buy justice. And we have a culture of accountability that’s in tatters. So out of all of that, you get scam artists making fake courtrooms and stealing from people, basically assuming the robes of justice themselves in the absence of any competition.
It’s inequality, not just income inequality but inequality of opportunity, upward mobility and justice that drives this. In these times, it couldn’t be more important for community groups to band together, work with their neighbors and build a collective voice. It’s almost the only hope left.
Posted by clinamen | November 9, 2010 10:55 AM
$14 million becomes $47 million?! Three letters come to mind: W. T. F.
Posted by Jim | November 9, 2010 10:56 AM
Eric,
Yes, I did write about it in May of 2008 when the problems first began to emerge. The other thing I've written, both on the SAP system and the Water Billing is that the city's own RFP (request for proposal) processes help ensure failure. You can probably find my piece on the water billing by googling "Dripping Dollars". It was in Brainstorm NW magazine back in July 2003.
Dave
Posted by Dave Lister | November 9, 2010 11:04 AM
If you look into a thing like this, what you're likely to find is that most of the problems come from customization. And most of the pressure for customization comes from — wait for it — the customer. People in the city's administration start with the view that their idiosyncratic ways are necessary, or better, or both, than the ways provided in the standard package. As far as I am concerned, they should be able to run the city on Excel. Or maybe Quicken.
Posted by Allan L. | November 9, 2010 11:41 AM
Allan L., so you think that "pressure for customization comes from-...the customer.???
Think of how many customers call or come down to all the bureaus and ask for more customizing of the computer programs-most of us don't even know how to even ask, don't care, or that we can for more diversity in all the 300 city programs. The lady trying to pay her water bill isn't interested in how many gallons she used 10 years ago-only the bureaucrats do.
It's like when I went down to BDS last week to review possible sewer hook up on an undeveloped city lot. The staff person brought up a sewer street plan that showed the information, but then he said that he could use another program that would highlight in color the sewer lines. How many programs can the commoner afford? He can't.
Posted by lw | November 9, 2010 12:15 PM
Is this the game plan - they dripping dollars while we have to penny pinch?
Posted by clinamen | November 9, 2010 12:49 PM
Might add, not only does the faucet have to be tightened, but the line has to be shut off.
Similar to what the water bureau does to customers who aren't able to pay.
Posted by clinamen | November 9, 2010 12:58 PM
It appears that the City adopted a number of guiding principles at the outset of the SAP implementation that may have helped it to stay closer to schedule and to control costs, then proceeded to violate most of those principles. The City may have tried to do too much in one step, but it seemed to lack an effective overall plan and the ability to make timely decisions to modify the plan when things went south. When Bureaus were faced with the need to change their diverse, outdated business practices to conform to a common set of accepted business practices embodied in SAP, many Bureaus resisted the change, and the City often caved in to those Bureaus. This led to many customizations and interfaces and greatly increased project costs. Responsibility for poor planning and decision making lies with City leaders and management, not the consultants.
SAP may not have been the right system for the City but it has invested more than $47 million in SAP, so it will be around for quite a while. The City that mis-managed the implementation will continue to struggle with SAP unless it finds the ability to standardize the way it does business, requires Bureaus to use SAP rather than their home grown systems and finds more employees with the ability to operate and maintain SAP. Look for ever increasing costs for consultants and contractors to operate and maintain the system. These costs will consume more of your taxes and be relected in increased utility rates and more user fees like the leaf pickup fee.
Posted by Mick Farr | November 9, 2010 1:04 PM
lw -- I'm pretty sure that when Allan was talking about customer demands, he was referring to the city's role as the customer purchasing the software.
I'm inclined to agree with his other point; couldn't something like 85 percent of the city's business be taken care of via Word, Excel, Access Outlook and their equivalents?
Posted by Roger | November 9, 2010 2:29 PM
Roger, you're probably right in interpreting Allan. But I was making the point that the customer is not CoP but us.
Do we need three or four programs to display a map? Is that what the true customer, us, needs? For example, does a retail paint store have numerous, duplicating programs to handle the customer buying a can of paint? If they do, paid the price for the numerous programs, then they'll eventually be out of business. Same for this city.
Posted by lw | November 9, 2010 3:43 PM
Can't believe nobody (quite) said "Opie lives." Will real people, and real little people, pay for these terrible mistakes as they did with the Water Department fiasco?
Posted by Sally | November 9, 2010 7:37 PM
People were actually fired over the Water Dept fiasco. But I won't hold my breath waiting for firings over this current debacle.
Posted by Frank | November 9, 2010 7:52 PM
Why do we all seem to sit back and stress over these problems and yet no one does anything? Can't we come together and make changes?
Posted by Eternal Hope | November 10, 2010 6:03 AM
$14 million becomes $47 million?! Three letters come to mind: W. T. F.
Yet another tripled cost overrun... it mostly prompted four-letter words to my mind. The only printable one was 'tram'.
Posted by PanchoPDX | November 10, 2010 7:28 AM