HP Autonomy Intelligent Universal Search (discontinued) vs. IBM Watson Explorer

It does a decent job at its core functions (that other free software does just as well or better).

The Watson Explorer is great because it potentially replaces a meriad of other low-level analytics products that we would need to use for data analytics and data mining. WEX isn't really suitable much beyond doing text and data analytics and performing machine learning, so if your team doesn't really have a use-case that fits all of these categories, it is worth looking at an alternative.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• It adheres to traditional Microsoft standards such as: fact-dump documentation with no coherent story or 'best practices' information, inability to automate common tasks, intentional obfuscation of its basic operations.
• It provides OK search results. Not great, but OK.

• Free to try - It's possible to use most of the useful features of Watson Explore on their trial/demo accounts.
• Super well-designed data analytics tool - Most of the tools and features of the explorer are really useful, and truly help you fully understand the depth of any format of textual data.
• Extensive sources compatibility - WEX can retrieve data from a large range of sources, and the compatibility there is quite good as well.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• There are about a dozen different config files to maintain, and the most important one is dynamically modified by Autonomy itself while it runs. Which means that it is impossible to automate the configuration or keep the configs in versioned source control. Even `cp *.cfg ~/cfgbak/` won't help you roll back a change, because it is never safe to restore a previous config. You'll be using `diff new.cfg old.cfg` a lot.
• The Linux port is poorly thought out. The binaries are named *.exe. The StartService.sh scripts contain both `echo 'Are you sure you want to start the service? Hit ctrl-C to cancel''; read dummy` and, I kid you not, a `chmod a+x /path/to/my/binary.exe`.
• Many features are poorly documented, leading to lots of back and forth with the support department just to answer basic questions like "what does this error code in my logs signify?"
• It seems to reinvent the wheel, poorly, everywhere. E.g. the scheduled backup feature rolls through a user-defined finite list of directories in which to store backups. On day 0 it uses directory 0, on day 1 it uses directory 1, and after day N it rolls back and overwrites directory 0. Why would this be preferable to using a single directory and naming zip files based on the current timestamp?

• Support is just OK, like most of the other IBM Watson products. The setup/integration is really hands-on, but it's also problematic because support later may take a considerable amount of time.
• UI could still use a little more improvement - part of the administration and sources dashboards are hard to navigate.
• The Application Builder is a great part of the product, but hard to learn/understand - this is where we needed the most support from IBM and tutorials/documentation.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

Management wants to see ROI on the (hefty) cost of purchasing this software, and has mandated that we continue using it. We would prefer to switch immediately.

Google Cloud offers a Natural Language product, but it is just an API. This API doesn't offer the useful visualizations of relations, analytics, and graphs that IBM Watson Explorer offers on their interface. For this reason, we chose to go with IBM WEX. For later stages of our production, we decided to use Google's NLP API because we found that it was quick to integrate into production after studying data and developing models using IBM WEX.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• I have learned to tack a zero onto the end of any estimate I make for how long an Autonomy change will take in both planning and implementation.

• Positive - Trial/demo period. This was really useful for us to figure out what features of WEX we liked most and how difficult it would be to integrate WEX into our workflow.
• Negative - On-boarding was long and almost always requires support from IBM support, unlike most other products this advanced.
• Positive - WEX replaced a large selection of alternative products we would have to use for the same functionality, and having all of that function in one place was definitely helpful.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info