Client Login



DBMS provides extensive LNP support.

In today’s operational world of 9-1-1, the number of service providers increases almost daily. Keeping track of record ownership, ensuring a timely ownership change and resolving any failed or stranded ownership change transactions takes up a lot of time and energy of the data analyst.

DBMS takes the work load off of the data analyst by automatically scrubbing data imports for record ownership transactions, notifying the data provider of the encountered data conditions, automating the processing of out of sequence or delayed Unlock records, keeping detailed audit records and offering detailed reporting, such as failed Migrates and stranded Unlocks, for both the DBMS host and the data provider to monitor the process closely according and going beyond the current NENA standard for LNP.

Come join us for the next training session on Training Tuesday to learn how this time consuming, mostly manual process can be turned into a highly automated system process, including pushing the status monitoring and resolution effort to the parties involved in the ownership change.

Automate SOI echo-back delivery to provider.

Service Order Input is a daily process for most DBMS hosts, involving files being sent in by various means and formats, requiring an increased amount of a data analyst’s work day. Once a file has been successfully imported, any associated echo back files will need to be copied, moved or attached to emails for return to the data provider.

DBMS provides for a convenient mechanism, which can be configured specifically for each data provider within the Service Order Provider (SOP) profile, which is easily accessible by a data analyst, and does not require IT staff to create or maintain. The DBMS mechanism can perform one or any combination of the below actions automatically.

a.) Email all echo back files associated to the SOI import file to a defined individual or group email. DBMS provides for a convenient mail server configuration within the application itself

b.) Deposit all echo back files associated to the SOI import file to a designated directory, such as a local network share, if so chosen, for further action by the data analyst or in support of the DBMS host’s data retention policy

c.) Deposit all echo back files associated to the SOI import file to a directory on a web server, allowing the data provider to conveniently pick up any files at his discretion (see WebDBMS)

Any import efforts are also being written to a central process log location, which can even be made accessible to the data provider via a web server (see WebDBMS) as well. This flexibility creates a high degree of self service for the data provider, relieving the data analyst of the DBMS host in his daily repetitive tasks. Most importantly, it provides for a significantly faster record processing cycle overall making the correct data available and ready for the subscriber’s emergency call sooner.

How do I create and configure a SOP profile?

The Service Order Provider (SOP) profile is at the heart of any DBMS configuration. It governs the rules by which a data provider can systematically manage their records within the system. The configuration screen can be found under Tools \ Configuration \ Service Order Provider.

Each SOP profile, at the minimum, requires a name that uniquely identifies the provider among all other providers within a system. The File ID value specifies the file name that the provider can send Customer records to the DBMS system under. The Company ID / NENA ID controls the ownership aspect of the profile, ensuring only Customer records carrying the correct company ID will be able to enter the system. The last of the required fields is the Import Type, which governs the NENA approved file format for the SOP profile.

All other fields are optional components for population and use and should be carefully reviewed under aspects of best practices and local site operational requirements.

Motivate MSAG providers to bring their data into compliance with NENA Standards.

Given there are numerous systems operated by numerous organizations, ranging from counties, communities, traditional telcos, big and small, as well as new technology service providers of dial tone, each one of them has a need to address its subscriber base. This is not only vital for billing purposes, but also, naturally, for 9-1-1 purposes.

To which location should the responders be sent to in case of an emergency call being placed by any one of those subscribers? How can the overall 9-1-1 process flow ensure that the dispatched location is correct relative to the maps the local PSAP and responder painstakingly maintains and quality assures? How can new service providers be helped to do ‘the right thing’ for its paying customers from the beginning? What kinds of implications are there if the 9-1-1 address is not being validated with the local 9-1-1 authority? What do 9-1-1 authorities do today to make up for the various non-standard addressing mechanisms in the field? What kind of migration strategies or motivational strategies have worked reliably and which ones have failed entirely?

One of the more timely questions with recent advancements in the field is ‘how and what does it take to make the leap into Next Generation 9-1-1’?

Join our board discussion and share your experiences and opinions regarding the use of non-standard and standard MSAG addressing. Make your voice heard and help the community discuss and devise a better way to create and motivate adherence to industry standards!

