Words of Wisdom from a Seasoned ECM Implementation Engineer Part 2
Post By: George Sarty | Professional Services Manager | Sword CTSpace
I have been developing and implementing software solutions for over 25 years and have spent the last 4 specializing in ECM solutions, primarily for the oil&gas, utilities and engineering/design industries.
In this series of blogs, I will share some of my experiences, tips, tricks, gotchas, etc., most learned the hard way. Hopefully, you will find some of this useful. If it is, or if it isn’t, please feel free to comment, correct or question. I don’t pretend to have all the answers and would also like to learn from others’ experiences.
Blog #2 – Evaluate and select your solution
As discussed in my 1st blog, your implementation is likely to not succeed unless you have a business case and strong commitment and active participation by the stakeholders and business users.
If you have the above, then you should have a good starting point for building your evaluation and selection criteria for a solution.
In general, your requirements/criteria will fall into 4 broad categories:
- Functional
- Platform
- Migration
- Schedule and Cost (acquisition and ongoing support)
Following are some considerations for each:
Functional:
Functional requirements will further breakdown as either base document management capabilities (not unique to your business) and your organization’s specific processes (use cases).
Base document management functions include (but aren’t necessarily limited to):
- Index/import/export
- Check in/check out
- Preview/open/print/render
- Markups, comments
- Copy/send link
- Notifications
- Document numbering, versioning
- Tracking/audit
- Workflow engine
- Collaboration
- Security (ideally integrated with your corporate directory)
Some examples of your organization’s specific processes would be:
- Review and approval workflow
- Bid package assembly, review and transmittal
- Operating manual update procedure
- Contract review
- Project startup
What you will need to determine from your users is any unique features your selected solution would need to have in order to accommodate their use cases. For example, if your process requires a document to be ‘watermarked’ at each stage in its lifecycle, then the solution you select needs to have workflow and/or lifecycle management and the ability to automatically render documents with watermarks.
Developing a complete set of your organization’s requirements will take detailed analysis with each functional area targeted to use the solution. Also insure that you understand which requirements are ‘must haves’ and which ones are of secondary importance.
Platform
First off, understand that this breaks down into two parts:
- The base document management repository e.g. FileNet, OpenText, Documentum
- The application that will provide the interface and processes designed for the business function (e.g. legal, HR, design and construction).
The base DM systems all come with tools that enable you to build these functional capabilities yourself but, in practice, this is time consuming and expensive compared to an ‘off the shelf’ solution
So with regards to both cases, considerations should include:
- Operating systems supported
- Server requirements
- Database requirements
- Storage requirements
- Programming environment (i.e. Java, .NET)
- Web based (browsers supported, active content, etc.) vs. thick client (desktop pre-requisites)
- Security capabilities
Migration
Migration of existing documents into the new system is frequently overlooked or underestimated. First off, determine your migration strategy (which basically mirrors your deployment strategy). There are typically 3 choices:
- Use new solution only going forward i.e. no migration, archive old content
- Migrate all existing content
- Migrate only active content and archive the rest
Essentially the choices are ALL, SOME or NONE. Chances are very good that it will be all or some. In this case, you need to specify your migration needs. Considerations include:
- Where is the existing content? How will it be migrated?
- How is the content structured? Can I infer the documents purpose/properties from the information available (i.e. folder name, document name, etc.)?
- Are there specific properties that I need to maintain during migration? Are there properties I need to map to the new environment? Does the solution provide tools to do this?
- What is the volume of documents? What are the types? Are there relationships between documents that need to be maintained?
Schedule and Cost
These two items are interrelated as cost can affect schedule and vice versa. Costs include:
- Hardware and software acquisition
- Internal labor
- Vendor implementation costs
- Migration costs
- Training
- Maintenance and Support
With regards to schedule, consider the elapsed times and labor time for the following:
- define requirements
- evaluate and select a solution
- negotiate contracts with vendor(s)
- ramp up time for both internal and external resources
- ordering and installing hardware
- define and perform configurations to the software (security, taxonomy, workflows, etc.)
- develop test plans
- user acceptance testing
- training
- migration
- go live activities
To summarize: the more complete and accurate all of the information gathered and documented during this process, the better chance you have of getting the best solution for your organization. All of the above should be detailed in your RFI to potential vendors and discussed with them during the evaluation process. The earlier everyone sets realistic expectations as to effort, schedule and cost, the smoother the implementation will be for everyone.
George Sarty is the Professional Services lead/senior implementation manager for Sword CTSpace. George has over 25 years of experience designing and implementing complex software solutions for a variety of industries. Prior to joining Sword, George spent a number of years with Microsoft Corporation working with customers such as Dell, Conoco Phillips, Shell and ExxonMobil.

