FUNCTION AGENDA Sample Clauses

FUNCTION AGENDA. DAY DATE START END FUNCTION ROOM SETUP ATTD RENTAL XXXXX XXXXX XXXXX XXXXX XXXXX XXXXX XXXXX XXXXX XXXXX DOE may contract with an entity other than Hotel for audiovisual services OR (pick which one applies) The Hotel hereby agrees to provide the following audiovisual services to DOE, on the following days, at the following specified rates: Include break-down of costs for these services.
AutoNDA by SimpleDocs
FUNCTION AGENDA. Hotel agrees to provide CA Compliance School the following requested meeting space and food and beverage requirements: DAY DATE START END FUNCTION ROOM SETUP ATTD RENTAL Thursday 11/03/2020 07:00 AM 05:00 PM Meeting Mesa Room Classroom Style 9 $600.00 Friday 11/04/2020 07:00 AM 05:00 PM Meeting Mesa Room Classroom Style 9 $600.00 Saturday 11/05/2020 07:00 AM 05:00 PM Meeting Mesa Room Classroom Style 9 $600.00

Related to FUNCTION AGENDA

  • 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

  • Local Negotiating Committee (a) A negotiating committee of four (4) employee representatives appointed by the union including the bargaining unit president.

  • Administrative Functions Include any or a combination of: liaising with other departments on work flows and other matters; participating in interdepartmental meetings; coordinating transactions with external agencies on behalf of department; formulating and updating departmental procedures; recommending changes to Administration; compiling statistical reports on departmental activity. Administrative Levels Duties First level: As listed above. Second level: Participates in development and monitoring of departmental budget.

  • Agenda The co-chairs will meet seven (7) days prior to each meeting to exchange agendas for that meeting. The items in the agendas will be listed in order of priority. The Company will arrange to have both agendas typed and distributed to Committee members prior to the meeting. Items from the agendas will be discussed at the meeting on an alternating basis with the first item being taken from either the Company's or the Union's agenda, depending on which party is chairing the meeting. Items not addressed at a meeting may be re-proposed for the next meeting's agendas. Emergency items arising after the agendas are prepared can be entertained on the agreement of the parties at the outset of the meeting. An item on the agendas may be disposed of by referral to a more appropriate forum or cancelled, by mutual agreement of the parties. The Union Representative who will be responsible for proposing the next list of Union agenda items will be identified at the conclusion of each meeting.

  • Function of Bargaining Committee All matters pertaining to performance of work, operational problems, rates of pay, hours of work, collective bargaining, and other working conditions, shall be referred by the Union bargaining committee to the Employer for discussion and settlement.

  • Project Steering Committee (a) The Recipient shall establish and maintain at all times until the completion of the Project, the Project Steering Committee with a composition, mandate and resources satisfactory to the Association.

  • Function of Committee The Committee shall concern itself with the following general matters:

  • Primary Function (a) The primary function of the troubleshooter shall be to address concerns of bargaining unit employees who seek a determination of their employment status (an employee of regular status or an employee of auxiliary status) pursuant to the terms of this Collective Agreement.

  • Joint Steering Committee [***] following the Effective Date [***], a joint steering committee (the “JSC”) will be established by the Parties to provide oversight and to facilitate information sharing between the Parties with respect to the activities under this Agreement.

  • Meeting Agenda 6.1 The Co-chairpersons will prepare an agenda and forward a copy of the agenda to all Joint Committee members at least one week in advance of the meeting (sample attached).

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