Basic Statistics by Domain Sample Clauses

Basic Statistics by Domain. The basis statistics of samples contained within the CX and Range Front fault zones are summarized in Table 17-2. Table 17-2: Drill-hole Sample Statistics by Fault Zone Table 17-3: Drill-hole Sample Statistics by HG/LG Portion of Fault Zone The results from the tables above indicate that the Range Front zone is slightly higher grade than the CX zone. Although the physical extent of the Range Front zone is larger, the CX zone has more contained samples due its higher density of drill holes. Note that the low-grade (LG) portion of the fault zones contains several relatively high-grade samples (they are described in more detail in section 17.7 of this report). These were considered somewhat anomalous during the development of the HG zone domains because they could not be included in the interpretation with any degree of confidence. Therefore, at present, they remain outside of the HG zone domain. The understanding of these intervals is expected to improve with additional drilling and it is anticipated that they may add to overall resource in the future.
AutoNDA by SimpleDocs

Related to Basic Statistics by Domain

  • Usage Statistics The Distributor shall ensure that the Publisher will provide access to both composite system-wide use data and itemized data for the Licensee, the Participating Institutions, individual campuses and labs, on a monthly basis. The statistics shall meet or exceed the most recent project Counting Online Usage of NeTworked Electronic Resources ("COUNTER") Code of Practice Release,3 including but not limited to its provisions on customer confidentiality. When a release of a new COUNTER Code of Practice is issued, the Distributor shall ensure that the Publisher will comply with the implementation time frame specified by COUNTER to provide usage statistics in the new standard format. It is more than desirable that the Standardized Usage Statistics Harvesting Initiative (SUSHI) Protocol4 is available for the Licensee to harvest the statistics.

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer.

  • Reporting on Utilization of Subject Inventions 1. The Performer agrees to submit, during the term of the Agreement, an annual report on the utilization of a subject invention or on efforts at obtaining such utilization that are being made by the Performer or its licensees or assignees. Such reports shall include information regarding the status of development, date of first commercial sale or use, gross royalties received by the Performer, and such other data and information as the agency may reasonably specify. The Performer also agrees to provide additional reports as may be requested by DARPA in connection with any march-in proceedings undertaken by DARPA in accordance with Paragraph I of this Article. DARPA agrees it shall not disclose such information to persons outside the Government without permission of the Performer, unless required by law. 2. All required reporting shall be accomplished, to the extent possible, using the i-Edison reporting website: xxxxx://x-xxxxxx.xxxx.xxx.xxx/iEdison/. To the extent any such reporting cannot be carried out by use of i-Edison, reports and communications shall be submitted to the Agreements Officer and Administrative Agreements Officer.

  • Return of Customer Data Okta shall return Customer Data to Customer and, to the extent allowed by applicable law, delete Customer Data in accordance with the procedures and time periods specified in the Trust & Compliance Documentation, unless the retention of the data is requested from Okta according to mandatory statutory laws.

  • Statistical Information Any third-party statistical and market-related data included in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate in all material respects.

  • Use of Customer Data Verizon, Verizon Affiliates and their respective agents, may use, process and/or transfer Customer Data (including intra-group transfers and transfers to entities in countries that do not provide statutory protections for personal information) as set forth in the Privacy Policy and as necessary: (a) in connection with provisioning of Services; (b) to incorporate Customer Data into databases controlled by Verizon, Verizon Affiliates or their respective agents for the purpose of providing Services; administration; provisioning; invoicing and reconciliation; verification of Customer identity, solvency and creditworthiness; maintenance, support and product development; fraud detection and prevention; sales, revenue and customer analysis and reporting; market and customer use analysis including in the manner described in the Privacy Policy; and (c) to communicate to Customer regarding Services.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Statistical, Demographic or Market-Related Data All statistical, demographic or market-related data included in the Registration Statement, the Disclosure Package or the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate and all such data included in the Registration Statement, the Disclosure Package or the Prospectus accurately reflects the materials upon which it is based or from which it was derived.

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

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