ECM BPM IT Architecture

2,175 views

Published on

Something that I did to show all the pieces and parts. Needs to be updated to reflect the changes in the industry.

Published in: Technology
  • Be the first to comment

ECM BPM IT Architecture

  1. 1. Enterprise Content and Business Process Management<br />Developing an ECM and BPM IT architecture<br />Feb 2008<br />
  2. 2. What Drives CM and BPM?<br />Business drives IT<br />Business requirements dictate the architectures<br />We must understand the business requirements before proposing solutions<br />The business must have a strategic vision<br />We in IT must work with the business to develop the architectures needed to implement the strategic vision of the business<br />
  3. 3. The Architectures<br />Data or information architecture<br />Application architecture<br />Infrastructure and Standards<br />Business process architecture (tasks)<br />
  4. 4. Data Architecture<br />The data flow architecture is comprised of 4 major pieces<br />Inputs<br />Content and metadata storage<br />Business processes<br />Outputs<br />The business requirements drive the dataflow architecture<br />
  5. 5. Data Architecture<br />Inputs<br />Scan<br />Fax<br />Desktop apps<br />Email<br />forms<br />Stored in repositories<br />Content , data and metadata storage<br />Content triggers business processes<br />Business Processes<br />Meet SLAs, compliance, customer service<br />Business Process<br />produce output<br />Outputs<br />Documents, historical data, web services, business information<br />
  6. 6. Data Architecture<br /><ul><li>Everyone has multiple repositories
  7. 7. data, metadata and content
  8. 8. We need to federate content repositories
  9. 9. We need real-time access to data and metadata repositories
  10. 10. The strategic plan must consider performance (e.g. document retrieval using cache services)
  11. 11. Physical architecture is driven by
  12. 12. Geography
  13. 13. Volume
  14. 14. Performance requirements
  15. 15. Business requirements</li></li></ul><li>Physical Architecture<br />Bringing together all the physical hardware<br />Capture, Image Services, Content Engine, Process Engine, Application Engine, Cache Server, Web Server, Database Server, Directory Server, Messaging Server, Reporting Engine, Rules Engine<br />
  16. 16. Application Architecture<br />J2EE assumed<br />Frameworks (e.g. BPF)<br />Multi-tier model (client, web, business, EIS)<br />Components (e.g. JSPs, servlets, portlets, EJBs)<br />Data interfaces (JDBC, JMS, APIs)<br />Web services<br />Legacy interfaces<br />User authentication and authorization (security)<br />
  17. 17. Application Architecture<br />All applications have some level of requirement for:<br />Authentication<br />Authorization<br />Auditing<br />Logging<br />Statistics<br />Error handling<br />These can be built into the architecture<br />
  18. 18. Business Process Architecture<br />All applications are not the same<br />Categorize the applications in the strategic plan<br />Internal documents (e.g. quarterly reports)<br />“One and done” applications (e.g. service documents)<br />Case management applications (e.g. underwriting)<br />
  19. 19. Creating the Architecture<br />Connect architecture to the business<br />Analyze the business current state<br />Construct the business target state<br />Analyze the business target state and identify gaps and opportunities<br />Create an architecture model (a graphical representation of the business view of the data)<br />
  20. 20. Translating Architecture to Projects<br />Common mistakes<br />Attempt to implement too much, too quickly<br />Inability to tie implementation to business success<br />Underestimation of resistance to change<br />No commitment or buy-in from the entire organization<br />Lack of supporting enterprise-wide processes<br />Insufficient focus on the people issues<br />
  21. 21. Translating Architecture to Projects<br />Identify candidate projects (translate the architecture into business-focus projects)<br />Select/prioritize key projects<br />Narrow the scope of selected projects<br />
  22. 22. Implementing the Architecture<br />Establish Metrics<br />Measure architecture effectiveness<br />Set business objectives<br />Set project objectives<br />Set architecture objectives<br />
  23. 23. Gaining support<br />Gaining executive support<br />Summarize the business needs/opportunities/gaps<br />Construct a presentation level model<br />Develop a brief proposal for the project(s)<br />Develop a one-page bottom line<br />Gaining IT support<br />Discuss early versions<br />Solicit input<br />Request volunteers to review the architecture<br />
  24. 24. Summary<br />Developing the CM/BPM architecture requires viewing the enterprise from many angles<br />The architecture must meet the business requirements<br />The architecture integrates content with business process<br />The architecture must provide benefits to the business<br />

×