What is our primary use case?
It serves as a content management solution at our company, Chevron, where it plays a crucial role in managing the extensive documentation associated with various aspects, such as sales and field operations.
How has it helped my organization?
When a field mechanic needs to inspect a pipeline to identify issues, they follow a specific procedure marked by a PSA code. In such cases, they need to access relevant documents stored within the Documentum system, which isn't stored on their personal devices like laptops or iPads. To access these documents, they simply open the Documentum app, enter the assigned PSA code, and, voilà, the system retrieves the associated documentation, including the structural details of the pipeline.
This quick access enables the mechanic to efficiently pinpoint and address the issue right on the spot, not only facilitating field operations but also ensuring the security of sensitive data through robust implementation.
What is most valuable?
It provides extensive accessibility to our content, and it's a vital component in our work processes. We've gained access to a plethora of applications through OpenText, which enables us to enhance our services for customers.
One notable example is the integration with Xfinity ECM, a solution that seamlessly integrates with SAP. For instance, when someone working with SAP needs to access a specific invoice document, SAP itself doesn't store these documents, instead, the content related to the invoice number seamlessly flows through Documentum.
It offers robust security features and it allows to leverage a variety of plugins from OpenText to enhance security. For example, there are plugins like Trusted Content Services that allow you to encrypt entire documents for added security, though it's essential to be aware that this might impact performance.
It is a highly potent content management tool. It stands out for its impressive records management capabilities and the ability to handle an extensive volume of documents, even reaching into the billions.
What needs improvement?
The documentation often leaves customers feeling somewhat frustrated, as OpenText seems to expect customers to remind them constantly about the need for better documentation, as they don't provide clear guidance on their documentation practices.
For how long have I used the solution?
I have been using it for eighteen years.
What do I think about the stability of the solution?
Its quarterly release schedule for new versions is appreciated, but it often introduces bugs that inconvenience customers. This puts customers in a dilemma between not upgrading and falling behind or upgrading and dealing with issues. Mobile apps provide seamless and automatic updates with minimal user hassle. I would rate it eight out of ten.
What do I think about the scalability of the solution?
OpenText offers a wealth of service engines and components that can be seamlessly integrated with Documentum, enhancing its capabilities significantly. It has shown excellent versatility in supporting various databases, with Oracle being notably powerful in this regard. I would rate it eight out of ten.
How are customer service and support?
The application has been upgraded, and the majority of relevant articles have been updated within the last two years. This means that when I used to search for solutions in the past, I often had to connect with support and wait for assistance. The shift towards a more self-service approach, where knowledge is readily available, has significantly improved the support experience. It provides direct support with a dedicated support engineer, which further enhances the overall support quality and about forty to fifty percent of our smaller issues can be resolved by referring to articles available, without having to open a ticket.
Which solution did I use previously and why did I switch?
In the past, Documentum and SharePoint were often seen as competitors, running side by side in many organizations. However, this came at a significant cost, especially when Documentum was owned by BMC, which had a different licensing strategy. Nowadays, Documentum has emerged as a robust competitor against SharePoint.
SharePoint has limitations when it comes to handling large volumes of data and lacks comprehensive records management features. When it comes to document retention, Documentum is a strong choice, emphasizing the importance of maintaining a clear document retention lifecycle. Previously we used content management systems like FileNet and eRoom at Chevron. However, neither of them is in use anymore.
The reason is that Documentum is a robust, heavy-duty vehicle capable of handling a substantial load and it excels at managing and handling heavy workloads, which signifies the vast amount of content and documents efficiently.
How was the initial setup?
The initial setup was relatively easy for me as I had prior experience. However, for newcomers, there might be a bit of a learning curve, especially when it comes to navigating the documentation.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, although I'm not directly involved, I've heard from my manager that the pricing has improved significantly. The price is considered affordable now.
What other advice do I have?
It is important to note that it follows a strategic approach of releasing updates incrementally every quarter, rather than providing a complete package all at once. It offers support for hostless SQL using an OpenText open-source database, which is known for its lightweight and efficient nature. Overall, I would rate it eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
*Disclosure: My company has a business relationship with this vendor other than being a customer: Partner