LIS Forecasting 7.2.2.8.1 Both CLEC and Qwest shall work in good faith to define a mutually agreed upon forecast of LIS trunking.
TRUNK FORECASTING 58.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. Embarq 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 Embarq 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:
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.
Marketing Plan The MCP shall submit an annual marketing plan to ODM that includes all planned activities for promoting membership in or increasing awareness of the MCP. The marketing plan submission shall include an attestation by the MCP that the plan is accurate is not intended to mislead, confuse or defraud the eligible individuals or ODM.
Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.
Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline: • •
Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.
Timetable In order to set a timetable and procedural framework within which the subcommittees will accomplish their tasks, the parties have further agreed to the following: The subcommittees referenced in Section 1 above will be appointed and have their first organizational meeting within six (6) weeks of the date of the MOU ratification. Each subcommittee shall provide to the Head of the affected Department a final report no later than thirty (30) weeks after the date of the MOU ratification. The Department Head who receives a final report will meet with the LMC to provide feedback on the report, indicating areas of acceptance and explaining the reasons for rejecting any of the recommendations in the report.
Ongoing Trunk Forecast Requirements Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.
Monitoring and Adjusting Forecasts Verizon will, for ninety (90) days, monitor traffic on each trunk group that it establishes at ECI’s suggestion or request pursuant to the procedures identified in Section 14.2 of this Attachment. At the end of such ninety-(90) day period, Verizon may disconnect trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. If, after such initial ninety (90) day period for a trunk group, Verizon determines that any trunks in the trunk group in excess of two (2) DS1s are not warranted by actual traffic volumes (considering engineering criteria for busy Centium Call Second (Hundred Call Second) and blocking percentages), then Verizon may hold ECI financially responsible for the excess facilities and disconnect such excess facilities.
