Request To Use Vacation Sample Clauses

Request To Use Vacation. An employee entitled to vacation shall make written request in the manner and within the time directed by the Appointing Authority. Every department head or designee shall establish a vacation schedule for each calendar year. The vacation schedule will generally be based on employee requests and seniority (which for purposes of use of vacation refers to the employee’s overall cumulative full-time service within the City) of the employees concerned. Vacation schedules are subject to the department head’s right to plan work under his/her control and to allow vacations when employees can be spared. Each year between November 1 and December 15 employees shall submit vacation requests for the next calendar year. The determination of which requests shall be granted shall be made by seniority with the City. Thereafter, requests shall be submitted throughout the year and the determination as to whether a request is granted or denied shall be made on a first come, first served basis. Seniority is only a factor when two or more employees request vacation at the same time. An employee with greater seniority cannot bump the vacation of a less senior employee whose vacation has already been approved. Employees shall be notified as soon as possible whether his/her request is approved, and if not, the employee may request alternate vacation days. Any request submitted shall be deemed “approved” unless denied in writing within 14 calendar days of its submission.
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs

Related to Request To Use Vacation

  • Other Customary Services Perform the customary services of a transfer agent, dividend disbursing agent and, as relevant, shareholder servicing agent in connection with dividend reinvestment, accumulation, open-account or similar plan (including without limitation any periodic investment plan or periodic withdrawal program), including but not limited to: maintaining all Shareholder accounts; arranging for mailing of Shareholder reports and prospectuses to current Shareholders; withholding taxes on U.S. resident and non-resident alien accounts; preparing and filing U.S. Treasury Department Forms 1099 and other appropriate forms required with respect to dividends and distributions by federal authorities for all Shareholders; preparing and mailing confirmation forms and statements of account to Shareholders for all purchases and redemptions of Shares and other confirmable transactions in Shareholder accounts; preparing and mailing activity statements for Shareholders; and providing Shareholder account information;

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process. 6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.

  • Network Elements and Other Services Manual Additive 2.13.5.1 The Commissions in some states have ordered per-element manual additive non- recurring charges (NRC) for Network Elements and Other Services ordered by means other than one of the interactive interfaces. These ordered Network Elements and Other Services manual additive NRCs will apply in these states, rather than the charge per LSR. The per-element charges are listed on the Rate Tables in Exhibit C.

  • Customary Services The Transfer Agent shall perform all the customary services of a transfer agent, agent of dividend reinvestment plan, cash purchase plan and other investment programs and of a dividend disbursing agent and a processor of payments as described above consistent with those requirements in effect as of the date of this Agreement.

  • GENERAL SERVICE DESCRIPTION Service Provider currently provides active medical, pharmacy(Rx) and dental administration for coverages provided through Empire and Anthem (medical), Medco(Rx), MetLife(dental) and SHPS (FSA) (Empire, Anthem, Medco, MetLife and SHPS collectively, the “Vendors”) for its U.S. Active, Salaried, Eligible Employees (“Covered Employees”). Service Provider shall keep the current contracts with the Vendors and the ITT CORPORATION SALARIED MEDICAL AND DENTAL PLAN (PLAN NUMBER 502 EIN 00-0000000) and the ITT Salaried Medical Plan and Salaried Dental Plan General Plan Terms (collectively, the “Plans”) and all coverage thereunder in full force through December 31, 2011 for Service Recipient’s Covered Employees. All claims of Service Recipient’s Covered Employees made under the Plans and incurred on or prior to December 31, 2011 the (“2011 Plan Year”) will be adjudicated in accordance with the current contract and Service Provider will continue to take such actions on behalf of Service Recipient’s Covered Employees as if such employees are employees of Service Provider. All medical, dental, pharmacy and FSA claims of Service Recipient’s Covered Employees made under the Plans (the “Claims”) will be paid by the Vendors on behalf of the Service Provider. Service Recipient will pay Service Provider for coverage based on 2011 budget premium rates previously set for the calendar year 2011 and described in the “Pricing” section below. Service Recipient will pay Service Provider monthly premium payments for this service, for any full or partial months, based on actual enrollment for the months covered post-spin using enrollments as of the first (1st) calendar day of the month, commencing on the day after the Distribution Date. Service Recipient will prepare and deliver to Service Provider a monthly self xxxx containing cost breakdown by business unit and plan tier as set forth on Attachment A, within five (5) Business Days after the beginning of each calendar month. The Service Recipient will be required to pay the Service Provider the monthly premium payments within ten (10) Business Days after the beginning of each calendar month. A detailed listing of Service Recipient’s employees covered, including the Plans and enrollment tier in which they are enrolled, will be made available to Service Provider upon its reasonable request. Service Provider will retain responsibility for executing funding of Claim payments and eligibility management with Vendors through December 31, 2013. Service Provider will conduct a Headcount True-Up (as defined below) of the monthly premiums and establish an Incurred But Not Reported (“IBNR”) claims reserve for Claims incurred prior to December 31, 2011 date, but paid after that date, and conduct a reconciliation of such reserve. See “Headcount True-Up” and “IBNR Reconciliation” sections under Additional Pricing for details.

  • Services Description 2.1 ‘Ethernet’ – shall mean the provision of a fibre or copper or radio or optical data circuit or any mix of fibre, copper, radio and optical between two locations based on IEEE 802.3 standard. 2.1 ‘VU Guard’ – shall mean a filtering service that can be switched on by a subscribed customer at any time from the customer portal in order to clean traffic and temporarily stop the effects of the DDoS attack until such time that the customer can speak with the upstream provider and stop the traffic.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition. 13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Court Ordered Requests for Call Detail Records and Other Subscriber Information 7.1 To the extent technically feasible, BellSouth maintains call detail records for Mpower end users for limited time periods and can respond to subpoenas and court ordered requests for this information. BellSouth shall maintain such information for Mpower end users for the same length of time it maintains such information for its own end users. 7.2 Mpower agrees that BellSouth will respond to subpoenas and court ordered requests delivered directly to BellSouth for the purpose of providing call detail records when the targeted telephone numbers belong to Mpower end users. Billing for such requests will be generated by BellSouth and directed to the law enforcement agency initiating the request. 7.3 Where BellSouth is providing to Mpower telecommunications services for resale or providing to Mpower the local switching function, then Mpower agrees that in those cases where Mpower receives subpoenas or court ordered requests regarding targeted telephone numbers belonging to Mpower end users, if Mpower does not have the requested information, Mpower will advise the law enforcement agency initiating the request to redirect the subpoena or court ordered request to BellSouth. Where the request has been forwarded to BellSouth, billing for call detail information will be generated by BellSouth and directed to the law enforcement agency initiating the request. 7.4 In all other instances, Mpower will provide Mpower end user and/or other customer information that is available to Mpower in response to subpoenas and court orders for their own customer records. When BellSouth receives subpoenas or court ordered requests regarding targeted telephone numbers belonging to Mpower end users, BellSouth will advise the law enforcement agency initiating the request to redirect the subpoena or court ordered request to Mpower.

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