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."You do not need to be a professional of enterprise modeling to contribute to the enrichment and improvement of the enterprise repository."
"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."
"Its availability is very good."
"It generates friendly websites and presents specific views of the enterprise (business, functional, applicative, technological, and infrastructure)."
"We use the portfolio management feature heavily."
"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."
"The platform is stable."
"The solution itself was easy to use."
"The most valuable features are scheduling, resource management, and, from a project perspective, the functions like issues that change orders. They are valuable because, from a project management perspective, we use the workflows that we build for project management and do active risk management and issue management for the projects that we want for our agencies."
"The most valuable feature of this solution is the completeness of the standard, underlying metamodel."
"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."
"When it comes to managing project plans, Enterprise One is awesome at enabling us to see what stage work is at. I've always thought it was awesome because it's good whether we're doing a traditional WBS or we're linking in epics into projects that are supporting the programs and the strategies, I've always thought it was an excellent tool."
"The look and feel of it is pretty clean."
"We've brought our portfolio altogether. We have had multiple ways of reporting out what our portfolio is, whether it's in Excel, Word, or in different places. We brought all of our projects together in one place. That has worked out well for us. We've been able to manage the work on Gantt charts and our resources better. The big thing for us on research and development is around managing people's time, on which projects they are working on, and how much effort does it take to launch our projects."
"We provided whatever feedback we had to the Planview team, and they went in and built those additional features that we requested. For example, they created a great way for our users to search for a specific resource, project, program, or role. We were not using some of the features, and we wanted them to not be visible, and they helped us with that. They also brought a feature to provide visibility into when a resource was never assigned to any task. There was no visibility to this before. This feature was really very good for visibility into the resource portfolio."
"The biggest impact has been the visibility into our IT assets."
"The features are limited. I'm hoping in the future the solution will be bigger and include more items. Right now, overall, it needs more."
"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."
"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."
"The initial setup is a little complex."
"They do tend to push people to their professional services, instead of helping the customers with their problems. I understand this is their business. At the same time, however, they need to work on fact sheets or offer some program to help the customers who want to implement it themselves and to make it run properly in their environment."
"I cannot recall coming across any missing features."
"We have a very close relationship with MEGA representatives in Mexico, and we ask them why they don't offer impact analysis. For example, we have a server in the center and provide the client a view of what's in the peripheral area, like one cluster, application, process area, and services. We want to offer our clients that level of visibility with HOPEX."
"It would be great if this solution could integrate with other tools such as ITSM (ServiceNow) or CMDB."
"Support is still a challenge. We find it challenging more due to the responsiveness and getting a case or ticket assigned to an analyst. That's what I was just doing. I was following up on an email that we opened last week. We haven't heard anything, so following up on that."
"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."
"The out-of-the-box reports, as far as I can tell, are weak. We've had to build a lot of reports using Power BI, which we connected to it."
"Visualization and reporting areas could use improvements by having canned reports."
"The solution is stable. However, it's so robust, there's so much data, that it has the tendency to lag."
"The number one thing that needs improvement is the UI. It should be easy for a casual project manager. It should provide customizable screens that can be a choice for project managers to choose as a professional level, medium level, and a very easy level."
"We are not very happy with the customer service. This is one of our main pain points. It doesn't cover the entirety of customer service, as there are reps who are really great and we've had good experiences. Many times, we've had people give us attitude, there was a delay in the response, or just a lack of interest. This got to the point where if there was a problem, we would rather try to solve it ourselves then call customer support."
"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."
MEGA HOPEX is ranked 5th in Enterprise Architecture Management with 36 reviews while Planview Portfolios is ranked 11th 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, Avolution ABACUS and Visio, 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.
