Stations: The Missing Link in the Utility Network | SSP iLLUMINATE 2020

2
00:00:02.120 --> 00:00:04.320
Thanks again for joining and welcome to today's webinar.

3
00:00:04.620 --> 00:00:08.040
My name is Keith Freeman. I'm the director of marketing here at SSP Innovations,

4
00:00:08.540 --> 00:00:12.760
and today's webinar is titled Stations the Missing Link in the Utility Network.

5
00:00:13.800 --> 00:00:18.380
Your speakers today will be David Miller and Aaron Everett.

6
00:00:18.430 --> 00:00:22.820
David Miller is a senior consultant at s p with 20 years of experience in

7
00:00:22.820 --> 00:00:24.500
utility design and field operations,

8
00:00:24.500 --> 00:00:28.780
including transmission and distribution design, distribution system management,

9
00:00:28.780 --> 00:00:32.380
field construction, outage restoration, and enterprise G I S.

10
00:00:34.070 --> 00:00:36.900
Aaron Everett works at S S P as a PRO project lead,

11
00:00:36.900 --> 00:00:39.380
specializing in data production and quality assurance,

12
00:00:39.460 --> 00:00:44.380
focusing mainly on work order processing and providing QA for all her projects.

13
00:00:45.540 --> 00:00:48.760
Our speakers will be answering questions at the end of this presentation,

14
00:00:49.220 --> 00:00:53.160
so please enter your questions along the way in the q and a button on your

15
00:00:53.160 --> 00:00:55.040
webinar toolbar. Finally,

16
00:00:55.240 --> 00:00:58.920
a recorded version of this webinar will be made available at a later date.

17
00:00:59.170 --> 00:01:00.480
David, whenever you're ready.

18
00:01:02.810 --> 00:01:03.643
Thank you, Keith,

19
00:01:04.020 --> 00:01:08.280
and thank you to everyone for taking the time to join us today. Um,

20
00:01:08.540 --> 00:01:13.080
I'm David Miller, and for anyone who's known me for a long time, yes,

21
00:01:13.200 --> 00:01:16.480
I did grow a quarantine beard in mustache. I did think it was possible,

22
00:01:16.740 --> 00:01:21.240
but I figured 10 weeks, 12 weeks was enough time to give it a shot. So

23
00:01:23.150 --> 00:01:24.850
now today's, uh,

24
00:01:25.040 --> 00:01:30.010
session's going to be about what I'm learning to be the missing link in u,

25
00:01:30.010 --> 00:01:31.290
the utility network process.

26
00:01:32.990 --> 00:01:37.330
SSP Innovations has this utility network advanced program where we go in and

27
00:01:37.330 --> 00:01:41.290
help utilities develop a roadmap and strategy on how to transition to the

28
00:01:41.290 --> 00:01:44.770
utility network and all the bits and pieces that might be involved with that.

29
00:01:46.210 --> 00:01:46.880
Invariably,

30
00:01:46.880 --> 00:01:51.200
this concussion comes up about what could be I included in the data model and

31
00:01:51.810 --> 00:01:56.460
talks about stations comes up. So before I get deeper into the subject,

32
00:01:57.190 --> 00:02:01.140
let's just set the stage for everyone. What's a station

33
00:02:02.880 --> 00:02:07.220
for the electric side? This is a substation or a switching station.

34
00:02:07.730 --> 00:02:12.660
It's a place where voltages step up or down for transmission CrossCountry to

35
00:02:12.820 --> 00:02:15.140
stepping down the voltage to serve to individual customers.

36
00:02:15.650 --> 00:02:19.820
It's also a place where you can reroute circuitry for the transmission grid.

37
00:02:20.710 --> 00:02:24.480
This also can serve as a demarcation point between different utilities,

38
00:02:24.620 --> 00:02:27.680
municipalities and customers.

39
00:02:29.750 --> 00:02:34.570
The ancillary on the gas side is gonna be your regulator compression compressor,

40
00:02:35.080 --> 00:02:38.820
town border, and gate stations like electric.

41
00:02:38.820 --> 00:02:42.540
This is a place where pressure is stepped up or down for cross-country

42
00:02:42.540 --> 00:02:46.740
transmission or moving it to a distribution pressure to serve customers.

43
00:02:48.160 --> 00:02:51.330
This also can be a demarcation point between other utilities,

44
00:02:51.710 --> 00:02:56.400
municipalities and customers themselves. Now,

45
00:02:56.400 --> 00:03:00.320
with these stations, they haven't typically been, well, well modeled in gis.

46
00:03:02.220 --> 00:03:06.770
First off, how do you model your stations Now, non interactive calls,

47
00:03:06.770 --> 00:03:11.320
since this is a recorded session, but are they point features?

48
00:03:12.560 --> 00:03:14.100
Do you serve 'em up as polygons?

49
00:03:14.890 --> 00:03:17.360
Maybe you have a combination of both depending on the map needs.

50
00:03:18.590 --> 00:03:20.770
Do you have some assets modeled for a station,

51
00:03:20.830 --> 00:03:22.130
but they're not hooked up to anything?

52
00:03:23.080 --> 00:03:26.950
Maybe you have a full connectivity model in some system or someplace,

53
00:03:28.570 --> 00:03:31.550
or this is all being housed in separate databases for, say,

54
00:03:31.790 --> 00:03:35.390
planning engineers or SCADA energy management systems.

55
00:03:36.650 --> 00:03:38.380
This list did not come about by accident.

56
00:03:39.050 --> 00:03:42.900
This is all stuff I've done at my prior life at an electric utility

57
00:03:43.950 --> 00:03:44.783
there.

58
00:03:45.120 --> 00:03:49.900
One thing we modeled was some assets inside the station and not

59
00:03:49.920 --> 00:03:53.620
any connectivity. We were modeling from the low side of the substation,

60
00:03:53.860 --> 00:03:55.420
transfer down through bus bars,

61
00:03:55.600 --> 00:04:00.140
tie switches and things like that to the top sides of the source are circuit

62
00:04:00.140 --> 00:04:00.973
breakers.

63
00:04:01.200 --> 00:04:04.540
We didn't hook 'em up because that would cause loops with the circuitry,

64
00:04:06.280 --> 00:04:11.020
but our operators needed them in the dispatch center because they were using GIS

65
00:04:11.130 --> 00:04:14.500
very heavily in their day-to-day functions and they needed those devices

66
00:04:14.500 --> 00:04:18.180
represented so they could plan out switching orders properly and plan

67
00:04:18.180 --> 00:04:21.180
maintenance properly. With that,

68
00:04:21.200 --> 00:04:25.420
we also had the separate database for the planning engineers where we took a

69
00:04:25.420 --> 00:04:28.100
copy of what we had created for the operations center,

70
00:04:28.880 --> 00:04:30.580
but we added some additional attributes,

71
00:04:30.580 --> 00:04:34.100
some additional features so that the planning model was more accurately

72
00:04:34.100 --> 00:04:38.100
represented and they could run more deep analysis.

73
00:04:40.460 --> 00:04:44.440
We also have the point feature for the large scale maps where if you zoomed out,

74
00:04:45.040 --> 00:04:48.400
polygons don't scale very well for that and they just kind of disappear into the

75
00:04:48.400 --> 00:04:50.200
map points scale up.

76
00:04:50.300 --> 00:04:55.160
So we had those to represent four large scale maps along

77
00:04:55.160 --> 00:04:57.920
with the thing we used every day, which was the polygon feature.

78
00:04:58.590 --> 00:05:03.400
This essentially was the fence line of a station. We showed it in G I s.

79
00:05:04.140 --> 00:05:08.760
We might have shown the cert breakers inside the fence line if it was readable

80
00:05:08.760 --> 00:05:13.000
card graphically. Otherwise it just represented the location of a station.

81
00:05:15.780 --> 00:05:19.000
So why have we done this to ourselves over the years?

82
00:05:20.240 --> 00:05:24.920
A lot of that has to do with the limitations of the geometric network itself

83
00:05:25.580 --> 00:05:26.413
out of the box.

84
00:05:26.500 --> 00:05:31.280
The geometric network only lets you have one source per circuit or

85
00:05:31.560 --> 00:05:33.760
pressure zone. Along with that,

86
00:05:33.810 --> 00:05:37.760
there was really no out of the box way to tie together the transmission and

87
00:05:38.000 --> 00:05:39.160
distribution tiers together.

88
00:05:41.250 --> 00:05:44.840
Since those two meet at stations and you didn't, we didn't model stations,

89
00:05:45.140 --> 00:05:45.973
you couldn't do that.

90
00:05:46.740 --> 00:05:51.000
The only way to accomplish this was through third party tools or customizations.

91
00:05:51.460 --> 00:05:55.400
So if you could pull off a trace from transmission through the stations into

92
00:05:55.600 --> 00:05:59.520
distribution, you had some sort of coding magic going on inside that fence line.

93
00:06:01.330 --> 00:06:05.840
We've also done this to ourselves to meet this different business needs points

94
00:06:05.900 --> 00:06:08.960
and polygon representations of stations being that,

95
00:06:09.880 --> 00:06:11.720
I don't know if there's really a great way around that,

96
00:06:11.860 --> 00:06:16.800
but the utility network can model a station as a point and a polygon at the

97
00:06:16.800 --> 00:06:20.040
same time. Also,

98
00:06:20.620 --> 00:06:24.040
the business drivers were not really there for modeling station assets.

99
00:06:24.700 --> 00:06:26.160
You knew where your stations were at,

100
00:06:26.420 --> 00:06:28.240
you knew generally what was inside of them,

101
00:06:28.820 --> 00:06:33.400
so why actually draw it up inside of gis? You could just send your, uh,

102
00:06:33.590 --> 00:06:35.920
your field worker out to a site says, Hey,

103
00:06:36.060 --> 00:06:40.680
go operate this valve in this station and they will go be able to do that.

104
00:06:43.980 --> 00:06:47.760
But all this together is leading to this missing link within the utility

105
00:06:47.760 --> 00:06:48.593
network.

106
00:06:49.060 --> 00:06:53.080
If you want to experience the paradigm shift that the utility network is

107
00:06:54.140 --> 00:06:56.120
and get this higher fidelity data model,

108
00:06:57.040 --> 00:07:00.880
tracking more assets at a more granular level with a higher connectivity

109
00:07:01.800 --> 00:07:02.633
standard,

110
00:07:03.050 --> 00:07:07.160
along with modeling your transmission and distribution together within one

111
00:07:07.220 --> 00:07:08.680
system, within one database,

112
00:07:09.460 --> 00:07:14.440
and moving towards that digital twin of what's in the real world represented in