There is a lot more to LVF/ECRF than GIS data.

LVF (Location Validation Function) and ECRF (Emergency Call Routing Function) do, in fact, use GIS data. This information represents the roads in a 9-1-1 territory and the service area polygons for a territory. However, those by themselves do not provide the functionality required to validate a location or to route a 9-1-1 call. This requires a combination of MSAG, Postal, and GIS data.

Postal data serves as a bridge to connect the address that a consumer knows to be their location, to the appropriate MSAG equivalent for that location. Service area polygons have to be supplemented with identifying information for call routing.

In today’s world that is an ESN; in NG9-1-1, it is an identifier which allows the call to be routed over IP to the correct PSAP. The MSAG does not “go away” with the advent of LVF/ECRF. Rather, it transforms into a powerful data repository that can perform all of today’s 9-1-1 functions as well as many more.

Learn more about our products and services with our online content library.


Answers to your most frequently asked questions are available online!

Datamaster Long Term Evolution Digest

Current Digest

Previous Digests - 2013

Previous Digests - 2012

Previous Digests - 2011

Previous Digests - 2010

911 Datamaster Contract Number

911 Datamaster Contract Number: DIR-CPO-4404

911 Datamaster Contract Link

DIR Cooperative Contracts webpage

Products and Services Awarded

Description of Product and Services Awarded

For database technology, we are proposing to utilize 911 Datamaster’s DataBond. DataBond is an evolution of 9-1-1 ALI. It can serve as a ‘Location Database’ (LDB), which is defined by NENA as a data structure that can serve as both an ALI and a LIS operating within a 9-1-1 authority’s jurisdiction. Since DataBond integrates with both existing and NG9-1-1 infrastructure, it allows for the migration to NG9-1-1 technology on your schedule without the need for a ‘fork lift’ upgrade. Our innovative software facilitates a migration mechanism of both data and business processes, making the transition a flexible, yet controlled, evolution. DataBond supports current and future versions of location validation, emergency call routing and location-based call routing.

DataBond consists of database and database management software. It provides request / response and is compatible with all leading ANI / ALI controllers as well as NG9-1-1 components such as Legacy Network Gateways (LNGs) and Emergency Service Routing Proxies (ESRPs). Some of the key features of DataBond include:

  • Microsoft™ Server-based for ease of use, lower cost and easy maintenance.
  • Encompasses all of the specifications for 9-1-1 ALI and LIS.
  • Supports IP communications with controllers and PSAPs.
  • Supports HTTP Enabled Location Determination (HELD).
  • Meets NENA ALI Query Service (AQS) Standard.
  • Meets J-STD-036 and E2+ cellular standards.
  • Interfaces with 9-1-1 DBMS software for ALI / LDB updates.
  • Supports replication with remote LIS implementations.
  • Scalability from less than one thousand to more than 50 million records.
  • Provides ALI response to multiple PSAP controllers.
  • ALI steering to other ALI providers and to MPCs and VPCs via pANIs.
  • Supports onboard and offboard selective routing updates with all major selective routing platforms.
  • Provides five call history-input and store details about a particular phone number.
  • Simple or advanced password protection and user login auditing.
  • Automatic synchronization of records on two Servers for full redundancy and reliability.
  • Maintains logs of call activity and imports and selective router updates.
  • Automatic status notification via pager, email, TL1 and SNMP.
  • Supported by 911 Datamaster’s comprehensive, 24/7/365 software support.

DataBond supports important standards such as:

  • NENA 02-011: Data Standards for Local Exchange Carriers, ALI Service Providers & 9-1-1 Jurisdictions.
  • NENA 02-015: Standard for Reporting and Resolving ANI/ALI Discrepancies and No Records Found for Wireline, Wireless and VoIP Technologies.
  • NENA 04-005: ALI Query Service Standard.
  • NENA 57-501: Wireless Phase I & II Features and Functions Information Document.

