REPORTING OF ACCIDENTS The Contractor shall report to the Engineer details of any accident as soon as possible after its occurrence. In the case of any fatality or serious accident, the Contractor shall, in addition, notify the Engineer immediately by the quickest available means. The Contractor shall also notify the relevant authority whenever the Laws of Kenya require such a report.
Reporting of Compliance Matters (a) The Sub-Adviser shall promptly provide to the Trust’s Chief Compliance Officer (“CCO”) the following documents: (i) copies of all SEC examination correspondences, including correspondences regarding books and records examinations and “sweep” examinations, issued during the term of this Agreement, in which the SEC identified any concerns, issues or matters (such correspondences are commonly referred to as “deficiency letters”) relating to any aspect of the Sub-Adviser’s investment advisory business and the Sub-Adviser’s responses thereto; (ii) a report of any material violations of the Sub-Adviser’s Compliance Program or any “material compliance matters” (as such term is defined in Rule 38a-1 under the 0000 Xxx) that have occurred with respect to the Sub-Adviser’s Compliance Program; (iii) a report of any material changes to the policies and procedures that compose the Sub-Adviser’s Compliance Program; (iv) a copy of the Sub-Adviser’s chief compliance officer’s report (or similar document(s) which serve the same purpose) regarding his or her annual review of the Sub-Adviser’s Compliance Program, as required by Rule 206(4)-7 under the Advisers Act; and (v) an annual (or more frequently as the Trust’s CCO may reasonably request) representation regarding the Sub-Adviser’s compliance with Paragraphs 7 and 8 of this Agreement. (b) The Sub-Adviser shall also provide the Trust’s CCO with: (i) reasonable access to the testing, analyses, reports and other documentation, or summaries thereof, that the Sub-Adviser’s chief compliance officer relies upon to monitor the effectiveness of the implementation of the Sub-Adviser’s Compliance Program; and (ii) reasonable access, during normal business hours, to the Sub-Adviser’s facilities for the purpose of conducting pre-arranged on-site compliance related due diligence meetings with personnel of the Sub-Adviser.
Reporting of Sales to TIPS by Vendor The Participation Fee that was published as part of the Solicitation and the fee published is the legally effective fee, along with any fee conditions stated in the Solicitation. Collection of the fees by TIPS is required under Texas Government Code §791.011 Et seq. Fees are due on all TIPS purchases reported by either Vendor or Member. Fees are due to TIPS upon payment by the Member to the Vendor, Reseller or Vendor Assigned Dealer. Vendor, Reseller or Vendor Assigned Dealer agrees that the participation fee is due to TIPS for all Agreement sales immediately upon receipt of payment including partial payment, from the Member Entity and must be paid to TIPS at least on a monthly basis, specifically within 31 calendar days of receipt of payment, if not more frequently, or as otherwise agreed by TIPS in writing and signed by an authorized signatory of TIPS. Thus, when an awarded Vendor, Reseller or Vendor Assigned Dealer receives any amount of payment, even partial payment, for a TIPS sale, the legally effective fee for that amount is immediately due to TIPS from the Vendor and fees due to TIPS should be paid at least on a monthly basis, specifically within 31 calendar days of receipt of payment, if not more frequently. Vendor is required to report all sales under the TIPS contract to TIPS. When a public entity initiates a purchase with a TIPS Awarded Vendor, if the Member inquires verbally or in writing whether the Vendor holds a TIPS Contract, it is the duty of the Vendor to verify whether or not the Member is seeking a TIPS purchase. Once verified, the Vendor must include the TIPS Contract number on any communications and related sales documents exchanged with the TIPS Member entity. To report sales, the Vendor must login to the TIPS Vendor Portal online at xxxxx://xxx.xxxx-xxx.xxx/vendors_form.cfm and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS. Failure to render the participation fee to TIPS shall constitute a breach of this agreement with our parent governmental entity, Texas Education Service Center Region 8, as established by the Texas legislature and shall be grounds for termination of this agreement and any other agreement held with TIPS and possible legal action. Any overpayment of participation fees to TIPS by a Vendor will be refunded to the Vendor within ninety (90) days of receipt of notification if TIPS receives written notification of the overpayment not later than the expiration of six (6) months from the date of overpayment and TIPS determines that the amount was not legally due to TIPS pursuant to this agreement and applicable law. It is the Vendor’s responsibility to identify which sales are TIPS Agreement sales and pay the correct participation fee due for TIPS Agreement sales. Any notification of overpayment received by TIPS after the expiration of six (6) months from the date of overpayment will be non-refundable. Region 8 ESC and TIPS reserve the right to extend the six (6) month deadline to notify if approved by the Region 8 ESC Board of Directors. TIPS reserves all rights under the law to collect the fees due. Please contact TIPS at xxxx@xxxx-xxx.xxx or call (000) 000-0000 if you have questions about paying fees.
Reporting of Reportable Events If Xxxxx determines (after a reasonable opportunity to conduct an appropriate review or investigation of the allegations) through any means that there is a Reportable Event, Xxxxx shall notify OIG, in writing, within 30 days after making the determination that the Reportable Event exists.
Board and Filings Information The Adviser will also provide the Trust with any information reasonably requested regarding its management of the Funds required for any meeting of the Board, or for any shareholder report, amended registration statement, proxy statement, or prospectus supplement to be filed by the Trust with the Commission. The Adviser will make its officers and employees available to meet with the Board from time to time on due notice to review its investment management services to the Funds in light of current and prospective economic and market conditions and shall furnish to the Board such information as may reasonably be necessary in order for the Board to evaluate this Agreement or any proposed amendments thereto.
Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 ARTICLE VII BLV/BLVI TRAFFIC 16 7.1 Busy Line Verification 16 7.2 Busy Line Verification Interrupt 16 7.3 BLV/BLVI Traffic 16 7.4 BLV/BLVI Compensation 16
Transactions Requiring Disclosure to FINRA 2.17.1 Finder’s Fees. There are no claims, payments, arrangements, agreements or understandings relating to the payment of a finder’s, consulting or origination fee by the Company or any Insider with respect to the sale of the Securities hereunder or any other arrangements, agreements or understandings of the Company or to the Company’s knowledge, assuming reasonable inquiry, any Insider that may affect the Underwriters’ compensation, as determined by FINRA.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
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
Research Independence The Company acknowledges that each Underwriter’s research analysts and research departments, if any, are required to be independent from their respective investment banking divisions and are subject to certain regulations and internal policies, and that such Underwriter’s research analysts may hold and make statements or investment recommendations and/or publish research reports with respect to the Company and/or the offering that differ from the views of its investment bankers. The Company hereby waives and releases, to the fullest extent permitted by law, any claims that the Company may have against such Underwriter with respect to any conflict of interest that may arise from the fact that the views expressed by their independent research analysts and research departments may be different from or inconsistent with the views or advice communicated to the Company by such Underwriter’s investment banking divisions. The Company acknowledges that the Representative is a full service securities firm and as such from time to time, subject to applicable securities laws, may effect transactions for its own account or the account of its customers and hold long or short position in debt or equity securities of the Company.
