Slashdot Mirror


NYC Mayor Demands $600M Refund On Software Project

alphadogg writes "New York Mayor Michael Bloomberg is demanding that systems integrator Science Applications International Corporation reimburse more than $600 million it was paid in connection with the troubled CityTime software project, a long-running effort to overhaul the city's payroll system. 'The City relied on the integrity of SAIC as one of the nation's leading technology application companies to execute the CityTime project within a reasonable amount of time and within budget given the system's size and complexity,' Bloomberg wrote in a letter Wednesday to SAIC CEO Walter Havenstein. CityTime was launched in 2003 at a budget of $63 million, but costs swelled dramatically as the project stumbled along for nearly a decade."

27 of 215 comments (clear)

  1. In Other News: by fuzzyfuzzyfungus · · Score: 4, Funny

    The Honorable Mayor Bloomberg is shocked, shocked, to discover fraud and waste going on here...

  2. SAIC ever have any successful projects? by MagikSlinger · · Score: 4, Informative

    Last time I heard of them, it was with the failed FBI casebook system. Does SAIC have a generally good delivery rate on projects otherwise?

    --
    The bitter lessons of a veteran coder: http://bitterprogrammer.blogspot.com
    1. Re:SAIC ever have any successful projects? by memyselfandeye · · Score: 3, Funny

      Nope. But they did stay at a Holiday Inn Express last night...

      to make sure that thousand dollar escort treated the Senator just right.

    2. Re:SAIC ever have any successful projects? by Anonymous Coward · · Score: 5, Informative

      Posting Anon, because people of interest may find this page.

      I have worked with 4 SAIC employees/contractors. I found them to be mediocre. However, that's okay, because we needed a mediocre job done, and were going to pay them mediocre money to do it. They performed the job, and testing revealed about the normal amount of bugs (1 per week or so). My experience with them has been they they were astoundingly average, technically.

      However, they were significantly above average in the other parts of the job. They made their software available for regular testing, were timely in delivery of monthly reports, showed initiative in going for above-and-beyond requirements (for extra money), were willing to work with us on emerging requirements, and put together a better-than-average cost estimate. The experience was pleasant overall, and the contract was 5% overbudget, and 10% behind schedule. Being a month late on a one-year project with emerging requirements is acceptable, and mostly our fault.

      I would work with them again, but, in general, I wouldn't trust them to build any system from the ground up, as this requires real skill. Modification or maintenance is about where they belong.

    3. Re:SAIC ever have any successful projects? by MrEricSir · · Score: 3, Funny

      This year's America's Cup is sponsored by another company that makes shoddy, overpriced software -- Oracle.

      I guess there's a connection between shady businesses and rich assholes who race yachts. Who ever would have guessed?

      --
      There's no -1 for "I don't get it."
    4. Re:SAIC ever have any successful projects? by rpillala · · Score: 3, Informative

      I'll wager that they were above average in their rate of having security clearances too. That's one major feature of the "Reinventing Government" era contracting companies. They supply security cleared personnel for whatever work you need.

      --
      When the axe came to the forest, the trees said, "Look out - the handle was once one of us."
    5. Re:SAIC ever have any successful projects? by Anonymous Coward · · Score: 3, Interesting

      I've worked there for close to 8 years now (hence posting anonymous). The projects in our division are delivered within days of their deadline and under budget. The clients we have in the military constantly come back to us for work.

      Saying SAIC's performance is "such and such" is kind of funny. When I first joined the company it was privately held by the employees until the founder stepped down and the board rushed to bring the company public. Before it went public, the company was like hundreds of little fiefdoms, each competing for projects sometimes even competing against themselves. It was not unusual for a project to have two bids from SAIC because two different parts of the company were bidding on it. After the public offering there were probably four or five reorganizations so that instead of hundreds of fiefdoms it's more like dozens. So are their divisions within the company that screw up? sure. It's hard to categorize the entire company because the divisions act independently of one another even if there are fewer of them now.

      This particular project was run by a crook. He was clearly not managed by higher level management properly because the cost overruns alone should have raised a ton of red flags within his division. I imagine that since the project started before the reorgs his group got shuffled between divisions every 9 months or so (like almost every other group), and the people he reported to never had a clue what was going on. It reflects badly on the current CEO, but the blame lies with the last CEO (we've had two since going public) who shook the company up far more than he probably should have.

  3. Time and Attendance by DarkOx · · Score: 3, Insightful

    Nothing seems so simple as Time and Attendance software until you to write/consult on/implement Time and Attendance software.

    --
    Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    1. Re:Time and Attendance by AdmiralXyz · · Score: 4, Interesting

      Nothing seems so simple as Time and Attendance software until you to write/consult on/implement Time and Attendance software.

      Would you mind going into more detail as to why? I have to admit, this is one of those things I've always been curious about. It always seemed to me that this should be one of those things that any decent team can crank out in a year, yet I've heard disaster story after disaster story about software like this and so clearly there's something I'm missing here. Is the actual software more difficult to design than I thought, or is it the fact that these are usually government projects, with all the additional requirements therein?

      --
      Dislike the Electoral College? Lobby your state to join the National Popular Vote Interstate Compact.
    2. Re:Time and Attendance by lpp · · Score: 4, Informative

      My little company does IT work for small local business, often playing liaison between them and their other vendors. Once I worked with a third party timekeeping software company to help onboard my client onto the system. I was like you, thinking "enter the hours on the day, done". I got to talking with one of the developers and, recognizing there must be some hidden complexity, politely broached the subject. He agreed that yes, it seems simple on the surface, and for a handful of cases it can be. But apparently where things can get bogged down is with adherence to local, state and federal regulations regarding various levels and types of compensation (overtime, sick time, holidays and the like) . He mentioned other issues too but that seemed to be the major bugbear.

    3. Re:Time and Attendance by trout007 · · Score: 3, Insightful

      I don't have experience with this type of software but I am familiar with how governments work.
      I've designed equipment to automate tasks that were done by government workers. If the software or equipment in any way threatens those jobs they stop you since their contracts give them that right. I've had to dumb down many systems because they were too efficient and required less people. One was designed to position a payload in a rocket. It used to take 20 something people with rulers hanging at the end of a platform calling out the distances. We replaced it with a system that used sensors to relay all of the information back to the control booth and had camera feeds from each location. It provided 10 times the accuracy as before. We couldn't get it approved since it eliminate so many man hours. Wht did we do to get it approved? We installed 20 emergency stop pendants so those people could still be required. By that time the project ran out of money and was canceled. And they kept doing it the old way.

      --
      I love Jesus, except for his foreign policy.
    4. Re:Time and Attendance by Kjella · · Score: 4, Interesting

      Usually, if you want just attendance like time in, time out that's not problem. If you start with tracking what they're working on, resource planning or internal/external billing, you're looking for a world of hurt.

      To take one example I got, one company I worked with insisted that sick leave was strictly a matter between the resource manager and that employee, and not for general display. Yet at the same time, they wanted lots of hours worked figures that'd essentially drill down to find the "missing" hours. Project managers were supposed to see what other projects the team was also working on, except if that was sick leave. To "fuzz" the data this had to be mixed with other administrative time so that others couldn't get good statistics on whether they were sick, study day, administrative meetings or whatever. But their immediate manager should of course get to drill down on those. After a lot of back and forth they decided data on an individual basis wasn't needed except in the real T&A system for salary, because we focused on overall project progress and resource planning. Then of course that became silly as project managers realized they had x hours tracked from a department, but not for each person from that department so they didn't know who over/underspent.

      Another good example I have is from financials - wouldn't it be nice if you could staff up a project and have that immediately converted to a budget, then just whatever hardware/software/other costs? Also great for checking billing, one hour worked means we'll expect a bill from the consultant on that amount. Except uh-oh, now everyone who can book a consultant one hour and create a budget can see their rates. Things hard negotiated and best kept secret. The solutions to this were many and varied, but they were all hacks to make fudge numbers one place then real numbers other places and don't mix them up to create a complete mess. Oh yes and secret projects were always interesting, they were supposed to show up in total budgets but not be visible other places, I mean just titles like "Buyout of [foo]" was stock sensitive and complete no-no to see. But people still worked on it and needed to track time somewhere and some people sometimes needed to know what project it really was. The whole logic made you want to strangle someone.

      --
      Live today, because you never know what tomorrow brings
    5. Re:Time and Attendance by gstrickler · · Score: 3, Informative

      There are a number of factors that bloat and/or doom these projects:

      1. No one person or group of people actually know all the specifications.
      2. Tracking time for vacations, PTO, sick time, personal time, leave of absence, overtime, etc. varies by jurisdiction, and changes over time.
      3. Other specifications may change during development due to legal or corporate policy changes. IRS rulings, FAS rulings, state and federal legislative changes, etc. can all effect the project.
      4. Contracts (especially gov't) aren't usually written to allow for significant changes or variation. Changes require a change request, a change cost estimate, and a change order. Work on the change can't begin until all of that is complete, meanwhile the project either continues without the change, or goes on hold.
      5. They don't hire a really good software architect to design a flexible system, they just design it to the incomplete (and often inaccurate) specs in the RFP/Contract.
      6. The amount of auditing, reporting, and security controls are almost always underestimated.

      So, it's far more complex that it first appears.

      Having said that, $600M is an insane amount. And the 2GB footprint another poster cited is also absurd. A good software architect could have prevented or minimized both of those.

      --
      make imaginary.friends COUNT=100 VISIBLE=false
    6. Re:Time and Attendance by luis_a_espinal · · Score: 4, Insightful

      If you approach the problem with a proper design methodology that generates a thorough set of use-cases before writing the first requirement, the solution falls out of the regs and obvious behaviors.

      And, if you build into that an ability to adapt the system to changing regulations, you've handled the most obvious case, in which regulations change, which they do, continually.

      To "a thorough set of use-cases before writing the first requirement", that's the most naive, most impractical stupidest thing I've heard, a blurp out of academic void. This is the number one mistake people in software engineering do, believing that this is possible. In fact, good software engineering recognizes this, and what you just suggested is anathema to it.

      Except with the most trivial of cases or in systems that strictly autonomous that interface with physical environments for which you have a model, requirements exist a-priori... ALWAYS.

      We are talking about systems that interface with people, business, and processes (internal and external) governed by law, contractual agreements, human behavior and market forces that can change at any time and for which no model exist (unlike models of physical phenomena.). These can change (and due change) by priorities greater than the ones driving the development of a system.

      And this does not count deadlines to deliver that typically exist to get something going and that are non-negotiable. Yeah, non-negotiable. You can get a legislative deadline to implement something just to be allowed to operate (think HIPAA or SOX), or mandated by business imperatives that can make or break a company.

      And we, software engineers, have to cope with that change because that's what we get paid the big bucks for . With that in mind, it is obvious that it is impossible to do what you suggest: to get a through set of use-cases before writing the first requirement. In fact, many of the requirements and use-cases only become known as progress is made. This is true for any complex system.

      Moreover, it flies in the face of agile development, rapid prototyping, or the older-but-always-good iterative/spiral models.

      You pretty much suggested that we do waterfall. Way to go bro.

  4. Re:Yeah by drunkle+j · · Score: 5, Insightful

    It's about time someone is calling out a company on their massive budget overrun. The SOP of underbidding contracts just to get them, knowing full well that you can just ignore the budget is nothing more than systemic fraud.

    Why they decided to pay $600M and then ask for a refund is a bit perplexing.

  5. Sorry, didn't you read the EULA? by elrous0 · · Score: 3, Funny

    The EULA specifically says that you can't ever, never sue us--for any reason. It also says that this software is not in any way obligated to ever function.

    Hey, you clicked through it.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
  6. Re:Yeah by PickyH3D · · Score: 4, Insightful

    You do not sound like an incompetent bureaucrat that wants to turn around and blame the contractor if anything goes wrong, all-the-while both changing and adding requirements throughout the project.

    With that said, I would hope that SAIC could have bought a company that already makes time management software on the desired scale for a fraction of the current cost. Maybe even for a portion of the original $63 million estimate.

    I am not sure what is so special about a city that they need their own unique time management system. It's not like there aren't a bajillion in existence already ranging from overly simple to extremely complex. While I'm sure they need the extremely complex region, it really should have been handed to a company with experience in the arena already to either purchase an existing product, or add required features to one.

    There I go thinking about someone outside of the government. I'll move along now.

  7. Re:Yeah by Kjella · · Score: 3, Insightful

    Probably a combination of several things. First of all it's probably been a disconnect between the tactical operation of the project (let's approve of budget increase to get enhancements x and y, consulting help to solve problem z and so on) and the strategical operation (should this project be red-flagged and halted/abandoned). You'd be surprised how many organizations really lack that emergency brake and when the train wreck finally happens everybody wonders why it wasn't stopped before.

    The second part is that for the most part projects aren't a scandal until they're officially scrapped. That means that in very political organizations you're looking to finish it somehow to back out gracefully. This leads to a high willingness to throw good money after bad, particularly if some of the key decision makers now hold high places in the organization. The only exception to this is when the new boss wants to deliberately throw the old boss' projects under the bus.

    And finally since this is turning into criminal investigations and all, they probably sailed under false flag. You can string a client along pretty far if you have absolutely no ethics and make business cases that are utterly false yet plausible. They were probably given a lot of good lies about the system being right around the corner to working and a lot of good excuses for why it'd take just a little more money. At least if the City's project manager was a wimp - and he was either that or corrupt too.

    --
    Live today, because you never know what tomorrow brings
  8. wrong from the start by roman_mir · · Score: 3, Insightful

    CityTime was launched in 2003 at a budget of $63 million, but costs swelled dramatically as the project stumbled along for nearly a decade.

    - this is the problem with government programs: from the very beginning they are already deep in trouble. It makes no sense that a computer payroll system should start at 63 million, why did it start at that number from the beginning?

    It makes no sense that government should be so large, as to require a computer payroll system that starts as a 63 million project, never mind that anybody getting that contract will make their best to prolong it as much as possible, simply because it IS government and it does not care about costs.

    When somebody says that government can do things efficiently, and they use the postal office as an example, they should really go back to that premise and realize, that the US post office is out of cash - it's selling 'forever stamps' today, and assuming it doesn't just dissolve over the next few years, it won't be able to make any money at that time and it will be in a worse fiscal shape than it is today, because the stamps sold today are basically protection against the 10% (current level) of monetary inflation that US Fed and Treasury are incurring on US population. Today the postal office cannot function already and they sell the forever stamps, tomorrow, they'll have to raise the prices but people will use those forever stamps and the postal office will either have to default on that stamp or dissolve, or there will be another bail out, and people use that as one of 'better' examples of government 'efficiency'.

    Another example they give is Medicare, while not realizing that Medicare costs are spread out among various parts of government that are not calculated into the costs directly, and just like SS, that program is bankrupt today, being the biggest pyramid scams of all times, making Madoff look like a preschooler.

    Anyway, back to this topic - who was the NYC mayor at the time when this ridiculous project started I wonder? Oh wait, Bloomberg has been the mayor of NYC since 2002 and this project started in 2003. So where was he all the time when the costs overran by x2, by x3, by x5, is the magic number for a politician to look at some cost overruns only when they exceed the x10 estimate?

    People blame corporations and businesses for waste and fraud, but at least corporations and businesses have to extract their money from customers (well, unless they are government protected monopolies of-course) by selling products that customers want.

    When business overruns its costs and credits like that, it likely goes under. Shouldn't the same apply to governments? I think it should. And those, who are allowing the money of tax payers to be wasted like that do need to spend some time thinking about in jail. Same should be done on all levels - federal and state and municipal, maybe then the governments will stop bailing out failing businesses and causing massive economic collapses.

    1. Re:wrong from the start by mcmonkey · · Score: 4, Interesting

      Anyway, back to this topic - who was the NYC mayor at the time when this ridiculous project started I wonder? Oh wait, Bloomberg has been the mayor of NYC since 2002 and this project started in 2003. So where was he all the time when the costs overran by x2, by x3, by x5, is the magic number for a politician to look at some cost overruns only when they exceed the x10 estimate?

      People blame corporations and businesses for waste and fraud, but at least corporations and businesses have to extract their money from customers (well, unless they are government protected monopolies of-course) by selling products that customers want.

      BTW, from TFA but not included in the summarys:

      The recent indictment of SAIC's leader project manager on the CityTime job, Gerard Denault, as well as the guilty plea to criminal charges made by SAIC systems engineer Carl Bell, who designed the software, are "extremely troubling and raise questions about SAIC's corporate responsibility and internal controls to prevent and combat fraud," he added. Denault and Bell were charged with were charged with taking kickbacks, wire fraud and money laundering.

      Also recently indicted were Reddy and Padma Allen, a couple who head up New Jersey systems integrator TechnoDyne, which was SAIC's primary subcontractor on the CityTime project. Federal authorities allege that the Allens and others conducted an elaborate overbilling and kickback scheme that siphoned millions of dollars from the project.

      Federal authorities have also contended that SAIC had received a whistleblower complaint about the project as far back as 2005, Bloomberg said in the letter. "It is unclear what SAIC did at that time to investigate these serious allegations."

      And Bloomberg is a billionaire. He's not some ivory tower academic or career politician. He's supposed to know better.

      I worked for a small company that was bought by a slightly less small company which was then gobbled up by SAIC. Anyone who didn't have their life savings wrapped up in the venture from starting the original small company got the heck out of there.

  9. Hundreds of millions for payroll software? by Sloppy · · Score: 5, Informative

    Yes, I have actually worked in this field. And yes, payroll is more complicated than it seems on the surface. But it's not that complicated. It's not "I can build a dozen F-14s for less" complicated.

    The money spent on these types of applications is just obscene. There's gotta be major corruption in the procurement process. And it's everywhere; this isn't just a NYC problem.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  10. Re:Yeah by mr1911 · · Score: 3, Insightful

    This is what happens when you privatize an important function of government.

    Nothing was privatized. The government hired a private contractor to do the job. This is how the vast majority of government projects are completed.

    I wonder how much of the federal budget deficit has ended up in the pockets of private contractors who overran costs and then didn't perform up to expectations.

    It depends on how you define overruns. Many government contracts are for projects that are large and complex to the point they cannot be completely defined before the work starts. If the government issues a contract with clauses to cover cost escalations, agrees to the cost escalations, and pays for the escalations, is it not the vendor's fault.

    Bloomberg should be suing his contracting managers. I'm quite sure SAIC did not bill a dime until they had a contract to bill against.

    --
    This post comes with a double-your-money-back guarantee!
    Any offense taken to this post is at your sole discretion.
  11. Re:Well done public sector by RichardJenkins · · Score: 3, Insightful

    Well I'm sure that public projects have boards of individually talented people running them and vested to a degree in their success, and let's not forget that the greatest things we've ever done (sanitation, electricity, the welfare state, insert your own list here, civil engineering mega projects) have been public works.

    I dunno, maybe this project is being run by people better suited to another career, it's certainly too complex to sum up in a sentence or two! The point I failed to make was that public projects seem to sit in special sort of bubble immune to anyone really kicking up a stink about them going wrong. The public peeks in from time to time as if gawking at a train crash where no one they know got hurt, gasps and shakes their head, then promptly forgets about it whilst the whole endeavour churns merrily along sucking up resource and offering no value. I was lamenting how easy it is to write something off as somebody else's problem more than anything.

    I, for one, am very happy to spend 10 minutes writing about this on Slashdot - instead of actually trying to participate.

  12. Re:Yeah by icebike · · Score: 3, Insightful

    You don't have to postulate corruption to see this kind of thing at this scale.

    All you have to do is give every little section chief in every backwater bureau of city government an opportunity to make their own little demands for special treatment. Get the unions involved and all bets are off.

    Rolling Requirements are the usual cause of such expansions, not corruption.

    --
    Sig Battery depleted. Reverting to safe mode.
  13. Re:Yeah by HungryHobo · · Score: 4, Insightful

    A piece of advice I was once given by an old coder:

    "If you ever do contract work for government make a special effort to cover your arse because you'll be blamed when something goes wrong no matter what.

    Especially if it's their fault. "

  14. Re:Yeah by PopeRatzo · · Score: 4, Insightful

    This argument only holds weight if we assume that government employees are qualified and capable of managing a project of this size and scope for less money than the private contractors' bid.

    Compare the cost of US military troops in Iraq vs contractor personnel in Iraq.

    If we can handle a moon landing, the invasion of Normandy, the Tennessee Valley Authority and Hoover Dam, and the Manhattan Project, I'm pretty sure we can handle putting together a payroll system.

    Here in Chicago, we had a public parking system that was hugely profitable, convenient and cheap. It was sold to a private company over a year ago to cover a budget shortfall arising out of the real estate crash and now parking fees have gone up 1600%, you are limited to 2 hours (in order to increase violations) and the privately hired enforcement workers are rude, ignorant and obnoxious. Sundays and holidays are no longer free. The situation is so bad that businesses along major streets are suffering because people don't want to deal with it. The public operation was far superior to the private one.

    Oh, and the private outfit that manages parking says they cannot make a profit even with the 1600% increase, so they're going to be raising parking prices yet again. The prices are so high that they had to take out the parking meters and put in these big machines that take credit cards (but not dollar bills). Oh, and the machines are always broken (which does not prevent you from being fined for not paying).

    Governments can certainly handle large, complex projects and do it more efficiently than the private sector. When you take out the 20-100% (minimum) profit margins that privateers add, it's not even close.

    Say, how well are those private space exploration companies doing? I'm sure by now they must have mines set up on Mars.

    Profit is not all it's cracked up to be.

    --
    You are welcome on my lawn.
  15. Re:Yeah by AK+Marc · · Score: 3, Informative

    The reason it's SOP to underbid the contract is that it's the only way to actually win the contract. Government entities award the contract based on the bid. They don't care that there's no way in hell their sprawling (and ever changing) requirements will drive the cost well past the original bid by several orders of magnitude.

    That's still criminal fraud on the part of SAIC. If you know you can't do it for the number quoted, to sign a contract saying you can is fraud. To use improper change control procedures in order to take advantage of a client to make an end run around the contract is fraud. There's almost nothing I can think of that would have SAIC not guilty of fraud.

    Not that this excuses any actions by the government. They were incompetent at best, and felonious co-conspirators at the worst. But no likely actions by the city excuse SAIC spending so much more than the contract.