What is our primary use case?
The primary use case is portfolio management. We're looking at the business unit portfolio and health of the portfolio as a whole. We are not just looking at projects on time, but capacity management for resources, and on the financial side, if we're on budget.
How has it helped my organization?
It brings visibility into capacity, how that affects our projects, and having the whole portfolio be able to see everything at the same time, then talk about it.
One of our guys actually has a great quote that I use, "Planview Enterprise One isn't a tool that takes away communication. It actually increases the need for communication." It brings people to the table to talk about more things because we have transparency in all of our stuff.
What is most valuable?
I like that everyone is able to see the same data. All of our users who aren't just time reporters have read access to all the data that is out there. So, it is one source of truth where everybody can go in and see the exact same data that everybody else sees. It is transparent.
To see work, resources, and ICPM and those different cuts and views is very beneficial for us if we just want to focus on resources. E.g., here are all the resources, but here are the projects that they're working on. If we want to look at the work, then we can look at the work and can bring in the resources. Being able to slice and dice that way is really good.
What needs improvement?
- The cost of other pieces and integrating them in.
- The response to certain issues that pop up.
For how long have I used the solution?
We just implemented it in March.
What do I think about the stability of the solution?
It has been pretty stable.
How are customer service and technical support?
When we put in tickets, they are responded to them as quickly as possible.
There is improvement there on responding back to customers. On our side, we've got quite a bit of experience in tools and systems like this. Normally, when we are putting forth a ticket, we know that it needs to be escalated.
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.
Which solution did I use previously and why did I switch?
In 2006, we engaged Clarity. We were using Clarity. We had just gone through one merger. We were completing another merger while we were trying to implement a tool: two different banks, two different cultures, and one new tool. The implementation wasn't that successful. So, we had a system that was too robust for what we needed. We sort of needed what was now called a low code common language type tool.
We ended up building our own. From building our own tool, we made changes to that, and rebranded it. Then, we made changes to that, and rebranded it.
One of our CIO's big things was we needed a tool that will be able to facilitate our evolution into automation, Agile, and everything else. That's how we came to Enterprise One.
How was the initial setup?
The initial setup is more straightforward for us because we've had other tools in the past, so everything is there. One of the things that we're excited about with version 18 is the configuration: Some of the entry points and user experience will be a lot better when we can collapse certain information. The clean look and feel of it will be really nice.
What other advice do I have?
The product is flexible. We have someone on our team named Allison Cobb who is our Power BI and reporting specialist. She went in and learned the whole schema of Enterprise One to where we have more flexibility than others because we can see certain things, and go, "We want to put that in a dashboard. We want to be able to use that in a different way."
I would give it an eight out of 10. The reason why I would give it an eight is what's being brought into the suite of Planview. The integrations that you're going to be able to do with Planview with LeanKit. All of these things, it's really forward thinking on, "These are all the different pieces which are needed to move forward." All of this is great.
Which deployment model are you using for this solution?