Drive Context and Relevancy into Every Process

Most business software is regularly versioned for updates or so that it can be used for different purposes, situations and even locations. Pega’s situational execution (or situational layer cake) is a revolutionary approach that frees you from having to make physical file-based versions for each business application. Instead, version differences are created as dynamic layers that are turned on and off depending on the circumstance. The exceptions to the rule that normally require human intervention are handled with a simple specialized layer that captures the rules for the particular situation. With Pega’s situational execution, you can:

• Enable dynamic business solutions that can adapt, improve and grow right along with your business.
• Substantially reduce costs for delivering multiple versions of an application at the same time.
• Eliminate time-consuming manual labor and increase staff productivity.
• Increase compliance with applications that manage varying regulations.

Key Capabilities

• Product or Offer – Products and product configurations that include terms and conditions, or combinations of these, can be dynamically varied based on rule-driven logic. For example, customers in a specific region are more receptive to Product A, while customers in a particular demographic and loyalty segment are shown to be most receptive to Product B.
• Customer – Customer segmentation by status and history can vary an application’s behavior according to time and relationship. For example, a platinum customer whose child is reaching the legal driving age can receive an invitational discount to expand insurance coverage.
• Time – A specialized layer can specify time or date, such as applying and promoting discounts for a certain time period to promote customer renewals.
• Location – Location can determine language and cultural specializations as well as legal compliance and regulatory controls that are location-specific. For example, a single application can manage Canadian FLSC or Know Your Customer regulations to account for requirements that differ from province to province and country to country.
• Intent – Pega’s situational execution can learn from history so that you can create specialized rules and versions for different business goals and intentions. When a user communicates an intent, an application can intelligently map how the business will respond to the particular intent and guide the interaction to a successful outcome.