Backwards Incompatible Changes. Google will notify Customer at least 12 months before significantly modifying a Customer-facing Google API in a backwards-incompatible manner.
Backwards Incompatible Changes Sample Clauses
Related to Backwards Incompatible Changes
Year 2000 Compatibility Take all action necessary to assure that its computer based systems are able to operate and effectively process data including dates on and after January 1, 2000, and, at the reasonable request of the Administrative Agent or the Required Lenders, provide evidence to the Lenders of such year 2000 compatibility.
Product Changes Vocera shall have the right, in its absolute discretion, without liability to End User, to update to provide new functionality or otherwise change the design of any Product or to discontinue the manufacture or sale of any Product. Vocera shall notify End User at least 90 days prior to the delivery of any Product which incorporates a change that adversely affects form, fit or function (“Material Change”). Vocera shall also notify End User at least 90 days prior to the discontinuance of manufacture of any Product. Notification will be made as soon as reasonably practical for changes associated with regulatory or health and safety issues.
Shift Changes When an employee is assigned to a specific shift and that assignment is changed, the employee shall be given seven (7) calendar days’ notice prior to the change.
Year 2000 Compliant The Administrator warrants that all software code owned or under control by it, used in the performance of its obligations hereunder will be Year 2000 Compliant. For purposes of this paragraph, "Year 2000 Compliant" means that the software will continue to operate beyond December 31, 1999 without creating any logical or mathematical inconsistencies concerning any date after December 31, 1999 and without decreasing the functionality of the system applicable to dates prior to January 1, 2000 including, but not limited to, making changes to (a) date and data century recognition; (b) calculations which accommodate same- and multi- century formulas and date values; and (c) input/output of date values which reflect century dates. All changes described in this paragraph will be made at no additional cost to the Fund.
Agreement Flexibility 8.1 An employer and employee covered by this enterprise agreement may agree to make an individual flexibility arrangement to vary the effect of terms of the agreement if: (a) the agreement deals with 1 or more of the following matters: (i) arrangements about when work is performed; (ii) overtime rates; (iii) penalty rates; (iv) allowances; (v) leave loading; and (b) the arrangement meets the genuine needs of the employer and employee in relation to 1 or more of the matters mentioned in paragraph (a); and (c) the arrangement is genuinely agreed to by the employer and employee. 8.2 The employer must ensure that the terms of the individual flexibility arrangement: (a) are about permitted matters under section 172 of the Fair Work Act 2009; and (b) are not unlawful terms under section 194 of the Fair Work Act 2009; and (c) result in the employee being better off overall than the employee would be if no arrangement was made. 8.3 The employer must ensure that the individual flexibility arrangement: (a) is in writing; and (b) includes the name of the employer and employee; and (c) is signed by the employer and employee and if the employee is under 18 years of age, signed by a parent or guardian of the employee; and (d) includes details of: (i) the terms of the enterprise agreement that will be varied by the arrangement; and (ii) how the arrangement will vary the effect of the terms; and (iii) how the employee will be better off overall in relation to the terms and conditions of his or her employment as a result of the arrangement; and (e) states the day on which the arrangement commences. 8.4 The employer must give the employee a copy of the individual flexibility arrangement within 14 days after it is agreed to. 8.5 The employer or employee may terminate the individual flexibility arrangement: (a) by giving no more than 28 days written notice to the other party to the arrangement; or (b) if the employer and employee agree in writing—at any time.
FINANCIAL IMPLICATIONS There are no budget implications. The applicant will be responsible for all costs, expenses, liabilities and obligations imposed under or incurred in order to satisfy the terms of this proposed development agreement. The administration of the proposed development agreement can be carried out within the approved 2019- 2020 budget and with existing resources.
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for Louisville Telephone when Louisville Telephone serves an end-user with four (4) or more voice-grade (DS-0) equivalents or lines served by BellSouth in one of 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.2.3 In the event that Louisville Telephone orders local circuit switching for an end user with four (4) or more DS0 equivalent lines within Density Zone 1 in an MSA listed above, BellSouth shall charge Louisville Telephone the market based rates in Exhibit B for use of the local circuit switching functionality for the affected facilities.
NETWORK CHANGES 3.1. Sprint shall provide notice of network changes and upgrades in accordance with §§ 51.325 through 51.335 of Title 47 of the Code of Federal Regulations. Sprint may discontinue any interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. Sprint agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers, which may result from such discontinuance of service.
Construction Change Directives 1.1.1, 3.4.2, 3.11, 3.12.8, 4.2.8, 7.1.1, 7.1.2, 7.1.3, 7.3, 9.3.1.1 Construction Schedules, Contractor’s 3.10, 3.11, 3.12.1, 3.12.2, 6.1.3, 15.1.6.2
Switching System Hierarchy and Trunking Requirements For purposes of routing PNG traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to PNG, the subtending arrangements between PNG Tandem Switches and PNG End Office Switches shall be the same as the Tandem/End Office subtending arrangements that PNG maintains for the routing of its own or other carriers’ traffic.
