May 2020

Committee Reports

Click on a committee name below to display this month's issues.

• INC: Industry Numbering Committee
  • Issue: 0888
  • Title: Add language to the TBCOCAG to address Company Code Reclamation and to direct NANPA/PA to share Reclamation information for Abandoned Numbering Resources
  • Statement: Recently, TMOC and NECA held a call with INC to discuss Company Code Reclamation. Part of the request included NANPA/PA forwarding information to NECA when they receive approval from a regulator to reclaim abandoned numbering resources. In addition, INC needs to determine what actions NANPA/PA should take when NECA notifies them that a Company Code is reclaimed/expired.
  • Resolution:
  • Status: New Issue

  • Issue: 0889
  • Title: Update TBCOCAG TO Clarify Effective Date Intervals for Thousands-Blocks and/or CO Codes
  • Statement: During discussion of Issue 883 where INC clarified language in the TBCOCAG regarding effective dates when an applicant doesnt specify a specific effective date, INC realized that the standard interval of 33 calendar days from the time an applicant requests a block until numbers from the assigned block can be assigned to customers is not clear in the TBCOCAG. INC should review the TBCOCAG language around the 33-day interval, as well as other intervals, to determine if clarifications should be made.
  • Resolution:
  • Status: New Issue

  • Issue: 0890
  • Title: Develop Service Provider Guidelines for Reporting Permanently Disconnected Number Data to the Reassigned Numbers Database
  • Statement: FCC Order 18-177 adopted December 12, 2018 requires that a Reassigned Numbers database (RND) be established and that service providers report permanently disconnected number data to it monthly once it is established. INC has agreed that guidelines are needed for service providers in collecting and reporting such data to the RND, and in November 2019 the INC advised the FCC that it would begin developing such guidelines. The Technical Requirements Document (TRD) for the RND were made public in late January 2020, so INC can move forward with developing the guidelines.
  • Resolution:
  • Status: New Issue

  • Issue: 0891
  • Title: TBCOCAG update to ensure all service providers are notified of expedited code activations or expedited change of porting/pooling status
  • Statement: Expedited code activations or expedited changes of Portability status beyond the expedite lead time specified in the guidelines have the potential of causing call failure in networks that have not been made aware of the expedited code activation. Additionally, the expedited code activation decision makers may not consider or be informed of the facility readiness of the requesting service providers homing tandem.
  • Resolution:
  • Status: New Issue

  • Issue: 0868
  • Title: New codes not in routing on and after the code effective date
  • Statement: Noticing during our testing, new NPA-NXXs are not in routing on and after our code effective date. This requires trouble tickets to the affecting carrier and usually several rounds of escalations for resolution. This is only with the carriers we are able to test with (6). No way to know how many if any other carriers dont have our new codes in routing until we get customer complaint calls. Some carriers have a separate process we are required to follow, but most are updating routing for new codes via LERG.
  • Resolution: INC agreed to add footnotes to various sections in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), as contained in INC-2020-00056R000, to advise readers of responsibilities around NXX code openings and the availability of trouble reporting contact information on the NGIIF website.
  • Status: Initial Closure

  • Issue: 0887
  • Title: Add Clarification to the TBCOCAG Regarding Documentation Needed for Thousands-Block Transfers
  • Statement: Recently, Pooling Administration (PA) has received incorrect/incomplete documentation in regard to Thousands-Block transfers. The PA identified improvements to Sections 9.1.9, 9.2.5 and 9.3.4 of the TBCOCAG in order to provide better direction to Service Providers on the documentation required when requesting a Thousands-Block transfer.
  • Resolution: INC updated ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Assignment Guidelines (TBCOCAG) Sections 9.1.9, 9.2.5, and 9.3.4 with clarifications on the documentation needed for Thousands-Block transfers as shown in INC-2020-00039R001.
  • Status: Initial Closure

  • Issue: 0061
  • Title: Update ATIS- 0300081, Wireless Interconnections Types and Dial Patterns
  • Statement: ATIS-0300081, Wireless Interconnections Types and Dial Patterns, is an old document that has not been reviewed/updated since NIIF was an ATIS committee. There are areas that are easily identifiable to be updated but an entire review of the document should be made to determine if there are other areas of the document that need to be updated or deleted, if new information needs to be included in the document, or should the document be merged with another ATIS NGIIF document.
  • Resolution:
  • Status: New Issue

  • Issue: 0062
  • Title: Update ATIS-0300082, Guidelines for Reporting Local Number Portability Troubles in a Multiple Service Provider Environment
  • Statement: ATIS-0300082, Guidelines for Reporting Local Number Portability Troubles in a Multiple Service Provider Environment, is an old document that has not been reviewed/updated since NIIF was an ATIS committee. There are areas that are easily identifiable to be updated but an entire review of the document should be made to determine if there are other areas of the document that need to be updated or deleted, if new information needs to be included in the document, or should the document be merged with another ATIS NGIIF document.
  • Resolution:
  • Status: New Issue

  • Issue: 0063
  • Title: Update ATIS-0300084, Telecommunications Relay Service (TRS)
  • Statement: ATIS-0300084, Telecommunications Relay Service (TRS), is an old document that has not been reviewed/updated since NIIF was an ATIS committee. There are areas that are easily identifiable to be updated but an entire review of the document should be made to determine if there are other areas of the document that need to be updated or deleted, if new information needs to be included in the document, or should the document be merged with another ATIS NGIIF document.
  • Resolution:
  • Status: New Issue

  • Issue: 0064
  • Title: Update ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook, to Include Analytics as a Call Completion Root Issue
  • Statement: There is a need to identify an additional root cause for call completion issues. The initial development of the call completion handbook did not contemplate the impact of call analytics to call completion.
  • Resolution:
  • Status: New Issue

  For more information, visit the INC home page or contact .

