Компания уполномочена пользоваться услугами прочих Брокеров/Принципалов для исполнения всех обязанностей или их части по настоящему Договору, а также предоставлять информацию по Счету таким Брокерам/Принципалам.
Компания уполномочена пользоваться Sample Clauses
Related to Компания уполномочена пользоваться
Volume or Maintenance License If you obtained the Apple Software under a volume or maintenance license program with Apple, the terms of your volume or maintenance license will determine the number of copies of the Apple Software you are permitted to download, install, use and run on Apple-branded computers you own or control. Except as agreed to in writing by Apple, all other terms and conditions of this License shall apply to your use of the Apple Software obtained under a volume or maintenance license.
Overtime-Eligible Unpaid Meal Periods The Employer and the Union agree to unpaid meal periods that vary from and supersede the unpaid meal period requirements of WAC 000-000-000. Unpaid meal periods for employees working more than five (5) consecutive hours, if entitled, will be a minimum of thirty (30) minutes and will be scheduled as close to the middle of the work shift as possible. Employees working three (3) or more hours longer than a normal workday will be allowed an additional thirty (30) minute unpaid meal period. When an employee’s unpaid meal period is interrupted by work duties, the employee will be allowed to resume their unpaid meal period following the interruption, if possible, to complete the unpaid meal period. In the event an employee is unable to complete the unpaid meal period due to operational necessity, the employee will be entitled to compensation, which will be computed based on the actual number of minutes worked within the unpaid meal period. Meal periods may not be used for late arrival or early departure from work and meal and rest periods will not be combined.
Extended After Hours: any time or day not within standard business hours Initial Response Times: CRITICAL support or service requests will be responded to within the following times. Calls to 933-3333 after hour calls will be answered by the WashU IT Systems Operations Center (SOC). The SOC will either resolve the issue or page on call staff to resolve the issue. On call staff will respond to the after hour pager on average* within 30 minutes *averages are calculated on a monthly basis Support Request Resolution Targets WashU IT has established the following general support escalation procedures and resolution targets to meet customer support request needs. Note that service request fulfillment is addressed in a latter section titled “Service Fulfillment Targets”. This section is only addressing support escalation and resolution. Support Escalation & Resolution Procedures – all support requests will be escalated from the initial general support team to a specialized support team based on the priority of the support request or if the general support team cannot resolve the issue within 20 minutes. Once the request is escalated to a specialized support team, the customer will be notified and the specialized support team may contact the customer for further information and testing. Once the specialized support team resolves the request, the general support team will review the resolution to ensure quality control. Once the general support team confirms the resolution has met the customer’s needs, the request will be closed. Communication with the customer will be via email. If the customer does not reply within 3 business days, the ticket will be automatically closed. Prioritization – all support requests will be given a medium priority unless the customer indicates an impact or urgency that requires a higher prioritization. Impact is defined as the affect to which a technology service or system is inhibiting the customer’s ability to conduct University business. Urgency is defined as the timeframe in which the customer needs the technology issues resolved or a workaround put in place. WashU IT uses the following priority scale for systems and services not performing normally. Priority Description Response Target Resolution Target Critical Global Issues Business critical issues – impacting ability to perform mission Issues affecting multiple users unable to be productive 15 minutes 4 hours High Issues affecting individual or multiple users with no workaround available 1 hour 1 Business Day Medium Default priority assigned to all tickets. Issues affecting multiple users with workaround available 1 Business Day 3 Business Days Low Issues affecting individual users with workaround available 2 Business Days 5 Business Days Service Request Fulfillment Targets WashU IT Service Owners work with customers to establish service fulfillment targets for each service request that comprise the Service Features listed in this document. The following table lists the service fulfillment target for each service request: Service Request Fulfillment Target • Availability of new internal and external data sources • Review/recommendation of analytics solution strategies • Enhancement and support of existing reporting and analytics delivery to meet customer needs, regulatory changes, and tool improvement • Customers who submit request during normal business hours will receive an initial response within 1 business day. • Requests will be reviewed by the team and the customer will receive additional follow-up contact after the initial response to determine appropriate request fulfillment steps. Service Availability • Reporting and Analytics environment is available Monday through Friday, 8 a.m.-5 p.m., with >= 95% day-of data availability quarterly. Service Reliability, Performance & Continuity Business customer obligation: The customer should develop and maintain a business continuity plan specific to their area of activity with respect to Reporting and Analytics service outages, so that in case of an unexpected or prolonged service outage, they might still be able to conduct their business appropriately. Change Management and Service Reviews WashU IT has established a change management and service review process to ensure changes and enhancements of services and systems are done in a controlled manner to prevent unintended consequences and to confirm that changes and updates are implemented according to an approved framework. Change Management The complete change management process is documented in the WashU IT Change Management Charter, but the following highlights from this charter are worth noting. Changes and updates to systems and services fall into one of three general categories: Standard – changes and updates that are considered routine, well documented and of low risk to the University. Normal – changes and updates that require scheduled review and approval by the Change Advisory Board (CAB) to ensure mitigation of risk to the University. Emergency – changes and updates that cannot wait until the next scheduled CAB meeting for approval and must be reviewed by the CAB to address a CRITICAL incident or upgrade. All non-standard changes will be communicated to customer according to established customer communication channels. All customer requests for a non-standard change or upgrade to a WashU IT supported service or system must follow the WashU IT change management process. General Maintenance Windows Non-standard changes approved by the CAB will occur during the following maintenance windows: M – Sat: 6pm – 6am Sunday: Anytime of the Day Regularly Scheduled Maintenance for Reporting and Analytics • Server patching occurs the 2nd Tuesday of each month from 5 – 10 pm and results in COGNOS and TM1 servers being unavailable for up to 30 minutes. Roles and Responsibilities The following roles and responsibilities between WashU IT and the customer are called out to highlight the important partnership that must exist between WashU IT as the service provider and WashU departments as the consumers of existing services and systems. Both parties play an important role in ensuring the overall health of services. WashU IT Responsibilities • Provide qualified support personnel to support WashU IT services and systems. • Document specific features and warranties of each service provided by WashU IT • Produce metrics that demonstrate the health of each service. • Provide customers with appropriate communication and governance channels to effect change to WashU IT services and systems in a way that furthers the University’s mission without posing significant risks. Customer’s Responsibilities • Provide an ongoing point of contact within their department with which WashU IT can interface to ensure support and service requests are addressed in a timely manner. • Make support and service requests as outlined in this document. • Use WashU IT established communication and governance channels to request changes to existing services and systems. Service Reporting & Metrics WashU IT will provide the customer with a quarterly report that documents key support and service metrics. Customers may request additional metrics and reporting schedules by contacting their CRM representative. The BIDW website will maintain a metric showing the prior quarter’s percentage of on-time data delivery. Review and Revision Timeline
Extended Tours Where the Hospital and the Union agree, subject to the approval of the Ministry of Labour, other arrangements regarding hours of work may be entered into between the parties on a local level with respect to tours beyond the normal or standard work day. The model agreement with respect to extended tour arrangements is set out below: MODEL AGREEMENT WITH RESPECT TO EXTENDED TOUR ARRANGEMENTS MEMORANDUM OF AGREEMENT Between: The Hospital - And: The Ontario Public Service Employees Union (and its Local ) This Model Agreement shall be part of the Collective Agreement between the parties herein, and shall apply to the employees described in Article 1 of the Model Agreement.
Extension After Suspension When a suspension occurs through no fault of PURCHASER, PURCHASER may request an extension of time for performance of this contract, for a period not to exceed the period of operations that were suspended. The request for extension must be in writing and:
Where Applicable 1. Retrogression shall apply where a regular employee becomes unable to perform the duties of a job for which he/she is receiving the standard rate and is transferred to a lower-rated job because of:
Interference or Impairment If a Party (“Impaired Party”) reasonably determines that the services, network, facilities, or methods of operation, of the other Party (“Interfering Party”) will or are likely to interfere with or impair the Impaired Party’s provision of services or the operation of the Impaired Party’s network or facilities, the Impaired Party may interrupt or suspend any Service provided to the Interfering Party to the extent necessary to prevent such interference or impairment, subject to the following:
Overtime Rest Periods If an employee is assigned one (1) or more hours of overtime work contiguous to his/her regular workshift or is called back within one (1) hour of his/her scheduled quitting time, the Agency will provide a fifteen (15) minute rest period after two (2) hours of overtime completed.
Overtime-Eligible Rest Periods The Employer and the Union agree to rest periods that vary from and supersede the rest periods required by WAC 000-000-000. Employees will be allowed rest periods of fifteen (15) minutes for each one-half (1/2) shift of four (4) or more hours worked at or near the middle of each one-half (1/2) shift of four (4) or more hours. Rest periods do not require relief from duty. Rest periods may not be used for late arrival or early departure from work and rest and meal periods will not be combined.
Reporting Model 1 FFI The term Reporting Model 1 FFI means a Financial Institution with respect to which a non-U.S. government or agency thereof agrees to obtain and exchange information pursuant to a Model 1 IGA, other than a Financial Institution treated as a Nonparticipating Financial Institution under the Model 1 IGA. For purposes of this definition, the term Model 1 IGA means an arrangement between the United States or the Treasury Department and a non-U.S. government or one or more agencies thereof to implement FATCA through reporting by Financial Institutions to such non-U.S. government or agency thereof, followed by automatic exchange of such reported information with the IRS.
