Year 2000 Compliant Borrower shall perform all acts reasonably necessary to ensure that (a) Borrower and any business in which Borrower holds a substantial interest, and (b) all customers, suppliers and vendors whose compliance is likely to be material to Borrower's business, become Year 2000 Compliant in a timely manner. Such acts shall include, without limitation, performing a comprehensive review and assessment of all Borrower's systems and adopting a detailed plan, with itemized budget, for the remediation, monitoring and testing of such systems. As used in this paragraph, "Year 2000 Compliant" shall mean, in regard to any entity, that all software, hardware, firmware, equipment, goods or systems utilized by or material to the business operations or financial condition of such entity, will properly perform date sensitive functions before, during and after the year 2000. Borrower shall, immediately upon request, provide to Agent such certifications or other evidence of Borrower's compliance with the terms of this paragraph as Bank may from time to time require.
Year 2000 The Borrower has made a full and complete assessment of the Year 2000 Issues and has a realistic and achievable program for remediating the Year 2000 Issues on a timely basis (the "Year 2000 Program"). Based on such assessment and on the Year 2000 Program the Borrower does not reasonably anticipate that Year 2000 Issues will have a Material Adverse Effect.
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.
Year 2000 Issues Each of the Borrower and its Subsidiaries has made a full and complete assessment of the Year 2000 Issues and has a realistic and achievable program for remediating the Year 2000 Issues on a timely basis. Based on such assessment and program, the Borrower does not reasonably anticipate that Year 2000 Issues will have a Material Adverse Effect.
Year 2000 Problem The Company and its Subsidiaries have reviewed the areas within their business and operations which could be adversely affected by, and have developed or are developing a program to address on a timely basis, the "Year 2000 Problem" (that is, the risk that computer applications used by the Company and its Subsidiaries may be unable to recognize and perform properly date-sensitive functions involving certain dates prior to and any date after December 31, 1999). Based on such review and program, the Company reasonably believes that the "Year 2000 Problem" will not have a Material Adverse Effect.
Year 2000 Compliance Each Party warrants that it has implemented a program the goal of which is to ensure that all software, hardware and related materials (collectively called “Systems”) delivered, connected with BellSouth or supplied in the furtherance of the terms and conditions specified in this Agreement: (i) will record, store, process and display calendar dates falling on or after January 1, 2000, in the same manner, and with the same functionality as such software records, stores, processes and calendar dates falling on or before December 31, 1999; and (ii) shall include without limitation date data century recognition, calculations that accommodate same century and multicentury formulas and date values, and date data interface values that reflect the century.
TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.
Compressed Work Week The Company and Union recognize the concept of the compressed work week. It is further understood that the compressed work week conditions will apply only to those departments that are on the compressed work week.
– HOURS OF WORK & SCHEDULING 15.01 The normal hours of work for an employee are not a guarantee of work per day or per week, or a guarantee of days of work per week. The normal hours of work shall be seven and one-half (7½) hours per day, and seventy-five (75) hours in any bi-weekly period. 15.02 The normal daily shift shall consist of seven and one-half (7½) consecutive hours, exclusive of a one-half (½) hour unpaid meal period. Employees shall be entitled to a fifteen (15) minute paid break during each half of the normal daily shift, at a time designated by the Employer. 15.03 Employees required for reporting purposes shall remain at work for a period of up to fifteen (15) minutes which shall be unpaid. Should the reporting time extend beyond fifteen (15) minutes however, the entire period shall be considered overtime for the purposes of payment. 15.04 Requests for change in posted work schedules must be submitted in writing and co-signed by the employee willing to exchange days off or shifts and are subject to the discretion of the Administrator or her designate. In any event, it is understood that such a change initiated by the employee and approved by the Employer shall not result in overtime compensation or payment or any other claims on the Employer by any employee under the terms of this Agreement. 15.05 Where there is a change to Daylight Savings from Standard Time or vice-versa, an employee who is scheduled and works a full shift shall be paid for a seven and one-half (7½) hour shift rather than the actual hours worked. 15.06 In the event that a meal period is interrupted requiring an employee to attend to a work related problem, then the balance of the unused meal period will be taken within two (2) hours of the interruption. If the employee is unable to reschedule such time, she shall be paid time and one-half (1½) her regular straight time hourly rate for all time worked in excess of her normal daily hours, in accordance with Article 16.01.
Switching and Tagging Rules Each Party shall provide the other Parties a copy of its switching and tagging rules that are applicable to the other Parties’ activities. Such switching and tagging rules shall be developed on a non-discriminatory basis. The Parties shall comply with applicable switching and tagging rules, as amended from time to time, in obtaining clearances for work or for switching operations on equipment.