DataBond support traditional ALI interfaces and provisioning as described in:

  • NENA 02-010: “Standard Legacy Data Formats for 9-1-1 Data Exchange GIS Mapping Data Structures"
  • NENA 02-501: “Wireless (Pre-XML) Static and Dynamic ALI Data Content Information Document”
  • NENA 04-005: “ALI Query Service Standard.”
  • NENA 02-011: “Data Standards for Local Exchange Carriers, ALI Service Providers & 9-1-1 Jurisdictions”
  • NENA 02-015: “Standard for Reporting and Resolving ANI/ALI Discrepancies and No Records Found for Wireline, Wireless and VoIP Technologies”

DataBond support NG9-1-1 standards as described in:

  • NENA-INF-008.2-2014: (originally 77-501): “NG9-1-1 Transition Plan Considerations Information Document”; (LDB section)
  • NENA STA-010 v2 (aka NENA 08-003 “Detailed Functional and Interface Standards for the NENA i3 Solution”; (LDB, LIS, LVF, and ECRF sections)
  • IETF RFC 5985: “HTTP-Enabled Location Delivery (HELD)”
  • IETF RFC 5139: “Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)”

DataNexus® is a fully functional LVF/ECRF that complies with all NENA and IETF standards and provides full migration into i3 without costly technology acquisition and process overhaul. Key aspects of DataNexus® include:

  • Allows data analysts to correlate street and community names from three data sources (Postal, MSAG, and GIS).
  • Allows authorized service providers to validate locations and route calls using real time data.
  • Integration with 9-1-1 DBMS, DataBond®, and SpatialCentral®.
  • Identifies common error discrepancies between MSAG, GIS, and Postal.
  • Extensive online help.
  • Extensive security mechanisms allow access and updating tailored to most organizations’ data operations.
  • Links to online mapping resources.
  • Web-based user interface for ease of data management.
  • Integration with 9-1-1 DBMS and DataBond® (ALI/Location Database (LDB).
  • Extensive reporting capabilities:
    • 17 reports – all of which can be exported to Excel, PDF, etc.
    • Tracking agency and individual progress in data preparation.
  • Allows establishment of translations:
    • Allows establishment of translations:
    • Community (e.g., “North Boone” = “Beaverton”)
    • Street (e.g., “SH 76” = “Fairground Rd.” = “State Line Rd.”)

DataNexus® provides for error handling, default routing, and logging. The ECRF handles LoST error conditions per RFC 5222 and provides at least a default route set up by the administrators on a geographic basis.

DataNexus fully complies with the LoST protocol as defined in IETF RFC 5222. Additionally, it complies with:

  • IETF RFC 6739: Synchronizing Service Boundaries and Elements Based on the Location-to-Service Translation (LoST) Protocol.
  • IETF RFC 5582: Location-to-URL Mapping Architecture and Framework.
  • IETF RFC 5031: A Uniform Resource Name (URN) for Emergency and Other Well-Known Services.
  • IETF RFC 4119: A Presence-based GEOPRIV Location Object Format.
  • IETF RFC 5130: Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO).
  • NENA STA-005 (Draft): NENA Standards for the Provisioning and Maintenance of GIS data to ECRF/LVF.
  • NENA STA-006.1-201 (Draft): NENA Standard for NG9-1-1 GIS Data Model.
  • NENA 08-003 v1 and v2 (Draft): Detailed Functional and Interface Specification for the NENA i3 Solution. This has subsequently been renamed to STA-010 with version 2 currently under public review.

SpatialCentral is designed to provide a robust and flexible server-based GIS data QA / QC application, and GIS database repository, for use in the role of Spatial Information Interface (SI) at the local or regional level.

SpatialCentral allows incoming data to retain its existing data model so long as it contains all required fields (which approximate the NENA GIS draft Data Model). Users simply map existing field names to the standard names used in SpatialCentral.

SpatialCentral will then re-project the data if necessary, to WGS-84 per NENA standards. Then SpatialCentral performs approximately 36 quality assurance checks on incoming GIS data. These checks also include identifying gaps/overlaps with neighboring jurisdictions data.

