Crash Data Clause Samples

The Crash Data clause defines the collection, use, and management of information generated by a device or system during a crash event. Typically, this clause outlines what types of crash-related data are recorded—such as speed, impact force, or system status at the time of the incident—and specifies who may access or analyze this information, such as manufacturers, insurers, or regulatory authorities. Its core practical function is to ensure that relevant crash data is available for safety analysis, liability determination, or compliance with legal requirements, thereby supporting transparency and accountability in the event of an accident.
Crash Data. WSB will utilize MnDOT’s CMAT website to collect and summarize crash rates for the intersection. This information will be included in the ICE report.
View SourceView Similar (3)
Crash Data. The CONSULTANT will obtain the most recent five (5) years of available data from the DEPARTMENT's crash database and other local sources for this Project. The crash data will include the number and type of crashes, crash locations, number of fatalities and injuries, and estimates of property damage and economic loss.
View SourceView Similar (3)
Crash Data. The consultant shall analyze the crash data for the latest three-years available to identify discernible crash patterns. The consultant shall also develop collision diagrams intersection/ corridor using any automated crash mapping tool. Such automated tool shall be presented to the FDOT project manager for approval prior to utilizing it for any project. The consultant shall also develop and implement a QA/QC process for automated collision diagrams. At a minimum the consultant shall create the following histograms and tables as part of the crash analysis:  Crashes by type  Crashes by contributing cause  Crashes by time of day  Crashes by lighting condition  Crashes by surface condition  Crashes by weather condition  Crashes by day of the week  Crashes by month of the year  Crashes by age group at fault  Crashes by alcohol/drug involvement  High crash spots  High crash segments  Crash summary by type  Crash summary by contributing cause  Crash summary by location
View SourceView Similar (2)
Crash Data. The Branch completed a two-year staff supplement contract that employed 16 temporary staff to eliminate the crash-records quality review and assurance backlog of 3.5 years. At present, all historical on-system crash records are processed and available for use. Currently received crash records in 2012—both on and off-system—are processed within four months of receipt from the Department of Revenue. The only remaining backlog is for the 2008-2011 off-system crash records, which will be processed once the Future Staffing of the Traffic Records Unit is addressed and resolved by Management. The Branch is working to achieve all current records with our permanent staff supplemented by a small group of temporary staff who will be with us until late 2013. Prior to their departure CDOT will develop a staffing model to implement in order to keep crash record processing—both for on-system and off-system crashes—within the safety performance measure of six months or less. Colorado does not have a primary seat-belt law. This actually comes from the Governor's Office to FHWA, not through OTS. Colorado is in compliance. Colorado is in compliance.
View Source
Crash Data. Provide pertinent motor vehicle crash data (fatalities and injuries) for each of the previous three (3) years.
View Source
Crash Data. The MPO shall provide technical resources and data.
View Source
Crash Data. For crash related data, the type of motor vehicle, its configuration and identifiers are also provided, alongside crash details containing the count of injuries, fatalities, vehicles involved and outcome containing but not limited to Hazmat involvement, towaway or citations were issued to said driver. Crash inspection data provides location, weather conditions, road surface conditions and light conditions pertaining to the crash incident.
View Source
Crash Data. Stantec engineers will request collision information for the study intersections. 4) Forecasted Traffic Volumes: Stantec will review recent traffic studies and establish projections of traffic based on the Town’s Comprehensive Plan and data available from NCTCOG and TxDOT for the area to determine short- and long-term traffic volume forecasts for the intersection after Legacy is extended.
View Source

Related to Crash Data

  • Device Data We may share certain personal information and device-identifying technical data about you and your devices with third party service providers, who will compare and add device data and fraud data from and about you to a database of similar device and fraud information in order to provide fraud management and prevention services, which include but are not limited to identifying and blocking access to the applicable service or Web site by devices associated with fraudulent or abusive activity. Such information may be used by us and our third party service providers to provide similar fraud management and prevention services for services or Web sites not provided by us. We will not share with service providers any information that personally identifies the user of the applicable device.

  • User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.

  • Customer Data 5.1 The Customer shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data. The customer being a contractor of DSA Airport, the customer shall not own the rights, title and interest in and to the Data which belongs to DSA Airport. 5.2 The Supplier shall follow its archiving procedures for Customer Data as set out in its Back- Up Policy available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended by the Supplier in its sole discretion from time to time. In the event of any loss or damage to Customer Data, the Customer's sole and exclusive remedy shall be for the Supplier to use reasonable commercial endeavours to restore the lost or damaged Customer Data from the latest back-up of such Customer Data maintained by the Supplier in accordance with the archiving procedure described in its Back-Up Policy. The Supplier shall not be responsible for any loss, destruction, alteration or disclosure of Customer Data caused by any third party (except those third parties subcontracted by the Supplier to perform services related to Customer Data maintenance and back-up). 5.3 The Supplier shall, in providing the Services, comply with its Privacy and Security Policy relating to the privacy and security of the Customer Data available at ▇▇▇.▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ or such other website address as may be notified to the Customer from time to time, as such document may be amended from time to time by the Supplier in its sole discretion. 5.4 If the Supplier processes any personal data on the Customer’s behalf when performing its obligations under this agreement, the parties record their intention that the Customer shall be the data controller and the Supplier shall be a data processor and in any such case: (a) the Customer acknowledges and agrees that the personal data may be transferred or stored outside the EEA or the country where the Customer and the Authorised Users are located in order to carry out the Services and the Supplier’s other obligations under this agreement; (b) the Customer shall ensure that the Customer is entitled to transfer the relevant personal data to the Supplier so that the Supplier may lawfully use, process and transfer the personal data in accordance with this agreement on the Customer's behalf; (c) the Customer shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable data protection legislation; (d) the Supplier shall process the personal data only in accordance with the terms of this agreement and any lawful instructions reasonably given by the Customer from time to time; and (e) each party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage.

  • Sensitive data Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.