 Hello, everyone. Thank you all for coming. I delighted to be here today. Unfortunately, the second speaker, Shambara Nat, didn't manage to join me today, but he passes his excuses and wished me good luck. Today, I'm presenting a smart baggage tracking. If you don't mind, I'll start with a short introduction. My name is Elena Chavkina. I lead IoT practice at Altairos. Altairos is a professional services company that provides services around cloud fundery, starting from deployment cloud fundery and ending building applications on top of cloud fundery. Altairos IoT practice is focused on cloud-based industrial internet solutions. In the last year, we implemented the number of prototypes proof of concepts for industrial internet. And today, I'll tell about one of it. Smart baggage tracking. But first of all, why baggage tracking? What are the particular reasons for choosing this area, especially for our company, for professional services company? Today, digital disruption is the talk of the town. Go digital. Digitalize your business. We hear it so often, so digitalization become a buzzword. The same with platform as a service is cloud computing, cloud native development. But what are the examples how cloud fundery can help businesses? Six months ago, Altairos decided to exemplify how the aviation industry can benefit from employing cloud fundery. With GE digital mentoring, we decided to build a baggage tracking solution, sensor-based end-to-end for airlines. Where did we start? We started with getting a clear understanding of the problem. And we started with learning the industry standards. A lot of documents, resolutions, reports, I don't want to tire you with all this stuff. So I'll tell a story. A story about Jessica and Mike. Meet Jessica and Mike. There are cloud fundery engineers and they are going to Frankfurt to the cloud fundery summit. Jessica and Mike are flying from San Francisco to Frankfurt through Chicago. And both of them have checked baggage. Jessica and Mike are thinking about the summit, but they don't know these sad statistics. According to CETA report, more than 23 million bags were mishandled in 2015. Most bags were delayed. And there are the reasons for mishandling. The biggest point is flight connections. But also a considerable number of mishandled bags related to the failures during baggage loading and unloading. But let's get back to Jessica and Mike. Jessica and Mike arrived in Frankfurt. Was a trip convenient? Not exactly. The story started in San Francisco with a long line to check in. But it was okay. They expected the long lines they were at the San Francisco airport on time and everything looks good till they landed in Chicago airport. There wasn't much time between flights around an hour. And Jessica and Mike ran to the gate. As soon as they reached it, they realized that the gate had been changed. Fortunately, they reached the correct gate in 15 minutes. But Mike didn't manage to buy the candies for his German friends. Unpleasant. But it's still okay. They arrived in Frankfurt on schedule. Mike's bag has been delivered. But where is my bag? Asked Jessica. Half an hour later, the bag still isn't there. And Jessica goes to the baggage service office to file a claim. Meet Ronald. Ronald works at the baggage service office. And Ron can tell a lot of sad stories. Ron says the normal cost of handling a bag is $10. The cost of delayed bag is $100. And the cost of lost bag could be $3,300. Moreover, mishandling bags make negative impact on customer satisfaction and can lead to additional losses. Jessica is filing a lost baggage claim. Ron is assuring that the bag will be found really soon even though he isn't believing it. And Mike is dreaming about the airport of the future. How do we make travel more convenient? How do we build the airport of the future? First of all, we should think about the essential improvements such as baggage tracking, such as guided navigation, informational services. And then we should consider optional improvements that can make a unique passenger experience like transfer services, home delivery, and all these services should be in one application, none in 10 of them. International Air Transport Association is also thinking about improving the baggage handling. And as a part of the in-back program, they launched Resolution 753 that obliges airlines to have end-to-end baggage custody information by June 2018. What does it mean? The main goal of Resolution 753 is provided to absolutely transparent vision of baggage handling for the all stakeholders, airlines, ground services, passengers. As Andrew Price says, this need comes from the industry members. So airlines want to know the weakest points in baggage handling chain and want to improve passenger experience. Let's look at how airlines and airports improve passenger experience and implement Resolution 753. Delta Airlines invested $50 million in RFID implementation. The test installations show that the bags are tracked at a 99 success rate. Alaska Airlines are doing a pilot project with their loyalty members. They distributed 500 electronic backtacks to their frequent flyers. And Las Vegas, Helsinki, Hong Kong, Milan, Amsterdam airports has all the essential infrastructure to work with RFIDs. Alteros has been involved in several initiatives with airlines and picked up a lot of knowledge about improving passenger satisfaction. So we decided to build this solution on top of GE Pradex as a suite of microservices and rest APIs. Let's look at the main features that were implemented. Our application works in two operation modes. Normal operation mode went back tracks from checking point to the claim belt and this operation mode supported that the baggage will be delivered on the proper claim belt on time without any issues. So the passenger finds his bag on the claim belt on time. The second operation mode handles exceptional cases like delayed bag, like closed bags. Also we implemented the restful IPI for the airlines to comply with Resolution 753 that allows airlines ground services to get all necessary information about the bag status. And all participants in this process get information in real time mode and all of them can get push notifications. Let's look about the push notifications and their role in the system. Push notification from passengers perspective guide passenger from the start of their journey to the end of it. They show the bag status. They warn about changing the gates. They warn about changing in boarding closure time. And optional push notification can contain information about the shop offers. At the start of the project we faced a number of challenges. How do we build our application secure? How do we manage the huge amount of data from the sensors? Which sensors do we choose to comply with industry standards? How do we reach high availability and scalability? And finally, how do you build our application quickly? At the start of the project we made three important decisions. We decided to use intelligent IoT platform which shows RFID tags as a sensors and we decided to use microservice architecture approach. Let's talk about each of them in detail. As intelligent IoT platform we chose a G-Predex. What is a G-Predex? Predex is a general electric cloud fund distribution optimized for industrial internet needs. Why Predex? First of all, because it's cloud foundry and it ensures fast development and fast deployment. But what does, which benefits does Predex offer in our case? First of all, Predex is built to promote and support microservice architecture approaches that we've chosen. Secondly, Predex provides a unique ecosystem around industrial internet of things. They provided a rich catalog, G-Digital together with their partners built a unique catalog that contains services and solutions around industrial internet of things. There are security services. So you can use security from the box, from the age devices to the mobile application. There are data management services, advanced analytic services that you can use in your application and build it really quickly. And the most amazing thing about Predex that it isn't vendor locked solution. The Predex catalog can be extended by adding additional services and additional applications. Because it's cloud foundry, you can develop, build, park or service broker and include your service into catalog. What issues have been solved by using Predex? Security, data management, device management, scalability and high availability. Let's look at the second our choice RFID as a tags. What is RFID? Radio frequency identification uses electromagnetic fields to automatically track tags attached to the objects. The tags could be passive and active. Active tags has a local power source like a battery and can work within 100 meters from RFID reader. Passive tags collect the energy from the nearby RFID reader. The operating principle of RFID is quite simple. RFID tag or transponder generates a unique signal that can be read by RFID reader. RFID reader sends information to the server or to the cloud. And RFID reader can work in read and write mode. What are advantages of RFID as technology? That isn't a new technology. It's extensively used in logistics. It's quite secure and well standardized. That's why we chosen it. And what about the benefits RFID in aviation? First of all, RFID have the higher reading rate and the higher data reading speed than barcodes. Reading rate for barcodes, it's around 80-85%. If we speak about RFID tags, the reading rate could be 98-100%. The RFIDs could be read through the boxes in bulk. They could be read at an angle. So what does it mean for the airlines? It means decreasing the number of mishandling bags, reducing the back transfer time, and also less frequent flight delays. From the ground services perspective, it means considerable improvement in operational efficiency and for the passengers, benefits are obvious. The passengers can be sure that their bag will be handled properly. What infrastructure do we need to implement RFID solution in the airports? First of all, the check-in points should be upgraded by adding RFID printers or RFID writers. RFID printers work with printable back tags and RFID writer can work with permanent back tags. Both types of tags are comply with industry standards. And also we need the number of check points. The check points could be fixed like a gate and the check points could be hand-held. The third factor of success in our project is microservice architecture approach. Why microservices? Because they can be developed separately. They can be scaled separately. You don't stick to one technology, to one programming language. You can work on different microservices in parallel and you can reach the maximum productivity faster. And also you can maintain microservices easily because you don't need to bring down the entire system to fix the issue in one microservice. Let's look at what has been done under our proof of concept. We implemented more than 10 microservices that logically can be divided into backend and front-end groups. They aren't forced to use the central data storage. Message queue handles microservices communication asynchronously and they can be used to load balance microservices requests. The services don't share the common runtime so they can use the different technology stacks and they use them. And let's look at one of them. The most important service in our application is Tracker UI. Tracker UI, the main goal of Tracker UI to show the back status for all participants in the system. Tracker UI is built based on event-driven approach and it updates information on the page without reloading immediately upon a real new data. Let's look how do things work from inside. Asynchronous messaging is primary communication pattern in our system. Tracker UI and Tracker backend keep a web socket connection opened at all time and sends requests to each other. Tracker backend sends the information to Tracker UI and Tracker UI updates the information on the web page. The Tracker backend listens for the events in the system and continuously update information in database. We use RADIS as data storage for our prototype and only Tracker backend has access to the data storage and decides what to store and how to store. Message broker is used for internal communication between microservices. The real demo solution is available on Alteroses booth. We installed two checkpoints and we can show how the back status changes in real time. So welcome to Alteroses booth and look at our solution. And also you can watch the video record of demo. It's available on this link. And if you want to see the whole implemented features and if you want to look at the whole implemented functionality, please feel free to contact me directly after this session during this day and I'll be glad to show the whole implemented functionality and answer your question. That's not in the end of the story. Let me tell a little bit about adoption step for this solution. We recommend to start adoption RFID baggage checking for assessment, the current infrastructure, current software. It could be reused and that's a way to cut the costs when we start implementing the new baggage checking solution. Then we suggest to assess the technologies used in this solution. Why is it so important? Because the accurate baggage checking is just a part of the big in-back program. So industry is in a lot of improvements and the technologies should ensure easily adoption of innovations and new regulations. And as a third step we recommend test installation in the airports. The best way to start this installation is choose hardware vendors. Actually in our solution we don't stick to one hardware vendor. So we can work with different hardware vendors. And as a second step we recommend to grab test data, analyze it, and to improve the reader's location map to reach maximum productivity in the airports. But what is the cost of implementation? The cost of implementation depends on the number of checkpoints in the airport. So it depends on the size of the airport. And according to IATA forecast for class B airports and major carriers, the payback period could be less than 12 months. That's all my presentation. And I'm ready to answer any question that you may have. I understand that this application remains, the real primary thing is tracking, right? So from some point when you get the tag to wherever the airport. So the systems must be connected. Yeah, definitely the system must be connected. So that's why as a first step it's recommended to use printable RFID tags that can contain the regular barcode and RFID into it. So the printable tags that's the point how to adopt this technology. And they widely used for example in Hong Kong from 2008 and in Las Vegas, McCarran Airport. Any questions? I mentioned microservice architecture. So first of all, actually I'm surprised a little bit that we use lettuce as a backing because I thought it was not guaranteed persistence. But I'm not sure compared to an asset database which we're eyeballing. The other question. Let's do that first. Yeah. Okay, okay. About RAZEX backends. First of all, it's not production radar solution. That's a proof of concept of solution that is built in three months by two developers really fast just from scratch. So that's an example how we can use cloud foundry and how we build application on top of Jeep, RAZEX for example really quickly. And TREDIS is used just that's easier. But taking into account that we use microservice approach we can connect to the other data storage easily. Don't change the whole system. We probably want some long-term history as well. So that's just kind of short-term that you know like where was the bag the year ago or something I don't know. Yeah. Yeah. Yeah. The question was you said microservice architecture. So which microservices did come up in the design? Do you have any information about that? So how the application code was cut to microservices? Do you mean the microservices that was implemented by Alteros? Is there just one microservice? The tracker? Not tracker. No, no. You can see that there is tracker UI, tracker backend, stuff backend. You can see the number of analytics engine, tracking engine, checkpoints. So there's a number of microservices. Not only one, just I picked just one to show it as an example. Yeah. What is the communication between the software and the edge devices? The communication is provided by GE Predyx. On the edge devices we install Predyx machine or Predyx edge, the special piece of software that connects to Predyx cloud and sends information to Predyx cloud. Only Predyx machine can be connected to Predyx cloud? No, yeah. But actually this make our work easier. It makes our application more secure. Of course, you can connect to the Predyx cloud without using Predyx machine, but it isn't so secure. Oh, you exceeded my technical knowledge. But I answered this question a little bit later. Okay. Predyx Edge, is it running in some special or just a regular machine that you run yourself with? Predyx Edge, yeah. Predyx Edge is running on Raspberry Pi. You can run it on Intel board. So it doesn't matter. It runs on each device. It's not on Predyx device, it's just. For example, we run it on Raspberry Pi 3 and our test booth is based on Raspberry 3. So that's not an issue. You can use different kinds of hardware. So thank you for your attention. I'll answer your question a little bit later. Thank you.