June 2023

Committee Reports

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

• AIDC: Automatic Identification & Data Capture Committee
  • Issue: 0039
  • Title: Review Product Marking Implementation Guide (ATIS-0300038)
  • Statement: There are many linear labels still in use in 2022 and this hinders how reliable bar code labels are for enhanced operations, supply chain, asset tracking/recording, even some PCNs are impacted by non-2D product labels.
  • Resolution: ATIS AIDC updated ATIS-0300038, Product Marking Implementation Guide, placing emphasis as to the standard product label, which is a product bar code label that contains a 2D type symbol, which are a MicroPDF417 or a Data Matrix ECC 200. AIDC also updated label placement considerations, scanner considerations, and label content hierarchy for labels with CLEI Code, GTIN, and USI.
  • Status: Initial Closure

  For more information, visit the AIDC home page or contact Mignot Asefa.

• ESIF: Emergency Services Interconnection Forum
  • Issue: 0114
  • Title: Develop checklist forms and guidelines documentation for use by Public Safety Answering Points (PSAPs) and 9-1-1 authorities to request services as described in the FCC NPRM on NG9-1-1 Connectivity
  • Statement: The FCC Notice of Proposed Rulemaking (NPRM) (PS Docket No. 21-479) on Facilitating Implementation of Next Generation 911 Services (NG911) outlines proposed rules and timelines to support the transition to IP-based networks and the development of capabilities to support NG9 1 1 elements and functions. Specifically, the NRPM proposes to require that wireline, interconnected Voice over Internet Protocol (VoIP), and Internet-based Telecommunications Relay Service (TRS) providers complete all translation and routing to deliver 9-1-1 calls, including associated location information, in the requested IP-based format . . . to destination point(s) in those networks designated by a 911 authority, including to a public safety answering point (PSAP), designated statewide default answering point, local emergency authority, ESInet, or other point(s) designated by 911 authorities that allow emergency calls to be answered, upon request of 911 authorities who have certified the capability to accept IP-based 911 communications.
    Given the provisions of the NPRM described above, there is a need for documented processes that provide the necessary prerequisites that must be met before a request is made, and the steps involved in making the request for NG9 1 1 connectivity services from an Originating Service Provider (OSP) toward a PSAP that has connectivity to an Emergency Services IP Network (ESInet) that supports Next Generation 9-1-1 Core Services (NGCS). This documentation would be in the form of an implementation/readiness checklist and guidelines for PSAPs to expedite requests and reduce confusion.
    To support NG9-1-1 transition, create checklists and guideline documentation for PSAPs/9-1-1 Authorities to request NG9-1-1 connectivity from OSPs, including wireline, Commercial Mobile Radio Service (CMRS), interconnected VoIP, Internet-based TRS providers and covered text providers.
  • Resolution:
  • Status: New Issue

  For more information, visit the ESIF home page or contact Drew Greco.

• INC: Industry Numbering Committee
  • Issue: 0943
  • Title: Update the TBCOCAG Section 7.3.7 Unassignable, Special Use CO Codes to allow NANPA to release a NXX that is the same as the NPA in a single NPA environment when the 10-digit local dialing is in place or is implemented
  • Statement: ATIS-0300119 Thousands-Block (NPA-NXX-X) and Central Office Code (NPA-NXX) Administration Guidelines Section 7.3.7 Unassignable, Special Use CO Codes currently only allows for the release of a NXX which is the same as the NPA in a single NPA environment when an overlay is implemented. There are single NPA areas (WA 206) where 10-digit local dialing is in place and no overlay exists. NANPA suggests updating Section 7.3.7 Unassignable, Special Use CO Codes to allow NANPA to release the NXX which is the same as the NPA in single NPA environments where 10-digit local dialing is in place or when 10-digit local dialing is implemented.
  • Resolution: INC agreed that NANPA shall consult with the industry on a case-by-case basis before making available for assignment the CO Codes that matches the home NPA when 10-digit dialing is being implemented. INC made the changes to ATIS-0300119, Thousands-Block (NPA-NXX-X) and Central Office Code (NPA-NXX) Administration Guidelines, as shown in INC-2023-00008R002, and ATIS-0300006, NPA Code Relief Planning and Notification Guidelines, as shown in INC-2023-00035R000.
  • Status: Final Closure

  • Issue: 0948
  • Title: Update the TBCOCAG to remove set aside CO Codes when an NPA is in Jeopardy and allow all CO codes to be assigned in an NPA when the NPA is within 60 days of service providers being able to request CO Codes in the new relief NPA(s)
  • Statement: ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Section 15 Central Office (CO) Code (NPA-NXX) Conservation and Jeopardy Procedures allows for CO Codes to be set aside for Thousands-Block Number Pooling when an NPA is in Jeopardy and does not prohibit Jeopardy when a new NPA is within 60 days of service providers being able to request numbering resources. Since the majority of NPAs and applications are Pooled, NANPA recommends removing set aside CO Codes for pooling applications as there is no longer a need for CO Codes to be set aside specifically for pooling purposes. Additionally, when an NPA is in danger of having all assignable CO Codes allocated, has regulatory approval for relief, and is within 60 days of service providers being able to request CO Codes in the relief NPA, NANPA recommends that Jeopardy will not be declared and all assignable CO Codes in the NPA may be assigned.
  • Resolution: INC agreed to the changes to Section 15 Central Office (CO) Code (NPA-NXX) Conservation and Jeopardy Procedures of ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines as shown in INC-2023-00023R001.
  • Status: Final Closure

  • Issue: 0950
  • Title: Update the submission methods in ATIS-0300068, North American Numbering Plan Numbering Resource Utilization/Forecast (NRUF) Reporting Guidelines
  • Statement: ATIS-0300068, North American Numbering Plan Numbering Resource Utilization/Forecast (NRUF) Reporting Guidelines indicate submissions will be accepted for CD and that NANPA will input NRUF submissions for a fee which are no longer supported by NANPA.
  • Resolution: INC agreed to the submission format changes made to ATIS-0300068, North American Numbering Plan Numbering Resource Utilization/Forecast (NRUF) Reporting Guideline, as shown in INC-2023-00027R001.
  • Status: Final Closure

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

