To: axial who wrote (31314 ) 9/11/2009 9:52:09 PM From: Frank A. Coluccio Respond to of 46821 Hi Jim. Thanks for posting that item. It called to mind the desk-level P&L systems we once developed that tracked traders assets, which included all in-house and outside systems usage and entitlements (features from each of the market data and ticker-plant apps, e.g., SIAC, NYSE, Reuters, Bloomberg, Dow, etc.), personal systems and power utilization costs, real estate, etc., against liabilities in determining a basis for a P&L accounting used to determine commissions. Wow. We never ran into anything that was so intractable as this, though. When I first read your post, in fact, I recalled a discussion I had with an acquaintance who was a quant at Lehman at the time the debacle unfolded, asking him what was going to happen in connection with this very type of eventuality, since it was generally perceived that virtually everyone would be let go (which turned out to be the case, at his stratum of involvement <which, as I understand it, was rather critical>, almost across the board). re: Once it went bankrupt, the staff who supported these systems “evaporated”, according to Steven O’Hanlon, president of Numerix, a pricing and valuation company which is working with Lehman Brothers Holding Inc to unwind the derivatives portfolio. “The more time goes by, the less insight remains in terms of the people who staffed those systems.” Contrast, from a blog I just bumped into: -- How to retire (respectfully) legacy systems Natty Gur, Enterprise Architect | 09-11-09 They served us for a long period of time, but (for different reasons that I wont cover in this post) now the time to say good bye and to retire them. Legacy systems exist in each and every enterprise and we all have the experience of retire them. The question is whether your enterprise have a predefine process to retire legacy systems or is just process that happened? In this post I'll try to share a retirement process for legacy systems. Cont.: weblogs.asp.net ------