facebooklinkedinrsstwitterBlogAsset 1PRDatasheetDatasheetAsset 1DownloadForumGuideLinkWebinarPRPresentationRoad MapVideofacebooklinkedinrsstwitterBlogAsset 1PRDatasheetDatasheetAsset 1DownloadForumGuideLinkWebinarPRPresentationRoad MapVideo
Actian Blog / Real-Time Decision-Making Use Cases in the Retail Industry – Part 3

Real-Time Decision-Making Use Cases in the Retail Industry – Part 3

Omni Channel Technology Of Online Retail Business.

In the first part of my blog on Real-Time Decision-Making (RTDM) highlighting Retail industry use cases, we discussed how combining existing historical data patterns with disparate new sources of data completes the Common Operational Picture (COP).  To illustrate the use-case, we used an Actian customer, Kiabi, and how they used RTDM strategic capabilities to enhance their customer loyalty program.

In the second part, we explored how different roles and responsibilities can use the COP in business-as-usual scenarios versus periods of market disruption using another Actian Retail customer, LeRoy Merlin.  LeRoy Merlin wanted to extend their decision making in a data-driven fashion down to managers in their retail locations across Asia, Europe, Latin American, and Africa with an emphasis on sales performance data by-product for a range of factors.

The key points I was hoping readers would take away were that in times of market uncertainties, enhanced customer focus requires business agility that can only be achieved by proper use of the COP to deliver situational awareness based on role and proximity to the point of action.  The further downstream you’re able to push the analysis and decisions, the better the results – provided you can balance speed and accuracy.

It takes two to make a thing go right

OK, it’s an old party song stuck in my head, but the sentiment is spot on.  One major theme of leveraging the COP to deliver more accurate, fresh intelligence down to frontline decision-makers on the ground is to ensure the focus on customers keeps them happy and satisfies their needs.  But it’s also about satisfying the needs of the business.  With Kiabi, they wanted to make sure their loyal customers got exactly what they wanted by monitoring their buying behaviors to predict what marketing programs would incentivize loyalty program members to buy more apparel.  With LeRoy Merlin, they wanted to empower their store managers to understand locally which inventory was moving and which was just sitting on the shelves to determine how to improve sales performance in that individual store.

Across both these use cases, we’re leveraging RTDM intelligence to drive existing programs and operations to yield better business outcomes.  Satisfaction for customers is measured in many ways, with the most critical from a business standpoint: repeated profitable business.  During periods of market uncertainty, demand fluctuates, and so does the cost of goods and services.  Organizations must ensure they are able to handle constituents – customers for businesses, patients if we’re talking healthcare, students if we’re talking education, in a way that avoids unexpected cost or risk.  In other words, profitability must be maintained.  Even if we’re talking non-profit, operational expenses must be covered for the mid- to long-term.  In summary, the thing that needs to go right is the relationship on both sides – for the customer and the business.

Balancing Customer Response and Risk

For several years now, we’ve been supporting The AA, the leading provider of roadside assistance services in the UK.  In addition to roadside services, The AA uses independent insurance brokers who work with a group of AA underwriters to offer a range of vehicle and home insurance policies.  Actian has helped The AA with its RTDM capability. The AA uses the Actian Avalanche hybrid database solution to analyze insurance applicant-supplied data against third party data and verification services to assess risk that is critical to quoting a competitive yet profitable policy.

In this case, the COP consists of internal but fluid actuarial data, fraud detection data and models, external sources to collect verification of prior applicant driving records and claims, and relevant demographic traffic accident and property crime rates by location, and so forth.  Decision making is pushed down to the frontline underwriters in that they are assigning risk and to the independent brokers in that they are providing the quotes. However, their roles are essentially as the feedback loop on risk assessment and quoting that is automated, and the interaction with prospective policyholders takes place on competitive Insurance websites like GoCompare.com and CompareTheMarket.com.  Prospect expectation and competitive table stakes dictate that all quotes be delivered side-by-side in under a second.

The Actian Avalanche platform was selected to support the risk assessment and quoting operation because of performance requirements in two separate areas.

  1. To meet the speed of collecting the information internally and externally to generate quotes in one second or less.
  2. The speed at which fresh data can be visualized for the underwriters in Looker, enabling them to tweak the risk-based decisions based on the competitive landscape.

Real-Time is in the “Eye of the Beholder”

In The AA use case, speed and accuracy are both important.  Driving record data changes all the time. There is no point in underwriting on a clean driving record based on yesterday’s data when today’s data says the 16-year old daughter just got her learners permit.  In other words, if you were to use a Cube to retrieve the data to meet performance requirements depending on the business requirements, your data may be stale, and so the speed is really only one part of real-time, the other part is the freshness of the data.

Both speed and freshness are the true definitions of real-time.  The requirements for The AA were 1 second, but for LeRoy Merlin, they’re daily.  For many businesses, the real-time requirement is weekly. For example, grocery stores may need to review sales at each supermarket weekly as part of a regular resupply process, and the speed may be an hour or less for populating the data across all stocked items, but the stock data before store managers show up Monday morning for work.  In this scenario, stock data doesn’t need to be updated every hour, but perhaps once per week.

During periods of market uncertainty, either or both speed and accuracy may require change.  Take the grocery store refresh rate of a week for their stock data, and use of a cube may be too coarse when you have panic buying across everything from pasta to peanut butter and its rolling across different products by day.  At that point, your need for fresh data and your real-time requirement change from weekly to daily, and the speed of data collection, analysis, and visualization may drop from an hour to minutes.

In The AA’s case, their real-time requirements are already set on speed and accuracy, and their RTDM capability for business-as-usual easily translates to scenarios where business disruption is taking place.  For many organizations, this is not the case, and the question really is, how do you ascertain what your speed and accuracy requirements are for periods of market uncertainty?  In our next blog in the series, we’ll look at what’s needed for speed and accuracy … on a budget. Until then, find out how The Actian Real-time Connected Data Warehouse can help you achieve your RTDM goals.

About Lewis Carr

Senior strategic vertical industries, horizontal solutions, product marketing, product management, and business development professional focused on Enterprise software, including Data Management and Analytics, Mobile and IoT, and distributed Cloud computing.