We performed a comparison between MEGA HOPEX and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Architecture Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Customer support is fantastic. They are very helpful whenever we get on the line with the support team."
"The main feature I find crucial in MEGA HOPEX is the catalog view, which provides a comprehensive visualization of all artifacts in one repository. Another valuable aspect is the availability of out-of-the-box outcomes, such as strategy maps and BPA models, eliminating the need for additional configuration. MEGA HOPEX allows users to focus on specific business areas, like risk management or data governance, providing a high-level overview while enabling deep dives into specific areas of interest. For risk management, MEGA HOPEX allows users to assess impacts, create recovery plans, and track action plans."
"HOPEX has a panel that offers various views. I think that is very good. MEGA has an app for integrating with a lot of apps. We help our clients integrate HOPEX with a different product like Apple Gateway, for example. I've been with the company for 15 years, and we connect with everything. Our clientele includes almost all of the banks in Mexico."
"An advantage is its accessibility."
"You do not need to be a professional of enterprise modeling to contribute to the enrichment and improvement of the enterprise repository."
"The most valuable feature is that the software controls everything from a single management window."
"The most valuable feature for this solution is the automatic updating and propagation of changes across the system."
"The most valuable features of MEGA HOPEX are the seamless VPA module and the good user experience. There are built-in connections that provide integration with other platforms, such as ServiceNow. There is a lot of customization available allowing a lot of freedom. The solution is updated frequently adding new features. For example, the feature GraphQL can be integrated into other solutions, such as ManageEngine for ITSM solutions. You are able to use GraphQL to connect APIs and query the APIs."
"It has been effective for our delivery. It's given us much better visibility into what is being delivered and when."
"I like that the data that we store is available for everybody. We're not trying to hide anything. Being an administrator, I know a lot about the tool. It is very easy to show somebody how to use the tool and get used to it. Hopefully that user doesn't come back and ask the same question twice is really what it is about. It's a very intuitive product as well. For what we use the tool for today, it's easy to learn and pick up."
"A lot of of the value is around the project metrics so far but as I get more plugged into the strategic management, it's strategic planning and programs and then tying that into outcomes. I work with executive leadership and that's really what they're looking for, to say, "Okay, what outcomes do we want to achieve and how are we going to get there, plan that out, sequence that out, and then get the work to do that? And then track the work back to where we're headed with our outcomes.""
"Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool."
"The sheer amount of information available in one single interface is valuable. Everything is there. It is also a lot of work to maintain all the information, but generally, you can find everything you need within this one tool."
"The portfolio management gives you a view of all the projects as well as all the information about the total amount of effort, time, and cost being spent on the projects. It gives the organization how much money and effort should be spent towards projects so they can budget and do better capacity planning in the next fiscal year. It gives them visibility into their resources and if they have capacity."
"The overall interface is very easy to use. It puts together strategy and execution across all your investments."
"Another good thing is that we can create custom reports, which is great. If I created a custom report, a tile that tells me how many people have logged in today. We currently have a little under 2000 users, and that's only users, we actually have integrations, that we created a custom form that sends hours directly to Planview. They're not using Planview directly, but they're sending their hours to Planview through an API."
"The solution is quite expensive."
"We would like to see integration with other products, such as being able to use our workflow with SharePoint and Microsoft Office."
"MEGA HOPEX can improve process simulation in the BPA module. If the solution was better we would not have to use another solution for this purpose. Simulating scenarios in the future for the to-be processes is in demand. If we can have the simulation engine built inside MEGA HOPEX, we would not have to purchase another license or solution to integrate them with each other. This would be a great improvement."
"Lacking more out of the box integrations."
"An area for improvement in MEGA HOPEX is its vast learning curve. The tool is also heavy, so that's a pain point. MEGA HOPEX is also tricky to use if you don't train for many hours."
"In my experience, I've encountered difficulties with consuming custom packages in MEGA HOPEX, which leads to redundant work when deploying them to production. This is an area where improvement is needed. While version six offers better UI and UX, resolving this issue should be a priority. I believe it's important to fully explore MEGA HOPEX's capabilities before suggesting new ones."
"The initial setup is a little complex."
"Scalability can be a problem sometimes."
"There can be improvement on the sense of urgency because a lot of times we've exhausted everything that we can, and now, we're reaching out. So, it isn't a, "Well, have you tried to reboot this?" We've already done everything. Once we put in a ticket, there should be more of a sense of urgency on it."
"Being the IT development manager who implements the upgrades for Planview, I would love to see more thorough testing of expenditures and more thorough testing in general. When we do an upgrade, we have to do quite a bit of testing because we can affect the bottom line."
"One of the reasons why we've upgraded so many times is because of performance standards. We've just run into issues where we've had performance problems. Maybe they are not upgrading, but they're adding more horsepower. Then, we do go upgrade and lose that horsepower, which is frustrating from my perspective as an admin to lose that horsepower. Hopefully, that'll change."
"The resource area needs improvement. The improvements that have been made recently in the later versions have been good improvements, but I think there are some more improvements needed there."
"It is not an end-user-friendly product, and that's really the biggest thing. The hardest or the biggest hurdle I've ever had to face was adoption. I did the installation of the HP product in 2011. The company used it from 2011 to 2015, and the adoption was very high. When I was given the Planview product, adoption was very low. It wasn't as extensively used. We actually had people who wanted to go back to HP PPM because the interface of Planview was so broken, and it still is to some degree. So, it is not user-friendly. It doesn't flow the way a project manager thinks. What we did with HP PPM was a lot more manual programming. It wasn't as nice in terms of the interface, and it wasn't as pretty, but you could design it and build it so that everything flows with the way you worked, but Planview doesn't quite do that. There are a lot of screens. You have to jump back and forth. There are so many different places you have to go to just to do some basic tasks. That's the biggest thing that has really hindered adoption."
"I think the capabilities are there, but it seems difficult for me to even create a report as I am not a Planview technical expert. It is not particularly intuitive. It slows us down in reporting the big picture to management."
"It is a bit of a rigid system."
"Our challenge will be this tool is complex. It is not necessarily easy to start and learn from the beginning. How do you get people who are not professionals to adopt it, use it, and not be mean about it?"
MEGA HOPEX is ranked 4th in Enterprise Architecture Management with 36 reviews while Planview Portfolios is ranked 12th in Enterprise Architecture Management with 63 reviews. MEGA HOPEX is rated 7.8, while Planview Portfolios is rated 8.0. The top reviewer of MEGA HOPEX writes "Easy to use and robust with good features". On the other hand, the top reviewer of Planview Portfolios writes "Helps prioritize projects, share the big picture with management, and has a great planning capacity". MEGA HOPEX is most compared with Sparx Systems Enterprise Architect, LeanIX, ARIS BPA, Visio and Avolution ABACUS, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, SAP Portfolio and Project Management and Planview ProjectPlace. See our MEGA HOPEX vs. Planview Portfolios report.
See our list of best Enterprise Architecture Management vendors.
We monitor all Enterprise Architecture Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
