Follow

LDB Manager NXG Quick Reference Guide v3.11

Logging in to the DDTi LDB Manager website

  1. Go to https://ldb.ma.state911.us/
  2. At the login screen, enter your email address and password that was provided to you.*
  3. Click the Sign In

*If you have lost or forgotten your password, click the “Forgot your password” button next to the Sign In button. You will be prompted to enter the email address that was used to register with the site in order to have instructions on how to reset your password emailed to you.

 

Internet Browsers Supported - DDTi LDB Manager NXG

Currently the internet browsers supported by DDTi for the LDB Manager NXG are Internet Explorer 11, the latest Firefox and Google Chrome versions with the release of version 3.2. 

There are plans to include older versions of the internet browsers to come in future version releases to the website.

 

Technical Support

For technical support, please contact DDTi by one of the following methods:

  • Telephone: (614) 429-3384 or 1-888-800-4003

Email: ldbsupport@ddti.net

 

Steps to Correct SOI Processing Errors

To begin working on the errors, after logging on to the database through the website, the user should go through the following steps.

  1. Go to the DATA dropdown menu.
  2. To view the SOI Job History click on SOI Jobs.
  3. Select Any from Status drop down menu and optionally select Service Provider by choosing from a list. Other fields can be used to further narrow down the search on the SOI Jobs.  Click on the search green button.  All SOI Jobs that have been processed will be listed with the last file processed first.
  4. To view the SOI Rejected records, select SOI Records from the dropdown list.
  5. In the Status drop down menu choose Rejected and click on the green search button.
  6. The user may further narrow down the Rejected records to be displayed by choosing the Service Provider and specific error codes in the Error Code
  7. In the SOI Job textbox, select the SOI job by clicking on the checkbox on the left hand side of the file name and click on the green ok button. Note: you can only select one file at a time.
  8. Enter the file name desired in the FILE NAME text box and click on the green SEARCH button to displays errors that have been generated for that file specifically.
  9. Click on the Telephone Number to display the entire rejected record. (It is important for the user to correct the earlier errors first in order to avoid other errors that may be generated if not processed in order.)
  10. Click on the grey edit
  11. Edit the record depending on the error code listed at the top of the page.

 Optional Recommendation:

The user will be able to resolve errors as they appear on the page but user must be careful to resolve each error the way it should be as shown in the Step-by-Step Error Correction shown below.

 

Error Correction

All of the following steps are assuming the SOI record is correct and the user wants that action performed on the LDB database.

The Telecommunications Service Provider (TSP) will primarily be working on the following errors:

  • 205 - Migrate attempt on a non-existent TN
  • 301 - Migrate attempted on a locked TN
  • 303 - Change attempted on TN that is unlocked
  • 304 - Delete attempted on a TN that is unlocked
  • 200 - Record already exists, Insert not allowed
  • 305 - NENA IDs do not match on change or delete

 

200 Record Already Exists, Insert Not Allowed

To minimize the occurrence of this error, request that I to C be enabled for the service provider.

Fix via Website

There are a couple of ways to fix this error via the website. If the existing device’s owner is not same as SOI record’s owner, then delete the existing device record. If the existing device’s owner is the same as the SOI record’s owner, then edit the SOI record and change FOC to C.

Existing Device’s Owner = SOI Record’s Owner

  1. From SOI Records Search Results page, find device with error
  2. Click on Device ID to view the SOI Record Details page
  3. Click EDIT
  4. Change FUNCTION CODE to C - Change
  5. Click TEST to verify SOI record will pass NENA error checks
  6. Click SAVE to save the SOI record and reprocess it.

Existing Device’s Owner NOT equal SOI Record’s Owner

  1. From the Records page, find the existing device by searching by DEVICE ID
  2. Click on Device ID to view the Device Details page for the device
  3. Click DELETE to delete the device record
  4. Go to the SOI Records page, find device with error
  5. Click the record to view the SOI Record Details page for the device
  6. Click RETRY to reprocess the SOI record.

Resubmit Service Order

