Forecasting Manager and Sprint PCS will work cooperatively to generate mutually acceptable forecasts of important business metrics including traffic volumes, handset sales, subscribers and Collected Revenues for the Sprint PCS Products and Services. The forecasts are for planning purposes only and do not constitute Manager's obligation to meet the quantities forecast.
Work Hour Penalty Eight hours of labor constitute a legal day's work, and forty hours constitute a legal week's work. Pursuant to Section 1813 of the Labor Code of the State of California, the Contractor shall forfeit to the County Twenty Five Dollars ($25) for each worker employed in the execution of this Contract by the Contractor or by any subcontractor for each calendar day during which such worker is required or permitted to work more than the legal day's or week's work, except that work performed by employees of said Contractor and subcontractors in excess of the legal limit shall be permitted without the foregoing penalty upon the payment of compensation to the workers for all hours worked in excess of eight hours per day of not less than 1-1/2 times the basic rate of pay.
Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.
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.
Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.
Civil Penalty Payment Pursuant to Health and Safety Code § 25249.7(b)(2), and in settlement of all claims alleged in the Notice or referred to in this Settlement Agreement, XR agrees to pay two thousand ($2,000.00) in civil penalties. The penalty payment will be allocated in accordance with California Health and Safety Code §§ 25249.12(c)(1) & (d), with 75% of the penalty amount paid to the California Office of Environmental Health Hazard Assessment (“OEHHA”) and the remaining 25% of the penalty amount retained by EHA. Shall issue two separate checks for the initial civil penalty payment to (a) “OEHHA” and (b) Environmental Health Advocates, Inc. as follows: One payment of $1,500.00 to OEHHA, due 14 (fourteen) days after the Effective Date. One payment of $500.00 to EHA, due 14 (fourteen) days after the Effective Date. All payments owed to OEHHA (EIN: 00-0000000), pursuant to this Section shall be delivered directly to OEHHA (Memo Line "Prop 65 Penalties") at the following addresses: P.O. Box 4010 Sacramento, CA 95812-4010 All penalty payments owed to EHA shall be sent to: Xxxxx Xxxxxx Environmental Health Advocates 000 Xxxxxxxx, Xxxxx 0000 Xxx Xxxxx, XX 00000
Forecast Customer shall provide Flextronics, on a monthly basis, a rolling [***] forecast indicating Customer’s monthly Product requirements. The first [***] of the forecast will constitute Customer’s written purchase order for all Work to be completed within the first [***] period. Such purchase orders will be issued in accordance with Section 3.2 below.
Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline:
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.
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.