Oracle Deflects Blame For Troubled Oregon Health Care Site
itwbennett (1594911) writes "Oracle is gearing up for a fight with officials in Oregon over its role developing an expensive health insurance exchange website that still isn't fully operational. In a letter obtained by the Oregonian newspaper this week, Oracle co-president Safra Catz said that Oregon officials have provided the public with a 'false narrative' concerning who is to blame for Cover Oregon's woes. In the letter, Catz pointed out that Oregon's decision to act as their own systems integrator on the project, using Oracle consultants on a time-and-materials basis, was 'criticized frequently by many'. And as far as Oracle is concerned, 'Cover Oregon lacked the skills, knowledge or ability to be successful as the systems integrator on an undertaking of this scope and complexity,' she added."
Never bring politics... to an electronic documentation of timeline fight with a database company.
We were forced to sign this contract. On gun point actually. And then they said that we should take their money or they'll break our knee caps.
You see, we are the victims here.
Larry
"...'Cover Oregon lacked the skills, knowledge or ability to be successful as the systems integrator on an undertaking of this scope and complexity,'
Gee, that's funny. And here I thought I was in the majority in thinking that it is in fact Oracle who lacks the skills, knowledge, or ability to fix that piece-of-shit Frankenstein they want to label a working product.
I suppose if you thought you were buying a perpetual bug and patch service, sure. They're fucking awesome at that. I might even be so bold as to say #1 in the industry.
Oregon's health website is a monstrosity. They budgeted way too much money, were way over ambitious, and involved way too many people. The opposite end of the spectrum is Kentucky, which budgeted the least amount of money, and was thus forced to implement a streamlined site with a small lean team. Kentucky's website was ready on Oct 1st, and has run since without a hitch.
Actually, no. KyNect worked without downtime on its frontend, however its backend was not very stable - as it had to interact with the federal exchange.
What you are really saying is that Oracle knew Oregon's exchange would be a POS before they even signed the consulting contract because of the lack of Oregon bureaucrat skills, but they took the contract anyway because they knew they could as they say MILK IT!
Since they knew full well it would fail, they would document everything to the hilt, including specific warnings, while padding up the consulting, knowing full well that they would never finish the job, but would get paid a pile of money anyway to add to Larry's billions.