Processing of Requests. In the determination of requests for voluntary reassignment and/or transfer, the wishes of the employee shall be honored to the extent that the transfer does not conflict with the best interest of the school system. If an employee's request for transfer has been denied, the Superintendent or his/her designee shall notify the employee in writing of the reasons for the denial of transfer. Copies of the notice to employee for assignment or denial shall be provided to the PESPA President.
Processing of Requests. 2 To access the nine hundred (900) hours of educational leave and/or the educational 3 funds described above, the nurse must submit a request to his or her manager for x 4 determination of whether the department schedule can accommodate the nurse's
Processing of Requests. 2 To access the 900 hours of educational leave and/or the educational funds described 3 above, the nurse must submit a request to his or her manager for a determination of 4 whether the department schedule can accommodate the nurse's absence. The 5 manager's decision as to scheduling and departmental needs will be final and binding 6 on all concerned. The manager will then forward the approved request to the 7 Professional Nursing Care Committee, which will review the request and forward its 8 determination and explanation to the manager. The PNCC shall have the final authority 9 to approve the disbursement of funds for programs (1) when the nurse’s absence from 10 work has been approved by the unit manager, or (2) that do not require the nurse to 11 miss work from his or her scheduled hours.
Processing of Requests. Processing of a Request will take 48 hours from the time the Request is received by Administrator on behalf of Sponsor. Once a Participant’s Request is processed, such Participant will be notified by email whether such Request has been successfully validated (as described in Section 7 and Section 8) or a reason why such Request could not be processed at such time, as determined by the Sponsor or Administrator in their sole and absolute discretion. It is the responsibility of the Participant to check the applicable email account for such notification including in the inbox, spam or junk folders. The Released Parties do not assume any responsibility and are not responsible for electronic communications which are undeliverable for any reason, including (but not limited to) as a result of any form of active or passive filtering of any kind or insufficient space in a participant’s mailbox to receive e-mail messages or other communications. All Requests become the property of Released Parties and will not be returned. Program is void where taxed, prohibited, or restricted by law. Receipts obtained through unauthorized means or illegitimate channels (i.e., other than via a purchase of Participating Products from Participating Retailers) will be void. Receipts that cannot be validated for any reason will be rejected, as determined by the Sponsor or Administrator in their sole discretion. For example only, and not an all- inclusive list, a receipt will be rejected if it: (i) fails to pass anti-fraud detection measures; (ii) is unauthorized, fake, or has been illegitimately obtained; (iii) contains any messages, code or other markings not recognized by the Program Parties; (iv) contains printing or other errors; (v) is illegible, unreadable or blank; (vi) has been previously used; (vii) reflects the use of more than an authorized number of coupons; or (viii) is incorrectly or incompletely entered or submitted.
Processing of Requests. Upon confirmation by the Trust Administrator that a Request by a Band Member complies with one of the purposes, policies and procedures, and that it has been accompanied by disclosure requirements acceptable to him her, the Trust Administrator shall forward such Request to the Trustees, if such Request involves funding which is equal to or less than ten thousand dollars, or to Council if such request involves funding in excess of ten thousand dollars, and if Council approves of the Request it shall forward such Request and Disclosure Requirement to the Trustees. If Council does not approve of the Request, it shall provide written reasons for such rejection to the Trust Administrator within thirty days of it having rendered a decision. If Council is making a Request for funding, it shall forward such Request to the Trustees. The Trustees may delegate the task of reviewing the adequacy of Requests to a committee established for this purpose if they deem such delegation efficient. Within thirty (30) days following their receipt of the Request and the Disclosure Requirement described in Article 8.2 of this Agreement, the Trustees shall either:
Processing of Requests. Within thirty (30) days following the receipt by the Corporate Trustee of the Request for funding, the Corporate Trustee shall either:
Processing of Requests. Phone A ticket will be created for each call received by the Service Desk, whether the issue is in scope or out of scope. For issues that are in scope, the Service Desk technician will stay with the call and work the issue to resolution. If there is a need for further investigation, the technician will set a call back time with the caller to complete the resolution. If NOC support is needed, a ticket will be forwarded to NOC and be addressed. For issues out of scope, the call will be answered by a technician who will log the information and assign the ticket to dispatch. If all technicians are unavailable, the caller will be placed in a hold queue and will be informed of their position in the queue if a technician is not available at that moment. They will be transferred from the hold queue once a technician becomes available Email The Service Desk can receive service requests via email. However, email requests should be limited to Low priority issues only. A ticket will be created for each email request received by the Service Desk. For email requests to be processed, the following information MUST be included in the body of the email: Requester’s full name Client company name and site location if applicable Call-back number Detailed description of the issue If this information is not in the email request, no ticket will be created and no further action will be taken by the Service Desk. A Service Desk technician will assign the proper priority and the ticket will then be placed in the Service Desk ticket queue, where it will be assigned to an escalation technician. Client Call back A technician will contact the end-client before connecting to their PC to work on it. If there is no answer, the technician will leave a voicemail asking for the client to call back. They will make additional attempts to contact the client for 3 consecutive days. If the client has not responded to the Service Desk after the third day, the ticket will be marked completed.
Processing of Requests. 21.1. Assistance and Maintenance deadlines First level actions are carried out within the time limits announced in the table below under the term "First level action". The aforementioned time limits begin to run from the point at which the Digiteal support engineer responds or from the return of the components by the Client as requested by the support engineer. In the absence of any further comments from the applicant within 2 Working Days of the final corrective or first-level action being taken to correct the situation, the support ticket shall be closed. Actions Intervention Deadline for first response 1 Working Day Qualification of 1st level ASSISTANCE CORRECTIVE MAINTENANCE TECHNICAL MAINTENANCE Second level qualification Technical and Functional Assistance Basic support Advanced support Expert support / First level action email response with suggested explanation or solution No Correction of the incident by re-parameterisation of the Services or email instructions pertaining to an alternative solution* update specific to the Anomaly Restoration of access to the Services Second level action / Correction made in a future update Correction made in a future update / /
Processing of Requests. Phone A ticket will be created for each call received by the DOC, whether the issue is in scope or out of scope. For issues that are in scope, the call will be answered by a Level 1 technician and if the incoming request can be handled within 10 minutes, the Level 1 technician will stay with the call to resolve the issue. If the Level 1 technician estimates that the incoming request will take longer, they will
