Traffic Forecasting Methodology Sample Clauses

Traffic Forecasting Methodology. Objective To develop a uniform approach to developing traffic forecasts for use in the environmental analysis that includes addressing the impacts of the implementation of tolls. Given the complexity of localized issues, a multiple step process will be needed using the statewide model for regional traffic shifts and for areas outside of the local MPO model areas. For areas where local models are available, the statewide information will be used in conjunction with the MPO models to develop the appropriate forecasts. The proposed methodology must address the full implementation in the horizon year but also must address staged implementation. It must also be able to address the impacts of changes to toll rates. Activity The CONSULTANT will perform the following activities: • Review previous interstate tolling environmental efforts (local and other states) and summarize methods/outcomes reflecting on any lessons learned and best practices related to traffic forecasting methodologies. • Develop draft traffic forecasting requirements for both corridor and off-corridor locations. This should address all needs for NEPA and design. They should outline time periods, level of detail (segment, ramp, intersection), with and without tolling, ranges of toll rates, differentiation between trucks and cars. • Review draft traffic forecasting requirements with appropriate agencies. This effort includes meetings with the MPO’s to discuss their models and share the forecasting methodologies with them. (Assumes up to 10 meetings) • Based on input a final set of traffic forecasting requirements will be developed • Review available models/tools/data to determine the suitability for producing traffic assignments in tolled conditions and its ability to work with the statewide model. Key details to be reviewed model temporality, value of time, traffic data accuracy, network and zonal details (existing and future), assignment algorithms used, current and forecasted socio-economic data used and other critical aspects of the model. (assumes up to 14 MPO models, the statewide model and other national tools & data sets) • A draft project-level traffic forecasting framework will be developed that details how to stitch the models together into a smooth forecasting tool capable of developing traffic forecasts for different toll rates, different implementation years, and multiple scenarios. The model framework will essentially a GIS coverage that utilizes the inputs and outputs from the ava...
Sample 1
AutoNDA by SimpleDocs

Related to Traffic Forecasting Methodology

  • TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Service Providing Methodology 1.3.1 Party A and Party B agree that during the term of this Agreement, where necessary, Party B may enter into further service agreements with Party A or any other party designated by Party A, which shall provide the specific contents, manner, personnel, and fees for the specific services. 1.3.2 To fulfill this Agreement, Party A and Party B agree that during the term of this Agreement, where necessary, Party B may enter into equipment or property leases with Party A or any other party designated by Party A which shall permit Party B to use Party A’s relevant equipment or property based on the needs of the business of Party B. 1.3.3 Party B hereby grants to Party A an irrevocable and exclusive option to purchase from Party B, at Party A’s sole discretion, any or all of the assets and business of Party B, to the extent permitted under PRC law, at the lowest purchase price permitted by PRC law. The Parties shall then enter into a separate assets or business transfer agreement, specifying the terms and conditions of the transfer of the assets.

  • Rolling Forecasts No later than ten (10) days of the Commencement Date, the Client shall provide Patheon with a written non-binding 18 month forecast of the volume of the Drug Product that the Client then anticipates will be required to be produced and delivered to the Client during each month of that 18 month period. Such forecast will be updated by the Client monthly on a rolling 18 month basis and updated forthwith upon the Client determining that the volumes contemplated in the most recent of such forecasts has changed by more than 20%. The most recent 18 month forecast shall prevail.

  • Methodology 1. The price at which the Assuming Institution sells or disposes of Qualified Financial Contracts will be deemed to be the fair market value of such contracts, if such sale or disposition occurs at prevailing market rates within a predefined timetable as agreed upon by the Assuming Institution and the Receiver. 2. In valuing all other Qualified Financial Contracts, the following principles will apply:

  • Rolling Forecast (i) On or before the fifteenth (15th) calendar day of each month during the Term (as defined in Section 6.1 herein), Buyer shall provide Seller with an updated eighteen (18) month forecast of the Products to be manufactured and supplied (each a “Forecast”) for the eighteen (18) month period beginning on the first day of the following calendar month. The first two months of each Forecast will restate the balance of the Firm Order period of the prior Forecast, and the first three (3) months of the Forecast shall constitute the new Firm Order period for which Buyer is obligated to purchase and take delivery of the forecasted Product, and the supply required for the last month of such new Firm Order period shall not be more than one (1) full Standard Manufacturing Batch from the quantity specified for such month in the previous Forecast (or Initial Forecast, as the case may be). Except as provided in Section 2.2(a), Purchase Orders setting forth Buyer’s monthly Product requirements will be issued for the last month of each Firm Order period no later than the fifteenth calendar day of the first month of each Firm Order period, and such Purchase Order will be in agreement with the Firm Order period of the Forecast. If a Purchase Order for any month is not submitted by such deadline, Buyer shall be deemed to have submitted a Purchase Order for such month for the amount of Product set forth in Buyer’s Forecast for such month. (ii) The remainder of the Forecast shall set forth Buyer’s best estimate of its Product production and supply requirements for the remainder of the Forecast period. Each portion of such Forecast that is not deemed to be a Firm Order shall not be deemed to create a binding obligation on Buyer to purchase and take delivery of Products nor a binding obligation of Seller to deliver Products, except as otherwise provided in Section 2.2(f). (iii) Forecast and Purchase Orders shall be in full Standard Manufacturing Batches. If a Product has multiple SKUs, then the composite of the forecasted SKU must equate to the Standard Manufacturing Batch. One Purchase Order shall be issued for each full Standard Manufacturing Batch of Product and contain the required information set forth in Section 2.2(e) hereof.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Usage Measurement Usage measurement for calls shall begin when answer supervision or equivalent Signaling System 7 (SS7) message is received from the terminating office and shall end at the time of call disconnect by the calling or called subscriber, whichever occurs first.

  • Long Term Cost Evaluation Criterion 4. READ CAREFULLY and see in the RFP document under "Proposal Scoring and Evaluation". Points will be assigned to this criterion based on your answer to this Attribute. Points are awarded if you agree not increase your catalog prices (as defined herein) more than X% annually over the previous year for the life of the contract, unless an exigent circumstance exists in the marketplace and the excess price increase which exceeds X% annually is supported by documentation provided by you and your suppliers and shared with TIPS, if requested. If you agree NOT to increase prices more than 5%, except when justified by supporting documentation, you are awarded 10 points; if 6% to 14%, except when justified by supporting documentation, you receive 1 to 9 points incrementally. Price increases 14% or greater, except when justified by supporting documentation, receive 0 points. increases will be 5% or less annually per question Required Confidentiality Claim Form This completed form is required by TIPS. By submitting a response to this solicitation you agree to download from the “Attachments” section, complete according to the instructions on the form, then uploading the completed form, with any confidential attachments, if applicable, to the “Response Attachments” section titled “Confidentiality Form” in order to provide to TIPS the completed form titled, “CONFIDENTIALITY CLAIM FORM”. By completing this process, you provide us with the information we require to comply with the open record laws of the State of Texas as they may apply to your proposal submission. If you do not provide the form with your proposal, an award will not be made if your proposal is qualified for an award, until TIPS has an accurate, completed form from you. Read the form carefully before completing and if you have any questions, email Xxxx Xxxxxx at TIPS at xxxx.xxxxxx@xxxx-xxx.xxx If the vendor is awarded a contract with TIPS under this solicitation, the vendor agrees to make any Choice of Law clauses in any contract or agreement entered into between the awarded vendor and with a TIPS member entity to read as follows: "Choice of law shall be the laws of the state where the customer resides" or words to that effect.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

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