Additionally, analysts may lack formal approaches for capturing and depicting cross functional views of legacy systems. A second advantage is that these analysis techniques provide the basis for an implementation plan based on BPR project findings. Stage one, Enterprise Redevelopment Planning, defines how common data is shared among systems. Once impacted areas are identified, individual systems are examined in more detail. In the customer service example, a dozen systems perform customer functions that impact dozens of data stores.
Functional analysis is performed based on project requirements.
Again, this effort is leveraged using tools and techniques. Results of this process yield a detailed plan to meet BPR requirements. Implementation recommendations resulting from a BPR project may take on tactical and strategic perspectives. GUI front-ends to host based systems and data bases. Both of these approaches are interim solutions to data centralization and are supported by techniques embedded in stages three and four of the USRM framework - Positioning and Transformation.