A trade fair day: three incidents in Halls 3-4
Halls 3 and 4 of the MEETT host a craft trade fair of about 110 stands. The game scenario Trade fair day of r-iosemit plays the day from 08:55 to 16:30: in the morning the entry flow at the Hall 3 entrance falls and a queue forms, late in the morning a liquid is spilled in aisle C, and in the afternoon a package is left alone in aisle A. Each incident is an alert of r-iota; the deduction builds the response of the MEETT operations team, and of the Police for the package, from the functions of the crisis event show references.
A sensor threshold raises an alert, and the same threshold held for ten minutes raises a second, persistent one. A referenced actuality of r-iosemit creates an incident on an aisle, and may impact several resources. The deduced processes carry decisions (a Yes / No output of a task chooses the branch), parallel tasks and photo outputs; a state of the Hall 3 entrance (Open or Frozen) is observed from the limit switch of its gates.
Load the use case and open the applications
MEETT Toulouse Exposition is a runtime use case: it ships in the distribution. Its people belong to the group MEETT operations, which acts on the MEETT site: Nathalie Roux (Event Supervisor), Hugo Lefebvre (Ticketing Manager), Camille Dubois (Parking Manager), Antoine Mercier (Dynamic Signage Manager), Leila Benali (Security Manager), Paul Girard (Cleaning Manager) and Marc Fontaine (General Installation Manager). The group Police, an external partner with the role Policeman, also acts on the site. Each of them carries a phone with a GPS.
- In r-ioga, Projects workspace, click the card
MEETT Toulouse Exposition, then Load, and close the confirmation with OK. - From the
APPLICATIONScolumn of Project List, open R-IOTA and R-IOSEMIT, each in its own tab.
ResultThe applications open on the project MEETT Toulouse Exposition.
Look at the site and the plan of Halls 3-4
The site MEETT - Toulouse Exhibition Centre holds the exhibition hall, the convention centre, the office building, the tram stop pavilion, two west buildings and six parkings, all modelled in 3D, with a road network and two pedestrian networks, one of them inside Halls 3-4. On the visitor route stand three security gates and three lines of Vauban barriers, the last one funnelling the visitors to the Hall 3 entrance airlock. The project opens its maps on the 2D Plan view: the ground floor plan of Halls 3-4 shows the stands, bars, cloakrooms, ticket sales, queues and emergency exits of the fair as named zones; the aisles A, B and C, the Hall 3 entrance and the restrooms of both halls are territories of the model.
- In r-iota, look at the map: it opens on the plan of Halls 3-4. Point at a zone to read its name.
- Optionally, open r-io4U and log in as one of the managers: its Map page opens on the same plan, and tapping a zone shows the name of the stand or equipment.
ResultThe plan of Halls 3-4 shows the stands, the aisles and the Hall 3 entrance.
Choose the scenario and set the supervision
The game scenario Trade fair day gathers on one timeline the three incidents that the scenarios Entrance queue at Hall 3, Liquid spill in aisle C and Suspicious package in aisle A play one at a time. It also prepares two tasks of the simulated actors: Photo proof and request to lift the signage and Take charge of the suspicious package are set to Auto, done, with a photo of the aisle or of the package as their output. With the auto mode of r-iota, each alert is deduced and its solution deployed without review.
- In r-iosemit, select the game scenario Trade fair day and open the TIMELINE mode.
- In r-iota, click the radar button of the toolbar: in the Supervision dialog, turn Supervision and Auto mode on, then click Save.
- In r-iosemit, click Play, tick Simulated actors do their tasks on their own and start the run.
ResultThe clock of the use case starts at 08:55; the entry flow of the Hall 3 entrance reads 80 to 90 entries per 5 minutes.
09:20 · A queue at the Hall 3 entrance
The sensor AXS - Hall 3 entrance flow counts the badge and ticket scans at the entrance of Halls 3-4 per 5 minutes; under 50, a queue forms at the control. At 09:20 the flow falls to 42: the CEP rule of the sensor activates the alert Entrance queue. The flow stays under 50 (38, 35, 40, 47) and, ten minutes later, the second rule of the same threshold activates Persistent entrance queue. The Ticketing Manager takes charge of the queue and says whether reserve control posts are free: if yes, the reserve posts and an e-badge lane are opened, the dynamic signage directs the visitors to the least busy entrance and the Security Manager opens a second bag control line; if not, the Event Supervisor sends hostesses from a quieter zone as reinforcement, which is also how the persistent queue is treated.
- In r-iota, read the alerts as they appear and follow the deduced process in the supervision.
- Keep the run going: from 09:45 the flow climbs back over 50 (55, 63, 70…).
ResultEach alert is released once the flow has stayed above 50 for ten minutes; the flow ends the morning at 80 to 85.
11:05 · A liquid spill in aisle C
At 11:05 r-iosemit creates Liquid spill in aisle C, a copy of the actuality Liquid spill of the references impacting the territory Aisle C, the south aisle towards the entrance. The Cleaning Manager takes charge of the spill and says whether the product is dangerous or the spill of technical origin; in parallel, the Security Manager sets up signs and cones around it. If not, the floor is cleaned and dried; if so, the Security Manager keeps the public away and the General Installation Manager intervenes (absorbent, ventilation, leak). Both branches end with Photo proof and request to lift the signage: the Cleaning Manager photographs the aisle made safe, and the Security Manager lifts the signage.
- Follow the alert and the process in r-iota; in r-ioga, the To Do List shows the tasks of the managers.
- When the photo task is done, open it: its output Photo of the aisle holds the photo prepared in the scenario.
ResultThe aisle is safe again and the signage lifted: the objective Treats Liquid spill is reached.
14:05 · A suspicious package in aisle A
At 14:05 r-iosemit creates Suspicious package in aisle A, impacting Aisle A, along the bars and the children's workshops, and also the Hall 3 entrance. The Security Manager goes to the package, keeps the visitors at a distance and photographs it, then removes the doubt (owner, video, announcement). If the owner is identified, the package is returned and the instructions reminded. If not, the Event Supervisor decides a security perimeter and calls the police; the Security Manager sets it up, the dynamic signage broadcasts the distancing and diversion message, the Ticketing Manager freezes the entries to the hall, and the cleaning and installation teams are withdrawn from the perimeter. The Police remove the doubt and end the perimeter, the Event Supervisor validates the return to normal and the Ticketing Manager resumes the entries.
- Follow the alert and the process in r-iota.
- On the map, watch the Hall 3 entrance: its state follows the sensor Hall 3 entrance gates closed, Frozen (hatched red) while the gates are closed, Open otherwise.
ResultThe output Photo of the package holds the photo of the scenario; the objective Treats Suspicious package is reached once the entries are resumed or the package returned.
End of the day
The timeline ends at 16:30. With the auto mode of r-iota, the incidents whose objectives are reached are closed on their own.
- Open the RUNS mode of r-iosemit to find the run, its settings and its moments.
ResultThe three incidents of the day have each been detected, deduced, executed and closed.
