Staff Meetings, Activities and Functions. Staff may be required to attend regularly scheduled staff meetings and other activities as directed by the Executive Director. Such meetings, activities and functions are time worked.
Staff Meetings, Activities and Functions Sample Clauses
Related to Staff Meetings, Activities and Functions
Duties and functions 23.2.1 The Independent Engineer shall discharge its duties and functions substantially in accordance with the terms of reference set forth in Schedule 16. 23.2.2 The Independent Engineer shall submit regular periodic reports (at least once every month) to the Authority in respect of its duties and functions set forth in Schedule 16.
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.
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
Reports and Meetings A. Sub-adviser shall furnish to the Board or Adviser, or both, as appropriate, such information, reports, evaluations, analyses and opinions as are required by law or that the Board or Adviser, as appropriate, may reasonably require, including, without limitation: compliance reporting and certification with respect to: 1. Affiliated Brokerage Transactions 2. Affiliated Underwritings 3. Cross Transactions 4. Prospectus Compliance 5. Code of Ethics 6. Soft Dollar Usage 7. Price Overrides/Fair Valuation Determinations B. Sub-adviser shall make available in person to the Board and to Adviser personnel of Sub-adviser as the Board or Adviser may reasonably request to review the investments and the investment program of the Fund and the services provided by Sub-adviser hereunder.
Activities of JCM The services of JCM to the Trust hereunder are not to be deemed to be exclusive, and JCM and its affiliates are free to render services to other parties. It is understood that trustees, officers and shareholders of the Trust are or may become interested in JCM as directors, officers and shareholders of JCM, that directors, officers, employees and shareholders of JCM are or may become similarly interested in the Trust, and that JCM may become interested in the Trust as a shareholder or otherwise.
Restrictions on Business Activities There is no agreement, commitment, judgment, injunction, order or decree binding upon Company or its subsidiaries or to which Company or any of its subsidiaries is a party which has or could reasonably be expected to have the effect of prohibiting or materially impairing any business practice of Company or any of its subsidiaries, any acquisition of property by Company or any of its subsidiaries or the conduct of business by Company or any of its subsidiaries as currently conducted.
Activities of the Adviser The services of the Adviser to the Fund hereunder are not to be deemed exclusive, and the Adviser and any of its affiliates shall be free to render similar services to others. Subject to and in accordance with the Agreement and Declaration of Trust and By-Laws of the Trust and Section 10(a) of the 1940 Act, it is understood that trustees, officers, agents and shareholders of the Trust are or may be interested in the Adviser or its affiliates as directors, officers, agents or stockholders; that directors, officers, agents or stockholders of the Adviser or its affiliates are or may be interested in the Trust as trustees, officers, agents, shareholders or otherwise; that the Adviser or its affiliates may be interested in the Fund as shareholders or otherwise; and that the effect of any such interests shall be governed by said Agreement and Declaration of Trust, By-Laws and the 1940 Act.
Contract Negotiation Meetings When operational requirements permit, the Employer will grant leave without pay to an employee for the purpose of attending contract negotiation meetings on behalf of the Alliance. Preparatory Contract Negotiation Meetings
Other Business Activities of the Noteholders Each Noteholder acknowledges that each other Noteholder or its Affiliates may make loans or otherwise extend credit to, and generally engage in any kind of business with, (i) (a) the Mortgage Loan Borrower or (b) any direct or indirect parent of the Mortgage Loan Borrower or (c) any Affiliate of the Mortgage Loan Borrower or (d) any Affiliate of any direct or indirect parent of the Mortgage Loan Borrower, (ii) any entity that is a holder of debt secured by direct or indirect ownership interests in the Mortgage Loan Borrower or any Affiliate of the holder of such debt, or (iii) any entity that is a holder of a preferred equity interest in the Mortgage Loan Borrower or any Affiliate of a holder of such preferred equity (each, a “Mortgage Loan Borrower Related Party”), and receive payments on such other loans or extensions of credit to Mortgage Loan Borrower Related Parties and otherwise act with respect thereto freely and without accountability in the same manner as if this Agreement and the transactions contemplated hereby were not in effect.
NOTIFICATION OF PUBLIC EVENTS AND MEETINGS 2 A. CONTRACTOR shall notify ADMINISTRATOR of any public event or meeting funded in 3 whole or in part by the COUNTY, except for those events or meetings that are intended solely to serve 4 clients or occur in the normal course of business. 5 B. CONTRACTOR shall notify ADMINISTRATOR at least thirty (30) business days in advance 6 of any applicable public event or meeting. The notification must include the date, time, duration, 7 location and purpose of the public event or meeting. Any promotional materials or event related flyers 8 must be approved by ADMINISTRATOR prior to distribution. 9
