Build vs. Buy

Over the course of my last 12 years in the Enterprise Content Management space, I have seen many progressions and changes.  When the industry was in its infancy stages, we relied on specialized PCI cards to drive the scanners at rated speeds, high resolution graphics cards to display clear images on a monitor, and every system installation needed holy water sprinkled on it to ensure that there weren’t any compatibility issues or conflicts with the operating system.  There were hundreds of software vendors that claimed to be the premier document imaging / document management / scanning / (whatever new term that AIIM came out with) system.  Systems were sold, installed, and many failed.  We have seen progressions where the hundreds of vendors have consolidated to a few leaders that are recognized as true ECM platforms.  We have seen Microsoft enter the market with SharePoint which has driven the need for a new wave of products and services to bridge the gaps in its functionality.  Along with these progressions and changes with the vendors, we have also seen how internal IT departments look at ECM.

In the beginning, there was many components, many moving parts, and technology that the IT staff wasn’t readily familiar with.  As the first and second generation systems were installed, the product sets matured where the IT staff technology professionals could be trained in a platform that was sustainable.  As this progressed software vendors could switch their focus from making the systems work in a rudimentary sense, and switch the focus to the development of features and functionality that led credence to aspects such as compliance, accountability, governance, and security.  The successful Tier 1 vendors (see Gartner report for leaders) now have scalable products that address all aspects of ECM – document imaging / document management / web content management / forms management / records management / workflow – Business Process Management.  With this, training is now readily available to equip any IT staff with the tools and resources to maintain and build upon systems where compliance, accountability, governance, and security are all part of the core.  Knowledge and education are now key determinants for success.

With this knowledge and education comes empowerment to the IT staff.  In the industry today, I am seeing an increasing number of corporate IT staffs choosing to forego their existing systems and internally build components that allow them to store, retrieve, maintain, and manage scanned images and data.   I understand that there are many talented programmers and systems architects in the workplace that are capable of building database management functionality and that can build user interfaces that allow for searching file structures.  What I don’t totally understand is the value to organizations when a top resource is consumed in developing a product / system and maintaining and supporting the product / system.  It has taken Oracle Stellent, IBM FileNET, EMC Documentum, OpenText (to name a few) each over 15 years to come up with a product offering that is stable and that meets 85% of most organization needs without customization.  Why reinvent the wheel when there are cost effective, proven solutions that can automate business processes that will show efficiencies and pay for themselves over time?  There are many technology focused companies that have invested multi-millions of dollars, and many years  in developing methodology and products.   I don’t know how an organization that is focused on their specific expertise – retail, manufacturing, healthcare, banking, can morph into a software development / systems delivery organization.

Build vs. Buy – no correct answer, but definitely worth discussing.

Feedback welcome.

Jeff Blissett
Senior Account Executive
ImageSource, Inc.
www.imagesourceinc.com

Share on Twitter

One thought on “Build vs. Buy

  1. Jeff makes some very good points. Additionally, the “Build” method, in order to be successful, requires that the organization doing the building have a method of documenting the system.

    Too often, these systems are built to meet a need, but the documentation is lacking. If the system needs to be expanded, upgraded, or modified, there is no way to reliably do so.

    Documenting a system and maintaining that documentation adds another layer of cost to the home built solution.

    Kathleen Fish
    Senior Account Executive
    ImageSource, Inc.
    http://www.imagesourceinc.com

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s