If the overlap in common modules produces multiple data sources with similar yet semantically incompatible data, then you must weigh the resulting data integration challenges as a cost.
The key to application rationalization is establishing a good set of metrics for measuring the costs and value of the application. AppRat is an ecellent tool for prioritizing projects. It also gives you an excellent business case for decommissioning applications. I think this is what Steve was referring to as heatmaps. AppRat will tell you which applications cost the most and produce the least value. Those are the ones to target first. Anne On 12/21/08, htshozawa <[email protected]> wrote: > Just want to clarify a point. By redundancy, are we talking about > having multiple set of similar data/functionalities or about multiple > set of similar business process? > > For example, if there are SAP app modules and Oracle app modules at a > company without any overlapping modules but an overlap in common > module functionalities, is there a redundancy. MDM and identity > management reduces users from doing the same operations on multiple > systems but IMO it doesn't really doesn't totally eliminate the data > on multiple systems. > > H.Ozawa > > --- In [email protected], "Anne Thomas > Manes" <atma...@...> wrote: >> >> Redundancy is appropriate when the business value contributed by the >> redundancy exceeds the costs of maintaining the redundancy. (and > that >> pertains to high availability use cases, too.) >> >> Anne >> > > >
