Utility Network 101 | SSP iLLUMINATE 2020

2
00:00:03.830 --> 00:00:07.290
My name is Keith Freeman. I'm the director of marketing here at SSP Innovations,

3
00:00:07.550 --> 00:00:12.490
and today's webinar is titled Utility Network 1 0 1 UN Fundamentals.

4
00:00:13.230 --> 00:00:13.970
Before we begin,

5
00:00:13.970 --> 00:00:16.810
we wanted to let you know that this webinar will run just over an hour,

6
00:00:17.030 --> 00:00:21.690
and then we will do q and a. Your speaker today will be Dr. Joaquin Madrid.

7
00:00:21.840 --> 00:00:26.050
Joaquin is a senior solutions architect at S S P with over 20 years of

8
00:00:26.050 --> 00:00:27.530
experience designing, developing,

9
00:00:27.530 --> 00:00:31.530
and deploying a wide range of GIS solutions for the utility industry.

10
00:00:32.230 --> 00:00:35.930
His expertise focuses on modeling and behavioral analysis of the electric

11
00:00:36.170 --> 00:00:40.290
distribution network and their implementation within fully integrated enterprise

12
00:00:40.590 --> 00:00:41.423
GIS solutions.

13
00:00:41.920 --> 00:00:44.930
Joaquin will be answering questions at the end of his presentation,

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

15
00:00:48.570 --> 00:00:50.210
toolbar. Finally,

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

17
00:00:54.040 --> 00:00:55.450
Joaquin, whenever you're ready.

18
00:00:56.410 --> 00:00:56.700
Well,

19
00:00:56.700 --> 00:01:01.460
thank you for the introduction and thanks to everybody for joining

20
00:01:02.480 --> 00:01:07.020
and participating in this webinar where we are gonna dive into the

21
00:01:07.020 --> 00:01:10.540
fundamental details of the utility network.

22
00:01:10.760 --> 00:01:14.940
And when I say fundamental, I mean we are gonna touch on all the basic,

23
00:01:16.200 --> 00:01:17.033
um,

24
00:01:17.240 --> 00:01:21.700
topics of the new implementation of the G S

25
00:01:22.160 --> 00:01:26.300
b3, particularly for utilities. And when I say basic,

26
00:01:26.370 --> 00:01:29.740
that doesn't mean that are simple, is, uh, basic,

27
00:01:30.040 --> 00:01:34.580
as fundamental as the way the utility network is gonna

28
00:01:34.610 --> 00:01:39.500
support now the enterprise gi uh, GIS going forward.

29
00:01:40.960 --> 00:01:45.500
So the way I would like to present these

30
00:01:45.500 --> 00:01:48.220
fundamental concepts is, uh,

31
00:01:48.220 --> 00:01:51.860
through three fundamental questions. What it is,

32
00:01:52.770 --> 00:01:57.060
what is the utility network, how does it work,

33
00:01:57.800 --> 00:02:00.780
and why do we have a utility network now?

34
00:02:02.400 --> 00:02:07.140
So the what is gonna be answered by

35
00:02:07.140 --> 00:02:11.900
looking at the schema of the utility network, feature classes,

36
00:02:12.190 --> 00:02:17.020
asset groups and asset types, a new concept you've already been hearing, uh,

37
00:02:17.020 --> 00:02:18.500
for the last two, three years.

38
00:02:19.290 --> 00:02:22.140
Then we are also gonna see how the model,

39
00:02:22.480 --> 00:02:26.420
the schema is used to somehow give you the

40
00:02:26.950 --> 00:02:31.780
properties of the equipment and the infrastructure that are gonna support your

41
00:02:31.780 --> 00:02:36.660
utility gis and we'll discuss some concepts about

42
00:02:36.880 --> 00:02:40.100
the level of fidelity that you want to,

43
00:02:41.280 --> 00:02:46.260
or you need to add to your GIS for a more realistic model based

44
00:02:46.440 --> 00:02:50.380
on the needs of your enterprise. G i s

45
00:02:51.920 --> 00:02:56.100
how is gonna be answering, uh, the,

46
00:02:56.640 --> 00:03:01.640
by talking about the behavior of your model and the behavior is supported by

47
00:03:01.640 --> 00:03:06.240
the association rules, the attribute rules, and then some,

48
00:03:06.700 --> 00:03:11.280
uh, additional functionality that is gonna be provided to you by the

49
00:03:11.520 --> 00:03:16.000
partners. And they can be called partner productivities, um,

50
00:03:16.700 --> 00:03:18.080
fac, uh, capacities.

51
00:03:18.940 --> 00:03:22.080
And among them I'm gonna discuss particularly the,

52
00:03:22.260 --> 00:03:27.080
the concept of the template in when used for the installations of

53
00:03:27.150 --> 00:03:31.000
your equipment. The third question,

54
00:03:31.220 --> 00:03:33.240
why is mainly, uh,

55
00:03:33.240 --> 00:03:37.520
gonna be discussing the limitations that we find nowadays with the geometric

56
00:03:37.520 --> 00:03:42.080
network and how the utility network will provide you the

57
00:03:42.540 --> 00:03:46.280
GIS of your future. And then we'll have some time for questions.

58
00:03:47.700 --> 00:03:51.920
So I want to start this, uh, fundamental introduction to utility network,

59
00:03:51.920 --> 00:03:55.840
talking about what I consider is a fundamental concept

60
00:03:56.520 --> 00:04:00.760
introduced as a change by Esri in the new

61
00:04:00.760 --> 00:04:02.520
implementation of the gis.

62
00:04:03.140 --> 00:04:07.270
And that is the utility network is

63
00:04:08.050 --> 00:04:12.870
mainly a new implementation of a concept of a

64
00:04:13.190 --> 00:04:16.630
directed graph that is gonna help your utility.

65
00:04:17.250 --> 00:04:19.830
So we all are familiarized with graphs.

66
00:04:19.940 --> 00:04:22.510
They are a collection of vertices edges,

67
00:04:22.960 --> 00:04:27.350
those edges have or not, but usually they have direction,

68
00:04:27.350 --> 00:04:30.750
ability and the direction ability and that, uh,

69
00:04:31.060 --> 00:04:34.190
association between the vertices and the agencies.

70
00:04:34.190 --> 00:04:39.070
What allows you to have a description of your entity,

71
00:04:40.250 --> 00:04:41.010
eh,

72
00:04:41.010 --> 00:04:45.710
by exploiting the con the properties of connectivity and

73
00:04:45.710 --> 00:04:50.230
directional tracing. So this all sounds very abstract, but in,

74
00:04:50.470 --> 00:04:54.390
in in essence what we have is that via a directed graph,

75
00:04:55.570 --> 00:05:00.530
tracing gives you the ability of obtaining information about your network.

76
00:05:01.310 --> 00:05:05.570
So if your vertices are representing equipment the

77
00:05:06.260 --> 00:05:09.890
edges are representing, then, uh,

78
00:05:10.070 --> 00:05:13.490
in an electric network for instance lines,

79
00:05:14.040 --> 00:05:17.930
what we are representing here is your, um,

80
00:05:19.950 --> 00:05:24.350
electric distribution, for instance, network. And by tracing,

81
00:05:24.730 --> 00:05:29.430
you can then find information about the equipment,

82
00:05:29.770 --> 00:05:33.110
the relationship between one equipment and the other and the lines.

83
00:05:34.010 --> 00:05:37.550
And not only that, but also because it's on top of a G I S,

84
00:05:37.940 --> 00:05:42.630
it's gonna provide you with the capability to figure out how is this

85
00:05:42.660 --> 00:05:47.270
equipment and these lines interacting and relating

86
00:05:47.930 --> 00:05:50.670
to the geographic, uh,

87
00:05:51.120 --> 00:05:55.150
background to the geographic environment in which they exist.

88
00:05:57.190 --> 00:05:58.023
So

89
00:05:58.940 --> 00:06:02.830
that is a fundamental idea from my point of view of the utility network,

90
00:06:03.190 --> 00:06:06.150
a new implementation of a directed graph.

91
00:06:07.090 --> 00:06:11.710
But we already had a directed graph in the utility network in the geometric

92
00:06:11.710 --> 00:06:12.290
network.

93
00:06:12.290 --> 00:06:17.150
So how about as we start familiarizing with ourselves with

94
00:06:17.190 --> 00:06:21.550
a utility network, we compare things that we are familiarized with now,

95
00:06:21.550 --> 00:06:26.110
which is a geometric network. So if we compare them,

96
00:06:27.330 --> 00:06:30.630
we see that both the geometric and the utility network

97
00:06:32.340 --> 00:06:36.920
are at the core of an enterprise GIS for utility with, uh,

98
00:06:37.200 --> 00:06:40.640
business applications in electric power, gas, water,

99
00:06:41.250 --> 00:06:44.920
sewer and telecom among others. Also,

100
00:06:45.230 --> 00:06:49.600
both geometric and utility network based g i s

101
00:06:50.380 --> 00:06:54.640
are able to model the equipment that convey your commodity.

102
00:06:55.910 --> 00:06:57.810
So it gives you, as I mentioned before,

103
00:06:57.830 --> 00:07:00.530
the location and the attribution of your equipment,

104
00:07:01.140 --> 00:07:03.210
which are representing your assets,

105
00:07:04.030 --> 00:07:08.930
and also the interconnectivity through the network. And because it's a G I s,

106
00:07:08.950 --> 00:07:11.690
the relationship with to the surrounding environment.

107
00:07:11.750 --> 00:07:13.090
So it gives you the context.

108
00:07:14.310 --> 00:07:17.490
Now also similar to each other,

109
00:07:17.800 --> 00:07:21.890
both the geometric and utility network are implemented with the S D E

110
00:07:22.400 --> 00:07:27.050
geodatabase, um, uh, technology. So in that sense,

111
00:07:27.390 --> 00:07:32.210
you are already familiarized with the use of feature classes related objects

112
00:07:32.430 --> 00:07:36.930
and tables. And so there is, in that sense,

113
00:07:36.930 --> 00:07:41.930
there is no differentiation and both the geometric and the

114
00:07:41.930 --> 00:07:46.730
utility networks do coexist within the enterprise. Gi uh,

115
00:07:46.890 --> 00:07:49.050
g I s and I want to make emphasis there.

116
00:07:49.470 --> 00:07:54.280
The utility network is not necessarily your GI s

117
00:07:54.660 --> 00:07:59.560
the utility network is a fundamental component of

118
00:07:59.560 --> 00:08:04.160
your enterprise g i s, to model that directed graph,

119
00:08:04.580 --> 00:08:09.440
but it coexist with many other data sets like, uh,

120
00:08:09.470 --> 00:08:13.400
land base and water, uh, ways and customer information.

121
00:08:14.020 --> 00:08:17.600
It just coexist within the enterprise g uh,

122
00:08:17.920 --> 00:08:22.360
g i s to give you information that can be found

123
00:08:23.300 --> 00:08:27.560
and analysis or analytics based on traceability.

124
00:08:29.040 --> 00:08:33.310
So they are similar in some sense,

125
00:08:33.370 --> 00:08:36.710
but of course they are a little bit different or quite different.

126
00:08:36.890 --> 00:08:40.910
So when we compare them in terms of differentiation,

127
00:08:42.050 --> 00:08:46.470
the fundamental one is that the directive graph in a geometric network

128
00:08:47.650 --> 00:08:51.310
is implemented by geometric coincidence.

129
00:08:51.830 --> 00:08:56.320
Snapping of points to vertices of align is what

130
00:08:56.320 --> 00:08:59.240
provides your, um, uh,

131
00:08:59.240 --> 00:09:02.920
connectivity and your traceability in the utility network,

132
00:09:03.760 --> 00:09:07.760
actually the concept of connectivity or,

133
00:09:08.580 --> 00:09:09.413
uh,

134
00:09:12.220 --> 00:09:16.930
other relationships established by the new concept of association.

135
00:09:18.330 --> 00:09:18.980
Now,

136
00:09:18.980 --> 00:09:23.840
another important thing in the differentiate geometric and utility

137
00:09:24.000 --> 00:09:28.880
networks is that in the geometric network you can selectively say

138
00:09:28.990 --> 00:09:33.920
what participates or not in the dataset

139
00:09:34.060 --> 00:09:38.720
in which unify the network itself in the

140
00:09:38.830 --> 00:09:40.680
utility network. On the contrary,

141
00:09:41.140 --> 00:09:45.760
all the features in that utility network do participate

142
00:09:45.860 --> 00:09:50.800
either directly or indirectly in the implementation

143
00:09:50.860 --> 00:09:52.160
of the directed graph.

144
00:09:53.290 --> 00:09:57.820
Another important differentiation is that the geometric network has been, uh,

145
00:09:57.820 --> 00:09:59.580
traditionally, um,

146
00:10:00.970 --> 00:10:05.340
supported by a database server, eh,

147
00:10:05.520 --> 00:10:06.980
and client architecture,

148
00:10:07.510 --> 00:10:12.300
where now the utility network is fully web server client

149
00:10:12.660 --> 00:10:15.380
architecture means usability.

150
00:10:17.530 --> 00:10:22.500
Also, just in more granular matter, the geometric network, as we know,

151
00:10:22.560 --> 00:10:27.540
is being always heavy on database relationships and table joints query

152
00:10:27.610 --> 00:10:32.540
definitions to represent objects of the same kind but with different symbol.

153
00:10:33.920 --> 00:10:34.640
Um,

154
00:10:34.640 --> 00:10:39.420
it always has needed custom functionality to accommodate the

155
00:10:39.580 --> 00:10:41.740
business processes that you have in your utility.