Existing Device’s Owner = SOI Record’s Owner

Submit a new service order for the device with FOC = C

Existing Device’s Owner NOT equal SOI Record’s Owner

Submit a new service order with a delete to delete the existing record (FOC = D) and an insert to insert the device again (FOC = I)

 

205 Migrate Attempted on a Non-existent TN

To minimize the occurrence of this error, request that M to I enabled for the service provider. NOTE for M to I to work, the submitting service provider must be verified owner of the record (according to NPAC)

Fix via Website

  1. From SOI Rejected Records Record Search page, find device with error
  2. Click on Device ID to view the SOI Record Details page
  3. Click EDIT to view Edit SOI Record page
  4. Change the FUNCTION CODE to I - Insert
  5. Click TEST to verify SOI record will pass NENA error checks
  6. Click SAVE to save the SOI record and it reprocesses the record.

Resubmit Service Order

Submit a new service order with an insert for the device

 

301 Migrate Attempted on Locked TN

Fix via Website

  1. From the SOI Record Search page, click on DEVICE ID
  2. View details on the SOI Record Details tab
  3. Copy Device ID from SOI Record Details page, click on Data dropdown select Records link and paste number in Device ID textbox and click on search
  4. Click on Device ID
  5. Click UNLOCK to unlock on the device on Device Details tab of the existing device record
  6. Go to the SOI Rejected Records page, find same device with error
  7. Click RETRY to reprocess the SOI record.

Resubmit Service Order

Submit a new service order with an unlock for the device followed by the migrate

 

303 Change Attempted on a TN that is Unlocked

There are two different methods for resolving this error depending on what the user is trying to accomplish. If you are trying to relock the existing record and change it, please follow the first method.  If you want to migrate it to a different service provider, please follow the second method.

Fix via Website

Existing device’s owner = SOI record’s owner

  1. Click on Device ID from the SOI Record Search Results page
  2. From the Records link under the Data Dropdown, find the existing locked device by searching for DEVICE ID from the Device ID textbox, click on search
  3. Click DEVICE ID to view the Device Details on the Device Details Tab in the Device page
  4. Click LOCK to relock the existing device record
  5. Go to the SOI Rejected Records page, find device with error
  6. Click RETRY to reprocess the SOI record.

Existing device’s owner is not SOI record’s owner

  1. From SOI Rejected Records page, find device with error
  2. Click on Device ID to view the SOI Record Details page
  3. Click EDIT to view Edit SOI Record page
  4. Change FUNCTION CODE to M - Migrate
  5. Click TEST to verify SOI record will pass NENA error checks
  6. Click SAVE to save the SOI record and reprocess it.

Resubmit Service Order

Submit a new service order with a migrate for the device

 

304 Delete Attempted on a TN that is Unlocked

Fix via Website

  1. From the Records page, find the existing locked device by searching DEVICE ID
  2. Click on Device ID to view the Record Details page
  3. Click LOCK to relock the existing device record
  4. Go to the SOI Rejected Records page, find device with error
  5. Click RETRY to reprocess the SOI record.

Resubmit Service Order

Submit a new service order with a migrate for the device followed by a Delete

 

305 NENA IDs Do Not Match on a Change or Delete

Fix via Website

FOC = C

  1. Select Records from the Data dropdown menu
  2. From the Records Search page, find the existing locked device by searching DEVICE ID
  3. Click on DEVICE ID to view the Record Details page
  4. Click UNLOCK to unlock the existing device record
  5. Go to the SOI Rejected Records page, find device with error
  6. Click EDIT to view Edit SOI Record page
  7. Change FUNCTION CODE to M - Migrate
  8. Click TEST to verify SOI record will pass NENA error checks
  9. Click SAVE to save the SOI record and reprocess it.

FOC = D

  1. Select Records from the Data dropdown menu
  2. From the Records Search page, find the existing locked device by searching DEVICE ID
  3. Click on DEVICE ID to view the Record Details page
  4. Click DELETE to the deleting the existing record
  5. Go to the SOI Rejected Records page, find device with error
  6. Click SAVE to save the record and since the record has already been deleted.
  7. Another Rejected (Deleted by Option to Ignore) error will be generated.

 

