| |
Excellent post from the Raging Bull Thread:
OK, your company just spend millions fixing its legacy business systems to be Y2K compliant. It's Jan 2000 and you made it over the hurdle - some glitches but what was still broken got fixed quickly. You now need to decide where you will spend your FY2000 systems budget. How? Web, of course. But your whole company is trained in use of your old mainframe order entry, HR, and accounting systems. Your systems staff knows them inside and out because of all the YYYY-MM-DD changes required (incidently its COBOL code!). Your options:
(1) Buy a Web enabled ERP like PeopleSoft or SAP. Downside: huge commitment; huge expense in software, training (systems staff and business personal) and consultants; probably won't seamlessly automate your existing business processes.
(2) Rebuild your apps from the ground up. Use all the in vogue Web development tools. Lets see, humm.. there's stuff to buy and learn ColdFusion, JAVA, HTML maybe C++ and even a new DBMS. Do you retrain your internal systems staff, hire costly consultants, and does anyone understand these 20 year old business processes to be able to generate decent requirements?
(3) Keep your existing apps that actually work, your systems staff understands them, your business people are familiar with the functionality and things continue running smoothly. But here's the kicker... you compliment the old character and/or GUI screens with Web accessibility using JCADA!! Your internal staff and external customers (where appropriate) can access your existing apps via their browser. If you didn't tell anyone, no one would be able to tell that your existing legacy apps are still doing all the work. But in the eyes of the user, your company have a Web presence as-good-as or superior to that of anything else out there.
THIS IS WHY JCADA SALES WILL EXPLODE NEXT YEAR. |
|