• NRSC: Network Reliability Steering Committee
  • Issue: 0045
  • Title: Intra-Company Outage Reporting Consistency (previously OC3 Reporting Consistency)
  • Statement: The NRSC has been asked by the PSHSB to look at ways to align the industry on reporting for (new in 2018) OC3 667 User Minute outages. (Modified 4/16/2020. Following the clarification as noted in the Issue Statement/Business need, the NRSC determined the Suggested Solution should be The NRSC should provide a recommendation to the industry to report outages consistently within each company.)
  • Resolution: The NRSC Outage Reporting Advisory Subcommittee drafted a Best Practice for consideration by CSRIC stating, “Network Operators and Service Providers should ensure intra-company consistency for NORS and DIRS outage reporting.” This Best Practice was submitted to CSRIC on Xxx xx, 2020.
  • Status: Final Closure

  For more information, visit the NRSC home page or contact .

• OBF: Ordering and Billing Forum
  • Issue: 3651
  • Title: Access Service Ordering Guidelines (ASOG): Update Access Service Request (ASR) Practice (001) to add a new field for Variable Term Agreement (VTAI) Indicator
  • Statement: There is a business need to update the ASR Practice (001) to add a new Variable Term Agreement (VTAI) Indicator Field to identify if the information populated in the VTA field is a request for a new term agreement or a recap/retain existing term agreement on a change/Move activity.
  • Resolution:
  • Status: New Issue

  • Issue: 3647
  • Title: Access Service Ordering Guidelines (ASOG): Update Access Service Request (ASR) Practice (001) to Make Design Facsimile Number (DSG FAX NO) Optional
  • Statement: There is a business need to update the ASR Prac (001) to make the DSG FAX NO optional and the DSG EMAIL field conditional.
  • Resolution: Updated the ASR documentation (Practice 001) to modify the usage notes for the DSG FAX NO, DSG EMAIL, DRC and FDRC fields.
  • Status: Initial Closure

  • Issue: 3648
  • Title: National Emergency Procedures for Access Ordering (NEPA): Modify the NEPA process to reflect recommended updates due to the ASOG 60 release delay
  • Statement: Modify the existing NEPA process to identify company contacts and internal processes.
  • Resolution: Modified NEPA process by adding additional descriptive text, modifications to the form, and updates to the process flow.
  • Status: Initial Closure

  • Issue: 3649
  • Title: Design Layout Record (DLR): Expand UNIT field on the DLR form
  • Statement: There is a business need to expand the UNIT field on the Design Layout Record (ATIS-0404130-0013) to 25 characters.
  • Resolution: Expanded the UNIT field on the Design Layout Record (ATIS-0404130-0013) to 25 characters.
  • Status: Initial Closure

  • Issue: 3650
  • Title: Access Service Ordering Guidelines (ASOG): Add Implementation Contact (IMPCON) Email
  • Statement: There is a need to add the email for the Implementation Contact to the ASR 001 Form.
  • Resolution: Added a new field for Implementation Contact Email to the ASR practice (001).
  • Status: Initial Closure

  For more information, visit the OBF home page or contact .

