Ayasdi Core is a business intelligence software offering from Ayasdi.
N/A
IBM Cognos Analytics
Score 8.1 out of 10
N/A
IBM Cognos is a full-featured business intelligence suite by IBM, designed for larger deployments. It comprises Query Studio, Reporting Studio, Analysis Studio and Event Studio, and Cognos Administration along with tools for Microsoft Office integration, full-text search, and dashboards.
Well suited: 1. If data set is not yet well organized. 2. Hypothesis is not yet established. 3. Need to visually explore to find patterns of data (often when analysts have no good understanding of data) 4. When [you need] to analyze events with a timeframe (specifically a sequence of events as a transaction) Less appropriate 1. If a data set is very large, such as Hadoop data, it becomes hard to manage data pipeline and process to feed the data into Ayasdi. To be feed into Ayasdi, data should be aggregated or organized to some level.
Reporting whose demands are not too high but simple tabulated format which can be used for over several years. Also adhoc reporting using Query Studio is better in making short time reports. Other options where it lacks is Dashboarding where I would prefer Tableau or PowerBI
Ayasdi Core provides an easy way to get some insight on data. Typically analytics may require having a model or hypothesis before starting to look into the data, but Ayasdi lets you just feed the data first then start seeing what the data looks like.
Ayasdi Core's topological network visualization is quite unique. It allows you to explore patterns and potential relations between multiple data elements. A user can also dynamically navigate data with different aspects on the web.
The Web version of Ayasdi is easy to use, stable, and fast. It hasn't crashed even when we feed it a lot of data sets, although it took time.
Use of Python SDK is required to feed data into Ayasdi, but it lacks training materials or sample codes for a novice to get started.
Although Web UI of Ayasdi is looking good, often it freezes when the user runs an analysis. It doesn't crash but the web page needs to be refreshed to see the progress of analysis.
Algorithms provided by Ayasdi, such as metrics types, lens types need to be explained (what they are and what their strengths and weaknesses are). We had to Google or do research on our own to understand what they are.
Data modules still can't match the flexibility of the framework manager. When dealing with large data models, or multi-grain, FM still wins.
The new native graphs, while pretty, still can't match the version 10 graphs in terms of flexibility or options. It is possible to import third-party graphs, but it's a pain.
Some functionality, like version control, is only available through third parties. Motio or BSP.
For an existing solution, renewing licenses does provide a good return on investment. Additionally, while rolling out scorecards and dashboards with little adhoc capabilities, to end users, cognos is very easily scalable. It also allows to create a solution that has a mix of OLAP and relational data-sources, which is a limitation with other tools. Synchronizing with existing security setup is easy too.
We have a strong user base (3500 users) that are highly utilizing this tool. Basic users are able to consume content within the applied security model. We have a set of advanced users that really push the limits of Cognos with Report and Query Studio. These users have created a lot of personal content and stored it in 'My Reports'. Users enjoy this flexibility.
Reports can typically be viewed through any browser that can access the server, so the availability is ultimately up to what the company utilizing it is comfortable with allowing, though report development tends to be more picky about browsers and settings as mentioned above. It also has an optional iPad app and general mobile browsing support, but dashboards lack the mobile compatibility. What keeps it from getting a higher score is the desktop tools that are vital to the development process. The compatibility with only Windows when the server has a wide range of compatibility can be a real sore point for a company that outfits its employees exclusively with Mac or Linux machines. Of course, if they are planning on outsourcing the development anyways, it's a rather moot point
Overall no major complaints but it doesn't handle DMR (Dimensionally Modeled for Relational) very well. DMR modelling is a capability that IBM Cognos Framework Manager provides allowing you to specify dimensional information for relational metadata and allows for OLAP-style queries. However, the capability is not very efficient and, for example, if I'm using only 2 columns on a 20-column model, the software is not smart enough to exclude 18 columns and the query side gets progressively larger and larger until it's effectively unusable.
Why is their web application not working as fast as you think it should? They never know, and it is always a a bunch of shots in the dark to find out. Trying to download software from them is like trying to find a book at the library before computers were invented.
Onsite training provided by IBM Cognos was effective and as expected. They did not perform training with our data which was a bit difficult for our end-users.
The online courses they offer are thorough and presented in such a way that someone who isn't already familiar with the general design methodologies used in this field will be capable of making a good design. The training environments are provided as a fully self contained virtual machine with everything needed already to create the environments. We've had some persisting issues with the environments becoming unavailable, but support has been responsive when these issues arise and straightening them out for us
Make sure that any custom tables that you have, are built into your metadata packages. You can still access them via SQL queries in Cognos, but it is much easier to have them as a part of the available metadata packages.
We had a working group that has been using R studio for the general purpose of statistical analysis in our organization. Although it is a great tool that provides enriched function sets, it is time-consuming for our clinical analysts to learn the tool to see the first result. R is somewhat of a developer-oriented/friendly tool. Ayasdi is friendly to a domain analyst or end users. Plus, support and consulting from Ayasdi were excellent so that we could get knowledge from them immediately whenever we needed.
We could deliver a corporate wide solution with Cognos, it is an end-to-end platform. No other option provided the same breadth of scope. I can't think of a feature that the others provide that Cognos lacks, but the others do not provide the same features and governance of data with user/data security in mind.
The Cognos architecture is well suited for scalability. However, the architecture must be designed with scalability in mind from day one of the implementation. We recently upgraded from 10.1 to 10.2.1 and took the opportunity to revamp our architecture. It is now poised for future growth and scalability.