Bulk Editing Functionality

The user must have the bulk editor role to be able to perform bulk actions and must have the appropriate service provider associations. The default value is 1000.  Bulk editing is available for Rejected SOI Records, Devices and Discrepancies.  Please see the appropriate section below for details.

Rejected SOI Records

Bulk Edit:  A user can select a group of rejected SOI records and start a task to bulk edit all of the selected records. The fields that can edited are Function code, Class of service, Type of service and Customer code. A task will edit each selected SOI record and report back the records edited along with their status. The task can be found in the task history (SOI Record Bulk Edit).

  1. From SOI Records Search page, chose Status of Rejected (and any other pertinent information that will limit the desired selection criteria) and click SEARCH.
  2. Chose records the user would like to bulk edit by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose EDIT.
  4. Once in the SOI Records Bulk Edit screen, chose the information that needs to be edited (Function Code, Class of Service, Type of Service, Customer Code).
  5. Click on the EDIT box at the bottom of the field that requires modification.
  6. Chose the appropriate action required to correct the discrepancy. Multiple fields can be updated simultaneously.
  7. The number of records that will be updated will be indicated in the Records Selected field.
  8. If desired, click the box titled EMAIL NOTIFICATION under Bulk Edit Options. This will send the user an email once the process is complete.
  9. Click RUN
  10. The user will be routed to the SOI Records Search page and will receive a message stating “The requested Bulk Edit is in progress. View the status on the Task History Details Page”.
  11. Click on the TASK HISTORY DETIALS PAGE
  12. The Task History SOI Record Bulk Edit page will provide a summary of the changes and if they were Accepted, Not Processed, Rejected or Skipped.

Bulk Retry:  A user can select a group of rejected SOI records and start a task to retry all of the selected records. The task will retry each selected SOI record and report back the records tried along with their status. The task can be found in the task history (SOI Record Bulk Retry).

  1. From SOI Records Search page, chose Status of Rejected (and any other pertinent information that will limit the desired selection criteria) and click SEARCH.
  2. Chose records the user would like to bulk Retry by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose RETRY
  4. On the SOI Records Bulk Retry page, the number of records selected will be populated based on the number of records selected.
  5. If desired, click the box titled EMAIL NOTIFICATION under Bulk Edit Options. This will send the user an email once the process is complete.
  6. Click RUN
  7. The user will be routed to the SOI Records Search page and will receive a message stating “The requested Bulk Retry is in progress. View the status on the Task History Details Page”.
  8. Click on the TASK HISTORY DETIALS PAGE
  9. The Task History SOI Record Bulk Retry page will provide a summary of the records submitted for retry and if they were Accepted, Not Processed, Rejected or Skipped.

Bulk Delete: A user can select a group of rejected SOI records and start a task to delete all of the selected records. The task will delete each selected SOI record and report back the records deleted along with their status. The task can be found in the task history (SOI Record Bulk Delete).

  1. From SOI Records Search page, chose Status of Rejected (and any other pertinent information that will limit the desired selection criteria) and click SEARCH.
  2. Chose records the user would like to bulk Delete by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose DELETE.
  4. On the SOI Records Bulk Delete page, the number of records selected will be populated based on the number of records selected.
  5. If desired, click the box titled EMAIL NOTIFICATION under Bulk Edit Options. This will send the user an email once the process is complete.
  6. Click RUN
  7. A message box will appear verifying Delete all the records
  8. Chose OK or CANCEL
  9. By choosing OK, the user will be routed to the SOI Records Search page and will receive a message stating “The requested Bulk Delete is in progress. View the status on the Task History Details Page”.
  10. Click on the TASK HISTORY DETIALS PAGE
  11. The Task History SOI Record Bulk Delete page will provide a summary of the records submitted for deletion and if they were Not Processed, Rejected-Deleted or Skipped.

Devices

