Different Flavors Of Real-Time Result In Significant Implications.
Many pundits, research insight folks, bloggers, and hand wavers keep talking about the need for real time in social business, analytics, mobile, and other disruptive technologies. Given the volume of data, bandwidth constraints, and magnitude of business processes to be supported, is the notion of real time even possible? It’s been the holy grail of many technology suppliers to state they are delivering information or reacting in “real-time”.
While researching the issue, I rediscovered a classic post from event processing researcher Dr. Opher Etzion, from IBM Labs Haifa. The central thesis from this 2007 classic post is that real-time is quite valuable in the context of “the damage caused when missing a deadline”. When you look at that from a business value perspective, his approach leads to four types of real-time (see Figure 1):
- Soft real-time: there is a sense to react after the deadline, but the utility decreases (maybe fast) and at some point gets to zero – no use to do it at that point, but no damage.
- Firm real-time: The utility go immediately to zero when the deadline is missed – no use to do it after the deadline, but no damage.
- Hard essential: Missing the deadline – the utility function goes to a constant negative value; there is a constant penalty.
- Hard critical: Missing the deadline – the utility function goes immediately to “minus infinity”, means: a catastrophe will happen.
Figure 1. Four Types Of Real-Time And their Implications Of Missing A Deadline
Source: Dr. Opher Etzion
The Shift From Real-Time To Right-Time Prioritizes Events By Business Value
A deeper examination of the four types shows that business value can easily be quantified in the hard essential and hard critical types as these result in penalties and disasters when real-time is not achieved. In the case of firm real-time, the lack of timely response results in a wasted and non-valiant effort.
Consequently, organizations must prioritize business processes for real-time by business value achieved and potentially lost. Essentially, this prioritization results in the notion of right time delivery of information. Moreover, right time increases in value as a concept when gauged against reactiveness versus proaactiveness.
As we break down business processes by interactions, an emerging class of applications move beyond transactions. In fact, these applications must quickly determine right time actions at the point of engagement that follow 4 distinct types (see Figure 2):
- Proactive value added anticipation: the heart of engagement applications, anticipation allows for proactive response. Examples include offers, suggestions, actions based on context drivers. Context drivers could include location, presence, time, proximity, relationships, previous purchase behaviour, etc..
- Mission critical reactions: where most “real-time” use cases tend to fit, this type addresses deadlines, commitments, and regulations. Examples include response times, regulatory requirements, alerts, threshold triggers, and service level agreements.
- Nice things to do: reminders with minimal impact but provide proactive engagement. Examples include status updates, background information suggestions, and non-critical notifications.
- Timeless responses: where useless information resides in an abyss. Examples include log reports, short action items, nice to know information from activity streams.
