10 steps. to implement a EDMS



Similar documents
White Paper Microsoft SharePoint for Engineering Document Management and Control

SharePoint for Engineering Document Management & Control

UltimaX EDM for Microsoft Dynamics AX TM

Diagram. Microsoft Dynamics Sure Step Methodology

SEVEN WAYS THAT BUSINESS PROCESS MANAGEMENT CAN IMPROVE YOUR ERP IMPLEMENTATION SPECIAL REPORT SERIES ERP IN 2014 AND BEYOND

SMART GOAL SETTING WORKSHEET With Guidance Notes

Change Management: Adopt and Implement Grant Management Software

Seven Critical Steps to a Successful CRM Solution

AgFirst Farm Credit Bank

Welcome to online seminar on. Agile PLM Overview. Presented by: Mahender Bist Partner Rapidflow Apps Inc

Integrating Microsoft Dynamics GP and Microsoft Dynamics CRM. Discussion Paper and FAQ s

The Buying Process as a. Sales Enablement Framework

Your 12 step plan to a successful SharePoint implementation. SharePoint Project Checklist

C O N S U L T C O N N E C T - C H A N G E. Does CRM Really Work?

Training Programs for Enterprise-Wide Change

Project Management Fact Sheet:

04 Executive Summary. 08 What is a BI Strategy. 10 BI Strategy Overview. 24 Getting Started. 28 How SAP Can Help. 33 More Information

KMS Implementation Roadmap

Microsoft SQL Server Master Data Services Roadmap

Change Analytics. What is the business change that arises from IT and application projects really all about and how to manage it efficiently?

Document Management Software Rollout Plan

Defining change management

GUIDELINES FOR DEVELOPING A SHAREPOINT REQUEST FOR PROPOSAL. by Jill Schubmehl, Evan Callender, and Chris Stafford

Project Implementation Process (PIP)

Envisia Learning 360 Feedback Online Project Flow Process

INTRODUCTION PRODUCT PRIORITIES INTEGRATION

>> BEYOND OUR CONTROL? KINGSLEY WHITE PAPER

Kenandy TM Cloud ERP White Paper. Kenandy Cloud ERP Overview

SharePoint Project Management: The Key to Successful User Adoption

WHITE PAPER. The 7 Deadly Sins of. Dashboard Design

Project Management Software Buyer s Guide: What You Need To Know Before Evaluating

Regulated Documents. A concept solution for SharePoint that enables FDA 21CFR part 11 compliance when working with digital documents

Enterprise Data Governance

What is BPM? Software tools enabling BPM

Project Management Software Systems

Build products with visual solution configuration in an integrated quotation management application.

DITA Adoption Process: Roles, Responsibilities, and Skills

SOS Publishing FAQ s

WHITE PAPER DEVELOPING A SUCCESSFUL WEBSITE RFP. Find the Right Web Development Partner through an Engaging and Informative RFP.

ZL UNIFIED ARCHIVE A Project Manager s Guide to E-Discovery. ZL TECHNOLOGIES White Paper

What s New in Sage 100 ERP

10 Steps Process to your LMS

File Folders. To produce a file folder you have the following options:

New Nintex Workflow 2010 Business Value: Actions and Functions

EVERYTHING YOU NEED FOR BRANDING ON MULTIPLE CHANNELS

SAP Integration and Certification Center

Defining the Relationship between Product Life Cycle and Project Life Cycle

2. Please describe the project s alignment with the Common System Principles (Appendix 1).

A Human Resource Capacity Tool for First Nations // planning for treaty

Using SolidWorks Enterprise PDM For ECO Management... 1

Change Management Approach

Work Process Management

Data Migration for Legacy System Retirement

Business Intelligence Town Hall

How to Run a Successful Big Data POC in 6 Weeks

10 TIPS TO A MORE EFFECTIVE PERFORMANCE/BEHAVIOR REVIEW PROCESS