113
00:07:14.440 --> 00:07:17.480
your gis with that digital twin,

114
00:07:17.790 --> 00:07:21.880
it's possible to say trace from a gathering field or a power plant through

115
00:07:21.880 --> 00:07:25.560
transmission, down through distribution and to a customer's meter.

116
00:07:26.500 --> 00:07:29.240
But to get all that you need the station assets.

117
00:07:29.780 --> 00:07:33.840
If you don't have station assets, things like representing,

118
00:07:33.870 --> 00:07:37.600
switching accurately through a station is not gonna be possible.

119
00:07:38.150 --> 00:07:42.600
Same goes for valve operations, stepping up voltages, stepping down,

120
00:07:42.600 --> 00:07:46.640
voltages not gonna be there. Same with pressure up and down.

121
00:07:46.860 --> 00:07:50.080
You can't change the pressure levels without the station assets being

122
00:07:50.080 --> 00:07:54.480
represented. If you don't have those items,

123
00:07:54.950 --> 00:07:59.680
it's harder to accurately model what's going on and also run accurate

124
00:07:59.680 --> 00:08:03.240
simulations on those assets. If you're missing a big chunk in the middle,

125
00:08:03.660 --> 00:08:05.960
how do you get from a higher voltage to a lower voltage?

126
00:08:06.140 --> 00:08:08.640
How do you get from a higher pressure to a lower pressure?

127
00:08:09.940 --> 00:08:14.320
You need those station assets. So how do you fill that gap?

128
00:08:14.500 --> 00:08:18.360
How do you establish this link? Where do you start? Well,

129
00:08:18.360 --> 00:08:20.720
first you need to figure out what are your business needs?

130
00:08:20.750 --> 00:08:24.120
What are your business requirements? Why are you gonna go through this effort?

131
00:08:24.620 --> 00:08:28.360
Are you gonna feed in your asset management and work management systems?

132
00:08:29.140 --> 00:08:32.920
Are you gonna feed planning models? Are you going to assist operations?

133
00:08:33.370 --> 00:08:36.320
Maybe you're gonna use this for regulatory reporting and compliance.

134
00:08:37.820 --> 00:08:40.160
So you need to examine what data systems are you feeding?

135
00:08:40.230 --> 00:08:42.960
What enterprise environments is this data gonna be shared with?

136
00:08:43.340 --> 00:08:48.160
How is it gonna be used and what are the needs from those systems that need to

137
00:08:48.160 --> 00:08:51.080
be included in this data model? Next up,

138
00:08:51.180 --> 00:08:56.160
you need to look at how many stations do you need to represent to pull off

139
00:08:56.160 --> 00:09:00.760
your business requirement. Do you need all of 'em? If you have 10,000 stations,

140
00:09:02.380 --> 00:09:03.640
do you have the time, money,

141
00:09:03.640 --> 00:09:07.680
and effort of people to actually generate 10,000 stations or

142
00:09:08.670 --> 00:09:13.480
does 1000 stations solve 90% of your problems and the rest can be filled in

143
00:09:13.480 --> 00:09:14.180
later?

144
00:09:14.180 --> 00:09:19.160
Or some other method or business process established that covers

145
00:09:19.160 --> 00:09:23.360
that hole Along with how many stations are you modeling,

146
00:09:24.060 --> 00:09:26.640
how many assets within the station are you modeling,

147
00:09:26.820 --> 00:09:29.720
and then how many data outreach are you gonna track per asset?

148
00:09:30.230 --> 00:09:34.120
This question comes down to data fidelity and with data fidelity.

149
00:09:35.390 --> 00:09:39.840
SSPs kind of loosely come up with this definition of low, medium,

150
00:09:39.980 --> 00:09:43.280
and high. Aaron is gonna talk more about this.

151
00:09:43.500 --> 00:09:46.640
I'm just introducing the concept now, but understand this,

152
00:09:47.140 --> 00:09:51.200
we just created these definitions to help a customer

153
00:09:51.870 --> 00:09:55.240
delineate between what's a a possible with this utility network model.

154
00:09:56.300 --> 00:09:57.840
If you said you want medium fidelity,

155
00:09:58.590 --> 00:10:00.680
that doesn't mean you've selected medium fidelity,

156
00:10:01.040 --> 00:10:04.960
fidelity for everything in your utility network. You can mix and match.

157
00:10:05.380 --> 00:10:08.600
You could have a very high fidelity transformer and a very low fidelity cable

158
00:10:08.600 --> 00:10:13.280
hooked up to it. So this is just for illustrative purposes only.

159
00:10:15.460 --> 00:10:18.400
But if you're going to map deeper into the utility network,

160
00:10:19.590 --> 00:10:22.160
what can you do with some of this stuff? Well,

161
00:10:22.740 --> 00:10:25.880
if you're mapping out all your bus bars and all your transmission electric

162
00:10:25.880 --> 00:10:29.760
facilities, you could potentially do limiting factor analysis and saying,

163
00:10:30.590 --> 00:10:35.480
what device is causing my line to be de-rated or limiting the rating on my

164
00:10:35.480 --> 00:10:38.440
transmission line? On the gas side,

165
00:10:38.540 --> 00:10:41.600
you can model your station piping out and figure out,

166
00:10:42.700 --> 00:10:43.720
run your validation says,

167
00:10:43.780 --> 00:10:48.040
are all my station piping up to snuff when it comes to the maximal allowable

168
00:10:48.040 --> 00:10:48.960
operating pressure?

169
00:10:49.980 --> 00:10:54.920
And is it meeting the requirements of of of femsa of D O T and all

170
00:10:54.920 --> 00:10:59.800
that? So once you've looked at these business processes, business needs,

171
00:10:59.800 --> 00:11:01.600
looking at this data fidelity questions,

172
00:11:02.140 --> 00:11:06.240
you need to start looking at where does this data live within your utility? Now,

173
00:11:07.360 --> 00:11:10.410
this could be in CAD files, this could be in the planning models.

174
00:11:11.060 --> 00:11:14.050
Maybe you're pulling it from SCADA and the energy management systems.

175
00:11:15.180 --> 00:11:18.890
Maybe it's still on paper. And with that,

176
00:11:18.920 --> 00:11:23.610
this is only showing you how everything's connected and maybe some attribute

177
00:11:23.680 --> 00:11:25.210
data. Don't forget,

178
00:11:25.310 --> 00:11:28.530
you might need a lot more attribute data that doesn't live in these systems.

179
00:11:29.070 --> 00:11:31.370
You might have to go to an asset management system and says,

180
00:11:32.230 --> 00:11:36.490
we need all the information about the substation transformer or this pump or

181
00:11:36.490 --> 00:11:38.610
valve within a gas regulator station.

182
00:11:42.160 --> 00:11:45.610
Once you have this all figured out and you figured out where you're getting

183
00:11:45.650 --> 00:11:49.610
connectivity, where you're getting your attributes, it's time to consolidate,

184
00:11:49.610 --> 00:11:53.050
convert, and maintain. This could be paper electronic,

185
00:11:53.830 --> 00:11:55.520
this could be CAD to gis.

186
00:11:55.730 --> 00:12:00.640
Maybe it's taking planning and SCADA and EMS models, converting them into gis.

187
00:12:01.290 --> 00:12:04.040
Maybe part of this is geo rectifying your data.

188
00:12:04.900 --> 00:12:08.960
If you take your CAD data and insert it in your GIS and it shows up off the

189
00:12:08.960 --> 00:12:10.640
coast of Africa on no island,

190
00:12:12.230 --> 00:12:17.000
your CAD data has no idea where it fits in the real world and your GIS data has

191
00:12:17.000 --> 00:12:20.360
no, I your GIS system has no idea where the CAD system should fit in.

192
00:12:21.380 --> 00:12:24.640
So geo rectification of data is a big effort as well.

193
00:12:26.250 --> 00:12:27.800
Along with that, as I said,

194
00:12:27.800 --> 00:12:32.120
don't forget those attributes and once you've gone through this effort of

195
00:12:32.400 --> 00:12:33.320
consolidating converting,

196
00:12:33.660 --> 00:12:37.480
you're gonna want to come up with the business processes of how do you maintain

197
00:12:37.480 --> 00:12:40.800
this data. It'd be a shame to take all this time, money,

198
00:12:40.800 --> 00:12:44.200
and effort and then set this on the shelf waiting for two years later when the

199
00:12:44.200 --> 00:12:45.320
utility network might roll around.

200
00:12:47.190 --> 00:12:50.120
Then you're gonna have to revalidate everything. I would say,

201
00:12:50.260 --> 00:12:53.880
if you're gonna build this out, take the time and establish the date,

202
00:12:53.880 --> 00:12:58.200
the lifecycle maintenance processes to ensure it stays fresh and up to date and

203
00:12:58.200 --> 00:13:01.440
even figure out some uses now before the utility network even shows up.

204
00:13:04.020 --> 00:13:07.560
So next up, Aaron's gonna discuss, uh, in deeper details.

205
00:13:07.680 --> 00:13:11.520
Some of the topics I have covered along with things she's seen and learned

206
00:13:11.520 --> 00:13:13.760
through different pilots we've run with companies.

207
00:13:14.540 --> 00:13:18.400
One in particular is we just completed a pilot for a Fortune 200 electric

208
00:13:18.400 --> 00:13:21.640
utility and they're working on transition to the utility network.

209
00:13:23.230 --> 00:13:23.720
With that,

210
00:13:23.720 --> 00:13:27.320
they wanted to explore how much effort would it take to build out all their

211
00:13:27.350 --> 00:13:28.183
substations.

212
00:13:29.640 --> 00:13:33.610
They have a lot and we had to help them figure out, alright,

213
00:13:34.030 --> 00:13:35.650
here's what it takes to build 'em all out.

214
00:13:36.030 --> 00:13:39.930
And Erin was the project lead on that. She experienced a lot of things,

215
00:13:39.930 --> 00:13:43.370
learned a lot of things that she's gonna go over with you now. Erin,

216
00:13:43.560 --> 00:13:44.410
take it away.

217
00:13:45.230 --> 00:13:49.130
Thanks David. So you're thinking of transitioning to the utility network.

218
00:13:49.870 --> 00:13:51.090
Before you start the process,

219
00:13:51.630 --> 00:13:55.290
let me share with you some tips I've learned from my own experience in mapping

220
00:13:55.360 --> 00:14:00.090
substations in the utility network project Pilots and workshops

221
00:14:00.150 --> 00:14:03.960
are good start to forge in the link through these processes.

222
00:14:03.960 --> 00:14:08.320
Transitioning to the utility network will go much smoother than trying to plunge

