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."

Comments

SAIC ever have any successful projects?

[MagikSlinger]

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?

Re:SAIC ever have any successful projects?

[Anonymous Coward]

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.

Re:Time and Attendance

[lpp]

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.

Hundreds of millions for payroll software?

[Sloppy]

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.