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.
Commercially Useful Function A prime consultant can credit expenditures to a DBE subconsultant toward DBE goals only if the DBE performs a Commercially Useful Function (CUF). A DBE performs a CUF when it is responsible for execution of the work of a contract and carries out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the DBE must also be responsible, with respect to materials and supplies on the contract, for negotiating price, determining quality and quantity, ordering the material, and installing (where applicable) and paying for the material itself that it uses on the project. To determine whether a DBE is performing a commercially useful function, the Department will evaluate the amount of work subcontracted, industry practices, whether the amount the firm is to be paid under the contract is commensurate with the work it is actually performing and the DBE credit claimed for its performance of the work, and other relevant factors. A DBE will not be considered to perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of DBE participation. In determining whether a DBE is such an extra participant, the Department will examine similar transactions, particularly those in which DBEs do not participate. If a DBE does not perform or exercise responsibility for at least 30 percent of the total cost of its contract with its own work force, or if the DBE subcontracts a greater portion of the work of a contract than would be expected on the basis of normal industry practice for the type of work involved, the Department will presume that the DBE is not performing a commercially useful function. When a DBE is presumed not to be performing a commercially useful function as provided above, the DBE may present evidence to rebut this presumption. The Department will determine if the firm is performing a CUF given the type of work involved and normal industry practices. The Department will notify the consultant, in writing, if it determines that the consultant’s DBE subconsultant is not performing a CUF. The consultant will be notified within seven calendar days of the Department’s decision. Decisions on CUF may be appealed to the ADOT State Engineer. The appeal must be in writing and personally delivered or sent by certified mail, return receipt requested, to the State Engineer. The appeal must be received by the State Engineer no later than seven calendar days after the decision of XXXX. XXXX’s decision remains in place unless and until the State Engineer reverses or modifies BECO’s decision. ADOT State Engineer will promptly consider any appeals under this subsection and notify the consultant of ADOT’s State Engineer findings and decisions. Decisions on CUF matters are not administratively appealable to USDOT. The BECO may conduct project site visits on the contract to confirm that DBEs are performing a CUF. The consultant shall cooperate during the site visits and the BECO’s staff will make every effort not to disrupt work on the project.
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
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.
Submission of Grievance Information a. Upon appointment of the arbitrator, the appealing party shall, within five (5) days after notice of appointment, forward to the arbitrator, with a copy to the School Board, the submission of the grievance which shall include the following:
1. The issues involved.
2. Statement of the facts.
3. Position of the grievant.
4. The written documents relating to Section 5 of the grievance procedure.
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.
Succession; Sub-Servicers; Subcontractors (a) For so long as the Trust or any Other Securitization Trust is subject to the reporting requirements of the Exchange Act (in addition to any requirements contained in Section 10.07 of this Agreement), in connection with the succession to the Master Servicer, the Special Servicer or any Sub-Servicer as servicer or sub-servicer (to the extent such Sub-Servicer is a “servicer” as contemplated by Item 1108(a)(2) of Regulation AB) or succession to the Certificate Administrator under this Agreement by any Person (i) into which the Master Servicer, the Special Servicer, such Sub-Servicer or Certificate Administrator may be merged or consolidated, or (ii) which may be appointed as a successor to the Master Servicer, the Special Servicer, any such Sub-Servicer or Certificate Administrator, the Certificate Administrator (or, in the case of a successor to the Certificate Administrator, the Trustee) shall provide to the Depositor, as well as any Other Depositor as to which the applicable Companion Loan is affected, at least five (5) Business Days prior to the effective date of such succession or appointment as long as such disclosure prior to such effective date would not be violative of any applicable law or confidentiality agreement, otherwise no later than one (1) Business Day after such effective date, (x) written notice to the Depositor and each such Other Depositor of such succession or appointment and (y) in writing and in form and substance reasonably satisfactory to the Depositor and each such Other Depositor, all information relating to such successor (which such successor Master Servicer, Special Servicer, Sub-Servicer or Certificate Administrator shall be required to provide) reasonably requested by the Depositor or any such Other Depositor in order to comply with its reporting obligation under Item 6.02 of Form 8-K pursuant to the Exchange Act (if such reports under the Exchange Act are required to be filed under the Exchange Act). The Certificate Administrator (or the Trustee, if applicable) shall provide similar notice to the Depositor and each such Other Depositor in connection with any resignation or termination of the Master Servicer, the Special Servicer, any Sub-Servicer or the Certificate Administrator. In addition, with respect to each Serviced Companion Loan, the Certificate Administrator shall comply with the Trust’s obligations under each Co-Lender Agreement (including with respect to the provision of any required notices) in connection with any resignation, termination, replacement or appointment of the Master Servicer, the Special Servicer, any Sub-Servicer or the Certificate Administrator or any successor thereto.
(b) For so long as the Trust or any Other Securitization Trust is subject to the reporting requirements of the Exchange Act, if the Master Servicer, the Special Servicer, any Sub-Servicer, the Custodian, the Trustee and the Certificate Administrator (each of the Master Servicer, the Special Servicer, the Custodian, the Trustee and the Certificate Administrator and each Sub-Servicer, for purposes of this Section 10.02(b), Section 10.02(c), Section 10.02(d) and Section 10.17, a “Servicer”) utilizes one or more Subcontractors to perform certain of its obligations hereunder, such Servicer shall promptly upon request provide to the Depositor, as well as any Other Depositor as to which the applicable Serviced Companion Loan is affected, a written description (in form and substance satisfactory to the Depositor and each such Other Depositor) of the role and function of each Subcontractor that is a Servicing Function Participant utilized by such Servicer during the preceding calendar year, specifying (i) the identity of such Subcontractor, and (ii) which elements of the Servicing Criteria will be addressed in assessments of compliance provided by each such Subcontractor. Each Servicer shall cause any Subcontractor determined to be a Servicing Function Participant used by such Servicer for the benefit of the Depositor to comply with the provisions of Section 10.09 and Section 10.10 of this Agreement to the same extent as if such Subcontractor were such Servicer. Such Servicer shall obtain from each such Subcontractor (or, in the case of each Sub-Servicer set forth on Exhibit S, shall use commercially reasonable efforts to cause such Sub-Servicer) and deliver to the applicable Persons any assessment of compliance report and related accountant’s attestation required to be delivered by such Subcontractor under Section 10.09 and Section 10.10 of this Agreement, in each case, as and when required to be delivered.
(c) For so long as the Trust or any Other Securitization Trust is subject to the reporting requirements of the Exchange Act, notwithstanding the foregoing, if a Servicer engages a Subcontractor in connection with the performance of any of its duties under this Agreement, such Servicer shall be responsible for determining whether such Subcontractor is a “servicer” within the meaning of Item 1101 of Regulation AB and whether such Subcontractor meets the criteria in Item 1108(a)(2)(i), (ii) or (iii) of Regulation AB. If a Servicer determines, pursuant to the preceding sentence, that such Subcontractor is a “servicer” within the meaning of Item 1101 of Regulation AB and meets the criteria in Item 1108(a)(2)(i), (ii) or (iii) of Regulation AB, then the engagement of such Subcontractor shall not be effective unless and until notice is given to the Depositor and the Certificate Administrator, as well as any Other Depositor as to which the applicable Companion Loan is affected, of any such Subcontractor and sub-servicing agreement and, if such Subcontractor is engaged by the Master Servicer or the Special Servicer, such Subcontractor shall be deemed to be a Sub-Servicer for purposes of this Agreement. Written notice of the engagement of such Subcontractor and the related Sub-Servicing Agreement (other than such agreements set forth on Exhibit S hereto) (with respect to the Master Servicer or the Special Servicer) or sub-servicing agreement (with respect to any other Servicer) shall be delivered to the Depositor, the Certificate Administrator and each such Other Depositor at least five (5) Business Days prior to the effective date of such engagement. Such notice shall contain all information reasonably necessary, and in such form as may be necessary, to enable the Certificate Administrator, as well as any Other Exchange Act Reporting Party as to which the applicable Serviced Companion Loan is affected, to accurately and timely report the event under Item 6.02 of Form 8-K pursuant to Section 10.07 of this Agreement (if such reports under the Exchange Act are required to be filed under the Exchange Act).
(d) For so long as the Trust or any Other Securitization Trust is subject to the reporting requirements of the Exchange Act, notwithstanding the foregoing and subject to Section 3.01(c) of this Agreement, if the Master Servicer or the Special Servicer engages a Sub-Servicer or if any other Servicer engages a sub-servicer, in each case, in connection with the performance of any of the duties of the Master Servicer, the Special Servicer or such other Servicer, as applicable, under this Agreement and the related Sub-Servicing Agreement (with respect to the Master Servicer or the Special Servicer) or sub-servicing agreement (with respect to any other Servicer) is either (i) assigned (other than, in the case of a Sub-Servicer engaged by the Master Servicer, an assignment to the Master Servicer) or (ii) amended or modified and the Master Servicer, the Special Servicer or such other Servicer, as applicable, determines that, as a result of such amendment or modification, the Sub-Servicer or sub-servicer, as applicable, would become a “servicer” within the meaning of Item 1101 of Regulation AB that (1) meets the criteria in Item 1108(a)(2)(i), (ii) or (iii) of Regulation AB or (2) meets the criteria in Item 1108(a)(2)(iii) of Regulation AB and services 20% or more of the pool assets, then the Master Servicer, the Special Servicer or such other Servicer, as applicable, shall provide written notice of such amendment, modification or assignment to the Depositor and the Certificate Administrator, as well as any Other Depositor as to which the applicable Companion Loan is affected at least five (5) Business Days prior to the effective date of such amendment, modification or assignment (or if such prior notice would be violative of applicable law or any applicable confidentiality agreement, no later than the time required under Section 10.07 of this Agreement). Such notice shall contain all information reasonably necessary, and in such form as may be necessary, to enable the Certificate Administrator, as well as any Other Exchange Act Reporting Party as to which the applicable Serviced Companion Loan is affected, to accurately and timely report the event under Item 6.02 of Form 8-K pursuant to Section 10.07 of this Agreement (if such reports under the Exchange Act are required to be filed under the Exchange Act).
(e) For so long as the Trust or any Other Securitization Trust is subject to the reporting requirements of the Exchange Act, in connection with the succession to the Trustee or Certificate Administrator under this Agreement by any Person (i) into which the Trustee or Certificate Administrator may be merged or consolidated, or (ii) which may be appointed as a successor to the Trustee or Certificate Administrator, the Trustee or Certificate Administrator, as applicable, shall notify the Depositor and each Other Depositor, at least ten (10) Business Days prior to the effective date of such succession or appointment (or if such prior notice would be violative of applicable law or any applicable confidentiality agreement, no later than the time required under Section 10.07 of this Agreement) and shall furnish pursuant to Section 10.07 of this Agreement to the Depositor and each Other Depositor in writing and in form and substance reasonably satisfactory to the Depositor and each Other Depositor, all information reasonably necessary for the Certificate Administrator, the Trustee and each Other Exchange Act Reporting Party to accurately and timely report the event under Item 6.02 of Form 8-K pursuant to Section 10.07 of this Agreement or otherwise (if such reports under the Exchange Act are required to be filed under the Exchange Act).
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.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
