Transfer Stations Report Sample Clauses

Open Split View

Download

Share

Cite

Transfer Stations Report. Contractor shall provide quarterly transfer station reports, as described in Article 4, Section 2 of this Agreement.

Sample 1

Save

Copy

Related to Transfer Stations Report

• Per-­‐Registrar Transactions Report This report shall be compiled in a comma separated-­‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-­‐transactions-­‐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 per registrar: Field # Field name Description 01 registrar-­‐name Registrar’s full corporate name as registered with IANA 02 iana-­‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-­‐ids 03 total-­‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-­‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-­‐adds-­‐1-­‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.

• 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).

• Transactions Requiring Instructions In addition to the actions requiring Proper Instructions set forth herein, upon receipt of Proper Instructions and not otherwise, Chase, directly or through the use of a Securities Depository or Book-Entry System, shall: (a) Execute and deliver to such persons as may be designated in such Proper Instructions, proxies, consents, authorizations, and any other instruments whereby the authority of the Fund as owner of any securities may be exercised; (b) Deliver any securities held for the Fund against receipt of other securities or cash issued or paid in connection with the liquidation, reorganization, refinancing, merger, consolidation or recapitalization of any issuer of securities or corporation, or the exercise of any conversion privilege; (c) Deliver any securities held for the Fund to any protective committee, reorganization committee or other person in connection with the reorganization, refinancing, merger, consolidation, recapitalization or sale of assets of any issuer of securities or corporation, against receipt of such certificates of deposit, interim receipts or other instruments or documents, and cash, if any, as may be issued to it to evidence such delivery; (d) Make such transfers or exchanges of the assets of the Fund and take such other steps as shall be stated in said instructions to be for the purpose of effectuating any duly authorized plan of liquidation, reorganization, merger, consolidation or recapitalization of the Fund; (e) Release securities belonging to the Fund to any bank or trust company for the purpose of pledge or hypothecation to secure any loan incurred by the Fund; provided, however, that securities shall be released only upon payment to Chase of the monies borrowed, or upon receipt of adequate collateral as agreed upon by the Fund and Chase which may be in the form of cash or obligations issued by the U.S. government, its agencies or instrumentalities, except that in cases where additional collateral is required to secure a borrowing already made, subject to proper prior authorization, further securities may be released for that purpose; and pay such loan upon re-delivery to it of the securities pledged or hypothecated therefore and upon surrender of the note or notes evidencing the loan; (f) Deliver securities in accordance with the provisions of any agreement among the Fund, Chase and a broker-dealer registered under the Securities Exchange Act of 1934 (the "Exchange Act") and a member of The National Association of Securities Dealers, Inc. ("NASD"), relating to compliance with the rules of The Options Clearing Corporation and of any registered national securities exchange, or of any similar organization or organizations, regarding escrow or other arrangements in connection with transactions by the Funds; (g) Deliver securities in accordance with the provisions of any agreement among the Fund, Chase and a Futures Commission Merchant registered under the Commodity Exchange Act, relating to compliance with the rules of the Commodity Futures Trading Commission and/or any Contract Market, or any similar organization or organizations, regarding account deposits in connection with transactions by the Fund; (h) Deliver securities against payment or other consideration or written receipt therefore for transfer of securities into the name of the Fund or Chase or a nominee of either, or for exchange or securities for a different number of bonds, certificates, or other evidence, representing the same aggregate face amount or number of units bearing the same interest rate, maturity date and call provisions, if any; provided that, in any such case, the new securities are to be delivered to Chase; (i) Exchange securities in temporary form for securities in definitive form; (j) Surrender, in connection with their exercise, warrants, rights or similar securities, provided that in each case, the new securities and cash, if any, are to be delivered to Chase; (k) Deliver securities upon receipt of payment in connection with any repurchase agreement related to such securities entered into by the Fund; and (l) Deliver securities pursuant to any other proper corporate purpose, but only upon receipt of, in addition to Proper Instructions, a certified copy of a resolution of the Board of Trustees or of the Executive Committee signed by an officer of the Funds and certified by the Secretary or an Assistant Secretary, specifying the securities to be delivered, setting forth the purpose for which such delivery is to be made, declaring such purpose to be a proper corporate purpose, and naming the person or persons to whom delivery of such securities shall be made.

• Calculations Respecting Mortgage Loans Calculations required to be made pursuant to this Agreement with respect to any Mortgage Loan in the Trust Fund shall be made based upon current information as to the terms of the Mortgage Loans and reports of payments received from the Mortgagor on such Mortgage Loans and payments to be made to the Securities Administrator as supplied to the Securities Administrator by the Master Servicer. The Securities Administrator shall not be required to recompute, verify or recalculate the information supplied to it by the Master Servicer or any Servicer.