SpatialCentral provides an intuitive web-based user interface which allows users to track the status of their data as well as identify potential errors. Valid GIS data is then passed to DataNexus, the LVF/ECRF. The data can also be passed to SpatialScene, a PSAP map display, or any other OGC compliant destination.

The movement of data from SpatialCentral can be immediate or delayed by an administrator setting as needed. Updates from SpatialCentral® to DataNexus® can also be manually initiated for any data layer. A user will automatically receive notification when GIS data is pushed from SpatialCentral to DataNexus. Additionally, the user can log into the SpatialCentral® web portal to view the status of their data.

Key features of SpatialCentral® include:

  • 24x7 real-time GIS data upload access.
  • On-the-fly geometry and attribution validation checks.
  • Gap / Overlap detection.
  • GIS database support for ‘Shape File’ and ‘File Geodatabase’ Esri formats.
  • File reversion support.
  • Dynamic field mapping to accommodate local GIS database structures.
  • Road Centerline, Address Point, and Polygon feature class analysis.
  • Live and fully interactive map display of validation errors location and type.
  • Dashboard monitoring for data uploads, downloads, user notification, and error counts.
  • Automated email notification for users and system administrators.
  • Stale data notification system based on administrator set time limit on date of data.
  • Activity history tracking and reporting.
  • Secure User Login for users and system administrators.
  • Real time relay of GIS updates to the LVF/ECRF.
  • Fully Esri compliant application.

Flexible and user-configurable, SpatialStation is designed to help GIS users build and validate mission critical spatial data to support the requirements of 9-1-1 Next Generation functionality for public safety and emergency response.

SpatialStation is fully supported and is constantly being enhanced. It allows a local jurisdiction’s data to be field mapped to the (draft) NG9-1-1 GIS Data Model so that all data is consistent and compliant with established schema formatting standards. SpatialStation also integrates seamlessly with 911 Datamaster’s SpatialCentral (SI) and DataNexus (LVF/ECRF) applications to facilitate automated call routing database updating.

SpatialStation performs a significant number of quality control validations:

  • Twelve attribution and geometry checks on address points.
  • Twenty-one attribution and geometry checks on road centerlines.
  • Five attribution and geometry checks on polygons.
  • Match comparison of road centerlines and MSAG records.
  • Match comparison of road centerlines and ALI records.
  • Match comparison of address points and ALI records.

Key features of SpatialStation include:

  • GIS edits prompt user for required 9-1-1 attribute inputs.
  • Configuration options for accessing a variety of data sets simultaneously.
  • Administrator password protection for configuration settings.
  • ALI change build / export.
  • MSAG & Change MSAG build / export.
  • Polygon gap analysis.
  • Multi-database ESN comparison.
  • Enhanced/simplified ArcGIS editing tools.
  • Auto field population utility.
  • Retains pending/valid statuses and notes.
  • Individual user edit tracking.
  • Visual feature edit history review capability.
  • Full GIS metrics reporting package.
  • Integrated GIS editing & traditional 9-1-1 DB data management workflows.
  • Single step data upload process to DataNexus and/or SpatialCentral.
  • Numerous user configurable tolerances and application functionality refinement controls.
  • Complete on-line documentation for users.

Flexible and highly-configurable, SpatialScene is designed to help 9-1-1 Call-Takers and EOC personnel observe, react, and manage their ongoing emergency incident activity.

OBSERVE – SpatialScene is a state-of-the-art map display for 9-1-1 call-taking Public Safety answering Points (PSAPs) and Emergency Operations Centers (EOCs). SpatialScene provides emergency management personnel with an easy-to-use and flexible map display and location query tool by merging the latest spatial data and communication technologies together for the Next Generation 9-1-1 environment. SpatialScene offers users traditional emergency event observation capabilities and simple, easy-to-use location query tools, while requiring a minimum of hardware and software.

REACT – Reacting to a 9-1-1 call or emergency event requires a map display that provides intuitive data representation. SpatialScene helps facilitate the representation of spatial location, both horizontally and vertically (supporting upcoming NENA and FCC mandates), through a complete set of cartographic rendering tools supporting landline, wireless, and VOIP call location identification. On screen annotation and markup features, as well as event notification, elevates emergency situation responses to the next level by allowing all staff in a 9-1-1 facility to share information in a spatial context through a shared map display.

