WEBVTT 00:00:01.084 --> 00:00:04.167 Every city is made up of millions of movements. 00:00:04.167 --> 00:00:08.432 People, services and decisions that need a shared understanding. 00:00:08.432 --> 00:00:14.598 LEXIMAR Global Hub connects that reality, turning shared context into a coordinated response. 00:00:18.734 --> 00:00:22.021 An urban fire draws attention to the central district. 00:00:22.021 --> 00:00:26.769 In Smart City, the decision-maker locates the incident and opens its context. 00:00:30.887 --> 00:00:33.494 Protecting the area is the first priority. 00:00:33.494 --> 00:00:37.900 The perimeter defines the affected zone before any action on mobility. 00:00:47.111 --> 00:00:50.376 Layers connect traffic, transit and emergency services. 00:00:50.376 --> 00:00:55.006 Each team can understand the same event through the needs of its own service. 00:00:59.136 --> 00:01:02.916 The affected road segments and priority corridor are identified. 00:01:02.916 --> 00:01:05.869 The mobility alternative is presented for review. 00:01:09.992 --> 00:01:16.447 When the response requires coordination between operators, the full context follows the incident into Supervisor. 00:01:20.575 --> 00:01:25.962 Supervisor brings the five operators and twelve affected routes together in one network view. 00:01:30.088 --> 00:01:35.429 The decision-maker reviews the territorial scope and the restrictions that every operation must respect. 00:01:39.566 --> 00:01:42.173 Every message stays linked to the incident. 00:01:42.173 --> 00:01:46.903 Sending, delivery, reading and acknowledgement form part of its traceability. 00:02:09.983 --> 00:02:16.624 The alternatives allow a comparison between a coordinated diversion and possible reinforcement, which still needs review. 00:02:20.757 --> 00:02:22.411 LEXIMAR provides the context. 00:02:22.411 --> 00:02:27.259 The responsible person chooses the response and records the reason for the decision. 00:02:36.471 --> 00:02:40.650 The decision is linked to its owner and prepared for the team that will carry it out. 00:02:44.779 --> 00:02:49.841 Operator receives the same incident, with the selected alternative and the network restrictions. 00:02:53.973 --> 00:03:01.171 In the operational workspace, the route, service, vehicle and driver appear as one connected reality. 00:03:05.304 --> 00:03:10.644 Before acting, the decision-maker checks field conditions and the scope of the affected service. 00:03:14.773 --> 00:03:20.207 The route review identifies restricted stops and the available alternatives for maintaining service. 00:03:24.351 --> 00:03:28.173 The network decision requires separate operational authorisation. 00:03:28.173 --> 00:03:30.760 Responsibility and the reason are recorded. 00:03:39.955 --> 00:03:43.809 The driver receives the alternative route and the stops to skip. 00:03:43.809 --> 00:03:47.060 Their acknowledgement allows the process to continue. 00:04:15.190 --> 00:04:20.577 Once the action is authorised, the service moves to the alternative route and operations continue. 00:04:24.702 --> 00:04:30.182 Monitoring makes execution visible and records what happens to the service while the incident continues. 00:04:34.320 --> 00:04:37.321 Service continuity with a diversion is confirmed. 00:04:37.321 --> 00:04:41.240 Restrictions and outstanding risks remain visible to all teams. 00:04:45.372 --> 00:04:51.084 The result keeps authorisation, communications and evidence of execution together in one record. 00:04:55.236 --> 00:04:58.003 The network receives this operational result. 00:04:58.003 --> 00:05:01.877 Recovery begins with the same history, without losing context. 00:05:06.005 --> 00:05:09.732 The decision-maker confirms that the fire is under control. 00:05:09.732 --> 00:05:13.017 Severity decreases and recovery of the area begins. 00:05:22.255 --> 00:05:26.388 The protection perimeter is explicitly reduced before mobility is restored. 00:05:30.563 --> 00:05:33.588 Both affected road segments become available again. 00:05:33.588 --> 00:05:36.554 Restoring the route still requires authorisation. 00:05:40.689 --> 00:05:46.401 Supervisor reviews the operators and routes, and withdraws the pending reinforcement that is no longer needed. 00:05:50.550 --> 00:05:56.772 Operator checks that the corridor has reopened and reviews service conditions before proposing a return to normal. 00:06:00.916 --> 00:06:07.417 Returning to the usual route is authorised through a new decision, with the responsible person and reason recorded. 00:06:16.633 --> 00:06:20.859 The driver receives the instruction to resume the original route and its stops. 00:06:25.001 --> 00:06:29.691 Delivery, reading and acknowledgement of the instruction are recorded before the return. 00:06:51.535 --> 00:06:56.365 The service resumes its usual route and both affected stops return to operation. 00:07:00.502 --> 00:07:03.060 The network and service return to normal. 00:07:03.060 --> 00:07:06.492 Extraordinary measures give way to regular operations. 00:07:10.635 --> 00:07:16.069 After verifying recovery, the responsible person closes the incident and records the decision. 00:07:25.282 --> 00:07:31.458 The audit trail brings decisions, messages and status changes together to review how the response unfolded. 00:07:35.694 --> 00:07:37.785 The city regains its rhythm. 00:07:37.785 --> 00:07:42.490 From territory to network, and from coordination to execution. 00:07:42.490 --> 00:07:43.983 LEXIMAR Global Hub. 00:07:43.983 --> 00:07:46.746 Where movement becomes intelligence.