The continuously growing number of contracts and their precise handling is a constant challenge to many organizations. Therefore, fme developed an OpenText Documentum D2 based Contract Management Framework. With this framework, clients can efficiently manage their contracts and ensure that they are accurately recorded and audited to meet compliance guidelines. But what’s behind all this? Let’s take a closer look!
OpenText Documentum D2 – a solid backbone
The OpenText D2 background provides a configurable and adaptable basis with which the contract management solution can easily be adapted to customer needs.
Main functions of the fme D2 Contract Management Framework
The solution contains all basic settings for the setup of contract management documents and processes: a set of document types with attributes, lifecycles and workflows, permission control and search and reporting functionality.
Additionally it contains a specific clause library functionally to compose contracts of already reviewed and internally approved text blocks, which are organized as part documents and serve as contract template parts. This reduces risks of inconsistency and ensures organizational compliance.
The implementation of a standardized DMS like D2 or the > Dell EMC Documentum Life Sciences Solution Suite requires the migration of documents from the old to the new system or a transforming of the data model within the system in order to work properly with the new application. Often this old data is not fully standardized and structured, but either based on a less controlled system such as Documentum Webtop or on a controlled system with slightly different structures such as CSC FirstDoc or Cara.
Out of curiosity to explore the new features of D2 4.6, I upgraded one of our D2 4.5 projects a few weeks ago. In this blog post I explain the new features, the upgrade, as well as our experiences with the new version of D2.
So apart from all the technical stuff, which new aspects will benefit the end users? The new release introduces a couple of valuable features.
With D2 4.0 EMC Documentum released a new approach of a content centric ECM client one year ago. In the meantime version 4.1 has come out with additional features and improvements in March this year. The main paradigm of this client is configuration instead of coding. In this blog post we want to explain the characteristics of D2 4.x and the experience we gathered with D2 during the last year.
Common D2 Characteristics
- D2 is a modern looking web client
- With D2 you configure your requirements instead of coding
- More intuitive than older Documentum clients
- Fast and easy deployment and testing of any configuration of a solution
- Configuration changes will take effect immediately (just every now and then a cache needs to be cleared here as well)
EMA is NOT an out-of-the-box product, it’s a tool set (framework) that ONLY the Documentum Professional Services Team uses. This tool is exclusively available through EMC IIG Services. Once the engagement is over, EMA leaves with the team and cannot be used for additional migrations. Partners and customers are not able to use EMA without IIG Consulting in a project because EMA bypasses the API (DFC).
The main use case for EMA is the high speed cloning from Oracle based on-premise Documentum installations to MS SQL Server based off-premise (EMC onDemand) installations. For this approach a simple dump&load is not feasible and a tool for cloning is needed. In addition EMC addressed some other use cases at EMC World 2013 like version upgrades (DCM to D2 life sciences and Webtop to D2 or xCP) and third-party migrations.
Speed vs. Business Requirements and methodology
Cloning or a 1:1 migration of all objects located in a repository without reorganization and clean-up has no additional business value, the result is just a new platform and/or version (garbage in, garbage out). With EMA, changes on business requirements can not be applied easily during the migration (e.g. new metadata, new object types, business logic etc.). The results of the actual migration can not be discussed with the business department before the content is imported in the target system. If needed, duplicates can not be dictated and managed. And furthermore it is not possible to apply changes during the project with just a few clicks of the mouse as you could with migration-center.
Mit dem Documentum D2 Client ist es EMC gelungen, ein hochinnovatives ECM Interface in ihre Produktlinie zu integrieren. Es ist nicht nur sehr benutzerfreundlich und intuitiv, sondern fast schon eine Revolution in der schnellen Bereitstellung von Enterprise Content Management Lösungen durch Konfiguration. Hier spielt der Client die Vorteile gegenüber anderen ECM Clients aus, da die unterschiedlichen Geschäftsanforderungen der Anwender weitgehend mit den von Documentum D2 zur Verfügung gestellten Konfigurationsmöglichkeiten umgesetzt werden können.
Das matrixbasierte Konfigurationsinterface stellt alle elementaren Aspekte der EMC Documentum Plattform bereit, die anschließend dem Endbenutzer in einer modernen browserbasierten Rich Internet Client Anwendung zur Verfügung stehen. Dadurch können erstmals ECM Projekte agil mit starker Einbeziehung des Kunden durchgeführt werden.