Data Management, The Path to Develop a Digial Twin | SSP iLLUMINATE 2020

2
00:00:02.490 --> 00:00:06.390
and welcome to today's Illuminate webinar series, topic Data Management,

3
00:00:06.570 --> 00:00:11.350
the Path to develop a Digital Twin. Your speaker today will be Michael Goggin.

4
00:00:11.540 --> 00:00:13.950
Michael is a principal consultant with S S P,

5
00:00:13.950 --> 00:00:17.830
working with utilities to develop their foundational geospatial direction.

6
00:00:18.330 --> 00:00:21.030
He has been part of mapping utilities for 28 years,

7
00:00:21.100 --> 00:00:25.830
from the many diverse perspectives of working for a utility for 13 years

8
00:00:26.090 --> 00:00:30.590
at Commonwealth Edison as a software provider working for nine years at Esri,

9
00:00:30.970 --> 00:00:33.190
and as a consultant spanning the last six years.

10
00:00:34.180 --> 00:00:37.270
Michael will be answering questions at the end of his presentation,

11
00:00:37.370 --> 00:00:42.270
so please enter your questions along the way in the q and a button on your

12
00:00:42.270 --> 00:00:44.180
webinar toolbar. Finally,

13
00:00:44.380 --> 00:00:48.780
a recorded version of this webinar will be made available at a later date.

14
00:00:48.970 --> 00:00:50.220
Michael, whenever you're ready.

15
00:00:50.790 --> 00:00:54.380
Thank you very much. I appreciate that, uh, introduction. Um,

16
00:00:54.680 --> 00:00:58.700
and I really appreciate, uh, the time that you're taking today to, uh,

17
00:00:58.850 --> 00:01:03.420
come in and check out, uh, this, uh, presentation. Uh, it's something that,

18
00:01:04.400 --> 00:01:08.980
uh, has been on my mind for a majority of my career, uh, this concept of,

19
00:01:09.120 --> 00:01:11.700
of data management, uh, and, uh,

20
00:01:11.770 --> 00:01:14.820
it's ever more important now as we start looking at, uh,

21
00:01:14.820 --> 00:01:19.660
the utility of the future. And, um, you know, we start talking about this, uh,

22
00:01:19.660 --> 00:01:22.900
this concept of digital twin. So the, uh,

23
00:01:22.920 --> 00:01:26.820
the culmination of this presentation today is to really kind of, uh,

24
00:01:26.840 --> 00:01:31.060
define a couple of those. So, to kind of take a look at, uh, data management,

25
00:01:31.330 --> 00:01:34.660
kind of define it a little bit. It's the way I see it at least. Uh,

26
00:01:34.740 --> 00:01:39.310
it's also to define a little bit, um, the digital twin. Uh, what is that?

27
00:01:39.460 --> 00:01:43.190
It's a buzzword. Uh, people are talking about it, but what does it really mean?

28
00:01:43.780 --> 00:01:48.670
I'll do my best to try to, uh, define those as, as well as I can.

29
00:01:49.170 --> 00:01:53.550
Uh, and then I'll get into, uh, kind of how to get there,

30
00:01:54.010 --> 00:01:57.870
uh, from, from my observations of where some folks are these days.

31
00:01:58.400 --> 00:02:03.190
Today we're gonna be talking about, uh, the digital twin as well as, you know,

32
00:02:03.190 --> 00:02:07.830
data management. So, if, if I asked you, um,

33
00:02:08.210 --> 00:02:12.990
you know, is GIS a critical part of your utility, right?

34
00:02:12.990 --> 00:02:16.570
Whether it's gas or electric, you know, what would your answer be?

35
00:02:18.160 --> 00:02:18.993
Okay,

36
00:02:20.580 --> 00:02:24.880
if I then asked the executives within your organization,

37
00:02:26.220 --> 00:02:30.760
is GIS critical to the organization? I'd be willing to bet,

38
00:02:30.760 --> 00:02:35.460
because I've heard it, that both, uh, the geospatial group,

39
00:02:35.560 --> 00:02:36.980
as well as the executives,

40
00:02:37.280 --> 00:02:40.740
as well as a lot of people that are surrounded within the organization,

41
00:02:41.270 --> 00:02:44.860
would all say, yes, it is definitely part of, uh,

42
00:02:44.940 --> 00:02:48.700
a critical part of the organization overall. Um, you know,

43
00:02:48.700 --> 00:02:52.220
not only does apri provide some, uh, immediate benefits on its own,

44
00:02:52.800 --> 00:02:56.380
but it also provides, you know, the network, um,

45
00:02:57.320 --> 00:03:02.160
to these network enabled systems like outage management or A D M S or

46
00:03:02.580 --> 00:03:07.050
gas outage and stuff like that. So then if I asked you,

47
00:03:07.070 --> 00:03:11.530
the other question is, how is the data within your GIS today,

48
00:03:11.780 --> 00:03:15.400
right? So what's the health of your data now, you know,

49
00:03:15.440 --> 00:03:20.120
I define health, you know, as, uh, complete, accurate,

50
00:03:20.660 --> 00:03:25.310
and timely, right? Uh, so those three things make up,

51
00:03:26.010 --> 00:03:29.310
uh, what I would consider health. You know, what, what would you say to that?

52
00:03:30.400 --> 00:03:32.270
Well, actually,

53
00:03:32.350 --> 00:03:37.350
a lot of you have said a lot over the time that I've been out into

54
00:03:37.350 --> 00:03:39.870
the consulting world, right? So this six or seven years,

55
00:03:39.890 --> 00:03:44.190
and I've been trying to, uh, you know, help organizations, um,

56
00:03:44.410 --> 00:03:47.870
get to one place or another, whether it's, uh, to an outage system,

57
00:03:47.930 --> 00:03:52.630
to an A D M S migration, to, uh, engineering design, uh,

58
00:03:52.630 --> 00:03:56.230
integrated design, uh, field work inspections, right?

59
00:03:56.230 --> 00:04:00.070
There's a lot of input, right, that I have received over time.

60
00:04:01.230 --> 00:04:06.170
So my observation is that all utilities have

61
00:04:06.170 --> 00:04:10.570
a data problem, right? So, kind of some of those things that, uh, you know,

62
00:04:10.810 --> 00:04:14.330
I see there, I see, you know, the spatial accuracy, right? As one,

63
00:04:14.510 --> 00:04:19.250
that's kind of one of the more common known ones, spatial accuracy, right? So,

64
00:04:19.250 --> 00:04:22.570
conflation, there's been a lot of conflation over the years. You know,

65
00:04:22.570 --> 00:04:27.170
the data sources that were, um, used to originally create your gis, uh,

66
00:04:27.170 --> 00:04:29.130
they weren't as accurate as they are today. The,

67
00:04:29.130 --> 00:04:32.370
the devices to capture stuff were weren't as accurate back then as they are

68
00:04:32.370 --> 00:04:33.440
today. Um,

69
00:04:33.440 --> 00:04:37.800
so spatial accuracy is definitely one of those lean legacy type points. Uh,

70
00:04:37.800 --> 00:04:42.680
but there's also the record and attributes accuracy, right? That's the,

71
00:04:43.180 --> 00:04:45.880
you know, how accurate is the,

72
00:04:45.900 --> 00:04:50.440
the attributes of a record within your GIS system? Is it have all the data,

73
00:04:50.690 --> 00:04:55.280
right? Does it, does the data that does have, is it correct? Is that the right,

74
00:04:55.540 --> 00:04:58.120
uh, streetlight size? Is that the right, uh,

75
00:04:58.530 --> 00:05:03.520
valve number of turns to operate that? Um, you know, that's the nature of that

76
00:05:05.040 --> 00:05:07.160
completeness, right? I kind of spoke to that just a little bit.

77
00:05:07.180 --> 00:05:11.520
So it's really the completeness. How much information is,

78
00:05:11.580 --> 00:05:16.200
is inside your GIS system, right? Maybe when you created your, uh,

79
00:05:16.680 --> 00:05:20.440
original system, you had a lot of attributes for, uh, the different features,

80
00:05:20.440 --> 00:05:23.200
right? The different assets within your organization.

81
00:05:24.490 --> 00:05:27.040
Maybe you never really populated those,

82
00:05:27.100 --> 00:05:30.280
cuz your workflows never really supported it, right? Um,

83
00:05:30.820 --> 00:05:34.040
and or maybe you have some data in there and you,

84
00:05:34.040 --> 00:05:35.520
you don't have the rest of the data.

85
00:05:35.540 --> 00:05:37.920
So some data was captured and some data was not.

86
00:05:37.920 --> 00:05:40.560
That happens sometimes with different operating companies coming together,

87
00:05:40.660 --> 00:05:43.800
or different parts, divisions, I guess, if you will.

88
00:05:44.030 --> 00:05:47.720
Some groups capture it and some groups don't. So that stuff happens. Uh,

89
00:05:47.720 --> 00:05:51.480
timeliness, right? This one is, is becoming more significant,

90
00:05:52.540 --> 00:05:57.040
um, as technology progresses within, uh,

91
00:05:57.100 --> 00:06:01.680
an organization, right? So timeliness is, is how fast, uh,

92
00:06:01.820 --> 00:06:06.200
do you get your assets, uh, or your edits, um,

93
00:06:06.390 --> 00:06:11.160
inserts updates or deletes into your GIS after it has been,

94
00:06:11.540 --> 00:06:13.240
uh, put into the field, right?

95
00:06:13.660 --> 00:06:18.280
So it's been either energized or it's been gased. Uh, how long does it take,

96
00:06:18.370 --> 00:06:22.720
right? Uh, this concept, or not even a concept, this notion of a backlog, right?

97
00:06:22.720 --> 00:06:26.840
How, how much of a backlog do you have? Or what does your process allow, right?

98
00:06:26.900 --> 00:06:30.920
So, um, we're saying, um, in one organization that, you know,

99
00:06:30.920 --> 00:06:33.760
we're given eight weeks to an organization, to a field group,

100
00:06:33.960 --> 00:06:38.160
or for that asset information to flow back into the geospatial department so

101
00:06:38.160 --> 00:06:41.800
that it could be placed and put into your GIS system. Uh,

102
00:06:41.800 --> 00:06:46.080
and I see other places that have, you know, really large backlogs. Um,

103
00:06:46.230 --> 00:06:50.640
when I hear years mentioned, uh, not like one year, two year, three year,

104
00:06:50.640 --> 00:06:55.280
but actual years, 2019, 2018, 2017,

105
00:06:55.540 --> 00:07:00.080
that's a real good indicator that something's just not right.

106
00:07:00.900 --> 00:07:04.040
Uh, that those edits shouldn't be, um,

107
00:07:04.190 --> 00:07:08.320
lost out there regardless of what they are, right? I get the, the realities of,

108
00:07:08.320 --> 00:07:10.640
uh, you know, a large job, uh, subdivision as an example.

109
00:07:10.960 --> 00:07:13.520
Probably the biggest one that's ever brought in front of me is like, well,

110
00:07:13.520 --> 00:07:15.600
you know, that subdivision may take, you know, two,

111
00:07:15.600 --> 00:07:20.080
three years to get completed, right? But along the way,

112
00:07:20.420 --> 00:07:23.560
things are getting energized, right? So people are moving in,

113
00:07:23.820 --> 00:07:27.520
meters are being set, and the power or the gas is being run,

114
00:07:27.700 --> 00:07:29.240
but the work order's not closed out.

