3 ms·
Yeah, that's due to a strong bias away from anything else. Lots of lobby dollars in play reinforcing that, and there is the strong perception that Oregon can't
by ddingus 12y ago
Yeah, that's due to a strong bias away from anything else. Lots of lobby dollars in play reinforcing that, and there is the strong perception that Oregon can't actually afford to make any kind of investment.
But this shows Oregon can, did, and it was botched horribly. Doing the same while providing local jobs, some great skills to be used all over the place, and build something that has a very likely lower overall ownership cost profile makes a ton of sense!
It just won't get proposed in the current political climate, which was the point of my reply.
Of course Oregon wants COTS. Everybody does, because they think the vendor will own it, saving them money through economies of scale. Quite frequently, COTS can do that, but for something like this, something new, that needs to communicate with a lot of varied systems?
No way in hell it was ever gonna be COTS, and that right there should have triggered a much different, "how does Oregon do this?" kind of discussion.
Oracle has a good sales team, and they sold it right to this dynamic, which is what they were supposed to do. Problem is the value really wasn't there. No matter what, it was going to take some real work to build out the exchange and have it function well.
As for the support contracts, those come with an annual cost. It's very highly likely that cost could simply provide a job for the people who built the thing. Additionally, having seen success on a project like that, the same team would be well positioned to build out more and or get funded by other municipalities seeking similar solutions.
I don't have the basic numbers a few of us ran back then, but they were compelling.
This works the same for States as it does companies or anyone else. Make the in-house investments and own the tools. From there, buying help is always an option. Avoiding it is another option. Relying on a vendor, who will very frequently oversell their support staff, counting on their product to be a winner, often results in that support contract merely funding the trouble shooting. More dollars are required to buy, implement, test, etc... fixes.
Fixes, which by the way, will be called custom patches for major customers due to the size and non COTS nature.
- ddingus 12y agoIt could go badly either way. However, I find it very hard to believe a competent group would actually fail in this spectacular of a way. Vendors often know just a little more than the client does, and they do oversell, and "cost effective" gets calculated to a point where the purchase price and services costs are much closer to building something than not. And some of my career is in selling just that kind of enterprise solution, and that's exactly how it goes a lot of the time. There is value there for sure, and the vendor will need to capture as much of it as it can in revenue, while delivering as little service as possible to keep margin. Those expensive people, who likely would have built the system, wouldn't be doing nothing. Not at all. Once that system is up and successful, they continue to build lots of things OSS style. Boring, simple, cost effective things and anybody anywhere can pick them up and use them too. Lots of synergies here for States and municipalities looking to create jobs and manage costs. Having been on the ugly end of these things, it's worth a look. Perhaps it wasn't the right call for this project, but it really wasn't evaluated. And there are few entities able to answer an RFP to make that evaluation, who don't also sell very expensive software licenses. Should have been evaluated, and Oregon should have some basic competency in State IT to do that. The savings potential is significant, and Oregon needs to own it's IT anyway. For a lot of things, vendor supplied software will win out. No question. But for those things where it won't, or cost of ownership over long periods of time do not make sense for the public, having a means to explore that was what the legislation was all about. Keeps vendors a bit more honest too.