Supporting Utility Network Phase Propagation with Pro Templates | SSP iLLUMINATE 2020

2
00:00:04.110 --> 00:00:05.250
My name is Keith Freeman.

3
00:00:05.310 --> 00:00:07.970
I'm the objective of marketing here at SSP Innovations,

4
00:00:07.970 --> 00:00:12.530
and today's webinar is titled On Phase Propagation Utility Network

5
00:00:13.090 --> 00:00:17.430
Electric Phase Management. Your speaker today will be Dr.

6
00:00:17.500 --> 00:00:18.350
Joaquin Madrid.

7
00:00:18.460 --> 00:00:23.390
Joaquin is a senior solutions architect at s p with over 20 years of experience

8
00:00:23.390 --> 00:00:25.070
designing, developing,

9
00:00:25.090 --> 00:00:28.350
and deploying a wide range of GI solutions for the utility industry.

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

11
00:00:32.870 --> 00:00:36.750
distribution network and the implementation within fully integrated enterprise

12
00:00:36.850 --> 00:00:37.683
GI solutions.

13
00:00:38.160 --> 00:00:41.710
While Key will be answering questions at the end of his presentation,

14
00:00:41.850 --> 00:00:45.870
so please enter your questions along the way in the go-to meeting panel.

15
00:00:46.420 --> 00:00:47.110
Finally,

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

17
00:00:51.420 --> 00:00:52.510
Joaquin, whenever you're ready.

18
00:00:55.200 --> 00:00:56.033
Thank you Keith.

19
00:00:56.570 --> 00:01:01.070
And thank you very Ali for joining this Illuminate session

20
00:01:01.690 --> 00:01:06.510
in which we are going to discuss the details of the utility network face

21
00:01:06.540 --> 00:01:10.870
propagation. And we are gonna do that by answering three main questions.

22
00:01:11.460 --> 00:01:15.230
What or is the utility network face propagation?

23
00:01:15.450 --> 00:01:19.190
How does it work and why is it important for you?

24
00:01:20.470 --> 00:01:24.870
I hope that this is a simple and straightforward explanation and I will

25
00:01:24.870 --> 00:01:27.830
compliment with some demonstration at the end.

26
00:01:28.250 --> 00:01:31.070
We will have some, uh,

27
00:01:31.390 --> 00:01:34.110
a session of questions and answer.

28
00:01:35.850 --> 00:01:36.870
So let's start.

29
00:01:38.330 --> 00:01:43.110
The contents of this presentation will be based on the what in which

30
00:01:43.360 --> 00:01:47.350
we'll discuss the essential concepts of the phase propagation.

31
00:01:47.660 --> 00:01:50.310
What is a u utility network propagator,

32
00:01:50.780 --> 00:01:53.390
what does a utility network propagator do?

33
00:01:54.250 --> 00:01:58.950
And these two very abstract concepts will be illustrated

34
00:01:59.130 --> 00:02:01.420
by an example. How,

35
00:02:03.280 --> 00:02:08.100
how is the place where we are gonna describe the configuration and the behavior

36
00:02:08.600 --> 00:02:11.660
of the face propagation in the utility network?

37
00:02:11.880 --> 00:02:16.060
I'm gonna give you a recipe of the ingredients and how to mix them so that we

38
00:02:16.160 --> 00:02:20.740
can propagate and I'm gonna guide you through a step-by-step behavioral

39
00:02:20.930 --> 00:02:22.980
demonstration. Also,

40
00:02:23.190 --> 00:02:27.900
we'll discuss how SSP is creating templates that are

41
00:02:28.900 --> 00:02:33.780
modeling equipment at a fidelity level that allows for this

42
00:02:33.940 --> 00:02:35.900
advanced functionality to work.

43
00:02:37.210 --> 00:02:42.100
When we ask a question why the face propagation will focus

44
00:02:42.280 --> 00:02:47.060
on the business value in the case, we'll talk about a couple of, uh, use cases.

45
00:02:47.710 --> 00:02:52.460
We'll consider these two face propagation as part of the data validation

46
00:02:52.930 --> 00:02:57.780
arsenal that you have is an out of the box functionality, uh,

47
00:02:57.810 --> 00:02:59.240
tool. So, uh,

48
00:02:59.340 --> 00:03:04.000
no need for customizations and then any other comments by the end

49
00:03:04.140 --> 00:03:08.880
of the conversation. But before we go anywhere,

50
00:03:09.020 --> 00:03:13.320
let me remind you that the utility network is SREs,

51
00:03:14.140 --> 00:03:18.680
uh, current implementation of a

52
00:03:18.840 --> 00:03:23.240
directed graph within a gis. So at the end,

53
00:03:23.240 --> 00:03:27.000
what we are dealing is with a bunch of vertices and edges,

54
00:03:27.110 --> 00:03:31.840
they are interconnected in some fashion and they have direction ability in those

55
00:03:31.890 --> 00:03:32.700
edges.

56
00:03:32.700 --> 00:03:37.680
So we can have a full description of this graph knowing the

57
00:03:37.720 --> 00:03:42.600
connectivity among the elements and using some directional tracing.

58
00:03:42.740 --> 00:03:44.440
And why is tracing so important?

59
00:03:44.470 --> 00:03:49.240
Because it gives us the ability to obtain information about your network

60
00:03:50.030 --> 00:03:53.520
with a father. And a let's start with the what section.

61
00:03:54.100 --> 00:03:57.160
So the essential concepts of the, uh,

62
00:03:57.160 --> 00:04:01.680
phase propagation in particular of any attribute propagation are already

63
00:04:02.040 --> 00:04:06.320
documented in the, um, website from esri.

64
00:04:06.860 --> 00:04:11.000
And it says that it is an advanced utility network functionality that triggers

65
00:04:11.590 --> 00:04:15.400
when you either run the update subnetwork,

66
00:04:15.500 --> 00:04:20.080
the export Subnetwork or trace Subnetwork. So as you can see,

67
00:04:20.080 --> 00:04:25.080
this is a functionality that is intrinsically related

68
00:04:25.340 --> 00:04:30.120
to downstream traversals from the circuit sources of from

69
00:04:30.140 --> 00:04:33.840
the subnetwork controllers. Also,

70
00:04:34.860 --> 00:04:37.800
the documentation tells you what propagators do.

71
00:04:38.430 --> 00:04:43.360
They do derive values from fields that have

72
00:04:43.360 --> 00:04:46.200
some specific network attribute assigned to them,

73
00:04:46.860 --> 00:04:51.840
and they apply functions with operators so that the result

74
00:04:52.270 --> 00:04:56.200
derived from this operation is then set into a target field.

75
00:04:57.420 --> 00:04:59.000
So in that sense,

76
00:04:59.060 --> 00:05:03.960
we can see that the fields and the values participating in face propagation

77
00:05:03.990 --> 00:05:08.960
have to be constrained by some rules and possibly and actually, uh,

78
00:05:10.860 --> 00:05:15.670
live without within the domain, uh, or concerns of a domain.

79
00:05:16.090 --> 00:05:20.950
And they can also participate in the operations if needed as big masks.

80
00:05:22.380 --> 00:05:26.830
Finally, even though the utility network and

81
00:05:27.850 --> 00:05:28.870
esri's, uh,

82
00:05:29.060 --> 00:05:33.630
utility network by out of the box brings propagation,

83
00:05:34.330 --> 00:05:36.630
the propagators must be configured.

84
00:05:37.050 --> 00:05:42.030
And this can be done either using GP tools, python, or model builder.

85
00:05:44.330 --> 00:05:48.210
Now, if we talk about face propagation,

86
00:05:48.300 --> 00:05:51.530
which is the propagator within an electric utility,

87
00:05:52.230 --> 00:05:56.650
the focus of this presentation, what does a face propagator does?

88
00:05:57.190 --> 00:05:59.600
Well, let's go back to what we just discussed.

89
00:06:00.100 --> 00:06:04.800
It derives the values from a collection of

90
00:06:04.820 --> 00:06:09.400
fields that have the network attribute e faces current

91
00:06:09.920 --> 00:06:10.800
assigned to them.

92
00:06:11.380 --> 00:06:16.200
And these fields in the S3 electric Foundation reference model are

93
00:06:16.820 --> 00:06:18.400
the faces,

94
00:06:18.400 --> 00:06:22.400
current field of the device junction and lines.

95
00:06:24.190 --> 00:06:26.880
Then using a function in particular,

96
00:06:26.880 --> 00:06:31.680
which is the bid wise and and applying some operation

97
00:06:31.780 --> 00:06:33.280
on those derived values,

98
00:06:33.940 --> 00:06:37.880
it sets the calculation value into a target field,

