Try our new research platform with insights from 80,000+ expert users
PPMS Manager at a pharma/biotech company with 10,001+ employees
Real User
Offers a lot of flexibility for assigning resources and budget monitoring and planning
Pros and Cons
  • "Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool. It affects our project management because our project management uses Planview to monitor their daily work. Every night it loads our SAP system and then they monitor the daily work. They use Planview as a full planning and monitoring tool."
  • "The outcome management and work resource management in terms of teams needs improvement. Team handling, how team requirements are generated, and how the resource managers can work with teams needs to be improved."

What is our primary use case?

At the moment, we use it for work and resource management modulesmainly in the area of R&D. In addition we started using the modules Planning and Outcomes in several areas for solution and program management.

How has it helped my organization?

With Planview we got  more transparency in the resource utilization and the budget ussage. Planview gives us the insights where we spend out budget and how we can improve the utilization of our internal resources. 

What is most valuable?

The most valuable features are: 

  • The resource management
  • Outcome management
  • Work management

It helps us to see resource utilization and resource needs. We get more transparency out of the system to plan the resources and resource skills to train our resources or support the long term onbording process.

We can see the budget spend for a product or release with the outcome area. We can also monitor what we have planned against what was spend, to monitor how good the programs or project is running.

The view into resource capacity and availability helps us to manage our work. It helps us with resource management and when we see have available resources we can easily start new projects. If we see with the tool that there not enough capacity available we can prioritize projects and programs according to our resources and the business needs.

In terms of reporting, we're mainly using Power BI connected to Planview data and we generate our own dashboards. 

Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool.

The system has helped with the prioritization of projects through alignment with strategic objectives. Enterprise One is the only offical place for our projekt data and in this way it gives the portfolio management back the data of the projects for prioritization and monitoring. 

Enterprise One provides a variety of types of resource assignments for assigning work to people. There are a lot of possibilities for the resource management. There are some improvments in the area of agile team managment and team assignment which could be improved in the future development of Enterprise One.

What needs improvement?

There is improvement space in the handeling of agile teams and team assignments in the work planning and the resource reservation. 

Buyer's Guide
Planview Portfolios
November 2024
Learn what your peers think about Planview Portfolios. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.

For how long have I used the solution?

My company has been using Enterprise One since 2016.

What do I think about the stability of the solution?

Up until the last few days, it's been very stable. It's been stable but slow for the last few days and last week we had some connectivity issues. 

What do I think about the scalability of the solution?

The scalability of the system is really good. You can choose which module you want to use and it is possible to make a seperate role out of the different modules.  

Enterprise One is able to be adapted to the already established processes and could be confugured in different ways. 

The main useres users are data stewards, scrum masters, some project leads, finance and resource management. 

How are customer service and support?

The quality of the support depends on the technician you get. Overall the expirence is really good and if there are second level support needed it is available same as the correct contact in the product management. Planview customer service is really good and is cutomer centric.

Which solution did I use previously and why did I switch?

Before Enterprise One, we had some solutions which we can't use further. 

How was the initial setup?

With the consulting team from planview it was a good process but sometime due to our business complex to get our work processes into the system. At the end of the configuration process all worked well

What about the implementation team?

We implemented direct with the planview teams.

What was our ROI?

As Enterprise One gives us more transparency we can use our budget and resources better and trough this the ROI is given

Which other solutions did I evaluate?

Yes we have one in 2015 an assesment with several tools and than decided for the best tool for us.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Planview Administrator and Robotic Process Engineer at a financial services firm with 10,001+ employees
Real User
Provides end-to-end work management for the full spectrum of types of work in one tool
Pros and Cons
  • "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 content management definitely needs to improve. We don't really use content management for projects inside Enterprise One. We have actually switched to a SharePoint site. We have a feed from Enterprise One every night of all the projects that are created."

What is our primary use case?

We use it for contractor and associate contracting which reflects directly to project resource, "our spend". We do a calculation based on the vendor that the contractor is through, as well as each associate has a per hour rate that is applied to the project to attract the spend applied to that project from the resources. 

We also track the number of hours spent per application. Every application in our bank has the application code that we tied back to Planview so that we can track and see how much time is spent within the application, either with upgrades, maintenance or break-fix type of situation and also to report. It's primarily for tracking reporting.

How has it helped my organization?

Enterprise One has improved my organization with the ability to look at the hours that people track. Prior to Enterprise One we didn't have any estimation model. As we grow within Enterprise One, we're able to pull reporting to see how much time it takes for each individual person or a team to perform a task to complete a project. So with that, we're able to start building that model to estimate the approximate number of hours for each task so that when we provide that to project managers, it reduces the amount of time building the project plan because they've already had that base model to use for each of those tasks. It's created our ability to forecast how much time it would take to perform specific tasks that are very similar to each other. 

It also improved our communication. Prior to Enterprise One, there was not that much communication between project managers and resource managers. So that when a project manager went out to Microsoft Office or to Microsoft Project to schedule a resource for a task, which they actually didn't, they have to have a separate spreadsheet. They would put down a number of hours and it was just a guess. A resource manager would then come back and say, "They can't do that." It was very back and forth. It wasn't like a synergist, a single point of information where everyone looking at the same thing, it was back and forth. So with a project manager entering just random hours and just guessing to get a specific dollar amount or to fit a specific dollar amount it was a lot of work on the project managers to try to adjust it to fit in with that dollar amount.

Now, with Planview, with them being able to see as soon as the project manager submits a request for some hours, the resource manager can communicate with that project manager instantly and say, "It won't do that. It's not going to take that much time". And then when it comes back where the resource is actually entering the hours on the task, there's an exact number. So it's hard to put a number on how many hours were saved or how accurate it's going to be because we're still growing. But prior to this, the accuracy was really, really off. It was terrible, but now we're getting more and more accurate where we're in the, I would say, closer to 70% accurate on the estimations. So it's getting really close to being very accurate.

Enterprise One helped with the prioritization of projects through alignment with strategic objectives. We use what we call Roadmap, Roadmap items under the planning and capacity section. We're the best at the capacity section. With the Roadmaps, our department heads are able to categorize the project by rank. By ranking those we're able to, especially during this COVID period, we've seen so many projects get pushed down to the bottom or completely removed due to the inability to complete those or the return on investment not being there. It really helped a lot with that planning, investment, and capacity planning.

