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

1. Enterprise Content and Business Process Management Developing an ECM and BPM IT architecture Feb 2008

2. What Drives CM and BPM? Business drives IT Business requirements dictate the architectures We must understand the business requirements before proposing solutions The business must have a strategic vision We in IT must work with the business to develop the architectures needed to implement the strategic vision of the business

3. The Architectures Data or information architecture Application architecture Infrastructure and Standards Business process architecture (tasks)

4. Data Architecture The data flow architecture is comprised of 4 major pieces Inputs Content and metadata storage Business processes Outputs The business requirements drive the dataflow architecture

5. Data Architecture Inputs Scan Fax Desktop apps Email forms Stored in repositories Content , data and metadata storage Content triggers business processes Business Processes Meet SLAs, compliance, customer service Business Process produce output Outputs Documents, historical data, web services, business information

7. data, metadata and content

8. We need to federate content repositories

9. We need real-time access to data and metadata repositories

10. The strategic plan must consider performance (e.g. document retrieval using cache services)

11. Physical architecture is driven by

12. Geography

13. Volume

14. Performance requirements

16. Application Architecture J2EE assumed Frameworks (e.g. BPF) Multi-tier model (client, web, business, EIS) Components (e.g. JSPs, servlets, portlets, EJBs) Data interfaces (JDBC, JMS, APIs) Web services Legacy interfaces User authentication and authorization (security)

17. Application Architecture All applications have some level of requirement for: Authentication Authorization Auditing Logging Statistics Error handling These can be built into the architecture

18. Business Process Architecture All applications are not the same Categorize the applications in the strategic plan Internal documents (e.g. quarterly reports) “One and done” applications (e.g. service documents) Case management applications (e.g. underwriting)

19. Creating the Architecture Connect architecture to the business Analyze the business current state Construct the business target state Analyze the business target state and identify gaps and opportunities Create an architecture model (a graphical representation of the business view of the data)

20. Translating Architecture to Projects Common mistakes Attempt to implement too much, too quickly Inability to tie implementation to business success Underestimation of resistance to change No commitment or buy-in from the entire organization Lack of supporting enterprise-wide processes Insufficient focus on the people issues

21. Translating Architecture to Projects Identify candidate projects (translate the architecture into business-focus projects) Select/prioritize key projects Narrow the scope of selected projects

22. Implementing the Architecture Establish Metrics Measure architecture effectiveness Set business objectives Set project objectives Set architecture objectives

23. Gaining support Gaining executive support Summarize the business needs/opportunities/gaps Construct a presentation level model Develop a brief proposal for the project(s) Develop a one-page bottom line Gaining IT support Discuss early versions Solicit input Request volunteers to review the architecture

24. Summary Developing the CM/BPM architecture requires viewing the enterprise from many angles The architecture must meet the business requirements The architecture integrates content with business process The architecture must provide benefits to the business