223
00:14:08.320 --> 00:14:10.600
into the process headfirst without any planning

224
00:14:12.100 --> 00:14:15.500
workshops help define what will be mapped through discussion and collaboration

225
00:14:16.000 --> 00:14:19.800
and help to ensure all features are accounted for. Meanwhile,

226
00:14:20.220 --> 00:14:24.600
pilots are a great way to figure out what can and cannot be done,

227
00:14:24.700 --> 00:14:28.160
as well as figure out the time and effort needed to convert at a much larger

228
00:14:28.250 --> 00:14:29.083
scale.

229
00:14:29.230 --> 00:14:33.920
This often means prototyping potential work processes and analyses to ensure

230
00:14:33.920 --> 00:14:36.480
your data model has everything it needs to be successful.

231
00:14:37.300 --> 00:14:40.730
Early planning can help create a stronger link when converting to utility

232
00:14:40.730 --> 00:14:45.430
network. Once they, one thing that is important to consider,

233
00:14:45.890 --> 00:14:50.430
um, is the fidelity level you want your data to be at. As previously mentioned,

234
00:14:50.540 --> 00:14:53.000
data fidelity can be low, medium,

235
00:14:53.180 --> 00:14:57.320
or high with one being able to mix and match for the needs of the company.

236
00:14:58.490 --> 00:15:02.780
Usually medium fidelity provides enough device detail to establish

237
00:15:02.780 --> 00:15:07.020
directionality of lines and devices and offers containment functionality.

238
00:15:07.780 --> 00:15:12.240
The connectivity between features is established using connectivity associations

239
00:15:12.240 --> 00:15:14.720
represented by the dash lines in the image. Sean.

240
00:15:16.620 --> 00:15:20.910
This image provides a good example of what the medium fidelity mapping looks

241
00:15:20.910 --> 00:15:24.910
like. The visibility of the dash lines can be turned on and off. However,

242
00:15:25.160 --> 00:15:29.910
these lines only show connectivity between features and have no

243
00:15:29.910 --> 00:15:30.743
attribution.

244
00:15:32.880 --> 00:15:36.970
This next image shows an example of high fidelity mapping here.

245
00:15:37.040 --> 00:15:39.050
Instead of connectivity associations,

246
00:15:39.350 --> 00:15:43.960
busbar features are used to show the connections high fidelity is considered the

247
00:15:43.960 --> 00:15:48.170
closest representation of a digital twin will. This additional,

248
00:15:48.460 --> 00:15:52.850
additional detail like adding bus work and other equipment that may not have

249
00:15:52.850 --> 00:15:57.290
been mapped under a medium fidelity model may be beneficial for maintenance and

250
00:15:57.290 --> 00:15:59.330
cons or construction plan in activities.

251
00:16:00.080 --> 00:16:04.330
It's not required to establish a fully operable model within gis.

252
00:16:06.390 --> 00:16:08.840
When deciding what fidelity you want to map at,

253
00:16:09.380 --> 00:16:12.520
do consider what maintenance of the data will look like down the road.

254
00:16:13.390 --> 00:16:17.280
More features and attributes added to a model will mean more upkeep later.

255
00:16:18.350 --> 00:16:22.240
Also taken into consideration that if an existing system already provides good

256
00:16:22.240 --> 00:16:23.920
storage for data and attributes,

257
00:16:24.470 --> 00:16:29.440
instead of copying all that data into digital twin and gis create a link

258
00:16:29.900 --> 00:16:33.600
for that, um, to that data using identifier unique to that device.

259
00:16:34.920 --> 00:16:39.620
The medium and high fidelity terminology is used by the SSP team as a method of

260
00:16:39.620 --> 00:16:43.700
categorizing the levels of detail associated with the work related to placing

261
00:16:43.700 --> 00:16:44.820
substation features.

262
00:16:45.340 --> 00:16:49.330
These are not as re delineations in terms of utility network model.

263
00:16:50.490 --> 00:16:54.530
Esri delineations can be used as a basis in deciding what fidelity is best,

264
00:16:54.790 --> 00:16:55.810
but as stated before,

265
00:16:56.730 --> 00:16:59.450
fidelity can be mixed and matched to fit the conversion needs.

266
00:17:04.300 --> 00:17:08.710
Next up is the mapping process or an example mapping process of

267
00:17:09.140 --> 00:17:11.590
what S S P has done in the past.

268
00:17:12.670 --> 00:17:17.520
So here's an example of the substation creation task list below. First,

269
00:17:17.520 --> 00:17:20.840
we'll do reference any PDF drawings, um, of the substation,

270
00:17:21.730 --> 00:17:25.560
place the substation features and fill out any attribution associated to them,

271
00:17:26.460 --> 00:17:28.640
create subnetwork controllers and connectivity,

272
00:17:29.300 --> 00:17:32.610
and then QA on each substation.

273
00:17:35.080 --> 00:17:36.700
So for the first step, um,

274
00:17:36.930 --> 00:17:40.980
what we do is we locate the substation that will be worked on. Um,

275
00:17:40.980 --> 00:17:44.060
we then identify whatever, one line,

276
00:17:44.070 --> 00:17:48.320
three line or any sort of imagery, um, four,

277
00:17:49.980 --> 00:17:54.480
um, kind of the detailed feature layout of the substation that you may have,

278
00:17:55.380 --> 00:17:58.960
and then we'll import that drawing into gis.

279
00:17:59.220 --> 00:18:03.910
So then we can start georeferencing that drawing to

280
00:18:04.020 --> 00:18:08.750
real world imagery. Um, from there we use the georeference,

281
00:18:09.250 --> 00:18:10.083
um,

282
00:18:10.410 --> 00:18:14.950
button to then start the georeferencing um, process.

283
00:18:16.380 --> 00:18:18.640
So navigate to the location in our pro.

284
00:18:18.780 --> 00:18:23.120
We get that image moved and then you start rotating scaling,

285
00:18:23.140 --> 00:18:25.280
and then moving that, um,

286
00:18:26.030 --> 00:18:30.940
image to fit the substation in the aerial as best as possible.

287
00:18:31.990 --> 00:18:36.860
While some cases it's not really possible to take that drawing and slap it

288
00:18:36.860 --> 00:18:39.650
right onto the aerial with no issues, um,

289
00:18:39.830 --> 00:18:43.880
we do our best to fit it in there, um,

290
00:18:45.020 --> 00:18:49.050
and try to at least match internal components, um,

291
00:18:49.510 --> 00:18:52.570
to where they would be in real life.

292
00:18:55.090 --> 00:18:59.420
The next um, step then is feature creation. Um,

293
00:18:59.420 --> 00:19:01.900
we place the switch breakers, transformers,

294
00:19:01.900 --> 00:19:06.500
which are usual medium fidelity features per the diagram layout.

295
00:19:07.160 --> 00:19:11.290
It is possible to create templates kind of like what you see here,

296
00:19:12.240 --> 00:19:15.740
um, with the line, um, breaker bus combo.

297
00:19:15.880 --> 00:19:19.860
So the circuit breaker combos or they can just each feature be placed

298
00:19:20.030 --> 00:19:21.340
separately, um,

299
00:19:21.340 --> 00:19:26.160
according to what the diagram shows once all features are placed.

300
00:19:26.420 --> 00:19:30.440
Um, we will add attributes of each fee, um, feature, um,

301
00:19:30.610 --> 00:19:32.600
using the available information provided.

302
00:19:34.900 --> 00:19:39.880
The next step then is creating connectivity and subnetwork controllers for

303
00:19:39.880 --> 00:19:43.180
the substation with associations.

304
00:19:43.450 --> 00:19:47.460
This is all within the internal substation, um, process.

305
00:19:47.800 --> 00:19:51.060
You create the associations usually between the switches and breakers,

306
00:19:51.080 --> 00:19:55.230
and then whatever other features are decided upon to add.

307
00:19:57.170 --> 00:19:57.730
For here,

308
00:19:57.730 --> 00:20:02.310
you can kind of see an example of the connections between the bus and the line

309
00:20:02.630 --> 00:20:03.210
terminals,

310
00:20:03.210 --> 00:20:07.910
and what we do is we have the line terminal feeds the bus terminal receives,

311
00:20:08.570 --> 00:20:13.180
and so that way we can then separate out our subnetwork

312
00:20:13.210 --> 00:20:15.300
controllers within the substation.

313
00:20:16.640 --> 00:20:19.750
Subnetwork controllers define an origin of a subnetwork.

314
00:20:20.010 --> 00:20:23.870
The type of subnetwork controller defines how a resource flows through a

315
00:20:23.870 --> 00:20:24.703
network.

316
00:20:25.130 --> 00:20:29.950
So creating those bus and line terminal connections actually helps

317
00:20:30.100 --> 00:20:33.430
with the flow of a subnetwork within, um,

318
00:20:33.430 --> 00:20:38.000
each substation subnetwork controllers are set on a device feature

319
00:20:38.360 --> 00:20:42.360
terminal to represent the origin of a subnetwork using the modified subnet

320
00:20:42.360 --> 00:20:46.920
controller pain. We then set terminals as subnetwork controllers. They're often,

321
00:20:46.920 --> 00:20:50.570
often the breakers, um, within the substation,

322
00:20:50.870 --> 00:20:54.110
but sometimes they end up being switches. Um,

323
00:20:54.180 --> 00:20:57.790
from there we get all the information in, um,

324
00:20:58.170 --> 00:21:01.070
and then create that subnetwork controller.

325
00:21:01.410 --> 00:21:05.590
So then that way we can then trace the subnetwork from one sub

326
00:21:06.210 --> 00:21:10.670
to another to potentially whatever else is connected, um,

327
00:21:11.050 --> 00:21:12.270
to that subnetwork.

328
00:21:15.950 --> 00:21:19.650
And then after all of those connection connections and the subnetwork

329
00:21:19.650 --> 00:21:23.830
controllers are, um, created, we then confirm,

330
00:21:24.530 --> 00:21:28.710
um, all connections have been made correctly through a trace that is performed

331
00:21:28.710 --> 00:21:32.620
within the sub networker, kind of as you see in the image here. Um,

332
00:21:32.630 --> 00:21:35.260
trace it out, make sure everything's connected, um,

333
00:21:35.290 --> 00:21:39.220
both within the substation as well as then going out.

334
00:21:40.440 --> 00:21:42.260
The final step then is qa.

335
00:21:43.160 --> 00:21:46.220
We confirm all connections have been made correctly, um,

336
00:21:46.840 --> 00:21:51.220
and we do that by performing traces within the substation.