156
00:10:42.560 --> 00:10:46.980
On top of that framework of the uh, g I S itself,

157
00:10:48.080 --> 00:10:50.140
the utility network, uh,

158
00:10:50.140 --> 00:10:53.500
comes now out of Esri with a lot of the

159
00:10:54.820 --> 00:10:59.500
functionality that you needed to customize in the past as an out of the box,

160
00:11:00.080 --> 00:11:03.780
uh, core, um, capabilities.

161
00:11:04.640 --> 00:11:08.140
So a lot of trace based analytics that are out of the box,

162
00:11:08.840 --> 00:11:13.660
the behavior of the model is also participated or is built in

163
00:11:14.000 --> 00:11:15.060
the utility network.

164
00:11:15.880 --> 00:11:20.660
The utility network manages not only your equipment and lines or

165
00:11:20.690 --> 00:11:25.580
equipment and pipes, but also the infrastructure that supports them.

166
00:11:26.170 --> 00:11:30.220
Like in the electric, uh, world, it could be, uh,

167
00:11:30.510 --> 00:11:34.740
poles and ducts and manholes. Uh, they, uh,

168
00:11:34.740 --> 00:11:39.060
now do participate in the utility network and there are a lot of

169
00:11:39.620 --> 00:11:44.340
implicit rules that provide with a mechanism to ensure a

170
00:11:44.520 --> 00:11:46.820
qa, qc and data integrity.

171
00:11:47.480 --> 00:11:50.700
And there are many other capabilities of the utility network.

172
00:11:52.640 --> 00:11:57.530
So let's now focus on each of the three fundamental questions in more

173
00:11:57.530 --> 00:12:02.050
detail. The, what, what is a utility network? And from my point of view,

174
00:12:02.070 --> 00:12:07.050
the best way to talk about a what is to dive into the actual model.

175
00:12:08.180 --> 00:12:11.880
So the model represented here as a pseudo, um,

176
00:12:13.270 --> 00:12:18.060
let's say U M L representation is made up of different

177
00:12:18.060 --> 00:12:19.180
parts, the core,

178
00:12:19.350 --> 00:12:24.340
which is the actual utility network implementation in from

179
00:12:24.540 --> 00:12:29.140
esri. Then the network components is the whole modeling of our,

180
00:12:29.140 --> 00:12:33.740
your equipment and the infrastructure supporting the equipment as well as the

181
00:12:33.750 --> 00:12:34.350
rules,

182
00:12:34.350 --> 00:12:39.300
which makes it possible for the model to work within a utility

183
00:12:39.330 --> 00:12:41.340
network, um, behavior.

184
00:12:43.100 --> 00:12:47.530
So also we can say that the network

185
00:12:47.660 --> 00:12:52.530
components are representing the what or responding to the what,

186
00:12:53.270 --> 00:12:56.370
the how is the rules of the utility network.

187
00:12:56.990 --> 00:13:01.850
And the why is the whole collection of the elements of the new utility

188
00:13:01.850 --> 00:13:06.770
network implementation. The core has elements such as the topology,

189
00:13:07.070 --> 00:13:10.610
the service territory, where your s is gonna be defined.

190
00:13:11.310 --> 00:13:15.890
It also provides now a collection of feature classes to

191
00:13:15.890 --> 00:13:17.450
support error management.

192
00:13:17.450 --> 00:13:22.210
You're gonna be able to see where the errors in your

193
00:13:22.210 --> 00:13:26.930
utility network from the point of view of validation of rules are located

194
00:13:26.930 --> 00:13:30.770
because you're gonna have points and lines and polygons, uh,

195
00:13:30.770 --> 00:13:33.850
representing that kind of error management.

196
00:13:34.350 --> 00:13:37.290
The utility network also supports diagrams,

197
00:13:37.830 --> 00:13:41.530
and those diagrams are actually, uh,

198
00:13:41.780 --> 00:13:46.690
one-to-one related to the map in the sense that any changes in the map

199
00:13:46.750 --> 00:13:50.450
are propagated immediately into the diagrams and vice versa.

200
00:13:52.160 --> 00:13:54.140
In terms of the network components,

201
00:13:55.040 --> 00:13:59.460
the utility network is characterized by implementing two

202
00:14:00.490 --> 00:14:04.110
or more, well actually one phone, uh,

203
00:14:04.320 --> 00:14:09.270
basic and essential, uh, network, which is a structure network,

204
00:14:09.610 --> 00:14:14.190
and then zero or many domain networks. Uh,

205
00:14:14.300 --> 00:14:16.230
zero would be a little meaningless.

206
00:14:16.370 --> 00:14:20.910
So you always have one or more domain networks where you are the modeling the

207
00:14:20.910 --> 00:14:24.950
equipment, the, the capacity to, uh,

208
00:14:25.080 --> 00:14:29.590
distribute your commodity, uh, is through the domain network.

209
00:14:30.010 --> 00:14:34.950
The structure network implements the model for the supporting

210
00:14:34.950 --> 00:14:35.783
infrastructure.

211
00:14:37.090 --> 00:14:40.870
The domain networks are classified, eh,

212
00:14:42.060 --> 00:14:45.270
also in terms of tiers and sub-networks,

213
00:14:45.440 --> 00:14:50.310
we'll discuss the details of those concepts. In terms of rules, as I mentioned,

214
00:14:50.310 --> 00:14:51.760
they are association rules,

215
00:14:51.760 --> 00:14:55.720
which are connectivity containing and attachment association rules,

216
00:14:56.340 --> 00:14:57.960
as well as a, uh,

217
00:14:57.960 --> 00:15:02.400
collection of attribute rules to ensure this data integrity.

218
00:15:04.270 --> 00:15:08.290
So let's look at in particular the domain network to start with,

219
00:15:08.400 --> 00:15:12.610
even though the structure network is the one that is always created when you

220
00:15:12.620 --> 00:15:15.650
stage a utility network, but I,

221
00:15:15.770 --> 00:15:20.650
I think it's important to start looking at the part of the utility network

222
00:15:20.720 --> 00:15:24.450
that is gonna be modeling the equipment, um,

223
00:15:24.950 --> 00:15:28.610
the lines or, or pipes and things like that.

224
00:15:29.940 --> 00:15:34.480
So a domain network is the part of the utility network

225
00:15:35.230 --> 00:15:39.480
that Mars your commodity, whether it's gas, electric,

226
00:15:40.380 --> 00:15:42.800
and I always make this point here,

227
00:15:42.850 --> 00:15:47.240
don't confuse domain here with a field domain. Uh,

228
00:15:47.400 --> 00:15:52.040
a coded value domain is the domain means what

229
00:15:52.040 --> 00:15:56.160
commodity you are representing with that network. Now,

230
00:15:56.220 --> 00:15:58.840
you could have one or more domains in your network.

231
00:15:59.140 --> 00:16:03.320
If we can think of a power company that could be using two domains,

232
00:16:03.660 --> 00:16:07.200
indivi independent domains, one for electric distribution,

233
00:16:07.220 --> 00:16:10.440
the other one for electric transmission. Um,

234
00:16:11.020 --> 00:16:15.800
we could also think of a multi utility company where they want to have

235
00:16:16.000 --> 00:16:17.640
a vertical for electric,

236
00:16:17.640 --> 00:16:21.480
another one for gas and another one for the water domains.

237
00:16:21.900 --> 00:16:26.720
And they will be implemented also as different domain networks.

238
00:16:27.730 --> 00:16:32.100
What is fundamental in the utility network now is that

239
00:16:32.310 --> 00:16:37.020
regardless of what you are representing in those domains,

240
00:16:37.770 --> 00:16:42.020
they can only be represented by five feature classes.

241
00:16:42.120 --> 00:16:44.180
And you may think that that is restrictive,

242
00:16:44.200 --> 00:16:48.700
but actually I think it's a very fundamental step forward

243
00:16:49.080 --> 00:16:53.940
in Esri thinking about what is a G I S A G I S is a collection of

244
00:16:54.390 --> 00:16:57.820
point features, blind features and polygon features.

245
00:16:57.880 --> 00:17:02.860
So what can we do with these three kind of features

246
00:17:04.000 --> 00:17:07.700
in terms of implementing everything needed for the G I s?

247
00:17:07.920 --> 00:17:10.700
And that's why I think there is this, uh,

248
00:17:10.900 --> 00:17:14.020
condensation now into only five feature classes,

249
00:17:14.750 --> 00:17:19.420
which of course they are farther classified into as a group and ASCE types to

250
00:17:19.420 --> 00:17:21.860
give the richness of the information.

251
00:17:22.160 --> 00:17:26.780
But it's important to know that we only have five feature classes participating

252
00:17:27.360 --> 00:17:31.140
in the domain network of a utility network.

253
00:17:33.160 --> 00:17:36.420
Now, all these feature classes do participate in the network.

254
00:17:36.610 --> 00:17:40.820
They are all discoverable by tracing

255
00:17:40.980 --> 00:17:44.500
capabilities in either directly or indirectly.

256
00:17:44.510 --> 00:17:49.280
We'll discuss that in more detail later if we pay attention to in the

257
00:17:49.370 --> 00:17:52.360
individual elements of the domain network.

258
00:17:53.450 --> 00:17:55.320
Let's start by looking at the device.

259
00:17:55.500 --> 00:17:59.880
The device feature class is actually a point, uh,

260
00:17:59.880 --> 00:18:04.880
feature class that is geared towards representing

261
00:18:05.750 --> 00:18:06.600
your assets,

262
00:18:07.020 --> 00:18:12.000
the equipment that actually delivers and operates and monitors the flow of your

263
00:18:12.000 --> 00:18:14.400
commodity. And for the first time,

264
00:18:14.470 --> 00:18:19.440
then you don't need related units to, uh, bank representation.

265
00:18:20.020 --> 00:18:24.720
You are actually capable of representing your assets,

266
00:18:25.700 --> 00:18:26.440
uh,

267
00:18:26.440 --> 00:18:31.200
geographically localize and network connected to

268
00:18:31.750 --> 00:18:33.600
your new g i s.

269
00:18:34.260 --> 00:18:37.240
So examples of course are transformers.

270
00:18:37.370 --> 00:18:41.040
Every closers in an electric valves, pumps, hydrants,

271
00:18:42.180 --> 00:18:45.320
you, you name item. The line feature class,

272
00:18:45.380 --> 00:18:50.200
of course is an implementation in either a simple or

273
00:18:50.350 --> 00:18:55.320
complex edge feature class that is the part of the network

274
00:18:55.430 --> 00:18:57.240
that is conveying the commodity.

275
00:18:58.340 --> 00:19:02.040
And as you can think of it is power lines, pipes, uh, cable,

276
00:19:02.310 --> 00:19:04.200
depending on your domain.

277
00:19:05.600 --> 00:19:10.500
The junction feature class is a very important one in the

278
00:19:10.500 --> 00:19:15.100
sense that is used to help you model connectivity

279
00:19:15.850 --> 00:19:19.820
attachments and other kind of associations so that

280
00:19:22.000 --> 00:19:22.833
you,

281
00:19:23.400 --> 00:19:28.380
you can ascribe some rules that allow or disallow

282
00:19:28.380 --> 00:19:30.940
this kind of connectivity or attachment.

283
00:19:31.880 --> 00:19:35.700
And the junctions are gonna facilitate that mechanism to,

284
00:19:35.880 --> 00:19:40.220
let me put an example. If you want to go from a, uh,

285
00:19:40.730 --> 00:19:45.380
pipe of, uh, a three inch pipe to a quarter inch pipe,

286
00:19:45.430 --> 00:19:48.420
which I don't know if you do often,

287
00:19:48.880 --> 00:19:52.460
but still you would need a fitting actually a three inch. Yeah,

288
00:19:52.560 --> 00:19:53.393
you could do that.

289
00:19:53.400 --> 00:19:57.580
You need a fitting and that is what the junction will be representing.

290
00:19:57.840 --> 00:20:02.060
The fitting will not be actually actually a device because it doesn't

291
00:20:02.450 --> 00:20:03.780
operate or monitor.

292
00:20:04.370 --> 00:20:07.980
It's mainly a way to facilitate that connectivity.

293
00:20:09.750 --> 00:20:14.650
Now then there is another feature class which is also implemented as

294
00:20:14.650 --> 00:20:16.050
points and is the assembly.

295
00:20:16.750 --> 00:20:21.670
The assembly feature class now is representing a

296
00:20:21.780 --> 00:20:26.470
equipment containment is a container that in a particular

297
00:20:26.750 --> 00:20:29.910
location hides all the complexity of your equipment.

298
00:20:30.370 --> 00:20:34.390
You can now look at a map at, uh, let's say, uh,

299
00:20:34.760 --> 00:20:38.830
scale of one to 1200 or 2,400, whatever you want.

300
00:20:39.370 --> 00:20:44.350
And you can see a a point and lines. And the point represents,

301
00:20:44.600 --> 00:20:46.230
let's say a transformer bank.

302
00:20:46.570 --> 00:20:51.280
The transformer bank itself is hiding the complexity of who

303
00:20:51.280 --> 00:20:56.120
knows what kind of fidelity level you want to put into your transformer model,

304
00:20:56.940 --> 00:20:59.600
but is heating at this high level, uh,

305
00:20:59.620 --> 00:21:02.400
as high scale because you don't want to be distracted.

306
00:21:02.400 --> 00:21:06.760
You don't want to clo your, um, maps with a lot of that information,

307
00:21:06.780 --> 00:21:10.640
but you still want to know that in that particular location you have a,

308
00:21:10.780 --> 00:21:14.550
an overhead three phase, um, uh,

309
00:21:15.300 --> 00:21:19.990
transformer or you have a regulator station in a gas distribution.

