BPM Use Cases

Companies seeking innovation and competitive edge should review the IBM® Business Process Management example use-cases below for indications of the types of areas where business events, combined with business rule management deliver a positive P&L or service impact.

Click on the tabs below to see further information about the types of activities which might apply or <<click here to learn more>>

Buying activities and rules

WebSphere Operational Decision Manager (WODM), and other BPM and integration solutions from IBM, can help you to capture and enact the rules that you need in order to manage supply, suppliers and buy-side activities.

The key characteristics here are the increased dynamism that is offered by WODM to allow development of, and consistency in, rules required to run supply operations or respond to changes in supply market conditions.

  • Most rules in this area would be concerned with triggering based on events and conditions detected in the supply-side operations or market.
  • For example order placement can be constrained to only approved suppliers or varied according to given rules and quantifiable conditions.
  • Notifications and alerts can be triggered based on combined events detected in the supply chain and/or market.
  • As with sell-side activities you can use WODM to radically expand or constrict buying activity and behaviour in support of production and sales activities. For example by suggesting movement, aggregation or disaggregation of supply from the supply based.
  • Approval processes, supplier on-boarding rules etc can be automated or varied, as well as conditionally executed, perhaps in support of differing requirements or policies in different operating units.

Selling activities and rules

WebSphere Operational Decision Manager (WODM), and other BPM and integration solutions from IBM, can help you to capture and enact the rules that you need in order to sell, up-sell and cross-sell.

The key characteristics here are the increased dynamism that is offered by WODM to allow immediate changes in market conditions or competitive landscape to be accommodated.

  • Most rules in this area would be concerned with triggering based on the profile of the customer, or customer responses elicited during the selling cycle – perhaps where you have a multi-channel sales approach.
  • For example product recommendations, bundles and pricing might be customised according to sets of rules and variables which can be quickly and repeatedly modified according to prospect/customer responses or to meet market conditions.
  • Similarly you might have promotional rules which you wish to enact or vary that link to competitive positioning or perhaps drive loyalty programmes which later reduce cost of sales.
  • You can use WODM to radically expand or constrict sales offerings and promotions. For example where the issue is one of lack of offering standardisation WODM can restrict and remove sales options, or where more flexibility is required new offerings can be introduced and market tested more quickly, whilst retaining control over the rules governing existing offerings.
  • Where sales involve channels and partners WODM can be used to capture and enact rules which govern different types of channel activity and behaviour. For example guiding partners and resellers to higher margin products.
  • In a similarly vein, rules which govern payment, reconciliation and transacting with partners can be encapsulated.

Compliance and Governance activities and rules

WebSphere Operational Decision Manager (WODM), and other BPM and integration solutions from IBM, can help you to capture and enact the rules that you need in order to meet compliance and governance obligations.

The key characteristics here are the ability to implement and change rules that ensure legislative or corporate compliance.

  • Most rules in this area would be concerned with ensuring transactions meet compliance, settlement or governance criteria. They can therefore be used to ensure conditions are met, or to ensure that other conditions are not met.
  • For example, rules can be enacted for authorisations (such as payment rules or fraud detection/prevention) or perhaps for legislative uses (such as accommodating differing operating taxes and duties in different parts of the world).
  • Similarly you might have approval or validation rules for claims processes or case management to ensure internal compliance or efficiency gains.
  • Rules may need to be enacted for regulatory compliance where they involve the capture of data or automation of previously manual task in order to meet a risk or compliance obligation.

Efficiency activities and rules

WebSphere Operational Decision Manager (WODM), and other BPM and integration solutions from IBM, can help you to capture and enact the rules that you need in order to drive efficiencies into certain processes through automation or enrichment.

The key characteristics here are the ability to ensure consistency of processes, to eliminate waste, to automate a manual task set, or to enrich it by adding to or reducing the steps and data which is used in the process.

  • Most rules in this area would be concerned with standardising a repeatable process.
  • For example, you might have rules and conditions around insurance policy renewals, or risk assessments during the renewal process, which therefore automate manual data collection tasks.
  • Similar processes might, since they are more consistent and standardised allow for processes to be speeded up whilst simultaneously delivering against other requirements – such as compliance obligations.
  • The encapsulation of consistent processes may also provide efficiencies when supporting multiple delivery channels. That is to say a single process may accommodate multiple channels (web, direct, mobile etc.) rather than having to have different processes for each channel.
  • Approval processes, diagnosis rules, escalations processes, transaction management etc. rules etc can be automated or varied, as well as conditionally executed, perhaps in support of differing requirements or policies in different operating units.

Public/Private Policy policy activities and rules

WebSphere Operational Decision Manager (WODM), and other BPM and integration solutions from IBM, can help you to capture and enact the rules the general ans specific rules required to meet the wide variety of needs in the public sector for service delivery.

The key characteristics here are the ability to implement and change rules that ensure legislative compliance or to meet specific, unique service delivery obligations.

  • Most rules in this area would be concerned with ensuring transactions or activities meet a (probably) unique public service requirement – for example a fiscal, legislative or governance obligation.
  • For example, rules can be enacted for approvals or compliance bodies (such as customs or border control in support of fraud detection/prevention) or perhaps for legislative uses (such as accommodating differing operating taxes and duties in different parts of the world).
  • Other examples might include infrastructure monitoring or central/local government policy delivery.