337
00:21:51.650 --> 00:21:56.260
Similar is then done to confirm the connectivity between subnetwork controllers

338
00:21:56.280 --> 00:21:59.820
as they are traced out of the subnetwork of the substation.

339
00:22:01.120 --> 00:22:05.420
Future placement and attribution has then checked over and once any errors have

340
00:22:05.420 --> 00:22:08.380
been corrected, the substation mapping is complete.

341
00:22:10.280 --> 00:22:14.460
And that is an example process of our mapping,

342
00:22:15.360 --> 00:22:18.220
um, for substations. Um,

343
00:22:18.240 --> 00:22:21.940
and that is actually the end of my portion and I will hand it back over to David

344
00:22:21.950 --> 00:22:23.540
where he'll finish up the talk.

345
00:22:24.930 --> 00:22:26.190
All right, thank you, Aaron.

346
00:22:26.380 --> 00:22:30.270
That was a great overview of just some of the things that people will be

347
00:22:30.270 --> 00:22:32.670
experiencing as they move through a,

348
00:22:32.870 --> 00:22:36.830
a conversion process of their station data and things that they can start

349
00:22:36.830 --> 00:22:40.010
preparing now. So additionally,

350
00:22:40.550 --> 00:22:43.590
how can SSP innovations help you with this? Well,

351
00:22:44.170 --> 00:22:46.070
we can do help you do that data conversion,

352
00:22:46.140 --> 00:22:48.670
whether it's CAD electronic on paper,

353
00:22:49.650 --> 00:22:53.790
we can help you go through that effort and realize this is not a small effort.

354
00:22:54.520 --> 00:22:58.510
After talking with multiple utilities about station data and figuring out just

355
00:22:58.650 --> 00:23:00.830
how much work it does take to create everything,

356
00:23:02.420 --> 00:23:07.170
maybe you do have enough time and resources internally to tackle this. Great.

357
00:23:08.280 --> 00:23:12.340
I'd say go for it. Do what you can now and get prepared for the utility network.

358
00:23:13.480 --> 00:23:15.500
But if you're like a lot of utilities,

359
00:23:15.600 --> 00:23:17.780
you don't have that much extra time to work with,

360
00:23:18.200 --> 00:23:22.300
you don't have the internal resources needed to support this type of a data

361
00:23:22.300 --> 00:23:23.133
build out.

362
00:23:23.530 --> 00:23:27.710
So that's where SSP can help with our qualified data team to come in and help

363
00:23:27.710 --> 00:23:32.230
build this out. And just like for this Fortune 200 utility,

364
00:23:32.810 --> 00:23:33.643
we helped,

365
00:23:33.810 --> 00:23:37.630
we can also conduct a pilot project and just figure out how much time and effort

366
00:23:37.650 --> 00:23:42.370
it would be for all stations. Such if you have 10,000 stations,

367
00:23:43.950 --> 00:23:46.400
you could start down the path right now and start converting 'em,

368
00:23:46.400 --> 00:23:50.120
but do you know how long it really is gonna take, how much work it's gonna take?

369
00:23:50.630 --> 00:23:55.400
With a pilot, we can take a small subset of data, 50 stations, convert that,

370
00:23:56.180 --> 00:23:57.280
see how much time that took,

371
00:23:57.300 --> 00:24:00.360
and then extrapolate that to everything else and say, all right,

372
00:24:01.120 --> 00:24:03.660
that's gonna be 10,000 stations is gonna take two years.

373
00:24:05.310 --> 00:24:09.200
Knowing this information can help you make better planning decisions and also

374
00:24:09.200 --> 00:24:10.920
reduce your risks and unknowns.

375
00:24:12.070 --> 00:24:14.600
It's really painful to start a conversion project like this.

376
00:24:14.610 --> 00:24:17.600
Think it's gonna cost X amount of dollars and take a year,

377
00:24:18.840 --> 00:24:19.740
get through a year,

378
00:24:19.760 --> 00:24:23.300
figure out you need another year and double the amount of money you budgeted

379
00:24:23.300 --> 00:24:25.780
for. So by going through these pilot efforts,

380
00:24:26.280 --> 00:24:30.500
you can really reduce your risk and have a better understanding of what work's

381
00:24:30.500 --> 00:24:33.900
gonna be involved. This helps you just explain to management better and,

382
00:24:34.040 --> 00:24:35.660
and just prepare everything better.

383
00:24:37.930 --> 00:24:41.030
And you might not be ready for the utility network. Now. You might be two,

384
00:24:41.160 --> 00:24:43.110
three years away, that's fine,

385
00:24:43.890 --> 00:24:46.670
but you could start building out your station data now. In fact,

386
00:24:46.730 --> 00:24:51.530
we almost recommend it a little bit because station takes

387
00:24:51.530 --> 00:24:54.930
time. It might blot your schedule if you start at the same time as the utility

388
00:24:54.930 --> 00:24:59.130
network, but if you start it now, you can just set the stage and say,

389
00:24:59.230 --> 00:25:00.490
we already have the state all set.

390
00:25:00.790 --> 00:25:05.410
We just have to migrate it into the co into the rest of the data to make it work

391
00:25:05.410 --> 00:25:09.990
with the utility network. So in closing,

392
00:25:10.230 --> 00:25:14.630
I have hope we'd explained to you how critical stations are to unlocking the

393
00:25:14.630 --> 00:25:18.570
full benefits of the utility network. Yeah,

394
00:25:18.590 --> 00:25:21.450
you don't have to do station data, you can really cut it down,

395
00:25:21.950 --> 00:25:23.330
but that's really gonna limit you.

396
00:25:23.920 --> 00:25:28.560
It'd be like buying race cars and putting 'em on a

397
00:25:28.560 --> 00:25:33.080
residential street and driving 'em 25 miles an hour when you have seven to 900

398
00:25:33.080 --> 00:25:34.960
horsepower under the hood that you could be using,

399
00:25:35.340 --> 00:25:36.480
but you're idling down the road.

400
00:25:38.430 --> 00:25:42.040
There's so much potential there with utility network and how you can use it for

401
00:25:42.410 --> 00:25:43.560
asset and work management,

402
00:25:44.350 --> 00:25:49.020
asset health analysis system loading analysis, planning systems.

403
00:25:50.000 --> 00:25:54.300
And like I mentioned before with M A O P validations and limiting, uh,

404
00:25:54.300 --> 00:25:59.100
element find or limiting elements in transmission systems that can

405
00:25:59.120 --> 00:26:02.140
tie to regulatory reporting and regulatory compliance.

406
00:26:03.910 --> 00:26:08.170
So all of this, this utility network with station data fully modeled in it,

407
00:26:08.200 --> 00:26:11.490
whether it's a medium fidelity, high fidelity model,

408
00:26:12.430 --> 00:26:16.170
you can gain more productivity from your employees and from your computer

409
00:26:16.170 --> 00:26:20.010
systems. You can connect people to authoritative sources of the data,

410
00:26:20.080 --> 00:26:23.570
give 'em a source of the truth that they can trust.

411
00:26:23.920 --> 00:26:25.690
They have confidence that, hey,

412
00:26:25.690 --> 00:26:27.570
this is the place where everyone keeps up to date,

413
00:26:27.670 --> 00:26:30.690
the station connectivity model and the asset data for it.

414
00:26:30.710 --> 00:26:33.970
So I know I can consume it into my planning model and trust it.

415
00:26:35.290 --> 00:26:36.510
You can also enhance safety.

416
00:26:37.170 --> 00:26:41.850
You send a field worker into a station and they

417
00:26:41.850 --> 00:26:43.420
typically have to pull up, say a, a cad,

418
00:26:43.420 --> 00:26:47.440
one line or an old paper document they're hoping has been kept up to date.

419
00:26:47.820 --> 00:26:50.640
If it hasn't, they might be putting themselves or someone else at risk.

420
00:26:52.240 --> 00:26:56.580
If you have the stations model with all the connectivity and they're consuming

421
00:26:56.580 --> 00:26:58.380
this on a cell phone or a tablet device,

422
00:26:58.380 --> 00:27:01.500
mobilely and using this network anywhere concept from esri,

423
00:27:02.620 --> 00:27:05.990
they can see exactly where the station assets are, how they're connected,

424
00:27:06.050 --> 00:27:09.070
and give them more confidence they're working on the correct piece of equipment.

425
00:27:10.210 --> 00:27:13.230
All this leads to more efficiencies and more flexibility.

426
00:27:13.650 --> 00:27:17.430
So let's say you established five business processes today that you stationed

427
00:27:17.430 --> 00:27:22.190
data, great. I'd be shocked if there's the only five that are ever developed.

428
00:27:22.540 --> 00:27:26.310
Someone a year or two now from now will say, oh, we have this data,

429
00:27:26.890 --> 00:27:28.270
we could do this and this with it,

430
00:27:28.690 --> 00:27:33.590
and you get that much more ROI in the future from an investment you make today.

431
00:27:35.830 --> 00:27:40.330
So with that, that's how we recommend you close this missing link,

432
00:27:40.420 --> 00:27:41.290
close that gap,

433
00:27:41.830 --> 00:27:46.410
and fully evolve from the geometric network into the full potential

434
00:27:46.630 --> 00:27:48.610
of what the utility network will offer you.

435
00:27:51.060 --> 00:27:52.560
Now this is a recorded session,

436
00:27:52.620 --> 00:27:56.790
so if you're watching this sometime in the future and you have questions,

437
00:27:56.810 --> 00:27:58.350
you can always email myself,

438
00:27:58.400 --> 00:28:02.790
david dot miller ssp innovations.com or you can email Erin

439
00:28:03.570 --> 00:28:06.270
and ask her some questions. If we don't have the answers,

440
00:28:06.280 --> 00:28:07.990
we'll put you in contact with someone who does,

441
00:28:08.410 --> 00:28:12.390
or if you'd like to talk further about having the data team involved with some

442
00:28:12.390 --> 00:28:13.270
efforts of your own,

443
00:28:13.850 --> 00:28:16.390
we can put you in account in contact with an account manager.

444
00:28:18.620 --> 00:28:22.430
With that, I wanna say thank you for taking the time today to be with us,

445
00:28:22.680 --> 00:28:27.230
learn some things with us, and, um, we're about to step into some life q and a.

446
00:28:27.330 --> 00:28:28.470
So again, thank you.

447
00:28:31.570 --> 00:28:36.350
All right, thanks David. And Aaron, we do have some questions that have come in.

448
00:28:37.430 --> 00:28:38.960
Okay, the first one.

449
00:28:40.180 --> 00:28:45.160
So what do we do if we don't trust our station data or a

450
00:28:45.160 --> 00:28:45.993
lot of it is missing?

