What is our primary use case?
As a business analyst, while working on a recent project, I used Hyland OnBase as an enterprise-like document management tool. It was used for storing, organizing, and retrieving invoices regarding our insurance project. I worked with the document management system specifically for managing invoices.
We used to receive pricing invoices from our customers, including customers in South Africa. We received those invoices and created a workflow automation. We navigated those invoices and fetched the required information by using OCR, which is already an integrated feature of Hyland OnBase. We extracted key information such as premiums, insurance policy names, premium coverage for the year, age, and particular PII information of the user. We sent them to our insurer. The person who was sitting in the back end performed verifications and then gave the underwriting result, and we provided the policy accepted or declined result. This entire workflow was automated by using Hyland OnBase.
Further, we managed documents including our training documents, business documentations, and business requirement documentations. We stored these in Hyland OnBase for our training and recording purpose for our next generation of colleagues to train them, whoever joined our new project.
What is most valuable?
Hyland OnBase offers features that are very much scalable. As the documentations, the size of the files, or number of files increase, it automatically scales itself. It is intuitive to use. It is easy for a newcomer to just get the KT and learn. There are technical support documentations, though there are fewer available from Hyland's side. Scalability is a major plus point. Customer support and technical service is also a good point for Hyland's side. It does not have any downtime. I have not faced it till now. All the services were up, fast, and reliable, and it is very secure. These are the features that stand out regarding Hyland OnBase.
During my project, as I already mentioned, Hyland OnBase can accommodate increasing document volumes and integrate additional users. During my project, the organization continued adding new documentation categories and increasing invoices that we saw. These were entirely integrated into Hyland OnBase without any further upgrade or storage upgrade, or affecting any system's performance. The architecture which Hyland OnBase works with has the capability of gradually increasing itself, rather than working on a fixed storage. That is how it was helpful to us.
I believe Hyland OnBase has impacted my organization positively by faster document retrieval that I mentioned earlier, intuitive setup, reduced manual processing, and comes with security. These insurance policies, underwriting, and invoices are very sensitive to the users as they contain PII information. From security aspects, it is very secure. It has increased the transparency of the processes and workflows. Every user who is involved in each of the steps is well aware. Even the manager gets an update. This is a very big plus point in seeing the transparency in this process. It has reduced the manual work and paperwork dependencies and also helped us to upskill more, make more business with less effort and person headcount. These are the helpful things.
What needs improvement?
More training videos, if they are more findable, would improve documentation and training documentations from Hyland's side, because there is a lack of documentation and training materials from Hyland's side in order to train new resources. Additionally, the use of AI should be introduced in the later features. If customer support is more quickly and easily reachable, it should be more useful. These are the three points.
The pricing structure could be more thought-out. If it were cheaper than it is now, I think it would be more useful and more companies could use it over other competitors.
If AI could be used more at an enterprise level, since we are purchasing at an enterprise level for the subscription of Hyland OnBase, I would say if those AI informations would stay within the enterprise and not go outside of our enterprise boundaries, it would be secure and maintain our privacy. This is the most important term in order to integrate AI into Hyland OnBase.
For how long have I used the solution?
I have used Hyland OnBase for a year and a half.
Which solution did I use previously and why did I switch?
Before using Hyland OnBase, the invoices used to come and we manually took out the key information details, which would take around a week's time, mainly four to five days. Now, with the onset of Hyland OnBase, this insurance workflow is done within one day. This much effort it has saved.
How was the initial setup?
VDI and cloud was very easy. I was responsible for gathering documentations, making the BRDs and the UAT scenarios. The setup was easy and the document management system was very easy and handy. We can automatically get the required documentations without hovering or just searching around. It always has a clean interface where we can find whatever we need in a few seconds.
What other advice do I have?
The two points I take off are for those improvement things which Hyland needs to work on that I talked about. If we generally speak about Hyland OnBase, it is a powerful enterprise management platform that is scalable, flexible, and secure in storing, retrieving, and making workflow automations. I am satisfied, but I would say it can look after the pricing, integrate more AI features, and improve training materials and documentations from their side.
I have not used AI as much because when I left the project, we were not using AI in Hyland OnBase. However, I have heard that they have integrated AI in recent releases. I am not sure about the accuracies of the AI integrated in Hyland OnBase.
My recommendation would be to have a focused business plan or use case. You can do a competitor analysis with Hyland OnBase and other products in the market. Hyland is a standout in every aspect because if you go ahead for your business use case, defining clear document classifications, then the metadata standards, then your workflow requirements before implementation, it would be better. Investing in document management for training materials is important because the platform has a learning curve, and people adoption significantly influences project success. Investing in user training is equally important, and also focusing from my role as a business analyst, involving business stakeholders early during project kickoff for requirement gathering and validation workflows through demos helps in ensuring we build a final solution that aligns with their business and operational needs. These are the things which users can consider before using Hyland OnBase. I gave this review a rating of 8.
Which deployment model are you using for this solution?
On-premises