Affected Parties and Roles Sample Clauses

Affected Parties and Roles. The following table defines the roles of the EBERO Event Team in relation to parties involved in the EBERO service: Notifies the Technical Services team of registries which are failing to meet service level commitments, based on ICANN’s SLA monitoring. failing to meet specifications for data escrow, as well as advising of historical compliance concerns with the registry. Should emergency thresholds be reached, prompt action should be taken to protect the stability and resilience of the DNS and domain name registrants. disclosures and releases to the public, press, or other affected parties.
AutoNDA by SimpleDocs
Affected Parties and Roles. ‌ The following table defines the roles of the EBERO Event Team in relation to affected parties: ICANN 24x7 Operations Center Notifies the executive committee of registries which are failing to meet service level commitments, based on ICANN’s SLA monitoring. ICANN Compliance Notifies the executive committee of registries which are failing to meet specifications for data escrow, as well as advising of historical compliance concerns with the registry. ICANN Executive Management Authorizes and delegates authority to an Event Director, so that should emergency thresholds be reached, prompt action can be taken to protect the stability and resilience of the DNS. ICANN Corporate Communications The Event Director provides information related to the EBERO event; Communications (with Senior Management) makes appropriate disclosures and releases to the public, press, or other affected parties. Accredited Registrars The Event Director provides technical and operational notices about transitioning and transitioned registries to all accredited registrars after an emergency transition occurs. Registry Escrow Agents The Event Director notifies the escrow agent to arrange the swift release of escrow deposits in accordance with the escrow agreements. EBERO Escrow Agent The Event Director notifies the contracted escrow agent to authorize the initiation and termination of escrow deposits by the EBERO service provider. IANA The Event Director notifies IANA of registry transition events and makes emergency requests for changes to the root zone and to IANA authorization databases.
Affected Parties and Roles. ‌ The following table defines the roles of the EBERO Event Team in relation to affected parties: Notifies the executive committee of registries which are failing to meet service level commitments, based on ICANN’s SLA monitoring. meet specifications for data escrow, as well as advising of historical compliance concerns with the registry. Authorizes and delegates authority to an Event Director, so that should emergency thresholds be reached, prompt action can be taken to protect the stability and resilience of the DNS. event; Communications (with Senior Management) makes appropriate disclosures and releases to the public, press, or other affected parties. The Event Director provides technical and operational notices about transitioning and transitioned registries to all accredited registrars after an emergency transition occurs. release of escrow deposits in accordance with the escrow agreements. The Event Director notifies the contracted escrow agent to authorize the initiation and termination of escrow deposits by the EBERO service provider.

