Buffer information

Buffer external information and subscribe to updates

Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) All sources

category: Information class: Rules for External Parties frameworkAspect: Information perspective: object/data

Description

Many processes stall while someone waits for information held by another party: a credit rating from a bureau, prices from a supplier, master data kept in a partner’s system, an entry in a public register. Each request costs a round trip and, more importantly, waiting time that no internal resource can shorten.

Obtaining information from other parties is a major, time consuming part in many workflows. By having information directly available when it is required, throughput times may be substantially reduced. Note that this buffering is a weak form of the integration pattern. Instead of direct access to the original source of information in the integration alternative a copy is maintained.

In practice, buffering means keeping a local, regularly refreshed copy of the external information you need repeatedly, and subscribing to updates instead of querying the source case by case. It works best for information that many cases need, that is requested often and that changes relatively slowly. Where Integration connects your process directly to the partner’s process or system, buffering decouples you from it.

The central design question is freshness. A buffer that is out of date silently introduces errors, so you need a clear refresh cycle, change notifications from the provider, or a rule that triggers a live lookup when the buffered value is older than a threshold or the case carries high risk.

Key Takeaways

  1. Buffer what you ask for repeatedly — Keep a local copy of external information that many cases need instead of requesting it each time.
  2. Manage freshness — Define refresh cycles, subscribe to change notifications and fall back to a live lookup when the buffer is too old.
  3. Weigh fees against waiting — Compare subscription and storage cost with the waiting time and per-request effort saved.
  4. A weak form of integration — Buffering copies the information, whereas integration gives direct access to the source.

Performance considerations

QualityTimeFlexibilityCost080

■ This pattern   ■ Baseline

This pattern can be compared to the caching principle microprocessors apply. Of course, the subscription fee for information updates may be rather costly. This is especially so when we consider the situation that an information source may contain far more information than is ever used. Substantial cost may also be involved with storing all the information.

The ratings follow this logic. Time improves markedly, because waiting for external replies disappears from the critical path of the case. Cost worsens, driven by subscription fees, storage and the effort of keeping the buffer synchronised, especially when you pay for far more data than your cases consume. Quality is neutral: the information is the same as at the source, provided it is fresh, so stale data is the main risk. Flexibility is neutral too. You become independent of the partner’s response times, but changing provider or data scope means rebuilding the buffer.

Example

For example, a leasing company that requests a credit report for every application, often for the same corporate customers, could subscribe to a monitoring service that sends an update whenever a customer’s rating changes. Applications from existing customers can then be assessed immediately against the buffered rating, while new customers still trigger a live request. The company would compare the subscription fee with the waiting time and per-request fees saved, and define when a buffered rating is too old to be relied on.

Spotting the opportunity in event data

Framed along the FLAC rule types — fitness, location, attribute, constraint.

Fitness: processes where a notable share of throughput time is spent waiting for information from external parties. Location: activity pairs such as Request information → Information received, and any reminders in between. Attributes: waiting time per request, request frequency, share of requests concerning the same object (customer, supplier, material) within a period, and how often the returned value actually changed compared with the last request. Constraints: information that changes frequently or must be current at the moment of decision; subscription or storage cost exceeding the value of the time saved; data-protection limits on holding copies.

Sources & references

  1. Reijers, H., & Liman Mansar, S. (2005). Best practices in business process redesign: an overview and qualitative evaluation of successful redesign heuristics. Omega, 33(4) Summary on this site Publisher page DOI 10.1016/j.omega.2004.04.012

Share this pattern

Enjoy these

Foundational free Patterns

Apply Integral technology

Elevate physical constraints by applying new technology

Apply triage

Consider the division of a general activity into two or more alternative activities

Appoint case managers

Assign a responsible individual for handling each case type

Assign cases

Let workers perform as many steps as possible for single cases

Automate activities

Consider automating activities

Automate for environmental impact

Implement automation in a sustainable way

Combine activities

Combine small activities into composite activities

Consolidate Work

Collect similar work items and work in batches

Constraint-based task assignment

Allocate tasks considering business process execution constraints

← Back

Connected to

Consolidate Work

Collect similar work items and work in batches

What's Happening?

Dec 2023
New Pattern

Consolidate Work

Nov 2023
Oct 2023
Oct 2023
New Cheat sheet

Redesign Essentials

Sep 2023
Sep 2023
Aug 2023
New Pattern

Task delegation

Aug 2023
Aug 2023
New Pattern

Green Feature

Aug 2023