In terms of the flexibility of configuring assignment, my other administrator and I actually came up with that solution. We decided that was the best way to go primarily because at the state that we are in our company, the project managers weren't mature enough to utilize allocations and the resource managers weren't mature enough to reject or approve those allocations. And that was causing people to be over-allocated because they weren't charging time. Because it the estimation on the number of hours needed was completely off. They were just putting however numbers in there. The resource would show over-utilized 1,300%, 1,300% and it would just throw off all of our reporting.

We cracked down on it. We had people to start utilizing the utilization percentage. Making sure that they had that communication line with the resource manager since we have our estimate as growing. But with the reserve and authorization, being able to authorize an entire team to a specific task and reserve them, allowed us to easily create the schedule that works best for that agile environment. Especially with the specific number of hours used for each person that was really easy to use those types of assignments.

What is most valuable?

We have different groups that use it for different purposes. There are project managers who use it in place of Microsoft Project. So they track their project through its phases, their financials, keeping on schedule, on time, and on budget. Our resource managers use it primarily to track their resources, to see how much capacity their team has to perform different tasks or different projects, and how much time they're spending on each individual application. Technology managers actually represent the overall group who use it to roadmap, outlook,  see what's down in the pipeline, what team has what capacity to actually take on a task, see if that project is worth the money, that return on investment is worth actually doing it. Executives are just in it for the reporting to track the financials, to see how much we're spending within the technology and enterprise operations departments. Enterprise One is useful in many ways. We have a little bit under 2,000 people using it.

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 2,000 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. We have over 1,500 contractors overseas and within the United States, that submit their time to Planview, so we can track their work in their project as well. In total, I would say the amount of user input for Planview would be close to 3,000.

Inside Planview, they have what they call a "lifecycle". It's basically a workflow, it's a set of steps that each project has to go through, and with its customization, being able to match our own project process, we match it one for one. And so we can see at each stage of the project where it is either through the gate, from gate zero through gate four, and even with Agile, being able to iterate through that same gate, by using scripted dialogues, or exit scripts, we've been able to track projects exactly where they are. Each schedule can be tied back to either the hours entered, by either date, or a percentage of the effort completed on it, so it ties together pretty good.

It's being used a lot for the remaining effort. We actually create tons of reporting off of it. We've created multiple Power BI dashboards. Data feed allows us to create our custom Power BI dashboards, so that way we can track what efforts been used, what efforts are remaining in a very graphical, easy to read way. We've created this primarily for the project managers and resource managers. My manager has a breakout session that discusses our Power BI dashboards. It's really nifty for tracking that. We use it a lot. Our executive challenged us to be able to forecast and estimate hours used on each task. That's why we implemented Enterprise One initially, but we since provided what she wanted and now we're providing more. Initially, it was just the requirement and now we're exceeding that requirement to give better visibility to all resource managers and project managers.

We have a really large organization, 22,000 associates total, including the 3,000 people using Planview. Being able to group projects into portfolios based on specific filters, either the project manager or any other approver organizational hierarchy, once you set your portfolio, you can either share that with your team or whomever so that they can all be on the same page. With the Power BI dashboards, we have a very open information model where we want everyone to be able to see the same thing. There's only one section where it's confidential and we as administrators have to provision that separately, but everything else is open for everyone else to see. So if you're just a time reporter or just have a reporting, you can go in and see the same information as a manager. Being able to group projects in the portfolios, filter them, and being able to see all of that data graphically using the Power BI or the standard reporting that came with the FastTrack setup has been very helpful to our entire organization.

For all the work that we perform, Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool. We have our technology projects. We have what we call non-technology projects, which are basically projects that don't necessarily have a technology component in it. It's things like branch opening and closures, even though sometimes they will have the technology, but it just depends. We also have what we call OTW, which is another planned work. This is primarily for resource managers so that they can track their applications like how much time is spent on their applications doing upgrades or break-fix. We also have programs of work, another resource manager tool that tracks Agile programs, and we also have Roadmaps. For all the project types that we, or work types that we have within our organization, it does great.

We just started doing the on time and on a budget since we are in infancy with Enterprise One, we weren't really holding the project managers to that. We were holding them to it through the governance, but not through the Enterprise One. Now that we're a little more mature, we've started tracking that grader as well as being able to use those change requests to track as scheduled, budget, or scope changes. It has allowed us to definitely increase our on-time and on-budget awareness.

What needs improvement?

The content management definitely needs to improve. We don't really use content management for projects inside Enterprise One. We have actually switched to a SharePoint site. We have a feed from Enterprise One every night of all the projects that are created. And once they're created, we run our process that goes out to create SharePoint sites for each project. Because of the inability for drag-and-drop file ingestion, the best thing about it is the versioning, but that's also done in SharePoint. We just don't use it because it's HTML and it's hard to use. It's a little bit more cumbersome than it should and then we like.

For how long have I used the solution?

We implemented Enterprise One initially for our pilot group at the end of 2018 and we went into production last year in April.

We have the cloud solution. It's all hosted. The team that is using it, for the most part, is just the technology area, application development, information security does our technology group. We have some enterprise groups also that are using it.

What do I think about the stability of the solution?

We haven't had any issues with stability. In the previous versions, there were interface issues with Internet Explorer because it's just an antiquated browser. With Microsoft adopting Microsoft more of the Edge and Chrome, the stability is fine. We haven't had any issues.

What do I think about the scalability of the solution?

Scalability is great, with the monthly improvement push, they're on a monthly cadence of updates with the new version 18, the improvements come every month. It's awesome. They have a vast library of API calls that we actually have a contractor system. We're actually onboarding that now and we're going to implement API calls to Planview that way. I have created a multiple UiPath robot that used Planview to create reporting, to add users, to do monthly maintenance, as well as the call API to UiPath. I do a lot of robotic process automation and I can do a lot of the automation with Planview. The scalability, being able to integrate with JIRA, Workday, create custom integrations if we need to, being able to use API calls through either JSON or primarily SOAP, is pretty awesome. I don't have any complaints so far on the scalability.

