CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.
MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to:
(a) maintain order, discipline and efficiency;
(b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided;
(c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service;
(d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith;
(e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement.
B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.
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
Operations Support Systems Functions 9.1 Effective as of February 8, 2021, notwithstanding any other term or condition of the Amended Agreement or a Verizon tariff or SGAT, and subject to the transitional provisions set forth in Subsection 9.2 below, unbundled access to Operations Support Systems Functions will not be available from Verizon on or after February 8, 2021, except when such functions are used to manage other UNEs that remain available from Verizon, local interconnection, or local number portability.
9.2 Any unbundled access to Operations Support System Functions eliminated pursuant to Section 9.1 above will continue to be provisioned for the period in which unbundled access is available to the UNE managed through the use of such functions, but not after such period.
Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden.
a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs.
b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources.
c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.
Amendments Concerning Agency Function The Agent shall not be bound by any waiver, amendment, supplement or modification of this Agreement or any other Facility Document which affects its duties hereunder or thereunder unless it shall have given its prior consent thereto.
Enterprise Information Management Standards Performing Agency shall conform to HHS standards for data management as described by the policies of the HHS Chief Data and Analytics Officer. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.
Meeting and Function Rooms to be Provided A. The Contractor shall provide to the Judicial Council the meeting and function rooms on the Dates and at the times set forth in Table 1, below, including necessary and appropriate set up. Prior to the Program, the Judicial Council will provide one
(1) or more BEO’s to the Contractor setting forth the final detail on these items. Date1 2:00pm – 24 hours Meeting Planning Office Boardroom 2 2:00pm – 24 hours Staff Office 1 rounds of 5, 4 6’ tables 5 2:00pm – 24 hours AV Storage 1 6’ table with 2 chairs 2 Date2 24 hours Meeting Planning Office Boardroom 2 24 hours Staff Office 1 rounds of 5, 4 6’ tables 5 24 hours AV Storage 1 6’ table with 2 chairs 2 6:00am – 24 hours Faculty Room Conference 6 6:00am – 24 hours Registration 2 6’ table with 2 chairs Flow 5:00am - 24 hours General Session Crescent Rounds of 5 92 6:00am – 24 hours Breakout #1 Crescent Rounds of 5 23 Date Time Function Location Set Up Expected Attendance 6:00am – 24 hours Breakout #2 Crescent Rounds of 5 23 6:00am – 24 hours Breakout #3 Crescent Rounds of 5 23 6:00am – 24 hours Breakout #4 Crescent Rounds of 5 23 Date3 24 hours Meeting Planning Office Boardroom 2 24 hours Staff Office 1 rounds of 5, 4 6’ tables 5 24 hours AV Storage 1 6’ table with 2 chairs 2 24 hours Faculty Room Conference 6 24 hours Registration / materials table 2 6’ table with 2 chairs Flow 24 hours General Session Crescent Rounds of 5 92 24 hours Breakout #1 Crescent Rounds of 5 23 24 hours Breakout #2 Crescent Rounds of 5 23 24 hours Breakout #3 Crescent Rounds of 5 23 24 hours Breakout #4 Crescent Rounds of 5 23 24 hours Breakfast/ Lunch room with speaker Rounds of 9-10 118 Date4 24 hours- 4:00pm Office 1 rounds of 5, 4 6’ tables 5 24 hours AV Storage 1 6’ table with 2 chairs 2 24 hours- 12:00pm Faculty Room Conference 6 24 hours- 1:00pm Registration / materials table 2 6’ table with 2 chairs Flow 5:00am - 24 hours General Session Crescent Rounds of 5 92 6:00am – 24 hours Breakout #1 Crescent Rounds of 5 23 24 hours- 6:00pm Breakout #2 Crescent Rounds of 5 23 24 hours- 6:00pm Breakout #3 Crescent Rounds of 5 23 24 hours - 6:00pm Breakout #4 Crescent Rounds of 5 23 24 hours- 10:00amm Breakfast room Rounds of 9-10 118 Date5 24 hours- 10:00am AV Storage 1 6’ table with 2 chairs 2
B. Upon reasonable Notice to the Contractor, the Judicial Council may change the Program function, meeting times, room configurations, number of meeting and function rooms, and the numbers of Attendees attending these functions and meetings.
C. The Contractor shall assure that the meeting and function rooms are maintained between sixty-eight degrees (68°) and seventy-four degrees (74°) Fahrenheit during all meeting and function sessions of the Program.
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.
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.
