IDI version 26.8 is now available.  Click here for details: IDI Updates.

MSAG and E911 Management

Prev Next

Note

If you prefer to use the IDI Knowledge Center as an alternative to this help, see the comprehensive article on MSAG and E911 Management. This article provides a quick overview and links to more detailed articles that fully cover this topic from start to finish..

MSAG/E911 Overview

As part of the emergency 9-1-1 system, Automatic Location Information (ALI) databases supply location information to Public Safety Answering Points (PSAPs) that dispatch emergency personnel where they are needed. Wireline carriers are required to maintain and update location information on their services. This information is distributed to E911 Providers who in turn keep ALI databases up-to-date.

In the IDI platform, E911 information is tied to Service Addresses and their associated E911-enabled service numbers. When you submit an order for an E911-enabled service, its Service Address is validated against a database in the IDI platform which comprises Master Street Address Guides (MSAGs) imported from the carrier’s applicable MSAG providers. The validated location information is saved to an E911 batch associated to a specific E911 Provider. Periodically, E911 batches are converted into export files to be transmitted to the applicable E911 Providers.

The basic process is as follows:

  • An authorized user imports MSAG files with E911 location information from one or more MSAG providers that cover their subscriber base.

  • Service Addresses are validated against the MSAG information stored in the IDI platform. This may occur when service addresses are added in bulk or individually.

  • When an E911-enabled service is included in an order, a Service Address (with E911 information) is associated to the service.

  • On submitting the order, a record with E911 information for the service is added to an E911 batch for a specific E911 Provider.

  • Periodically E911 export files are generated from the E911 Batch information. This can be done manually or by scheduled job. Only approved batch records get added to the export file and ultimately get sent to the applicable E911 provider. When files are generated via scheduled job, the job also automatically approves all batch records; otherwise users will need to manually approve batch records in order to include them in the export file.

  • In either case, the export file is placed on the main server in the eFrameNet / Environments / environmentName / environmentName_BackgroundProcesses / E911 Export folder. Carriers are responsible for file transfer.

  • The IDI platform creates a new batch to store records for new Equal Access orders. Records in the batch that were not approved are placed in the new batch where they can be approved and added to another export file at a later time.

  • IDI platform users can also manage individual batch records, for example resubmit already sent records as needed.

    The IDI platform must be set up to support this functionality. For more on setting up and using this functionality see E911 and MSAG Setup.

    For guidelines on using the various tools for E911 and MSAG management, see:

  • About MSAG Management

  • About E911 Management