Geological and archaeological finds It is expressly agreed that mining, geological or archaeological rights do not form part of this Agreement with the Contractor for the Works, and the Contractor hereby acknowledges that it shall not have any mining rights or interest in the underlying minerals, fossils, antiquities, structures or other remnants or things either of particular geological or archaeological interest and that such rights, interest and property on or under the Site shall vest in and belong to the Authority or the concerned Government Instrumentality. The Contractor shall take all reasonable precautions to prevent its workmen or any other person from removing or damaging such interest or property and shall inform the Authority forthwith of the discovery thereof and comply with such instructions as the concerned Government Instrumentality may reasonably give for the removal of such property. For the avoidance of doubt, it is agreed that any reasonable expenses incurred by the Contractor hereunder shall be reimbursed by the Authority. It is also agreed that the Authority shall procure that the instructions hereunder are issued by the concerned Government Instrumentality within a reasonable period.
PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:
List of Operator’s Subprocessors [Box 26] [Box 27] [Box 28] [Box 29]
Quarterly Contractor Performance Reporting Customers shall complete a Contractor Performance Survey (Exhibit I) for each Contractor on a Quarterly basis. Customers will electronically submit the completed Contractor Performance Survey(s) to the Department Contract Manager no later than the due date indicated in Contract Exhibit D, Section 17, Additional Special Contract Conditions. The completed Contractor Performance Survey(s) will be used by the Department as a performance-reporting tool to measure the performance of Contractors. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MyFloridaMarketPlace or on the Department's website).
REPORT ON CONTRACT SALES ACTIVITY AND ADMINISTRATIVE FEE PAYMENT A. CONTRACT SALES ACTIVITY REPORT. Each calendar quarter, Supplier must provide a contract sales activity report (Report) to the Sourcewell Supplier Development Administrator assigned to this Contract. Reports are due no later than 45 days after the end of each calendar quarter. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Supplier must submit a report indicating no sales were made). The Report must contain the following fields: • Participating Entity Name (e.g., City of Staples Highway Department); • Participating Entity Physical Street Address; • Participating Entity City; • Participating Entity State/Province; • Participating Entity Zip/Postal Code; • Participating Entity Contact Name; • Participating Entity Contact Email Address; • Participating Entity Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Supplier.
B. ADMINISTRATIVE FEE. In consideration for the support and services provided by Sourcewell, the Supplier will pay an administrative fee to Sourcewell on all Equipment, Products, and Services provided to Participating Entities. The Administrative Fee must be included in, and not added to, the pricing. Supplier may not charge Participating Entities more than the contracted price to offset the Administrative Fee. The Supplier will submit payment to Sourcewell for the percentage of administrative fee stated in the Proposal multiplied by the total sales of all Equipment, Products, and Services purchased by Participating Entities under this Contract during each calendar quarter. Payments should note the Supplier’s name and Sourcewell-assigned contract number in the memo; and must be mailed to the address above “Attn: Accounts Receivable” or remitted electronically to Sourcewell’s banking institution per Sourcewell’s Finance department instructions. Payments must be received no later than 45 calendar days after the end of each calendar quarter. Supplier agrees to cooperate with Sourcewell in auditing transactions under this Contract to ensure that the administrative fee is paid on all items purchased under this Contract. In the event the Supplier is delinquent in any undisputed administrative fees, Sourcewell reserves the right to cancel this Contract and reject any proposal submitted by the Supplier in any subsequent solicitation. In the event this Contract is cancelled by either party prior to the Contract’s expiration date, the administrative fee payment will be due no more than 30 days from the cancellation date.
Proprietary Information and Developments 9.1 The Consultant will not at any time, whether during or after the termination of this Agreement for any reason, reveal to any person or entity any of the trade secrets or confidential information concerning the organization, business or finances of the Company or of any third party which the Company is under an obligation to keep confidential, except as may be required in the ordinary course of performing the Consultant Services to the Company, and the Consultant shall keep secret such trade secrets and confidential information and shall not use or attempt to use any such secrets or information in any manner which is designed to injure or cause loss to the Company. Trade secrets or confidential information shall include, but not be limited to, the Company's financial statements and projections, expansion proposals, property acquisition opportunities and business relationships with banks, lenders and other parties not otherwise publicly available.
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
CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11164 et seq. and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.
