Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : PSFT - 1999: The "Make-It-or-Break-It" Year? -- Ignore unavailable to you. Want to Upgrade?

To: esterina who wrote (191)	3/8/1999 11:41:00 AM
From: The Player	Read Replies (3) \| Respond to of 1274

Another article from Information Week on crappy implementations. Anybody have any thoughts on when, and if PSFT is gonna pull out of this slump? Does anyone feel that this ERP setback will continue post-Y2K, despite software co.'s statements to the contrary? Regards, The Player Mar. 07, 1999 (InformationWeek - CMP via COMTEX) -- Enterprise resource planning software can replace a host of legacy systems that aren't year 2000 compliant. But with the millennium just around the corner, some companies are facing a crunch: Their ERP implementations can't be finished by Dec. 31. Entex Information Services Inc., a $2.5 billion systems integration and outsourcing company, last month abandoned a large-scale implementation of SAP R/3, taking a $10.7 million write-off. CIO Spencer McIlmurray says Entex had continued to renovate its legacy systems in case the SAP implementation wasn't successful. The company will now spend about $7 million to update those homegrown systems. "If this were 1995, we might have continued with SAP," he says. "But the closer it got to the year 2000 without being fully implemented, the more we jeopardized our ability to be safeguarded." An SAP spokeswoman says the project was canceled because Entex didn't have enough money to continue, not because of a Y2K deadline. Entex will look at several ERP products next year. Trimble Navigation Ltd., a maker of global positioning systems in Sunnyvale, Calif., also hit the Y2K wall. Last year, it began implementing manufacturing, distribution, and financial software from Baan Co. The goal was to replace its noncompliant Manman application, from the MK Group, with 400 Baan user licenses by July. But the Baan software didn't mesh well with the way Trimble does business. Baan has its own way of doing things, and that made it difficult for Trimble to implement without major modifications, says CIO Bob Denis. The company would have been forced to drastically alter its manufacturing processes to effectively run the software, he says. Because Trimble has a U.K. subsidiary, the company also would have had to do extra development work to make Baan meet its euro requirements. "Every modification adds more time," says Denis. Earlier this year, Trimble killed the Baan implementation and placed a Y2K patch on its Manman system; by year's end, it will upgrade to the newest release of that software, which is Y2K compliant. It will be easier to implement the latest Manman version, Denis says, because the company is familiar with the software." Little Caesars Enterprises Inc., the Detroit pizza chain, also faced an imposing Y2K crunch. The company recently replaced an implementation of PeopleSoft's financial applications with Infinium Software Inc., according to Maria Burud, VP of North American operations at Infinium. Infinium's applications treat Little Caesars' many disparate enterprises, which include the National Hockey League champion Detroit Red Wings, as separate business units without requiring heavy customization. PeopleSoft says the problems at Little Caesars were due to a change in IT management. Little Caesars didn't return calls. David Dobrin, an analyst with Benchmarking Partners, says too many companies select an ERP package that doesn't meet their needs. But knowing when to pull the plug, he says, "is a sign of maturity, [not] a case of cold feet."