Autodesk Docs is a cloud-based common data environment for Autodesk's AEC Collection and the Autodesk Construction Cloud. The solution helps to reduce errors, streamline review and approval workflows, as well as align team members to ease project scheduling.
$65
per month per user
OpenText Documentum
Score 8.4 out of 10
N/A
OpenText acquired Documentum from Dell EMC in 2017, and now supports the enterprise content management (ECM) system. The vendor says users can build content-centric applications and solutions from collaborating on business documents to delivering case-based applications to managing highly precise processes in the most regulated business environments.
N/A
Pricing
Autodesk Docs
OpenText Documentum
Editions & Modules
Monthly Subscription
$65
per month per user
Yearly Subscription
$500
per year per user
3-Year Subscription
$1500
3 years per user
No answers on this topic
Offerings
Pricing Offerings
Autodesk Docs
OpenText Documentum
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Autodesk Docs
OpenText Documentum
Features
Autodesk Docs
OpenText Documentum
Enterprise Content Management
Comparison of Enterprise Content Management features of Product A and Product B
Autodesk Docs
-
Ratings
OpenText Documentum
9.2
Ratings
14% above category average
Content capture & imaging
00 Ratings
10.00 Ratings
File sync, storage & archiving
00 Ratings
9.00 Ratings
Document management
00 Ratings
9.00 Ratings
Records management
00 Ratings
9.00 Ratings
Content search & retrieval
00 Ratings
9.00 Ratings
Enterprise content collaboration
00 Ratings
9.00 Ratings
Content publishing & creation
00 Ratings
9.00 Ratings
Security, risk management & information governance
Since my favorite feature is that it brings everyone together, I find it appropriate to interpret it from this perspective. The platform created for all project stakeholders to work together in real time helps increase project efficiency, reduce errors and minimize delays. It creates real-time data, analysis and reporting that will ensure increased and high project performance, which is a quantitative contribution to project management.
What are the document volume, the throughput - currently and expected in year, 3 years etc.? Is the company doing content management on international level, where access from multiple locations is needed - then Documentum can be good investment. What ECM system will be used for - document storage, document lifecycle or retention? Or all of the above? - Documentum works very well if all 3 items are combined, yet for storage there must be cheaper and more easily adaptable solutions available.
It's good at integration with external systems through standard industry supported APIs, including but not limited to web services integration and file system integration.
Good support from major up and downstream technologies such as image capturing and back end ERP, Database, and HR.
It is a bit expensive for small construction companies or project offices, and it is more difficult to reach, especially for countries with high exchange rates such as Turkey.
It cannot integrate with other non-Autodesk software we use within the company.
Being dependent on the internet is a problem. Of course, I know that being cloudy requires internet, but it may be an advantage to at least keep the used files in its own memory for a while.
Expense. If Documentum costs less it would penetrate more markets. This is often the reason a lighter weight solution is chosen.
Web Publishing. Documentum is not a great solution for replacing CMSs like SiteCore or Drupal. Probably better as an archiving target for parallel publishing to both web and Documentum. Documentum is also not a web hosting solution like some other systems, it is possible to try and consume directly from the repository in real time but it is better to push web content out and consume from another platform.
Development. The price of broad functionality is complexity. Arguably, Documentum drank the kool-aid and tried to become like other enterprise solutions by adapting Java, Windows, etc. in the late '90s and it made them slower, more complex in design, and less stable. They recovered from that but it still requires developers with a few years of experience in Documentum to safely develop in Documentum. The issue is not knowing Java but knowing what to do or not do in an ECM system. This is even more important in regulated ECM/RM systems.
Stability is a key factor as well as its flexibility. Also, any organization that deploys Documentum will have made a significant investment in terms of time and money, so not renewing its commitment can come with a significant cost. That said, the decision to deploy Documentum initially should come only after extensive evaluation, knowing that once deployed it will likely remain the platform of choice.
Subjective but here's how I see it: Heavy duty (in order of how much they can do and how much they can handle): 1)Documentum, 2)FileNet 3)OpenText Middle duty: 1)WCC-WebCenter Content, 2)Alfresco, 3)M-Files (3rd b/c it is Windows only), 4)Nuxeo (only b/c of its newish approach that may lead somewhere) Light duty: 1) BOX (not an ECM but it says it is), 2) EFSS (pick your poison, BOX is an enhanced EFSS), 3) CMSs (some have some ECM capability, none have much)
After this product, the client is able to manage content security and due to it, the client is able to use the business process, and this really reduces effort and increases the profit in business.
It provides integration with SAP easily which really helps the client to manage this effectively and with minimum effort system is ready to use.
Also searching, automated flows also create a bigger impact and reduce a lot manual effort.