451
00:28:47.430 --> 00:28:48.570
Hey, Keith, I can take this one.

452
00:28:49.440 --> 00:28:54.300
So I'm gonna assume this is hypothetical because data's always perfect in gis.

453
00:28:55.480 --> 00:28:59.460
Um, if that's not the case, the odd, the odd chance that that's not the case.

454
00:29:00.120 --> 00:29:03.580
Um, a as David mentioned earlier, we we wanna look for,

455
00:29:03.920 --> 00:29:07.260
for sources around your enterprise where you can source data where,

456
00:29:07.260 --> 00:29:11.020
where you already have ha have data stored in an existing enterprise system.

457
00:29:11.580 --> 00:29:15.580
A couple that David mentioned are your OMS systems or DMS systems,

458
00:29:15.580 --> 00:29:19.660
these downstream systems that are often consuming gis. Well, what we know is,

459
00:29:19.960 --> 00:29:23.140
is that in the absence of having this substation data, historically,

460
00:29:23.650 --> 00:29:26.580
some of these systems had to create their, that data themselves.

461
00:29:26.880 --> 00:29:30.340
So switching operations in OMS needed to happen anyway. So it's,

462
00:29:30.340 --> 00:29:33.980
it's not uncommon that that folks will have created those elements manually

463
00:29:33.980 --> 00:29:37.060
within your OMS or dms. If that's the case,

464
00:29:37.640 --> 00:29:42.240
we can look to those data sources a, a as a source for migration. Um,

465
00:29:42.240 --> 00:29:46.120
we've even seen some, some folks who have have this data in,

466
00:29:46.140 --> 00:29:50.840
in great detail sitting in a, uh, on a spatial database in a D M S system,

467
00:29:51.460 --> 00:29:54.410
which is fantastic because it simplifies, uh,

468
00:29:54.650 --> 00:29:56.610
simplifies a lot of our work in getting it to gis.

469
00:29:56.610 --> 00:30:01.410
And then perhaps we just change the flow of, of, of data treat. We,

470
00:30:01.470 --> 00:30:02.930
we then have the opportunity to,

471
00:30:03.150 --> 00:30:05.330
to look at GIS as the system of record for that,

472
00:30:05.330 --> 00:30:09.090
for that data that could then be propagated to, to your OMS or DMS system

473
00:30:10.590 --> 00:30:14.690
as far. And that's, that's kind of, um, mostly as it pertains to,

474
00:30:14.790 --> 00:30:19.450
to connected elements. Um, if you're looking at, if, if, if you have a,

475
00:30:19.530 --> 00:30:22.770
a business driver, um, pushing you towards a, a, a really,

476
00:30:22.790 --> 00:30:25.690
really detailed asset maintenance schedule or,

477
00:30:25.710 --> 00:30:30.210
or you're really looking to build out an operational level of detail within your

478
00:30:30.210 --> 00:30:34.370
substation, you may want to look to your asset management systems. If you're,

479
00:30:34.590 --> 00:30:39.510
if you're tracking cts and PTs, power transformers,

480
00:30:40.210 --> 00:30:43.870
um, relays, details like that, if you're tracking them currently within your,

481
00:30:43.870 --> 00:30:46.790
within your enterprise asset management system, uh, we,

482
00:30:46.810 --> 00:30:49.310
we may look to to create a, um,

483
00:30:49.550 --> 00:30:53.990
a a a a a kind of peer feature within GIS to,

484
00:30:53.990 --> 00:30:56.110
to integrate with. And that's to be clear,

485
00:30:56.110 --> 00:30:58.150
that's not to say that in those cases,

486
00:30:58.180 --> 00:31:01.270
it's not to say GIS needs to become the system of record for them,

487
00:31:01.610 --> 00:31:04.150
but let's see that if you've got that data and you have a, you have a,

488
00:31:04.350 --> 00:31:07.550
a maintenance process for keeping that data up to date in your AM system,

489
00:31:07.840 --> 00:31:10.550
let's make use of that. Let's, let's create points, um,

490
00:31:10.550 --> 00:31:12.430
points for those respective features in gis.

491
00:31:12.680 --> 00:31:16.270
Let's synchronize those assets across in some way. And, and you,

492
00:31:16.290 --> 00:31:19.870
you find ways to start to build out your model. Um, but it, but importantly,

493
00:31:20.660 --> 00:31:24.890
if there's a, there are a lot of, there are a lot of elements that,

494
00:31:24.920 --> 00:31:26.970
that the UN is going to want or, or,

495
00:31:26.970 --> 00:31:31.330
or can make use of to really take advantage of, of the functionality.

496
00:31:31.330 --> 00:31:35.570
And station data is, is absolutely one of those, those use cases. So, um,

497
00:31:36.610 --> 00:31:38.770
whenever possible we, we wanna look around for,

498
00:31:38.990 --> 00:31:43.250
for ways to leverage data that exists somewhere, uh, already rather than, uh,

499
00:31:43.250 --> 00:31:44.450
than creating data from scratch.

500
00:31:46.410 --> 00:31:51.240
Thanks for that Isaac. Uh, next question we have,

501
00:31:51.460 --> 00:31:55.880
um, does E S R I utility network offer any ways to visualize

502
00:31:57.300 --> 00:32:02.020
vertical AR arrangements using either and or positive

503
00:32:02.340 --> 00:32:06.280
negative ground level, both substation and regulations?

504
00:32:07.040 --> 00:32:11.880
Compressor slash compressors have many piping that are on top of each other

505
00:32:11.980 --> 00:32:12.960
in plain view,

506
00:32:12.980 --> 00:32:17.520
that's difficult to create a digital twin if not using Z Access

507
00:32:17.520 --> 00:32:21.470
somehow. Hope you got that. Um, Isaac,

508
00:32:21.610 --> 00:32:22.910
do you think you can take that one? Yeah,

509
00:32:23.380 --> 00:32:26.310
Yeah, yeah, that's, this is a great question. So I'm, uh, I'm,

510
00:32:26.330 --> 00:32:28.710
I'm curious if you're, uh, if you're looking,

511
00:32:28.770 --> 00:32:31.950
if you're aware of the specific function, but it's a, it's a, uh,

512
00:32:32.270 --> 00:32:35.590
a great question to ask. Um, so as, as you just described,

513
00:32:35.590 --> 00:32:38.790
there's particularly when we get in these more congested areas,

514
00:32:38.790 --> 00:32:42.680
there's a lot going on. It's not as simple as, um, as,

515
00:32:42.860 --> 00:32:47.800
as just a horizontal axis. Um, so we, we know that in a, in a substation or in,

516
00:32:47.800 --> 00:32:52.720
in a, in a, um, uh, a regulator, we are, we're looking at a number of,

517
00:32:52.820 --> 00:32:56.080
of elements that may be stocked on top of one another and, um,

518
00:32:56.090 --> 00:33:00.920
which historically that that means coincident geometry, which is, is no good.

519
00:33:01.580 --> 00:33:05.840
Um, so utility network and RJs Pro are natively zen enabled.

520
00:33:06.380 --> 00:33:10.200
Um, so if, particularly when you're looking to migrate, um,

521
00:33:10.230 --> 00:33:14.240
data to these more congested areas where you know that truly the difference

522
00:33:14.240 --> 00:33:18.880
between, um, a, a physical element is, is vertical, um,

523
00:33:19.550 --> 00:33:23.280
look to where we can source that, um, that hype from that,

524
00:33:23.280 --> 00:33:27.240
that hype or depth from, uh, and, and the model can absolutely store it. Um,

525
00:33:27.240 --> 00:33:31.310
and, and in fact we are, uh, and some, some migrations we're doing now,

526
00:33:31.710 --> 00:33:34.990
I can think of at least one gas utility where we're migrating from geometric

527
00:33:34.990 --> 00:33:39.470
network to utility network. Uh, and we're they didn't historically track,

528
00:33:40.130 --> 00:33:43.150
um, z value for, for some features that would otherwise be,

529
00:33:43.150 --> 00:33:45.870
otherwise be coincidence. So we are, uh,

530
00:33:46.050 --> 00:33:50.830
we are creating those z differences during the migration. Um, so yes,

531
00:33:50.830 --> 00:33:54.590
very, very good question. Um, and, and totally feasible.

532
00:33:54.590 --> 00:33:57.110
Definitely one of those things to think about as, as part of your migration.

533
00:33:58.250 --> 00:34:01.620
Okay, thanks again. Uh, this one is following up on that previous question.

534
00:34:01.820 --> 00:34:04.660
I think, um, also inside it's from the same person.

535
00:34:05.320 --> 00:34:09.660
So he asked also inside these stations, is there a way to say,

536
00:34:09.840 --> 00:34:11.180
at this exact point,

537
00:34:11.270 --> 00:34:16.180
start the new circuit slash pressure system out of regulatory

538
00:34:16.650 --> 00:34:17.483
transformer,

539
00:34:18.250 --> 00:34:23.180
thus downstream network trace outs could inherit this data as you're building

540
00:34:23.200 --> 00:34:26.500
out the network and or performing QA tracing.

541
00:34:27.340 --> 00:34:28.240
So, so this one,

542
00:34:29.450 --> 00:34:33.000
there are a couple different ways I can think to answer it and I'm, um,

543
00:34:33.310 --> 00:34:37.760
apologies if I, if I, if I don't get exactly your intent. But, so in,

544
00:34:37.760 --> 00:34:42.480
in looking at this question, I see, um, I, I see a couple different, uh,

545
00:34:42.720 --> 00:34:46.400
functions that you could be chasing. So one is, uh, is just a trace operation,

546
00:34:46.660 --> 00:34:50.400
uh, and if that's the case, then, um, so the utility network has,

547
00:34:50.900 --> 00:34:53.240
has tracing inherent within it. Um,

548
00:34:53.410 --> 00:34:57.800
Aaron talked about leveraging that or relying on that tracing, uh,

549
00:34:57.800 --> 00:35:01.280
quite a bit as part of the QA process for migration. And so if,

550
00:35:01.300 --> 00:35:05.120
if you're simply looking for a trace connected features kind of thing or trace

551
00:35:05.120 --> 00:35:09.160
to upstream or downstream, um, barriers, um, that is,

552
00:35:09.300 --> 00:35:13.120
is possible to, to execute from within a station. Um, and then,

553
00:35:13.340 --> 00:35:14.440
and kind of set out in,

554
00:35:14.500 --> 00:35:19.480
in a number of directions if you're talking about the other way that I

555
00:35:19.480 --> 00:35:22.640
could potentially interpret this, so that, that was, if we're looking at just a,

