The main module we use is ITPM. The ability to have standardized reports around obsolescence and lifecycle management is probably the most valuable.
We are trying to move to a more standardized approach regarding how we do lifecycle management and having the ability to generate the obsolescence report which says what applications are impacted by obsolete technologies on a rolling horizon is valuable so that we can actually do our business planning and manage technical data in a more organized manner then the way that we have been doing it today.
It shows you for all of the applications that are depending upon obsolete technology, what is the technology that is going obsolete and what is the application that is impacted. Essentially, it's a list view.
Improvements to My Organization
We are not using the entire platform, although we are licensed for a couple modules. The main one that we are using is ITPM. The other thing that I think we find useful outside of the obsolescence report is also having a more organized view of our applications and their technology dependencies. Matching it up with roadmaps related to technologies in a singular view. We had an application technology view that also becomes quite useful.
Room for Improvement
I think it has a lot to offer, but we have been focusing in on ITPM. I think we ourselves need to do a little bit more exploration of how we can benefit from some of the other modules.
Something that might be helpful is to have a little bit more of a curriculum-based engagement of MEGA where we are actually educated more on the bigger picture, not just the tool, but really what is the big picture that MEGA is trying to solve. What are the different pieces and how they fit together? I think that will help expose the power of MEGA to us to see how we can actually use it better. Kind of the Art of the Possible type of positioning.
From the capabilities perspective, the user experience is not the best. It needs to be a lot more easy to use, more intuitive.
It could also drive adoption. We are a pretty large organization with a lot of application and it's not all architects that are using this tool. There are people that are in peripheral organizations that we rely on to provide information and the user interface really needs to be simple and clean and be able to move from task to task very efficiently. The feedback we have gotten so far has not been that. It's been, it's hard to navigate. It's not intuitive. It takes time to do multiple updates in a sitting.
What that means today is that people export data out of MEGA, manage an Excel spreadsheet and then do vault uploads and it kind of defeats the purpose of having a tool like this.
Use of Solution
18 months. We are getting to the first real use of it with our business planning for next year and kind of starting now.
We have had challenges with scale. We had to refactor the way that we organize the data due to that scaling issue. Originally, we had brought in every application landscape as an individual application and if the reports were timing out and we were not able to get a performance response. In fact, our users were complaining as well. We have refactored so that applications are really more of our business service construct that are grouping multiple landscapes which are becoming software installations. It's working a little bit better, but we still have struggles with some reports that are large or go out to large data sets that the system sent tends to time out. In fact, we had to put automated timers to terminate tasks that are taking too long just because it becomes ineffective. These jobs are in the background that cause other problems. Performance and scale has been an issue.
If you have an interactive application, people don't expect it to be taking hours. People expect responses within minutes. When they're sitting there for 10, 15, 20 minutes and there is nothing back, something is obviously not done right whether the architecture behind the scenes is not done right or the way it fans out to compute is not done right, something is not right. We've had performance issues and continue to struggle with it. Another example is when we do these reports, as I mentioned, obsolescence, really have to do with volume.
You have to do it on a portfolio by portfolio basis. You need to go to the top level and say, "Run this obsolescence report for everything in my environment." Then we have to say, "Do it for a subset of the data set just because of performance."
Customer Service and Technical Support
My team actually runs the platform, I don't really deal with technical support themselves, but I do get feedback. Yes, they have used technical support. It's kind of a mixed bag. Sometimes we have gotten good results, but other times it hasn't been what we would hope for.
Generally we do engage them as well as professional services. In fact, we've probably been engaging professional services a lot more than we need to. That's a different issue.
Other Solutions Considered
We got an introduction to MEGA from a smaller group within our company. The conversation with the person that was already using it was essentially focused on how much customization were they doing.
At the time they told me it had unlimited customization and that is kind of what drove me to say we are going to adopt MEGA for the Enterprise, but truth be told, since we have adopted it, we are actually doing a lot more customization than I would have hoped for. The out-of-the-box capabilities don't really align with the broader vision. Hence, we are spending a lot of time with pro services.
When they did the assessment I think they looked at Alfabet and a couple of others.
Be very clear on what you need because MEGA has a lot to offer and if you are really going to be able to take advantage of MEGA's portfolio, then you should consider it. Be ready for the journey we went through which took 18 months to get to where we are at.
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Aug 07 2016