Data Repository Sample Clauses

Data Repository. The “Data Repository” shall mean the data repository(ies) and databases (not including the Licensed Software) that HCO will have access to as part of the Services.
Data Repository. A computerized, secure electronic data and information 40 storage repository system controlled and maintained by the Régie and located within the 41 Province of Québec. Information, data and documents related to activities of the QCMEP 42 whether filed by a Registered Entity, or created or obtained by the Régie, NPCC, or NERC 43 are stored on the Data Repository. 44
Data Repository. (a) The Supplier will provide a secure web-based portal through which Hawaiian Telcom will be able to access online (i) electronic copies of all of the reports run on a periodic basis (so as to provide meaningful, actionable information), (ii) such raw data underlying such reports as to provide the auditability of the reports, and (iii) the other items described below in this Section 5.4.2 (the “Data Repository”).
Data Repository. If any research conducted by Novartis or any of its Affiliates, either alone or with a Novartis Collaboration Partner that has shared its Clinical Data with SomaLogic, is part of a study funded by a United States federal agency or similar government entity that has a data sharing policy to which Novartis, any of its Affiliates or any such Novartis Collaboration Partner must adhere that requires the integration into a public database of all or substantially all of the SOMAscan Data provided to Novartis under a Project Plan, Novartis or its Affiliates will not, and it will procure that any Novartis Collaboration Partner will not, to the extent permitted by the study’s data sharing policy, provide any SOMAscan Data to the data repository until the earlier to occur of [****] after completion of the applicable clinical study or other project or waive [****] after acceptance for publication of a primary manuscript describing the Novartis Results of the applicable clinical study or other project conducted by Novartis or any of its Affiliates, either alone or with any such Novartis Collaboration Partner. For the avoidance of doubt, any Novartis Collaboration Partner that has not shared its Clinical Data with SomaLogic will not be permitted to provide any SOMAscan Data to a data repository at any time unless such Novartis Collaboration Partner is subject to an obligation (naming SomaLogic as a third party beneficiary) that such Novartis Collaboration Partner will not file any Patents claiming Biomarkers discovered or created through the use of the SOMAscan Data.

Related to Data Repository

  • Data Reporting Licensee is responsible for the accuracy and completeness of all data it submits to Xxxxxx Mae’s systems, and Xxxxxx Mae does not have any obligation to authenticate the source of, or verify the accuracy of, any such data. Licensee is solely responsible for the back‐up and restoration of its data and other materials.

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

  • Data Retention The Company will use the Grantee’s personal data only as long as necessary to implement, administer and manage the Grantee’s participation in the Plan or as required to comply with legal or regulatory obligations, including under tax and securities laws. When the Company no longer needs the Grantee’s personal data, which will generally be seven (7) years after the Grantee participates in the Plan, the Company will remove it from its systems. If the Company keeps the data longer, it would be to satisfy legal or regulatory obligations and the Company’s legal basis would be relevant laws or regulations.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Identity Verification You agree to provide us with the information we request for the purposes of identity verification and the detection of money laundering, terrorist financing, fraud, or any other financial crime and permit us to keep a record of such information. You will need to complete certain verification procedures before you are permitted to use the Services and your access to the Services may be altered as a result of information collected on an ongoing basis. The information we request may include certain personal information, including, but not limited to, your name, address, telephone number, e-mail address, date of birth, taxpayer identification number, government identification number, and information regarding your bank account (such as the name of the bank, the account type, routing number, and account number). In providing us with this or any other information that may be required, you confirm that the information is accurate and authentic. You agree to update this information and keep it current at all times. You authorize us to make the inquiries, whether directly or through third parties, that we consider appropriate, in our sole discretion, to verify your identity or protect you and/or us against fraud or other financial crimes, and to take action we reasonably deem necessary based on the results of such inquiries.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Account Verification Whether or not a Default or Event of Default exists, Agent shall have the right at any time, in the name of Agent, any designee of Agent or any Borrower, to verify the validity, amount or any other matter relating to any Accounts of Borrowers by mail, telephone or otherwise. Borrowers shall cooperate fully with Agent in an effort to facilitate and promptly conclude any such verification process.

  • Implementation Report Within 150 days after the Effective Date, CHSI shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.