556
00:35:22.760 --> 00:35:25.880
a trace function of features that already have connectivity established.

557
00:35:26.460 --> 00:35:30.130
The other way I think this may be interpreted, interpreted, um,

558
00:35:30.870 --> 00:35:33.930
is if you're looking to say, um,

559
00:35:34.030 --> 00:35:37.640
create these devices and you're looking to, I'm gonna use a specific term,

560
00:35:37.750 --> 00:35:41.680
propagate these values downstream, um, in,

561
00:35:41.980 --> 00:35:46.720
in this case, um, that it, this is, uh, a method used for establishing,

562
00:35:47.340 --> 00:35:51.400
um, connectivity. So something you heard, you heard Aaron mention, um,

563
00:35:51.400 --> 00:35:56.000
David May have mentioned it as well, uh, is a subnetwork controller. So, um,

564
00:35:56.180 --> 00:36:00.240
within the utility network we have this, this concept of a feeder is,

565
00:36:00.500 --> 00:36:04.760
is effectively, uh, a feeder or a zone is effectively a sub network. Um,

566
00:36:05.030 --> 00:36:08.320
each sub network has a subnetwork controller that is basically its,

567
00:36:08.660 --> 00:36:12.640
or maybe liken to, uh, an existing what you would see now as a circuit source.

568
00:36:13.420 --> 00:36:17.200
Um, when you establish a subnetwork, you, you give it a name.

569
00:36:17.200 --> 00:36:20.480
So that would be your, your feeder name and you're able to propagate that,

570
00:36:20.630 --> 00:36:25.600
that name, uh, downstream. Beyond that, there are, uh,

571
00:36:25.600 --> 00:36:29.360
this is where I i we can kind of go a number of different directions in that

572
00:36:30.070 --> 00:36:34.860
there are some values, uh, like phase in an electric system like phasing.

573
00:36:35.200 --> 00:36:39.500
Um, you can propagate phase from that subnetwork controller downstream to all

574
00:36:39.500 --> 00:36:42.340
devices. Uh, and then there, there are some other, if you're,

575
00:36:42.340 --> 00:36:47.260
if you're wanting to propagate voltage or propagate some other kind of network

576
00:36:47.260 --> 00:36:50.780
attribute, there are other methods to go about it. Um, they get,

577
00:36:50.980 --> 00:36:54.660
they get pretty specific depending on which value specifically you're looking

578
00:36:54.680 --> 00:36:59.680
for. So hopefully that gives, um, that gives you some, uh, some general ideas.

579
00:37:00.020 --> 00:37:03.000
Uh, if I did not answer your questions specifically enough, uh,

580
00:37:03.000 --> 00:37:05.720
please feel free to for chime in with, uh, with a follow up.

581
00:37:06.070 --> 00:37:08.890
Thanks Isaac. Alright, next up, what is,

582
00:37:09.080 --> 00:37:13.810
what is the more common use of schema in utility network for transmission

583
00:37:13.810 --> 00:37:17.330
substations? One line schema or three phase schema?

584
00:37:18.390 --> 00:37:22.510
I can answer that, Keith. Um, so for this one,

585
00:37:22.510 --> 00:37:27.190
it's kind of dependent on how much detail you want within the

586
00:37:27.300 --> 00:37:32.190
transmissions. Um, substation one lines, they, um,

587
00:37:32.890 --> 00:37:34.670
are great to kind of show the location,

588
00:37:35.130 --> 00:37:39.830
but oftentimes we find they're not as detailed as say the three, um,

589
00:37:39.830 --> 00:37:43.670
phase ones. And it's just, it's dependent on what you want.

590
00:37:43.730 --> 00:37:48.350
So if you want say more of a medium fidelity, so not just, you know,

591
00:37:48.350 --> 00:37:51.830
placing those switches, transformers, um,

592
00:37:53.290 --> 00:37:57.830
um, circuit breakers out there, um, on the map,

593
00:37:59.090 --> 00:38:03.670
the one line can work fine, but if you're wanting to see more features, more,

594
00:38:03.850 --> 00:38:05.070
um, equipment out there,

595
00:38:05.390 --> 00:38:09.550
I have found that the three line or the three phase shows more.

596
00:38:11.010 --> 00:38:11.370
Um,

597
00:38:11.370 --> 00:38:15.990
but there's also been times where I've actually used both the one line and the

598
00:38:15.990 --> 00:38:19.950
three phase together. Um, cuz sometimes the three phase,

599
00:38:19.970 --> 00:38:24.310
it gives you all of that detail, but it doesn't say certain things like, oh,

600
00:38:24.550 --> 00:38:28.990
this switch is actually closed, or the switch is open. There's, we've,

601
00:38:28.990 --> 00:38:33.030
there's no good like say, yeah, you should be using one line or yeah,

602
00:38:33.030 --> 00:38:37.400
you should be using three. It's whatever works best for the data if you need.

603
00:38:37.400 --> 00:38:40.760
Yeah, if you need phasing information on devices, um,

604
00:38:40.760 --> 00:38:44.490
you'll have to use the three line. But if you're just there,

605
00:38:44.510 --> 00:38:49.370
if you just want the orientation, the placement, um, of those features,

606
00:38:49.550 --> 00:38:52.010
one lines are often good enough, um,

607
00:38:52.430 --> 00:38:57.060
but it's whatever the company feels is, you know,

608
00:38:57.490 --> 00:39:01.660
what they need. Um, yeah, there's no easy way to say, oh,

609
00:39:01.660 --> 00:39:04.580
you should do this or that one. Um, but it's kind of just,

610
00:39:04.690 --> 00:39:09.540
this is something you can work with during the pilot especially to

611
00:39:09.540 --> 00:39:12.060
figure out what's gonna best fit your me, um, needs.

612
00:39:13.360 --> 00:39:16.140
So I think that should kind of answer that.

613
00:39:16.160 --> 00:39:19.680
Thanks. Thanks Aaron. Yep. Um,

614
00:39:19.680 --> 00:39:24.520
within a single geodatabase can one feature class support medium

615
00:39:24.960 --> 00:39:27.720
fidelity and another feature class support high fidelity,

616
00:39:28.910 --> 00:39:33.560
Love this question. Yeah. So, uh, great, great question to ask and, and, uh,

617
00:39:33.560 --> 00:39:36.760
some notes that I wanted to, to share after this, um,

618
00:39:36.760 --> 00:39:40.200
this video you just gave me, the, uh, this recording or webinar, sorry,

619
00:39:40.200 --> 00:39:43.600
you just gave me the, the, the perfect avenue for, so, um, yes.

620
00:39:43.740 --> 00:39:48.720
So when we're talking about, um, levels of, of fidelity, we, our,

621
00:39:48.720 --> 00:39:52.680
our, our webinar so far has, has talked about pretty macro level at,

622
00:39:52.680 --> 00:39:56.800
at the level of our substation is gonna, or our station is going to be low,

623
00:39:56.800 --> 00:40:01.800
medium, or high. But to your, to your question, absolutely, um, this,

624
00:40:01.830 --> 00:40:05.840
this configuration is and can be and should be much more specific.

625
00:40:06.180 --> 00:40:09.920
And so ev even further than future class levels. So, uh,

626
00:40:09.980 --> 00:40:13.680
the way the utility network is, is structured. You have, uh, you,

627
00:40:13.740 --> 00:40:15.640
you have only five feature classes now,

628
00:40:16.260 --> 00:40:18.680
but within or or beneath those feature classes,

629
00:40:18.900 --> 00:40:23.800
you have asset groups and then asset types beneath them. Uh,

630
00:40:23.800 --> 00:40:27.600
and, and you're able to set, uh, that that level of fidelity basically.

631
00:40:27.600 --> 00:40:31.520
So if say we're, we're talking about let's use a, a switch as an example,

632
00:40:32.720 --> 00:40:35.700
you may a, a low fidelity switch or something that is,

633
00:40:36.200 --> 00:40:40.980
is very comparable to your GN is just, it's a point. Um, where,

634
00:40:40.990 --> 00:40:44.300
where the UN gets much more interesting is that kind of medium fidelity range

635
00:40:44.300 --> 00:40:48.540
where you introduce terminals. Terminals are really what give us the,

636
00:40:48.600 --> 00:40:50.540
the ability to to be directional.

637
00:40:50.880 --> 00:40:55.540
So this is what has enabled network behavior. This is what's enabled, um,

638
00:40:55.560 --> 00:40:57.780
at really modeling substations. Uh, and,

639
00:40:57.800 --> 00:41:01.860
and then by way of that modeling transmission. So, um, a,

640
00:41:01.900 --> 00:41:05.820
a really important element in systems outside of GIS that's now part of, of gis.

641
00:41:06.000 --> 00:41:06.440
And so,

642
00:41:06.440 --> 00:41:10.980
so those terminals and that level of detail can be established at the asset type

643
00:41:10.980 --> 00:41:14.220
level. So you can actually get very specific and,

644
00:41:14.240 --> 00:41:19.000
and you may even choose to say, um, like I've, I've got a, I've got a,

645
00:41:19.000 --> 00:41:22.360
a certain, uh, a fitting a gas fitting going forward that we,

646
00:41:22.360 --> 00:41:26.240
we know going forward, we want to capture X number, we wanna capture 10,

647
00:41:26.420 --> 00:41:30.840
10 details on it, we want to have directionality, but we know our historic data,

648
00:41:31.340 --> 00:41:35.480
uh, doesn't quite support that. So how can we mesh the two together? Well,

649
00:41:35.480 --> 00:41:36.760
you can actually have an,

650
00:41:36.780 --> 00:41:40.520
an asset type for basically going forward for the level of data that we want to

651
00:41:40.520 --> 00:41:42.920
require going forward and then create a,

652
00:41:43.000 --> 00:41:47.920
a different asset type with different network rules, um, to, to fit your,

653
00:41:47.920 --> 00:41:52.520
your legacy data. So, um, you can kind of, uh, have, have both. So the,

654
00:41:52.520 --> 00:41:57.160
the rules are, are associated and very specifically with those asset types. So,

655
00:41:57.580 --> 00:42:01.680
um, yes, to answer the question more succinctly, um, or to button up, uh,

656
00:42:01.680 --> 00:42:04.240
you can absolutely be very specific. It's, um,

657
00:42:04.390 --> 00:42:08.340
that level of fidelity is not across the system and there's,

658
00:42:08.340 --> 00:42:11.980
there's nothing to say. You can't increase it over time. In, in, in fact,

659
00:42:12.020 --> 00:42:14.940
I think it's, I think it makes a lot of sense for folks to look for,

