My primary use cases for this solution are:
- Time reporting
- Portfolio management
- Capacity planning
My primary use cases for this solution are:
Enterprise One has improved my organization by enabling us to stop committing to work that we can't do.
The most valuable feature is capacity planning because only Planview does that.
The resource capacity and availability have helped us to manage work by preventing us from starting work that we cannot consume.
It gives us flexibility in configuring assignments. We can do both Agile Teams and non-Agile Teams. This flexibility affects our ability to meet our company's particular needs by allowing us to work in a hybrid model, some Agile Teams, and some non-Agile Teams.
The solution out-of-the-box that we established was insufficient. We had to purchase and set up OData. I don't believe that it's a great solution out-of-the-box but eventually you can get there.
It does not provide end-to-end work management for the full spectrum of types of work in one tool. It also does not help with the prioritization of projects through alignment with strategic objectives.
The portfolio creation user interface needs improvement. It's not intuitive, from a user experience perspective. If you've never used it, it doesn't click here and then the next thing opens, click here, then the next thing opens. You get all the features upon opening to create a portfolio.
The request screens, the request process, and the workflows have a poor user experience also. The workflows are definitely not intuitive. You're clicking links and going back and forth. It's way too many clicks and it doesn't make sense. It's not intuitive. On the request side, it hasn't been updated in a long time and it's the entry point for all of our work. It could provide more data value than it does today.
I have been using Planview Enterprise One for 15+ years.
The stability is fairly high. The only problem we've had so far is that for whatever reason, Friday morning, the page load is ridiculously slow. I don't know if that's when the staff is doing updates or what, but Friday mornings are very slow.
I'm not worried about scalability.
We have about 450 project managers, resource managers, team members, leadership viewers, and power admin users.
There are two staff members for maintenance. They both administer maintenance, consult on new capabilities, and develop reports and new functionality.
We're only one of 20 lines of business in the organization and we're the only ones currently using the solution. Within that number, there is around 20% adoption. Time reporters have to report time, but I don't know that I would consider that. They do it, but that's not a tipping point. We do have plans to increase usage. We have a proof of concept with one department outside of ours.
I'm unimpressed with technical support. When my folks call or email they say if it doesn't do whatever it's supposed to do out-of-the-box they can't answer a question and we end up back with some solution consultant.
I did not enjoy the setup process. It comes with a set way of thinking that is sometimes limiting.
We started the last deployment in June of last year and we deployed early November. Employees started using it a hundred percent in December of last year.
We used a consultant from Planview for the deployment. They went above and beyond, but their approach needs upgrading.
We are seeing the start of ROI. We have additional capability. It didn't save us money at all, but it gave us new capabilities.
I like where they're headed with the whole FLEX model. Your license gives you access to whichever tool is the one that makes sense on the Planview platform. That was a pleasant surprise. That has not been their approach over the 10 years I've had exposure to them.
We also evaluated PPM Pro and prior to that, in another organization, I evaluated CA and PPM Pro before it was owned by Planview. We have applications of Workfront, WeTeam, Trello, Azure DevOps, and various things.
Enterprise One's sweet spot is people, work, and money. They're pretty much the only one that can do that hat trick. If you want that, you have to get them, but we don't use it for any team capability. It's too cumbersome and the user interface is still lacking.
My advice would be to discuss your data upfront before you agree to an implementation. See what it looks like to have the data you need and what sort of costs would be required to do that from the very beginning. Then, see not only how will you visualize and record that data but how will you migrate data. That cost us a lot of time and delay in the user adoption because the migration of data was manual.
I would rate Enterprise One a six out of ten.