My use cases involve building out a template library based on our methodology and continuing to iterate on that. We used a template, and basically, to start this out, we built out the template library based on the methodology and continued to iterate on that and reapplied the template. Templates were really nice. We defined deliverables with custom deliverable IDs built in, as well as the full workstreams, and we had a lot of customization in the columns which directly translated from the methodology. We would apply that method based on a phase, and then continue to build that out. Each phase of the project was a multi-year project consisting of over 3,000 lines, 4,000 lines apiece. We had many contributors and nine project managers along with a program manager. We attempted to use project status reporting, KPIs, and project status reporting, but due to the scale of that project, the templates were challenging. So we did use them as backup slides for each of the workstreams. Each workstream would have a filter for showing on the KPI and the dashboard, having a flag to show. We would snapshot those before the meeting from each of the five or seven different workstreams. We also did integration to Power BI for all of our reporting. We extensively assigned resources and capacity. We requested a workflow for task requests based on the forecast and managed the demand and capacity approvals, which went out to a SharePoint site. However, due to the size of this particular project, we ended up auto-approving everything because we had around 1,300 resources, and things were shifting rapidly. We did not use the collaboration tools and scenario planning features directly. Instead, we did what-ifs with multiple workstreams, having five workstreams and then under each one, nine separate end-to-end workstreams. The scenario planning and what-ifs were complicated because if one end-to-end workstream made a change, it would impact the entire program. Therefore, we operated a command and control waterfall style and froze that. We pivoted those WBS items out to our Kanbans and managed synchronization between the Kanban and the start and end for the level five; I think we actually went all the way down to level seven. We managed the reconciliation of the percent complete to identify any slippage.
Solution Architect | Planisware Consultant at Schlumberger
Real User
Top 5
2025-07-14T12:14:50Z
Jul 14, 2025
I work for an oil and extraction company, and previously I've worked with pharma and automobile industries as well. Planisware is primarily used for planning, scheduling, resourcing, and budgeting. In addition to that, Planisware also has the flexibility to do work management execution and agile modules. It is an all-rounder. Though it is a complex tool and the customizations are limited, it is one of the best tools available in the market for project portfolio and program management.
We actually use it for project planning and estimating the cost for the projects, in resource management, and as a timecard application. Users can log their time using the timesheet.
The use case involves a highly sophisticated project and portfolio management tool. While it comes with a hefty price tag, it delivers exceptional value by seamlessly handling all necessary operations for successful project management, ensuring a significant return on investment.
Practice Head - Wipro Digital - PPMS at Wipro Limited
Real User
2022-07-04T14:52:51Z
Jul 4, 2022
Planisware is used for project management, resource planning, and effort trackings such as time sheets. You can use it for financial planning, portfolio planning, for enterprise portfolio, where you can define what your cost will be. Planisware can do all of these things.
Resource forecasting and demand planning. One can do both short-term and long-term planning. Generic resources and named resources can be structured according to corporate need. Using an integrated Organizational Breakdown Structure (OBS; sometimes called Responsibility) distinct from the Resource Breakdown Structure gives substantial reporting flexibility out of the box. (Of course, each company has to populate those structures with internal data.) A distinct advantage of Planisware Enterprise is that any given customer installation can respond to local priorities, such as scheduling or time reporting, then phase in other priorities in your application roadmap over time. Version 6.3 significantly improves data exchange and integration with Office 365 and Google Suite applications. Key project leaders can work productively from within Planisware Enterprise. Multiple JIRA servers can connect with Planisware Enterprise 6.3.5. A project manager can select the appropriate mapping sprint for a given project. Please be aware that Planisware Orchestra is a "lightweight" integrated project portfolio management system designed for smaller organizations. It is completely distinct from Planisware Enterprise--the subject of the current review.
Resource and cost scheduling, time tracking, risk and document management in a collaborative environment. Software solution that supports the end-to-end governance of company portfolios, from finance and resource planning, to the life cycle management of products.
My use cases involve building out a template library based on our methodology and continuing to iterate on that. We used a template, and basically, to start this out, we built out the template library based on the methodology and continued to iterate on that and reapplied the template. Templates were really nice. We defined deliverables with custom deliverable IDs built in, as well as the full workstreams, and we had a lot of customization in the columns which directly translated from the methodology. We would apply that method based on a phase, and then continue to build that out. Each phase of the project was a multi-year project consisting of over 3,000 lines, 4,000 lines apiece. We had many contributors and nine project managers along with a program manager. We attempted to use project status reporting, KPIs, and project status reporting, but due to the scale of that project, the templates were challenging. So we did use them as backup slides for each of the workstreams. Each workstream would have a filter for showing on the KPI and the dashboard, having a flag to show. We would snapshot those before the meeting from each of the five or seven different workstreams. We also did integration to Power BI for all of our reporting. We extensively assigned resources and capacity. We requested a workflow for task requests based on the forecast and managed the demand and capacity approvals, which went out to a SharePoint site. However, due to the size of this particular project, we ended up auto-approving everything because we had around 1,300 resources, and things were shifting rapidly. We did not use the collaboration tools and scenario planning features directly. Instead, we did what-ifs with multiple workstreams, having five workstreams and then under each one, nine separate end-to-end workstreams. The scenario planning and what-ifs were complicated because if one end-to-end workstream made a change, it would impact the entire program. Therefore, we operated a command and control waterfall style and froze that. We pivoted those WBS items out to our Kanbans and managed synchronization between the Kanban and the start and end for the level five; I think we actually went all the way down to level seven. We managed the reconciliation of the percent complete to identify any slippage.
I work for an oil and extraction company, and previously I've worked with pharma and automobile industries as well. Planisware is primarily used for planning, scheduling, resourcing, and budgeting. In addition to that, Planisware also has the flexibility to do work management execution and agile modules. It is an all-rounder. Though it is a complex tool and the customizations are limited, it is one of the best tools available in the market for project portfolio and program management.
The use cases for the Planisware solution were described.
We actually use it for project planning and estimating the cost for the projects, in resource management, and as a timecard application. Users can log their time using the timesheet.
The use case involves a highly sophisticated project and portfolio management tool. While it comes with a hefty price tag, it delivers exceptional value by seamlessly handling all necessary operations for successful project management, ensuring a significant return on investment.
We use the solution for portfolio programs and project management. We are now improvising on intake and ideation.
Our main use case for Planisware is for CapEx control for a portfolio.
Planisware is used for project management, resource planning, and effort trackings such as time sheets. You can use it for financial planning, portfolio planning, for enterprise portfolio, where you can define what your cost will be. Planisware can do all of these things.
It is mainly used for program management, which includes cost, risks, and obviously, resources.
The solution can be used for performance monitoring, project management, and support.
Resource forecasting and demand planning. One can do both short-term and long-term planning. Generic resources and named resources can be structured according to corporate need. Using an integrated Organizational Breakdown Structure (OBS; sometimes called Responsibility) distinct from the Resource Breakdown Structure gives substantial reporting flexibility out of the box. (Of course, each company has to populate those structures with internal data.) A distinct advantage of Planisware Enterprise is that any given customer installation can respond to local priorities, such as scheduling or time reporting, then phase in other priorities in your application roadmap over time. Version 6.3 significantly improves data exchange and integration with Office 365 and Google Suite applications. Key project leaders can work productively from within Planisware Enterprise. Multiple JIRA servers can connect with Planisware Enterprise 6.3.5. A project manager can select the appropriate mapping sprint for a given project. Please be aware that Planisware Orchestra is a "lightweight" integrated project portfolio management system designed for smaller organizations. It is completely distinct from Planisware Enterprise--the subject of the current review.