We're looking to integrate JIRA into our Enterprise One with LeanKit. We're still working out the financials on that to try to figure out a way to integrate that either through a flexible license or through individual licensing. Initially, we started off with technology because that was the executive who decides to start tracking the projects since that's where the project management organization lives, under technology. But more and more enterprise business unit groups are starting to want to track time and see what their resources are spending their time on as well. We're growing slowly throughout the rest of the organization. With the amount of data that the Planview provides and that type of reporting, it's kind of giving other departments and other groups visuals into what they could have by using Enterprise One. We're growing through them. 

How are customer service and technical support?

Technical support is great. It's just like technical support at any other institution where sometimes you'll get someone who is very adept in the system, and then the others are a little less. But, generally with the way that Planview is set up, if we have any issues, we have a representative we can talk to and bail and get the right people to work on it. We've had no issues.

Which solution did I use previously and why did I switch?

We were previously using a homegrown SharePoint site that we worked with our SharePoint team to build. It didn't have a nearly as robust workflow, reporting approval ability, and tracking as Planview.

How was the initial setup?

In terms of the setup, I actually got hired on in the middle of implementation, but we had a Planview representative on-site performing the configuration. She basically did training while we were there so I was able to pick it up really quickly and become adjusted to building or configuring the system through configuring screens, scripted dialogues, and the lifecycle. It was really easy. It seems like a low-code solution, so it was really easy to pick up.

I would estimate the setup took from July to December. That is when we did the primary build-out of all of the integrations. We had a previous system that was homegrown through SharePoint that we had a lot of projects and data in. We had to do a lot of data manipulation in order to put it in a format that's ingestible by Planview. That took a little while too. I wrote a robot that would automatically convert all of the data over to the new data format, and we were able to send that to Plan B to have them import it.

The big parts of the strategy were just integrations with our financial system. We have a general ledger financial system that we had to integrate with and that we had to send a file over to Plan B to enter that information. We also have a Workday integration for resource management. That is a pretty nifty one where whenever the Workday feed comes over, it either removes resources, adds resources, and creates users based on if they're in a specific hierarchy of the bank. That was really nice.

From our end, it was primarily just me and my teammates working on the deployment. We were the primaries. We actually had one other resource through application development that was helping us. That was primarily for the deal integration. The Workday was just a file feed, and that was all in Planview. My colleague is also a Planview administrator. He doesn't do the robotic automation, but he does a lot of the architecting of the system.

For management, at this point, it's just me and my teammate. We have one other person who is specialized in the reporting. They do a lot of the SQL queries, SSRS, and Power BI setups, but they don't do really much of the administering of the system. 

What about the implementation team?

We only worked through Planview. We didn't work with any other third parties.

What was our ROI?

The area with the most ROI is our ICCMO, being able to track that on time and on budget, all of the resource managers. Those are going to be the department heads for each of our technology departments. They would be the ones that would see the most return on investment. As well as tracking their contractors and the hours they're spending on the applications.

What's my experience with pricing, setup cost, and licensing?

The pricing and licensing are fine, but with the model we currently have, we don't have the FLEX license just yet. We actually have the tiered based on the access side from just a team member to project, we call it portfolio manager to admin. The pricing is fine. That was one of the solid points for switching to Planview. There are additional costs for integrations.

Which other solutions did I evaluate?

We actually did an RFP. So we looked at the Gartner quadrants and we had other people provide proposals. But with all the requirements, Planview was the only one that was able to provide all of the items that we needed which is why we went with them.

What other advice do I have?

The biggest lesson learned would be regarding making sure to have Planview do the training. When we did our training for our organization, we did a train the trainer where Planview came in and trained just a few people in our organization and then they went out and trained their people.

But it's like a game where you tell one thing to a person that you pass it down the line and it gets changed by the time it reaches the very end. If you have the budget for it, have Planview perform the training because I think that would increase adoption a lot easier. We had a lot of people who came from different areas that had different methods of tracking projects from Visio Excel and Microsoft Project. Getting everybody on the same page to Planview we had a lot of contention and a lot of people who didn't like the product initially. And that came down to me to training. With the trainer themselves not being very familiar with the system, being unsure about what they're trying to train the other people on didn't give the other associates much confidence in the system initially.

The adoption was a lot slower than we wanted. I think that if Planview had worked to perform the training, it would have made people a lot more of a point of contact to reach out to. And having a lot more acceptance and what they were being taught. So that would be the lesson learned.

Especially if you're an administrator, go through the advanced training if you're doing FastTrack and if you're doing the configuration so that you'll be more familiar with what the consultant is doing. Our consultant was great. She did a lot for us, but we also saw afterward, once we became more familiar with it, we saw a few errors that needed to be corrected but they were easy and we were able to fix them ourselves. If you don't go through advanced training, you wouldn't recognize it. 

I would rate Planview Enterprise One a nine and a half out of ten because nothing is perfect.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Planview Portfolios
November 2024
Learn what your peers think about Planview Portfolios. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Senior Engineer at Northwestern Mutual
Real User
Provides visibility into our IT assets. However, there have been some interruptions in service.
Pros and Cons
  • "The biggest impact has been the visibility into our IT assets."
  • "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."

What is our primary use case?

We use it to help us manage our IT assets for our company.

How has it helped my organization?

We've heard many heard sound bites from other areas where, five to seven years ago, they did not have this type of visibility into the IT assets for the organization. As it is now, we work with multiple teams who ask us for these different types of information. None of which would have been possible without having an application like Enterprise One.

The biggest impact has been the visibility into our IT assets.

What is most valuable?

Some of the most important features that we find are the ability to relate assets to one another (applications to software and hardware) and associate capabilities to each of our assets, as well as to whom the users in our user base are, whether they're internal/external customers and which departments. From this, we can create reports which can help identify for a particular department the applications that they use or own. Then, from there, the capabilities they offer.

We do find the solution flexible. Having the ability to make customizations to the product offers a great deal of flexibility to buy business requirements as well as meet the needs of our clients and customers.

What needs improvement?

The product can probably improve in a couple areas: 

  1. 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. So, that's one area of opportunity.
  2. I would like them to be more product-focused with the continuing evolution of the product. As companies transform the way they do IT asset management, the product should continually change with it as well.

What do I think about the stability of the solution?

