Conditions System Top Level Overview Sample Clauses

Conditions System Top Level Overview. The Conditions System will incorporate automated data from the Florida Highway Patrol’s (FHP) Computer Aided Dispatch (CAD) system, FDOT’s construction information, FDOT’s Telemetered Traffic Monitoring Sites (TTMS), FDOT District 5’s Surveillance Systems, the Orlando Orange County Expressway Authority’s (OOCEA) Travel Time Data Server, available transit and airport information, and Meteorlogix’s segment weather conditions, alerts, and forecasts (to be provided as part of a separate iFlorida procurement). The Conditions System will also include an operator interface to enable appropriate personnel from FDOT, its partner agencies, and approved private contractors/consultants to enter incident/event reports directly into the Conditions System database, both from the RTMC and remotely via a standard Internet browser. In addition, the operator interface will be linked to both the Central Florida and Statewide 511 Systems. This link will enable FDOT operators to view alerts and/or abnormal conditions generated by these systems, as well as insert one or more unique ad-hoc announcements (.WAV file) into one or both of these 511 systems. For the Central Florida 511 System, the Conditions System will also select from a list of pre-recorded announcements based on operator- defined, travel time scenarios. The Conditions System will fuse all available input data into pre-defined Data Collection Links. A Data Collection Link is a segment of roadway bounded by two endpoints for which roadway information (time/speed, incident/event and other transportation information) is collected in a timely fashion. The lengths of the links are approximately 1 to 5 miles for the more detailed Central Florida interstates, expressways, and arterials and approximately 15 to 45 miles for the more generalized statewide Florida Intrastate Highway System (FIHS) roadways. The links will then be aggregated into Data Collection Link Reports for data dissemination. All input/output associated with the Conditions System will utilize relevant ITS standards to the maximum extent possible. Proposed standards include the Traffic Management Data Dictionary (ITE TM1.03), Standard for Traffic Incident Management Message Sets for Use by Emergency Management Centers (IEEE 1512.1) and/or Standard for Common Incident Management Message Sets for use by EMCs (IEEE 1512.2), and Converting ATIS Message Standards from ASN.1 to XML (SAE J2360). All operator inputs will be Traffic Management Data Dictionary (TMDD)...
AutoNDA by SimpleDocs

Related to Conditions System Top Level Overview

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

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

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

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