115
00:07:29.240 --> 00:07:32.680
So the work orders what would flow into the geospatial department, right?

116
00:07:32.680 --> 00:07:36.600
The technicians, I understand that, that that's a scenario.

117
00:07:37.180 --> 00:07:40.640
But there's a, there's, there's, you have to work through that scenario.

118
00:07:41.180 --> 00:07:45.920
You can't have assets in the field that are energized or gased and not mapped.

119
00:07:46.760 --> 00:07:51.380
You know, that. I know that. It's, cuz you tell me that,

120
00:07:51.380 --> 00:07:55.140
that that's not right. Um, so that's the, the timeliness of it.

121
00:07:56.320 --> 00:07:58.020
Um, other ones are, uh,

122
00:07:58.020 --> 00:08:02.460
where systems are integrated and the data doesn't match. Very,

123
00:08:02.460 --> 00:08:06.620
very common. Could be many different things, but, but that's another, um,

124
00:08:06.980 --> 00:08:10.360
scenario out there that I see often. The other one, uh,

125
00:08:10.380 --> 00:08:14.360
the last one I'll list is really like data, uh, uh, disparate data, right?

126
00:08:14.380 --> 00:08:19.320
So an organization that, um, you know, may have, uh, their data or their system,

127
00:08:20.020 --> 00:08:23.840
um, kind of captured in multiple different places, right? Whether it's, uh,

128
00:08:23.930 --> 00:08:28.240
maybe your meters or on meter cards or services are on service cards, or,

129
00:08:28.820 --> 00:08:33.640
um, valve regulator stations or regulator stations rather are in,

130
00:08:33.740 --> 00:08:35.360
you know, a CAD or on paper,

131
00:08:35.500 --> 00:08:40.480
or it's a substation on the electric side or a vault or a large switching

132
00:08:40.480 --> 00:08:44.320
cabinet, right? That's more complex and you just,

133
00:08:44.460 --> 00:08:47.440
you choose to maybe base cuz you had to,

134
00:08:47.980 --> 00:08:50.920
you have that place and you manage it somewhere else, right?

135
00:08:50.940 --> 00:08:55.080
One of the larger ones I ever saw was, you know, the most of the system was,

136
00:08:55.540 --> 00:08:58.800
was in gis, but once you got into the urban areas, right?

137
00:08:58.800 --> 00:09:03.650
The downtown areas of something, it was in CAD and, you know, so you had,

138
00:09:03.650 --> 00:09:05.890
you know, multiple departments needed to manage that,

139
00:09:05.890 --> 00:09:09.490
and they had to coordinate it in one lines and, and the GIS updates. And,

140
00:09:09.910 --> 00:09:11.810
you know, circuits don't only, you know,

141
00:09:11.810 --> 00:09:16.640
confine themselves into the urban areas. So that would read along the,

142
00:09:16.820 --> 00:09:20.800
um, you know, the data, uh, disparate data sources.

143
00:09:22.790 --> 00:09:27.530
So this data, right? And, and impact,

144
00:09:28.380 --> 00:09:30.720
it has impacts many things, right?

145
00:09:30.820 --> 00:09:35.120
So workflows are definitely one of 'em. You've got, um,

146
00:09:35.120 --> 00:09:38.600
what I'll call, uh, geo dependent systems, right?

147
00:09:38.620 --> 00:09:42.960
So geo dependent systems are like what I mentioned earlier, um,

148
00:09:43.070 --> 00:09:47.600
your your outage management system, your, um, a D M S system,

149
00:09:48.460 --> 00:09:52.880
um, you know, it could be scada, rarely is it scada, but it could be scada.

150
00:09:53.150 --> 00:09:57.840
It's, it's anything that is consuming the network. Um, it could be, uh,

151
00:09:57.860 --> 00:10:00.800
an engineering analysis package sign, for example,

152
00:10:00.940 --> 00:10:05.440
on the electric side and synergy on the gas side. These, uh,

153
00:10:05.660 --> 00:10:10.480
geo dependent systems need network information from

154
00:10:10.900 --> 00:10:14.960
gis, right? So they need that to, to do what they do, right?

155
00:10:15.260 --> 00:10:19.760
So that's the geo dependent systems. The other ones are the geo enabled systems,

156
00:10:19.770 --> 00:10:23.880
right? So these are not so much network intensive,

157
00:10:24.460 --> 00:10:28.200
but they're other, um, and again, I listened high level, uh,

158
00:10:28.880 --> 00:10:32.000
scenarios like, uh, engineering design or staking as an example,

159
00:10:32.730 --> 00:10:37.240
asset management, um, you know, your inspections or your compliance,

160
00:10:37.620 --> 00:10:41.260
uh, stuff like that. Things as you go in the field and you collect. Um,

161
00:10:42.080 --> 00:10:44.340
and then there's also the, um, uh,

162
00:10:44.360 --> 00:10:47.940
gas outage management I put down here because it's, it's, um,

163
00:10:48.050 --> 00:10:50.940
it's not entirely geo, uh,

164
00:10:51.260 --> 00:10:55.700
dependent or network dependent. There's a portion of it that is right.

165
00:10:55.720 --> 00:11:00.340
The valve isolation, the analysis of getting the customers, and, uh,

166
00:11:00.520 --> 00:11:04.620
you know, that feeds into your, the real big portion of,

167
00:11:04.760 --> 00:11:08.860
of gas outage management, which is, you know, the, uh, the, the gas, uh,

168
00:11:08.860 --> 00:11:12.700
relight, uh, shut down and relay orders, right? So getting your customers, uh,

169
00:11:12.960 --> 00:11:17.100
turned back on and are turned off and turned back on safely. Uh,

170
00:11:17.100 --> 00:11:19.940
and there's things like reporting, right? So things that, um,

171
00:11:20.000 --> 00:11:24.220
aren't necessarily network related, but where your assets are,

172
00:11:24.510 --> 00:11:27.940
these all have impacts, right? There's all impacted on the workflows,

173
00:11:28.400 --> 00:11:31.300
but in addition to the workflows,

174
00:11:32.340 --> 00:11:35.820
business is impacted, right? So, you know,

175
00:11:35.890 --> 00:11:40.500
I've listed out a bunch of high level things here, but ultimately, bad data is,

176
00:11:40.880 --> 00:11:45.740
um, is impacting the way you do business, whether it's the, um, reliability,

177
00:11:46.200 --> 00:11:50.660
uh, matrixes on the electric side. Uh, it could be safety,

178
00:11:51.080 --> 00:11:53.800
it could be, uh, longer, right?

179
00:11:54.210 --> 00:11:58.400
Folks are out either gas or electric for a longer period of time

180
00:11:58.910 --> 00:12:02.360
because your network isn't where it needs to be, right? Uh,

181
00:12:03.180 --> 00:12:06.720
and or your processes aren't where they need to be. Um,

182
00:12:07.390 --> 00:12:11.240
that has an impact. It could be more frequent outages, right?

183
00:12:11.580 --> 00:12:14.440
So reliability is not very good. Um,

184
00:12:15.060 --> 00:12:17.640
and the reason I put that in there is because your gis,

185
00:12:17.640 --> 00:12:22.640
your geo enabled systems, right? They can, uh, help harden the grid,

186
00:12:22.890 --> 00:12:27.520
right? They can help make the gas system safer by identifying, uh,

187
00:12:27.520 --> 00:12:32.320
and help on identifying in maybe the integrity portions of,

188
00:12:32.540 --> 00:12:35.720
um, of the workflows and stuff like that, right? So it's asset failure,

189
00:12:35.720 --> 00:12:39.160
there's compliance, right? There's a lot of things that the gis, uh,

190
00:12:39.340 --> 00:12:44.120
can and is helping with in many different organizations across the country.

191
00:12:44.660 --> 00:12:49.480
But again, bad data, it just isn't doing as much as it could be doing.

192
00:12:49.980 --> 00:12:54.400
You need it to do more, more importantly, you need it to be trusted.

193
00:12:54.860 --> 00:12:59.240
It needs to be trusted. And it, it's, uh, you know,

194
00:12:59.350 --> 00:13:03.680
been shown to me over and over again that when I just come out and ask that

195
00:13:03.960 --> 00:13:07.160
question, right? So some folks will, will get in a room and, um,

196
00:13:07.410 --> 00:13:11.920
we're looking at it with migration to utility network as an example. And, uh,

197
00:13:12.180 --> 00:13:15.000
you know, we start talking about data and, and it's, uh,

198
00:13:15.060 --> 00:13:18.360
the lack of data and the feedback from the different groups within the

199
00:13:18.360 --> 00:13:22.280
organization. And then I just flat out and ask, it says, is your data trusted?

200
00:13:22.820 --> 00:13:27.000
And their answer is, every time so far has been, no,

201
00:13:27.470 --> 00:13:30.980
it's not trusted, uh, not trusted 100%.

202
00:13:30.980 --> 00:13:34.940
There may be some things that they trust, but a majority of it,

203
00:13:35.450 --> 00:13:37.580
it's just not trusted. So if it's not trusted,

204
00:13:37.900 --> 00:13:39.660
nobody's really gonna go outta their way to use it.

205
00:13:39.660 --> 00:13:42.900
They're not going to be elated with a brand new mobile solution,

206
00:13:43.320 --> 00:13:47.900
gis or geo enabled mobile solution that takes the information out into the

207
00:13:47.900 --> 00:13:51.580
field, regardless of how great it is, right? If they can't trust the data,

208
00:13:51.770 --> 00:13:55.060
then they're gonna struggle with the application, uh,

209
00:13:55.080 --> 00:13:59.000
and the application of it in the workflows that support it. Okay?

210
00:13:59.100 --> 00:14:03.740
So where does that bring us at this point? So, at the very beginning, right?

211
00:14:03.980 --> 00:14:07.940
And I really didn't call it out, right? But I like this concept of, you know,

212
00:14:08.080 --> 00:14:12.960
is, uh, is the fault in our gis, right? Not in our stars,

213
00:14:13.020 --> 00:14:17.850
but is it in our gis? Is something wrong with the GIS in general?

214
00:14:19.100 --> 00:14:22.680
And the answer is, in my opinion, not exactly.

215
00:14:24.200 --> 00:14:28.830
There are some things that have prevented you from doing

216
00:14:28.830 --> 00:14:31.990
certain things within your organization, but overall,

217
00:14:32.290 --> 00:14:35.720
the fault is not in the gis,

218
00:14:37.540 --> 00:14:39.950
okay? It's in the data management.

219
00:14:40.260 --> 00:14:44.070
It's in how you are using that system,

220
00:14:44.170 --> 00:14:48.790
how the system is being used, how is that data being managed,

221
00:14:49.610 --> 00:14:52.960
um, who is managing it, right?

222
00:14:53.260 --> 00:14:57.400
So the governance over it. Uh, so it's in the data management.

223
00:14:58.100 --> 00:15:02.360
So what is data management? I think that's a, you know, I, like I said,

224
00:15:02.360 --> 00:15:06.440
I've been, I was gonna try to define these as best as I could. Um,

225
00:15:07.200 --> 00:15:09.220
and, and here we go. Here's my shot at data management.

226
00:15:09.490 --> 00:15:14.300
Data management is the people process and technologies that are used to

227
00:15:14.300 --> 00:15:19.100
record and manage data, uh, into the appropriate system of record.

