• Strong support for development and deployment lifecycle management.
• Depends on sophisticated development expertise (preferably a Pega-certified system architect) from the outset.
• Lacks an inherent, role-based model for work assignment, complicating process modeling.
• Too many opportunities for programmers to step around the configuration features and break model-driven applications
With the 5.1 release of its SmartBPM Suite, Pegasystems has made its powerful product easier to use for process participants, business analysts and developers. Although the suite is one of the more daunting BPM systems to deploy, this new release is significant because of the kind of business process management suite it offers. Pega's package manages processes in a fundamentally different way than any other BPMS I've examined.
SmartBPM is based on a unified rules-and-process engine in which processes are first-class citizens alongside different types of business rules. Pega effectively binds all the elements required to deliver an application at run time, including process fragments, business rules, presentation elements, integration calls and security controls. Everything is dynamically selected and bound based on the work context, as defined by the events and attributes of the case (process instance).
Competitive approaches tend to limit the use of business rules to decision points calling a standalone rules engine. With Pega, the inferencing capability of the core rules engine detects changes in the state of the related information and then works out what to do based on the goals of the process. That could be just about anything, from forward chaining (moving to the next step in the process), invoking a separate process thread in parallel, raising an alert to a manager or even backward chaining through the rule set to retrieve some piece of missing information automatically.
Keep Data In The Domain
Another key differentiator for Pega is that rather than regarding the information domain as out of the scope of the BPMS, the entire SmartBPM environment is based on a componentized, service-oriented run-time environment in which data classes are specialized alongside the business processes and declarative rules. This approach lets Pega resolve the right rules and processes to bind to the case based on the context of the work. Although specialization delivers tremendous downstream flexibility, enabling better market segmentation, it also presents challenges in the early stages of deployment.
Overall, the approach facilitates app customization to meet particular needs. Say you have a standard way of processing orders, for example, but when an order comes in for a key customer and the product is out of stock, you want to offer a special alternative. Or perhaps it is a first-time customer and, as a result of a directive from on high, you want to use a special set of customer-satisfaction checks. Pega handles these situations by layering on specializations from the rule base, adding alternatives without your having to go back and manually weave these revisions into the baseline process.
Other BPM suites require a cut-and-paste approach, where each scenario requires a copy of the process that is then adapted. Over time, this can lead to fragmented process architectures and a higher cost of ownership. However, creating the right class structures to meet the downstream goals of the organization demands long-range planning and expertise. For a major enterprisewide project, it's best to involve a Pega-certified system architect from the outset.
How Enterprises Are Attacking the IT Security EnterpriseTo learn more about what organizations are doing to tackle attacks and threats we surveyed a group of 300 IT and infosec professionals to find out what their biggest IT security challenges are and what they're doing to defend against today's threats. Download the report to see what they're saying.
Digital Transformation Myths & TruthsTransformation is on every IT organization's to-do list, but effectively transforming IT means a major shift in technology as well as business models and culture. In this IT Trend Report, we examine some of the misconceptions of digital transformation and look at steps you can take to succeed technically and culturally.