Enterprises have been struggling for years to leverage all the information on business processes they have stored away in order to conduct business better. The problem is much of this information is created in unstructured documents, such as spreadsheets and word processing documents, rather than in a database, making it difficult to control and manage.
Several vendors offer enterprise content management (ECM) solutions to deal with unstructured documents, but different vendors’ solutions do not talk to each other. Businesses store their unstructured documents in multiple repositories from different vendors, so they have to spend a great deal of time and money to integrate these repositories so they can communicate with one another.
A potential solution, the Content Management Interoperability Services (CMIS) specification, was announced today by tech heavyweights Microsoft (NASDAQ: MSFT), IBM (NYSE: IBM) and EMC (NYSE: EMC).
“When companies operate in silos, with information scattered throughout the enterprise, it becomes extremely difficult for customers to realize [the information’s] full value,” Jeff Teper, corporate vice president of Microsoft’s office business platform in the vendor’s Office SharePoint Server Group said. “By working together, we believe we can enable customers to maximize the use of critical business assets.”
CMIS will use Web services and Web 2.0 interfaces to let applications in an enterprise work with multiple ECM repositories from different vendors without as much integration work as is now needed. Currently, every link between systems need a connector, and Microsoft’s ECM team blog says this is a problem because each link requires a different connection and connections tend to be specialized.
The specification will also promises to help businesses as they struggle with compliance.
“If you have any form of legal discovery need, or want to implement a policy across your organization that says all contracts must be kept for, say, exactly five years, then having a single archive to store content for longer than the application that created it is quite useful,” Richard Anstey, vice president, technology and product strategy for ECM Suite at content management vendor Open Text, (NASDAQ: OTEX) told InternetNews.com.
Going through the standards process
CMIS was submitted today to OASIS for acceptance as a standard. OASIS, the Organization for the Advancement of Structured Information Standards, is a not-for-profit consortium driving the development, convergence and adoption of open standards for the global information society. The standards process will take some time, Anstey said.
The vendors “intend to form a new OASIS Technical Committee and contribute the CMIS specification,” OASIS director of communications Carol Geyer said in an e-mailed response to a query. “We look forward to that happening and we applaud their goal of bringing CMIS into the open standards process.”
IBM, Microsoft and EMC have been working on CMIS since 2006, and were joined by other vendors, including Alfresco Software, Open Text, Oracle (NASDAQ: ORCL) and SAP (NYSE: SAP). All seven worked to ensure CMIS made their solutions interoperable.
“There’s what’s elegantly named a plug fest, where all the vendors get together and see if all their solutions work with each other,” Anstey said, adding that this “has been going on for a year.”
CMIS will let enterprises manage their content separately from the repositories instead of having a management policy for each repository as they do now, because it decouples Web services and content from the content management repository. Better yet, it lets enterprises serve up content as a service in a service-oriented architecture (SOA)
“We believe records management should be a service that works with other applications that don’t necessarily have to manage the records themselves,” Open Text’s Anstey explained. “You want a single place for the policy for how long you keep your records and, if you can expose the records and archives and functionality as a service to be consumed by multiple applications within the enterprise, you’re doing yourself a great service.”
CMIS will let independent software vendors create specialized applications that can run over various ECM systems. It provides common Web services and Web 2.0 interfaces to simplify application development. Anstey said CMIS will be REST-based and have a SOAP-based Web services application programming interface (API).
Next Page: Prototype using CMIS debuts
Page 2 of 2
Prototype using CMIS debuts
REST
CMIS is development platform- and language-agnostic, and supports composite application development and mash-ups by business or IT analysts.
The first prototype using CMIS is already out — Open Text this week announced that it has worked with SAP to create a prototype that uses CMIS to manage content from SAP applications with Open Text Enterprise Library Services. “We wanted to work alongside SAP to create a standard way to ingest content from the SAP solution to keep it for the long term,” Open Text’s Anstey said.
There are reports that CMIS will be applied to Microsoft SharePoint Server 2007, which Microsoft has been touting as its ECM solution. A Microsoft spokesperson would only say by e-mail that “because we are just beginning the process to standardize the CMIS specification, we have nothing to announce today regarding how it will be used with specific Microsoft products.”
However, Ethan Gur-esh, program manager for Microsoft’s CMIS team, said on the ECM team blog that “we’ll provide more information on when and how you’ll see support for CMIS for SharePoint and other Microsoft products.”