Qlik Community

Ask a Question

Qlik Design Blog

All about product and Qlik solutions: scripting, data modeling, visual design, extensions, best practices, etc.


The holidays are approaching, and Santa is almost ready to deliver toys to children around the world again! But just how does Santa run such an enormous enterprise and continue to scale to meet global demand each and every year? With the help of Qlik Sense, of course! From supply chain to operations to distribution, Santa uses Qlik Sense to enable all aspects of his organization to make data-driven decisions.

Since it’s that time of year, let’s look at how Qlik Sense is used on the shop floor in Santa’s Workshop to monitor and improve production. Qlik Sense is available to shop managers and teams on mobile devices throughout the shop floor, and real-time data and alerting enables timely action to any changes. Below are four real-world examples from Santa’s workshop this year.

Click to open the "Santa's Workshop" Qlik Sense app

All Wrapped Up

On September 26 the Jingle, Twinkle, Merry, and Peppermint Teams were trending on average 5% below target. Qlik Sense alerted management that the teams were not meeting production targets and that downstream bottleneck time for the three teams was more than 3x higher than average, so a manager went to investigate the packaging department. What they discovered was quite a scene! One of the newer elves, in the midst of trying to prove himself and working as fast as he possibly could, had gotten himself so tangled up in gift wrap and tape that the other packaging elves were having a frightfully difficult time getting him free of the mess. The manager quickly went and got Grandma Elf, who is particularly apt at solving such crises, and packaging was then resumed, relieving the downstream bottleneck for the Jingle, Twinkle, Merry, and Peppermint Teams, and bringing production back in line with targets.




Industrious Elves

On October 11, Jingle Team’s production dropped to more than 16% below target. When the manager received an alert from Qlik Sense and checked to identify a cause she discovered that personal break time for the team was 8x more than average for the day. She immediately went to talk to the team to discuss the finding, but they were not at their workstations or the candy bar break room. She eventually discovered the entire team outside engaged in an intense and prolonged snowball fight. While elves are generally an industrious bunch, they love a good snowball fight, and the Jingle Team had lost track of time amidst the fierce battle. After the manager jumped in to toss a few snowballs herself and show the elves who’s boss she got the team back to work and production back on track.




North Pole Blues

Then on November 19, Qlik Sense alerted that the production of both the Jingle Team and the Holly Team was more than 11% under target. Downtime caused by an upstream bottleneck was more than 5x average for both teams. Turns out that having your workshop in the North Pole presents some unique logistical challenges, and essential materials due to arrive that morning were held up in transit after Jack Frost decided it would be a good day for an impromptu artic blizzard. Luckily, the real-time alerting of Qlik Sense enabled the problem to be identified quickly, and production on the two lines was shifted to use available resources and quickly get production levels back up to capacity.




A Sticky Situation

On December 16, less than ten days out from Christmas Eve during the final push to reach production goals for the year, Qlik Sense alerted that the Marshmallow Team was operating at almost 12% under their daily target. Analyzing the data revealed that repair downtime was 5.5x longer than average, so a specialist repair team was sent to investigate. The repair team discovered cotton candy in the machine gears, causing increasingly frequent shutdowns, a sticky situation to say the least. The repair team got to work right away, licking the machine clean despite the health department protest, and the Marshmallow Team was back to full production just two days later.