Within the Enterprise Architecture (EA) activities of the Federal Government, one of the most difficult issues is the justification and quantification of major IT programs. EA plans cover the current processes, data systems and infrastructure, (the AS-IS), the future processes, data, systems and infrastructure (the TO-BE) and the roadmap transition plan from one to the other. Associated with EA is a real requirement to provide a Business Case Analysis (BCA) for major changes based upon quantifiable improvement in key mission/business measures in accordance with the organization/mission goals and objectives. In order to provide the steps in the transition plan, PROCESSES, DATA, SYSTEMS GAP analysis (difference between AS-IS inventory and TO-BE plan, including COTS as a TO-BE reference model) is being done in most EA plans. Now, a similar technique is being used with the business process activity models in a more proactive sense, applying volume, frequency and value parameters to simulate the AS-IS for validation and the TO-BE plan to view the future payoff. This paper shows some of those techniques/methods and addresses specific successes to demonstrate the validity of the approach to show return on IT investment.
Published in 2004
https://enterprisearchitecture.dk/files/PerformanceBasedEnterpriseArchPlanningjp01.pdf
Publisher:
https://enterprisearchitecture.dk/files/PerformanceBasedEnterpriseArchPlanningjp01.pdf
Date added: 08/02/2018
Enterprise Architecture