What is our primary use case?
We use the solution on the cloud, and Jedox hosts it. I'm the admin at my company, and we do corporate planning and management, including all the budgeting and forecasting. We also do a lot of reporting, such as monthly management reports, and we have a few HR dashboards for that. We also do a lot of actual reporting on leaves, headcounts, and standard HR reporting. We also do a lot of revenue reporting, and one of Jedox's key uses, apart from reporting, forecasting, budgeting, and planning, is we also use the solution for ETL jobs. We use Jedox as an integrator tool, so we use Jedox to get data from old systems into new systems.
What is most valuable?
The ease of reporting is one of Jedox's most valuable features. It's like an online spreadsheet, so it's easy for anybody to get used to making reports on it. Jedox helps you to perform dynamic reports, which are reports that expand and contract based on variables, one of the key features.
Working with dashboards is pretty intuitive, where you have a set of variables, and if they remain consistent across your different cubes, you can control the whole report. For example, you have information from the accounting, HR, and revenue systems in an executive dashboard. If you have your dimensions common across these different systems, or "cubes," you can ask for information, which can change for any year, time, month, or department you choose. You can make dynamic reports that can refresh and appear to provide seamless information to the end user, who just needs to change some variables to get the reports they want. However, at the back end, you have a complex system pulling information from different systems. That's one of the key features I found.
Suppose you want to have reports that expand. For example, if you have a list of employees, you might want to know how much was paid to each employee in a department. You can change the department, so if one department has 100 employees and the other has 20 employees, you'll want the report to expand and contract when you switch between departments. It's very easy to do that in Jedox. From the reporting point of view, this is a valuable feature. I found it intuitive with ETL jobs because Jedox graphs on the side, so you can see which jobs depend on which. You can visually follow jobs end to end without painstakingly figuring out which job depends on which one.
Jedox works well across different systems. You can integrate Salesforce, RBI, and standard databases to make API calls. It's easy to do all that out of the box without doing a lot of manual API integration.
What needs improvement?
There is not much training for Jedox. There was no training available in the beginning at all. I had to reach out to them so they would give us something. I think they're getting better, though. The other issue is the dependence on the partner network. We used to deal directly with Jedox, but now it is all through partners, and Jedox's representatives are not in the picture anymore. It's not that partners are not doing a good job, but you're not dealing with the company directly since it's a partner most of the time. If you build your know-how within the company, it's good. Otherwise, the dependence on partners could end up being more costly. Suppose you do your development or don't need to develop constantly by starting with a sprint, deciding what you want to do, and setting up the cubes, databases, and everything correctly. In that case, you only need to develop different reports using the same data. However, it could be costly if you constantly need to develop reports or different cubes and store different systems without the in-house know-how.
For how long have I used the solution?
I've been using Jedox for over five years now.
What do I think about the stability of the solution?
I rate Jedox's stability a seven out of ten. Jedox goes off sometimes, and you need to go on the console and restart some of the backend things, like servers. Otherwise, the platform is okay 85% of the time. That could sometimes be because one of our users ran a query, causing Jedox to crash.
What do I think about the scalability of the solution?
I haven't noticed many performance issues when users log in. The performance issues mainly come when you try developing a new report. With the criteria you're passing, the report enters an infinite loop because it gets too much data, and the server slows down. But when we had budgets and planning going on, I didn't see issues with it slowing down because many users logged in simultaneously. We have 50 users on Jedox.
How are customer service and support?
Their response time was okay, but I was looking for a solution and didn't get one. I was referring to one of their knowledge bases and trying to develop a report. I thought the features I needed didn't exist, and then support said what I wanted to do could be done on the newest version of Jedox. But their knowledge base should say exactly which version I'm supposed to be using. It was frustrating to spend time looking for something that didn't exist. Jedox's support is from Germany, so language barriers and cultural differences need to be considered.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We had another system in a company I used to work for. The system was called Calumo, and I think it's called insightsoftware now. We were used to that system but at my current company, one of the things we were putting up in a business case for which system to choose, one of the things we came across with Jedox was that it was a bit cheaper compared to Calumo. I had not used Jedox then, but after using it, I found one feature good in Jedox compared to Calumo. The ease of reporting. You can do many things in Excel using Calumo, but the solution was heavily focused on doing pure table analysis at that time. Calumo also gave users the power to slice and dice the data in Excel or on the web, but when you have to do dynamic reporting, you need to know another language called MDX. If you know the language, which is very complicated, only then can you do dynamic reporting. Otherwise, you need somebody else to do it for you. You could do this directly in Jedox. That was a key difference after the purchase. Also, the person from Jedox gave us a demo, which seemed pretty good then.
How was the initial setup?
We had on-prem installation first, which was straightforward, but the cloud one took some time for us to move to. But once we got on the cloud, it was also pretty seamless.
What other advice do I have?
If you are considering Jedox, it's a good choice. But it still has a price, so you have to consider a few things, and one is what's your need? What's the use case? If you have certain things you want to achieve, such as planning and management and all those things, and you have the budget for it, then I recommend Jedox. If I were to go to a new company and start all over, I would choose Jedox. If you make good use of Jedox, it's worth the money. You can integrate tools like MuleSoft into Jedox, which otherwise costs $60,000. I rate Jedox a nine out of ten.