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). 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%
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).
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.
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). 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.
Trunk Design Blocking CriteriaIn 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. 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.
Trunk Design Blocking Criteria. 4.5.1 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 (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 1 During implementation the Parties will mutually agree on an Economic Centum Call Seconds (ECCS) or some other means for the sizing of this trunk group. 000068 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-13STATE 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%
Trunk Design Blocking CriteriaTrunk 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%

Related to Trunk Design Blocking Criteria

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By February 1, 2017, the Division will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the Division to provide equally effective alternative access. The Plan for New Content will require the Division, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternatives are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the Division online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the Division will officially adopt and fully implement the amended policies and procedures.

  • 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.