310
00:21:21.120 --> 00:21:25.430
There is one more feature class in the domain network, which is a subnet line.

311
00:21:25.450 --> 00:21:30.110
The subnet line, which is also implemented as a simple or complex edges,

312
00:21:31.210 --> 00:21:35.430
is an underlying and core supported,

313
00:21:36.570 --> 00:21:37.403
uh,

314
00:21:37.980 --> 00:21:42.390
multiline feature class that represents your circuits,

315
00:21:42.580 --> 00:21:45.430
your feeders, your um,

316
00:21:46.580 --> 00:21:51.170
areas of pressure in a way that with one single feature,

317
00:21:52.640 --> 00:21:57.420
you can represent a lot of the information in your network for that

318
00:21:57.550 --> 00:22:00.620
particular, uh, feeder in, in sensee.

319
00:22:00.920 --> 00:22:05.820
Now I say this core manage, so we don't have much,

320
00:22:06.440 --> 00:22:07.273
um,

321
00:22:07.600 --> 00:22:12.510
of a configuration to put into this subnet line

322
00:22:12.610 --> 00:22:16.230
except for what information we want to extract from it.

323
00:22:17.050 --> 00:22:21.390
And there is no capability to access it or,

324
00:22:21.890 --> 00:22:25.710
or manipulate it except for view it or

325
00:22:27.130 --> 00:22:31.270
create. So it's a read only kind of, um, feature class.

326
00:22:31.970 --> 00:22:36.950
And because it doesn't govern, um,

327
00:22:37.100 --> 00:22:41.350
much of the modeling of your network that you would need,

328
00:22:41.900 --> 00:22:43.830
then I consider as a

329
00:22:45.330 --> 00:22:47.890
internal feature class for, um,

330
00:22:49.820 --> 00:22:52.710
good to know, important to know, important to use,

331
00:22:53.170 --> 00:22:57.110
but one we don't interact with in the modeling, uh,

332
00:22:57.110 --> 00:23:01.710
level that I want to present in the rest of the, uh, of this webinar.

333
00:23:03.200 --> 00:23:06.980
Now, lemme just give you an example of what I'm talking about.

334
00:23:07.080 --> 00:23:11.500
The organization of features in the utility network with

335
00:23:11.610 --> 00:23:16.460
another pseudo U M L um, diagram representation.

336
00:23:16.770 --> 00:23:20.140
What I'm saying is that in the utility network in the domain,

337
00:23:21.120 --> 00:23:26.100
all the feature classes derived from an abstract utility network feature

338
00:23:26.230 --> 00:23:31.020
class, they belong to a domain network. Or let me put it this way,

339
00:23:31.950 --> 00:23:34.410
if I want to talk about the line feature class,

340
00:23:34.730 --> 00:23:39.450
I know that the line feature class derives from the utility network

341
00:23:39.450 --> 00:23:41.690
feature class. It belongs to a domain.

342
00:23:41.710 --> 00:23:46.360
So it's a domain feature class and participates in connectivity.

343
00:23:47.500 --> 00:23:51.560
Now, in, um, in this

344
00:23:53.070 --> 00:23:54.480
orangey area here,

345
00:23:54.580 --> 00:23:59.520
I'm representing that the line can implement any number of

346
00:23:59.520 --> 00:24:03.800
custom attribution with the fields and the types and all this stuff,

347
00:24:04.140 --> 00:24:07.640
and that is the main structure of the line feature class.

348
00:24:08.260 --> 00:24:13.200
Now then further classification of the line feature class comes in the form of

349
00:24:13.250 --> 00:24:16.560
asset groups and asset types. So for instance,

350
00:24:16.650 --> 00:24:21.640
asset group that we see here are busbar, medium voltage connector,

351
00:24:21.880 --> 00:24:26.360
neutrals, sub transmission, low voltage, those are your asset groups.

352
00:24:26.460 --> 00:24:30.040
And now each asset group has a collection of asset types,

353
00:24:30.110 --> 00:24:34.600
like the busbar has a cabinet busbar, a low voltage, uh,

354
00:24:34.890 --> 00:24:39.440
substation busbar and things like that. That's a further classification.

355
00:24:40.600 --> 00:24:45.020
The other important thing is that all those feature classes can

356
00:24:45.130 --> 00:24:49.580
participate either in one or several tiers. For instance,

357
00:24:50.280 --> 00:24:55.140
in the sub transmission tier, we could have sub transmission lines,

358
00:24:55.600 --> 00:24:59.660
you know, let's say the above 33, uh, kilovolts,

359
00:24:59.660 --> 00:25:01.260
the 69 kilovolts,

360
00:25:01.680 --> 00:25:06.260
but also the busbar that are inside of the substation,

361
00:25:07.120 --> 00:25:08.140
but could also,

362
00:25:08.150 --> 00:25:13.140
those busbar could also participate in some part of the primary tier

363
00:25:13.610 --> 00:25:18.150
equipment, whether it is in a, uh, uh,

364
00:25:19.630 --> 00:25:22.410
big switch gear somewhere or something like that.

365
00:25:23.630 --> 00:25:28.370
And so this is a classification in tiers and how different

366
00:25:28.900 --> 00:25:32.090
asset groups, uh, can participate in those tiers.

367
00:25:33.500 --> 00:25:38.190
Another capability of the utility network that resembles the, uh,

368
00:25:38.460 --> 00:25:43.350
what we are used to in the ESR implementation of the database is

369
00:25:43.490 --> 00:25:47.910
the use of related tables such as,

370
00:25:48.170 --> 00:25:49.003
for instance,

371
00:25:49.030 --> 00:25:53.950
a wire type or a wire data related table

372
00:25:54.050 --> 00:25:57.230
to the line where there is a, an actual relationship.

373
00:25:57.850 --> 00:26:02.590
And also there is farther hierarchy and relation

374
00:26:03.020 --> 00:26:07.990
when we could have associated tables that do not really participate in

375
00:26:08.130 --> 00:26:10.110
the utility network,

376
00:26:10.610 --> 00:26:13.870
but contribute with information such as align catalog.

377
00:26:14.850 --> 00:26:19.750
So that's an representation of an example of

378
00:26:19.850 --> 00:26:23.550
how the feature classes are organized in the utility network.

379
00:26:24.130 --> 00:26:29.110
As another example now of how they are represented, for instance, in a, uh,

380
00:26:29.610 --> 00:26:30.443
in a map,

381
00:26:31.430 --> 00:26:35.190
I want to compare how the geometric network would

382
00:26:36.160 --> 00:26:37.550
model a,

383
00:26:37.890 --> 00:26:42.110
an overhead three phase transformer in the

384
00:26:42.830 --> 00:26:46.520
geometric network. And that is by placing a

385
00:26:48.570 --> 00:26:52.630
one feature of the primary conductor feature class, right?

386
00:26:52.740 --> 00:26:55.630
That would be your three phase overhead line.

387
00:26:56.750 --> 00:27:00.280
Then at some vertex of your line,

388
00:27:01.020 --> 00:27:06.000
you would snap a one feature of the transformer

389
00:27:06.310 --> 00:27:07.680
bank feature class.

390
00:27:09.190 --> 00:27:12.970
And also out of the same point right there,

391
00:27:13.510 --> 00:27:17.970
you will be then connecting some segments representing

392
00:27:18.410 --> 00:27:21.090
actually three features of the secondary conductor,

393
00:27:21.290 --> 00:27:23.250
a completely different feature class.

394
00:27:24.030 --> 00:27:28.170
And at the end of those you will be snapping three service location.

395
00:27:29.150 --> 00:27:30.130
Now also,

396
00:27:30.270 --> 00:27:34.770
but not seeing the map are the three transformer units that

397
00:27:35.050 --> 00:27:38.490
represent the assets that provide for the cap, the,

398
00:27:38.630 --> 00:27:43.410
the electric properties of that transformation. How do we do this?

399
00:27:43.430 --> 00:27:47.930
In the utility network, there are several models. This is a fairly,

400
00:27:48.790 --> 00:27:53.010
um, simple, uh, fidelity model that I'm gonna represent.

401
00:27:53.030 --> 00:27:57.490
But the in fundamental concept is that we also have one feature,

402
00:27:58.540 --> 00:28:02.520
but it's a a line feature, meaning it's a feature of the line feature class,

403
00:28:03.010 --> 00:28:07.910
which belongs to the primary, um, asset group,

404
00:28:08.460 --> 00:28:11.950
okay? It would have an asset type probably of three phase overhead.

405
00:28:12.730 --> 00:28:14.340
Now the,

406
00:28:14.520 --> 00:28:19.500
for the first time we can see that the devices themselves, the asset,

407
00:28:19.520 --> 00:28:24.460
the transformers are coming in as three features of the device

408
00:28:24.460 --> 00:28:29.300
feature class of the asset group transformer as they could

409
00:28:29.300 --> 00:28:32.300
be of asset type overhead, single phase each.

410
00:28:33.610 --> 00:28:36.980
They would also bring a junction,

411
00:28:37.980 --> 00:28:40.580
a feature of the junction, uh,

412
00:28:40.580 --> 00:28:45.020
feature class of the asset group or asset type tap,

413
00:28:45.390 --> 00:28:50.060
which is gonna participate in the connectivity among

414
00:28:50.400 --> 00:28:51.700
the, uh,

415
00:28:52.110 --> 00:28:56.940
three devices underlying itself from the

416
00:28:56.940 --> 00:28:59.860
device, whether we want to snap it or or not.

417
00:29:00.560 --> 00:29:03.460
We will have then three lines again,

418
00:29:03.920 --> 00:29:06.980
but now of the secondary as a group.

419
00:29:07.890 --> 00:29:12.590
And at the end of those, we could actually place the devices we don't need,

420
00:29:12.590 --> 00:29:15.750
if we don't want to the, um,

421
00:29:17.320 --> 00:29:19.220
the service location anymore.

422
00:29:19.280 --> 00:29:23.660
The same way that we do not need the bank to be in the map

423
00:29:23.970 --> 00:29:28.900
anymore. That doesn't mean that we don't that because we don't need it anymore.

424
00:29:28.900 --> 00:29:33.740
We don't want it. I'm gonna show you later how it's advantageous to have those

425
00:29:34.190 --> 00:29:36.900
containers to hide some of that information.

426
00:29:37.490 --> 00:29:40.700
What about the structure network? Well, the structure network,

427
00:29:41.000 --> 00:29:44.280
I said is always created with the staging of the utility network.

428
00:29:45.020 --> 00:29:50.000
So every utility network has a single structure network representing all that

429
00:29:50.000 --> 00:29:54.440
infrastructure and is shared among all the domains of the network.

430
00:29:56.220 --> 00:29:58.640
In that sense, when I, uh,

431
00:29:58.860 --> 00:30:02.680
it brings into the utility network,

432
00:30:02.970 --> 00:30:05.440
three feature classes again is a fundamental,

433
00:30:05.740 --> 00:30:09.040
the structure junction is a point structure, line is aligned,

434
00:30:09.040 --> 00:30:13.380
and structure boundary is a polygon. So the,

435
00:30:13.650 --> 00:30:17.700
they are also further classified by as a group and asset type.

436
00:30:18.280 --> 00:30:22.860
And the important thing is that they now in the utility network

437
00:30:23.250 --> 00:30:27.340
participate indirectly in any

438
00:30:28.220 --> 00:30:32.060
tracing analytics that you run in your data.

439
00:30:32.800 --> 00:30:34.380
In some sense. Let me explain.

440
00:30:34.440 --> 00:30:38.900
In the past you would have to have custom, uh,

441
00:30:39.220 --> 00:30:43.660
functionality so that if you are tracing an electric feeder,

442
00:30:44.040 --> 00:30:48.660
but you wanted to know how many poles were supporting that electric,

443
00:30:49.600 --> 00:30:53.660
um, uh, lines and, and, and the equipment,

444
00:30:54.000 --> 00:30:58.780
you had to have custom functionality to find those through the

445
00:30:58.780 --> 00:31:01.820
tray, some proximity and things like that. Now,

446
00:31:02.080 --> 00:31:07.060
out of the box and if your model has been built correctly through

447
00:31:07.060 --> 00:31:08.380
attachment association,

448
00:31:08.380 --> 00:31:12.500
which we are gonna discuss the containing association,

449
00:31:13.240 --> 00:31:18.220
the elements of the network do participate and can be

450
00:31:18.460 --> 00:31:21.260
discovered through tracing analytics.

451
00:31:22.910 --> 00:31:24.730
So let's think about it.

452
00:31:24.800 --> 00:31:28.930
What we have is the structure junction represented as points

453
00:31:29.720 --> 00:31:33.200
have the elements that support, uh, or,

454
00:31:33.200 --> 00:31:37.880
or model elements of your infrastructure that support, uh,

455
00:31:38.370 --> 00:31:43.200
punctually elements of your domain. So poles, pads, vaults,

456
00:31:43.820 --> 00:31:47.840
and any equipment or any line then attaches

457
00:31:48.710 --> 00:31:52.010
to the structure junction. And then in that sense,

458
00:31:52.350 --> 00:31:55.250
the structure feature is, um,

459
00:31:55.830 --> 00:31:59.810
by attachment is discoverable through tracing

460
00:32:00.770 --> 00:32:02.030
the structure line,

461
00:32:02.360 --> 00:32:07.270
which is implemented by a simple or complex edge represents things like

462
00:32:07.270 --> 00:32:08.430
conduit, casing,

463
00:32:08.630 --> 00:32:13.070
trenches and equipment and lines of your domain are

464
00:32:13.260 --> 00:32:17.110
contained within your electric, um, sorry,