Related to Affected Parties and Roles

  • PARTIES AND DATE This Agreement is made and entered into this 19th day of June, 2019 (“Effective Date”) by and between the City of Corona, a municipal corporation organized under the laws of the State of California with its principal place of business at 000 Xxxxx Xxxxxxxx Xxxxxx, Xxxxxx, Xxxxxxxxxx 00000 (“City”) and Xxxxx, a California Corporation with its principal place of business at 000 Xxxxx Xxxxxx, Xxxxxxxxx, XX 00000 (“Consultant”). City and Consultant are sometimes individually referred to as “Party” and collectively as “Parties” in this Agreement.

  • Certification Regarding Business with Certain Countries and Organizations Pursuant to Subchapter F, Chapter 2252, Texas Government Code, PROVIDER certifies it is not engaged in business with Iran, Sudan, or a foreign terrorist organization. PROVIDER acknowledges this Purchase Order may be terminated if this certification is or becomes inaccurate.

  • OBLIGATIONS AND ACTIVITIES OF CONTRACTOR AS BUSINESS ASSOCIATE 1. CONTRACTOR agrees not to use or further disclose PHI COUNTY discloses to CONTRACTOR other than as permitted or required by this Business Associate Contract or as required by law. 2. XXXXXXXXXX agrees to use appropriate safeguards, as provided for in this Business Associate Contract and the Agreement, to prevent use or disclosure of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY other than as provided for by this Business Associate Contract. 3. XXXXXXXXXX agrees to comply with the HIPAA Security Rule at Subpart C of 45 CFR Part 164 with respect to electronic PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY. 4. CONTRACTOR agrees to mitigate, to the extent practicable, any harmful effect that is known to CONTRACTOR of a Use or Disclosure of PHI by CONTRACTOR in violation of the requirements of this Business Associate Contract. 5. XXXXXXXXXX agrees to report to COUNTY immediately any Use or Disclosure of PHI not provided for by this Business Associate Contract of which CONTRACTOR becomes aware. CONTRACTOR must report Breaches of Unsecured PHI in accordance with Paragraph E below and as required by 45 CFR § 164.410. 6. CONTRACTOR agrees to ensure that any Subcontractors that create, receive, maintain, or transmit PHI on behalf of CONTRACTOR agree to the same restrictions and conditions that apply through this Business Associate Contract to CONTRACTOR with respect to such information. 7. CONTRACTOR agrees to provide access, within fifteen (15) calendar days of receipt of a written request by COUNTY, to PHI in a Designated Record Set, to COUNTY or, as directed by COUNTY, to an Individual in order to meet the requirements under 45 CFR § 164.524. If CONTRACTOR maintains an Electronic Health Record with PHI, and an individual requests a copy of such information in an electronic format, CONTRACTOR shall provide such information in an electronic format. 8. CONTRACTOR agrees to make any amendment(s) to PHI in a Designated Record Set that COUNTY directs or agrees to pursuant to 45 CFR § 164.526 at the request of COUNTY or an Individual, within thirty (30) calendar days of receipt of said request by COUNTY. XXXXXXXXXX agrees to notify COUNTY in writing no later than ten (10) calendar days after said amendment is completed. 9. CONTRACTOR agrees to make internal practices, books, and records, including policies and procedures, relating to the use and disclosure of PHI received from, or created or received by CONTRACTOR on behalf of, COUNTY available to COUNTY and the Secretary in a time and manner as determined by COUNTY or as designated by the Secretary for purposes of the Secretary determining COUNTY’S compliance with the HIPAA Privacy Rule. 10. CONTRACTOR agrees to document any Disclosures of PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, and to make information related to such Disclosures available as would be required for COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 11. CONTRACTOR agrees to provide COUNTY or an Individual, as directed by COUNTY, in a time and manner to be determined by COUNTY, that information collected in accordance with the Agreement, in order to permit COUNTY to respond to a request by an Individual for an accounting of Disclosures of PHI in accordance with 45 CFR § 164.528. 12. XXXXXXXXXX agrees that to the extent CONTRACTOR carries out COUNTY’s obligation under the HIPAA Privacy and/or Security rules CONTRACTOR will comply with the requirements of 45 CFR Part 164 that apply to COUNTY in the performance of such obligation. 13. If CONTRACTOR receives Social Security data from COUNTY provided to COUNTY by a state agency, upon request by COUNTY, CONTRACTOR shall provide COUNTY with a list of all employees, subcontractors and agents who have access to the Social Security data, including employees, agents, subcontractors and agents of its subcontractors. 14. CONTRACTOR will notify COUNTY if CONTRACTOR is named as a defendant in a criminal proceeding for a violation of HIPAA. COUNTY may terminate the Agreement, if CONTRACTOR is found guilty of a criminal violation in connection with HIPAA. COUNTY may terminate the Agreement, if a finding or stipulation that CONTRACTOR has violated any standard or requirement of the privacy or security provisions of HIPAA, or other security or privacy laws are made in any administrative or civil proceeding in which CONTRACTOR is a party or has been joined. COUNTY will consider the nature and seriousness of the violation in deciding whether or not to terminate the Agreement.

  • Costs, Expenses, Liabilities and Obligations The Developer shall be responsible for all costs, expenses, liabilities and obligations imposed under or incurred in order to satisfy the terms of this Agreement and all Federal, Provincial and Municipal laws, by-laws, regulations and codes applicable to the Lands.

  • Disclosure of Contractor Parties Litigation The Contractor shall require that all Contractor Parties, as appropriate, disclose to the Contractor, to the best of their knowledge, any Claims involving the Contractor Parties that might reasonably be expected to materially adversely affect their businesses, operations, assets, properties, financial stability, business prospects or ability to Perform fully under the Contract, no later than ten (10) Days after becoming aware or after they should have become aware of any such Claims. Disclosure shall be in writing.

  • Parties and Purpose This agreement (the “Agreement”) is entered by and between certain portfolios and classes thereof, specified below and in Schedule C, of Franklin Xxxxxxxxx Variable Insurance Products Trust, an open-end management investment company organized as a statutory trust under Delaware law (the “Trust”), Franklin/Xxxxxxxxx Distributors, Inc., a California corporation which is the principal underwriter for the Trust (the “Underwriter,” and together with the Trust, “we” or “us”), the insurance company identified on Schedule A (together “you”) and your distributor, on your own behalf and on behalf of each segregated asset account maintained by you that is listed on Schedule B, as that schedule may be amended from time to time (“Account” or “Accounts”). The purpose of this Agreement is to entitle you, on behalf of the Accounts, to purchase the shares, and classes of shares, of portfolios of the Trust (“Portfolios”) that are identified on Schedule C, consistent with the terms of the prospectuses of the Portfolios, solely for the purpose of funding benefits of your variable life insurance policies or variable annuity contracts (“Contracts”) that are identified on Schedule D. This Agreement does not authorize any other purchases or redemptions of shares of the Trust.

  • Facilities and Services The Company shall furnish the Executive with office space, secretarial and support staff, and such other facilities and services as shall be reasonably necessary for the performance of his duties under this Agreement.

  • Properties and Insurance (a) HUBCO and its Subsidiaries have good and, as to owned real property, marketable title to all material assets and properties, whether real or personal, tangible or intangible, reflected in HUBCO's consolidated balance sheet as of December 31, 1997, or owned and acquired subsequent thereto (except to the extent that such assets and properties have been disposed of for fair value in the ordinary course of business since December 31, 1997), subject to no encumbrances, liens, mortgages, security interests or pledges, except (i) those items that secure liabilities that are reflected in said balance sheet or the notes thereto or that secure liabilities incurred in the ordinary course of business after the date of such balance sheet, (ii) statutory liens for amounts not yet delinquent or which are being contested in good faith, (iii) such encumbrances, liens, mortgages, security interests, pledges and title imperfections that are not in the aggregate material to the business, operations, assets, and financial condition of HUBCO and its subsidiaries taken as a whole and (iv) with respect to owned real property, title imperfections noted in title reports. Except as disclosed in the HUBCO Disclosure Schedule, HUBCO and its Subsidiaries as lessees have the right under valid and subsisting leases to occupy, use, possess and control all property leased by HUBCO or its Subsidiaries in all material respects as presently occupied, used, possessed and controlled by HUBCO and its Subsidiaries. (b) The business operations and all insurable properties and assets of HUBCO and its Subsidiaries are insured for their benefit against all risks which, in the reasonable judgment of the management of HUBCO, should be insured against, in each case under policies or bonds issued by insurers of recognized responsibility, in such amounts with such deductibles and against such risks and losses as are in the opinion of the management of HUBCO adequate for the business engaged in by HUBCO and its Subsidiaries. As of the date hereof, neither HUBCO nor any of its Subsidiaries has received any notice of cancellation or notice of a material amendment of any such insurance policy or bond or is in default under any such policy or bond, no coverage thereunder is being disputed and all material claims thereunder have been filed in a timely fashion.

  • Working Facilities and Expenses It is understood by the parties that the Executive’s principal place of employment shall be at the Bank’s principal executive office located in New Haven, Connecticut, or at such other Bank Board approved location within 50 miles of the address of such principal executive office, or at such other location as the Employer and the Executive may mutually agree upon. The Employer shall provide the Executive at his principal place of employment with a private office, secretarial services and other support services and facilities suitable to his position with the Employer and necessary or appropriate in connection with the performance of his assigned duties under this Agreement. The Employer shall reimburse the Executive for his ordinary and necessary business expenses attributable to the Employer’s business, including, without limitation, the Executive’s travel and entertainment expenses incurred in connection with the performance of his duties for the Employer under this Agreement, in each case upon presentation to the Employer of an itemized account of such expenses in such form as the Employer may reasonably require, and such reimbursement shall be paid promptly by the Employer and in any event no later than March 15 of the year immediately following the year in which the expenses were incurred.

  • Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.

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