228
00:15:20.410 --> 00:15:25.140
Okay? That's kind of a, of a mouthful of a sentence, but, um,

229
00:15:25.190 --> 00:15:26.900
we've all heard of people, processes,

230
00:15:26.900 --> 00:15:30.740
and technologies before as it pertains to most things that,

231
00:15:30.740 --> 00:15:34.780
that are going on within utility, that that's what kind of makes up that.

232
00:15:34.800 --> 00:15:39.210
And it's very true, right? It's very true. But system of record,

233
00:15:39.620 --> 00:15:40.810
right? So what is that?

234
00:15:41.510 --> 00:15:45.690
So I kind of threw that kind of hoping to define that as best as I could as

235
00:15:45.690 --> 00:15:48.290
well, and right to, to really,

236
00:15:48.590 --> 00:15:52.850
the system of record is the authoritative data source

237
00:15:54.180 --> 00:15:58.850
for a particular attribute of information, right? So,

238
00:15:58.910 --> 00:16:03.410
for example, uh, a lot of times you hear, uh, that the gis,

239
00:16:03.990 --> 00:16:08.810
uh, the system of record in an organization for location is gis.

240
00:16:08.940 --> 00:16:12.810
Makes sense, right? It's a based on geography. Um,

241
00:16:13.150 --> 00:16:18.130
you go to the best extent that you can to, to locate that, um, as,

242
00:16:18.270 --> 00:16:22.870
as close to as possible as where it is in the field. And,

243
00:16:23.090 --> 00:16:23.990
and that's, so therefore,

244
00:16:23.990 --> 00:16:26.710
if I'm going to look for something location of something,

245
00:16:26.890 --> 00:16:31.520
that's where I would expect to find the most accurate right

246
00:16:31.730 --> 00:16:33.360
piece of information around location.

247
00:16:34.310 --> 00:16:38.810
The other one is the system of record for, um, network configuration,

248
00:16:39.260 --> 00:16:43.610
right? So how your electric and gas networks are configured, right?

249
00:16:43.720 --> 00:16:46.210
Pipe to pipe, pipe to fitting, um,

250
00:16:46.730 --> 00:16:50.570
overhead underground with a riser in the middle. Um, you know,

251
00:16:50.600 --> 00:16:54.970
just what is upstream, uh, what is downstream? Um,

252
00:16:55.000 --> 00:16:59.610
what is isolating, right? So how are things connected,

253
00:17:00.390 --> 00:17:04.620
right? There's not another system within the organization that manages that,

254
00:17:05.280 --> 00:17:07.380
um, better than your GIS can, right?

255
00:17:07.820 --> 00:17:09.740
A lot of you are trying to do it in other places,

256
00:17:10.400 --> 00:17:15.020
but your GIS is the best place for that. So that would be, you know, the, uh,

257
00:17:15.020 --> 00:17:18.740
system of record for location and the system of record for, um,

258
00:17:18.740 --> 00:17:22.850
network configuration. Now, what is what? So what are some other things?

259
00:17:22.850 --> 00:17:27.130
So what is the asset of record or system of record for asset condition?

260
00:17:28.220 --> 00:17:31.790
Well, I mean, that could be your asset management system, right?

261
00:17:31.810 --> 00:17:36.310
If you have an asset management system and you have your assets in the asset

262
00:17:36.750 --> 00:17:40.030
registry, and you're, you're dispatching work, right?

263
00:17:40.080 --> 00:17:44.390
Based on maintenance plans, meaning when does that, um,

264
00:17:44.770 --> 00:17:45.570
you know,

265
00:17:45.570 --> 00:17:50.440
device that widget need to be inspected to keep or keep, you know,

266
00:17:50.440 --> 00:17:51.880
nameplate, um,

267
00:17:52.510 --> 00:17:57.090
for reliability or whatever scheduled an access asset system gets out,

268
00:17:57.090 --> 00:18:00.130
communicates with work management, work management, they go out in the field,

269
00:18:00.520 --> 00:18:05.090
they gather the actual, um, you know, condition of the asset,

270
00:18:05.510 --> 00:18:09.810
and then they bring that back somewhere. Right? Now it can live in the gis.

271
00:18:09.840 --> 00:18:13.250
That doesn't mean the GIS is the system of record for condition,

272
00:18:13.270 --> 00:18:14.103
but it could live there.

273
00:18:14.550 --> 00:18:18.530
And I think that it should live there because I think it's beneficial for folks,

274
00:18:18.990 --> 00:18:20.890
uh, to have that in multiple systems.

275
00:18:20.920 --> 00:18:22.690
It's not a duplication of data as long as you,

276
00:18:22.690 --> 00:18:27.130
well define your system of record that could go back into your, um,

277
00:18:27.180 --> 00:18:31.970
asset management system. Um, so that's, uh, kind of the, the system of record,

278
00:18:33.110 --> 00:18:37.700
uh, kind of definition, the best I could there. So the other thing is, um,

279
00:18:37.700 --> 00:18:41.740
you know, data management and, and really when I look at data management, uh,

280
00:18:41.740 --> 00:18:46.500
to try to find, you know, where is the fault in the data management, you know,

281
00:18:46.580 --> 00:18:49.660
I really follow the asset lifecycle, really, cuz that's where, you know,

282
00:18:49.660 --> 00:18:52.930
something enters into your system, right?

283
00:18:53.030 --> 00:18:55.970
And then it'll eventually exit outta your system.

284
00:18:56.070 --> 00:19:00.730
And then everything in between there is an action against

285
00:19:01.080 --> 00:19:04.770
that asset, right? So it could be, um, you know,

286
00:19:04.940 --> 00:19:08.130
originally it could be purchased and it can be in your inventory system.

287
00:19:08.550 --> 00:19:12.370
And then at some point it gets to, um, you know, a design, uh,

288
00:19:12.370 --> 00:19:17.110
maybe it's via a compatible unit that gets installed into the

289
00:19:17.110 --> 00:19:20.430
field, uh, that gets either energized or gets gased, right?

290
00:19:20.450 --> 00:19:25.310
And then you start in on maintaining that asset moving forward once it's

291
00:19:25.310 --> 00:19:28.390
been commissioned, and then you continue to operate it,

292
00:19:28.490 --> 00:19:32.070
you continue to maintain it, and then at some point at the end of its life,

293
00:19:32.070 --> 00:19:35.590
you're gonna decommission it, right? So that's the, the,

294
00:19:35.690 --> 00:19:37.230
the life cycle of an asset.

295
00:19:37.250 --> 00:19:41.390
So if you wanna track reliable information against your assets,

296
00:19:41.690 --> 00:19:46.030
you need to follow that circle that what I call the asset life cycle around

297
00:19:46.850 --> 00:19:50.990
and interrogate, right? What you're looking at, follow the workflows,

298
00:19:50.990 --> 00:19:54.230
follow the data, right? As I like to say, follow the data.

299
00:19:55.540 --> 00:19:58.880
And that's how you will end up, um, figuring out a lot of stuff.

300
00:19:58.900 --> 00:20:02.120
And we'll get into that actually in a little bit. So,

301
00:20:02.120 --> 00:20:04.040
data management com management component.

302
00:20:04.180 --> 00:20:06.560
So I talked a little bit about this before, it's the people,

303
00:20:06.870 --> 00:20:10.050
it's the process and it's the technology. Now,

304
00:20:10.050 --> 00:20:14.490
you'll learn a little bit later on that it's not just those three in my opinion,

305
00:20:14.710 --> 00:20:16.330
but let's break it down right here.

306
00:20:16.910 --> 00:20:21.530
So the people are the people that are, uh, part of the workflows,

307
00:20:21.530 --> 00:20:24.570
part of the processes, right? They're either in the field, um,

308
00:20:24.570 --> 00:20:27.810
they're in the office, right? They could be field workers, operators,

309
00:20:27.960 --> 00:20:32.590
trouble people, um, field technicians, locators, you name it.

310
00:20:33.290 --> 00:20:37.380
On the other end, the office workers could be a plethora of folks.

311
00:20:37.380 --> 00:20:39.180
They could be planning, they can be engineering,

312
00:20:39.330 --> 00:20:42.620
they could be integrity management. It, it goes on, it's, it's,

313
00:20:42.650 --> 00:20:45.140
it's the people in the office, the people in the field,

314
00:20:45.440 --> 00:20:49.040
and then there's ultimately the people that are the GIS professionals within

315
00:20:49.040 --> 00:20:53.160
your organization that are taking everything that is going on in the field,

316
00:20:53.160 --> 00:20:56.120
that everything is going on in the office and in the other system.

317
00:20:56.340 --> 00:21:00.720
And they're making sure that it's, uh, you know, inside the gis,

318
00:21:00.720 --> 00:21:05.120
they are the proprietors of your GIS system, right? So those are the people,

319
00:21:05.400 --> 00:21:08.800
right? There's a plethora of people around the workflows and the process in the

320
00:21:08.800 --> 00:21:13.600
organization. Then you have the technology, right? So technology is,

321
00:21:13.900 --> 00:21:18.400
is not as simple as you would think it is. It's not just the devices.

322
00:21:18.430 --> 00:21:20.240
It's not just, um,

323
00:21:20.580 --> 00:21:25.480
an iPad or a tablet or a PC or ArcGIS

324
00:21:25.550 --> 00:21:27.320
this or ArcGIS that.

325
00:21:28.170 --> 00:21:31.910
It is how all of the systems in addition to that,

326
00:21:32.170 --> 00:21:36.710
it is on how all of the systems kind of come together to,

327
00:21:37.130 --> 00:21:37.460
uh,

328
00:21:37.460 --> 00:21:42.390
formulate the workflow and ultimately allow the data to flow

329
00:21:42.660 --> 00:21:44.510
from one place to another.

330
00:21:44.840 --> 00:21:49.550
There is not one system in an organization that is the system

331
00:21:49.810 --> 00:21:51.430
of the organization. It's,

332
00:21:51.510 --> 00:21:54.630
I don't believe that it's not asset and work management,

333
00:21:55.180 --> 00:21:59.910
it's not outage management in ADMs, it's not cis, I get the billing part.

334
00:22:00.130 --> 00:22:04.590
But as far as operationally goes, it's not, there's not one system,

335
00:22:05.360 --> 00:22:07.990
right? So it's how all of these systems work together.

336
00:22:08.050 --> 00:22:11.950
How does your customer system communicate with your GIS or your gis with your

337
00:22:12.150 --> 00:22:14.350
customer system? You know, how does your, uh,

338
00:22:14.550 --> 00:22:16.110
engineering design and taking packages,

339
00:22:16.250 --> 00:22:20.910
how do they communicate with GIS and visa versa? And then the asset systems,

340
00:22:21.240 --> 00:22:23.430
right? How do they communicate back and forth,

341
00:22:23.430 --> 00:22:26.950
whether they're compliance or whether they're enterprise, it doesn't matter.

342
00:22:26.950 --> 00:22:30.910
It's how your systems are com communicate. It's the integration,

343
00:22:31.610 --> 00:22:34.800
right? So, you know, back to some of the problems that I see,

344
00:22:34.840 --> 00:22:39.520
I see these systems that, um, aren't in, not in, they're not in sync.

345
00:22:39.550 --> 00:22:43.760
They're not passing the right information back and forth, right? Is it?

346
00:22:44.240 --> 00:22:48.520
I don't know exactly all the reasons behind why it was configured or built the