We do have some interruptions in service for one reason or another, but a majority of the time, it seems very stable.

What do I think about the scalability of the solution?

We don't scale. We don't have a lot of users, just in the hundreds, even though our organization is in the thousands. 

It seems fairly scalable, particularly as our organization is in the cloud.

How are customer service and technical support?

We interact with technical support quite often, whether it's deployments, bugs, or errors that we run into. We work with them on a fairly regular basis, whether it's just typical deployments or if it's actual issues that we run into. Most of the time, it's on the Planview side, whether it is an outage or some performance issues. Occasionally, it's something that we introduced.

How was the initial setup?

I was not involved with the initial setup.

What was our ROI?

Our ROI is the visibility and relationships between our applications and software with one another along with the ability to tie capabilities and assign owners to identify individuals who are related to the assets. In a lot of cases, different areas of the organization have different needs. They come to us for information regarding different IT assets, and we're fortunate enough to be able to provide that information from what we've captured and placed into the Enterprise One application.

What other advice do I have?

I would rate the product a seven out of 10.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1208529 - PeerSpot reviewer
Sr PPM Administrator with 5,001-10,000 employees
Real User
Provides the ability to see your resources and what they're working on in one place
Pros and Cons
  • "With the lifecycles, it helps us step through our processes easier. We'll take a process and create it in Visio, then we'll go and implemented in Planview. Anytime that we have to do a new process, this is what we use. We just step it through the lifecycles and the configure screens are very easy to use. The fields that you need are easy to use."
  • "I would suggest for the request module that they open up the fields and columns so it's like we are doing our work in the work module. You can't do that with today. We also have to make sure that the fields can go both ways with the request and work modules. Including fields in the column sets would be helpful, because today they only use attributes."

What is our primary use case?

Our company has a PMO, which they use to intake their projects. They use the request module and do a process for the steering committee before its turned into a project. Once they turn it into a project, the project managers take it over and work the WBS all the way through to the end of the project.

The product is deployed on the Planview cloud.

How has it helped my organization?

With the lifecycles, it helps us step through our processes easier. We'll take a process and create it in Visio, then we'll go and implemented in Planview. Anytime that we have to do a new process, this is what we use. We just step it through the lifecycles and the configure screens are very easy to use. The fields that you need are easy to use.

With the prioritization that the company is getting into, it's easier to do that using this solution, including a ROM. Normally, the ROM is done in the work, but we put it in the request module. You don't have to have an in-depth ROM. You don't have to create a project, we just do it in a request module today, which has been very helpful.

For the delivery, we can tell when a project will be late, so the PM can find out why. The PM would have to tell management why it's going to be late, but they can see that right off because they do weekly status reports. So, they don't have to wait to get a status report. They can just go in there and look. Also, with the reporting capability, where they can do the subscriptions, they get it every Friday.

Resource managers can see their resources. They try to do things on their own, so that is good. Today, we don't have high-level resource management, but we are going to start doing that. We will start having demand or resource meetings to see where resources are available. However, we are still developing that. 

We don't have that today, but I worked at other companies who used Planview and saw where resources were available, scheduled, and short. It was very useful. We would meet every two weeks to view resource management. We would just sit in a room and say, "These are our projects. These are the projects that are incoming. Where are our resources today? What are they working on?" So, it was very good.

The biggest impact has been the ability to see your resources and what they're working on. Most importantly is having your projects in one place. We don't have that specifically here at GM today, but we're working towards that. That's our new initiative: Get everything in one place and have one place to go for intake. So, if you have a new request, they go straight to plan B. Once we post a project, they can do that today. We get on reporting for Power BI and the ease of use of Power BI is very big.

What is most valuable?

It's easy to use compared to other platforms that I've worked on, e.g., Microsoft Project. Innotas was one of our contenders, but they ended up buying them, so it's good to see that those features are coming out across Enterprise One. 

  • I love the requested intake.
  • I love how you can do calculations of fields. 
  • We put in the lifecycles, which I love. 
  • Love that you can get notifications within Outlook. 
  • The reporting: How you can do subscriptions of the reporting. So, you don't have to sit there and send reports manually. That's very helpful.

These features save me time. Anything that you can automate is always helpful. When somebody doesn't have to come and ask me, "Hey, can you do this for me?" They can do it themselves, then it's easy to use. You can show them one time, and they go through it the next time by themselves.

It's flexible and very easy to use. Just having all of our projects centralized and all our programs in one place so we can see what the PMs are working on. Now that we've gone global, we can bring in the other PMs and PMOs easily because we've already configured stuff. Although, they may have things that they're reporting on, we can easily integrate those into our current system. 

What needs improvement?

I would suggest for the request module that they open up the fields and columns so it's like we are doing our work in the work module. You can't do that with today. We also have to make sure that the fields can go both ways with the request and work modules. Including fields in the column sets would be helpful, because today they only use attributes.

For the multiple fields that you have, there is not a single select field, but multiple selections. You can't use those in column sets today. It excludes those fields when being reported on. So, you have to figure out another way to do that.

It would be beneficial for us if it was able to integrate with other tools and have those tools integrated into Planview, which they're working on. Examples of tools being integrated DevOps, JIRA and Projectplace. Since we're a mature PMO, and not all of our PMOs are, if they can integrate with Projectplace or the Planview PPM Pro, that's good. 

For how long have I used the solution?

The company has been on it for at least five years. I've used it previously with other companies for over seven years.

What do I think about the stability of the solution?

I have never had an issue with the stability of Planview. That's one thing that they can tout very well. Performance issues have not been an issue. When running a report, all I have to do is let them know, and they will expand my timeout limits. So, I've never had an issue with performance with them, not in the cloud.

What do I think about the scalability of the solution?

It's very scalable. We're on Enterprise One, so you normally have to be pretty mature. Where I came from, we were immature. We adapted to Planview and became very mature. I know that other companies can do that too. They start out with Projectplace or PPM Pro, then they'll go to Enterprise One. So, it's very scalable. It's a great solution for scalability.

How are customer service and technical support?

The technical support is very good. I've never had an issue with them. They answer their tickets right away and always come back with a solution very quickly.

Which solution did I use previously and why did I switch?