465
00:32:17.300 --> 00:32:20.390
your structure line elements. Finally,

466
00:32:21.800 --> 00:32:26.760
structure boundary, uh, is a polygon feature class representing,

467
00:32:26.780 --> 00:32:30.280
for instance your substation, yard park, pumping yard,

468
00:32:30.860 --> 00:32:35.360
and all the equipment is then contained within the boundary

469
00:32:36.060 --> 00:32:38.040
of these, um, polygons.

470
00:32:39.180 --> 00:32:42.400
And they can also contain other structure themselves.

471
00:32:42.540 --> 00:32:47.280
So this hierarchy is for domain features as

472
00:32:47.280 --> 00:32:52.160
well. Containment can be for domain features as well as structure features

473
00:32:53.720 --> 00:32:55.610
very quickly to represent you.

474
00:32:55.840 --> 00:33:00.570
Also that classification in pseudo U M L representation

475
00:33:01.310 --> 00:33:05.490
of the utility network feature classes for,

476
00:33:06.190 --> 00:33:09.050
um, structures. What I'm gonna represent here,

477
00:33:09.600 --> 00:33:13.690
similar to the line feature class from the domain is for instance,

478
00:33:13.690 --> 00:33:18.130
this structure junction feature class from the structured

479
00:33:18.310 --> 00:33:22.450
domain, uh, sorry, structure network. And that is, uh,

480
00:33:22.680 --> 00:33:27.530
represented as a feature class that inherits from the

481
00:33:27.530 --> 00:33:31.290
utility network feature class. So that's participates in the utility network.

482
00:33:31.750 --> 00:33:36.050
It participates actually in the structure network, not in the domain network.

483
00:33:36.830 --> 00:33:40.930
And it can also be owed with any collection of, uh,

484
00:33:41.040 --> 00:33:45.090
attribution that is needed to support your, um, business needs.

485
00:33:46.080 --> 00:33:48.390
It's then, uh,

486
00:33:48.660 --> 00:33:51.750
also classified in terms of as asset groups and as a type.

487
00:33:51.750 --> 00:33:53.710
And here for instance, the structure junction,

488
00:33:54.170 --> 00:33:58.790
we have highlighted a few of the asset groups like the push brace anchor guy

489
00:33:59.230 --> 00:34:03.350
overhead structures. Now the overhead structure would be farther,

490
00:34:04.090 --> 00:34:08.670
um, classified by H frames, pole tower,

491
00:34:09.330 --> 00:34:12.830
uh, ornament, like for light poles and things like that.

492
00:34:13.330 --> 00:34:17.590
And also what I have represented is that there is a

493
00:34:17.670 --> 00:34:22.550
relationship or in actually in the true sense there

494
00:34:22.550 --> 00:34:26.030
is association between these feature classes,

495
00:34:26.260 --> 00:34:29.350
whether it is by attachment or containment.

496
00:34:31.130 --> 00:34:34.790
So we have described the what, what is a utility network,

497
00:34:34.970 --> 00:34:39.550
and we have done it through the description of the

498
00:34:40.070 --> 00:34:43.070
elements that participate in the model and what they do.

499
00:34:44.910 --> 00:34:49.180
Um, now how do this, uh,

500
00:34:49.200 --> 00:34:53.900
how does this equipment, um, behave? What,

501
00:34:53.930 --> 00:34:58.540
what is a utility network providing us that helps us

502
00:34:58.870 --> 00:35:01.220
model this, um,

503
00:35:02.240 --> 00:35:06.860
the needs of a utility besides providing a

504
00:35:06.860 --> 00:35:08.340
description of the equipment.

505
00:35:08.640 --> 00:35:12.700
And that is a behavior and the capabilities to, um,

506
00:35:13.810 --> 00:35:18.370
Q A Q C and validate data as it's being used in the,

507
00:35:18.910 --> 00:35:22.880
uh, g I s let's think for a minute. At the end,

508
00:35:22.900 --> 00:35:27.560
the behavior is implemented by, uh, good, um,

509
00:35:30.870 --> 00:35:35.850
reorganization of the logical network and we discussed with the graph,

510
00:35:35.880 --> 00:35:38.560
dialectic graph is just a collection of, uh,

511
00:35:38.880 --> 00:35:43.870
junctions and edges and some junctions are

512
00:35:43.870 --> 00:35:47.750
connected to others through some other edges. So you could say,

513
00:35:47.770 --> 00:35:48.603
but wait a minute,

514
00:35:48.940 --> 00:35:53.750
both the geometric network and the utility network already rely on

515
00:35:53.870 --> 00:35:56.230
a logical network. So what is the difference?

516
00:35:56.730 --> 00:36:01.190
The main difference is that in the geometric network, the network elements,

517
00:36:01.690 --> 00:36:06.230
the network elements are features, meaning they do have geometry,

518
00:36:06.230 --> 00:36:11.150
those junctions and those edges that participate and provide

519
00:36:11.420 --> 00:36:15.590
with the implementation of the directi graph do have geometry.

520
00:36:16.170 --> 00:36:19.350
And then in order to establish that connectivity,

521
00:36:19.930 --> 00:36:24.750
you are forced to use not only geometric coincidence, but also, um,

522
00:36:25.020 --> 00:36:29.470
mathematics behind that is heavy on geometry.

523
00:36:30.810 --> 00:36:35.190
So then what is the advantage in that sense of using

524
00:36:35.730 --> 00:36:36.790
the utility network?

525
00:36:37.210 --> 00:36:41.430
The advantage is that the network elements in the utility network are

526
00:36:41.550 --> 00:36:45.430
associations. Associations are indexes.

527
00:36:45.650 --> 00:36:50.540
So your junctions and your edges do not really exist as features.

528
00:36:50.970 --> 00:36:55.420
They do exist as indices in tabular index,

529
00:36:56.120 --> 00:36:56.340
uh,

530
00:36:56.340 --> 00:37:01.180
representation that represents I the

531
00:37:01.760 --> 00:37:06.620
and records the connectivity in a way that can be easily and

532
00:37:06.770 --> 00:37:11.500
very efficiently traversed instead of all those geometric

533
00:37:11.500 --> 00:37:16.220
calculations that are needed to establish connectivity through a

534
00:37:16.220 --> 00:37:17.053
geometric network.

535
00:37:18.440 --> 00:37:23.060
So that's a fundamental aspect and main differentiation between the

536
00:37:23.060 --> 00:37:26.460
geometric network and the utility network. In the utility network,

537
00:37:27.660 --> 00:37:32.380
junctions and edges of the topological or logical,

538
00:37:33.320 --> 00:37:35.620
uh, network are indices.

539
00:37:37.730 --> 00:37:41.420
Now the way those indices,

540
00:37:41.510 --> 00:37:44.400
those um, uh,

541
00:37:46.090 --> 00:37:50.330
vertices and edges or junction and edges are being

542
00:37:50.840 --> 00:37:55.770
managed by the topological network is through association

543
00:37:55.770 --> 00:37:56.450
rules,

544
00:37:56.450 --> 00:38:01.370
associations with which define how a junction can or

545
00:38:01.370 --> 00:38:03.490
cannot be connected to another junction.

546
00:38:03.990 --> 00:38:08.930
How junctions connect to different edges and how edges may

547
00:38:09.130 --> 00:38:12.730
connect to other edges via a junction in between.

548
00:38:13.790 --> 00:38:18.770
So as an example, and you may have seen this in the S3 web, uh, pages,

549
00:38:19.390 --> 00:38:22.730
if we are representing in the utility network,

550
00:38:23.030 --> 00:38:25.770
the model for a three phase overhead transformer,

551
00:38:26.230 --> 00:38:30.970
now we can do it with a little more detail and in a way

552
00:38:30.970 --> 00:38:34.090
where what we have is our electric line there,

553
00:38:34.870 --> 00:38:39.440
it has a connection point and that connection point is probably a tap,

554
00:38:40.360 --> 00:38:45.110
uh, representing the way the three individual

555
00:38:45.950 --> 00:38:49.630
transformers are connected to the electric line.

556
00:38:50.250 --> 00:38:55.070
And the connection is not through jumpers like in the physical world,

557
00:38:55.330 --> 00:38:58.350
but it's actually through connectivity association,

558
00:38:58.350 --> 00:39:02.270
meaning T 1 22 and T3 participate

559
00:39:03.310 --> 00:39:08.050
or have representation of their junction, uh,

560
00:39:08.180 --> 00:39:10.530
image into industries table.

561
00:39:11.950 --> 00:39:16.890
And the industry table are telling us that T1 is related to

562
00:39:16.900 --> 00:39:21.450
their representation in edges and vertices of

563
00:39:21.450 --> 00:39:22.330
connection point,

564
00:39:22.910 --> 00:39:27.850
the same way T2 and t3 and also everything is

565
00:39:27.920 --> 00:39:32.410
contained. There is a containing association between the different,

566
00:39:32.910 --> 00:39:36.810
uh, cans or transformer, um, uh,

567
00:39:38.360 --> 00:39:42.770
devices into the composition. The bank itself,

568
00:39:43.070 --> 00:39:47.410
the bank is now structurally attached to the pole.

569
00:39:47.670 --> 00:39:51.890
The connection point is also, uh, attached to the pole.

570
00:39:52.390 --> 00:39:57.370
And the whole configuration then provides a seamless

571
00:39:58.670 --> 00:40:02.520
network implementation of your equipment, your lines,

572
00:40:03.260 --> 00:40:05.840
and your infrastructure supporting.

573
00:40:07.670 --> 00:40:12.220
There is also a collection of attribute rules that are using calculations,

574
00:40:12.810 --> 00:40:17.460
constraints, using a lot of code value domains and

575
00:40:18.820 --> 00:40:23.580
implicit validation that are gonna be running as you are editing your data.

576
00:40:23.840 --> 00:40:26.740
And they are gonna be, you know, probably, uh,

577
00:40:26.790 --> 00:40:30.580
indicating to you whether there is a validation, uh,

578
00:40:30.810 --> 00:40:32.140
violation at some point.

579
00:40:32.680 --> 00:40:37.300
And it's gonna try to ensure that the data that you are posting

580
00:40:37.770 --> 00:40:39.700
into your default, uh,

581
00:40:39.700 --> 00:40:44.660
representation of the g I s is the best, uh, that you can create.

582
00:40:46.520 --> 00:40:47.660
Let me uh,

583
00:40:47.830 --> 00:40:51.420
illustrate the concept of the connectivity association because as I said,

584
00:40:51.420 --> 00:40:55.980
these associations are not now visual in the sense that there are no lines

585
00:40:55.990 --> 00:40:58.180
connecting things. We have,

586
00:40:58.570 --> 00:41:03.100
this is a more complex or higher fidelity model for the,

587
00:41:04.230 --> 00:41:08.370
uh, three phase of our head transformer feeding three devices,

588
00:41:08.860 --> 00:41:13.170
three meters, okay? And that one still has a line,

589
00:41:13.350 --> 00:41:15.410
the overhead line, it has a tap,

590
00:41:16.150 --> 00:41:20.370
and then we can represent the three protection fuses, the,

591
00:41:20.470 --> 00:41:24.530
the expulsion cutouts and the three, uh,

592
00:41:25.080 --> 00:41:29.410
also protection arresters or or lining arresters, which,

593
00:41:29.950 --> 00:41:30.670
um,

594
00:41:30.670 --> 00:41:35.400
are connected in parallel with those fuses and protect the three

595
00:41:35.510 --> 00:41:37.760
devices or, or transformers.

596
00:41:38.180 --> 00:41:41.160
How is this connectivity association established?

597
00:41:41.780 --> 00:41:45.800
If we were to represent it graphically with dash lines,

598
00:41:45.830 --> 00:41:50.110
what we would see is that the tab is actually feeding the,

599
00:41:50.890 --> 00:41:51.723
uh,

600
00:41:52.180 --> 00:41:57.070
fuse and also in parallel with the fuse is the

601
00:41:57.190 --> 00:42:02.150
arrester to ground. And now the fuse is actually feeding the transformer,

602
00:42:02.730 --> 00:42:05.630
but particularly, and we are gonna talk about the terminals,

603
00:42:05.930 --> 00:42:09.310
is feeding the transformer in a high side terminal.

604
00:42:09.730 --> 00:42:13.990
In the low side is where we establish a another connectivity

605
00:42:14.180 --> 00:42:17.190
association to the line that fits the meter.

606
00:42:18.250 --> 00:42:22.030
So this is an important thing that as we move to the utility net,

607
00:42:22.030 --> 00:42:26.110
where we need to start making a mental abstraction in which we don't see the

608
00:42:26.110 --> 00:42:30.790
connectivity anymore. The connectivity is established, not geometrically,

609
00:42:31.130 --> 00:42:32.150
not by features,

610
00:42:32.450 --> 00:42:37.430
but actually by collection of indices that we can visualize if we

611
00:42:37.750 --> 00:42:42.710
represent some dash lines just to help, uh, the user if needed.

612
00:42:44.280 --> 00:42:48.660
So I discussed a, well, I presented the concept of terminal. What is a terminal,

613
00:42:48.940 --> 00:42:52.660
a device terminal to be precise. It's a logical connection.

614
00:42:52.780 --> 00:42:57.380
A terminal is not an element of the network in the sense that is not the utility

615
00:42:57.380 --> 00:43:02.180
network because it's not a a feature, it's not like a point, uh,

616
00:43:02.240 --> 00:43:05.860
or a part of your feature. It's actually a configuration.

617
00:43:05.970 --> 00:43:10.700
It's a property that you embed in the utility network that you can use and

618
00:43:10.700 --> 00:43:13.860
associate to network devices.