• Communications Relating to Portfolio Securities Subject to the provisions of Section 2.3, the Custodian shall transmit promptly to the Fund for each Portfolio all written information (including, without limitation, pendency of calls and maturities of domestic securities and expirations of rights in connection therewith and notices of exercise of call and put options written by the Fund on behalf of the Portfolio and the maturity of futures contracts purchased or sold by the Portfolio) received by the Custodian from issuers of the securities being held for the Portfolio. With respect to tender or exchange offers, the Custodian shall transmit promptly to the Portfolio all written information received by the Custodian from issuers of the securities whose tender or exchange is sought and from the party (or his agents) making the tender or exchange offer. If the Portfolio desires to take action with respect to any tender offer, exchange offer or any other similar transaction, the Portfolio shall notify the Custodian at least three business days prior to the date on which the Custodian is to take such action.

• 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

• Information Packages As soon as available and in any event not later than two (2) Business Days prior to each Settlement Date, an Information Package as of the most recently completed Fiscal Month.

• CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.

• Monthly Reports No later than 10:00 a.m., Chicago, Illinois time, two Business Days prior to each Distribution Date, the Servicer shall deliver to the Trustees and each Rating Agency a Monthly Report.

• Remittance Reports (a) The Remittance Report for each Distribution Date shall identify the following items, in addition to the items specified in Section 4.01 of the Standard Terms: (1) the Interest Distribution Amount for each Class of the Certificates for such Distribution Date (which shall equal the Priority Interest Distribution Amount for the Corresponding Subaccount) and the Carryover Interest Distribution Amount, as well as any Writedown Interest Distribution Amount and any Carryover Writedown Interest Distribution Amount, for each Class of the Certificates for such Distribution Date, and the amount of interest of each such category to be distributed on each such Class based upon the Available Distribution Amount for such Distribution Date; (2) the amount to be distributed on such Distribution Date on each Class of the Certificates to be applied to reduce the Certificate Principal Balance of such Class (which will be equal to the amount to be allocated on such Distribution Date on the Corresponding Subaccount to be applied to reduce the Subaccount Principal Balance of such Subaccount), separately identifying any portion of such amount attributable to any prepayments, the amount to be distributed to reduce the Principal Distribution Shortfall Carryover Amount on each such Class based upon the Available Distribution Amount for such Distribution Date. (3) the aggregate amount, if any, to be distributed on the Residual Certificates; (4) the amount of any Writedown Amounts to be allocated to reduce the Certificate Principal Balance of any Class of Subordinated Certificates (which will be equal to the amount of any Writedown Amount to be allocated to the Corresponding Subaccount) on such Distribution Date; (5) the amount of the Limited Guarantee Payment Amount, if any, for such Distribution Date and the aggregate amount of any unpaid Limited Guarantee Payment Amounts for any previous Distribution Dates; (6) the Certificate Principal Balance of each Class of the Certificates (which will be equal to the Subaccount Principal Balance of the Corresponding Subaccount) and the Adjusted Certificate Principal Balance of each Class of the Offered Subordinated Certificates (which will be equal to the Adjusted Subaccount Principal Balance of the Corresponding Subaccount) after giving effect to the distributions to be made (and any Writedown Amounts to be allocated) on such Distribution Date; (7) the aggregate Interest Distribution Amount remaining unpaid, if any, and the aggregate Carryover Interest Distribution Amount remaining unpaid, if any, for each Class of Certificates (which will be equal to the Priority Interest Distribution Amount and Carryover Interest Distribution Amount remaining unpaid on the Corresponding Subaccount), after giving effect to all distributions to be made on such Distribution Date; (8) the aggregate Writedown Interest Distribution Amount remaining unpaid, if any, and the aggregate Carryover Writedown Interest Distribution Amount remaining unpaid, if any, for each Class of Certificates (which will be equal to such amounts remaining unpaid on the Corresponding Subaccount), after giving effect to all distributions to be made on such Distribution Date; and (9) the aggregate Principal Distribution Shortfall Carryover Amount remaining unpaid, if any, for each Class of Certificates, after giving effect to the distributions to be made on such Distribution Date. In the case of information furnished pursuant to clauses (1), (2) and (3) above, the amounts shall be expressed, with respect to any Class A, Class M or Class B Certificate, as a dollar amount per $1,000 denomination. (b) In addition to mailing a copy of the related Remittance Report to each Certificateholder on each Distribution Date in accordance with Section 4.01 of the Standard Terms, on each Distribution Date, the Trustee shall mail a copy of the related Remittance Report to the Underwriters (to the attention of the person, if any, reported to the Trustee by the Underwriters) and to THE BLOOMBERG (to the address and to the person, if any specified to the Trustee by Credit Suisse First Boston Corporation). The Trustee shall not be obligated to mail any Remittance Report to THE BLOOMBERG unless and until Credit Suisse First Boston Corporation shall have notified the Trustee in writing of the name and address to which such reports are to be mailed, which notice, once delivered, will be effective for all Distribution Dates after the date such notice is received by the Trustee unless and until superseded by a subsequent notice.