Request Types Sample Clauses

Request Types. 1. A consistent schedule change to reduce hours each pay period. Example: Your regular work schedule is Monday through Friday, 40 hours. You request 4 hours Salary Savings Leave to be taken every Wednesday afternoon from July 7th- September 22nd (12 Wednesdays = 48 hours total). 2. Specific full days without pay. Example: Your regular work schedule is Monday through Friday, 40 hours. You request Salary Savings Leave to be taken July 26th-July 30th and October 4th-October 8th (10 full days = 80 hours total). 3. If IFO, reduction in credit load. Example: Your regular credit load is 12 credits for fall semester. You request Salary Savings Leave for 1 credit. Additional Resources: • Minnesota Statute 493A.49 • MMB Salary Savings Leave General Memo #2014-3 (PDF) • Minnesota State Voluntary Leave FAQ • Bargaining Unit/Plan Provisions: o AFSCME: Article 15 o Commissioner's Plan: Chapter 6 o Managerial Plan: Chapter 6 o MAPE: Article 29 o MMA: Article 25 o MNA: Article 13 o MnSCU Administrators Personnel Plan: Section 1.07 o MSUAASF: Article 19
Sample 1Sample 2
AutoNDA by SimpleDocs
Request Types. 1. A consistent schedule change to reduce hours each pay period. Example: Your regular work schedule is Monday through Friday, 40 hours. You request 4 hours Salary Savings Leave to be taken every Wednesday afternoon from July 12th- September 27th (12 Wednesdays = 48 hours total). 2. Specific full days without pay. Example: Your regular work schedule is Monday through Friday, 40 hours. You request Salary Savings Leave to be taken July 24th-July 28th and October 2nd-October 6th (10 full days = 80 hours total). Salaried exempt employees must utilize this option. 3. If IFO, reduction in credit load. Example: Your regular credit load is 12 credits for fall semester. You request Salary Savings Leave for 1 credit. Salary Savings Leave
Sample 1Sample 2
Request Types. Integration of new internal and external data sources in support of analytics requirements • Review/recommendation of analytics solution strategies • Enhancement and support of existing reporting and analytics delivery to meet customer needs, regulatory changes, and tool improvement This section will include a simple two column table as shown here: Included in Service Excluded from Service - General Assistance for existing and new Data Warehouse data. - General Assistance with reporting and analytics tool usage. - Reporting and Analytics toolset access and training - Advise on Report Design and Development - Interpretation of data in reports - Writing of Reports Service Warranty‌ This section describes the support structure in place for all WashU IT services and any unique warranties and specialized support associated with the Reporting and Analytics service. Support Model‌ WashU IT has established technology services and systems to meet customer objectives in support of the University’s mission. To ensure IT services and systems meet customer needs, WashU IT has established the following support model: General Support
Sample 1
Request Types. An SDZ Administrator(s) can raise the following three service requests using the online JIRA tool. Defects The SDZ Administrator(s) can raise requests for system related defects and issues. Examples: Production application down User is unable to access the tool Change Request/New Requirement Request can be raised for any new requirement or functionality that does not exist in the current version of SDZ. The SDZ support team will assess these requests against the product roadmap before responding back to the customer. For detailed information about the Change Request process refer to “Service Desk User Guide” document. Examples: New field required for Benefit Profile record Custom report or dashboard requirement User Feedback An SDZ Administrator can raise ‘user feedback’ requests which are suggestions to improve the tool. The user feedback guides and informs SDZ Product team decision-making and influences the product roadmap.
Sample 1

Related to Request Types

  • Contract Type OASIS SB is a family of Multiple Award, Indefinite Delivery, Indefinite Quantity (MA-IDIQ) task order contracts for Government-wide professional service based requirements which is available for use by all Federal agencies and other entities as listed in the current General Services Administration (GSA) Order, OGP 4800.2I, Eligibility to Use GSA Sources of Supply and Services. OASIS SB allows for all contract types at the task order level (e.g., Cost-Reimbursement (all types), Fixed-Price (all types), Time-and-Materials, and Labor-Hour). Task orders may also combine more than one contract type (e.g., FFP/Cost, FFP/Labor Hour etc.). Additionally, task orders may include incentives, performance based measures, multi-year or option periods, and commercial or non-commercial items.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups:

  • Order Types As defined in FAR Part 16, Type of Contracts, all types of Fixed-Price, Cost-Reimbursement, Incentive, Time-and-Materials (T&M), and Labor-Hour (L-H) are permissible for Orders under the Basic Contract. In addition, the Award Term Incentive may be used for Orders under the Basic Contract. Indefinite Delivery, Indefinite Quantity, Blanket Purchase Agreements, and Letter Contracts are not permissible Order types under the Basic Contract. Orders may be multi-year and/or include options as defined in FAR Part 17 and agency-specific FAR Part 17 supplements.

  • TYPES OF CONTRACT MODIFICATIONS In order to expedite processing of a contract modification, where proposed changes involve more than one category below, each change should be submitted to OGS as a separate request.

  • Bona Fide Request (BFR) The process described in the UNE Attachment that prescribes the terms and conditions relating to a Party's request that the other Party provides a UNE that it is not otherwise required to provide under the terms of this Agreement.

  • Training Credit Type Code Select and insert the appropriate training credit designation type code: Code Short Description

  • OTHER TYPES OF LEAVE Court Leave

  • Request Procedure The employee shall furnish evidence to his/her immediate supervisor that leave taken in accordance with the provisions of this section is in connection with family illness. The employee shall notify his/her immediate supervisor if any of the circumstances necessitating the leave change.

  • Action Requested Consider approval of the agreements with the Nebraska Department of Education as summarized below.

  • Alternate Billed Calls 1.1 The Parties will engage in settlements of intraLATA intrastate alternate-billed calls (e.g., collect, calling card, and third-party billed calls) originated or authorized by their respective Customers in accordance with an arrangement mutually agreed to by the Parties.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!