skip to main |
skip to sidebar
Extract Transform and Load (ETL) operations can be homogeneous or heterogeneous. Homogeneous operations involve extract from a repository and load into a repository of the same technology. As an example, one can synchronize the content in a North American Documentum repository with the content in a European Documentum repository via a homogeneous extract and load (i.e., from Documentum and to Documentum). Two or more technologies are involved in a heterogeneous operation. As an example, one can migrate from FileNet to Documentum, by extracting from FileNet and loading into Documentum.
The challenge with content consolidation is that there are several, if not numerous, repository technologies to be addressed. For example, if content in SharePoint, FileNet, Lotus Notes, and ApplicationXtender are content sources to be consolidated into a Documentum target infrastructure, then extract must be performed on four different technologies and load into one technology. Each of the technologies involved implies a need for knowledge of the technology, technical infrastructure (e.g., test environment), and existing functionality to connect to each repository technology. A heterogeneous ETL platform capability addresses each of these needs:- Knowledge of each technology is required to inform consolidation strategy from an enterprise taxonomy point of view. Knowing each source technology is required to understand how the content in each source will map to a taxonomy for the enterprise. Knowledge of each source technology is also important for consolidation efficiency. Consolidation efficiency can be improved by best leveraging technical capabilities in the source, such as indexes and application programming interfaces.
- Technical infrastructure (for the several or numerous technologies involved) to test and execute consolidations can be costly and time consuming to establish, but is required for an effective consolidation program. In most consolidation programs, the technical infrastructure is required for a finite period of time, and obtaining required infrastructure via outsourcing is an economically attractive idea. Aside from traditional outsourcing or hosting, large consolidation programs can also leverage infrastructure of solution providers or software vendors.
- Constructing extract connections to each source repository technology is the most technically risky portion of a consolidation effort. Using pre-existing extract connections for the source repositories or proven models for constructing them greatly reduces the risk.
If you are like 69% of companies in a recent Gartner survey (see my April 19, 2009 post), you have more than 6 content repository technologies in use. Crown’s Professional Services and Crown’s Buldoser Center Product represent a heterogeneous ELT platform that reduces the risk and cost of consolidations. Cost and risk are the two main obstacles to consolidation, and with those obstacles addressed, what’s stopping you from consolidating?
Organizations consolidate diverging and rogue infrastructures to reduce cost and improve efficiency. Infrastructure consolidation is increasingly popular among users of software, and Crown enables those consolidations (see “Enabling Consolidation with Universal ETL”). Software vendors also need to undertake consolidations. They need to consolidate products and the installed bases of customers for those products.
An example of vendor consolidation from the automotive industry is Ford’s acquisition of Jaguar. When Ford acquired Jaguar, it maintained the Jaguar brand and distribution channel, but supplied Jaguar manufacturing with many of the same components that were used across other Ford models, especially Taurus. The idea was to keep serving the same customers, but reduce costs by consolidating the manufacturing.
Like the Ford-Jaguar example, software vendors also need to consolidate products. When Oracle acquired Stellent, it planned to consolidate the Stellent product with its own Oracle Content Data Base. When Open Text acquired Ixos and Humingbird, it planned to consolidate those products into its own Livelink product. FatWire acquired OpenMarket product from Divine with the plan to consolidate with its own products.
In the case of software product consolidations, one product of the two consolidated products is typically considered the strategic product. Customers using the non-strategic product will be required to undergo a conversion to adapt their information to fit the design of the strategic product. To keep customer loyalty and sustain maintenance revenues, vendors need to make that conversion as easy as possible.
Crown’s Buldoser technology is commonly used to enable conversions, and can be adapted to perform conversions on a mass scale to convert an installed base of customers. Most recently, Crown has adapted its Buldoser technology to converting the world-wide installed base of EMC’s eRoom customers to EMC’s strategic product, CenterStage. Crown’s technology is the only technology endorsed by EMC for the eRoom to CenterStage conversion. To make the conversion from eRoom to CenterStage as easy as possible, Crown has not only adapted the Buldoser technology, but has also created specialized branding, marketing, product support, professional services and distribution capabilities.
Crown’s hybrid software and professional services capabilities are well suited for migration, archiving, and upgrade of individual businesses. The same hybrid software and professional services capabilities wrapped into an integrated program, are well suited to conversion of a large installed base of customers. While Crown possesses unique capabilities for migration, archiving, upgrade, and installed base conversion, Crown is not resting on its laurels. Crown continues to make investments in software technology, professional services, marketing, and support capabilities to allow fluid consolidations on individual-business or installed-base scales. On behalf of the Crown leadership team, we are eager to assist with your conversion needs, large or small.
