Putting Together an ECM Project Team

Part 3 – The Project Team

In previous blogs on this same subject, we have discussed the role of Executive Management in the overall Project Team effort.  And what elements from the  internal organization would likely comprise an effective team.   In summary, vibrant and effective executive leadership is likely to be critical in solidifying the vision for the project.  The target of effort to achieve project acceptance and enthusiasm is cascading in that the focus of executive leadership is middle management.  The components of a project team may be different for each organization or type of organization – whatever best suites the particular organizational structure, and what special considerations there might be in the project (i.e. does it involve web content, collaboration, integration with ERP or SharePoint environments, etc.).

The Role of Line of Business Managers in the Project Team

As your project will likely either be addressing a limited requirement of a single department or two, or will be the start of an enterprise wide implementation of ECM, it is always recommended that it focus on a manageable quantity of work – normally one or two Departmental or workgroup solutions.  Enterprise wide ECM, ERM, and Business Process Management implementations usually start with one or two departments.   The Department(s) chosen for the Project are normally those where enthusiasm for improvements is high, cooperation is supportive, and where the business entity will benefit highly from the application of ECM technologies.

Starting with one or two areas that have been carefully selected based on their high potential for success and strong need for improvement, permits the rapid and clear demonstration of  ECM technology benefits – and that strong example can assist in the acceptance of the larger project to come across the enterprise.

Departmental management and supervisory involvement and strong support is crucial.  The organization’s line-of-business (LOB) managers understand the routine and cyclical “problems and challenges” of business operations.  They are operational experts within their areas of responsbilbity, know the character of the staff resources they have to work with, entity strengths and weaknesses, the potential to accept change, and what “change management” efforts should be implemented.   These LOB Managers and supervisors routinely “concentrate on organizational effectiveness through current processes” they will become the bridges that will carry the success of the ECM project forward into routine of daily work production.

The LOB Managers and other key supervisory or lead personnel need to be considered for the Project Team for either full involvement, or participation in the development of specific new process or workflow designs.

• They are most cognizent of what is done in their departments and why, what documents are received and how they are processed, the various sources of data (paper from internal and mail sources, voice mails, emails, internet provided input, etc.).
• They understand the decision criteria in the flow of work, the point where specific processes are needed, risks to successful processing, exception processing, and all the rest of the challenges that will need to be considered in a process design.
• They also know which other business areas need access to their documents and data.
• They usually have the only available insight into key details regarding operational systems, processes, and policies that support their organization’s mission.

When you apply ECM and BPM technology to an organization’s routine processes, you must have input and significant levels of planning participation from the managers and key personnel who are most familiar with operations so they can ensure that the new system will be successful in meeting objectives at all meaningful levels.  These people are needed to allow the project team to reach all objectives through consistent operational production.

From time to time this blog will continue with the subject of project team challenges, some considerations to remember, use of supporting vendor resources, and some recommended methods for implementation.

Neil W. Lindsey, ECMm, CDIA+

Project Manager / Senior Business Analyst
ImageSource, Inc.

Considerations for Architecture and Deployment of Global Capture Systems

 

The considerations for architecture and deployment of global capture systems are several fold. In our experience they include the traditional considerations and methodologies (software deployment models, conventional server models, fault tolerance considerations, human resource considerations, change management, etc.), however, in the global context there is another set of considerations that must be factored into the decision making processes. Regardless of the quality or nature of the software, there are myriad factors (independent of the software application) within any global corporation that can and will affect how that software is implemented and how it performs in any given region of the world. The ability to implement quickly and efficiently is tied directly to the organization’s communication structure, reporting structure, internal politics, policies and procedures, physical infrastructure, and the relationships that exist between the various IT support groups and the business. Any distributed applications performance can be impacted by the network, security configurations, load balancing systems, WAN Acceleration systems, and all of the rest of the traffic traversing those global backbone and regional networks. Many of these factors can and often are completely beyond the control of the customer’s project teams, and those that do control them often have completely different reporting structures within the organization.

Having a clear handle on the state and configuration of the existing environment combined with well managed Command and Change Control structure and a central hierarchy of authority that can be used for escalations is vital to the ability of ground teams to implement, troubleshoot, correct, adjust, optimize and complete rollouts in a predictable, consistent and timely manner.

