Traffic Operational Analysis Sample Clauses

Traffic Operational Analysis. The Engineer shall perform operational analysis for the existing conditions as well as proposed condition for the segment of IH 40 from West of Xxxxxx Street to West of Eastern Street the Engineer shall perform operational analysis for the existing conditions as well as up to three (3) total geometric alternatives for the ultimate configuration of the project corridor. The following tasks shall be completed for the operational analysis:
Sample 1
AutoNDA by SimpleDocs
Traffic Operational Analysis. 6.1. Perform peak hour traffic operational analyses for all scenarios in scope item 4.1 and for all the project intersections in scope item 1 using Synchro traffic modeling software. Evaluate the project intersections under the following traffic conditions and roadway configurations:
Sample 1
Traffic Operational Analysis. The study area is defined as the intersections and roadway links where data was collected (two intersections), KH will conduct the analysis for the weekday AM and PM peak hour time periods. KH will perform the following tasks: ⚫ Evaluate the existing (2022) intersection operational conditions at each existing study intersection; ⚫ Calculate the site buildout year each study intersection by inspection of growth rates and addition of traffic from other committed developments in the vicinity; ⚫ Evaluate the intersection operational conditions for each background traffic scenario; ⚫ Calculate new site-generated traffic based on ITE Trip Generation Manual, latest edition, including reductions for internal capture and transit adjacency; ⚫ Create distribution of site-generated traffic in the major directions; ⚫ Assign site-generated traffic onto site driveways and adjacent roadways; ⚫ Evaluate intersection traffic operations for the buildout scenarios using background and site- generated traffic at the study intersections; ⚫ Perform a link capacity analysis for the roadway adjacent to the site for the existing and future year scenarios; ⚫ Identify intersection and thoroughfare deficiencies based on background and site-related traffic; ⚫ Recommend site access and transportation improvements needed to maintain traffic flow in the study area, and identify the site’s pro-rata share of the costs, if any, and ⚫ Recommend intersection geometry and type of traffic control at project driveways. ⚫ No traffic signal warrant analysis is included as part of this scope of services
Sample 1
Traffic Operational Analysis. The Engineer shall perform operational analysis for the existing conditions as well as proposed condition for US 54 from the Xxxx Xxxxxx Bridge to the US54/US 87 intersection. The Engineer shall develop VISSIM traffic models for the existing conditions and the 3-lane configuration for the existing and design year traffic. The following tasks shall be completed for the operational analysis:
Sample 1
Traffic Operational Analysis. The Engineer shall perform operational analysis for the existing conditions as well as proposed condition for the segment of US 54 from the vicinity of the BNSF railroad crossing to the FM 2677 intersection. The Engineer shall develop VISSIM traffic models for the existing conditions as well as up to five (5) total geometric alternatives for the ultimate configuration. The following tasks shall be completed for the operational analysis:
Sample 1
Traffic Operational Analysis. The Engineer shall perform operational analysis for the existing conditions as well as proposed controlled access facility for segment C-1, C-2, D, and A-3. The Engineer shall perform operational analysis for the existing conditions as well as up to two (2) total geometric alternatives for the ultimate configuration of the SL 335 and US 87 interchange. The following tasks shall be completed for the operational analysis:
Sample 1

Related to Traffic Operational Analysis

  • Data Analysis In the meeting, the analysis that has led the College President to conclude that a reduction- in-force in the FSA at that College may be necessary will be shared. The analysis will include but is not limited to the following: ● Relationship of the FSA to the mission, vision, values, and strategic plan of the College and district ● External requirement for the services provided by the FSA such as accreditation or intergovernmental agreements ● Annual instructional load (as applicable) ● Percentage of annual instructional load taught by Residential Faculty (as applicable) ● Fall Full-Time Student Equivalent (FFTE) inclusive of dual enrollment ● Number of Residential Faculty teaching/working in the FSA ● Number of Residential Faculty whose primary FSA is the FSA being analyzed ● Revenue trends over five years for the FSA including but not limited to tuition and fees ● Expenditure trends over five years for the FSA including but not limited to personnel and capital ● Account balances for any fees accounts within the FSA ● Cost/benefit analysis of reducing all non-Residential Faculty plus one Residential Faculty within the FSA ● An explanation of the problem that reducing the number of faculty in the FSA would solve ● The list of potential Residential Faculty that are at risk of layoff as determined by the Vice Chancellor of Human Resources ● Other relevant information, as requested

  • Technology Research Analyst Job# 1810 General Characteristics Maintains a strong understanding of the enterprise’s IT systems and architectures. Assists in the analysis of the requirements for the enterprise and applying emerging technologies to support long-term business objectives. Responsible for researching, collecting, and disseminating information on emerging technologies and key learnings throughout the enterprise. Researches and recommends changes to foundation architecture. Supports research projects to identify and evaluate emerging technologies. Interfaces with users and staff to evaluate possible implementation of the new technology in the enterprise, consistent with the goal of improving existing systems and technologies and in meeting the needs of the business. Analyzes and researches process of deployment and assists in this process.

  • Statistical Analysis 31 F-tests and t-tests will be used to analyze OV and Quality Acceptance data. The F-test is a 32 comparison of variances to determine if the OV and Quality Acceptance population variances 33 are equal. The t-test is a comparison of means to determine if the OV and Quality Acceptance 34 population means are equal. In addition to these two types of analyses, independent verification 35 and observation verification will also be used to validate the Quality Acceptance test results.

  • Project Planning GOVERNMENTAL APPROVALS; ENVIRONMENTAL COMPLIANCE; PUBLIC INFORMATION 30 4.1 Planning and Engineering Activities 30 4.2 Site Conditions 30 4.3 Governmental Approvals 30 4.4 Environmental Compliance 34 4.5 Community Outreach and Public Information 35

  • Industrial Operations Analyst (IOA ‌ The IOA is a GSA Government official who audits Contractor records and conducts Contractor Assistance Visits (CAVs) to the Contractor’s place of business to assist the Contractor with task order reporting, Contract Access Fee (CAF) management, and other general contract administration functions deemed necessary by the Government.

  • Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • Reverse Engineering The Customer must not reverse assemble or reverse compile or directly or indirectly allow or cause a third party to reverse assemble or reverse compile the whole or any part of the software or any products supplied as a part of the Licensed System.

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

  • Requirement for Project Planning No physical work will begin on the construction site until the receipt of a Proceed Order issued by the Owner. The Contract assumes that a Proceed Order will be issued in not more than sixty days from the Effective Date of the Contract. Failure of the Contractor to provide the necessary documentation for the issuance of a Proceed Order shall not entitle the Contractor to any extension of time. If a Proceed Order is not issued within sixty days from the award of the Contract and non-issuance is due to nonperformance by the Contractor, the Contractor may be in default.

Time is Money Join Law Insider Premium to draft better contracts faster.