3 ms·
It 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 j
by ddingus 12y ago
It 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.