Traffic Assessment and Management Sample Clauses

Traffic Assessment and Management. (a) One year after completion and occupancy of Phase 1 and again one year after the issuance of the final Certificate of Occupancy for the Project, the Developer shall undertake trip counts to assess daily project traffic. “Phase I” shall mean either the issuance of final certificates of occupancy for the portion of the Development on Lots 2 – 6, as reflected in the Vesting Tentative Tract Map, or the issuance of final certificates of occupancy for the portion of the Development on Lots 8 – 10, as reflected in the Vesting Tentative Tract Map, whichever comes first. Such counts shall be taken mid-week over a two-week period in accordance with standard traffic engineering practice. The counts shall assess whether the Project's daily traffic generation exceeds a trip cap based upon standard traffic engineering trip assessment for the 790-unit project. Results will be provided to the City and presented by City staff to City Council at a public meeting. In the unlikely event Project traffic generation exceeds the trip cap, the Project shall implement traffic demand management ("TDM") efforts, in consultation with the City as to the specific measures, in an attempt to reduce Project traffic below the trip cap.
Sample 1
AutoNDA by SimpleDocs
Traffic Assessment and Management. (a) One year after completion and occupancy of Phase 1 and again one year after the issuance of the final Certificate of Occupancy for the Project, the Developer shall undertake individual Project trip counts to assess daily Project traffic. “Phase I” shall mean either the issuance of final certificates of occupancy for the portion of the Development on Lots 2 –6, as reflected in the Vesting Tentative Tract Map, or the issuance of final certificates of occupancy for the portion of the Development on Lots 8 – 10, as reflected in the Vesting Tentative Tract Map, whichever comes first. Such counts shall be taken mid-week over a two-week period in accordance with standard traffic engineering practice, with all costs associated with traffic counts, including preparation of a report detailing the counts, paid for by Developer. The counts shall assess whether the Project's daily traffic generation exceeds a trip cap based upon standard traffic engineering trip assessment for the number of units in each Phase of the Project, in accordance with the total trips estimated to be generated by a 790-unit project. . Results will be provided to the City and presented by City staff to City Council at a public meeting. In the event Project traffic generation exceeds the trip cap, the Project shall implement traffic demand management ("TDM") efforts, in consultation with the City as to the specific measures, in an attempt to reduce Project traffic below the trip cap.
Sample 1

Related to Traffic Assessment and Management

  • RECORDS MANAGEMENT AND MAINTENANCE CONTRACTOR, its officers, agents, employees and subcontractors shall, throughout the term 12 of this Agreement, prepare, maintain and manage records appropriate to the services provided and in 13 accordance with this Agreement and all applicable requirements.

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!