619
00:43:15.770 --> 00:43:17.110
And what are they for?

620
00:43:17.460 --> 00:43:22.350
They are there to support a more realistic model of the behavior of your

621
00:43:22.420 --> 00:43:25.790
equipment in your network. The terminals,

622
00:43:26.060 --> 00:43:27.870
what they are doing is, uh,

623
00:43:27.900 --> 00:43:32.230
providing with connectivity paths so we can be more precise.

624
00:43:32.550 --> 00:43:37.360
Remember in the utility in the geometric network, there is only one pass

625
00:43:39.190 --> 00:43:40.023
on the trace,

626
00:43:40.180 --> 00:43:45.170
which is from one edge to one point and then multiple edges or one,

627
00:43:46.070 --> 00:43:50.650
but there is no differentiation of how

628
00:43:51.600 --> 00:43:56.050
that trace behaves in at that particular place where we are

629
00:43:56.050 --> 00:43:57.330
representing the equipment.

630
00:43:58.610 --> 00:44:01.110
And we are gonna see an example of how that works.

631
00:44:02.380 --> 00:44:06.590
Another important thing before we go into the example is that the terminals

632
00:44:06.840 --> 00:44:10.950
don't need to con be configured whatsoever to all the devices,

633
00:44:11.170 --> 00:44:13.790
but just to a specific collection of devices.

634
00:44:14.450 --> 00:44:19.190
And for sure we need to or is mandated that we provide

635
00:44:19.590 --> 00:44:24.230
terminal configuration for devices that require a high and a low,

636
00:44:25.010 --> 00:44:25.230
uh,

637
00:44:25.230 --> 00:44:30.070
some kind of asymmetry in the way they are propagating your commodity as

638
00:44:30.070 --> 00:44:34.080
well as those that participate as the

639
00:44:34.590 --> 00:44:37.800
sources or syncs in your utility network,

640
00:44:37.980 --> 00:44:42.000
the controllers of your network. So from now on,

641
00:44:42.140 --> 00:44:47.000
we are able to actually represent with higher fidelity the properties

642
00:44:47.000 --> 00:44:51.440
of a transformer bank because now we can have a terminal

643
00:44:51.840 --> 00:44:55.440
configuration that represents the bushing, which is at a, uh,

644
00:44:55.580 --> 00:44:59.640
12.7, uh, kilovolt, for instance,

645
00:44:59.940 --> 00:45:04.440
versus the lu, uh, the logs that are feeding,

646
00:45:04.860 --> 00:45:07.360
uh, two 40, um, uh,

647
00:45:08.430 --> 00:45:10.360
residential customer for instance.

648
00:45:11.300 --> 00:45:16.120
So what you see about this connectivity granularity or or detail

649
00:45:16.780 --> 00:45:20.940
is that let me represent you with a bypass switch.

650
00:45:21.360 --> 00:45:22.580
We have, uh,

651
00:45:23.380 --> 00:45:28.300
a model now that allows us to say a bypass switch has four terminals,

652
00:45:28.460 --> 00:45:30.820
T 1 22, T3 and t4.

653
00:45:31.440 --> 00:45:34.820
And if we define the path of

654
00:45:36.280 --> 00:45:40.450
flow from T one two, T two, and then from T3 two t4,

655
00:45:40.960 --> 00:45:44.650
this path will be considered the energized path

656
00:45:45.250 --> 00:45:50.210
representing the connectivity in this particular configuration of

657
00:45:50.230 --> 00:45:53.170
our device. And similarly,

658
00:45:53.990 --> 00:45:58.690
if we define another, an alternative path, which is from T1 two t4,

659
00:45:59.030 --> 00:46:03.930
it will be representing in a very high detail the de-energized

660
00:46:04.410 --> 00:46:08.870
behavior of your bypass switch. So

661
00:46:10.380 --> 00:46:15.350
with the same example of the three phase transformer that I

662
00:46:15.350 --> 00:46:19.350
discussed before for uh, connectivity association,

663
00:46:19.650 --> 00:46:23.430
I'm gonna talk now about containing association and why it's important

664
00:46:23.680 --> 00:46:28.550
containing association, even though it's not necessary, but it's very important.

665
00:46:29.370 --> 00:46:32.670
So we have this model and there is a lot of detail at this,

666
00:46:33.000 --> 00:46:36.870
let's say level of, um, resolution,

667
00:46:36.880 --> 00:46:40.870
which let's say this is a 1 25, uh,

668
00:46:41.400 --> 00:46:42.550
scale in the map,

669
00:46:43.490 --> 00:46:48.390
but we could now associate here by containment all the elements

670
00:46:48.570 --> 00:46:53.350
of the equipment into an assembly feature that we are gonna

671
00:46:53.350 --> 00:46:57.430
call all the, as a group, trans transformer bank. What happens,

672
00:46:58.370 --> 00:47:03.270
uh, an as, uh, similarly, we could now have two assembly features,

673
00:47:04.300 --> 00:47:09.040
column service location that are to represent where

674
00:47:09.340 --> 00:47:11.760
for a customer, a, uh,

675
00:47:11.760 --> 00:47:16.520
you are providing some power and also for a customer B and C

676
00:47:16.990 --> 00:47:21.600
that has maybe a main house and an attached apartment or something like that,

677
00:47:21.620 --> 00:47:24.160
you are providing also, uh, power there.

678
00:47:24.740 --> 00:47:28.960
But now the beauty or the usability of the cont uh,

679
00:47:29.700 --> 00:47:34.280
the containers is that they can hide all that very minute

680
00:47:34.820 --> 00:47:35.653
detail

681
00:47:36.740 --> 00:47:40.200
in such a way that if this was a representation at

682
00:47:40.300 --> 00:47:43.240
1 10, 1 50 scale,

683
00:47:43.510 --> 00:47:48.320
when you are looking at the map at one 1200 for instance,

684
00:47:48.460 --> 00:47:51.960
or 24, 1 of the common ways that you look at a map,

685
00:47:52.300 --> 00:47:54.080
all that information would be hidden,

686
00:47:54.540 --> 00:47:58.720
but you would still be able to discern from your map representation that there

687
00:47:58.720 --> 00:48:03.640
is an overhead three phase feeding two different, uh, service locations.

688
00:48:04.220 --> 00:48:09.080
So again, the associations are not presented as,

689
00:48:09.420 --> 00:48:12.040
uh, features, they are indexes.

690
00:48:12.540 --> 00:48:16.040
And we also have to have the mental, uh,

691
00:48:16.150 --> 00:48:21.080
leap to think of the abstraction that things are contained in

692
00:48:21.410 --> 00:48:26.400
assemblies because there is an indexed based association between

693
00:48:26.780 --> 00:48:30.480
the devices, the lines, and the container itself.

694
00:48:31.570 --> 00:48:36.280
Attachment association is a less kind of association and that allows us for

695
00:48:36.900 --> 00:48:41.880
the domain devices and junctions and lines to

696
00:48:41.900 --> 00:48:44.160
be attached to structures.

697
00:48:44.220 --> 00:48:49.160
And what is the advantage of that is simply so that simply

698
00:48:49.180 --> 00:48:52.080
or not simply is so that the

699
00:48:53.380 --> 00:48:54.280
infrastructure,

700
00:48:54.500 --> 00:48:59.320
the elements like poles and trenches and vaults that do

701
00:48:59.320 --> 00:49:04.000
not really convey the power in a u in an electric utility,

702
00:49:04.740 --> 00:49:09.680
but they can participate in the network indirectly by

703
00:49:09.680 --> 00:49:14.640
attachment association and then can be discovered through, uh,

704
00:49:14.810 --> 00:49:15.880
trace analytics

705
00:49:17.480 --> 00:49:21.300
and the structured junction supports, um,

706
00:49:22.280 --> 00:49:26.300
at attachment association while the, um,

707
00:49:27.730 --> 00:49:32.170
structure lines and structure polygon support, eh,

708
00:49:32.980 --> 00:49:37.490
containing association as well. And just to represent here,

709
00:49:37.990 --> 00:49:41.250
eh, following the model that we were talking about before,

710
00:49:41.630 --> 00:49:45.410
we would be attaching just simply by attaching the

711
00:49:46.550 --> 00:49:48.850
um, bank to the pole.

712
00:49:49.550 --> 00:49:53.770
We ensure that the pole is discoverable when we are tracing.

713
00:49:53.790 --> 00:49:58.170
We could also attach the, um, connection point to the pole.

714
00:49:58.270 --> 00:50:00.690
We could even attach the different devices,

715
00:50:00.790 --> 00:50:05.630
but one attachment is enough to discover the pole.

716
00:50:07.170 --> 00:50:09.660
This concept of tiers and sub-networks,

717
00:50:09.660 --> 00:50:13.820
which also respond on how does the utility network work

718
00:50:14.760 --> 00:50:19.750
is of fundamental interest because tiers provide a

719
00:50:19.990 --> 00:50:21.710
classification or,

720
00:50:21.810 --> 00:50:26.690
or a partition of your domain

721
00:50:26.840 --> 00:50:31.210
network into areas that distinguish

722
00:50:32.370 --> 00:50:36.970
business functionality. So for instance, we could have, uh,

723
00:50:37.110 --> 00:50:41.290
in a electric domain, we could have different tiers,

724
00:50:41.310 --> 00:50:45.210
one for transmission, primary distribution, secondary distribution,

725
00:50:46.270 --> 00:50:49.490
but also we could have divided them by just voltage.

726
00:50:49.980 --> 00:50:52.530
Level one is high, medium, and low.

727
00:50:53.070 --> 00:50:58.010
So there are many different ways of creating this classification of your

728
00:50:58.070 --> 00:51:01.890
domain network into tiers. But the other, uh,

729
00:51:02.030 --> 00:51:06.210
and in gas it would be the gathering from the well to the compressor

730
00:51:06.210 --> 00:51:10.250
transmission distribution as well. The other concept,

731
00:51:10.430 --> 00:51:15.370
the concept of the sub network is a ASAP network is an element of a tier

732
00:51:15.520 --> 00:51:20.330
that represents all the equipment aligns and

733
00:51:20.330 --> 00:51:23.890
infrastructure that is connected or

734
00:51:24.900 --> 00:51:29.800
associated, whether it's by connectivity, um,

735
00:51:30.940 --> 00:51:35.330
containment or attachment association into a single

736
00:51:36.860 --> 00:51:41.540
hmm entity. So let me explain with example, it's, uh,

737
00:51:42.260 --> 00:51:47.060
a sub network is a collection of elements in your

738
00:51:47.240 --> 00:51:51.460
domain network in a particular tier that are all participating

739
00:51:52.860 --> 00:51:56.750
in the, um, in,

740
00:51:56.750 --> 00:51:59.670
in a feeder in the electric world or,

741
00:51:59.970 --> 00:52:03.030
or in a domain of the gas world.

742
00:52:03.530 --> 00:52:07.310
So each feeder has a collection of all the

743
00:52:08.230 --> 00:52:12.750
elements that are connected and associated by attachment

744
00:52:13.330 --> 00:52:18.070
to a particular layout of your um,

745
00:52:18.830 --> 00:52:19.663
infrastructure.

746
00:52:21.760 --> 00:52:26.410
Some networks then have either sources which are the

747
00:52:26.430 --> 00:52:30.570
origin of the commodity or sinks if you,

748
00:52:30.590 --> 00:52:34.090
we are talking about a gravity driven network like sewer.

749
00:52:36.090 --> 00:52:36.923
And finally,

750
00:52:37.050 --> 00:52:41.750
to explain how the utility network can

751
00:52:42.250 --> 00:52:45.390
put together all this information, uh,

752
00:52:45.690 --> 00:52:50.190
I'm gonna discuss a concept of templates as presented by

753
00:52:50.430 --> 00:52:52.070
partners like S S P.

754
00:52:52.330 --> 00:52:56.350
The concept of the template in R G I S PRO can be extended

755
00:52:57.290 --> 00:53:02.110
to consolidate into a single entity the fidelity

756
00:53:02.250 --> 00:53:06.950
of the model, all the connectivity of the different elements of that model,

757
00:53:07.910 --> 00:53:12.050
the containment attachment and all the attribute rules that we want to govern

758
00:53:12.470 --> 00:53:16.930
the behavior and, and, and the properties of that,

759
00:53:17.470 --> 00:53:22.410
of the installation of that equipment is a, an encapsulation of that property.

760
00:53:23.160 --> 00:53:24.530
It's better to show an example.

761
00:53:24.710 --> 00:53:29.200
And here is an example of the template that we would provide

762
00:53:29.580 --> 00:53:34.120
for a three phase capacitor. Here what we have is a,

763
00:53:34.500 --> 00:53:38.440
an assembly which represe in the square that represents

764
00:53:39.540 --> 00:53:44.200
the container of all these equipment, which are the three,

765
00:53:44.780 --> 00:53:48.360
uh, assets, the three capacitors devices themselves.

766
00:53:49.180 --> 00:53:52.120
And then the tapping represent,

767
00:53:52.140 --> 00:53:56.680
or this junction represents the way capacitors are tapping to,

768
00:53:57.140 --> 00:53:59.200
um, to a mainline.

769
00:54:00.060 --> 00:54:04.880
And what I'm illustrating here with these dash lines which do

770
00:54:04.900 --> 00:54:07.520
not exist in the utility network,

771
00:54:07.670 --> 00:54:10.600
they are representing the indexing association.

772
00:54:11.150 --> 00:54:15.320
What I'm representing here is that the template

773
00:54:16.280 --> 00:54:19.970
overall encapsulates not only the

774
00:54:20.970 --> 00:54:24.980
quality of the equipment, meaning what do we have in there,