We moved from another tool to Planview. I don't know what tool this current company was on. I worked for them for 10 months, then I left and I came back. I've been with them since June again. Another company that I worked with, we went from MS Project Pro (the PPM tool) to Planview.

How was the initial setup?

It was more complex because I came from MS Project Pro. Planview has so much more to offer, so you had to consider a lot more. You had to figure out what its capability were, what your portfolio and programs were going to be, what your teams were, how they were structured, and what type of resources you had in what roles. So, there were things that we had to consider, but Planview asks the right questions. They bring that out of you.

We did a test for three months, then we did a soft launch. So, only our PMs were on it, and they brought all their projects over and managed their projects there. We had another tool, where we had to do double-duel entry for time sheets. So, when they ended their time sheet over there, then they started doing it in Planview. That was just to get them used to it, and saying, "We're going to do our time sheets." We were a company that already did time sheets. That seems to be a big thing for other companies. How do you get your people to do time sheets? But if you're doing financials, they're going to do time sheets.

What about the implementation team?

We used consultants, and I would recommend that for everyone. They're very easy to use. They listen to your needs and requirements. They gather them. They've been in the business so long that they understand what people are saying. Some people may want a lot of details, and they'll talk them down from that by saying, "Do you really need that? Let's start with this, and then we'll see. Does that give you what you need?" So, they're really good about listening to the requirements and providing what you need from the beginning.

When you talk to a consultant, make sure you know where you are, how many users you're going to have, what number of projects you have today, where you think you're going to go with it, and what are your pain points. 

Know your pain points, and definitely tell Planview what your pain points are, because they'll have a solution for them, whether it's reporting, which is real big, or just the ease of use. Everybody is so used to using Microsoft Project, but it's really not that different from Microsoft Project. You just have to use the tool, like Word or Excel, and the more you use it, the better you get at it. It's a very good PPM tool.

The learning curve is not steep. They have very good training and a lot of people. My recommendation is when you take on Planview, get the training. Have trainers come onsite and make sure you budget for that. Make sure you budget for consultants to come onsite and train your people. Don't try to do it yourself, let them do it.

What was our ROI?

I think our company has seen ROI. If you can see where all your projects are, what type of projects you have, what resources that they're working on, and finally, where your budget is. That's a win-win, all the way. 

What's my experience with pricing, setup cost, and licensing?

We have unlimited licenses for all of our functionalities. Since we went global, we went with that model.

Which other solutions did I evaluate?

We evaluated MS Project, because we thought we going to stay with them. We evaluated Planview and Innotas. There was another minor one too and we want to be more mature than that. Those were the main ones that we evaluated.

We chose Planview probably for the centralization of all the projects, ease of use, views, and the configured screens were very easy to use. Ours was more about resources, knowing where your resources are, for example:

"What projects are you working on?" 

"I'm over here working on these five projects." 

"But they're not on my list!" 

This solution is just about able to see what your resources are working on and having all your projects in one place, even team schedules.

What other advice do I have?

We do not use the solution’s Lean/Agile delivery tools yet. That's one reason why we were looking at this heavily at the conference. They seem to be really focused on that, which is good. A lot of companies that I talked to seemed to be struggling with it, so it's good to see that Planview is trying to move into that direction, taking everything with it.

Today, Planview does not help connect funding and strategic outcomes with work execution because we only have one PMO which is using finances. I don't think that they're doing a capital budget yet, to say, "These are the projects that we're going to work on." But, as we've gone global, we will start doing that. So, it'd be very beneficial. The other company that I worked for, it was very highly used. We forecasted constantly to see where our budgets were, what our capital budget was for that year, and what projects we were going to work on at the beginning of the year. That was good.

There are so many different functionalities within it that you don't have to take in all in one day. You can just grow with it. So, that's what I like about it.

I'm always a person who will never give anything a 10. I would probably give it, compared to other tools, a nine (out of 10). I would've given it an eight (out of 10), but they've made improvements this year. So many good things are coming out, and they really listen to the customers. I'll give them a nine for that.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Supervisor ITSP EPMO at a energy/utilities company with 10,001+ employees
Real User
The sheer amount of information available in a single interface is valuable, but its reporting and analytics could be improved
Pros and Cons
  • "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."
  • "Its reporting needs to be improved. My main complaint when it comes to Planview is that it is good to maintain all the data but to actually use the information that is in it, you actually have to use a different tool. We use Power BI. So, we pull all the information, and then we use a Power BI dashboard to stage or look at the information."

What is our primary use case?

We have a portfolio of 81 projects that are all related to IT. I work for an oil and gas company, but my customers are IT. So, the use cases are related to the active projects that we're currently running through the organization. We have CTOs that are working on it, so we use it for capturing time and dividing time. We use it for the entire lifecycle of the projects, and we also use it for planning our next cycle, such as 2022 planning opportunities.

How has it helped my organization?

Enterprise One helps with the prioritization of projects through alignment with strategic objectives. It makes conversations easier and leads to more effective communication. Instead of having to go through all the details, we can just look at the tool. We can have multiple people look at the same set of data and then work through and prioritize the list of opportunities that we have, for instance, for next year. We create a subset of data; for example, we create an opportunity before it becomes an active project, and we input all the data. By having standardized data inputs, it becomes easier to compare multiple opportunities because you have all the information at hand.

Enterprise One allows program managers to group work together to see the resource demands and costs at a consolidated level. It makes life simpler. They have an easier overview. To some extent, it is Planview's influence, but then it is also because of that dashboard capability that we have to apply at the backend so that the portfolio managers can look at their portfolios through a dashboard. So, it's not necessarily 100% within the tool, but it has made our life easier. It is a 50:50 contribution of Planview versus Power BI. We are able to drill down into the details underlying the consolidated information. So, we have better data accuracy and, therefore, better metadata.

What is most valuable?

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.

What needs improvement?

Its reporting needs to be improved. My main complaint when it comes to Planview is that it is good to maintain all the data but to actually use the information that is in it, you actually have to use a different tool. We use Power BI. So, we pull all the information, and then we use a Power BI dashboard to stage or look at the information.

I can look at one project to see what its stage is, but it is not easy. I would be able to get the information because it is a part of the work and assignment detail, but it's not something where with one click of a button, I have the information. The information is not too easily or readily available to see the stage of work.

