By now, you’ve most likely heard the recent news about OpenText’s intent to acquire EMC Documentum. As a Documentum customer, you may be asking what this means for you? As of right now, there are few answers about Documentum’s fate. Because the process will likely take months to a year, you may not feel you need need to make a decision right now. However, we recommend taking some time to assess what your next steps should be.
Join us for an informative webinar where Zia Consulting will discuss possible outcomes for Documentum in the wake of the potential acquisition, how you can co-exist, or how you can migrate to a more suitable option.
View the recording here: https://attendee.gotowebinar.com/register/6075356275672664068
13. People
Is All We Do
“Mike always says Zia is best in the world at
content management. This is hard to believe until
you meet the team. They really are the best.”
Brian Gray – CIO, Baldwin & Lyons
24. Next Steps/
Questions
• Join Our Next Webinar
• Deep Dive on Migration
Best Practices Series
• Alfresco Discounts
• Contact Us
• Reply to follow up
email
• mike@ziaconsulting.co
m
• 888-732-4101
Continued Documentum Support
Added to OpenText’s long term product offerings and improved
The Slow and Painful Death of Documentum
Innovation will be halted and eventually phased out
Forced Close
Provide a timeline for which Documentum will be shut down
Best of Both Worlds
Incorporate best Documentum features into an already established product
Lack of innovation: Documentum’s product stack has not innovated in years and is built on old technology.
Unfulfilled promises: EMC has been big on promises and slow on delivery. Most people believe the acquisition is going to make this more of a problem. EMC has been working on their “next gen” platform for many years and have changed direction multiple times. They have finally created some simple applications in their new environment, but not much of their technology has moved into the cloud.
Difficult integration: Documentum has never had a strong commitment to openness or easy integration outside of their own stack. They built FTP and WebDAV connectors (as separate products), but have end-of-lifed them. Documentum has some support for CMIS (open standard for connecting to different content management systems), but is slow to keep current as CMIS is not core to how people access their repository.
Elusive licensing model: Documentum tends to sell new licenses for their upgrades rather than simply including new functionality. Their main user interface (WebTop) has not had any real functional or usability upgrades for years. When they came out with D2 and xCP, products that provided enhanced UIs and functionality, these products came with an additional cost. This is also not likely to change with an OpenText purchase.
Doesn’t play well with anyone: Newer Documentum products do not work well together. The D2 and xCP products work on the Documentum Content Server, but don’t work together, so workflows created within D2 do not automatically appear in xCP and vice versa. Documentum has tried to re-engineer other aspects of these and other “new” products due to a lack of a common architecture over multiple releases.
He also says, “Documentum during that same time evolved in a very different way. Under the leadership of Dave DeWalt who took over in 2001, Documentum acquired complementary adjacent technologies to upsell to their customers. Even after the acquisition by EMC, Documentum seemed to have a degree of autonomy (no pun intended) in working within a larger hardware business. That changed when the EMC hardware side took control, DeWalt left and it’s been a slow decline ever since.”
The third category of risk is the rapidly evolving future of content management. Bernard Marr has an excellent article in Forbes on 20 mind-boggling big data stats that illustrate our specific concerns quite well. Documentum and OpenText’s ECM platforms are already stagnant technologies, and companies can’t prepare for the future with a platform that can’t remain agile or grow along with them. There are four areas of risk around the evolving content market:
Content is exploding: According to IDC, there is no end in sight, they predict that by 2020, the digital universe will increase by 10 times moving from 4.4ZB to 44ZB. It is crucial that your ECM system integrate with the line-of-business applications you have today.
Device count and complexity has grown: The number of devices used to create and work with content has increased significantly. According to Forrester Research, greater than 50% of knowledge workers use an average of three devices to create content. This creates real security and management concerns for organizations.
Our data is not secure enough: It is estimated that 43% of the digital universe of data needs security and less than 52% has it. The future is evolving rapidly and we don’t have time to support legacy systems that can’t scale and integrate.
IT budgets are moving away from legacy support: These must decrease in order to innovate for business needs. According to IDC Digital Universe Report for 2020, 25% of external development spend and 50% of IT spend will be on cloud, social, mobile, and analytics.
To minimize these risks—as the complexity of content continues to grow, with multiple types of devices, accessibility anywhere, and increased security risks—you need a platform that can respond quickly. If you are looking to build scalable systems that integrate with your existing technology investments and handle a rapidly evolving future, you have to be seriously concerned about further investment in Documentum and OpenText.
Wait it out
Go with the flow and wait on a decision to be announced by OpenText
Plan for co-existence
Utilize workflow applications like SharePoint to access Documentum
Plan to Migrate
Hit the road and adopt a different ECM system
Add CO Companies to watch
books
If you are looking to build scalable systems that integrate with your existing technology investments and handle a rapidly evolving future, you have to be seriously concerned about further investment in Documentum and OpenText.
Migration can be an overwhelming prospect, so what can companies do?
First, select a technology platform that can address today’s content challenges and help you prepare for your future needs. This is what makes Alfresco our ECM partner of choice. Their highly-scalable (Alfresco hits a 1 Billion document benchmark), lightweight platform embraces an open architecture, open standards, open APIs, and open source. One community of CIOs has recognized that open-source software has eight advantages over proprietary software that benefits organizations. These are:
Flexibility and Agility
Speed
Cost-Effectiveness
Ability to Start Small
Solid Information Security
Ability to Attract Better Talent
Share Maintenance Costs
Open Source is the Future
Process re-engineering opportunity to consider – but that can be scary. So, instead, take a step back and look at reducing the number of steps – sub-processes and other techniques can make this less scary.
Our strategic consulting professionals have successfully helped leading organizations to create value and achieve a competitive advantage through the alignment of technology and business strategy. While determining how to adopt, transition to, or wholly migrate to a new ECM platform, Zia ensures that your migration path is well-planned and future-proofed. Some of our services include:
Initial Consulting Engagement (ICE): Deep dive into your enterprise needs.
ECM performance management: Services that analyze how to not only migrate, but also improve ECM performance and help the organization get the most value from your ECM and capture spending.
Business process transformation: Working together, Zia can help you document, analyze, and map the transformation of business processes from old system to new system to automate and revolutionize your business.
Enterprise platform and integration analysis: Using a critical eye across the entire organization, we apply approaches that bring together Zia’s solution frameworks to help articulate future direction, infuse and align your business strategy with technology opportunities, and build a roadmap to innovate your enterprise.
These steps create a discovery and process assessment, a technical review and recommendations, and finally a clear set of milestones backed by an achievable project management plan. You will know what you currently have, what the risk to change might be, a clear picture of the timing and cost of each phase, and how to move forward for an ideal implementation.
The strategy for implementation often utilizes various approaches to migration which may include determining how to break down the migration into achievable milestones—possibly using a hybrid ECM strategy (old and new platforms in parallel) for a certain period of time—and protecting the business from downtime or data loss. We strive to save you both time and money during complex, multi-faceted projects.
So what does success with our methodology look like? Across multiple industries and utilizing variations of out-of-the-box features and targeted customizations, our solution-based approaches have shown incredible results. Read the full case studies for supporting details on these statistics:
Migrated and improved the management of material for more than 700 university courses
Moved millions of files from shared drives into a system for 1200 users that was integrated with their office, line of business, and email tools
Changed the way a company does business by migrating 10 million documents to a new CM repository in just seven days
Decreased employee hours spent on classification and verification of data by 50%
Business Drivers:
- Cost
- Mergers and Acquisitions
- Improved Customer Experience
Regulatory Compliance
Modernization
Content enabled vertical apps (reducing swivel chair)
ECM Vendor / Maintenance consolidation
Key Requirements
What problems/issues are you trying to solve
What content
Change structure?
Is auditing and traceability critical?
Content info checklist:
Volume of data – provides guidance for runtime of migration
Changes to documents – need to manage and support incremental migration?
Metadata & Properties – how critical is the data about the data?
Sources of content – total choice and approach
Target location – readiness of platform
Document lifecycle – need for custom code?
Extraction details: structure, metadata, categories, lists, users, groups, permissions, and other legacy ECM functions