Outgoing Administering Authority Shadowing Sample Clauses

Outgoing Administering Authority Shadowing. 3.11.1 Either:
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
Outgoing Administering Authority Shadowing. 3.11.1 Either: (a) at least six months prior to the Handover Date where the Outgoing Administering Authority is resigning in accordance clause 7.1; or (b) no later than three months from receipt of written notice from the other Partner Authorities that they intend to replace the Administering Authority in accordance with clause 7.2, the Outgoing Administering Authority shall provide reasonable assistance to the Replacement Administering Authority to familiarise itself with the delivery of the Administering Authority Obligations and this may include reasonable information on and access to: (c) relevant facilities including assets and accommodation; (d) the Outgoing Administering Authority Personnel; (e) the Key Personnel; and (f) the following information (subject to any overriding confidentiality obligations and licence restrictions): (i) detailed system documentation; and (ii) the key provisions of more significant decisions made about the Principal Contracts that would assist the Replacement Administering Authority in undertaking its duties; and (iii) contact details for the Key Personnel and/or Outgoing Administering Authority Personnel; and (iv) information regarding any unresolved disputes and those which are likely to remain unresolved at the Handover Date, all of such information to be updated and finalised by the Outgoing Administering Authority at the Handover Date.
Sample 1
Outgoing Administering Authority Shadowing 
Sample 1

Related to Outgoing Administering Authority Shadowing

  • Appointing Authority If the grievance is not settled under Step 1, it may be formally submitted to the appointing authority. The grievance shall be submitted within seven (7) days after receipt of the written decision from Step 2 or the verbal decision of Step 1, whichever applies. Within seven (7) days after receipt of the written grievance, the appointing authority or designated representative shall meet with the employee. Within seven (7) days thereafter, a written decision shall be delivered to the employee.

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting the HUB Program at 000-000-0000 or toll-free in Texas at 0-000-000-0000.

  • Level Three - Board of Education If the aggrieved person is not satisfied with the disposition of his grievance at Level Two, or if no decision has been rendered within ten (10) school days after the presentation of the grievance to the Superintendent, he may file the grievance in writing with the Association within five (5) school days after the decision of Level Two or ten (10) school days after the grievance was presented, whichever is sooner. Within five (5) school days after receiving the written grievance, the Association shall refer it to the Board of Education through the Business Administrator/Board Secretary.

  • Board of Education a) If the unit member and the Association are not satisfied with the decision at Stage 2, the Grievance Committee will file an appeal in writing with the Board of Education within fifteen (15) school days after receiving the decision at Stage 2. The official grievance record maintained by the Superintendent of Schools shall be available for the use of the Board of Education.

  • Contracting authority The contracting authority of this public contract is Enabel, the Belgian development agency, public-law company with social purposes, with its registered office at Xxx Xxxxx 000, 0000 Xxxxxxxx xx Xxxxxxx (enterprise number 0264.814.354, RPM/RPR Brussels). Enabel has the exclusive competence for the execution, in Belgium and abroad, of public service tasks of direct bilateral cooperation with partner countries. Moreover, it may also perform other development cooperation tasks at the request of public interest organisations, and it can develop its own activities to contribute towards realisation of its objectives. For this procurement contract, Xxxxxx is represented by person(s) who shall sign the award letter and are mandated to represent the organisation towards third parties.

  • Project Manager, County The County shall appoint a Project Manager to act as liaison between the County and the Subrecipient during the term of this Contract. The County’s Project Manager shall coordinate the activities of the County staff assigned to work with the Subrecipient. The County’s Project Manager, in consultation and agreement with the County, shall have the right to require the removal and replacement of the Subrecipient’s Project Manager and key personnel. The County’s Project Manager shall notify the Subrecipient in writing of such action. The Subrecipient shall accomplish the removal within three (3) business days after written notice from the County’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Subrecipient’s Project Manager from providing further services under the Contract.

  • 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

  • Signing Authority Will the above-named Partner be able to sign contracts on behalf of the Partnership? ☐ Yes ☐ No Partner 3: with a mailing address of . a.) Ownership: %

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