99
00:06:38.290 --> 00:06:41.000
which in the electric, uh,

100
00:06:41.130 --> 00:06:45.600
foundation reference model happens to be the faces

101
00:06:45.870 --> 00:06:49.960
energized device junction and lines attribute.

102
00:06:51.270 --> 00:06:56.090
So in this example that I'm showing you on the right we have a simple

103
00:06:56.090 --> 00:06:59.370
circuit is a circuit breaker test,

104
00:06:59.370 --> 00:07:02.250
zero zero connected, uh,

105
00:07:02.250 --> 00:07:06.170
through some branches of, uh, overhead three phase,

106
00:07:06.270 --> 00:07:08.010
and at the end underground three phase.

107
00:07:08.390 --> 00:07:13.290
And important thing there is that to illustrate the process, we have added two,

108
00:07:13.790 --> 00:07:18.770
uh, switching devices in this case, two fuse banks, uh, three phase each.

109
00:07:19.710 --> 00:07:24.090
And we are also using in this map the labeling of

110
00:07:24.430 --> 00:07:26.610
phases, current colon phases,

111
00:07:26.650 --> 00:07:30.970
energize so that we see what it is that we need to configure and what are the

112
00:07:30.970 --> 00:07:34.690
results Now then,

113
00:07:36.950 --> 00:07:41.770
um, what is the propagator going to do

114
00:07:43.430 --> 00:07:47.730
If we have configured the propagation correctly and we have given initial

115
00:07:47.730 --> 00:07:49.210
conditions to the data.

116
00:07:49.880 --> 00:07:54.570
Then if we have scenario like this one in which the B phase of, uh,

117
00:07:54.570 --> 00:07:57.290
of the fuse, first fuse bank blows up,

118
00:07:58.200 --> 00:08:02.210
then in the uh, gis, we,

119
00:08:03.070 --> 00:08:05.370
uh, simulate this, uh,

120
00:08:05.400 --> 00:08:10.290
situation as editing the feature and changing the close for

121
00:08:10.480 --> 00:08:11.230
open.

122
00:08:11.230 --> 00:08:15.290
Now of course I was a little dramatic here by saying it blows up and it seems

123
00:08:15.290 --> 00:08:19.970
like I'm talking about the g i s following, uh, real time,

124
00:08:20.670 --> 00:08:23.810
uh, state of the network. No, please don't,

125
00:08:24.370 --> 00:08:28.730
I don't want to mislead you into that direction. Um,

126
00:08:29.710 --> 00:08:34.650
any edit of a attribute network attribute

127
00:08:34.870 --> 00:08:38.250
in a feature such as the current, uh,

128
00:08:38.270 --> 00:08:43.010
status will drive any of

129
00:08:43.070 --> 00:08:47.410
the utility network advanced, uh, functionality.

130
00:08:48.430 --> 00:08:53.370
And what we could be seeing here is a scenario where for

131
00:08:53.610 --> 00:08:58.600
whatever reason and for whatever amount of time the B phase of

132
00:08:58.960 --> 00:09:03.480
a uh, fuse bank is going to be disabled,

133
00:09:03.670 --> 00:09:06.160
it's gonna be off, it's gonna be open.

134
00:09:07.100 --> 00:09:11.480
So I'm not implicitly saying that the

135
00:09:11.510 --> 00:09:16.320
application of face propagation is meant to do, uh,

136
00:09:16.480 --> 00:09:18.320
realtime analysis,

137
00:09:18.860 --> 00:09:23.320
but it's just a face management. It's not just,

138
00:09:23.540 --> 00:09:27.840
it is a face management, uh, capability of the utility network,

139
00:09:28.310 --> 00:09:32.360
even for a steady state view of the network.

140
00:09:33.180 --> 00:09:36.200
But what I was saying is that from close to open,

141
00:09:36.830 --> 00:09:39.400
it's gonna trigger the, uh,

142
00:09:39.400 --> 00:09:44.320
capabilities of the utility network only with if we had already configured

143
00:09:44.320 --> 00:09:48.520
switching devices to have a particular field such as the current, uh,

144
00:09:48.520 --> 00:09:53.280
device status from the reference model to be assigned the

145
00:09:53.870 --> 00:09:57.520
network attribute eev device status. So think about it,

146
00:09:57.540 --> 00:10:02.280
the network attributes are the drivers of all these traceability

147
00:10:02.820 --> 00:10:04.880
and capabilities of the utility network.

148
00:10:06.540 --> 00:10:10.520
So in a scenario this, if the b uh,

149
00:10:10.590 --> 00:10:15.240
fuse of the first fuse bank happened to be open and we run

150
00:10:16.010 --> 00:10:20.360
trace, um, updates of network, some kind of tracing,

151
00:10:20.630 --> 00:10:24.000
what we are gonna see is that after running it,

152
00:10:25.030 --> 00:10:30.000
what is gonna propagate past that downstream from that,

153
00:10:30.340 --> 00:10:34.640
uh, circuit, sorry, from that phase,

154
00:10:35.300 --> 00:10:37.440
uh, sorry, three phase. Uh,

155
00:10:37.590 --> 00:10:42.520
fuse bank is just the A and the C phases and it will leave

156
00:10:42.770 --> 00:10:46.600
every other device in the B phase der energized.

157
00:10:48.270 --> 00:10:52.440
Another important thing that I mentioned here is a concept of tier.

158
00:10:53.380 --> 00:10:57.920
So face propagation, just like tracing

159
00:10:59.430 --> 00:11:03.960
isly related to what tier you're working in because the tiers is where the

160
00:11:03.960 --> 00:11:08.760
subnetwork control is reside and they are the ones where the

161
00:11:09.590 --> 00:11:13.160
different sub-networks, uh, coexist.

162
00:11:14.220 --> 00:11:19.160
In order to remember or to discover for the first time the concept

163
00:11:19.300 --> 00:11:20.133
of tier,

164
00:11:20.640 --> 00:11:25.160
I suggest that you look on online also in the s3,

165
00:11:25.740 --> 00:11:27.800
um, documentation,

166
00:11:28.820 --> 00:11:32.440
the model for the utility network, uh,

167
00:11:32.580 --> 00:11:35.920
in particularly in this diagrammatic representation.

168
00:11:36.740 --> 00:11:39.880
So in particular I'm gonna focus on saying that uh,

169
00:11:40.300 --> 00:11:44.280
the tiers in your network are collection of devices,

170
00:11:44.280 --> 00:11:47.720
lines and injections that represent a particular behavior,

171
00:11:47.810 --> 00:11:52.760
let's say in an electric utility. And the electric domain could be,

172
00:11:53.500 --> 00:11:58.200
um, high voltage, uh, substation level voltage distribution,

173
00:11:58.200 --> 00:11:59.480
voltage, low voltage.

174
00:12:00.060 --> 00:12:03.680
Now then when you group those devices for a particular tier,

175
00:12:03.770 --> 00:12:07.120
let's talk about distribution for instance. Those devices,

176
00:12:07.170 --> 00:12:11.680
lines and junctions in a particular distribution tier that are

177
00:12:11.710 --> 00:12:16.520
connected among themselves and which are responding to the

178
00:12:16.570 --> 00:12:21.520
conditions of the sub network controller are defined

179
00:12:21.740 --> 00:12:26.120
as a individual sub networks of the, uh,

180
00:12:26.310 --> 00:12:28.120
utility network implementation.

181
00:12:28.510 --> 00:12:33.220
This is all a very formal way of saying that

182
00:12:33.290 --> 00:12:36.180
some networks are in the electric domain,

183
00:12:36.450 --> 00:12:39.220
your circuits or your feeders.

184
00:12:40.520 --> 00:12:44.620
So now let's go to face propagation. How, first of all,

185
00:12:44.710 --> 00:12:49.420
let's understand that face propagation is a type of conditional traverse,

186
00:12:50.450 --> 00:12:55.380
meaning tracing a graph is traversing the graph to get information out of

187
00:12:55.380 --> 00:12:58.380
it. And there are either simple, uh,

188
00:12:58.740 --> 00:13:03.700
tracing mechanisms based solely on connectivity and using some algorithms

189
00:13:03.810 --> 00:13:08.580
like the breath first and depth first or conditional,

190
00:13:09.520 --> 00:13:10.320
uh,

191
00:13:10.320 --> 00:13:15.180
traces such as the face propagation in which it's not just a

192
00:13:15.180 --> 00:13:17.100
connectivity, what drive the trace,

193
00:13:17.520 --> 00:13:22.420
but also some specific conditions that are applied to the edges

194
00:13:22.680 --> 00:13:23.740
and vers.