347
00:22:48.520 --> 00:22:51.680
way it is or not built. I don't know what their considerations were.

348
00:22:51.720 --> 00:22:54.560
I wasn't there. But, but they're not to support, you know,

349
00:22:54.600 --> 00:22:59.120
a true data management environment. They're just not. Okay. So that's the,

350
00:22:59.120 --> 00:23:02.320
the technology. So it's a plethora of, of things in the technology.

351
00:23:02.660 --> 00:23:03.960
And then there's the process. Well,

352
00:23:03.960 --> 00:23:08.360
the process is really kind of what brings the people and the technology

353
00:23:08.880 --> 00:23:13.400
together. They follow a process. Technology is built against a process.

354
00:23:14.070 --> 00:23:18.680
That process needs to be documented because you're gonna find that when you

355
00:23:18.680 --> 00:23:23.160
start to look at your processes and your technology and your people,

356
00:23:23.160 --> 00:23:25.320
you're gonna find problems in all of 'em.

357
00:23:25.660 --> 00:23:29.960
But the process is what needs to be defined in order to define the other two.

358
00:23:31.050 --> 00:23:34.300
They have to, that's your, that's the guideline. That's the book.

359
00:23:34.560 --> 00:23:39.300
That's how things flow. That's what it's okay.

360
00:23:40.940 --> 00:23:45.760
So, um, when you do have good data management,

361
00:23:45.850 --> 00:23:48.640
right? When you have all the, the stars are aligned, if you will,

362
00:23:49.140 --> 00:23:50.040
and you have your people,

363
00:23:50.230 --> 00:23:53.880
your process and your technology all where they need to be,

364
00:23:54.230 --> 00:23:58.160
then your data becomes this complete, accurate, timely,

365
00:23:58.700 --> 00:24:02.720
and organized all in the right place, right back to the system of record,

366
00:24:03.450 --> 00:24:07.480
right? So this isn't a, a data management focus on just gis,

367
00:24:07.480 --> 00:24:11.080
it's data management within an organization. It goes beyond just gis.

368
00:24:12.070 --> 00:24:13.370
GIS is gonna house a lot of tools,

369
00:24:13.370 --> 00:24:16.810
and I definitely have a lot of arguments to say why there should be so much data

370
00:24:16.810 --> 00:24:20.170
in gis, but it's not just about gis, right?

371
00:24:20.170 --> 00:24:23.970
So I'm gonna add one more thing to that piece. People process of technology,

372
00:24:24.310 --> 00:24:27.980
and that's data data's the other components.

373
00:24:28.370 --> 00:24:32.180
It's not necessarily just the output, it's also part of the input.

374
00:24:32.180 --> 00:24:35.380
It's also part of the process. So it needs to be included in there.

375
00:24:37.140 --> 00:24:40.670
Okay? So why is this important? Now

376
00:24:42.330 --> 00:24:45.590
the reality is, is it, it never wasn't important.

377
00:24:46.100 --> 00:24:50.550
It's always been important. Data has always been important,

378
00:24:51.620 --> 00:24:55.080
but there has been some things that have been happening, uh,

379
00:24:55.080 --> 00:24:59.480
over the last decade that are making it more important, right?

380
00:24:59.630 --> 00:25:04.160
More important. Um, and it's really a lot of different things, right?

381
00:25:04.190 --> 00:25:07.480
Even from, uh, the technology itself, right?

382
00:25:07.480 --> 00:25:09.360
And what I mean by the technologies, I mean,

383
00:25:09.530 --> 00:25:12.200
those other technologies that I was talking about before, the,

384
00:25:12.420 --> 00:25:17.200
the sign and the synergy that need network information, it's the ADMs that,

385
00:25:17.200 --> 00:25:20.440
you know, not only needs a great network information,

386
00:25:20.440 --> 00:25:25.280
but it also needs more information on a particular

387
00:25:25.410 --> 00:25:30.020
asset in order to do all of its great analytical things, right?

388
00:25:30.080 --> 00:25:30.570
So it's,

389
00:25:30.570 --> 00:25:35.220
it's the technology's forcing itself onto the data

390
00:25:35.360 --> 00:25:37.860
and onto an organization to increase their data,

391
00:25:38.200 --> 00:25:41.940
to really tighten up their data management. You know, on a timeliness thing,

392
00:25:42.450 --> 00:25:47.120
ADMs can't wait 8, 10, 12, 2 weeks for

393
00:25:47.630 --> 00:25:52.160
that new, you know, SECTIONALIZING asset that was put into the field. It,

394
00:25:52.160 --> 00:25:54.240
it needs it as soon as possible. It needs it right now.

395
00:25:54.300 --> 00:25:57.920
It actually needs it as soon as it's been energized in the field and

396
00:25:57.920 --> 00:25:58.800
commissioned in the field,

397
00:25:59.070 --> 00:26:03.000
because that's what it's gonna use to analyze and do all of this great smart

398
00:26:03.000 --> 00:26:04.640
grid stuff that we think about, right?

399
00:26:04.660 --> 00:26:08.120
The self-healing or the sectionalizing minimizing customer outages.

400
00:26:08.800 --> 00:26:11.660
That's what it needs to do. That it needs all of this good data.

401
00:26:12.320 --> 00:26:16.420
But then there's other things that are also driving, right? It's regulatory, um,

402
00:26:16.530 --> 00:26:19.540
it's internal, external, it's financial, it's reliability.

403
00:26:19.850 --> 00:26:24.740
There's just quite a bit that's driving this need for, um,

404
00:26:25.360 --> 00:26:25.690
you know,

405
00:26:25.690 --> 00:26:30.060
good data or in a good data management process is the solution to that, right?

406
00:26:30.160 --> 00:26:34.450
So really kind of taking a look at it and going from there, okay,

407
00:26:34.800 --> 00:26:37.570
digital twin, it's definition time. So digital twin,

408
00:26:37.960 --> 00:26:40.930
what does this have to do with a digital twin? Well,

409
00:26:41.150 --> 00:26:44.440
it kind of really tailors on to what I was was saying just in the previous

410
00:26:44.520 --> 00:26:49.320
comments, and that is, is these other technologies, and those are workflows and,

411
00:26:49.460 --> 00:26:49.700
and,

412
00:26:49.700 --> 00:26:54.640
and other pressures within an organization are really driving the organization

413
00:26:54.860 --> 00:26:59.680
to, uh, to get a digital twin. So a digital twin is, is really a,

414
00:26:59.880 --> 00:27:03.400
a copy, um, copy of your,

415
00:27:03.680 --> 00:27:08.600
whatever your assets are in the field in a digital system. Uh,

416
00:27:08.750 --> 00:27:13.600
easiest correlation is gis, right? So if I have, um, you know, poles and,

417
00:27:13.620 --> 00:27:18.320
and wires and spans and guys and underground and overhead and vaults and, and,

418
00:27:18.340 --> 00:27:21.920
and I have a lot of good detail work and substations all the way up to

419
00:27:21.920 --> 00:27:26.440
transmission to district, you know, to tr uh, generation, uh, you know,

420
00:27:26.540 --> 00:27:28.200
and the higher, um, you know,

421
00:27:28.200 --> 00:27:31.560
systems on the gas side down to the smaller systems in the isolation,

422
00:27:32.510 --> 00:27:35.310
I want to be able to capture that information, right?

423
00:27:35.310 --> 00:27:39.630
Because there's so much more technology that's coming out in this, you know,

424
00:27:39.630 --> 00:27:42.180
this notion of sensors. Um,

425
00:27:42.240 --> 00:27:45.780
and when you start to get sensors on your systems, then you start to get,

426
00:27:45.800 --> 00:27:49.220
you know, you start to see the realization of some of these, you know,

427
00:27:49.220 --> 00:27:52.180
utility of the future things. And the one that comes to,

428
00:27:52.200 --> 00:27:55.660
to mind the most for me is, is on the electric side, right? The, um,

429
00:27:56.240 --> 00:27:59.780
the smart grid. They're getting more, you know, uh,

430
00:27:59.990 --> 00:28:04.820
SCADA enabled systems or devices out onto the electric network that are

431
00:28:04.820 --> 00:28:09.500
helping, um, you know, really kind of improve reliability and reduce,

432
00:28:09.720 --> 00:28:11.660
um, customer outages and, and durations.

433
00:28:11.660 --> 00:28:15.100
And really the matrices to make people like me, uh, in electric, uh,

434
00:28:15.500 --> 00:28:18.420
customer happy, right? I don't have to worry about my power quality.

435
00:28:18.880 --> 00:28:22.140
And that all happens through enablement of technology, right? From sensors.

436
00:28:22.360 --> 00:28:25.260
So you have to have all of your systems modeled correctly,

437
00:28:25.460 --> 00:28:29.100
creating this digital twin. When you have that digital twin created,

438
00:28:29.410 --> 00:28:32.900
then you can start propagating that information to the other systems that can be

439
00:28:32.900 --> 00:28:36.780
consumed and used and leveraged, like better engineering models. Um,

440
00:28:36.800 --> 00:28:39.700
are you under building or overbuilding too much, right? Or in,

441
00:28:39.720 --> 00:28:41.300
in the operational system side,

442
00:28:41.300 --> 00:28:44.900
whether it's some gas outage management or whether it's electric outage

443
00:28:44.900 --> 00:28:49.450
management, um, quality and safety, all of those things.

444
00:28:49.550 --> 00:28:50.810
So this, this idea of,

445
00:28:50.950 --> 00:28:54.250
of modeling digitally everything that you have in the field,

446
00:28:55.070 --> 00:28:59.010
that's where the, um, the industry is going. Now,

447
00:28:59.010 --> 00:29:02.710
that's a huge hurdle for, um,

448
00:29:03.250 --> 00:29:04.150
for utilities.

449
00:29:04.410 --> 00:29:07.950
Cuz there is a lot of information out there that's not modeled right now.

450
00:29:08.330 --> 00:29:10.470
And if we go back to my conversation is,

451
00:29:10.470 --> 00:29:14.470
is the fault in our gis that was one of the things that, you know,

452
00:29:15.020 --> 00:29:18.950
well that's part of, you know, the, the reasoning why, you know,

453
00:29:18.950 --> 00:29:23.350
digital twins were tough is because you couldn't necessarily model everything

454
00:29:23.490 --> 00:29:27.470
within, uh, it's out in the field like your vaults and your, um,

455
00:29:28.140 --> 00:29:31.910
regulator stations and, and you know, these close quarter things with,

456
00:29:31.910 --> 00:29:34.590
with lots of assets in them, uh,

457
00:29:34.590 --> 00:29:38.910
network configurations that just didn't really work well in gis. You know,

458
00:29:39.380 --> 00:29:43.720
well roll forward 2018 January and Esri comes out with utility

459
00:29:43.810 --> 00:29:48.600
networking. This is the, the new network management system, um,

460
00:29:48.660 --> 00:29:50.120
for all of Esri customers.

461
00:29:50.580 --> 00:29:55.280
And this will get you off of the old legacy system that didn't allow you to,

462
00:29:55.540 --> 00:29:59.480
uh, to really kind of capture in the level of detail. Now, some utilities did,

463
00:29:59.480 --> 00:30:01.720
but it was kind of a workaround and it was kind of,

464
00:30:02.140 --> 00:30:05.360
it wasn't a really good solution, right?

465
00:30:05.590 --> 00:30:08.960
Utility network is opening that up through things like containment and

