Specific Authority for Joint Functional Activities. In addition to the general authorization to enter into interlocal agreements, State law specifically authorizes localities to deliver the following services jointly:
Specific Authority for Joint Functional Activities Sample Clauses
Related to Specific Authority for Joint Functional Activities
Promotional Activities 19 At the request of North Sound BH-ASO, Provider shall display promotional materials in its 20 offices and facilities as practical, in accordance with applicable law and cooperate with and 21 participate in all reasonable marketing efforts. Provider shall not use any North Sound BH- 22 ASO name in any advertising or promotional materials without the prior written permission of 23 North Sound BH-ASO.
Additional Activities I agree that during the period of my employment by the Company I will not, without the Company's express written consent, engage in any employment or business activity which is competitive with, or would otherwise conflict with, my employment by the Company. I agree further that for the period of my employment by the Company and for one (l) year after the date of termination of my employment by the Company I will not induce any employee of the Company to leave the employ of the Company.
Regulatory Activities Beginning on the Effective Date and to the extent UGNX remains the Lead Development Party with respect to a particular territory, subject to and in accordance with the terms and conditions of this Agreement and the requirements of Applicable Laws, UGNX, shall: (a) use Commercially Reasonable Efforts to file (or have filed) all Regulatory Filings with respect to the Licensed Products in the Field in order to obtain Marketing Approvals in each country in the Territory and the European Territory (or to obtain the European Centralized Approval in the European Core Territory) and in order to obtain Pricing and/or Reimbursement Approvals in the Profit Share Territory; (b) respond in a timely fashion to requests for data and information from Regulatory Authorities with respect to the Licensed Products in the Field in the Territory and the European Territory; and (c) meet with officials of the Regulatory Authorities at such times as may be requested by such Regulatory Authorities with respect to the Core Development Activities (“Regulatory Activities”), provided that KHK will have primary responsibility for obtaining, and UGNX shall provide all assistance reasonably requested by KHK, in relation to Pricing and/or Reimbursement Approvals for the Licensed Products in the Field in the European Territory. For the avoidance of doubt, UGNX will be responsible for obtaining, and KHK will provide all assistance reasonably requested by UGNX, in relation to Pricing and/or Reimbursement Approvals, if any, for the Licensed Products in the Field in the Profit Share Territory as part of the UGNX Core Development Activities, it being understood that the costs incurred by UGNX in connection with such activities will be shared equally (50/50). All such Regulatory Activities will be conducted in a manner consistent with the Core Development Plan and coordinated by the JSC in accordance with Article 3. Without limiting the applicability of the foregoing and the remainder of this Article 5, UGNX shall interface with the applicable Regulatory Authority(ies) and, through the JDC, shall keep KHK reasonably informed of all material events and developments occurring in the course of the Regulatory Activities, including scheduled UGNX regulatory strategy discussions and meetings with Regulatory Authorities in the Territory and the European Territory relating to the Licensed Products in the Field.
Professional Activities The Superintendent/Principal shall be encouraged to attend appropriate professional meetings at the local, state, and national levels. Within budget constraints, such costs of attendance shall be paid by the Board. The Superintendent/Principal’s attendance at professional meetings at the national level must have prior approval of the Board.
Outside Professional Activities 27.01 Outside professional activities conducted with professional and academic responsibility can enhance the reputation of the University and the abilities of its academic staff and librarians. This article applies only to outside professional activities that involve the application of special skills and knowledge within the member’s particular professional expertise. While a member has a primary obligation to fulfil their University responsibilities, they have the right to engage in outside professional activities subject to the following conditions: 27.01.01 A member shall notify the Xxxx/University Librarian in writing of the type, time commitment, and location of any such proposed professional activity. If the proposed activity involves the teaching at another educational institution of a course related to the faculty member's professional expertise, the faculty member shall obtain the prior written permission of the Xxxx/University Librarian, and such permission shall not be unreasonably withheld; 27.01.02 Such activities shall not require the commitment of a block of time on a regular basis which might interfere with the faculty member's normal timetable for teaching activities or a librarian's performance of normal professional responsibilities. For faculty, such activities shall not require the member to devote more than an average of one working day per five-day week on an annual basis. For librarian members, such activities shall not require the member to devote more than 20 working days per calendar year. 27.01.03 Such activities shall not hinder the fulfilment of the member's obligations to the University; 27.01.04 The name of the University and University letterhead shall not be used in such activities unless agreed to in advance by the President, although nothing shall prevent a member from stating the nature and place of employment, rank, and title in connection with such professional activities, provided that they shall not purport to represent the University or to speak for it, or to have its approval, unless such approval has been given in advance in writing by the Xxxx/University Librarian; 27.01.05 Use of University facilities, equipment, supplies, services or other personnel shall require prior written authorization from the member's Xxxx/University Librarian or from the appropriate administrative officer. Financial arrangements for such use shall be made in advance. University activities shall have priority in the use of such facilities, equipment, supplies, services and personnel; 27.01.06 A member engaged in outside professional activities shall hold the University harmless against any loss or damage that the University may suffer from such activities; and, 27.01.07 In preparing their Annual Report, each member shall include a statement of their outside professional activities in the previous year. 27.02 If the Xxxx/University Librarian has cause for concern, the Xxxx/University Librarian has the right to review a member's current or proposed outside professional activities and may require the member to provide information concerning the time devoted to current and past outside professional activities. The Xxxx/University Librarian shall inform the member in writing of the results of the review and, if necessary, of any corrective action which might be required of the member.
TECHNOLOGY/KNOWLEDGE TRANSFER ACTIVITIES The goal of this task is to develop a plan to make the knowledge gained, experimental results, and lessons learned available to the public and key decision makers. • Prepare an Initial Fact Sheet at start of the project that describes the project. Use the format provided by the CAM. • Prepare a Final Project Fact Sheet at the project’s conclusion that discusses results. Use the format provided by the CAM. • Prepare a Technology/Knowledge Transfer Plan that includes: o An explanation of how the knowledge gained from the project will be made available to the public, including the targeted market sector and potential outreach to end users, utilities, regulatory agencies, and others. o A description of the intended use(s) for and users of the project results. o Published documents, including date, title, and periodical name. o Copies of documents, fact sheets, journal articles, press releases, and other documents prepared for public dissemination. These documents must include the Legal Notice required in the terms and conditions. Indicate where and when the documents were disseminated. o A discussion of policy development. State if project has been or will be cited in government policy publications, or used to inform regulatory bodies. o The number of website downloads or public requests for project results. o Additional areas as determined by the CAM. • Conduct technology transfer activities in accordance with the Technology/Knowledge Transfer Plan. These activities will be reported in the Progress Reports. • When directed by the CAM, develop Presentation Materials for an Energy Commission- sponsored conference/workshop(s) on the project. • When directed by the CAM, participate in annual EPIC symposium(s) sponsored by the California Energy Commission. • Provide at least (6) six High Quality Digital Photographs (minimum resolution of 1300x500 pixels in landscape ratio) of pre and post technology installation at the project sites or related project photographs. • Prepare a Technology/Knowledge Transfer Report on technology transfer activities conducted during the project. • Initial Fact Sheet (draft and final) • Final Project Fact Sheet (draft and final) • Presentation Materials (draft and final) • High Quality Digital Photographs • Technology/Knowledge Transfer Plan (draft and final) • Technology/Knowledge Transfer Report (draft and final)
Specific Activities Please give detailed information about the specific activities of the Project promoter and the Partner(s), with budget allocations 7.1 The main tasks of [name of the Project Promoter], referred to as the ‘Project Promoter’, are summarized as follows: Name Project activities Project budget 1 .... [mention the budget allocated to Project Promoter for the respective activity] EUR.... Activity 2 .... EUR... 7.2 The main input/responsibilities of [name of the Project Partner(s)], referred to as Partner 1, 2, etc., are summarized as follows: Name Project activities Project budget Partner 1... [briefly present the project activity implemented by Partner]. Activity 1 .... [mention the budget allocated to Partner 1 for the respective activity] EUR.... Activity 2 .... EUR... Name Project activities Project budget
Commercial Activities Neither Contractor nor its employees shall establish any commercial activity or issue concessions or permits of any kind to Third Parties for establishing commercial activities on the Site or any other lands owned or controlled by Owner.
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.
Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES
