Guide to Enterprise Content Management & Collaboration
Oceans of unmanaged content are swamping companies. It's time to rethink ECM and collaboration to keep your head above water
December 16, 2008
By Andrew Conry-Murray, InformationWeek, December 15, 2008 11:00 AM
Larry Hawkins has a problem. Actually, he has several million. The company he works for, First Energy, generates 2 million e-mails a week. Then there are untold Word documents, spreadsheets, CAD files, videos, and other pieces of content flooding the company.
"We are great at creating information, but really bad at deleting low-value information," says Hawkins, First Energy's director of records and information compliance. "The more stuff laying around out there represents a risk to the company."
It may be cold comfort, but Hawkins isn't alone. At companies everywhere, e-mail, collaboration tools, and Office applications generate a rising tide of unstructured business content. It's not enough to simply soak it up with additional storage. Compliance and e-discovery requirements demand more discrimination, identifying which information should be retained and which can safely be destroyed. At the same time, companies must make sure employees and other users can access the content they need to conduct daily business.
Companies have two choices: manage this business content, or drown in it.The choice may require some radical rethinking about enterprise content management systems. Companies have been using ECM products to handle official business records--such as contracts, invoices, medical records, and financial statements--for years. And the policies, processes, and technologies to manage these types of records are well understood and widely implemented. That's not the case for the larger class of unstructured content, which tends to live outside the bounds of an ECM platform. ECM vendors are trying to expand the boundaries of their products to serve as general-purpose information governance systems. In addition to being the big bucket for companies' unstructured content, they're trying to provide a management layer that applies policies to content even if it doesn't sit in the vendor's repositories.
Read the whole story at InformationWeek
You May Also Like