466
00:30:09.120 --> 00:30:13.960
associations. In addition to that, the, the quality control that is,

467
00:30:14.060 --> 00:30:15.560
um, is behind, you know,

468
00:30:15.560 --> 00:30:19.960
the network configurations and what can connect to what, um, uh,

469
00:30:19.980 --> 00:30:22.880
the ability to extend certain things for you,

470
00:30:23.700 --> 00:30:26.480
lessen the amount of effort on your editors. Um,

471
00:30:26.480 --> 00:30:31.200
better quality data can be more timely cuz it's more of a network everywhere,

472
00:30:31.540 --> 00:30:36.000
uh, versus, you know, just kind of stuck into a desktop application. You know,

473
00:30:36.000 --> 00:30:39.240
we can get it out. It's more mobile, um, easier to get to,

474
00:30:39.240 --> 00:30:41.120
it's easier to use is what it comes down to.

475
00:30:41.700 --> 00:30:46.120
So that's my definition of digital twin and kind of how it can fits into why is

476
00:30:46.120 --> 00:30:49.200
it important today. And then tailing on, you know, the,

477
00:30:49.220 --> 00:30:51.600
the data management portion of the discussion.

478
00:30:53.310 --> 00:30:57.840
So I said it wasn't easy to get here and, um,

479
00:30:57.950 --> 00:31:02.080
data management's not easy, right? There's, there's no easy way to get there.

480
00:31:02.080 --> 00:31:06.680
There's no magic, um, silver bullet, if you will, right?

481
00:31:07.220 --> 00:31:09.920
So I kind of put together some, some thoughts on,

482
00:31:09.920 --> 00:31:13.360
on how you can get there from here, right? So these are the steps here. Uh,

483
00:31:13.360 --> 00:31:17.560
define the scope and the goal. Uh, document the as is, uh,

484
00:31:18.110 --> 00:31:22.080
determine the gaps, what are the gaps in that? Uh, and then look at, uh,

485
00:31:22.100 --> 00:31:24.960
or look at what the two B design would look like,

486
00:31:25.420 --> 00:31:26.960
and then kind of a plan your approach.

487
00:31:27.540 --> 00:31:31.280
Now this is all set on a bedrock foundation of change management, right?

488
00:31:31.280 --> 00:31:35.160
Change management has to be part of this because it's impacting people,

489
00:31:35.270 --> 00:31:36.440
processes, technology.

490
00:31:37.260 --> 00:31:41.000
So that's why there's a bedrock foundation there of change management and

491
00:31:41.000 --> 00:31:42.880
governance. Governance is huge, right?

492
00:31:42.940 --> 00:31:47.840
Who controls what changes in your systems, uh, whether it's data related or,

493
00:31:48.020 --> 00:31:50.040
you know, application related. Okay?

494
00:31:50.040 --> 00:31:54.740
And we're gonna go through each one of these. I do have an approach tip though,

495
00:31:54.740 --> 00:31:56.660
and it kind of gets back to, um,

496
00:31:56.730 --> 00:31:59.620
what I was saying about the asset lifecycle before. And that is,

497
00:31:59.640 --> 00:32:03.820
is when you're going to go into this data management, um, uh,

498
00:32:03.820 --> 00:32:07.700
process and looking at your data management, follow the asset lifecycle,

499
00:32:08.050 --> 00:32:10.300
it's gonna be a significant, um,

500
00:32:11.320 --> 00:32:14.060
way for you to see where, um,

501
00:32:14.060 --> 00:32:17.540
things are going right and where they're going wrong. What you can improve.

502
00:32:17.840 --> 00:32:20.940
Is it process related? People related, technology related,

503
00:32:21.370 --> 00:32:26.010
flat out data related, okay? Okay.

504
00:32:26.190 --> 00:32:30.870
Define the scope and the goal. And so what do I mean by that? Well, not all, um,

505
00:32:30.900 --> 00:32:35.870
data management. Um, tracks are ex enterprise, right?

506
00:32:35.870 --> 00:32:40.120
That everything is, is bad. Everything is broken, right? You have,

507
00:32:40.140 --> 00:32:44.680
you may have more of confined concerns maybe on an, a particular asset,

508
00:32:45.180 --> 00:32:49.440
uh, or maybe it's a particular division within the organization, right?

509
00:32:49.460 --> 00:32:52.840
So that's why you need to define your scope. How big are you looking at this?

510
00:32:54.010 --> 00:32:58.210
Um, what are your drivers, right? Define the stakeholders.

511
00:32:58.620 --> 00:33:00.730
Who's impacted? What are your drivers for doing it?

512
00:33:01.230 --> 00:33:05.290
And then who are the stakeholders that have any kind of, of, uh,

513
00:33:05.290 --> 00:33:08.850
whether they're consuming the information that's gathered, uh,

514
00:33:08.870 --> 00:33:11.250
or whether they're gathering it. It doesn't matter.

515
00:33:11.630 --> 00:33:13.810
You need the full roundabout. Think of asset lifecycle.

516
00:33:14.090 --> 00:33:15.410
Everyone that touches the asset,

517
00:33:15.410 --> 00:33:19.850
that sees the asset's gonna have and provide input to that, right? Um,

518
00:33:20.590 --> 00:33:23.850
do you have clear goals in mind and what you want to reach, right?

519
00:33:23.850 --> 00:33:26.690
You have some drivers, but what are the goals, right? Set those goals.

520
00:33:27.510 --> 00:33:30.090
So you need something measurable that you want to come out on the end with.

521
00:33:30.780 --> 00:33:35.160
You need the executive sponsor, right? And I highly recommend, uh, forming, um,

522
00:33:35.160 --> 00:33:37.960
you know, a governance committee as well to help keep, uh,

523
00:33:37.960 --> 00:33:42.080
to help get everybody actually as into the understanding of,

524
00:33:42.420 --> 00:33:45.520
of all of this, the drivers. Um, and,

525
00:33:45.660 --> 00:33:50.120
and helping drive actually everything you're looking at, um, moving forward,

526
00:33:50.130 --> 00:33:53.760
right? And then, um, again, that change management,

527
00:33:54.100 --> 00:33:59.080
you want that change management to be established from day one or the day

528
00:33:59.080 --> 00:34:03.590
before, document the as is, right?

529
00:34:03.690 --> 00:34:08.470
So I know, I think we've, we've all potentially done a lot of this before, um,

530
00:34:08.470 --> 00:34:11.470
but it's a more robust in, in my opinion, it's,

531
00:34:11.540 --> 00:34:14.190
it's not an easy effort to go into and,

532
00:34:14.330 --> 00:34:18.430
and really kind of tear back all of the layers to find out exactly,

533
00:34:19.290 --> 00:34:24.030
um, how stuff is being done, what is being used to do it, right?

534
00:34:24.130 --> 00:34:28.270
And then who is doing it? Again, you're gonna find problems all over the place.

535
00:34:28.650 --> 00:34:32.870
And, uh, just be aware of that and we'll touch on that in the gap process. Uh,

536
00:34:32.870 --> 00:34:36.190
define all your systems, your tools, and your integrations. We talked about,

537
00:34:36.190 --> 00:34:38.990
you know, what was important and where, where things could break down.

538
00:34:39.410 --> 00:34:42.470
You're obviously, you already docked your stakeholders and you know,

539
00:34:42.470 --> 00:34:47.030
you're gonna want to definitely put these into, um, workflow diagrams, right?

540
00:34:47.030 --> 00:34:50.790
Definitely workflow diagrams and, and they can range from swim lanes,

541
00:34:51.150 --> 00:34:53.830
diagrams to just, you know, flow chart type stuff,

542
00:34:53.860 --> 00:34:57.270
just as long as you're capturing it, right? Understand the dependencies,

543
00:34:57.330 --> 00:35:01.750
what's dependent on what, whether it's workflow data, um,

544
00:35:01.750 --> 00:35:06.190
people handoffs. Um, find all those dependencies in record 'em,

545
00:35:06.570 --> 00:35:11.190
uh, document your pain points, right? Various success document those. Uh,

546
00:35:11.190 --> 00:35:12.790
they will come in handy because they're,

547
00:35:12.790 --> 00:35:15.510
you're documenting not your pain points necessarily,

548
00:35:15.530 --> 00:35:19.430
or not the pain point that we don't have accurate information for this

549
00:35:19.430 --> 00:35:20.390
particular asset.

550
00:35:20.930 --> 00:35:23.310
You are documenting the pain points of everyone that's involved,

551
00:35:24.050 --> 00:35:28.510
and that could help shed some light on defining the solution, right?

552
00:35:28.530 --> 00:35:31.390
If you know what everyone's pain points are, you can go, oh, okay,

553
00:35:31.660 --> 00:35:34.310
that application doesn't do that. Or, you know, hey,

554
00:35:34.310 --> 00:35:38.480
that integration isn't coming over. So now, you know, Mary in,

555
00:35:38.700 --> 00:35:41.800
in accounting is having to run this outside report in blah, blah, blah.

556
00:35:41.940 --> 00:35:46.340
So document all the pain points and then in, in that,

557
00:35:46.400 --> 00:35:50.060
in the nature of wanting to solve a solution as a community change management,

558
00:35:50.060 --> 00:35:53.780
right? Ask for, for, um, you know, the future.

559
00:35:53.850 --> 00:35:57.490
What would somebody like to see something done differently, right?

560
00:35:57.520 --> 00:36:01.410
Take that opportunity when you're sitting down with them to not only, uh,

561
00:36:01.550 --> 00:36:04.410
dig out what it is that you are looking for,

562
00:36:04.790 --> 00:36:07.290
but then also make them part of the solution.

563
00:36:07.600 --> 00:36:11.170
Because we all know that people that are part of the solution, um,

564
00:36:11.310 --> 00:36:16.130
are going to accept the solution a whole lot better than

565
00:36:16.130 --> 00:36:18.930
if they were just handed the solution. Hugely important.

566
00:36:18.950 --> 00:36:23.190
How many projects have we seen like that, right? Determine the gap, right?

567
00:36:23.190 --> 00:36:27.390
This is, um, uh, gap analysis, right? I mean,

568
00:36:27.390 --> 00:36:31.830
that's the easiest way to describe it, but it's really kind of digging into, um,

569
00:36:31.850 --> 00:36:35.230
you know, everything that you found, you know, everything from, uh, you know,

570
00:36:35.230 --> 00:36:38.030
it's a lack of a process so people aren't, uh,

571
00:36:38.030 --> 00:36:41.950
doing the right things or something is sitting on that desk or, you know,

572
00:36:41.950 --> 00:36:46.430
there's model inconsistencies or there's integration, uh, break points. Uh,

573
00:36:46.430 --> 00:36:48.990
something's not configured properly. Um,

574
00:36:48.990 --> 00:36:52.750
they're doing it differently across all, you know, these different divisions.

575
00:36:53.150 --> 00:36:55.630
I mean, it could be everything. This is where that, um, you know,

576
00:36:55.630 --> 00:36:56.950
prior statement comes from. There's,

577
00:36:57.090 --> 00:37:02.030
you're gonna find a lot of things that you weren't aware of that, uh,

578
00:37:02.290 --> 00:37:05.750
you know, that might be contributing to the overall, um,

579
00:37:06.700 --> 00:37:10.440
reason for needing to develop a goal in what are your drivers, right?

580
00:37:10.440 --> 00:37:13.600
Something is there, um, that's preventing the,

