This document discusses the basics of an ECM (Enterprise Content Management) project. It outlines that the first steps are to analyze the business processes, understand the business language and taxonomy, and map out the flow of content. The business analyst should determine the type of business process (e.g. case management, straight through processing), identify roles and steps, and draw pictures to define the current and target states to identify gaps for the new process.

1. Some Basics of an ECM ProjectDavid ChampeauIBM FileNet Certified ProfessionalAIIM ECM MasterAIIM BPM PracitionerAIIM IOA Practioner

2. ECM – What is it?Document MgmtRecords MgmtBusiness Process MgmtDigital Asset MgmtWeb Content MgmtClassificationeDiscoveryFormsCollaborationCaptureand more

3. Where to StartInfrastructure decisions in another trackThe usual role is the “business analyst”The BA has to “analyze the business”Analyze the Business does not equal Gather RequirementsBasic rule “You cannot have a business process without information (content)”

4. Analyze the BusinessDetermine if the business process falls into a well-known patternCase ManagementAuthor / Review / Approve / PublishStraight Thru ProcessingOne and Done

5. Understand the LanguageEach business organization has its own languageSets of words used daily in the businessExample: InsuranceNew BusinessServicingClaimsAgent ContractsAgent Services

6. Transform the LanguageTransform the language of the business into a “taxonomy”Structured vocabulary7 forms of taxonomyFacet taxonomy is a set lists that allow different views of the same information

7. Importance of TaxonomyThe taxonomy:Leads into the technical aspectsBecomes the design of the content databaseDefines how the content is classifiedDefines the “findability” of the content (e.g. search)

8. Impact of business analysis

9. Flow of Content

10. Basic Process ScenariosScopeAd-hocNon-repetitive, typically collaborativeProductionRepetitive process, set rules, often high volumeFunctionalRoutingLinearWorkflowMore complex, parallel activitiesFully-Integrated Business ProcessComplex human and system-centric integrations

11. Business Process AnalysisHave a process for gather informationHave a methodologyConsistentStructuredRepeatableDetermine what information to gatherDevelop requirements of the new processStart with a mock-up of the user interface is possible

12. Business Process AnalysisDetermine the business process patternIdentify the RolesIdentify the flowSequential, parallel stepsIdentify integration points

13. Business Process AnalysisDraw some pictures of the new processKeep it simpleOthers have to understand itCompare the Current State and Target State side-by-sideStart on the Gap AnalysisBuild a prototype as soon as possibleGet the flow correct while working on the details of the UI