• SNAC: SMS/800 Number Administration Committee
  • Issue: 3438
  • Title: Determine impacts to ATIS-0417001-003 from FCC ROA: New Measures for Toll Free Assignment (FCC 18-137)
  • Statement: The Federal Communications Commission announced the adoption of new measures to explore the use of competitive bidding for the assignment of toll free numbers on September 26, 2018. There is a need for SNAC participants to review ATIS-0417001-003, Industry Guidelines for Toll Free Number Administration to determine the impacts the new measures outlined in FCC 18-137 may have on previously established guidelines. Additionally, attention will be considered to whether other revisions are necessary to align with active or closed SNAC items following the previous publication.
  • Resolution: SNAC agreed to the update of the Guidelines for Toll-Free Administration (ATIS-0417001-003) as indicated in SNAC-2020-00006R003.
  • Status: Initial Closure

  For more information, visit the SNAC home page or contact .

• STEP: Sustainability in Telecom: Energy and Protection Committee
  • Issue: 0191
  • Title: Review of Battery plant questions and ATIS 0600315, Voltage Levels for DC-Powered Equipment Used in the Telecommunications Environment
  • Statement: Review ATIS 0600315 to determine if any changes in the requirements and test procedures are needed.
  • Resolution:
  • Status: New Issue

  • Issue: 0192
  • Title: Security Requirements for Communications Equipment Sites and Structures
  • Statement: Maintaining physical security of communications infrastructure, including remote sites and structures located in the outside plant, is critical to sustained operation of communications networks. A well-defined set of minimum standards for physically securing and controlling access to such sites would be helpful in maintaining security and accurately communicating the level of physical security of any given site.
  • Resolution:
  • Status: New Issue

  • Issue: 0193
  • Title: Revision of ATIS-0600336.2015, Design Requirements for Universal Cabinets and Framework
  • Statement: ATIS-0600336.2015, Design Requirements for Universal Cabinets and Framework. Make updates to standards within the document and remove all reference to years. Update hyperlinks within document.
  • Resolution:
  • Status: New Issue

  For more information, visit the STEP home page or contact .

Definitions

• New Issue: Business, operational, or technical needs that a committee has reached consensus to address.
• Issue in Initial Closure: Issues for which a committee has reached consensus on a proposed resolution. The industry has a 21 calendar day period to review and comment on the consensus resolution developed by the committee. The committee's consensus resolution concludes its work on an issue unless new or substantive information is brought forth. During the 21 day review period, comments on a consensus resolution may be provided to the committee contact and committee leaders.
• Issue in Initial Pending: Issues previously in Initial Closure for which new and substantive information impacting the consensus resolution has been received. An issue may also be in Initial Pending if output that may impact the consensus resolution is expected from another industry group, regulatory body or similar organization.
• Issue in Final Closure: Issues for which work is completed and the resolution accepted by the industry.

Recently Approved ATIS Standards

No new Standards approved this month.

Recent Policy Filings

INC, NGIIF, PTSC, SNAC

• Date: May 15, 2020
• Description: Comments filed jointly on behalf of INC, NGIIF, SNAC, and PTSC in response to the FNPRM on SHAKEN.
• View filing