775
00:54:25.400 --> 00:54:30.300
but also the relationship or the association that exists,

776
00:54:30.300 --> 00:54:35.220
that establishes the connectivity as well as that en

777
00:54:35.220 --> 00:54:39.260
closing into a single assembly. We also have, um,

778
00:54:41.040 --> 00:54:44.260
uh, examples of the,

779
00:54:45.960 --> 00:54:50.660
uh, templates for what we call splitting devices. Instead of,

780
00:54:50.920 --> 00:54:51.690
um,

781
00:54:51.690 --> 00:54:56.020
tapping devices like capacitors or overhead transformers.

782
00:54:56.290 --> 00:54:59.780
Splitting devices would be fuse inline fuses,

783
00:54:59.830 --> 00:55:04.820
where the template is also containing the equipment,

784
00:55:05.090 --> 00:55:10.060
meaning the three devices and they are all within

785
00:55:10.500 --> 00:55:11.620
a particular assembly,

786
00:55:12.480 --> 00:55:17.420
but also the way they are connected to the line ends is supported

787
00:55:17.760 --> 00:55:21.100
by the template in a single encapsulated object.

788
00:55:22.400 --> 00:55:23.940
Why are these templates and,

789
00:55:24.760 --> 00:55:28.300
and the way that they are installed or in the field important?

790
00:55:28.690 --> 00:55:33.090
Because they can hide all this behavioral information

791
00:55:33.840 --> 00:55:36.730
into a single object. For instance,

792
00:55:36.950 --> 00:55:41.010
we have pad mounted switch gear templates that encompass

793
00:55:41.340 --> 00:55:46.330
everything as the bus lines, the elbows, uh, some other,

794
00:55:46.790 --> 00:55:49.050
uh, type of switches, the pad,

795
00:55:49.670 --> 00:55:54.290
the encapsulating what I call the green box in the switch gear that you see on,

796
00:55:54.390 --> 00:55:56.610
uh, sitting on the pad on the street.

797
00:55:57.160 --> 00:56:01.810
Also a three phase pad mounted transformer where we can now model also

798
00:56:02.390 --> 00:56:06.650
the elbows that could be part or not in the

799
00:56:07.570 --> 00:56:12.370
structure. The fidelity of the business, uh,

800
00:56:12.370 --> 00:56:12.670
sorry,

801
00:56:12.670 --> 00:56:17.650
the fidelity of the model also should reflect

802
00:56:18.190 --> 00:56:21.250
the needs for your business functionality.

803
00:56:21.470 --> 00:56:26.080
Let me explain why is it important to have this level of

804
00:56:27.270 --> 00:56:28.103
detail?

805
00:56:28.460 --> 00:56:33.290
Let's consider an underground residential distribution open

806
00:56:33.360 --> 00:56:36.730
loop here in the upper part of the, uh,

807
00:56:36.790 --> 00:56:41.370
map representing that is being fed from the low, uh,

808
00:56:41.370 --> 00:56:46.210
lower left side by a backbone

809
00:56:46.680 --> 00:56:50.050
underground three phase, um, conductor.

810
00:56:50.430 --> 00:56:55.290
It comes to the switch gear and now it fits the neighborhood

811
00:56:56.030 --> 00:57:00.650
by a sequence of single phase transformers that

812
00:57:00.990 --> 00:57:05.570
are probably changing the faces. So we have an A phase B, phase C phase,

813
00:57:05.590 --> 00:57:09.410
and then another A phase B phase and C phase. It's just a simple example.

814
00:57:09.830 --> 00:57:12.370
And at the end there is an open, um,

815
00:57:12.920 --> 00:57:16.650
open loop because there is an open switch there probably, uh, for,

816
00:57:17.850 --> 00:57:21.590
uh, to establish the, the closure of the circuit.

817
00:57:22.090 --> 00:57:25.840
Now then if we in the utility network,

818
00:57:26.100 --> 00:57:30.840
we could face a trace by phase and if we were to

819
00:57:30.840 --> 00:57:34.760
trace this, uh, u r d on B phase,

820
00:57:35.060 --> 00:57:36.640
we would see that, well,

821
00:57:36.900 --> 00:57:41.800
the main trunk has B phase and it goes into the open loop

822
00:57:41.830 --> 00:57:46.440
here and it bypasses if we model correctly, the,

823
00:57:47.870 --> 00:57:49.250
uh, pan mount the transformer,

824
00:57:49.710 --> 00:57:54.330
it bypasses the A and C phase transformer,

825
00:57:54.870 --> 00:57:59.730
but it actually selects in the trace the B transformer because they are

826
00:57:59.730 --> 00:58:04.410
participating in the distribution of B phase power.

827
00:58:06.000 --> 00:58:10.570
What will happen in this level of detail if now the

828
00:58:11.630 --> 00:58:14.380
elbow that is feeding this, uh,

829
00:58:14.380 --> 00:58:18.660
particular B phase on the lower part of the open loop,

830
00:58:19.530 --> 00:58:24.510
uh, got blown or was part in order

831
00:58:24.690 --> 00:58:27.470
to, um, do some, uh,

832
00:58:27.470 --> 00:58:30.190
maintenance on the padman transformer.

833
00:58:30.530 --> 00:58:34.550
If we were to run the same B phase trace,

834
00:58:35.180 --> 00:58:39.750
then we would see how still bypassing the A and C single phase

835
00:58:39.750 --> 00:58:43.550
transformer is identifying this upper, uh,

836
00:58:43.670 --> 00:58:47.670
B transformer as, uh, providing, uh,

837
00:58:47.680 --> 00:58:50.350
power to the residents. And,

838
00:58:50.730 --> 00:58:55.610
but the last transformer is not participating

839
00:58:55.750 --> 00:58:59.930
in that trace because there's, uh, fuse, sorry,

840
00:59:01.250 --> 00:59:06.090
the fused elbow there has stopped the

841
00:59:06.090 --> 00:59:10.130
trace in the behavior of the network. So that's the important thing.

842
00:59:10.130 --> 00:59:13.210
What do you want to provide in your gis?

843
00:59:13.210 --> 00:59:16.130
What kind of capabilities you want to, um,

844
00:59:16.230 --> 00:59:20.530
be able to analyze is what is gonna determine

845
00:59:21.300 --> 00:59:24.480
the, how the level of fidelity, the,

846
00:59:24.780 --> 00:59:29.160
the complexity or or simplicity of your model representation.

847
00:59:29.780 --> 00:59:30.613
And finally,

848
00:59:30.620 --> 00:59:35.600
why So why is Esri uh,

849
00:59:35.600 --> 00:59:40.000
been working for several years on the utility network mainly

850
00:59:40.740 --> 00:59:45.520
to provide better performance and data integrity in your g I s

851
00:59:45.880 --> 00:59:46.700
solution?

852
00:59:46.700 --> 00:59:51.200
So we have the geometric network running quite well for 20 years,

853
00:59:51.620 --> 00:59:53.120
but now it's gonna be deprecated.

854
00:59:53.500 --> 00:59:58.160
We have noticed slow execution problems with broken network corrupted

855
00:59:58.230 --> 01:00:03.000
data. Um, we had to maintain circuits via,

856
01:00:03.580 --> 01:00:08.480
uh, mass app updates and that created some version reconciliation problems.

857
01:00:09.310 --> 01:00:10.060
Also,

858
01:00:10.060 --> 01:00:14.680
the databases had to be replicated if we wanted to use the same data

859
01:00:14.900 --> 01:00:19.280
in different, uh, applications now for the next 10 years.

860
01:00:19.620 --> 01:00:21.520
On the contrary, uh,

861
01:00:21.960 --> 01:00:26.880
ESRI is bringing a robust and reliable implementation of

862
01:00:27.040 --> 01:00:28.040
a directi graph,

863
01:00:28.040 --> 01:00:33.040
which is a utility network in which first you can localize and,

864
01:00:33.660 --> 01:00:36.680
and connect to the network all your assets,

865
01:00:36.950 --> 01:00:39.840
they are not related units anymore.

866
01:00:40.110 --> 01:00:44.840
They are actually participating in the conveyance of your u

867
01:00:45.140 --> 01:00:47.630
uh, commodity. The,

868
01:00:48.610 --> 01:00:53.070
the model comes with a fixed number of, uh, feature, uh, classes.

869
01:00:53.290 --> 01:00:57.950
So any interaction with your database requires less

870
01:00:58.060 --> 01:01:02.630
queries. There is topological association instead of geometric,

871
01:01:03.010 --> 01:01:07.910
uh, asso uh, relationships and they are done by indexing,

872
01:01:07.920 --> 01:01:08.950
which is, uh,

873
01:01:09.090 --> 01:01:13.550
far faster than analyzing geometric coincidence.

874
01:01:16.740 --> 01:01:17.800
The, um,

875
01:01:19.270 --> 01:01:23.690
the circuits are now managed by out-of-the-box DAAP network

876
01:01:24.210 --> 01:01:28.290
functionality. So you don't require, um, custom,

877
01:01:29.390 --> 01:01:33.290
uh, applications to maintain the the circuits.

878
01:01:34.310 --> 01:01:38.530
And another important thing is that is the same

879
01:01:40.140 --> 01:01:45.000
web raced and rest interface that you expose

880
01:01:45.540 --> 01:01:49.560
for one instance of your utility network can be consumed

881
01:01:50.430 --> 01:01:55.290
in different flavors by all the other client applications supporting

882
01:01:55.320 --> 01:01:56.970
your enterprise business.

883
01:01:57.830 --> 01:02:02.370
So now the G I S rests really as a unique

884
01:02:02.870 --> 01:02:07.610
implementation at the core of your, uh, enterprise,

885
01:02:08.190 --> 01:02:09.610
um, infrastructure.

886
01:02:11.420 --> 01:02:15.400
And of course talking about data integrity. The utility network,

887
01:02:15.540 --> 01:02:16.560
as I have mentioned,

888
01:02:16.610 --> 01:02:20.880
comes with a lot of attributing association rules that are configured to

889
01:02:21.550 --> 01:02:26.040
give you the confidence that the quality of your data is maintained.

890
01:02:27.410 --> 01:02:32.150
So we like to call the GIS of your future the utility network

891
01:02:32.290 --> 01:02:37.070
as a GIS of your future because it's a better

892
01:02:37.560 --> 01:02:41.600
enterprise, uh, is a better,

893
01:02:42.060 --> 01:02:46.960
it represents a better integration within your enterprise systems because the

894
01:02:46.980 --> 01:02:50.920
assets and the association are now part of the network.

895
01:02:52.070 --> 01:02:56.770
It allows you for a higher fidelity that then can be fed

896
01:02:57.590 --> 01:03:02.050
to other systems that require the higher fidelity like O M S A M,

897
01:03:02.990 --> 01:03:07.850
sca SCADA in the substation internals and it provides out

898
01:03:07.850 --> 01:03:12.730
of the box advanced analytics. Uh, you can, uh,

899
01:03:13.020 --> 01:03:17.650
trace by phase, you have vault, uh, phase propagation nowadays.

900
01:03:17.830 --> 01:03:22.810
You will have a voltage propagation, you have pressure propagation, uh,

901
01:03:22.830 --> 01:03:26.730
you can model electric face swapping, uh,

902
01:03:27.430 --> 01:03:31.610
and you can now even implement not out of the box,

903
01:03:31.710 --> 01:03:36.250
but you can now implement functionality such as load estimation

904
01:03:37.030 --> 01:03:37.670
and,

905
01:03:37.670 --> 01:03:41.650
but you can also out of the box count the number of poles and customers that you

906
01:03:41.650 --> 01:03:45.970
have down a particular location of your feeder to to the last branch.

907
01:03:47.320 --> 01:03:48.153
So in summary,

908
01:03:49.160 --> 01:03:54.100
the utility network is SSRI's new implementation of the

909
01:03:54.100 --> 01:03:55.060
directive graph.

910
01:03:55.440 --> 01:04:00.140
It has the capability of offering a higher fidelity model

911
01:04:01.050 --> 01:04:05.580
that con uh, that represents in a,

912
01:04:06.720 --> 01:04:08.300
uh, consolidating manner,

913
01:04:08.960 --> 01:04:12.980
the contents of the equipment and the behavior of the equipment.

914
01:04:13.320 --> 01:04:16.820
It facilitates integration with other enterprise system,

915
01:04:16.920 --> 01:04:19.420
not just because of the level of fidelity,

916
01:04:19.640 --> 01:04:23.340
but also because of the exposure through web services.

917
01:04:24.000 --> 01:04:28.660
It has a lot of built in rules that ensure that the validation and the

918
01:04:28.810 --> 01:04:30.260
integrity of your data,

919
01:04:31.200 --> 01:04:36.060
it has a lot of built-in functionality that ensures

920
01:04:36.060 --> 01:04:40.820
that the behavior is accurate and it accounts within

921
01:04:41.040 --> 01:04:43.420
the same utility network,

922
01:04:43.760 --> 01:04:48.460
not only for the equipment but also for the infrastructure that supports the

923
01:04:48.620 --> 01:04:52.950
equipment. It coexist with your enterprise.

924
01:04:53.230 --> 01:04:57.990
G i s The utility network is not there to maintain your land

925
01:04:57.990 --> 01:05:01.030
base or your customer information if you don't want to,

926
01:05:01.370 --> 01:05:06.050
is there to maintain that part of the model that actually

927
01:05:06.050 --> 01:05:10.970
implements a direct graph for traceable analytics.

928
01:05:12.730 --> 01:05:17.320
And the fact that it is exposed through web services means it can be

929
01:05:17.400 --> 01:05:20.200
consumed the same instance by multiple apps.