Most of these factors are never fully known or understood until the teams are well into the planning stage of a given project. There are several ways that any global rollout can be approached from our perspective. Our preference is to work closely with your teams to understand the traditional factors as well as the lesser known and intangible ones so that together, we can arrive at the most effective, efficient and reliable ways to implement for each given region of the world. In our experience we have also found that being flexible as a combined team in our approach can help to ensure successful outcomes at the end of the day. We have to plan based on the information available at the time. As new information becomes available, we work together as necessary to modify the plan to achieve our stated goals and objectives for the implementation and to satisfy the needs of the users. At the end of the day, from a users perspective, it just has to work.

Gene Eckhart

Program Manager

ImageSource, Inc.

  

PUTTING TOGETHER AN ECM PROJECT TEAM

Part 2 – The Project Team

I discussed in the last blog on this general topic that the strong support of the intended Project by executive management is a critical factor for success – they need to support the projects sponsor, and smooth the path of challenges that sometimes occur when change is contemplated.  Vibrant and effective executive leadership is likely to be critical in solidifying the vision for the project.  The target of effort to achieve project acceptance and enthusiasm is cascading in that the focus of executive leadership is middle management, and then it effort fans out to focus on users and supervisors. 

What Will be the Right Team
The right team of players, working together to hone the vision, is required to construct the concepts to be considered, refine the concepts, and to develop strategies to support the selected conceptual structure to fruition.  The people on the team are as integral to your project’s success as the solution, the project plan, the software tools, and infrastructure that is chosen.

Forming the right team is not easy – as not all leaders and users welcome new ideas and changes to the routine process.  But the executive support and the right team members are just as important for for standard ECM projects success as these factors are vital for business process management (BPM) and integrated implementations.

The primary key role types that are required on any ECM project team are listed below.  The exact position titles and numbers of team members recommended for participation will differ depending on an organization’s size and individuals’ skill levels. It is important that the eight classifications of people resources below are part of the Project team.

1. Executives: provide the supporting vision and enthusiasm for the solution objective

2. Line-of-Business (LOB) Managers: provide important project support and key higher level objectives

3. Business Analyst: provide discovery and analytical resources, reporting, perspective and ideas

4. Records/Compliance Manager: assure objectives and solutions match mandates and requirements

5. IT/IS Manager: supporting infrastructure, including business & IT challenges into the plan

6. WorkGroup Manager/Supervisor staff:  provide working knowledge of operations being addressed and realistic possibilities on what will work and where the challenges will be

7. End users: discovering what will and won’t work and where the challenges for acceptance are

8. Project Manager:  This person is the organization’s operational leader of the project and the coordinator with outside resources – ECM industry experts, software vendors, conversion resources, Training, etc. 

From time to time this blog will continue with the subject of team challenges, some considerations to remember, use of supporting vendor resources, and some recommended methods for implementation.

Neil W. Lindsey, ECM^M, CDIA+
Project Manager / Senior Business Analyst
ImageSource, Inc.

ECM Best Practices – Green Support

Enterprise Content Management Solutions
– Remote and Mobile Employees

Many of today’s business discussions revolve around the fact that providing select employees with the ability to work from home, in a mobile environment, or otherwise more independently, is a positive factor towards fostering conservation and a “GREEN” initiative.  Considering the integrated component benefits of a well conceived and implemented Enterprise Content Management System (ECM), with the right employees selected for a remote work environment, this green initiative can also promote a highly efficient and productive business environment.

Employees that successfully work from home or on the road as much as they do in the office are likely characterized by desirable core competencies.  This is nothing new and these strong employee qualities have always been required of the person working independently from constant co-worker and management relationships and support. 

Successful remote employees are oriented towards achieving results, and as such, as a group they can be described as being self-motivated, self-disciplined, and as self-sufficient as their supporting infrastructure will allow them to be.   “Remote” employees very often maintain a strong client focus and spend a lot of time working at client sites, communicating with clients, and seeking new clients. 

In order to give the successful remote employee the best opportunity to be as productive as they can be, and promote an organization’s green initiative,  that organization can develop the information management and communications infrastructure that fosters collaboration and information self service.  This also prepares an organization to address the current business trend towards more remote employees.  This developed business structure can also support instances where employees are able to work, but have to do that work away from the office due to illness, convalescence, family emergency, transportation problems, etc.