Bulk New: This allows the user with the Bulk Editor role to insert devices with all the same information in bulk. If a Device ID with the range specified in the wizard is already in use, the entire task will fail and the user can view the errors in the task.

  1. On the Record Search page, click BULK NEW.
  2. Enter the appropriate information for Bulk Device ID Start Range, Bulk Device ID End Range, Service Provider, Class of Service and Type of Service, click NEXT.
  3. Enter the appropriate location information and click NEXT. If the location is invalid and you would still like to add it, click “Create/Update discrepancy and assign to GIS”.
  4. Add any appropriate additional information, click RUN.
  5. The user will be routed to the Record Search page and will receive a message stating “The requested Device Bulk Insert is in progress. View the status on the Task History Details Page”.
  6. Click on the TASK HISTORY DETIALS PAGE
  7. The Task History Device Bulk Insert page will provide a summary of results.

Bulk Edit:  A user can select a group of devices and start a task to edit all of the selected records to another value. The task can be found in the task history (Device Bulk Edit).

  1. From the Record Search page, enter any pertinent information that will limit the desired selection criteria and click SEARCH.
  2. Chose records the user would like to bulk edit by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose EDIT.
  4. Once in the Device Bulk Edit screen, chose the information that needs to be edited (House Num, Street Name, etc).
  5. Click on the EDIT box at the bottom of the field that requires modification.
  6. Chose the appropriate action required to correct the discrepancy. Multiple fields can be updated simultaneously.
  7. The number of records that will be updated will be indicated in the Records Selected field.
  8. If desired, click the box titled EMAIL NOTIFICATION under Bulk Edit Options. This will send the user an email once the process is complete.
  9. Click RUN
  10. The user will be routed to the Record Search page and will receive a message stating “The requested Device Bulk Edit task is in progress. View the status on the Task History Details Page”.
  11. Click on the TASK HISTORY DETIALS PAGE
  12. The Task History Device Bulk Edit page will provide a summary of the changes.

Bulk Delete: A user can select a group of Devices and start a task to delete all of the selected records. The task will delete each Device and report back the records deleted along with their status. The task can be found in the task history (Device Bulk Delete).

  1. From the Record Search page, enter any pertinent information that will limit the desired selection criteria and click SEARCH.
  2. Chose records the user would like to bulk Delete by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose DELETE.
  4. On the Device Bulk Delete page, the number of records selected will be populated based on the number of records selected.
  5. If desired, click the box titled EMAIL NOTIFICATION under Bulk Delete Options. This will send the user an email once the process is complete.
  6. Click RUN
  7. A message box will appear verifying Delete all the records
  8. Chose OK or CANCEL
  9. By choosing OK, the user will be routed to the Record Search page and will receive a message stating “The requested Device Bulk Delete is in progress. View the status on the Task History Details Page”.
  10. Click on the TASK HISTORY DETIALS PAGE
  11. The Task History Device Bulk Delete page will provide a summary of the records submitted for deletion and if they were Not Processed, Rejected-Deleted or Skipped.

Bulk Unlock:  A user can select a group of Devices and start a task to unlock all of the selected records. The task will unlock each Device and report back the records unlocked along with their status. The task can be found in the task history (Device Bulk Unlock).

  1. From the Record Search page, enter any pertinent information that will limit the desired selection criteria and click SEARCH.
  2. Chose records the user would like to bulk Unlock by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose UNLOCK.
  4. On the Device Bulk Delete page, the number of records selected will be populated based on the number of records selected.
  5. If desired, click the box titled EMAIL NOTIFICATION under Bulk Unlock Options. This will send the user an email once the process is complete.
  6. Click RUN
  7. The user will be routed to the Record Search page and will receive a message stating “The requested Device Bulk Unlock is in progress. View the status on the Task History Details Page”.
  8. Click on the TASK HISTORY DETIALS PAGE
  9. The Task History Device Bulk Unlock page will provide a summary of the results.

Discrepancies