E-COMMERCE OPERATIONAL RISK MANAGEMENT PLAN

Matrox Imaging White Paper

Business Intelligence. A Presentation of the Current Lead Solutions and a Comparative Analysis of the Main Providers

MODULE 7: TECHNOLOGY OVERVIEW. Module Overview. Objectives

A Brief Guide to Executive Onboarding

Project Management Office: Seeing the Whole Picture

Developing Policies, Protocols and Procedures using Kotter s 8 step Change Management Model

Invensys-Skelta Takes BPM to Operations. customers and the Invensys challenge is to Invensys manufacturing customers.

SharePoint Project Management: The Key to Successful User Adoption

Implementation of Concur as Travel and Expense Solution at York U. OUCC, Monday April 28, 10:30 AM

Web Team Roles & Responsibilities. This document defines the approved Roles & Responsibilities for the Web Team and related Job Descriptions.

Recruitment and Selection

Contract and Vendor Management Guide

Implementing a Project Portfolio Management (PPM) Solution. Sean Hansen, PMP

Stuart McPhee s Trading Plan Template

5REASONS WHY YOU NEED A CRM

SMART CRM Desk for Service Sector. Solution for Customer Relationship Mgmt (CRM) in Service Industry

and 2010: rprise Increasingly, must ation, es, partners, s intelligence.

Digital Asset Management (DAM):

Business Intelligence

Test Automation. Full service delivery for faster testing at optimum cost

Transcription:

10 steps to implement a EDMS

Introduction In today s business processes, information plays a key role. Information is used to steer business processes and to provide people the information and instructions to do their job. Most of our information is kept in documents and it is very important that documents are well managed and that they are available to the right people at the right time. A Document Management System is therefore crucial to steer business processes and to ensure that people have access to the right information; whenever they want and wherever they are. Since Document Management Systems are closely related to business processes, a Document Management System should not be implemented overnight. An organization needs to be well prepared and needs to understand their requirements, scope and objectives to successfully implement a Document Management Solution. This white paper describes 10 steps to a successful implementation of a (Electronic) Document Management System. 01 Assign a project champion To implement a successful project, it needs to be supported by the full organization. The best way to manage this is to assign a project champion that knows your organization, understands your business processes and is capable of getting and keeping the various people and disciplines on board. Your project champion will be the engine for your project and will see to it that your project keeps momentum. 02 Get management support Next to having a project champion, it is very important to have your management supporting the project. An EDMS implementation is directly related to the business and involves many of your disciplines. As a result, people and disciplines need to team up, which requires the support of your (senior) management. 03 Prepare yourself A successful project starts with proper preparations. You need to well understand what you are up to and what you want to achieve. It is important to properly define your scope, objectives and time frame. Define the success of your project and create a business case that secures your budget an determines your potential cost savings. LogicalDOC 10 steps to implement a EDMS Page02

Take a step by step approach 04 Many implementations have failed or largely exceeded budget because companies wanted to do too much too soon. Document management is related to your business processes, so you need to fully understand the impact of an EDMS implementation on your business and organization. Business processes can be complex and it is possible that users respond different to a document management implementation than expected. Therefore it is best to take a step by step approach. By defining small steps with clear milestones, you are better able to oversee what you are doing, are able to control and manage the process, and give users time to adjust to the new situation. Furthermore you can easily evaluate each step and make any adjustments needed without the risk of a big setback. With a step by step approach you manage and control your implementation process and achieve the right results. It is more important to properly evaluate all functionality, than to evaluate all functionality at once! Define your requirements 05 Draw up your blue print To implement a system that really supports your business and users, you need to understand your requirements. Therefore you need to analyze your documents and document processes and you need to talk to various users from various disciplines to understand how they work with documents and how documents steer their tasks. It is best to start at a business level by describing your requirements from a business perspective, without being influenced by technical (im)possibilities. As a next step, describe your functional and detailed requirements and specifications. Together, your business and functional requirements form the blue print for your EDMS. Some of the topics you should describe in your requirements are: LogicalDOC 10 steps to implement a EDMS Your document processes: Document creation; Document approval & review; Document revision; Reference file management; Document distribution; Your documents (quantity, internal, external, etc.); Your document types (Office, Pdf, Email); Your document (and project) structure; Your document properties (metadata); Your users and groups, including roles and rights. Continued page 06... Page 03