195
00:13:25.600 --> 00:13:30.340
How is the utility network asset package from the electric

196
00:13:30.340 --> 00:13:35.180
foundation reference model that we obtained from Esri solution already prepared

197
00:13:35.240 --> 00:13:37.460
for phase propagation? Well,

198
00:13:37.600 --> 00:13:40.700
if you look at the device and among many other fields,

199
00:13:40.880 --> 00:13:43.100
it has a collection of phase like fields.

200
00:13:43.670 --> 00:13:47.420
Those phase like fields can already configured for this different

201
00:13:47.700 --> 00:13:50.540
functionalities. And in particular for phase propagation,

202
00:13:50.920 --> 00:13:55.380
the faces currenting and faces energized are the fields to

203
00:13:55.690 --> 00:13:56.900
take into consideration.

204
00:13:57.510 --> 00:14:01.940
Those two fields are designed of da of data type, uh, short,

205
00:14:02.400 --> 00:14:06.660
and they are both governed by the domain electric distribution phase

206
00:14:06.660 --> 00:14:11.500
attribution, all of it out of the box. In particular the phase, uh,

207
00:14:11.560 --> 00:14:12.010
phases,

208
00:14:12.010 --> 00:14:16.860
energized field is set up so that by default it will always

209
00:14:16.860 --> 00:14:18.300
start with de-energized.

210
00:14:19.560 --> 00:14:24.500
Now then what is the contents of that domain? What is the domain which, uh,

211
00:14:24.560 --> 00:14:28.420
the code through a bit mass represents the, uh,

212
00:14:28.670 --> 00:14:30.420
faces in a particular value.

213
00:14:31.000 --> 00:14:35.740
And the weigh on is through the binary representation of the

214
00:14:35.770 --> 00:14:40.740
integer in which the last niel and in particular the last three bits of

215
00:14:40.800 --> 00:14:44.500
the are the masks to, uh,

216
00:14:44.980 --> 00:14:47.140
indicate whether the value has or not,

217
00:14:47.500 --> 00:14:50.300
A and or B and or C faces.

218
00:14:52.210 --> 00:14:56.870
The reference model also comes configured already with the net network attribute

219
00:14:57.960 --> 00:14:58.793
faces current,

220
00:14:59.040 --> 00:15:03.910
which is also governed by the same domain and it's defined as an inline,

221
00:15:04.370 --> 00:15:05.390
uh, network attribute,

222
00:15:05.390 --> 00:15:09.550
meaning it the last four bids can be used as a big mask.

223
00:15:10.780 --> 00:15:14.030
Also, the electric device,

224
00:15:14.510 --> 00:15:19.230
electric junction and electric line faces current fields are

225
00:15:19.230 --> 00:15:23.470
already assigned the E faces current

226
00:15:23.820 --> 00:15:24.653
attribute.

227
00:15:27.620 --> 00:15:32.510
Even though the utility network provides out

228
00:15:32.510 --> 00:15:35.470
of the box face propagation, it needs to,

229
00:15:35.610 --> 00:15:38.070
in the reference model asset package,

230
00:15:38.770 --> 00:15:40.630
it needs to be configured.

231
00:15:40.990 --> 00:15:45.750
Actually you need to configure it in a either file, uh,

232
00:15:45.970 --> 00:15:50.230
geo database or enterprise geo database version of that asset package.

233
00:15:50.650 --> 00:15:53.470
And the way to do it, or a simple way to do it,

234
00:15:53.810 --> 00:15:58.030
is through model builder around the set sub network

235
00:15:58.600 --> 00:16:00.710
definition, uh, GP tool,

236
00:16:00.760 --> 00:16:04.870
which already comes with RGIS Pro and the corresponding packages.

237
00:16:05.260 --> 00:16:09.470
What is doing is taking the, uh, utility network, uh,

238
00:16:09.490 --> 00:16:12.150
of interest and applying a propagator,

239
00:16:12.650 --> 00:16:16.910
it then configures a propagator into the electric network. Now again,

240
00:16:17.570 --> 00:16:19.750
the propagator has to be, uh,

241
00:16:20.030 --> 00:16:24.550
configured as I'm showing with the e faces current as a attribute that is gonna

242
00:16:24.550 --> 00:16:28.550
be propagated. Uh, substitution attribute is also important,

243
00:16:28.610 --> 00:16:33.310
but as I probably mentioned before, is a subject for another, um,

244
00:16:33.470 --> 00:16:36.160
presentation not outside.

245
00:16:36.180 --> 00:16:40.640
The scope of this one for face propagation is more geared towards, uh,

246
00:16:41.380 --> 00:16:42.480
uh, face swapping

247
00:16:44.160 --> 00:16:48.980
and the function and operators are the midwives with an include

248
00:16:48.980 --> 00:16:51.980
the values and using a, B,

249
00:16:52.100 --> 00:16:57.100
C as the mask that then derives the values

250
00:16:57.410 --> 00:17:01.780
from the faces current and places it in the target faces

251
00:17:02.260 --> 00:17:06.110
energize. Now then

252
00:17:08.030 --> 00:17:12.370
not only the utility network has to be properly configured. Also,

253
00:17:12.520 --> 00:17:17.490
your data must have some initial conditions which represent the following.

254
00:17:17.510 --> 00:17:21.090
In every subnetwork you must have a controller, which is a device,

255
00:17:21.110 --> 00:17:25.810
and for all the devices you must have the faces current represent the value of

256
00:17:25.810 --> 00:17:27.970
the faces that you want that device to have.

257
00:17:28.550 --> 00:17:33.490
Now then the faces energized are left to default in this case de-energized.

258
00:17:34.110 --> 00:17:36.250
For junctions, it's the same thing,

259
00:17:36.470 --> 00:17:40.770
except if your junction is gonna act as a tab and will discuss

260
00:17:41.670 --> 00:17:44.230
during the demo. Uh,

261
00:17:44.410 --> 00:17:49.360
so in if the junction is a tab, yes, you need to, uh,

262
00:17:49.580 --> 00:17:53.600
set the value of the faces current. If it's not gonna be a tab,

263
00:17:53.620 --> 00:17:57.880
if it's gonna be a plain junction, something used to establish connectivity,

264
00:17:58.510 --> 00:18:01.680
then you don't need, you should not, uh,

265
00:18:01.700 --> 00:18:05.320
set the value of the faces current whatsoever. And the same for lines.

266
00:18:05.780 --> 00:18:10.240
The values of the faces current should be known and the faces energized are

267
00:18:10.240 --> 00:18:11.073
gonna be the default.

268
00:18:11.420 --> 00:18:15.440
If we look at a map that I use in the beginning as an example,

269
00:18:15.890 --> 00:18:18.080
right before we run face propagation,

270
00:18:18.080 --> 00:18:23.000
this is a correct initial conditions of the data in which the lines are

271
00:18:23.000 --> 00:18:26.480
de-energized in default, uh, with no faces current.

272
00:18:27.380 --> 00:18:32.000
And the only elements that do have a faces current define are the,

273
00:18:32.420 --> 00:18:34.440
uh, controller, um,

274
00:18:35.450 --> 00:18:39.390
and also the individual fuss in the fuse banks.

275
00:18:41.400 --> 00:18:44.260
How does the core functionality work? Well,

276
00:18:44.570 --> 00:18:47.980
when you trigger it by either running the update network,

277
00:18:48.280 --> 00:18:50.700
the expose network or the trace sub network,

278
00:18:51.450 --> 00:18:54.900
then you get from each element that you are tracing,

279
00:18:55.000 --> 00:18:59.460
you get the value indicated by the effaces current network attribute.

280
00:18:59.600 --> 00:19:00.280
In other words,

281
00:19:00.280 --> 00:19:04.940
you are getting the value from the faces current and you are operating on that

282
00:19:04.940 --> 00:19:09.540
value based on big masking and hand operations

283
00:19:09.890 --> 00:19:14.220
with the ABC value and many other additional conditions.

284
00:19:14.320 --> 00:19:18.830
The algorithm is not, uh, simple as I'm expressing, um,

285
00:19:18.890 --> 00:19:23.590
but it has this approach and then it takes a derived computer

286
00:19:23.640 --> 00:19:27.990
value and propagates it or places it in the target feature

287
00:19:28.410 --> 00:19:30.030
phases energized value.

288
00:19:31.400 --> 00:19:34.660
If we look at the map now after running data sub network,

289
00:19:35.200 --> 00:19:39.820
we can see that all the features received the propagated value, a, B, C,

290
00:19:40.720 --> 00:19:41.410
uh,

291
00:19:41.410 --> 00:19:46.260
through the propagator in the faces energized except