In terms of Enterprise One's ability to create summary reports across multiple projects, 
I can input the information on a project-to-project level. So, I have the information in there for each project, which goes to a central database. However, getting the information out of the tool is not so easy. So, entering the information input is great, but I'm not sure I know how to get the output. I'm not sure if my company knows how to do that. We have a Planview team, but I doubt that they would be more knowledgeable on this particular aspect. That's because they're more data and tool-oriented. They're not for user support. They're more like tool support.

It works for large work efforts, but it is too complex for smaller work efforts. Planview has a different tool that they want you to use for less complex work. They want you to buy both tools, but I don't know how the integration would work. Having to have a second tool for less complex work sort of gives you the idea that the original tool, Enterprise One, is too complex. It should be simpler to use so that I can also use it for less complex efforts.

In terms of forecasting the remaining effort, if it is expressed in dollars, then I'm pretty okay with figuring it out, but when it is expressed in tasks, that information is not necessarily there for me. The timeline doesn't really give me that overview. So, from a financial perspective, it is good. From a scheduled perspective, it is not so good, and from an execution perspective, it is even worse.

For how long have I used the solution?

I've been using Enterprise One since 2018. In our company, we have been using other products from Planview way before that.

What do I think about the stability of the solution?

It is better this year than in previous years. There used to be data issues and duplication issues. The snapshots weren't taken every month. So, the snapshots wouldn't work. There was some sort of MuleSoft software being used that was creating issues last year. This year, generally, we have had fewer issues with the tool itself. That may have something to do with the fact that we have a release schedule. Planview releases an upgrade or update every month, and then our team combines the updates for three or four months and rolls them out all at once. The quarterly update schedule is probably working better.

What do I think about the scalability of the solution?

It works for large work efforts, but it is too complex for smaller work efforts.

How are customer service and support?

We have an operations team within the company, and they work with Planview.

How was the initial setup?

It was pretty straightforward. It sort of takes you through the step-by-step setup, so you cannot really go wrong. The tool itself guides you to the next step.

What about the implementation team?

We probably used a consultant, but I cannot be sure. It was done too long ago, and I wasn't involved.

What was our ROI?

They do ROI all the time, but I don't know if they've done it for the implementation of this tool.

What other advice do I have?

I would advise making sure that your data is up to speed and your data is clean before you start implementing it. That's because once it is implemented, it is a lot more difficult to clean up your data.

Using Planview Enterprise One has made me aware of the sheer amount of data that is there to classify for a single project. When you look at a project, you generally think about the normal stuff such as what is the beginning date and end date, what are the stages, how much you spend, how much you spend per stage or per month, whether it is an actual or a forecast, etc. There are just so many different data points to one single project. I wasn't aware of them until I started using Planview Enterprise One.

I know that Enterprise One has the capability to view resource capacity and availability, but our company is not using that capability to its fullest extent. That's because, in the previous versions, it wasn't there. So, it is hard to get that paradigm shift. People use other tools to look at resource availability. About 50% of our projects run through Planview, and the remaining 50% of projects are managed out of the organization itself. So, they are not necessarily tracked in Planview. So, when I look at resource availability, I always have to look at the general overview. I have to combine those two sources to see how many resources I have available for a certain period of time.

Enterprise One doesn't provide end-to-end work management for the full spectrum of types of work in one tool. It is good for projects, but it is not good for non-project work. At least for us, it does not provide that capability. That's why only about 50% of our projects run through Planview, and the remaining 50% of projects are managed out of the organization itself.

Enterprise One provides a variety of types of resource assignments for assigning work to people, but we don't use it.

I would rate Planview Enterprise One a seven out of 10. I like the tool, but I am looking forward to getting that reporting and analytics part fixed. For me, that's not working right now.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2333736 - PeerSpot reviewer
Cloud system engineer at a consultancy with 1-10 employees
Real User
Top 5Leaderboard
Great centralized platform with robust reporting and analytics
Pros and Cons
  • "Planview Management integrates seamlessly with other tools and systems used within the organization, such as enterprise resource planning (ERP) software, customer relationship management (CRM) systems, and collaboration platforms."
  • "While Planview Management provides robust reporting and analytics capabilities, further enhancements could include more advanced data visualization options, predictive analytics features, and customizable dashboards to provide deeper insights into project performance and trends."

What is our primary use case?

We use Planview Management to assess the current project portfolio, evaluate resource availability, and prioritize projects based on strategic objectives, ROI, and risk factors. 

Planview Management improves an organization depending on how well it aligns with the organization's goals and processes and how effectively it is implemented and utilized by the team. 

Our overall experience was good. Our primary use case is Planview Management. In this scenario, it is to improve project visibility, optimize resource utilization, and drive better decision-making to achieve organizational goals effectively.

How has it helped my organization?

This software totally changed our organization's workflow. Planview Management offers a centralized platform for managing all projects and portfolios. This helps to improve visibility into project status, progress, and resource allocation across the organization. 

What is most valuable?

Planview Management enables our organizations to make data-driven decisions. The centralized platform offers robust reporting and analytics capabilities. 

Planview Management integrates seamlessly with other tools and systems used within the organization, such as enterprise resource planning (ERP) software, customer relationship management (CRM) systems, and collaboration platforms. This integration enhances data visibility, streamlines workflows, and eliminates silos between departments. All other services are sophisticated

What needs improvement?

Enhancements are needed in:

Advanced reporting and analytics: While Planview Management provides robust reporting and analytics capabilities, further enhancements could include more advanced data visualization options, predictive analytics features, and customizable dashboards to provide deeper insights into project performance and trends. 

Enhanced collaboration tools: While Planview Management facilitates collaboration, additional features such as real-time chat, video conferencing integration, and collaborative document editing can further improve communication and teamwork among project teams and stakeholders. 

Scalability and performance: As organizations grow and their project portfolios expand, it's essential for Planview Management to ensure scalability and performance. This could involve optimizing the platform's architecture, enhancing database management, and improving response times for large-scale deployments. 

Overall, by addressing these areas for improvement and incorporating additional features in the next release, Planview Management can continue to meet the evolving needs of organizations and remain a leading solution for project and portfolio management.

For how long have I used the solution?

