Eskom without Oracle technical support

so now who is going to pay?

I mean Eskom is technically insolvent,
just like SAA and other SOE's,

or did the government guarantee the debt will be paid and left it at that.
There is a thing called "tax payers" who pays for everything and this is an endless bottomless pit of money at their disposal. The only reason that Oracle is not being paid is because some cadres need to stuff their nest eggs with that money and maybe throw some money at SAA, but also with the intent to gather the money in cadre nest eggs.
 
There is a thing called "tax payers" who pays for everything and this is an endless bottomless pit of money at their disposal. The only reason that Oracle is not being paid is because some cadres need to stuff their nest eggs with that money and maybe throw some money at SAA, but also with the intent to gather the money in cadre nest eggs.
so the new CEO hasn't shone a light into the deep dark hole of Eskoms Procurement department yet?
or one needs a auditors to determine exactly how deep the rabbit hole goes.
 
Did you not read or did you ignore what was posted in the last thread where you suggested this?

Banging your drum about a product that does not nearly cover all of the use-cases that Eskom requires, that likely needs further development for specific customization and that will need to ultimately be supported (either in-house or via contractors) is not an immediately viable solution as much as you'd like to make it.
I've never seen an Oracle product that could be dropped in and used - it usually required many millions of Rands customisation and implementation. No ERP product gets dropped in and used, and they tend to keep sucking money too over the years. Odoo was mentioned as the best-known example of an enterprise ERP system and actually 90 other energy supply companies are using (https://www.odoo.com/customers/industry/energy-supply-4) it as it covers the full range including manufacturing, inventory, purchase, maintenance, IoT, quality control, field service, planning, etc apart from the obvious core solutions. But to repeat no alternative will be an immediate solution.
 
Im not sure if Eskom has any competent people left.
I have worked in many situations where companies have no vendor support agreements, it just meant you had to resolve the issues yourself instead of logging a support request.
Even if you have vendor support often I try fix the issues myself where possible. Only if it gets to the real extreme like hardware failure or some odd errors do I hand over to the vendor.
 
Have you actually ever migrated ERP systems? You will ten to one find that the level of customization is also pretty high and messy which makes said migration even worse. Also keep in mind that every single interface will have to be rebuilt using a middleware tool that will cost you money.

I dont know much about their landscape but replacing Oracle will not sommer be a tjoef-tjaf hit and run exercise.
Certainly agreed. I've seen SAP and Oracle ERP implementations and know how much time and ongoing money both took. No replacement of a system (legacy or ERP) is ever a 'drop-in' solution. For government, it makes a lot of sense to invest in something you can run the distance on without having to rip it out and replace it in a few years, something where 100% of the revenue is retained in country and can benefit local partners, and that can be adapted and re-used in different SOEs and Depts without re-inventing all the consultancy costs. It was done with Alfresco as an enterprise ECM product where government runs the solution at no extra cost to the benefit of multiple departments (some employed local companies to support but others ran it themselves).

Agreed nothing is ever a quick replacement but we've seen Unix replaced by Linux and similar examples. Over time SOEs have had to replace brands as tenders recommend new ones. We actually have a few SMMEs in SA who support migrating from ESRI's ArcGIS to QGIS, from legacy servers to open source cloud solutions, etc. Only big difference is these solutions don't lock you into a single vendor.
 
Yep, because the support for a free & open-source application for a company the size of Eskom will be the better option...
Well you do eliminate the massive foreign licensing costs. The onsite consulting and support still needs to get done, but the big issue raised by Eskom was that licensing cost. So yes there is still that same local component cost that is paid for support but at least it is 100% local and does not go offshore, and they are free to use alternative companies because there is no vendor lock-in.
 
Free? did you miss the pricing tab on their website? And who is going to pay for the migration project? and all the custom dev work required to make this random half arsed ERP solution fit for purpose in the Eskom ecosystem?

BTW, it will only replace a portion of their Oracle footprint, possibly.
Open source usually comes in two models: A paid hosted solution (which is really hosting costs plus support) or you can install itself free of any purchase/license cost but then you support it yourself (or you pay a local Odoo partner to support it for you onsite). Yes any ERP is going to have support costs, as well as customisation costs (even Oracle), and such a replacement is never instantaneous - a year is minimum and often it takes two years to replace something complex.
 
Open source usually comes in two models: A paid hosted solution (which is really hosting costs plus support) or you can install itself free of any purchase/license cost but then you support it yourself (or you pay a local Odoo partner to support it for you onsite). Yes any ERP is going to have support costs, as well as customisation costs (even Oracle), and such a replacement is never instantaneous - a year is minimum and often it takes two years to replace something complex.

two years?

BWAHAHAHAHAHAHA *breathes* HAHAHAHAHAHAHA

*changes underpants*
HAHAHAHAHAHAHA
 
