Skip to main content

Inside Disney’s Internet Of Things by Christian Sylt [@ Forbes]


I first learned about the article (here) from the latest edition of The DISUnplugged Podcast, of which I am a weekly listener.

While I constantly hear park proprietors complain that a bit of infrastructure has failed to account for the demand when it comes to dining reservations (or recently, park passes due to the reopening of Magic and Animal Kingdom on July 11th), I've always been interested in how they use technology to encourage guests to give up autonomy, interact with the 'on-stage' setting, and get the most out of their Disney World trip.

The last time I was at Walt Disney World (WDW) was in April or May of 2013. While MagicBands were announced in January of 2013, I'm not sure when they started being given to guests to use with MyMagic+.

I never got one.



When I return (A goal of mine is to spend a week at Animal Kingdom Lodge - Actual Park Visits be damned!), I know which one I want.




But what exactly can one do with this thing?

Let's start with what it does in general:

The long-range device inside them sends out signals to beacons all over the parks so that guests can have their experience personalized.

In short, RFID. Radio Frequency to track movements.


"After choosing a PIN, guests can link their credit cards to their MagicBands so that they can be used to pay in Disney World’s shops and restaurants. All guests need to do is type in their PIN and touch the band to a reader which also bears the outline of Mickey’s ears. Not needing to use cash or credit cards adds to the escapist atmosphere in the parks and even manages to make paying seem like an enchanting experience."

Great way to ensure people aren't paying close attention to what they're really spending. "It's not real money if it comes from a cute cartoon character!" The bands also talk to beacons on attractions - The article mentions Expedition Everest in detail.

Sylt interviews one Kelly White, Disney World’s vice president of digital strategy, about the company's plans to wrap consumer tracking in pixie dust.

“Now it is a little bit about the queue but it is actually much more about the rest of the land, the rest of the parks and giving you an immersive experience in the land that you may not have been able to access before.”

Smartphones already have a place in entertaining you in endless queues and Star Wars: Galaxy's Edge, to interact with the surround land and Millennium Falcon, and it seems here's a lot of work going into the apps to make it a bit of a treasure hunt within the lands kind of attraction.

I'm not here to quote the entire article at you, so I'll quote one final section:

"Sensors are found in the most unexpected of places at Disney World, even underneath the paper drinks cups to control the number of times they can be refilled."

You know, if I pay 3000$ for a 3 day vacation, I'd like to be able to refill more than twice. But I'm speaking on things I don't know. Someone out there, tell me how many times you can refill your paper cup.





Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.