Administrator Reporting Functions Sample Clauses

Administrator Reporting Functions. Administrator shall create and distribute program reports to PIHP and/or, CMHSP Members for those functions in which the Administrator assumes delegated responsibility in accordance with scope specified in Exhibit I Delegation Grid. Administrator will not assume responsibility for MDHHS required program report assembly, creation or submission. Administrator will provide PIHP and Member CMHSPs with data in a timely manner and within required timeframes for the creation of required reports that must include information from the Administrator.
AutoNDA by SimpleDocs

Related to Administrator Reporting Functions

  • CERTIFYING FUNCTION Department of Information Resources acting as the owner of the DIR Contracts hereby certifies the eligibility of the DIR Customer to use the DIR Contracts.

  • MANAGEMENT FUNCTIONS 6.01 The Union acknowledges that it is the exclusive function of the Employer to:

  • Primary Function The primary function of the Program Manager is to provide strategic guidance and direction to the Project Team and to manage the Project on behalf of the Owner. Program Manager agrees that the services provided by the Program Manager are intended to coordinate and complement the activities of the Project Team, but not to diminish, alter or substitute for any of the services, authority, obligations or responsibilities being provided by the Design Professional and CM/GC under their respective contracts. Nothing herein shall be deemed to impose upon the Program Manager any responsibilities to provide any services constituting the practice of architecture, engineering, or any related design profession, or to provide any services constituting construction or means and methods of construction. The Program Manager should seek to exercise its authority through sound principles of leadership and persuasion to achieve effective coordination of the design and construction of the Project. The Program Manager should use its authority to direct the activities of the Design Professional and CM/GC within the requirements of their respective contracts; or in unusual or ambiguous situations, after consultation with the Owner and under the specific direction of the Owner.

  • Administrator Compliance Statement On or before ninety (90) days after the end of each fiscal year, commencing with the fiscal year ended March 31st immediately following the Closing Date, the Administrator shall deliver to the Issuer a statement of compliance addressed to the Issuer and signed by an authorized officer of the Administrator to the effect that (i) a review of the Administrator’s activities during the immediately preceding reporting year (or applicable portion thereof) and of its performance under this Agreement during such period has been made under such officer’s supervision, and (ii) to the best of such officer’s knowledge, based on such review, the Administrator has fulfilled all of its obligations under this Agreement in all material respects throughout such reporting year (or applicable portion thereof) or, if there has been a failure to fulfill any such obligation in any material respect, specifically identifying each such failure known to such officer and the nature and the status thereof. If the Administrator is the same party as the Servicer, such party’s compliance with Section 3.11(a) of the Sale and Servicing Agreement will satisfy the Administrator’s obligations set forth in this Section 1.21(b).

  • 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: Field # Field Name Description 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

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • EDD Independent Contractor Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the state.” The term is further defined by the California Employment Development Department to refer specifically to independent Contractors. An independent Contractor is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm

  • Nondiscretionary Functions The Custodian shall attend to all nondiscretionary details in connection with the sale, exchange, substitution, purchase, transfer or other dealings with securities or other assets of each Portfolio held by the Custodian, except as otherwise directed from time to time pursuant to Proper Instructions.

  • Training Fund Employers and/or individuals who manage, operate, assist or own, either partially or wholly, a company or companies working non-union in the construction industry on Mainland Nova Scotia within the craft jurisdiction of xxx Xxxxxxxxxx Local 83 shall not be eligible to be appointed to serve, or to continue to serve, as trustees on any trust fund referred to within this Collective Agreement. This provision shall apply to management trustees and union trustees alike.

  • Additional Reporting Under Regulation AB With respect to any period during which the Trust is subject to the reporting requirements of the Exchange Act, the Mortgage Loan Seller shall provide to the Depositor and the Certificate Administrator any information that constitutes “Additional Form 10-D Information” or “Additional Form 10-K Information” but only if and to the extent that the Mortgage Loan Seller (or any originator of the Mortgage Loans sold by the Mortgage Loan Seller to the Depositor, if such originator constitutes an “originator” contemplated by Item 1110(b) of Regulation AB and such information is required to be reported with respect to such originator) is the applicable “Party Responsible” (solely in its capacity as a sponsor or originator (or as successor in interest to any predecessor originator), within the meaning of Regulation AB, of any Mortgage Loans) under the terms of Schedule V or Schedule VI to the Pooling and Servicing Agreement (it being acknowledged that the Mortgage Loan Seller (solely as in its capacity as a sponsor or originator (or as successor in interest to any predecessor originator), within the meaning of Regulation AB, of any Mortgage Loans) does not constitute the “Party Responsible” for any “Form 8-K Information” set forth on Schedule VII of the Pooling and Servicing Agreement). In each case, such delivery shall be made in a form readily convertible to an XXXXX compatible form, or in such other form as otherwise agreed by the Depositor, the Certificate Administrator and the Mortgage Loan Seller. In each case, such delivery shall be made not later than 5 calendar days after the related Distribution Date (in the case of any such “Additional Form 10-D Information”), and no later than March 7th of each year subsequent to the fiscal year that the Trust is subject to the Exchange Act reporting requirements (in the case of any such “Additional Form 10-K Information”). In no event shall the Mortgage Loan Seller be required to provide any information that is not required to be reported on Form 10-D or Form 10-K, as the case may be, under the Exchange Act and the rules and regulations of the Securities and Exchange Commission thereunder.

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