– Department Functions Sample Clauses

– Department Functions. Each department shall develop procedures pertaining to its areas of responsibility as set forth in this AGREEMENT. To this end, each department shall hold at least one meeting at the beginning of each academic quarter. Department meetings shall be called by the department head in a written notice with accompanying agenda to each full-time faculty member in the department. A copy of any such notice shall be sent to the appropriate Xxxx at the same time, and in the same form. Each department shall participate in college-wide registration and advising, which shall be coordinated by the appropriate xxxx. Further, each department shall be responsive to the recommendations of students, community members, other departments and units of the District, and the appropriate advisory boards regarding its course offerings and educational philosophy.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
– Department Functions. The functions of the departments are as follows:
Sample 1Sample 2Sample 3
– Department Functions. The functions of the departments are as follows: Xxxxxx communication among members of the department, between the department and other departments, and between the department and the appropriate administrator. Meet regularly to discuss department business and report recommendations to the appropriate administrator. Participate in college-wide registration and advising. Cooperate with its advisory board(s), if any. Evaluate existing departmental curriculum and course content, develop new courses, and recommend new courses and program changes to the appropriate administrator. Make recommendations regarding staff needed by the department. In accordance with Article 4, make recommendations regarding job descriptions and position qualifications for full and part-time positions. Make recommendations regarding quarterly schedules. Recommend departmental budget items to the appropriate administrator.
Sample 1

Related to – Department Functions

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

  • Mixed Functions An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

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

  • Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.

  • Departments Each teaching member shall belong to one home department. Departments of a university shall be established by the University administration with the advice of the Senate according to criteria of commonality of interest and academic purpose, without any numerical limits on size. Divisions or other major groupings of departments with some common interest may also be formed.

  • Department Chairs The release time required to perform the administrative functions of the Department Chair positions shall be deducted from the total workload of the Department Chair with no less than fifty percent (50%) of this release taken from direct instructional duties.

  • Department Responsibilities The use of sick leave may properly be denied if these procedures are not followed. Abuse of sick leave on the part of the employee is cause for disciplinary action. Departmental approval of sick leave is a certification of the legitimacy of the sick leave claim. The department head or designee may make reasonable inquiries about employee absences. The department may require medical verification for an absence of three (3) or more working days. The department may also require medical verification for absences of less than three (3) working days for probable cause if the employee had been notified in advance in writing that such verification was necessary. Inquiries may be made in the following ways:

  • Department Heads 14.5.1 Appointments to the position of Department Head shall follow the procedures set out in Article 21: Administration of Academic Sub-units.

  • Department Chairpersons The principal shall designate a high school librarian to serve as department chairperson, and such chairperson shall attend all school department chairperson meetings.

  • 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

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