1
00:31:08,000 --> 00:31:10,200
>> Good morning and welcome to our second

2
00:31:10,200 --> 00:31:13,200
meeting of the year. We will go ahead

3
00:31:13,200 --> 00:31:16,000
and get started. And it's January

4
00:31:16,000 --> 00:31:19,600
22nd, 2026 at 9:02 and we're ready to

5
00:31:20,100 --> 00:31:22,100
please take roll call.

6
00:31:22,100 --> 00:31:23,100
>> Director Ames?

7
00:31:23,100 --> 00:31:24,100
>> Here.

8
00:31:24,100 --> 00:31:25,100
>> Director Flores?

9
00:31:25,100 --> 00:31:26,100
>> Here.

10
00:31:26,100 --> 00:31:27,100
>> Director Foley?

11
00:31:27,100 --> 00:31:28,100
>> Present.

12
00:31:28,100 --> 00:31:29,100
>> Director Ghosh?

13
00:31:29,100 --> 00:31:30,100
>> Here.

14
00:31:30,100 --> 00:31:31,100
>> Director Li?

15
00:31:31,100 --> 00:31:32,100
>> Here.

16
00:31:32,100 --> 00:31:33,100
>> Director Raburn?

17
00:31:33,100 --> 00:31:34,100
>> Here.

18
00:31:34,100 --> 00:31:35,100
>> Director Rinn?

19
00:31:35,100 --> 00:31:36,100
>> Here.

20
00:31:36,100 --> 00:31:37,100
>> Vice President Wright?

21
00:31:37,100 --> 00:31:38,100
>> Here.

22
00:31:38,100 --> 00:31:39,100
>> President Hernandez?

23
00:31:39,100 --> 00:31:40,100
>> Present.

24
00:31:40,100 --> 00:31:41,100
>> We have a quorum.

25
00:31:41,100 --> 00:31:42,100
>> Thank you. We'll go ahead and

26
00:31:42,100 --> 00:31:43,100
please stand for the Pledge of

27
00:31:43,100 --> 00:31:44,100
Allegiance.

28
00:31:44,100 --> 00:31:45,100
I pledge allegiance to the flag of the

29
00:31:45,100 --> 00:31:46,100
United States of America, and to the

30
00:31:46,100 --> 00:31:47,100
republic for which it stands, one

31
00:31:47,100 --> 00:31:48,100
nation under God, indivisible, with

32
00:31:48,100 --> 00:31:51,100
liberty and justice for all.

33
00:32:04,100 --> 00:32:06,100
>> We're now heading into your

34
00:32:06,100 --> 00:32:07,100
introduction of special guests. And I

35
00:32:07,100 --> 00:32:10,100
will at this time turn it over to

36
00:32:10,100 --> 00:32:13,100
Director Ghosh, who will introduce

37
00:32:17,100 --> 00:32:19,100
William White.

38
00:32:25,100 --> 00:32:28,100
>> Thank you, Chair. I wanted to take

39
00:32:28,100 --> 00:32:31,601
this time to recognize Mr. William

40
00:32:34,100 --> 00:32:36,100
White for his leadership over the last

41
00:32:36,100 --> 00:32:39,601
15 years and founding Member of the

42
00:32:41,100 --> 00:32:43,100
BART Police Civilian Review Board.

43
00:32:43,100 --> 00:32:46,100
This happened soon after the murder of

44
00:32:46,100 --> 00:32:49,601
Oscar Grant and William played a

45
00:32:50,100 --> 00:32:52,100
pivotal role in transparent oversight

46
00:32:52,100 --> 00:32:54,100
of the BART's Police Department. I

47
00:32:54,100 --> 00:32:58,100
did not get a chance to work with him,

48
00:32:58,100 --> 00:33:00,100
as I started my term last year, but

49
00:33:00,100 --> 00:33:03,100
even in the one year that we have

50
00:33:03,100 --> 00:33:05,100
interacted, I have just been to

51
00:33:05,100 --> 00:33:07,100
grateful for his advice and his

52
00:33:07,100 --> 00:33:11,201
presence, and his deep history with the

53
00:33:12,100 --> 00:33:15,100
Civilian Review Board. He consistently

54
00:33:15,100 --> 00:33:17,100
elevated community voice and he was

55
00:33:17,100 --> 00:33:19,401
instrumental in advancing critical

56
00:33:21,100 --> 00:33:23,100
policies, including body-worn camera,

57
00:33:23,100 --> 00:33:25,100
bias-based profiling, one of the

58
00:33:25,100 --> 00:33:27,401
nation's first minimal use-of-force

59
00:33:28,100 --> 00:33:30,100
stars. His fairness, integrity and

60
00:33:30,100 --> 00:33:33,100
leadership in case review strengthened

61
00:33:33,100 --> 00:33:34,100
public trust and accountability for the

62
00:33:34,100 --> 00:33:37,100
BART Police Department. We want to

63
00:33:37,100 --> 00:33:39,100
extend our sincere appreciation for his

64
00:33:39,100 --> 00:33:42,100
many years' of service, and we were

65
00:33:42,100 --> 00:33:44,100
coordinating with William, and thank

66
00:33:44,100 --> 00:33:46,100
you, Mag and Bob, for all of the work

67
00:33:46,100 --> 00:33:48,100
that you did, but unfortunately he did

68
00:33:48,100 --> 00:33:50,100
have a family emergency this morning.

69
00:33:50,100 --> 00:33:52,100
He was supposed to join us by Zoom. He

70
00:33:52,100 --> 00:33:54,100
is not able to do that. But I'm happy

71
00:33:54,100 --> 00:33:58,201
if there are any comments from folks,

72
00:33:59,100 --> 00:34:03,100
we can us send him the recording. But

73
00:34:03,100 --> 00:34:05,100
truly it was a great honor to have

74
00:34:05,100 --> 00:34:08,601
interacted with him even for the

75
00:34:10,100 --> 00:34:13,100
chance that I got. We have a plaque

76
00:34:13,100 --> 00:34:17,201
for him that will be accepted by

77
00:34:19,100 --> 00:34:22,100
Dana Lang and former BPCRB

78
00:34:25,100 --> 00:34:28,100
Member Kidd. Can we go to comments?

79
00:34:28,100 --> 00:34:30,100
>> We can continue.

80
00:34:41,100 --> 00:34:43,401
>> Good morning, President Hernandez,

81
00:34:45,100 --> 00:34:46,100
and Members of BART Board of

82
00:34:46,100 --> 00:34:48,100
Directors. My name is Dana Lang and

83
00:34:48,100 --> 00:34:52,201
I'm current Chair of the Bart Police

84
00:34:53,100 --> 00:34:56,100
Civilian Review Board. We value Mr.

85
00:34:56,100 --> 00:34:58,100
William White's work for the

86
00:34:58,100 --> 00:35:00,100
last 15 years as a founding Member of

87
00:35:00,100 --> 00:35:02,100
this very important organization, and

88
00:35:02,100 --> 00:35:04,100
it's particularly important at this

89
00:35:04,100 --> 00:35:07,100
point in time. His mantra was

90
00:35:07,100 --> 00:35:08,100
transparency, and fairness. And that

91
00:35:08,100 --> 00:35:12,100
is what we want to continue to advance.

92
00:35:12,100 --> 00:35:16,201
So thank you for honoring him. And

93
00:35:17,100 --> 00:35:21,801
with me is Sharon Kidd, who will be

94
00:35:22,100 --> 00:35:24,100
accepting on his behalf.

95
00:35:24,100 --> 00:35:26,100
>> Great. Good morning everyone. My

96
00:35:26,100 --> 00:35:29,100
name is Sharon Kidd and I'm a past

97
00:35:29,100 --> 00:35:31,100
Board Member of BART's Civilian Review

98
00:35:31,100 --> 00:35:35,801
Board. I came on with Bill and George,

99
00:35:36,100 --> 00:35:40,100
and Bill was our pillar. He was the

100
00:35:40,100 --> 00:35:44,801
one who instructed us and kept us in

101
00:35:46,100 --> 00:35:48,100
your places because we both came from

102
00:35:48,100 --> 00:35:51,601
the City of Berkeley Police Civilian

103
00:35:52,100 --> 00:35:54,100
Review Board. I wish Bill were here,

104
00:35:54,100 --> 00:35:57,100
but I'm honored for receiving and thank

105
00:35:57,100 --> 00:36:00,601
you for recognizing him. Thank you.

106
00:36:19,100 --> 00:36:21,100
[ APPLAUSE ]

107
00:36:24,100 --> 00:36:28,201
>> Thank you. I think I'm done. It's

108
00:36:38,100 --> 00:36:42,100
hard to encapsulate so many decades' of

109
00:36:42,100 --> 00:36:45,100
work, but very grateful. Thank you.

110
00:36:45,100 --> 00:36:48,601
>> Thank you, Director Ghosh and thank

111
00:36:49,100 --> 00:36:51,100
you, Mr. White for all your dedication

112
00:36:51,100 --> 00:36:55,100
and service to the BART family, and

113
00:36:55,100 --> 00:36:58,601
wish you would have been here

114
00:36:59,100 --> 00:37:01,100
in-person, but I'm sure the award will

115
00:37:01,100 --> 00:37:04,100
be given to you gratefully and again,

116
00:37:04,100 --> 00:37:07,100
appreciate all your time and

117
00:37:07,100 --> 00:37:10,601
dedication. We have a public speaker.

118
00:37:12,100 --> 00:37:14,100
Patrick Caceres.

119
00:37:14,100 --> 00:37:17,100
>> Good morning, Board of Directors.

120
00:37:18,100 --> 00:37:20,100
Patrick Caceres Investigator with

121
00:37:20,100 --> 00:37:25,100
Bart's Office of the IP. I will be very

122
00:37:25,100 --> 00:37:28,100
Brave and thank you Director Ghosh for

123
00:37:28,100 --> 00:37:29,100
recognizing William White. He was always

124
00:37:29,100 --> 00:37:31,100
a Board Member since the time that

125
00:37:31,100 --> 00:37:33,100
I have gotten here, and so I have

126
00:37:33,100 --> 00:37:35,100
worked over ten-plus years with him,

127
00:37:35,100 --> 00:37:37,100
and as everyone said, he has always been

128
00:37:37,100 --> 00:37:40,100
a very amazing leader. Someone that

129
00:37:40,100 --> 00:37:42,100
has led with integrity and somebody who

130
00:37:42,100 --> 00:37:45,100
has always brought a voice to the table

131
00:37:45,100 --> 00:37:48,100
that was needed. So I appreciate him

132
00:37:48,100 --> 00:37:50,100
and his mentorship and his cooperation

133
00:37:50,100 --> 00:37:53,100
with our office, the Office of the

134
00:37:53,100 --> 00:37:56,100
Independent Police Auditor. Thank you.

135
00:37:56,100 --> 00:37:59,100
>> Thank you, Patrick. At this time,

136
00:37:59,100 --> 00:38:02,100
we'll go to Item No. 2, which is report

137
00:38:02,100 --> 00:38:04,100
of the Board President. I just wanted

138
00:38:04,100 --> 00:38:06,100
to remind our Board of Directors that

139
00:38:06,100 --> 00:38:10,201
we'll be having our meeting on February

140
00:38:12,100 --> 00:38:14,100
12th, and it's an all-day, it's casual.

141
00:38:14,100 --> 00:38:17,100
You don't have to wear your suit and

142
00:38:17,100 --> 00:38:19,100
tie and please come comfy, if you would

143
00:38:19,100 --> 00:38:22,601
like. So we'll look forward to

144
00:38:23,100 --> 00:38:25,100
that and sending out kind of the run of

145
00:38:25,100 --> 00:38:28,100
the show and if you have questions,

146
00:38:28,100 --> 00:38:31,100
please make sure you tell Mr. Powers.

147
00:38:31,100 --> 00:38:33,401
And then Item No. 3.

148
00:38:35,100 --> 00:38:36,100
>> We have two public comments,

149
00:38:36,100 --> 00:38:37,100
sorry.

150
00:38:37,100 --> 00:38:40,601
>> The first is Barney Smits. Barney.

151
00:38:42,100 --> 00:38:43,100
>> Barney, go ahead.

152
00:38:43,100 --> 00:38:46,100
>> My name is Barney Smits. I'm a

153
00:38:46,100 --> 00:38:47,100
licensed professional engineer with

154
00:38:47,100 --> 00:38:50,100
over 25 years' experience as a BART

155
00:38:50,100 --> 00:38:51,100
engineer and Fire/Life Safety expert.

156
00:38:51,100 --> 00:38:53,100
Thank you, President Hernandez. I see

157
00:38:53,100 --> 00:38:56,100
many in the agenda where the seats on

158
00:38:56,100 --> 00:38:58,100
the various BART Board Committees are

159
00:38:58,100 --> 00:39:00,100
being appointed. Over the last three

160
00:39:00,100 --> 00:39:02,100
years, I have pointed out the

161
00:39:02,100 --> 00:39:05,100
mismanagement and lack of transparency

162
00:39:05,100 --> 00:39:07,100
on the BSVII project. I have made

163
00:39:07,100 --> 00:39:09,100
numerous requests for the BART Board to

164
00:39:09,100 --> 00:39:11,100
establish a Sub-Committee on the BSVII

165
00:39:11,100 --> 00:39:14,100
project as both BART and VTA are

166
00:39:14,100 --> 00:39:17,100
failing in BART Board oversight.

167
00:39:17,100 --> 00:39:19,100
Again, this Sub-Committee appears to be

168
00:39:19,100 --> 00:39:21,100
missing. How many Members of the

169
00:39:21,100 --> 00:39:23,100
Board have read the report from the

170
00:39:23,100 --> 00:39:26,601
BART Office of Inspector General dated

171
00:39:27,100 --> 00:39:29,401
December 19, 2025? The record entitled

172
00:39:31,100 --> 00:39:32,100
"transparency and communication gaps

173
00:39:32,100 --> 00:39:35,100
in the BSVII project." Noted the limited

174
00:39:35,100 --> 00:39:36,100
public discussion and mixed messaging

175
00:39:36,100 --> 00:39:39,100
that evolve over the past decade and

176
00:39:39,100 --> 00:39:40,100
the report noted without clear

177
00:39:40,100 --> 00:39:42,401
communication and consistent Board

178
00:39:43,100 --> 00:39:45,100
oversight, BART risks losing influence

179
00:39:45,100 --> 00:39:47,100
over the design decisions that directly

180
00:39:47,100 --> 00:39:49,100
affect its ability to operate and

181
00:39:49,100 --> 00:39:52,100
maintain the future extension safely

182
00:39:52,100 --> 00:39:54,100
and efficiently. The report confirms

183
00:39:54,100 --> 00:39:56,100
that the comprehensive agreement gives

184
00:39:56,100 --> 00:39:58,100
BART approval authority over design

185
00:39:58,100 --> 00:40:00,100
elements that affect operations,

186
00:40:00,100 --> 00:40:03,100
maintenance and safety. The report

187
00:40:03,100 --> 00:40:05,401
recommended that BART management

188
00:40:06,100 --> 00:40:07,100
provide detailed reoccurring public

189
00:40:07,100 --> 00:40:09,100
presentations to the BART Board on the

190
00:40:09,100 --> 00:40:12,100
status of the BSVII project, and as a

191
00:40:12,100 --> 00:40:14,100
minimum, these updates should include

192
00:40:14,100 --> 00:40:16,100
BART's review and approval process

193
00:40:16,100 --> 00:40:19,100
under the design criteria manual.

194
00:40:19,100 --> 00:40:21,100
These public presentations are designed

195
00:40:21,100 --> 00:40:24,100
to strengthen governance and enhance

196
00:40:24,100 --> 00:40:25,100
transparency. Please continue -- I

197
00:40:25,100 --> 00:40:27,100
continue trying to help this Board and

198
00:40:27,100 --> 00:40:29,100
BART management to understand how to

199
00:40:29,100 --> 00:40:31,100
keep BART safe. I believe that a BART

200
00:40:31,100 --> 00:40:33,100
Sub-Committee is essential to restoring

201
00:40:33,100 --> 00:40:36,100
BART's full participation in this

202
00:40:36,100 --> 00:40:38,100
critical project. I hope that you will

203
00:40:38,100 --> 00:40:40,100
double your efforts to be a full and

204
00:40:40,100 --> 00:40:43,601
equal partner on the BSVII project.

205
00:40:44,100 --> 00:40:45,100
Thank you.

206
00:40:45,100 --> 00:40:48,601
>> We also have Aleta Dupree. Aleta.

207
00:40:50,100 --> 00:40:53,100
>> Thank you, good morning. President

208
00:40:54,100 --> 00:40:56,100
Melissa Hernandez and Members. Aleta

209
00:40:56,100 --> 00:40:59,100
Dupree, for the record, she and her

210
00:40:59,100 --> 00:41:01,100
with team folds. Regarding the

211
00:41:01,100 --> 00:41:04,100
Workshop. I'm looking forward to it.

212
00:41:04,100 --> 00:41:07,100
I did get to go to the Workshop last

213
00:41:07,100 --> 00:41:13,100
year. I hope we can do that Q&A again

214
00:41:13,100 --> 00:41:14,100
where you all were asked questions

215
00:41:14,100 --> 00:41:17,100
about which did and didn't do and I

216
00:41:17,100 --> 00:41:20,100
shared about my hang gliding and

217
00:41:20,100 --> 00:41:24,100
operating trains and the fact that I

218
00:41:24,100 --> 00:41:28,100
did not play flute and I cannot play

219
00:41:28,100 --> 00:41:31,601
any musical instruments. So I like

220
00:41:32,100 --> 00:41:33,100
those ice breakers. While we

221
00:41:33,100 --> 00:41:36,100
normally don't have the agendas ready

222
00:41:36,100 --> 00:41:39,100
until usually the Friday before the

223
00:41:39,100 --> 00:41:42,100
meeting, I hope that further ahead of

224
00:41:42,100 --> 00:41:46,100
time we can publish the general theme

225
00:41:46,100 --> 00:41:50,100
of what this Workshop is about. I know

226
00:41:50,100 --> 00:41:53,100
that every year our Workshop has a

227
00:41:53,100 --> 00:41:55,100
general theme. And it is this theme

228
00:41:55,100 --> 00:41:59,801
that will help me to inform my comments

229
00:42:02,100 --> 00:42:06,100
to you, written and spoken. I hope to

230
00:42:06,100 --> 00:42:10,201
be at your Workshop. I'm presuming I'm

231
00:42:12,100 --> 00:42:14,100
always casual and I'm sure I will be

232
00:42:14,100 --> 00:42:16,100
wearing a new skirt, maybe I will wear

233
00:42:16,100 --> 00:42:19,100
a skirt with folds. Anyway, let's do

234
00:42:19,100 --> 00:42:22,100
our preparation work for this Workshop,

235
00:42:22,100 --> 00:42:25,100
pun intended and I hope to be this.

236
00:42:25,100 --> 00:42:27,100
Thank you.

237
00:42:28,100 --> 00:42:30,100
>> Thank you, Aleta. If you come

238
00:42:30,100 --> 00:42:32,100
in-person, I have a newspaper from New

239
00:42:32,100 --> 00:42:36,201
York for you. Let Bob Franklin know.

240
00:42:37,100 --> 00:42:38,100
Any other public comment?

241
00:42:38,100 --> 00:42:41,100
>> There are no additional requests to

242
00:42:41,100 --> 00:42:42,100
address the Board.

243
00:42:42,100 --> 00:42:44,100
>> Okay. Not seeing any other public

244
00:42:44,100 --> 00:42:46,100
comment we'll go to the Consent

245
00:42:46,100 --> 00:42:50,100
Calendar. I would like to just quickly

246
00:42:50,100 --> 00:42:54,100
pull item b. Just to make one little

247
00:42:54,100 --> 00:42:58,100
quick change on there, and then, do I

248
00:42:58,100 --> 00:43:00,100
have any Directors? Not seeing any

249
00:43:00,100 --> 00:43:02,100
other Directors pulling anything, I

250
00:43:02,100 --> 00:43:05,100
will go ahead and ask for a motion for

251
00:43:05,100 --> 00:43:07,100
the remaining of the agenda?

252
00:43:07,100 --> 00:43:08,100
>> President Hernandez?

253
00:43:08,100 --> 00:43:09,100
>> Yes.

254
00:43:09,100 --> 00:43:13,201
>> I would like to ask regarding item

255
00:43:15,100 --> 00:43:19,100
C if the appointee to the Bart Police

256
00:43:19,100 --> 00:43:21,100
citizen Review Board is in the audience?

257
00:43:21,100 --> 00:43:23,100
>> Yes.

258
00:43:23,100 --> 00:43:24,100
>> Or online?

259
00:43:24,100 --> 00:43:26,100
>> Perfect. Let's just go and let's

260
00:43:26,100 --> 00:43:29,100
go in a row with item B. I would just

261
00:43:29,100 --> 00:43:34,401
like to make a quick change of -- on

262
00:43:35,100 --> 00:43:38,601
the VTA Committee. We're doing a

263
00:43:39,100 --> 00:43:42,601
little switcheroo as Ames as the

264
00:43:46,100 --> 00:43:49,100
Member. Now we'll go to item C. The

265
00:43:49,100 --> 00:43:52,601
appoint of Bart Police Civilian Review

266
00:43:53,100 --> 00:43:55,100
Board Member District 7. That is

267
00:43:55,100 --> 00:43:56,100
Jennifer.

268
00:43:56,100 --> 00:43:58,100
>> Rakowski.

269
00:43:59,100 --> 00:44:01,100
>> Correct.

270
00:44:06,100 --> 00:44:08,401
>> Welcome and please introduce

271
00:44:09,100 --> 00:44:10,100
yourself.

272
00:44:10,100 --> 00:44:14,100
>> Thank you so much to all of the

273
00:44:14,100 --> 00:44:16,100
Directors. My name is Jennifer

274
00:44:16,100 --> 00:44:20,100
Rakowski. I have been a Bart rider,

275
00:44:20,100 --> 00:44:24,100
proudly, for over 30 years, and I want

276
00:44:24,100 --> 00:44:26,401
to particularly acknowledge Director

277
00:44:28,100 --> 00:44:31,601
Flores for nominating me for this

278
00:44:32,100 --> 00:44:36,100
Review Board, and for all of the

279
00:44:36,100 --> 00:44:39,100
Directors' consideration. I am humbled

280
00:44:39,100 --> 00:44:41,100
both by the legacy of those who have

281
00:44:41,100 --> 00:44:44,100
been on the Board before, and the

282
00:44:44,100 --> 00:44:47,100
knowledge that the current oversight

283
00:44:48,100 --> 00:44:51,601
structure is rooted in the community

284
00:44:52,100 --> 00:44:55,100
grief and family grief of Oscar Grant

285
00:44:55,100 --> 00:44:58,601
that took place in District 7. Many

286
00:45:00,100 --> 00:45:03,100
community voices have risen up to

287
00:45:03,100 --> 00:45:07,201
direct BART on a path towards more

288
00:45:08,100 --> 00:45:10,100
equity and Justice, and I see BART

289
00:45:10,100 --> 00:45:14,801
stepping up to be a leader in transit

290
00:45:18,100 --> 00:45:20,401
agency around use-of-force, around

291
00:45:24,100 --> 00:45:25,100
excited delirium and I look forward to

292
00:45:25,100 --> 00:45:28,601
playing a role in continuing that

293
00:45:29,100 --> 00:45:31,100
integrity. I personally have knowledge

294
00:45:31,100 --> 00:45:34,100
of the important role and unique role

295
00:45:34,100 --> 00:45:38,201
BART plays in our region with missing

296
00:45:39,100 --> 00:45:42,601
children, and disabled who are lost,

297
00:45:44,100 --> 00:45:48,201
and needing to be secured in an

298
00:45:49,100 --> 00:45:52,100
equitable manner. And ultimately the

299
00:45:54,100 --> 00:45:56,100
importance BART plays getting people to

300
00:45:56,100 --> 00:45:58,100
work, getting them to family, getting

301
00:45:58,100 --> 00:46:01,100
them to all of the places where they

302
00:46:01,100 --> 00:46:05,201
make memories, and I plan to approach

303
00:46:06,100 --> 00:46:09,100
this role with respect, transparency,

304
00:46:09,100 --> 00:46:12,100
and accountability as the Hallmarks of

305
00:46:12,100 --> 00:46:14,401
the position. Thank you.

306
00:46:16,100 --> 00:46:19,100
>> Thank you. And this morning we've

307
00:46:19,100 --> 00:46:22,100
honored William White for his 15

308
00:46:24,100 --> 00:46:28,100
years' of service of he was thoughtful,

309
00:46:28,100 --> 00:46:32,100
fair and dedicated for 15 years, and he

310
00:46:32,100 --> 00:46:34,100
exhibited outstanding character. And

311
00:46:34,100 --> 00:46:37,100
your comments really resonate with me,

312
00:46:37,100 --> 00:46:41,100
and I saw Chair Dana Lang in the

313
00:46:41,100 --> 00:46:42,100
audience smiling as well. So welcome

314
00:46:42,100 --> 00:46:44,100
on-board.

315
00:46:45,100 --> 00:46:48,601
>> Thank you. I will move approval

316
00:46:50,100 --> 00:46:51,100
of the Consent Calendar.

317
00:46:51,100 --> 00:46:54,100
>> I will second. I will just

318
00:46:54,100 --> 00:46:56,100
clarify, as amended, on the consent

319
00:46:56,100 --> 00:46:57,100
item and I will second that.

320
00:46:57,100 --> 00:47:00,100
>> Yes, we do have -- thank you,

321
00:47:00,100 --> 00:47:03,601
Director Raburn and Director Rinn. We

322
00:47:06,100 --> 00:47:09,100
also have another public comment.

323
00:47:12,100 --> 00:47:15,601
Esther Waltz for item 3I. Good

324
00:47:18,100 --> 00:47:20,100
morning, Esther.

325
00:47:28,100 --> 00:47:31,601
>> Good morning. Nice to meet you,

326
00:47:35,100 --> 00:47:39,801
Bob, and thank you for having me, and

327
00:47:43,100 --> 00:47:47,801
the reason I would like to join the

328
00:47:50,100 --> 00:47:54,801
BART Task Force is to help make BART

329
00:47:55,100 --> 00:47:57,100
friendlier through improvements, you

330
00:47:57,100 --> 00:48:00,100
know, like, making it more efficient

331
00:48:00,100 --> 00:48:01,100
for people transitioning from the

332
00:48:01,100 --> 00:48:04,100
concourse down to the platform, make

333
00:48:04,100 --> 00:48:06,100
that area part of the system more

334
00:48:06,100 --> 00:48:10,201
efficient. So that it allows the train

335
00:48:11,100 --> 00:48:13,100
that sits at the stop, for those that

336
00:48:13,100 --> 00:48:17,201
need a little extra time embarking and

337
00:48:18,100 --> 00:48:21,601
disembarking the trains can do so

338
00:48:24,100 --> 00:48:26,100
safely, and making thing -- educating

339
00:48:26,100 --> 00:48:29,601
people on being more courteous to

340
00:48:30,100 --> 00:48:33,100
Seniors and disabled, and educating

341
00:48:33,100 --> 00:48:37,201
youth, because I have seen some things

342
00:48:38,100 --> 00:48:42,100
where people have -- I have seen it

343
00:48:42,100 --> 00:48:44,100
with people haven't always been

344
00:48:44,100 --> 00:48:45,100
courteous enough to give up in

345
00:48:45,100 --> 00:48:48,601
particular the seats that are marked

346
00:48:50,100 --> 00:48:52,401
yellowish-green, which designates that

347
00:48:53,100 --> 00:48:56,601
a Priority Area for the disabled

348
00:49:00,100 --> 00:49:02,100
people. Expectant mothers and others

349
00:49:02,100 --> 00:49:08,601
who need -- I know I have seen a lot of

350
00:49:09,100 --> 00:49:12,100
people willy nilly, giving me their

351
00:49:12,100 --> 00:49:16,801
seat, and they stand the rest of their

352
00:49:17,100 --> 00:49:20,601
ride. I'm capable with standing and

353
00:49:23,100 --> 00:49:27,201
holding on. Thank you for your time.

354
00:49:34,100 --> 00:49:36,100
>> Thank you, Esther. All right, do

355
00:49:36,100 --> 00:49:38,100
we have any public speakers?

356
00:49:38,100 --> 00:49:40,100
>> We have one, Aleta Dupree.

357
00:49:40,100 --> 00:49:41,100
>> Aleta.

358
00:49:41,100 --> 00:49:43,401
>> Aleta, please, go ahead.

359
00:49:44,100 --> 00:49:46,401
>> Thanks again, President Melissa

360
00:49:48,100 --> 00:49:50,100
Hernandez, and Members. Aleta Dupree

361
00:49:50,100 --> 00:49:52,100
for the, she and her with team folds.

362
00:49:52,100 --> 00:49:55,601
Thank you for the streamlined handling

363
00:49:57,100 --> 00:50:01,201
of the public comment today because I

364
00:50:02,100 --> 00:50:04,100
often get tripped up on the Consent

365
00:50:04,100 --> 00:50:06,100
Calendar. Some business about the cash

366
00:50:06,100 --> 00:50:08,100
carts. Very good report. We need to

367
00:50:08,100 --> 00:50:12,100
make it easier for people to haul that

368
00:50:12,100 --> 00:50:14,100
heavy money around. I do think about

369
00:50:14,100 --> 00:50:17,100
when in New York, they have the revenue

370
00:50:17,100 --> 00:50:18,100
trains, and they had all those carts

371
00:50:18,100 --> 00:50:21,100
that they had to move through the

372
00:50:21,100 --> 00:50:23,100
tunnels to 370.

373
00:50:24,100 --> 00:50:26,100
J Street. They stopped doing that. I

374
00:50:26,100 --> 00:50:28,100
hope we can someday do something about

375
00:50:28,100 --> 00:50:31,100
our old revenue trains. I think we

376
00:50:31,100 --> 00:50:33,100
have revenue trains, but anyway, I can

377
00:50:33,100 --> 00:50:37,201
ask Bob about that someday. I am

378
00:50:38,100 --> 00:50:41,601
looking forward to our new appointees

379
00:50:42,100 --> 00:50:46,100
who are going to join in this work on

380
00:50:46,100 --> 00:50:48,100
our Advisory Committees. I do engage

381
00:50:48,100 --> 00:50:50,100
with both of those Committees from time

382
00:50:50,100 --> 00:50:54,100
to time, can't say I have met either of

383
00:50:54,100 --> 00:50:55,100
these people. In reading the

384
00:50:55,100 --> 00:50:58,601
background, I'm not seeing any issues.

385
00:50:59,100 --> 00:51:00,100
Certainly hope they wouldn't --

386
00:51:00,100 --> 00:51:02,100
somebody like me who is different

387
00:51:02,100 --> 00:51:05,100
wearing a skirt, because I might be

388
00:51:05,100 --> 00:51:07,100
there in-person someday. So I hope as

389
00:51:07,100 --> 00:51:09,100
they go forward that they have

390
00:51:09,100 --> 00:51:11,100
inclusive perspectives of the people

391
00:51:11,100 --> 00:51:13,100
who ride BART and being able to have

392
00:51:13,100 --> 00:51:16,100
their issues heard, and addressed.

393
00:51:31,100 --> 00:51:33,100
[ INAUDIBLE ]

394
00:51:40,100 --> 00:51:43,100
Reasonable, so I believe that this

395
00:51:43,100 --> 00:51:45,100
entire Consent Calendar reflects the

396
00:51:45,100 --> 00:51:47,401
People's system. Thank you.

397
00:51:51,100 --> 00:51:53,100
>> Thank you, Aleta. Any other public

398
00:51:53,100 --> 00:51:55,100
comment?

399
00:51:55,100 --> 00:51:57,100
>> No, there --

400
00:51:57,100 --> 00:51:59,401
>> I have Director Flores.

401
00:52:00,100 --> 00:52:02,100
>> Thank you. Before we go on to the

402
00:52:02,100 --> 00:52:05,100
vote, I would like to thank Jennifer

403
00:52:05,100 --> 00:52:07,100
for her initiative in applying for this

404
00:52:07,100 --> 00:52:09,100
position for the Civilian Review Board.

405
00:52:09,100 --> 00:52:12,100
She comes highly recommended from many

406
00:52:12,100 --> 00:52:13,100
constituents in Alameda for her years'

407
00:52:13,100 --> 00:52:15,100
of service to the City around Police

408
00:52:15,100 --> 00:52:18,100
reform and racial equity, as well as

409
00:52:18,100 --> 00:52:20,100
her public service and tenant

410
00:52:20,100 --> 00:52:21,100
protections. So I just want to say

411
00:52:21,100 --> 00:52:23,100
thank you and look forward to her

412
00:52:23,100 --> 00:52:25,401
service here at BART.

413
00:52:26,100 --> 00:52:29,601
>> Thank you. And we have --

414
00:52:30,100 --> 00:52:34,801
>> If I may, I would also like to

415
00:52:35,100 --> 00:52:37,100
thank Esther Waltz for stepping up to

416
00:52:37,100 --> 00:52:40,100
represent the riders of the blue line,

417
00:52:40,100 --> 00:52:41,100
which I rode in this morning. So thank

418
00:52:41,100 --> 00:52:43,100
you again.

419
00:52:43,100 --> 00:52:46,100
>> Yes, we always want to thank our

420
00:52:46,100 --> 00:52:47,100
Committee Members, on all of our boards

421
00:52:47,100 --> 00:52:50,100
because a lot of it is dedication of

422
00:52:50,100 --> 00:52:52,100
their own time, their own personal

423
00:52:52,100 --> 00:52:53,100
time. Thank you again. Thank you for

424
00:52:53,100 --> 00:52:55,100
the public speakers. We have a motion

425
00:52:55,100 --> 00:52:56,100
and second for the Consent Calendar.

426
00:52:56,100 --> 00:52:58,100
If you could please take the roll.

427
00:52:58,100 --> 00:52:59,100
>> Yes.

428
00:52:59,100 --> 00:53:00,100
Director Ames?

429
00:53:00,100 --> 00:53:01,100
>> Yes.

430
00:53:01,100 --> 00:53:02,100
>> Director Flores?

431
00:53:02,100 --> 00:53:03,100
>> Aye.

432
00:53:03,100 --> 00:53:04,100
>> Director Foley?

433
00:53:04,100 --> 00:53:05,100
>> Aye.

434
00:53:05,100 --> 00:53:07,100
>> Director Ghosh?

435
00:53:07,100 --> 00:53:08,100
>> Yes.

436
00:53:08,100 --> 00:53:09,100
>> Director Li?

437
00:53:09,100 --> 00:53:10,100
>> Yes.

438
00:53:10,100 --> 00:53:11,100
>> Director Raburn?

439
00:53:11,100 --> 00:53:12,100
>> Yea.

440
00:53:12,100 --> 00:53:13,100
>> Director Rinn?

441
00:53:13,100 --> 00:53:14,100
>> Aye.

442
00:53:14,100 --> 00:53:15,100
>> Vice President Wright?

443
00:53:15,100 --> 00:53:16,100
>> Aye.

444
00:53:16,100 --> 00:53:17,100
>> President Hernandez?

445
00:53:17,100 --> 00:53:18,100
>> Aye.

446
00:53:18,100 --> 00:53:19,100
>> Motion passes unanimously.

447
00:53:19,100 --> 00:53:21,100
>> Thank you. We'll go on to our

448
00:53:21,100 --> 00:53:22,100
General Manager's report.

449
00:53:22,100 --> 00:53:24,401
>> Good morning, President Hernandez,

450
00:53:25,100 --> 00:53:26,100
Vice President Wright, Board of Directors.

451
00:53:26,100 --> 00:53:30,100
A couple of updates from the GM here:

452
00:53:30,100 --> 00:53:33,100
Ridership, we're tracking about 3.5% above

453
00:53:33,100 --> 00:53:34,100
budget for January and it continues to grow.

454
00:53:34,100 --> 00:53:38,100
A lot of it is driven by our on-time

455
00:53:38,100 --> 00:53:40,100
performance and the work we're doing

456
00:53:40,100 --> 00:53:42,100
there, but also these large events,

457
00:53:42,100 --> 00:53:45,601
especially over this past weekend. The

458
00:53:46,100 --> 00:53:49,100
Memorial for Bob Weir at the Civic

459
00:53:49,100 --> 00:53:51,100
Center, the K-Pop band twice had had a

460
00:53:51,100 --> 00:53:53,100
nice ridership boost at the Oakland

461
00:53:53,100 --> 00:53:56,601
arena and obviously, the good weather

462
00:53:57,100 --> 00:54:01,201
has helped our ridership. I wanted to

463
00:54:03,100 --> 00:54:04,100
second President Hernandez, our next

464
00:54:04,100 --> 00:54:06,100
Board Meeting the very next one is

465
00:54:06,100 --> 00:54:09,100
going to be the Workshop, February

466
00:54:09,100 --> 00:54:12,100
12th, all day in this Board Room. You

467
00:54:12,100 --> 00:54:13,100
heard about the dress attire from the

468
00:54:13,100 --> 00:54:15,100
President there, but I would say this,

469
00:54:15,100 --> 00:54:18,100
it's got a singular focus, and I sent

470
00:54:18,100 --> 00:54:21,100
out a note, I think, last Friday or

471
00:54:21,100 --> 00:54:22,100
last Thursday or Wednesday or

472
00:54:22,100 --> 00:54:24,100
something. The singular focus on that

473
00:54:24,100 --> 00:54:27,601
Workshop is the fiscal cliff. There's

474
00:54:29,100 --> 00:54:32,100
variants of that fiscal Cliff, the

475
00:54:32,100 --> 00:54:35,100
pre-before the fiscal cliff itself and

476
00:54:35,100 --> 00:54:36,100
obviously, what we're doing to drive

477
00:54:36,100 --> 00:54:39,100
ridership up in 2026, FY'26, and

478
00:54:41,100 --> 00:54:43,401
calendar-year 26 and build public

479
00:54:44,100 --> 00:54:45,100
confidence. At the core of the next

480
00:54:45,100 --> 00:54:47,100
meeting is going to be a discussion

481
00:54:47,100 --> 00:54:51,100
about our fiscal cliff at the Workshop.

482
00:54:51,100 --> 00:54:53,100
Single tracking is going to happen the

483
00:54:53,100 --> 00:54:57,100
next two Sundays on the yellow line

484
00:54:57,100 --> 00:55:00,100
between Rockridge and Orinda. And it's

485
00:55:00,100 --> 00:55:02,100
for vegetation management, and we'll be

486
00:55:02,100 --> 00:55:04,100
out there doing that, and then our

487
00:55:04,100 --> 00:55:07,100
traction power group will take

488
00:55:07,100 --> 00:55:10,601
advantage of that window to maximize

489
00:55:11,100 --> 00:55:13,100
their access to the trackway. So that

490
00:55:13,100 --> 00:55:17,100
is the next two Sundays we'll be single

491
00:55:17,100 --> 00:55:19,100
tracking. I guess to all of the

492
00:55:19,100 --> 00:55:22,100
directors here, but you know, maybe I

493
00:55:22,100 --> 00:55:24,100
will take a little -- I minor league

494
00:55:24,100 --> 00:55:26,100
get myself into trouble, but that is

495
00:55:26,100 --> 00:55:28,100
okay. Director Flores, and Director

496
00:55:28,100 --> 00:55:31,100
Raburn, but for everybody, West Oakland

497
00:55:31,100 --> 00:55:35,100
TOD phase 1, a quick update on that.

498
00:55:35,100 --> 00:55:38,100
Been able to secure tax credits and

499
00:55:38,100 --> 00:55:41,601
financing for phase 1, and it's going

500
00:55:43,100 --> 00:55:45,100
to deliver approximately 240

501
00:55:45,100 --> 00:55:47,100
Affordable-Housing Units there. And

502
00:55:47,100 --> 00:55:50,100
what is most important, for me, on

503
00:55:50,100 --> 00:55:52,100
schedule, schedule, schedule, we hope

504
00:55:52,100 --> 00:55:55,601
to begin construction on that phase

505
00:55:57,100 --> 00:55:58,100
1,240-Affordable-Housing Units this

506
00:55:58,100 --> 00:56:00,100
summer, the summer of 26 here, right

507
00:56:00,100 --> 00:56:02,100
around the corner. I know it's

508
00:56:02,100 --> 00:56:05,100
Director Flores and Director Raburn

509
00:56:05,100 --> 00:56:09,100
have a long history out there trying to

510
00:56:09,100 --> 00:56:12,100
take that happen. So I appreciate

511
00:56:12,100 --> 00:56:14,100
yours and Director Flores' commitment

512
00:56:14,100 --> 00:56:16,100
there. Comedy train is this Saturday

513
00:56:16,100 --> 00:56:19,100
and it's -- I'm telling -- I'm a firm

514
00:56:19,100 --> 00:56:20,100
believer it's these complementary

515
00:56:20,100 --> 00:56:22,100
events that we're doing that help drive

516
00:56:22,100 --> 00:56:25,100
up ridership, and this is just another

517
00:56:25,100 --> 00:56:28,601
example of that. It's this Saturday,

518
00:56:29,100 --> 00:56:31,100
it's called SF sketch fest on rails.

519
00:56:31,100 --> 00:56:34,601
We're going to have four comedians

520
00:56:36,100 --> 00:56:38,100
performing 15-minute sets on-board.

521
00:56:38,100 --> 00:56:39,100
It's sold out. You had to get a ticket

522
00:56:39,100 --> 00:56:43,100
and all of that. It's sold out,

523
00:56:43,100 --> 00:56:46,100
running from 12th Street to

524
00:56:51,100 --> 00:56:54,100
Pittsburg-Bay Point. So it's disco style

525
00:56:54,100 --> 00:56:56,100
with headphones and all of that. We're

526
00:56:56,100 --> 00:56:58,100
trying that and look like it's going to

527
00:56:58,100 --> 00:57:00,100
be a success, because it sold-out

528
00:57:00,100 --> 00:57:04,100
quick. I want to assure everybody here

529
00:57:04,100 --> 00:57:07,100
about our being at the center of and

530
00:57:07,100 --> 00:57:10,100
being ready for these large events and

531
00:57:10,100 --> 00:57:12,100
the next big one coming up is obviously

532
00:57:12,100 --> 00:57:15,100
the Super Bowl. Our Chief

533
00:57:18,100 --> 00:57:20,100
Transportation Officer and Chief

534
00:57:20,100 --> 00:57:21,100
Communication Officer, Rodd Lee is at

535
00:57:21,100 --> 00:57:24,100
the center of discussions, running

536
00:57:27,100 --> 00:57:29,100
longer trains, not just the event

537
00:57:29,100 --> 00:57:32,100
itself, but a watch party at Lake

538
00:57:32,100 --> 00:57:34,100
Merritt and a watch party downtown and

539
00:57:34,100 --> 00:57:37,100
tracking all of that and coordinating

540
00:57:37,100 --> 00:57:40,100
with the other agencies including

541
00:57:40,100 --> 00:57:41,100
Capitol Corridor, which runs all the way

542
00:57:41,100 --> 00:57:44,100
down to the Stadium this. So and we

543
00:57:44,100 --> 00:57:48,100
fronted a website on our website it's

544
00:57:48,100 --> 00:57:52,100
BART.gov Super Bowl at the center of

545
00:57:52,100 --> 00:57:54,100
those discussions and making sure that

546
00:57:54,100 --> 00:57:56,100
all works out. Two more items

547
00:57:56,100 --> 00:57:59,100
quickly here: I hope you are all

548
00:57:59,100 --> 00:58:02,100
tracking later today, we have a Member

549
00:58:02,100 --> 00:58:03,100
of the BART Accessibility Task Force

550
00:58:03,100 --> 00:58:06,100
that was in front of you and you just

551
00:58:06,100 --> 00:58:07,100
approved that Membership to that

552
00:58:07,100 --> 00:58:10,100
Committee. They are going to their

553
00:58:10,100 --> 00:58:11,100
annual meet-and-greet here today in

554
00:58:11,100 --> 00:58:13,100
this room, ore actually it's across the

555
00:58:13,100 --> 00:58:16,100
hall, sorry in the multi-purpose room

556
00:58:16,100 --> 00:58:18,100
from 3-4:30, if you are around it's

557
00:58:18,100 --> 00:58:19,100
always a nice event. Introduce

558
00:58:19,100 --> 00:58:22,100
yourself, get to know some of the

559
00:58:22,100 --> 00:58:24,100
Members of the BART Accessibility Task

560
00:58:24,100 --> 00:58:26,100
Force. Michael and I will make every

561
00:58:26,100 --> 00:58:28,100
attempt to get there. I know I have a

562
00:58:28,100 --> 00:58:30,100
3:00, but I will be down there at some

563
00:58:30,100 --> 00:58:33,100
point and Michael will be down there.

564
00:58:33,100 --> 00:58:35,100
Anyway, it's just good to strengthen

565
00:58:35,100 --> 00:58:37,100
those relationships, because all voices

566
00:58:37,100 --> 00:58:40,100
matter here at BART. And then the last

567
00:58:40,100 --> 00:58:44,100
item in front of you, you should have a

568
00:58:44,100 --> 00:58:47,601
folder. But so next Tuesday and

569
00:58:48,100 --> 00:58:49,100
Wednesday, we, collectively we are

570
00:58:49,100 --> 00:58:53,100
going to be up in Sacramento. It looks

571
00:58:53,100 --> 00:58:54,100
like there's six Directors heading up

572
00:58:54,100 --> 00:58:57,100
there. It will be the six of you,

573
00:58:57,100 --> 00:58:59,100
Staff, and our advocates, our labor

574
00:58:59,100 --> 00:59:00,100
partners as well. And we're going to

575
00:59:00,100 --> 00:59:02,100
be up in the Capitol. We're going to

576
00:59:02,100 --> 00:59:04,100
meet with our State Legislators from

577
00:59:04,100 --> 00:59:06,100
both parties and the Governor's Office.

578
00:59:06,100 --> 00:59:10,100
Right now you have a draft run of

579
00:59:10,100 --> 00:59:13,601
show, the meetings are always changing

580
00:59:14,100 --> 00:59:16,100
getting added, getting subtracted.

581
00:59:16,100 --> 00:59:20,100
We're trying to fit that into their

582
00:59:20,100 --> 00:59:23,601
calendars there and I want to

583
00:59:26,100 --> 00:59:29,100
say because we always run so fast,

584
00:59:29,100 --> 00:59:30,100
going boom, boom, boom. I wanted to

585
00:59:30,100 --> 00:59:32,100
thank you for taking time out of

586
00:59:32,100 --> 00:59:33,100
everything else you have got going to

587
00:59:33,100 --> 00:59:37,100
join me up there with me and Rodd and

588
00:59:37,100 --> 00:59:40,100
others as we look forward to some very

589
00:59:40,100 --> 00:59:43,100
productive discussions up there. So

590
00:59:43,100 --> 00:59:45,100
with that, President Hernandez, Vice

591
00:59:45,100 --> 00:59:47,100
President Wright, I will conclude my

592
00:59:47,100 --> 00:59:48,100
GM's report.

593
00:59:48,100 --> 00:59:50,100
>> Thank you. And I unfortunately

594
00:59:50,100 --> 00:59:53,100
will not be able to attend the

595
00:59:53,100 --> 00:59:56,100
accessibility. I will be at ACTC and I

596
00:59:56,100 --> 00:59:58,100
know my -- the person that I had

597
00:59:58,100 --> 01:00:01,100
appointed to that Task Force had

598
01:00:01,100 --> 01:00:03,100
emailed me. So I'm sure she will be

599
01:00:03,100 --> 01:00:05,100
there.

600
01:00:05,100 --> 01:00:06,100
>> We'll be there.

601
01:00:06,100 --> 01:00:08,100
>> And that you are able to make it as

602
01:00:08,100 --> 01:00:10,100
well. So we'll go ahead and go on to

603
01:00:10,100 --> 01:00:12,100
public comment and I do have Glen

604
01:00:12,100 --> 01:00:14,100
Overton.

605
01:00:32,100 --> 01:00:33,100
Good morning, Mr. Overton.

606
01:00:33,100 --> 01:00:35,401
>> Good morning, President Hernandez.

607
01:00:38,100 --> 01:00:41,601
General Manager Powers. You know they

608
01:00:42,100 --> 01:00:45,601
say stuff roll downhills. Well, this

609
01:00:46,100 --> 01:00:50,100
guy is a lot of good stuff rolling

610
01:00:50,100 --> 01:00:53,100
downhills. Believe me when I tell you.

611
01:00:53,100 --> 01:00:57,100
I came into the station this morning,

612
01:00:57,100 --> 01:01:01,801
and I couldn't even use my dust mop.

613
01:01:03,100 --> 01:01:07,801
Well, I got a different one this time.

614
01:01:09,100 --> 01:01:11,100
I declare I already I was all fired

615
01:01:11,100 --> 01:01:15,801
up. I was looking for those spots. I

616
01:01:16,100 --> 01:01:21,401
couldn't find a one. I seen a lot of

617
01:01:24,100 --> 01:01:27,100
contented BART riders. Hereby I

618
01:01:29,100 --> 01:01:32,601
entered the system -- why? Because

619
01:01:34,100 --> 01:01:37,601
President Hernandez and Bob Powers and

620
01:01:39,100 --> 01:01:43,801
Staff care. And the State ought to care.

621
01:01:44,100 --> 01:01:48,201
This is a caring for California, not

622
01:01:50,100 --> 01:01:54,801
just the Bay Area. It's a caring for

623
01:01:55,100 --> 01:01:59,201
the world, not just California. It's a

624
01:02:00,100 --> 01:02:04,100
caring for us, and all of our riders

625
01:02:04,100 --> 01:02:08,100
count, a moment of silence for all of

626
01:02:08,100 --> 01:02:10,100
us.

627
01:02:22,100 --> 01:02:24,401
For us. Thank you.

628
01:02:29,100 --> 01:02:30,100
>> Thank you

629
01:02:30,100 --> 01:02:33,100
>> Thank you. Public speakers online,

630
01:02:34,100 --> 01:02:37,601
Aleta Dupree and then Barney Smits.

631
01:02:40,100 --> 01:02:42,100
>> Thanks again, President Melissa

632
01:02:42,100 --> 01:02:43,100
Hernandez, and Members. Aleta Dupree, for

633
01:02:43,100 --> 01:02:47,100
the record, she and her with team

634
01:02:47,100 --> 01:02:49,100
folds. Very good report. I always

635
01:02:49,100 --> 01:02:51,100
enjoy Bob's meaningful and helpful

636
01:02:51,100 --> 01:02:54,100
reports. We're doing better and we're

637
01:02:54,100 --> 01:02:56,100
doing well with ridership. I see where

638
01:02:56,100 --> 01:02:59,601
that is considered to pre-pandemic. I

639
01:03:00,100 --> 01:03:04,100
think the New York City subways around

640
01:03:04,100 --> 01:03:07,100
85-90%. So we want to get people back

641
01:03:07,100 --> 01:03:09,100
on the trains. And I'm interested in

642
01:03:09,100 --> 01:03:12,100
the idea of this comedy train. I

643
01:03:12,100 --> 01:03:14,100
didn't buy a ticket for it, couldn't be

644
01:03:14,100 --> 01:03:18,801
there. I like the disco theme, and we

645
01:03:19,100 --> 01:03:21,100
don't do express trains very often.

646
01:03:21,100 --> 01:03:24,100
When I go to New York, they have these

647
01:03:24,100 --> 01:03:26,100
express routes, and I think this

648
01:03:26,100 --> 01:03:29,100
express train is going to be longer

649
01:03:29,100 --> 01:03:31,100
than the old JFK express that ran in

650
01:03:31,100 --> 01:03:34,601
New York City from 1978 to 1990, I

651
01:03:37,100 --> 01:03:39,100
think, which I used often. They still

652
01:03:39,100 --> 01:03:41,100
have express routes in New York City

653
01:03:41,100 --> 01:03:43,100
that I enjoy. And given the disco

654
01:03:43,100 --> 01:03:47,201
theme, I'm going to borrow some Don

655
01:03:49,100 --> 01:03:50,100
Cornelius here would say at the end of

656
01:03:50,100 --> 01:03:55,401
the show, it's going to be a stone gas,

657
01:03:57,100 --> 01:03:59,100
honey, peace, love and soul. Let me

658
01:03:59,100 --> 01:04:01,100
know how that goes. We need to be

659
01:04:01,100 --> 01:04:03,100
ready for our special events especially

660
01:04:03,100 --> 01:04:05,100
with Clipper. Clipper Executive Board

661
01:04:05,100 --> 01:04:07,100
will meet on Monday. Maybe I will be

662
01:04:07,100 --> 01:04:10,100
there. And last year I did get to go

663
01:04:10,100 --> 01:04:13,601
to the BART Accessibility Task Force

664
01:04:15,100 --> 01:04:18,100
meet-and-greet and found it to be very

665
01:04:18,100 --> 01:04:21,100
helpful and Christine Arsenault at the

666
01:04:21,100 --> 01:04:23,100
time was Chair. I hope you will be

667
01:04:23,100 --> 01:04:25,100
there. I'm not going to be there, I'm

668
01:04:25,100 --> 01:04:29,100
too far away and I'm sure the food will

669
01:04:29,100 --> 01:04:31,100
be very good. Thank you, Bob answered

670
01:04:31,100 --> 01:04:34,100
the question about the theme of the

671
01:04:34,100 --> 01:04:36,100
Workshop. So now I know. I can get

672
01:04:36,100 --> 01:04:40,100
ready for that. I ask in all of these

673
01:04:40,100 --> 01:04:41,100
items here, we remember that BART is

674
01:04:41,100 --> 01:04:44,100
the People's system. Thank you.

675
01:04:44,100 --> 01:04:48,201
>> Thank you. And now we have Barney.

676
01:04:50,100 --> 01:04:53,100
>> My name is Barney Smits. I'm a

677
01:04:53,100 --> 01:04:55,100
licensed professional engineer with

678
01:04:55,100 --> 01:04:56,100
over 25 years' experience as a

679
01:04:56,100 --> 01:04:59,100
BART engineer and Fire/Life Safety

680
01:04:59,100 --> 01:05:00,100
expert. Thank you General Manager

681
01:05:00,100 --> 01:05:03,100
Powers for the update on ridership and

682
01:05:03,100 --> 01:05:05,100
the upcoming public events. See there's

683
01:05:05,100 --> 01:05:07,100
a report on nine safety incidents in

684
01:05:07,100 --> 01:05:10,100
the 4th quarter of last year. I note

685
01:05:10,100 --> 01:05:11,100
that BART never finished their analysis

686
01:05:11,100 --> 01:05:14,100
on the TransBay Tube Fire and smoke

687
01:05:14,100 --> 01:05:16,100
incident. What happened after train

688
01:05:16,100 --> 01:05:18,100
387 got moving again, and during

689
01:05:18,100 --> 01:05:20,100
the remaining seven minutes before the

690
01:05:20,100 --> 01:05:22,100
train exited the tunnel to safety?

691
01:05:22,100 --> 01:05:24,100
When is BART going to publish a full

692
01:05:24,100 --> 01:05:27,100
public briefing on the safety incident?

693
01:05:27,100 --> 01:05:30,100
I asked every times about the status

694
01:05:30,100 --> 01:05:32,100
of various traction power Substations

695
01:05:32,100 --> 01:05:34,100
and the overall traction power system?

696
01:05:34,100 --> 01:05:37,100
No information has been provided to the

697
01:05:37,100 --> 01:05:39,100
public. Is the Civic Center Substation

698
01:05:39,100 --> 01:05:41,100
still not operational? How many months

699
01:05:41,100 --> 01:05:43,100
behind schedule is this Substation?

700
01:05:43,100 --> 01:05:45,100
Again, I'm asking how many Substations

701
01:05:45,100 --> 01:05:48,100
are out of service, how many traction

702
01:05:48,100 --> 01:05:50,100
power cable faults are currently

703
01:05:50,100 --> 01:05:52,100
hindering BART operations? What is

704
01:05:52,100 --> 01:05:54,100
wrong with the TransBay Tube's

705
01:05:54,100 --> 01:05:56,100
electrical power system? I understand

706
01:05:56,100 --> 01:05:59,100
that there's been an operating

707
01:05:59,100 --> 01:06:02,100
restriction in the TransBay Tube since

708
01:06:02,100 --> 01:06:05,100
April. That appears to be nine months.

709
01:06:05,100 --> 01:06:08,100
Next I would like to ask about the

710
01:06:08,100 --> 01:06:10,100
BSVII project. Did the General Manager

711
01:06:10,100 --> 01:06:13,100
read the BART Inspector General's

712
01:06:14,100 --> 01:06:16,100
report of 2025 and are you prepared to

713
01:06:16,100 --> 01:06:18,100
provide this Board and the public with

714
01:06:18,100 --> 01:06:20,100
the detailed presentation on the status

715
01:06:20,100 --> 01:06:23,100
of the BSVII project that the report

716
01:06:23,100 --> 01:06:25,100
recommended? If not, could you

717
01:06:25,100 --> 01:06:27,100
enlighten the Board and the public how

718
01:06:27,100 --> 01:06:29,100
you plan to strengthen governance and

719
01:06:29,100 --> 01:06:31,100
transparency on this project as BART is

720
01:06:31,100 --> 01:06:34,100
a full partner and bears fiduciary and

721
01:06:34,100 --> 01:06:36,100
legal responsibilities for the safety

722
01:06:36,100 --> 01:06:39,100
and transparent execution of this

723
01:06:40,100 --> 01:06:41,100
project. Thank you.

724
01:06:41,100 --> 01:06:45,801
>> Thank you. Moving on to one of our

725
01:06:46,100 --> 01:06:47,100
Directors. Robert Raburn.

726
01:06:47,100 --> 01:06:50,100
>> Thank you, President Hernandez. I

727
01:06:52,100 --> 01:06:56,201
just wanted to thank GM Powers for

728
01:06:59,100 --> 01:07:02,100
his report and while BART trains

729
01:07:02,100 --> 01:07:06,100
are sold out on that date, sketch fest,

730
01:07:06,100 --> 01:07:09,100
I went to the website and looked at the

731
01:07:09,100 --> 01:07:11,100
list of events, and I started

732
01:07:11,100 --> 01:07:14,100
scrolling. And I kept scrolling. And

733
01:07:14,100 --> 01:07:19,401
it is page after page of events with a

734
01:07:23,100 --> 01:07:24,100
number of headliners, Bob Odenkirk at

735
01:07:24,100 --> 01:07:29,100
the top of the list. This is a big

736
01:07:29,100 --> 01:07:31,100
deal and most venues all over the Bay

737
01:07:31,100 --> 01:07:35,100
Area, and most of those are BARTable.

738
01:07:35,100 --> 01:07:38,601
So anybody that feels left-out, you're

739
01:07:42,100 --> 01:07:43,100
not. Thank you.

740
01:07:43,100 --> 01:07:46,100
>> Thank you, Director Raburn. We

741
01:07:48,100 --> 01:07:49,100
will go onto to public comment,

742
01:07:49,100 --> 01:07:53,201
item No. 6 and we have Glen Overton.

743
01:08:01,100 --> 01:08:04,100
We have Glen Overton for Item No. 5.

744
01:08:04,100 --> 01:08:07,100
We now have Item No. 5. And then we'll

745
01:08:07,100 --> 01:08:09,100
have public comment and we'll have our

746
01:08:09,100 --> 01:08:12,601
Inspector General right after that if

747
01:08:16,100 --> 01:08:18,100
you want to go ahead and do public

748
01:08:18,100 --> 01:08:22,100
comment, sure and we'll go onto our

749
01:08:22,100 --> 01:08:24,100
Inspector General.

750
01:08:33,100 --> 01:08:37,201
>> I believe that -- I'm sorry, Madam

751
01:08:39,100 --> 01:08:42,100
President, and General Manager, Staff.

752
01:08:43,100 --> 01:08:48,401
I believe that BART has a not only an

753
01:08:52,100 --> 01:08:54,401
infrastructure responsibility, but an

754
01:09:01,100 --> 01:09:03,100
institutional responsibility. To

755
01:09:04,100 --> 01:09:07,601
educate the public the stations should

756
01:09:11,100 --> 01:09:14,100
educate, not just serve. Anyone can do

757
01:09:14,100 --> 01:09:16,100
that. We have in the United States, I

758
01:09:16,100 --> 01:09:20,100
don't know how many in the world how

759
01:09:20,100 --> 01:09:24,100
many transit stations, but how many of

760
01:09:24,100 --> 01:09:27,601
them are cultural artifacts? That can

761
01:09:28,100 --> 01:09:31,100
express community? This is an

762
01:09:33,100 --> 01:09:36,100
innovative community. BART needs to

763
01:09:39,100 --> 01:09:41,100
inspire innovation, education,

764
01:09:41,100 --> 01:09:43,401
advancement, equality. The stations

765
01:09:44,100 --> 01:09:48,201
should speak, levy upon the community a

766
01:09:50,100 --> 01:09:53,601
sense of community because it brings

767
01:09:55,100 --> 01:09:57,100
the communities together. I believe

768
01:09:57,100 --> 01:10:01,201
we have a responsibility not just for

769
01:10:03,100 --> 01:10:06,601
transit, but for community. Thank you.

770
01:10:11,100 --> 01:10:14,601
>> So the other public comments for

771
01:10:16,100 --> 01:10:19,601
No. 5. Barney Smits, please, go ahead.

772
01:10:21,100 --> 01:10:23,100
>> Actually this was item 6, but we'll

773
01:10:23,100 --> 01:10:26,100
go for it. My name is Barney Smits.

774
01:10:26,100 --> 01:10:27,100
I'm a licensed professional engineer

775
01:10:27,100 --> 01:10:30,100
with 25 years' experience as a BART

776
01:10:30,100 --> 01:10:31,100
engineer and Fire/Life Safety expert.

777
01:10:31,100 --> 01:10:33,100
Last meeting I asked about the

778
01:10:33,100 --> 01:10:36,601
significant reduction in safety on BART

779
01:10:38,100 --> 01:10:40,100
to Silicon Valley project and extended

780
01:10:40,100 --> 01:10:43,100
tunnel between emergency exits. I

781
01:10:43,100 --> 01:10:45,100
asked about why VTA extended the

782
01:10:45,100 --> 01:10:48,100
spacing to 500' when the BART facility

783
01:10:48,100 --> 01:10:50,100
standards requires a maximum of 300'

784
01:10:50,100 --> 01:10:52,100
between cross passages? This is a

785
01:10:52,100 --> 01:10:54,100
significant reduction in safety. This

786
01:10:54,100 --> 01:10:56,100
meeting I would like to ask why

787
01:10:56,100 --> 01:10:58,100
additional reductions in safety require

788
01:10:58,100 --> 01:11:00,100
patrons in an emergency to climb ten

789
01:11:00,100 --> 01:11:03,100
flights of stairs to reach safety at

790
01:11:03,100 --> 01:11:05,100
the surface? No existing BART Station

791
01:11:05,100 --> 01:11:08,100
requires this many stairs. No existing

792
01:11:08,100 --> 01:11:11,100
BART Station has -- all existing BART

793
01:11:11,100 --> 01:11:13,100
Stations have the surface as a point of

794
01:11:13,100 --> 01:11:15,401
safety. Since the comprehensive

795
01:11:17,100 --> 01:11:19,100
agreement gives BART approval authority

796
01:11:19,100 --> 01:11:20,100
over design elements that affect

797
01:11:20,100 --> 01:11:22,100
operations, maintenance and safety, I

798
01:11:22,100 --> 01:11:25,100
ask why BART is jeopardizing BART

799
01:11:25,100 --> 01:11:27,100
employees, patron and first-responders

800
01:11:27,100 --> 01:11:29,100
by allowing these significant

801
01:11:29,100 --> 01:11:32,100
reductions in safety? I have tried to

802
01:11:32,100 --> 01:11:35,100
make everyone aware of the dangers of

803
01:11:35,100 --> 01:11:37,100
smoke filed stations and Fire deep

804
01:11:37,100 --> 01:11:39,100
underground. Some say that won't

805
01:11:39,100 --> 01:11:40,100
happen, but the New Year's derailment

806
01:11:40,100 --> 01:11:44,100
and Fire a few years ago and the

807
01:11:44,100 --> 01:11:45,100
September TransBay Tube coverboard Fire

808
01:11:45,100 --> 01:11:47,100
should be a clear incident that fires

809
01:11:47,100 --> 01:11:50,601
and smoke filled stations do happen.

810
01:11:51,100 --> 01:11:54,100
The increase in third rail insulator

811
01:11:54,100 --> 01:11:55,100
failures coverboard and smoke

812
01:11:55,100 --> 01:11:57,100
incidents last year are more examples

813
01:11:57,100 --> 01:12:00,100
of the danger of reducing safety in the

814
01:12:00,100 --> 01:12:02,100
BART system. VTA's reduction in safety

815
01:12:02,100 --> 01:12:05,100
could result in the loss of life.

816
01:12:05,100 --> 01:12:07,100
Please insist that BART management

817
01:12:07,100 --> 01:12:09,100
utilize the comprehensive agreement to

818
01:12:09,100 --> 01:12:12,100
force VTA to provide BART patrons a

819
01:12:12,100 --> 01:12:15,100
comparable level of safety BART-Silicon

820
01:12:17,100 --> 01:12:21,201
Valley Phase II is safety in spite

821
01:12:23,100 --> 01:12:26,100
Mayor and deeper underground than any

822
01:12:26,100 --> 01:12:28,100
BART Station at 100' and BART should

823
01:12:28,100 --> 01:12:32,100
insist of returning to the faster and

824
01:12:32,100 --> 01:12:35,601
cheaper to twin-bore design. Thank you.

825
01:12:37,100 --> 01:12:40,100
>> Thank you. We are going to Item

826
01:12:40,100 --> 01:12:44,100
No. 5, which is our Office of Inspector

827
01:12:44,100 --> 01:12:45,100
General OIG report. If we can please

828
01:12:45,100 --> 01:12:47,401
have them come forward.

829
01:13:15,100 --> 01:13:17,100
>> Good morning Directors it's good

830
01:13:17,100 --> 01:13:20,100
to see you this morning. I want to go

831
01:13:20,100 --> 01:13:24,801
ahead and click -- thank you. I'm very

832
01:13:25,100 --> 01:13:28,100
pleased to present our audit of

833
01:13:28,100 --> 01:13:31,100
construction change orders conducted by

834
01:13:34,100 --> 01:13:37,601
GPP Analytics an independent firm and

835
01:13:38,100 --> 01:13:40,100
thank GPP Analytics and Mr. Metcalf for

836
01:13:40,100 --> 01:13:43,100
his work on the audit and the BART

837
01:13:43,100 --> 01:13:46,601
Staff that cooperated and often result

838
01:13:57,100 --> 01:14:00,100
from factor as unforeseen site

839
01:14:01,100 --> 01:14:02,100
conditions design refinements

840
01:14:02,100 --> 01:14:04,401
regulatory requirement and owner

841
01:14:05,100 --> 01:14:07,100
initiated changes. And also, you know,

842
01:14:07,100 --> 01:14:10,100
there is fraud risk associated with

843
01:14:10,100 --> 01:14:13,100
them and Julian will touch on that in

844
01:14:13,100 --> 01:14:15,100
his report. But ultimately what this

845
01:14:15,100 --> 01:14:18,100
report is for to provide context for

846
01:14:18,100 --> 01:14:21,601
how change orders function within BART,

847
01:14:22,100 --> 01:14:25,100
and how there are opportunities for

848
01:14:25,100 --> 01:14:26,100
continued improvements, and governance

849
01:14:26,100 --> 01:14:28,100
accountability and of course,

850
01:14:28,100 --> 01:14:30,100
stewardship of public resources. With

851
01:14:30,100 --> 01:14:33,100
that, I'm going to hand that over to

852
01:14:33,100 --> 01:14:34,100
Mr. Metcalf.

853
01:14:34,100 --> 01:14:37,100
>> Thank you, Inspector General and

854
01:14:37,100 --> 01:14:39,100
thank you, Directors for having me here

855
01:14:39,100 --> 01:14:42,100
today. My name is Julian Metcalf and

856
01:14:42,100 --> 01:14:43,100
just for my presentation we'll do a

857
01:14:43,100 --> 01:14:46,100
quick overview of the audit scope and

858
01:14:46,100 --> 01:14:48,100
objectives. There's a Section on the

859
01:14:48,100 --> 01:14:50,100
context to help put everything into

860
01:14:50,100 --> 01:14:52,100
perspective, and make sure there are

861
01:14:52,100 --> 01:14:54,100
shared terminology and I will go over

862
01:14:54,100 --> 01:14:57,100
the four findings of the audit, and

863
01:14:57,100 --> 01:14:58,100
there's opportunity for questions at

864
01:14:58,100 --> 01:15:01,100
the end, of course. So you may also be

865
01:15:01,100 --> 01:15:05,201
aware of this, but the audit was

866
01:15:06,100 --> 01:15:08,100
conducted using the GAGAS standards

867
01:15:08,100 --> 01:15:11,100
offer otherwise known as the yellow

868
01:15:11,100 --> 01:15:13,100
book and to look at construction change

869
01:15:13,100 --> 01:15:15,100
order practices and compliance with

870
01:15:15,100 --> 01:15:17,401
laws and regulation, identify

871
01:15:18,100 --> 01:15:21,100
opportunity for improve related to

872
01:15:21,100 --> 01:15:23,100
risks of fraud, waste and abuse. We had

873
01:15:23,100 --> 01:15:26,100
a four-year scope. But I believe the

874
01:15:26,100 --> 01:15:27,100
findings and recommendations apply

875
01:15:27,100 --> 01:15:28,100
beyond this period of time to the

876
01:15:28,100 --> 01:15:31,100
practices in general and worth noting

877
01:15:31,100 --> 01:15:35,201
most of the time our sampling Mench

878
01:15:36,100 --> 01:15:39,100
ogle used 95% confidence level and 10%

879
01:15:39,100 --> 01:15:41,100
margin of error to remind everyone that

880
01:15:41,100 --> 01:15:42,100
the numbers here are not going to be

881
01:15:42,100 --> 01:15:44,100
perfect. What we talk about in one of

882
01:15:44,100 --> 01:15:45,100
the audit finding in particular are

883
01:15:45,100 --> 01:15:47,100
some limitations with the data and

884
01:15:47,100 --> 01:15:48,100
information that is available. So when

885
01:15:48,100 --> 01:15:50,100
you see the numbers I would encourage

886
01:15:50,100 --> 01:15:53,100
ug to look at them as ballpark figures

887
01:15:53,100 --> 01:15:56,100
often times they are derived from this

888
01:15:56,100 --> 01:15:58,100
estimate methodology and in cases

889
01:15:58,100 --> 01:16:01,100
where we deviated from this, the report

890
01:16:01,100 --> 01:16:04,601
gets into detail, and footnotes. So

891
01:16:05,100 --> 01:16:08,100
before getting into the nitty gritty

892
01:16:08,100 --> 01:16:10,100
it's worth noting that things we

893
01:16:10,100 --> 01:16:11,100
observed BART doing well. In our

894
01:16:11,100 --> 01:16:14,601
testing we saw a common compliance-

895
01:16:15,100 --> 01:16:17,100
oriented culture and practice. Teams

896
01:16:17,100 --> 01:16:20,100
and individuals were following BART

897
01:16:21,100 --> 01:16:22,100
policies, and concerned about BART

898
01:16:22,100 --> 01:16:24,100
policies as we could tell from

899
01:16:24,100 --> 01:16:26,100
documentation and from individual

900
01:16:26,100 --> 01:16:29,100
reviews. We also noticed instances of

901
01:16:29,100 --> 01:16:31,401
continuous improvement and proactive

902
01:16:32,100 --> 01:16:34,100
approach, in particular before we

903
01:16:34,100 --> 01:16:37,601
engage in the audit, BART's performance

904
01:16:38,100 --> 01:16:40,100
and innovation team engaged in a rapid

905
01:16:40,100 --> 01:16:42,100
improvement event convening variation

906
01:16:42,100 --> 01:16:44,100
stakeholders involved in the change

907
01:16:44,100 --> 01:16:47,100
order process and identified various

908
01:16:47,100 --> 01:16:49,100
inefficiencies and opportunities for

909
01:16:49,100 --> 01:16:51,100
improvement of which, not all of them

910
01:16:51,100 --> 01:16:53,100
were implemented. And a lot of that I

911
01:16:53,100 --> 01:16:55,100
believe was in anticipation of this

912
01:16:55,100 --> 01:16:58,100
audit being completed. So they may

913
01:16:58,100 --> 01:17:02,201
have made advancements since then, but we

914
01:17:04,100 --> 01:17:06,100
noted the proactive before the audit

915
01:17:06,100 --> 01:17:07,100
began. For context, you may all know

916
01:17:07,100 --> 01:17:09,100
this, but I think it's just to make

917
01:17:09,100 --> 01:17:11,100
sure we're speaking the same term I

918
01:17:11,100 --> 01:17:14,601
wanted to just mention the different

919
01:17:15,100 --> 01:17:17,100
definitions here. And change orders

920
01:17:17,100 --> 01:17:20,100
are very common, and what they mean are

921
01:17:20,100 --> 01:17:23,100
modifications to add or reduce work and

922
01:17:23,100 --> 01:17:25,100
scope, adjust timelines to contract

923
01:17:25,100 --> 01:17:27,100
terms. This often is due to

924
01:17:27,100 --> 01:17:28,100
differences in site condition and one

925
01:17:28,100 --> 01:17:30,100
of our findings talks about

926
01:17:30,100 --> 01:17:32,100
opportunities to identify many of those

927
01:17:32,100 --> 01:17:35,100
unexpected site conditions a little bit

928
01:17:35,100 --> 01:17:37,100
better. There are also allowances.

929
01:17:37,100 --> 01:17:40,601
Allowances are built into the contract

930
01:17:41,100 --> 01:17:42,100
pre-approved amount for anticipated,

931
01:17:42,100 --> 01:17:45,100
but not fully defined cost. So

932
01:17:45,100 --> 01:17:47,100
contingencies that are built in. So one

933
01:17:47,100 --> 01:17:51,100
of the challenges we see when we try to

934
01:17:51,100 --> 01:17:53,401
compare apples-to-apples of change

935
01:17:54,100 --> 01:17:55,100
orders across jurisdictions and Capital

936
01:17:55,100 --> 01:17:58,100
Programs outside of BART is not every

937
01:17:58,100 --> 01:18:01,100
system and not every user are use these

938
01:18:01,100 --> 01:18:03,100
same terms. Allowances in some

939
01:18:03,100 --> 01:18:04,100
situations play be considered change

940
01:18:04,100 --> 01:18:08,801
order by others. So when you look at

941
01:18:09,100 --> 01:18:11,100
raw number it's not always aims to

942
01:18:11,100 --> 01:18:14,100
Apples because of the term. They are

943
01:18:14,100 --> 01:18:15,100
good practice and present in BART and

944
01:18:15,100 --> 01:18:19,100
also options in contract as you likely

945
01:18:19,100 --> 01:18:21,100
know, if information or changes come up

946
01:18:21,100 --> 01:18:23,100
later in the process, BART can exercise

947
01:18:23,100 --> 01:18:25,100
these options and they are pre-defined

948
01:18:25,100 --> 01:18:28,100
and built into the contract. That is

949
01:18:28,100 --> 01:18:30,100
another area if you look across time,

950
01:18:30,100 --> 01:18:33,100
you could sending differ from what the

951
01:18:33,100 --> 01:18:34,100
intended amount to the actual amount

952
01:18:34,100 --> 01:18:37,100
and this was because of pre-defined

953
01:18:37,100 --> 01:18:39,100
option and finally, a type of change

954
01:18:39,100 --> 01:18:42,100
order is a credit and descoping. And

955
01:18:42,100 --> 01:18:44,401
these are noteworthy. It's

956
01:18:45,100 --> 01:18:47,100
positive because when you credit money

957
01:18:47,100 --> 01:18:49,100
back to BART, that is money coming

958
01:18:49,100 --> 01:18:51,100
back, but it's also worth noting these

959
01:18:51,100 --> 01:18:54,100
carry some amount of fraud risk,

960
01:18:54,100 --> 01:18:56,100
collusion and different activities

961
01:18:56,100 --> 01:18:59,100
could be involved in them. Yes, it's

962
01:18:59,100 --> 01:19:02,100
possible to bring money back, still

963
01:19:02,100 --> 01:19:04,100
worthy of scrutiny and attention. So

964
01:19:04,100 --> 01:19:07,100
this is where we get into some of the

965
01:19:07,100 --> 01:19:09,100
challenges of definition. This is a

966
01:19:09,100 --> 01:19:11,100
busy table here but you can see the

967
01:19:11,100 --> 01:19:13,100
first row is the total capital

968
01:19:13,100 --> 01:19:15,100
construction spending and we pulled

969
01:19:15,100 --> 01:19:16,100
this from BART's audited financial

970
01:19:16,100 --> 01:19:18,100
statement. So there was a consistent

971
01:19:18,100 --> 01:19:20,100
publicly available number we could

972
01:19:20,100 --> 01:19:23,100
compare against. And in the asterisks

973
01:19:23,100 --> 01:19:25,100
to read the fine print of what goes

974
01:19:25,100 --> 01:19:28,100
into it, but it's roughly the amount of

975
01:19:28,100 --> 01:19:30,100
money spent in each Fiscal Year on an

976
01:19:30,100 --> 01:19:32,100
accounting basis for capital

977
01:19:32,100 --> 01:19:33,100
construction spending. The next line

978
01:19:33,100 --> 01:19:35,100
down is the next change orders. This

979
01:19:35,100 --> 01:19:38,100
is the amount of extra money that was

980
01:19:38,100 --> 01:19:40,100
spent from change orders that have

981
01:19:40,100 --> 01:19:43,100
costs, and the net amount of descope

982
01:19:43,100 --> 01:19:45,100
and credits that were taken out of

983
01:19:45,100 --> 01:19:48,100
that. The lines below though these

984
01:19:48,100 --> 01:19:50,100
separated out, but the amount is

985
01:19:50,100 --> 01:19:52,100
important here because that is the net

986
01:19:52,100 --> 01:19:55,100
amount that costs more than planned due

987
01:19:55,100 --> 01:19:57,100
to change orders specifically. And

988
01:19:57,100 --> 01:19:59,100
when you compare them as a percentage

989
01:19:59,100 --> 01:20:01,100
of total capital spending it's a

990
01:20:01,100 --> 01:20:03,100
relatively small percent, but as we'll

991
01:20:03,100 --> 01:20:07,100
see in a slide shortly, this percentage

992
01:20:07,100 --> 01:20:10,100
is extremely varied on a project by

993
01:20:10,100 --> 01:20:12,100
project basis. You can start to see a

994
01:20:12,100 --> 01:20:14,100
hint of this here. This is showing you

995
01:20:14,100 --> 01:20:17,601
the distribution of them, the top

996
01:20:18,100 --> 01:20:21,100
Section shows the amounts and

997
01:20:21,100 --> 01:20:23,100
frequency of cost decreases, the

998
01:20:23,100 --> 01:20:25,100
credits and descopes. The middle

999
01:20:25,100 --> 01:20:27,100
Section shows the no-cost ones, no

1000
01:20:27,100 --> 01:20:29,100
dollar cost, but changes to the term

1001
01:20:29,100 --> 01:20:31,100
still run as a change order and the

1002
01:20:31,100 --> 01:20:32,100
bottom Section shows the cost

1003
01:20:32,100 --> 01:20:35,100
increases. You can see there are

1004
01:20:35,100 --> 01:20:36,100
numerous small cost increase change

1005
01:20:36,100 --> 01:20:39,100
order and a handful of very large ones

1006
01:20:39,100 --> 01:20:42,100
at the bottom. Now a very notable

1007
01:20:42,100 --> 01:20:45,100
thing is the TransBay Tube retrofit

1008
01:20:45,100 --> 01:20:47,100
that occurred. As you are well-aware

1009
01:20:47,100 --> 01:20:49,100
this was a very long-term project and

1010
01:20:49,100 --> 01:20:51,100
in our audit period, that project was

1011
01:20:51,100 --> 01:20:55,100
nearing its end. There was a very

1012
01:20:55,100 --> 01:20:57,100
significant 28.3 million credit that

1013
01:20:57,100 --> 01:20:59,100
occurred in this, this was money that

1014
01:20:59,100 --> 01:21:01,100
BART identified and requested back from

1015
01:21:01,100 --> 01:21:03,100
the vendors, and was credited back in a

1016
01:21:03,100 --> 01:21:05,100
change order that came back to BART.

1017
01:21:05,100 --> 01:21:08,100
On the next slide, if we exclude that

1018
01:21:08,100 --> 01:21:11,601
amount, because this is a large

1019
01:21:14,100 --> 01:21:15,100
project not captured in the full audit finding.

1020
01:21:15,100 --> 01:21:18,100
If you take that out because a

1021
01:21:18,100 --> 01:21:21,100
lot of change orders that were costly

1022
01:21:21,100 --> 01:21:23,100
occurred much earlier for this project,

1023
01:21:23,100 --> 01:21:26,100
from it we see nearly 50% increase in

1024
01:21:26,100 --> 01:21:30,100
the total net amount of change orders.

1025
01:21:30,100 --> 01:21:31,100
So it's just worth noting that when you

1026
01:21:31,100 --> 01:21:33,100
look at all of these numbers we have

1027
01:21:33,100 --> 01:21:36,100
the tail-end of very large project with

1028
01:21:36,100 --> 01:21:39,100
a very large credit, and it skews it.

1029
01:21:39,100 --> 01:21:41,100
So we showed it so you can try and see

1030
01:21:41,100 --> 01:21:43,100
what might be a more normal

1031
01:21:43,100 --> 01:21:45,100
circumstance. There may never been a

1032
01:21:45,100 --> 01:21:47,100
single year where everything is normal.

1033
01:21:47,100 --> 01:21:50,100
Is it will always be caveated a little

1034
01:21:50,100 --> 01:21:53,100
bit. And when I mention variability,

1035
01:21:53,100 --> 01:21:55,100
this chart shows some of the projects

1036
01:21:55,100 --> 01:21:58,100
that we looked at in-depth, and you can

1037
01:21:58,100 --> 01:22:00,100
see that there's the contract amount,

1038
01:22:00,100 --> 01:22:01,100
the net change orders. This is the

1039
01:22:01,100 --> 01:22:03,100
cost and the money coming back, and

1040
01:22:03,100 --> 01:22:05,100
then the percentage of the contract

1041
01:22:05,100 --> 01:22:06,100
that these change the orders

1042
01:22:06,100 --> 01:22:09,100
represented. If we look at the El

1043
01:22:09,100 --> 01:22:10,100
Cerrito Del Norte modernization

1044
01:22:10,100 --> 01:22:14,201
project, you can see that 49% of the

1045
01:22:15,100 --> 01:22:18,100
costs was due to change orders. Above

1046
01:22:18,100 --> 01:22:22,100
and beyond the contract amount. As you

1047
01:22:22,100 --> 01:22:25,100
go down, TransBay Tube retrofit, almost

1048
01:22:25,100 --> 01:22:27,100
30% then you get down to some smaller

1049
01:22:27,100 --> 01:22:30,100
cases. Well, you have the Hayward

1050
01:22:30,100 --> 01:22:31,100
Maintenance Complex phase 2, very small

1051
01:22:31,100 --> 01:22:33,100
amount of net change orders because of

1052
01:22:33,100 --> 01:22:36,100
some credits there. And then you have

1053
01:22:36,100 --> 01:22:39,100
other cases, such as tradition power

1054
01:22:39,100 --> 01:22:42,100
sub stations with a cost much lower

1055
01:22:42,100 --> 01:22:44,100
than anticipated due to credits and

1056
01:22:44,100 --> 01:22:45,100
change the orders. When we talk about

1057
01:22:45,100 --> 01:22:47,100
some of the data systems and

1058
01:22:47,100 --> 01:22:49,100
information challenges that BART has

1059
01:22:49,100 --> 01:22:52,601
with tracking change orders, what it

1060
01:22:54,100 --> 01:22:56,100
comes down to each project based on

1061
01:22:56,100 --> 01:22:57,100
information you can manual calculate

1062
01:22:57,100 --> 01:22:59,100
this by digging through a lot of

1063
01:22:59,100 --> 01:23:01,100
information. What is very difficult,

1064
01:23:01,100 --> 01:23:02,100
and I'm cutting ahead here a little

1065
01:23:02,100 --> 01:23:05,100
bit, is to look at this globally. It's

1066
01:23:05,100 --> 01:23:07,100
very difficult for Staff to pull this

1067
01:23:07,100 --> 01:23:09,100
information together and say well this

1068
01:23:09,100 --> 01:23:11,100
is what is happening and track it in

1069
01:23:11,100 --> 01:23:14,100
realtime, because each project has a

1070
01:23:14,100 --> 01:23:15,100
lot of circumstantial unique

1071
01:23:15,100 --> 01:23:17,100
information compiled on how it's

1072
01:23:17,100 --> 01:23:20,100
architected in information system and

1073
01:23:21,100 --> 01:23:24,100
when you look at small percentage

1074
01:23:24,100 --> 01:23:26,100
BARTwide and each project may have a

1075
01:23:26,100 --> 01:23:28,100
very different story depending on what

1076
01:23:28,100 --> 01:23:31,601
happened with each project. So it's

1077
01:23:40,100 --> 01:23:42,100
circumstantial. A lot of this stems

1078
01:23:42,100 --> 01:23:45,100
from the Office of Infrastructure

1079
01:23:45,100 --> 01:23:47,100
Delivery being tasked with

1080
01:23:47,100 --> 01:23:49,100
simultaneously enforcing contract

1081
01:23:49,100 --> 01:23:50,100
terms, and also maintaining project

1082
01:23:50,100 --> 01:23:52,100
progress. So you can imagine this

1083
01:23:52,100 --> 01:23:55,100
creates some amount of tension for a

1084
01:23:55,100 --> 01:23:58,100
Project Manager to be both

1085
01:23:58,100 --> 01:23:59,100
simultaneously pushing a project

1086
01:23:59,100 --> 01:24:01,100
forward quickly and with the highest

1087
01:24:01,100 --> 01:24:03,100
quality, but at the same time in charge

1088
01:24:03,100 --> 01:24:06,100
of policing and enforcing those

1089
01:24:06,100 --> 01:24:08,401
vendors, and ensuring contract

1090
01:24:09,100 --> 01:24:11,100
compliance. Now speaking with the

1091
01:24:11,100 --> 01:24:12,100
Office of Infrastructure Delivery they

1092
01:24:12,100 --> 01:24:15,100
report a lot of internal practices to

1093
01:24:15,100 --> 01:24:18,601
balance this within their own group.

1094
01:24:20,100 --> 01:24:21,100
But separating it out is the real

1095
01:24:21,100 --> 01:24:23,100
opportunity so that they can focus on

1096
01:24:23,100 --> 01:24:27,100
project delivery and can be a stronger

1097
01:24:27,100 --> 01:24:30,100
emphasis on separate monitoring. On

1098
01:24:30,100 --> 01:24:33,100
this next slide you can see that a lot

1099
01:24:33,100 --> 01:24:34,100
of different functions within BART are

1100
01:24:34,100 --> 01:24:37,100
involved in looking at change orders.

1101
01:24:37,100 --> 01:24:39,100
This is where I earlier mentioned the

1102
01:24:39,100 --> 01:24:42,100
compliance oriented approach comes in.

1103
01:24:42,100 --> 01:24:44,100
All of these functions will review

1104
01:24:44,100 --> 01:24:46,100
change orders and have some role in

1105
01:24:46,100 --> 01:24:49,100
looking at them. They are looking at

1106
01:24:49,100 --> 01:24:52,100
them individually, and it seems to be

1107
01:24:52,100 --> 01:24:53,100
mostly compliant-oriented view. There

1108
01:24:53,100 --> 01:24:57,100
are very few instances where anyone has

1109
01:24:57,100 --> 01:24:58,100
the opportunity, access to all of the

1110
01:24:58,100 --> 01:25:00,100
information to independently look at

1111
01:25:00,100 --> 01:25:03,100
change orders in a systematic

1112
01:25:03,100 --> 01:25:05,100
pattern-driven way to look for fraud,

1113
01:25:05,100 --> 01:25:08,100
waste and abuse. If you look at single

1114
01:25:08,100 --> 01:25:11,100
change order for compliance, it may

1115
01:25:11,100 --> 01:25:13,100
well be heavily scrutinized by these

1116
01:25:13,100 --> 01:25:15,100
individuals and that is quite a

1117
01:25:15,100 --> 01:25:17,100
positive function. There is a limited

1118
01:25:17,100 --> 01:25:19,100
occurrence of anyone stepping back and

1119
01:25:19,100 --> 01:25:22,100
looking at it. Our recommendation is

1120
01:25:22,100 --> 01:25:25,100
for internal Audit Division to take a

1121
01:25:25,100 --> 01:25:27,100
stronger lead in this, talking with

1122
01:25:27,100 --> 01:25:29,100
them, they had already had some of this

1123
01:25:29,100 --> 01:25:32,100
in the works. So I don't know exactly

1124
01:25:32,100 --> 01:25:34,100
where they are today, because this

1125
01:25:34,100 --> 01:25:36,100
audit work occurred a while ago, so I

1126
01:25:36,100 --> 01:25:37,100
don't want to speak too much to their

1127
01:25:37,100 --> 01:25:39,100
current plans, but they had already

1128
01:25:39,100 --> 01:25:42,100
started talking about how to have a

1129
01:25:42,100 --> 01:25:44,100
more active role. One of the reasons

1130
01:25:44,100 --> 01:25:46,100
it's difficult for them to do it, or

1131
01:25:46,100 --> 01:25:49,100
others within BART, is because not

1132
01:25:49,100 --> 01:25:50,100
everyone has access to all of the

1133
01:25:50,100 --> 01:25:53,100
information systems that they need and

1134
01:25:53,100 --> 01:25:55,100
reliant on information from the Office

1135
01:25:55,100 --> 01:25:58,100
of Infrastructure Delivery. So cutting

1136
01:25:59,100 --> 01:26:01,100
into our recommendations giving access

1137
01:26:01,100 --> 01:26:03,100
to the internal Audit Division for

1138
01:26:03,100 --> 01:26:05,100
frankly whoever is charged with this to

1139
01:26:05,100 --> 01:26:06,100
have access to all of the information

1140
01:26:06,100 --> 01:26:08,100
systems to get it in a read only

1141
01:26:08,100 --> 01:26:11,100
fashion and so that they can do this

1142
01:26:11,100 --> 01:26:13,100
monitoring concurrently. We're not

1143
01:26:13,100 --> 01:26:16,100
recommending a new step in the approval

1144
01:26:16,100 --> 01:26:19,601
of each change order. We are

1145
01:26:20,100 --> 01:26:21,100
recommending ongoing concurrent

1146
01:26:21,100 --> 01:26:23,100
monitoring of all of the change order

1147
01:26:23,100 --> 01:26:24,100
activity. So that change orders don't

1148
01:26:24,100 --> 01:26:26,100
have to be delayed by one more review.

1149
01:26:26,100 --> 01:26:28,100
It's already a very lengthily process

1150
01:26:28,100 --> 01:26:31,100
and that could add time to it. We're

1151
01:26:31,100 --> 01:26:33,100
recommending concurrent review, and

1152
01:26:33,100 --> 01:26:35,100
looking at patterns and trends as well

1153
01:26:35,100 --> 01:26:38,100
and having access to the information.

1154
01:26:38,100 --> 01:26:40,100
Getting ahead to finding 2, this is

1155
01:26:40,100 --> 01:26:43,100
where some of the challenges will

1156
01:26:43,100 --> 01:26:44,100
persist for the time being as well,

1157
01:26:44,100 --> 01:26:46,100
even if folks have access to all of the

1158
01:26:46,100 --> 01:26:49,100
information. A lot of the information

1159
01:26:49,100 --> 01:26:51,100
is locked up in systems that don't talk

1160
01:26:51,100 --> 01:26:54,100
to each other. This is common in any

1161
01:26:54,100 --> 01:26:56,100
organization. There are always digital

1162
01:26:56,100 --> 01:26:58,100
systems that end up functioning in

1163
01:26:58,100 --> 01:27:00,100
silos even with the best intentions.

1164
01:27:00,100 --> 01:27:02,100
There are two systems to talk about, as

1165
01:27:02,100 --> 01:27:05,100
you are probably familiar PeopleSoft is

1166
01:27:05,100 --> 01:27:08,601
the main enterprise system used, but

1167
01:27:10,100 --> 01:27:13,100
WongCMS is a repository used for

1168
01:27:13,100 --> 01:27:15,100
project management information and most

1169
01:27:15,100 --> 01:27:17,100
of the change order details are

1170
01:27:17,100 --> 01:27:19,100
stored there in the documents. The

1171
01:27:19,100 --> 01:27:22,100
way these two systems are designed they

1172
01:27:22,100 --> 01:27:25,601
use different field names. There's as

1173
01:27:26,100 --> 01:27:28,100
I mentioned credits, allowances,

1174
01:27:28,100 --> 01:27:30,100
options. Not all of those are properly

1175
01:27:30,100 --> 01:27:32,100
differentiated in these two systems,,

1176
01:27:32,100 --> 01:27:34,100
nor aligned with each other. So you

1177
01:27:34,100 --> 01:27:37,100
could imagine if you needed to

1178
01:27:37,100 --> 01:27:38,100
understand overall project spending,

1179
01:27:38,100 --> 01:27:40,100
you would think oh, I could get that

1180
01:27:40,100 --> 01:27:41,100
information from PeopleSoft very

1181
01:27:41,100 --> 01:27:43,100
easily. And then you think oh, well

1182
01:27:43,100 --> 01:27:45,100
let see how many of these are change

1183
01:27:45,100 --> 01:27:48,100
orders? That is not a possible

1184
01:27:48,100 --> 01:27:49,100
function today. So what needs to

1185
01:27:49,100 --> 01:27:51,100
happen, if you have a question about

1186
01:27:51,100 --> 01:27:53,100
change orders is someone will need to

1187
01:27:53,100 --> 01:27:55,100
manually look at the information and

1188
01:27:55,100 --> 01:27:58,100
compile that from what is in WongCMS.

1189
01:27:58,100 --> 01:28:00,100
So there's an opportunity here, because

1190
01:28:00,100 --> 01:28:03,100
it's our understanding that WongCMS is

1191
01:28:03,100 --> 01:28:06,601
in the process of an upgrade

1192
01:28:08,100 --> 01:28:10,100
replacement, to when that is replaced

1193
01:28:10,100 --> 01:28:12,100
to make them integrated and unify the

1194
01:28:12,100 --> 01:28:15,100
field and improve governance. So our

1195
01:28:15,100 --> 01:28:16,100
recommendations are centered around the

1196
01:28:16,100 --> 01:28:19,100
center to do that. We have a third

1197
01:28:19,100 --> 01:28:21,100
recommendation here, which may have

1198
01:28:21,100 --> 01:28:23,100
already been considered, but because so

1199
01:28:23,100 --> 01:28:27,100
much of this information is tied up in

1200
01:28:27,100 --> 01:28:31,201
WongCMS if and when it's replaced that

1201
01:28:33,100 --> 01:28:34,100
historic information is critical with

1202
01:28:34,100 --> 01:28:36,100
the long length of projects it would be

1203
01:28:36,100 --> 01:28:40,801
a major loss not to have access to

1204
01:28:41,100 --> 01:28:43,100
that. The third finding talks again

1205
01:28:43,100 --> 01:28:46,100
about some inconsistent records. The

1206
01:28:51,100 --> 01:28:54,601
Office of Civil Rights sanctioned small

1207
01:28:57,100 --> 01:28:59,100
business participation programs when we

1208
01:28:59,100 --> 01:29:02,100
did our sampling of 41 change orders in

1209
01:29:02,100 --> 01:29:04,100
this case, the Office of Civil Rights

1210
01:29:04,100 --> 01:29:05,100
could probably only eight of them from

1211
01:29:05,100 --> 01:29:08,100
their own records and 33 they needed to

1212
01:29:08,100 --> 01:29:09,100
request from project teams. Meaning

1213
01:29:09,100 --> 01:29:12,100
that while they were charged with

1214
01:29:12,100 --> 01:29:14,100
looking at these historically, they had

1215
01:29:14,100 --> 01:29:16,100
no access to them. It's our

1216
01:29:16,100 --> 01:29:18,100
understanding that a major problem was

1217
01:29:18,100 --> 01:29:20,100
simply just not getting emailed when

1218
01:29:20,100 --> 01:29:22,100
the change orders happened. Our

1219
01:29:22,100 --> 01:29:25,100
proposal is simple, update standard

1220
01:29:25,100 --> 01:29:26,100
operating procedures and give the

1221
01:29:26,100 --> 01:29:29,100
Office of Civil Rights access to this

1222
01:29:29,100 --> 01:29:30,100
information in a read-only capacity, so

1223
01:29:30,100 --> 01:29:34,100
they don't have to ask for it. It will

1224
01:29:34,100 --> 01:29:37,100
be reduce friction and hopefully save

1225
01:29:37,100 --> 01:29:38,100
everybody time and give them an

1226
01:29:38,100 --> 01:29:40,100
opportunity to perform their

1227
01:29:40,100 --> 01:29:42,100
functions better. And finally our

1228
01:29:42,100 --> 01:29:43,100
fourth finding is about improving

1229
01:29:43,100 --> 01:29:46,100
opportunities in Planning and design.

1230
01:29:46,100 --> 01:29:48,100
Of our samples about 5% of them

1231
01:29:48,100 --> 01:29:50,100
appeared to have avoidable errors. I

1232
01:29:50,100 --> 01:29:52,100
have to caveat this. I'm not an

1233
01:29:52,100 --> 01:29:55,601
engineer. So I do not like

1234
01:29:56,100 --> 01:29:57,100
Monday-morning quarterbacking here.

1235
01:29:57,100 --> 01:30:02,401
When we looked at a few of them, cases

1236
01:30:03,100 --> 01:30:06,100
for example, known 50-year-old conduit

1237
01:30:06,100 --> 01:30:09,100
that was underground, just a simple

1238
01:30:09,100 --> 01:30:13,100
Google search will tell you 50 years is

1239
01:30:13,100 --> 01:30:17,801
past its useful life. When it was dug

1240
01:30:18,100 --> 01:30:20,100
up, oh, yes, the conduit is corroded

1241
01:30:20,100 --> 01:30:22,100
and needed to be replaced. And

1242
01:30:22,100 --> 01:30:24,100
Planning for these types of things

1243
01:30:24,100 --> 01:30:27,601
could save both time and money.

1244
01:30:28,100 --> 01:30:30,100
Jumping back here, during the audit

1245
01:30:30,100 --> 01:30:32,100
period about $2.7 million of what

1246
01:30:32,100 --> 01:30:35,601
appeared to be avoidable costs. Best

1247
01:30:37,100 --> 01:30:39,100
practices suggest that doing better

1248
01:30:39,100 --> 01:30:42,100
Planning, even though there's a cost

1249
01:30:42,100 --> 01:30:44,100
to do subsurface investigations and

1250
01:30:44,100 --> 01:30:46,100
understand what is underground where

1251
01:30:46,100 --> 01:30:49,100
you finalize your plans, tends to have

1252
01:30:49,100 --> 01:30:51,100
a 4:1 return on investment. So even

1253
01:30:51,100 --> 01:30:54,100
though there would be an increased cost

1254
01:30:54,100 --> 01:30:55,100
with more subsurface investigations

1255
01:30:55,100 --> 01:30:58,100
doing so would have a savings over the

1256
01:30:58,100 --> 01:30:59,100
long-term. It's our understanding that

1257
01:30:59,100 --> 01:31:02,100
this is something that the Office of

1258
01:31:02,100 --> 01:31:04,100
Infrastructure Delivery was already

1259
01:31:04,100 --> 01:31:05,100
thinking about. It's very logical and

1260
01:31:05,100 --> 01:31:08,100
again, not as an engineer myself, I

1261
01:31:08,100 --> 01:31:10,100
feel silly even mentioning it because

1262
01:31:10,100 --> 01:31:12,100
I'm sure all of the professionals have

1263
01:31:12,100 --> 01:31:15,100
already been thinking heavily about

1264
01:31:16,100 --> 01:31:17,100
this, but reinforces the opportunity

1265
01:31:17,100 --> 01:31:18,100
for more Planning and investment

1266
01:31:18,100 --> 01:31:22,201
upfront to save time and money later.

1267
01:31:25,100 --> 01:31:27,100
And so that is the end of my

1268
01:31:27,100 --> 01:31:29,100
presentation. I will open up to any

1269
01:31:29,100 --> 01:31:32,100
questions that we might be able to

1270
01:31:32,100 --> 01:31:33,100
answer.

1271
01:31:33,100 --> 01:31:36,100
>> Thank you. I appreciate the

1272
01:31:36,100 --> 01:31:37,100
presentation. Do we have any questions

1273
01:31:37,100 --> 01:31:40,100
from the Board? Director Foley?

1274
01:31:43,100 --> 01:31:44,100
>> Thank you, President Hernandez.

1275
01:31:44,100 --> 01:31:48,100
Thank you for the presentation. I come

1276
01:31:48,100 --> 01:31:51,100
away with more questions than answers.

1277
01:31:51,100 --> 01:31:55,100
So I will ask a few. First off, how

1278
01:31:55,100 --> 01:31:58,601
does this report intersect with the

1279
01:31:59,100 --> 01:32:01,100
Bond Oversight Committee? Where is

1280
01:32:01,100 --> 01:32:04,100
this, you know, really directed to

1281
01:32:04,100 --> 01:32:07,100
what they do and how they look at

1282
01:32:07,100 --> 01:32:08,100
capital spending?

1283
01:32:08,100 --> 01:32:11,100
>> We didn't do this audit with this

1284
01:32:11,100 --> 01:32:12,100
perspective. It wasn't part of the

1285
01:32:12,100 --> 01:32:14,100
scope.

1286
01:32:14,100 --> 01:32:15,100
>> Is this something we will share

1287
01:32:15,100 --> 01:32:17,100
with them?

1288
01:32:17,100 --> 01:32:18,100
>> We certainly can, yeah.

1289
01:32:18,100 --> 01:32:22,100
>> I would think as the overseers of

1290
01:32:22,100 --> 01:32:25,100
our capital spending, that they would

1291
01:32:25,100 --> 01:32:28,100
want to understand this. So on a very

1292
01:32:28,100 --> 01:32:30,100
high-level we look at the change order

1293
01:32:30,100 --> 01:32:33,100
amounts compared to the contract

1294
01:32:34,100 --> 01:32:35,100
amount. When we're looking at the root

1295
01:32:35,100 --> 01:32:37,100
cause of change order need? In other

1296
01:32:37,100 --> 01:32:40,100
words, is this an -- error -- I don't

1297
01:32:40,100 --> 01:32:43,100
want to say error, but is there a

1298
01:32:43,100 --> 01:32:45,100
finding on our part as we go through

1299
01:32:45,100 --> 01:32:47,100
construction? Is this a contractor

1300
01:32:47,100 --> 01:32:49,100
issue? Because I would think that not

1301
01:32:49,100 --> 01:32:52,100
all change orders are created equal.

1302
01:32:52,100 --> 01:32:56,801
So how do we determine ones that are

1303
01:32:58,100 --> 01:32:59,100
necessary, from ones preventable?

1304
01:32:59,100 --> 01:33:03,201
>> I think I will let Julian answer

1305
01:33:04,100 --> 01:33:05,100
that one because he is closer to the

1306
01:33:05,100 --> 01:33:06,100
work.

1307
01:33:06,100 --> 01:33:07,100
>> Thank you, Director. It's

1308
01:33:07,100 --> 01:33:10,100
difficult to say in some cases. This is

1309
01:33:10,100 --> 01:33:13,100
a bit of a deflection. I apologize,

1310
01:33:13,100 --> 01:33:14,100
it's getting the information better so

1311
01:33:14,100 --> 01:33:17,100
that that can be answered more often.

1312
01:33:17,100 --> 01:33:21,100
Because it's difficult to know, in all cases.

1313
01:33:21,100 --> 01:33:23,100
>> It sounds like in cases where we

1314
01:33:23,100 --> 01:33:26,100
get a credit, we're actually reducing

1315
01:33:26,100 --> 01:33:28,100
the scope of work originally bid for?

1316
01:33:28,100 --> 01:33:29,100
>> Correct.

1317
01:33:29,100 --> 01:33:31,100
>> So we're getting less bang for the

1318
01:33:31,100 --> 01:33:34,100
buck, if you will, because of the

1319
01:33:34,100 --> 01:33:37,100
change order eating away at what our

1320
01:33:37,100 --> 01:33:39,100
approve dollar amount was, is that fair?

1321
01:33:39,100 --> 01:33:42,100
>> I'm not sure. I'm not sure if what

1322
01:33:42,100 --> 01:33:44,100
you mean by bang for the buck? When

1323
01:33:44,100 --> 01:33:46,100
they reduce something there could be so

1324
01:33:46,100 --> 01:33:47,100
much different reasons why they do it.

1325
01:33:47,100 --> 01:33:51,100
So it's kind of like -- I hate -- like

1326
01:33:51,100 --> 01:33:53,100
what Julian was saying deflecting a

1327
01:33:53,100 --> 01:33:57,100
little bit. If we look at just the TBT

1328
01:33:57,100 --> 01:34:00,601
descope, which was over $30 million was

1329
01:34:02,100 --> 01:34:05,100
quite significant. The question what

1330
01:34:05,100 --> 01:34:08,100
did they remove and Julian reviewed

1331
01:34:08,100 --> 01:34:10,100
those. I don't know off the top of my

1332
01:34:10,100 --> 01:34:12,100
head, but it depends upon did we really

1333
01:34:12,100 --> 01:34:14,100
need that to begin with or some

1334
01:34:14,100 --> 01:34:16,100
logistically reason it had to come out?

1335
01:34:16,100 --> 01:34:19,100
So it just really depends. Yes, we're

1336
01:34:19,100 --> 01:34:23,801
not getting exactly what we set out to

1337
01:34:26,100 --> 01:34:28,100
do initially when we descope?

1338
01:34:28,100 --> 01:34:30,100
>> So we did a scope of work with

1339
01:34:30,100 --> 01:34:33,100
these credits it sounds like that scope

1340
01:34:33,100 --> 01:34:34,100
is reduced.

1341
01:34:34,100 --> 01:34:35,100
>> Yes.

1342
01:34:35,100 --> 01:34:36,100
>> That we're actually not getting

1343
01:34:36,100 --> 01:34:37,100
what we approved as a Board.

1344
01:34:37,100 --> 01:34:39,100
>> Yes.

1345
01:34:39,100 --> 01:34:40,100
>> Okay.

1346
01:34:40,100 --> 01:34:41,100
>> Okay.

1347
01:34:41,100 --> 01:34:45,100
>> What I would like to see going

1348
01:34:45,100 --> 01:34:48,100
forward is as we approve contracts here

1349
01:34:48,100 --> 01:34:52,100
at the Board, if we can have some sort

1350
01:34:52,100 --> 01:34:55,100
of running list of you approved a

1351
01:34:55,100 --> 01:34:59,201
project for X amount of dollars, here's

1352
01:35:00,100 --> 01:35:01,100
the change order amounts through the

1353
01:35:01,100 --> 01:35:03,100
life of the contract. For me it would

1354
01:35:03,100 --> 01:35:06,100
just be things that we have approved at

1355
01:35:06,100 --> 01:35:08,100
this level, probably want to see a

1356
01:35:08,100 --> 01:35:10,100
bigger picture. I would be interested

1357
01:35:10,100 --> 01:35:13,100
to see how what we approved actually

1358
01:35:13,100 --> 01:35:15,100
changes during the life of the

1359
01:35:15,100 --> 01:35:17,100
contract, and how the scope has changed

1360
01:35:17,100 --> 01:35:19,100
during the life of the contract. So

1361
01:35:19,100 --> 01:35:23,801
that would be -- not necessarily to the

1362
01:35:25,100 --> 01:35:27,100
IG's office, but the GM's office. I

1363
01:35:27,100 --> 01:35:28,100
think that would be helpful as a Board

1364
01:35:28,100 --> 01:35:29,100
Member.

1365
01:35:29,100 --> 01:35:32,100
>> I think it's an excellent

1366
01:35:32,100 --> 01:35:34,100
recommendation. And one of the things

1367
01:35:34,100 --> 01:35:36,100
that Julian touched on a little bit,

1368
01:35:36,100 --> 01:35:40,100
but for me, I'm always thinking of the

1369
01:35:40,100 --> 01:35:42,100
worst case fraud scenario is always at

1370
01:35:42,100 --> 01:35:46,100
the back of my head. When I see really

1371
01:35:46,100 --> 01:35:47,100
big descopes I know from my experience

1372
01:35:47,100 --> 01:35:51,100
and training that is sometimes a way

1373
01:35:51,100 --> 01:35:54,100
that that -- like associated with

1374
01:35:54,100 --> 01:35:57,100
collusion, or some sort of scheme,

1375
01:35:57,100 --> 01:35:58,100
where a contractor might bid on

1376
01:35:58,100 --> 01:36:00,100
something and intentionally bid it low,

1377
01:36:00,100 --> 01:36:02,100
because they know in advance it's going

1378
01:36:02,100 --> 01:36:04,100
to come out anyway and they can win the

1379
01:36:04,100 --> 01:36:08,100
Ward. award. That is why I worry

1380
01:36:08,100 --> 01:36:09,100
about that and why it's important that

1381
01:36:09,100 --> 01:36:13,100
you see all of the information to ask

1382
01:36:13,100 --> 01:36:16,100
probing questions like why was there

1383
01:36:16,100 --> 01:36:20,801
such a descope and the other bid items?

1384
01:36:21,100 --> 01:36:23,100
Were they many, many higher than the

1385
01:36:23,100 --> 01:36:26,100
contract who won the award? Not that

1386
01:36:26,100 --> 01:36:30,100
it's fraud, but it's an indicator of

1387
01:36:30,100 --> 01:36:32,100
potential fraud. I highly agree with

1388
01:36:32,100 --> 01:36:33,100
that, and I think it's an excellent

1389
01:36:33,100 --> 01:36:34,100
recommendation.

1390
01:36:34,100 --> 01:36:35,100
>> Thank you.

1391
01:36:35,100 --> 01:36:37,100
>> Good morning, Directors. Michael

1392
01:36:37,100 --> 01:36:40,100
Jones, Deputy General Manager and to

1393
01:36:40,100 --> 01:36:44,100
jump in and I'm catching myself cold,

1394
01:36:44,100 --> 01:36:47,100
so don't hold me to any of the

1395
01:36:47,100 --> 01:36:48,100
information, Director Foley. The

1396
01:36:48,100 --> 01:36:51,100
TransBay Tube was for 100-year storm

1397
01:36:51,100 --> 01:36:53,100
design and designed several years ago

1398
01:36:53,100 --> 01:36:56,100
and when we actually started doing the

1399
01:36:56,100 --> 01:36:58,100
work we determined that we didn't need

1400
01:36:58,100 --> 01:37:01,100
as much scope as we did, and we brought

1401
01:37:01,100 --> 01:37:03,100
that back to the Board and

1402
01:37:03,100 --> 01:37:05,100
transparently reported that.

1403
01:37:05,100 --> 01:37:06,100
>> It did go back in front of the

1404
01:37:06,100 --> 01:37:07,100
Board.

1405
01:37:07,100 --> 01:37:11,801
>> So I don't anyone to say there's a

1406
01:37:12,100 --> 01:37:14,401
$28 million descope and there's

1407
01:37:15,100 --> 01:37:17,100
collusion, because it was 100%

1408
01:37:17,100 --> 01:37:18,100
transparent.

1409
01:37:18,100 --> 01:37:22,201
>> I was just wondering from the pure

1410
01:37:23,100 --> 01:37:25,100
numbers point, how the dollar amounts

1411
01:37:25,100 --> 01:37:27,100
change and the scope changes through

1412
01:37:27,100 --> 01:37:29,100
the life of contract ? that is all I

1413
01:37:29,100 --> 01:37:30,100
have. Thank you.

1414
01:37:30,100 --> 01:37:31,100
>> Thank you. Director Ames.

1415
01:37:31,100 --> 01:37:34,100
>> I do remember that tunnel

1416
01:37:34,100 --> 01:37:37,601
discussion, and I was concerned about

1417
01:37:38,100 --> 01:37:41,100
the descope. Because I wasn't sure if

1418
01:37:41,100 --> 01:37:42,100
the seismic performance would be equal

1419
01:37:42,100 --> 01:37:45,100
to what we planned for. So I wanted to

1420
01:37:45,100 --> 01:37:49,100
get a white paper on that. But we

1421
01:37:49,100 --> 01:37:51,100
never got confirmation. So I do agree

1422
01:37:51,100 --> 01:37:55,201
that descoping is a concern. I would

1423
01:37:56,100 --> 01:37:58,100
like to see BART or engineering Staff

1424
01:37:58,100 --> 01:38:01,100
to come up with a way, if they do think

1425
01:38:01,100 --> 01:38:05,100
there's more to be done with the price,

1426
01:38:05,100 --> 01:38:09,201
maybe we can consider descoping at the

1427
01:38:10,100 --> 01:38:14,100
award of contract? I have only done

1428
01:38:14,100 --> 01:38:17,100
that one in my career, but if you know

1429
01:38:17,100 --> 01:38:20,100
you don't have enough funding you have

1430
01:38:20,100 --> 01:38:23,601
alternative items to descope or maybe

1431
01:38:24,100 --> 01:38:27,100
working with the contractor to descope

1432
01:38:27,100 --> 01:38:29,100
or before the contract comes to the

1433
01:38:29,100 --> 01:38:30,100
Board, which is difficult, because you

1434
01:38:30,100 --> 01:38:32,100
are negotiating with the contractor

1435
01:38:32,100 --> 01:38:34,100
after the bid came in. You know

1436
01:38:34,100 --> 01:38:36,100
upfront what would be potentially

1437
01:38:36,100 --> 01:38:38,100
removed, given the constraints on the

1438
01:38:38,100 --> 01:38:42,100
budget. And then the other issue which

1439
01:38:42,100 --> 01:38:43,100
I do appreciate is maybe you could go

1440
01:38:43,100 --> 01:38:45,100
to that slide where it's got all the

1441
01:38:45,100 --> 01:38:49,100
check marks that shows you have got

1442
01:38:49,100 --> 01:38:51,100
some review of other Departments. I

1443
01:38:51,100 --> 01:38:55,100
guess we have this audit -- sorry,

1444
01:38:55,100 --> 01:38:57,100
let's see. The internal Audit Division

1445
01:38:57,100 --> 01:39:00,100
would potentially look at change

1446
01:39:00,100 --> 01:39:03,100
orders, I guess. Is that what we're

1447
01:39:03,100 --> 01:39:05,100
suggesting here?

1448
01:39:05,100 --> 01:39:07,100
Overview of the change orders?

1449
01:39:07,100 --> 01:39:09,100
>> Correct, they are currently

1450
01:39:09,100 --> 01:39:11,100
reviewing aspects of change orders

1451
01:39:11,100 --> 01:39:12,100
especially from an individual change

1452
01:39:12,100 --> 01:39:15,601
order by change order signoff approach.

1453
01:39:16,100 --> 01:39:19,100
But giving them the clear policy --

1454
01:39:19,100 --> 01:39:22,100
written policy direction to review

1455
01:39:22,100 --> 01:39:25,100
change orders at-large, and looking at

1456
01:39:25,100 --> 01:39:26,100
all change orders, and doing that

1457
01:39:26,100 --> 01:39:29,100
concurrently, because there's a risk to

1458
01:39:29,100 --> 01:39:32,601
the review process that makes the

1459
01:39:33,100 --> 01:39:36,100
review process longer and doing it

1460
01:39:36,100 --> 01:39:37,100
simultaneously.

1461
01:39:37,100 --> 01:39:41,100
>> I do like this and when I do change

1462
01:39:41,100 --> 01:39:43,100
orders I always had oversight. Some

1463
01:39:43,100 --> 01:39:46,100
would get cherry-picked because there

1464
01:39:46,100 --> 01:39:48,100
was concerns with the change order and

1465
01:39:48,100 --> 01:39:50,100
they would ask me questions if it was

1466
01:39:50,100 --> 01:39:51,100
compliant with the project? But it was

1467
01:39:51,100 --> 01:39:53,100
good to have that oversight. There was

1468
01:39:53,100 --> 01:39:55,100
a little bit of a delay, but it wasn't

1469
01:39:55,100 --> 01:39:57,100
like every change order was audited.

1470
01:39:57,100 --> 01:40:01,801
But they did look at the change orders

1471
01:40:02,100 --> 01:40:04,100
for red-flags and the Procurement

1472
01:40:04,100 --> 01:40:07,100
Department also has a good check on the

1473
01:40:07,100 --> 01:40:09,100
funding that is being used. And then

1474
01:40:09,100 --> 01:40:10,100
amount of change orders being used.

1475
01:40:10,100 --> 01:40:12,100
Because there's a lot of confusion, who

1476
01:40:12,100 --> 01:40:15,100
is managing the project? They might

1477
01:40:15,100 --> 01:40:18,100
have their own spreadsheet of their

1478
01:40:18,100 --> 01:40:20,100
accounting. But then the Procurement

1479
01:40:20,100 --> 01:40:21,100
Department doesn't have this. So it's

1480
01:40:21,100 --> 01:40:24,100
really great to see that we would -- we

1481
01:40:24,100 --> 01:40:26,100
could consider having maybe the

1482
01:40:26,100 --> 01:40:28,100
procurement or whoever is looking at

1483
01:40:28,100 --> 01:40:32,100
the financing of the contract also that

1484
01:40:32,100 --> 01:40:33,100
would be a different Department. Then

1485
01:40:33,100 --> 01:40:35,100
you have this internal Audit Division.

1486
01:40:35,100 --> 01:40:38,100
So I think we should have those two

1487
01:40:38,100 --> 01:40:41,601
Departments looking at change orders in

1488
01:40:42,100 --> 01:40:45,100
a systematic way, so we're not leaving

1489
01:40:45,100 --> 01:40:49,100
up to the Project Managers to control

1490
01:40:49,100 --> 01:40:51,401
everything. Basically they are

1491
01:40:52,100 --> 01:40:53,100
controlling the change order process

1492
01:40:53,100 --> 01:40:55,100
and the budget. So there's a need for

1493
01:40:55,100 --> 01:40:58,601
oversight. So I'm hopeful Staff comes

1494
01:41:03,100 --> 01:41:04,100
back to elaborate on the improvements

1495
01:41:04,100 --> 01:41:07,100
and get more consistent software, so

1496
01:41:07,100 --> 01:41:08,100
everything is documented in one place,

1497
01:41:08,100 --> 01:41:10,100
and people can understand -- you don't

1498
01:41:10,100 --> 01:41:12,100
have to have your own private file to

1499
01:41:12,100 --> 01:41:16,100
document what is going on with the

1500
01:41:16,100 --> 01:41:18,100
project. Thank you.

1501
01:41:20,100 --> 01:41:22,100
>> All right, VP Wright.

1502
01:41:22,100 --> 01:41:25,100
>> Thank you. Thank you for the

1503
01:41:25,100 --> 01:41:27,100
presentation as always I appreciate the

1504
01:41:27,100 --> 01:41:28,100
rigor of your oversight and the work

1505
01:41:28,100 --> 01:41:31,100
that goes into these audits. We

1506
01:41:31,100 --> 01:41:33,100
already touched on this in Committee,

1507
01:41:33,100 --> 01:41:35,100
so I won't get into all of that, but I

1508
01:41:35,100 --> 01:41:39,100
thought it might be helpful if BART's

1509
01:41:39,100 --> 01:41:41,100
management wants to share anything

1510
01:41:41,100 --> 01:41:43,100
about your responses to the findings

1511
01:41:43,100 --> 01:41:45,100
and recommendation or actions that have

1512
01:41:45,100 --> 01:41:47,100
been undertaken since the audit came

1513
01:41:47,100 --> 01:41:48,100
out?

1514
01:41:48,100 --> 01:41:49,100
>> Good morning, Director Wright. Not

1515
01:41:49,100 --> 01:41:53,100
other than we have accepted all of the

1516
01:41:53,100 --> 01:41:54,100
recommendations and internal auditing

1517
01:41:54,100 --> 01:41:57,100
Staff is working to implement

1518
01:41:58,100 --> 01:42:00,100
>> Excellent, thank you.

1519
01:42:02,100 --> 01:42:04,100
>> Director Raburn.

1520
01:42:04,100 --> 01:42:06,401
>> Thank you, President Hernandez.

1521
01:42:07,100 --> 01:42:10,601
And thank you, Claudette for pursuing

1522
01:42:12,100 --> 01:42:15,100
the audit of our change orders. Thank

1523
01:42:15,100 --> 01:42:18,601
you, Julian for your presentation. I

1524
01:42:19,100 --> 01:42:22,601
have two questions. The first revolves

1525
01:42:23,100 --> 01:42:26,100
around contingencies. And you note

1526
01:42:27,100 --> 01:42:30,100
that contingencies are allowances that

1527
01:42:30,100 --> 01:42:34,201
are built in. And my experience has

1528
01:42:35,100 --> 01:42:39,100
been that contingencies get swept up at

1529
01:42:39,100 --> 01:42:42,601
the conclusion of the project, and

1530
01:42:46,100 --> 01:42:49,100
they're gone, instead of maybe being

1531
01:42:49,100 --> 01:42:52,100
saved or reallocated to a worthy

1532
01:42:52,100 --> 01:42:56,100
project. And so my question is really

1533
01:42:56,100 --> 01:42:59,100
around did you discover any

1534
01:42:59,100 --> 01:43:02,601
contingencies that weren't swept up and

1535
01:43:03,100 --> 01:43:07,100
awarded at the conclusion of a project?

1536
01:43:07,100 --> 01:43:10,100
>> That is a good question, and I have

1537
01:43:10,100 --> 01:43:12,100
to it got a little out of scope. We

1538
01:43:12,100 --> 01:43:16,201
spent a lot of time looking and

1539
01:43:17,100 --> 01:43:18,100
tracking down change order information

1540
01:43:18,100 --> 01:43:21,601
that next level of contingencies which

1541
01:43:23,100 --> 01:43:26,100
would be have a valid place to look,

1542
01:43:26,100 --> 01:43:27,100
change orders was challenging enough to

1543
01:43:27,100 --> 01:43:29,100
get the information together.

1544
01:43:29,100 --> 01:43:33,201
>> Let me ask in your experience is

1545
01:43:35,100 --> 01:43:38,100
there a procedural mechanism for

1546
01:43:39,100 --> 01:43:42,100
example, the Office of Infrastructure

1547
01:43:43,100 --> 01:43:45,401
Delivery to reallocate contingency

1548
01:43:47,100 --> 01:43:48,100
funds?

1549
01:43:48,100 --> 01:43:50,100
>> I think that would be a good

1550
01:43:50,100 --> 01:43:51,100
suggestion. I do not know how often

1551
01:43:51,100 --> 01:43:55,100
that is happening in these cases. But

1552
01:43:55,100 --> 01:43:56,100
using those contingency fund and not

1553
01:43:56,100 --> 01:43:58,100
treating them as a certainty, I think,

1554
01:43:58,100 --> 01:44:01,100
would be the baseline expectation for

1555
01:44:01,100 --> 01:44:02,100
practices in this case.

1556
01:44:02,100 --> 01:44:05,601
>> Thank you. I'm seeing Sylvia Lamb,

1557
01:44:06,100 --> 01:44:09,100
the AGM of Our Office of Infrastructure

1558
01:44:09,100 --> 01:44:12,601
Delivery nod her head in agreement.

1559
01:44:13,100 --> 01:44:16,100
Thank you. And the other question I

1560
01:44:16,100 --> 01:44:19,601
have is really regarding the Board's

1561
01:44:21,100 --> 01:44:25,201
role. And the Board really only hears

1562
01:44:26,100 --> 01:44:29,100
about change orders sort of at the end

1563
01:44:29,100 --> 01:44:33,100
of the tailpipe. We're not part and

1564
01:44:33,100 --> 01:44:36,601
parcel part of that routine monitoring

1565
01:44:37,100 --> 01:44:41,100
that you recommend. And I do recall

1566
01:44:41,100 --> 01:44:44,100
when I first joined the Board I was

1567
01:44:44,100 --> 01:44:48,201
involved in a major project, and there

1568
01:44:49,100 --> 01:44:52,100
was involvement of Board Members on

1569
01:44:52,100 --> 01:44:55,100
Committee of oversight and we tracked

1570
01:44:55,100 --> 01:44:58,601
that project from inception to delivery.

1571
01:45:00,100 --> 01:45:03,100
I haven't seen such an effort since.

1572
01:45:03,100 --> 01:45:06,100
But by the way, the contingency on

1573
01:45:06,100 --> 01:45:10,801
that project was swept up at the end

1574
01:45:11,100 --> 01:45:14,601
without any alternative being put forth

1575
01:45:15,100 --> 01:45:18,100
to the Board. So thank you for your

1576
01:45:18,100 --> 01:45:22,100
report. And I'm inclined to agree that

1577
01:45:22,100 --> 01:45:25,100
an internal Audit Division should

1578
01:45:26,100 --> 01:45:28,100
routinely monitor all of our projects,

1579
01:45:28,100 --> 01:45:31,601
and maybe with some Board involvement.

1580
01:45:33,100 --> 01:45:35,401
>> All right, Director Ghosh.

1581
01:45:38,100 --> 01:45:42,201
>> Yes, thank you. Thank you first of

1582
01:45:44,100 --> 01:45:47,100
all, for such an amazing audit. I

1583
01:45:47,100 --> 01:45:51,100
learned so much from reading it about

1584
01:45:51,100 --> 01:45:53,100
how BART works. And I had a chance to

1585
01:45:53,100 --> 01:45:58,100
chat with Sylvia, and I think all of us

1586
01:45:58,100 --> 01:46:02,100
appreciate us looking out for BART and

1587
01:46:02,100 --> 01:46:04,100
public dollar together, which is how I

1588
01:46:04,100 --> 01:46:07,100
see the purpose of this audit. I think

1589
01:46:07,100 --> 01:46:09,100
all of the recommendations are stellar,

1590
01:46:09,100 --> 01:46:11,100
and I'm glad to hear that they have

1591
01:46:11,100 --> 01:46:12,100
been accepted. I did have a question

1592
01:46:12,100 --> 01:46:15,100
about is there a timeline for

1593
01:46:15,100 --> 01:46:17,100
implementation of those

1594
01:46:18,100 --> 01:46:20,100
recommendations?

1595
01:46:21,100 --> 01:46:24,100
I'm looking at -- yes.

1596
01:46:24,100 --> 01:46:27,100
>> Let me ask Dennis Markham, who is

1597
01:46:27,100 --> 01:46:32,401
much closer than I am, to step up to

1598
01:46:33,100 --> 01:46:35,401
the podium. Mr. Markham.

1599
01:46:39,100 --> 01:46:41,401
>> Good morning, Dennis Markham,

1600
01:46:43,100 --> 01:46:45,100
Director of Performance and audit. All

1601
01:46:45,100 --> 01:46:47,100
of the recommendations that we

1602
01:46:47,100 --> 01:46:49,100
estimated would be implemented either

1603
01:46:49,100 --> 01:46:53,100
June or July of this year. And so far

1604
01:46:53,100 --> 01:46:55,100
we're on-track of doing all of those,

1605
01:46:55,100 --> 01:46:58,100
and getting them in on-time.

1606
01:46:58,100 --> 01:47:00,100
>> That is great. Could we get a

1607
01:47:00,100 --> 01:47:04,201
little note from you when they're done?

1608
01:47:05,100 --> 01:47:06,100
We would appreciate it.

1609
01:47:06,100 --> 01:47:08,100
>> Happy to follow-up.

1610
01:47:08,100 --> 01:47:12,100
>> Thank you. I also had the same

1611
01:47:12,100 --> 01:47:14,100
question about contingency and wanted

1612
01:47:14,100 --> 01:47:19,100
to know if -- if there was a list of

1613
01:47:19,100 --> 01:47:21,100
projects that were either flagged where

1614
01:47:21,100 --> 01:47:24,100
the change orders took it over budget,

1615
01:47:24,100 --> 01:47:26,100
or were they always, you know, within

1616
01:47:26,100 --> 01:47:29,100
the budget and using up the

1617
01:47:29,100 --> 01:47:31,100
contingency? I feel like I still don't

1618
01:47:31,100 --> 01:47:33,100
have that picture, but I can also see

1619
01:47:33,100 --> 01:47:36,100
that record keeping in itself is a huge

1620
01:47:36,100 --> 01:47:38,100
challenge. So I'm hoping that we can

1621
01:47:38,100 --> 01:47:41,100
ask and get that information more

1622
01:47:41,100 --> 01:47:44,601
easily, so everybody can benefit from

1623
01:47:46,100 --> 01:47:48,100
it. And it's challenging, I think,

1624
01:47:48,100 --> 01:47:50,100
with an old system like ours to even

1625
01:47:50,100 --> 01:47:53,100
know what is under the ground every

1626
01:47:53,100 --> 01:47:56,100
time. So of course, we expect, you

1627
01:47:56,100 --> 01:48:00,100
know, I don't know what -- when I did

1628
01:48:00,100 --> 01:48:03,601
my house, it's like 100-year-old house,

1629
01:48:05,100 --> 01:48:06,100
130-year-old now. There's surprises

1630
01:48:06,100 --> 01:48:08,100
all the time and that is why we have

1631
01:48:08,100 --> 01:48:09,100
contingencies. So we have to just

1632
01:48:09,100 --> 01:48:13,100
accept that is part of how we do work

1633
01:48:13,100 --> 01:48:16,100
on our systems. And I agree that you

1634
01:48:16,100 --> 01:48:18,100
know, we can look at it ahead of time,

1635
01:48:18,100 --> 01:48:22,100
but that might mean the bid would go

1636
01:48:22,100 --> 01:48:26,801
up. So it's hard. We're all trying to

1637
01:48:27,100 --> 01:48:28,100
game contractors everybody gains the

1638
01:48:28,100 --> 01:48:30,100
system to make sure you profit and get

1639
01:48:30,100 --> 01:48:32,100
the project. So I think good record

1640
01:48:32,100 --> 01:48:34,100
keeping and trends is what we should be

1641
01:48:34,100 --> 01:48:37,100
looking at, even more than project by

1642
01:48:37,100 --> 01:48:40,100
project. And we should do our best to

1643
01:48:40,100 --> 01:48:41,100
make sure that we understand the

1644
01:48:41,100 --> 01:48:44,100
reasons for these change orders and how

1645
01:48:44,100 --> 01:48:48,100
we can leverage the amount of power

1646
01:48:48,100 --> 01:48:51,100
that we have as a big agency that

1647
01:48:51,100 --> 01:48:55,100
spends a lot of money on these to even

1648
01:48:55,100 --> 01:48:57,100
change industry standards. My last

1649
01:48:57,100 --> 01:49:00,100
question, again, I think for

1650
01:49:01,100 --> 01:49:04,601
management, is with descoping, is a

1651
01:49:05,100 --> 01:49:08,100
certain percentage off the overall

1652
01:49:08,100 --> 01:49:10,100
budget at which point it has to go back

1653
01:49:10,100 --> 01:49:12,100
to bid? Because when you are putting

1654
01:49:12,100 --> 01:49:15,100
something out to bid, and you're

1655
01:49:15,100 --> 01:49:17,100
expecting all of these different sort

1656
01:49:17,100 --> 01:49:21,100
of parts of the project, one big part

1657
01:49:21,100 --> 01:49:23,100
goes away and maybe a different

1658
01:49:23,100 --> 01:49:25,100
contractor may have been better at

1659
01:49:25,100 --> 01:49:27,100
providing the different parts?

1660
01:49:27,100 --> 01:49:30,100
Of course the TransBay Tube in the

1661
01:49:30,100 --> 01:49:31,100
grand scheme of things was a small

1662
01:49:31,100 --> 01:49:33,100
amount for the overall amount, but I'm

1663
01:49:33,100 --> 01:49:36,100
curious if we have any best practice,

1664
01:49:36,100 --> 01:49:38,100
or guidance around when it goes back --

1665
01:49:38,100 --> 01:49:43,100
is forced to go back to bid, if there's

1666
01:49:43,100 --> 01:49:45,100
a descoping that comes up in the early

1667
01:49:45,100 --> 01:49:48,100
days, or even later on?

1668
01:49:48,100 --> 01:49:50,100
>> So I will look to my colleague here

1669
01:49:50,100 --> 01:49:53,100
to my right, Jeana, to help me if I

1670
01:49:53,100 --> 01:49:55,100
mess this up. I don't believe we have

1671
01:49:55,100 --> 01:49:57,100
any regulations, any BART or

1672
01:49:57,100 --> 01:49:58,100
procurement regulations that requires

1673
01:49:58,100 --> 01:50:01,100
us to go back and re-bid, if we

1674
01:50:01,100 --> 01:50:03,100
significantly descope a project. I

1675
01:50:03,100 --> 01:50:05,100
don't think that exists.

1676
01:50:05,100 --> 01:50:08,100
>> I can confirm that is generally

1677
01:50:08,100 --> 01:50:10,100
correct, yes.

1678
01:50:10,100 --> 01:50:12,100
>> I guess that is the only thing that

1679
01:50:12,100 --> 01:50:16,100
gives me pause is just to make sure

1680
01:50:16,100 --> 01:50:20,100
that we understand the project, as much

1681
01:50:20,100 --> 01:50:23,100
as possible where there's no

1682
01:50:23,100 --> 01:50:26,100
significant descoping, where going back

1683
01:50:26,100 --> 01:50:28,100
to Director Foley's comment about

1684
01:50:28,100 --> 01:50:32,100
making sure that it never appears as

1685
01:50:32,100 --> 01:50:34,100
collusion of any kind; that you are

1686
01:50:34,100 --> 01:50:35,100
putting forward a certain kind of

1687
01:50:35,100 --> 01:50:38,100
project to bid and the project changes

1688
01:50:38,100 --> 01:50:41,100
substantially, but we're still keeping

1689
01:50:42,100 --> 01:50:43,100
the same contractor. I'm not saying

1690
01:50:43,100 --> 01:50:47,100
that is happening, to be clear. This

1691
01:50:47,100 --> 01:50:51,100
is all proactive trying to make sure

1692
01:50:51,100 --> 01:50:54,100
that -- yeah. Thank you.

1693
01:50:55,100 --> 01:50:57,100
>> Director Li.

1694
01:50:57,100 --> 01:51:00,601
>> Thank you. Just had some general

1695
01:51:02,100 --> 01:51:04,100
comment and one question. First, I

1696
01:51:04,100 --> 01:51:05,100
know that every one of these

1697
01:51:05,100 --> 01:51:07,100
performance audits is a huge amount of

1698
01:51:07,100 --> 01:51:10,100
work not only for the OIG and our

1699
01:51:10,100 --> 01:51:13,100
consultants, but also for the Staff who

1700
01:51:13,100 --> 01:51:16,100
are interviewed, are providing lots of

1701
01:51:16,100 --> 01:51:17,100
information, you know? Engaging in

1702
01:51:17,100 --> 01:51:19,100
back and forth and most importantly, I

1703
01:51:19,100 --> 01:51:22,100
really want to thank BART management

1704
01:51:22,100 --> 01:51:23,100
for accepting all of the

1705
01:51:23,100 --> 01:51:25,100
recommendations and for the work that

1706
01:51:25,100 --> 01:51:28,100
has already begun to implement those

1707
01:51:28,100 --> 01:51:29,100
recommendations. I at the end of the

1708
01:51:29,100 --> 01:51:31,100
very important for the processes to be

1709
01:51:31,100 --> 01:51:34,100
collaborative and to acknowledge every

1710
01:51:34,100 --> 01:51:35,100
single party is singularly focused on

1711
01:51:35,100 --> 01:51:36,100
improving BART. That is what we're

1712
01:51:36,100 --> 01:51:41,100
trying to get to. So that is all good.

1713
01:51:41,100 --> 01:51:44,601
And also, to Claudette, and your

1714
01:51:45,100 --> 01:51:47,100
office, I'm very appreciative of the

1715
01:51:47,100 --> 01:51:49,100
cadence of these performance audits.

1716
01:51:49,100 --> 01:51:51,100
These reports are exactly what we

1717
01:51:51,100 --> 01:51:52,100
envisioned for this office to be

1718
01:51:52,100 --> 01:51:54,100
focused on when we were going through

1719
01:51:54,100 --> 01:51:56,100
the hiring process what we had said we

1720
01:51:56,100 --> 01:52:00,100
wanted our OIG to be focused on. So

1721
01:52:00,100 --> 01:52:03,100
it's a huge amount of work for

1722
01:52:03,100 --> 01:52:05,100
everyone, and we're seeing the results

1723
01:52:05,100 --> 01:52:09,100
that are really informative for us as a

1724
01:52:09,100 --> 01:52:11,100
Board. Second, I think it's really

1725
01:52:11,100 --> 01:52:14,100
important that we're doing these

1726
01:52:14,100 --> 01:52:17,100
performance audits now, when things

1727
01:52:17,100 --> 01:52:19,100
aren't breaking down. I would say sort

1728
01:52:19,100 --> 01:52:22,100
of like trying to drink a lot of water

1729
01:52:22,100 --> 01:52:25,100
when you are already dehydrated or

1730
01:52:25,100 --> 01:52:28,100
trying to go to marriage counseling

1731
01:52:28,100 --> 01:52:30,100
when somebody is I want a divorce.

1732
01:52:30,100 --> 01:52:32,100
Sort of hard to fix things at that

1733
01:52:32,100 --> 01:52:34,100
point. So I want to be clear that the

1734
01:52:34,100 --> 01:52:37,100
top line on slide 7 is something that I

1735
01:52:37,100 --> 01:52:39,100
hope BART management and Sylvia and

1736
01:52:39,100 --> 01:52:41,100
Shane's teams are particularly proud of

1737
01:52:41,100 --> 01:52:44,100
that. We know that change orders are

1738
01:52:44,100 --> 01:52:47,100
in -- a necessary reality of major

1739
01:52:47,100 --> 01:52:49,100
capital projects, whether it's CBTC or

1740
01:52:49,100 --> 01:52:51,100
our power cable replacement projects,

1741
01:52:51,100 --> 01:52:54,100
but on the whole, change orders are

1742
01:52:54,100 --> 01:52:56,100
minimal. The cost increases are small,

1743
01:52:56,100 --> 01:53:00,100
and some of these change orders are

1744
01:53:00,100 --> 01:53:01,100
actually creating project savings.

1745
01:53:01,100 --> 01:53:04,100
Yes, the more detailed look is really

1746
01:53:04,100 --> 01:53:06,100
helpful to understand where there are

1747
01:53:06,100 --> 01:53:07,100
process recommendations and where there

1748
01:53:07,100 --> 01:53:10,100
are much larger variances specific

1749
01:53:15,100 --> 01:53:16,100
projects so it prevents us from getting

1750
01:53:16,100 --> 01:53:20,201
to a bad place and 15 years when

1751
01:53:21,100 --> 01:53:25,100
perhaps we're not here anymore that we

1752
01:53:25,100 --> 01:53:27,100
have a successful transit system.

1753
01:53:27,100 --> 01:53:31,801
Maybe it's not this slide. It is the

1754
01:53:32,100 --> 01:53:35,100
big chart, yes, this one. Like, this

1755
01:53:35,100 --> 01:53:37,100
is huge. This is a slide I want to

1756
01:53:37,100 --> 01:53:40,100
share with a lot of folks because I

1757
01:53:40,100 --> 01:53:43,100
think that from the general public,

1758
01:53:43,100 --> 01:53:45,100
especially, you know, there are, in

1759
01:53:45,100 --> 01:53:48,100
fact, some BART haters out there, that

1760
01:53:48,100 --> 01:53:51,100
sort of like change orders is

1761
01:53:51,100 --> 01:53:53,100
government bloat, you know? These

1762
01:53:53,100 --> 01:53:55,100
major capital projects that are wasting

1763
01:53:55,100 --> 01:53:57,100
all of these taxpayer dollars, and

1764
01:53:57,100 --> 01:54:00,100
there's no accountability. There's lot

1765
01:54:00,100 --> 01:54:03,100
of ram for improvement and we accepted

1766
01:54:03,100 --> 01:54:04,100
those recommendations and those will

1767
01:54:04,100 --> 01:54:08,801
be underway, but on the whole, BART has

1768
01:54:11,100 --> 01:54:13,100
a strong grasp on project cost and

1769
01:54:13,100 --> 01:54:15,100
using change orders as part of project

1770
01:54:15,100 --> 01:54:17,100
reality and I think is a really

1771
01:54:17,100 --> 01:54:19,100
important thing for us to acknowledge

1772
01:54:19,100 --> 01:54:21,100
here. The only question I have is sort

1773
01:54:21,100 --> 01:54:23,100
of a process one for management and

1774
01:54:23,100 --> 01:54:25,100
sort of going off of what Director

1775
01:54:25,100 --> 01:54:28,100
Ghosh had asked. I know I requested

1776
01:54:28,100 --> 01:54:30,100
this recently with the overtime audit

1777
01:54:30,100 --> 01:54:32,100
as well. But I would really like for

1778
01:54:32,100 --> 01:54:35,100
there to be some sort of follow-up

1779
01:54:35,100 --> 01:54:36,100
particularly with the implementation of

1780
01:54:36,100 --> 01:54:38,100
the recommendations being able to

1781
01:54:38,100 --> 01:54:42,100
track, you know, what is already been

1782
01:54:42,100 --> 01:54:43,100
implemented? What is in the works?

1783
01:54:43,100 --> 01:54:46,100
What might just take a little bit of

1784
01:54:46,100 --> 01:54:49,100
time? What needs to be a larger

1785
01:54:49,100 --> 01:54:52,100
conversation? So for management, is

1786
01:54:52,100 --> 01:54:54,100
this a plan how you report-back,

1787
01:54:54,100 --> 01:54:57,100
whether to the full Board or Audit

1788
01:54:57,100 --> 01:54:59,100
Committee, via email, memo or otherwise?

1789
01:54:59,100 --> 01:55:02,601
>> Director Li, we provide the OIG

1790
01:55:03,100 --> 01:55:04,100
with quarterly updates, I believe, of

1791
01:55:04,100 --> 01:55:07,100
our progress on every one. So I'm sure

1792
01:55:07,100 --> 01:55:10,100
she can share in a with the BART Board

1793
01:55:10,100 --> 01:55:11,100
on every audit, every recommendation we

1794
01:55:11,100 --> 01:55:13,100
have Staff people that provide that to

1795
01:55:13,100 --> 01:55:15,100
them on a quarterly basis.

1796
01:55:15,100 --> 01:55:17,100
>> That is excellent. I wasn't aware.

1797
01:55:17,100 --> 01:55:19,401
Claudette, is that possible?

1798
01:55:20,100 --> 01:55:23,100
>> Yes, as Deputy General Manager

1799
01:55:27,100 --> 01:55:29,100
said, we present bi-annually now, but

1800
01:55:29,100 --> 01:55:31,100
follow-up really to find the status of

1801
01:55:31,100 --> 01:55:32,100
recommendations are. One of the things

1802
01:55:32,100 --> 01:55:35,100
that I wanted to point out, I have been

1803
01:55:35,100 --> 01:55:36,100
hearing comments not only during this

1804
01:55:36,100 --> 01:55:38,100
presentation, but other presentations

1805
01:55:38,100 --> 01:55:41,100
about wanting information about where

1806
01:55:41,100 --> 01:55:43,100
the status of recommendations are. So

1807
01:55:43,100 --> 01:55:45,100
we're doing a deep-dive look at the

1808
01:55:45,100 --> 01:55:47,100
status of our recommendations and not

1809
01:55:47,100 --> 01:55:49,100
just looking at ones that are still

1810
01:55:49,100 --> 01:55:50,100
unimplemented to see the progress or

1811
01:55:50,100 --> 01:55:52,100
some way to assist to find ways to get

1812
01:55:52,100 --> 01:55:55,100
them across the finish line? But also,

1813
01:55:55,100 --> 01:55:58,100
to make sure things didn't become

1814
01:55:58,100 --> 01:56:00,100
unimplemented, which is something we

1815
01:56:00,100 --> 01:56:02,100
see from time to time. We are, I

1816
01:56:02,100 --> 01:56:04,100
think, right in the middle of betting

1817
01:56:04,100 --> 01:56:06,100
that done and hope to bring that to you

1818
01:56:06,100 --> 01:56:08,100
all and have deeper discussions where

1819
01:56:08,100 --> 01:56:10,100
things stand and make sure that you

1820
01:56:10,100 --> 01:56:12,100
have that information. As always, our

1821
01:56:12,100 --> 01:56:13,100
dashboard on our website provides

1822
01:56:13,100 --> 01:56:15,100
information on the status -- I got the

1823
01:56:15,100 --> 01:56:17,100
thumb's up.

1824
01:56:19,100 --> 01:56:22,100
>> Sorry. Okay. That is really

1825
01:56:22,100 --> 01:56:24,100
helpful, because reports are great.

1826
01:56:24,100 --> 01:56:27,100
But best reports are ones that are

1827
01:56:27,100 --> 01:56:29,100
leading to effective and helpful

1828
01:56:29,100 --> 01:56:32,100
changes, not ineffective and unhelpful

1829
01:56:32,100 --> 01:56:33,100
ones. Those are my comments. Thank

1830
01:56:33,100 --> 01:56:34,100
you so much.

1831
01:56:34,100 --> 01:56:36,401
>> Thank you. Director Flores.

1832
01:56:37,100 --> 01:56:40,100
>> Thank you all for the presentation.

1833
01:56:40,100 --> 01:56:43,100
And just want to second a lot of

1834
01:56:43,100 --> 01:56:45,100
comments from previous Directors. So I

1835
01:56:45,100 --> 01:56:47,100
will keep my remarks short. I

1836
01:56:47,100 --> 01:56:50,100
definitely want to highlight that I

1837
01:56:50,100 --> 01:56:51,100
agree with follow-up on different audit

1838
01:56:51,100 --> 01:56:53,100
reports just to see where the

1839
01:56:53,100 --> 01:56:55,100
implementation is. And definitely

1840
01:56:55,100 --> 01:56:58,100
appreciate the OIG's office doing all

1841
01:56:58,100 --> 01:57:00,100
of these audit, but also the Staff is

1842
01:57:00,100 --> 01:57:04,100
that have been involved in making sure

1843
01:57:04,100 --> 01:57:05,100
we're sharing data and information to

1844
01:57:05,100 --> 01:57:07,100
get this information to the Board. I

1845
01:57:07,100 --> 01:57:10,601
definitely also want to highlight the

1846
01:57:11,100 --> 01:57:15,100
ability, making sure that we have the

1847
01:57:15,100 --> 01:57:16,100
integration and standardization with

1848
01:57:16,100 --> 01:57:18,100
our softwares that we can take a deeper

1849
01:57:18,100 --> 01:57:20,100
dive into what is causing change

1850
01:57:20,100 --> 01:57:23,601
orders? Just for the visibility of

1851
01:57:24,100 --> 01:57:26,100
Staff and for the Board. I think for me

1852
01:57:26,100 --> 01:57:29,100
one of the takeaways from this audit:

1853
01:57:29,100 --> 01:57:33,100
One, BART has done a pretty good job

1854
01:57:33,100 --> 01:57:34,100
already, and also accepted

1855
01:57:34,100 --> 01:57:36,100
recommendations and has been

1856
01:57:36,100 --> 01:57:38,100
identifying ways to make those

1857
01:57:38,100 --> 01:57:39,100
improvements. So I just want to say

1858
01:57:39,100 --> 01:57:41,100
thank you for all of the work that has

1859
01:57:41,100 --> 01:57:43,100
been going on there and for the

1860
01:57:43,100 --> 01:57:45,100
willingness to accept those

1861
01:57:45,100 --> 01:57:46,100
recommendations, because I know when

1862
01:57:46,100 --> 01:57:48,100
people think about audits sometimes it

1863
01:57:48,100 --> 01:57:50,100
can be -- some people might think of it

1864
01:57:50,100 --> 01:57:52,100
as a scary thing. People might get in

1865
01:57:52,100 --> 01:57:55,100
trouble, or you know, you know -- you

1866
01:57:55,100 --> 01:57:57,100
pulled back behind the curtain, and

1867
01:57:57,100 --> 01:57:59,100
some people might be afraid of what is

1868
01:57:59,100 --> 01:58:03,801
behind it, but what I'm seeing is a

1869
01:58:04,100 --> 01:58:06,100
good, good numbers, good stats and

1870
01:58:06,100 --> 01:58:08,401
trends. Room for improvement,

1871
01:58:09,100 --> 01:58:11,100
definitely. But things that we can fix

1872
01:58:11,100 --> 01:58:14,601
before we get to that dehydration

1873
01:58:15,100 --> 01:58:16,100
stage. So thank you all so much and

1874
01:58:16,100 --> 01:58:19,601
look forward to seeing those updates.

1875
01:58:22,100 --> 01:58:24,100
>> Not seeing any other Directors with

1876
01:58:24,100 --> 01:58:25,100
any more questions

1877
01:58:25,100 --> 01:58:28,100
I do have a quick question with regards

1878
01:58:28,100 --> 01:58:30,100
is this the first audit change order

1879
01:58:30,100 --> 01:58:31,100
audit you have brought forward to the

1880
01:58:31,100 --> 01:58:32,100
Board?

1881
01:58:32,100 --> 01:58:33,100
>> Yes.

1882
01:58:33,100 --> 01:58:35,100
>> So moving forward, are you going to

1883
01:58:35,100 --> 01:58:38,100
do this on an annual basis?

1884
01:58:38,100 --> 01:58:40,100
>> No. That would be too much of a

1885
01:58:40,100 --> 01:58:42,100
lift for us to be able to do that. I

1886
01:58:42,100 --> 01:58:45,100
think though with the work that the

1887
01:58:45,100 --> 01:58:47,100
internal audit may be doing maybe

1888
01:58:47,100 --> 01:58:49,100
reports, but don't want to speak for

1889
01:58:49,100 --> 01:58:51,100
the General Manager on that. These

1890
01:58:51,100 --> 01:58:52,100
audits take a tremendous amount of time

1891
01:58:52,100 --> 01:58:55,100
and energy and we have a lot of things

1892
01:58:55,100 --> 01:58:56,100
on our audit plan that we need to get

1893
01:58:56,100 --> 01:58:58,100
through.

1894
01:58:59,100 --> 01:59:02,100
>> Okay. Thank you. And maybe we'll

1895
01:59:02,100 --> 01:59:03,100
have further conversation moving

1896
01:59:03,100 --> 01:59:06,100
forward as we get some more information

1897
01:59:06,100 --> 01:59:08,100
with regards to whether it's this audit

1898
01:59:08,100 --> 01:59:09,100
or other audits in the future. Thank

1899
01:59:09,100 --> 01:59:13,100
you for your time. I will let our Mag

1900
01:59:13,100 --> 01:59:15,100
move forward and she will call any

1901
01:59:15,100 --> 01:59:19,100
public comment that is in the public,

1902
01:59:19,100 --> 01:59:21,100
or online.

1903
01:59:21,100 --> 01:59:23,100
>> Okay. Glen Overton, come to the

1904
01:59:23,100 --> 01:59:25,100
podium, please.

1905
01:59:46,100 --> 01:59:49,100
>> Every once in a while you have to

1906
01:59:49,100 --> 01:59:50,100
dust off your books and keep

1907
01:59:50,100 --> 01:59:53,601
everything in line there. Sorry, Madam

1908
01:59:57,100 --> 02:00:00,601
President, Mr. General Manager and Staff

1909
02:00:03,100 --> 02:00:07,801
, when you look at the IG, take a

1910
02:00:15,100 --> 02:00:19,801
picture of your own body. The IG is

1911
02:00:24,100 --> 02:00:28,801
like a liver, and a liver accounts in

1912
02:00:29,100 --> 02:00:32,100
realtime. You got up this morning,

1913
02:00:32,100 --> 02:00:35,601
you're happy, because of your liver.

1914
02:00:36,100 --> 02:00:39,100
You go around saying thanks to your

1915
02:00:39,100 --> 02:00:44,401
liver, an IG is a friend of the people,

1916
02:00:50,100 --> 02:00:54,201
and gets value for our tax dollars

1917
02:00:55,100 --> 02:00:58,601
every cent. The Board of Directors,

1918
02:01:04,100 --> 02:01:08,801
which is your brain, can vouch for that

1919
02:01:10,100 --> 02:01:13,100
in realtime. Integrated, in realtime.

1920
02:01:17,100 --> 02:01:21,201
It doesn't ask for a budget, it's

1921
02:01:24,100 --> 02:01:28,801
there. :again, the IG is a friend of

1922
02:01:29,100 --> 02:01:33,801
the people. And maybe the IG needs to

1923
02:01:36,100 --> 02:01:39,601
integrate with the AI. Thank you.

1924
02:01:42,100 --> 02:01:45,100
>> Okay we have two online speakers.

1925
02:01:45,100 --> 02:01:48,100
The first is Aleta Dupree. Aleta,

1926
02:01:48,100 --> 02:01:50,100
please, go ahead.

1927
02:01:50,100 --> 02:01:52,401
>> Thanks again, President Melissa

1928
02:01:53,100 --> 02:01:54,100
Hernandez and Members. Aleta Dupree,

1929
02:01:54,100 --> 02:01:58,801
for the record, she and her with team

1930
02:02:01,100 --> 02:02:03,100
folds. Very informative report. I do

1931
02:02:03,100 --> 02:02:06,100
have some issue with language, when I

1932
02:02:06,100 --> 02:02:09,100
go into finding 1. I see some

1933
02:02:09,100 --> 02:02:12,100
sentences here, such as OID effectively

1934
02:02:12,100 --> 02:02:15,100
operates without meaningful check on

1935
02:02:16,100 --> 02:02:19,100
decisions in these areas. I'm really

1936
02:02:19,100 --> 02:02:22,100
concerned about how we're framing some

1937
02:02:22,100 --> 02:02:25,601
of this language. I don't want

1938
02:02:28,100 --> 02:02:31,100
anything that OIG does to be

1939
02:02:31,100 --> 02:02:32,100
adversarial. I know if I was running a

1940
02:02:32,100 --> 02:02:34,100
Department and somebody said that to

1941
02:02:34,100 --> 02:02:36,100
me, I would be really offended. I know

1942
02:02:36,100 --> 02:02:39,100
people who work for OID, they're good

1943
02:02:39,100 --> 02:02:41,100
people. I trust them, and I would be

1944
02:02:41,100 --> 02:02:44,100
honored to eat lunch with them every

1945
02:02:44,100 --> 02:02:46,100
day, any day. So how can we make sure

1946
02:02:46,100 --> 02:02:50,100
that we frame any of this language in a

1947
02:02:50,100 --> 02:02:53,601
way that doesn't imply adversary, I

1948
02:03:02,100 --> 02:03:04,100
want to be clear, change orders are a

1949
02:03:04,100 --> 02:03:06,100
fact of life. It happens in my house

1950
02:03:06,100 --> 02:03:09,100
and sometimes I have to pivot when I'm

1951
02:03:09,100 --> 02:03:12,601
cooking, I'm going to use more

1952
02:03:13,100 --> 02:03:16,100
ingredients, it's going to cost me more

1953
02:03:16,100 --> 02:03:18,100
money, yes. One doesn't know what a

1954
02:03:18,100 --> 02:03:21,100
day will bring forth. We can mitigate

1955
02:03:21,100 --> 02:03:24,100
risk. I'm not an expert on this, but I

1956
02:03:24,100 --> 02:03:25,100
have 55 years' of using the New York

1957
02:03:25,100 --> 02:03:27,100
City subway and I think that gives me

1958
02:03:27,100 --> 02:03:31,100
some leg to stand on. So there's a lot

1959
02:03:31,100 --> 02:03:35,100
going on. And I still am expecting a

1960
02:03:35,100 --> 02:03:39,100
nexus, how does this affect me, the

1961
02:03:39,100 --> 02:03:41,100
ordinary rider, who tap my Clipper card

1962
02:03:41,100 --> 02:03:44,100
and gets on the train? I ask that this

1963
02:03:44,100 --> 02:03:47,100
work not be about painting targets on

1964
02:03:47,100 --> 02:03:48,100
people's backs, but instead reflecting

1965
02:03:48,100 --> 02:03:52,100
the idea that BART is the People's

1966
02:03:52,100 --> 02:03:53,100
system. Thank you.

1967
02:03:53,100 --> 02:03:56,601
>> The next speaker is Barney Smits.

1968
02:03:58,100 --> 02:03:59,100
Barney, please unmute yourself.

1969
02:03:59,100 --> 02:04:01,100
>> Thank you. My name is Barney

1970
02:04:01,100 --> 02:04:03,100
Smits. I'm a licensed professional

1971
02:04:03,100 --> 02:04:05,100
engineer with over 25 years' experience

1972
02:04:05,100 --> 02:04:09,100
as a BART engineer and Fire/Life Safety

1973
02:04:09,100 --> 02:04:10,100
expert. I don't suppose any of you are

1974
02:04:10,100 --> 02:04:13,100
aware of the fact that I received Chief

1975
02:04:13,100 --> 02:04:15,100
Engineer's award for putting together

1976
02:04:15,100 --> 02:04:18,100
an RE training class and teaching 50

1977
02:04:18,100 --> 02:04:19,100
BART engineers about contract

1978
02:04:19,100 --> 02:04:23,201
management and RE work at BART. I

1979
02:04:24,100 --> 02:04:25,100
suppose that is important because I

1980
02:04:25,100 --> 02:04:27,100
could give the Board a class, if they

1981
02:04:27,100 --> 02:04:30,100
wanted on contracts and change

1982
02:04:32,100 --> 02:04:33,100
orders. Moving along, the most

1983
02:04:33,100 --> 02:04:35,100
important thing is that the IG has put

1984
02:04:35,100 --> 02:04:37,100
together a report. And it comes down

1985
02:04:37,100 --> 02:04:41,100
to is are all of these reports that the

1986
02:04:41,100 --> 02:04:43,100
IG is presenting, are they being

1987
02:04:43,100 --> 02:04:47,100
accepted by the Board? And if so, is

1988
02:04:47,100 --> 02:04:50,100
the Board actually going to implement

1989
02:04:50,100 --> 02:04:53,601
the recommendations that the IG is

1990
02:04:54,100 --> 02:04:57,100
recommending? So I think the IG's

1991
02:04:57,100 --> 02:04:59,100
recommendations update is important,

1992
02:04:59,100 --> 02:05:03,100
and I think a periodic, or quarterly

1993
02:05:03,100 --> 02:05:06,100
review of whether or not those

1994
02:05:06,100 --> 02:05:07,100
recommendations are being followed by

1995
02:05:07,100 --> 02:05:09,100
management and Staff is absolutely

1996
02:05:09,100 --> 02:05:11,100
critical to making sure that the public

1997
02:05:11,100 --> 02:05:15,201
is getting what it needs. Thank you.

1998
02:05:21,100 --> 02:05:22,100
>> That was last public comment or

1999
02:05:22,100 --> 02:05:23,100
this item.

2000
02:05:23,100 --> 02:05:25,100
>> Thank you.

2001
02:05:25,100 --> 02:05:26,100
Not seeing any other public comment,

2002
02:05:26,100 --> 02:05:29,100
not seeing any other questions from the

2003
02:05:29,100 --> 02:05:33,801
Board on item 5, we'll move on to Item

2004
02:05:34,100 --> 02:05:36,401
No. 6 for public comment.

2005
02:05:38,100 --> 02:05:40,100
>> We do not have any public comments

2006
02:05:40,100 --> 02:05:44,801
-- oh, we do, just one popped up.

2007
02:05:45,100 --> 02:05:47,100
Aleta Dupree, Aleta, please, go ahead.

2008
02:05:47,100 --> 02:05:49,401
>> Thanks again, President Melissa

2009
02:05:52,100 --> 02:05:53,100
Hernandez and Members, Aleta Dupree,

2010
02:05:53,100 --> 02:05:55,100
for the record, she and her with team

2011
02:05:55,100 --> 02:05:57,100
folds. Thank you for calling that out.

2012
02:05:57,100 --> 02:06:00,601
I was afraid I wouldn't speak

2013
02:06:02,100 --> 02:06:04,100
today, but I appreciate it. I wrote

2014
02:06:04,100 --> 02:06:07,100
you more letters and hope you got to

2015
02:06:07,100 --> 02:06:10,100
read them. I'm sure Bob

2016
02:06:11,100 --> 02:06:12,100
Franklin read them. I talked about a

2017
02:06:12,100 --> 02:06:14,100
number of different things and I frame

2018
02:06:14,100 --> 02:06:19,100
the thing that I say to you in your

2019
02:06:19,100 --> 02:06:21,100
experiences. Yes, I wish I had a part

2020
02:06:21,100 --> 02:06:23,100
in bringing the soul train to New York

2021
02:06:23,100 --> 02:06:25,100
City. I probably would have go to

2022
02:06:25,100 --> 02:06:30,401
trainings all the time if it was in New

2023
02:06:31,100 --> 02:06:33,100
York City and I think I would have

2024
02:06:33,100 --> 02:06:35,100
enjoyed more with images of the City.

2025
02:06:35,100 --> 02:06:39,100
How do we build a better BART? I try

2026
02:06:39,100 --> 02:06:43,201
to share with you from experience as

2027
02:06:44,100 --> 02:06:46,100
opposed to academic conjecture and I

2028
02:06:46,100 --> 02:06:50,100
want BART to be something that is not

2029
02:06:50,100 --> 02:06:52,100
just used, but to be enjoyed. I'm

2030
02:06:52,100 --> 02:06:54,100
learning things all the time. You

2031
02:06:54,100 --> 02:06:57,100
know, I don't know if I teach you

2032
02:06:57,100 --> 02:06:59,100
anything that -- I don't know if any of

2033
02:06:59,100 --> 02:07:02,601
you have experience with the soul

2034
02:07:03,100 --> 02:07:04,100
train? Don Cornelius saying it's going

2035
02:07:04,100 --> 02:07:08,801
to be a stone gas, peace, love and

2036
02:07:09,100 --> 02:07:11,100
soul. See, I grew up with some of

2037
02:07:11,100 --> 02:07:15,201
that, sharing with you about life in

2038
02:07:16,100 --> 02:07:17,100
New York, where I come from. I would

2039
02:07:17,100 --> 02:07:20,100
like to be with you in-person more.

2040
02:07:20,100 --> 02:07:22,100
It's hard. I have to travel 600 miles

2041
02:07:22,100 --> 02:07:25,100
to come and see you, and get to spend

2042
02:07:25,100 --> 02:07:29,100
time with you. It's not easy. But how

2043
02:07:29,100 --> 02:07:32,100
do we have the focus on the basics?

2044
02:07:32,100 --> 02:07:33,100
Things that are most important? Don't

2045
02:07:33,100 --> 02:07:37,201
want us to be preoccupied with whether

2046
02:07:39,100 --> 02:07:42,100
people wear skirts on BART, but to be

2047
02:07:42,100 --> 02:07:45,100
preoccupied making sure that we offer

2048
02:07:45,100 --> 02:07:46,100
high-quality transportation service

2049
02:07:46,100 --> 02:07:49,100
that we're known for and most of all

2050
02:07:49,100 --> 02:07:50,100
that everybody should practice the idea

2051
02:07:50,100 --> 02:07:51,100
that BART is the People's system.

2052
02:07:51,100 --> 02:07:53,100
Thank you.

2053
02:07:53,100 --> 02:07:55,100
>> Our next speaker is Chris Finn,

2054
02:07:55,100 --> 02:07:58,601
please come up to the mic.

2055
02:08:01,100 --> 02:08:04,100
>> Good morning. Chris Finn, ATU

2056
02:08:05,100 --> 02:08:07,100
1555. And I know BART is doing

2057
02:08:07,100 --> 02:08:10,100
everything they can to improve service

2058
02:08:10,100 --> 02:08:13,100
and attract public ridership and

2059
02:08:15,100 --> 02:08:16,100
increase ridership. And especially

2060
02:08:16,100 --> 02:08:21,401
with the connect Bay Area, to put it on

2061
02:08:22,100 --> 02:08:25,100
the ballot in November. The news I

2062
02:08:25,100 --> 02:08:27,100
received yesterday morning about BART

2063
02:08:27,100 --> 02:08:28,100
partnering with Uber, that was probably

2064
02:08:28,100 --> 02:08:30,100
the most amount of feedback I got

2065
02:08:30,100 --> 02:08:33,100
yesterday was concern from different

2066
02:08:33,100 --> 02:08:36,100
community and transit agencies and

2067
02:08:36,100 --> 02:08:39,100
other transit unions about advocating,

2068
02:08:40,100 --> 02:08:42,100
or supporting private transit rather

2069
02:08:42,100 --> 02:08:44,100
than advocating for other AC Transit or

2070
02:08:44,100 --> 02:08:46,100
other measures to cover that last mile.

2071
02:08:46,100 --> 02:08:48,100
So just wanted to put that out there,

2072
02:08:48,100 --> 02:08:51,100
again, I'm new to office. I'm just

2073
02:08:51,100 --> 02:08:54,100
taking office January 1st. I wasn't

2074
02:08:54,100 --> 02:08:55,100
privy to previous communications about

2075
02:08:55,100 --> 02:08:59,100
this topic. But I think it came out as

2076
02:08:59,100 --> 02:09:03,801
-- we might get a little more negative

2077
02:09:05,100 --> 02:09:06,100
feedback on that, to put that out

2078
02:09:06,100 --> 02:09:07,100
there. Thank you.

2079
02:09:07,100 --> 02:09:09,100
>> Thank you, Chris. I would be happy

2080
02:09:09,100 --> 02:09:11,100
to speak you at a later time with

2081
02:09:11,100 --> 02:09:13,100
regards to the Uber. There was a price

2082
02:09:13,100 --> 02:09:14,100
limit on that, correct? What was the

2083
02:09:14,100 --> 02:09:16,100
amount

2084
02:09:17,100 --> 02:09:18,100
$50,000 pilot.

2085
02:09:18,100 --> 02:09:20,100
>> It's a pilot program and we can

2086
02:09:20,100 --> 02:09:22,100
talk offline, happy to do

2087
02:09:22,100 --> 02:09:25,601
there are no additional public comments

2088
02:09:26,100 --> 02:09:27,100
for this item that was the last public

2089
02:09:27,100 --> 02:09:29,100
comment or item 6.

2090
02:09:29,100 --> 02:09:32,601
>> Okay. So Item No. 7 is our

2091
02:09:33,100 --> 02:09:34,100
Engineering and Operations item, and I

2092
02:09:34,100 --> 02:09:38,801
will go ahead and let our Chair Foley

2093
02:09:39,100 --> 02:09:40,100
take over.

2094
02:09:40,100 --> 02:09:42,401
>> Thank you, Madam President.

2095
02:09:43,100 --> 02:09:46,100
Colleagues, we have one information

2096
02:09:46,100 --> 02:09:48,100
item on the E&O agenda today and that

2097
02:09:48,100 --> 02:09:50,100
is the root-cause investigation on the

2098
02:09:50,100 --> 02:09:53,601
update on the recent M-line service

2099
02:09:55,100 --> 02:09:58,100
disruptions. I will turn it over to

2100
02:09:58,100 --> 02:10:00,100
Assistant General Manager Deputy Jones

2101
02:10:00,100 --> 02:10:02,100
and Staff for presentation.

2102
02:10:02,100 --> 02:10:04,100
>> Thank you. Once again, good

2103
02:10:04,100 --> 02:10:07,100
morning Bus Rapid Transit Michael

2104
02:10:09,100 --> 02:10:11,100
Jones, before I turn it over to Sylvia

2105
02:10:11,100 --> 02:10:14,100
and her team to provide context for the

2106
02:10:14,100 --> 02:10:15,100
information that we'll sharing this

2107
02:10:15,100 --> 02:10:17,100
in. First, Staff with support from

2108
02:10:17,100 --> 02:10:19,100
consultant team has conducted a thorough

2109
02:10:19,100 --> 02:10:21,100
and comprehensive analysis of all of

2110
02:10:21,100 --> 02:10:23,100
the service disruptions that our

2111
02:10:23,100 --> 02:10:25,100
customers have experienced since

2112
02:10:25,100 --> 02:10:28,601
August of 2025. I want to definitely

2113
02:10:29,100 --> 02:10:31,100
state Staff has not identified a single

2114
02:10:31,100 --> 02:10:33,100
cause of the disruptions. Said

2115
02:10:33,100 --> 02:10:36,100
differently there's no smoking gun to

2116
02:10:36,100 --> 02:10:39,100
share this morning. However, l

2117
02:10:40,100 --> 02:10:42,100
evaluated all possible causes that

2118
02:10:42,100 --> 02:10:44,100
could have contributed to the events

2119
02:10:44,100 --> 02:10:46,100
and focused on all aspects of rail,

2120
02:10:46,100 --> 02:10:48,100
including traction power system,

2121
02:10:48,100 --> 02:10:50,100
Wayside equipment, as well as rolling

2122
02:10:50,100 --> 02:10:52,100
stock. I'm confident that as we

2123
02:10:52,100 --> 02:10:54,100
present our findings, it will be clear

2124
02:10:54,100 --> 02:10:56,100
that we evaluated everything that we

2125
02:10:56,100 --> 02:11:00,100
possibly could to get to root cause and

2126
02:11:00,100 --> 02:11:01,100
share the mitigation efforts both

2127
02:11:01,100 --> 02:11:04,100
completed and ongoing that should

2128
02:11:04,100 --> 02:11:05,100
proffers confidence to the Board and

2129
02:11:05,100 --> 02:11:07,100
public that we continue to operate a

2130
02:11:07,100 --> 02:11:09,100
safe, reliable and efficient transit

2131
02:11:09,100 --> 02:11:12,601
system. Lastly, I want to address

2132
02:11:13,100 --> 02:11:14,100
several misconceptions that Staff heard

2133
02:11:14,100 --> 02:11:17,100
recently from the public and Members of

2134
02:11:17,100 --> 02:11:19,100
the BART Board. First, there's

2135
02:11:19,100 --> 02:11:21,100
speculation that BART leadership has

2136
02:11:21,100 --> 02:11:23,100
Intel on the single root cause of these

2137
02:11:23,100 --> 02:11:26,100
incidents, but we're not sharing it.

2138
02:11:26,100 --> 02:11:29,100
This is false. Second, there's a

2139
02:11:29,100 --> 02:11:30,100
suggestion that insulators are the

2140
02:11:30,100 --> 02:11:33,100
root cause of service disruptions.

2141
02:11:33,100 --> 02:11:35,100
This is also false. I want to point

2142
02:11:35,100 --> 02:11:38,601
out that blown insulators are a

2143
02:11:39,100 --> 02:11:40,100
common occurrence on electrified

2144
02:11:40,100 --> 02:11:43,100
railroads. It happens and while it can

2145
02:11:43,100 --> 02:11:45,100
cause arcing, it hasn't present a

2146
02:11:45,100 --> 02:11:48,100
dangerous condition to cause alarm. We

2147
02:11:48,100 --> 02:11:49,100
have contacted several transit

2148
02:11:49,100 --> 02:11:51,100
properties around the country and we're

2149
02:11:51,100 --> 02:11:53,100
not unique in experiencing blown

2150
02:11:53,100 --> 02:11:54,100
insulators, and our maintenance

2151
02:11:54,100 --> 02:11:57,100
and mitigation standards are in line

2152
02:11:57,100 --> 02:11:58,100
with those agencies. We'll discuss

2153
02:11:58,100 --> 02:12:01,601
this in more detail during the

2154
02:12:03,100 --> 02:12:04,100
presentation. Third, there's

2155
02:12:04,100 --> 02:12:07,100
speculation this effort did not require

2156
02:12:07,100 --> 02:12:08,100
the effort of external consultant and

2157
02:12:08,100 --> 02:12:10,100
consultants don't have the expertise

2158
02:12:10,100 --> 02:12:12,100
necessary to increase resolving our

2159
02:12:12,100 --> 02:12:14,100
challenges. I can assure you that the

2160
02:12:14,100 --> 02:12:16,100
team we Assembled exceeds the expertise

2161
02:12:16,100 --> 02:12:18,100
of our in-house Staff. They are

2162
02:12:18,100 --> 02:12:20,401
credentialed professionals from global

2163
02:12:21,100 --> 02:12:24,601
firms that have decades of experience

2164
02:12:26,100 --> 02:12:28,100
in tackling the issues we're face.

2165
02:12:28,100 --> 02:12:32,100
With this context, I will turn it over

2166
02:12:32,100 --> 02:12:34,100
to Sylvia Lamb, AGM of infrastructure and

2167
02:12:34,100 --> 02:12:37,100
delivery and to point out that we have

2168
02:12:37,100 --> 02:12:38,100
our entire maintenance and

2169
02:12:38,100 --> 02:12:39,100
infrastructure team in the room and I

2170
02:12:39,100 --> 02:12:43,100
would like them to stand and be

2171
02:12:43,100 --> 02:12:46,100
recognized. So these are the

2172
02:12:48,100 --> 02:12:50,100
individuals that respond to the 1:00

2173
02:12:50,100 --> 02:12:53,100
a.m. calls, 4:00 a.m. calls when we have

2174
02:12:53,100 --> 02:12:55,100
these incidents and they are responding

2175
02:12:55,100 --> 02:12:58,100
with their frontline workforce and

2176
02:12:58,100 --> 02:12:59,100
mitigating these issues. These are the

2177
02:12:59,100 --> 02:13:01,100
people behind the challenges that we're

2178
02:13:01,100 --> 02:13:03,100
having, and I can guaranty that they

2179
02:13:03,100 --> 02:13:05,100
are totally committed to making sure

2180
02:13:05,100 --> 02:13:07,100
that we move this forward in a positive

2181
02:13:07,100 --> 02:13:08,100
direction. So with that, Ms. Lamb, I

2182
02:13:08,100 --> 02:13:11,100
will turn it over to you.

2183
02:13:11,100 --> 02:13:14,601
>> Thank you, Michael. I would like

2184
02:13:15,100 --> 02:13:18,100
to acknowledge also that Parsons was

2185
02:13:18,100 --> 02:13:22,801
the lead firm in this effort for the

2186
02:13:23,100 --> 02:13:27,201
root-cause analysis and they are in the

2187
02:13:29,100 --> 02:13:33,801
audience. To my left is Zara -- and

2188
02:13:35,100 --> 02:13:37,100
while there were tons of experts

2189
02:13:37,100 --> 02:13:40,100
involved in this investigation, working

2190
02:13:41,100 --> 02:13:44,100
for Parsons, multiple subs probably 50

2191
02:13:47,100 --> 02:13:50,100
individuals engaged, Zara is a

2192
02:13:51,100 --> 02:13:53,100
California PE and Chief Engineer to the

2193
02:13:53,100 --> 02:13:56,100
subconsultant to Parsons and worked in

2194
02:13:56,100 --> 02:13:58,100
the UK and USA and worked for London

2195
02:13:58,100 --> 02:14:01,601
Underground and worked for BART systems

2196
02:14:02,100 --> 02:14:03,100
with traction systems and worked on

2197
02:14:03,100 --> 02:14:06,100
issues for BART related to the track

2198
02:14:06,100 --> 02:14:09,100
engineering and so she is very familiar

2199
02:14:09,100 --> 02:14:12,100
with our system. As she came in, she

2200
02:14:12,100 --> 02:14:16,201
is also for other agencies worked at

2201
02:14:19,100 --> 02:14:21,100
WMATA, London Underground and other

2202
02:14:21,100 --> 02:14:23,100
places in U.S. and the U.K. Her

2203
02:14:23,100 --> 02:14:25,100
credentials are long and wide and I'm

2204
02:14:25,100 --> 02:14:27,100
only touching a small bit of it. But

2205
02:14:27,100 --> 02:14:31,100
we're happy to have her here and to

2206
02:14:31,100 --> 02:14:33,100
serve as the focus point of all

2207
02:14:33,100 --> 02:14:36,100
expertise on the project. So to get

2208
02:14:36,100 --> 02:14:38,100
started, I want to talk a little bit

2209
02:14:38,100 --> 02:14:40,100
about the scope of this investigation.

2210
02:14:40,100 --> 02:14:45,100
As you can see in the middle, we really

2211
02:14:45,100 --> 02:14:48,100
focused on the area between West

2212
02:14:48,100 --> 02:14:49,100
Oakland and Civic Center. So that is

2213
02:14:49,100 --> 02:14:52,100
not to say that if an incident popped

2214
02:14:52,100 --> 02:14:54,100
up that we didn't also include that

2215
02:14:54,100 --> 02:14:58,100
into just a check and see if it was

2216
02:14:58,100 --> 02:14:59,100
something holistic that was also added

2217
02:14:59,100 --> 02:15:02,100
to this? We did do that, but from a

2218
02:15:02,100 --> 02:15:04,100
root-cause analysis perspective and a

2219
02:15:04,100 --> 02:15:05,100
scope perspective, it was really

2220
02:15:05,100 --> 02:15:08,100
important for us to stay focused and

2221
02:15:08,100 --> 02:15:10,100
not like kind of trace a thread down.

2222
02:15:10,100 --> 02:15:12,100
An example of that is there was an

2223
02:15:12,100 --> 02:15:15,100
incident in Lake Merritt that was

2224
02:15:15,100 --> 02:15:17,100
incident No. 3 during this period of

2225
02:15:17,100 --> 02:15:19,100
time. We did go there and find it was

2226
02:15:19,100 --> 02:15:23,100
specifically a rod that had fallen from

2227
02:15:23,100 --> 02:15:24,100
the ceiling and landed which caused

2228
02:15:24,100 --> 02:15:26,100
that incident. So I just wanted to

2229
02:15:26,100 --> 02:15:28,100
make sure that we had an understanding

2230
02:15:28,100 --> 02:15:31,100
of what that scope was and the

2231
02:15:31,100 --> 02:15:34,100
timeframe, we started, we looked

2232
02:15:35,100 --> 02:15:37,100
incidents in August, starting August

2233
02:15:37,100 --> 02:15:39,100
29th. If something pops up today, the

2234
02:15:39,100 --> 02:15:41,100
team will go out there and look at that

2235
02:15:41,100 --> 02:15:43,100
as well. This is not over, but an

2236
02:15:43,100 --> 02:15:45,100
ongoing investigation and we're

2237
02:15:45,100 --> 02:15:47,100
continuing to look at any incidents

2238
02:15:47,100 --> 02:15:51,100
that come up within our trackway. We

2239
02:15:51,100 --> 02:15:54,100
followed a very scientific approach to

2240
02:15:54,100 --> 02:15:58,100
this. That means it had to be super

2241
02:15:58,100 --> 02:16:00,100
methodical and trying to get down to

2242
02:16:00,100 --> 02:16:02,100
root-cause analysis is not an easy

2243
02:16:02,100 --> 02:16:04,100
thing in a very complex system is a

2244
02:16:04,100 --> 02:16:07,100
high-voltage system. It's not unusual

2245
02:16:07,100 --> 02:16:10,100
to see arcing or sparks on our system.

2246
02:16:10,100 --> 02:16:13,100
So it was really important to stay

2247
02:16:13,100 --> 02:16:15,100
focused and keep a methodical approach

2248
02:16:15,100 --> 02:16:18,100
and that started with collecting data.

2249
02:16:18,100 --> 02:16:19,100
That meant our data that we have

2250
02:16:19,100 --> 02:16:23,801
in-house as far as designs, as far as

2251
02:16:24,100 --> 02:16:27,100
maintenance records, as far as other

2252
02:16:27,100 --> 02:16:29,100
work that was going on, but also the

2253
02:16:29,100 --> 02:16:32,100
very first thing that was done was for

2254
02:16:32,100 --> 02:16:36,100
a whole slew of people to go to these

2255
02:16:36,100 --> 02:16:38,100
incidents physically and look at them.

2256
02:16:38,100 --> 02:16:41,100
That is part of that collecting of the

2257
02:16:41,100 --> 02:16:42,100
data. So the process went through

2258
02:16:42,100 --> 02:16:45,100
collecting the data and then analyzing

2259
02:16:45,100 --> 02:16:49,100
the data, and then getting down to some

2260
02:16:49,100 --> 02:16:51,100
hypotheses. A fish bone diagram is

2261
02:16:51,100 --> 02:16:53,100
simply a graphical representation

2262
02:16:53,100 --> 02:16:55,100
that helps a team after collecting a

2263
02:16:55,100 --> 02:16:59,201
whole bunch of data to and trace

2264
02:17:01,100 --> 02:17:03,100
through looking for cause and effect.

2265
02:17:03,100 --> 02:17:07,801
It's a common diagram that is used in

2266
02:17:08,100 --> 02:17:09,100
lien practices different quality

2267
02:17:09,100 --> 02:17:11,100
practices. So this is a standard

2268
02:17:11,100 --> 02:17:14,100
industry in order to do these types of

2269
02:17:14,100 --> 02:17:15,100
investigations -- I won't go through

2270
02:17:15,100 --> 02:17:17,100
every single one of these, but it gives

2271
02:17:17,100 --> 02:17:19,100
you an idea of the extent of how the

2272
02:17:19,100 --> 02:17:22,601
team went through to analyze root

2273
02:17:24,100 --> 02:17:27,100
cause. You know, Michael said it and

2274
02:17:27,100 --> 02:17:28,100
kind of stole my thunder there is a

2275
02:17:28,100 --> 02:17:31,100
saying, this was a very thorough and

2276
02:17:31,100 --> 02:17:33,100
comprehensive investigation, and

2277
02:17:33,100 --> 02:17:35,100
report. Again, ongoing. You can look

2278
02:17:35,100 --> 02:17:37,100
at the amount of man hours that was put

2279
02:17:37,100 --> 02:17:39,100
on, the amount of field visits. So

2280
02:17:39,100 --> 02:17:43,100
site visits we were in the tube, you

2281
02:17:43,100 --> 02:17:47,201
know, 37 site visits, but that is not

2282
02:17:49,100 --> 02:17:52,100
just to the tube and that is not just

2283
02:17:52,100 --> 02:17:54,100
the Parson's team. So the consultant

2284
02:17:54,100 --> 02:17:56,100
team had 50 individuals engaged

2285
02:17:56,100 --> 02:17:58,100
throughout this process, but we were

2286
02:17:58,100 --> 02:17:59,100
all hands-on deck and those -- the

2287
02:17:59,100 --> 02:18:02,100
folks that stood up in the back are not

2288
02:18:02,100 --> 02:18:04,100
the only folks that are involved in

2289
02:18:04,100 --> 02:18:07,100
this. There's actually more folks that

2290
02:18:07,100 --> 02:18:09,100
didn't stand up. I was going to tell

2291
02:18:09,100 --> 02:18:10,100
them to stand up, but that is okay. We

2292
02:18:10,100 --> 02:18:13,100
have had tons of people involved.

2293
02:18:13,100 --> 02:18:15,100
These 37 site visits probably I would

2294
02:18:15,100 --> 02:18:18,100
say at least 15 of them involved going

2295
02:18:18,100 --> 02:18:20,100
out in the middle of the night. And

2296
02:18:20,100 --> 02:18:22,100
sometimes that involved going out

2297
02:18:22,100 --> 02:18:23,100
working all day here, going through

2298
02:18:23,100 --> 02:18:26,100
files of data, and then going out and

2299
02:18:26,100 --> 02:18:28,100
leaving this office, taking a break for

2300
02:18:28,100 --> 02:18:31,100
a couple of hours and going to the site

2301
02:18:31,100 --> 02:18:33,100
and going out into graveyard with the

2302
02:18:33,100 --> 02:18:35,100
power off to really investigate that.

2303
02:18:35,100 --> 02:18:38,100
A huge part of this, too, going through

2304
02:18:38,100 --> 02:18:41,100
the bottom right is the amount of

2305
02:18:41,100 --> 02:18:44,100
documentation that was reviewed, and

2306
02:18:44,100 --> 02:18:46,100
requested by Parsons and by the

2307
02:18:46,100 --> 02:18:48,100
consultant team. It's not unusual when

2308
02:18:48,100 --> 02:18:49,100
you bring a consultant in, they are

2309
02:18:49,100 --> 02:18:51,100
coming in cold. The first thing they

2310
02:18:51,100 --> 02:18:54,100
want to know is all this information,

2311
02:18:54,100 --> 02:18:56,100
where is this, where is this, you know?

2312
02:18:56,100 --> 02:18:58,100
Sometimes it could be frustrating --

2313
02:18:58,100 --> 02:19:00,100
make sure your mic is on. Sometimes

2314
02:19:00,100 --> 02:19:02,100
it's frustrating for the BART team,

2315
02:19:02,100 --> 02:19:04,100
because we want to get going right?

2316
02:19:04,100 --> 02:19:07,100
and there has to be a combination of

2317
02:19:07,100 --> 02:19:10,100
that because the team needs all that

2318
02:19:10,100 --> 02:19:11,100
information.

2319
02:19:11,100 --> 02:19:14,601
>> that is correct, the Parsons team

2320
02:19:15,100 --> 02:19:19,100
does submit over 300 RFIs and to thank

2321
02:19:19,100 --> 02:19:22,100
them for the very fast turnaround on

2322
02:19:22,100 --> 02:19:25,100
those responses. Some were same day

2323
02:19:25,100 --> 02:19:28,100
and did not same day, next day. So we

2324
02:19:28,100 --> 02:19:29,100
appreciate that.

2325
02:19:29,100 --> 02:19:31,100
>> There was a huge amount of data and

2326
02:19:31,100 --> 02:19:34,100
all the BART team was very supportive

2327
02:19:34,100 --> 02:19:37,100
as far as again maintenance records,

2328
02:19:37,100 --> 02:19:38,100
engineering records everything that

2329
02:19:38,100 --> 02:19:41,100
we could do and the whole team knew

2330
02:19:41,100 --> 02:19:45,100
this was a top priority to get this

2331
02:19:45,100 --> 02:19:46,100
investigation done and figure out what

2332
02:19:46,100 --> 02:19:50,100
is happening in your system. So as far

2333
02:19:50,100 --> 02:19:54,100
as when we get through the fish bone

2334
02:19:54,100 --> 02:19:58,100
diagram and Zara will talk about the

2335
02:19:58,100 --> 02:20:00,100
hypotheses. Before she does to say

2336
02:20:00,100 --> 02:20:02,100
again to Michael's point, other than

2337
02:20:02,100 --> 02:20:04,100
the Lake Merritt incident, where we do

2338
02:20:04,100 --> 02:20:07,100
know it was one rod that fall, every

2339
02:20:07,100 --> 02:20:09,100
other incident has a combination of

2340
02:20:09,100 --> 02:20:11,100
factors. It's not one single thing,

2341
02:20:11,100 --> 02:20:15,100
and there's not one single thing that

2342
02:20:15,100 --> 02:20:17,100
happened for all, correct, Zara?

2343
02:20:17,100 --> 02:20:19,100
>> That is correct. Yes.

2344
02:20:19,100 --> 02:20:23,100
So this slide here represents the main

2345
02:20:23,100 --> 02:20:26,100
group of hypotheses put together by the

2346
02:20:26,100 --> 02:20:30,100
Parsons team. And in some cases the

2347
02:20:30,100 --> 02:20:31,100
incidents are straightforward, where

2348
02:20:31,100 --> 02:20:34,100
there may be one or two casual factors.

2349
02:20:34,100 --> 02:20:38,201
In a few instances that are actually

2350
02:20:39,100 --> 02:20:41,100
more complicated and require detailed

2351
02:20:41,100 --> 02:20:43,100
analysis to determine root cause. This

2352
02:20:43,100 --> 02:20:44,100
represent a comprehensive look at

2353
02:20:44,100 --> 02:20:47,100
system as well as Substations, and

2354
02:20:47,100 --> 02:20:50,100
external factors and also human

2355
02:20:51,100 --> 02:20:52,100
factors. Thank you.

2356
02:20:52,100 --> 02:20:55,601
>> Thanks. So let me start with

2357
02:20:57,100 --> 02:20:58,100
redescribing our traction power system.

2358
02:20:58,100 --> 02:21:02,100
You may remember when Myat was here a

2359
02:21:02,100 --> 02:21:04,100
couple of months ago to give an

2360
02:21:04,100 --> 02:21:06,100
overview of our traction power system.

2361
02:21:06,100 --> 02:21:08,100
It's really important before we get

2362
02:21:08,100 --> 02:21:09,100
started today to talk about how our

2363
02:21:09,100 --> 02:21:11,100
system works and kind of work through

2364
02:21:11,100 --> 02:21:13,100
that. Also I want to point out at the

2365
02:21:13,100 --> 02:21:15,100
end of this presentation, I think

2366
02:21:15,100 --> 02:21:17,100
there's like two-and-a-half pages worth

2367
02:21:17,100 --> 02:21:18,100
of glossary. It's really hard for us

2368
02:21:18,100 --> 02:21:22,100
sometimes to figure out how to not use

2369
02:21:22,100 --> 02:21:24,100
the terms that we're always using. So

2370
02:21:24,100 --> 02:21:28,100
we wanted to include a glossary so it

2371
02:21:28,100 --> 02:21:32,201
would help. Our power comes from at

2372
02:21:34,100 --> 02:21:37,100
115 kV AC, the utility is then we then

2373
02:21:37,100 --> 02:21:41,201
step that down to 34.5kV, those are

2374
02:21:47,100 --> 02:21:50,100
redundant left and right cables through

2375
02:21:50,100 --> 02:21:53,601
the systems that feeds into the

2376
02:22:01,100 --> 02:22:06,100
Substation and take from AC to D.C. and

2377
02:22:06,100 --> 02:22:07,100
that is used to power the third

2378
02:22:07,100 --> 02:22:09,100
rail. The connection from the

2379
02:22:09,100 --> 02:22:11,100
Substation to the third rail that gets

2380
02:22:11,100 --> 02:22:14,100
the thousand volts out there. The

2381
02:22:14,100 --> 02:22:17,100
railcars have a collective shoe

2382
02:22:21,100 --> 02:22:24,100
assembly, which means there's a paddle

2383
02:22:24,100 --> 02:22:26,100
riding along the third rail, pulling

2384
02:22:26,100 --> 02:22:30,801
power to help it go forward and to

2385
02:22:31,100 --> 02:22:33,100
power the auxiliary systems within the

2386
02:22:33,100 --> 02:22:34,100
trains themselves. When you move the

2387
02:22:34,100 --> 02:22:37,100
train as and wheels are turning and

2388
02:22:37,100 --> 02:22:40,100
different heat, there's is current

2389
02:22:40,100 --> 02:22:41,100
being generated and that current needs

2390
02:22:41,100 --> 02:22:45,100
to go back to the Substation. So if

2391
02:22:45,100 --> 02:22:46,100
follow the Orange lines around, it's

2392
02:22:46,100 --> 02:22:48,100
really important that we close the loop

2393
02:22:48,100 --> 02:22:51,100
in any kind of electrical environment.

2394
02:22:51,100 --> 02:22:54,100
So the paddle is pulling power from the

2395
02:22:54,100 --> 02:22:57,601
third rail. It's moving the train

2396
02:22:58,100 --> 02:22:59,100
forward. It's powering the inside all

2397
02:22:59,100 --> 02:23:01,100
of the equipment inside of there and

2398
02:23:01,100 --> 02:23:03,100
the wheels and different heat are

2399
02:23:03,100 --> 02:23:05,100
generating current. That current goes

2400
02:23:05,100 --> 02:23:09,201
back out through the wheels, along the

2401
02:23:10,100 --> 02:23:12,100
running rails to a negative return

2402
02:23:12,100 --> 02:23:16,100
shunt and that shunt has a cable that

2403
02:23:16,100 --> 02:23:19,100
goes back to the Substation and that

2404
02:23:19,100 --> 02:23:22,100
closes the loop of our circuit with our

2405
02:23:22,100 --> 02:23:25,100
trains. Also in addition to that, we

2406
02:23:25,100 --> 02:23:28,100
have regenerative braking. If you have

2407
02:23:28,100 --> 02:23:31,100
Electric Vehicles you already know what

2408
02:23:31,100 --> 02:23:32,100
regenerative braking is, but for us I

2409
02:23:32,100 --> 02:23:34,100
will describe with where the negative

2410
02:23:34,100 --> 02:23:36,100
return current goes through the wheels

2411
02:23:36,100 --> 02:23:39,100
to the running rail as a train brakes

2412
02:23:39,100 --> 02:23:43,201
that excess power goes back out through

2413
02:23:44,100 --> 02:23:46,100
the paddle onto the third rail and

2414
02:23:46,100 --> 02:23:49,100
allows trains within the vicinity to

2415
02:23:49,100 --> 02:23:51,100
pull power from excess power as opposed

2416
02:23:51,100 --> 02:23:54,100
to pulling from the substation, which

2417
02:23:54,100 --> 02:23:57,100
again makes us more efficient. This

2418
02:23:57,100 --> 02:23:59,100
was in our legacy cars as in our cars

2419
02:23:59,100 --> 02:24:03,100
today. So as we go through this, it

2420
02:24:03,100 --> 02:24:07,201
really requires a lot of integration as

2421
02:24:08,100 --> 02:24:09,100
far as this discussion and can't look

2422
02:24:09,100 --> 02:24:12,100
at one thing in a bubble and say it's

2423
02:24:12,100 --> 02:24:15,100
it or not it and how it integrates

2424
02:24:15,100 --> 02:24:17,100
together? You probably remember from

2425
02:24:17,100 --> 02:24:19,100
the CBTC presentation how important

2426
02:24:19,100 --> 02:24:20,100
that systems integration is. As Zara

2427
02:24:20,100 --> 02:24:22,100
goes through the rest of the slides she

2428
02:24:22,100 --> 02:24:24,100
is going to talk about not just these

2429
02:24:24,100 --> 02:24:26,100
individual pieces, but also how do they

2430
02:24:26,100 --> 02:24:28,100
relate to each other? And so with that

2431
02:24:28,100 --> 02:24:30,100
I will turn it over to Zara to talk

2432
02:24:30,100 --> 02:24:32,100
about the very first piece.

2433
02:24:32,100 --> 02:24:35,100
>> Thank you very much. So we'll

2434
02:24:35,100 --> 02:24:36,100
start with traction power and looking

2435
02:24:36,100 --> 02:24:40,100
at some of the findings and the

2436
02:24:40,100 --> 02:24:42,100
analysis. What we're looking at on

2437
02:24:42,100 --> 02:24:46,100
this slide is a rough representation of

2438
02:24:46,100 --> 02:24:48,100
the traction power Substation

2439
02:24:48,100 --> 02:24:50,100
configuration in the

2440
02:24:53,100 --> 02:24:54,100
vicinity of the TransBay Tube and the

2441
02:24:54,100 --> 02:24:57,100
green icons represent those in-service.

2442
02:24:58,100 --> 02:25:02,201
So we'll look at the design intent,

2443
02:25:03,100 --> 02:25:04,100
R-2 traction power Substations on the

2444
02:25:04,100 --> 02:25:08,100
West side in San Francisco, there is

2445
02:25:08,100 --> 02:25:11,100
MTW. And it is capable of providing 10

2446
02:25:11,100 --> 02:25:14,100
megawatts. On the East Bay it's match

2447
02:25:14,100 --> 02:25:16,100
bird KTE, shown in gray, that is the

2448
02:25:16,100 --> 02:25:19,601
gray icon, because it's undergoing a

2449
02:25:20,100 --> 02:25:22,100
planned upgrade. To facilitate that

2450
02:25:22,100 --> 02:25:25,100
upgrade BART introduced a portable

2451
02:25:25,100 --> 02:25:28,100
Substation known as KPS. We looked

2452
02:25:28,100 --> 02:25:30,100
extensively at the dynamic of this and

2453
02:25:30,100 --> 02:25:34,201
the records, and it was determined that

2454
02:25:35,100 --> 02:25:38,100
this possible Substation has been used

2455
02:25:38,100 --> 02:25:39,100
elsewhere successfully on the system.

2456
02:25:39,100 --> 02:25:42,601
It's interesting that it has five

2457
02:25:46,100 --> 02:25:47,100
megawatt rectifier with the

2458
02:25:47,100 --> 02:25:49,100
transformer. So therefore, the overall

2459
02:25:49,100 --> 02:25:53,100
capacity is noted on the diagram to be

2460
02:25:53,100 --> 02:25:55,401
3 Megawatts. Typically on BART

2461
02:25:57,100 --> 02:26:00,100
traction power substation, they are 5

2462
02:26:02,100 --> 02:26:05,100
Megawatt typically give or take 1-2

2463
02:26:05,100 --> 02:26:07,100
miles apart. What is interesting while

2464
02:26:07,100 --> 02:26:10,601
we originally had 10 Megawatt to the

2465
02:26:11,100 --> 02:26:14,601
West and 10 Megawatt to East has

2466
02:26:15,100 --> 02:26:18,601
dropped to 3 Megawatt. This is being

2467
02:26:27,100 --> 02:26:29,100
analyzed and some of the hypotheses

2468
02:26:29,100 --> 02:26:32,100
that have been bounced around. In

2469
02:26:32,100 --> 02:26:35,100
addition to that, to be able to

2470
02:26:35,100 --> 02:26:38,100
evaluate that further. That is

2471
02:26:38,100 --> 02:26:39,100
happening through modeling. I would

2472
02:26:39,100 --> 02:26:41,100
also like to point out how to our

2473
02:26:41,100 --> 02:26:44,100
review of the records, this change

2474
02:26:44,100 --> 02:26:46,100
happened in 2021. So it has been

2475
02:26:46,100 --> 02:26:50,100
operating in this way for about 4-5

2476
02:26:50,100 --> 02:26:51,100
years and therefore, it's not

2477
02:26:51,100 --> 02:26:53,100
considered to be the root cause.

2478
02:26:53,100 --> 02:26:56,100
However, we're looking at whether any

2479
02:26:56,100 --> 02:26:58,100
of these small changes have moved the

2480
02:26:58,100 --> 02:27:01,100
needle in terms the power quality.

2481
02:27:01,100 --> 02:27:05,100
>> Zara said it, but I want to repeat,

2482
02:27:05,100 --> 02:27:08,100
that KTE, the gray Substation is out of

2483
02:27:08,100 --> 02:27:10,100
service because we had planned for a

2484
02:27:10,100 --> 02:27:14,100
couple of years before that to upgrade

2485
02:27:14,100 --> 02:27:16,100
that Substation. So it was a planned

2486
02:27:16,100 --> 02:27:19,100
out of service, and we were waiting for

2487
02:27:19,100 --> 02:27:21,100
-- well, not waiting, but when the

2488
02:27:21,100 --> 02:27:23,100
portable substation was available it

2489
02:27:23,100 --> 02:27:26,100
was all planned to be done this way.

2490
02:27:26,100 --> 02:27:29,100
>> Thank you. So another finding, and

2491
02:27:29,100 --> 02:27:32,100
design change that we came across

2492
02:27:32,100 --> 02:27:35,601
through our review now this occurred

2493
02:27:36,100 --> 02:27:37,100
through site inspections. I would like

2494
02:27:37,100 --> 02:27:40,100
to take a moment to thank the BART

2495
02:27:40,100 --> 02:27:41,100
structures crew, and BART maintenance

2496
02:27:41,100 --> 02:27:43,100
for supporting these requests. They

2497
02:27:43,100 --> 02:27:46,100
were through the night back-to-back. I

2498
02:27:46,100 --> 02:27:48,100
personally did go out and walk the

2499
02:27:48,100 --> 02:27:51,100
track as well to perform these

2500
02:27:51,100 --> 02:27:52,100
inspections. And through these

2501
02:27:52,100 --> 02:27:54,100
inspections we were able to verify that

2502
02:27:54,100 --> 02:27:57,601
during the dates of the incidents

2503
02:27:58,100 --> 02:28:01,601
between August and October, the cross

2504
02:28:04,100 --> 02:28:07,100
bonds were not in place. There should

2505
02:28:07,100 --> 02:28:10,100
have been ten cross bonds in place in

2506
02:28:10,100 --> 02:28:12,100
the TransBay Tube and the purple

2507
02:28:12,100 --> 02:28:15,100
represents the cross bond, essentially

2508
02:28:15,100 --> 02:28:17,100
a cable that connects between two

2509
02:28:17,100 --> 02:28:19,100
tracks and help provides additional

2510
02:28:19,100 --> 02:28:21,100
parts for the return current to flow

2511
02:28:21,100 --> 02:28:24,601
back to the Substation through both

2512
02:28:25,100 --> 02:28:28,100
tracks. And when upon our further

2513
02:28:28,100 --> 02:28:30,100
request for information, we determined

2514
02:28:30,100 --> 02:28:33,100
that they were removed to support a

2515
02:28:33,100 --> 02:28:36,100
single tracking project in 2020. And

2516
02:28:37,100 --> 02:28:39,100
one finding is that upon completion of

2517
02:28:39,100 --> 02:28:43,201
that project, the cross bonds were not

2518
02:28:46,100 --> 02:28:47,100
reinstalled. However, since have been

2519
02:28:47,100 --> 02:28:48,100
reinstalled.

2520
02:28:48,100 --> 02:28:51,100
>> Thank you. I should also

2521
02:28:51,100 --> 02:28:54,601
because this happened in 2020 and run

2522
02:28:57,100 --> 02:29:00,100
in this configuration for 4-5 years

2523
02:29:00,100 --> 02:29:02,100
it's not considered root cause, but

2524
02:29:02,100 --> 02:29:03,100
taken together with the previous

2525
02:29:03,100 --> 02:29:06,100
finding and this as well, we're looking

2526
02:29:06,100 --> 02:29:09,100
at cumulative impact. So this is being

2527
02:29:09,100 --> 02:29:10,100
analyzed through low-flow modeling.

2528
02:29:10,100 --> 02:29:14,100
>> We did, since you added more, we

2529
02:29:14,100 --> 02:29:16,100
did talk through why would those cross

2530
02:29:16,100 --> 02:29:19,601
bonds been removed during 2020 and when

2531
02:29:21,100 --> 02:29:23,100
I said negative return going back

2532
02:29:23,100 --> 02:29:25,100
through the running rails. So those

2533
02:29:25,100 --> 02:29:27,100
cross bonds connect the rails together.

2534
02:29:27,100 --> 02:29:29,100
So there was a concern from the team

2535
02:29:29,100 --> 02:29:31,100
working on that one sets of tracks

2536
02:29:31,100 --> 02:29:33,100
while we were single tracking on the

2537
02:29:33,100 --> 02:29:37,100
other side of the tracks there may be a

2538
02:29:37,100 --> 02:29:39,100
potential for feeling that current.

2539
02:29:39,100 --> 02:29:41,100
There are other ways to make sure that

2540
02:29:41,100 --> 02:29:43,100
doesn't happen, and so this was, I

2541
02:29:43,100 --> 02:29:45,100
think, put in place as kind of an extra

2542
02:29:45,100 --> 02:29:49,100
measure, just to make sure that those

2543
02:29:49,100 --> 02:29:51,100
two tracks were isolated.

2544
02:29:51,100 --> 02:29:54,100
>> In order to take a closer look at

2545
02:29:54,100 --> 02:29:58,100
what might be happening on the power

2546
02:29:58,100 --> 02:30:00,100
system, the Parsons team recommended

2547
02:30:00,100 --> 02:30:02,100
installing the power quality monitors

2548
02:30:02,100 --> 02:30:07,100
on the top left you will see a photo of

2549
02:30:07,100 --> 02:30:10,601
an actual PQA from this investigation,

2550
02:30:11,100 --> 02:30:14,601
PQA being power quality analyzer and

2551
02:30:17,100 --> 02:30:19,100
load monitoring tests were performed to

2552
02:30:19,100 --> 02:30:21,100
look at incoming power quality and

2553
02:30:21,100 --> 02:30:24,100
looking closely at the incoming current

2554
02:30:24,100 --> 02:30:26,100
and incoming voltage into that

2555
02:30:26,100 --> 02:30:29,100
Substation, as well as recording any

2556
02:30:29,100 --> 02:30:32,601
harmonics. If you not familiar with

2557
02:30:33,100 --> 02:30:37,100
the term "harmonics" think of them as

2558
02:30:37,100 --> 02:30:40,100
unwanted frequency and harmonics are

2559
02:30:43,100 --> 02:30:47,801
not of interest on this side, but could

2560
02:30:50,100 --> 02:30:52,100
result in a change in the D.C. ripple

2561
02:30:52,100 --> 02:30:55,100
and what we mean by D.C. ripple? So on

2562
02:30:55,100 --> 02:30:58,601
the typical Substation with a thousand

2563
02:31:00,100 --> 02:31:02,100
volt D.C. output much like a D.C.

2564
02:31:02,100 --> 02:31:05,100
battery, you would expect that to be a

2565
02:31:05,100 --> 02:31:06,100
constant voltage, but in practice it

2566
02:31:06,100 --> 02:31:09,100
does come with a small amount of

2567
02:31:09,100 --> 02:31:12,100
ripple. That ripple is normal. These

2568
02:31:12,100 --> 02:31:15,100
are 12 pulse rectifiers, and through

2569
02:31:15,100 --> 02:31:19,100
the process to take AC and rectify it,

2570
02:31:19,100 --> 02:31:22,100
it's never possible to completely

2571
02:31:25,100 --> 02:31:28,100
eliminate that ripple. What we were

2572
02:31:28,100 --> 02:31:31,100
looking at is did that increase? With

2573
02:31:31,100 --> 02:31:33,100
all of the minor changes here and

2574
02:31:33,100 --> 02:31:37,201
there, did that D.C. ripple look

2575
02:31:38,100 --> 02:31:41,100
different? And there were additional

2576
02:31:43,100 --> 02:31:45,100
loggers. BART took proactive measures

2577
02:31:45,100 --> 02:31:48,100
before the Parsons team started to

2578
02:31:48,100 --> 02:31:50,100
install D.C. loggers. So similar to

2579
02:31:50,100 --> 02:31:53,100
the AC loggers installed through this

2580
02:31:53,100 --> 02:31:55,100
investigation there were D.C. loggers

2581
02:31:55,100 --> 02:31:58,601
looking at the output of the

2582
02:31:59,100 --> 02:32:01,100
Substations. The power quality

2583
02:32:01,100 --> 02:32:03,100
analyzers installed to look at AC side

2584
02:32:03,100 --> 02:32:06,100
coming in. So that gives our team a

2585
02:32:06,100 --> 02:32:09,100
complete picture, and that data is

2586
02:32:09,100 --> 02:32:12,601
currently being analyzed in, in fact,

2587
02:32:14,100 --> 02:32:16,100
those power quality analyzers are in

2588
02:32:16,100 --> 02:32:18,100
place at the MTW Substation and they

2589
02:32:18,100 --> 02:32:20,100
were installed on the East Bay side at

2590
02:32:20,100 --> 02:32:25,100
KPS and on the West Bay side at MTW.

2591
02:32:25,100 --> 02:32:29,201
What was very interesting is that MTW

2592
02:32:31,100 --> 02:32:33,100
incoming voltage was higher than

2593
02:32:33,100 --> 02:32:35,100
expected. If you can squint enough you

2594
02:32:35,100 --> 02:32:40,100
might be able to see on the a phase,

2595
02:32:40,100 --> 02:32:44,100
815 volt and 810 on B and C. So this

2596
02:32:44,100 --> 02:32:48,201
is not the 34.5 coming in. In between

2597
02:32:51,100 --> 02:32:53,100
the transformer and rectifier, that

2598
02:32:53,100 --> 02:32:56,100
line to line voltage should be 783.

2599
02:32:56,100 --> 02:32:58,100
That is how we know it's higher. When

2600
02:32:58,100 --> 02:33:00,100
we account for the term ratio, we

2601
02:33:00,100 --> 02:33:02,100
calculate that back and we were able to

2602
02:33:02,100 --> 02:33:05,100
determine that basically what that

2603
02:33:05,100 --> 02:33:08,601
means is instead of 34.5 coming in,

2604
02:33:09,100 --> 02:33:14,401
it's closer to 35.5 on the B and C and

2605
02:33:16,100 --> 02:33:19,100
36.5 on the A. Overall this is a

2606
02:33:19,100 --> 02:33:21,100
change of less than 5%, which is

2607
02:33:21,100 --> 02:33:24,100
considered to be a tolerable limit.

2608
02:33:24,100 --> 02:33:27,100
What we are currently looking at is

2609
02:33:27,100 --> 02:33:31,201
what were the harmonics with that and

2610
02:33:34,100 --> 02:33:36,100
resulting in frequencies on the D.C.

2611
02:33:36,100 --> 02:33:38,100
side that perhaps the vehicles cannot

2612
02:33:38,100 --> 02:33:40,100
tolerate? The vehicles are equipped

2613
02:33:40,100 --> 02:33:43,100
with line filters so they are designed

2614
02:33:43,100 --> 02:33:46,601
to handle these types of variations,

2615
02:33:48,100 --> 02:33:50,100
but the analysis requires further look

2616
02:33:50,100 --> 02:33:52,100
in terms of modeling and calculations

2617
02:33:52,100 --> 02:33:55,100
to actually quantify that value. There

2618
02:33:55,100 --> 02:33:57,100
are -- there are also standards that

2619
02:33:57,100 --> 02:34:01,100
govern this, the en standards and ICC

2620
02:34:01,100 --> 02:34:03,401
standards look particularly at

2621
02:34:05,100 --> 02:34:06,100
electromagnet capability and immune

2622
02:34:06,100 --> 02:34:07,100
limits for the system and that is also

2623
02:34:07,100 --> 02:34:11,100
part of the analysis being performed by

2624
02:34:11,100 --> 02:34:12,100
this time.

2625
02:34:12,100 --> 02:34:15,601
>> To recap one thing said, some

2626
02:34:22,100 --> 02:34:24,100
fluctuation is expected and 5% is

2627
02:34:24,100 --> 02:34:27,100
tolerable. As long as it's -- not

2628
02:34:27,100 --> 02:34:29,100
sustained; right? Like a sustained

2629
02:34:29,100 --> 02:34:31,100
ripple could be a more problematic.

2630
02:34:31,100 --> 02:34:34,100
But also something that we have for

2631
02:34:34,100 --> 02:34:36,100
next steps and opportunities for

2632
02:34:36,100 --> 02:34:38,100
improvements right now in order to do

2633
02:34:38,100 --> 02:34:40,100
this, maintenance has to go out and put

2634
02:34:40,100 --> 02:34:42,100
a logger there physically. So it's

2635
02:34:42,100 --> 02:34:45,100
kind of a snapshot in time while that

2636
02:34:45,100 --> 02:34:47,100
logger is there. So outside of that

2637
02:34:47,100 --> 02:34:50,100
time, we're not sure when that is going

2638
02:34:50,100 --> 02:34:53,100
up or down? So looking for remote

2639
02:34:53,100 --> 02:34:56,100
monitoring tools that would allow us to

2640
02:34:56,100 --> 02:34:58,100
do this logging in realtime moving

2641
02:34:58,100 --> 02:35:00,100
forward is one of our recommendations.

2642
02:35:00,100 --> 02:35:03,601
>> Thank you. And with the hypothesis

2643
02:35:06,100 --> 02:35:07,100
that small incremental changes may have

2644
02:35:07,100 --> 02:35:10,100
led to an increase in that D.C. ripple,

2645
02:35:10,100 --> 02:35:13,100
the BART data loggers were looked at,

2646
02:35:13,100 --> 02:35:17,100
and the output did seem to be

2647
02:35:17,100 --> 02:35:19,100
consistent with D.C. ripple oof the

2648
02:35:19,100 --> 02:35:21,100
normal limits, but that does not mean

2649
02:35:21,100 --> 02:35:23,100
that they are outside of the tolerable

2650
02:35:23,100 --> 02:35:26,100
limits. That is why the calculations

2651
02:35:26,100 --> 02:35:28,100
are necessary. So in addition to that,

2652
02:35:28,100 --> 02:35:32,100
now we'll talk more about the negative

2653
02:35:32,100 --> 02:35:34,100
return and grounding and bonding. So

2654
02:35:34,100 --> 02:35:36,100
again thanks to the BART structures

2655
02:35:36,100 --> 02:35:39,601
team and BART M & E, inspections

2656
02:35:42,100 --> 02:35:44,100
through the TransBay Tube to field

2657
02:35:44,100 --> 02:35:47,100
verify all the negative return cables.

2658
02:35:47,100 --> 02:35:48,100
We talked briefly about the

2659
02:35:48,100 --> 02:35:50,100
correspondence and I won't repeat that.

2660
02:35:50,100 --> 02:35:53,100
There was some electrical tests

2661
02:35:53,100 --> 02:35:55,100
performed and what we can see there in

2662
02:35:55,100 --> 02:35:59,801
the lower left corner is a fluke meter.

2663
02:36:00,100 --> 02:36:03,100
Just looking at the resistance in

2664
02:36:03,100 --> 02:36:05,100
particular. This time between the

2665
02:36:05,100 --> 02:36:09,201
running rail and the track slab. And

2666
02:36:10,100 --> 02:36:12,100
in two places along the tunnel, that

2667
02:36:12,100 --> 02:36:14,100
resistance was low. We don't expect it

2668
02:36:14,100 --> 02:36:17,100
to be low. We want the running rail to

2669
02:36:17,100 --> 02:36:20,100
be insulated from the track slab.

2670
02:36:20,100 --> 02:36:23,601
There were further tests performed in

2671
02:36:24,100 --> 02:36:27,100
particular look at the Negative

2672
02:36:29,100 --> 02:36:32,100
Grounding Device, if you are not

2673
02:36:32,100 --> 02:36:34,100
familiar, the running rails can -- the

2674
02:36:34,100 --> 02:36:37,100
rail potential can increase to slightly

2675
02:36:37,100 --> 02:36:40,100
higher voltage. Once it reach a

2676
02:36:40,100 --> 02:36:43,100
specific set point, those NGDs will

2677
02:36:43,100 --> 02:36:47,100
Fire and that is a safety device. So

2678
02:36:47,100 --> 02:36:49,100
the NGD at Powell was found to be

2679
02:36:49,100 --> 02:36:53,100
shorted. That was taken care of by the

2680
02:36:53,100 --> 02:36:55,100
BART team. And after that, we did see

2681
02:36:55,100 --> 02:36:58,100
an overall improvement in those

2682
02:36:59,100 --> 02:37:01,100
resistance values.

2683
02:37:08,100 --> 02:37:12,201
>> So moving on to the third rail

2684
02:37:13,100 --> 02:37:15,100
insulators looking at extensive

2685
02:37:15,100 --> 02:37:17,100
including wayside inspections and

2686
02:37:17,100 --> 02:37:19,100
off-site inspections. A number of

2687
02:37:19,100 --> 02:37:21,100
insulators with were taken to an

2688
02:37:21,100 --> 02:37:24,100
oversight lab, pictured in the bottom

2689
02:37:24,100 --> 02:37:26,100
right in various conditions. Several

2690
02:37:26,100 --> 02:37:28,100
as founding and two new. The tests

2691
02:37:28,100 --> 02:37:31,100
performed in two different labs

2692
02:37:31,100 --> 02:37:33,401
actually included destructive testing

2693
02:37:34,100 --> 02:37:36,100
and non-destructive testing. Some of

2694
02:37:36,100 --> 02:37:38,100
the observations in the lab including

2695
02:37:38,100 --> 02:37:40,100
the forensic testing that was

2696
02:37:40,100 --> 02:37:43,100
performed, the surface layer of dirt on

2697
02:37:43,100 --> 02:37:46,100
some of those insulators was found to

2698
02:37:46,100 --> 02:37:48,100
be conductive at least on the ones that

2699
02:37:48,100 --> 02:37:50,100
were tested in the lab. And the shims,

2700
02:37:50,100 --> 02:37:52,100
which are the thin layers of material

2701
02:37:52,100 --> 02:37:55,100
that sit beneath the insulators help

2702
02:37:55,100 --> 02:37:58,601
adjust the height of insulators were

2703
02:38:01,100 --> 02:38:05,201
found to be damp. These findings are

2704
02:38:14,100 --> 02:38:18,100
not perceived to be the root cause and

2705
02:38:18,100 --> 02:38:21,100
there appears to be other factors that

2706
02:38:21,100 --> 02:38:24,100
may have initiated some of these

2707
02:38:24,100 --> 02:38:27,100
insulator failures and it's also worth

2708
02:38:27,100 --> 02:38:31,201
noting that not all of the incidents

2709
02:38:32,100 --> 02:38:33,100
included insulator failures. So

2710
02:38:33,100 --> 02:38:36,100
another finding we'll touch on later is

2711
02:38:36,100 --> 02:38:38,100
rail relay storage practices.

2712
02:38:38,100 --> 02:38:40,100
>> Sorry, if you don't mind, if I

2713
02:38:40,100 --> 02:38:42,100
could jump in one -- real quickly on

2714
02:38:42,100 --> 02:38:45,100
the insulators just to follow-up from

2715
02:38:45,100 --> 02:38:48,100
the earlier conversation. So there's

2716
02:38:48,100 --> 02:38:51,100
also been news reports that we are

2717
02:38:51,100 --> 02:38:52,100
cleaning the insulators and that is

2718
02:38:52,100 --> 02:38:56,201
partially true. We have cleaned all of

2719
02:38:57,100 --> 02:39:00,100
our insulators from Embarcadero to 24th

2720
02:39:00,100 --> 02:39:01,100
and Mission. We did that primarily

2721
02:39:01,100 --> 02:39:03,100
because we had incidents in this area,

2722
02:39:03,100 --> 02:39:06,100
which we're focusing on the root cause

2723
02:39:06,100 --> 02:39:10,100
now, but it takes a crew of eight

2724
02:39:10,100 --> 02:39:13,601
overnight to do 20 insulators. We have

2725
02:39:14,100 --> 02:39:16,401
over 100,000 insulator and varying

2726
02:39:20,100 --> 02:39:21,100
degrees of maintenance across the

2727
02:39:21,100 --> 02:39:22,100
industry. So I want to put out and

2728
02:39:22,100 --> 02:39:26,100
clarify we're not planning to clean all

2729
02:39:26,100 --> 02:39:29,100
100,000 plus insulators, but this area.

2730
02:39:38,100 --> 02:39:40,100
Thank you, Zara.

2731
02:39:40,100 --> 02:39:42,100
>> Let's go back one slide to point

2732
02:39:42,100 --> 02:39:45,601
out that the team has extensive

2733
02:39:51,100 --> 02:39:53,401
experience in analyzing insulator

2734
02:40:00,100 --> 02:40:01,100
failure. This is how we're able to for

2735
02:40:01,100 --> 02:40:04,601
example to determine if the insulator

2736
02:40:05,100 --> 02:40:08,100
was root cause or not? So looking at

2737
02:40:08,100 --> 02:40:10,100
the red and Black line that represents

2738
02:40:10,100 --> 02:40:12,100
the coverboard and thicker gray block

2739
02:40:12,100 --> 02:40:14,100
beneath it represents the third rail.

2740
02:40:14,100 --> 02:40:16,100
It's as if you are standing in front

2741
02:40:16,100 --> 02:40:20,100
and facing the third rail. The white

2742
02:40:20,100 --> 02:40:23,100
rectangles with the blue underneath

2743
02:40:23,100 --> 02:40:26,100
represent undamaged insulators, and the

2744
02:40:28,100 --> 02:40:30,100
red represents damaged insulators. In

2745
02:40:30,100 --> 02:40:34,100
this case we'll start with the yellow

2746
02:40:34,100 --> 02:40:36,100
oval with damage noted to the top of

2747
02:40:36,100 --> 02:40:39,100
the coverboard that would be

2748
02:40:39,100 --> 02:40:42,100
consistent with that damage from at the

2749
02:40:42,100 --> 02:40:44,100
top-down from an initiating source. We

2750
02:40:44,100 --> 02:40:48,201
also can see here when insulators fail

2751
02:40:51,100 --> 02:40:54,100
there's a characteristic usually aligned

2752
02:40:56,100 --> 02:40:59,100
with it and not in all cases, but we

2753
02:40:59,100 --> 02:41:02,100
saw it in location 8 and location c and

2754
02:41:02,100 --> 02:41:06,100
we have a team of Fire/Life Safety

2755
02:41:06,100 --> 02:41:08,100
experts on this panel that have being

2756
02:41:08,100 --> 02:41:11,100
involved in this review. And what is

2757
02:41:11,100 --> 02:41:13,100
interesting too, is that it does tail

2758
02:41:13,100 --> 02:41:16,100
left in the direction of travel. But

2759
02:41:16,100 --> 02:41:18,100
the most interesting finding is that

2760
02:41:18,100 --> 02:41:21,100
pattern did not exist behind insulator

2761
02:41:21,100 --> 02:41:24,100
B. It was nowhere to be found. The

2762
02:41:24,100 --> 02:41:26,100
wall was relatively clean, the tunnel

2763
02:41:26,100 --> 02:41:30,100
wall. But what was interesting is that

2764
02:41:30,100 --> 02:41:31,100
it was projected downwards onto the

2765
02:41:31,100 --> 02:41:35,201
track slab and in the direction of

2766
02:41:36,100 --> 02:41:38,100
travel. So the hypothesis that is

2767
02:41:38,100 --> 02:41:40,100
under evaluation right now is that

2768
02:41:40,100 --> 02:41:44,100
insulator b did not fail on its own.

2769
02:41:44,100 --> 02:41:48,100
It was an initiating event from above.

2770
02:41:48,100 --> 02:41:51,100
A D.C. arcing event, and we'll look at

2771
02:41:51,100 --> 02:41:55,201
some of the actual photos from this

2772
02:41:57,100 --> 02:42:01,100
incident. So once A then B would have

2773
02:42:01,100 --> 02:42:05,100
failed in quick succession, as well as

2774
02:42:05,100 --> 02:42:09,201
C. We're still evaluating A. This is

2775
02:42:12,100 --> 02:42:15,601
under analysis in that initiating was

2776
02:42:16,100 --> 02:42:19,100
at play in insulator A. On the top

2777
02:42:19,100 --> 02:42:22,100
right is a photo of the coverboard I

2778
02:42:22,100 --> 02:42:23,100
mentioned and stepped profile on the

2779
02:42:23,100 --> 02:42:25,100
top of that coverboard, where it's

2780
02:42:25,100 --> 02:42:27,100
evident based on this evidence that the

2781
02:42:27,100 --> 02:42:31,100
damage was from the top-down. It also

2782
02:42:31,100 --> 02:42:33,100
aligns with the area of the material

2783
02:42:33,100 --> 02:42:36,100
loss in the third rail. So for third

2784
02:42:36,100 --> 02:42:38,100
rail to have essentially a hole in it

2785
02:42:38,100 --> 02:42:42,801
of that size, that is typically due to

2786
02:42:43,100 --> 02:42:45,100
high-energy arcing. That would be the

2787
02:42:45,100 --> 02:42:47,100
type of energy required to essentially

2788
02:42:47,100 --> 02:42:50,601
vaporize that metal in that location.

2789
02:42:52,100 --> 02:42:56,100
And that is beneath it is the remnants

2790
02:42:56,100 --> 02:42:59,601
of the insulator and the deposition

2791
02:43:03,100 --> 02:43:07,100
pattern and the left is how looks on C,

2792
02:43:07,100 --> 02:43:09,100
directly behind where the insulator

2793
02:43:09,100 --> 02:43:10,100
stood.

2794
02:43:10,100 --> 02:43:14,100
>> I wanted to add here just to again

2795
02:43:14,100 --> 02:43:19,100
give kind of a level of the effort that

2796
02:43:19,100 --> 02:43:21,100
was put. Not only was this kind of

2797
02:43:21,100 --> 02:43:24,100
detail looked at, but even that when

2798
02:43:24,100 --> 02:43:27,100
you see that splatter behind it on the

2799
02:43:27,100 --> 02:43:29,100
wall, scrapings were taken of that and

2800
02:43:29,100 --> 02:43:30,100
sent to a forensic lab to determine

2801
02:43:30,100 --> 02:43:32,100
what materials that was as part of the

2802
02:43:32,100 --> 02:43:34,100
investigation? Just to give you a

2803
02:43:34,100 --> 02:43:37,100
little bit more context on how detailed

2804
02:43:37,100 --> 02:43:40,100
and how thorough the investigation has

2805
02:43:40,100 --> 02:43:44,801
been. So in addition, just to be very

2806
02:43:45,100 --> 02:43:48,100
thorough the team also looked at the

2807
02:43:48,100 --> 02:43:51,100
protection scheme and the third rail is

2808
02:43:51,100 --> 02:43:55,201
protected by D.C. breakers, like at

2809
02:43:59,100 --> 02:44:02,100
home, but much larger that can trip and

2810
02:44:02,100 --> 02:44:04,100
isolate faults. The review of the

2811
02:44:04,100 --> 02:44:08,201
records revealed that, in fact, that --

2812
02:44:10,100 --> 02:44:11,100
typically the D.C. breakers have an

2813
02:44:11,100 --> 02:44:15,201
ability to trip without an MPR. The

2814
02:44:16,100 --> 02:44:19,100
MPR is Multi-Function Protection Relay

2815
02:44:19,100 --> 02:44:20,100
that helps customize settings. We can

2816
02:44:20,100 --> 02:44:23,100
think of it as an additional layer of

2817
02:44:23,100 --> 02:44:25,100
protection. When based on the review

2818
02:44:25,100 --> 02:44:28,100
of the reports, these functions have

2819
02:44:28,100 --> 02:44:30,100
been disabled during the time of the

2820
02:44:30,100 --> 02:44:34,201
incidents. Now that does not mean that

2821
02:44:35,100 --> 02:44:36,100
the breakers didn't have the ability to

2822
02:44:36,100 --> 02:44:38,100
trip because they have a mechanism, but

2823
02:44:38,100 --> 02:44:40,100
they are more basic. It would have

2824
02:44:40,100 --> 02:44:43,601
relied on that basic mechanism. So

2825
02:44:45,100 --> 02:44:46,100
further RFIs were submitted and we

2826
02:44:46,100 --> 02:44:49,100
asked why they were disabled? And the

2827
02:44:49,100 --> 02:44:53,100
reason that was provided is that they

2828
02:44:53,100 --> 02:44:56,601
were nuisance tripping in the opinion

2829
02:44:57,100 --> 02:44:59,100
upon return to service and perhaps

2830
02:44:59,100 --> 02:45:02,100
Sylvia might want to weigh-in.

2831
02:45:02,100 --> 02:45:04,100
>> There's apparently nuisance

2832
02:45:04,100 --> 02:45:06,100
tripping that impacted being able to

2833
02:45:06,100 --> 02:45:07,100
run cars in the morning, like

2834
02:45:07,100 --> 02:45:10,100
consistently every morning. So we

2835
02:45:10,100 --> 02:45:14,100
found that they disabled these in order

2836
02:45:14,100 --> 02:45:16,100
to make sure that trains were running

2837
02:45:16,100 --> 02:45:20,100
smoothly. I also want to add though

2838
02:45:20,100 --> 02:45:22,100
these this had a been replaced and you

2839
02:45:22,100 --> 02:45:25,100
see the old one versus the new one,

2840
02:45:25,100 --> 02:45:28,100
although to me they don't look a whole

2841
02:45:28,100 --> 02:45:30,100
lot different. Our MPRs in our system

2842
02:45:30,100 --> 02:45:33,100
have been aging and a lot of them are

2843
02:45:33,100 --> 02:45:35,100
within 20-25 years old. We do have a

2844
02:45:35,100 --> 02:45:39,201
project, and we have had an ongoing

2845
02:45:41,100 --> 02:45:43,100
project to replace MPRs. We're about

2846
02:45:43,100 --> 02:45:46,100
60% done with that, about $20-22

2847
02:45:51,100 --> 02:45:54,100
million and should be completed within

2848
02:45:54,100 --> 02:45:57,601
months, but had not been completed.

2849
02:46:00,100 --> 02:46:03,601
>> Moving on to vehicles and includes

2850
02:46:05,100 --> 02:46:08,100
vehicle specialists, from actually all

2851
02:46:09,100 --> 02:46:13,100
over the world we'll start with the

2852
02:46:13,100 --> 02:46:16,100
collector shoe assembly and there is an

2853
02:46:16,100 --> 02:46:18,100
image of the typical shoe assembly and

2854
02:46:18,100 --> 02:46:20,100
bottom left shows the position on the

2855
02:46:20,100 --> 02:46:22,100
vehicle. On the bottom right is a

2856
02:46:22,100 --> 02:46:24,100
close-up view of the collector shoe and

2857
02:46:24,100 --> 02:46:26,100
the braid, and the fuse. So we'll talk

2858
02:46:26,100 --> 02:46:28,100
more about this on the next slide. I

2859
02:46:28,100 --> 02:46:32,801
just wanted to give an overview of when

2860
02:46:33,100 --> 02:46:35,100
it's actually located. Okay four of

2861
02:46:35,100 --> 02:46:36,100
these collector assemblies from the

2862
02:46:36,100 --> 02:46:39,100
instance were taken to an o site lab

2863
02:46:39,100 --> 02:46:41,100
for forensic testing.

2864
02:46:41,100 --> 02:46:43,100
?

2865
02:46:44,100 --> 02:46:46,100
>> Next slide. In addition to that

2866
02:46:46,100 --> 02:46:50,100
four fuses were provided to the Parsons

2867
02:46:50,100 --> 02:46:54,100
team by the BART vehicles team. These

2868
02:46:54,100 --> 02:46:56,100
fuses appear to exhibit a non-standard

2869
02:46:56,100 --> 02:47:00,100
failure, and they were taken to a lab

2870
02:47:00,100 --> 02:47:02,100
for further testing including forensic

2871
02:47:02,100 --> 02:47:03,100
testing. So fuses much like the fuses

2872
02:47:03,100 --> 02:47:07,100
that you find in your home appliances

2873
02:47:07,100 --> 02:47:10,100
have a fusible link that will melt if

2874
02:47:10,100 --> 02:47:13,100
the current exceeds that threshold.

2875
02:47:14,100 --> 02:47:16,100
And these fuses are different because

2876
02:47:16,100 --> 02:47:18,100
they are slightly larger, but they do

2877
02:47:18,100 --> 02:47:21,100
include that fusible link. They also

2878
02:47:21,100 --> 02:47:23,100
have quenching sand that helps

2879
02:47:23,100 --> 02:47:27,100
extinguish that arch at that point. So

2880
02:47:27,100 --> 02:47:30,100
when that fuse typically fails that we

2881
02:47:30,100 --> 02:47:33,100
would expect that to turn back, but in

2882
02:47:33,100 --> 02:47:36,100
this case, the sound remained white.

2883
02:47:36,100 --> 02:47:38,100
And we can see extensive damage to the

2884
02:47:38,100 --> 02:47:42,201
exterior of the fused body also known

2885
02:47:43,100 --> 02:47:46,100
as carbonization. The tests were

2886
02:47:48,100 --> 02:47:49,100
extensive, including an elementary

2887
02:47:49,100 --> 02:47:53,100
analyzer test on the area that looks

2888
02:47:53,100 --> 02:47:55,100
like brass. It was confirmed to be

2889
02:47:55,100 --> 02:47:59,100
brass. So those pins actually zinc or

2890
02:47:59,100 --> 02:48:01,100
zinc plated. And it was interesting

2891
02:48:01,100 --> 02:48:03,100
that brass was found there. That is

2892
02:48:03,100 --> 02:48:06,100
for brass to form with zinc, we need

2893
02:48:06,100 --> 02:48:09,100
copper and an extremely high

2894
02:48:10,100 --> 02:48:12,100
temperature. So it it's yet to be

2895
02:48:12,100 --> 02:48:14,100
confirmed, but the hypothesis is that

2896
02:48:14,100 --> 02:48:17,100
there was high-energy arcing in that

2897
02:48:17,100 --> 02:48:19,100
area. In addition to that there were

2898
02:48:19,100 --> 02:48:23,100
other signs, looking at the log. So if

2899
02:48:23,100 --> 02:48:26,601
you are not familiar with the

2900
02:48:27,100 --> 02:48:31,100
log, the braid is connected to the fuse

2901
02:48:31,100 --> 02:48:35,201
and that rectangular piece with the two

2902
02:48:37,100 --> 02:48:39,100
holes, thank you. That also has

2903
02:48:39,100 --> 02:48:41,100
material loss. You can see that

2904
02:48:41,100 --> 02:48:45,100
there's a kink in it. It's not

2905
02:48:45,100 --> 02:48:47,100
designed that way and that is another

2906
02:48:47,100 --> 02:48:50,100
sign there was perhaps high-energy

2907
02:48:50,100 --> 02:48:53,100
arcing at that point and more evidence

2908
02:48:53,100 --> 02:48:56,100
was looking closely at the end of the

2909
02:48:56,100 --> 02:48:59,100
end cap where there is beading. That

2910
02:48:59,100 --> 02:49:01,100
is basically those tiny little metal

2911
02:49:01,100 --> 02:49:04,100
balls that you can see there. That

2912
02:49:04,100 --> 02:49:08,100
would be indicative of perhaps a high

2913
02:49:08,100 --> 02:49:10,100
energy, maybe a thermal event, or arcing

2914
02:49:10,100 --> 02:49:14,100
within the end cap and it may have come

2915
02:49:14,100 --> 02:49:18,100
from the log itself. However, this is

2916
02:49:18,100 --> 02:49:21,100
still under analysis. Further testing

2917
02:49:21,100 --> 02:49:25,201
is recommended on the fuses, and we'll

2918
02:49:28,100 --> 02:49:30,100
have additional updates in the report.

2919
02:49:30,100 --> 02:49:32,100
>> The quenching sand, sorry you are

2920
02:49:32,100 --> 02:49:36,201
expecting that sand to be Black instead

2921
02:49:37,100 --> 02:49:39,100
of white. Next slide. I will start

2922
02:49:39,100 --> 02:49:42,100
with the rail storage. Zara brought it

2923
02:49:42,100 --> 02:49:46,801
up a minute ago briefly. At BART the

2924
02:49:48,100 --> 02:49:50,100
maintenance practice for years and

2925
02:49:50,100 --> 02:49:54,100
years I don't know -- like forever, has

2926
02:49:54,100 --> 02:49:58,801
been to do our rail in 800' sections.

2927
02:49:59,100 --> 02:50:01,100
And I noticed before or when talking to

2928
02:50:01,100 --> 02:50:04,100
one of the Directors about rail

2929
02:50:04,100 --> 02:50:06,100
rally and it just means replacing

2930
02:50:06,100 --> 02:50:08,100
the rail. That is our projects that we

2931
02:50:08,100 --> 02:50:11,100
do all over the place. But given the

2932
02:50:11,100 --> 02:50:14,100
short windows of maintenance windows

2933
02:50:14,100 --> 02:50:15,100
during the blanket that three hours

2934
02:50:15,100 --> 02:50:17,100
where the power is off, it take a long

2935
02:50:17,100 --> 02:50:20,100
time to get that rail moved out to the

2936
02:50:20,100 --> 02:50:23,100
right Section and then to do the work.

2937
02:50:23,100 --> 02:50:26,100
So what the practice has been is to

2938
02:50:26,100 --> 02:50:30,201
bring rail out, and place it Wayside

2939
02:50:32,100 --> 02:50:34,100
either in between the third rail and

2940
02:50:34,100 --> 02:50:36,100
running rail or between the two running

2941
02:50:36,100 --> 02:50:41,100
rail and then at a later time doing the

2942
02:50:41,100 --> 02:50:42,100
actual project BART maintenance are l

2943
02:50:42,100 --> 02:50:45,100
go out with single tracking or shut

2944
02:50:45,100 --> 02:50:47,100
down and replace the rail. They leave

2945
02:50:47,100 --> 02:50:49,100
the old rail there and over the next

2946
02:50:49,100 --> 02:50:53,201
period of time, come out during the

2947
02:50:54,100 --> 02:50:56,100
blanket and pick that rail up -- they

2948
02:50:56,100 --> 02:50:59,100
cut it into sections and take it out.

2949
02:50:59,100 --> 02:51:00,100
What the team saw, I will turn it over

2950
02:51:00,100 --> 02:51:02,100
to Zara

2951
02:51:03,100 --> 02:51:05,100
thank you, Sylvia. As part of the

2952
02:51:05,100 --> 02:51:08,100
analysis on track, one of the findings

2953
02:51:08,100 --> 02:51:10,100
was a non-standard practice to store

2954
02:51:10,100 --> 02:51:13,100
ribbon rail in the gap between the

2955
02:51:13,100 --> 02:51:15,100
rail and the third rail and to

2956
02:51:15,100 --> 02:51:18,601
accommodate that, it does appear that

2957
02:51:19,100 --> 02:51:21,100
the cantilever brackets were cutback.

2958
02:51:21,100 --> 02:51:24,100
So in the top photo you can see an

2959
02:51:24,100 --> 02:51:27,601
example of that where there's a

2960
02:51:28,100 --> 02:51:31,100
diagonal cut. That was cutback to

2961
02:51:31,100 --> 02:51:34,100
accommodate this. So why is this

2962
02:51:34,100 --> 02:51:35,100
important? Well, there was one event

2963
02:51:35,100 --> 02:51:39,100
that did appear to include the ribbon

2964
02:51:39,100 --> 02:51:42,100
rail, involved the ribbon rail that was

2965
02:51:42,100 --> 02:51:44,100
evidence of arcing found on that ribbon

2966
02:51:44,100 --> 02:51:46,100
rail itself. So yes.

2967
02:51:46,100 --> 02:51:48,100
>> Since the investigation, all that

2968
02:51:48,100 --> 02:51:50,100
rail has been removed in this area by

2969
02:51:50,100 --> 02:51:52,100
the way. And then you want to talk

2970
02:51:52,100 --> 02:51:54,401
about the insulated joints.

2971
02:51:55,100 --> 02:51:57,401
>> Insulated joints were also

2972
02:51:58,100 --> 02:52:00,100
carefully looked at. Insulates joints

2973
02:52:00,100 --> 02:52:02,100
are a normal part of the BART

2974
02:52:02,100 --> 02:52:05,100
infrastructure and typically used to

2975
02:52:05,100 --> 02:52:08,100
help with the detection of train and

2976
02:52:08,100 --> 02:52:12,100
negative return current has got to go

2977
02:52:12,100 --> 02:52:14,100
around the IJ locations that is

2978
02:52:14,100 --> 02:52:18,201
facilitated by jumpers around the IJ, the

2979
02:52:19,100 --> 02:52:22,100
D.C. current can't pass through them

2980
02:52:22,100 --> 02:52:24,100
without going around. What we noticed

2981
02:52:24,100 --> 02:52:28,201
in support of the earlier project that

2982
02:52:29,100 --> 02:52:31,100
was mentioned, IJs were installed at the

2983
02:52:31,100 --> 02:52:34,100
locations shown on that graphic. To

2984
02:52:34,100 --> 02:52:36,100
picture an IJ, there's an photo of that

2985
02:52:36,100 --> 02:52:38,100
captioned, and the graphic is showing

2986
02:52:38,100 --> 02:52:41,100
the green rectangles as the IJs that were

2987
02:52:41,100 --> 02:52:44,100
installed to support those projects.

2988
02:52:44,100 --> 02:52:46,100
And the purple was also green at one

2989
02:52:46,100 --> 02:52:49,601
time. So during the investigation, it

2990
02:52:50,100 --> 02:52:52,100
was determined that through the rail

2991
02:52:52,100 --> 02:52:55,100
relay work that was done on the M-2

2992
02:52:55,100 --> 02:52:58,100
track, so basically a new length of

2993
02:52:58,100 --> 02:53:02,201
running rail was installed on the M-2

2994
02:53:04,100 --> 02:53:06,100
track 10/12 and IJ was removed and two

2995
02:53:06,100 --> 02:53:08,100
weeks later, the other side, the

2996
02:53:08,100 --> 02:53:10,100
running rail on the other side was

2997
02:53:10,100 --> 02:53:12,100
installed, and the IJ was removed. So

2998
02:53:12,100 --> 02:53:15,100
basically for a period of two weeks,

2999
02:53:15,100 --> 02:53:17,100
there was a different operating

3000
02:53:17,100 --> 02:53:19,100
condition in play for one of the --

3001
02:53:19,100 --> 02:53:22,100
least two of the incidents. So that,

3002
02:53:22,100 --> 02:53:25,100
too, is being analyzed and again, it

3003
02:53:25,100 --> 02:53:27,100
requires modeling to fully determine

3004
02:53:27,100 --> 02:53:30,100
what the impacts are of this.

3005
02:53:30,100 --> 02:53:32,100
>> Next slide.

3006
02:53:33,100 --> 02:53:36,100
>> Finally just to be thorough, there

3007
02:53:36,100 --> 02:53:40,100
was a huge effort to look at

3008
02:53:40,100 --> 02:53:42,100
environmental factors and human and

3009
02:53:42,100 --> 02:53:46,100
external factors. So I mean the slides

3010
02:53:46,100 --> 02:53:48,100
are self-explanatory, but there's

3011
02:53:48,100 --> 02:53:50,100
evidence of water intrusion in places.

3012
02:53:50,100 --> 02:53:53,100
During one of the inspections, our team

3013
02:53:53,100 --> 02:53:56,601
also noticed there was standing water

3014
02:53:58,100 --> 02:54:00,100
in the TransBay Tube, only a small

3015
02:54:00,100 --> 02:54:04,201
area, and we submitted an RFI confirmed

3016
02:54:06,100 --> 02:54:11,100
to be due to a broken sump pump that

3017
02:54:11,100 --> 02:54:13,100
has been repaired. Generally debris as

3018
02:54:13,100 --> 02:54:16,100
you can see throughout platform area

3019
02:54:16,100 --> 02:54:19,100
and the tunnel. And rail grinding as

3020
02:54:19,100 --> 02:54:22,100
well, which I believe Shane with speak

3021
02:54:22,100 --> 02:54:25,100
more to that on the rail grinding

3022
02:54:25,100 --> 02:54:27,100
practices, because there are good

3023
02:54:27,100 --> 02:54:31,201
measures in place to minimize that. So

3024
02:54:33,100 --> 02:54:34,100
overall, because these incidents

3025
02:54:34,100 --> 02:54:37,601
happened in the TBT, the environmental

3026
02:54:38,100 --> 02:54:40,100
factors will probably remain as one of

3027
02:54:40,100 --> 02:54:41,100
the contributing factors, but not

3028
02:54:41,100 --> 02:54:43,401
necessarily the root cause.

3029
02:54:46,100 --> 02:54:48,100
>> Next slide.

3030
02:54:51,100 --> 02:54:53,100
>> So the final area is the interface.

3031
02:54:53,100 --> 02:54:56,100
The interface is basically where all

3032
02:54:56,100 --> 02:54:59,100
disciplines come together, and this is

3033
02:54:59,100 --> 02:55:02,100
where we have basically the interaction

3034
02:55:02,100 --> 02:55:05,100
of the shoe, and the third rail. The

3035
02:55:05,100 --> 02:55:08,601
team has looked at extensive data,

3036
02:55:10,100 --> 02:55:12,100
including the geo car Dator, looking at

3037
02:55:12,100 --> 02:55:15,100
track defects in particular and their

3038
02:55:15,100 --> 02:55:18,100
locations. The team also performed a

3039
02:55:18,100 --> 02:55:19,100
third rail gapping study, which

3040
02:55:19,100 --> 02:55:22,100
confirms the location of third rail

3041
02:55:22,100 --> 02:55:26,801
gaps. And one of the hypotheses is the

3042
02:55:27,100 --> 02:55:31,100
possibility of shoe bounce or a quality

3043
02:55:31,100 --> 02:55:35,100
of contact issue where a D.C. arc might

3044
02:55:35,100 --> 02:55:39,201
momentarily form, but if it does form,

3045
02:55:41,100 --> 02:55:43,100
perhaps it's being sustained, and we're

3046
02:55:43,100 --> 02:55:45,100
looking into this as a possibility.

3047
02:55:45,100 --> 02:55:49,100
But while we're looking at this it's

3048
02:55:49,100 --> 02:55:53,100
also important to remember that a small

3049
02:55:53,100 --> 02:55:57,201
amount of arcing is also normal on

3050
02:55:58,100 --> 02:56:00,100
major D.C. electrified third rail

3051
02:56:00,100 --> 02:56:02,100
systems. It's momentarily and not

3052
02:56:02,100 --> 02:56:06,201
expected to be a sustained arc. Once

3053
02:56:08,100 --> 02:56:11,100
the D.C. arc does form, it's difficult

3054
02:56:11,100 --> 02:56:12,100
to break that arc.

3055
02:56:12,100 --> 02:56:15,100
>> Next slide. These are all of the

3056
02:56:15,100 --> 02:56:18,100
improvements that have been implemented

3057
02:56:18,100 --> 02:56:20,100
while the roots cause analysis team has

3058
02:56:20,100 --> 02:56:23,100
been working on the investigation. So

3059
02:56:23,100 --> 02:56:26,100
I just want to mention that the first

3060
02:56:26,100 --> 02:56:31,100
one up there is that there was a -- not

3061
02:56:31,100 --> 02:56:34,100
our structure, but San Francisco at the

3062
02:56:34,100 --> 02:56:36,100
San Francisco transition structure,

3063
02:56:36,100 --> 02:56:38,100
there were two transformers that had

3064
02:56:38,100 --> 02:56:41,100
been out of service, one from, I think,

3065
02:56:41,100 --> 02:56:43,100
December of 2024 and one in February.

3066
02:56:43,100 --> 02:56:46,100
That has been since put back in place.

3067
02:56:46,100 --> 02:56:50,801
But all of ones with check marks is

3068
02:56:53,100 --> 02:56:54,100
what maintenance has done for instance

3069
02:56:54,100 --> 02:56:58,100
to restore the cross bond and clean

3070
02:56:58,100 --> 02:57:01,100
up debris, you know? As Michael

3071
02:57:01,100 --> 02:57:04,100
mentioned cleaning the insulators, and

3072
02:57:04,100 --> 02:57:08,100
also looking at the repairs of the

3073
02:57:08,100 --> 02:57:10,100
negative return device that one short

3074
02:57:10,100 --> 02:57:12,100
was repaired, but we're looking at all

3075
02:57:12,100 --> 02:57:15,100
of the other device as well. And

3076
02:57:15,100 --> 02:57:17,100
looking at which ones need to be

3077
02:57:17,100 --> 02:57:19,100
prioritized to be repaired or replaced.

3078
02:57:19,100 --> 02:57:21,100
There is already a project for that

3079
02:57:21,100 --> 02:57:24,601
for maintenance to do that replacement.

3080
02:57:26,100 --> 02:57:30,201
And RS & S is looking at different

3081
02:57:37,100 --> 02:57:38,100
vehicles and maintenance has removed

3082
02:57:38,100 --> 02:57:42,100
the ribbon rail and also been replacing

3083
02:57:42,100 --> 02:57:45,100
direct fixation pads, which were found

3084
02:57:45,100 --> 02:57:49,100
to also be degraded and also had some

3085
02:57:49,100 --> 02:57:52,100
moisture. Again, that is a project

3086
02:57:52,100 --> 02:57:54,100
being done by maintenance. Next slide.

3087
02:57:54,100 --> 02:57:57,100
Do you want to talk about these? So

3088
02:57:57,100 --> 02:58:00,100
in each -- I will talk about them. So

3089
02:58:00,100 --> 02:58:02,100
we said in the beginning that for each

3090
02:58:02,100 --> 02:58:05,601
incident it was most likely multiple

3091
02:58:06,100 --> 02:58:09,100
things that had caused those incidents.

3092
02:58:09,100 --> 02:58:11,100
And there wasn't, you know, even

3093
02:58:11,100 --> 02:58:14,100
though we're kind of combining these

3094
02:58:14,100 --> 02:58:16,100
into categories, there wasn't like one

3095
02:58:16,100 --> 02:58:17,100
thing that affected every single

3096
02:58:17,100 --> 02:58:21,100
incident. So this is just kind of a

3097
02:58:21,100 --> 02:58:22,100
breakdown of the incidents that

3098
02:58:22,100 --> 02:58:25,100
happened, and what were the potential

3099
02:58:25,100 --> 02:58:27,100
causes related to that? Again, except

3100
02:58:27,100 --> 02:58:29,100
for incident 3, where we know there was

3101
02:58:29,100 --> 02:58:32,100
a rod that fell from the ceiling, that

3102
02:58:32,100 --> 02:58:36,100
had that impact. Next slide. And next

3103
02:58:36,100 --> 02:58:38,100
steps, before I get started, I just

3104
02:58:38,100 --> 02:58:40,100
want to say the picture on the right is

3105
02:58:40,100 --> 02:58:44,100
not the BART system. It's a picture

3106
02:58:44,100 --> 02:58:47,100
from the rail inspection vehicle

3107
02:58:47,100 --> 02:58:49,100
software to use for display purposes.

3108
02:58:49,100 --> 02:58:51,100
But the next steps, there's a couple of

3109
02:58:51,100 --> 02:58:53,100
big ones. First is the finish the

3110
02:58:53,100 --> 02:58:54,100
modeling that the consultant is doing

3111
02:58:54,100 --> 02:58:58,100
of this area. They are putting in

3112
02:58:58,100 --> 02:59:01,100
every single piece of equipment,

3113
02:59:01,100 --> 02:59:02,100
everything in the system, just

3114
02:59:02,100 --> 02:59:03,100
everything having to do with that.

3115
02:59:03,100 --> 02:59:05,100
There's a couple of things that are

3116
02:59:05,100 --> 02:59:07,100
good with that. One, it's going to

3117
02:59:07,100 --> 02:59:10,100
help us run different scenarios to

3118
02:59:10,100 --> 02:59:12,100
validate the causes that we think about

3119
02:59:12,100 --> 02:59:15,100
-- that we have come up, or the team

3120
02:59:15,100 --> 02:59:18,100
has come up with. And also be able to

3121
02:59:18,100 --> 02:59:22,801
run scenarios to see if we can recreate

3122
02:59:24,100 --> 02:59:27,601
that explosion, or arcing digitally as

3123
02:59:28,100 --> 02:59:31,100
opposed to physically? We're also

3124
02:59:31,100 --> 02:59:34,100
looking at opportunities to better

3125
02:59:34,100 --> 02:59:35,100
maintain our insulators, whether that

3126
02:59:35,100 --> 02:59:37,100
means looking at different design and

3127
02:59:37,100 --> 02:59:38,100
materials being used. Nationally we

3128
02:59:38,100 --> 02:59:40,100
have already been in touch with many

3129
02:59:40,100 --> 02:59:42,100
other agencies on their cleaning

3130
02:59:42,100 --> 02:59:45,100
practices, as well as the type of

3131
02:59:45,100 --> 02:59:48,100
insulators that they use. And Zara

3132
02:59:48,100 --> 02:59:51,100
mentioned for the vehicles we're

3133
02:59:51,100 --> 02:59:53,100
conducting some additional vibration

3134
02:59:53,100 --> 02:59:56,100
studies, and tests, on the collector

3135
02:59:56,100 --> 02:59:59,100
shoes. And then for policy and

3136
02:59:59,100 --> 03:00:00,100
procedures, working with safety, I

3137
03:00:00,100 --> 03:00:03,601
think between safety and maintenance to

3138
03:00:06,100 --> 03:00:09,100
develop a configuration control type

3139
03:00:09,100 --> 03:00:11,100
document, and procedures. So that when

3140
03:00:11,100 --> 03:00:12,100
certain changes are made in the system,

3141
03:00:12,100 --> 03:00:15,100
they are signed off. Like, that

3142
03:00:15,100 --> 03:00:17,100
everybody knows that has happened, and

3143
03:00:17,100 --> 03:00:19,100
they all agree to why it happened, and

3144
03:00:19,100 --> 03:00:21,100
in that document, or in that procedure,

3145
03:00:21,100 --> 03:00:26,100
also what is the date for that to be

3146
03:00:26,100 --> 03:00:30,100
put back the way it should be. So that

3147
03:00:30,100 --> 03:00:31,100
is definitely an opportunity for

3148
03:00:31,100 --> 03:00:34,601
us. I mentioned earlier about having

3149
03:00:36,100 --> 03:00:37,100
constant continual remote monitoring,

3150
03:00:37,100 --> 03:00:39,100
and logging tools. I want to note and

3151
03:00:39,100 --> 03:00:41,100
one of the reasons that we added the

3152
03:00:41,100 --> 03:00:44,100
picture to the right, you guys, most

3153
03:00:44,100 --> 03:00:47,100
people are familiar with our rail

3154
03:00:47,100 --> 03:00:50,100
inspection vehicle. We use that for

3155
03:00:50,100 --> 03:00:54,801
mostly we have been using it mostly for

3156
03:00:55,100 --> 03:00:57,100
track, looking at track defect and

3157
03:00:57,100 --> 03:00:59,100
needs there. Just this week we started

3158
03:00:59,100 --> 03:01:01,100
running it with power on to use that

3159
03:01:01,100 --> 03:01:05,201
vehicle to look for any heat anomalies

3160
03:01:06,100 --> 03:01:08,100
or power anomalies in that area. They

3161
03:01:08,100 --> 03:01:10,100
have done two runs this week and that

3162
03:01:10,100 --> 03:01:12,100
is also something we'll evaluate the

3163
03:01:12,100 --> 03:01:16,100
data that we're getting from there and

3164
03:01:16,100 --> 03:01:19,100
how helpful that will be in future.

3165
03:01:19,100 --> 03:01:22,100
With the modeling depending how it

3166
03:01:22,100 --> 03:01:24,100
turns out it may be that we expand to

3167
03:01:24,100 --> 03:01:26,100
other places in the system to help

3168
03:01:26,100 --> 03:01:29,601
identify and be proactive about any

3169
03:01:30,100 --> 03:01:31,100
potential vulnerabilities. With that,

3170
03:01:31,100 --> 03:01:34,100
next slide. We'll take questions.

3171
03:01:39,100 --> 03:01:42,601
>> Thank you Michael, Sylvia and Zara.

3172
03:01:43,100 --> 03:01:46,100
I appreciate the very in-depth

3173
03:01:46,100 --> 03:01:47,100
presentation about these incidents.

3174
03:01:47,100 --> 03:01:49,100
Let us first turn to public comment

3175
03:01:49,100 --> 03:01:52,601
before we go to Directors comments.

3176
03:01:53,100 --> 03:01:54,100
District Secretary, who do you have for

3177
03:01:54,100 --> 03:01:55,100
us?

3178
03:01:55,100 --> 03:01:58,100
>> We have four public comments at the

3179
03:01:58,100 --> 03:02:01,601
moment. The first is Glen Overton.

3180
03:02:04,100 --> 03:02:06,401
Glen, please come up.

3181
03:02:22,100 --> 03:02:25,100
Madam President, Mr. General Manager

3182
03:02:25,100 --> 03:02:28,100
and staff, Board of Directors,

3183
03:02:33,100 --> 03:02:36,601
California in 2024 was a 4.1 billion --

3184
03:02:39,100 --> 03:02:42,601
trillion dollar economy. What part of

3185
03:02:47,100 --> 03:02:50,601
that economy does BART generate? You

3186
03:02:54,100 --> 03:02:57,100
have objective or subjective accounting

3187
03:02:58,100 --> 03:03:01,601
. I don't care whether it's objective

3188
03:03:02,100 --> 03:03:05,601
or subjective. The State needs to

3189
03:03:08,100 --> 03:03:11,100
realize its responsibility to refurbish

3190
03:03:14,100 --> 03:03:17,100
a more than 50-year-old system.

3191
03:03:30,100 --> 03:03:33,601
Those parts need changing. We take

3192
03:03:35,100 --> 03:03:39,100
care our bodies, we take care of our

3193
03:03:39,100 --> 03:03:43,201
homes, we stitch our clothes, mend our

3194
03:03:45,100 --> 03:03:49,201
socks, we don't take care of insulators?

3195
03:03:53,100 --> 03:03:55,100
Because of budget neglect or something

3196
03:03:55,100 --> 03:03:58,100
of that sort? $4.1 trillion in 2024

3197
03:04:08,100 --> 03:04:12,801
budget and all we're asking for is a

3198
03:04:13,100 --> 03:04:16,601
budget that will renew this system.

3199
03:04:18,100 --> 03:04:20,100
>> Thank you, Glen.

3200
03:04:21,100 --> 03:04:23,100
>> Jerry Grace. Followed by Barney

3201
03:04:23,100 --> 03:04:26,601
Smits, Aleta Dupree and Roland. Jerry.

3202
03:04:35,100 --> 03:04:37,100
>> Good morning. I hope this is

3203
03:04:37,100 --> 03:04:39,100
still morning. Good afternoon. I

3204
03:04:39,100 --> 03:04:43,100
don't know which is which? But I

3205
03:04:43,100 --> 03:04:47,100
appear because will you please put the

3206
03:04:47,100 --> 03:04:51,201
picture No. 13, please? I wish -- I

3207
03:04:55,100 --> 03:04:57,100
thought there was a picture. I'm

3208
03:04:57,100 --> 03:05:00,100
trying to point out to you guys about

3209
03:05:00,100 --> 03:05:04,201
the picture up there on that screen,

3210
03:05:07,100 --> 03:05:10,100
because what you used for Clipper and

3211
03:05:10,100 --> 03:05:13,100
that machine -- I brought it up last

3212
03:05:13,100 --> 03:05:16,100
time. How for me, use that machine,

3213
03:05:16,100 --> 03:05:21,100
because I do not know how to use that

3214
03:05:21,100 --> 03:05:24,100
kind of machine. Either BART's

3215
03:05:25,100 --> 03:05:28,100
machine, that one, AC Transit and the

3216
03:05:28,100 --> 03:05:31,100
one before that changed it. You have

3217
03:05:31,100 --> 03:05:33,100
San Francisco -- I don't like that one

3218
03:05:33,100 --> 03:05:36,100
too much. And the same thing I just

3219
03:05:36,100 --> 03:05:38,100
saw now, the yellow one. I don't know

3220
03:05:38,100 --> 03:05:41,100
how to use that one, and San Francisco

3221
03:05:41,100 --> 03:05:43,100
Muni one. But everybody else has the

3222
03:05:43,100 --> 03:05:47,801
same one, the gray one. Better -- the

3223
03:05:49,100 --> 03:05:51,100
yellow one, or the Muni one. I don't

3224
03:05:51,100 --> 03:05:55,100
like that one too much. I do not know

3225
03:05:55,100 --> 03:05:58,100
how to use that machine. I tried to

3226
03:05:58,100 --> 03:06:02,100
use it once before. I do not know how

3227
03:06:02,100 --> 03:06:06,201
to do it. What I'm hoping you

3228
03:06:07,100 --> 03:06:11,100
understand what I mean, please I wish

3229
03:06:11,100 --> 03:06:14,100
somebody or someone or somebody could

3230
03:06:14,100 --> 03:06:17,100
show me how to use that kind of

3231
03:06:17,100 --> 03:06:21,100
machine. I ask somebody once before in

3232
03:06:21,100 --> 03:06:24,100
San Francisco and nobody at all can

3233
03:06:24,100 --> 03:06:27,100
help me and nobody there at all to help

3234
03:06:27,100 --> 03:06:30,100
me use the machine, and add more money

3235
03:06:30,100 --> 03:06:32,401
on Clipper. Thank you.

3236
03:06:33,100 --> 03:06:36,100
>> Barney Smits. Please, go ahead.

3237
03:06:36,100 --> 03:06:39,601
>> Actually, Bob, I think GM Powers

3238
03:06:43,100 --> 03:06:44,100
was going to respond

3239
03:06:44,100 --> 03:06:48,100
I will make it my business to help Mr.

3240
03:06:48,100 --> 03:06:49,100
Grace to learn that machine,

3241
03:06:49,100 --> 03:06:50,100
Chairperson Foley.

3242
03:06:50,100 --> 03:06:51,100
>> Appreciate it, thank you.

3243
03:06:51,100 --> 03:06:52,100
>>> Barney.

3244
03:06:52,100 --> 03:06:54,100
>> Thank you. My name is Barney Smits

3245
03:06:54,100 --> 03:06:55,100
I'm a licensed professional engineer

3246
03:06:55,100 --> 03:06:58,100
with over 25 years' experience as

3247
03:06:58,100 --> 03:07:00,100
a BART engineer and Fire/Life Safety

3248
03:07:00,100 --> 03:07:02,100
expert. Looking at the report, I'm not

3249
03:07:02,100 --> 03:07:05,100
sure what the hired expert consultants

3250
03:07:05,100 --> 03:07:08,100
provided BART? There's no definitive

3251
03:07:08,100 --> 03:07:09,100
conclusion. The report does not

3252
03:07:09,100 --> 03:07:12,100
clearly present a root cause for these

3253
03:07:12,100 --> 03:07:14,100
traction power arcing flash over and

3254
03:07:14,100 --> 03:07:17,100
Fire incidents. Of the nine incidents

3255
03:07:17,100 --> 03:07:20,601
investigated in the report, one within

3256
03:07:21,100 --> 03:07:24,100
Lake Merritt station appears to be a

3257
03:07:24,100 --> 03:07:26,100
human error and the other has no

3258
03:07:26,100 --> 03:07:27,100
comment. That leaves seven incidents,

3259
03:07:27,100 --> 03:07:29,100
two of which were in the TransBay Tube.

3260
03:07:29,100 --> 03:07:32,100
What is the root cause? It's clear

3261
03:07:32,100 --> 03:07:34,100
from the report that five of the seven

3262
03:07:34,100 --> 03:07:37,601
remaining incidents have four or more

3263
03:07:38,100 --> 03:07:40,100
possible causes. And that six of the

3264
03:07:40,100 --> 03:07:42,100
seven incidents have traction power

3265
03:07:42,100 --> 03:07:45,100
transients as a cause and all seven

3266
03:07:45,100 --> 03:07:48,100
incidents have environmental factors as

3267
03:07:49,100 --> 03:07:52,100
a cause. Defined as metal dust, rail

3268
03:07:52,100 --> 03:07:54,100
dust, on the insulator and moisture in

3269
03:07:54,100 --> 03:07:57,100
the air. While some tunnels are very

3270
03:07:57,100 --> 03:07:59,100
wet like the poorly could be structed

3271
03:07:59,100 --> 03:08:01,100
tunnel from Colma to the airport, they

3272
03:08:01,100 --> 03:08:04,100
are not relevant. The TransBay Tube is

3273
03:08:04,100 --> 03:08:06,100
very dry. So approximately five of the

3274
03:08:06,100 --> 03:08:09,100
seven incidents are in try areas,

3275
03:08:09,100 --> 03:08:12,100
leaving metal rail dust as the most

3276
03:08:12,100 --> 03:08:13,100
likely root caused. Since insulator

3277
03:08:13,100 --> 03:08:16,601
cleaning stopped five years ago, but

3278
03:08:17,100 --> 03:08:18,100
was restored in December, note eight

3279
03:08:18,100 --> 03:08:21,100
incidents took place in the three

3280
03:08:21,100 --> 03:08:23,100
months between late August and late

3281
03:08:23,100 --> 03:08:26,100
November. And only one incident under

3282
03:08:26,100 --> 03:08:28,100
investigation has happened since the

3283
03:08:28,100 --> 03:08:31,100
cleaning of the insulators restarted in

3284
03:08:31,100 --> 03:08:34,100
December. The missing cross bonds are

3285
03:08:34,100 --> 03:08:36,100
likely a contributing factor as

3286
03:08:36,100 --> 03:08:38,100
electrical power will choose the

3287
03:08:38,100 --> 03:08:39,100
shortest distance to complete the

3288
03:08:39,100 --> 03:08:41,100
circuit and the missing cross bonds

3289
03:08:41,100 --> 03:08:44,100
forced it to move down the dust

3290
03:08:44,100 --> 03:08:47,100
costed insulators and note the

3291
03:08:47,100 --> 03:08:48,100
significant coverboard damage that

3292
03:08:48,100 --> 03:08:50,100
indicates Fire and is the source of the

3293
03:08:50,100 --> 03:08:54,201
smoke had a hindered the operations in

3294
03:09:00,100 --> 03:09:01,100
the TransBay Tube. Thank you.

3295
03:09:01,100 --> 03:09:03,401
>> Thank you, Barney. Next

3296
03:09:06,100 --> 03:09:07,100
speaker is Aleta Dupree.

3297
03:09:07,100 --> 03:09:10,100
>> Thank you, Chair Mark Foley and

3298
03:09:10,100 --> 03:09:13,100
Members. Aleta Dupree, for the record,

3299
03:09:13,100 --> 03:09:16,100
she and her representing team folds,

3300
03:09:16,100 --> 03:09:17,100
swearing skirt folds. Thank you for

3301
03:09:17,100 --> 03:09:19,100
the report. I think it's comprehensive

3302
03:09:19,100 --> 03:09:22,100
and helpful and I like going to the

3303
03:09:22,100 --> 03:09:24,100
force. These incidents are like

3304
03:09:24,100 --> 03:09:26,100
snowflakes, none is really like the

3305
03:09:26,100 --> 03:09:29,100
other. They may have common themes.

3306
03:09:29,100 --> 03:09:33,201
But they still have difference even if

3307
03:09:34,100 --> 03:09:36,100
they are nuanced. Arcing in the system

3308
03:09:36,100 --> 03:09:38,100
does happen. I go to New York and I

3309
03:09:38,100 --> 03:09:40,100
see arcing in the subway all the time.

3310
03:09:40,100 --> 03:09:44,801
I was riding a METRO North train from

3311
03:09:46,100 --> 03:09:48,100
New Haven Connecticut and I was in the

3312
03:09:48,100 --> 03:09:51,100
big running through the big railyard

3313
03:09:51,100 --> 03:09:54,601
that lead into Grand Central Terminal

3314
03:09:59,100 --> 03:10:01,100
located in New York City and maybe 20

3315
03:10:01,100 --> 03:10:05,100
tracks wide there was a big bang flash

3316
03:10:05,100 --> 03:10:09,100
that lit up the whole tunnel. I think

3317
03:10:09,100 --> 03:10:12,100
it kicked up dust, that is arcing for

3318
03:10:12,100 --> 03:10:14,100
you and we perceive it as normal and

3319
03:10:14,100 --> 03:10:18,100
I'm sure they have ways that they saw

3320
03:10:18,100 --> 03:10:20,100
what happened and addressed it. I

3321
03:10:20,100 --> 03:10:23,100
appreciate the explanations about AC

3322
03:10:23,100 --> 03:10:25,100
and D.C., and ripple, I know it's not

3323
03:10:25,100 --> 03:10:28,100
the same thing as the wine or alcohol

3324
03:10:28,100 --> 03:10:32,801
known as ripple. You know, AC is like

3325
03:10:33,100 --> 03:10:38,401
skirt with folds and D.C. is like a

3326
03:10:41,100 --> 03:10:44,100
skirt that doesn't have folds. This is

3327
03:10:44,100 --> 03:10:47,100
what I have seen. Now how do we make

3328
03:10:47,100 --> 03:10:50,601
sure these things don't happen again?

3329
03:10:53,100 --> 03:10:56,100
And I do know Bob Powers and Michael

3330
03:10:56,100 --> 03:10:58,100
Jones our management team does take

3331
03:10:58,100 --> 03:11:02,100
very serious -- does take safety very

3332
03:11:02,100 --> 03:11:05,601
seriously to the point of being

3333
03:11:06,100 --> 03:11:07,100
paramount

3334
03:11:07,100 --> 03:11:09,100
>> I ask that you take it seriously

3335
03:11:09,100 --> 03:11:10,100
too and remember that BART is the

3336
03:11:10,100 --> 03:11:12,100
People's system. Thank you.

3337
03:11:12,100 --> 03:11:14,100
>> Thank you, Aleta.

3338
03:11:14,100 --> 03:11:17,601
>> And our last speaker is Roland,

3339
03:11:21,100 --> 03:11:24,601
Roland, please, go ahead thank you,

3340
03:11:26,100 --> 03:11:28,100
>> Good morning. Happy New Year.

3341
03:11:28,100 --> 03:11:31,100
Well, I just wanted to express my

3342
03:11:31,100 --> 03:11:33,100
personal gratitude for the quality of

3343
03:11:33,100 --> 03:11:34,100
this report.

3344
03:11:34,100 --> 03:11:38,201
And I'm going to circle back eleven

3345
03:11:40,100 --> 03:11:43,100
years to show you how to move forward

3346
03:11:43,100 --> 03:11:46,100
in terms of transparency. I'm talking

3347
03:11:46,100 --> 03:11:49,100
about the incidents when we were

3348
03:11:49,100 --> 03:11:52,601
getting voltage surges. We know now

3349
03:11:54,100 --> 03:11:57,100
the voltage, 750, 783 and we're surging

3350
03:11:57,100 --> 03:12:00,601
to 1500 volts. What was happening is

3351
03:12:03,100 --> 03:12:05,100
that people when going, profiling the

3352
03:12:05,100 --> 03:12:08,100
rail, but not picking up the shavings,

3353
03:12:08,100 --> 03:12:12,100
and what ended up happening that we

3354
03:12:12,100 --> 03:12:13,100
have two sections, with the same

3355
03:12:13,100 --> 03:12:15,100
Section of third rail at the same time

3356
03:12:15,100 --> 03:12:18,100
and that is how we ended up with 1500

3357
03:12:18,100 --> 03:12:21,100
volts. And I'm not going to get into

3358
03:12:21,100 --> 03:12:23,100
details how we eventually figured that

3359
03:12:23,100 --> 03:12:26,100
out, but what I can tell you is that

3360
03:12:26,100 --> 03:12:27,100
what I'm telling you is probably the

3361
03:12:27,100 --> 03:12:30,100
first time you ever heard of it. There

3362
03:12:30,100 --> 03:12:33,100
was a complete Blackout. There was no

3363
03:12:33,100 --> 03:12:35,100
explanation, and suddenly the problem

3364
03:12:35,100 --> 03:12:38,100
disappeared, and you know, people just

3365
03:12:38,100 --> 03:12:42,201
went on with their business. So FAST

3366
03:12:43,100 --> 03:12:45,100
forward ten-plus years and look at

3367
03:12:45,100 --> 03:12:48,100
today, the transparency, the amount of

3368
03:12:48,100 --> 03:12:51,100
analyses, and that is a direct result

3369
03:12:51,100 --> 03:12:54,100
of good governance. Thank you, BART.

3370
03:12:54,100 --> 03:12:57,100
We're in good hands. Thank you.

3371
03:12:57,100 --> 03:12:58,100
>> Thank you, Roland.

3372
03:12:58,100 --> 03:13:01,601
>> That was the last public speaker.

3373
03:13:02,100 --> 03:13:06,100
>> All right. I will now turn to

3374
03:13:06,100 --> 03:13:07,100
Director comments. I do not see any

3375
03:13:07,100 --> 03:13:10,100
Directors in the queue at this point.

3376
03:13:10,100 --> 03:13:12,100
Director Raburn.

3377
03:13:14,100 --> 03:13:17,100
>> Well, I'm first. I really don't

3378
03:13:17,100 --> 03:13:20,601
feel qualified to speak elaborately on

3379
03:13:23,100 --> 03:13:25,100
this. My academic training was no in

3380
03:13:25,100 --> 03:13:27,401
the operation of high-voltage

3381
03:13:28,100 --> 03:13:31,100
electrical systems as the BART and

3382
03:13:31,100 --> 03:13:34,100
hence I have refused to

3383
03:13:35,100 --> 03:13:37,100
speculate on the nine incidents that

3384
03:13:37,100 --> 03:13:39,100
involved power that disrupted service

3385
03:13:39,100 --> 03:13:42,100
between August 29th and December 5th.

3386
03:13:42,100 --> 03:13:45,100
Instead of I have encourage our General

3387
03:13:45,100 --> 03:13:47,100
Manager to seek explanations from

3388
03:13:47,100 --> 03:13:49,100
professionals, and implement the

3389
03:13:49,100 --> 03:13:51,100
necessary changes to end further

3390
03:13:51,100 --> 03:13:54,100
delays. That is all of our goals, I'm

3391
03:13:54,100 --> 03:13:57,100
sure. I'm satisfied that the

3392
03:13:59,100 --> 03:14:01,100
root-cause analysis report we're

3393
03:14:01,100 --> 03:14:03,401
reviewing followed a rigorous

3394
03:14:04,100 --> 03:14:06,100
investigation and scientific process.

3395
03:14:06,100 --> 03:14:10,201
Is the report conclusive? No, but it

3396
03:14:12,100 --> 03:14:13,100
identified several contributing factors

3397
03:14:13,100 --> 03:14:16,100
that BART has already changed

3398
03:14:16,100 --> 03:14:18,100
operational procedure and advanced

3399
03:14:18,100 --> 03:14:20,401
numerous infrastructure changes as

3400
03:14:23,100 --> 03:14:25,100
illustrated on page 23 of the report.

3401
03:14:25,100 --> 03:14:27,100
This allows me a degree of optimism

3402
03:14:27,100 --> 03:14:31,100
that we're doing our best to protect

3403
03:14:31,100 --> 03:14:34,601
our passengers from harm, delay. As

3404
03:14:37,100 --> 03:14:39,100
well in the near-term I anticipate

3405
03:14:39,100 --> 03:14:42,100
completing the upgrade to the 10

3406
03:14:46,100 --> 03:14:49,100
megawatt Transbay East Substation KTE

3407
03:14:51,100 --> 03:14:54,100
abbreviation to replace the 3 megawatt

3408
03:14:54,100 --> 03:14:57,100
Substation and I also anticipate the

3409
03:14:57,100 --> 03:15:00,100
operation of BART's modern rail

3410
03:15:01,100 --> 03:15:04,100
geometry car to inspect the system

3411
03:15:04,100 --> 03:15:07,601
while the system is energized. And

3412
03:15:11,100 --> 03:15:14,601
And with those additional data point

3413
03:15:15,100 --> 03:15:19,201
and removing variations in some of the

3414
03:15:21,100 --> 03:15:22,100
potential causes by correcting the

3415
03:15:22,100 --> 03:15:26,100
cross bonds, I think that is a critical

3416
03:15:26,100 --> 03:15:30,100
aspect of what we have done already.

3417
03:15:30,100 --> 03:15:36,100
So all I can say is good work so far,

3418
03:15:36,100 --> 03:15:40,100
and let's keep working at it until we

3419
03:15:40,100 --> 03:15:44,100
get it done to no defects. Thank you.

3420
03:15:44,100 --> 03:15:47,100
>> Thank you. Any other Director

3421
03:15:48,100 --> 03:15:51,100
comments? We have virtual system you

3422
03:15:51,100 --> 03:15:53,100
can use. Director Ames.

3423
03:15:53,100 --> 03:15:55,100
>> Sorry. I'm having a little

3424
03:15:55,100 --> 03:15:58,100
technical problem with my computer.

3425
03:16:00,100 --> 03:16:04,100
Okay. Sorry. I would like to go to

3426
03:16:04,100 --> 03:16:08,801
slide 3. I can't look at the slides --

3427
03:16:09,100 --> 03:16:12,100
I need some technical support. Can we

3428
03:16:12,100 --> 03:16:15,100
go to slide 3, please? Yes.

3429
03:16:24,100 --> 03:16:28,100
So on August 29th, we had an

3430
03:16:28,100 --> 03:16:30,100
evaluation. Staff did an evaluation on

3431
03:16:30,100 --> 03:16:33,100
the smoke in the tube. And it was on

3432
03:16:33,100 --> 03:16:37,100
August 29th, and we also had two other

3433
03:16:37,100 --> 03:16:41,100
incidents that I don't see on there.

3434
03:16:41,100 --> 03:16:43,100
There were three separate incidents.

3435
03:16:43,100 --> 03:16:45,100
They were not collectively the problem.

3436
03:16:45,100 --> 03:16:48,100
It was very specific, different

3437
03:16:49,100 --> 03:16:52,100
locations. So we had a power outage at

3438
03:16:52,100 --> 03:16:55,100
West Oakland in the morning around 5:00

3439
03:16:55,100 --> 03:16:56,100
a.m.

3440
03:16:56,100 --> 03:16:59,100
So that was likely due to a malfunction

3441
03:16:59,100 --> 03:17:01,100
with the switches, which maybe even

3442
03:17:01,100 --> 03:17:02,100
could equate to something that happened

3443
03:17:02,100 --> 03:17:06,100
in San Leandro, but not as bad. But we

3444
03:17:06,100 --> 03:17:07,100
lost power completely in West Oakland.

3445
03:17:07,100 --> 03:17:11,201
Then in the afternoon, there was a

3446
03:17:12,100 --> 03:17:16,100
train that lost a paddle, a car, lost a

3447
03:17:16,100 --> 03:17:19,100
paddle and a fuse was blown and there

3448
03:17:19,100 --> 03:17:23,801
was a small Fire. That was in the

3449
03:17:24,100 --> 03:17:26,100
afternoon around 2:00 and then the

3450
03:17:26,100 --> 03:17:30,801
smoke in the tunnel in the commute hour

3451
03:17:34,100 --> 03:17:36,100
at 5:00ment so I don't think

3452
03:17:36,100 --> 03:17:38,100
collectively there's are forming with

3453
03:17:38,100 --> 03:17:40,100
hypotheses and more questions. I

3454
03:17:40,100 --> 03:17:41,100
think we have isolated events that we

3455
03:17:41,100 --> 03:17:46,100
need to hone in on. I just want to --

3456
03:17:46,100 --> 03:17:49,100
so right now I don't see those

3457
03:17:49,100 --> 03:17:51,100
incidents on August 29th. Right now it

3458
03:17:51,100 --> 03:17:54,100
looks like we're just focusing on loud

3459
03:17:54,100 --> 03:17:56,100
noises insulator flashes, but I really

3460
03:17:56,100 --> 03:17:58,100
want to hone in on August 29th and get

3461
03:17:58,100 --> 03:18:00,100
more information on this. Because I do

3462
03:18:00,100 --> 03:18:03,100
think we can get to the bottom of the

3463
03:18:03,100 --> 03:18:06,100
root cause quickly. Although we have a

3464
03:18:06,100 --> 03:18:09,601
lot of good analyses that shows

3465
03:18:10,100 --> 03:18:11,100
there's room for improvement. I wanted

3466
03:18:11,100 --> 03:18:16,401
to go to like slide -- I guess 4. So

3467
03:18:19,100 --> 03:18:23,100
this to me is a slide that is telling

3468
03:18:23,100 --> 03:18:25,100
because you need to define the problem

3469
03:18:25,100 --> 03:18:28,100
before you collect the data. So did we

3470
03:18:28,100 --> 03:18:30,100
define the problem here? It doesn't

3471
03:18:30,100 --> 03:18:34,100
look like we did. We went to this

3472
03:18:34,100 --> 03:18:37,100
really giant field of possibilities,

3473
03:18:38,100 --> 03:18:40,100
and created hypotheses. So this is a

3474
03:18:40,100 --> 03:18:41,100
frustrating report, although there's a

3475
03:18:41,100 --> 03:18:44,100
lot of good data to look at, but I

3476
03:18:44,100 --> 03:18:48,201
don't see massive -- you know, studies,

3477
03:18:49,100 --> 03:18:51,100
and more follow-up in the fashion that

3478
03:18:51,100 --> 03:18:54,100
is being presented today. But so

3479
03:18:54,100 --> 03:18:57,100
again, I will go back to August 29th.

3480
03:18:57,100 --> 03:19:01,801
I would say what data did we collect

3481
03:19:02,100 --> 03:19:06,100
for example, on the outage -- power

3482
03:19:06,100 --> 03:19:07,100
outage at West Oakland? I would like

3483
03:19:07,100 --> 03:19:12,100
to know what that is. And then why are

3484
03:19:12,100 --> 03:19:15,100
we having paddles being removed off the

3485
03:19:15,100 --> 03:19:18,100
train car? And then we have got the

3486
03:19:18,100 --> 03:19:21,100
insulator problems, which is likely the

3487
03:19:21,100 --> 03:19:23,100
cause of the TransBay Tube smoke event.

3488
03:19:23,100 --> 03:19:27,801
Because I do recall when we got an

3489
03:19:29,100 --> 03:19:30,100
evaluation from Staff September 11th

3490
03:19:30,100 --> 03:19:33,601
there was a blown insulator picture.

3491
03:19:34,100 --> 03:19:37,100
That was the 29th. And we showed the

3492
03:19:37,100 --> 03:19:40,100
blown insulator, and it looked

3493
03:19:41,100 --> 03:19:44,601
conclusive it was an insulator. So

3494
03:19:45,100 --> 03:19:47,100
when we start compiling data, did you

3495
03:19:47,100 --> 03:19:50,100
-- I guess I would ask the consultant,

3496
03:19:50,100 --> 03:19:52,100
doing these RFIs and you got

3497
03:19:52,100 --> 03:19:54,100
information, did you get information on

3498
03:19:54,100 --> 03:19:57,100
the maintenance of the insulators?

3499
03:20:02,100 --> 03:20:03,100
>> Yes.

3500
03:20:03,100 --> 03:20:05,100
>> So what was the determination of

3501
03:20:05,100 --> 03:20:08,100
the maintenance on the insulators -- I

3502
03:20:08,100 --> 03:20:10,401
apologize for my voice.

3503
03:20:11,100 --> 03:20:13,100
>> Well, we reviewed all of the

3504
03:20:13,100 --> 03:20:15,100
record and it does appear there is

3505
03:20:15,100 --> 03:20:18,100
maintenance process in place for the

3506
03:20:18,100 --> 03:20:21,601
insulators. We did also obtain that

3507
03:20:22,100 --> 03:20:25,100
data on the West Oakland outage you are

3508
03:20:25,100 --> 03:20:28,601
referring to. We have looked extensive

3509
03:20:29,100 --> 03:20:33,201
as well at SCADA logs, and the

3510
03:20:37,100 --> 03:20:39,100
field fields and forensics. Overall,

3511
03:20:39,100 --> 03:20:42,601
the information is as presented here.

3512
03:20:45,100 --> 03:20:48,100
There is nothing evidence to currently

3513
03:20:48,100 --> 03:20:50,100
suggest that the insulator was the root

3514
03:20:50,100 --> 03:20:52,100
cause of that particular incident at

3515
03:20:52,100 --> 03:20:53,100
this stage.

3516
03:20:53,100 --> 03:20:54,100
>> I just want to drill-down on this

3517
03:20:54,100 --> 03:20:57,100
and to understand what was the

3518
03:20:57,100 --> 03:21:00,100
maintenance for the insulators when

3519
03:21:02,100 --> 03:21:03,100
this data collection started? I just

3520
03:21:03,100 --> 03:21:06,100
want to know what was given to the

3521
03:21:06,100 --> 03:21:09,100
consultant, and the data of what we did

3522
03:21:09,100 --> 03:21:12,100
on the insulators? What was the

3523
03:21:12,100 --> 03:21:14,100
maintenance program? So maybe you got

3524
03:21:14,100 --> 03:21:15,100
to get back to me on this.

3525
03:21:15,100 --> 03:21:18,100
>> Well, I think there's some

3526
03:21:18,100 --> 03:21:20,100
confusion. So I will speak up and go

3527
03:21:20,100 --> 03:21:23,100
from here. There is some Maximo data

3528
03:21:23,100 --> 03:21:26,100
that the consultants looked for. There

3529
03:21:26,100 --> 03:21:29,601
is also replacement projects that say

3530
03:21:30,100 --> 03:21:32,100
if there's a, you know, if there's a

3531
03:21:32,100 --> 03:21:35,100
defect or see a defect inspecting it,

3532
03:21:35,100 --> 03:21:38,100
we should replace the insulators. I

3533
03:21:38,100 --> 03:21:41,100
think what you may be getting to the

3534
03:21:41,100 --> 03:21:43,100
question is did we have a cleaning

3535
03:21:43,100 --> 03:21:45,100
process in place and the answer I think

3536
03:21:45,100 --> 03:21:47,100
is no, we did not is have a cleaning

3537
03:21:47,100 --> 03:21:48,100
protocol in place.

3538
03:21:48,100 --> 03:21:51,100
>> Can we get the information of what

3539
03:21:51,100 --> 03:21:54,100
we're doing and why we stopped the

3540
03:21:54,100 --> 03:21:56,100
cleaning? It's a question I get often

3541
03:21:56,100 --> 03:21:57,100
from the press.

3542
03:21:57,100 --> 03:21:58,100
>> Understood.

3543
03:21:58,100 --> 03:22:00,100
>> So I would like to get that and I

3544
03:22:00,100 --> 03:22:01,100
appreciate you trying to be transparent

3545
03:22:01,100 --> 03:22:03,100
on this

3546
03:22:03,100 --> 03:22:06,100
sorry, Director Ames, the last cleaning

3547
03:22:06,100 --> 03:22:07,100
program we had, my understanding we

3548
03:22:07,100 --> 03:22:10,100
were using dry ice and it was

3549
03:22:10,100 --> 03:22:13,100
deteriorating the quality of insulators

3550
03:22:15,100 --> 03:22:17,100
and why we deferred that going forward.

3551
03:22:17,100 --> 03:22:20,100
>> And to get the detail of why it was

3552
03:22:20,100 --> 03:22:22,100
happening and why it stopped, just on

3553
03:22:22,100 --> 03:22:25,601
the cleaning itself of the insulators?

3554
03:22:29,100 --> 03:22:35,100
So let's -- I think did you on the data

3555
03:22:38,100 --> 03:22:39,100
collection, maybe we can jump over to

3556
03:22:39,100 --> 03:22:42,100
another slide, because this is not very

3557
03:22:42,100 --> 03:22:46,201
exciting. We can go to the paddle,

3558
03:22:47,100 --> 03:22:51,201
showing the paddle of the train. The

3559
03:23:01,100 --> 03:23:04,601
collector paddle. You want to do

3560
03:23:05,100 --> 03:23:09,201
another slide? Yeah. So that I would

3561
03:23:15,100 --> 03:23:19,100
like to know why that paddle got

3562
03:23:19,100 --> 03:23:22,100
dislodged off the car, and how many

3563
03:23:22,100 --> 03:23:24,100
times that has happened during this

3564
03:23:24,100 --> 03:23:26,100
timeframe? So to me this is another

3565
03:23:26,100 --> 03:23:27,100
data point that is interesting, like

3566
03:23:27,100 --> 03:23:31,100
what happened? And I know you will

3567
03:23:31,100 --> 03:23:34,100
evaluate this, I guess it's called a

3568
03:23:34,100 --> 03:23:36,100
collector shoe, sorry, not called a

3569
03:23:36,100 --> 03:23:39,100
paddle. Sorry. But to find out why

3570
03:23:39,100 --> 03:23:42,100
these paddles are coming off the cars

3571
03:23:42,100 --> 03:23:44,100
is a concern. This is a separate issue

3572
03:23:44,100 --> 03:23:46,100
now. We have insulator and now we have

3573
03:23:46,100 --> 03:23:50,801
this issue. This is a car issue, train

3574
03:23:51,100 --> 03:23:54,100
car issue. And if a paddle comes off,

3575
03:23:54,100 --> 03:23:57,601
and doesn't connect with the third

3576
03:23:58,100 --> 03:24:02,100
rail, what happens to the system? Does

3577
03:24:02,100 --> 03:24:05,100
a Fire start? Does the fuse blow?

3578
03:24:05,100 --> 03:24:07,100
Because that was my understanding.

3579
03:24:07,100 --> 03:24:11,201
>> Director Ames, I'm going to ask Leo

3580
03:24:12,100 --> 03:24:13,100
Pica, our Chief rolling stock Officer to

3581
03:24:13,100 --> 03:24:16,100
answer that question. I think Zara and

3582
03:24:16,100 --> 03:24:18,100
Leo will say that is a common

3583
03:24:18,100 --> 03:24:20,100
occurrence as well. But I will let Leo

3584
03:24:20,100 --> 03:24:22,100
speak for himself.

3585
03:24:23,100 --> 03:24:25,100
>> Thank you.

3586
03:24:26,100 --> 03:24:29,100
>> Hello Directors. Leo Pica, Chief

3587
03:24:30,100 --> 03:24:31,100
Mechanical Officer RS&S. They are

3588
03:24:31,100 --> 03:24:35,100
designed to break with a notch in there

3589
03:24:35,100 --> 03:24:37,100
and when the paddle breaks, the

3590
03:24:37,100 --> 03:24:42,401
collector on the car will -- and if two

3591
03:24:44,100 --> 03:24:47,100
paddles break, the rest of the cars

3592
03:24:47,100 --> 03:24:51,100
will take over. So they are designed

3593
03:24:51,100 --> 03:24:54,100
to break, for the paddle to break

3594
03:24:54,100 --> 03:24:57,100
damage to collector assembly, that

3595
03:24:57,100 --> 03:25:01,201
Assembly with the fuse, and other items.

3596
03:25:02,100 --> 03:25:05,100
>> Is it your understanding that if a

3597
03:25:05,100 --> 03:25:08,100
paddle breaks, something -- the fuse in

3598
03:25:08,100 --> 03:25:12,201
the train car could blow from your

3599
03:25:13,100 --> 03:25:14,100
experience?

3600
03:25:14,100 --> 03:25:17,100
>> So the paddle is what connects to

3601
03:25:17,100 --> 03:25:20,100
the third rail. So once the paddle is

3602
03:25:20,100 --> 03:25:24,100
broken, no power is going to the fuse,

3603
03:25:24,100 --> 03:25:26,100
or collector assembly. And the

3604
03:25:26,100 --> 03:25:28,100
Assembly on the other side of the car

3605
03:25:28,100 --> 03:25:30,100
take over. Also when the trains

3606
03:25:30,100 --> 03:25:33,100
travel, each car has four paddles. So

3607
03:25:33,100 --> 03:25:36,100
as the train is traveling any one of

3608
03:25:36,100 --> 03:25:38,100
those paddles will collect power from

3609
03:25:38,100 --> 03:25:39,100
the third rail.

3610
03:25:39,100 --> 03:25:41,100
>> My understanding there's a surge of

3611
03:25:41,100 --> 03:25:43,100
power without the paddle and then the

3612
03:25:43,100 --> 03:25:46,601
fuse blows, is that not correct?

3613
03:25:47,100 --> 03:25:49,100
Maybe I could ask the consultant this

3614
03:25:49,100 --> 03:25:51,100
and to know the nexus between the blown

3615
03:25:51,100 --> 03:25:53,100
fuse in the train car and the paddle

3616
03:25:53,100 --> 03:25:55,100
issue? So maybe this can be done

3617
03:25:55,100 --> 03:25:56,100
further -- I just thought we might have

3618
03:25:56,100 --> 03:25:58,100
none.

3619
03:25:58,100 --> 03:25:59,100
>> Director Ames, we're happy to bring

3620
03:25:59,100 --> 03:26:01,100
you into the office and walk you

3621
03:26:01,100 --> 03:26:05,100
through, you know, and trace the power

3622
03:26:05,100 --> 03:26:07,100
from the shoe collector to the paddle.

3623
03:26:07,100 --> 03:26:10,100
Happy to bring you into the with Leo

3624
03:26:10,100 --> 03:26:12,100
and walk you through very patiently all

3625
03:26:12,100 --> 03:26:13,100
of those mechanics.

3626
03:26:13,100 --> 03:26:16,100
>> Okay. I think it would be good to

3627
03:26:16,100 --> 03:26:18,100
know, because I know there was a Fire

3628
03:26:18,100 --> 03:26:21,601
that happened when that paddle came

3629
03:26:22,100 --> 03:26:27,100
off, a few was blown. It was a very

3630
03:26:27,100 --> 03:26:29,100
small Fire. It got resolved and it was

3631
03:26:29,100 --> 03:26:31,100
all August 29th. So I think that is a

3632
03:26:31,100 --> 03:26:33,100
separate issue, and I'm glad you are

3633
03:26:33,100 --> 03:26:35,100
looking at this to find out what is

3634
03:26:35,100 --> 03:26:37,100
happening -- I guess, there's another

3635
03:26:37,100 --> 03:26:39,100
picture of the fuse. But you have got

3636
03:26:39,100 --> 03:26:42,100
fuses in the train cars that are also a

3637
03:26:42,100 --> 03:26:44,100
problem. So I would like to know the

3638
03:26:44,100 --> 03:26:45,100
nexus of what is happening between the

3639
03:26:45,100 --> 03:26:49,100
two system and that is a train car

3640
03:26:49,100 --> 03:26:53,100
issue. And I think I just wanted to

3641
03:26:53,100 --> 03:26:55,100
maybe conclude to -- because I know I

3642
03:26:55,100 --> 03:26:57,100
have a lot of questions probably.

3643
03:26:57,100 --> 03:27:01,201
Maybe to the next steps. Right before

3644
03:27:04,100 --> 03:27:06,100
the next steps. I just want to point

3645
03:27:06,100 --> 03:27:07,100
out something to the consultant.

3646
03:27:07,100 --> 03:27:11,201
Because I know you have worked, WMATA,

3647
03:27:19,100 --> 03:27:21,401
Washington Transportation Authority in

3648
03:27:23,100 --> 03:27:25,100
Washington, D.C., the Federal Transit

3649
03:27:25,100 --> 03:27:28,100
Administration actually gave a safety

3650
03:27:34,100 --> 03:27:36,100
directive that is related to

3651
03:27:36,100 --> 03:27:39,601
insulators. Excuse me, let me look

3652
03:27:48,100 --> 03:27:52,201
here -- where is it? Apologize. Okay.

3653
03:27:53,100 --> 03:27:56,601
This is from the FTA "safety

3654
03:27:59,100 --> 03:28:01,100
directive." Must update design

3655
03:28:01,100 --> 03:28:04,100
specifications for third rail insulator

3656
03:28:04,100 --> 03:28:07,100
and establish update procedures for

3657
03:28:08,100 --> 03:28:10,401
testing, storage, install, inspect,

3658
03:28:11,100 --> 03:28:14,100
cleaning and replacement. And it goes

3659
03:28:14,100 --> 03:28:15,100
into details related to that directive.

3660
03:28:15,100 --> 03:28:18,601
The other directive is must explain

3661
03:28:23,100 --> 03:28:25,100
the original tenet and define the

3662
03:28:25,100 --> 03:28:27,100
rationale for stopping the program and

3663
03:28:27,100 --> 03:28:30,100
clarify intentions to reinstate the

3664
03:28:30,100 --> 03:28:33,100
program of putting in -- I guess what

3665
03:28:33,100 --> 03:28:36,100
they did, they stopped, they stopped

3666
03:28:36,100 --> 03:28:39,100
repairing their insulators or stop

3667
03:28:39,100 --> 03:28:41,100
cleaning their insulators. To me, this

3668
03:28:41,100 --> 03:28:43,100
is a root cause and I know Staff says,

3669
03:28:43,100 --> 03:28:46,100
we don't know what the root cause is

3670
03:28:46,100 --> 03:28:50,801
for the insulator, but it's a tried and

3671
03:28:52,100 --> 03:28:55,100
trued issue, but finding out that we

3672
03:28:55,100 --> 03:28:57,100
didn't maintain the insulators could be

3673
03:28:57,100 --> 03:28:59,100
something that FTA is interested in.

3674
03:28:59,100 --> 03:29:03,201
Because they clearly told WMATA and directed

3675
03:29:05,100 --> 03:29:08,100
them to further replace the insulator

3676
03:29:08,100 --> 03:29:10,100
and maintain the insulators. So this

3677
03:29:10,100 --> 03:29:11,100
is very serious to me. I don't know

3678
03:29:11,100 --> 03:29:12,100
what we're going to do with this

3679
03:29:12,100 --> 03:29:15,100
report? I don't know if FTA is going

3680
03:29:15,100 --> 03:29:16,100
to get involved with this? I don't

3681
03:29:16,100 --> 03:29:18,100
really want them to get involved, but I

3682
03:29:18,100 --> 03:29:21,100
would like to go to next steps, please.

3683
03:29:21,100 --> 03:29:23,100
Because I think it gets to what you

3684
03:29:23,100 --> 03:29:25,100
want to do.

3685
03:29:39,100 --> 03:29:43,801
this is great. This is what the FTA

3686
03:29:45,100 --> 03:29:49,100
asked them to do. I wanted to be a

3687
03:29:49,100 --> 03:29:53,801
direct result of what we didn't do, we

3688
03:29:57,100 --> 03:29:59,401
didn't clean, that step.

3689
03:30:02,100 --> 03:30:05,601
>> To be clear, Director, I would

3690
03:30:07,100 --> 03:30:10,100
caution us and the Deputy General

3691
03:30:10,100 --> 03:30:12,100
Manager was very clear and our experts

3692
03:30:12,100 --> 03:30:15,100
in the field were very clear, that the

3693
03:30:15,100 --> 03:30:17,100
cleanliness of the insulators was not

3694
03:30:17,100 --> 03:30:19,100
the root cause. So I would just

3695
03:30:19,100 --> 03:30:23,100
caution us to be choose your words

3696
03:30:23,100 --> 03:30:25,100
wisely. Because as of right now, that

3697
03:30:25,100 --> 03:30:30,401
is not the case. So I just have to

3698
03:30:31,100 --> 03:30:32,100
push back and ask you to be careful

3699
03:30:32,100 --> 03:30:34,100
there.

3700
03:30:34,100 --> 03:30:35,100
>> Okay, maybe we get some more data

3701
03:30:35,100 --> 03:30:38,100
and we can figure out, this is a link.

3702
03:30:38,100 --> 03:30:42,801
The lack of cleaning relates to a new

3703
03:30:45,100 --> 03:30:46,100
program less flashovers, less

3704
03:30:46,100 --> 03:30:48,100
explosions. I do appreciate that you

3705
03:30:48,100 --> 03:30:50,100
clean the insulators in the tube. So

3706
03:30:50,100 --> 03:30:52,100
that is a step forward. I know Shane

3707
03:30:52,100 --> 03:30:56,100
said he was going to start cleaning the

3708
03:30:56,100 --> 03:30:58,100
insulator, even though he knew the

3709
03:30:58,100 --> 03:30:59,100
report was coming out.

3710
03:30:59,100 --> 03:31:02,601
>> Director, I'm going to be clear,

3711
03:31:06,100 --> 03:31:09,100
from our experts the cleanliness of the

3712
03:31:09,100 --> 03:31:11,100
insulators by itself was not the

3713
03:31:11,100 --> 03:31:13,100
singular root cause. You heard that

3714
03:31:13,100 --> 03:31:15,100
and you keep trying to make the

3715
03:31:15,100 --> 03:31:18,100
statement that it is -- it is not that.

3716
03:31:18,100 --> 03:31:21,100
>> So are we going -- are we deciding

3717
03:31:21,100 --> 03:31:23,100
right now that it's not true, that the

3718
03:31:23,100 --> 03:31:26,100
cleaning has nothing to do with the

3719
03:31:26,100 --> 03:31:27,100
exploding insulators?

3720
03:31:27,100 --> 03:31:30,100
>> Isolated just the cleanliness of

3721
03:31:30,100 --> 03:31:31,100
the insulators, no.

3722
03:31:31,100 --> 03:31:35,100
>> Okay. I beg to differ. If we go

3723
03:31:35,100 --> 03:31:37,100
back in time, I would like back to in

3724
03:31:37,100 --> 03:31:41,201
time to see what insulators blew up

3725
03:31:42,100 --> 03:31:44,100
with BART's history? And find out what

3726
03:31:44,100 --> 03:31:49,100
we did? If an innocent -- if there was

3727
03:31:49,100 --> 03:31:51,100
insulator issue with BART, I would like

3728
03:31:51,100 --> 03:31:53,100
to know to validate what we're saying.

3729
03:31:53,100 --> 03:31:57,100
I see your point not to jump to

3730
03:31:57,100 --> 03:31:59,100
conclusion, but to see more maintenance

3731
03:31:59,100 --> 03:32:01,100
and historical data that happened to

3732
03:32:01,100 --> 03:32:04,601
BART with blown insulators, and then

3733
03:32:09,100 --> 03:32:10,100
we're done.

3734
03:32:10,100 --> 03:32:14,100
>> I don't know if we're ever done,

3735
03:32:14,100 --> 03:32:15,100
Director. It's continually improvement

3736
03:32:15,100 --> 03:32:17,100
is what we're about. I would just say

3737
03:32:17,100 --> 03:32:20,100
Director, I hope you are with me and

3738
03:32:20,100 --> 03:32:22,100
Michael and the team up here. What

3739
03:32:22,100 --> 03:32:26,801
we're trying to do is -- is minimize

3740
03:32:28,100 --> 03:32:30,100
these occurrences, eliminate these

3741
03:32:30,100 --> 03:32:31,100
occurrences; right? And with the best

3742
03:32:31,100 --> 03:32:34,100
probable data that we have. That is

3743
03:32:34,100 --> 03:32:36,100
where we want your help with; right?

3744
03:32:36,100 --> 03:32:39,100
And we have 100,000 insulators and

3745
03:32:41,100 --> 03:32:44,100
insulators go out not just on BART, but

3746
03:32:44,100 --> 03:32:46,100
other systems. So we're doing the work

3747
03:32:46,100 --> 03:32:49,100
right now. So you know, we're moving

3748
03:32:49,100 --> 03:32:51,100
forward to collect the data, to find

3749
03:32:51,100 --> 03:32:54,601
out where the risk points are,

3750
03:33:00,100 --> 03:33:02,100
eliminate those risks moving forward.

3751
03:33:02,100 --> 03:33:04,100
I'm not going back ten years and

3752
03:33:04,100 --> 03:33:06,100
looking at every single insulators that

3753
03:33:06,100 --> 03:33:07,100
went out. I'm not.

3754
03:33:07,100 --> 03:33:10,100
>> I just want to try to correlate the

3755
03:33:10,100 --> 03:33:12,100
cleaning related to the exploding

3756
03:33:12,100 --> 03:33:13,100
insulators. That is all

3757
03:33:13,100 --> 03:33:16,100
I'm moving forward to make this

3758
03:33:16,100 --> 03:33:18,401
world-class operation even more

3759
03:33:19,100 --> 03:33:21,100
world-class, Director Ames.

3760
03:33:22,100 --> 03:33:25,100
>> Right I'm on the same page with

3761
03:33:25,100 --> 03:33:28,100
that. Going to the vehicles. We want

3762
03:33:28,100 --> 03:33:32,100
to look at the vibration study and the

3763
03:33:32,100 --> 03:33:36,100
fuse Assembly. I just like to know can

3764
03:33:36,100 --> 03:33:38,100
we get more information of why this

3765
03:33:38,100 --> 03:33:40,100
issues are coming up and if that is

3766
03:33:40,100 --> 03:33:42,100
causing flashover?

3767
03:33:42,100 --> 03:33:45,100
>> Again, the shoes, the paddles and

3768
03:33:45,100 --> 03:33:48,100
shoes, Leo will bring you in. I'm

3769
03:33:48,100 --> 03:33:50,100
trying to help us move this discussion

3770
03:33:50,100 --> 03:33:52,100
forward, because I want to hear if we

3771
03:33:52,100 --> 03:33:54,100
have missed anything, if you think that

3772
03:33:54,100 --> 03:33:56,100
we're short here or need to pay

3773
03:33:56,100 --> 03:33:58,100
attention more there. But the design

3774
03:33:58,100 --> 03:34:00,100
-- happy to bring you in, Director

3775
03:34:00,100 --> 03:34:02,100
answer, and give you a graduate-level

3776
03:34:02,100 --> 03:34:05,100
course with Leo and his team on the

3777
03:34:05,100 --> 03:34:07,100
design and how the paddles are designed

3778
03:34:07,100 --> 03:34:09,100
to the shoes, the cars, and how --

3779
03:34:09,100 --> 03:34:13,100
happy to do that and walk you through

3780
03:34:13,100 --> 03:34:17,100
very with great detail, and so that you

3781
03:34:17,100 --> 03:34:19,100
can fully understand how that works.

3782
03:34:19,100 --> 03:34:22,100
>> And I want to can be I do want to

3783
03:34:22,100 --> 03:34:25,100
say to BART that we have done a lot of

3784
03:34:25,100 --> 03:34:29,201
work in the system. And we replaced

3785
03:34:30,100 --> 03:34:33,100
34.5kv cable from Balboa to the West

3786
03:34:33,100 --> 03:34:37,100
portal. We replaced a lot of equipment

3787
03:34:37,100 --> 03:34:40,100
related to grounding, monitoring the

3788
03:34:40,100 --> 03:34:43,100
currents in the system. Sylvia you had

3789
03:34:43,100 --> 03:34:44,100
brought up. Do you want to show that

3790
03:34:44,100 --> 03:34:47,100
slide you brought up that shows we

3791
03:34:47,100 --> 03:34:49,100
spent $22 million? I think that was

3792
03:34:49,100 --> 03:34:51,100
another slide you had on there.

3793
03:34:51,100 --> 03:34:53,100
>> That is not on the slide, but it's

3794
03:34:53,100 --> 03:34:56,100
the MPRs. If we go to the MPRs.

3795
03:34:56,100 --> 03:34:57,100
>> The Multi-Function Protection

3796
03:34:57,100 --> 03:34:58,100
Relays.

3797
03:34:58,100 --> 03:34:59,100
>> Yes.

3798
03:34:59,100 --> 03:35:03,100
>> We have a project in place that is

3799
03:35:03,100 --> 03:35:06,601
funded for about $20-22 million to

3800
03:35:07,100 --> 03:35:08,100
replace those systemwide,

3801
03:35:08,100 --> 03:35:10,100
and retrofitting of negative

3802
03:35:10,100 --> 03:35:12,100
grounding which is critical for

3803
03:35:12,100 --> 03:35:14,100
limiting voltage. So I say BART is

3804
03:35:14,100 --> 03:35:17,100
doing a good job. You are seeing an

3805
03:35:17,100 --> 03:35:18,100
assessment of our system that may not

3806
03:35:18,100 --> 03:35:20,100
be the root cause of the insulators,

3807
03:35:20,100 --> 03:35:22,100
but you are basically showing that it

3808
03:35:22,100 --> 03:35:25,100
works. I don't see a -- I don't see a

3809
03:35:25,100 --> 03:35:27,100
real threat here based on what the

3810
03:35:27,100 --> 03:35:28,100
consultant provided other than we do

3811
03:35:28,100 --> 03:35:32,201
have some problems with the trains, the

3812
03:35:34,100 --> 03:35:37,601
paddles, fuses and insulators and power

3813
03:35:38,100 --> 03:35:39,100
outages with the Substation going out.

3814
03:35:39,100 --> 03:35:42,100
I would like to know exactly how we

3815
03:35:42,100 --> 03:35:43,100
resolved that particular issue, which

3816
03:35:43,100 --> 03:35:44,100
was on the 29th.

3817
03:35:44,100 --> 03:35:46,100
>> Director Ames, for the record, the

3818
03:35:46,100 --> 03:35:48,100
things that you just said are not

3819
03:35:48,100 --> 03:35:50,100
accurate. We have -- and unless,

3820
03:35:50,100 --> 03:35:53,100
unless you are making the assertions

3821
03:35:53,100 --> 03:35:57,201
that the consultants that we have hired

3822
03:35:58,100 --> 03:36:00,100
are not professionals and not

3823
03:36:00,100 --> 03:36:03,601
credentialed and willing to risk their

3824
03:36:10,100 --> 03:36:11,100
credentials.

3825
03:36:11,100 --> 03:36:12,100
>> Which comment was that?

3826
03:36:12,100 --> 03:36:16,201
>> We have problems with the fuse and

3827
03:36:19,100 --> 03:36:22,100
insulators. Unless you saying that the

3828
03:36:22,100 --> 03:36:25,601
Parsons team, a global firm is

3829
03:36:26,100 --> 03:36:29,100
willfully at this dais telling

3830
03:36:30,100 --> 03:36:32,100
untruths, your comments are inaccurate.

3831
03:36:32,100 --> 03:36:35,100
>> I want to clear about this, I don't

3832
03:36:35,100 --> 03:36:38,100
think we have enough information on the

3833
03:36:38,100 --> 03:36:39,100
insulators and the maintenance is and

3834
03:36:39,100 --> 03:36:43,100
with what we're doing or not doing and

3835
03:36:43,100 --> 03:36:46,100
I just read that WMATA had a safety

3836
03:36:46,100 --> 03:36:49,100
directive to maintain their insulators

3837
03:36:50,100 --> 03:36:52,100
and what we're going to do?

3838
03:36:52,100 --> 03:36:53,100
>> Director Ames?

3839
03:36:53,100 --> 03:36:55,100
>> Yes.

3840
03:36:55,100 --> 03:36:56,100
>> We have other Directors in the

3841
03:36:56,100 --> 03:36:57,100
queue.

3842
03:36:57,100 --> 03:37:00,100
>> Okay. I will move on. Thank you.

3843
03:37:00,100 --> 03:37:03,100
>> Thank you. Vice President Wright

3844
03:37:03,100 --> 03:37:05,100
followed by Director Ghosh.

3845
03:37:05,100 --> 03:37:07,100
>> Thank you. I guess I have to start

3846
03:37:07,100 --> 03:37:11,201
by saying we're not the WMATA Board.

3847
03:37:12,100 --> 03:37:15,601
Sylvia, have been issued an directives

3848
03:37:16,100 --> 03:37:18,100
on insulator cleaning?

3849
03:37:18,100 --> 03:37:19,100
>> No.

3850
03:37:19,100 --> 03:37:22,601
>> Zara, in your opinion, is insulator

3851
03:37:26,100 --> 03:37:27,100
a problem at BART?

3852
03:37:27,100 --> 03:37:29,100
>> Certainly that is an issue

3853
03:37:29,100 --> 03:37:32,100
everywhere, not just at BART.

3854
03:37:33,100 --> 03:37:35,100
>> I think the question is do you

3855
03:37:35,100 --> 03:37:37,100
think that is a problem at BART?

3856
03:37:37,100 --> 03:37:39,100
>> Do you think it's the root cause of

3857
03:37:39,100 --> 03:37:40,100
this?

3858
03:37:40,100 --> 03:37:43,601
>> Ultimately, I would say that based

3859
03:37:44,100 --> 03:37:47,100
on the evidence it does not appear to

3860
03:37:47,100 --> 03:37:49,100
have been the root cause. With the

3861
03:37:49,100 --> 03:37:51,100
photo that we presented earlier with

3862
03:37:51,100 --> 03:37:54,100
the coverboard damage, that is directly

3863
03:37:54,100 --> 03:37:57,100
above the insulator and even a comment

3864
03:37:57,100 --> 03:38:00,100
from Barney Smits, who also did

3865
03:38:00,100 --> 03:38:04,201
weigh-in on that, it's coming from above

3866
03:38:05,100 --> 03:38:08,100
the flashover is irrelevant to some

3867
03:38:08,100 --> 03:38:11,100
event, with the hypes even with a new

3868
03:38:11,100 --> 03:38:14,100
insulator at that location, subject to

3869
03:38:14,100 --> 03:38:16,100
that type of event from above it would

3870
03:38:16,100 --> 03:38:18,100
have probably also failed in that way.

3871
03:38:18,100 --> 03:38:20,100
So we're well-aware of all of the

3872
03:38:20,100 --> 03:38:23,100
circumstances and if you look back at

3873
03:38:23,100 --> 03:38:25,100
that slide, there were a number of

3874
03:38:25,100 --> 03:38:27,100
other insulators in between that were

3875
03:38:27,100 --> 03:38:28,100
subjected to similar environmental

3876
03:38:28,100 --> 03:38:30,100
conditions, and they did not fail.

3877
03:38:30,100 --> 03:38:33,100
There were also instances that do not

3878
03:38:33,100 --> 03:38:34,100
include insulator failures, and even

3879
03:38:34,100 --> 03:38:38,100
the ones that did have some insulator

3880
03:38:38,100 --> 03:38:40,100
involvement, those insulators in some

3881
03:38:40,100 --> 03:38:44,100
cases there's a glow, which we describe

3882
03:38:44,100 --> 03:38:46,100
as Corona discharge and they actually

3883
03:38:46,100 --> 03:38:48,100
didn't fully fail and didn't flashover,

3884
03:38:48,100 --> 03:38:51,100
and speaks to the resilience of some of

3885
03:38:51,100 --> 03:38:54,601
the insulators. So we're fully aware,

3886
03:38:55,100 --> 03:38:59,801
of course there's no such thing as a

3887
03:39:00,100 --> 03:39:02,100
perfect insulator and our team has read

3888
03:39:02,100 --> 03:39:04,100
the WMATA report and we're well-aware

3889
03:39:04,100 --> 03:39:06,100
of that. But these are different

3890
03:39:06,100 --> 03:39:08,100
circumstances as to what WMATA was

3891
03:39:08,100 --> 03:39:09,100
dealing with.

3892
03:39:09,100 --> 03:39:12,100
>> Thank you, on that particular

3893
03:39:12,100 --> 03:39:15,100
question sounds conclusive to me.

3894
03:39:15,100 --> 03:39:18,601
Thank you, Zara, thank you, Sylvia,

3895
03:39:19,100 --> 03:39:22,100
thank you, Shane and thank you, Bob. I

3896
03:39:22,100 --> 03:39:25,601
say BART reliability is great, and

3897
03:39:27,100 --> 03:39:28,100
customer satisfaction at historic highs

3898
03:39:28,100 --> 03:39:30,100
all of that is true. None of that

3899
03:39:30,100 --> 03:39:34,100
should be lost in this conversation and

3900
03:39:34,100 --> 03:39:36,100
none of that excuses the service shut

3901
03:39:36,100 --> 03:39:39,100
down and disruptions. I know our

3902
03:39:39,100 --> 03:39:40,100
management knows that. And I don't

3903
03:39:40,100 --> 03:39:43,100
think anyone is here making excuses. I

3904
03:39:43,100 --> 03:39:45,100
think the detail and rigor of this

3905
03:39:45,100 --> 03:39:47,100
analysis speaks for itself. And it

3906
03:39:47,100 --> 03:39:49,100
shows this is a serious problem that

3907
03:39:49,100 --> 03:39:52,100
we're taking seriously. I do have

3908
03:39:52,100 --> 03:39:55,601
questions, Sylvia. I'm sorry I didn't

3909
03:39:56,100 --> 03:39:58,100
ask more in our briefing and I'm sorry,

3910
03:39:58,100 --> 03:40:00,100
it took me a while to absorb

3911
03:40:00,100 --> 03:40:02,100
this. This is a really substantive

3912
03:40:02,100 --> 03:40:05,100
analysis and I think it does a

3913
03:40:05,100 --> 03:40:07,100
disservice to the rigor of the work to

3914
03:40:07,100 --> 03:40:09,100
limit to a slide deck and memo. I

3915
03:40:09,100 --> 03:40:11,100
talked about this before, but the item

3916
03:40:11,100 --> 03:40:13,100
before this just for example had a

3917
03:40:13,100 --> 03:40:15,100
27-page detailed report in the packet

3918
03:40:15,100 --> 03:40:17,100
that is the real meat of that item.

3919
03:40:17,100 --> 03:40:18,100
And I'm disappointed we didn't have

3920
03:40:18,100 --> 03:40:21,100
that here. I know this is a norm for

3921
03:40:21,100 --> 03:40:24,100
BART, but I think it's a norm that we

3922
03:40:24,100 --> 03:40:26,100
need to change. Now onto the slides

3923
03:40:26,100 --> 03:40:27,100
and questions. For this, I really

3924
03:40:27,100 --> 03:40:30,100
want to focus on the thing in our

3925
03:40:30,100 --> 03:40:31,100
control and decisions that were made by

3926
03:40:31,100 --> 03:40:33,100
BART, because there's a lot of things

3927
03:40:33,100 --> 03:40:36,100
that are not in our control. Can we go

3928
03:40:36,100 --> 03:40:37,100
to slide 12?

3929
03:40:37,100 --> 03:40:39,100
>> Sylvia, you can change the slide

3930
03:40:39,100 --> 03:40:41,100
now.

3931
03:40:50,100 --> 03:40:52,100
>> Thank you. I'm still trying to wrap

3932
03:40:52,100 --> 03:40:54,100
my head around this a little bit. I

3933
03:40:54,100 --> 03:40:56,100
understand why the cross bond were

3934
03:40:56,100 --> 03:40:59,100
removed and I don't understand why they

3935
03:40:59,100 --> 03:41:01,100
weren't put back and I don't understand

3936
03:41:01,100 --> 03:41:03,100
why for nearly six years we went

3937
03:41:03,100 --> 03:41:05,100
without what seems a pretty possible

3938
03:41:05,100 --> 03:41:08,100
aspect of our system as designed? Can

3939
03:41:08,100 --> 03:41:11,601
you speak to that bit more?

3940
03:41:12,100 --> 03:41:16,100
>> I will turn it over to Shane Edwards,

3941
03:41:16,100 --> 03:41:18,100
AGM of Operations.

3942
03:41:18,100 --> 03:41:21,100
>> Thank you. Director, first of all,

3943
03:41:21,100 --> 03:41:24,100
no excuses. But that being said, it

3944
03:41:24,100 --> 03:41:28,100
was initially done as a result of a

3945
03:41:28,100 --> 03:41:31,100
safety factor that was recognized

3946
03:41:31,100 --> 03:41:33,100
during the TBT retrofit project. In

3947
03:41:33,100 --> 03:41:35,100
order to isolate the track they were

3948
03:41:35,100 --> 03:41:39,801
working on, you have to make it an

3949
03:41:41,100 --> 03:41:43,100
island and disconnect from the other

3950
03:41:43,100 --> 03:41:45,100
track with current that has to go

3951
03:41:45,100 --> 03:41:46,100
somewhere. So every night they would

3952
03:41:46,100 --> 03:41:49,100
go in at 9:00 p.m. during revenue

3953
03:41:49,100 --> 03:41:51,100
service.

3954
03:41:51,100 --> 03:41:53,100
>> I'm sorry, just in the interest of

3955
03:41:53,100 --> 03:41:57,100
time, I understand why it happened and

3956
03:41:57,100 --> 03:41:58,100
just asked why they weren't put back

3957
03:41:58,100 --> 03:42:00,100
and why it took six years to talk about

3958
03:42:00,100 --> 03:42:02,100
it

3959
03:42:06,100 --> 03:42:08,100
>> Sylvia mentioned to work on from

3960
03:42:08,100 --> 03:42:09,100
the project to maintenance standpoint

3961
03:42:09,100 --> 03:42:11,100
and we're usually the first ones in and

3962
03:42:11,100 --> 03:42:12,100
last ones out, and that is something

3963
03:42:12,100 --> 03:42:16,100
that you can't close out the project or

3964
03:42:16,100 --> 03:42:20,100
take in this case close a project out

3965
03:42:20,100 --> 03:42:22,100
with underbudget, you know on-schedule.

3966
03:42:22,100 --> 03:42:24,100
And we shouldn't just report that out.

3967
03:42:24,100 --> 03:42:27,100
We should report that all things have

3968
03:42:27,100 --> 03:42:29,100
been put back in the same configuration

3969
03:42:29,100 --> 03:42:33,100
that they were prior to the project

3970
03:42:33,100 --> 03:42:34,100
starting.

3971
03:42:34,100 --> 03:42:37,100
>> Director, just to be clear -- you

3972
03:42:37,100 --> 03:42:41,100
know, Sylvia has got it together moving

3973
03:42:41,100 --> 03:42:42,100
forward. But you know, you're

3974
03:42:42,100 --> 03:42:44,100
absolutely right. They came out with

3975
03:42:44,100 --> 03:42:46,100
the TransBay Tube project and they

3976
03:42:46,100 --> 03:42:49,100
should have put back in there. There's

3977
03:42:49,100 --> 03:42:50,100
no two ways. We didn't put them back

3978
03:42:50,100 --> 03:42:52,100
in; right? And that is on the people

3979
03:42:52,100 --> 03:42:55,100
up here, that is on the people in the

3980
03:42:55,100 --> 03:42:58,100
audience here from the maintenance

3981
03:42:58,100 --> 03:42:59,100
folks and operations folks. They

3982
03:42:59,100 --> 03:43:01,100
should have been put back in, you know?

3983
03:43:01,100 --> 03:43:03,100
With that project, or that project

3984
03:43:03,100 --> 03:43:05,100
should have had operations put them

3985
03:43:05,100 --> 03:43:07,100
back in. So they are back in now. She

3986
03:43:07,100 --> 03:43:09,100
has got the change stuff in, but you

3987
03:43:09,100 --> 03:43:13,100
know, I have had this discussion. That

3988
03:43:13,100 --> 03:43:15,100
same question on Tuesday, you know,

3989
03:43:15,100 --> 03:43:17,100
take them out, fine for safety thing,

3990
03:43:17,100 --> 03:43:19,100
but they should have been put back in

3991
03:43:19,100 --> 03:43:23,100
with that project. There is no two

3992
03:43:23,100 --> 03:43:25,100
ways about that and we're owning that

3993
03:43:25,100 --> 03:43:28,100
and Shane knows that. He is not going

3994
03:43:28,100 --> 03:43:30,100
to sugar-coat over that, that those

3995
03:43:30,100 --> 03:43:32,100
bonds should have been put back in.

3996
03:43:32,100 --> 03:43:33,100
>> Thank you. I appreciate that.

3997
03:43:33,100 --> 03:43:35,100
Just to clarify what you said as kind

3998
03:43:35,100 --> 03:43:38,100
of action we're taking in response, do

3999
03:43:38,100 --> 03:43:41,100
we now have just sort of standardized

4000
03:43:41,100 --> 03:43:44,100
project language or contract language

4001
03:43:44,100 --> 03:43:46,100
on returning work sites to normal

4002
03:43:46,100 --> 03:43:47,100
working order?

4003
03:43:47,100 --> 03:43:49,100
>> Director Wright, we do not have

4004
03:43:49,100 --> 03:43:51,100
that today. But we will have it within

4005
03:43:51,100 --> 03:43:54,100
the next oh, I don't know few weeks for

4006
03:43:54,100 --> 03:43:55,100
that part. And then we're working with

4007
03:43:55,100 --> 03:43:59,201
safety on what would be the right

4008
03:44:01,100 --> 03:44:02,100
configuration control or change control

4009
03:44:02,100 --> 03:44:05,100
process, because that is something that

4010
03:44:05,100 --> 03:44:09,100
would -- so if this type of event

4011
03:44:09,100 --> 03:44:11,100
happens in the past, who all needs to

4012
03:44:11,100 --> 03:44:13,100
sign-off, that they all agree stack

4013
03:44:13,100 --> 03:44:17,100
hands and the date they will be put

4014
03:44:17,100 --> 03:44:18,100
back. Yes.

4015
03:44:18,100 --> 03:44:19,100
>> Are we look at other projects that

4016
03:44:19,100 --> 03:44:22,100
have happened, just to make sure this

4017
03:44:22,100 --> 03:44:24,100
kind of thing didn't happen elsewhere?

4018
03:44:24,100 --> 03:44:25,100
>> Yes, absolutely.

4019
03:44:25,100 --> 03:44:27,100
>> Thank you.

4020
03:44:30,100 --> 03:44:33,100
Slide 17 on MPRs being disabled.

4021
03:44:33,100 --> 03:44:35,100
Were these considered in a State of Good

4022
03:44:35,100 --> 03:44:37,100
Repair as disabled or considered past

4023
03:44:37,100 --> 03:44:38,100
their useful life?

4024
03:44:38,100 --> 03:44:41,100
>> They were considered past their

4025
03:44:41,100 --> 03:44:44,100
useful life, which is why we have a

4026
03:44:44,100 --> 03:44:47,100
project to replace them all.

4027
03:44:47,100 --> 03:44:48,100
>> Excellent, that speaks to me for

4028
03:44:48,100 --> 03:44:52,201
the funding that we have for capital

4029
03:44:53,100 --> 03:44:54,100
work. Slide 20 on storage.

4030
03:44:54,100 --> 03:44:55,100
Something you said on

4031
03:44:55,100 --> 03:44:57,100
this slide has stuck with me, which is

4032
03:44:57,100 --> 03:45:01,201
the way we were storing railways was

4033
03:45:02,100 --> 03:45:04,100
a maintenance project forever, and

4034
03:45:04,100 --> 03:45:06,100
that sentiment to me might be one of

4035
03:45:06,100 --> 03:45:08,100
the root causes here. I don't know how

4036
03:45:08,100 --> 03:45:09,100
many longstanding practices that we

4037
03:45:09,100 --> 03:45:11,100
might have that are not best practices?

4038
03:45:11,100 --> 03:45:14,100
I'm not the expert, and I'm not trying

4039
03:45:14,100 --> 03:45:18,100
to pretend I am. But I do think we

4040
03:45:18,100 --> 03:45:21,100
should be thinking about a procedure

4041
03:45:21,100 --> 03:45:22,100
commitment to review and not limited to

4042
03:45:22,100 --> 03:45:24,100
the causes that we have looked at

4043
03:45:24,100 --> 03:45:27,100
through this analysis, but across our

4044
03:45:27,100 --> 03:45:29,100
maintenance work.

4045
03:45:29,100 --> 03:45:31,100
Slide 23. I don't need it now.

4046
03:45:31,100 --> 03:45:33,100
But I would love it if you could

4047
03:45:33,100 --> 03:45:35,100
follow-up with implementation timeline

4048
03:45:35,100 --> 03:45:38,100
for all of the in-progress

4049
03:45:38,100 --> 03:45:40,100
improvements. I would also love

4050
03:45:40,100 --> 03:45:41,100
implementation timeline for the next

4051
03:45:41,100 --> 03:45:43,401
steps listed on slide 25.

4052
03:45:44,100 --> 03:45:48,100
>> So we -- we brought that up at our

4053
03:45:48,100 --> 03:45:49,100
prep meeting, Director. We'll pull

4054
03:45:49,100 --> 03:45:52,100
together an update, you know, on all of

4055
03:45:52,100 --> 03:45:54,100
those that are in progress where we

4056
03:45:54,100 --> 03:45:56,100
are, the timeline and we'll provide

4057
03:45:56,100 --> 03:45:57,100
that all that information to the entire

4058
03:45:57,100 --> 03:45:58,100
Board.

4059
03:45:58,100 --> 03:46:01,100
>> Thank you. I really appreciate.

4060
03:46:02,100 --> 03:46:04,100
And just in general it has been talked,

4061
03:46:04,100 --> 03:46:08,100
but it seems to me this is more an

4062
03:46:08,100 --> 03:46:11,100
interim update than a final report, am

4063
03:46:11,100 --> 03:46:12,100
I correct in my judgment?

4064
03:46:12,100 --> 03:46:13,100
>> We're not done with all of the

4065
03:46:13,100 --> 03:46:14,100
investigation, yes.

4066
03:46:14,100 --> 03:46:17,100
>> I think that is fine. I'm glad we

4067
03:46:17,100 --> 03:46:18,100
didn't wait for conclusion to have a

4068
03:46:18,100 --> 03:46:20,100
conversation about this. I do hope

4069
03:46:20,100 --> 03:46:23,100
this comes back to the Board as a final

4070
03:46:23,100 --> 03:46:24,100
report when it's ready and trust that

4071
03:46:24,100 --> 03:46:26,100
will happen. Just to summarize, I

4072
03:46:26,100 --> 03:46:30,100
think we have -- confirm. Thank you.

4073
03:46:30,100 --> 03:46:31,100
Just to summarize, I think we have done

4074
03:46:31,100 --> 03:46:33,100
a lot of work to understand what has

4075
03:46:33,100 --> 03:46:35,100
happened. I think we're doing a lot of

4076
03:46:35,100 --> 03:46:37,100
things to address potential causes and

4077
03:46:37,100 --> 03:46:38,100
prevent these disruptions from

4078
03:46:38,100 --> 03:46:40,100
happening again. And we don't have a

4079
03:46:40,100 --> 03:46:42,100
short answer to what is causing this,

4080
03:46:42,100 --> 03:46:44,100
because this is lots of different

4081
03:46:44,100 --> 03:46:47,100
things at different time and different

4082
03:46:47,100 --> 03:46:49,100
places and it's a complex system. It's

4083
03:46:49,100 --> 03:46:50,100
frustrating, but it's honest. What I

4084
03:46:50,100 --> 03:46:53,100
want to focus on is having clear

4085
03:46:53,100 --> 03:46:55,100
timeframes for next steps that we're

4086
03:46:55,100 --> 03:46:57,100
taking. I think we need a clear

4087
03:46:57,100 --> 03:46:59,100
commitment to broader review of

4088
03:46:59,100 --> 03:47:00,100
longstanding maintenance practices and

4089
03:47:00,100 --> 03:47:02,100
just the fact that you mentioned

4090
03:47:02,100 --> 03:47:04,100
briefly we haven't had anyone signing

4091
03:47:04,100 --> 03:47:06,100
off on system changes is alarming to

4092
03:47:06,100 --> 03:47:10,100
me. I think we need to do a better job

4093
03:47:10,100 --> 03:47:12,100
making our performance metrics easily

4094
03:47:12,100 --> 03:47:13,100
accessible to the public, so they don't

4095
03:47:13,100 --> 03:47:15,100
only Lear or see them when they are bad

4096
03:47:15,100 --> 03:47:18,100
and I think we need to have 134

4097
03:47:18,100 --> 03:47:20,100
conversations on responsibility and

4098
03:47:20,100 --> 03:47:22,100
accountability on this, because BART is

4099
03:47:22,100 --> 03:47:23,100
essential infrastructure for the Bay

4100
03:47:23,100 --> 03:47:27,100
Area, and that means we can't fail and

4101
03:47:27,100 --> 03:47:30,100
we have it's not about being punitive,

4102
03:47:30,100 --> 03:47:32,100
but taking responsibility and I want to

4103
03:47:32,100 --> 03:47:35,100
close again by thanking everyone who

4104
03:47:35,100 --> 03:47:37,100
contributed to this work immense amount

4105
03:47:37,100 --> 03:47:39,100
of work that has gone into it. It's

4106
03:47:39,100 --> 03:47:41,100
not conclusive. It's critical. It's

4107
03:47:41,100 --> 03:47:43,100
comprehensive and it's deeply

4108
03:47:43,100 --> 03:47:45,100
appreciated. Thank you.

4109
03:47:45,100 --> 03:47:47,401
>> Thank you. Director Ghosh,

4110
03:47:49,100 --> 03:47:51,401
follow by Director Flores.

4111
03:47:52,100 --> 03:47:56,201
>> Thank you. I think I shared this

4112
03:47:57,100 --> 03:47:59,100
during our briefing this is a lot for

4113
03:47:59,100 --> 03:48:02,100
someone when is not an engineer to

4114
03:48:02,100 --> 03:48:04,100
internalize. At the same time, the

4115
03:48:04,100 --> 03:48:06,100
Board is not the only people who are

4116
03:48:06,100 --> 03:48:10,100
looking at these reports. So I truly

4117
03:48:10,100 --> 03:48:13,100
appreciate the depth, the detail, the

4118
03:48:13,100 --> 03:48:16,601
rigor, and the transparency, and the

4119
03:48:18,100 --> 03:48:19,100
vulnerability with which we're sharing

4120
03:48:19,100 --> 03:48:22,100
this information. I think it's really

4121
03:48:22,100 --> 03:48:25,100
critical and important to do it in that

4122
03:48:25,100 --> 03:48:28,100
way. And I think it would be nice if

4123
03:48:28,100 --> 03:48:31,100
we had a clear root cause, that it

4124
03:48:31,100 --> 03:48:33,100
wasn't so messy. That we could just

4125
03:48:33,100 --> 03:48:35,100
have the insulators and start cleaning

4126
03:48:35,100 --> 03:48:37,100
them. So I think, you know, we have to

4127
03:48:37,100 --> 03:48:39,100
keep that in mind, the easy answer

4128
03:48:39,100 --> 03:48:42,100
would be to have a clear root cause.

4129
03:48:42,100 --> 03:48:45,100
The more difficult answer is it's a

4130
03:48:45,100 --> 03:48:47,100
fragile system in many ways that a lot

4131
03:48:47,100 --> 03:48:51,100
of folks work to keep resilient, and

4132
03:48:51,100 --> 03:48:53,100
work on redundancies to keep BART sort

4133
03:48:53,100 --> 03:48:57,201
of going, and moving. And again, to

4134
03:48:58,100 --> 03:49:01,601
Director Wright's -- to VP Wright's

4135
03:49:02,100 --> 03:49:03,100
point we're seeing really high

4136
03:49:03,100 --> 03:49:06,100
satisfaction with BART's service right

4137
03:49:06,100 --> 03:49:08,100
now. That being said, I do have to say

4138
03:49:08,100 --> 03:49:11,601
that these kind of failures are

4139
03:49:12,100 --> 03:49:14,100
devastating for our riders. My bus was

4140
03:49:14,100 --> 03:49:16,100
ten minutes late today and just the

4141
03:49:16,100 --> 03:49:18,100
stress of waiting, knowing if I'm going

4142
03:49:18,100 --> 03:49:21,100
to make it to the meeting on time? It

4143
03:49:21,100 --> 03:49:23,100
really messes with your day, with your

4144
03:49:23,100 --> 03:49:26,100
job, with your life, especially it

4145
03:49:26,100 --> 03:49:29,100
messes with our freeways, you know? It

4146
03:49:29,100 --> 03:49:30,100
really does drive home the point that

4147
03:49:30,100 --> 03:49:32,100
we're a critical part of moving people

4148
03:49:32,100 --> 03:49:35,100
around the bay. So we do have to do

4149
03:49:35,100 --> 03:49:38,100
better. But the responsibility for

4150
03:49:38,100 --> 03:49:40,100
that doesn't just lay with BART, but

4151
03:49:40,100 --> 03:49:44,201
lays with our funding and lies with

4152
03:49:45,100 --> 03:49:46,100
historical underinvestment in the

4153
03:49:46,100 --> 03:49:47,100
maintenance of our public transit

4154
03:49:47,100 --> 03:49:51,100
systems. All of that. So I hope that

4155
03:49:51,100 --> 03:49:54,100
we -- I don't hope. I know the Board

4156
03:49:54,100 --> 03:49:56,100
has been very clear that we want you to

4157
03:49:56,100 --> 03:49:58,100
look at this, and we want you to look

4158
03:49:58,100 --> 03:50:00,100
at it in-depth and to figure out

4159
03:50:00,100 --> 03:50:01,100
everything that we could be doing

4160
03:50:01,100 --> 03:50:03,100
better to avoid these incidents in the

4161
03:50:03,100 --> 03:50:06,100
future. So I would like you all to

4162
03:50:06,100 --> 03:50:09,100
continue on this, and report-back on

4163
03:50:09,100 --> 03:50:12,601
these sort of scenarios. And to

4164
03:50:14,100 --> 03:50:15,100
understand how electricity moves

4165
03:50:15,100 --> 03:50:16,100
through our system and what we can do

4166
03:50:16,100 --> 03:50:19,100
to make it better? I think there are

4167
03:50:19,100 --> 03:50:21,100
benefits to the study, just in figuring

4168
03:50:21,100 --> 03:50:23,100
out if there are small things across

4169
03:50:23,100 --> 03:50:26,100
the system we doing better? It's

4170
03:50:26,100 --> 03:50:29,100
almost like an audit of how our system

4171
03:50:29,100 --> 03:50:31,100
works day-to-day. What are some best

4172
03:50:31,100 --> 03:50:33,100
practices that we can implement? Along

4173
03:50:33,100 --> 03:50:34,100
with understanding that some of these

4174
03:50:34,100 --> 03:50:36,100
challenges are round how much time do

4175
03:50:36,100 --> 03:50:39,100
we have to do this work? I think with

4176
03:50:39,100 --> 03:50:43,100
the storage of the rails with the

4177
03:50:43,100 --> 03:50:45,100
limited time to do the work and phasing

4178
03:50:45,100 --> 03:50:48,100
it. So the solutions will not be just

4179
03:50:48,100 --> 03:50:50,100
engineering. It will also be human

4180
03:50:50,100 --> 03:50:51,100
factor and processes, and we have to

4181
03:50:51,100 --> 03:50:53,100
make sure that in the process of doing

4182
03:50:53,100 --> 03:50:55,100
this, we don't create any new issues

4183
03:50:55,100 --> 03:50:57,100
especially when we're so focused -- if

4184
03:50:57,100 --> 03:51:01,100
you are so focused on the insulators

4185
03:51:01,100 --> 03:51:04,100
and know we stopped cleaning them to

4186
03:51:04,100 --> 03:51:06,100
avoid other issues. So it's a little

4187
03:51:06,100 --> 03:51:08,100
bit of game to figure out, you know,

4188
03:51:08,100 --> 03:51:12,100
how to make the system work for us in

4189
03:51:12,100 --> 03:51:15,100
the best way able to. I did want to ask

4190
03:51:15,100 --> 03:51:19,201
in your further analyses, is there any

4191
03:51:23,100 --> 03:51:25,100
incorporation the schedule changes that

4192
03:51:25,100 --> 03:51:26,100
happened just before the first

4193
03:51:26,100 --> 03:51:29,100
incident? I think August 11th is when

4194
03:51:29,100 --> 03:51:30,100
some schedule changes happened. I'm

4195
03:51:30,100 --> 03:51:32,100
curious about that, or if you have

4196
03:51:32,100 --> 03:51:34,100
looked at it and put it aside as this

4197
03:51:34,100 --> 03:51:37,100
is not a factor? I didn't hear that

4198
03:51:37,100 --> 03:51:40,601
being discussed. And then the second

4199
03:51:41,100 --> 03:51:42,100
thing is just looking at where the

4200
03:51:42,100 --> 03:51:45,100
incidents happened is very much in that

4201
03:51:45,100 --> 03:51:47,100
particular area. And that particular

4202
03:51:47,100 --> 03:51:50,100
area does see from my understanding,

4203
03:51:50,100 --> 03:51:52,100
the most amount of train traffic

4204
03:51:52,100 --> 03:51:55,100
compared to any other part of the

4205
03:51:55,100 --> 03:51:56,100
system. So I'm also just curious if

4206
03:51:56,100 --> 03:52:00,201
you had any kind of control sample

4207
03:52:01,100 --> 03:52:05,100
where that is comparable -- where it

4208
03:52:05,100 --> 03:52:07,100
may not exactly there, but somewhere

4209
03:52:07,100 --> 03:52:09,100
else that seems the same train traffic

4210
03:52:09,100 --> 03:52:14,401
and can be tested in any way? As a

4211
03:52:19,100 --> 03:52:22,100
layperson, the schedule change and that

4212
03:52:22,100 --> 03:52:24,100
particular Section and in the load flow

4213
03:52:24,100 --> 03:52:26,100
analysis that you are doing is that

4214
03:52:26,100 --> 03:52:28,100
something that you will consider or

4215
03:52:28,100 --> 03:52:30,100
plans to consider or has it been put

4216
03:52:30,100 --> 03:52:31,100
aside?

4217
03:52:31,100 --> 03:52:32,100
>> That is absolutely a good question.

4218
03:52:32,100 --> 03:52:34,100
We did look at schedule change and the

4219
03:52:34,100 --> 03:52:37,100
impact and also one of the things that

4220
03:52:37,100 --> 03:52:41,100
we asked for, and did review is for

4221
03:52:41,100 --> 03:52:44,601
instance on the 8/29 incident in the

4222
03:52:45,100 --> 03:52:47,100
afternoon, to look at all of the trains

4223
03:52:47,100 --> 03:52:51,100
and the car, the number of cars and

4224
03:52:51,100 --> 03:52:53,100
where they were just past West Oakland

4225
03:52:53,100 --> 03:52:55,100
and past civic center on a map to see

4226
03:52:55,100 --> 03:52:57,100
where they were and the configuration?

4227
03:52:57,100 --> 03:53:01,100
We also compared that to exactly the

4228
03:53:01,100 --> 03:53:02,100
way the system looked a month earlier

4229
03:53:02,100 --> 03:53:04,100
to see how many cars and see if there

4230
03:53:04,100 --> 03:53:06,100
was anything? And there was nothing

4231
03:53:06,100 --> 03:53:07,100
mind blowing out of there, but when we

4232
03:53:07,100 --> 03:53:11,201
do the modeling to put in the

4233
03:53:13,100 --> 03:53:16,100
train cars and whether they are

4234
03:53:16,100 --> 03:53:18,100
accelerating or decelerating and the

4235
03:53:18,100 --> 03:53:20,100
negative return if anything come out of

4236
03:53:20,100 --> 03:53:22,100
that is one of the values of that.

4237
03:53:22,100 --> 03:53:23,100
>> I appreciate that. I would have

4238
03:53:23,100 --> 03:53:25,100
loved it to be one of these sort of

4239
03:53:25,100 --> 03:53:29,201
bullet points in that slide because I

4240
03:53:31,100 --> 03:53:33,100
think it's so specific to where it

4241
03:53:33,100 --> 03:53:34,100
happened, that addressing that will be

4242
03:53:34,100 --> 03:53:37,100
important to us and understanding the

4243
03:53:37,100 --> 03:53:40,601
entire system. Thank you so much.

4244
03:53:41,100 --> 03:53:43,401
>> Thank you. Director Flores.

4245
03:53:44,100 --> 03:53:47,100
>> Thank you for the presentation. I

4246
03:53:47,100 --> 03:53:51,100
just want to begin by stating that I

4247
03:53:51,100 --> 03:53:53,100
think what has been clearly said, but

4248
03:53:53,100 --> 03:53:56,100
want to re-emphasize it our customer

4249
03:53:56,100 --> 03:53:58,100
and taxpayers deserve transparency

4250
03:53:58,100 --> 03:53:59,100
accountability and quality service and

4251
03:53:59,100 --> 03:54:01,100
this presentation is part of that

4252
03:54:01,100 --> 03:54:03,100
process. I believe that having an

4253
03:54:03,100 --> 03:54:04,100
outside group investigate these

4254
03:54:04,100 --> 03:54:07,100
incidents to provide an outside and

4255
03:54:07,100 --> 03:54:09,100
non-biased perspective is important,

4256
03:54:09,100 --> 03:54:12,100
just to make sure we're not missing

4257
03:54:12,100 --> 03:54:15,100
anything. And while more analysis work

4258
03:54:15,100 --> 03:54:17,100
needs to be done, it's important that

4259
03:54:17,100 --> 03:54:19,100
we have that information early right

4260
03:54:19,100 --> 03:54:22,100
now, so that we can share that out with

4261
03:54:22,100 --> 03:54:24,100
the public. And glad this is not --

4262
03:54:24,100 --> 03:54:26,100
it's not a final report. We're

4263
03:54:26,100 --> 03:54:29,100
expecting that to come back. So that

4264
03:54:29,100 --> 03:54:32,601
we can have more concrete information

4265
03:54:33,100 --> 03:54:36,100
that is taking place. So just with

4266
03:54:36,100 --> 03:54:38,100
that being said, I do want to thank you

4267
03:54:38,100 --> 03:54:41,100
all for next steps and for making sure

4268
03:54:41,100 --> 03:54:43,100
that we get more details on that. And

4269
03:54:43,100 --> 03:54:47,100
sharing that out. But I do have a few

4270
03:54:47,100 --> 03:54:50,100
follow-up questions. I was curious

4271
03:54:53,100 --> 03:54:56,601
about the fuses and that show

4272
03:54:57,100 --> 03:55:00,100
non-standard failure. Do we have

4273
03:55:02,100 --> 03:55:03,100
suspected cause for non-standard

4274
03:55:03,100 --> 03:55:05,100
failure or is it still something that

4275
03:55:05,100 --> 03:55:07,100
is too early to tell?

4276
03:55:07,100 --> 03:55:08,100
>> We're currently investigating that,

4277
03:55:08,100 --> 03:55:10,100
and this is why we have recommended

4278
03:55:10,100 --> 03:55:11,100
further testing.

4279
03:55:11,100 --> 03:55:15,201
>> Okay. Thank you. And then just on

4280
03:55:16,100 --> 03:55:18,100
the paddles, just so I'm understanding

4281
03:55:18,100 --> 03:55:20,100
correctly. What it sounds like is that

4282
03:55:20,100 --> 03:55:23,100
the paddles are designed to break as a

4283
03:55:23,100 --> 03:55:27,201
safety function. So if that does happen

4284
03:55:28,100 --> 03:55:31,100
, could be associated with some of the

4285
03:55:31,100 --> 03:55:35,100
other causes the paddle breaking in in

4286
03:55:35,100 --> 03:55:37,100
and of itself would not necessarily be

4287
03:55:37,100 --> 03:55:39,100
the cause of arcing, blown cover,

4288
03:55:39,100 --> 03:55:41,100
anything like that; right? Is that

4289
03:55:41,100 --> 03:55:43,100
what I'm hearing?

4290
03:55:43,100 --> 03:55:45,100
>> So we've looked extensively at the

4291
03:55:45,100 --> 03:55:48,100
paddle loss and we have data on that.

4292
03:55:48,100 --> 03:55:52,801
There's a loss of analysis done on the

4293
03:55:53,100 --> 03:55:56,100
vehicles, vehicle log and certainly

4294
03:56:00,100 --> 03:56:04,100
included in that analysis. A number of

4295
03:56:04,100 --> 03:56:06,100
factors coming together, unusual

4296
03:56:06,100 --> 03:56:08,100
circumstances, if you like. And it

4297
03:56:08,100 --> 03:56:09,100
certainly has not been ruled out, but

4298
03:56:09,100 --> 03:56:12,100
it's part of the analysis.

4299
03:56:12,100 --> 03:56:16,201
>> Okay. That is helpful for me to

4300
03:56:19,100 --> 03:56:21,100
know. And I just want to make sure

4301
03:56:21,100 --> 03:56:24,100
that one of the things that I feel

4302
03:56:24,100 --> 03:56:26,100
Director Ames is saying, and she can

4303
03:56:26,100 --> 03:56:30,100
correct me if I'm wrong later is that

4304
03:56:30,100 --> 03:56:31,100
potentially the insulators may be the

4305
03:56:31,100 --> 03:56:34,100
root cause of some of these issues, but

4306
03:56:34,100 --> 03:56:36,100
what I'm seeing in this presentation,

4307
03:56:36,100 --> 03:56:39,100
and what I'm hearing is that rather

4308
03:56:39,100 --> 03:56:42,601
than insulators being the cause of

4309
03:56:43,100 --> 03:56:47,100
these issues, it is these other whether

4310
03:56:47,100 --> 03:56:50,100
environmental, human, all of these

4311
03:56:50,100 --> 03:56:53,100
other issues could be the potential

4312
03:56:53,100 --> 03:56:56,100
causing factors for the insulators

4313
03:56:57,100 --> 03:56:59,100
being blown or some cases not being

4314
03:56:59,100 --> 03:57:02,100
blown rather than the insulators being

4315
03:57:02,100 --> 03:57:03,100
the cause; right?

4316
03:57:03,100 --> 03:57:05,100
>> That is correct. This appears to

4317
03:57:05,100 --> 03:57:09,201
be in some cases an underlying factor

4318
03:57:10,100 --> 03:57:14,100
and perhaps the insulators may be more

4319
03:57:14,100 --> 03:57:16,100
vulnerable to failure because of the

4320
03:57:16,100 --> 03:57:18,100
condition, but that doesn't mean they

4321
03:57:18,100 --> 03:57:19,100
are the root cause.

4322
03:57:19,100 --> 03:57:23,100
>> I think it's important for me to

4323
03:57:23,100 --> 03:57:26,100
understand, just because there's nine,

4324
03:57:27,100 --> 03:57:30,100
eight, seven separate incidents with

4325
03:57:30,100 --> 03:57:31,100
potentially different contributing

4326
03:57:31,100 --> 03:57:34,100
causes. I did like what Director Ames

4327
03:57:34,100 --> 03:57:37,601
said about narrowing it down per

4328
03:57:38,100 --> 03:57:41,100
incident to see. Because there might

4329
03:57:41,100 --> 03:57:45,100
not be that one single cause and

4330
03:57:45,100 --> 03:57:47,100
understanding what happened would be

4331
03:57:47,100 --> 03:57:49,100
helpful. So that is all I wanted to

4332
03:57:49,100 --> 03:57:51,100
clarify, just to make sure that I was

4333
03:57:51,100 --> 03:57:53,100
on the same page with all of you.

4334
03:57:53,100 --> 03:57:55,100
Because it sounded like there was a lot

4335
03:57:55,100 --> 03:57:57,100
of back and forth -- there was a lot of

4336
03:57:57,100 --> 03:57:59,100
back and forth and I just wanted to

4337
03:57:59,100 --> 03:58:03,100
make sure that I understand what you

4338
03:58:03,100 --> 03:58:05,100
were all saying.

4339
03:58:05,100 --> 03:58:08,100
>> Director Flores, even though you

4340
03:58:08,100 --> 03:58:10,100
didn't ask the question, will be a

4341
03:58:10,100 --> 03:58:13,100
final report in the format as well.

4342
03:58:13,100 --> 03:58:15,100
You saw that one incident that we laid

4343
03:58:15,100 --> 03:58:18,100
out that showed the insulators, we'll

4344
03:58:18,100 --> 03:58:19,100
do a similar diagram for every single

4345
03:58:19,100 --> 03:58:22,100
incident, so will you have that. Once

4346
03:58:22,100 --> 03:58:24,100
again, once we get to the final report

4347
03:58:24,100 --> 03:58:25,100
stage will include that for every

4348
03:58:25,100 --> 03:58:27,100
single incident

4349
03:58:27,100 --> 03:58:28,100
.

4350
03:58:28,100 --> 03:58:29,100
>> That will be great and thank you

4351
03:58:29,100 --> 03:58:32,100
all for outlining the next step and

4352
03:58:32,100 --> 03:58:35,100
moving forward so quickly. I think

4353
03:58:35,100 --> 03:58:37,100
that is it for me right now and look

4354
03:58:37,100 --> 03:58:38,100
forward to getting more information at

4355
03:58:38,100 --> 03:58:40,100
a later point. Thank you.

4356
03:58:40,100 --> 03:58:42,100
>> Thank you. President Hernandez.

4357
03:58:42,100 --> 03:58:44,401
Followed by Director Li.

4358
03:58:45,100 --> 03:58:48,100
>> Thank you. Sylvia you and I spoke

4359
03:58:48,100 --> 03:58:50,100
yesterday with regards to what was

4360
03:58:50,100 --> 03:58:52,100
going to be in discussion today. And

4361
03:58:52,100 --> 03:58:55,100
the one thing that I see BART has been

4362
03:58:55,100 --> 03:58:57,100
a system for over 50 years and the one

4363
03:58:57,100 --> 03:58:59,401
item that was brought

4364
03:59:02,100 --> 03:59:05,100
was the checks and balances and making

4365
03:59:05,100 --> 03:59:06,100
sure that each Director in

4366
03:59:06,100 --> 03:59:08,100
charge of

4367
03:59:08,100 --> 03:59:12,201
whether an item to make sure we're

4368
03:59:19,100 --> 03:59:22,100
being proactive. I know we cannot know

4369
03:59:22,100 --> 03:59:24,100
every incident that is going to happen.

4370
03:59:24,100 --> 03:59:28,100
But it's our due diligence to make

4371
03:59:28,100 --> 03:59:31,100
sure there's communication. And going

4372
03:59:31,100 --> 03:59:35,100
back and making sure that each item is

4373
03:59:35,100 --> 03:59:39,801
checked off. And when I say that, when

4374
03:59:40,100 --> 03:59:43,100
a pilot gets into the cockpit, his

4375
03:59:43,100 --> 03:59:46,100
responsibility is to make sure

4376
03:59:46,100 --> 03:59:48,100
everything is checked off before he

4377
03:59:48,100 --> 03:59:49,100
moves the plane forward and if

4378
03:59:49,100 --> 03:59:51,100
something is not correct, then

4379
03:59:51,100 --> 03:59:53,100
maintenance comes in. They fix the

4380
03:59:53,100 --> 03:59:56,100
problem, and move on or they actually

4381
03:59:56,100 --> 03:59:59,100
cancel the flight and so on. So what

4382
03:59:59,100 --> 04:00:02,100
I'm seeing from our discussion a little

4383
04:00:02,100 --> 04:00:05,100
bit is making sure that each Director

4384
04:00:05,100 --> 04:00:08,100
is responsible for checking off that

4385
04:00:08,100 --> 04:00:11,100
list. And I just want to make sure

4386
04:00:11,100 --> 04:00:15,100
it's clear that each Director for each

4387
04:00:15,100 --> 04:00:17,100
Department moving forward understands

4388
04:00:17,100 --> 04:00:20,100
that. Whether it's making sure there's

4389
04:00:20,100 --> 04:00:22,100
more check-offs, making sure that our

4390
04:00:22,100 --> 04:00:25,100
General Manager gets the last word.

4391
04:00:25,100 --> 04:00:27,100
Can you just clarify how we're going to

4392
04:00:27,100 --> 04:00:29,100
do that moving forward?

4393
04:00:29,100 --> 04:00:32,601
>> Well, I think it's a combination.

4394
04:00:35,100 --> 04:00:38,100
What Shane's direction to his Staff and

4395
04:00:38,100 --> 04:00:40,100
his maintenance Department. I think

4396
04:00:40,100 --> 04:00:43,100
there's also from a higher-level

4397
04:00:43,100 --> 04:00:46,100
there's -- we need to put into place a

4398
04:00:46,100 --> 04:00:48,100
Change Control Board that has safety,

4399
04:00:48,100 --> 04:00:52,801
has a General Manager, has the AGM of

4400
04:00:54,100 --> 04:00:55,100
Operations signing off and potentially

4401
04:00:55,100 --> 04:00:58,100
the OID if it's a construction project

4402
04:00:58,100 --> 04:01:01,100
versus a maintenance project. So I

4403
04:01:01,100 --> 04:01:03,100
think you know, in initial

4404
04:01:03,100 --> 04:01:04,100
conversations with our Chief Safety

4405
04:01:04,100 --> 04:01:07,100
Officer, what he talked about is a

4406
04:01:07,100 --> 04:01:09,100
Change Control Board basically. So I

4407
04:01:09,100 --> 04:01:13,100
think what we'd have to do is use maybe

4408
04:01:13,100 --> 04:01:16,100
our asset risk register to identify

4409
04:01:16,100 --> 04:01:17,100
criticality of assets which already

4410
04:01:17,100 --> 04:01:19,100
know what that is and I think we need

4411
04:01:19,100 --> 04:01:24,100
to put a set of criteria that says if

4412
04:01:24,100 --> 04:01:27,100
this changes, in this configuration,

4413
04:01:27,100 --> 04:01:29,100
you are not allowed to make that change

4414
04:01:29,100 --> 04:01:31,100
without signoff and BART has tons of

4415
04:01:31,100 --> 04:01:35,100
processes that require us to do system

4416
04:01:35,100 --> 04:01:39,100
access requests, or site -- what is

4417
04:01:39,100 --> 04:01:41,100
that? Site-specific Work Plans that

4418
04:01:41,100 --> 04:01:43,100
have to get into place months before we

4419
04:01:43,100 --> 04:01:45,100
do the work. So we can tack it onto

4420
04:01:45,100 --> 04:01:47,100
that process that says this person has

4421
04:01:47,100 --> 04:01:49,100
to sign off before we can move forward.

4422
04:01:49,100 --> 04:01:51,100
And I think in some of those cases

4423
04:01:51,100 --> 04:01:54,100
that insides to be escalated up, and

4424
04:01:54,100 --> 04:01:57,100
again, part of that has to be what are

4425
04:01:57,100 --> 04:01:58,100
you going to do at the end? How you

4426
04:01:58,100 --> 04:02:02,801
are going to put that back in place?

4427
04:02:04,100 --> 04:02:06,100
And again as Shane said, maintenance is

4428
04:02:06,100 --> 04:02:08,100
there first and last and there needs to

4429
04:02:08,100 --> 04:02:10,100
be something to trigger the signoff

4430
04:02:10,100 --> 04:02:12,100
through maintenance or the contractor

4431
04:02:12,100 --> 04:02:14,100
that says that work has been completed.

4432
04:02:14,100 --> 04:02:17,100
>> President Hernandez, just to add

4433
04:02:17,100 --> 04:02:21,100
what she is saying more directly, you

4434
04:02:21,100 --> 04:02:22,100
know, this accountability, and however

4435
04:02:22,100 --> 04:02:25,100
you want to frame it, the check-off,

4436
04:02:25,100 --> 04:02:27,100
the pilot, and checking that. Those

4437
04:02:27,100 --> 04:02:31,100
folks that you are talking about, those

4438
04:02:31,100 --> 04:02:33,100
"pilots" are in this room right now.

4439
04:02:33,100 --> 04:02:36,100
That is why Michael brought them in.

4440
04:02:36,100 --> 04:02:38,100
It's Mike Gibson and Derek Calhoun

4441
04:02:38,100 --> 04:02:42,201
and Leo Pica, Jeff Lau and Myat

4442
04:02:45,100 --> 04:02:47,100
San and those that are responsible for

4443
04:02:47,100 --> 04:02:49,100
elements in the system and that

4444
04:02:49,100 --> 04:02:52,100
checklist, that check off list, that is

4445
04:02:52,100 --> 04:02:56,201
their world. So having them here that

4446
04:02:57,100 --> 04:03:00,100
comment from you, it is very powerful,

4447
04:03:00,100 --> 04:03:03,100
because that kind of accountability is

4448
04:03:03,100 --> 04:03:05,100
what we need to get to what Director

4449
04:03:05,100 --> 04:03:07,100
Ghosh was talking about. About

4450
04:03:07,100 --> 04:03:10,100
improving the system, improving the

4451
04:03:11,100 --> 04:03:13,100
reliabilities for our riders and

4452
04:03:13,100 --> 04:03:14,100
couldn't agree more.

4453
04:03:14,100 --> 04:03:15,100
>> Thank you. I just bring that

4454
04:03:15,100 --> 04:03:17,100
forward because in a City, I always

4455
04:03:17,100 --> 04:03:19,100
revert back to the City, we tend to do

4456
04:03:19,100 --> 04:03:23,100
that; right? We want to make sure

4457
04:03:23,100 --> 04:03:24,100
that before we have something that

4458
04:03:24,100 --> 04:03:26,100
needs to be fixed, because it's age,

4459
04:03:26,100 --> 04:03:29,100
that we want to bring it forward in

4460
04:03:29,100 --> 04:03:32,100
enough time. So that we can beat that

4461
04:03:32,100 --> 04:03:33,100
time-lapse. So just wanted to make

4462
04:03:33,100 --> 04:03:37,100
sure that we're all on the same vision

4463
04:03:37,100 --> 04:03:40,100
of moving forward, and I do appreciate

4464
04:03:40,100 --> 04:03:42,100
the thorough report.

4465
04:03:42,100 --> 04:03:43,100
>> Thank you. Director Li.

4466
04:03:43,100 --> 04:03:46,601
>> I have really brief comments here.

4467
04:03:47,100 --> 04:03:49,100
So my colleagues have said so much and

4468
04:03:49,100 --> 04:03:51,100
to associate myself with the comments

4469
04:03:51,100 --> 04:03:53,100
to thank Staff and third-quarter party

4470
04:03:53,100 --> 04:03:54,100
consultants at Parsons for the

4471
04:03:54,100 --> 04:03:55,100
extensive investigation and

4472
04:03:55,100 --> 04:03:57,100
particularly want to associate myself

4473
04:03:57,100 --> 04:03:59,100
with Director Wright's comments. Look,

4474
04:03:59,100 --> 04:04:03,100
we have been at this conversation for

4475
04:04:03,100 --> 04:04:07,100
what two hours now? That is such a

4476
04:04:07,100 --> 04:04:10,601
tiny fraction of near 15,000 hours that

4477
04:04:13,100 --> 04:04:15,100
went into the investigation and no one

4478
04:04:15,100 --> 04:04:17,100
this Board, love you all, my

4479
04:04:17,100 --> 04:04:20,100
colleagues, no one on this Board are

4480
04:04:20,100 --> 04:04:22,401
subject-matter experts and certainly

4481
04:04:23,100 --> 04:04:24,100
we're not subject-matter experts on the

4482
04:04:24,100 --> 04:04:26,100
breadth of knowledge needed to

4483
04:04:26,100 --> 04:04:27,100
unravel the situations that had

4484
04:04:27,100 --> 04:04:30,100
happened, which is why we bring in

4485
04:04:30,100 --> 04:04:31,100
third-party consultants which amongst

4486
04:04:31,100 --> 04:04:33,100
all of your people, you all can figure

4487
04:04:33,100 --> 04:04:35,100
this out. We're not going to figure

4488
04:04:35,100 --> 04:04:37,100
this out. We're not going to just go

4489
04:04:37,100 --> 04:04:40,100
into your grab bag of brainstorm idea

4490
04:04:40,100 --> 04:04:42,100
and have you looked at this? You have.

4491
04:04:42,100 --> 04:04:45,601
You have done 15,000 hours of looking

4492
04:04:46,100 --> 04:04:48,100
at stuff and we're not going to do that

4493
04:04:48,100 --> 04:04:53,100
in two hours and not smart enough to do

4494
04:04:53,100 --> 04:04:56,100
in two hours. What is really, really

4495
04:04:56,100 --> 04:04:58,100
important is BART is safe for our

4496
04:04:58,100 --> 04:05:00,100
riders and we know that BART is safe

4497
04:05:00,100 --> 04:05:02,100
for our riders, because born out of our

4498
04:05:02,100 --> 04:05:05,100
data, you can see that in our Quarterly

4499
04:05:05,100 --> 04:05:06,100
Service Performance Reviews. I looked

4500
04:05:06,100 --> 04:05:08,100
at our latest one that you presented

4501
04:05:08,100 --> 04:05:11,601
back in December cover Q1, July,

4502
04:05:13,100 --> 04:05:15,100
August and September. Which includes a

4503
04:05:15,100 --> 04:05:18,601
few of the incidents that you

4504
04:05:20,100 --> 04:05:22,401
investigated. We have point .14

4505
04:05:23,100 --> 04:05:26,100
vehicles per million riders when

4506
04:05:26,100 --> 04:05:27,100
looking at passenger safety number

4507
04:05:27,100 --> 04:05:29,100
and give or take about a million rides per

4508
04:05:29,100 --> 04:05:33,100
week in our system. So you can see how

4509
04:05:33,100 --> 04:05:35,100
incredibly rare passenger safety

4510
04:05:35,100 --> 04:05:38,100
incidents on our trains occur. That

4511
04:05:38,100 --> 04:05:41,100
puts BART as one of the safety transit

4512
04:05:41,100 --> 04:05:44,100
system in our country and that is in

4513
04:05:44,100 --> 04:05:47,100
the data. That we report to the FTA

4514
04:05:47,100 --> 04:05:51,100
regularly. And that we present to the

4515
04:05:51,100 --> 04:05:54,100
public quarterly. BART is a damn safe

4516
04:05:54,100 --> 04:05:57,100
system. So thank you for those

4517
04:05:57,100 --> 04:06:00,601
efforts. With all that said, and

4518
04:06:02,100 --> 04:06:05,100
echoing what Director Wright said,

4519
04:06:05,100 --> 04:06:06,100
that's the perception of our system that

4520
04:06:06,100 --> 04:06:08,100
make a difference for our riders in

4521
04:06:08,100 --> 04:06:12,201
trusting us as a government agency, and

4522
04:06:14,100 --> 04:06:16,100
trusting us believing beyond just the

4523
04:06:16,100 --> 04:06:18,100
numbers that we're the safety system.

4524
04:06:18,100 --> 04:06:21,100
And I think this investigation, these

4525
04:06:21,100 --> 04:06:23,100
man hours, this deeper look and

4526
04:06:23,100 --> 04:06:26,100
ultimately what will become a final

4527
04:06:26,100 --> 04:06:28,100
full report is that level of

4528
04:06:28,100 --> 04:06:29,100
transparency we need to give

4529
04:06:29,100 --> 04:06:31,100
credibility to the work that you have

4530
04:06:31,100 --> 04:06:35,201
all done, that Parsons has done to

4531
04:06:36,100 --> 04:06:38,100
ensure we remain safe and we're

4532
04:06:38,100 --> 04:06:40,100
proactive and building in your

4533
04:06:40,100 --> 04:06:42,100
protocols every step of our

4534
04:06:42,100 --> 04:06:43,100
construction projects every step of our

4535
04:06:43,100 --> 04:06:46,100
State of Good Repair work that we're

4536
04:06:46,100 --> 04:06:48,100
doing everything right. We're being

4537
04:06:48,100 --> 04:06:51,100
proactive and we're preventing further

4538
04:06:51,100 --> 04:06:53,100
incidents from occurring. That keep

4539
04:06:53,100 --> 04:06:55,100
our system running. So I will end my

4540
04:06:55,100 --> 04:06:57,100
comments there. Thank you so much.

4541
04:06:57,100 --> 04:07:01,100
>> Thank you, Director Li. Let me ask

4542
04:07:01,100 --> 04:07:02,100
a few questions, or provide a few

4543
04:07:02,100 --> 04:07:06,100
comments before we wrap up. First off,

4544
04:07:06,100 --> 04:07:08,100
thank you. Honesty and transparency

4545
04:07:08,100 --> 04:07:10,100
are critical in government, and so you

4546
04:07:10,100 --> 04:07:12,100
coming to us today, and identifying

4547
04:07:12,100 --> 04:07:16,100
some areas where we have some gaps that

4548
04:07:16,100 --> 04:07:20,100
we can fix is important. That does

4549
04:07:20,100 --> 04:07:24,100
build our reputation in the area that

4550
04:07:24,100 --> 04:07:27,100
folks that we care about ridership. I

4551
04:07:27,100 --> 04:07:30,100
will also be clear that when BART has

4552
04:07:30,100 --> 04:07:32,100
an issue, it isn't just BART passengers

4553
04:07:32,100 --> 04:07:34,100
impacted, but it's the entire Bay Area

4554
04:07:34,100 --> 04:07:37,100
and traffic throughout the Bay Area is

4555
04:07:37,100 --> 04:07:40,100
greatly impacted when we aren't able to

4556
04:07:40,100 --> 04:07:42,100
provide service. So the world is much

4557
04:07:42,100 --> 04:07:44,100
larger than the ridership that we live

4558
04:07:44,100 --> 04:07:47,100
in today. So I look at this as a

4559
04:07:47,100 --> 04:07:49,100
learning opportunity. This is a chance

4560
04:07:49,100 --> 04:07:52,100
for us as an agency to identify what we

4561
04:07:52,100 --> 04:07:56,100
see as challenges that we can address

4562
04:07:56,100 --> 04:07:57,100
and understand what are some of the

4563
04:07:57,100 --> 04:07:59,100
challenges that we may not yet be

4564
04:07:59,100 --> 04:08:01,100
seeing? I so welcome this and I think

4565
04:08:01,100 --> 04:08:04,100
it's ultimately in the best interest of

4566
04:08:04,100 --> 04:08:06,100
BART and the greater Bay Area. With

4567
04:08:06,100 --> 04:08:10,201
that said, did we look at other

4568
04:08:14,100 --> 04:08:16,100
electrified railways? Are we unique in

4569
04:08:16,100 --> 04:08:17,100
it sense or something that other

4570
04:08:17,100 --> 04:08:20,601
agencies have experienced and did we

4571
04:08:22,100 --> 04:08:24,100
gain anything from that?

4572
04:08:24,100 --> 04:08:26,100
>> Yes, we have looked at other

4573
04:08:26,100 --> 04:08:29,601
systems, and many team members, and

4574
04:08:32,100 --> 04:08:34,100
SMEs and technical specialists have

4575
04:08:34,100 --> 04:08:36,100
direct experience working for those

4576
04:08:36,100 --> 04:08:37,100
other agencies not just myself, but

4577
04:08:37,100 --> 04:08:39,100
other Members of the Team have worked

4578
04:08:39,100 --> 04:08:42,100
for New York City Transit, and other

4579
04:08:42,100 --> 04:08:44,100
agencies. So that data point, those

4580
04:08:44,100 --> 04:08:47,100
data points are there. I think it's

4581
04:08:47,100 --> 04:08:51,100
too early to say right now, but based

4582
04:08:51,100 --> 04:08:54,100
on our understanding and our analysis

4583
04:08:54,100 --> 04:08:56,100
these circumstances appear to be quite

4584
04:08:56,100 --> 04:08:57,100
unique to this system.

4585
04:08:57,100 --> 04:09:00,100
>> Thank you. We have been told BART

4586
04:09:00,100 --> 04:09:03,100
is unique many times before. So

4587
04:09:03,100 --> 04:09:05,100
understood. As part of this sort of

4588
04:09:05,100 --> 04:09:09,201
data analyses, did we bring in Alstom,

4589
04:09:11,100 --> 04:09:13,100
the folks that take care of our trains?

4590
04:09:13,100 --> 04:09:17,100
The creators of our trains to give us

4591
04:09:17,100 --> 04:09:19,100
some SME feedback?

4592
04:09:19,100 --> 04:09:21,100
>> Chair, sorry about that, we have

4593
04:09:21,100 --> 04:09:24,100
not brought them in yet. We wanted to

4594
04:09:24,100 --> 04:09:25,100
do this completely independent. As far

4595
04:09:25,100 --> 04:09:29,801
as that review , but we do plan to

4596
04:09:30,100 --> 04:09:32,100
bring them in moving forward.

4597
04:09:32,100 --> 04:09:34,100
>> Based on what I'm hearing today, I

4598
04:09:34,100 --> 04:09:35,100
think it's critical that we bring in

4599
04:09:35,100 --> 04:09:37,100
our train manufacturer to look at are

4600
04:09:37,100 --> 04:09:39,100
there any contributes issues or

4601
04:09:39,100 --> 04:09:41,100
potential causes? So I think that

4602
04:09:41,100 --> 04:09:42,100
would be critical for us to do. And

4603
04:09:42,100 --> 04:09:46,801
kind of speaking to that issue, do we

4604
04:09:47,100 --> 04:09:48,100
capture any undercarriage video?

4605
04:09:48,100 --> 04:09:50,100
Because I think we should explore that

4606
04:09:50,100 --> 04:09:51,100
if we don't?

4607
04:09:51,100 --> 04:09:53,100
>> We don't right now. But it is one

4608
04:09:53,100 --> 04:09:56,100
of the recommendations from the team.

4609
04:09:56,100 --> 04:09:57,100
There's different reasons why we

4610
04:09:57,100 --> 04:09:59,100
haven't done that. But definitely

4611
04:09:59,100 --> 04:10:02,100
something we can talk to the Chief

4612
04:10:02,100 --> 04:10:04,100
Mechanical Officer.

4613
04:10:05,100 --> 04:10:08,100
>> All right. To me it's another data

4614
04:10:08,100 --> 04:10:11,100
point and another potential piece of

4615
04:10:11,100 --> 04:10:14,100
the puzzle to identify some of these

4616
04:10:14,100 --> 04:10:17,100
challenges. Lastly, I know you

4617
04:10:17,100 --> 04:10:19,100
mentioned rail grinding vehicles and

4618
04:10:19,100 --> 04:10:22,100
not necessarily being a root cause, but

4619
04:10:22,100 --> 04:10:24,100
could be a contributing factor. Have

4620
04:10:24,100 --> 04:10:27,100
we thought about -- I know at home,

4621
04:10:27,100 --> 04:10:31,201
with your sanding, some of your tools

4622
04:10:34,100 --> 04:10:37,100
have a vac built into it, so the dust is

4623
04:10:37,100 --> 04:10:41,201
captured as you are grinding. Is we

4624
04:10:43,100 --> 04:10:44,100
looked at retrofitting those as we're

4625
04:10:44,100 --> 04:10:45,100
grinding?

4626
04:10:45,100 --> 04:10:47,100
>> Directors, we have two rail grinders

4627
04:10:47,100 --> 04:10:50,100
that have vacuum system on them with

4628
04:10:50,100 --> 04:10:53,100
two collector cars. They collect as

4629
04:10:53,100 --> 04:10:57,100
much of the spoil and not micro dust,

4630
04:10:57,100 --> 04:10:59,100
but dust that it can. And then the

4631
04:10:59,100 --> 04:11:02,601
other thing that we're talking about,

4632
04:11:03,100 --> 04:11:07,201
when we're talking about metal dust is

4633
04:11:10,100 --> 04:11:13,100
the rear wheel interface, which is not

4634
04:11:13,100 --> 04:11:17,100
picked up by the grinder every night.

4635
04:11:17,100 --> 04:11:19,100
Because the wheels won't get newer and

4636
04:11:19,100 --> 04:11:21,100
we have that dilemma as well.

4637
04:11:21,100 --> 04:11:24,601
>> Understood. Well, maybe we need a

4638
04:11:26,100 --> 04:11:27,100
vacuum truck to run around the system.

4639
04:11:27,100 --> 04:11:30,100
With that I will conclude my feedback

4640
04:11:30,100 --> 04:11:32,100
and the E&O agenda items, I will turn

4641
04:11:32,100 --> 04:11:34,100
it back over to President Hernandez.

4642
04:11:34,100 --> 04:11:36,100
>> Thank you, Directors.

4643
04:11:37,100 --> 04:11:39,100
>> Thank you

4644
04:11:42,100 --> 04:11:44,100
>> Thank you. Our Item No. 8 is our

4645
04:11:44,100 --> 04:11:47,100
Planning, Public Affairs, Access and

4646
04:11:48,100 --> 04:11:51,601
Legislation item. And Chaired by Chair

4647
04:11:54,100 --> 04:11:56,100
Raburn.

4648
04:12:12,100 --> 04:12:15,100
>> We'll plough on through the

4649
04:12:16,100 --> 04:12:17,100
Planning, Public Affairs, Access and

4650
04:12:17,100 --> 04:12:19,100
Legislation and we have one item to

4651
04:12:19,100 --> 04:12:20,100
discuss, and it's the -- ?

4652
04:12:20,100 --> 04:12:23,100
>> Excuse me, can you please take out

4653
04:12:23,100 --> 04:12:25,100
any conversation outside of this room.

4654
04:12:25,100 --> 04:12:27,401
>> Continue your conversation outside,

4655
04:12:29,100 --> 04:12:33,801
and the one item for approval is the

4656
04:12:34,100 --> 04:12:37,601
goals and objectives for the Fremont

4657
04:12:39,100 --> 04:12:40,100
station Transit-Oriented Development

4658
04:12:40,100 --> 04:12:43,100
project. Each of the Directors have a

4659
04:12:43,100 --> 04:12:46,601
letter from the City of Fremont's

4660
04:12:48,100 --> 04:12:50,100
Community Development Director, or

4661
04:12:50,100 --> 04:12:52,100
signed by the development Director.

4662
04:12:52,100 --> 04:12:55,100
It's a very supportive letter. And I

4663
04:12:55,100 --> 04:12:59,100
want to share that I'm excited about

4664
04:12:59,100 --> 04:13:03,100
this project and I hope we can move

4665
04:13:03,100 --> 04:13:05,100
right along with getting everybody's

4666
04:13:05,100 --> 04:13:08,601
input into those goals and objectives

4667
04:13:10,100 --> 04:13:11,100
without delay. Thank you.

4668
04:13:11,100 --> 04:13:13,100
>> Thank you, Director Raburn, we're

4669
04:13:13,100 --> 04:13:15,100
excited about this project as well. So

4670
04:13:15,100 --> 04:13:17,100
we're here to get approval today on the

4671
04:13:17,100 --> 04:13:20,100
goals and objectives for the Fremont

4672
04:13:20,100 --> 04:13:23,100
TOD. Our Staff has worked with

4673
04:13:23,100 --> 04:13:26,100
stakeholders in the City to take the

4674
04:13:26,100 --> 04:13:29,100
Board adopted TOD goals and develop

4675
04:13:29,100 --> 04:13:30,100
specific project objectivities. So we

4676
04:13:30,100 --> 04:13:33,601
have Matt Lewis, our Principal property

4677
04:13:36,100 --> 04:13:38,100
Vermont and Kamala Park our Principal

4678
04:13:38,100 --> 04:13:41,100
planner on station planning and I will

4679
04:13:41,100 --> 04:13:45,100
hand it to Kasheica, our Director of TOD.

4680
04:13:45,100 --> 04:13:47,100
>> Good afternoon, Directors. Before I

4681
04:13:47,100 --> 04:13:51,100
hand it over to Matt and Kamala to work

4682
04:13:51,100 --> 04:13:53,100
through the presentation to say why

4683
04:13:53,100 --> 04:13:55,100
Fremont is such a great TOD

4684
04:13:55,100 --> 04:13:57,100
opportunity. The station opened in the

4685
04:13:57,100 --> 04:14:01,201
early 70s. And for 45 years served as

4686
04:14:02,100 --> 04:14:05,100
a major access point into the BART

4687
04:14:05,100 --> 04:14:08,100
system and in 2017, when the Warms

4688
04:14:08,100 --> 04:14:10,100
Springs station opened, it was no

4689
04:14:10,100 --> 04:14:12,100
longer a huge demand for parking at the

4690
04:14:12,100 --> 04:14:13,100
Fremont station.

4691
04:14:13,100 --> 04:14:16,100
>> Can you pull the mic a little

4692
04:14:16,100 --> 04:14:17,100
closer?

4693
04:14:17,100 --> 04:14:20,100
>> Okay. So there was no longer a

4694
04:14:20,100 --> 04:14:22,100
huge demand for parking as there had

4695
04:14:22,100 --> 04:14:24,100
been in the past at Fremont statement

4696
04:14:24,100 --> 04:14:26,100
with the opening of the Warms Springs

4697
04:14:26,100 --> 04:14:28,100
station. So with close to 2,000

4698
04:14:28,100 --> 04:14:31,601
parking spaces with less than 30% now

4699
04:14:32,100 --> 04:14:33,100
being utilized, we think that the

4700
04:14:33,100 --> 04:14:36,100
Fremont station can be very

4701
04:14:39,100 --> 04:14:41,401
thoughtfully developed to create

4702
04:14:42,100 --> 04:14:43,100
residential housing, walkable

4703
04:14:43,100 --> 04:14:44,100
amenities, and stronger ridership base.

4704
04:14:44,100 --> 04:14:49,100
So now I will turn it over to Matt and

4705
04:14:49,100 --> 04:14:52,100
Kamala to work you through the details

4706
04:14:52,100 --> 04:14:55,100
of goals and objectives for the TOD,

4707
04:14:55,100 --> 04:14:58,100
which we worked very closely with our

4708
04:14:58,100 --> 04:15:01,100
City partners and the community to

4709
04:15:01,100 --> 04:15:03,100
attain these goals. Turn it over.

4710
04:15:03,100 --> 04:15:04,100
>> Good afternoon, Directors. Thank

4711
04:15:04,100 --> 04:15:06,100
you for your time and attention on

4712
04:15:06,100 --> 04:15:09,100
Fremont TOD goals and objectives,

4713
04:15:11,100 --> 04:15:13,100
reviewing the site, station access and

4714
04:15:13,100 --> 04:15:15,100
planning efforts to-date and dive into

4715
04:15:15,100 --> 04:15:19,100
the goals and the objectives and the

4716
04:15:19,100 --> 04:15:21,100
community engagement done so far and

4717
04:15:21,100 --> 04:15:25,201
proceed to next steps and a motion.

4718
04:15:30,100 --> 04:15:33,100
Back in 2024 the parking stations

4719
04:15:34,100 --> 04:15:36,100
development for the site and we have

4720
04:15:36,100 --> 04:15:39,100
largely confirmed the advantages that

4721
04:15:39,100 --> 04:15:41,100
were previously identified. For one,

4722
04:15:41,100 --> 04:15:44,601
the parking lots are an expansive 23

4723
04:15:47,100 --> 04:15:50,100
gross acres. Sizeable for a

4724
04:15:50,100 --> 04:15:51,100
large-scale development and positioned

4725
04:15:51,100 --> 04:15:54,100
for development through state and local

4726
04:15:54,100 --> 04:15:56,100
policy including AB 2923 and the City

4727
04:15:56,100 --> 04:15:58,100
of Fremont's zoning standards that

4728
04:15:58,100 --> 04:16:01,100
allow up to 12 stories for most of

4729
04:16:01,100 --> 04:16:03,100
the site. City also identified in its

4730
04:16:03,100 --> 04:16:05,100
most recent housing element and we

4731
04:16:05,100 --> 04:16:07,100
closely coordinated with City of

4732
04:16:07,100 --> 04:16:08,100
Fremont Planning and transportation

4733
04:16:08,100 --> 04:16:10,100
Staff and given an opportunity to

4734
04:16:10,100 --> 04:16:13,100
comment and contribute to the goals

4735
04:16:13,100 --> 04:16:14,100
and objectives statement. Finally, the

4736
04:16:14,100 --> 04:16:16,100
rider parking lots have low

4737
04:16:16,100 --> 04:16:18,100
utilization, which creates the

4738
04:16:18,100 --> 04:16:20,100
opportunity to use a portion of rider

4739
04:16:20,100 --> 04:16:22,100
parking lot for TOD, and avoid the

4740
04:16:22,100 --> 04:16:25,100
expense and complication of building a

4741
04:16:25,100 --> 04:16:29,100
BART rider garage to replace the lost

4742
04:16:29,100 --> 04:16:33,100
Park and Kamala will explain more of

4743
04:16:33,100 --> 04:16:37,100
that in a moment. We have conducted

4744
04:16:37,100 --> 04:16:38,100
several due diligence studies on the

4745
04:16:38,100 --> 04:16:41,100
site. The most important study done to

4746
04:16:41,100 --> 04:16:44,601
identify the location of the Hayward

4747
04:16:45,100 --> 04:16:48,100
fault. Fortunately the area was

4748
04:16:48,100 --> 04:16:51,100
heavily study for the Warms Springs

4749
04:16:51,100 --> 04:16:54,100
extension and able to utilize the study

4750
04:16:54,100 --> 04:16:56,100
as shown in the image to the right. In

4751
04:16:56,100 --> 04:16:58,100
response to the research we decided to

4752
04:16:58,100 --> 04:17:01,100
exclude the areas that are closest to

4753
04:17:01,100 --> 04:17:03,100
the fault from the developer

4754
04:17:03,100 --> 04:17:05,100
solicitation that we're proposing to do

4755
04:17:05,100 --> 04:17:07,100
this year. We also conducted market

4756
04:17:07,100 --> 04:17:09,100
research with real estate developers

4757
04:17:09,100 --> 04:17:12,100
and heard that major office and retail

4758
04:17:12,100 --> 04:17:15,100
developments not viable here, but high

4759
04:17:15,100 --> 04:17:17,100
density residential is. And several

4760
04:17:17,100 --> 04:17:19,100
developers suggested dividing up the

4761
04:17:19,100 --> 04:17:22,601
site into different phases to reduce

4762
04:17:24,100 --> 04:17:27,100
their risk exposure and we contacted

4763
04:17:27,100 --> 04:17:28,100
the nearby Hospital facilities to see

4764
04:17:28,100 --> 04:17:30,100
if they are interested and they are not

4765
04:17:30,100 --> 04:17:32,100
currently looking for additional land

4766
04:17:32,100 --> 04:17:34,100
for expansion. We closely studied the

4767
04:17:34,100 --> 04:17:35,100
station access conditions here, which I

4768
04:17:35,100 --> 04:17:39,201
will hand over to Kamala to explain.

4769
04:17:43,100 --> 04:17:46,100
>> Thank you, Matt. So Fremont

4770
04:17:49,100 --> 04:17:51,100
station folks get there by a variety of

4771
04:17:51,100 --> 04:17:53,100
modes, but the most important thing in

4772
04:17:53,100 --> 04:17:56,100
this chart is that driving and parking

4773
04:17:56,100 --> 04:18:00,100
has been reducing as a share of the

4774
04:18:00,100 --> 04:18:03,100
riders who get there. For example,

4775
04:18:03,100 --> 04:18:06,601
looking at the most current 2024 data,

4776
04:18:07,100 --> 04:18:10,100
40% get there without a car while

4777
04:18:10,100 --> 04:18:13,100
nearly 30% are dropped off and less

4778
04:18:13,100 --> 04:18:16,601
than 34% drive and Park. You may

4779
04:18:17,100 --> 04:18:20,100
already be aware that BART's 2016

4780
04:18:21,100 --> 04:18:24,100
station access policy set five

4781
04:18:24,100 --> 04:18:26,401
different station access typologies.

4782
04:18:28,100 --> 04:18:29,100
From urban to auto-dependent partially

4783
04:18:29,100 --> 04:18:31,100
based on the share of riders would

4784
04:18:31,100 --> 04:18:34,100
drive. This station is currently

4785
04:18:35,100 --> 04:18:37,100
intermodal auto reliant, but with TOD

4786
04:18:37,100 --> 04:18:39,100
it's expected to become balanced

4787
04:18:39,100 --> 04:18:40,100
intermodal as the share of riders who

4788
04:18:40,100 --> 04:18:43,100
drive to the station decreases. Even

4789
04:18:43,100 --> 04:18:46,100
without the TOD the Fremont station is

4790
04:18:46,100 --> 04:18:49,100
already in the balanced intermodal

4791
04:18:50,100 --> 04:18:53,100
share. The TOD will change access to

4792
04:18:53,100 --> 04:18:56,601
the station with the expectation that

4793
04:18:57,100 --> 04:18:59,100
less riders will drive and Park and

4794
04:18:59,100 --> 04:19:01,401
thankfully Fremont has being

4795
04:19:02,100 --> 04:19:03,100
diligently transforming their streets

4796
04:19:03,100 --> 04:19:06,100
to prioritize safety and accessibility

4797
04:19:07,100 --> 04:19:08,100
for all. Three City-led infrastructure

4798
04:19:08,100 --> 04:19:10,100
projects to improve walking and biking

4799
04:19:10,100 --> 04:19:14,201
within a mile of this Fremont station

4800
04:19:15,100 --> 04:19:17,100
received safe routes to BART funding.

4801
04:19:17,100 --> 04:19:20,601
The City of Fremont has implemented

4802
04:19:23,100 --> 04:19:25,100
many roadway projects citywide, like

4803
04:19:25,100 --> 04:19:27,100
the one around the station as part of

4804
04:19:27,100 --> 04:19:29,100
their Vision Zero program. Their

4805
04:19:29,100 --> 04:19:32,100
annual rate of traffic fatalities is

4806
04:19:32,100 --> 04:19:35,601
three, whereas the nation, state and

4807
04:19:36,100 --> 04:19:39,100
Bay Area cities range from 4-13

4808
04:19:39,100 --> 04:19:41,100
fatalities per 100,000 people. This

4809
04:19:41,100 --> 04:19:43,100
means that our riders are getting --

4810
04:19:43,100 --> 04:19:47,100
are getting to our stations safer, and

4811
04:19:47,100 --> 04:19:50,100
doesn't matter what mode of travel they

4812
04:19:50,100 --> 04:19:53,601
are using. The Fremont station as

4813
04:19:54,100 --> 04:19:57,100
Kasheica mentioned was built with 1900

4814
04:19:59,100 --> 04:20:02,100
space because it was end-of-line until

4815
04:20:02,100 --> 04:20:04,100
2017. Parking demand in the

4816
04:20:04,100 --> 04:20:07,100
foreseeable future will not require more

4817
04:20:07,100 --> 04:20:10,100
than 740 spaces. The first three rows

4818
04:20:10,100 --> 04:20:12,100
show how Tuesday through Thursday

4819
04:20:12,100 --> 04:20:15,100
parking occupancies have been trending

4820
04:20:17,100 --> 04:20:20,100
down since 2015 to 29% currently. The

4821
04:20:21,100 --> 04:20:23,100
last row shows expected ridership based

4822
04:20:23,100 --> 04:20:25,100
on BART's financial projections, and

4823
04:20:25,100 --> 04:20:27,401
associated parking demand in 2038.

4824
04:20:28,100 --> 04:20:31,100
This assumes that Core Capacity

4825
04:20:32,100 --> 04:20:34,100
Program, and VTA's BART extension to

4826
04:20:34,100 --> 04:20:36,100
Santa Clara are fully operation by

4827
04:20:36,100 --> 04:20:38,100
then. You can see that parking demand

4828
04:20:38,100 --> 04:20:41,100
would be at most 740 spaces, less than

4829
04:20:41,100 --> 04:20:45,100
half of the 1900 spaces. Now back to

4830
04:20:45,100 --> 04:20:47,100
Matt.

4831
04:20:49,100 --> 04:20:52,100
>> Thanks Kamala. On the right of the

4832
04:20:52,100 --> 04:20:54,100
slide an overview of the general

4833
04:20:54,100 --> 04:20:55,100
process of developing TOD of so right

4834
04:20:55,100 --> 04:20:58,100
now we're proposing to move from step

4835
04:20:58,100 --> 04:21:00,100
1, pre-solicitation planning to step 2,

4836
04:21:00,100 --> 04:21:02,100
develop solicitation and goals and

4837
04:21:02,100 --> 04:21:04,100
objectives is the vehicle for doing

4838
04:21:04,100 --> 04:21:05,100
that. As the high-level parameters of

4839
04:21:05,100 --> 04:21:09,100
the TOD project and will be included in

4840
04:21:09,100 --> 04:21:11,100
the solicitation for developer. The

4841
04:21:11,100 --> 04:21:13,100
goals and objectives statement is shaped

4842
04:21:13,100 --> 04:21:14,100
around the goals for the overall TOD

4843
04:21:14,100 --> 04:21:16,100
program, which were adopted by the

4844
04:21:16,100 --> 04:21:19,100
Board in 2020. And are listed here in

4845
04:21:19,100 --> 04:21:21,100
the third bullet. The objectives for

4846
04:21:21,100 --> 04:21:24,100
each goal is how tailoring the goals to

4847
04:21:24,100 --> 04:21:25,100
the particular condition and

4848
04:21:25,100 --> 04:21:28,601
aspirations for the Fremont TOD. It's

4849
04:21:37,100 --> 04:21:38,100
not operating. Something is wrong with

4850
04:21:38,100 --> 04:21:42,100
the clicker here -- there we go. These

4851
04:21:42,100 --> 04:21:45,100
next two slides have the Board adopted

4852
04:21:45,100 --> 04:21:48,100
goals and key objectives for Fremont

4853
04:21:48,100 --> 04:21:51,601
TOD. We're highlighting them, the main

4854
04:21:52,100 --> 04:21:56,201
ones here. And these are the three

4855
04:21:59,100 --> 04:22:02,100
remaining goals and their main

4856
04:22:02,100 --> 04:22:03,100
objectives. In addition to the

4857
04:22:03,100 --> 04:22:06,100
affordability goal we're proposing the

4858
04:22:07,100 --> 04:22:08,100
City of Fremont's inclusionary zoning

4859
04:22:08,100 --> 04:22:11,100
policy also applies to the TOD, which

4860
04:22:11,100 --> 04:22:14,100
call for a portion of the project to

4861
04:22:14,100 --> 04:22:17,100
have middle-income housing in some

4862
04:22:17,100 --> 04:22:22,100
cases as well. We put out a draft of

4863
04:22:22,100 --> 04:22:24,100
the objective statement for public

4864
04:22:24,100 --> 04:22:26,100
feedback. We held open houses at

4865
04:22:26,100 --> 04:22:29,100
Fremont station and survey open for

4866
04:22:29,100 --> 04:22:33,801
weeks, and we got a lot of great

4867
04:22:35,100 --> 04:22:38,100
feedback on how to design TOD and

4868
04:22:38,100 --> 04:22:39,100
parking and affordable levels as well

4869
04:22:39,100 --> 04:22:43,201
and covered in the local news. The

4870
04:22:47,100 --> 04:22:49,100
next few slides height the important

4871
04:22:49,100 --> 04:22:51,100
objective proposing of the first up to

4872
04:22:51,100 --> 04:22:53,100
divide the parking lots into two phases

4873
04:22:53,100 --> 04:22:54,100
for development and leave out a

4874
04:22:54,100 --> 04:22:56,100
substantial portion that is

4875
04:22:56,100 --> 04:22:57,100
undevelopable due to the presence of

4876
04:22:57,100 --> 04:23:00,100
the Hayward fault and the first phase

4877
04:23:00,100 --> 04:23:01,100
shown in yellow, undevelopable area is

4878
04:23:01,100 --> 04:23:04,100
shown in red, and the second phase is

4879
04:23:04,100 --> 04:23:06,100
shown in purple. First phase we're

4880
04:23:06,100 --> 04:23:08,100
proposing to do a developer

4881
04:23:08,100 --> 04:23:10,100
solicitation for this year. And it

4882
04:23:10,100 --> 04:23:11,100
will include eight acres and primarily

4883
04:23:11,100 --> 04:23:14,100
consist of housing and ground floor

4884
04:23:14,100 --> 04:23:16,100
retail, which is consistent with the

4885
04:23:16,100 --> 04:23:18,100
City's zoning. So advantages on this

4886
04:23:18,100 --> 04:23:20,100
phasing approach at first reserves

4887
04:23:20,100 --> 04:23:23,100
enough parking spaces for existing and

4888
04:23:23,100 --> 04:23:26,100
foreseeable demand. That means no

4889
04:23:26,100 --> 04:23:28,100
replacement parking garage is necessary for

4890
04:23:28,100 --> 04:23:30,100
the first phase to proceed in full and

4891
04:23:30,100 --> 04:23:31,100
second, it's responsive to developer

4892
04:23:31,100 --> 04:23:33,100
feedback that the site would attract

4893
04:23:33,100 --> 04:23:34,100
more interest if divided up, and third,

4894
04:23:34,100 --> 04:23:37,100
it gives us time on phase 2 to wait for

4895
04:23:37,100 --> 04:23:40,100
market conditions for conducive for

4896
04:23:43,100 --> 04:23:45,100
development. I will hand it back to

4897
04:23:45,100 --> 04:23:47,100
Kamalu.

4898
04:23:47,100 --> 04:23:49,100
>> Public feedback we received

4899
04:23:49,100 --> 04:23:50,100
stated concern about the BART

4900
04:23:50,100 --> 04:23:53,601
loss of parking for TOD phase 1

4901
04:23:55,100 --> 04:23:57,100
retaining 700 parking spaces on-site,

4902
04:23:57,100 --> 04:23:59,100
430 near Washington Hospital, where TOD

4903
04:23:59,100 --> 04:24:02,601
phase 2 would be located and 250 were

4904
04:24:05,100 --> 04:24:06,100
the Hayward earthquake fault prevents

4905
04:24:06,100 --> 04:24:08,100
development. There's also a 30-space

4906
04:24:08,100 --> 04:24:10,100
parking lot under the track near

4907
04:24:10,100 --> 04:24:13,601
Mallory that could be re-opened if

4908
04:24:14,100 --> 04:24:16,100
needed. Riders who drive may opt to

4909
04:24:16,100 --> 04:24:18,100
Park at Union City and Warms

4910
04:24:18,100 --> 04:24:21,100
Springs/South Fremont stations which

4911
04:24:22,100 --> 04:24:24,100
also have underutilized parking lots.

4912
04:24:24,100 --> 04:24:27,100
Parking demand will be revisited before

4913
04:24:27,100 --> 04:24:28,100
pursuing solicitation for TOD phrase 2,

4914
04:24:28,100 --> 04:24:31,100
along with strategies to accommodate it

4915
04:24:31,100 --> 04:24:34,100
by investigating options for on-site

4916
04:24:34,100 --> 04:24:37,601
surface podium and garage parking, and

4917
04:24:38,100 --> 04:24:39,100
off-site on-streets, and in private

4918
04:24:39,100 --> 04:24:42,100
lots where BART riders could be allowed

4919
04:24:42,100 --> 04:24:45,100
to pay to Park. Improving walking and

4920
04:24:45,100 --> 04:24:48,100
biking in and around the station area

4921
04:24:48,100 --> 04:24:51,100
was also a frequent comment from

4922
04:24:51,100 --> 04:24:54,601
community members, and that aligns with

4923
04:24:56,100 --> 04:24:59,100
our adopted policies. Many community

4924
04:25:00,100 --> 04:25:02,100
members were real excited about the

4925
04:25:02,100 --> 04:25:05,100
potential development. They want the

4926
04:25:05,100 --> 04:25:09,100
Fremont station TOD to create a "dense

4927
04:25:09,100 --> 04:25:12,100
intensive an active focal point for the

4928
04:25:12,100 --> 04:25:14,100
entire City Center."

4929
04:25:15,100 --> 04:25:18,100
That was articulated from the 2015

4930
04:25:18,100 --> 04:25:20,100
Community Plan. The current zoning of

4931
04:25:20,100 --> 04:25:22,100
BART land is City Center Transit

4932
04:25:22,100 --> 04:25:24,100
Neighborhood, this is mostly

4933
04:25:24,100 --> 04:25:26,401
high-density residential with some

4934
04:25:27,100 --> 04:25:30,100
small-scale services and retail. The

4935
04:25:30,100 --> 04:25:31,100
two-phased approach to development

4936
04:25:31,100 --> 04:25:33,100
would allow us to advance mostly

4937
04:25:33,100 --> 04:25:35,100
housing on the Northeast side while

4938
04:25:35,100 --> 04:25:37,100
keeping that West side available for

4939
04:25:37,100 --> 04:25:40,100
non-residential options in the future.

4940
04:25:40,100 --> 04:25:43,100
We refined the objectives under

4941
04:25:45,100 --> 04:25:48,100
complete community goals to emphasize

4942
04:25:48,100 --> 04:25:49,100
recreation and socializing

4943
04:25:49,100 --> 04:25:51,100
opportunities with the caveat that

4944
04:25:51,100 --> 04:25:53,100
non-residential components are

4945
04:25:53,100 --> 04:25:55,100
dependent on market feasibility, and

4946
04:25:55,100 --> 04:25:57,100
what the selected developer team

4947
04:25:57,100 --> 04:25:58,100
proposes. Now I will hand it back to

4948
04:25:58,100 --> 04:26:01,100
Matt to wrap it up.

4949
04:26:06,100 --> 04:26:09,100
>> Thank you Kamala. First we request

4950
04:26:09,100 --> 04:26:11,100
that the Board approve the proposed

4951
04:26:11,100 --> 04:26:13,100
goals and objectives statement and if

4952
04:26:13,100 --> 04:26:16,601
approved BART Staff will issue a

4953
04:26:18,100 --> 04:26:19,100
solicitation for developer. For

4954
04:26:19,100 --> 04:26:22,100
summer 2026 to return to the Board

4955
04:26:22,100 --> 04:26:24,100
for development partner and authority to enter

4956
04:26:24,100 --> 04:26:25,100
into an Exclusive Negotiating Agreement

4957
04:26:25,100 --> 04:26:27,100
with them and then BART Staff and

4958
04:26:27,100 --> 04:26:29,100
developer will negotiate a term sheet

4959
04:26:29,100 --> 04:26:33,100
and return to the Board with terms and

4960
04:26:33,100 --> 04:26:35,100
construction would start as early as a

4961
04:26:35,100 --> 04:26:37,100
year after that. Thank you for your

4962
04:26:37,100 --> 04:26:41,100
time and interest. We're happy to take

4963
04:26:41,100 --> 04:26:45,201
your questions and to proceed to the

4964
04:26:46,100 --> 04:26:47,100
slide with the motion.

4965
04:26:47,100 --> 04:26:48,100
>> Thank you, we have the best Staff.

4966
04:26:48,100 --> 04:26:51,100
Do we have any public comments?

4967
04:26:51,100 --> 04:26:54,601
>> We have one, Glen Overton. Glen.

4968
04:27:12,100 --> 04:27:15,100
>> Madam President, and Staff. I'm

4969
04:27:22,100 --> 04:27:25,601
for any housing development on BART

4970
04:27:30,100 --> 04:27:32,100
land. TOD, Transit-Oriented

4971
04:27:37,100 --> 04:27:40,100
Development is not just a fad, it's a

4972
04:27:40,100 --> 04:27:44,801
need. We need TOD, so we don't turn

4973
04:27:48,100 --> 04:27:51,100
out like Los Angeles and burn every

4974
04:27:51,100 --> 04:27:55,201
damn thing down. People need to live

4975
04:27:56,100 --> 04:27:59,601
close to their transit to have

4976
04:28:01,100 --> 04:28:02,100
transit-friendly and community-friendly

4977
04:28:02,100 --> 04:28:04,100
access.

4978
04:28:05,100 --> 04:28:09,201
To have a choice between leaving the

4979
04:28:10,100 --> 04:28:13,100
car parked, walking, accessing culture,

4980
04:28:22,100 --> 04:28:24,100
and their environment, providing for

4981
04:28:24,100 --> 04:28:27,100
their children and working and just

4982
04:28:27,100 --> 04:28:31,801
living life the way life should be led.

4983
04:28:37,100 --> 04:28:39,401
Accessible housing, transit is

4984
04:28:44,100 --> 04:28:45,100
optimal, thoughtful, necessary. Thank

4985
04:28:45,100 --> 04:28:47,100
you.

4986
04:28:48,100 --> 04:28:52,201
>> Thank you, Glen. Any other -- no

4987
04:28:53,100 --> 04:28:55,100
further public speakers. The Chair

4988
04:28:55,100 --> 04:28:59,100
likes to speak last. I would like to

4989
04:28:59,100 --> 04:29:02,601
hear from Director Ames first, whose

4990
04:29:03,100 --> 04:29:05,100
District this project is in. Again,

4991
04:29:05,100 --> 04:29:08,100
our goal is to get to approval of a

4992
04:29:08,100 --> 04:29:09,100
motion.

4993
04:29:09,100 --> 04:29:11,100
>> Thank you, Director Raburn. Thank

4994
04:29:11,100 --> 04:29:15,801
you, Staff. You did a great job. I'm

4995
04:29:17,100 --> 04:29:19,100
very pleased. I went to a few Town

4996
04:29:19,100 --> 04:29:22,100
Hall and I do appreciate that you want

4997
04:29:22,100 --> 04:29:25,100
to reserve a portion of the site for

4998
04:29:25,100 --> 04:29:26,100
potential commercial activity in the

4999
04:29:26,100 --> 04:29:28,100
future and I'm all about the transit

5000
04:29:28,100 --> 04:29:31,100
Village, but I don't want housing and a

5001
04:29:31,100 --> 04:29:33,100
little retail, but jobs and housing

5002
04:29:33,100 --> 04:29:35,100
balance. So I did meet with a hotel

5003
04:29:35,100 --> 04:29:37,100
developer before COVID and they were

5004
04:29:37,100 --> 04:29:38,100
interested in putting a hotel there

5005
04:29:38,100 --> 04:29:41,100
because of all of the hospitals. It's

5006
04:29:41,100 --> 04:29:43,100
not just Washington Hospital, but

5007
04:29:43,100 --> 04:29:46,100
Kaiser and the Palo Alto Foundation is

5008
04:29:46,100 --> 04:29:47,100
just about a mile-and-a-half away. So

5009
04:29:47,100 --> 04:29:51,100
it's a great site. The County --

5010
04:29:51,100 --> 04:29:54,100
Alameda County library is close by and

5011
04:29:54,100 --> 04:29:56,100
it's a fantastic location to build

5012
04:29:56,100 --> 04:30:00,201
housing at a dense rate. Hopefully we

5013
04:30:07,100 --> 04:30:09,100
can get those standards. Fremont has a

5014
04:30:09,100 --> 04:30:12,601
higher standard -- what is it? 12

5015
04:30:13,100 --> 04:30:16,601
stories. Ours is 7 stories, and they

5016
04:30:17,100 --> 04:30:19,100
have 12 stories.

5017
04:30:34,100 --> 04:30:37,100
The intermodal standard BART placed on

5018
04:30:37,100 --> 04:30:41,100
the side, but received so many grants

5019
04:30:41,100 --> 04:30:44,601
and activated the Street. So much

5020
04:30:46,100 --> 04:30:48,100
improvement. They had elevated with

5021
04:30:48,100 --> 04:30:51,100
the sidewalk with the multimodal

5022
04:30:51,100 --> 04:30:52,100
corridor, where they eliminated the

5023
04:30:52,100 --> 04:30:56,801
right turn lane. So you have a huge

5024
04:30:59,100 --> 04:31:00,100
multimodal corridor where cars have

5025
04:31:00,100 --> 04:31:04,801
to wait at the light and turn when

5026
04:31:05,100 --> 04:31:07,100
it's green. Because they took out the

5027
04:31:07,100 --> 04:31:11,201
turn lane, it's a tremendous open area

5028
04:31:12,100 --> 04:31:15,601
for biking and walking and using

5029
04:31:18,100 --> 04:31:21,100
scooters. This multimodal corridor is

5030
04:31:24,100 --> 04:31:26,100
also going to the High School. The

5031
04:31:26,100 --> 04:31:29,601
site is a complete success. I'm

5032
04:31:30,100 --> 04:31:32,100
excited. I guess I just had questions

5033
04:31:32,100 --> 04:31:33,100
about the Hayward fault. My

5034
04:31:33,100 --> 04:31:36,100
understanding with the Hayward fault,

5035
04:31:36,100 --> 04:31:39,100
it does have a core fault and it's got

5036
04:31:39,100 --> 04:31:41,100
transverse cracks and you can't build

5037
04:31:41,100 --> 04:31:42,100
on the cracks. So I just want to make

5038
04:31:42,100 --> 04:31:44,100
sure that the Staff has a good

5039
04:31:44,100 --> 04:31:47,100
evaluation on that. Because I thought

5040
04:31:47,100 --> 04:31:49,100
the Building Code didn't allow you to

5041
04:31:49,100 --> 04:31:51,100
build on those -- it's not just a crack

5042
04:31:51,100 --> 04:31:54,100
itself. The Hayward fault there's like

5043
04:31:54,100 --> 04:31:57,100
100' buffer from the fault. Then

5044
04:31:57,100 --> 04:31:59,100
there's other cracks that go across the

5045
04:31:59,100 --> 04:32:04,100
fault. So I just want to make sure you

5046
04:32:04,100 --> 04:32:07,100
could follow-up on that. But

5047
04:32:07,100 --> 04:32:09,100
essentially, having the mixed-use

5048
04:32:09,100 --> 04:32:13,201
component next to the bus depot is

5049
04:32:16,100 --> 04:32:17,100
tremendous. The only thing I wanted to

5050
04:32:17,100 --> 04:32:22,100
see in addition to this is -- I hate to

5051
04:32:22,100 --> 04:32:26,100
say it, but vendor activation in the

5052
04:32:26,100 --> 04:32:28,100
station itself. A lot of people want

5053
04:32:28,100 --> 04:32:30,100
to hang out inside the station and I

5054
04:32:30,100 --> 04:32:32,100
know there's many Directors that want

5055
04:32:32,100 --> 04:32:34,100
to activate our stations inside, and

5056
04:32:34,100 --> 04:32:37,100
also outside. But inside, I know we

5057
04:32:37,100 --> 04:32:39,100
keep resisting. I hope we can maybe --

5058
04:32:39,100 --> 04:32:41,100
I don't know if that is a goal for the

5059
04:32:41,100 --> 04:32:44,100
TOD? But I think it should be a goal

5060
04:32:44,100 --> 04:32:48,201
for BART to consider ways to activate

5061
04:32:49,100 --> 04:32:52,100
inside the station. So I also just

5062
04:32:52,100 --> 04:32:54,100
after we were so excited about this

5063
04:32:54,100 --> 04:32:56,100
project, I did talk to the City of

5064
04:32:56,100 --> 04:32:59,100
Fremont and they are looking at similar

5065
04:32:59,100 --> 04:33:01,100
to the Berryessa station, where we

5066
04:33:01,100 --> 04:33:03,100
would connect the Fremont station to

5067
04:33:03,100 --> 04:33:06,100
the Bay Area ridge trail and the Vargas

5068
04:33:06,100 --> 04:33:08,100
plateau. It's not in the bike plan,

5069
04:33:08,100 --> 04:33:10,100
but Fremont is taking the lead on that.

5070
04:33:10,100 --> 04:33:14,100
So look at what happened to stimulate

5071
04:33:14,100 --> 04:33:15,100
the community. They are really excited

5072
04:33:15,100 --> 04:33:18,100
and I will move to approve these

5073
04:33:18,100 --> 04:33:19,100
measures. Just one more thing about

5074
04:33:19,100 --> 04:33:22,100
housing. I have one more comment. I

5075
04:33:22,100 --> 04:33:24,100
do appreciate, Matt, that you brought

5076
04:33:24,100 --> 04:33:27,100
up the missing middle-income housing

5077
04:33:27,100 --> 04:33:30,100
element, which I guess you are saying

5078
04:33:30,100 --> 04:33:33,100
Fremont has. So the middle-income

5079
04:33:34,100 --> 04:33:37,100
bracket is 80% to 120% Area Median

5080
04:33:38,100 --> 04:33:41,100
Income. So the City has a target, it's

5081
04:33:41,100 --> 04:33:45,100
a little over 10%. And a lot of

5082
04:33:45,100 --> 04:33:47,100
communities don't build housing. This

5083
04:33:47,100 --> 04:33:49,100
is really the middle-income bracket.

5084
04:33:49,100 --> 04:33:53,100
It doesn't get built. I hope this

5085
04:33:53,100 --> 04:33:56,100
project does that, because it's very

5086
04:33:56,100 --> 04:33:57,100
difficult to build. It just doesn't

5087
04:33:57,100 --> 04:33:59,100
happen in the Bay Area. It's

5088
04:33:59,100 --> 04:34:03,100
unfortunate. So I move to approve the

5089
04:34:03,100 --> 04:34:04,100
TOD goals thank you.

5090
04:34:04,100 --> 04:34:06,100
>> I will second.

5091
04:34:06,100 --> 04:34:10,801
>> Thank you. We have a motion and a

5092
04:34:12,100 --> 04:34:13,100
second. Director Foley.

5093
04:34:13,100 --> 04:34:16,100
>> Thank you, Chair Raburn. First

5094
04:34:16,100 --> 04:34:19,100
off, thank you for to the TOD team for

5095
04:34:19,100 --> 04:34:23,801
bringing this to us today. I'm glad to

5096
04:34:24,100 --> 04:34:26,100
hear that Director Ames supports this,

5097
04:34:26,100 --> 04:34:28,100
because I also support this and it's

5098
04:34:28,100 --> 04:34:30,100
good to know we're all on the same page

5099
04:34:30,100 --> 04:34:32,100
here. I did have a couple of quick

5100
04:34:32,100 --> 04:34:35,601
questions. Because it seemed odd you

5101
04:34:36,100 --> 04:34:38,100
were bringing back objectives, which I

5102
04:34:38,100 --> 04:34:39,100
hadn't really the past. So you are

5103
04:34:39,100 --> 04:34:42,100
looking for us to approve what you laid

5104
04:34:42,100 --> 04:34:44,100
out on slides 11, 12 and 13, is that

5105
04:34:44,100 --> 04:34:48,201
correct? It's not a blanket approve of

5106
04:34:49,100 --> 04:34:51,401
everything under the sun?

5107
04:34:52,100 --> 04:34:55,100
>> The EDD included in the Board

5108
04:34:55,100 --> 04:34:57,100
packet had an attachment with the full

5109
04:34:57,100 --> 04:35:00,100
list of goals and objectives.

5110
04:35:01,100 --> 04:35:03,100
>> Super. You will be coming back to

5111
04:35:03,100 --> 04:35:06,100
us in the future for an update on phase

5112
04:35:06,100 --> 04:35:08,100
2 when we get there, and I assume phase

5113
04:35:08,100 --> 04:35:12,100
1 as we get into the ENA process and

5114
04:35:12,100 --> 04:35:16,201
all of that good stuff? Super. Okay.

5115
04:35:27,100 --> 04:35:29,100
The last point, concern I will raise,

5116
04:35:29,100 --> 04:35:32,100
we're going to do a ground lease, how

5117
04:35:32,100 --> 04:35:34,100
do we protect our investment when

5118
04:35:34,100 --> 04:35:37,100
building so close to a fault? What I

5119
04:35:37,100 --> 04:35:41,201
don't want is repeat of the Coliseum

5120
04:35:42,100 --> 04:35:46,801
connection, where we have an act of God

5121
04:35:48,100 --> 04:35:51,100
or natural disaster that displaced

5122
04:35:51,100 --> 04:35:55,100
people for more than a year and had a

5123
04:35:55,100 --> 04:35:59,201
less than willing partner in making the

5124
04:36:00,100 --> 04:36:02,100
property something that people could --

5125
04:36:02,100 --> 04:36:05,100
excuse me, return to? So I just want

5126
04:36:05,100 --> 04:36:07,100
to know, are we looking at language,

5127
04:36:07,100 --> 04:36:09,100
when we start looking at agreements on

5128
04:36:09,100 --> 04:36:11,100
this? Where there is some sort of

5129
04:36:11,100 --> 04:36:15,100
protection for this agency? If the --

5130
04:36:15,100 --> 04:36:18,100
if -- whoever is going to operate this

5131
04:36:18,100 --> 04:36:22,100
piece of property is not meeting their

5132
04:36:22,100 --> 04:36:24,100
obligations?

5133
04:36:24,100 --> 04:36:28,100
>> So as it relates to the proximity

5134
04:36:28,100 --> 04:36:31,100
to the fault, and kind of the zone of

5135
04:36:31,100 --> 04:36:34,601
influence of the default, there has

5136
04:36:36,100 --> 04:36:39,100
been extensive studies and assessments

5137
04:36:39,100 --> 04:36:41,100
done already and in addition to that,

5138
04:36:41,100 --> 04:36:43,100
any developer developing on our sites

5139
04:36:43,100 --> 04:36:45,100
have to comply with Building Code for

5140
04:36:45,100 --> 04:36:49,100
the State, as it relates to the

5141
04:36:49,100 --> 04:36:51,100
proximity or building anywhere near a

5142
04:36:51,100 --> 04:36:55,100
fault. And to, of course, the local

5143
04:36:55,100 --> 04:36:57,100
Building Codes, which are more strict

5144
04:36:57,100 --> 04:37:01,201
than they were in the past. And

5145
04:37:02,100 --> 04:37:04,100
Fremont is not unique to any other part

5146
04:37:04,100 --> 04:37:06,100
of the Bay Area necessarily in its

5147
04:37:06,100 --> 04:37:09,100
proximity to the fault. I understand

5148
04:37:09,100 --> 04:37:12,100
that we just so happen to know where

5149
04:37:12,100 --> 04:37:16,201
this one is exactly, but we have

5150
04:37:17,100 --> 04:37:19,100
existing structures, and we will do

5151
04:37:19,100 --> 04:37:20,100
additional assessment. The developer

5152
04:37:20,100 --> 04:37:23,100
will do their own assessment to make

5153
04:37:23,100 --> 04:37:26,601
sure that we are mitigating and

5154
04:37:28,100 --> 04:37:29,100
limiting our risks.

5155
04:37:29,100 --> 04:37:33,801
>> I just want to make sure that we're

5156
04:37:34,100 --> 04:37:38,100
in a position where we're not exposed

5157
04:37:38,100 --> 04:37:40,100
after something occurs? That is really

5158
04:37:40,100 --> 04:37:42,100
what I'm most concerned about here is

5159
04:37:42,100 --> 04:37:44,100
that exposure in limiting that? So I

5160
04:37:44,100 --> 04:37:46,100
would argue that the Coliseum

5161
04:37:46,100 --> 04:37:48,100
connection was built to building

5162
04:37:48,100 --> 04:37:51,100
standards, and all of the above, but we

5163
04:37:51,100 --> 04:37:55,100
still had an issue and problem that we

5164
04:37:55,100 --> 04:37:57,100
had to resolve. I would like not to

5165
04:37:57,100 --> 04:37:59,100
have that in future and have some

5166
04:37:59,100 --> 04:38:01,100
language in any sort of agreement that

5167
04:38:01,100 --> 04:38:03,401
gives us an out.

5168
04:38:04,100 --> 04:38:08,100
>> Director Foley -- sorry I was going

5169
04:38:08,100 --> 04:38:10,100
to call you President Foley, sore

5170
04:38:10,100 --> 04:38:12,100
before I that President Hernandez.

5171
04:38:12,100 --> 04:38:15,100
Both I and Michael and Kasheica are

5172
04:38:15,100 --> 04:38:16,100
looking for opportunities to strengthen

5173
04:38:16,100 --> 04:38:19,100
language had a may or may not have

5174
04:38:19,100 --> 04:38:21,100
being in the Coliseum connection lease

5175
04:38:21,100 --> 04:38:24,100
agreement. They are working with Jeana

5176
04:38:24,100 --> 04:38:28,201
and Legal Counsel to make sure that

5177
04:38:32,100 --> 04:38:35,100
BART is protected and airtight, so BART

5178
04:38:35,100 --> 04:38:36,100
is protected and more importantly the

5179
04:38:36,100 --> 04:38:38,100
residents of the community are

5180
04:38:38,100 --> 04:38:40,100
protected. So the three of us are

5181
04:38:40,100 --> 04:38:44,801
tight on that, and you know, and Jeana

5182
04:38:46,100 --> 04:38:49,100
is with us on that concept.

5183
04:38:49,100 --> 04:38:52,100
>> Thank you, I appreciate the words

5184
04:38:52,100 --> 04:38:56,201
of support. Thank you. Tch thank you,

5185
04:39:00,100 --> 04:39:01,100
Director Foley. Director Flores.

5186
04:39:01,100 --> 04:39:02,100
>> Thank you so much for the

5187
04:39:02,100 --> 04:39:05,100
presentation. I agree the site is

5188
04:39:05,100 --> 04:39:06,100
primed for TOD development. I think

5189
04:39:06,100 --> 04:39:08,100
that all the work that the City has

5190
04:39:08,100 --> 04:39:10,100
done not only in rezoning and

5191
04:39:10,100 --> 04:39:11,100
identifying this in their housing

5192
04:39:11,100 --> 04:39:14,601
element, but also doing the Pedestrian

5193
04:39:15,100 --> 04:39:18,100
and bike improvements in that area make

5194
04:39:18,100 --> 04:39:22,100
this a perfect place. I am very happy

5195
04:39:22,100 --> 04:39:25,100
that the City of Fremont has being a

5196
04:39:25,100 --> 04:39:26,100
collaborative partner and you can see

5197
04:39:26,100 --> 04:39:28,100
that I think in their capacity that

5198
04:39:28,100 --> 04:39:31,100
they have zoned for this area. I'm

5199
04:39:31,100 --> 04:39:35,100
supportive of this, but just curious if

5200
04:39:35,100 --> 04:39:38,100
the middle-income housing program that

5201
04:39:39,100 --> 04:39:41,100
they're expecting, or requiring would

5202
04:39:41,100 --> 04:39:43,100
that be managed by the developer, by

5203
04:39:43,100 --> 04:39:47,100
the City, or a low-income program that

5204
04:39:47,100 --> 04:39:50,601
someone applies and you need income

5205
04:39:52,100 --> 04:39:53,100
verification and the selection process,

5206
04:39:53,100 --> 04:39:57,100
do you all know how that would work?

5207
04:39:57,100 --> 04:40:00,100
>> So as far as getting into the

5208
04:40:00,100 --> 04:40:03,100
details of the qualifications, or

5209
04:40:03,100 --> 04:40:04,100
qualifying residents, and things like

5210
04:40:04,100 --> 04:40:07,100
that we're not at that int we would be

5211
04:40:07,100 --> 04:40:09,100
able to really speak with any certainty

5212
04:40:09,100 --> 04:40:13,100
on how that process would go. But as

5213
04:40:13,100 --> 04:40:16,100
far as having the 80-120% AMI as a

5214
04:40:16,100 --> 04:40:18,100
goal, I think that would be something

5215
04:40:18,100 --> 04:40:20,100
that we would have if the solicitation.

5216
04:40:20,100 --> 04:40:24,100
And then we would have the developers

5217
04:40:24,100 --> 04:40:26,100
come back, and basically do a proposal

5218
04:40:26,100 --> 04:40:28,100
on how they might meet that goal.

5219
04:40:28,100 --> 04:40:30,100
>> So the developers would be

5220
04:40:30,100 --> 04:40:33,100
responsible for managing that. Okay.

5221
04:40:34,100 --> 04:40:35,100
Thanks.

5222
04:40:35,100 --> 04:40:38,601
>> Thank you very much. And Director

5223
04:40:39,100 --> 04:40:40,100
Ghosh.

5224
04:40:40,100 --> 04:40:42,100
>> I just wanted to express my support

5225
04:40:42,100 --> 04:40:46,100
for the project. I think I just see

5226
04:40:46,100 --> 04:40:50,100
the TOD at each station that we do

5227
04:40:50,100 --> 04:40:53,601
really expanding access for our people

5228
04:40:54,100 --> 04:40:56,100
who rely on BART. Fremont station used

5229
04:40:56,100 --> 04:40:58,100
to be my home station in the sense I

5230
04:40:58,100 --> 04:41:00,100
used to go from Berkeley to Fremont,

5231
04:41:00,100 --> 04:41:02,100
because that is where my in-laws lived

5232
04:41:02,100 --> 04:41:04,100
and now Warms Springs is closer to

5233
04:41:04,100 --> 04:41:05,100
them. So I haven't been to the

5234
04:41:05,100 --> 04:41:07,100
station, but it always felt like it's

5235
04:41:07,100 --> 04:41:09,100
in the middle of nowhere and I still

5236
04:41:09,100 --> 04:41:11,100
remember trying to ride my bike once

5237
04:41:11,100 --> 04:41:15,201
from that station to their house, and

5238
04:41:16,100 --> 04:41:18,100
it was a nightmare. So I think there's

5239
04:41:18,100 --> 04:41:20,100
great potential here to develop

5240
04:41:20,100 --> 04:41:23,601
housing, and almost to bring our

5241
04:41:24,100 --> 04:41:26,100
communities closer. When you are only

5242
04:41:26,100 --> 04:41:30,100
a BART ride away to visit someone who

5243
04:41:30,100 --> 04:41:35,100
lives at a BART TOD and it's great to

5244
04:41:35,100 --> 04:41:38,100
see that most of the goals that we have

5245
04:41:38,100 --> 04:41:41,100
throughout our TOD listed objectives

5246
04:41:41,100 --> 04:41:43,100
were aligned with that. It seems like

5247
04:41:43,100 --> 04:41:45,100
with the City. And that you all have

5248
04:41:45,100 --> 04:41:48,100
adjusted to make it more appropriate

5249
04:41:48,100 --> 04:41:51,100
for what is site-specific, and

5250
04:41:51,100 --> 04:41:52,100
community-specific. So I look forward

5251
04:41:52,100 --> 04:41:56,801
to seeing where this goes, and I hope

5252
04:41:57,100 --> 04:42:00,100
we can make even more of a place there

5253
04:42:00,100 --> 04:42:04,201
with this project. Thank you for all

5254
04:42:06,100 --> 04:42:08,100
the work.

5255
04:42:08,100 --> 04:42:11,601
>> Any other Board Members? I will

5256
04:42:13,100 --> 04:42:16,100
conclude then, and I have a few goals I

5257
04:42:16,100 --> 04:42:19,601
want to underline that our existing

5258
04:42:21,100 --> 04:42:24,601
policy for 35% affordable is the goal

5259
04:42:25,100 --> 04:42:29,201
that we would seek on building housing

5260
04:42:30,100 --> 04:42:33,601
at this site. Regarding recreation, of

5261
04:42:36,100 --> 04:42:39,100
course, there's a ginormous Park

5262
04:42:42,100 --> 04:42:46,100
nearby that will serve this area well.

5263
04:42:46,100 --> 04:42:49,100
However, for preschoolers, tots, I

5264
04:42:49,100 --> 04:42:53,100
think we'll need to plan for some tot

5265
04:42:53,100 --> 04:42:57,201
lots adjacent to the Housing. So that

5266
04:42:58,100 --> 04:43:01,601
it's very convenient. As well, access

5267
04:43:05,100 --> 04:43:09,201
to Lake Elizabeth crosses a couple of

5268
04:43:10,100 --> 04:43:14,100
major arterials that BART shows on our

5269
04:43:14,100 --> 04:43:17,601
high injury network maps that are

5270
04:43:18,100 --> 04:43:22,201
included in our safe trips to BART

5271
04:43:26,100 --> 04:43:28,401
plan. Mallory, Mission, Fremont

5272
04:43:29,100 --> 04:43:32,100
Boulevard, Paseo Padre, these require

5273
04:43:32,100 --> 04:43:33,100
countermeasures. So specifically we

5274
04:43:33,100 --> 04:43:37,201
want to get people safely from that

5275
04:43:38,100 --> 04:43:42,100
phase 1 site to both Lake Elizabeth, as

5276
04:43:42,100 --> 04:43:46,801
well as to the shopping in the central

5277
04:43:50,100 --> 04:43:54,201
Central Park area. And so within the

5278
04:43:56,100 --> 04:43:59,601
BART property, there is an internal

5279
04:44:00,100 --> 04:44:04,201
Street that connects phase 1 over to the

5280
04:44:08,100 --> 04:44:12,201
central toward The Paso Padre side of

5281
04:44:17,100 --> 04:44:20,100
the station. So that I think need to

5282
04:44:20,100 --> 04:44:23,601
be retained and prioritized for bike

5283
04:44:24,100 --> 04:44:26,100
and Pedestrian travel. There will be

5284
04:44:26,100 --> 04:44:30,201
increased demand to travel on that road

5285
04:44:32,100 --> 04:44:34,100
from motor vehicles, and don't let it

5286
04:44:34,100 --> 04:44:37,100
just happen, and then say oh, my gosh,

5287
04:44:37,100 --> 04:44:40,100
what are we going to do to protect the

5288
04:44:40,100 --> 04:44:43,100
bicyclists, or the pedestrians? So

5289
04:44:44,100 --> 04:44:48,100
that has to be an essential component

5290
04:44:48,100 --> 04:44:52,100
in order to get people from the new

5291
04:44:52,100 --> 04:44:54,100
development out, because all of our

5292
04:44:54,100 --> 04:44:58,201
Planning has mainly been to get people

5293
04:44:59,100 --> 04:45:03,100
to the station, and back home from the

5294
04:45:03,100 --> 04:45:07,201
station. So now we're planning with at

5295
04:45:08,100 --> 04:45:11,100
least two different destinations, both

5296
04:45:11,100 --> 04:45:13,100
the shopping. There's a rally's

5297
04:45:13,100 --> 04:45:17,201
nearby, but there is also Walnut square

5298
04:45:20,100 --> 04:45:24,100
-- or Walnut Plaza, which is a little

5299
04:45:24,100 --> 04:45:27,601
bit beyond rally's and another high

5300
04:45:29,100 --> 04:45:32,100
injury network to cross. So there's a

5301
04:45:32,100 --> 04:45:33,100
couple of additional goals to add in,

5302
04:45:33,100 --> 04:45:36,100
but I'm going to give my solid support

5303
04:45:36,100 --> 04:45:39,100
on this, and I look forward to seeing

5304
04:45:39,100 --> 04:45:42,100
the development proposals roll in.

5305
04:45:44,100 --> 04:45:46,100
Let's hear from the District Secretary,

5306
04:45:46,100 --> 04:45:48,100
would you please call the roll?

5307
04:45:48,100 --> 04:45:50,100
>> Yes. Certainly. Director Ames?

5308
04:45:50,100 --> 04:45:52,100
>> Yes.

5309
04:45:52,100 --> 04:45:53,100
>> Director Flores?

5310
04:45:53,100 --> 04:45:54,100
>> Aye.

5311
04:45:54,100 --> 04:45:55,100
>> Director Foley?

5312
04:45:55,100 --> 04:45:56,100
>> Aye.

5313
04:45:56,100 --> 04:45:57,100
>> Director Ghosh?

5314
04:45:57,100 --> 04:45:58,100
>> Yes.

5315
04:45:58,100 --> 04:45:59,100
>> Director Li?

5316
04:45:59,100 --> 04:46:00,100
>> Yes.

5317
04:46:00,100 --> 04:46:01,100
>> Director Raburn?

5318
04:46:01,100 --> 04:46:02,100
>> Yea.

5319
04:46:02,100 --> 04:46:03,100
>> Director Rinn?

5320
04:46:03,100 --> 04:46:04,100
>> Aye.

5321
04:46:04,100 --> 04:46:05,100
>> Vice President Wright?

5322
04:46:05,100 --> 04:46:06,100
>> Aye.

5323
04:46:06,100 --> 04:46:07,100
>> President Hernandez?

5324
04:46:07,100 --> 04:46:08,100
>> Aye.

5325
04:46:08,100 --> 04:46:09,100
>> Motion passes unanimously.

5326
04:46:09,100 --> 04:46:12,100
>> Thank you for your support everyone.

5327
04:46:12,100 --> 04:46:15,100
>> You're welcome. That concludes the

5328
04:46:17,100 --> 04:46:20,601
PPAAL Committee. Thank you, this moves

5329
04:46:23,100 --> 04:46:27,801
us over to Item No. 9, which is our

5330
04:46:30,100 --> 04:46:31,100
Board matters. Item A, any Board

5331
04:46:31,100 --> 04:46:34,100
Member reports at this time?

5332
04:46:34,100 --> 04:46:36,100
>> Yeah.

5333
04:46:36,100 --> 04:46:38,100
>> Director Ames.

5334
04:46:38,100 --> 04:46:42,201
>> Thank you. I thank Alicia and the

5335
04:46:43,100 --> 04:46:45,100
Staff, we have a Super Bowl web page

5336
04:46:45,100 --> 04:46:47,100
up and I talked to Alicia a lot about

5337
04:46:47,100 --> 04:46:49,100
this, because I wanted to see more

5338
04:46:49,100 --> 04:46:50,100
presentation on our website for the

5339
04:46:50,100 --> 04:46:54,100
soccer game and we got Super Bowl

5340
04:46:54,100 --> 04:46:58,100
coming. And I have been trying to

5341
04:46:58,100 --> 04:47:00,100
contact Levi Stadium with no success. I

5342
04:47:00,100 --> 04:47:02,100
just did it this morning, just trying

5343
04:47:02,100 --> 04:47:08,100
to get them to put our BART link on the

5344
04:47:12,100 --> 04:47:15,100
Levi's Stadium. They have even the

5345
04:47:15,100 --> 04:47:16,100
Bicycle Coalition. Silicon Valley

5346
04:47:16,100 --> 04:47:19,100
Bicycle Coalition is on the Levi's

5347
04:47:19,100 --> 04:47:21,100
Stadium website. I cannot figure out,

5348
04:47:21,100 --> 04:47:24,100
and Alicia is working on this, but we

5349
04:47:24,100 --> 04:47:26,100
have to get BART's link on there.

5350
04:47:26,100 --> 04:47:28,100
Because a lot of people in their

5351
04:47:28,100 --> 04:47:31,601
roadmap or their transit map doesn't

5352
04:47:32,100 --> 04:47:36,201
understand how BART links over to the

5353
04:47:39,100 --> 04:47:42,100
Stadium. Everybody lived there so

5354
04:47:43,100 --> 04:47:47,100
long, there's a link at Milpitas. It's

5355
04:47:47,100 --> 04:47:49,100
a relatively new station and to get the

5356
04:47:49,100 --> 04:47:53,801
word out to get Levi's Stadium to get

5357
04:47:54,100 --> 04:47:58,100
the BART transit icon on there, so they

5358
04:47:58,100 --> 04:48:01,100
can see that BART is a partner.

5359
04:48:01,100 --> 04:48:04,601
Caltrain is also on their website.

5360
04:48:05,100 --> 04:48:07,100
It's unfortunate. I know you are

5361
04:48:07,100 --> 04:48:09,100
trying Alicia, so keep it up. I don't

5362
04:48:09,100 --> 04:48:13,100
know, Bob, who can talk to the Levi's

5363
04:48:13,100 --> 04:48:14,100
Stadium folks? Maybe it's political.

5364
04:48:14,100 --> 04:48:17,100
I appreciate you doing more outreach

5365
04:48:17,100 --> 04:48:19,100
and I'm hoping to see our BART link on

5366
04:48:19,100 --> 04:48:22,100
the outside of Levi's Stadium.

5367
04:48:29,100 --> 04:48:31,100
>> Thank you, item B, Roll Call for

5368
04:48:31,100 --> 04:48:32,100
Introduction. Any Roll Call for

5369
04:48:32,100 --> 04:48:33,100
Introductions?

5370
04:48:33,100 --> 04:48:35,100
>> Can I just jump in and say, Bob,

5371
04:48:35,100 --> 04:48:36,100
can you talk about the role that you

5372
04:48:36,100 --> 04:48:40,201
play in the Bay Area Host Committee

5373
04:48:41,100 --> 04:48:42,100
just briefly?

5374
04:48:42,100 --> 04:48:45,601
>> So I'm on the Host Committee,

5375
04:48:46,100 --> 04:48:48,100
Directors, and the Host Committee is

5376
04:48:48,100 --> 04:48:50,100
the kind of the think-tank of not only

5377
04:48:50,100 --> 04:48:53,100
the Super Bowl and the FIFA games, but

5378
04:48:53,100 --> 04:48:55,100
other events that we're -- we as a

5379
04:48:55,100 --> 04:48:58,601
region, are chasing with the leadership

5380
04:48:59,100 --> 04:49:01,100
here. And so me being on the Host

5381
04:49:01,100 --> 04:49:04,100
Committee, and the link between -- to

5382
04:49:04,100 --> 04:49:06,100
all the other operators is very

5383
04:49:06,100 --> 04:49:10,100
critical. And I have a lot of back and

5384
04:49:10,100 --> 04:49:11,100
forth with Members directly with the

5385
04:49:11,100 --> 04:49:14,601
Host Committee with Rodd Lee staffing

5386
04:49:16,100 --> 04:49:19,601
the thing. So Director Ames, we're

5387
04:49:20,100 --> 04:49:21,100
pretty plugged in there and the

5388
04:49:21,100 --> 04:49:24,100
connection there to jump on VTA, and

5389
04:49:24,100 --> 04:49:26,100
down to the Stadium there. So we can

5390
04:49:26,100 --> 04:49:28,100
reinforce that. I can talk to the head

5391
04:49:28,100 --> 04:49:30,100
of the Host Committee, and see if

5392
04:49:30,100 --> 04:49:32,100
there's an opportunity there. But

5393
04:49:32,100 --> 04:49:33,100
also, then Capitol Corridor; right?

5394
04:49:33,100 --> 04:49:36,100
Comes right down, and makes that

5395
04:49:36,100 --> 04:49:40,100
connection there. And we had at my --

5396
04:49:40,100 --> 04:49:43,100
I shouldn't say my, by I just run it as

5397
04:49:43,100 --> 04:49:46,100
the BART GM, the 9:00 Monday morning

5398
04:49:46,100 --> 04:49:50,201
meeting all the GMs had the Host

5399
04:49:51,100 --> 04:49:54,601
Committee with MTC as well to

5400
04:49:55,100 --> 04:49:59,100
coordinate this stuff and BART is at

5401
04:49:59,100 --> 04:50:01,100
the center of conversation. Whether

5402
04:50:01,100 --> 04:50:04,100
it's the Communications Officer or he

5403
04:50:04,100 --> 04:50:06,100
just left here our Chief transportation

5404
04:50:06,100 --> 04:50:07,100
Officer is at the center of these

5405
04:50:07,100 --> 04:50:09,100
discussions and I can certainly keep

5406
04:50:09,100 --> 04:50:10,100
you posted on that.

5407
04:50:10,100 --> 04:50:13,100
>> Thank you, Bob. I have been trying

5408
04:50:13,100 --> 04:50:17,100
for a couple of years with the Swifties

5409
04:50:17,100 --> 04:50:20,100
and all the events happening at Levi's

5410
04:50:20,100 --> 04:50:21,100
Stadium. We really need to get our

5411
04:50:21,100 --> 04:50:24,100
logo on there, so people can see that

5412
04:50:24,100 --> 04:50:25,100
we're connected all around the bay.

5413
04:50:25,100 --> 04:50:28,100
Thank you so much. Hopefully you can

5414
04:50:28,100 --> 04:50:31,601
put pressure on them. Thank you.

5415
04:50:32,100 --> 04:50:33,100
>> Director Foley and Director Raburn.

5416
04:50:33,100 --> 04:50:36,100
>> Thank you, just a brief update on

5417
04:50:36,100 --> 04:50:40,100
January 8th I attended the Contra Costa

5418
04:50:40,100 --> 04:50:42,100
Mayors conference. January 13th, I

5419
04:50:42,100 --> 04:50:45,100
attended the Contra Costa County Board

5420
04:50:45,100 --> 04:50:46,100
of Supervisors reorganization event.

5421
04:50:46,100 --> 04:50:49,100
On the 20th, earlier this week, I made

5422
04:50:49,100 --> 04:50:51,401
a Role-in-the-Region presentation to

5423
04:50:52,100 --> 04:50:54,100
East Contra Costa Democratic club and I

5424
04:50:54,100 --> 04:50:55,100
want to thank Director Rinn for

5425
04:50:55,100 --> 04:50:59,100
covering for me last night at the

5426
04:50:59,100 --> 04:51:01,100
Contra Costa Transportation Authority.

5427
04:51:01,100 --> 04:51:05,201
I was attending my East Bay MUD

5428
04:51:07,100 --> 04:51:09,401
retirement party. Thank you.

5429
04:51:10,100 --> 04:51:13,100
>> That came out of nowhere --

5430
04:51:13,100 --> 04:51:15,100
--

5431
04:51:15,100 --> 04:51:18,100
[laughter ]Did he just drop he is

5432
04:51:18,100 --> 04:51:19,100
retiring?

5433
04:51:19,100 --> 04:51:21,100
[ APPLAUSE ]

5434
04:51:22,100 --> 04:51:25,100
If we would have none, we would have

5435
04:51:25,100 --> 04:51:28,601
made sure that Franklin brought some

5436
04:51:29,100 --> 04:51:30,100
cupcakes. Congratulations -- how many

5437
04:51:30,100 --> 04:51:31,100
years? How many years?

5438
04:51:31,100 --> 04:51:35,100
>> I was in my 33rd year of employment

5439
04:51:35,100 --> 04:51:38,100
with East Bay MUD. I'm vacationing out

5440
04:51:38,100 --> 04:51:42,801
to April Fools, which is my official day

5441
04:51:43,100 --> 04:51:44,100
off the books.

5442
04:51:44,100 --> 04:51:46,100
>> Congratulations!

5443
04:51:46,100 --> 04:51:48,100
>> Thank you, Jerry.

5444
04:51:53,100 --> 04:51:54,100
Congratulations for your years of

5445
04:51:54,100 --> 04:51:55,100
service, 33.

5446
04:51:55,100 --> 04:51:56,100
>> Director?

5447
04:51:56,100 --> 04:51:59,100
>> I'm amazed you are still a young

5448
04:51:59,100 --> 04:52:03,201
man. On January 10th, I attended Mayor

5449
04:52:09,100 --> 04:52:10,100
Stephen Cassidy's service and the

5450
04:52:10,100 --> 04:52:13,100
community came out enforce. This was a

5451
04:52:13,100 --> 04:52:16,100
large group. On the 12th, I usually

5452
04:52:16,100 --> 04:52:20,100
don't report that I attend our Advisory

5453
04:52:20,100 --> 04:52:23,601
Committee meetings, but I attended the

5454
04:52:25,100 --> 04:52:28,601
BPCRB meeting which was attended by

5455
04:52:31,100 --> 04:52:34,601
Cephus and Wanda Johnson who invited

5456
04:52:35,100 --> 04:52:38,100
people to participate in the

5457
04:52:41,100 --> 04:52:43,100
Happy Birthday Oscar Grant, which

5458
04:52:43,100 --> 04:52:46,601
will be an ongoing event. Cephus

5459
04:52:48,100 --> 04:52:50,100
inquired about a collaborative report

5460
04:52:50,100 --> 04:52:52,100
underway between the State Department

5461
04:52:52,100 --> 04:52:54,100
of Justice and the Bart Police

5462
04:52:54,100 --> 04:52:56,100
Department resulting from Senate Bill

5463
04:52:56,100 --> 04:52:59,100
2, which was passed in 2023. Further

5464
04:53:01,100 --> 04:53:04,100
information about the status of this

5465
04:53:04,100 --> 04:53:07,100
report is probably available from

5466
04:53:07,100 --> 04:53:10,601
either our Office of Inspector General,

5467
04:53:13,100 --> 04:53:16,100
pardon me, our Police Inspector or

5468
04:53:16,100 --> 04:53:20,100
Chief Franklin. That is all. Thank you

5469
04:53:20,100 --> 04:53:21,100
.

5470
04:53:21,100 --> 04:53:23,100
>> Director Li, and Director Ghosh.

5471
04:53:23,100 --> 04:53:27,100
>> I just want to note one thing, I

5472
04:53:27,100 --> 04:53:29,100
want to shout-out our General Manager,

5473
04:53:29,100 --> 04:53:32,601
and Chief Franklin for attending the

5474
04:53:34,100 --> 04:53:36,100
Mayor State of City, which I also

5475
04:53:36,100 --> 04:53:39,601
attended last Thursday, the 15th. It

5476
04:53:40,100 --> 04:53:43,601
was a very, very well-attended event.

5477
04:53:44,100 --> 04:53:46,100
I appreciated it. It was right in my

5478
04:53:46,100 --> 04:53:49,601
own neighborhood of the inner Richmond

5479
04:53:50,100 --> 04:53:52,100
at Rossi playground. The one thing I

5480
04:53:52,100 --> 04:53:56,100
will note is that Mayor Lurie did

5481
04:53:56,100 --> 04:53:58,100
express his commitment to supporting

5482
04:53:58,100 --> 04:54:00,100
public transit, particularly Muni and

5483
04:54:00,100 --> 04:54:04,100
BART, and I gave a little cheer for

5484
04:54:04,100 --> 04:54:07,100
BART. Maybe inappropriate, but hey.

5485
04:54:07,100 --> 04:54:09,100
So yeah, just want to thank BART for

5486
04:54:09,100 --> 04:54:11,401
showing up for that.

5487
04:54:14,100 --> 04:54:15,100
>> Director Ghosh.

5488
04:54:15,100 --> 04:54:18,100
>> Just briefly wanted to shout-out

5489
04:54:20,100 --> 04:54:23,601
the Berkeley MLK breakfast that I

5490
04:54:26,100 --> 04:54:29,100
attended on Monday, January 19th. It

5491
04:54:29,100 --> 04:54:33,100
was one of the first events I attended

5492
04:54:33,100 --> 04:54:35,100
after I got elected and it's always

5493
04:54:35,100 --> 04:54:38,100
been a great way to start the year and

5494
04:54:38,100 --> 04:54:40,100
be grounded in those values, especially

5495
04:54:40,100 --> 04:54:42,100
with the times that we're in. Thank

5496
04:54:42,100 --> 04:54:44,100
you.

5497
04:54:44,100 --> 04:54:45,100
>> Thank you. And VP Wright.

5498
04:54:45,100 --> 04:54:47,100
>> Thank you. I just wanted to take

5499
04:54:47,100 --> 04:54:50,100
the opportunity to again thank our

5500
04:54:50,100 --> 04:54:51,100
Staff, who made possible the incredible

5501
04:54:51,100 --> 04:54:53,100
event that we had at our 16th Street

5502
04:54:53,100 --> 04:54:57,201
Plaza in the mission on January 10th.

5503
04:54:59,100 --> 04:55:02,100
I think it was a really big success and

5504
04:55:02,100 --> 04:55:04,100
in my hopes of a preview of more

5505
04:55:04,100 --> 04:55:05,100
collaborations to come, with the City

5506
04:55:05,100 --> 04:55:08,100
and County of San Francisco, the

5507
04:55:08,100 --> 04:55:09,100
conversations are actively underway.

5508
04:55:09,100 --> 04:55:12,100
When I went, the first thing that the

5509
04:55:12,100 --> 04:55:15,100
vendors asked me was when can we do

5510
04:55:15,100 --> 04:55:17,100
this again? So we're actively in

5511
04:55:17,100 --> 04:55:19,100
discussion with our City partners and

5512
04:55:19,100 --> 04:55:22,100
hopefully, I'll have more to share

5513
04:55:22,100 --> 04:55:24,100
soon. Thank you.

5514
04:55:24,100 --> 04:55:27,601
>> We have one public speaker. Jerry

5515
04:55:35,100 --> 04:55:37,100
Grace. Jerry.

5516
04:55:39,100 --> 04:55:42,601
>> Hello everybody. Last year, two of

5517
04:55:44,100 --> 04:55:48,100
you guys was doing last year -- and you

5518
04:55:48,100 --> 04:55:52,801
know who you are. You were there once

5519
04:55:55,100 --> 04:55:59,100
before. This year, ADA has a meeting

5520
04:55:59,100 --> 04:56:03,201
again for Robert Orr. Will you please

5521
04:56:07,100 --> 04:56:11,801
help me say the name? The thing again?

5522
04:56:14,100 --> 04:56:15,100
>> The name?

5523
04:56:15,100 --> 04:56:17,100
>> Yes.

5524
04:56:17,100 --> 04:56:20,100
That is what I tried to point out. Two

5525
04:56:20,100 --> 04:56:24,100
of them were there once before and

5526
04:56:24,100 --> 04:56:26,100
others were not there before. That is

5527
04:56:26,100 --> 04:56:30,100
what I'm trying to say about the

5528
04:56:30,100 --> 04:56:33,601
meeting today after this one. Thank

5529
04:56:35,100 --> 04:56:38,601
you. 3:00, please join us this time,

5530
04:56:40,100 --> 04:56:43,100
this year 226. And I do not know who

5531
04:56:43,100 --> 04:56:46,100
you are. -- a lot of them do not know

5532
04:56:46,100 --> 04:56:48,100
who you are. Please join us at 3:00

5533
04:56:48,100 --> 04:56:50,100
this afternoon. We want to see you

5534
04:56:50,100 --> 04:56:53,100
there at our -- two of you guy were

5535
04:56:53,100 --> 04:56:56,601
there before, and some other people

5536
04:56:57,100 --> 04:56:59,100
did not. Please, please come, join us,

5537
04:56:59,100 --> 04:57:02,100
have fun and a good time. Thank you.

5538
04:57:02,100 --> 04:57:03,100
>> In this room?

5539
04:57:03,100 --> 04:57:05,401
>> No, across the hall.

5540
04:57:07,100 --> 04:57:11,100
>> Thank you. Our item B, any Roll

5541
04:57:11,100 --> 04:57:13,100
Call for Introductions? Not seeing

5542
04:57:13,100 --> 04:57:16,100
any, we do not have any in memoriam.

5543
04:57:16,100 --> 04:57:18,100
We'll go ahead and go to Closed

5544
04:57:18,100 --> 04:57:22,801
Session, which is item 10. I do need to

5545
04:57:24,100 --> 04:57:26,100
read that there was -- we'll now enter

5546
04:57:26,100 --> 04:57:29,100
into Closed Session under item 10.A of

5547
04:57:29,100 --> 04:57:33,100
the agenda, please note the agenda had

5548
04:57:33,100 --> 04:57:36,100
an error and identified as wrong court

5549
04:57:36,100 --> 04:57:38,100
Case No., the court -- the correct

5550
04:57:38,100 --> 04:57:40,100
court and Case No. in San Francisco's

5551
04:57:40,100 --> 04:57:42,401
Superior Court Case No.

5552
04:57:43,000 --> 04:57:46,600
CGC24-613504. We'll reconvene in Open

5553
04:57:50,100 --> 04:57:51,100
Session upon conclusion of the Closed

5554
04:57:51,100 --> 04:57:53,100
Session item.

5555
05:33:29,100 --> 05:33:31,100
[ GAVEL ]

5556
05:33:37,000 --> 05:33:38,100
We're back out of Closed Session and

5557
05:33:38,100 --> 05:33:40,100
there's nothing to report. And we'll

5558
05:33:40,100 --> 05:33:42,100
adjourn this meeting at 2:05.

5559
05:33:42,100 --> 05:33:44,100
[ GAVEL ]