930
01:05:20.780 --> 01:05:24.040
And that way you don't have to do all this, uh,

931
01:05:24.150 --> 01:05:27.200
replication of databases for different, uh,

932
01:05:28.400 --> 01:05:29.560
business uh, values.

933
01:05:30.300 --> 01:05:34.840
So we like to call the utility network the g i s of the future.

934
01:05:35.700 --> 01:05:36.520
And with this,

935
01:05:36.520 --> 01:05:41.040
I have completed the presentation and thank you for listening to this

936
01:05:41.040 --> 01:05:45.160
presentation. I'm looking forward to answering any questions you may have.

937
01:05:46.340 --> 01:05:51.120
All right, thanks Joaquin. The first one is,

938
01:05:51.540 --> 01:05:55.720
why is the attachment association important in the utility network?

939
01:05:57.110 --> 01:05:58.850
The way I look at it is, um,

940
01:05:59.790 --> 01:06:03.290
in the past we were not able to,

941
01:06:05.210 --> 01:06:08.990
out of the box in the S3 R G I S 10,

942
01:06:10.180 --> 01:06:13.720
uh, to ten six, um, prior, uh,

943
01:06:13.770 --> 01:06:17.240
capability to say, okay, given this for instance,

944
01:06:17.640 --> 01:06:20.920
electric feeder or given this, um, pressure system,

945
01:06:21.750 --> 01:06:26.280
give me also all the other components of the G I s

946
01:06:26.850 --> 01:06:31.080
which are actually not participating in the network such as

947
01:06:31.520 --> 01:06:36.040
manholes, vaults, uh, poles, things like that, and,

948
01:06:36.180 --> 01:06:40.640
and provide them to me automatically so that I can have account or I can do

949
01:06:40.880 --> 01:06:43.000
whatever kind of analytics. Uh,

950
01:06:43.380 --> 01:06:48.000
so how is Esri resolving that gap in the functionality?

951
01:06:48.590 --> 01:06:53.520
Because we all know that even though the

952
01:06:53.720 --> 01:06:58.560
structure that sent participate in the conveyance of the commodity,

953
01:06:59.220 --> 01:07:04.010
but we do know that is fundamental to, to the, uh,

954
01:07:05.040 --> 01:07:07.100
to the working of the utility.

955
01:07:07.680 --> 01:07:11.940
So the gap is now fixed by having this attachment

956
01:07:12.010 --> 01:07:16.540
association. If a particular part of the equipment or lines or,

957
01:07:16.600 --> 01:07:21.220
or part of the domain is attached to a

958
01:07:21.270 --> 01:07:23.740
given structure feature,

959
01:07:24.530 --> 01:07:29.140
then the trace will actually discover the feature and

960
01:07:29.160 --> 01:07:33.060
return it as part of the selection set. So in that sense,

961
01:07:33.060 --> 01:07:38.060
that's why I say structures now do participate in the network,

962
01:07:38.820 --> 01:07:43.500
although they participate in an indirect way and also be

963
01:07:44.220 --> 01:07:45.053
cautious.

964
01:07:45.340 --> 01:07:49.940
A particular structure will participate and be discoverable in your network

965
01:07:50.600 --> 01:07:53.980
if is, um, uh,

966
01:07:54.420 --> 01:07:56.860
attached it has an attachment association.

967
01:07:58.210 --> 01:08:01.060
Alright, thank you. Next one up.

968
01:08:01.440 --> 01:08:05.860
Do you differentiate between the template of an overhead versus pad mounted

969
01:08:06.100 --> 01:08:06.933
transformer?

970
01:08:09.170 --> 01:08:10.100
Well, there is a,

971
01:08:11.400 --> 01:08:15.680
in the geometric network both, uh,

972
01:08:16.160 --> 01:08:18.570
overhead and underground, uh,

973
01:08:18.650 --> 01:08:23.410
transformers would actually be represented as a

974
01:08:23.540 --> 01:08:28.050
point feature class and actually it will not be representing the

975
01:08:28.050 --> 01:08:28.930
transformer itself.

976
01:08:28.990 --> 01:08:33.210
It will be representing the transformer bank and then a relationship to the

977
01:08:33.410 --> 01:08:35.970
transformer units. So in that sense,

978
01:08:36.720 --> 01:08:41.220
both literally are just points snapped

979
01:08:41.600 --> 01:08:43.850
to the, uh,

980
01:08:43.910 --> 01:08:48.610
ver to a vertex of the line overhead or underground with the

981
01:08:48.610 --> 01:08:53.180
utility network. And if you, uh,

982
01:08:53.540 --> 01:08:56.220
business requires a higher level of detail,

983
01:08:56.920 --> 01:09:01.220
now you can represent for an overhead, uh,

984
01:09:01.430 --> 01:09:06.340
three phase transformer. You can represent it with a template that actually,

985
01:09:07.630 --> 01:09:12.340
uh, behaves like in the real world where the individual

986
01:09:12.690 --> 01:09:17.460
devices are tapping through some kind of, uh, jumper,

987
01:09:18.400 --> 01:09:23.000
the, the lines. And in that sense they are not splitting the line.

988
01:09:23.000 --> 01:09:25.800
They are just clumping and,

989
01:09:25.940 --> 01:09:30.630
and tapping the line while the underground transformer

990
01:09:30.930 --> 01:09:35.550
is usually splitting the line and connected between

991
01:09:36.050 --> 01:09:36.883
elbows.

992
01:09:37.490 --> 01:09:42.430
So now really you have the option with a utility network or have two different

993
01:09:42.430 --> 01:09:46.710
representation for something that in the past was just a point

994
01:09:47.420 --> 01:09:48.790
snapped in a vertex.

995
01:09:49.530 --> 01:09:51.590
All right, one more that I see here.

996
01:09:51.610 --> 01:09:54.830
Is it necessary to model the utility network in high fidelity?

997
01:09:56.170 --> 01:10:01.030
No, it is not. Uh, there are several different,

998
01:10:01.690 --> 01:10:03.390
uh, quote unquote standard.

999
01:10:03.720 --> 01:10:07.750
There are three different standard models for the utility network.

1000
01:10:08.610 --> 01:10:12.710
Uh, the most, uh, fundamental one is, uh,

1001
01:10:13.600 --> 01:10:18.390
one-to-one representation of the current geometric network into the

1002
01:10:18.390 --> 01:10:22.550
utility network. Why? Because the utility network,

1003
01:10:23.900 --> 01:10:27.270
uh, also, uh,

1004
01:10:28.730 --> 01:10:32.730
includes geometric connectivity in the,

1005
01:10:33.550 --> 01:10:37.490
in the implementation. So if you have two things snapped to each other,

1006
01:10:38.230 --> 01:10:43.160
you can have connectivity there with the appropriate rules and

1007
01:10:44.530 --> 01:10:48.830
you could then represent your current geometric network,

1008
01:10:49.740 --> 01:10:53.950
what I call verbatim into the utility network. Now, then

1009
01:10:55.470 --> 01:10:56.890
why would you do that?

1010
01:10:56.950 --> 01:11:01.810
If you're gonna go through the process of upgrading or move into the utility

1011
01:11:01.810 --> 01:11:03.010
network, uh,

1012
01:11:03.350 --> 01:11:08.170
and not take advantage of all the functionality that would, uh,

1013
01:11:08.310 --> 01:11:12.770
uh, hire, whether it's the basic or the advanced, uh,

1014
01:11:12.840 --> 01:11:17.280
modeling would provide you. So that's where, no,

1015
01:11:17.300 --> 01:11:18.840
you don't need the complexity,

1016
01:11:19.420 --> 01:11:24.200
but your business processes will dictate what level of complexity

1017
01:11:25.100 --> 01:11:29.960
you want or higher fidelity do you want to introduce in your model so

1018
01:11:29.960 --> 01:11:34.760
that you can now respond to some functionality that you may not have been

1019
01:11:34.760 --> 01:11:37.120
able to do, at least out of the box.

1020
01:11:39.600 --> 01:11:41.860
All right. It looks like we have a, we have a lot of questions and, and,

1021
01:11:42.000 --> 01:11:44.700
and just as a heads up, we may not get to all these,

1022
01:11:44.720 --> 01:11:47.820
so if you've asked the questions, we don't get to it, you'll likely see it as a,

1023
01:11:47.860 --> 01:11:49.580
a future blog post. Um,

1024
01:11:49.600 --> 01:11:52.980
but Carrie also is on the line and I think she has a few more.

1025
01:11:54.120 --> 01:11:59.020
Uh, yeah. So we have, um, a few here that I I'd like you to touch on. One is,

1026
01:11:59.250 --> 01:12:04.100
will gas distribution and transmission be two separate domains or

1027
01:12:04.190 --> 01:12:05.023
tiers?

1028
01:12:05.290 --> 01:12:09.660
Well, the ma uh, the answer depends on how you want to model.

1029
01:12:11.020 --> 01:12:15.180
Actually, before we go, and I'm sorry Keith to take, uh, one more minute.

1030
01:12:15.920 --> 01:12:16.780
The fundamental

1031
01:12:18.390 --> 01:12:23.350
property of the utility network is that it is extremely

1032
01:12:23.650 --> 01:12:28.030
simple because in order to be able to

1033
01:12:28.430 --> 01:12:33.240
represent any domain, whether it's electric, gas,

1034
01:12:33.690 --> 01:12:37.640
water, and at any level of tiering,

1035
01:12:38.060 --> 01:12:39.880
the utility network itself,

1036
01:12:40.460 --> 01:12:44.560
the core is extremely simple points,

1037
01:12:44.890 --> 01:12:49.840
lines and polygons participating, uh, in, uh,

1038
01:12:50.030 --> 01:12:54.520
association. So what I mean with that is that there,

1039
01:12:54.940 --> 01:12:59.400
the choice of what you include in the same domain or not

1040
01:13:00.460 --> 01:13:05.400
is based on your final, uh, business needs. So,

1041
01:13:05.700 --> 01:13:10.110
but also we need to understand, for instance, if the,

1042
01:13:10.330 --> 01:13:14.310
the tracing, uh, at least in in version two,

1043
01:13:14.310 --> 01:13:19.210
four and two five right now cannot go from one um,

1044
01:13:19.880 --> 01:13:23.330
tier, uh, uh, from from one domain to the other.

1045
01:13:23.870 --> 01:13:28.170
But if you want to trace from a transmission to a distribution,

1046
01:13:28.600 --> 01:13:33.410
then you need to put 'em in the same domain in future versions. They may even,

1047
01:13:33.830 --> 01:13:38.810
uh, disassociate the domains and provide with a capability to trace

1048
01:13:38.810 --> 01:13:42.690
from one to the other. And it is functionality like that.

1049
01:13:42.710 --> 01:13:45.450
Is it behavior like that? What answer,

1050
01:13:45.710 --> 01:13:48.730
how do we model my com? Um,

1051
01:13:48.830 --> 01:13:50.890
my utility network right now?

1052
01:13:51.680 --> 01:13:55.290
Okay. Um, Joaquin, I have what someone's asking.

1053
01:13:55.440 --> 01:13:58.090
What is the U U D P M

1054
01:13:58.890 --> 01:13:59.170
U P

1055
01:13:59.170 --> 01:14:02.610
D M? Okay, I believe it's called U P D M, uh,

1056
01:14:03.050 --> 01:14:05.890
u utility and pipeline data model.

1057
01:14:06.110 --> 01:14:10.290
And it's a standard or pseudo standard that, uh,

1058
01:14:10.540 --> 01:14:15.400
tries to represent or tries to consolidate models

1059
01:14:15.780 --> 01:14:17.440
for the gas industry,

1060
01:14:17.750 --> 01:14:22.520
both at the pipeline of transmission as well as the

1061
01:14:22.920 --> 01:14:23.760
distribution level.

1062
01:14:24.780 --> 01:14:28.310
Okay. Um, this one might be little bit, here we go.

1063
01:14:28.380 --> 01:14:32.870
What are the options for modeling multi-phase

1064
01:14:33.080 --> 01:14:37.870
conductors? This is multi, uh, multi-question question here. Um,

1065
01:14:38.230 --> 01:14:42.990
multiple lines with phasing attribute, single lines with multiple related,

1066
01:14:43.350 --> 01:14:45.550
a associated phase records, et cetera.

1067
01:14:46.420 --> 01:14:50.870
Yeah, that's a really good one. Um, in the sense that, again,

1068
01:14:51.690 --> 01:14:56.390
the o the opportunity to make different modeling choices

1069
01:14:57.530 --> 01:15:02.470
is now, um, a greater advantage than before.

1070
01:15:03.450 --> 01:15:07.690
In general, the electrical, for instance, yeah,

1071
01:15:07.750 --> 01:15:12.530
the electric line defi defines whether it is single two

1072
01:15:12.550 --> 01:15:17.290
or three phase simply by differentiating the asset

1073
01:15:17.290 --> 01:15:22.090
type. And then, so in that sense, a line,

1074
01:15:22.270 --> 01:15:24.490
uh, uh, no matter how many phases you have,

1075
01:15:24.550 --> 01:15:28.770
the the com model represents the line as a single feature.

1076
01:15:29.980 --> 01:15:34.000
Now then what about the properties, uh,

1077
01:15:34.790 --> 01:15:39.120
that are dependent on the faces such as the conductor size,

1078
01:15:39.150 --> 01:15:41.840
conductor material, the number of conductors per face,

1079
01:15:42.500 --> 01:15:45.560
all those can be now model in different ways.

1080
01:15:46.340 --> 01:15:50.520
One way could be to extend your line feature class to have,

1081
01:15:50.610 --> 01:15:54.600
let's say 12 more fields. Three if,

