Collision Avoidance Sample Clauses

Open Split View

Download

Share

Cite

Collision Avoidance. The satellite shall be able phase by [***] in true anomaly one time over [***]

Sample 1

Save

Copy

Related to Collision Avoidance

• Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

• Name Collision Report Handling 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS. 6.3.2 Registry Operator shall develop an internal process for handling in an expedited manner reports received pursuant to subsection 6.3.1 under which Registry Operator may, to the extent necessary and appropriate, remove a recently activated name from the TLD zone for a period of up to two years in order to allow the affected party to make changes to its systems.

• Vision Care Insurance The District agrees to provide vision care insurance for 39 eligible employees. The Medical Eye Services plan provides one (1) comprehensive 40 examination every twelve (12) consecutive months; two (2) pairs of lenses in any 41 twenty-four (24) consecutive months. Employee is responsible for paying a ten 42 dollar ($10) deductible per calendar year. Prior enrollment in the plan is required. 43

• Catastrophic Leave Program Leave credits, as defined below, may be transferred from one (1) or more employees to another employee, on an hour-for-hour basis, in accordance with departmental policies upon the request of both the receiving employee and the transferring employee and upon approval of the employee's appointing authority, under the following conditions: A. The receiving employee is required to be absent from work due to injury or the prolonged illness of the employee, employee's spouse, registered domestic partner, a domestic partner listed on an “Affidavit for Enrollment of Domestic Partners,” submitted to employee benefits, parent or child, has exhausted all earned leave credits, including but not limited to sick leave, compensatory time, holiday credits and disability leave and is therefore facing financial hardship. B. The transfers must be for a minimum of four (4) hours and in whole hour increments thereafter. C. Transfers shall be allowed to cross-departmental lines in accordance with the policies of the receiving department. D. The total maximum leave credits received by an employee shall normally not exceed five hundred twenty (520) hours; however, if approved by his/her appointing authority, the total leave credits may be up to one thousand forty (1,040) hours. Total leave credits in excess of one thousand forty (1,040) hours will be considered on a case-by-case basis by the appointing authority subject to the approval of the Chief Administrative Officer. E. The transfers are irrevocable, and will be indistinguishable from other leave credits belonging to the receiving employee. Transfers will be subject to all taxes required by law. F. Leave credits that may be transferred under this program are defined as the transferring employee’s vacation credits or up to twenty-four (24) hours of sick leave per fiscal year. G. Transfers shall be administered according to the rules and regulations of the Auditor and Controller, and made on a form prescribed by the Auditor and Controller. Approvals of the receiving and donating employee, the donating employee's appointing authority and the receiving employee's appointing authority (in the case of an interdepartmental transfer) will be provided for on such form. H. This program is not subject to the Grievance Procedure of this Agreement.

• Shared Loss Arrangement (a) Loss Mitigation and Consideration of Alternatives. (i) For each Single Family Shared-Loss Loan in default or for which a default is reasonably foreseeable, the Assuming Institution shall undertake reasonable and customary loss mitigation efforts, in accordance with any of the following programs selected by Assuming Institution in its sole discretion, Exhibit 5 (FDIC Mortgage Loan Modification Program), the United States Treasury's Home Affordable Modification Program Guidelines or any other modification program approved by the United States Treasury Department, the Corporation, the Board of Governors of the Federal Reserve System or any other governmental agency (it being understood that the Assuming Institution can select different programs for the various Single Family Shared-Loss Loans) (such program chosen, the “Modification Guidelines”). After selecting the applicable Modification Guideline for each such Single Family Shared-Loss Loan, the Assuming Institution shall document its consideration of foreclosure, loan restructuring under the applicable Modification Guideline chosen, and short-sale (if short-sale is a viable option) alternatives and shall select the alternative the Assuming Institution believes, based on its estimated calculations, will result in the least Loss. If unemployment or underemployment is the primary cause for default or for which a default is reasonably foreseeable, the Assuming Institution may consider the borrower for a temporary forbearance plan which reduces the loan payment to an affordable level for at least six (6) months. (ii) Losses on Home Equity Loans shall be shared under the charge-off policies of the Assuming Institution’s Examination Criteria as if they were Single Family Shared-Loss Loans. (iii) Losses on Investor-Owned Residential Loans shall be treated as Restructured Loans, and with the consent of the Receiver can be restructured under terms separate from the Exhibit 5 standards. Please refer to Exhibits 2(a)(1)-(2) for guidance in Calculation of Loss for Restructured Loans. Losses on Investor-Owned Residential Loans will be treated as if they were Single Family Shared-Loss Loans. (iv) The Assuming Institution shall retain its loss calculations for the Shared Loss Loans and such calculations shall be provided to the Receiver upon request. For the avoidance of doubt and notwithstanding anything herein to the contrary, (x) the Assuming Institution is not required to modify or restructure any Shared-Loss Loan on more than one occasion and (y) the Assuming Institution is not required to consider any alternatives with respect to any Shared-Loss Loan in the process of foreclosure as of the Bank Closing if the Assuming Institution can document that a loan modification is not cost effective and shall be entitled to continue such foreclosure measures and recover the Foreclosure Loss as provided herein, and (z) the Assuming Institution shall have a transition period of up to 90 days after Bank Closing to implement the Modification Guidelines, during which time, the Assuming Institution may submit claims under such guidelines as may be in place at the Failed Bank.