I've used the solution for six months.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Mark Hillman - PeerSpot reviewer
Global Head of Portfolio Management at a wholesaler/distributor with 1,001-5,000 employees
Real User
User-friendly interface, but the reporting could be improved
Pros and Cons
  • "In my opinion, the financial planning feature is the most valuable feature of Planview Enterprise One."
  • "The reporting is absolutely shocking. It's not good reporting and requires improvement."

What is our primary use case?

We use Planview Enterprise One to capture information about all of our IT projects, IT resources, and financials associated with those projects. We then use information from Planview to understand how we are progressing in plan delivery, what our pipeline of work looks like, and what resources are required to deliver that pipeline of work and the execution. We are utilizing a broad range of capabilities across what Planview Enterprise One provides.

We don't use it for task management, and the work breakdown that we keep in Planview is relatively high. As a result, it is at key milestones rather than individual activities.

What is most valuable?

In terms of features, the financial planning modules are quite good, and they are the ones that are used the most. For us at this stage in our use, the financial planning feature is the most valuable feature of Planview Enterprise One.

What needs improvement?

The reporting is poor and requires improvement.

The tiles and exception-based activities in the application are sufficient to get by. However, when it comes to producing executive reports, MI reports, or any other type of reporting, we must exit Planview and work offline. We have been working with them to improve on that, as well as using some of the Power BI capabilities that have been available for a while, but it's still more difficult than it should be.

In the next release, I would like to be able to use the data in the tool to gain insight much more easily.

For how long have I used the solution?

We have been working with Planview Enterprise One in our company for the last two and a half years. Prior to that, I implemented it in a different organization. I strong level of knowledge of this solution.

What do I think about the stability of the solution?

We are six months behind because we had a few problems when we took current releases. While we didn't do any customization, some of our configurations failed in some releases and required re-work.

What do I think about the scalability of the solution?

We haven't run into any scalability performance issues. We have over 500 work items and 2,500 resources, and it's been fine for us. 

We use this solution across the company's IT and have approximately 250 users.

How are customer service and support?

We've opened a few tickets with Planview due to bugs, defects, or configuration issues. Because it varies so much, I would have to put their rating somewhere in the middle. They are sometimes excellent and sometimes poor. It all depends on the circumstances.

How would you rate customer service and support?

Neutral

How was the initial setup?

The initial setup was straightforward. We took a very quick approach to delivery. It was simple from a Planview standpoint. The questions and approach they used worked well for us. There are no concerns about the initial implementation process. Aside from us being clear on our requirements, the tool itself is fine.

What was our ROI?

We weren't looking at this as purely a return on the investment project. The return is generated by the projects themselves, allowing us to deliver the projects more efficiently. It's difficult to quantify the improved performance of our project delivery. 

What's my experience with pricing, setup cost, and licensing?


Which other solutions did I evaluate?

We went through an RFI and RFP process before going to market. We specified our requirements. We went through a series of presentations from vendors to determine who could meet our needs. And we looked at five, and we narrowed it down to three: KeyedIn, Daptive, and Planview. The process we went through there made it clear that it didn't really matter which tool you chose; what mattered was whether or not you felt the implementation process was going to go well. In addition, we compared user feedback to how well the user would interact with the tool. Against those two key criteria during the implementation process, Planview outperformed the others at the time. Based on user feedback on the UI and usability, Planview came out on top.

What other advice do I have?

My advice would be to be very clear about requirements and the associated value. Planview, like many other tools, has a broad range of capabilities, it does some things well and some things not so well. If the things you want to do are the things it excels at, then use it. If you want to do other things, this is not the tool for you. I would be focusing on the requirements against the capabilities, the core capabilities of the tool, rather than the features that may or may not have been added.

It does what it says it will do, and the majority of it is fairly simple to do. I would rate Planview Enterprise One a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1683516 - PeerSpot reviewer
Vice President, PMO Portfolio Management at a insurance company with 5,001-10,000 employees
Real User
Useful for time reporting and milestone management, but its reporting is not quite what we're looking for
Pros and Cons
  • "We use time reporting. We convert time reporting into financial costs and do contractor and capacity planning for our resources. We track our work. So, that's the module we use extensively. As a matter of fact, we have upwards of 300 open projects at this given moment. It is pretty close to 300 open activities that are working."
  • "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."

What is our primary use case?

We use it for change control for all IT changes in the organization. It is used to do the project work for anything that is changing from the technology perspective. We also use it for forecasting and planning work on the projects. We don't do detailed planning in Planview.

We are using the July 2021 version. It is a cloud version. We use Planview's cloud. They host it for us.

How has it helped my organization?

Having a single source of the truth, specifically with the integration with Power BI, enables us to give leadership more relative content for decision-making. From being just a local project manager and reporting status type of a tool, it is now being leveraged heavily in the executive decision-making process. They meet every month with summary reports that we generate to make decisions.

It has helped with the prioritization of projects. That's a part of the reporting process. From an IT perspective, we've gotten better at the delivery process. We're not, by any means, near great yet, but it is a journey that we're starting. Over the last two years, we've had a lot of adoption because of senior leadership's involvement, and therefore, things are moving more aggressively towards that point where it is more relative to what we do on a day-to-day basis.

It allows program managers to group work together and see the resource demands and costs at a consolidated level. It puts the data that the program managers need right in a single source. However, they don't do capacity planning and capacity management in Planview. So, while they can see their burn rates, the resources that they're using, and the roles that are being leveraged, they don't actually use it for capacity planning.

We use it for high-level milestone management. We use it to see if projects are falling behind. We also use it for change control and financial reporting. Our senior leadership makes decisions based on the data that is reported out of Planview. So, it is used not for detailed project planning but rather for executive reporting and consolidating the information down into manageable pieces.

It definitely improves the change process when things are running behind. When we didn't have a tool or when we didn't use Planview necessarily, data was more or less the opinion of the project manager or the program manager who would then say that we're just going to push this date out. Because there was nothing locked in stone, it was just reported that we're going to make a little change here and a little change there. They moved dates, and everybody agreed verbally. There was no question of you didn't complete on time, whereas now, the system asks about your target date. If you change that target date on a huge project by a couple of days or two or three weeks, it is obvious. Previously, where you wouldn't notice it because there was no real firm tracking mechanism, today, it stands out. When the date goes from January 1st to January 29th, the system shows that as a variance or a change. Now, it is obvious when things move, and you know when things aren't completing on time. With the reporting that we're doing to the leadership team, they can see when things aren't going as planned.