581
00:37:13.620 --> 00:37:18.160
the migration of that data flow from front to end. So gap is, is, uh,

582
00:37:18.220 --> 00:37:21.520
is an interesting, all I can say. The advice I would give there is,

583
00:37:21.780 --> 00:37:22.880
is don't stop digging.

584
00:37:23.150 --> 00:37:27.800
Turn over every stone and ask as many questions as you can all the time.

585
00:37:30.320 --> 00:37:31.940
Design the two B, right?

586
00:37:32.040 --> 00:37:36.380
My biggest message on this is have

587
00:37:36.760 --> 00:37:39.460
vision, right? You need to have vision.

588
00:37:39.460 --> 00:37:43.660
Someone in your organization needs to have vision because

589
00:37:44.370 --> 00:37:48.630
you're not just gonna wanna solve the exact problem, it's right in front of you.

590
00:37:49.130 --> 00:37:53.550
You're gonna find many things and you're gonna have to think about, um,

591
00:37:53.570 --> 00:37:58.450
you know, the next five to 10 years down the road. Now, that's a lot.

592
00:37:58.870 --> 00:38:02.210
That's a lot to ask, right? If, especially if you're thinking about technology,

593
00:38:02.210 --> 00:38:05.330
right? Everyone, or a lot of people say that, you know,

594
00:38:05.570 --> 00:38:09.890
a five year technology plan is a rough, that's hard to do, and they're right.

595
00:38:09.890 --> 00:38:13.090
It is hard to do, um, because things change so much.

596
00:38:13.350 --> 00:38:17.450
But you have to have that vision. Don't try to, uh, have the,

597
00:38:17.450 --> 00:38:19.570
if it's a technology solution, right?

598
00:38:20.100 --> 00:38:24.330
Don't use the same process or look at it in the same way,

599
00:38:25.150 --> 00:38:28.810
um, that you're doing business today when you're gonna have this new technology

600
00:38:28.850 --> 00:38:32.370
capabilities, right? Because new technology, uh,

601
00:38:32.370 --> 00:38:36.800
could open up a huge door for a better way of doing something.

602
00:38:37.260 --> 00:38:40.320
And, and wouldn't we all want that a better way of doing something?

603
00:38:40.320 --> 00:38:43.280
Maybe your stakeholders would want a better way of doing something.

604
00:38:43.300 --> 00:38:47.040
And I think they do, and I think you do as well. So have a vision.

605
00:38:47.810 --> 00:38:51.720
Don't stop, don't be complacent on this. It's, it's valuable.

606
00:38:52.180 --> 00:38:56.810
Hugely important that you have that vision, right? And, and,

607
00:38:56.910 --> 00:39:00.530
and that's the other thing I would say is, um, you know,

608
00:39:00.670 --> 00:39:04.940
design the solution to the workflow, right?

609
00:39:05.560 --> 00:39:10.380
The technology to the workflow. Don't design the workflow to the technology.

610
00:39:10.640 --> 00:39:14.260
Now, you're gonna have to make concessions here and there,

611
00:39:15.180 --> 00:39:19.560
but I think it's a big mistake if somebody just changes the entire workflow,

612
00:39:20.010 --> 00:39:23.520
right? Uh, just because the technology can't do something right,

613
00:39:23.700 --> 00:39:25.000
or they're gonna have to force it.

614
00:39:25.070 --> 00:39:28.640
There's 10 more steps to achieve it using the technology, you know,

615
00:39:28.660 --> 00:39:31.360
change management wise, or you're thinking it from that direction,

616
00:39:31.910 --> 00:39:34.560
keeping that vision in place in front of you.

617
00:39:34.700 --> 00:39:38.520
You're listening to the pain points that are coming from everyone. Um,

618
00:39:38.580 --> 00:39:40.240
you want people to accept the decision,

619
00:39:40.340 --> 00:39:44.080
cuz ultimately you want to meet your goal, right? Of data management,

620
00:39:44.200 --> 00:39:47.560
a better data, a better reliability, a safer work environment,

621
00:39:47.990 --> 00:39:52.920
then you can't overcomplicate things, right? So in addition to,

622
00:39:52.920 --> 00:39:57.760
right, it might sound a conflicting message there, have vision, but, you know,

623
00:39:58.600 --> 00:40:01.560
designed to the workflow, the technology of the workflow, not the other way.

624
00:40:02.030 --> 00:40:05.080
It's not, it's not conflicting at all. It's a balance. I said it wasn't easy.

625
00:40:05.540 --> 00:40:08.920
And, and you just have to keep this in mind. You have to, it's not, uh,

626
00:40:09.140 --> 00:40:11.240
you get in and you flip this over and you go, oh,

627
00:40:11.240 --> 00:40:13.480
there's the solution right there. It's not that easy all the time.

628
00:40:13.700 --> 00:40:14.680
Not that easy at all.

629
00:40:16.740 --> 00:40:21.700
So plan the approach, right? So this is, is hugely important.

630
00:40:21.700 --> 00:40:26.060
So you have a lot of data you built up, uh, you've gathered and garnered, um,

631
00:40:26.160 --> 00:40:30.820
as is two bs some gaps. Um, you've applied some vision,

632
00:40:31.440 --> 00:40:34.140
um, you've found a lot of technology problems. Uh,

633
00:40:34.140 --> 00:40:37.140
you've found a lot of process problems. You found a lot of people, problems,

634
00:40:37.140 --> 00:40:39.460
potentially whatever you find now,

635
00:40:39.460 --> 00:40:43.580
you have to sit down and figure out how you're going to move forward, right?

636
00:40:43.680 --> 00:40:46.620
You may have to put a business case together, you may have to, uh,

637
00:40:46.780 --> 00:40:51.180
get in front of a board and, and, um, and justify something. Um,

638
00:40:51.400 --> 00:40:55.580
my biggest advice here is, is don't eat the elephant all in one bite.

639
00:40:56.640 --> 00:40:59.680
Consider a phased approach. You don't have to solve everything,

640
00:41:00.170 --> 00:41:02.800
solve a portion at a time, right?

641
00:41:03.520 --> 00:41:06.920
I was taught back at the utility, um, that you,

642
00:41:06.980 --> 00:41:09.760
you plan the work and you work the plan, right?

643
00:41:09.820 --> 00:41:13.840
So that means you have to have a plan. So plan the workout, right?

644
00:41:13.840 --> 00:41:18.480
This is everything from what's gonna have to be done, uh, to maybe negotiating,

645
00:41:19.060 --> 00:41:22.880
um, certain, uh, things with different organizations, or maybe it's, you know,

646
00:41:22.980 --> 00:41:26.920
uh, having, uh, more working sessions, right? So you,

647
00:41:26.940 --> 00:41:29.240
you have a lot of documentation, a lot of information,

648
00:41:29.660 --> 00:41:33.540
but maybe when you start designing, right? Um, you,

649
00:41:33.640 --> 00:41:36.660
you want to go through requirements more. You wanna bring those groups back in,

650
00:41:36.660 --> 00:41:36.860
right?

651
00:41:36.860 --> 00:41:40.620
So you just need to plan accordingly about how you're gonna do all of that,

652
00:41:40.790 --> 00:41:45.760
right? Plan to work and work the plan. Change management,

653
00:41:46.540 --> 00:41:51.200
um, again, should be always, and by this point, uh, deafening for me,

654
00:41:51.750 --> 00:41:56.660
make sure you have change management involved. Okay? Now, in closing,

655
00:41:56.980 --> 00:42:01.300
I, I know there was a lot of information, um, really kinda laid out here,

656
00:42:01.450 --> 00:42:05.820
several definitions. Um, what is data management? Um, you know,

657
00:42:05.970 --> 00:42:10.940
what is, um, the, the digital twin? Um, and then, you know,

658
00:42:11.280 --> 00:42:15.620
why they were important. Uh, in addition to, um, you know, the,

659
00:42:15.680 --> 00:42:19.860
the process to get from, uh, to potentially turn your data management around,

660
00:42:19.860 --> 00:42:24.140
right? If you have data management issues, um, whether they're big or small, um,

661
00:42:24.320 --> 00:42:26.780
you know, how you're going to, uh,

662
00:42:26.780 --> 00:42:29.500
really kind of get to them or get them accomplished, right?

663
00:42:29.680 --> 00:42:33.660
So I guess just starting from, from somewhere, you know,

664
00:42:33.730 --> 00:42:38.020
organizations are data driven organizations, right? That's a reality.

665
00:42:38.680 --> 00:42:42.380
Um, we need to try to get, uh, better data quality, um,

666
00:42:42.380 --> 00:42:44.900
more timely and more complete data into, uh,

667
00:42:45.130 --> 00:42:48.540
into our systems so that they can be leveraged for, uh,

668
00:42:48.540 --> 00:42:52.700
these other analysis and analytical capabilities. Uh,

669
00:42:52.700 --> 00:42:54.540
good data is a requirement, right?

670
00:42:54.730 --> 00:42:56.940
It's a requirement for these organizations to be,

671
00:42:56.940 --> 00:42:59.580
or your organization to be data driven. Um,

672
00:43:01.060 --> 00:43:04.000
the fault is not in the gis. Um,

673
00:43:04.140 --> 00:43:07.520
the fault of the larger portion of the fault is, is, is in data management.

674
00:43:07.520 --> 00:43:11.480
It's in the workflows, the people processing technologies. Um,

675
00:43:11.580 --> 00:43:14.560
and I'm sure there's some fault in GI somewhere. Uh, and,

676
00:43:14.580 --> 00:43:17.160
and I'm not gonna deny that, but it just needs to be found out.

677
00:43:17.180 --> 00:43:19.640
It needs to be figured out how to resolve that problem.

678
00:43:20.690 --> 00:43:25.520
There is no we easy way into good data. There's just not, um,

679
00:43:25.520 --> 00:43:29.400
like I I've been saying it, it is gonna be a difficult task. Um,

680
00:43:29.540 --> 00:43:33.240
but you just need to have that process down and hopefully follow some of the

681
00:43:33.240 --> 00:43:36.600
things that I said and it works for you or alter 'em a little bit. That worked,

682
00:43:36.660 --> 00:43:40.000
uh, to kind of, to your style and just kind of go with that.

683
00:43:41.960 --> 00:43:46.460
Um, all processes that touch data need to be looked at,

684
00:43:46.790 --> 00:43:50.740
right? Getting back to that whole life cycle, uh, asset life cycle,

685
00:43:51.090 --> 00:43:52.500
following that through, you know,

686
00:43:52.500 --> 00:43:55.660
the planning all the way through decommissioning, really looking at everything,

687
00:43:55.660 --> 00:43:57.820
everything that touches the data.

688
00:43:58.040 --> 00:44:01.620
And the one thing I will say is that the one process that that rarely gets

689
00:44:01.620 --> 00:44:05.920
thought about is, is not the planned, but the unplanned, right?

690
00:44:05.920 --> 00:44:10.360
Whether that's storms or whether that's an event of some kind of failure and,

691
00:44:10.980 --> 00:44:11.280
you know,

692
00:44:11.280 --> 00:44:15.600
assets are touched and they are not recorded anywhere because there's not,

693
00:44:15.830 --> 00:44:20.080
there's not always a good process around capturing, you know,

694
00:44:20.150 --> 00:44:24.360
when somebody knocks that pole down or knocks that pole over, even if it's like,

