Likelihood to Recommend I work as a Hospital Manager and in our hospital we need various equipment and advanced machines that can diagnose the best and give us the best results so that we can analyse the patient's best possible condition. Getting new machines and types of equipment is not an easy task we need so many planning the funds for the projects and implementation of those machines can become challenging part if we don't have a proper roadmap of resource management, funds, vendors suppliers, etc. Here Planview Portfolio smartly computes the all data counts all the variables and gives us the best roadmap to follow it is very useful to get crucial projects in organizations. If the organization doesn't have multiple projects or they work in a monotonous way then this tool might not be the best option for them.
Read full review In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Read full review Pros Capture potential opportunities using the Requests Module and analyze and rank these opportunities via lifecycles and promote (dispatch) approved opportunities into Projects. Information captured during the request process automatically get transferred to projects. Robust schedule management; time reporting; resource management and financial planning and management Risk and Issue management controlled via robust lifecycles. Extensive reporting capabilities via SSRS and Power BI Dashboards and delivered to users via tiles in Project and Portfolio views. Read full review When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests. I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload. Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on. To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting. Read full review Cons this is the area I can see Planview Portfolios is very much lagging behind. If you see Atlassian, they are having a robust API information and using that we can securely access the necessary information based on the role. I think a similar kind of approach need to done in Planview Portfolios as well. User Information and Resource information is separate. Expecting that, during the User creation, when a resource is linked, automatically all the basic fields should be populated with the values, also if a person is having an User account there is no way for that person to know that what User role that he/she is having. Also none of the reports covering that details. Automation - It's mentioned using the UiPath some of the Automation has been done in the User creation but don't find any necessary document for better understanding. Read full review It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos. The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes. The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it! Read full review Likelihood to Renew We have been a Planview customer since 1999 and have seen it grow and mature as a tool. We have looked at other tools and have found that PV continues to meet our needs and is easy for our resources to use. They work to stay up on the project management industry and the direction it is going, keep on on current technology so that we can work more effectively, provide excellent customer support and have great pricing for what they offer. We can purchase only the modules we need versus buying a tool where we would only use a portion of the functionality.
Read full review To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
Read full review Usability I feel it is very difficult to use, and very limiting and of over complicated in it's basic project management basic functions. In my opinion it is over engineered to the point of un-useful
Read full review The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
Read full review Reliability and Availability We are long time Planview users and its availability is only limited to our internal SLAs for nightly backups. I have never experienced any unexpected or prolonged software downtime from Planview itself.
Read full review We have never had any issues with ServiceNow's availability that I am aware of in the two years I have been using it.
Read full review Performance For a massive system, page loads are reasonably quick, including searches.
Read full review Support Rating Consultants are knowledgeable and friendly; it is easy to build relationships with the support people you work with and they learn how best to help you. The vendor is continuously looking for honest feedback about their tool and they use that information to design their product roadmaps
Read full review I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
Read full review Online Training To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Read full review Implementation Rating Always have a pre-implementation meeting or conference call with Planview to ensure all are on the same page, disclosure of all and any customization (including reports) and plan for support after implementation of a specified amount of time with the assigned implementation resource. And document everything
Read full review Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
Read full review Alternatives Considered Odoo , like this platform, has allowed us to efficiently organize our projects so that they can be prioritized by importance, to know which is the most urgent, in addition, it has also allowed us to assign work in an organized way among our collaborators, and their reports have allowed us to improve.
Read full review We used to use
Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of
Jira , you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Read full review Scalability ServiceNow works as an enterprise solution.
Read full review Return on Investment It has improved Resource Management. We now consistently represent resource available-to-promise against operational commitments, other projects, q-end commitments, vacations, etc. It has improved our quality of forecasting. We now model project changes and future requests against available time and resources ("what-if" scenarios). It has improved our strategic focus. We now manage our projects from a program/portfolio point of view to ensure we are resourcing company strategic initiatives. Read full review Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers. One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad. Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket. Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in. Read full review ScreenShots Planview Portfolios Screenshots