Bulk Assign:  A user can select a group of open discrepancies and start a task to re-assign all of the selected records to another group or user. The task will allow a user to select multiple open discrepancies and reassign them to a different group and/or add a comment to the selected open discrepancies.  The task can be found in the task history (Discrepancy Bulk Assign).

  1. From Discrepancy Search page, chose Status of Open (and any other pertinent information that will limit the desired selection criteria) and click SEARCH.
  2. Chose records the user would like to bulk Assign by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose ASSIGN.
  4. On the Discrepancy Bulk Assign page, the Assignments section will show the number of selected records as well as who those open discrepancies are currently assigned to. Also, the number of records selected will be populated based on the number of records selected in the records Selected text box.
  5. From the Assignment Group dropdown menu, the user can choose the group that the open discrepancies selected should be assigned to and add comments to the Comment text box.
  6. If desired, click the box titled EMAIL NOTIFICATION under Bulk Assign Options. This will send the user an email once the process is complete.
  7. Click RUN.
  8. When the run button is clicked, a background process is started that will assign each the open discrepancies to the selected Assignment Group and add a comment to each discrepancy. The results of the process can be found on the Task History page.
  9. Click on the TASK drop down menu, select HISTORY from the list. Select the task and the Task History for the Discrepancy Bulk Assign is displayed. 
  10. The Task History Discrepancy Bulk Assign page will provide the update criteria including the Assignment Group and Comments added as well as a summary of results for the records submitted for reassignment.

Bulk Edit:  A user can select a group of open discrepancies and start a task to edit all of the selected records to another value. The task can be found in the task history (Discrepancy Bulk Edit).

  1. From the Discrepancy Search page, chose Status of Open (and any other pertinent information that will limit the desired selection criteria) and click SEARCH.
  2. Chose records the user would like to bulk edit by clicking on the CHECK BOX to the left of the Device ID.
  3. At the bottom of the screen, click on BULK ACTIONS and chose EDIT.
  4. Once in the Discrepancy Bulk Edit screen, chose the information that needs to be edited (House Num, Street Name, etc).
  5. Click on the EDIT box at the bottom of the field that requires modification.
  6. Chose the appropriate action required to correct the discrepancy. Multiple fields can be updated simultaneously.
  7. The number of records that will be updated will be indicated in the Records Selected field.
  8. If desired, click the box titled EMAIL NOTIFICATION under Bulk Edit Options. This will send the user an email once the process is complete.
  9. Click RUN
  10. The user will be routed to the Discrepancy Search page and will receive a message stating “The requested Discrepancy Bulk Edit task is in progress. View the status on the Task History Details Page”.
  11. Click on the TASK HISTORY DETIALS PAGE
  12. The Task History Discrepancy Bulk Edit page will provide a summary of the changes.

 

Discrepancy Review

  1. Select Discrepancies from the Data dropdown menu
  2. Enter the appropriate search criteria and click SEARCH (or for a full list of discrepancies just click SEARCH)
  3. On the Discrepancy Search Results page, click on the Discrepancy you wish to view
  4. Click the ASSIGNMENT HISTORY tab
  5. The Comments section contains the relevant information

To fix the Discrepancy via the LDB Manager website

  1. Click the LOCATION INFORMATION tab
  2. Click EDIT
  3. Make the appropriate correction
  4. Click VALIDATE
    1. If the discrepancy is now LVF valid a “Validation SUCCESSFUL” message is displayed at the top of the page, click SAVE
    2. If it is not LVF valid, a “Validation FAILED” message is displayed at the top of the page
      1. Please investigate further with the appropriate agency and add a Comment under the DISCREPANCY DETAILS tab by clicking EDIT and adding any pertinent information, click SAVE

Discrepancy Severity Definitions

Each discrepancy is assigned a severity.  Critical, high and moderate discrepancies require more immediate attention than low discrepancies because they could impact call routing.  Here is a brief definition of each severity level.

Critical: Unable to locate address error, or other error that returns no mappings or call routing at all. This is typically a server error and should be reported to DDTi immediately.