292
00:19:46.490 --> 00:19:49.340
that the particular features, uh,

293
00:19:49.440 --> 00:19:53.780
of the devices they have been propagated their own,

294
00:19:54.640 --> 00:19:59.180
uh, faces current in some sense the faces currently the, uh,

295
00:19:59.460 --> 00:20:03.260
determinant condition of what phase goes through that device.

296
00:20:05.850 --> 00:20:10.270
Now we are gonna show some of the capabilities of the phase

297
00:20:10.420 --> 00:20:14.590
propagation using a real, uh, data scenario.

298
00:20:15.050 --> 00:20:19.590
In this case a particular subset that you see, they are in blue, uh,

299
00:20:19.970 --> 00:20:22.870
on, uh, derived from uh,

300
00:20:22.900 --> 00:20:27.710
real electric distribution and, um, radio,

301
00:20:28.290 --> 00:20:29.950
uh, electric distribution data.

302
00:20:31.420 --> 00:20:35.920
The first step in this demonstration is going to be to el um,

303
00:20:36.230 --> 00:20:38.760
hide the rest of the network,

304
00:20:39.260 --> 00:20:44.040
the real network data that I mentioned and just focus on the sample,

305
00:20:44.980 --> 00:20:49.600
uh, data that we have. As you can see right now, the conditions,

306
00:20:49.910 --> 00:20:54.560
initial conditions for the data are established. We have all the lines, uh,

307
00:20:54.560 --> 00:20:57.280
the energized with no current phases.

308
00:20:57.340 --> 00:21:02.000
If we go for instance to a three phase, uh,

309
00:21:02.000 --> 00:21:03.040
transformer here,

310
00:21:03.660 --> 00:21:08.240
we can see that each of the transformers is being given the faces current that

311
00:21:08.240 --> 00:21:13.120
is supposed to represent while the um, uh,

312
00:21:15.680 --> 00:21:18.120
junction that doesn't participate as a tapping,

313
00:21:18.460 --> 00:21:23.400
it doesn't have any current phases. And the tapping, uh,

314
00:21:23.640 --> 00:21:28.560
junctions has the three or the value of ABC for

315
00:21:28.650 --> 00:21:31.920
their um, current faces. Also,

316
00:21:32.260 --> 00:21:35.040
if we go all the way or on the secondary,

317
00:21:35.500 --> 00:21:38.160
we don't have any faces yet either.

318
00:21:38.940 --> 00:21:42.600
And if we go to the, uh, circuit breakers,

319
00:21:43.190 --> 00:21:47.560
well there we have the circuit breakers have already been configured with their

320
00:21:47.690 --> 00:21:50.480
three phases and they subnetwork name.

321
00:21:51.220 --> 00:21:55.640
So this is now the time to actually, uh,

322
00:21:55.820 --> 00:21:58.480
run the updates of network, for instance.

323
00:21:59.340 --> 00:22:03.240
And when running that, uh,

324
00:22:03.300 --> 00:22:08.080
we will obtain the propagation downstream. So let's see that.

325
00:22:09.620 --> 00:22:13.600
And then we apply the data network to one of the

326
00:22:13.950 --> 00:22:15.760
subnetworks we have, in this case,

327
00:22:15.900 --> 00:22:20.520
we are gonna be doing just for the feeder 36 1 7.

328
00:22:21.030 --> 00:22:21.880
Upon completion,

329
00:22:22.230 --> 00:22:26.960
then we can see that the ABC faces from the circuit

330
00:22:27.030 --> 00:22:31.920
breaker, the sub network source or controller has propagated

331
00:22:32.430 --> 00:22:37.160
down on the lines. And if we analyze the part of the circuit,

332
00:22:37.940 --> 00:22:42.560
it goes all the way down to the all the elements.

333
00:22:42.980 --> 00:22:47.200
If we zoom in now, we can see that even the,

334
00:22:48.060 --> 00:22:53.040
uh, secondaries were updated with secondary faces.

335
00:22:53.780 --> 00:22:56.800
And the reason being is because one of the, um,

336
00:22:58.280 --> 00:23:02.960
templates that we use in SSP to model, uh,

337
00:23:03.280 --> 00:23:08.200
a behavior of the transformer so that they can be um,

338
00:23:09.710 --> 00:23:13.800
face propagation compliant is via a

339
00:23:14.480 --> 00:23:19.280
connectivity that we establish between the low side of the

340
00:23:19.280 --> 00:23:21.800
transformer and the secondary,

341
00:23:21.950 --> 00:23:26.320
that visibility that we can see if we enter, um,

342
00:23:27.870 --> 00:23:31.950
association view. And as we can see,

343
00:23:31.950 --> 00:23:36.430
then the faces have propagated to the

344
00:23:37.360 --> 00:23:41.390
faces energized of all the components of the network.

345
00:23:42.380 --> 00:23:46.840
Look at another example now with another of the three

346
00:23:47.100 --> 00:23:51.400
sample, uh, feeders. Let's also notice that even though,

347
00:23:52.060 --> 00:23:54.080
um, propagation and

348
00:23:55.760 --> 00:23:59.280
tracing are intimacy linked together,

349
00:23:59.800 --> 00:24:02.640
tracing is more fundamental than propagation.

350
00:24:03.550 --> 00:24:08.000
What I mean with this is that we can right now trace the upper

351
00:24:08.390 --> 00:24:09.223
circuit

352
00:24:10.390 --> 00:24:14.480
even though face propagation has hasn't been executed in it.

353
00:24:14.980 --> 00:24:16.640
So let's see how we do that.

354
00:24:16.780 --> 00:24:21.160
We place a flag there and then we run our tracer

355
00:24:23.020 --> 00:24:26.600
and we expect to see in the, uh,

356
00:24:26.600 --> 00:24:31.360
selection set all the features downstream from that circuit

357
00:24:31.390 --> 00:24:35.920
breaker like we see there. Now stopping where barrier conditions are,

358
00:24:36.030 --> 00:24:40.040
such as the tie switch here, which is normally open.

359
00:24:40.380 --> 00:24:45.160
And also I force the recloser here to be open just to see more

360
00:24:45.160 --> 00:24:49.360
clearly that the trace finishes at a particular point.

361
00:24:50.020 --> 00:24:54.320
So keep in mind tracing works even if there is no

362
00:24:54.770 --> 00:24:58.120
phase propagation rang into a particular feed.

363
00:24:58.820 --> 00:25:02.840
So now before I run that, um,

364
00:25:05.590 --> 00:25:09.920
yeah data network on that feed to propagate the faces,

365
00:25:10.130 --> 00:25:14.360
let's pay attention for a minute to one of the features

366
00:25:15.810 --> 00:25:20.160
right here, which is implementing a tap.

367
00:25:21.020 --> 00:25:22.320
So I have, um,

368
00:25:23.670 --> 00:25:28.120
checked off the labels from the lines so that for clarity,

369
00:25:28.420 --> 00:25:32.960
we can see here this junction has had the faces current,

370
00:25:33.660 --> 00:25:34.493
um,

371
00:25:34.660 --> 00:25:38.680
set to BC this function is actually a

372
00:25:39.210 --> 00:25:42.680
subnetwork tap function, uh, junction,

373
00:25:43.210 --> 00:25:46.840
which is actually tapping from the trunk of three phase,

374
00:25:47.140 --> 00:25:52.120
and it only wants to provide B and C phases down these

375
00:25:52.220 --> 00:25:55.880
two phase. Um, primary, uh, branch.

376
00:25:57.020 --> 00:26:01.640
We also can see that the branch is protected by a two-face, uh,

377
00:26:02.270 --> 00:26:06.920
fuse bank and a face fuse bank in the initial conditions

378
00:26:07.300 --> 00:26:11.720
is set with the same faces as they are being, um,

379
00:26:12.220 --> 00:26:16.800
set by the tap. So let's see now what happens when we do run,

380
00:26:17.660 --> 00:26:19.240
uh, face, uh,

381
00:26:19.240 --> 00:26:23.280
propagation down this feed and once completed,

382
00:26:23.340 --> 00:26:28.280
we see that the three phases from the trunk have been actually,

383
00:26:29.780 --> 00:26:30.150
uh,

384
00:26:30.150 --> 00:26:34.880
processed by the face propagator based on the faces carrying of the tab

385
00:26:35.380 --> 00:26:39.920
and only the BC faces are then extracted

386
00:26:40.270 --> 00:26:44.880
from the trunk down the branch. The lines become phases,

387
00:26:45.300 --> 00:26:50.280
uh, energized BC and the equipment where it was B

