Y2K how bad and whygreenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread
I am finishing up Y2K checks on all of my programs which number about 800. Also we are in the process of selecting a new system to replace my system and the existing factory / distribution center system. We will probably go with SAP of Germany. It will take a few months to implement the SAP system but it can be done before 12/99. These are Y2K solutions.
On the other hand our NCR 3443 series platforms have a year 2000 problem and will have to be upgraded or replaced if we don't implement the SAP system which will include an AS400 computer to replace what is now used.
The bottom line is we should be Y2K ready either way. There are many other organizations that will need to replace systems and hardware to be compliant.
Leaving out imbedded chips these are reasons in my opinion why Y2K could be serious: 1) In the remaining 14 months it may be impossible to fully meet demand for new systems and hardware. 2) At some point soon some, maybe many organizations may loose what IT personal they have to other organizations willing to pay the bucks. 3) This is my main reason for thinking Y2K may be severe. Early this year I changed jobs for more pay only to come back to my previous employer. Durning the prehire interview I met and was interviewed by the MIS director, a non programmer and the company COO. I asked the COO if they had a handle on Y2K. He nodded approvingly. Soon after going to work for my new employer while writing some test programs and learning the new language / system I discovered that the existing application which was sold to 200 to 300 customers could not handle the year 2000 without modifications. The year 2000 would become 1900. I pointed this out in an MIS meeting and it was decided to make it a new project. However it was still treated as an out of favor stepson the new applications in progress or planned.
I suspect that the above applies to many organizations. I also suspect that this will remain true until Y2K makes the front page day after day sometime in 1999, probably mid 1999. July 1, 1999 COO dictates letter for secretary to type up requesting MIS department to drop everything and start working on Y2K. Secretary brings memo to COO for signature and at the same time informs him that the last programmer on staff has just given notice.
-- Ed Stevens (firstname.lastname@example.org), October 30, 1998
A few months to implement a SAP package. I can almost hear the laughing all over America tonight.
-- Rancherdick (email@example.com), October 30, 1998.
A lot of the 'hire em cheap, let em leave, plenty more where they came from' small software companies are going to hurt soon - and some of them are going to go out of business due to Y2K problems with the software they have been peddling. The sad part of that is that Microsoft will be there to take another piece of the market away from the little guy.
-- Paul Davis (firstname.lastname@example.org), October 30, 1998.
Are Microsoft's systems certified y2k compliant? Is there some reason why they should be considered in any better than any other huge corporation? Is there any reason to think that a company that has never delivered a software program or update on the scheduled day can complete assessment, remediation and testing by the year 2000? ==================================================================
-- Michael Taylor (email@example.com), October 31, 1998.
Some of my clients are SAP installers for *******company. I hope you have hireds a LOT of help.
-- Chuck a Night Driver (firstname.lastname@example.org), October 31, 1998.
Excuse me but my only exposure to SAP was a demo yesterday. I am a code head not the MIS director. SAP is saying smaller companies can implement SAP in 3 to 8 months. Exactly what is involved in the transition that I am missing?
I do see the file conversions, training and tweaking but some of you are suggesting more. From your experience what can I expect?
-- Ed Stevens (email@example.com), October 31, 1998.
From my experience it doesn't matter whether MS products are Y2K compliant or not. What matters is whether or not the marketing dept. can sell management on more MS junk. Which they always can. MS has the best marketing dept. on the planet. And when they sell the boss on using Access to deploy company wide shared databases - guess who will get the job of explaining the boss ordered something that won't run if more than 20 or 30 people log in at the same time? It won't be the MS marketing dept. - and if the boss calls to complain about performance they will just sell him SQL. And so it goes ...... and the little guy who provides better service from day one gets it in the neck because he did not understand it does not matter if the software works perfectly or not - all that matters is selling it and providing plenty of patches that sound like they might fix the problem. And always having an upgrade path. Have you ever had an MS tech or market person NOT recommend an upgrade? I think it is part of their standard script - if you called and said your mouse had quit they would try to sell you a mouse upgrade!!!
-- Paul Davis (firstname.lastname@example.org), November 02, 1998.
You're going to implement a SAP package in a few months are you? Best of luck. Quite frankly it amazes me that a company that has 800 programs is still deciding what approach to take to solve their y2k problem.
Assuming the best, that it only takes a few months, don't you think that there are thousands of other companies like yours that are planning on doing the same thing in the same timeframe? There's no doubt that there is not enough experienced manpower for all the companies that want to go that route to actually do so.
Then to top it off, there is still the testing phase to ensure that the new SAP system interfaces correctly with any other applications you are using, and the matter of whether your data is in a format that is compliant with that of your suppliers and customers.
You'll also need enough time for your employees to be fully trained in the new SAP system as well.
I sincerely hope you make it. Everybody certainly won't!
-- Craig (email@example.com), November 03, 1998.
Ed with SAP experience you can make a fortune in Europe, maybe you can over there.
-- Richard Dale (firstname.lastname@example.org), November 04, 1998.