Laserfiche WebLink
methodology meeting would assist the applicant and his professional (an engineer or <br />architect) in obtaining preliminary information allowing discussion with staff in a <br />knowledgeable fashion. He commented it would rely upon the applicant to understand <br />the magnitude of issues. <br />Mr. Paladin concurred a rough outline of the traffic due diligence period as far as <br />concurrency, trips, appropriate intersections, etc., would provide a status of the plan. <br />Chairperson Robinson said if the Code was changed to resubmittal time, there <br />would be nothing to preclude the applicant from providing the Traffic Study early, at the <br />TRC meeting, as a part of the due diligence. She agreed the engineer should have a <br />good concept of whether or not the Traffic Study would "sink the ship" before doing the <br />project. <br />Mr. McCoy, said the methodology meeting with the Traffic Division would provide <br />where and what the "skeletons" were, prior to refining project site plan design. <br />Mr. McCoy stated in support of Mr. Schulke's idea of the initial submittal of the <br />Traffic Study moved to the resubmittal of the formal Traffic Impact Statement, the <br />developer would want the verification of the methodology meeting prior to the TRC <br />meeting submittal. He continued this would allow Traffic Division to have an idea of <br />what to expect, methodology -wise, because approaching the approval stage, the Traffic <br />Division was required to sign off on the Traffic Study and approve the site plan, closing <br />the gap and getting to the end result quicker. <br />Mr. Szpyrka summarized there would be the pre -app conference to ensure the <br />developer could do what they wish to do, then there would be a methodology meeting <br />with the Traffic Division, having the information of what the developer thought could be <br />accomplished, then the TRC meeting, allowing the comments to go back to the <br />developer, then the full-blown Traffic Study with the resubmittal. <br />Mr. Greg Burke, Member at Large representative shared he thought it was a <br />good idea for staff to see the project upfront in the planning stage and to ensure good <br />understanding by inviting staff to be partners in the design of the project, which would <br />save time. <br />ON MOTION BY Mr. Paladin, SECONDED BY Mr. <br />Mechling, to shift the time frame where the Traffic <br />Report was required to resubmittal. <br />UNDER DISCUSSION, Mr. Burke inquired about a timeline for the approval of <br />the Traffic Study; depending upon the consultant providing the correct information. <br />Mr. Szpyrka informed the committee, according to the current Code, the Public <br />Works Director has 15 days in which to get the Traffic Study reviewed and back to the <br />developer, and that time frame runs concurrently with the TRC, so when the TRC plan <br />5 <br />C:\Users\sjohnson\AppData\Local\Microsoft\Windows\INetCache\Content.Outlook\SEU7ML71\11.8.17 DRPP Minutes.doc 63 <br />