388
00:26:50.790 --> 00:26:55.280
then continues to be B phase C, C phase,

389
00:26:55.900 --> 00:27:00.840
and the other junctions that do not participate as a

390
00:27:01.280 --> 00:27:06.120
injunction then just maintain the same propagated

391
00:27:06.220 --> 00:27:09.720
values downstream. So let's look at this scenario. Now,

392
00:27:10.110 --> 00:27:14.160
this is part of the third feed which we have not energized yet.

393
00:27:14.860 --> 00:27:18.880
Or let me put it this way. We have not run the updates of network on that feed.

394
00:27:19.060 --> 00:27:23.560
So phase has not been propagated and we are gonna pay attention to this

395
00:27:23.560 --> 00:27:27.800
particular scenario where using one of SSP templates,

396
00:27:28.220 --> 00:27:30.440
the one for overhead, uh,

397
00:27:30.440 --> 00:27:33.360
single phase transformer is actually

398
00:27:35.070 --> 00:27:39.960
connected to the line via a junction that is not tapping.

399
00:27:40.860 --> 00:27:43.440
Um, we could be using a tab,

400
00:27:43.580 --> 00:27:45.920
but I want to illustrate an example here.

401
00:27:46.310 --> 00:27:50.960
Then we have the tab that would be normal in a, uh, overhead transformer,

402
00:27:51.380 --> 00:27:54.400
we have the transformer itself. Down here is the assembly,

403
00:27:54.620 --> 00:27:57.640
so that when we look at it from, um,

404
00:27:58.040 --> 00:28:01.000
a higher scale or with is the assembly

405
00:28:02.700 --> 00:28:07.680
and the connectivity is established between the low side of the

406
00:28:07.880 --> 00:28:11.040
A phase transformer to the secondary,

407
00:28:11.040 --> 00:28:15.320
which is still deenergize. So what,

408
00:28:15.510 --> 00:28:19.320
what would happen if we now edit? In other words,

409
00:28:19.430 --> 00:28:23.920
what if we said the current phases of this junction,

410
00:28:24.010 --> 00:28:27.200
which is not acting as a tab or is not, sorry,

411
00:28:27.670 --> 00:28:31.560
it's not defined with the attribute, uh,

412
00:28:31.560 --> 00:28:34.200
network attribute of sub network tab.

413
00:28:34.940 --> 00:28:39.720
So it's not acting as a tab and then we run the update sub

414
00:28:39.720 --> 00:28:44.120
network. And as a result, a junction that is not,

415
00:28:45.380 --> 00:28:45.680
uh,

416
00:28:45.680 --> 00:28:50.680
equipped as a tab will make a constraint in the face propagation

417
00:28:50.830 --> 00:28:54.880
such that the propagator will not be able to,

418
00:28:55.620 --> 00:28:56.270
uh,

419
00:28:56.270 --> 00:29:01.040
push the faces downstream from it even though the propagator

420
00:29:01.900 --> 00:29:06.680
was still as I do showing now the, um,

421
00:29:07.850 --> 00:29:12.230
labels of the three phase line that I had

422
00:29:12.830 --> 00:29:17.590
actually hidden for clarity before the propagator has propagated all the

423
00:29:17.680 --> 00:29:21.790
faces. However, at this point, if the junction is not attacked,

424
00:29:22.130 --> 00:29:27.070
it doesn't execute as suspected because in order to tap

425
00:29:27.850 --> 00:29:32.750
the sub network element has to be either a tap or it

426
00:29:32.750 --> 00:29:35.070
has to be a junction that is not a taped,

427
00:29:35.170 --> 00:29:37.870
but with no constraint in the current faces.

428
00:29:39.050 --> 00:29:43.680
So after this, um, illustrative hopefully,

429
00:29:44.260 --> 00:29:48.240
uh, informative demonstration, um,

430
00:29:49.720 --> 00:29:54.200
I would like to point out that we've been talking about SSP

431
00:29:54.480 --> 00:29:58.680
templates as supporting this face propagation, uh,

432
00:29:59.210 --> 00:30:04.200
capability. So SSP has spent, uh, quite a bit of time

433
00:30:05.730 --> 00:30:09.490
creating a collection of templates to model the equipment,

434
00:30:09.590 --> 00:30:12.730
not only from the assets point of view, what devices,

435
00:30:12.730 --> 00:30:14.370
what junctions or assemblies,

436
00:30:14.430 --> 00:30:18.850
but also what behavior that equipment needs to

437
00:30:19.320 --> 00:30:24.210
implement within the utility network to provide the fidelity level

438
00:30:24.720 --> 00:30:27.210
that supports advanced functionality.

439
00:30:28.760 --> 00:30:31.500
Two of the classifications of this, uh,

440
00:30:31.900 --> 00:30:36.180
templates is how they connect to the lines, how the equipment connects.

441
00:30:36.240 --> 00:30:39.140
And in general, we can have two categories,

442
00:30:39.450 --> 00:30:43.580
equipment that taps to the line, equipment that splits the line.

443
00:30:43.610 --> 00:30:48.060
When we say split is not that actually the equipment that's cut the line,

444
00:30:48.600 --> 00:30:52.900
but the equipment actually sits between two ends of the lines

445
00:30:53.560 --> 00:30:57.860
and establishes a connectivity via, uh, topological association.

446
00:30:59.320 --> 00:31:03.540
And the advanced functionality of these templates is supported by the fact that

447
00:31:03.540 --> 00:31:08.480
the features, uh, faces current is either, uh,

448
00:31:09.620 --> 00:31:14.480
val valued for devices or is known for any other

449
00:31:14.590 --> 00:31:15.760
part of the equipment,

450
00:31:16.340 --> 00:31:21.240
as well as the phases energized are always created with a default value,

451
00:31:21.240 --> 00:31:22.440
which is de-energized.

452
00:31:22.820 --> 00:31:27.280
Let me show you some examples we've already seen in the demo, uh, the,

453
00:31:27.980 --> 00:31:31.720
uh, fuse banks, and this is just a collection of, uh,

454
00:31:31.970 --> 00:31:35.360
three of those fuse banks. Um,

455
00:31:35.860 --> 00:31:39.960
the three phase followed, uh, below by the two phase and the single phase,

456
00:31:40.070 --> 00:31:43.400
just very simple, each of the elements, uh,

457
00:31:43.400 --> 00:31:46.760
each of the devices are connected to the line ends,

458
00:31:46.940 --> 00:31:50.560
and that's what I we mean by splitting. It just splits the line,

459
00:31:50.780 --> 00:31:55.320
it sits in the middle and establish a connectivity by the connectivity

460
00:31:55.350 --> 00:31:59.600
association, not necessarily by having a line connected to it.

461
00:32:00.270 --> 00:32:01.560
Another example,

462
00:32:01.670 --> 00:32:05.840
very similar to that and behave similarly also is that of our closer

463
00:32:06.730 --> 00:32:09.790
or even a pad mounted transformer three,

464
00:32:09.930 --> 00:32:14.790
two and single phase where now the connectivity to the lines is actually the,

465
00:32:14.790 --> 00:32:15.330
uh,

466
00:32:15.330 --> 00:32:20.070
elbows where the open or closed represent whether the elbow is parked or

467
00:32:20.130 --> 00:32:23.230
not to, um, to the unit.

468
00:32:25.560 --> 00:32:30.370
Another example, and this one is for tapping equipment, is out of,

469
00:32:30.510 --> 00:32:32.650
uh, capacitors, overhead capacitors,

470
00:32:32.650 --> 00:32:35.930
particularly where they do tap to the line.

471
00:32:36.670 --> 00:32:41.320
And we have a template for two templates for three phase

472
00:32:41.370 --> 00:32:43.800
capacitors. Very common three phase capacitors,

473
00:32:44.060 --> 00:32:48.960
one in the top that is implemented by a single three phase uh, device.

474
00:32:49.380 --> 00:32:53.840
The one below is implemented by three single phase

475
00:32:54.190 --> 00:32:58.680
devices. And when we say three, it could be six, it could be actually 12, uh,

476
00:32:58.740 --> 00:33:03.080
is whatever you need to implement for the fidelity of your model.

477
00:33:03.700 --> 00:33:07.560
And also we've seen in the demonstration how, uh,

478
00:33:07.660 --> 00:33:10.800
in particularly the lower, uh,

479
00:33:10.890 --> 00:33:12.800
image of the single phase

480
00:33:14.680 --> 00:33:18.150
overhead transformer that then, um,

481
00:33:18.630 --> 00:33:22.070
connects through the low side to secondaries.

482
00:33:22.490 --> 00:33:25.190
And that way these, um,

