Why we need an enterprise architecture

2,588 views
2,279 views

Published on

Presented to the managers of Philippine Health Insurance Co. to show the need for an Enterprise Architecture.

1 Comment
1 Like
Statistics
Notes
No Downloads
Views
Total views
2,588
On SlideShare
0
From Embeds
0
Number of Embeds
17
Actions
Shares
0
Downloads
76
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

Why we need an enterprise architecture

  1. 1. Enterprise Architecture Why We Need It By Ruben Canlas Jr. IT & Change Management Advisor Feb. 29, 2012Sunday, March 4, 12
  2. 2. Why is architecture important? Airport Shanty in Metro Manila jiggmin.comSunday, March 4, 12
  3. 3. Stovepipe Company Billing & Collection 2002Sunday, March 4, 12
  4. 4. Stovepipe Company Billing & Collection Payroll 2007Sunday, March 4, 12
  5. 5. Stovepipe Company Billing & Collection Payroll Customers 2009Sunday, March 4, 12
  6. 6. Stovepipe Company Billing & Web: Collection Payroll Customers Self-service & Trouble 2011 handlingSunday, March 4, 12
  7. 7. Issues Billing & Payroll Collection Web: Customers Self-service & Trouble handlingSunday, March 4, 12
  8. 8. Issues • Territorial: kanya-kanya Billing & Payroll Collection Web: Customers Self-service & Trouble handlingSunday, March 4, 12
  9. 9. Issues • Territorial: kanya-kanya • Doing things the right way -- but are they the right things? Billing & Payroll Collection Web: Customers Self-service & Trouble handlingSunday, March 4, 12
  10. 10. Issues • Territorial: kanya-kanya • Doing things the right way -- but are they the right things? Billing & Collection Payroll • Slow time to develop products & services Web: Customers Self-service & Trouble handlingSunday, March 4, 12
  11. 11. Issues • Territorial: kanya-kanya • Doing things the right way -- but are they the right things? Billing & Collection Payroll • Slow time to develop products & services • Duplication of data and work Web: Customers Self-service & Trouble handlingSunday, March 4, 12
  12. 12. Issues • Territorial: kanya-kanya • Doing things the right way -- but are they the right things? Billing & Collection Payroll • Slow time to develop products & services • Duplication of data and work • Unreliable information Web: Customers Self-service & Trouble handlingSunday, March 4, 12
  13. 13. Issues • Territorial: kanya-kanya • Doing things the right way -- but are they the right things? Billing & Collection Payroll • Slow time to develop products & services • Duplication of data and work • Unreliable information • Web: Customers Self-service Lots of waste and rework & Trouble handlingSunday, March 4, 12
  14. 14. Issues • Territorial: kanya-kanya • Doing things the right way -- but are they the right things? Billing & Collection Payroll • Slow time to develop products & services • Duplication of data and work • Unreliable information • Web: Customers Self-service Lots of waste and rework & Trouble handling • Knowledge lostSunday, March 4, 12
  15. 15. EA FOUNDATIONS BUSINESS STRATEGY Enterprise Architecture Information & Application Technical Process Architecture Architecture Architecture Business Software Infrastructure processesSunday, March 4, 12
  16. 16. EA FOUNDATIONS BUSINESS STRATEGY UHC Alignment Enterprise Architecture Information & Application Technical Process Architecture Architecture Architecture Business Software Infrastructure processes Governance and IntegrationSunday, March 4, 12
  17. 17. Enterprise Architecture: aligns processes, information, applications, & infrastructure with Philhealth strategy & objectivesSunday, March 4, 12
  18. 18. Enterprise Architecture: will help Philhealth become customer-focused, process-oriented, and make better programs & decisionsSunday, March 4, 12
  19. 19. THANK YOU! slideshare.net/rubencanlasSunday, March 4, 12

×