Monica Crocker Implementing Ecm Aiim 2009

Implementing Enterprise Content Management Gaining the Benefits while Avoiding the Headaches Monica Crocker, PMP, CRM, LIT ECM Business Consultant [email_address] 952-844-2683 Minnesota AIIM CONTROL Expo January 26, 2009

Definitions Enterprise Content Management, as per AIIM: Capture, manage, store, preserve and deliver content and documents related to organizational processes. Structured versus Unstructured Information: ECM allows the management of the organizations unstructured info, wherever that information exists. Records Management: Providing the right information to the right person at the right time at the lowest possible cost. Business Process Management, as per AIIM: practice that seeks to model, modularize, service-enable, monitor and ultimately optimize business processes.

Business Drivers Increased efficiency/productivity (do more or use less or keep more revenue) Better reporting/transparency Improve process consistency Improve organizational flexibility/agility Retain corporate knowledge Extend processes outside the organization Retain staff or make new ones productive faster Improve customer service/satisfaction Enable compliance with regulations or standards Facilitate litigation response

Technologies Included page 1 of 2 Imaging/Scanning-for content that originates as paper Character Recognition (ICR/OCR)- for conversion of bitmap characters into ASCII Document Management-for content that originates as electronic files (Sharepoint and shared drives) Electronic Forms-for repeatable transactions that can be completed electronically Email Mgmt-for…well, you know Workflow-to apply automated rules to standardized, high volume or high value electronic business processes

Technologies Included page 2 of 2 Web Content Management-for content published to web sites Collaboration Tools-for ad hoc management of content creation and communication, included related tasks Electronic Records Mgmt-the tools needed to ensure electronic records are managed in a manner compliant with applicable rules, such as retention Electronic Discovery Tools-the tools needed to find and secure content subject to litigation or audit Enterprise Report Mgmt (COLD)-for content that used to be printed on green bar reports

Movement toward standards File Formats: TIFF, PDF-A Data exchange format: XML Development tools: java, .NET Repository “federation”: access across repositories Storage media: no longer requires optical disk Web-based user interfaces Use industry standard databases Vendors offering packaged interfaces to solutions with a significant % of the marketplace (such as SharePoint) CMIS: Content Management Interoperability Services (from IBM, Microsoft, EMC, SAP, OpenText, Oracle, and Alfresco)

Budget/Staffing Issues Significant ongoing expense of “capture” labor Install/upgrades may require vendor assistance Application support requires specialized training Users need significant training (initial and ongoing) Systems require redundancy/high availability Applications require a lot of data and can significantly impact database infrastructure Solutions require massive storage To out source or not to outsource…. Document capture services Support (including SaaS) Development

Implementation Pain The top 5 issues encountered during implementation Underestimated process and organizational issues; Understand solution impact & organizational readiness, commitment & acceptance Lack of training for internal staff; Application (use and support) Process and policies Internal politics Lack of support (lack of understanding of strategic importance) Changing priorities Uneven use-poor procedures and enforcement; Ways of working change(process & people) Alternatives remain (printers, personal storage) Underestimated the effort to migrate content; Electronic Paper (source, AIIM Top 5 ECM Implementation Issues, YouTube)

Project Approach Plan the solution for the enterprise, but implement on a functional level (information architecture) Identify Project Steering Committee-for the program Identify Project Champion-for each project Gather Requirements-for the enterprise Identify Standards-for the enterprise Define Deployment Approach-how centralized? Design Solution (both enterprise and function level) Complete Business Process Redesign/Re-engineering Define Functional Requirements (functions, NOT features) Develop Solution (see slide) Implement Solution – one function at a time (which is not the same as piecemeal)

Project Anomaly Over-communication is almost impossible COMMUNICATE strategically COMMUNICATE politically COMMUNICATE within the project team COMMUNICATE tactically (users) COMMUNICATE with other organizations/users COMMUNICATE with the vendor(s) COMMUNICATE with anyone that might be creating a “content silo”

Design Solution Options include: Archival of documents created by another system - file import Conversion of existing backfile - file capture, including indexing, bar codes, ICR/OCR Capture of day forward documents - file capture, including indexing and fax capture Automated routing of documents in workflow Flexible searches – including full text, multiple record types and reuse of documents for future work Integration with other system(s) – as needed to facilitate all the functions above Various tools/techniques for user support/training

Resources Required page 1 of 2 Technical Strategy/architecture Database Application Support Infrastructure Support Developer Security Business Analyst Project Manager (with strong hold on scope creep) Subject Matter Expert from all affected business areas Executive Level Sponsorship or other strong driver

Resources Required page 2 of 2 Records Manager and/or Legal Taxonomist/Librarian/Information Architect-to help with Taxonomy (see following slides) Change Management Expert Governance/Steering Committee-that is willing to provide long term oversight Solution Support Options Internal Outsourced SaaS

Taxonomy Soapbox Definitions Metadata: data about data, or in this case, content Dublin Core Metadata (ISO Standard 15836-2003): The Dublin Core Metadata Element Set is a vocabulary of fifteen properties for use in resource description. Taxonomy: Means to classify content Functional Taxonomy: classifying content based on the function it supports, versus the part of the organization that created it or the specific topic (Human Resources example) Other types of taxonomies: hierarchical, folksonomy, Lesson learned: come up with taxonomy before adding content, make that lexicon intuitive, long lasting and readily available for reference, including preferred terms, definitions, synonyms, etc. (blue form example)

Findability Why it’s important and what it is* The art and science of making content findable, based on the standards users set as a result of their web experience “ A fundamental difference between Findability and its predecessor and component, search, is where the burden of effort lies. Under Findability, the burden of intelligent content processing is placed on the content itself. It is the content that is made “findable” in any number of scenarios….Findability strategies establish content that is aware of its potential value in any number of settings, and leverage art and science to respond to these settings.” Precision versus Recall – finding only what is relevant, versus finding everything When asked the degree to which Findability is critical to their overall business goals and success, 62% of respondents indicated that it is imperative or significant. *AIIM, Int’l White Paper “Findability” )

Taxonomy Approach Develop standard (ideally, enterprise-wide) taxonomy (or at least metadata) Collect all existing organization “taxonomies” and research other examples Develop, test, implement organizational taxonomy Implement lexicon within ECM Individuals don’t want to figure it out themselves Consistency is critical to system integrity Intuitive indexing leads to improved system usability Indexing is a significant portion of effort associated with system, so it should be foolproof Automated indexing only works if both systems use similar values (call things the same name)

Conclusion A successful, sustainable ECM program must involve collaboration between records management, information management, IT, and business users. You must have a foundation of policies and standards that are practical and consistently implemented. Update and/or create records retention schedules and follow up with regular, proper disposal of records. Institute on-going education and training for business users at all levels. Build on what others have done!

Resources AIIM: www.aiim.org and http://www.aiim.org/chapters/minnesota/ ARMA: www.arma.org and http://www.twincities.arma.barr.com/ ISO: www.iso.org ANSI: www.ansi.org TAWPI: www.tawpi.org BFMA: www.bfma.org Dublin Core Metadata Initiative: www.dublincore.org National Archives Records Mgmt: www.archives.gov/records-mgmt/ KMWorld: www.kmworld.com/WhitePapers

Questions? Monica Crocker, PMP, CRM, LIT ECM Business Consultant [email_address] 952-844-2683

Monica Crocker Implementing Ecm Aiim 2009

More Related Content

What's hot (19)

Viewers also liked (6)

Similar to Monica Crocker Implementing Ecm Aiim 2009 (20)

Recently uploaded (20)

Monica Crocker Implementing Ecm Aiim 2009