Thanks for watching, please subscribe and hit the bell icon to be notified when I'm done.
Just community, heck of whatever and try to think that energy transformation sounds interesting.
How do you get into that? I want to help.
Here I'm going to show you an example on how you can do that.
Okay, thank you.
So this is a short talk, which is more of a community-oriented thing, although there's not a few technical bits in it.
So my name is Kim Takan, I'm a self-employed book and source consultant now.
And it's champagne in a corner.
So yeah, this is about how I got involved in the energy domain.
So I have some mixed technical background.
Actually before I start, I'd like to do a quick and then I'm a survey.
Can you please raise your hand if you're not currently working in the energy sector.
If you're not working for energy company.
Yes, I'd like to have a third of the audience, so this may be for you.
So this is also for people already in the energy sector.
How to bring in more people and how to make the community grow in general.
So I studied electronics, like mixed-ignore electronics and power electronics at the university,
but then I worked a lot more into the embedded software world.
So it kind of related to electronics, but more and more on the software side.
And then I worked in dedicated myself to open source world for seven years at Colour Breiner,
worked on Colour CI, which is a Linux Foundation project for testing Linux kernel.
And two years ago I decided to go freelance.
I still do some kernel stuff and some of the other pure software world activities if you want.
But one of my goals was to transition to the energy sector.
This is something I really wanted to do when I was a student.
And then we really got the opportunity to work on.
I wanted to do energy and open source.
And I got the open source box decked a few on.
Now moving more into the energy world.
So it was a big turn for me, in my career, a few months.
It started two years ago.
I came to Phels Dample to the energy bedroom.
So maybe this is a familiar place to you, a daily room that used to be the big meeting point for a Friday night.
Before Phels Dample.
So I wrote a lot of blog posts.
That was kind of me doing my homework, basically.
So I learned about what I wrote a blog post about the energy bedroom.
But also he made me think about all the different actors in the ecosystem, all the different projects,
all the different companies.
So yeah, there's my personal website. You can check more blog posts if you want.
So none of the day basically, if you come in from a software world, you might think, okay, it's electrical grids, energy, this could be dangerous.
It's dangerous if you have batteries.
It's dangerous if you have high voltage lines.
But this is fine.
You can work in energy world without having a lab without having access to dangerous stuff.
So it's basically software as usual.
That's my biggest takeaway.
As an individual, they've brought up with a laptop or an individual in your company.
If you're doing pure software, you don't really want to manage this stuff.
You can still contribute to a lot of things.
So the energy sector is really a big sector. There's lots of things, you know, from,
I guess some of these topics, I guess, we've just talked about them.
So battery technology, of course, sort of from Casting.
It's a big fan of those here as well.
And so I had to find my space there.
So there's something everybody has to do.
Like, where do you want to go basically?
And I guess it depends on lots of factors.
Mostly, like in circumstances I would say.
So eventually, I've got myself involved in digital substations.
So substation, some of you may already know this.
Substation is basically a onto call it a glorified transformer.
So it's like taking different volumes.
But from the incoming voltage between our lower voltage to higher voltage for transmission.
And then to lower voltage again, before distribution.
Also it has lots of security features.
So it needs to be used to control a circuit breakers.
If there's a problem.
And a lot of this has been done.
Well, it's always been done historically in hardware,
with lots of hardware equipment to detect when there's a fault on the line.
And actually a circuit breaker, for example.
Now there's a big effort to move this logic into software.
So that's what's called digital substations.
And one of that in exclamation projects.
I've been involved with now is C path.
So that's to provide the basic operating system to run in digital substation.
Another very important thing in this area is the ICT and the ICT-61 and 50,
which describes how a digital substation should work.
So all protocols, the ways to communicate between all the different parts of their substation.
So on detail of these diagram here, it's just to give you a quick idea.
Also this is a short talk.
So I don't have to mention it.
Yeah, key thing here is real time.
So something we can't see here is PTP.
This is precision time protocol.
And everything has to be done really real time in accurate real time.
If you want to know where there's a fault, every millisecond, something can burn.
Basically you have to really write really quickly.
And that's one of the main challenges here.
So as I've worked on this, coming from the outside world if you want.
What struck me was that there were lots of missing bits in it.
If you wanted to have a full stack to run on your own machine.
Like if you don't have an actual substation where you can deploy it.
It seems to me like some tools were available,
some tools were available in source.
And there was lots of other things that were missing to actually be able to contribute or try
in the software yourself without being in the industry already.
So in blue here you have the things that already exist.
There's the C-Path project which provides like basically a high provider to run virtual machines and containers.
That's where the logic will be to do the safety functions.
And you have compass which is a tool for configuring.
It's just all substations.
That's also an explanation project.
And you have Ansible configuration that comes with C-Path.
So you can deploy your application.
So that's already the end available.
The only way to install it right now is if you have some dedicated server.
And you install it on the server because this is what you normally have in a substation.
So something I worked on as a proof of concept was to have this in the virtual stack.
So like a net nested virtual machines basically.
So that was the first step and then I realized okay.
Now the I-C standard you can only have access to.
It's not an open standard so you need to pay to access to it.
There are some implementations of it.
But it basically all in hardware manufacturers use their own proprietary implementation.
So there isn't some effort right now.
Now I'll skip there.
There's a seam implementation that it comes with caveats.
So there's several people including me included.
Want to work on implementing the I-C-6150.
At least some parts of the standard in a rest library as well as some middleware.
So this is something that's happening now.
I can see a lot of people there interested in this.
And then having some hardware models.
So instead of having a real sensor and a real circuit breaker.
You can have some models that will receive or send these messages.
So that's some old values and groups.
These are things, messages to communicate with the hardware.
So basically the lesson learned here is coming from the outside.
There's lots of things that you can see that people in the industry don't see it.
So that's a great way of getting involved as well.
So it could be in documentation.
It could be in testing.
It could be also just to fill in the gaps from a substance point of view.
So I call it a handling experience because I had to learn a lot of things from scratch.
It's a bit like learning a new language if you want.
So actually there's a lot of terms like Watson, IED,
that's intelligent, electronic, electric device.
You hear this term a lot at the beginning.
Sometimes I felt like it was ahead of the game because some people are quite in the energy sector.
Some people are quite far away from the open source world in a way.
So a lot of people were astonished to know that I've contributed to the alien experience.
I have like thousands of people contributed to them.
It seemed like something from another planet which was quite interesting to see the difference of culture.
And so it's really important to hear basically to listen to him just talking.
I spent a lot of time listening to all, you know,
to learn all the different types of cultures and that's really interesting experience as well.
Yeah, to bridge the cultural one gap if you want.
So that's kind of what I was saying.
So there's a lot of people in the energy sector that come from a hardware background.
And you don't have the same natural inclination for using unique healths,
for example, you know, there's a lot of tools that are still based using based on Windows, for example.
So however, I found it to be really a welcoming and open-minded ecosystem.
So don't be afraid to get in touch with people.
I found some open source communities, sometimes a bit more put it to size.
I would say because they've been fighting against things to bring open source there.
So they're always very specific about things.
And that's good in a way.
Sometimes you might feel a bit difficult to join some open source communities.
In the energy world, I haven't found that to be an issue at all.
And people are really welcoming.
So that's great.
There's a lot more physics in math.
I mean, that's usually very well.
Of course you have cryptography and software engineering.
But I found there's a lot of physics and science everywhere.
So that's interesting as well.
It's a bit more refreshing in the way of you.
So, and the last thing is, of course it's a century old industry.
And electricity has been around for a long time.
And now it's becoming a lot more complex.
But the software history is relatively recent.
So that's one of my takeaways from this.
And I think that's basically where it makes sense as a contributor to join in.
If you have some past experience in software, you can help bring this.
So I feel that was basically the close loop with my first question.
If you're in this room, and you're not yet in energy sector,
I guess it was being interested in energy in open source software.
So yes, you can.
I think part in this actually.
I hope you can.
Like everybody will have a different journey.
So the way I did it was to become freelance and had some fallback options as well.
I could still work on operating system work and stuff like that.
So everybody would have a different way to do this.
It could be convincing your management.
Lots of different ways to do this.
But if you're really interested in this, I think there's definitely a good way forward.
And there's a need for new people as well.
It's good for refreshing fully industry to have people coming from different backgrounds.
And it's a big industry.
So we won't move very fast.
Don't worry.
If it takes time.
I found.
Something's move fast.
But the industry has a whole move slowly.
So yeah, big thank you for the positive organizers.
Because that really helped me actually.
When I joined the this.
Devroom 2 years ago that really opened the door to me to be able to join the energy.
The energy sector from an open source point of view.
So just naming it.
And then.
And you as well.
And I mean, you need teachers.
My coach.
And also yeah, my younger self when I was 20 years ago when I was a student.
I think that's really important to like sometimes.
Take a step back and think about what you really want to do.
So that's kind of what I did here.
I guess I was a different person from now.
So think that on the person.
Okay.
I think we still have a couple of minutes.
Three minutes.
Three.
Thank you.
So.
This.
For.
This.
So.
So the question is whether I have I'm starting.
Well, I've completely transitioned and I'm making money for myself.
So yeah, I have some contracts, but not in the energy sector yet.
So.
I could have tried to just join company, but I wanted to.
I was not really in a rush to do that.
So I wanted to.
To.
To the.
To.
And then.
But.
A.
I no.