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