Trunk Design Blocking Criteria Sample Clauses

Trunk Design Blocking Criteria. 4.5.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in the Table below. Trunk requirements shall be based upon time consistent average busy season busy hour twenty (20) day averaged loads applied to industry standard Xxxx-Xxxxxxxxx Trunk Group Capacity algorithms (using Medium day-to-day Variation and 1.0 Peakedness factor until actual traffic data is available). Trunk Group Type Design Blocking Objective Local Interconnection Trunk Group – Direct End Office (Primary High) ECCS1 Local Interconnection Trunk Group – Direct End Office (Final) 2% IntraLATA Toll Trunk Group (Local/Access or Access Tandem Switch) 1% Local Interconnection Trunk Group (Local Tandem) 1% Meet Point (Local/Access or Access Tandem Switch) (AT&T-12STATE only) 0.5% E911 1% Operator Services (DA/DACC) 1% Operator Services (0+, 0-) 1% Busy Line Verification/Emergency Interrupt 1% Third Party (AT&T SOUTHEAST REGION 9-STATE only) 1%
Sample 1Sample 2Sample 3See All (64)
AutoNDA by SimpleDocs
Trunk Design Blocking Criteria. 7.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon average busy season bouncing busy hour twenty(20) day averaged loads applied to industry standard Erlang-B Trunk Group Capacity algorithms (use Medium day- to-day Variation and 1.0 Peakedness factor until actual traffic data is available). TABLE 1
Sample 1Sample 2Sample 3See All (22)
Trunk Design Blocking Criteria. 3.6.1 In accordance with industry traffic engineering standards, trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon a time consistent average busy season busy hour Erlang B .001 factor. TABLE 1
Sample 1Sample 2Sample 3See All (21)
Trunk Design Blocking Criteria. 4.5.1 Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table
Sample 1Sample 2Sample 3See All (15)
Trunk Design Blocking Criteria. Trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon time consistent average busy season, busy hour twenty (20) day averaged loads applied to industry standard Xxxx-Xxxxxxxxx Trunk Group Capacity algorithms (use Medium day-to-day Variation and 1.0 Peakedness factor until actual traffic data is available). TABLE 1 Trunk Group Type Local Tandem Local Direct End Office (Primary High) Local Direct End Office (Final) Design Blocking Objective 1% ECCS* 2% IntraLATA 1% Local/IntraLATA 1% InterLATA (Meet Point) Tandem 0.5% 911 1% Operator Services (DA/DACC) 1% Operator Services (0+, 0-) 1% Busy Line Verification-Inward Only 1% *During implementation the Parties will mutually agree on an ECCS or some other means for the sizing of this trunk group.
Sample 1Sample 2Sample 3See All (8)
Trunk Design Blocking Criteria. In accordance with industry traffic engineering standards, trunk requirements for forecasting and servicing shall be based on the blocking objectives shown in Table 1. Trunk requirements shall be based upon a time consistent average busy season busy hour Erlang B .001 factor. TABLE 1 Trunk Group Type Design Blocking Objective Local Direct End Office (Primary High) as mutually agreed upon Local Direct End Office (Final) .01% 74.8. Trunk Servicing 74.8.1. Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (ASR). **CLEC will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. Where one-way trunks are used (as discussed in Section 3.2), CenturyLink will issue ASRs for trunk groups for traffic that originates from CenturyLink and terminates to **CLEC. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other Party.
Sample 1Sample 2
Trunk Design Blocking Criteria. Trunk forecasting and servicing for the Section 251(b)(5), ISP-Bound Traffic and intraLATA toll trunk groups will be based on the industry standard objective of 2% overall time consistent average busy season busy hour loads 1% from the End Office to the Tandem and 1% from tandem to End Office based on Xxxx Xxxxxxxxx B.0lM [Medium Day-to-Day Variation] until traffic data is available. Listed below are the trunk group types and their objectives: Trunk Group Type Blocking Objective (Xxxx Xxxxxxxxx B.01M) Local Tandem 1% Local Direct 2% IntraLATA Interexchange Direct 1 % IntraLATA Interexchange Tandem 0.5% 911 1 % Operator Services (DA/DACC) 1 % Operator Services (0+, 0-) 0.5% Third Party 0.5% Busy Line Verification/Emergency Interrupt 1%
Sample 1
AutoNDA by SimpleDocs
Trunk Design Blocking Criteria 
Sample 1

Related to Trunk Design Blocking Criteria

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

  • Scope of Work For the 2022/2023 Grant Period, the Provider will maintain a victim services program that will be available to provide direct services to victims of crime who are identified by the Provider or are presented to the Provider, as specified in the Provider’s 2022/2023 Grant Application as approved by the OAG and incorporated herein by reference.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!