This document represent my Point of View in the field of ECM

1. Enterprise Content Management Point of View Presentation kit – version 2.0 2010-08-01 Claudio Reyes [email_address] +46 8 699 7357

3. Which Leads to Information Overflow and Pain Categories Typical Pain Points (not exhausting ) 11-02-21 70 % of all the created information could have come from reuse (AIIM) Time Cost Risk Single source driving different and unique business processes – unsustainable Content is difficulty to access (e.g. invoices, checks, memos, etc.) – impossible to use. Demands for rapid document life cycle R&D, information/clams processing, etc. – not being meet. Organization content increases 200% annually. (Forrester Research) Multiple, disparate technologies to manage multiple content types – no control. Content applications requires integration with other applications – it is not working. Managing multiple localized points of presence on the Web - is not working Uncertain if our regulatory needs are meet - we do not know why? Operations in a regulated environment - is not working Long term preservation demands are not meet - it is a mess Structured Unstructured 80% of the company information is unstructured (Fulcrum Research )

5. ECM Solution Framework 11-02-21

6. The ECM Solution Framework Why do I have difficulties controlling content when working in projects? Why do I have a multitude of redundant ECM applications? Why am I not compliant with regulations? What culture and technology will enable efficient content flow in a collaborative environment? What platform and solution vendor satisfies my future needs? What system/solution will make my business compliant? How do I make the cultural and technology change to maximise content flow? How do I change my application landscape whilst keeping the current efficiency and end-user satisfaction? How do I maintain the organisation compliant over time? Develop insight (Why?) Explore Solutions (What?) Execute a plan (How?) Workflow “ Manage content flow” Consolidation “ Manage content effectiveness” Compliance “ Manage content risk” Solution Approach ECM Scenarios 11-02-21

11. Additional Slides

15. Typical Client Scenario Using the Scenario “Consolidation” 11-02-21

18. Explore Solutions Architecture Capability Basic Intermediate Advanced 0 1 2 3 4 Anecdotal Anticipated Need Current Ability 3-5 Year Need 11-02-21 Illustrative example Process Governance Technology People Strategy Technology People Process Strategy Governance Why do I have difficulties controlling content when working in projects? Why do I have a multitude of redundant ECM applications? Why am I not compliant with regulations? Which culture and technology will enable efficient content flow in a collaborative environment? Which platform and solution vendor satisfies my future needs? Which system/solution will make my business compliant? How do I make the cultural and technology change to maximise content flow? How do I change my application landscape whilst keeping the current efficiency and end-user satisfaction? How do I maintain the organisation compliant over time? Develop insight (Why?) Explore options (Which?) Solution Development (How?) Collaboration “ Manage growth” Consolidation “ Manage effectiveness” Compliance “ Manage risk” Solution Approach Focus Areas User Interface Document Management Collaboration Workflow/BPM Search Forms Management E-mail Content Integration Applications Server Client Composite Service Business Process UI UI UI

21. Knowledge Capital in the Area 11-02-21

24. ECM Strategic Workbook 11-02-21 Tools, templates, checklist, frameworks 2. Develop Insight 1. Planning 3. Explore Solutions Plan and organize Gather stakeholder input Determine key business objectives Assess current business Define Organizational needs Cost and benefit analysis Create vision Define value proposition Assess current technology Roadmap 4. Transformation Plan

25. Screen shoot from the actual Workbook 11-02-21 Phases describing the topic Activities with step by step instructions Frameworks, templates, checklist, etc.