Online Ticketing System Pre-Launch Resource Page


Migration from EDEN to GeoCall

Georgia 811 is migrating from its existing system called EDEN, to a new notification system, GeoCall. This new system has many advantages over EDEN and will help us provide greater service in the future.

GeoCall is used by twelve other states’ 811 Contact Centers, including surrounding states such as Tennessee, Alabama and South Carolina. As we migrate to the new system, we are also becoming a member of a partnership with these states which will allow us to share resources and expertise.

Deployment Date: October 15, 2020

Geocall will go live and all EDEN-related systems will go off-line. Ticketing data will be available for seven years. As this date approaches, Georgia 811 will share the hour-by-hour schedule of activities that will be occurring on the launch date.

Member Development Period

Georgia 811 is committed to providing members with information and assistance needed to update any automated systems used to receive locate tickets. Sample programming code and ticket data output will be shared with members, and Georgia 811 IT staff will host regular conference calls to assist members.

Georgia 811 GeoCall Deployment Calls

Georgia 811 will be hosting phone conference every two weeks to share project status and implementation information, as well as to answer any member questions. These calls will be hosted on Fridays at 2 PM. You can sign up for these calls by clicking here. Simply click on the sign-up link for the date when you want to attend. As calls are completed, a recording of the conference call is posted in place of the sign-up link. If you do not receive a confirmation email after you sign up, be sure to check your Junk/Spam folder.
Click here to view previous deployment calls and sign up for future calls

Member Portal

GeoCall includes a Member Portal where Members can view and respond to requests, as well as submit tickets themselves. This portal also includes functionality for homeowners and excavators.  This will replace the existing online system. A test system will be available soon.

Mobile App

Georgia 811 will be launching a replacement to the current Georgia 811 mobile applications.  You can see similar apps in the app stores for Tennessee, Alabama, South Carolina as well as other states which use the GeoCall system.

Ticket Creation Training for Georgia 811’s New Ticketing System

Georgia 811’s new online ticketing system will be launching on July 30, and we want to make sure current EDEN users are prepared for the transition. Georgia 811 will be focusing on three primary training dates to best help online users retain the information once the new system is live.

On July 27 a self-paced training option will be released that features short training modules followed by assessment questions. The entire training will last no more than one hour and will be available for users to take at their own convenience. Trainees will become Certified Web Users upon completion of this training.

Click here to register for self-paced training. You will receive email instructions on how to sign into this training by July 27.



An Overview of Changes


Here is some information on the major changes you’ll see with the move to GeoCall.

1.       Ticket Number format is changing

Ticket numbering in EDEN is a combination of three codes separated with hyphens: a date code, a three-digit type code, and a serial number.

A version number can be added to this to identify the specific ticket version as well.  So, a full EDEN ticket number looks like 02180-300-001, and a ticket number with its version would be 02180-300-001-000.

GeoCall will have a date code plus a serial number.  There are no group codes or versions.  The date code is YYMMDD, and the serial number is a six-digit serial number.  So, a GeoCall ticket number would look like 200218-001001 (for a ticket created on February 18, 2020).

2.       Ticket Versions are going away

GeoCall does not version its tickets as EDEN does.  EDEN sends out new versions of tickets for various purposes such as Additional Requests, Cancelations and Large Project Excavation Notices.  GeoCall will be handling this functionality differently using new ticket types – such as the Cancel ticket type and the Large Project Excavation ticket type along with special system responses in PRIS (see below).

3.       Grids are going away

Grids will no longer be listed on the ticket output.  This will reduce the size of the actual ticket.  In order to render the proposed dig site from your ticket management system that receives our tickets you can use the new WKT (Well Known Text), a text string representing the dig site polygon like: POLYGON (( -84.82342342 26.034534 ….

4.       Overhead Ticket Type

Overhead Service Areas will be treated differently in the new system. GeoCall will use a new ticket type to notify members when excavators request overhead protection for their overhead service areas.  These will need to be created in addition to a Normal ticket if the excavator is also digging underground.  Service area codes will be demarked as underground and or overhead and will show up on the appropriate ticket type.

5.       Insufficient Ticket Type Is Going Away

Insufficient tickets will not be available in GeoCall.  Georgia 811 will no longer be taking this type of request.

6.       Normal Tickets Associated with Large Projects are Going Away

Members who respond to a Large Project Meeting Ticket with a 10D code (Disagree to treat as Large Project – will mark in accordance with 25-9-6) will not receive a new ticket number for the associated normal ticket. Rather, automated System Response Codes will be added to the original Large Project Meeting Ticket to remind members to mark the entire dig site every 30 days (see below).



GeoCall Ticket Types


GeoCall supports the following ticket types:

Normal – Tickets for regular 30 day locate requests

Overhead – Tickets for overhead protection

Design – Tickets for design requests

Cancel – When a cancel request is received from the excavator, a Cancel ticket will be issued doing the following:

Large Project Meeting – Meeting Ticket for a large project

Large Project Excavation – Ticket for Large Project Excavation, which will have its own ticket number

Normal Ticket Example(click to expand)



GeoCall Notification Types


Emergency – Notifications reporting emergency excavations.

Damage – Notifications reporting damages.



An Explanation of System Responses


A system response is a code on a ticket that is automated in the system and not from a member utility.

System responses will be used to replace some of the functionality currently achieved with ticket versions. Their purpose is to provide member utility companies with additional information about the ticket. System responses will be used to communicate late notices, cancelations, additional requests, and some large project information (such as normal ticket date information for members who respond to Large Projects with the 10D code – Disagree to treat as Large Project – will mark in accordance with 25-9-6).

For instance, here is a comparison of how Additional Requests are done in EDEN, and how it will be done in GeoCall:
EDEN: When an additional request is received by Georgia 811, a new ticket version is created. The Remarks are updated, the digsite remains unchanged, and that new version of the ticket is sent.
GeoCall: When the additional request is received, an automatic system code is added to PRIS for the affected members. The existing ticket is then sent to affected members, with the system response in the body of the notice. For web services, this is in the XML body in the LatestResponse element, which includes the code, the description of the code and any comments:


In an email notification, the system response code will be in the Latest Response section, just below the ticket header (which includes the ticket number, type, source, etc.)

These responses will be available in the PRIS history for that ticket, so you will see member positive responses and system responses, in descending chronological order (so the last response is always shown first).  So, responses on the example above might look like this:

2/19/2020 09:40 1A Marked
2/18/2020 14:00 AR03 Facility markings no longer visible, please re-mark
2/18/2020 10:01 1A Marked