1082
01:15:54.600 --> 01:15:57.280
if those are the three fields that you want to, uh,

1083
01:15:57.280 --> 01:15:59.760
monitor three fields for a,

1084
01:15:59.760 --> 01:16:03.920
three fields for B and C and then maybe for neutral.

1085
01:16:04.470 --> 01:16:08.320
Another way is by establishing a relationship

1086
01:16:09.030 --> 01:16:13.160
exactly like the one you have right now in the, um,

1087
01:16:13.270 --> 01:16:17.130
between the primary and underground

1088
01:16:18.000 --> 01:16:19.650
with the conductor info table.

1089
01:16:20.110 --> 01:16:24.250
So you will have that the utility network still supports,

1090
01:16:25.030 --> 01:16:28.690
um, relationships with object classes.

1091
01:16:29.280 --> 01:16:33.010
It's just that if you can avoid relationships, the performance is, uh,

1092
01:16:33.030 --> 01:16:37.930
is improved. So, uh, that's another model to do it. Definitely.

1093
01:16:38.360 --> 01:16:43.240
Also you can represent each line individually. There is no,

1094
01:16:43.380 --> 01:16:46.360
no nothing stopping you for that. And as a matter of fact,

1095
01:16:46.420 --> 01:16:51.160
you may want to represent in some underground, uh,

1096
01:16:51.520 --> 01:16:56.370
scenarios that out of a particular switch gear that was

1097
01:16:56.470 --> 01:17:01.330
fed by three phase, single line, now you have the need to say, okay, well,

1098
01:17:01.750 --> 01:17:02.060
uh,

1099
01:17:02.060 --> 01:17:06.930
phase C is going northeast while phase A and B are

1100
01:17:06.930 --> 01:17:07.890
going southwest,

1101
01:17:08.670 --> 01:17:13.200
and they are gonna come back again to the switch gear and another, um, later on.

1102
01:17:13.540 --> 01:17:15.520
And in that case, you are going to,

1103
01:17:15.820 --> 01:17:20.080
to have to represent your lines as single phase lines,

1104
01:17:20.780 --> 01:17:22.320
but you have now really the,

1105
01:17:22.380 --> 01:17:27.240
the richness to decide on the model based on the functionality, the,

1106
01:17:27.540 --> 01:17:29.920
uh, and the behavior that you want to represent.

1107
01:17:30.890 --> 01:17:34.760
Keith, do we have time for one more? Yeah, I think we got more time. Go for it.

1108
01:17:34.760 --> 01:17:38.960
Keep going. Um, we'll see. I'll start with this one. How,

1109
01:17:39.020 --> 01:17:41.320
how would you one, okay, let me say this again.

1110
01:17:41.980 --> 01:17:46.680
How would one model a three line system in, in the un?

1111
01:17:46.780 --> 01:17:47.613
Is it a terminal?

1112
01:17:48.180 --> 01:17:52.240
Is it by a terminal in connections corresponding to each phase on a single

1113
01:17:52.970 --> 01:17:55.200
three phase conductor representation?

1114
01:17:57.430 --> 01:18:02.050
Uh, no, this is related a little bit to the previous question. Uh, um,

1115
01:18:02.110 --> 01:18:06.850
but before that, terminals do not determine the,

1116
01:18:08.680 --> 01:18:09.970
well, lemme put it this way,

1117
01:18:10.390 --> 01:18:15.090
the way I interpret the question is if I have a three phase or

1118
01:18:15.230 --> 01:18:19.090
two phase, actually three phase and then a lateral of one phase,

1119
01:18:19.430 --> 01:18:24.050
how do I establish that connectivity? Do I need terminals? No, in that sense,

1120
01:18:24.320 --> 01:18:27.210
what you are doing is you are using tabs,

1121
01:18:27.660 --> 01:18:32.650
these joint junctions that you can manipulate

1122
01:18:33.230 --> 01:18:38.130
the face and indicate to the tracer to the out of the box trace

1123
01:18:38.130 --> 01:18:38.963
capability.

1124
01:18:39.350 --> 01:18:43.610
As you are going down this three phase line and you get to this particular,

1125
01:18:44.230 --> 01:18:48.890
um, junction in a vertex, what do you want to do?

1126
01:18:49.630 --> 01:18:50.930
Uh, well if it's,

1127
01:18:50.950 --> 01:18:54.930
if I'm tracing by phase A and that junction

1128
01:18:55.830 --> 01:18:59.490
is a phase B because A lateral is B, I'm just gonna bypass it,

1129
01:18:59.490 --> 01:19:04.210
otherwise I'm gonna also turn to the right and trace downstream.

1130
01:19:04.710 --> 01:19:08.330
So terminals are only, uh,

1131
01:19:08.500 --> 01:19:12.210
there to provide different, um,

1132
01:19:13.410 --> 01:19:15.850
tracing paths, conditions,

1133
01:19:16.510 --> 01:19:21.170
but they are not there to control in,

1134
01:19:21.430 --> 01:19:26.290
in a facing way if I, if that's what I'm understanding the,

1135
01:19:26.430 --> 01:19:29.530
the way the tracing capabilities behave.

1136
01:19:30.080 --> 01:19:31.010
Okay, thank you for that.

1137
01:19:32.480 --> 01:19:37.290
Some utilities use GE small world, which has their own container views,

1138
01:19:37.890 --> 01:19:42.280
internal worlds and directional and other tracing capabilities.

1139
01:19:42.430 --> 01:19:46.120
What advantages does the UN have over small world?

1140
01:19:47.130 --> 01:19:50.300
Yeah, I saw this question in the very beginning. Um,

1141
01:19:51.060 --> 01:19:55.460
I know properties of the small world, but I have never worked with small world.

1142
01:19:55.560 --> 01:19:57.140
I'm gonna say that upfront.

1143
01:19:57.140 --> 01:20:01.500
So I'm not in a position to qualitatively compare the two products

1144
01:20:01.810 --> 01:20:05.180
regarding those two, uh, concepts. What, uh,

1145
01:20:05.290 --> 01:20:09.960
what I can say is that the assembly is now a

1146
01:20:10.270 --> 01:20:12.760
mechanism in the utility network,

1147
01:20:13.060 --> 01:20:17.960
mainly for cardiographic representation of your data that hides

1148
01:20:18.220 --> 01:20:19.800
all the, um,

1149
01:20:20.150 --> 01:20:24.640
details very similar in that sense to the internal views in,

1150
01:20:25.100 --> 01:20:29.680
uh, the small world. And in that sense, it participates by,

1151
01:20:30.500 --> 01:20:35.480
uh, association containing association in the result of your trace analytics

1152
01:20:36.380 --> 01:20:40.840
on the other hand trace. Yeah. Uh, their software, of course,

1153
01:20:40.870 --> 01:20:43.600
that provide tracing, and again, I cannot compare,

1154
01:20:43.700 --> 01:20:48.640
but I know that the utility network out of the box allows

1155
01:20:48.900 --> 01:20:53.640
you now to trace and propagate values

1156
01:20:54.260 --> 01:20:57.080
in your network. Like in the electric field,

1157
01:20:57.080 --> 01:21:00.480
which is where I feel more comfortable, you can trace by face,

1158
01:21:00.980 --> 01:21:05.680
you can actually also propagate the face values to devices

1159
01:21:06.060 --> 01:21:07.200
and, and lines.

1160
01:21:07.980 --> 01:21:12.600
And you can configure out of the box also the behavior of your trace

1161
01:21:13.220 --> 01:21:16.520
by setting up what barrier conditions you have,

1162
01:21:16.520 --> 01:21:20.600
which are based on network properties or network attributes.

1163
01:21:20.600 --> 01:21:25.240
So you can truly, uh, out of the box say, Hey, from, from down here,

1164
01:21:25.290 --> 01:21:29.160
trace upstream to all my, uh, devices,

1165
01:21:29.450 --> 01:21:34.360
which have been configured with a load breaking, uh, attribute.

1166
01:21:35.020 --> 01:21:39.800
And then the results of the trace will return accordingly.

1167
01:21:40.340 --> 01:21:41.720
And that is all out of the box.

1168
01:21:42.580 --> 01:21:46.840
Uh, one final question we have time for here and um, this one is,

1169
01:21:47.020 --> 01:21:50.200
how is the neutral model in the un?

1170
01:21:50.770 --> 01:21:54.760
Again, depending on your needs, uh, I've seen models, uh,

1171
01:21:54.770 --> 01:21:58.240
where the neutral is actually, uh,

1172
01:21:58.520 --> 01:22:03.400
single line that is drawn offset from

1173
01:22:03.400 --> 01:22:04.440
the, uh,

1174
01:22:04.510 --> 01:22:09.160
main line and it just contains the properties of the

1175
01:22:09.630 --> 01:22:14.280
size material. And in that case usually is just a single, uh,

1176
01:22:14.390 --> 01:22:19.200
wire and it just goes along and is used in that particular

1177
01:22:19.200 --> 01:22:23.840
model is used so that you can explicitly connect an

1178
01:22:23.880 --> 01:22:28.130
arrester, for instance, with terminal configuration,

1179
01:22:28.130 --> 01:22:29.010
which is not common,

1180
01:22:29.430 --> 01:22:33.010
but you could do it with terminal configuration where one terminal is connecting

1181
01:22:33.010 --> 01:22:37.210
to the, uh, phase or, or the energized line,

1182
01:22:37.510 --> 01:22:41.090
the other one to the neutral, which is also energized, but it's,

1183
01:22:41.090 --> 01:22:44.850
it is a neutral phase. So, um, that will be a model.

1184
01:22:45.320 --> 01:22:49.330
Most of the models will continue using the, uh,

1185
01:22:49.630 --> 01:22:54.490
the representation I mentioned before, which is using a, the data,

1186
01:22:55.390 --> 01:22:56.223
um,

1187
01:22:56.390 --> 01:23:01.370
the wire data table that the S3 solutions team provides

1188
01:23:01.390 --> 01:23:06.040
in the reference model, which is a table that is, um,

1189
01:23:06.640 --> 01:23:11.320
establishing a relationship with the line feature class.

1190
01:23:11.820 --> 01:23:13.240
So that a given line,

1191
01:23:13.540 --> 01:23:18.040
you will have a record associated to that feature that represents the neutral

1192
01:23:18.100 --> 01:23:21.960
for that. And then you don't have it in your map to be represented.

1193
01:23:22.620 --> 01:23:25.880
But again, it depends on your needs in that sense.

1194
01:23:26.540 --> 01:23:31.040
The static of our transmission line would be a similar example in that

1195
01:23:31.040 --> 01:23:35.440
Sense. Alright. Um, Joaquin, we have, uh, just everyone knows we have, uh,

1196
01:23:35.960 --> 01:23:37.560
a bunch of questions still left, but there are,

1197
01:23:37.560 --> 01:23:41.520
there are pretty broad questions, uh, that we don't have time. What,

1198
01:23:41.520 --> 01:23:45.200
what we're gonna do though is if you've sent in a question, uh,

1199
01:23:45.420 --> 01:23:49.080
expect that to be a blog post. Again, some of these are, are, are pretty wide,

1200
01:23:49.190 --> 01:23:51.240
wide range of questions. Um,

1201
01:23:51.650 --> 01:23:54.600
Keith, if I may actually, and because I,

1202
01:23:54.840 --> 01:23:59.840
I said in the beginning that my expertise is in the electric, um, modeling,

1203
01:24:00.380 --> 01:24:05.360
but I've seen several questions about the gas and I just wanted to

1204
01:24:05.380 --> 01:24:09.760
answer in a general sense. The utility network, again,

1205
01:24:10.020 --> 01:24:14.920
is commodity agnostic and it has been designed from the core

1206
01:24:15.100 --> 01:24:19.200
and it's supported to provide a model for any,

1207
01:24:20.680 --> 01:24:24.820
uh, directing graph, any commodity that needs that directing graph.

1208
01:24:25.320 --> 01:24:26.460
So yes,

1209
01:24:26.680 --> 01:24:31.620
the utility network is actually being implemented and S S

1210
01:24:31.660 --> 01:24:35.180
P is actually, uh, collaborating in several projects, uh,

1211
01:24:35.180 --> 01:24:39.780
implementing not only the gas pipeline

1212
01:24:40.360 --> 01:24:45.260
and distribution, uh, models, and actually they are using,

1213
01:24:45.920 --> 01:24:48.860
uh, the U P D M model for that.

1214
01:24:49.320 --> 01:24:54.220
And Esri has had a lot of input into how that model works.

1215
01:24:55.010 --> 01:24:59.270
No, thanks for that note. Uh, that helps. Alright, everybody, uh,

1216
01:24:59.460 --> 01:25:03.430
just wanted let you know, uh, please go out to ssp illuminate.com. Uh,

1217
01:25:03.490 --> 01:25:08.190
our next illuminate webinar series session is in two weeks. And this is our,

1218
01:25:08.190 --> 01:25:11.630
our, our mobile session. It's integrating MIMS Mobile with enterprise systems,

1219
01:25:12.210 --> 01:25:12.430
uh,

1220
01:25:12.430 --> 01:25:17.150
and that's with Darris friend from G R U Gainesville Regional Utilities and uh,

1221
01:25:17.680 --> 01:25:19.590
Maris Rocher. Um,

1222
01:25:20.600 --> 01:25:23.860
please go to the website register and we'll see you in two weeks.

1223
01:25:23.860 --> 01:25:27.860
Thanks for making the time, uh, to join us today and uh, we'll see you then.

1224
01:25:27.860 --> 01:25:28.693
Thanks a lot.

1225
01:25:28.710 --> 01:25:29.740
Thank you everybody.