In addition to the infrastructure, it is important to implement a training program so that these resources are known to the remote employees and they are well trained in making the most of them.

The following are among those driving guidelines that support effective mobile and remote employees:

• Digital information and content are increasingly pervasive and require well developed broadband technologies and services.  Remote employees must be provided with required independent information access and research needed for commercial, client, and business awareness.  ECM Benefits contributing towards a green initiative and remote employee support include:
  • ECM – Customer and business information access through web based document and image management
  • ECM – Research and document re-purposing through web based document management
  • ECM – Work and transaction processing continuation through web based workflow processing
• Group and teamwork oriented communications channels are instrumental to effective and collaboration between the remote employee, clients, co-workers, and management, and to providing effective remote presentation resources.  Integration of Collaboration Management and web based meeting services with compatible ECM systems provides a productive team environment contributing to a focused energy and natural resource conservation effort.
• Businesses (and individuals) must effectively communicate on the move and be supported by personal mobile communication technology and web services.  Personal mobile devices now provide a technology that not only communicates between people, but also communicates information to people using compatible web based Enterprise Content Management systems.
• Data submission and resolution tool resources allowing for information communication and independent problem solving must be provided to the remote employee dependent upon business type and objectives.  Digital Forms Processing and Management systems, a major component of many ECM systems, can provide effective solutions.

Neil W. Lindsey
Project Manager / Senior Business Analyst
ImageSource, Inc.

Attend the following GREEN oriented sessions at
NEXUS 2009, November 2nd, 3rd, 2009, Bellevue,
Washington

Finding the PR Value in your Green ECM Technology
Reducing Your Organization’s Cost and Carbon
Footprint Through Inter-Office Scanning
Economical & Environmental Benefits of eForms

Basics of Consulting for the ECM Project

Many organizations look for expert assistance in a quest to justify, plan, and develop the concepts for an Enterprise Content Management system (ECM) or smaller departmental system using this technology.  A provider of these services needs to have demonstrated expertise regarding consulting services focused on the application of the entire breadth of the disciplines associated with Enterprise Content Management.  General business process or management consultants seldom have the experience necessary to provide the requisite resources.  The solutions addressed by the consultation project need to focus each client’s objectives and how they may have to be addressed by the professional application of a combination of:

• Document Management
• Document Imaging / Image Management
• Digital and Physical Records Management
• Digital Asset Management
• Business Process Management and Workflow
• Reports Management (ERM / COLD)
• Content Addressable Storage
• eForms Design, Library management & business processes
• Legacy system and database integration for data sharing (i.e. SAP, Oracle, PeopleSoft)
• Legacy system integration for image enablement of third party applications
• Digital signatures and data encryption
• Large Document Viewing Enhancements
• Data capture technologies & custom document and data capture management
• OCR/ICR/OMR & bar code reading
• Data capture from Digital forms and Web forms
• Web Publishing & Content Management
• Web based information delivery systems
• Network Fax Systems and capture
• Collaborative Portals and resources
• File conversion, document migration, and scanning services
• Application Development and Programming Services for Custom Requirements

Consultants need to be able to actively provide expert participation and guidance in analysis to determine requirements/objectives, develop and validate goals and expectations, and apply capabilities of technology for application concepts, business processes, and design at the workgroup, departmental, and enterprise requirement levels per objectives. 

Consultants need to provide resources to advise and direct on project aspects such as technical design specification for hardware, ECM software platforms and components, the network infrastructure, conversion and migration of document information, the training program and facilities to be utilized. 

A consultant’s roll can consider numerous other ECM specific factors such as performance standards, operational and functional objectives, ROI analysis, Change Management considerations, and others which frequently need to be addressed, researched, analyzed, documented, and presented to the client when . 

ECM Consulting Services should also be able to address and provide guidance on the following when generating documentation to the client in the form of a Consultant Report, a Project Charter, and/or a subsequent full Project Plan with design detail:

• Current process documents and flows of work
• Project Scope Planning, Definition, and Management
• Definitions – Process Re-engineering to Technical Opportunities
• Project Deliverables Definition
• Work Breakdown Structure (WBS) at the Project Plan level
• Conversion and Migration Services Requirements – Deliverables
• Standard and Advanced Training Curriculum Planning and Management
• Quality Control Strategies and Planning
• Project Cost Estimating Costing

Application Design for Project Standard Deliverables as well as Architecture Engineering Analysis and recommendations.  These can include conceptual to detailed Design for standard and custom system components and design details for:

• system configuration, and all standard software modules
• document/image capture including information capture considerations for workflows and business processes
• planning, design, and development for web-based resources
• interfaces and integrations with legacy systems as required by objectives
• Activity Definition, Sequencing, and Predication Planning
• Risk Identification and Management Planning
• Duration Estimation with Project Schedule Development and Control (Microsoft Project) when developing Project Plan level strategies plans.
• Project Team Development and Management with Resource Planning
• Communications, Information Distribution, and Performance Report Planning

The consulting organization may bring multiple experts to guide and participate with the client in the discovery and analysis process. Consultants, no matter what their expertise in a particular vertical application, should remain open to a client’s specific goals and interests and not automatically apply past experiences to the specifics of what solution a new client will need.  There should be an initial concentration on specifically defining business challenges, phased implementation priorities, and evaluations of the best opportunities for initial success. This process leads to business solutions that integrate with a client’s standing technology investment and unique business culture, and result in real returns if managed professionally.

Find out more about ECM Strategies and Project Planning at NEXUS 2009

Neil W. Lindsey, Project Manager
ImageSource, Inc.
www.imagesourceinc.com

What Type of Search is Right for You?

For many functions in the organization the full text “Google” like search capability found in most document management systems may be useful.  For others, it’s not sufficient in providing the business value.  Here’s some situations that may help determine what is right for you.

A business professor once said “There are three core functions to any process… 1. Procurement of Materials 2. Conversion of Materials and 3. Distribution of those Materials.  All other functions only support these three”.  In translation, these three things can map to any function found in business for any department (Sales, HR, Information Technology etc.)  It seems that when analyzing any business process, this old adage always comes back and discussing search in the enterprise is no exception.

When looking at search it’s helpful to see both sides of these functions for document management.  Documents either “drive the process” as a core function, or documents are ”driven by the process” as in a supporting role.  The differences are not all that hard to see.  Document that drive the process are directly related to the three functions above 1. Procurement 2. Conversion and 3. Distribution.  Documents that are driven by the process may be everything else.

Vouchers, Invoices and Checks are all documents that drive Purchasing.  Service Orders and Proof of Delivery are documents that drive Operations.  Purchase Orders and Service Contracts drive sales. 

On the other side, Marketing Literature  is driven by Marketing.  Brochures are driven by Sales.  The company Calendar is driven by HR and Inventory Reports are driven by Operations.  These documents support the functions of their departments.

A less technical way to look at this dichotomy is ”gotta have that document now” and “gee, this looks like what I’m looking for”.  When designing a search architecture, this is one of the basic questions you can ask yourself.

Documents that drive the business process tend to require a discrete index field search.  This is because the user is typically looking for the one document they need, and they need it quick.  A Sales Order for a customer service representative or an Invoice for a purchasing manager.  These documents also typically already have a structured meta-data component already designed for them before the document management system is in place.  A Sales Order Number field is always generated for Sales Orders and an Invoice Number Field always has an Invoice number.  This is true before or after a document management system exists.

Documents that are driven by the process are less structured in nature.  Marketing Literature, Progress Reports and the Employee Vacation schedule to name a few.  The user is typically looking for some information that could be in one, or many of these documents.  Could an employee figure out if Memorial Day is a company holiday by finding the wrong documents to their search?  Like last years vacation schedule?  Probably so.  If this is the case, a full text content search may prove successful.

Documents that “drive the process” answer questions to a search that only that one document can satisfy.  What items were billed for Invoice # 123456?  What date was Employee #78910 hired?  Who signed for Proof of Delivery #34567?  In these cases, a discrete index field search is required.

 

John Moffitt

Systems Engineer

ImageSource, Inc.

http://www.nexusecm.com/index.htm

www.imagesourceinc.com

www.ilinxcapture.com