What is most valuable?

We use time reporting. We convert time reporting into financial costs and do contractor and capacity planning for our resources. We track our work. That's the module we use extensively. As a matter of fact, we have upwards of 300 open projects at this given moment. It is pretty close to 300 open activities that are working.

What needs improvement?

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. 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.

We use it for forecasting and planning work on the projects. We are able to leverage the data that it provides to do some more concise consolidated reporting, but we mine the data using other functions. The data is collected into Planview, but its reporting is just not quite what we're looking for. We don't use it to do reporting directly. So, we create data sets or pull the data out of Planview, and to get the data down into a view that leadership can then work with, we reformat it by using tools like Excel, PowerPoint, and those kinds of things. We do quite a bit with Excel. We export the data and run it through certain functions. We deliver that data to different groups for feeding into other products because we don't currently allow direct interface into our financial systems. To eliminate the need for exporting data into Excel reports, for the most part, the Power BI capability will eventually replace the external reporting that we do by using other tools. Power BI interface is a huge improvement in the capability, but it is new in our organization, so we probably have a learning curve there. The SaaS reporting is obviously more complex and less user-friendly, but the Power BI solution has definitely more reporting, and it is leadership-data focused. It easily allows the creation of dashboards that executives can manipulate and work with themselves.

We don't find Planview's guides and documentation extremely useful. There is room for improvement. It is very difficult to find things on their website. There is no easy way to find what you're looking for. Everything appears to be broken and in small snippets of data. When you go to their customer success center sites for documentation, everything is just a little snippet of information. There is no clarity about how something works, and how something should be configured. If you're an administrator, it is even less useful, and it is very vague. We end up spending more time taking that snippet of information, and then we have to actually go and figure out the details ourselves. It is not something that tells you how to make something work. It says this is what this does, and this is what it can do. You have to then go and figure it out. They have a consulting arm of the organization, and I think they expect you to call up and ask them to come and show you how to configure something.

For how long have I used the solution?

I have been using this solution for five years.

What do I think about the stability of the solution?

It is very stable from an operational perspective. In the five years that I've been managing the product, I've never had an outage of more than 15 minutes.

What do I think about the scalability of the solution?

It seems to scale very well. We had migrated 1,900 users from HP's PPM to Planview, which was a user community of 300. We now maintain an average of 1,800 users in the system. So, we went from 300 to 1,800, and there wasn't any impact on the performance of the product.

In terms of the roles of its users, we have project managers, portfolio managers, developers, release people, architects, engineers, and a management team that does overall oversight.

How are customer service and support?

I do use technical support. At the moment, I have to. Most of the time, they're knowledgeable. They tend to be responsive. I'm the product owner for the company that I'm with. So, from my perspective, they're never responsive enough, but when I think about how bad it could be, I want to say they're reasonable. Sometimes, the turnaround time is a couple of hours, and other times, the turnaround time is months but not from an actual impact to resolution. Sometimes, it takes weeks.

Which solution did I use previously and why did I switch?

There was a merger of two companies. One of them was using HP PPM, and one of them was using Planview. The company that was running HP PPM decided that it was better to go to Planview, and that's when I became the owner of the Planview product. That's when I started the current path that we're on for migrating to the way the product is used. They switched because it was cost-effective.

How was the initial setup?

I was not a part of the initial setup because the original setup was done in 2013 or 2014 by a company that we acquired. In 2015, we migrated HPs' PPM. 

What was our ROI?

We're starting to see a return on our investment. Obviously, it is a journey, and you have to first get adoption. We're starting to get some serious adoption. Now that leadership is starting to adopt this solution, they're looking for more from it. So, as we grow, we get more from it. 

We got an organized environment in the beginning in terms of project reporting and project management to a clear set of guides and principles. We have a single source of data for that kind of stuff, and that was a huge piece because it was all broken before. So, on that journey, return on investment has to be looked at from an individual company's perspective. We're seeing the return on the investment more so today because the leadership team is now using the data to make real-time decisions. They're forecasting their work for the next year. They're now using the data that's actually in Planview. Three years ago, we didn't do that.

What's my experience with pricing, setup cost, and licensing?

Planview is a little pricey. From a licensing perspective, for just a simple timesheet user who does nothing in the system but reports time, the licensing is a little pricey, but you have to look at it from what it is that you get.

We have 6,000 users, and I don't manage the system at all. I just have to add them to the system. The servers, maintenance, OS levels, security patching for the OS, and all other things are not something that we maintain. So, you have to look at it from an operational perspective. It is not just the product itself. A holistic view has to be taken when you look at the product and how you're going to support it. I would have to hire an entire operation staff to bring it in-house, and at the end of the day, that might cost me more. The license might cost me less. I might get a whole lot lower cost on my contract, but at the end of the day, I'd have to have all of the backend resources and the knowledge on the backend resources to support the app locally. So, the cost is strictly going to be looked at from a company's perspective.

Which other solutions did I evaluate?

We've looked at other options. We've looked at the possibility of a different product. As a matter of fact, our current agreement is about to expire. So, we're looking at other options and other capabilities to see if there is something out there that makes more sense for us.

We've looked at Clarity and Azure. We have Azure and Jira in the organization today, and they are used widely. We also have ServiceNow in the organization. We are evaluating whether those products meet what we get from Planview today and whether we can reasonably migrate to that type of solution. It is really more about the migration to a new product in terms of adoption and training.

What other advice do I have?

Its view into resource capacity and availability helps us to manage work to a degree, but we don't use it extensively. That's the one area where we're looking to improve or increase the capability of the product from our own internal perspective. It is not necessarily in terms of the way the product works; it is in terms of the management and administration of our resource pool. That's the step that we're working on now.

We don't use it for end-to-end work management, resource assignment, and creating summary reports across multiple projects. All the reporting is done in Power BI.

I would rate Planview Enterprise One a six out of 10.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Planview Portfolios Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Buyer's Guide
Download our free Planview Portfolios Report and get advice and tips from experienced pros sharing their opinions.