Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Software Government The Almighty Buck Technology

NYC Mayor Demands $600M Refund On Software Project 215

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."
This discussion has been archived. No new comments can be posted.

NYC Mayor Demands $600M Refund On Software Project

Comments Filter:
  • by AdmiralXyz ( 1378985 ) on Thursday June 30, 2011 @05:03PM (#36627664)

    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?

  • by blair1q ( 305137 ) on Thursday June 30, 2011 @05:25PM (#36627942) Journal

    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.

  • by Kjella ( 173770 ) on Thursday June 30, 2011 @05:52PM (#36628272) Homepage

    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.

  • by mcmonkey ( 96054 ) on Thursday June 30, 2011 @05:53PM (#36628280) Homepage

    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.

  • by Anonymous Coward on Thursday June 30, 2011 @08:26PM (#36629540)

    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.

Genetics explains why you look like your father, and if you don't, why you should.

Working...