High: Default mapping or call routing returned.  This is typically configured to be one PSAP for the entire state.

Moderate: Multiple mappings or call routings returned with matching criteria. In this case the system will randomly select one of the mappings returned which may or may not be correct.

Low: Single mapping or call routing is returned but contains some invalid fields and may not be a valid dispatch location.

Filtering Discrepancies

There is an Advance Search section at the top of the Discrepancies page with the following searchable fields:

  • DEVICE ID
  • SUB STATUS
  • CREATED ON
  • CUSTOMER
  • HOUSE NUMBER (HNO)
  • PREFIX (PRD)
  • STREET NAME (RD)
  • TYPE (STS)
  • POST DIR (POD)
  • COMMUNITY (A3/PCN/COMM)       
  • STATE (A1)
  • ZIP CODE (PC)

The user may search on any one field or multiple fields at any time.

If multiple fields are used in the search, then all values entered must match in order for the record to be displayed.

To include closed discrepancies: Click the checkbox located next to the INCLUDE CLOSED DISCREPANCIES

Similar Locations

Similar locations for an address are displayed at the bottom of the details and edit pages of the discrepancy location information when user clicks on validate button. Similar locations for an address (if present) always are displayed at the bottom of the edit page.  On the edit page the user has the ability to select an address, select it's fields and update the page with the selected fields.

  1. From the Discrepancy Location Information page, click VALIDATE.
  2. The blue notification box at the top of the page will notify the user if similar locations are available for the active discrepancy. If similar locations are available, they will be listed at the bottom of the page.
  3. Click on an address in the similar locations list (bottom left) to see it populate the compare box (bottom right). The compare box compares the original value to the LVF value.
  4. Click EDIT.
  5. To apply the values from the LVF to the location information of the discrepancy, check all values you wish to apply and click APPLY.
  6. Click SAVE.

Sub Address Components in the LDB

The LDB follows the NENA NG9-1-1 Civic Location Data Exchange Format (CLDXF).  This format has separate fields designated for the sub address elements of Building/Floor/Unit/Room/Seat.  LVF validation requires matches between the phone record and the GIS data at the sub address level.  There are two different ways to update this information on the phone record.

  1. Update via the LDB Manager
    1. Click on the discrepancy you wish to edit
    2. Click on the Location Information tab
    3. Click on edit
    4. Update the appropriate field
    5. Click validate
    6. If validation is successful, click save
  2. Update via SOI file
    1. Update the Comments field on the phone record with the appropriate field name or token followed by the value (i.e. if the update is to make UNIT = 10, then place UNIT 10 in the Comments field). When the SOI file is processed the value of 10 will be parsed from the Comments and placed in the UNIT field.
    2. Please see TSP Guidelines for Sub Address Parsing for more information

Discrepancy Sub Status

A discrepancy can now have a sub status value, which is helpful. When a discrepancy is first created, the sub status will be null.  A user may assign a sub status value to a discrepancy from the discrepancy details edit page.  A sub status is used to specify what is happening with the discrepancy for internal review or requesting action from an external group.  To assign a sub status, perform the following steps:

  1. On the Discrepancy Details page, click edit.
  2. Click Choose on the sub status box and select the appropriate sub status.
  3. Add an appropriate comment and click save.

Sub Status can also be assigned in bulk from the Discrepancy Bulk Assign page.

DISCREPANCY SUBSTATUS

DEFINITION

Subaddress Issue

GIS internal substatus – the discrepancy lies within the subaddress.

Non-Occupiable Structure

GIS internal substatus – the GIS structure is not occupiable.

Reassigned

When DA or SP are reassigning a discrepancy to GIS.

GIS Update Pending

A GIS update is coming in the next export.

GIS Reviewing

GIS is holding on and doing research.

DA Reviewing

Discrepancy Arbitrator is holding on and doing research.

Translate Requested

A translate is needed (and usually the discrepancy fixed in the process). 

GIS Update Requested

A change / update to the GIS data is requested.

SP Reviewing

Service Provider is holding on a doing research

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk