We tested HyperScience on structured formats of the forms, and it worked really well. We tested it with semi-structured formats, and it worked well. We also tested creating a new form that does not have any format. HyperScience has less capability while working on unstructured forms. Unstructured forms are those where there is no standard structure and the information can be anywhere on the form. They need to develop this capability. Such a capability would make it a perfect system for processes like data entry, accounts tables, etc. Secondly, before putting the actual volume in the tool, I believe that we have to create a manual form every time. If the procedure of creating the forms can be shortened or automated, it would help. It would reduce the manual effort of creating a form every time you start working on it. There should be an automated form creation system that does not require any manual intervention. Whenever a new form comes, the system should be able to create a dummy form for that. That will help.
Extracting tables from certain documents could be improved. The next product release should include a utility that provides HyperScience JSON output. It would be related to any application, like other platforms and include Power Apps. We need to impact their REST API, but we would need a connection bridge application. And the second feature would be HyperScience providing different outputs. At present, HyperScience only provides JSON output. If a business needs a different output, we must create the utility ourselves and provide that data to XML or something similar. But if HyperScience could do that, we would no longer need third-party apps.
Head of AI and Automation at a insurance company with 5,001-10,000 employees
Real User
Jul 14, 2022
They could work on the price and make it a bit more reasonable. HyperScience is already working on some classification models and text classification models in their documents. That's a good roadmap for them. Roadmap-wise, they're on the right track.
Lead Analyst at a financial services firm with 1,001-5,000 employees
Real User
Mar 23, 2022
No solution is perfect and there are several different scenarios that could be improved in HyperScience. One area is where there are multiple tables in the same form I have seen HyperScience struggle. There is some issue with supporting the extraction from multiple tables involved on the same form. If this could improve, it would be a big benefit. The document extraction works well in conjunction with other automation suites. If HyperScience can provide some way to directly integrate with these other RPA automation tools, it would be a good add-on.
OCR Developer at a tech vendor with 10,001+ employees
Vendor
Aug 12, 2021
The product's usability could be better. The first pain point is that we're getting the output in a different format, and we were expecting a different timetable. The second point is that if you want better results, HyperScience says you have to configure a minimal PDF or a maximum of 400 PDFs. If you want results with 400 PDFs for what's written by these doctors, then you also configure the maximum of 400 templates for that. So, it's essentially a lack of support from HyperScience. In the next release, it would be better if failure scenarios were reduced. It would also help if they offered different formats, inputs or injections, and added different scenarios.
HyperScience is a cloud-based input-to-output platform that automates document-based workflows and extracts data for analysis from both physical and digital documents.
The HyperScience platform simply integrates with your current business systems thanks to an open API, an intuitive UI, and pre-trained models, resulting in a totally automated digital workflow.
The classic scanning paradigm has been reimagined by HyperScience; it has replaced the need for human verification with intelligent...
We tested HyperScience on structured formats of the forms, and it worked really well. We tested it with semi-structured formats, and it worked well. We also tested creating a new form that does not have any format. HyperScience has less capability while working on unstructured forms. Unstructured forms are those where there is no standard structure and the information can be anywhere on the form. They need to develop this capability. Such a capability would make it a perfect system for processes like data entry, accounts tables, etc. Secondly, before putting the actual volume in the tool, I believe that we have to create a manual form every time. If the procedure of creating the forms can be shortened or automated, it would help. It would reduce the manual effort of creating a form every time you start working on it. There should be an automated form creation system that does not require any manual intervention. Whenever a new form comes, the system should be able to create a dummy form for that. That will help.
Extracting tables from certain documents could be improved. The next product release should include a utility that provides HyperScience JSON output. It would be related to any application, like other platforms and include Power Apps. We need to impact their REST API, but we would need a connection bridge application. And the second feature would be HyperScience providing different outputs. At present, HyperScience only provides JSON output. If a business needs a different output, we must create the utility ourselves and provide that data to XML or something similar. But if HyperScience could do that, we would no longer need third-party apps.
They could work on the price and make it a bit more reasonable. HyperScience is already working on some classification models and text classification models in their documents. That's a good roadmap for them. Roadmap-wise, they're on the right track.
No solution is perfect and there are several different scenarios that could be improved in HyperScience. One area is where there are multiple tables in the same form I have seen HyperScience struggle. There is some issue with supporting the extraction from multiple tables involved on the same form. If this could improve, it would be a big benefit. The document extraction works well in conjunction with other automation suites. If HyperScience can provide some way to directly integrate with these other RPA automation tools, it would be a good add-on.
The product's usability could be better. The first pain point is that we're getting the output in a different format, and we were expecting a different timetable. The second point is that if you want better results, HyperScience says you have to configure a minimal PDF or a maximum of 400 PDFs. If you want results with 400 PDFs for what's written by these doctors, then you also configure the maximum of 400 templates for that. So, it's essentially a lack of support from HyperScience. In the next release, it would be better if failure scenarios were reduced. It would also help if they offered different formats, inputs or injections, and added different scenarios.