695
00:44:24.420 --> 00:44:28.200
for, like, right? There's, uh, content that needs to be gathered,

696
00:44:28.200 --> 00:44:31.040
like the year of that poll for inspections, which is, you know,

697
00:44:31.080 --> 00:44:35.560
compliance and sorts. So you're gonna find many gaps,

698
00:44:36.260 --> 00:44:39.560
uh, in all of these, you know, different processes, people, technology,

699
00:44:39.740 --> 00:44:42.160
and document. All right? Get 'em all down.

700
00:44:42.430 --> 00:44:45.320
That'll give you a better chance to figure out what you wanna attack when you're

701
00:44:45.320 --> 00:44:48.160
looking at your planning. You know, what can you do? What can you afford to do,

702
00:44:48.160 --> 00:44:51.400
right? You may have some constraints that, you know, you can't, um,

703
00:44:51.400 --> 00:44:55.360
you're constrained to. You need to use the same technology or, or, um, you know,

704
00:44:55.360 --> 00:44:57.960
you, you, you only have so much budget, right? So per year.

705
00:44:57.980 --> 00:45:02.480
So kind of work towards that. Um, have a vision look,

706
00:45:02.820 --> 00:45:07.440
um, bigger than what you're at. Don't get it caught in a microscope.

707
00:45:07.860 --> 00:45:10.600
Really have a vision. And when you're going into it,

708
00:45:10.820 --> 00:45:14.160
really leverage to see what's out there. The gis uh, for example,

709
00:45:14.160 --> 00:45:18.080
the Esri platform's been so significantly changed over the last decade,

710
00:45:18.260 --> 00:45:22.640
at least that, um, not everybody is looking at the different ways to leverage,

711
00:45:22.820 --> 00:45:25.880
you know, the Esri platform. So really kind of have that vision.

712
00:45:26.690 --> 00:45:29.240
Don't eat the elephant all in one bite. You know,

713
00:45:29.460 --> 00:45:33.440
really kind of pace yourself out. Uh, figure it out. Plan the work, right?

714
00:45:33.510 --> 00:45:36.080
Plan the work and work plan. That's what you want to do there.

715
00:45:36.840 --> 00:45:41.060
And then make sure that you manage change. Um, it's gonna be hugely important.

716
00:45:41.330 --> 00:45:43.500
Keep it, you know, from the very beginning,

717
00:45:43.500 --> 00:45:47.860
even though you're not necessarily managing change until the end, but you are,

718
00:45:47.960 --> 00:45:51.140
cuz there's change that's going throughout. You're talking about change.

719
00:45:51.600 --> 00:45:53.700
And people are gonna want to be part of that change,

720
00:45:53.700 --> 00:45:57.260
and you're gonna want 'em to be part of that change so that they can understand,

721
00:45:57.720 --> 00:46:00.660
you know, and be part of the solution instead of, you know,

722
00:46:00.660 --> 00:46:03.700
just get handed the solution at the end. You'll,

723
00:46:03.900 --> 00:46:08.380
you'll find yourself more successful that way. So that's in closing. Again,

724
00:46:08.580 --> 00:46:12.060
I appreciate your time, uh, today for listening. Um,

725
00:46:12.300 --> 00:46:14.780
I believe we're gonna head into a, a q and a period of,

726
00:46:14.780 --> 00:46:17.180
and see if any questions have come in. Thank you very much.

727
00:46:18.760 --> 00:46:22.350
Thank you, Michael. Uh, as we mentioned, uh,

728
00:46:22.410 --> 00:46:26.870
please use a q and A button on your, uh, toolbar to submit some questions.

729
00:46:26.870 --> 00:46:30.940
We already have some coming in. You mentioned processes. Uh,

730
00:46:30.940 --> 00:46:35.820
should we be fixing our processes before going to the utility

731
00:46:35.820 --> 00:46:36.653
network?

732
00:46:38.290 --> 00:46:40.020
Yeah, good question. Can, can you hear me, Keith?

733
00:46:40.140 --> 00:46:43.540
I just wanna make sure I'm still, still loud, loud and clear. Perfect. Perfect.

734
00:46:44.200 --> 00:46:48.940
Um, I'm afraid there's, there's no 100% clear answer to that.

735
00:46:49.280 --> 00:46:53.780
Uh, it really depends on, on where you are at, uh, in your, uh,

736
00:46:53.800 --> 00:46:58.400
in your endeavor into the utility network, right? So, uh, you know,

737
00:46:58.400 --> 00:46:59.600
correcting your data management,

738
00:46:59.600 --> 00:47:04.120
looking at your processes is always gonna be a great thing. If nothing else,

739
00:47:05.180 --> 00:47:09.880
uh, if you can document the processes as they are,

740
00:47:10.620 --> 00:47:14.090
right? Um, kind of like that first step, defining the, you know,

741
00:47:14.090 --> 00:47:15.450
the current state or the as is,

742
00:47:15.450 --> 00:47:20.210
if you can at least get that far before heading into a utility

743
00:47:20.350 --> 00:47:24.090
net project, you're gonna be that much farther ahead. Uh,

744
00:47:24.370 --> 00:47:29.090
actually encourage that if you can do it. If not, maybe bundle it with, uh,

745
00:47:29.120 --> 00:47:33.840
your utility network, uh, migration. Um, but definitely, uh,

746
00:47:34.000 --> 00:47:35.200
I hope that answers the question.

747
00:47:35.900 --> 00:47:38.760
Gotcha. Okay. Thank you. I think Carrie has our next question.

748
00:47:38.950 --> 00:47:41.240
Yeah. Um, so this one says, Mike,

749
00:47:41.380 --> 00:47:44.960
I'm seeing lines start to blur on gis, scada,

750
00:47:45.080 --> 00:47:49.360
A D M S and associated apps that are bolting all these tools.

751
00:47:49.860 --> 00:47:50.693
In your opinion,

752
00:47:50.970 --> 00:47:55.880
where are we headed with the concept of system of state versus system of

753
00:47:55.880 --> 00:47:58.880
record? And how does this tie to the digital twin?

754
00:48:00.980 --> 00:48:02.520
Wow. Deep, deep question right there.

755
00:48:04.590 --> 00:48:08.200
Touches on a lot of different things. Um, I'm gonna,

756
00:48:08.340 --> 00:48:13.160
I'm gonna divide that up a little bit there. So, uh, I'm gonna go with the, um,

757
00:48:13.540 --> 00:48:16.040
you know, the system of record and the digital twin, right? As,

758
00:48:16.060 --> 00:48:19.120
as I talk through, you know, the different, uh, you know,

759
00:48:19.120 --> 00:48:22.840
the data management as it relates to that system of record is hugely important.

760
00:48:23.200 --> 00:48:26.560
Defining where is the, you know, the attribute, you know,

761
00:48:26.560 --> 00:48:29.560
the system of record for whatever attribute, uh,

762
00:48:29.560 --> 00:48:33.000
or data that you're looking to define, that's hugely important.

763
00:48:33.380 --> 00:48:36.000
That's also related to the digital twin, uh,

764
00:48:36.000 --> 00:48:39.120
as well as data management as to how you're collecting that information,

765
00:48:39.520 --> 00:48:40.800
identifying your systems of record,

766
00:48:41.300 --> 00:48:46.080
and then allowing your data to flow right now the system

767
00:48:46.140 --> 00:48:50.960
of state. Now that's interesting, right? So I see the system of state as, um,

768
00:48:51.180 --> 00:48:55.440
as designed, um, as built and as operated. I,

769
00:48:55.480 --> 00:48:58.840
I think those are the only three that I'm aware of in all of those different

770
00:48:58.840 --> 00:49:02.720
systems, right? There's different systems that, that really kind of own those,

771
00:49:02.720 --> 00:49:06.760
right? The, um, the design system usually owns the, uh, you know,

772
00:49:06.760 --> 00:49:11.280
the design portion of GIS is usually responsible for the as-built portion of it.

773
00:49:11.500 --> 00:49:15.360
And then OMS and ADMs is, is really kind of the, um, you know,

774
00:49:15.380 --> 00:49:20.040
the as operated or the system state there, meaning that you can have, uh,

775
00:49:20.280 --> 00:49:24.920
you know, temporary, uh, switching in the field or, uh, run temporary lines,

776
00:49:25.380 --> 00:49:27.080
uh, all over the place. And as long as you're,

777
00:49:27.100 --> 00:49:29.000
it doesn't change how the system is built,

778
00:49:29.000 --> 00:49:33.560
it's just how it's operated temporarily. It's not a permanent change. Um,

779
00:49:33.820 --> 00:49:35.400
that's a really good question. I,

780
00:49:35.580 --> 00:49:40.440
I'm a firm believer that an organization needs to get their system of

781
00:49:40.440 --> 00:49:43.720
record down, their data management, their processes, who owns what,

782
00:49:44.180 --> 00:49:46.480
how that all flows together with the people, process,

783
00:49:46.480 --> 00:49:50.760
technologies and data that will create your digital twin. And then,

784
00:49:50.980 --> 00:49:55.920
in my opinion, that digital twin helps the other systems of state,

785
00:49:56.290 --> 00:49:58.800
right, accomplish what they're looking to accomplish.

786
00:49:59.180 --> 00:50:03.990
And the utilities themselves really looking at those systems when they need to

787
00:50:03.990 --> 00:50:08.230
look at 'em, whether it's operational engineering planning or, um, you know,

788
00:50:08.230 --> 00:50:11.430
more compliance and asset management like the Asbuilt systems.

789
00:50:12.170 --> 00:50:13.430
Really deep question.

790
00:50:15.890 --> 00:50:19.510
Thanks, Michael. Okay, next question. Back to processes.

791
00:50:19.770 --> 00:50:23.670
How do you recommend cleaning up the data once the processes are fixed?

792
00:50:25.030 --> 00:50:28.880
Yeah, that's, uh, these are are really good questions. Um,

793
00:50:29.400 --> 00:50:32.760
I have seen a, a couple of, um,

794
00:50:33.150 --> 00:50:37.400
kind of avenues taken there, strategies taken there. The one that, that I,

795
00:50:37.720 --> 00:50:39.720
I didn't really ever thought I would see,

796
00:50:40.180 --> 00:50:44.520
but I have seen more and more of is a field inventory to where

797
00:50:45.020 --> 00:50:49.440
an organization using internal resources or using external resources

798
00:50:49.740 --> 00:50:53.680
really kind of walks down the system and, uh, you know, with,

799
00:50:53.680 --> 00:50:56.680
with all the U R D or the underground stuff, right?

800
00:50:56.680 --> 00:51:01.360
There's new processes being developed to, um, and, and technologies to really,

801
00:51:01.900 --> 00:51:06.120
you know, garner that information that I've seen. Those are emerging. Of course,

802
00:51:06.140 --> 00:51:09.320
the overhead is site and technology, usually it's, you know,

803
00:51:09.350 --> 00:51:12.320
some kind of spatial awareness, um,

804
00:51:12.660 --> 00:51:15.960
geo enabled that they're out in the field capturing. Um,

805
00:51:16.630 --> 00:51:19.840
another one that I've recently heard of though is, you know, we've,

806
00:51:19.840 --> 00:51:23.040
we've talked about some desperate or disparate systems, you know,

807
00:51:23.040 --> 00:51:27.760
like Synergy or Sign or, um, OMS and stuff like that. And, um,

808
00:51:28.020 --> 00:51:30.840
you know, I've heard recently that folks are saying, you know, Hey,

