Streamlining compensation program with IBM WebSphere ILOG JRules BRMS
Company Size
1,000+
Region
- America
Country
- Brazil
Product
- IBM WebSphere ILOG JRules business rule management system
Tech Stack
- IBM WebSphere
- ILOG JRules
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Employee Satisfaction
- Productivity Improvements
Technology Category
- Application Infrastructure & Middleware - API Integration & Management
Applicable Industries
- Retail
Applicable Functions
- Human Resources
- Sales & Marketing
Services
- Software Design & Engineering Services
About The Customer
The customer is a large Brazilian retailer of durable goods. The company has grown to be one of Brazil’s largest durable goods retail chains with 613 stores nationwide. With gross revenues of R$5.7 billion and EBITDA of R$320 million in 2010, the retailer has 21 thousand employees serving 23 million customers. The retail outlets are catalog stores, where sales representatives use computers to display and sell the company’s goods. About 30 percent of sales representatives’ monthly paycheck is flat salary, and the other 70 percent is commission and bonuses.
The Challenge
The Brazilian retailer had a business-critical incentive compensation system that had 60 rules for calculating bonuses, and provided little flexibility in product promotion. The monthly processing time took 12 - 18 hours causing a rush to meet the payroll deadline. The compensation system was a 15-year-old COBOL program with very little documentation that depended on a single systems analyst to keep it running. There was a two-day window at the end of each month to collect and process all store transactions in order to determine incentive compensation. If a problem appeared, such as an unexpected or erroneous transaction volume or money value, the IT team would work around the clock to make adjustments and reprocess batches. Making timely updates to the compensation plan to meet constantly changing business needs was a challenge.
The Solution
The company implemented IBM® WebSphere® ILOG® JRules business rule management system to create a flexible, easy-to-manage incentive compensation system. The ILOG JRules solution processes all the transactions for each day and the previous days, running all 60 business rules, to keep a running total of commissions and to determine how bonuses are progressing against monthly goals. The processing for each day takes only 55 minutes, and there’s no longer any rush at the end of the month to meet a two-day window, because the work has been broken up into 30 daily parts. The JRules solution brings unprecedented transparency to the compensation program, saves time, boosts satisfaction for employees and reassures management that written policies are being observed across the board.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Improving Production Line Efficiency with Ethernet Micro RTU Controller
Moxa was asked to provide a connectivity solution for one of the world's leading cosmetics companies. This multinational corporation, with retail presence in 130 countries, 23 global braches, and over 66,000 employees, sought to improve the efficiency of their production process by migrating from manual monitoring to an automatic productivity monitoring system. The production line was being monitored by ABB Real-TPI, a factory information system that offers data collection and analysis to improve plant efficiency. Due to software limitations, the customer needed an OPC server and a corresponding I/O solution to collect data from additional sensor devices for the Real-TPI system. The goal is to enable the factory information system to more thoroughly collect data from every corner of the production line. This will improve its ability to measure Overall Equipment Effectiveness (OEE) and translate into increased production efficiencies. System Requirements • Instant status updates while still consuming minimal bandwidth to relieve strain on limited factory networks • Interoperable with ABB Real-TPI • Small form factor appropriate for deployment where space is scarce • Remote software management and configuration to simplify operations
Case Study
How Sirqul’s IoT Platform is Crafting Carrefour’s New In-Store Experiences
Carrefour Taiwan’s goal is to be completely digital by end of 2018. Out-dated manual methods for analysis and assumptions limited Carrefour’s ability to change the customer experience and were void of real-time decision-making capabilities. Rather than relying solely on sales data, assumptions, and disparate systems, Carrefour Taiwan’s CEO led an initiative to find a connected IoT solution that could give the team the ability to make real-time changes and more informed decisions. Prior to implementing, Carrefour struggled to address their conversion rates and did not have the proper insights into the customer decision-making process nor how to make an immediate impact without losing customer confidence.
Case Study
Digital Retail Security Solutions
Sennco wanted to help its retail customers increase sales and profits by developing an innovative alarm system as opposed to conventional connected alarms that are permanently tethered to display products. These traditional security systems were cumbersome and intrusive to the customer shopping experience. Additionally, they provided no useful data or analytics.
Case Study
Ensures Cold Milk in Your Supermarket
As of 2014, AK-Centralen has over 1,500 Danish supermarkets equipped, and utilizes 16 operators, and is open 24 hours a day, 365 days a year. AK-Centralen needed the ability to monitor the cooling alarms from around the country, 24 hours a day, 365 days a year. Each and every time the door to a milk cooler or a freezer does not close properly, an alarm goes off on a computer screen in a control building in southwestern Odense. This type of alarm will go off approximately 140,000 times per year, equating to roughly 400 alarms in a 24-hour period. Should an alarm go off, then there is only a limited amount of time to act before dairy products or frozen pizza must be disposed of, and this type of waste can quickly start to cost a supermarket a great deal of money.
Case Study
Supermarket Energy Savings
The client had previously deployed a one-meter-per-store monitoring program. Given the manner in which energy consumption changes with external temperature, hour of the day, day of week and month of year, a single meter solution lacked the ability to detect the difference between a true problem and a changing store environment. Most importantly, a single meter solution could never identify root cause of energy consumption changes. This approach never reduced the number of truck-rolls or man-hours required to find and resolve issues.
