WEBVTT 00:00.000 --> 00:09.000 Hello everybody. 00:09.000 --> 00:18.000 First, I will just say that I would not, I'm sorry. 00:18.000 --> 00:24.000 That I was not supposed to be here, but as a talk was cancelled, some people. 00:25.000 --> 00:30.000 Yesterday, I wanted to be here, just say, oh, you could present your software. 00:30.000 --> 00:32.000 It's software we work on. 00:32.000 --> 00:37.000 So, you know, I say, yes, this morning I say, why? 00:38.000 --> 00:40.000 That's what we gave you here. 00:40.000 --> 00:41.000 Yes. 00:41.000 --> 00:43.000 So here I am. 00:43.000 --> 00:47.000 So I will try to present this subject called a partner for a week. 00:47.000 --> 00:52.000 Hopefully, I already present this subject in another meeting. 00:52.000 --> 01:02.000 The presentation was, is much longer, so I will try to shorten the presentation and we'll see. 01:02.000 --> 01:10.000 So I'm working for a company with, which is called RTE, which is a French, what's called TSO, 01:10.000 --> 01:21.000 Transpator System Operator, which is in charge of the electricity supply for high voltage in a influence. 01:21.000 --> 01:31.000 And as I guess for more, for a lot of companies, the energy sector, we face more and more complex situation in the network. 01:31.000 --> 01:41.000 So the operators have more and more information, and as we have more and more information, more and more business application, more and more screens. 01:41.000 --> 01:50.000 So starting from this idea, we try to think of a more centralized way of providing information. 01:50.000 --> 01:57.000 That's one of, one of solution is, so a tool called a partner for a week. 01:57.000 --> 01:59.000 So I will switch to the presentation. 01:59.000 --> 02:02.000 I did a few times ago. 02:11.000 --> 02:15.000 So let's first start what is a partner for a week. 02:15.000 --> 02:21.000 And I will see after I will get started with using it. 02:21.000 --> 02:30.000 So a partner for a week is a tool that can help in control rooms to first centralize information. 02:30.000 --> 02:40.000 The idea is that you can, in one screen, we serve mainly events coming from business application. 02:40.000 --> 02:50.000 And you can use this tool to extend information and interaction with operators in different control rooms or inside the control rooms. 02:50.000 --> 02:56.000 So you can do the software as well as a technical module if you want. 02:56.000 --> 03:01.000 So first part is centralized real time business events. 03:01.000 --> 03:14.000 So you will see in the software we make a demonstration, that we have a good set name cards that we show events, events are on notification. 03:14.000 --> 03:20.000 And we can dispatch events depending on rules to the good operators. 03:20.000 --> 03:25.000 Of course, we are not providing this event, this business application that are creating this event. 03:25.000 --> 03:32.000 So we provide an API mainly to send events. 03:32.000 --> 03:40.000 And you can customize all the events using a template mechanism. 03:40.000 --> 03:45.000 I will no go further on another feature. 03:45.000 --> 03:51.000 The other second feature is that you can change information in real time between operators. 03:51.000 --> 03:57.000 So you can send performance message between operators in control rooms. 03:57.000 --> 04:08.000 And you can even interact with the question response mechanism and share events in calendar. 04:08.000 --> 04:10.000 So getting started. 04:10.000 --> 04:13.000 First of course, sort of on two tools. 04:13.000 --> 04:17.000 So you can all find all the information on the internet. 04:18.000 --> 04:22.000 And we made a getting started that helps you to start. 04:22.000 --> 04:28.000 So you just have to clone GitHub reports that we and to start a script. 04:28.000 --> 04:30.000 So it's working in darker environment. 04:30.000 --> 04:33.000 So you just have to have darker on your computer to use it. 04:33.000 --> 04:38.000 So I will show you. 04:38.000 --> 04:42.000 Of course, I started it before the demonstration in start. 04:42.000 --> 04:47.000 And in start it before is it ups. 04:47.000 --> 04:51.000 Okay. 04:51.000 --> 04:54.000 So we're going to use the demo configuration. 04:54.000 --> 04:57.000 Let me show you the demo configuration. 04:57.000 --> 05:02.000 Yes, so the demo configuration is completely effective. 05:02.000 --> 05:09.000 So we create demo data with control control rooms in West Europe. 05:09.000 --> 05:18.000 So first, you have nothing on the screen. 05:18.000 --> 05:21.000 And once we've gotten a pop-up inside this screen. 05:21.000 --> 05:29.000 So I will emulate, simulate some events coming from business communication. 05:29.000 --> 05:36.000 So the first event is really when you use a project just the yellow wall stuff. 05:36.000 --> 05:40.000 If, of course, it should pop. 05:40.000 --> 05:47.000 So you have on the left all the notifications are going to arise. 05:47.000 --> 05:52.000 So first one is the yellow wall stuff of our tool. 05:52.000 --> 05:57.000 But of course, you can do better than just sending simple messages. 05:57.000 --> 06:01.000 And I will show you a few examples. 06:01.000 --> 06:05.000 There is a message notification. 06:05.000 --> 06:09.000 Let's show you the one, for example. 06:09.000 --> 06:13.000 So this is another event. 06:13.000 --> 06:16.000 So this one, you can have a more complex information. 06:16.000 --> 06:24.000 So this one is an example of data quality from study modeling in RT. 06:24.000 --> 06:31.000 And as the operators can acknowledge and of course all the events. 06:31.000 --> 06:33.000 When it's not equivalent anymore. 06:33.000 --> 06:40.000 So I can filter just filter to not show any of the acknowledged information. 06:40.000 --> 06:44.000 And so this one was just graphics. 06:44.000 --> 06:53.000 You can have some stuff like it is usually in pictures to show, for example, contingency on an network. 06:53.000 --> 07:01.000 So you can introduce inside this what's so called cards. 07:01.000 --> 07:03.000 You can introduce whatever you want. 07:03.000 --> 07:05.000 It's a templating mechanism. 07:05.000 --> 07:10.000 So you just have to provide some HTML and some JavaScript. 07:10.000 --> 07:12.000 And you can make whatever you want. 07:12.000 --> 07:14.000 The idea is you can mix inside the tools. 07:14.000 --> 07:20.000 Information from different sources, different business process, different context. 07:21.000 --> 07:24.000 And of course you can plug the system with sound. 07:24.000 --> 07:25.000 So you can be sounded. 07:25.000 --> 07:30.000 And in RT we even plug it with an external sounding system. 07:30.000 --> 07:32.000 Okay. 07:32.000 --> 07:36.000 Just to show you just a template mechanism. 07:36.000 --> 07:41.000 So here for the first stuff with the yellow world just. 07:41.000 --> 07:47.000 HTML and you wish us data from the what's so called cards, the events. 07:48.000 --> 07:50.000 You can have a no. 07:50.000 --> 07:52.000 The other one. 07:52.000 --> 07:55.000 This one is more complex is the one with data quality. 07:55.000 --> 07:57.000 So. 07:57.000 --> 08:02.000 So you can you can do whatever you want with the data and put on the data as you want. 08:02.000 --> 08:05.000 And you can introduce if you want. 08:05.000 --> 08:11.000 You're using a child's library to provide some some charts. 08:11.000 --> 08:16.000 So that was first feature. 08:16.000 --> 08:19.000 And another. 08:19.000 --> 08:21.000 So that was a feature where you centralize events. 08:21.000 --> 08:23.000 Your feature is to be able to. 08:23.000 --> 08:26.000 Exxon with operators. 08:26.000 --> 08:31.000 So I have one a partner here and I have another operator that is connected to the system. 08:31.000 --> 08:34.000 So this one. 08:34.000 --> 08:36.000 He has a white screen. 08:36.000 --> 08:38.000 So you can change between night and day mode. 08:38.000 --> 08:43.000 But to his a presentation for one operator will be white and the other black. 08:43.000 --> 08:44.000 Oops. 08:44.000 --> 08:49.000 I guess. 08:49.000 --> 08:51.000 Let's say. 08:51.000 --> 08:55.000 You want to communicate and this is a partner working in different control center. 08:55.000 --> 08:58.000 But they want to exchange information. 08:58.000 --> 08:59.000 For example. 08:59.000 --> 09:03.000 So you have a way of what's called creating card. 09:03.000 --> 09:05.000 This time it's not a business application. 09:05.000 --> 09:07.000 It's simply an operator. 09:07.000 --> 09:10.000 Once to send something to another operators. 09:10.000 --> 09:12.000 It's not like a child. 09:12.000 --> 09:14.000 It's not like a team's or whatever. 09:14.000 --> 09:16.000 It's just really important message. 09:16.000 --> 09:20.000 And you need to do the other person to have it and drag knowledge it. 09:20.000 --> 09:23.000 So you can define. 09:23.000 --> 09:25.000 You can sense basic messages. 09:25.000 --> 09:26.000 Okay. 09:26.000 --> 09:27.000 But you can define. 09:27.000 --> 09:28.000 You can always. 09:28.000 --> 09:29.000 You can define. 09:29.000 --> 09:30.000 You can predefined messages. 09:30.000 --> 09:32.000 For example, one use case we have. 09:32.000 --> 09:35.000 It's in a critical situation in the grid. 09:35.000 --> 09:36.000 The power grid. 09:37.000 --> 09:40.000 It's important to communicate fast between everybody. 09:40.000 --> 09:44.000 And to communicate with all controls on control room fast. 09:44.000 --> 09:47.000 So in our actually, we have predefined situation. 09:47.000 --> 09:51.000 And the operator can just communicate with. 09:51.000 --> 09:53.000 We can define. 09:53.000 --> 09:55.000 On predefined situation. 09:55.000 --> 09:58.000 So this one is what we call a critical situation. 09:58.000 --> 10:00.000 And for example. 10:00.000 --> 10:01.000 If you have enough. 10:01.000 --> 10:03.000 Not enough margin on the system. 10:03.000 --> 10:06.000 To say to everybody. 10:06.000 --> 10:09.000 Be aware that the system is in a critical situation. 10:09.000 --> 10:10.000 Okay. 10:10.000 --> 10:12.000 Your special procedure to follow. 10:12.000 --> 10:13.000 So everything is prepared. 10:13.000 --> 10:16.000 And you just put it on your message. 10:16.000 --> 10:18.000 And you just send your message. 10:18.000 --> 10:19.000 Everybody. 10:19.000 --> 10:22.000 We should be aware of the critical situation. 10:22.000 --> 10:23.000 We will also. 10:23.000 --> 10:26.000 We'll use that message to win in the control room. 10:26.000 --> 10:28.000 And anyway, acknowledge message. 10:28.000 --> 10:30.000 So you could put whatever you want. 10:30.000 --> 10:31.000 Instruction inside the message. 10:31.000 --> 10:35.000 Which are already, which are present before. 10:35.000 --> 10:38.000 So for example, if I acknowledge this message. 10:38.000 --> 10:40.000 And I will see. 10:40.000 --> 10:42.000 I can see in C and follow. 10:42.000 --> 10:43.000 Not this. 10:43.000 --> 10:44.000 So win. 10:44.000 --> 10:46.000 Just make a mistake on it. 10:46.000 --> 10:47.000 I think it's a demo. 10:47.000 --> 10:48.000 Okay. 10:48.000 --> 10:49.000 It's a demo stuff. 10:49.000 --> 10:50.000 Okay. 10:50.000 --> 10:52.000 It should mean not be acknowledged for me. 10:52.000 --> 10:53.000 But. 10:53.000 --> 10:54.000 Okay. 10:54.000 --> 10:56.000 So you see. 10:56.000 --> 10:57.000 You see. 10:57.000 --> 10:59.000 You can see here. 11:00.000 --> 11:03.000 All the control control rooms are acknowledge message. 11:03.000 --> 11:04.000 Okay. 11:04.000 --> 11:07.000 You even have some mechanism where you can massage a message if, 11:07.000 --> 11:09.000 in a certain period of time, you know, 11:09.000 --> 11:13.000 if one of the control fronters did not acknowledge a message 11:13.000 --> 11:15.000 for, let's say, after five minutes. 11:15.000 --> 11:16.000 Okay. 11:19.000 --> 11:21.000 And other. 11:21.000 --> 11:23.000 Oops. 11:23.000 --> 11:26.000 And you can provide more. 11:26.000 --> 11:28.000 More complex situation, for example. 11:29.000 --> 11:31.000 Here it's. 11:31.000 --> 11:35.000 Here we have we have some situation on network, which are new situation today. 11:35.000 --> 11:37.000 Where. 11:37.000 --> 11:40.000 Due to the market price. 11:40.000 --> 11:44.000 If we, we had some. 11:44.000 --> 11:45.000 Some. 11:45.000 --> 11:50.000 Time where the price of electricity became let's say negative or willy low. 11:50.000 --> 11:53.000 And certainly every renewable. 11:53.000 --> 11:57.000 Power plant just stop producing electricity. 11:57.000 --> 12:01.000 So it's a big problem for the network because so the network. 12:01.000 --> 12:04.000 Go down and just have to go up. 12:04.000 --> 12:06.000 So the goes willy fast. 12:06.000 --> 12:08.000 So it was a new situation for Archie. 12:08.000 --> 12:09.000 Okay. 12:09.000 --> 12:11.000 And. 12:11.000 --> 12:14.000 We need to to tell people. 12:14.000 --> 12:17.000 The situation is going to rise in two hours in three hours. 12:17.000 --> 12:18.000 We want to dissipate it. 12:18.000 --> 12:20.000 We are no tools to do that. 12:20.000 --> 12:21.000 We have. 12:21.000 --> 12:22.000 Okay. 12:22.000 --> 12:23.000 So. 12:23.000 --> 12:25.000 You can create fast in about five weeks sort of forms. 12:25.000 --> 12:26.000 You can create fast template. 12:26.000 --> 12:31.000 Prepare all the field and the operator within charge of monitoring this stuff. 12:31.000 --> 12:33.000 Concert the message to all control room fast. 12:33.000 --> 12:34.000 Okay. 12:34.000 --> 12:35.000 So this is a 50 one. 12:35.000 --> 12:36.000 It's not. 12:36.000 --> 12:38.000 So that's that's the idea. 12:38.000 --> 12:40.000 The idea is with this template mechanism. 12:40.000 --> 12:42.000 You can fast deploy a new. 12:42.000 --> 12:44.000 Use case in production. 12:44.000 --> 12:45.000 Okay. 12:45.000 --> 12:47.000 So it's. 12:47.000 --> 12:48.000 So it's. 12:48.000 --> 12:51.000 The template I show you are dynamically loaded. 12:51.000 --> 12:54.000 So you don't you don't you don't have to to we started. 12:54.000 --> 13:01.000 The two just I have to push a new version and you use case and it's instantly in production. 13:01.000 --> 13:04.000 Okay. 13:04.000 --> 13:08.000 Let's go back to this line. 13:08.000 --> 13:12.000 So I did this one. 13:12.000 --> 13:13.000 This one. 13:13.000 --> 13:14.000 I show you. 13:14.000 --> 13:16.000 So. 13:17.000 --> 13:18.000 Um. 13:18.000 --> 13:21.000 In our chief for business what's. 13:21.000 --> 13:25.000 What's interesting is when you have a new new business case, new use case. 13:25.000 --> 13:29.000 You can first extend simple message between operators. 13:29.000 --> 13:32.000 And if the situation is a long. 13:32.000 --> 13:36.000 More than multi time let's say you can configure predefined message. 13:36.000 --> 13:39.000 And you can define custom screen and things like that. 13:39.000 --> 13:40.000 Okay. 13:40.000 --> 13:42.000 And the great thing is. 13:42.000 --> 13:44.000 If for example. 13:44.000 --> 13:46.000 On my example. 13:46.000 --> 13:47.000 Uh. 13:47.000 --> 13:51.000 Tomorrow we have a tool that can predict this loss of power. 13:51.000 --> 13:52.000 Or the wind farms. 13:52.000 --> 13:53.000 We can. 13:53.000 --> 13:54.000 We can. 13:54.000 --> 13:59.000 We can still have the same one doing but this time it's not going to be. 13:59.000 --> 14:02.000 It's not going to be the operator sense of message within applications. 14:02.000 --> 14:05.000 That's going to send a message in this. 14:05.000 --> 14:08.000 So this time it's going to be business applications. 14:08.000 --> 14:12.000 It's going to send the same message as the operators. 14:12.000 --> 14:13.000 Okay. 14:13.000 --> 14:16.000 Let's go back if I have it. 14:16.000 --> 14:17.000 Yeah. 14:17.000 --> 14:18.000 So this one. 14:18.000 --> 14:21.000 Okay. 14:21.000 --> 14:25.000 So the idea is that you can using a pattern for a week. 14:25.000 --> 14:28.000 Just implement some process fast and test some process. 14:28.000 --> 14:29.000 So make some of that. 14:29.000 --> 14:30.000 Okay. 14:30.000 --> 14:34.000 No. 14:34.000 --> 14:36.000 What. 14:37.000 --> 14:38.000 Yes. 14:38.000 --> 14:40.000 I have five minutes left. 14:40.000 --> 14:42.000 Okay. 14:42.000 --> 14:45.000 And you have a mechanism of question response. 14:45.000 --> 14:47.000 So you can define some. 14:47.000 --> 14:48.000 Some mechanism. 14:48.000 --> 14:49.000 It's not. 14:49.000 --> 14:51.000 Only sending information. 14:51.000 --> 14:52.000 You can reply to information. 14:52.000 --> 14:53.000 Yeah. 14:53.000 --> 14:54.000 What. 14:54.000 --> 14:56.000 I can do. 14:56.000 --> 14:57.000 Hmm. 14:57.000 --> 14:59.000 Yeah. 14:59.000 --> 15:00.000 Okay. 15:00.000 --> 15:01.000 Sorry. 15:01.000 --> 15:03.000 Um. 15:04.000 --> 15:05.000 We use it. 15:05.000 --> 15:08.000 We use this use case in in archie again. 15:08.000 --> 15:09.000 Um. 15:09.000 --> 15:10.000 Um. 15:10.000 --> 15:11.000 With the archi departments. 15:11.000 --> 15:13.000 The problem we face is. 15:13.000 --> 15:15.000 Um. 15:15.000 --> 15:17.000 Historically. 15:17.000 --> 15:18.000 It's. 15:18.000 --> 15:19.000 It's. 15:19.000 --> 15:23.000 Part of font situation of font as his own control center with his own scar assistant. 15:23.000 --> 15:24.000 Okay. 15:24.000 --> 15:26.000 For people who know scar assistant. 15:26.000 --> 15:27.000 And. 15:27.000 --> 15:30.000 We change this to other one central scar assistant. 15:30.000 --> 15:32.000 But we keep what you know people. 15:32.000 --> 15:33.000 Okay. 15:33.000 --> 15:37.000 And it means when you need to touch the central scar assistant, which is critical for 15:37.000 --> 15:39.000 your character. 15:39.000 --> 15:41.000 You can do that whenever you want. 15:41.000 --> 15:44.000 So you need to coordinate it to ask everybody is it possible for now. 15:44.000 --> 15:46.000 Is it possible now to touch this stuff. 15:46.000 --> 15:47.000 Is it the. 15:47.000 --> 15:48.000 Are you in a critical situation? 15:48.000 --> 15:51.000 Are you in a situation where I can touch this tool. 15:51.000 --> 15:53.000 So we use. 15:53.000 --> 15:57.000 Operator for make to send message to the operator and ask them. 15:57.000 --> 15:58.000 Is it okay? 15:58.000 --> 15:59.000 If I. 15:59.000 --> 16:00.000 Is it okay? 16:00.000 --> 16:01.000 If I. 16:01.000 --> 16:03.000 If I change the configuration of the scar assistant. 16:03.000 --> 16:04.000 Are you all okay? 16:04.000 --> 16:08.000 So I teach system use it as well when you have a problem. 16:08.000 --> 16:10.000 For example, you have a problem to scar assistant. 16:10.000 --> 16:11.000 They can communicate to everybody. 16:11.000 --> 16:12.000 We have a problem. 16:12.000 --> 16:13.000 And they can exchange with it. 16:13.000 --> 16:14.000 Okay. 16:14.000 --> 16:16.000 So let's make sure the question was. 16:16.000 --> 16:17.000 Make an exam. 16:17.000 --> 16:18.000 Maybe. 16:18.000 --> 16:20.000 The. 16:20.000 --> 16:22.000 The. 16:22.000 --> 16:23.000 The. 16:23.000 --> 16:24.000 The. 16:24.000 --> 16:26.000 Lost with my. 16:26.000 --> 16:30.000 So it's just basic card, but you can you can ask a question to your 16:30.000 --> 16:31.000 character. 16:31.000 --> 16:32.000 So that is my question. 16:32.000 --> 16:33.000 Okay. 16:33.000 --> 16:37.000 So no, so much. 16:37.000 --> 16:40.000 So you can ask question. 16:40.000 --> 16:44.000 And you is the operator, which. 16:44.000 --> 16:46.000 You know, we said you question. 16:46.000 --> 16:47.000 And of course, so it. 16:47.000 --> 16:49.000 It's a demo effect. 16:49.000 --> 16:51.000 It should be able to respond. 16:51.000 --> 16:54.000 And you, you see all the responses in the end of the card. 16:54.000 --> 16:55.000 Yeah. 16:55.000 --> 16:57.000 Anyway, I'm not so much time. 16:57.000 --> 16:59.000 And so you see your. 16:59.000 --> 17:00.000 You see it here. 17:00.000 --> 17:03.000 So each time in a part of the punch, everybody sees a response. 17:03.000 --> 17:05.000 So we can action and we are time. 17:05.000 --> 17:07.000 We got in this specific situation. 17:07.000 --> 17:09.000 And last. 17:09.000 --> 17:10.000 That was not. 17:11.000 --> 17:13.000 Something we we. 17:13.000 --> 17:15.000 We especially wanted, but that's. 17:15.000 --> 17:19.000 A needs that was not cover in the control rooms. 17:19.000 --> 17:22.000 Is we're guarding task. 17:22.000 --> 17:25.000 As you know, it's. 17:25.000 --> 17:26.000 The. 17:26.000 --> 17:27.000 The. 17:27.000 --> 17:28.000 The. 17:28.000 --> 17:29.000 The. 17:29.000 --> 17:30.000 The. 17:30.000 --> 17:31.000 The. 17:31.000 --> 17:32.000 The. 17:32.000 --> 17:33.000 The. 17:33.000 --> 17:34.000 The. 17:34.000 --> 17:35.000 The. 17:35.000 --> 17:36.000 The. 17:36.000 --> 17:37.000 The. 17:37.000 --> 17:38.000 The. 17:38.000 --> 17:39.000 The. 17:39.000 --> 17:42.000 The. 17:42.000 --> 17:44.000 Please Oh. 17:44.000 --> 17:48.000 It. 17:48.000 --> 17:49.000 So. 17:49.000 --> 17:50.000 It. 17:50.000 --> 17:52.000 If you go. 17:52.000 --> 17:54.000 있지. 17:54.000 --> 17:57.000 So it's. 17:57.000 --> 18:06.000 K billion, 20. 18:06.000 --> 18:28.200 So the technical research is on the back Java, so we have some modules, I would not take 18:28.200 --> 18:33.960 my microservice, but a few modules in Java, and some modules are not the GIS, and in the 18:33.960 --> 18:52.960 front we are using Angular's Angular framework. 18:52.960 --> 19:01.960 Yes, this one. 19:01.960 --> 19:11.960 So for this one, the idea is that we call an API that gives us a network diagram. 19:11.960 --> 19:19.960 But this one is just an example with SVG, but in real life, we just call an API that gives us 19:19.960 --> 19:28.960 the diagram. 19:28.960 --> 19:34.960 In fact, when we want to generate automatic events, it's the next one or two, that's just 19:34.960 --> 19:35.960 called our API. 19:35.960 --> 19:42.960 Okay, the only automatic stuff we have is when we have this with mine feature, so you can 19:42.960 --> 19:50.960 say this task feature, you can show here, you have an agenda, so you can create task, 19:50.960 --> 19:53.960 and it can make sure you will mind of task. 19:53.960 --> 20:08.960 So as it's in charge of business tools, that generates the events. 20:08.960 --> 20:13.960 Yeah, yeah, it's using both use case, so use case where you have an application, the 20:13.960 --> 20:20.960 detected problems, so this sends a problem, and in the case where it's an operator, we 20:20.960 --> 20:29.960 need to inform someone, okay, times up, but I will be outside if you have any question 20:29.960 --> 20:31.960 or no, and I'll see you all in a minute.