Pega Platform vs. ServiceNow IT Service Management

Pega [RPA] is good to address a specific business function requirement with not too many bots or automation processes. It takes time and effort to set it up. Though once done, it is very easy to configure and use. One should also run a POC to verify if this product meets the scalability requirements.

Incentivized

I think [ServiceNow IT Service Management is] best suited for very straight-forward customer support type ticketing. If the problem can't be solved by the customer support team, then the ticket likely is a larger issue (ie: a bug) and then likely a Jira ticket would need to be created for more robust documentation.

Incentivized

• Reusability
• Pega’s Situational layer cake architecture is capable of organizing application to suit enterprise needs. An enterprise can have a complex organization structure located around the globe. Because of Situational layer cake architecture reusing common policies and procedures is easy while allowing for differences between products, regions, channels and customer segments.Whereas with some application development platforms, separate copies of the application should be created to suite different business context.
• Faster application delivery
• With Pega developers can reuse common policies and procedures, replicate functions and industry specific frameworks and utilize pega UI elements to develop applications. IT is easy to deploy.Therefore developers are capable of delivering application earlier compared to some application development platforms. Pega reduces time taken to deliver an outcome.
• Pega upgrades
• Pega platform is upddated to adapt and work with latest technologies.
• Proprietary users support and maintain Pega platform continuously. Pega customer support is always willing to enhance product support.

Incentivized

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

Incentivized

• Reporting is not extensive in Pega. Because of this higher management is not able to get the reports which will give them insights into a different area. So Reporting functionality can be improved in Pega.
• Organizations that want to fully use all the features of the Pega 7 platform must follow Pega’s solution development methodology which may not be aligned fully with the organization objectives.
• During upgrades, some of the rules which are deprecated have to be changed to new available rules. This becomes a problem as one has to understand all the functionality and then change a lot of things.

Incentivized

• ServiceNow knowledgebase is limited for self-learning on how to use their features.
• ServiceNow sometimes has a very linear approach to some workflows or assignments where there could only be one child/parent relationship.
• The ServiceNow features for Project Management serves its function is rather cumbersome. The dependencies aspect or predecessors or successors options are rather limited. It is more focused on hours planned vs hours worked then dependencies.
• ServiceNow customer support is hit or miss. They could serve to have more self-help step by step articles.
• ServiceNow needs to have a better export or import features for their Project Management module.

Incentivized

Pegasystems has continued to demonstrate a strong partnership with our organization and investment in their product that aligns with our overall vision and need. Pegasystems has engaged us at every level, with the assistance of minor defects to the overall roadmap planning and alignment of our goals

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.

Pega Platform is enhancing its product and launching new features day by day which help to achieve customers needs. If I talk about the earlier version of Pega Platform (i.e. pega v5 and 6.3) there were many numbers of limitations in Pega Platform and if we need to do some customization then needed to write custom java and jave scripts to achieve the functionally. Now I can say Pega Platform is running with market trends and demand. Pega Platform is giving all the options which support the current technologies like decisioning capabilities, real time processing, mashup, process fabrics etc..

Incentivized

The Geneva version has improved overall usability a lot, but would still be overwhelming for new users. Much like SAP or other large-scale applications- it can be very daunting when you get the first glance of all the modules, but you'll get the hang of it after some training and strong discipline.

Incentivized

We have never had any issues with ServiceNow's availability that I am aware of in the two years I have been using it.

Incentivized

For a massive system, page loads are reasonably quick, including searches.

Incentivized

It’s very slow sometimes, but that may be our servers. Also the Knowledge Library needs some work - again, not sure if it’s our setup or what- but I’m unable to search the body of an article for content, so I have to be very intentional with tagging, but it’s not ideal.

Incentivized

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.

Incentivized

The online training is an excellent one, but still it is missing hands on development.

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.

Implementation is totally depend up on the requirement

Incentivized

ServiceNow implements its solutions for customers using the Start Now Implementation Methodology. The StartNow (STrategicAlignment and drive Rapid Transformation) Implementation Methodology include five deployment stages Plan, Discover, Prepare, Deploy, and Operate. Follow these steps for smooth implementation.

Incentivized

We did evaluate multiple products offerings with Pega Platform capabilities and observed that Pega PRPC rules engine and case management capabilities are better over so many BPM Tools. We also conducted a detailed study with developers to identify the best products out of Suite of BPM products. It's observed that Rules engines integration is very streamlined with forms in Pega whereas other tools multiple have powerful data model capabilities but lacks the ease of creating business rules.

Incentivized

This software was used previously. the software was not easy to configure like servicenow and the visual dashboards and the ui experience was less appealing compared to ServiceNow. ServiceNow offers a lot pf features which can be used across the industry. Gives better integration options compared to Remedy. CMDB and Service Watch are great tools offered by ServiceNow which is lacking on Remedy

ServiceNow works as an enterprise solution.

Incentivized

• Our company has boomed in the past few years because we of how we use Pega.
• We will get a project from a client and the turnaround will be so quick they will throw 3-4 more projects at us.
• Smaller developer teams means less complexity and less overhead.

Incentivized

• We don't currently have a CMDB, so we are leveraging ServiceNow to build one using their ITSM and ITOM tools. This is a huge gap for us as a company and it will be a big win once this is in place.
• The core help desk functions are comparable to most other tools on the market, but SN does a great job of integrating that data with other modules like Problem, Change and Event Management to provide a truly integrated solution.
• The tool is expensive, so you will need to try to do as much as you can with the platform. We currently use other systems for HAM and SAM but will be including these in our ServiceNow instance in the future to help maximize our ROI.

Incentivized