483
00:33:26.030 --> 00:33:30.990
templates are actually supporting the behavior of bringing the high vol

484
00:33:31.370 --> 00:33:35.550
or or the distribution voltage to the low voltage, uh,

485
00:33:35.930 --> 00:33:40.750
and allows for propagation of phases and tracing

486
00:33:41.300 --> 00:33:42.990
down to the consumer.

487
00:33:44.450 --> 00:33:48.910
The other two are the two phase and the three phase, uh, capacitor example, uh,

488
00:33:48.910 --> 00:33:52.750
sorry, transformer example. So why

489
00:33:54.950 --> 00:33:59.370
should you or consider adopting, uh, face propagation?

490
00:33:59.470 --> 00:34:02.570
If you have implemented an electric, um,

491
00:34:03.490 --> 00:34:05.300
utility network model?

492
00:34:06.100 --> 00:34:10.150
It's because this is histories out of the box.

493
00:34:10.750 --> 00:34:15.630
Advanced functionality for face management use cases that we

494
00:34:15.630 --> 00:34:18.430
can think of are, uh, data migration.

495
00:34:19.020 --> 00:34:20.910
When you are migrating your data,

496
00:34:21.330 --> 00:34:25.790
you may want to make sure not only that the recipient or the target utility

497
00:34:25.790 --> 00:34:28.870
network is configured for phase propagation,

498
00:34:29.210 --> 00:34:32.630
but also that the way you are exporting that data, uh,

499
00:34:33.170 --> 00:34:35.150
abides to the initial conditions.

500
00:34:36.040 --> 00:34:40.940
You don't want to have junctions being exported with, uh,

501
00:34:41.320 --> 00:34:44.980
phases current set to a particular value because then you know that phase

502
00:34:45.090 --> 00:34:46.900
propagation is Nolan work.

503
00:34:47.000 --> 00:34:50.460
So you need to plan this when you are doing data migration.

504
00:34:50.770 --> 00:34:52.420
Another use case of course,

505
00:34:52.520 --> 00:34:57.340
is after a temporary change in your gis that requires somebody to edit

506
00:34:57.920 --> 00:35:00.620
the phases of particular equipment.

507
00:35:01.040 --> 00:35:05.740
And then after the edits have been approved

508
00:35:05.880 --> 00:35:08.540
and and committed, then you can run, uh,

509
00:35:08.880 --> 00:35:13.140
update some network and have the faces propagated

510
00:35:13.210 --> 00:35:17.180
accordingly. Also, during simulations, that will be another, uh,

511
00:35:17.180 --> 00:35:21.240
use case that comes to mind. Think of phase, uh,

512
00:35:21.350 --> 00:35:25.960
propagation also as a tool for data validation that you can impose some

513
00:35:25.960 --> 00:35:30.960
conditions on and also take advantage of it in the cases of labeling an

514
00:35:30.960 --> 00:35:32.960
annotation for your mapping needs.

515
00:35:35.040 --> 00:35:39.910
Now I want to make a point that current that we've been using the word

516
00:35:39.910 --> 00:35:44.600
current a lot doesn't really mean anything about real time gis

517
00:35:44.600 --> 00:35:49.120
still the system of record of your steady state of the network,

518
00:35:49.570 --> 00:35:53.720
while other systems such as OMS or IDMs and uh, scada,

519
00:35:53.950 --> 00:35:58.280
they are actually representing your real time in some fashion.

520
00:35:58.860 --> 00:36:03.560
So don't get lost in this translation face propagation or, and the,

521
00:36:03.560 --> 00:36:07.160
and the propagator itself is only gonna rely and look for

522
00:36:08.400 --> 00:36:11.550
attributes that are, um,

523
00:36:12.300 --> 00:36:16.630
network attribute and assign the network attribute e faces current.

524
00:36:17.530 --> 00:36:22.030
So in this case, if we are using the S3 reference model,

525
00:36:22.460 --> 00:36:27.230
that field is a faces current and that has a name faces current to

526
00:36:27.250 --> 00:36:30.070
be in line with the name of the network attribute.

527
00:36:30.650 --> 00:36:34.830
But the face propag is gonna ignore any other field such as faces,

528
00:36:34.830 --> 00:36:39.070
normal phases plan. And you can actually set values to those,

529
00:36:39.290 --> 00:36:40.310
to those faces.

530
00:36:40.310 --> 00:36:44.670
Normal phases plan among any other phases in in your target

531
00:36:45.260 --> 00:36:49.510
because the propagator is not gonna be, uh, looking into them.

532
00:36:49.530 --> 00:36:53.510
So it's not gonna be taking them into consideration in the calculations.

533
00:36:53.930 --> 00:36:56.510
And also you need to find out what is the best,

534
00:36:56.650 --> 00:37:01.640
the best field in which you are gonna set the value of that

535
00:37:01.640 --> 00:37:02.473
propagation.

536
00:37:02.780 --> 00:37:07.520
And in the reference model is a faces energizes for the devices

537
00:37:07.760 --> 00:37:12.600
junctions and lines that you have the freedom to, uh, configure your,

538
00:37:13.180 --> 00:37:13.450
uh,

539
00:37:13.450 --> 00:37:18.400
propagator to place those values in any other field that

540
00:37:18.460 --> 00:37:21.920
is convenient to you. And then you can drive the, uh,

541
00:37:21.920 --> 00:37:24.280
labeling and annotation based on those fields.

542
00:37:26.240 --> 00:37:28.140
So in essence, please, uh,

543
00:37:28.140 --> 00:37:31.740
don't consider current as meaning real time.

544
00:37:33.460 --> 00:37:34.293
As a summary,

545
00:37:34.870 --> 00:37:39.640
this presentation has discussed the details of Aries

546
00:37:40.100 --> 00:37:45.000
out of the box propagators and in particularly in particular the phase

547
00:37:45.070 --> 00:37:49.280
propagation. We have pointed out how phase propagation,

548
00:37:50.020 --> 00:37:54.920
uh, or any propagator requires a set of configuration and initial conditions.

549
00:37:55.240 --> 00:38:00.000
Particularly it requires an advanced data model with enough, uh,

550
00:38:00.320 --> 00:38:04.800
fidelity that not only represents the contents of your equipment but the

551
00:38:04.960 --> 00:38:08.310
behavior as well. Uh, such a model, uh,

552
00:38:08.410 --> 00:38:13.380
is provided by ESRI from the electric foundation and you also

553
00:38:13.380 --> 00:38:18.340
need some advanced utility network configuration that doesn't come out of the

554
00:38:18.340 --> 00:38:21.140
box from the uh, electric foundation.

555
00:38:21.280 --> 00:38:25.980
And we have explained how to do that propagation uh, configuration.

556
00:38:26.960 --> 00:38:28.980
The initial data set up is very important.

557
00:38:29.610 --> 00:38:34.060
Make sure that only switchable devices have their specific,

558
00:38:34.760 --> 00:38:37.400
uh, phases, uh,

559
00:38:37.410 --> 00:38:41.320
being assigned in the current phases for the, uh,

560
00:38:41.320 --> 00:38:43.440
propagator to work correctly.

561
00:38:44.330 --> 00:38:49.230
And we have indicated several times that this advanced functionality

562
00:38:49.490 --> 00:38:54.030
is triggered by either update sub network, export sub subnetwork,

563
00:38:54.450 --> 00:38:57.150
or when you are tracing a particular subnetwork,

564
00:38:58.540 --> 00:39:03.040
the face propagation and the face management from ESRI

565
00:39:03.040 --> 00:39:07.520
contributes to your data integrity and it can be

566
00:39:07.520 --> 00:39:10.560
complemented or it can complement itself.

567
00:39:11.230 --> 00:39:14.460
Other validation rules in your model,

568
00:39:16.010 --> 00:39:20.950
the S3 out of the box face management provided by face

569
00:39:21.020 --> 00:39:25.470
propagation could be an a very important tool for the

570
00:39:25.930 --> 00:39:30.060
GIS of the future. And with that said,

571
00:39:30.440 --> 00:39:33.420
we can go to a QA uh, session.

572
00:39:33.890 --> 00:39:36.700
I'll be glad to answer any questions you have. Keith,

573
00:39:37.280 --> 00:39:39.980
We do have about six questions that have come in. Give us a second,

574
00:39:40.120 --> 00:39:41.700
but the question is,

575
00:39:42.160 --> 00:39:45.940
you talked about labeling annotation based on device attributes,

576
00:39:46.200 --> 00:39:49.900
but I will be labeling an annotation off the assemblies.

577
00:39:49.920 --> 00:39:53.380
How could the propagated phase value be used in this scenario?