660
00:42:15.090 --> 00:42:18.220
look for a manageable place to start something that we,

661
00:42:18.240 --> 00:42:20.500
we can keep up with this data and it meets our, our,

662
00:42:20.520 --> 00:42:21.860
our near term business needs.

663
00:42:22.160 --> 00:42:25.220
And you can always increase that level of detail over time.

664
00:42:26.240 --> 00:42:30.960
Excellent. Thank you, Isaac. All next up. Uh, and once again,

665
00:42:30.960 --> 00:42:33.600
please hit the q and a button on your toolbar to answer your, uh,

666
00:42:33.600 --> 00:42:35.240
answer some questions. Alright.

667
00:42:35.460 --> 00:42:39.280
How long can it typically take to map out a substation?

668
00:42:41.180 --> 00:42:45.480
That's a, um, good question. So typically it, like, it depends on,

669
00:42:46.170 --> 00:42:49.680
first off, the fidelity level, the lower the fidelity,

670
00:42:49.820 --> 00:42:51.320
so anything like medium and stuff,

671
00:42:51.330 --> 00:42:55.400
it'll take a lot less time than if you're mapping to a higher fidelity,

672
00:42:55.450 --> 00:42:59.280
which has a lot more detail, um, and features to place. Um,

673
00:42:59.350 --> 00:43:02.930
smaller substations can take may,

674
00:43:02.930 --> 00:43:07.930
like maybe if a mapper really gets into it, potentially like just an hour,

675
00:43:07.950 --> 00:43:12.410
if not less. Um, but as you kind of put, get more features,

676
00:43:12.480 --> 00:43:17.330
more things to map, it will increase the typical one. Um, I would say,

677
00:43:17.590 --> 00:43:21.770
so something that's not too complicated can take about,

678
00:43:23.670 --> 00:43:28.510
um, say three or four hours, um, once kind of a mapper really gets going.

679
00:43:29.890 --> 00:43:33.110
And oftentimes that can get, um,

680
00:43:34.980 --> 00:43:39.270
that time to map can be decreased, um,

681
00:43:39.300 --> 00:43:43.790
with use of templates. So if we start noticing that, oh,

682
00:43:43.790 --> 00:43:47.430
this switch breaker, um, combo is showing up a lot,

683
00:43:47.930 --> 00:43:52.190
we can make a template and it's just an easy click that once instead of placing

684
00:43:52.190 --> 00:43:55.140
everything, um, individually,

685
00:43:56.000 --> 00:43:57.940
and then some substations,

686
00:43:57.960 --> 00:44:01.940
if they're larger subs can take potentially more than a day

687
00:44:02.800 --> 00:44:06.780
to map, but it's all dependent on how much detail, um,

688
00:44:06.960 --> 00:44:10.620
and attributes that need to get filled out, um, within that substation.

689
00:44:11.490 --> 00:44:13.470
So I think that should answer that.

690
00:44:14.370 --> 00:44:17.230
That's perfect. Thank you. Um,

691
00:44:17.690 --> 00:44:22.590
say I want to do a M A O P or limine factor analysis through

692
00:44:22.590 --> 00:44:26.620
the station. How much do data do I really need to model?

693
00:44:27.520 --> 00:44:28.460
Who wants to take that one?

694
00:44:29.100 --> 00:44:33.200
I I can, I can take a swing at this. So this one is, um,

695
00:44:34.100 --> 00:44:37.280
the, the answer to this, the, the how much data do I really need?

696
00:44:37.460 --> 00:44:41.720
Answer is probably a lot. So, um, for,

697
00:44:42.540 --> 00:44:47.120
for those unfamiliar, um, there is, there, there there's a,

698
00:44:47.720 --> 00:44:52.440
a behavior or a function to, to basically say, where in my entire system is,

699
00:44:52.580 --> 00:44:56.640
is is the weakest link, let's say not the missing link. Um, and,

700
00:44:56.640 --> 00:45:00.960
and so these are typically in, in my experience, at least on the electric side,

701
00:45:01.420 --> 00:45:05.880
um, this is typically a, a process that's managed entirely outside of gis. Um,

702
00:45:05.900 --> 00:45:06.960
but it, it might be,

703
00:45:07.140 --> 00:45:12.000
it might be dependent on an export of GIS features that are then dumped into an

704
00:45:12.000 --> 00:45:16.040
Excel spreadsheet and we add amperage to every device or something like that.

705
00:45:16.260 --> 00:45:18.420
So if you have this process going on,

706
00:45:18.420 --> 00:45:21.060
it probably exists somewhere within your utility. Um,

707
00:45:21.970 --> 00:45:26.900
there's a potential to to include the amperage if you're talking,

708
00:45:27.600 --> 00:45:31.900
um, uh, if you're talking electric or, uh, or, or, or pressure rating.

709
00:45:31.960 --> 00:45:35.780
If you're talking gas, um, apply that as an attribute to,

710
00:45:36.000 --> 00:45:38.820
to basically every element that you're modeling within your gis.

711
00:45:39.080 --> 00:45:42.700
If we're talking about mapping that specific one within a station, then you're,

712
00:45:42.700 --> 00:45:46.940
you're looking at you, you'd need, this would be a, a good, uh,

713
00:45:47.260 --> 00:45:51.250
a good business driver for figuring out what level of detail to put in your

714
00:45:51.250 --> 00:45:54.210
system. Um, but you'd be needing to,

715
00:45:54.310 --> 00:45:59.090
to basically model then whichever level of detail you are historically seeing as

716
00:45:59.130 --> 00:46:02.450
a limiting factor. So, uh, perhaps not bus work. We don't,

717
00:46:02.710 --> 00:46:04.850
we wouldn't normally see a bus as a limiting factor,

718
00:46:04.870 --> 00:46:08.090
but you might have a jumper within a substation that is, is your limiter.

719
00:46:08.090 --> 00:46:10.330
It's only related to two to 600 amp, let's say,

720
00:46:10.330 --> 00:46:13.250
instead of 900 amps has the rest of the system. Um,

721
00:46:13.260 --> 00:46:15.090
you'd want to be sure that anything that you've,

722
00:46:15.090 --> 00:46:18.490
you've really historically seen being a limiting element, you,

723
00:46:18.540 --> 00:46:21.850
you'd want to model those within GIS and capture those attributes that you're

724
00:46:21.850 --> 00:46:23.770
looking at in your limiting factor analysis.

725
00:46:24.410 --> 00:46:28.090
I Thanks Isaac. Okay. I think it's a follow up from the previous question. Uh,

726
00:46:28.090 --> 00:46:32.290
perhaps are there any design tools that can assist in creating these station GS

727
00:46:32.290 --> 00:46:36.370
objects as they are in process of being designed and constructed as opposed to

728
00:46:36.370 --> 00:46:37.770
after the fact record keeping?

729
00:46:38.230 --> 00:46:43.090
It seems that drafting design AutoCAD teams could start working in conjunction

730
00:46:43.120 --> 00:46:46.690
with classic GIS techs to create and maintain this data.

731
00:46:47.240 --> 00:46:52.210
Does the MIMS product have any of this capability? Wow.

732
00:46:52.840 --> 00:46:57.730
Yeah, this is a, So there's a, a couple different, a couple ways to go here.

733
00:46:58.190 --> 00:47:02.810
Um, so the, the mention of of CAD is a,

734
00:47:02.810 --> 00:47:03.370
is a good one,

735
00:47:03.370 --> 00:47:08.290
and I know historically CAD and GM and and GIS are diametrically opposed,

736
00:47:08.290 --> 00:47:10.650
right? And it's, it, I, I've,

737
00:47:11.200 --> 00:47:14.850
I've some sometimes in my career wondered why they were almost laughably at

738
00:47:14.880 --> 00:47:19.090
odds. Um, so fortunately, um, they have, uh,

739
00:47:19.320 --> 00:47:22.410
come to be much more aligned as you are hopefully aware. Um,

740
00:47:23.130 --> 00:47:27.650
Esri and AutoCAD have, have developed much more of a partnership. Um,

741
00:47:27.710 --> 00:47:30.880
and there is starting at, uh, at ARC Map 10 61,

742
00:47:30.950 --> 00:47:33.560
there's a cat interoperability extension, uh,

743
00:47:33.560 --> 00:47:36.760
and then at RJs Pro it is natively enabled. Um,

744
00:47:36.980 --> 00:47:40.080
so what that means really interesting, I think, um,

745
00:47:40.100 --> 00:47:44.040
in the world of the utility network, which is all services based, um, and,

746
00:47:44.260 --> 00:47:49.000
and with, with that function being native to pro, you have the potential of,

747
00:47:49.820 --> 00:47:54.050
um, of actually editing GIS in cad.

748
00:47:54.710 --> 00:47:58.650
And what I mean by that is you can, you could have, um, a, a,

749
00:47:58.890 --> 00:48:02.890
a CAD document that has, that has layer sources, which are, um,

750
00:48:02.890 --> 00:48:07.810
services from your GIS system. And so I, I think I, I really think that, um,

751
00:48:08.200 --> 00:48:11.410
this is a great use for that because when we're talking about this level of

752
00:48:11.410 --> 00:48:12.570
detail that you see within your stations,

753
00:48:12.570 --> 00:48:14.410
you're talking about really precise sketching.

754
00:48:14.830 --> 00:48:18.890
And anyone who's tried to do really precise sketching in GIS has learned that

755
00:48:18.890 --> 00:48:22.080
it's not always the ideal place for it. So for me,

756
00:48:22.080 --> 00:48:24.480
this is another one of those things where we can kind of have our cake too.

757
00:48:24.500 --> 00:48:28.800
We can have our, our data, uh, source B G I S,

758
00:48:29.180 --> 00:48:32.200
but use the right tool for the job. In the case that we're talking about really,

759
00:48:32.200 --> 00:48:36.000
really precise, or I'm, I'm, I'm mapping switches or bus work or,

760
00:48:36.060 --> 00:48:39.880
or it might be much more practical. It might be the case that, um,

761
00:48:39.880 --> 00:48:43.320
we don't have bodies to start taking on this extra work on the GIS side,

762
00:48:43.620 --> 00:48:47.040
but we do have this, this CAD team that maintains these diagram,

763
00:48:47.130 --> 00:48:50.000
these substation diagrams now, and we want to continue using,

764
00:48:50.610 --> 00:48:52.920
using those skills and, and, uh, and,

765
00:48:52.980 --> 00:48:56.600
and letting them use a platform that's familiar to them. There's,

766
00:48:56.600 --> 00:48:58.760
there's very much a hybrid workflow here where,

767
00:48:58.810 --> 00:49:02.600
where we can accomplish all of that, um, and as I said, have, have the,

