Splunk Data Request Guidelines Sample Clauses

Splunk Data Request Guidelines. Splunk’s general practices for responding to requests by government agencies and other third parties is published on Splunk Protects at xxxxx://xxx.xxxxxx.xxx/en_us/pdfs/legal/splunk-data-request-guidelines.pdf
AutoNDA by SimpleDocs

Related to Splunk Data Request Guidelines

  • Design Guidelines The Owner’s “Design Guidelines” are as published on the Owner’s website (xxxx://xxxxx.xxxxx.xxx/for-vendors/design-guidelines/). In addition to providing a guide to be used in the preparation of design documents for the Owner’s construction projects, the Design Guidelines also contain regulatory code compliance and other Owner requirements. The “Effective Date” (as noted in Section 2.7 of the Design Guidelines), determining which edition will be used for a given project, is set at the beginning of Design Development and will govern the preparation of construction documents for the project unless noted otherwise. Compliance with the Design Guidelines does not relieve the Design Professional from any of its responsibility.

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

  • Agreed Guidelines Applications With respect to the application of the Sentencing Guidelines to this case, the parties stipulate and agree as follows:

  • HIV/AIDS Model Workplace Guidelines Grantee will:

  • Hot Weather Guidelines For the purposes of site based discussions regarding the need to plan and perform work during expected periods of hot weather, the following issues shall be considered in conjunction with proper consideration of Occupational Health and Safety issues.

  • Sentencing Guidelines Calculations 8. Defendant understands that in imposing sentence the Court will be guided by the United States Sentencing Guidelines. Defendant understands that the Sentencing Guidelines are advisory, not mandatory, but that the Court must consider the Guidelines in determining a reasonable sentence.

  • Ordering Guidelines and Processes 1.14.1 For information regarding Ordering Guidelines and Processes for various Network Elements, Combinations and Other Services, TWTC should refer to the “Guides” section of the AT&T Interconnection Web site. TWTC will be notified of any material changes to such “Guides”.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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