Well you do eliminate the massive foreign licensing costs. The onsite consulting and support still needs to get done, but the big issue raised by Eskom was that licensing cost. So yes there is still that same local component cost that is paid for support but at least it is 100% local and does not go offshore, and they are free to use alternative companies because there is no vendor lock-in.
It's never going to happen with a company the size of Eskom. Would you see a vehicle manufacturer do this? Or a pharmaceutical company?
 
Have you actually ever migrated ERP systems? You will ten to one find that the level of customization is also pretty high and messy which makes said migration even worse. Also keep in mind that every single interface will have to be rebuilt using a middleware tool that will cost you money.

I dont know much about their landscape but replacing Oracle will not sommer be a tjoef-tjaf hit and run exercise.
Oracle is only part of their ERP landscape, you are right.

Having worked on numerous ERP migrations, and for Eskom as well, let me tell you, a migration like that will take 2 years, just to PLAN it.
 
Well you do eliminate the massive foreign licensing costs. The onsite consulting and support still needs to get done, but the big issue raised by Eskom was that licensing cost. So yes there is still that same local component cost that is paid for support but at least it is 100% local and does not go offshore, and they are free to use alternative companies because there is no vendor lock-in.
Or they can just get Cubans. :ROFL:
 
It's never going to happen with a company the size of Eskom. Would you see a vehicle manufacturer do this? Or a pharmaceutical company?
Don't see why not as many large companies run off spreadsheets, but seriously they count 136 Heal/Social Welfare organisations as clients including hospitals and medical manufacturers, 89 energy supply companies, and 606 manufacturing clients worldwide. See https://www.odoo.com/customers.
 
two years?

BWAHAHAHAHAHAHA *breathes* HAHAHAHAHAHAHA

*changes underpants*
HAHAHAHAHAHAHA
Yes speaking from the experience of an Oracle ERP with finance and sales done in a 1,500 person company with 9 branches around our country.
 
Yes speaking from the experience of an Oracle ERP with finance and sales done in a 1,500 person company with 9 branches around our country.

Wow a whole 9 branches and 1500 people.

How does that in any way shape or form relate to a company with 40000+ employees, many power stations, hundreds of thousands of kms of distribution network and switching gear and and and and and and and and....
 
That Oracle tech support must be as happy as a pig in Palastine. He does not have to help people that can't even remember their username or password...
 
Wow a whole 9 branches and 1500 people.

How does that in any way shape or form relate to a company with 40000+ employees, many power stations, hundreds of thousands of kms of distribution network and switching gear and and and and and and and and....
No it doesn't but it was the example I do know about. Not sure though that Eskom actually manufactures? Their business really is maintenance and contract/tender management. Those two areas were covered in our ERP implementation. We had a look at dedicated maintenance applications but realised that all plant equipment/IT/etc is a description, category, serial number, quantity, location, owner, warranty period, maintenance contract, depreciation period, etc with related trouble-ticketing, that was really generic to everything including even medical equipment, as far as asset tracking and maintaining it goes.

But agreed any switch over from any system to another is going to be complex no matter what you put in. It does not magically happen.
 
Don't see why not as many large companies run off spreadsheets, but seriously they count 136 Heal/Social Welfare organisations as clients including hospitals and medical manufacturers, 89 energy supply companies, and 606 manufacturing clients worldwide. See https://www.odoo.com/customers.
They don't run off spreadsheets. They use proper ERP exported to spreadsheets for data manipulation.
 
No it doesn't but it was the example I do know about. Not sure though that Eskom actually manufactures? Their business really is maintenance and contract/tender management. Those two areas were covered in our ERP implementation. We had a look at dedicated maintenance applications but realised that all plant equipment/IT/etc is a description, category, serial number, quantity, location, owner, warranty period, maintenance contract, depreciation period, etc with related trouble-ticketing, that was really generic to everything including even medical equipment, as far as asset tracking and maintaining it goes.

But agreed any switch over from any system to another is going to be complex no matter what you put in. It does not magically happen.
Do you perhaps work for this open source software company?
 
No it doesn't but it was the example I do know about. Not sure though that Eskom actually manufactures? Their business really is maintenance and contract/tender management. Those two areas were covered in our ERP implementation. We had a look at dedicated maintenance applications but realised that all plant equipment/IT/etc is a description, category, serial number, quantity, location, owner, warranty period, maintenance contract, depreciation period, etc with related trouble-ticketing, that was really generic to everything including even medical equipment, as far as asset tracking and maintaining it goes.

But agreed any switch over from any system to another is going to be complex no matter what you put in. It does not magically happen.

You are aware that none of us are in Eskoms senior IT strategy decision making bodies, so you constantly pushing your open source ERP solution here isn't going to achieve anything, other than making you look desperate for sales.

I would also put money on the fact that your ERP implementation would need years of custom dev work to be done to it to even vaguely be fit for purpose for an entity like Eskom.
 
Top
Sign up to the MyBroadband newsletter
X