809
00:51:30.840 --> 00:51:33.320
we might be able to complete this, uh,

810
00:51:33.390 --> 00:51:37.840
some of our information model right within our GIS by taking some of this

811
00:51:37.840 --> 00:51:39.440
information from these other systems, right?

812
00:51:39.490 --> 00:51:44.240
Think about Utility Network is opening up how much geospatial g s is

813
00:51:44.270 --> 00:51:47.640
able to capture. A lot of times these, uh,

814
00:51:47.640 --> 00:51:51.880
systems like Synergy and SIM are having to kind of, um,

815
00:51:52.400 --> 00:51:57.320
hydrate those models with information that's not normally captured in G I

816
00:51:57.400 --> 00:51:59.520
s. So it's kind of this extra step,

817
00:51:59.720 --> 00:52:03.000
which I think creating your digital twin and,

818
00:52:03.000 --> 00:52:06.480
and having a good data management strategy is going to, uh, you know,

819
00:52:06.660 --> 00:52:11.400
be a business benefit. You're not having to do that down the road. So you have,

820
00:52:11.580 --> 00:52:15.600
you know, several different aspects. Now, that's a, a going backwards scenario,

821
00:52:15.600 --> 00:52:17.120
right? Obviously going forwards,

822
00:52:17.430 --> 00:52:21.080
once you get your processes and stuff all figured out, your,

823
00:52:21.270 --> 00:52:25.160
your data moving forward should be good. Uh, again, not a,

824
00:52:25.750 --> 00:52:28.240
I'll keep leaning on that. It's not an easy thing,

825
00:52:28.260 --> 00:52:30.000
but those are the couple things I can think of.

826
00:52:31.370 --> 00:52:34.900
Okay. Looks like we have a few more questions here, um,

827
00:52:35.280 --> 00:52:38.740
and we'll just keep going until, until the end of the hour. Um,

828
00:52:39.480 --> 00:52:44.020
you said moving to Utility Network is an enabler for data management.

829
00:52:44.520 --> 00:52:45.820
Can you expand on that?

830
00:52:46.520 --> 00:52:49.220
Uh, yeah, absolutely. So, um, you know,

831
00:52:49.220 --> 00:52:52.580
over the last couple of years there's been, you know, more, uh,

832
00:52:52.640 --> 00:52:56.820
or several organizations that are really moving into direction, right?

833
00:52:56.820 --> 00:52:59.740
Their strategy is to move into the direction of Utility Network.

834
00:52:59.880 --> 00:53:03.870
And what this opens up is, um, you know, I've said that, you know,

835
00:53:03.870 --> 00:53:05.830
utility Network is, um,

836
00:53:06.330 --> 00:53:10.950
an unbelievably solid quality system in terms of keeping your data

837
00:53:11.100 --> 00:53:15.590
organized once it's in there. The, the challenge is,

838
00:53:15.590 --> 00:53:16.910
is getting your data in there.

839
00:53:16.970 --> 00:53:19.910
So there's a couple of things going to UN that would help.

840
00:53:20.030 --> 00:53:24.390
A is the actual migration of your existing, uh, system.

841
00:53:24.460 --> 00:53:28.520
That could be an existing ESRI system, it could be on a geometric network,

842
00:53:28.860 --> 00:53:32.120
not using network, it could be on another system, right?

843
00:53:32.180 --> 00:53:35.440
But that act of migrating from that,

844
00:53:35.440 --> 00:53:39.840
those systems to UN is gonna force you to clean up your data. Uh,

845
00:53:39.840 --> 00:53:42.400
in some cases it'll, it'll force you to, um,

846
00:53:42.680 --> 00:53:46.320
actually hydrate with more data that you're usually collecting. Now, again,

847
00:53:46.320 --> 00:53:50.950
using maybe some of those methodologies I just talked about, or, you know,

848
00:53:51.140 --> 00:53:55.070
it's, uh, once it's in the utility network model,

849
00:53:55.580 --> 00:53:59.070
then the data, you know, you can set and configure certain, um,

850
00:53:59.200 --> 00:54:01.350
rules within the system that says, you know, Hey,

851
00:54:01.650 --> 00:54:06.030
my data cannot go backwards in quality,

852
00:54:06.030 --> 00:54:10.270
meaning I'm setting this baseline, this is the data, uh,

853
00:54:10.340 --> 00:54:15.270
attribution that I need for a quality network. And once I set that,

854
00:54:15.750 --> 00:54:20.270
I, I almost close that door on data management problems that are related to

855
00:54:20.270 --> 00:54:23.510
technology. There's still all sorts of process stuff we can work out,

856
00:54:23.730 --> 00:54:26.270
but from a technology perspective, thirdly,

857
00:54:26.270 --> 00:54:30.750
I'll state this UN also forces you, um, just,

858
00:54:30.750 --> 00:54:32.870
it's a large project, right?

859
00:54:32.890 --> 00:54:37.390
So you want to take advantage of that large project to do as much as you can,

860
00:54:37.400 --> 00:54:41.430
which includes some process. Re-engineering is what I kind of look at,

861
00:54:41.430 --> 00:54:45.430
basically what we talked around about of trying to, uh, you know,

862
00:54:45.430 --> 00:54:48.710
go with your data management or increase your data management capabilities.

863
00:54:49.220 --> 00:54:52.630
It's just those large projects often give you the opportunity to do that,

864
00:54:52.930 --> 00:54:55.190
and sometimes they force you to do that. And,

865
00:54:55.190 --> 00:54:59.830
and I think that going to Utility Network, you may have both scenarios in there.

866
00:54:59.850 --> 00:55:02.670
So that's why you win, um, uh, is a,

867
00:55:02.670 --> 00:55:07.670
is a huge opportunity for organizations to really solidify their, um,

868
00:55:07.760 --> 00:55:08.830
their data management.

869
00:55:10.070 --> 00:55:12.960
Awesome. Thanks, Michael. All right, another one coming up here.

870
00:55:13.870 --> 00:55:14.800
Back to Digital Twin.

871
00:55:15.300 --> 00:55:19.840
Not sure how the digital twin fits into this conversation on data management.

872
00:55:20.020 --> 00:55:21.280
Is it a requirement?

873
00:55:22.610 --> 00:55:27.440
Um, the, the short answer is no, it is not a requirement. Um,

874
00:55:27.440 --> 00:55:31.960
digital twin is, is, uh, is, is a goal, right? It's, you know,

875
00:55:32.190 --> 00:55:34.600
most utilities I've talked with are, are, you know,

876
00:55:34.620 --> 00:55:38.720
are these wanna become these data driven organizations? In order to do that,

877
00:55:38.720 --> 00:55:42.280
they need to build out their backend systems with everything that matches what's

878
00:55:42.300 --> 00:55:46.720
in the field. So the digital twin is the goal. Um, it's getting there.

879
00:55:46.870 --> 00:55:50.440
That data management is gonna help you. That's the DxD.

880
00:55:50.440 --> 00:55:55.000
How you achieve your digital twin is by, uh, going through and,

881
00:55:55.300 --> 00:55:55.760
and, uh,

882
00:55:55.760 --> 00:56:00.680
really solidifying your data management processes and tools and the people

883
00:56:00.900 --> 00:56:05.640
and everything surrounding it so that you can actually get and meet that goal

884
00:56:05.740 --> 00:56:07.000
of a digital twin.

885
00:56:09.070 --> 00:56:13.120
Okay. Um, it's one UN model in database housing,

886
00:56:13.950 --> 00:56:16.520
both gas and electric or each has their own.

887
00:56:18.310 --> 00:56:22.890
Um, that is, uh, so that's a like really kind of a utility network, uh,

888
00:56:23.420 --> 00:56:26.080
you know, kind of question, uh, which I'll tackle here.

889
00:56:26.140 --> 00:56:30.640
So you can have them in, in one, uh,

890
00:56:30.920 --> 00:56:35.800
database, right? There's some, um, some things that you'll need to, uh, do.

891
00:56:35.840 --> 00:56:37.320
I think the structure network, uh,

892
00:56:37.320 --> 00:56:40.040
starting to get up my head out above my skis are a little bit technically,

893
00:56:40.300 --> 00:56:43.440
but I think structure network and sharing structure networks might be a

894
00:56:43.440 --> 00:56:45.640
challenge. Uh, what I'm seeing is,

895
00:56:45.660 --> 00:56:50.600
is organizations so far have been making the decision to go separately just

896
00:56:50.600 --> 00:56:53.280
because the businesses are run so separately. Now,

897
00:56:53.380 --> 00:56:57.200
if we're talking electric distribution, electric transmission, gas distribution,

898
00:56:57.300 --> 00:56:58.133
gas transmission,

899
00:56:58.580 --> 00:57:03.360
that's where we're seeing more of a trend in those sharing in the same, uh,

900
00:57:03.640 --> 00:57:06.100
databases. I hope I answered that question.

901
00:57:07.760 --> 00:57:10.520
Excellent. We are, we have a few more questions,

902
00:57:10.520 --> 00:57:15.120
but we're almost out of time here. We've got about a minute plus left. Um,

903
00:57:16.010 --> 00:57:20.680
let's see if we can hit one of these. If you think you be gonna ask fast, uh,

904
00:57:21.080 --> 00:57:23.640
answered fast, we have limited resources to work with,

905
00:57:24.260 --> 00:57:26.410
where do you think we should start?

906
00:57:28.110 --> 00:57:32.650
Um, I'm gonna go back and, and just say, start documenting your processes.

907
00:57:33.430 --> 00:57:35.970
Um, right. I mean, I, I think, you know, if,

908
00:57:35.970 --> 00:57:39.970
if you know what some of the problems are, right? Getting out of the gate,

909
00:57:40.120 --> 00:57:44.170
understanding what your scope is, your breadth, is it, you know, a single,

910
00:57:44.180 --> 00:57:48.050
particular asset set? Is it, you know, your entire data set?

911
00:57:48.590 --> 00:57:52.050
Is it polls or just transformers or regulators or CP test points?

912
00:57:52.390 --> 00:57:54.610
Really kind of, you know, I guess start there.

913
00:57:55.030 --> 00:57:59.770
And then once you can define what it is that you want to, uh,

914
00:57:59.790 --> 00:58:03.730
tackle, then really start documenting your processes. And I think you can,

915
00:58:03.910 --> 00:58:05.770
you can do that without, um,

916
00:58:06.070 --> 00:58:10.490
at least that starting point without a huge amount of effort and a huge project,

917
00:58:11.190 --> 00:58:15.410
uh, more just, you know, at a, at a leisurely pace, um, you know,

918
00:58:15.420 --> 00:58:20.090
along the way as your organization has the time, uh, and resources to do it.

919
00:58:21.350 --> 00:58:24.640
Fantastic. Alrighty, well, we're out of time here,

920
00:58:24.640 --> 00:58:26.640
but just wanna say thanks for joining us, uh,

921
00:58:26.660 --> 00:58:30.320
on this Illuminate Webinar series topic. Uh, please join us in two weeks,

922
00:58:30.670 --> 00:58:33.440
June 18th. Uh, we'll be presenting with C P S Energy.

923
00:58:33.540 --> 00:58:38.000
The title of that one is Dashboards That Matter a business case for intelligent

924
00:58:38.360 --> 00:58:42.320
location-based dashboards. Uh, we'll see you then. Have a great afternoon.