This document discusses enterprise content and business process management (ECM/BPM) architectures and operating models. It describes four operating models - coordination, diversification, unification, and replication - and provides examples of each. It emphasizes that the enterprise architecture should reflect the company's operating model and integrate business processes, data, technologies, and customer interfaces. It outlines phases of architectural maturity from business silos to optimized core business and modularity. Key aspects of developing an ECM/BPM architecture include understanding requirements, performing a gap analysis, selecting strategic technologies, and ensuring performance, scalability, integration and an integrated product suite.

1. Enterprise Content and Business Process Management Developing an ECM/BPM architecture David M Champeau Feb 2008

2. The Operating Model Coordination Model Organic: stream of product innovations easily made available to existing customers using existing integrated channels Acquisition: can acquire new customers for existing products but must integrate data Diversification Model Organic: small business units may feed core business; company grows through business unit growth Acquisition: unlimited opportunities; must ensure shareholder value Unification Model Organic: leverage economies of scale by introducing existing products/services in new markets; grow product line incrementally Acquisition: can acquire competitors to leverage existing foundation; must rip and replace infrastructure Replication Organic: replicate best practices in new markets; innovations extended globally Acquisition: can acquire competitors to extend market reach; must rip and replace High Business Process Integration Low Low High Business process standardization

3. Operating Model Examples Coordination Model MetLife Diversification Model Carlson Companies Unification Model Delta Airlines Replication Model ING Direct

4. Characteristics of Four Operating Models Coordination Shared customers, products or suppliers Impact on other business unit transactions Operationally unique business units or functions Autonomous business management Business unit control over business process design Shared customer/supplier/product data Consensus processes for designing IT infrastructure services; IT application decisions made in the business units

5. Coordination Model Example Merrill Lynch Global Private Client Single face to customer through multiple channels Customer transactions are independent, but product data is shared Individual financial advisors own their customer relationships Financial advisors customize their interactions with customers Financial advisors in 630 offices exercise local autonomy within bounds of their responsibilities Total Merrill platform provides shared access to technology and data IT organization provides central technology standards Goals Seamless access to shared data All things to some people Integrated but not standardized product lines and functions Built to enhance customer service

6. Enterprise Architecture vs IT Architecture Enterprise Architecture Organizing logic for business process and IT infrastructure reflecting the integration and standardization requirements of the companies operating model Identify the processes, data, technologies and customer interfaces that take the operating model from vision to reality IT Architecture Business process architecture (tasks) Data or information architecture Application architecture Infrastructure and standards

7. Understand Where You Are and Where You Want to Go Undertand that you must go through certain phases as a company It takes a team effort Everything revolves around the business IT needs to learn the business before offering solutions

8. Phases of Architecture Maturity Business Silos Standardized Technologies Optimized Core Business Modularity Phase 1 Phase 2 Phase 4 Phase 3 You are here Some of your competitors are here

9. Building a team 3 areas of knowledge are required Business Technology Process

10. CM and BPM enterprise model Scan BP1 Rpts Fax BP2 XML Content Repository Content Repository PDF BP3 PDF XML BP4 DB email

11. CM and BPM enterprise model CM and BPM enterprise model Scan BP1 Rpts Fax BP2 XML Content Repository Content Repository PDF BP3 PDF XML BP4 DB email Content Engine Process Engine Appl Engine Rules Engine Web Services Admin Systems Content Repositories

12. Insurance Business Model Case management Case - a specific occurrence or matter requiring discussion, investigation and decision A Case contains one-to-many object relationships Claim can relate to multiple policies and accounts Address change can affect multiple accounts A Case is a work-in-process folder

13. Where to Start Current State diagram Target State diagram Identify the gaps (gap analysis) Each future project must contribute something to the Enterprise Architecture

14. Next Step – Standardized Technologies Understand the Business Vision Moving from Business Silos to Standardized Technologies requires some hard decisions Understand that we are making business decisions Identify requirements for the technologies

15. Technology Business Requirements in CM and BPM How do we decide on which company(s) is best positioned to provide strategic technologies? One place to start is the stock prices

16. Example - Stock price of Tibco

17. Stock price of IBM

18. Enterprise CM and BPM Requirements Integrated product suite Performance Scalability Centralized and Distributed Integration with other technologies Complete content federation

19. Integrated Product Suite Content Management Business Process Management Records Management Email Management Web Content Management Application Development Frameworks (BPF) Component Plug-in capability

20. Why an integrated product suite? Why not mix and match pieces from many companies? Too much time wasted trying to figure out how the pieces fit together Perfection does not exist Begin today implementing a platform that does 80% This will free up resources to deal with the other 20%

21. Performance Federated content repositories need high-performance content engines Ability to cache images around the enterprise

22. Scalable Horizontally Build up the core engines Vertically Distribute engines Standardized server platform

23. Integration with other technologies LDAP Rules engines Web services On-Demand Sharepoint connectivity

24. Expanding the vision Process Analysis Process Simulation Records Management Records Crawler Electronic Forms System Monitoring Process modeling tools