• Window Coverings No curtains, draperies, blinds, shutters, shades, awnings, screens or other coverings, window ventilators, hangings, decorations or similar equipment shall be attached to, hung or placed in, or used in or with any window of the Building without the prior written consent of Landlord, and Landlord shall have the right to control all lighting within the Premises that may be visible from the exterior of the Building.

• Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <xxxxx://xxx.xxx-­‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

• Local Circuit Switching Capability, including Tandem Switching Capability 4.1.3.1 Definition 4.1.3.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for <<customer_name>> when <<customer_name>> serves end-users with four (4) or more voice-grade (DS-0) equivalents or lines in locations served by BellSouth’s local circuit switches, which are in the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non-discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.1.3.3 In the event that <<customer_name>> orders local circuit switching for a single end user account name at a single physical end user location with four (4) or more 2-wire voice-grade loops from a BellSouth central office in an MSA listed above, BellSouth shall charge <<customer_name>> the market based rate in Exhibit C for use of the local circuit switching functionality for the affected facilities. 4.1.3.4 A featureless port is one that has a line port, switching facilities, and an interoffice port. A featured port is a port that includes all features then capable or a number of then capable features specifically requested by <<customer_name>>. Any features that are not currently then capable but are technically feasible through the switch can be requested through the NBR/BFR process. 4.1.3.5 BellSouth will provide to <<customer_name>> customized routing of calls: (i) to a requested directory assistance services platform; (ii) to an operator services platform pursuant to Section 10 of Attachment 2; (iii) for <<customer_name>>’s PIC’ed toll traffic in a two (2) PIC environment to an alternative OS/DA platform designated by <<customer_name>>. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers. 4.1.3.6 Remote Switching Module functionality is included in Switching Capability. The switching capabilities used will be based on the line side features they support. 4.1.3.7 Switching Capability will also be capable of routing local, intraLATA, interLATA, and calls to international customer’s preferred carrier; call features (e.g. call forwarding) and Centrex capabilities. 4.1.3.8 Where required to do so in order to comply with an effective Commission order, BellSouth will provide to <<customer_name>> purchasing local BellSouth switching and reselling BellSouth local exchange service under Attachment 1, selective routing of calls to a requested directory assistance services platform or operator services platform. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers, but obtain a <<customer_name>> branded service.

• Sick Leave Abuse ‌ When the Employer suspects sick leave abuse, the employee will be provided the opportunity to explain the circumstances surrounding their sick leave use prior to disciplining the employee, or making reference to sick leave use in the employee’s performance evaluation. The Employer may not adopt or enforce any policy that counts the use of paid sick leave time as an absence that may lead to or result in disciplinary action for an authorized purpose. The Employer may not discriminate or retaliate against an employee for the use of paid sick leave for an authorized purpose.

• Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.