Pavement Management System Sample Clauses

Pavement Management System. The Pavement Management Technical Committee meets a minimum of five times a year to identify and resolve issues with the Pavement Management System. The condition reports, and maps are provided, each October to the Transportation Commission and Asset Management Program. A functioning Pavement Management software setup is provided to the regions in December so that the regions can compile project recommendation lists for use in planning the Surface Treatment Program. Differences in condition or project selection, as recommended by the Pavement Management System, from that observed by the Region are categorized and work is undertaken to resolve these differences.
Sample 1Sample 2
AutoNDA by SimpleDocs
Pavement Management System. The Pavement Management Technical Committee meets a minimum of five times a year to identify and resolve issues with the Pavement Management System. The condition reports and maps are provided each September to the Transportation Commission and Asset Management Program in September. A functioning Pavement Management software setup is provided to the Regions in December so that the Regions can compile project recommendation lists for use in planning the Surface Treatment Program. Differences in condition or project selection, as recommended by the Pavement Management System from that observed by the Region, are categorized and work is undertaken to resolve these differences. The following performance indicators will be used to assess the health of the Pavement and Materials Program: SAP # Indicator Description Reporting Mechanism Target/ Baseline Reporting Frequency 253 Percent of resurfacing projects matching recommendations of the Pavement Management Systems annual review1 Percent of resurfacing projects recommended by the Pavement Management System for each State fiscal year Pavement Management Systems Work Plan Track trend State FY 255 & 259-263 Percent of surface treatment funds planned for pavement preservation within each region1 Percent of surface treatment funds planned for pavement preservation within each region (per Chief Engr Policy Memo 18) Pavement Management Systems Work Plan Track trend State FY 1 Due to the ongoing Pavement Management transition from the Remaining Service Life metric to the Drivability Life metric, these indicators can be calculated, but should be considered for information only. It is expected that full reinstatement of specific targets will being in time for the 2015 annual report. Previous targets were 70% of resurfacing projects matching recommendations of the Pavement Management Systems annual review and 5% of surface treatment funds planned for pavement preservation within each region. The FY2015 Surface Treatment Plan (STP) of projects is a mixture of established project delivery commitments aligned with the old RSL philosophies and new projects aligned with the new DL philosophies.. PMS Match status represents simple comparison of the final FY2015 STP to current DL PMS recommendations, and is therefore below target and historic levels. Next year’s report expects to have a project matching percentage in the 80s.The percent of planned preventive maintenance for this year, achieves historic targets. The following perf...
Sample 1
Pavement Management System. (a) Strengthening of KGM’s capacity for collection of data on pavement surface conditions and road geometry through the provision of equipment and technical assistance. (b) Introduction of a bridge management system by strengthening KGM’s existing computerized bridge inventory.
Sample 1
Pavement Management System. (PMS) OPTIMIZATION: 1. Review and analyze city’s current Pavement Management System (PMS) and existing decision trees for maintenance applications and provide recommendation for optimization. Pavement condition prediction models (performance curves and deduct values) are to be calibrated for each pavement classification within the PMS using previous and currently surveyed data. The existing deducts values and distress and severity definitions will be provided by the City. 2. Develop methodology to prioritize projects to optimize spending and budgeting for future maintenance and repair projects. 3. Identify work requirements necessary to meet goals and objectives. 4. Determine various budget scenarios for maintenance and repair 5. A draft report with recommendation for optimization of City’s current pavement maintenance practice using existing and recently collected data under this contract shall be due within six (6) months of awarding this contract. 6. A written report signed and sealed by a licensed professional engineer shall be submitted as a deliverable of this task. Firm with demonstrated experience in successfully integrating data with the Cartegraph Pavement Management Module for municipalities will be viewed favorably.
Sample 1

Related to Pavement Management System

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • PERFORMANCE MANAGEMENT SYSTEM 5.1 The Employee agrees to participate in the performance management system that the Employer adopted for the employees of the Employer; 5.2 The Employee accepts that the purpose of the performance management system will be to provide a comprehensive system with specific performance standards to assist the employees and service providers to perform to the standards required; 5.3 The Employer must consult the Employee about the specific performance standards and targets that will be included in the performance management system applicable to the Employee; 5.4 The Employee undertakes to actively focus on the promotion and implementation of the key performance indicators (including special projects relevant to the employee’s responsibilities) within the local government framework; 5.5 The criteria upon which the performance of the Employee shall be assessed shall consist of two components, Operational Performance and Competencies both of which shall be contained in the Performance Agreement; 5.6 The Employee’s assessment will be based on his performance in terms of the outputs/outcomes (performance indicators) identified as per attached Performance Plan, which are linked to the KPAs, and will constitute 80% of the overall assessment result as per the weightings agreed to between the Employer and Employee; 5.7 The Competencies will make up the other 20% of the Employee’s assessment score. The Competencies are spilt into two groups, leading competencies (indicated in blue on the graph below) that drive strategic intent and direction and core competencies (indicated in green on the graph below), which drive the execution of the leading competencies. Strategic direc on and leadership People management Program and project management Financial management Change leadership Governance leadersip Moral competence Planning and organising Analysis and innova on Knowledge and informa on management Communica on Results and quality focus

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Transportation Management Tenant shall fully comply with all present or future programs intended to manage parking, transportation or traffic in and around the Building, and in connection therewith, Tenant shall take responsible action for the transportation planning and management of all employees located at the Premises by working directly with Landlord, any governmental transportation management organization or any other transportation-related committees or entities.

  • Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • Financial Management System Subrecipient shall establish and maintain a sound financial management system, based upon generally accepted accounting principles. Contractor’s system shall provide fiscal control and accounting procedures that will include the following: i. Information pertaining to tuition rates, payments, and educational assistance payments; and

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

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