REPORT DELIVERY PROTOCOL Sample Clauses

REPORT DELIVERY PROTOCOL. The Company agrees that all Proceeds to be reported and remitted to a Signatory State pursuant to this Agreement shall be reported by the Company to a Signatory State with a notation indicating that the report is made pursuant to the Audit, and shall be remitted by the Company to the Signatory State either through Verus or in accordance with Verus’ instructions. Further, the Company agrees that it shall provide to Verus a copy of all such reports and remittances. The Company also agrees that no Proceeds to be reported and remitted to a Signatory State pursuant to this Agreement shall be included in any annual filings or any supplemental filings made by the Company to the Signatory States. Nothing in this Agreement, however, shall prohibit the Company from identifying and remitting Proceeds to a Beneficiary if permitted or required by a Signatory State’s UP Laws. At such time as the Company provides notice of remittance to a Beneficiary under a Signatory State’s UP Laws, the Company shall provide a copy of the notice of remittance to Verus. The Signatory State and Verus shall have access to all relevant records documenting the identification of the Beneficiary and the remittance of Proceeds pursuant to this Section. Verus and the Company mutually agree to deliver all notices and reports required under the Agreement according to the following protocols. Reports provided to the Company shall be delivered in electronic, encrypted, password protected, unlocked (to permit sorting) Excel format (or such other format as Verus and the Company mutually agree in writing) to Xxxxx Xxxxx at Transamerica. The Company may designate in writing to Verus one or more persons to receive such reports instead of Xxxxx Xxxxx at Transamerica. Reports provided to Verus shall be delivered in electronic, encrypted, password protected, unlocked (to permit sorting) Excel format (or such other format as Verus and the Company mutually agree in writing) to Xx. Xxxxxx Xxxxx, at xxxxxx@xxxxxxxxxxxxxx.xxx. Where Verus is to provide notice to a Signatory State under Section D of the Agreement or this Schedule D, the date of notice is the date on which notice is sent by Verus. Where a Signatory State is to provide notice or a report to the Company under Section D of the Agreement or this Schedule D, the date of notice is the date on which notice is sent by the Signatory State to the Company. Report delivery protocol questions, issues, concerns, or disputes shall, in the first instance, be add...
Sample 1
AutoNDA by SimpleDocs

Related to REPORT DELIVERY PROTOCOL

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • ELECTRICITY INFORMATION EXCHANGE PROTOCOLS 31.1 Protocols for exchanging information: The Distributor and the Trader must, when exchanging information to which an EIEP listed in Schedule 3 relates, comply with that EIEP.

  • REPORT SUBMISSION 1. Copies of reporting packages for audits conducted in accordance with 2 CFR Part 200, Subpart F-Audit Requirements, and required by PART I of this form shall be submitted, when required by 2 CFR 200.512, by or on behalf of the recipient directly to the Federal Audit Clearinghouse (FAC) as provided in 2 CFR 200.36 and 200.512

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Benchmarking Report For the purposes of this Framework Schedule 12 “

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Protocol No action to coerce or censor or penalize any negotiation participant shall be made or implied by any other member as a result of participation in the negotiation process.

  • Metering Data At Developer’s expense, the metered data shall be telemetered to one or more locations designated by Connecting Transmission Owner, Developer and NYISO. Such telemetered data shall be used, under normal operating conditions, as the official measurement of the amount of energy delivered from the Large Generating Facility to the Point of Interconnection.

Time is Money Join Law Insider Premium to draft better contracts faster.