FDOT Planning Office GIS Linear Reference System (LRS) and RCI Basemap Correction/Update Analysis Sample Clauses

FDOT Planning Office GIS Linear Reference System (LRS) and RCI Basemap Correction/Update Analysis. The CONSULTANT may be requested to conduct a detailed review of the FDOT Planning Office GIS LRS and Basemap including, but not limited to, roadway section alignments, lengths, curve data, overall descriptions, classifications, etc. Updates are to be reviewed for inconsistencies between the Basemap and RCI database, using ESRI ArcGIS, digital ortho quarter quad maps, aerials, Videolog and the RCI database. The CONSULTANT will prepare draft RCI/LRS Correction submittal packages for review by the FDOT Project Manager or designee prior to transmittal to FDOT Central Office. Unless requested by the FDOT project manager, the CONSULTANT will not request adjustment to section lengths if the measured DMI length in the field is within tolerance of the Basemap length.
AutoNDA by SimpleDocs

Related to FDOT Planning Office GIS Linear Reference System (LRS) and RCI Basemap Correction/Update Analysis

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • 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.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 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, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Student Evaluation A. All unit members shall be subject to student evaluations each semester in each course taught.

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