05 continued To better clarify your business and document processes, it can be very useful to create process flowcharts. Since most people are visually oriented, a process flowchart can be very illustrative. Work from a best practice If you are unable or having difficulties to draw up your blue print, a good alternative is to work from a best practice example that reflects how similar companies have setup their engineering document management environment. You can use a best practice to learn from it and either adopt it or further adjust it to your needs. Many organizations have benefit from best practices, helping them to (better) understand their own requirements and to have a quick start in their implementation. Start a pilot 06 It is highly recommended to start with a pilot project or Proof of Concept (POC). The advantage is that you gain experience, understand the impact of a document management implementation, and better understand your requirements. Furthermore you can better evaluate your first steps and make any adjustments needed. A pilot project should comprise only a defined part of your company and business, for instance a defined project or department. Do not include too many users, documents, document types, document flows, etc. at once, but focus on a defined pilot environment that you can easily manage and that will give you the right feedback and results to define your next step. Evaluate your pilot 07 A good evaluation of your pilot is critical to continue a successful implementation. It is very rare that companies are able to draw up their blue print first time right. Hardly anyone can oversee all aspects of a document management implementation up front, and therefore it is important to take small steps, evaluate each step and make any adjustment needed. Don t panic if the first results of a pilot are disappointing. You will probably learn more from a pilot than you first expected. Do a proper evaluation with the users, your project team and your vendor or implementation partner, and see what needs to be done to come to the right configuration and implementation that supports your document management needs and business processes. After a successful pilot project, your requirements are clear and you are able to define and create templates to support the further rollout of your EDMS to your organization. LogicalDOC 10 steps to implement a EDMS Page 04

08 Scale up After a successful first step you can scale up. You can scale up to more users more departments, more projects, more documents or document types, etc. How to scale up depends on your specific situation and the best way to do a step by step rollout in your organization. When scaling up, continue to take small steps to ensure a successful rollout. 09 Provide training and support User acceptance is critical for a successful implementation! Make sure you provide proper training for your users. Train your users in a production environment that reflects a real life situation, so your users immediately experience the advantages and benefits of the solution. Base your training on real data and documents that have meaning to your users. When users are able to immediately work with real documents and data, they will easier accept the system. Prepare your organization for possible changes. The introduction of an EDMS could introduce changes in working methods, or you might want to take the opportunity to make changes to existing working methods yourself. Focus on the benefits of a changed working method, so that your users will support it and not fight it. Make sure that your users have no reason not to work with the new EDMS, for instance because they can continue to work with the old system. Also make sure that your users are properly supported in working with the new system and that they get quick and proper answers to any questions they might have. 10 Foundation first, integrations next Document management supports your primary business processes, and data and documents in your EDMS are often related to data in other management systems (e.g. ERP, PDM, CRM, etc.). Before starting to integrate your EDMS with other systems, make sure your foundation stands. To build a skyscraper, you first need to build a solid foundation! So make sure that you have a solid document management foundation, before looking into (complex) integration with other systems. LogicalDOC 10 steps to implement a EDMS Page 05

About LogicalDOC LogicalDOC is the best choice among all document management solutions. Its intuitive interface makes it easy to use and requires no training. The combination of advanced technologies and widely accepted international standards facilitates a non-invasive integration within your environment. With LogicalDOC you will definitely solve all your document management needs. For more informations about LogicalDOC, visit us at http://www.logicaldoc.com LogicalDOC 10 steps to implement a EDMS Page 06