Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
NO EXCLUDED NATION OR TERRORIST ORGANIZATION CERTIFICATION As required by Chapter 2252 of the Texas Government Code the Contractor must certify that it is not a company engaged in active business operations with Sudan, Iran, or a foreign terrorist organization – specifically, any company identified on a list prepared and maintained by the Texas Comptroller under Texas Government Code §§806.051, 807.051, or 2252.153. (A company that the U.S. Government affirmatively declares to be excluded from its federal sanctions regime relating to Sudan, Iran, or any federal sanctions regime relating to a foreign terrorist organization is not subject to the contract prohibition.)
OWNERSHIP AND USE OF ELIGIBLE CONSUMER DATA Competitive Supplier acknowledges that the Town shall have exclusive ownership of all right, title, and interest in and to all Eligible Consumer data (including addresses, telephone numbers or other identifying information) made available to Competitive Supplier as a result of execution of this ESA. Competitive Supplier shall use Eligible Consumer data solely to provide All- Requirements Power Supply to Participating Consumers and to render other services expressly required or permitted under this ESA. Any other use of Eligible Consumer data without the prior written consent of the Town is strictly prohibited. Pursuant to such authorized use, Competitive Supplier may share such Eligible Consumer data with affiliates and third-party vendors as reasonably necessary to accommodate Competitive Supplier’s provision of All-Requirements Power Supply or other performance pursuant to this ESA (including, without limitation, collection of receivables), provided that Competitive Supplier will take reasonable measures to inform any such vendor of the confidential nature of such data and the restrictions set forth in this Article 2.5 and elsewhere in this ESA. Except as expressly provided in this ESA, Competitive Supplier shall not disclose any Eligible Consumer data to any third-party that has not executed a non-disclosure certificate or agreement in a form mutually acceptable to the Parties, and Competitive Supplier shall take Commercially Reasonable measures to protect Eligible Consumer data from access by, or beneficial use for, any third-party. Notwithstanding the foregoing, the Parties agree that contract employees and entities with which Competitive Supplier contracts to provide contract employees shall not be deemed third parties for purposes of this Section 2.5. To the extent that the provision of All-Requirements Power Supply or other services under this ESA requires that Competitive Supplier have access to or make use of any Eligible Consumer data, Competitive Supplier shall treat such Eligible Consumer data as confidential information. Competitive Supplier may use Eligible Consumer data to engage in direct marketing only during the term of this ESA and subject to the terms set forth in Article
Commerce eXtensible Markup Language (cXML) This standard establishes the data contents required for invoicing via cXML within the context of an electronic environment. This transaction set can be used for invoicing via the AN for catalog and non-catalog goods and services. The cXML format is the Ariba preferred method for electronic invoicing.
Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.
Safety and Security Contractor is responsible for maintaining safety in the performance of this Contract. Contractor shall be responsible for complying with the District’s rules and regulations pertaining to safety, security, and driving on school grounds, particularly when children are present.
Identification of Goods Identification of the goods shall not be deemed to have been made until both Buyer and Seller have agreed that the goods in question are to be appropriate to the performance of this Agreement.
ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to Image Access via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (one hundred seventy-five (175) byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
Fraud, Waste, and Abuse Contractor understands that HHS does not tolerate any type of fraud, waste, or abuse. Violations of law, agency policies, or standards of ethical conduct will be investigated, and appropriate actions will be taken. Pursuant to Texas Government Code, Section 321.022, if the administrative head of a department or entity that is subject to audit by the state auditor has reasonable cause to believe that money received from the state by the department or entity or by a client or contractor of the department or entity may have been lost, misappropriated, or misused, or that other fraudulent or unlawful conduct has occurred in relation to the operation of the department or entity, the administrative head shall report the reason and basis for the belief to the Texas State Auditor’s Office (SAO). All employees or contractors who have reasonable cause to believe that fraud, waste, or abuse has occurred (including misconduct by any HHS employee, Grantee officer, agent, employee, or subcontractor that would constitute fraud, waste, or abuse) are required to immediately report the questioned activity to the Health and Human Services Commission's Office of Inspector General. Contractor agrees to comply with all applicable laws, rules, regulations, and System Agency policies regarding fraud, waste, and abuse including, but not limited to, HHS Circular C-027. A report to the SAO must be made through one of the following avenues: ● SAO Toll Free Hotline: 1-800-TX-AUDIT ● SAO website: xxxx://xxx.xxxxx.xxxxx.xx.xx/ All reports made to the OIG must be made through one of the following avenues: ● OIG Toll Free Hotline 0-000-000-0000 ● OIG Website: XxxxxxXxxxxXxxxx.xxx ● Internal Affairs Email: XxxxxxxxXxxxxxxXxxxxxxx@xxxx.xxxxx.xx.xx ● OIG Hotline Email: XXXXxxxxXxxxxxx@xxxx.xxxxx.xx.xx. ● OIG Mailing Address: Office of Inspector General Attn: Fraud Hotline MC 1300 P.O. Box 85200 Austin, Texas 78708-5200
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)
