WEBVTT

00:00:00.056 --> 00:00:01.506 A:middle
>> My name is John Hart.

00:00:02.136 --> 00:00:05.646 A:middle
And I am an electrical power
systems protection engineer.

00:00:06.366 --> 00:00:09.766 A:middle
So part of what I do is setting
protective devices

00:00:09.766 --> 00:00:13.206 A:middle
to protect Duke Energy's
distribution electric grid.

00:00:13.896 --> 00:00:19.036 A:middle
I also work in the field with some of
these devices, hands-on in some scenarios.

00:00:19.696 --> 00:00:25.116 A:middle
And so basically, what setting a protection
device means is that I use modeling software,

00:00:25.526 --> 00:00:31.386 A:middle
I look at available fault duties in any given
area of the system, and I set the devices

00:00:31.386 --> 00:00:33.616 A:middle
that protect that area according
to what I model.

00:00:34.396 --> 00:00:38.096 A:middle
And so my job is to pull those
models into the simulation software

00:00:38.426 --> 00:00:42.306 A:middle
and I can throw different scenarios at
it and I can see what the grid will do

00:00:42.306 --> 00:00:43.886 A:middle
in response to those different scenarios.

00:00:44.256 --> 00:00:51.036 A:middle
So looking for the relative available
fault duty -- and when we say fault duty,

00:00:51.036 --> 00:00:56.206 A:middle
I mean how high can the current spike
in a given area if we have a problem?

00:00:56.596 --> 00:01:00.976 A:middle
And so based on that, that dictates
kind of how we set our devices.

00:01:01.306 --> 00:01:05.996 A:middle
And then another big piece of my job is dealing
with emerging issues that pop up where maybe one

00:01:05.996 --> 00:01:08.936 A:middle
of these devices that's already out there,
already been commissioned and in service,

00:01:09.266 --> 00:01:12.896 A:middle
maybe it worked properly, but we have
a problem that we can't figure out

00:01:12.896 --> 00:01:15.436 A:middle
or maybe it didn't work properly
and we had an issue.

00:01:15.436 --> 00:01:20.526 A:middle
And they're kind of -- it's an after the fact,
kind of like an outage follow-up sort of thing.

00:01:20.526 --> 00:01:22.916 A:middle
So wee look into a lot of those scenarios.

00:01:23.086 --> 00:01:28.306 A:middle
And that's not my primary role, but if
there is something that the guys that do

00:01:28.306 --> 00:01:29.726 A:middle
that on a regular basis can't figure out,

00:01:29.726 --> 00:01:31.886 A:middle
sometimes they send it to
me and I get to look at it.

00:01:31.886 --> 00:01:36.226 A:middle
So we have a number of roles at the
company that do have an on-call, you know,

00:01:36.326 --> 00:01:39.836 A:middle
part and those type of responsibilities
kind of bounce around.

00:01:40.096 --> 00:01:42.956 A:middle
So you may have it one week and you may
not the next week two or three or whatever.

00:01:42.956 --> 00:01:45.186 A:middle
I fortunately am not in one of those roles.

00:01:45.186 --> 00:01:46.546 A:middle
So I'm not an on-call guy.

00:01:46.546 --> 00:01:49.706 A:middle
So if you catch me between 8:00
and 5:00 with a problem, great.

00:01:49.706 --> 00:01:52.416 A:middle
And if it's not, I'll get to it on Monday.

00:01:52.416 --> 00:01:53.266 A:middle
You know, that sort of thing.

00:01:53.346 --> 00:01:55.086 A:middle
So it's pretty nice that way.