MANAGE – System Administrators are provided with logical map display configuration controls as well as call history reporting for post call or emergency event review which is an important tool for emergency response managers. SpatialScene allows users to review the flow of 9-1-1 caller and event activity in the PSAP or EOC, both visually and in savable report formats. Users can watch an animated representation of an incoming call or event activity in playback mode in order to review and refine response performance.

SpatialScene integrates seamlessly with 911 Datamaster’s SpatialCentral (SI) application for automated spatial data updating. SpatialScene can also be used with 911 Datamaster’s SpatialStation application to allow user-initiated discrepancy reports to be sent to the GIS database administrator. Together, SpatialScene, SpatialCentral, and SpatialStation provide 9-1-1 authorities with a comprehensive way to observe, react, and manage their mission critical operations.

SpatialScene supports:

  • USPS Pub 28 abbreviation standards.
  • NENA NG911 GIS data standards.
  • SpatialStation 5.2 or higher (ArcGIS Desktop 10.4.1 is required to support direct integration and map updating).
  • Pictometry Electronic Field Study (EFS) Version 2.7 Production Release 1, Revision 10.

How to Obtain Specific Contracted Pricing

  1. For specific product contract pricing information, contact Eric Regnier at

Discount percentage (%) off MSRP or List Price

Category Subcategory Brand Product Description Service Description Service Category Product / Service Part Number MSRP DIR Customer Discount % off MSRP DIR Customer Price*
9-1-1 Database DataBond-ALI/LDB 9-1-1 ALI/LDB database. Unit price is per 1000 population per month. DataBond Brochure N/A N/A DM-Bond $18.75 20% $15.11
9-1-1 Installation DataBond-ALI/LDB installation and training 911 DataBond® (ALI/LDB/LIS). Initial training and implementation. Non- recurring charge Installation and training Installation DM-BOND-NRC $9,375 20% $7,556.25
9-1-1 Database DataNexus-ECRF NG9-1-1 Emergency Call Routing Function (ECRF). Unit price is per 1000 population served per month. DataNexus Brochure N/A N/A DM-ECRF $6.25 20% $5.04
9-1-1 Installation DataNexus-ECRF installation and training DataNexus® - ECRF. Initial training and implementation. Non- recurring charge. Installation and training Installation DM-ECRF-NRC $6,250 20% $5,037.50
9-1-1 Database DataNexus-LVF NG9-1-1 Location Validation Function (LVF). Unit price is per 1000 population served per month. DataNexus Brochure N/A N/A DM-LVF $7.50 20% $6.05
9-1-1 Installation DataNexus-LVF installation and training DataNexus® - LVF. Initial training and implementation. Non- recurring charge. Installation and training Installation DM-LVF-NRC $6,250 20% $5,037.50
9-1-1 Database SpatialCentral NG9-1-1 Spatial Interface. Unit price is for the 1st 1 million (or portion thereof) per month. SpatialCentral Brochure N/A N/A DM-SC1 $125,000 20% $100,750.00
9-1-1 Database SpatialCentral NG9-1-1 Spatial Interface. Unit price is per 1000 population served over the 1st 1 million per month. SpatialCentral Brochure N/A N/A DM-SC2 $125 20% $100.75
9-1-1 SaaS SpatialCentral NG9-1-1 Spatial Interface. Unit price per month. SpatialCentral N/A N/A DM-SC3 $175,000 20% $141,050.00
9-1-1 Installation SpatialCentral installation and training SpatialCentral Initial training and implementation. Non- recurring charge per PSAP. Installation and training Installation DM-SC-NRC $56,250 20% $45,337.50
9-1-1 GIS Quality Assurance SpatialStation SpatialStation®. Note Offered Price is per workstation per year. Requires Esri ArcGIS. SpatialStation Brochure N/A N/A DM-SPS $9,375 20% $7,556.25
9-1-1 Installation SpatialStation installation and training SpatialStation Initial training and implementation. Non- recurring charge per PSAP. Installation and training Installation DM-SPS-NRC $4,375 20% $3,526.25
9-1-1 Mapping SpatialScene Telecommunicator Map Display. Note Offered Price is on a per seat basis per year. SpatialScene Brochure N/A N/A DM-SSC $1,125 20% $906.75
9-1-1 Mapping SpatialScene initial license bundle SpatialScene®. Initial License Bundle per seat. Non- recurring charge per seat. N/A N/A DM-SSC-B-NRC $813 20% $655.28
9-1-1 Installation SpatialScene installation and training SpatialScene Initial training and implementation. Non- recurring charge per PSAP. Installation and training Installation DM-SSC-NRC $3,750 20% $3,022.50

