{"component": "clause", "props": {"groups": [{"size": 21, "snippet": "The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TPP traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP\u2019s comments.", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "pavement-design", "type": "clause", "offset": [80, 95]}, {"key": "traffic-analysis", "type": "clause", "offset": [151, 167]}, {"key": "with-state", "type": "clause", "offset": [184, 194]}, {"key": "traffic-projections", "type": "clause", "offset": [256, 275]}, {"key": "environmental-analysis", "type": "definition", "offset": [309, 331]}, {"key": "traffic-forecasts", "type": "clause", "offset": [360, 377]}, {"key": "main-lanes", "type": "clause", "offset": [386, 396]}, {"key": "cross-streets", "type": "clause", "offset": [405, 418]}, {"key": "frontage-roads", "type": "clause", "offset": [453, 467]}, {"key": "build-alternatives", "type": "clause", "offset": [485, 503]}, {"key": "representations-of-the", "type": "clause", "offset": [545, 567]}, {"key": "design-schematic", "type": "clause", "offset": [646, 662]}, {"key": "environmental-document", "type": "definition", "offset": [667, 689]}, {"key": "based-on", "type": "clause", "offset": [809, 817]}, {"key": "information-provided", "type": "clause", "offset": [822, 842]}, {"key": "proposed-methodology", "type": "clause", "offset": [910, 930]}, {"key": "the-state", "type": "clause", "offset": [936, 945]}, {"key": "review-and-approval", "type": "clause", "offset": [1065, 1084]}], "samples": [{"hash": "9Obzopf1Kp5", "uri": "/contracts/9Obzopf1Kp5#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 22.6960983276, "published": true}, {"hash": "jaCQJuwtqJM", "uri": "/contracts/jaCQJuwtqJM#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 22.6659812927, "published": true}, {"hash": "dpUEu2Ew8ds", "uri": "/contracts/dpUEu2Ew8ds#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 22.6454486847, "published": true}], "hash": "cae62b8cb3c4da0b77faa98949ae4495", "id": 1}, {"size": 3, "snippet": "The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP\u2019s comments. DocuSign Envelope ID: 81680129-218F-4A62-86EE-68C3C135A630\ni. Financial Plan and Project Management Plan The Engineer shall prepare a Financial Plan (FP) and Project Management Plan (PMP) in accordance with the most recent FHWA Financial Plan Guidance, for submission by the State to the FHWA Division Office for review and approval. The purpose of the FP is to document the project cost estimate and revenue structure and provide reasonable assurance that sufficient financial resources shall be available to implement and complete the project as planned. The FP shall cover topics such as the project cost estimate, revenue structure, funding resources, project implementation over time based on the available financial resources, and the cost and revenue assumptions used in development.\na. The initial FP shall consist of at least five main sections including: \u25aa Cost Estimate. \u25aa Implementation Plan. \u25aa Financing and Revenues. \u25aa Cash Flow. \u25aa Risk Identification and Mitigation Factors.\nb. The Engineer shall prepare for and attend a cost estimate review (CER) workshop with the State and the FHWA to develop and review information for inclusion in the FP such as cost estimation procedures and tools, identifying funding sources and revenues, and project implementation schedules. In preparation for the CER, the Engineer shall conduct a risk analysis assessment, provide cost spreadsheets and models for input into the FHWA\u2019s probability modeling software, review and provide comments on the CER summary report, and update cost information in the initial FP to reflect confidence limits established during the CER.\nc. The Engineer shall provide annual updates (AUs) to the Initial FP reflecting changes in project finances and funding resources. Each update shall include revisions to the five main sections mentioned above as well as discussions of significant cost or revenue changes, comparisons to previous plan estimates, and explanations of mitigating actions taken to adjust for deviations.\nd. The Engineer shall submit the PMP, FP and FP AUs to the State for review and comment. For scoping purposes, it is assumed that the initial drafts of the FP and FP AUs shall be reviewed concurrently by the District, and the State\u2019s Design and Finance Divisions. The Engineer shall address the State\u2019s comments and prepare a revised draft for review by the FHWA. The Engineer shall address FHWA comments and prepare the DocuSign Envelope ID: 81680129-218F-4A62-86EE-68C3C135A630 final FP (up to three revision cycles from the State and FHWA) for the State to submit to the FHWA for approval. To document each revision cycle, the Engineer shall develop comment response forms that includes the comments, comment numbers, page and line numbers of draft where comments originated, page and line numbers where revisions can be located, and the responses.", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "pavement-design", "type": "clause", "offset": [80, 95]}, {"key": "traffic-analysis", "type": "clause", "offset": [151, 167]}, {"key": "with-state", "type": "clause", "offset": [184, 194]}, {"key": "traffic-projections", "type": "clause", "offset": [256, 275]}, {"key": "environmental-analysis", "type": "definition", "offset": [309, 331]}, {"key": "traffic-forecasts", "type": "clause", "offset": [360, 377]}, {"key": "main-lanes", "type": "clause", "offset": [386, 396]}, {"key": "cross-streets", "type": "clause", "offset": [405, 418]}, {"key": "frontage-roads", "type": "clause", "offset": [453, 467]}, {"key": "build-alternatives", "type": "clause", "offset": [485, 503]}, {"key": "representations-of-the", "type": "clause", "offset": [545, 567]}, {"key": "design-schematic", "type": "clause", "offset": [646, 662]}, {"key": "environmental-document", "type": "definition", "offset": [667, 689]}, {"key": "based-on", "type": "clause", "offset": [809, 817]}, {"key": "information-provided", "type": "clause", "offset": [822, 842]}, {"key": "proposed-methodology", "type": "clause", "offset": [906, 926]}, {"key": "review-and-approval", "type": "clause", "offset": [1061, 1080]}, {"key": "docusign-envelope", "type": "definition", "offset": [1156, 1173]}, {"key": "financial-plan-and-project-management-plan", "type": "clause", "offset": [1218, 1260]}, {"key": "in-accordance-with", "type": "clause", "offset": [1344, 1362]}, {"key": "most-recent", "type": "definition", "offset": [1367, 1378]}, {"key": "by-the-state", "type": "clause", "offset": [1424, 1436]}, {"key": "fhwa-division-office", "type": "definition", "offset": [1444, 1464]}, {"key": "purpose-of-the", "type": "clause", "offset": [1494, 1508]}, {"key": "project-cost-estimate", "type": "clause", "offset": [1531, 1552]}, {"key": "reasonable-assurance", "type": "clause", "offset": [1587, 1607]}, {"key": "sufficient-financial-resources", "type": "clause", "offset": [1613, 1643]}, {"key": "available-to", "type": "definition", "offset": [1653, 1665]}, {"key": "complete-the-project", "type": "definition", "offset": [1680, 1700]}, {"key": "funding-resources", "type": "clause", "offset": [1793, 1810]}, {"key": "project-implementation", "type": "clause", "offset": [1812, 1834]}, {"key": "over-time", "type": "clause", "offset": [1835, 1844]}, {"key": "cost-and-revenue", "type": "clause", "offset": [1897, 1913]}, {"key": "in-development", "type": "definition", "offset": [1931, 1945]}, {"key": "consist-of", "type": "clause", "offset": [1971, 1981]}, {"key": "implementation-plan", "type": "clause", "offset": [2040, 2059]}, {"key": "cash-flow", "type": "definition", "offset": [2089, 2098]}, {"key": "risk-identification-and-mitigation-factors", "type": "clause", "offset": [2102, 2144]}, {"key": "to-develop", "type": "definition", "offset": [2257, 2267]}, {"key": "and-review", "type": "clause", "offset": [2268, 2278]}, {"key": "information-for-inclusion", "type": "clause", "offset": [2279, 2304]}, {"key": "cost-estimation", "type": "definition", "offset": [2323, 2338]}, {"key": "and-tools", "type": "clause", "offset": [2350, 2359]}, {"key": "funding-sources", "type": "clause", "offset": [2373, 2388]}, {"key": "preparation-for", "type": "clause", "offset": [2444, 2459]}, {"key": "risk-analysis", "type": "clause", "offset": [2498, 2511]}, {"key": "modeling-software", "type": "clause", "offset": [2599, 2616]}, {"key": "summary-report", "type": "definition", "offset": [2657, 2671]}, {"key": "cost-information", "type": "clause", "offset": [2684, 2700]}, {"key": "annual-updates", "type": "clause", "offset": [2806, 2820]}, {"key": "changes-in-project", "type": "clause", "offset": [2856, 2874]}, {"key": "and-funding", "type": "clause", "offset": [2884, 2895]}, {"key": "previous-plan", "type": "definition", "offset": [3063, 3076]}, {"key": "actions-taken", "type": "clause", "offset": [3119, 3132]}, {"key": "review-and-comment", "type": "clause", "offset": [3228, 3246]}, {"key": "by-the-district", "type": "clause", "offset": [3360, 3375]}, {"key": "for-the-state", "type": "definition", "offset": [3702, 3715]}, {"key": "submit-to", "type": "definition", "offset": [3719, 3728]}, {"key": "for-approval", "type": "definition", "offset": [3738, 3750]}], "samples": [{"hash": "4A5pq53LW3e", "uri": "/contracts/4A5pq53LW3e#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 25.0054759979, "published": true}], "hash": "48ee19901f7c342c2a185105d4be5ee7", "id": 2}, {"size": 2, "snippet": "The Engineer shall develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis in coordination with State Transportation and Programming Division (TPP). The developed traffic projections must be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the main lanes, ramps, cross streets, interchanges, intersections, and frontage roads for no-build and build alternatives. These projections must include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TPP for review and approval, and the Engineer will revise the traffic volumes based on TPP\u2019s comments. The Engineer shall perform travel demand modeling analysis to develop traffic volume forecasts appropriate for the level of traffic operations analysis required based on project needs. The travel demand modeling analysis must be based on regional metropolitan area planning organization travel demand models, statewide area analysis model, and/or other standard practice and guidelines depending on the study area of each project.", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "pavement-design", "type": "clause", "offset": [80, 95]}, {"key": "traffic-analysis", "type": "clause", "offset": [151, 167]}, {"key": "with-state", "type": "clause", "offset": [184, 194]}, {"key": "traffic-projections", "type": "clause", "offset": [256, 275]}, {"key": "environmental-analysis", "type": "definition", "offset": [308, 330]}, {"key": "traffic-forecasts", "type": "clause", "offset": [359, 376]}, {"key": "main-lanes", "type": "clause", "offset": [385, 395]}, {"key": "cross-streets", "type": "clause", "offset": [404, 417]}, {"key": "frontage-roads", "type": "clause", "offset": [452, 466]}, {"key": "build-alternatives", "type": "clause", "offset": [484, 502]}, {"key": "representations-of-the", "type": "clause", "offset": [543, 565]}, {"key": "design-schematic", "type": "clause", "offset": [644, 660]}, {"key": "environmental-document", "type": "definition", "offset": [665, 687]}, {"key": "based-on", "type": "clause", "offset": [807, 815]}, {"key": "information-provided", "type": "clause", "offset": [820, 840]}, {"key": "proposed-methodology", "type": "clause", "offset": [904, 924]}, {"key": "the-state", "type": "clause", "offset": [930, 939]}, {"key": "review-and-approval", "type": "clause", "offset": [1059, 1078]}, {"key": "to-develop", "type": "definition", "offset": [1213, 1223]}, {"key": "volume-forecasts", "type": "clause", "offset": [1232, 1248]}, {"key": "traffic-operations-analysis", "type": "clause", "offset": [1278, 1305]}, {"key": "metropolitan-area", "type": "definition", "offset": [1401, 1418]}, {"key": "standard-practice", "type": "definition", "offset": [1507, 1524]}, {"key": "and-guidelines", "type": "clause", "offset": [1525, 1539]}, {"key": "study-area", "type": "clause", "offset": [1557, 1567]}], "samples": [{"hash": "hBD28oEWEht", "uri": "/contracts/hBD28oEWEht#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 25.470911026, "published": true}], "hash": "b53daf3112b0c47f85ad1580061501de", "id": 3}, {"size": 1, "snippet": "The Engineer shall obtain the base year traffic data from available traffic data available or new counts and develop the opening-year, design-year (opening year +20) and pavement design year (opening year + 30) travel forecasts, and related traffic analysis. The developed traffic projections must be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for the mainlanes, cross streets, and intersections for no-build and build alternatives. These projections must include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the traffic analysis for highway design table. The Engineer shall prepare a traffic projections methodology memo, based on the information provided in the traffic analysis package. The Engineer shall review the proposed methodology with the Owner and refine it based on these discussions. The Engineer shall submit the traffic volumes developed by the Engineer to the Owner for review and approval. The Engineer shall revise the traffic volumes based on the Owner\u2019s comments.", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "base-year", "type": "definition", "offset": [30, 39]}, {"key": "traffic-data", "type": "clause", "offset": [40, 52]}, {"key": "data-available", "type": "clause", "offset": [76, 90]}, {"key": "pavement-design", "type": "clause", "offset": [170, 185]}, {"key": "traffic-analysis", "type": "clause", "offset": [241, 257]}, {"key": "traffic-projections", "type": "clause", "offset": [273, 292]}, {"key": "environmental-analysis", "type": "definition", "offset": [325, 347]}, {"key": "traffic-forecasts", "type": "clause", "offset": [376, 393]}, {"key": "cross-streets", "type": "clause", "offset": [413, 426]}, {"key": "build-alternatives", "type": "clause", "offset": [463, 481]}, {"key": "representations-of-the", "type": "clause", "offset": [522, 544]}, {"key": "design-schematic", "type": "clause", "offset": [623, 639]}, {"key": "environmental-document", "type": "definition", "offset": [644, 666]}, {"key": "based-on", "type": "clause", "offset": [786, 794]}, {"key": "information-provided", "type": "clause", "offset": [799, 819]}, {"key": "proposed-methodology", "type": "clause", "offset": [883, 903]}, {"key": "the-owner", "type": "definition", "offset": [909, 918]}, {"key": "review-and-approval", "type": "clause", "offset": [1050, 1069]}], "samples": [{"hash": "aGynZspSeHV", "uri": "/contracts/aGynZspSeHV#traffic-data-and-projections", "label": "Professional Services Agreement", "score": 32.1925407072, "published": true}], "hash": "0173f19d774d098cd46a3bc24a455e8f", "id": 4}, {"size": 1, "snippet": "The Engineer shall obtain the base year traffic data from new counts and develop the opening- year, design-year (opening year +20), and pavement design year (opening year + 30) travel forecasts for the AM peak hour, PM peak hour, and 24-hour scenarios. The following traffic data locations shall be obtained on a Tuesday, Wednesday, or Thursday: \u2022 4-Hr Turning Movement Counts (7-9 AM and 4-6 PM) o Goforth Road at \u2587\u2587\u2587\u2587\u2587\u2587 Creek Road o Lehman High School Driveway west of Lake Washington Drive o Lehman High School Driveway east of Lake Washington Drive \u2022 24-Hr Bidirectional Tube Count o Bunton Creek Road west of \u2587\u2587\u2587\u2587\u2587\u2587 Circle o \u2587\u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587 east of Twin Estate Drive The Owner shall provide information regarding proposed developments near the study area that have not yet been built. Traffic forecasts shall consider the traffic generated by these proposed developments. The developed traffic projections must be utilized for design analysis. The Engineer shall develop traffic forecasts for the mainlanes and intersections listed in this section for no-build and build alternatives. Traffic projections for the AM peak hour, PM peak hour, and 24-hour shall be presented graphically.", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "base-year", "type": "definition", "offset": [30, 39]}, {"key": "traffic-data", "type": "clause", "offset": [40, 52]}, {"key": "pavement-design", "type": "clause", "offset": [136, 151]}, {"key": "am-peak", "type": "definition", "offset": [202, 209]}, {"key": "pm-peak-hour", "type": "definition", "offset": [216, 228]}, {"key": "high-school", "type": "clause", "offset": [442, 453]}, {"key": "the-owner-shall", "type": "clause", "offset": [668, 683]}, {"key": "information-regarding", "type": "clause", "offset": [692, 713]}, {"key": "study-area", "type": "clause", "offset": [745, 755]}, {"key": "traffic-forecasts", "type": "clause", "offset": [786, 803]}, {"key": "traffic-projections", "type": "clause", "offset": [887, 906]}, {"key": "design-analysis", "type": "clause", "offset": [928, 943]}, {"key": "build-alternatives", "type": "clause", "offset": [1066, 1084]}], "samples": [{"hash": "2qlP2371rOh", "uri": "/contracts/2qlP2371rOh#traffic-data-and-projections", "label": "Professional Services Agreement", "score": 31.0822925568, "published": true}], "hash": "5c4494abfa0e87dabd58e25f396f1a1d", "id": 5}, {"size": 1, "snippet": "The Engineer shall provide additional engineering services to update the development of the opening-year (2020), design-year (2040); and pavement design year (2050) travel forecasts, and related traffic analysis in coordination with the TxDOT Transportation Planning and Programming Division (TP&P) The Engineer shall collect existing turning movement counts (TMC) for the AM and PM peak hours at signalized intersections along LP 1604. Using these TMC\u2019s the Engineer shall develop traffic data projections and modeling of current conditions. The Engineer shall use the developed traffic projections for design and environmental analysis. The Engineer shall develop traffic forecasts for both the no-build alternatives for LP \u2587\u2587\u2587\u2587, \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587, and DocuSign Envelope ID: 1DB60CEF-DAD9-4F47-8AE2-182BB19769B8 interchanges at:\n(1) FM 143 (2) East-West Connectors", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "additional-engineering-services", "type": "clause", "offset": [27, 58]}, {"key": "development-of-the", "type": "clause", "offset": [73, 91]}, {"key": "pavement-design", "type": "clause", "offset": [137, 152]}, {"key": "traffic-analysis", "type": "clause", "offset": [195, 211]}, {"key": "planning-and-programming", "type": "clause", "offset": [258, 282]}, {"key": "peak-hours", "type": "definition", "offset": [383, 393]}, {"key": "signalized-intersections", "type": "clause", "offset": [397, 421]}, {"key": "traffic-data", "type": "clause", "offset": [482, 494]}, {"key": "current-conditions", "type": "definition", "offset": [523, 541]}, {"key": "traffic-projections", "type": "clause", "offset": [580, 599]}, {"key": "environmental-analysis", "type": "definition", "offset": [615, 637]}, {"key": "traffic-forecasts", "type": "clause", "offset": [666, 683]}, {"key": "build-alternatives", "type": "clause", "offset": [700, 718]}, {"key": "docusign-envelope", "type": "definition", "offset": [751, 768]}], "samples": [{"hash": "fO1Eek5MDfE", "uri": "/contracts/fO1Eek5MDfE#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 23.0999317169, "published": true}], "hash": "cee111a3493552aaa59689de627cfed0", "id": 6}, {"size": 1, "snippet": "Obtain from the City the 2017 and design-year (opening year +20) travel forecasts, and related traffic analysis. The developed traffic projections shall be utilized for design and environmental analysis. Obtain traffic counts for side streets for use in determining median openings. Obtain traffic forecasts for the lanes, cross streets, and intersections, for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table.", "snippet_links": [{"key": "obtain-from", "type": "clause", "offset": [0, 11]}, {"key": "the-city", "type": "clause", "offset": [12, 20]}, {"key": "traffic-analysis", "type": "clause", "offset": [95, 111]}, {"key": "traffic-projections", "type": "clause", "offset": [127, 146]}, {"key": "environmental-analysis", "type": "definition", "offset": [180, 202]}, {"key": "traffic-counts", "type": "clause", "offset": [211, 225]}, {"key": "traffic-forecasts", "type": "clause", "offset": [290, 307]}, {"key": "cross-streets", "type": "clause", "offset": [323, 336]}, {"key": "build-alternatives", "type": "clause", "offset": [374, 392]}, {"key": "representations-of-the", "type": "clause", "offset": [434, 456]}, {"key": "design-schematic", "type": "clause", "offset": [535, 551]}, {"key": "environmental-document", "type": "definition", "offset": [556, 578]}], "samples": [{"hash": "hUomahJAfKo", "uri": "/contracts/hUomahJAfKo#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 23.9801502228, "published": true}], "hash": "ca21e77d12f781a477d4681f23a2e0b2", "id": 7}, {"size": 1, "snippet": "The Engineer shall provide existing traffic counts. The Engineer shall perform an Origin/Destination Analysis of the IH35W/IH20 and IH 35W/SH 174 interchanges. The Engineer shall develop base year 2025, interim year, and design year 2045 daily and a.m. and p.m. peak travel forecasts for the No-Build Conditions, corridor alternatives and geometric design schematic of the preferred alternative including all upstream/downstream interchanges within the study area. These traffic forecasts shall be prepared from a corridor model in coordination with North Central Texas Council of DocuSign Envelope ID: B4E47CBB-54AA-4467-B86B-B1C47B94F45E", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "traffic-counts", "type": "clause", "offset": [36, 50]}, {"key": "base-year", "type": "definition", "offset": [187, 196]}, {"key": "design-schematic", "type": "clause", "offset": [349, 365]}, {"key": "preferred-alternative", "type": "clause", "offset": [373, 394]}, {"key": "study-area", "type": "clause", "offset": [453, 463]}, {"key": "traffic-forecasts", "type": "clause", "offset": [471, 488]}, {"key": "be-prepared", "type": "clause", "offset": [495, 506]}, {"key": "central-texas", "type": "clause", "offset": [556, 569]}, {"key": "docusign-envelope", "type": "definition", "offset": [581, 598]}], "samples": [{"hash": "e6KiGbKNqSb", "uri": "/contracts/e6KiGbKNqSb#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 22.8658447266, "published": true}], "hash": "f033b8e6bc34dd889e837a496e65722b", "id": 8}, {"size": 1, "snippet": "The Engineer shall develop the opening-year (2020), design-year (2040) and pavement design year (2050) travel forecasts, and related traffic analysis in coordination with State Transportation Planning and Programming Division (TPP). Existing turning movement counts (TMC\u2019s) will be collected for the AM and PM peak hours at signalized intersections and major cross streets along LP 1604. These TMC\u2019s will be useful in the development of the traffic data projections and modeling of current conditions. The Engineer will collect 24 hour classification volumes at three (3) locations along Loop 1604 to provide daily traffic and percent trucks for existing conditions. The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for LP 1604, interchanges at US 281 and IH 37, and cross streets at FM 3499, Cambellton Road, Priest DocuSign Envelope ID: 719137B1-7E3D-42BC-8A29-9D6AE732CB6A", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "pavement-design", "type": "clause", "offset": [75, 90]}, {"key": "traffic-analysis", "type": "clause", "offset": [133, 149]}, {"key": "with-state", "type": "clause", "offset": [166, 176]}, {"key": "planning-and-programming", "type": "clause", "offset": [192, 216]}, {"key": "peak-hours", "type": "definition", "offset": [310, 320]}, {"key": "signalized-intersections", "type": "clause", "offset": [324, 348]}, {"key": "cross-streets", "type": "clause", "offset": [359, 372]}, {"key": "development-of-the", "type": "clause", "offset": [422, 440]}, {"key": "traffic-data", "type": "clause", "offset": [441, 453]}, {"key": "current-conditions", "type": "definition", "offset": [482, 500]}, {"key": "to-provide", "type": "clause", "offset": [598, 608]}, {"key": "existing-conditions", "type": "definition", "offset": [646, 665]}, {"key": "traffic-projections", "type": "clause", "offset": [681, 700]}, {"key": "environmental-analysis", "type": "definition", "offset": [734, 756]}, {"key": "traffic-forecasts", "type": "clause", "offset": [785, 802]}, {"key": "docusign-envelope", "type": "definition", "offset": [904, 921]}], "samples": [{"hash": "xC5iBouKOd", "uri": "/contracts/xC5iBouKOd#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 22.2169742584, "published": true}], "hash": "7df47954e3d8e5104d4191bbf0ea66ac", "id": 9}, {"size": 1, "snippet": "The Engineer shall develop the opening-year (2020), design-year (2040) and pavement design year (2050) travel forecasts, and related traffic analysis in coordination with State Transportation Planning and Programming Division (TP&P). Existing turning movement counts (TMC\u2019s) will be collected for the AM and PM peak hours at signalized intersections along LP 1604. These TMC\u2019s will be useful in the development of the traffic data projections and modeling of current conditions. The developed traffic projections shall be utilized for design and environmental analysis. The Engineer shall develop traffic forecasts for LP \u2587\u2587\u2587\u2587, \u2587\u2587\u2587\u2587\u2587 \u2587\u2587\u2587\u2587\u2587\u2587\u2587, interchanges at FM 143, East- West Connector (City of San Antonio (COSA), Metropolitan Transportation Plan (MTP)), Union Pacific Railroad (UPRR) /Macdona-Lacoste Road, \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 Road, UPRR/\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 Road and at IH 35, for no-build and build alternatives. These projections shall include graphic representations of the anticipated daily movements along the corridor (suitable for inclusion in the design schematic and environmental document) and the Traffic Analysis for Highway Design table. The Engineer shall prepare Line diagrams of existing and proposed conditions to submit to TP&P for traffic projections. The Engineer shall prepare a Traffic Projections Methodology memo, based on the information provided in the TP&P traffic analysis package. The Engineer shall review the proposed methodology with the State and shall refine it based on these discussions. Traffic volumes developed by the Engineer will be submitted to TP&P for review and approval, and the Engineer will revise the traffic volumes based on TP&P\u2019s comments. DocuSign Envelope ID: ED57FAE2-481A-4535-A126-CE7F0E526760", "snippet_links": [{"key": "the-engineer", "type": "definition", "offset": [0, 12]}, {"key": "pavement-design", "type": "clause", "offset": [75, 90]}, {"key": "traffic-analysis", "type": "clause", "offset": [133, 149]}, {"key": "with-state", "type": "clause", "offset": [166, 176]}, {"key": "planning-and-programming", "type": "clause", "offset": [192, 216]}, {"key": "peak-hours", "type": "definition", "offset": [311, 321]}, {"key": "signalized-intersections", "type": "clause", "offset": [325, 349]}, {"key": "development-of-the", "type": "clause", "offset": [399, 417]}, {"key": "traffic-data", "type": "clause", "offset": [418, 430]}, {"key": "current-conditions", "type": "definition", "offset": [459, 477]}, {"key": "traffic-projections", "type": "clause", "offset": [493, 512]}, {"key": "environmental-analysis", "type": "definition", "offset": [546, 568]}, {"key": "traffic-forecasts", "type": "clause", "offset": [597, 614]}, {"key": "city-of", "type": "clause", "offset": [689, 696]}, {"key": "san-antonio", "type": "definition", "offset": [697, 708]}, {"key": "metropolitan-transportation-plan", "type": "definition", "offset": [717, 749]}, {"key": "union-pacific-railroad", "type": "clause", "offset": [758, 780]}, {"key": "build-alternatives", "type": "clause", "offset": [876, 894]}, {"key": "representations-of-the", "type": "clause", "offset": [936, 958]}, {"key": "design-schematic", "type": "clause", "offset": [1037, 1053]}, {"key": "environmental-document", "type": "definition", "offset": [1058, 1080]}, {"key": "submit-to", "type": "definition", "offset": [1213, 1222]}, {"key": "based-on", "type": "clause", "offset": [1320, 1328]}, {"key": "information-provided", "type": "clause", "offset": [1333, 1353]}, {"key": "proposed-methodology", "type": "clause", "offset": [1422, 1442]}, {"key": "the-state", "type": "clause", "offset": [1448, 1457]}, {"key": "review-and-approval", "type": "clause", "offset": [1578, 1597]}, {"key": "docusign-envelope", "type": "definition", "offset": [1674, 1691]}], "samples": [{"hash": "8vmt7Uu1ecc", "uri": "/contracts/8vmt7Uu1ecc#traffic-data-and-projections", "label": "Contract for Engineering Services", "score": 22.2073917389, "published": true}], "hash": "b2d1400c341fb876bdc64fa7078f97a9", "id": 10}], "next_curs": "CmUSX2oVc35sYXdpbnNpZGVyY29udHJhY3RzckELEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IiV0cmFmZmljLWRhdGEtYW5kLXByb2plY3Rpb25zIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"children": [], "size": 34, "title": "Traffic Data and Projections", "parents": [["pertinent-non-discrimination-authorities", "PERTINENT NON-DISCRIMINATION AUTHORITIES"], ["non-discrimination-provisions", "Non Discrimination Provisions"], ["environmental-terms", "Environmental Terms"], ["boycott-israel", "Boycott Israel"], ["organization-of-design-project-folder-and-files-electronic-project-files", "Organization of Design Project Folder and Files (Electronic Project Files)"]], "id": "traffic-data-and-projections", "related": [["contract-database-metadata-elements", "Contract Database Metadata Elements", "Contract Database Metadata Elements"], ["false-statements-concerning-highway-projects", "FALSE STATEMENTS CONCERNING HIGHWAY PROJECTS", "FALSE STATEMENTS CONCERNING HIGHWAY PROJECTS"], ["course-materials", "Course Materials", "Course Materials"], ["evaluation-software", "Evaluation Software", "Evaluation Software"], ["shop-drawings-product-data-and-samples", "SHOP DRAWINGS, PRODUCT DATA AND SAMPLES", "SHOP DRAWINGS, PRODUCT DATA AND SAMPLES"]], "related_snippets": [], "updated": "2025-07-17T04:25:46+00:00", "also_ask": ["What minimum data sources and methodologies should be mandated for reliable traffic projections?", "How can parties allocate risk if actual traffic deviates significantly from projections?", "What are the most common legal challenges to the enforceability of traffic data clauses in court?", "How do traffic data requirements in this agreement compare to industry standards or similar contracts?", "What negotiation leverage exists around updating or revising traffic projections post-signing?"], "drafting_tip": "Specify data sources and methodologies to ensure reliability; define projection periods to provide clarity; require regular updates to maintain accuracy.", "explanation": "The 'Traffic Data and Projections' clause defines how information regarding current and anticipated traffic volumes is collected, analyzed, and used within the context of an agreement or project. Typically, this clause outlines the methodologies for gathering traffic data, the frequency of data collection, and the standards for projecting future traffic patterns, which may include vehicle counts, peak usage times, or growth estimates. Its core practical function is to ensure that all parties have a clear, data-driven basis for planning, decision-making, and resource allocation, thereby reducing uncertainty and supporting informed infrastructure or operational choices."}, "json": true, "cursor": ""}}