Database Updates. Database updates for directory assistance/listings and E911 include the processes by which these systems are updated with Customer information which has changed due to the service provisioning activity. Measurements in this category are designed to evaluate the timeliness and accuracy with which changes to Customer information, as submitted to these databases, are completed by GTE.
Database Updates. At least weekly, Property Manager shall update Operating Partnership’s proprietary database with such information as Operating Partnership may reasonably request.
Database Updates. The CONTRACTOR agrees to provide WSDOT and the CONTRACTOR’s contracting partners with updated lists of affected or participating worksites, employee transportation coordinators, and jurisdiction contacts, as requested. These updates will be submitted in a format specified by WSDOT.
Database Updates. 6.1 Customer shall furnish all information reasonably requested by Provider in order for Provider to provide each Service. Customer shall ensure that all information and data that it has given or that it will give to Provider, including but not limited to Customer's billing information, mailing address and email address, and Customer’s Subscriber information is current and accurate at all times. Provider shall have no responsibility to verify the accuracy of any information provided by Customer. Provider shall have no liabilities or obligations relative to any amount billed or notices delivered incorrectly as a result of inaccurate information provided by Customer and Customer's failure to correct or update the same. Customer agrees to indemnify, defend, and hold Provider, Provider’s Affiliates, the Third-Party Vendors, and the parent companies, sister companies, employees, directors, officers, and shareholders of the same, harmless from and against any and all claims, liabilities, losses, judgments, damages and expenses, including without limitation attorneys' fees and costs of litigation, incurred or suffered by such party relating to Customer's failure to perform the foregoing obligation.
Database Updates. If End User does not correctly identify the physical location when defining the Registered Location, 911 calls through the Service may not reach the correct PSAP. During initial activation of the Service and following updates to the Registered Location information, there is a delay before complete and accurate automatic number and location information is provided to the local emergency service operator.
Database Updates. If End User does not correctly identify the physical location when defining the Initial Registered Location, 9-1-1 calls through WPaaS may not reach the appropriate PSAP.
Database Updates. The Ground Shaking Working Group previously discussed the need for and analysis of large-scale ground-shaking maps for the Wasatch Front, based on a WFCVM incorporating shallow shear-wave velocity (Vs30) and deep-basin structure, and new liquefaction-hazard maps. The UGS has compiled databases that identify existing data on shallow shear-wave velocities (Vs30), deep-basin structure, geotechnical landslide shear strengths, and Quaternary faults and folds. We continue to track new geologic mapping and studies of Quaternary faults in Utah for updates to the Utah Quaternary Fault and Fold Database and Map. A thorough review of all fault data is ongoing, as part of a complete rebuild of the database using ESRI SDE technology. Once through the UGS review process, the revised database files will be forwarded to the USGS for incorporation into the Quaternary Fault and Fold Database of the United States. We continue to develop an interactive map and database of Utah’s Quaternary faults and folds that will be accessible through the UGS website. This version of the map and database supplements the USGS Quaternary Fault and Fold Database of the United States by highlighting structures for which new data exist, but may not yet be available through the national database. The map will be served on the UGS website with XXXX’s ArcServer technology, for user on-the-fly location querying and map generation. The initial release of the new Utah Quaternary Fault Database is anticipated in mid-2015.
Database Updates. Update of the Database with any Database Transaction shall be less than one (1) second.
Database Updates. Subject to Section 3.2, during the Update Term, LookSmart shall provide Microsoft with Database Updates. LookSmart shall deliver the Database Updates to Microsoft as frequently as may be reasonably requested by Microsoft, provided that LookSmart agrees that: (i) starting no later than as soon as is reasonably practicable, but in any event no later than three (3) months (for the purposes of this Section 3.1, the "Update Start-up Period") following the Effective Date, Microsoft will receive Database Updates from LookSmart once per day at a mutually agreed upon time of day by delivery of a complete refreshed copy of the Database (as delivered by LookSmart up to the time of the delivery) as more completely set forth in Exhibit B attached hereto and incorporated herein by this reference and (ii) prior to the Update Start-up Period, Microsoft will receive Database Updates from LookSmart once per week on a mutually agreed upon day and at a mutually agreed upon time of day by delivery of a complete refreshed copy of the Database (as delivered by LookSmart up to the time of the delivery) in the format set out in Section 2 of this Agreement. If, after the Update Start-up Period, LookSmart does not provide Microsoft with a Database Update at least once daily for more than five (5) days in any one- half Year period, Microsoft may, upon Microsoft's notice to LookSmart made within ninety (90) days of the end of such one-half Year period, as Microsoft's sole remedy for such non-performance, receive a payment of the following amount from LookSmart:
(i) if the total number of days during the one-half Year period for which LookSmart does not deliver a Database Update is thirty-five (35) or fewer, a per day amount of [**] for day six (6) and each additional day over six (6) days;
(ii) if the total number of days during the one-half Year period for which LookSmart does not deliver a Database Update is thirty-six (36) or more, a per day amount of [**] for day six (6) and each additional day over six (6) days. Any amounts due under this Section 3.1, shall have no affect on any amounts due under Section 7 and shall be due and payable within ten (10) business days of Microsoft's submitting an invoice to LookSmart for the applicable amount, and the election of Microsoft to receive such amount shall prohibit Microsoft from pursuing any other remedy that may be available to Microsoft under Section 12 of this Agreement or otherwise.
Database Updates. The Software includes a database that defines mobile phone profiles. When you use the Software to transfer or copy your files onto a flash memory product and identify the mobile phone on which the card will be used, the database helps the Software identify how to best format your files so that you can access them more easily on the mobile phone you have specified. An updated mobile phone profile database is sent to your computer whenever you use the Software and have an active internet connection. You therefore agree that SanDisk may upload such updated mobile phone database onto your computer.