Designated Order Fulfillers

911 Datamaster Fulfiller
Contact: Jim Shepard
Phone: 1- 512- 291- 3457

How to get a Quote

  1. For product and pricing information, contact Eric Regnier at

Warranty Policies

1.1. So long as the Customer has paid Datamaster all amounts due and payable pursuant to this License Agreement, Datamaster warrants that the Software licensed to the Customer will operate substantially in conformance with the Documentation for such Software for the term of this License Agreement. Datamaster shall have no obligations under this Section 10 in connection with (i) any Use of any version of the Software other than a current, unaltered release of the Software; (ii) the combination, operation, or Use of the Software with software, hardware or data other than as specified and approved by Datamaster in the Documentation and Hardware and Software Specifications (Appendix C); (iii) where any alteration, modification or addition has been made to the Software by a party other than Datamaster; and (iv) warranty claims made outside the warranty period above.

1.2. The Customer’s sole and exclusive remedy for breach of any of the foregoing warranties shall be either repair or replacement of the defective Software by Datamaster or, in Datamaster’s sole discretion, a refund of a prorated portion of the current year’s fee paid by the Customer. In order for Datamaster to be liable to the Customer under this Section 10, the Customer must notify Datamaster within the warranty period and provide a reasonable opportunity to Datamaster to cure any alleged breach.


Return Policies

Returns can be coordinated through the 911 Datamaster Help Desk .

911 Datamaster Contract Link

Data Submission

Please fill out the form below to submit your GIS data and/or ALI/MSAG databases to 911 Datamaster for review. Select Add Files to navigate to the data you wish to send then select Start Upload to complete your submission. You'll receive a confirmation e-mail once the form has been submitted and received.

Fields marked with ( * ) are required.

Please enter first name.

Please enter last name.

Please enter company name.

Please enter phone number.

Please enter email.

Please select state.

Please note that all data must be submitted in zip file format.

Add files...

Combine World Class 9-1-1 Technology with Superior ALI and GIS Data Management Services.

 PDF Click here to view the Data Services Brochure

Benefit from 911 Datamaster’s industry leading software with hosted data management services.

911 Datamaster, a long time industry leader in 9-1-1 and Next Gen 9-1-1 technology, offers its world class platforms as a managed service. Whether you are looking to upgrade your ALI database management to improve quality, control costs, and prepare for NG9-1-1 or desiring to prepare and maintain your GIS data to a quality level requisite for NG9-1-1 deployment, we have the resources and expertise to make you successful. Improve quality and control costs by letting us manage your ALI. 911 Datamaster has over 20 years of experience with database management and ALI software. With hundreds of installations throughout the U.S. and abroad, we have developed a deep knowledge of database management. We offer a simple migration from your incumbent provider to a state of the art, NG9-1-1 ready platform that can reside either on your premises or in our hosted environment. Service providers will send service orders directly to this platform where our analysts will help ensure data integrity. PSAPs can easily migrate to our geographically diverse ALIs with a few simple network changes.

DataBond®, our DBMS and ALI, is a NENA’s NG9-1-1 transitional compliant Location Database (LDB). Our LDB / ALI enables migration of your 9-1-1 system to NG9-1-1 with no changes to the underlying database or need for “fork-lift upgrades”. Traditional PSAPs and NG-capable PSAPs can utilize the same database. A web-based user interface ensures that you always have access to your data.

© 2023 911 Datamaster  |  Contact