578
00:39:55.040 --> 00:39:55.580
Um, yeah,

579
00:39:55.580 --> 00:39:59.980
that's a good question because actually that's the main role of the assemblies

580
00:40:00.200 --> 00:40:01.100
is to be

581
00:40:02.980 --> 00:40:07.760
a cardiographic aids, uh, to, uh,

582
00:40:07.830 --> 00:40:12.480
produce maps. So if the face is current that I've been talking about,

583
00:40:12.480 --> 00:40:16.480
the face is energized that I've been talking about at all at the uh,

584
00:40:16.540 --> 00:40:19.840
device and the junction level and also the line level,

585
00:40:20.260 --> 00:40:25.080
how do you actually use them in a map if those devices and junctions

586
00:40:25.100 --> 00:40:29.920
are gonna be usually either hidden inside of assemblies

587
00:40:30.260 --> 00:40:31.680
or um,

588
00:40:32.140 --> 00:40:36.080
at a level of scale that doesn't mess up your,

589
00:40:36.270 --> 00:40:38.560
your mapping representation? Well,

590
00:40:38.660 --> 00:40:43.120
the way to do that is by using um, uh,

591
00:40:43.850 --> 00:40:48.720
rules applied between the assembly and

592
00:40:48.860 --> 00:40:53.240
the content devices in that assembly so that you can,

593
00:40:53.900 --> 00:40:58.800
uh, take those phases, for instance and just uh, add a map, um,

594
00:40:59.070 --> 00:41:03.800
push 'em up all the way to the assembly and then use then in the

595
00:41:04.000 --> 00:41:08.280
assembly the label text like we've always used to do the labeling

596
00:41:08.820 --> 00:41:13.800
and also drive the label text as the attribute

597
00:41:14.300 --> 00:41:16.200
for the corresponding annotation.

598
00:41:18.340 --> 00:41:23.050
Could you please give an example of phase propagation as a tool for data

599
00:41:23.060 --> 00:41:23.893
validation?

600
00:41:26.220 --> 00:41:27.200
Yes. Um,

601
00:41:28.880 --> 00:41:33.870
the propagator is not necessarily looking

602
00:41:34.650 --> 00:41:38.190
at the asset type of your features.

603
00:41:38.810 --> 00:41:42.510
So lemme put it this way. You may have like one of the examples,

604
00:41:43.230 --> 00:41:48.110
a lateral branch, uh, you have configured, uh,

605
00:41:48.110 --> 00:41:52.910
correctly as of let's say asset type two overhead.

606
00:41:53.970 --> 00:41:56.910
Uh, while the trunk is three phase overhead as a type,

607
00:41:58.810 --> 00:41:59.990
if you were not use,

608
00:42:00.610 --> 00:42:05.070
if you did not use the app to

609
00:42:05.340 --> 00:42:08.430
constrain the phases that go into the branch,

610
00:42:08.970 --> 00:42:12.470
and instead you had used one of the common

611
00:42:13.850 --> 00:42:16.710
non tapped uh junctions,

612
00:42:17.690 --> 00:42:22.070
the phase propagator would just push phases ABC down that

613
00:42:22.890 --> 00:42:27.750
two phase asset type line because you not pay attention to the asset type

614
00:42:28.290 --> 00:42:32.270
and then all of a sudden you have three phases in a two phase line.

615
00:42:33.140 --> 00:42:36.950
That for instance, to me is an example of how

616
00:42:38.820 --> 00:42:41.230
face propagation among many other things.

617
00:42:41.810 --> 00:42:44.990
Not only being a phase management system,

618
00:42:45.410 --> 00:42:49.870
it can also be seen as a way to identify, uh,

619
00:42:50.090 --> 00:42:54.550
errors in your model and also provide yeah,

620
00:42:54.550 --> 00:42:56.310
and then provide with that data integrity.

621
00:42:57.710 --> 00:42:59.260
Thank you Joaquin. Next one.

622
00:43:00.090 --> 00:43:03.020
What about phase order i e phasing?

623
00:43:03.080 --> 00:43:05.580
If one phase is normally de-energized?

624
00:43:08.120 --> 00:43:12.230
Could you repeat the question? The, the end? I couldn't hear the end.

625
00:43:13.060 --> 00:43:13.893
Sure thing.

626
00:43:13.940 --> 00:43:18.110
What about phase order i e phasing if one phase is normally

627
00:43:18.190 --> 00:43:19.023
de-energized,

628
00:43:20.080 --> 00:43:23.910
Right? Well phase propagation, that's not,

629
00:43:25.770 --> 00:43:28.910
um, propagate face order.

630
00:43:29.970 --> 00:43:33.470
It does actually take into consideration if a device

631
00:43:35.000 --> 00:43:39.830
along the way is de-energized or open like we showed

632
00:43:39.830 --> 00:43:42.950
in the very simple, uh, blown example.

633
00:43:44.090 --> 00:43:48.630
But face propagation does not have an

634
00:43:48.710 --> 00:43:52.830
ordering in the a b C mask used

635
00:43:53.690 --> 00:43:58.150
for the computation of the derived value. And in that case,

636
00:43:59.010 --> 00:44:03.510
the knowledge of phase, um, ordering,

637
00:44:03.760 --> 00:44:08.190
which is very important for the electric utility, uh, industry,

638
00:44:09.020 --> 00:44:13.590
it's not actually directly supported by face propagation.

639
00:44:13.680 --> 00:44:16.710
There needs to do some other, um,

640
00:44:17.150 --> 00:44:21.870
configurations in the database, but it's not just by face propagation.

641
00:44:24.610 --> 00:44:28.990
Are there any other interdependencies between tracing and phase

642
00:44:29.180 --> 00:44:30.013
propagation?

643
00:44:31.140 --> 00:44:35.610
Mm, let's see. Oh yeah,

644
00:44:35.790 --> 00:44:38.370
if you, uh, with the utility network,

645
00:44:38.670 --> 00:44:43.130
you can now even out of the box configure the tracers

646
00:44:43.680 --> 00:44:48.370
with and conditions and barriers and things like that.

647
00:44:48.470 --> 00:44:52.810
So you can actually configure, not program,

648
00:44:54.310 --> 00:44:58.650
but simply configure a tracer to do trace by face.

649
00:44:59.510 --> 00:45:01.250
So if you are

650
00:45:02.770 --> 00:45:06.580
combining phase propagation with phase

651
00:45:07.800 --> 00:45:10.540
traces or face by trace,

652
00:45:11.090 --> 00:45:15.620
then you have a good compliment there on finding out downstream from a

653
00:45:15.620 --> 00:45:20.420
particular point while the devices that are in a

654
00:45:20.420 --> 00:45:24.900
phase or that they were in a phase but they have been de-energized for some

655
00:45:24.900 --> 00:45:26.860
reason. That's an example that comes to mind.

656
00:45:28.040 --> 00:45:32.340
Thanks wa keen. Uh, actually this next one, what id,

657
00:45:32.420 --> 00:45:34.780
I don't want to use face propagation.

658
00:45:34.780 --> 00:45:37.580
Will the utility network still support my GIS model?

659
00:45:39.050 --> 00:45:43.190
Oh yes, absolutely. Advanced functionality is,

660
00:45:43.930 --> 00:45:48.830
uh, very recommended addon once you are moving into the utility network.

661
00:45:49.970 --> 00:45:50.410
Um,

662
00:45:50.410 --> 00:45:55.030
if you were to go through the whole process of migrating from the geometric

663
00:45:55.030 --> 00:45:59.910
network to the utility network and in that process you then

664
00:45:59.910 --> 00:46:04.270
put the extra effort to allow for advanced functionality,

665
00:46:04.770 --> 00:46:07.990
you may be missing some important, uh,

666
00:46:08.750 --> 00:46:13.110
functionality because of the cost of the migration

667
00:46:15.270 --> 00:46:18.830
wouldn't justify just going on a one to one, uh,

668
00:46:18.830 --> 00:46:22.830
whether in the geometric network you don't really have phase um,

669
00:46:22.840 --> 00:46:26.630
management unless you have some third party tools. So,

670
00:46:28.110 --> 00:46:32.450
but what I'm saying is that you can still have a perfectly, uh,

671
00:46:32.480 --> 00:46:35.690
traceable and um, uh,

672
00:46:36.050 --> 00:46:40.690
workable G i s is just that you are gonna have to figure out

673
00:46:40.840 --> 00:46:45.570
then what mechanism if you are interested in managing

674
00:46:46.000 --> 00:46:47.890
automatically the phases,

675
00:46:48.270 --> 00:46:52.650
you need to then figure out a mechanism to do that if you are not,