• NRSC: Network Reliability Steering Committee
  • Issue: 0055
  • Title: Determine Best Methods to Normalize Network Growth
  • Statement: During a meeting with FCC staff in November 2021, the FCC suggested that they were examining methods to normalize outage data with relation to network growth and requested that NRSC should also examine its own resources. This is particularly in relation to broadband and OC3 networks.
  • Resolution: This Issue was initially prompted by the FCC; however, due to lack of feedback and consistent, publicly available network growth metrics, NRSC closed this Issue in June 2023 without a work output.
  • Status: Final Closure

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

• OBF: Ordering and Billing Forum
  • Issue: 3663
  • Title: Moving the Ethernet Virtual Connection Quantity (EVC QTY) Field
  • Statement: Requesting a move of the EVC QTY field from the EVC Form to the ASR Form.
  • Resolution:
  • Status: New Issue

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

• SNAC: SMS/800 Number Administration Committee
  • Issue: 3429
  • Title: Toll Free Code Opening Methodology
  • Statement: The FCC has informally requested the SNAC to review various options and methodologies for opening the next toll-free code.
  • Resolution: SNAC submitted a petition to the FCC on April 5, 2016, providing a list of recommendations regarding the methodology for the 833 code opening. Specifically, SNAC recommended the following:
    1. Schedule new toll-free code openings based upon the expected number of months until code exhaustion, rather than upon the percentage of numbers in use for currently open codes;
    2. Require that the date of the code opening, once set, not be changed, given that RespOrgs, Service Control Point Owner/Operators, Service Providers, and toll-free subscribers plan and rely on that date;
    3. Implement rationing rules when exhaustion predictions indicate that number utilization in advance of a code opening is proceeding faster than expected;
    4. Make only a single new toll-free code available at a time, to promote order and efficiency and to reduce the potential risk of warehousing desirable vanity numbers; and
    5. Limit each RespOrg Group, including any two or more Responsible Organizations (RespOrgs) that are affiliates of each other, to reserving 100 numbers per day during the first twenty (20) days of a new code opening to ensure fair and efficient number distribution.
  • Status: Initial Closure

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

• WTSC: Wireless Technologies and Systems Committee
  • Issue: 0096
  • Title: State/Local Test Guidelines
  • Statement: The State/Local Test, designed by CSRIC IV and specified by ATIS WTSC, provides Alert Originators the opportunity to validate their WEA operations within their jurisdictions using the equivalent of a live field experience rather than a test environment. The State/Local Test is a coordinated effort among participants, with manual opt-in for the State/Local Test alert class and reported observations by the test participants. The State/Local Test produces a complete set of data, allowing for an analysis of the reliability, speed and accuracy of WEA, as well as allowing Alert Originators to run specific targeted scenarios based on capabilities and/or target portions within their jurisdiction, such as Device-Based Geo-Fencing.
    Given concerns cited in the FCCs FNPRM (PS Docket 15-91, 15-94) regarding the State/Local Test, WTSC ATIS is committing to providing educational materials and documented guidelines, similar to those provided for other topics in the Practical Hints document.
  • Resolution: This Issue was placed into Final Closure with the publication of ATIS-0700049, WEA 3.0 Practical Hints for Alert Originators.
  • Status: Final Closure

  For more information, visit the WTSC home page or contact Anna Karditzas.

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

INC

• Document Number: ATIS-0300061
• Title: NPA Code Relief Planning and Notification Guidelines
• Type: Revision
• View Here
• Document Number: ATIS-0300068
• Title: North American Numbering Plan Numbering Resource Utilization/Forecast (NRUF) Reporting Guidelines
• Type: Revision
• View Here
• Document Number: ATIS-0300119
• Title: Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines
• Type: Revision
• View Here

WTSC

• Document Number: ATIS-0700049
• Title: WEA 3.0 Practical Hints for Alert Originators
• Type: Revision
• View Here

Recent Policy Filings

ATIS

• Date: 06/22/2023
• Description: Letter nominating Jim McEachern, ATIS Principal Technologist, to serve as ATIS’ representative on the NANC Call Authentication Trust Anchor (CATA) Working Group
• View filing
• Date: 06/22/2023
• Description: Letter nominating Jackie Wohlgemuth, ATIS Director of Global Standards Development, to serve as ATIS’ representative on the NANC Call Authentication Trust Anchor (CATA) and Toll-Free: Future Utilization of Numbers (TFFUN) Working Groups
• View filing

NRSC

• Date: 06/06/2023
• Description: Reply Comments in response to FCC rulemaking on the National 988 Suicide and Crisis Lifeline
• View filing
• Date: 06/26/2023
• Description: Comments in support of Petition for Rulemaking regarding PSAP Outage Notifications
• View filing