768
00:49:02.600 --> 00:49:04.320
the schema established, um,

769
00:49:04.340 --> 00:49:08.660
in gis and create those features or edit those features or update them, um,

770
00:49:08.690 --> 00:49:12.740
through, through CAD and, um, and it's this big happy marriage.

771
00:49:13.760 --> 00:49:17.790
Um, the other question, um, about mims,

772
00:49:17.790 --> 00:49:22.750
so does the mims product have it in this capability? Um, so with, with mims,

773
00:49:23.010 --> 00:49:27.160
um, MIMS is even even more lightweight, right? So the, the,

774
00:49:27.160 --> 00:49:31.720
the ease of sketching is, is fantastic. When I, I first saw this before I,

775
00:49:32.020 --> 00:49:35.720
um, was employed here and, and, um, my, my background in,

776
00:49:35.780 --> 00:49:38.880
in engineering and design, I, I looked at this and I was like, oh my gosh,

777
00:49:38.880 --> 00:49:41.160
this is, this is what it was supposed to be like all along.

778
00:49:41.160 --> 00:49:44.920
It's so much simpler. Um, but that from, from the ex,

779
00:49:44.920 --> 00:49:46.280
the explanation I just gave you, you,

780
00:49:46.300 --> 00:49:49.600
you may gather that these are kind of a different end of the spectrum a bit.

781
00:49:49.740 --> 00:49:52.440
So MIMS is really built for, um,

782
00:49:52.960 --> 00:49:56.720
a kind of more macro skill drawing and design. Um,

783
00:49:56.740 --> 00:50:01.160
so Mims may absolutely be used for, uh,

784
00:50:01.160 --> 00:50:02.800
like say we're building out a new substation,

785
00:50:02.800 --> 00:50:07.640
we're building out a new regulator station, and I want to, I want to place, um,

786
00:50:08.260 --> 00:50:10.920
the macro elements, let's say those templates that Aaron mentioned earlier.

787
00:50:11.030 --> 00:50:13.520
I've got a, I've got a template which is, uh,

788
00:50:13.560 --> 00:50:16.080
a breaker and two disconnects on either side, or I've got a template,

789
00:50:16.080 --> 00:50:20.800
which is a regular station with fittings and a number of details within it. Um,

790
00:50:21.100 --> 00:50:25.840
you can, you can place those very, very simply on, uh, within mims.

791
00:50:26.180 --> 00:50:28.220
Um, but just know that there's gonna be, there would be some,

792
00:50:28.450 --> 00:50:31.380
some background detail you'd want to do, uh, once the,

793
00:50:31.380 --> 00:50:34.940
once the job got into Pro, once the features got into pro. So, um, again,

794
00:50:34.940 --> 00:50:39.250
kind of a hybrid. I would, I would say, frankly,

795
00:50:39.310 --> 00:50:43.370
if you're talking about drawing bus work and drawing these really detailed, um,

796
00:50:43.400 --> 00:50:48.130
station internals, um, Mims is, is probably not the, the, the place that I,

797
00:50:48.130 --> 00:50:51.450
were trying to button up all that detail, but it can, it can absolutely get you,

798
00:50:51.910 --> 00:50:55.650
um, a a quick and easy, um, starting point.

799
00:50:56.980 --> 00:51:00.170
All right. Thanks, Isaac. Okay. All right. For gas,

800
00:51:00.590 --> 00:51:04.090
are Reg stations currently are just points to get started.

801
00:51:04.100 --> 00:51:06.410
Could we start with a low fidelity model,

802
00:51:06.690 --> 00:51:10.770
a polygon container with just an inlet pressure and outlet pressure,

803
00:51:10.920 --> 00:51:14.130
then over time fill in the details within the container?

804
00:51:15.440 --> 00:51:20.100
Yes. Um, if in, in this case, um, I think this is,

805
00:51:20.800 --> 00:51:24.020
uh, so you could, you would configure your rules either to really,

806
00:51:24.020 --> 00:51:27.660
your rules should support what your data can support. Um, there,

807
00:51:27.660 --> 00:51:30.940
there are going to be some, some outliers to that, some areas where you need to,

808
00:51:31.440 --> 00:51:36.300
uh, to increase your data for the, the, the network to really function. Um, I'm,

809
00:51:36.600 --> 00:51:38.420
I'm, I'm throwing that out as a potential,

810
00:51:38.420 --> 00:51:41.220
but I have not seen it actually firsthand. Um, for,

811
00:51:41.280 --> 00:51:45.940
for all the projects I've been involved in so far, um, we've, there,

812
00:51:45.940 --> 00:51:47.380
there is a, there is a way to,

813
00:51:47.380 --> 00:51:50.300
to mesh up to get the existing data and your existing business rules to,

814
00:51:50.640 --> 00:51:55.220
to have the UN function. So to answer your, your question shortly, um, yes,

815
00:51:56.160 --> 00:51:59.860
you can start at that, that lower end and increase it over time. Um, and,

816
00:51:59.920 --> 00:52:03.480
and really that's a, that's an approach I think makes sense for a lot of people.

817
00:52:03.630 --> 00:52:07.080
What, what low, what the lower end means is kind of, um,

818
00:52:07.100 --> 00:52:11.680
is gonna depend a little bit on, on utility for some, for some folks that they,

819
00:52:11.680 --> 00:52:13.680
they may look at medium as kind of their low end and,

820
00:52:13.680 --> 00:52:16.800
and know that in the future they want to go to a crazy level of detail. Um,

821
00:52:17.110 --> 00:52:20.280
this is, but definitely something you can, you can address. Um,

822
00:52:20.280 --> 00:52:24.920
you can support with, um, configuration of UN rules. Uh, and if you,

823
00:52:24.940 --> 00:52:26.920
if you need, like, as I mentioned earlier,

824
00:52:26.940 --> 00:52:29.920
you can create distinct asset types for different rule sets.

825
00:52:31.300 --> 00:52:33.920
How do you make sure this type of data stays up to date?

826
00:52:34.540 --> 00:52:36.680
The station engineers don't tell us anything.

827
00:52:37.460 --> 00:52:41.560
You just hope for the best, not really. Um, so,

828
00:52:42.260 --> 00:52:44.800
um, this, I I think, um, one,

829
00:52:45.380 --> 00:52:48.520
anyone who's lived with a GS for a while knows that this is a,

830
00:52:48.520 --> 00:52:50.360
this is a challenge, right? Particularly when we start to,

831
00:52:50.750 --> 00:52:54.920
when we're looking to model additional data. I, I, I think this,

832
00:52:55.030 --> 00:52:58.480
this again goes back to, uh, when we're looking to source data,

833
00:52:58.770 --> 00:53:01.640
where can we find it now? Um, and, and so I,

834
00:53:01.680 --> 00:53:05.520
I think the more you can plug into sourcing this additional data to,

835
00:53:05.980 --> 00:53:09.200
to establish work practices and establish systems within the,

836
00:53:09.200 --> 00:53:12.680
within your enterprise that have it, the more we can kind of, uh,

837
00:53:12.680 --> 00:53:16.320
we can find a way to make use of this process rather than create a new workflow,

838
00:53:16.320 --> 00:53:21.200
create a new process for, uh, for maintaining data forever and ever,

839
00:53:21.200 --> 00:53:25.640
right? So, um, this, this could take, uh,

840
00:53:25.710 --> 00:53:30.480
take shape in the form of, um, pulling some of these, these assets from,

841
00:53:30.780 --> 00:53:35.720
uh, from your Maximo system. So you've got a, your substation engineers are,

842
00:53:35.900 --> 00:53:39.320
are conditioned to, um, to input their assets and,

843
00:53:39.460 --> 00:53:42.720
and their inspection records into Maximo. Let's make use of that, like,

844
00:53:42.720 --> 00:53:46.200
let's not right create it, but let's look at a way to, um, to create a, a,

845
00:53:46.560 --> 00:53:49.440
a one-way integration to push that detail to gis.

846
00:53:49.580 --> 00:53:52.000
So we're not asking them for any other work, but we have another,

847
00:53:52.060 --> 00:53:56.120
we have another tool for them, uh, to consume it. Um, another,

848
00:53:56.150 --> 00:54:00.000
another thing that I, I, I think is, is very useful, um, to,

849
00:54:00.000 --> 00:54:03.520
to support this data maintenance is that CAD interoperability,

850
00:54:03.600 --> 00:54:06.000
I think is really, is really a big one. Um, the,

851
00:54:06.000 --> 00:54:09.120
the fact that we don't have to have this hard break away from cad, uh,

852
00:54:09.120 --> 00:54:12.360
they actually can play nicely together and, and we can make use of,

853
00:54:12.580 --> 00:54:16.240
of what what skillsets actually exist within your utility, I think is a,

854
00:54:16.460 --> 00:54:18.960
is a big benefit for keeping data up to date.

855
00:54:19.540 --> 00:54:23.560
Thanks, Isaac. All right. This next one, it's, uh, it's a blunt question. Are,

856
00:54:23.620 --> 00:54:25.440
are people actually doing all of this?

857
00:54:26.860 --> 00:54:30.200
Uh, yes. So, um, Mo I think

858
00:54:31.760 --> 00:54:35.680
probably all of our, of our details we've shared today, um,

859
00:54:35.700 --> 00:54:39.120
are from existing projects we have ongoing. Um, so we've got a, a,

860
00:54:39.160 --> 00:54:44.080
a couple different, um, tran uh, uh, like substation pods that have gone on and,

861
00:54:44.080 --> 00:54:48.080
and different levels of detail. We had, um, we had one, one client who,

862
00:54:49.160 --> 00:54:51.940
uh, who started with, they kinda wanted to see what the,

863
00:54:51.940 --> 00:54:55.460
the minimum viable product was for establishing connectivity across the

864
00:54:55.460 --> 00:54:59.060
substation. And, and we accomplished that with, with,

865
00:55:01.400 --> 00:55:04.910
Uh oh, may have lost Isaac. Okay.

866
00:55:05.400 --> 00:55:10.270
We're gonna close out. Uh, just wanna say thank you to our speakers. Uh,

867
00:55:10.440 --> 00:55:12.990
thank you for joining us today. Taking time outta your day, uh,

868
00:55:12.990 --> 00:55:13.870
and attending this webinar.

869
00:55:14.050 --> 00:55:18.110
We look forward to seeing you in two weeks at the location based MIM structure

870
00:55:18.120 --> 00:55:22.240
inspection. To register for this, please go to SSP Illuminate.

871
00:55:22.950 --> 00:55:25.260
Thanks everyone. Thank you.