676
00:46:54.080 --> 00:46:54.530
uh,

677
00:46:54.530 --> 00:46:59.100
abiding to this configuration and initial data

678
00:46:59.100 --> 00:47:03.340
conditions of the phase preparation. But it will,

679
00:47:03.340 --> 00:47:04.500
it will work perfectly.

680
00:47:05.700 --> 00:47:10.080
All right, next up, I am not using the electric found,

681
00:47:10.140 --> 00:47:14.680
the electric foundation reference model. Can I still run phase propagation?

682
00:47:16.320 --> 00:47:17.540
Yes. Um,

683
00:47:18.160 --> 00:47:22.820
of course the examples I've given are based on the electric foundation

684
00:47:23.510 --> 00:47:28.100
asset package because that asset package has already been worked out by

685
00:47:28.600 --> 00:47:33.080
S3 solutions and they have all the knowledge internally

686
00:47:33.580 --> 00:47:37.880
of, uh, what the capabilities are. However, if you start

687
00:47:39.840 --> 00:47:41.840
a utility network from scratch,

688
00:47:42.290 --> 00:47:46.600
which which you can do and you can actually follow the documentation online and

689
00:47:46.800 --> 00:47:49.120
many examples, um,

690
00:47:50.420 --> 00:47:55.400
as long as you configure, uh, or,

691
00:47:55.460 --> 00:48:00.200
or you rehabilitate a network attribute called E faces current

692
00:48:01.140 --> 00:48:05.560
and you assign that to a fill in your devices,

693
00:48:06.360 --> 00:48:11.080
junctions and lines that have an integer

694
00:48:11.230 --> 00:48:16.040
type and driven by a face

695
00:48:16.230 --> 00:48:18.760
like domain. There you go.

696
00:48:19.100 --> 00:48:23.960
You don't need to inherit the whole reference model if you

697
00:48:23.960 --> 00:48:24.800
don't want to,

698
00:48:24.900 --> 00:48:29.360
if you want to restrict your model to a different type,

699
00:48:30.180 --> 00:48:34.640
but you can still run the, um, advanced functionality.

700
00:48:34.860 --> 00:48:39.480
By the way, this advanced functionality is not just for electric domains.

701
00:48:39.480 --> 00:48:43.360
Propagated, uh, exists for the gas domains,

702
00:48:43.620 --> 00:48:46.680
for the water domains. The propagation there is pressure.

703
00:48:47.380 --> 00:48:52.320
And so the concept is just really at the

704
00:48:52.320 --> 00:48:56.800
basis is the conditional traverse on a graph.

705
00:48:57.620 --> 00:49:00.200
So as long as you configure your graph correctly,

706
00:49:00.660 --> 00:49:04.240
you will always be able to run this functionally.

707
00:49:05.270 --> 00:49:06.200
Okay, thanks for that.

708
00:49:07.210 --> 00:49:11.980
When do I choose a tap junction versus a regular junction?

709
00:49:13.670 --> 00:49:18.140
Right? When the, the way I would say is when you want to,

710
00:49:18.920 --> 00:49:21.780
um, consume from the line,

711
00:49:21.800 --> 00:49:26.320
you are tapping a specific, uh,

712
00:49:26.380 --> 00:49:27.520
number of faces.

713
00:49:28.760 --> 00:49:32.580
And going back even to the question of the facing order,

714
00:49:32.730 --> 00:49:34.140
when I place a tab,

715
00:49:34.610 --> 00:49:38.620
like in the example it was a BC tab on the line.

716
00:49:39.280 --> 00:49:43.900
The propagator doesn't consider it a BC or a

717
00:49:44.200 --> 00:49:44.970
cb,

718
00:49:44.970 --> 00:49:49.500
it's just those two bits in the last nibble

719
00:49:50.160 --> 00:49:53.620
are saying these are the two, um,

720
00:49:55.040 --> 00:49:59.030
faces that are gonna be propagated downstream from this point.

721
00:50:00.170 --> 00:50:02.790
So, um, you,

722
00:50:03.370 --> 00:50:08.070
if you want to extract a subset of the faces

723
00:50:08.300 --> 00:50:11.230
running face propagation out of a line,

724
00:50:11.780 --> 00:50:13.430
then you use a tab.

725
00:50:13.970 --> 00:50:17.950
If what you are doing with the junction is actually just establishing

726
00:50:17.950 --> 00:50:20.270
connectivity between two line ns,

727
00:50:20.850 --> 00:50:25.710
you just leave them with no current faces and let the

728
00:50:25.710 --> 00:50:30.480
propagator push the faces because those junctions are not

729
00:50:31.040 --> 00:50:34.640
actually supposed to participate in that

730
00:50:35.900 --> 00:50:40.640
discriminative selection of what faces to go

731
00:50:40.690 --> 00:50:41.523
where.

732
00:50:42.300 --> 00:50:44.760
All right, thanks. Why can't we have another question that just come in?

733
00:50:45.620 --> 00:50:50.560
Is it possible to propagate energized phases in a version without

734
00:50:50.560 --> 00:50:52.480
needing to update the subnetwork?

735
00:50:54.510 --> 00:50:58.330
To my knowledge, not yet. I mean, you can, the prop,

736
00:50:58.630 --> 00:51:01.010
the propagator runs, sorry, let me explain that.

737
00:51:01.010 --> 00:51:05.640
The propagator runs with a trace, or in other words,

738
00:51:05.820 --> 00:51:10.720
if you are tracing the underlying advanced functionality is,

739
00:51:11.340 --> 00:51:12.360
uh, is supported.

740
00:51:13.460 --> 00:51:17.540
And then as soon as you change the,

741
00:51:18.320 --> 00:51:23.060
um, let's say like in our example, you change the B phase to open,

742
00:51:24.460 --> 00:51:26.780
right? And then you are in aver,

743
00:51:26.960 --> 00:51:30.620
you're editing your version and you say that edit

744
00:51:31.690 --> 00:51:32.523
immediately.

745
00:51:32.560 --> 00:51:37.500
If you were to trace downstream going through that fuse,

746
00:51:38.520 --> 00:51:43.480
the the B phase downstream from the fuse would be

747
00:51:43.480 --> 00:51:46.760
de-energized. Now then that value,

748
00:51:48.030 --> 00:51:49.720
because it's not the,

749
00:51:49.720 --> 00:51:53.720
because a trace is not carrying with it,

750
00:51:54.100 --> 00:51:55.160
the um,

751
00:51:56.700 --> 00:52:01.110
the propagation itself then would not

752
00:52:02.250 --> 00:52:07.110
be updated in any of the fields. But the internals of the,

753
00:52:07.650 --> 00:52:07.980
uh,

754
00:52:07.980 --> 00:52:12.790
utility network do know that downstream from that

755
00:52:13.060 --> 00:52:16.910
fuse, the B components are de-energized.

756
00:52:18.170 --> 00:52:21.990
Let me put it because this has been some kind of conversations there.

757
00:52:22.570 --> 00:52:23.230
In that sense,

758
00:52:23.230 --> 00:52:28.230
you will not be able to drive right now an annotation real

759
00:52:28.230 --> 00:52:31.350
time as you are doing the traces or, uh,

760
00:52:31.970 --> 00:52:35.150
unless you do an update subnetwork,

761
00:52:35.440 --> 00:52:40.190
which is when finally the values derived by the

762
00:52:40.190 --> 00:52:44.870
propagator good burned into the target

763
00:52:45.320 --> 00:52:46.153
field.

764
00:52:47.760 --> 00:52:51.230
Again. Do you have any questions? Uh, please use your go meeting panel. Uh,

765
00:52:51.360 --> 00:52:55.190
we're, I think we're out of questions just about time.

766
00:52:56.380 --> 00:52:58.590
Give another couple seconds here.

767
00:53:01.630 --> 00:53:05.030
Alrighty, let's move on. Uh, we wanna take,

768
00:53:05.030 --> 00:53:09.070
we wanna thank you for taking the time to join us today on our webinar. Uh,

769
00:53:09.170 --> 00:53:13.670
please join us in two weeks for a fantastic presentation from paper to survey

770
00:53:13.770 --> 00:53:16.790
1 23 updating the transmission inspection process.

771
00:53:16.890 --> 00:53:20.270
You don't wanna miss this one, it'll be August 20th. Uh,

772
00:53:20.270 --> 00:53:24.310
you can go to ssp illuminate.com and register there. Again,

773
00:53:24.370 --> 00:53:26.390
we hope you see you there and have a great day.

774
00:53:27.060 --> 00:53:28.270
Well, thank you very well.

775
00:53:28.860 --> 00:53:29.680
Thanks Joaquin.