Laserfiche WebLink
number, someone might come to us and give us a small number and then we're still <br />coming back to ITE. That's our standard. The infrastructure that we anticipated in the <br />General Plan uses those numbers as well based on the different office categories, and <br />that's how we calculate our traffic impact fees so we look at where General Plan <br />buildout will take us, and those improvements then go into a bucket, a big list. We tally it <br />up and then assess a fee based on that and the Council has the ability to adjust that <br />before they adopt it. <br />So we're in the process of updating our fees at this point in time and we have a long list <br />of traffic improvements we know need to be paid for and we're looking at them with a <br />pretty consistent methodology not one by one. I don't have the number for you. There is <br />a development agreement though for this project and that's not being opened up with <br />this. Because it's a Major Modification but it's actually less square footage, I believe the <br />traffic impact fees are actually locked in based on the prior development. This is an <br />interesting circumstance because it's considered a Major Modification but there are a <br />number of other agreements already in place for this project. <br />Commissioner O'Connor: Gerry, correct me if I'm wrong too, but the analysis here on <br />trips really doesn't take into account their proximity to BART, does it? I mean, our code <br />is by building size and it doesn't matter if it's next to BART or if it's someplace else. <br />Beaudin: That's right and we typically try and adjust for that with our analysis, but for <br />traffic impact fee calculation purposes and things like that, we're using our standard <br />methodology. <br />Commissioner Nagler: As I understand the number of parking spaces that are being <br />planned there are almost one -to -one as one form of relationship between the number of <br />employees that Workday anticipates in these buildings and the number of parking <br />spaces being created, right? So in other words, the plan doesn't anticipate people <br />using public transportation and bicycling and walking and carpooling and whatever else, <br />right? <br />Otto: The parking for the site is using our normal code as the guide which is based on <br />square footage and not employees, which is 1 per 300, so that is what the project is <br />providing. It provides 304 square feet, but when proposing that, we did factor in the <br />proximity to the BART station, the bus stop, and all the traffic demand program <br />measures that the applicant is going to implement and we were comfortable with the <br />parking ratio of 1:304. <br />Commissioner Nagler: Just in the raw numbers of it, the number of employees' Workday <br />projects having on the site when the project is completed as compared to the actual <br />number of parking spaces that will exist. It's almost a one -to -one relationship, isn't it? <br />Otto: Workday, in their building can anticipate potentially up to 2200 employees but we <br />have five other buildings that are also using the overall parking that we're talking <br />about —the roughly 3800 spaces that are being proposed. <br />Commissioner Nagler: So once this project is built and all of the buildings are occupied, <br />using the company's numbers because you can't know, right, so just taking their <br />PLANNING COMMISSION MINUTES, April 13, 2016 Page 24 of 33 <br />