FME Before You Dig

Richard SnyderGIS Administrator

Sunesys, LLC

Dark Fiber provider for over 25 years 12 States across the country Over 10,000 Route Miles Roughly 1,000,000 Fiber Miles

OSS at Sunesys

GIS Physical Network

Oracle Spatial AutoCAD Map

Logical Network Smallworld

Web Applications FME

FME at Sunesys

Reports Sunesys USA, Fiber Mileage Report

GIS Data Management Scorecard, AutoCAD Backups

OSS-BSS Integration CLLI Codes

Maintenance Applications NJUNS, OneCall

What is OneCall?

If your company is planning to installunderground facilities, it must contact the State-run OneCall Ticketing System before digging

Each OCTS is different, but they do share some characteristics A company or individual contacts their OCTS,

providing location information about the dig site The OCTS creates a ticket for that location, and

sends it to its registered members with facilities in the area

Some OCTSes require ticket response codes

Sunesys OneCall Business Requirements

Register underground facilities with each OCTS and keep them up-to-date

Mark Conflict locations in the field Conflict locations are tickets where Sunesys

underground facilities could be damaged if not properly marked

Ticket response times Both for field marking and providing response codes Normal tickets – 3 days Emergency tickets – 3 hours

Sunesys’ Old Process

OCTS Registered Locations Updated manually, locations added one-at-a-time Hundreds of locations to track per OCTS Incorrectly placed plant or proposed routes that

never became as-built remained registered with OCTS more often than not

Contractors managed OneCall Sunesys invoiced for admin fees and marking fees Invoices provided little detail of cost breakdowns

Sunesys’ Current Process

OCTS Registered Locations In FME Server, on the first of every month:

GIS underground changes selected Shapefile created per OCTS where changes occurred Email sent to admin with list of OCTSes to update

Update process is different for each OCTS

Sunesys OneCall Automated Response System SOCARS processes tickets and response codes

SOCARS Process

Web Service Tickets Terribly boring

Email Tickets Exchange service creates DB record Ticket information parsed from email

OCTS Ticket Number Type (Normal, Emergency) Location

All scripts run in FME Server on an hourly basis

SOCARS Process

Ticket locations geocoded Multiple locations per ticket

Address Nearest Intersection

Points buffered based on return results Lower quality result = larger buffer

HullReplacer grouped by Ticket Number Tickets tagged with Locating Contractor Service

Areas and Email Addresses

All scripts run in FME Server on an hourly basis

SOCARS Process

Tickets spatially related to GIS records Buffered underground facilities group by PDF Link

Non-conflicts OCTS that don’t require Response Codes

Ticket Status set to “Closed” OCTS that require Response Codes

Tickets tagged with Non-conflict response codes Ticket Status set to “Response Ready”

All scripts run in FME Server on an hourly basis

SOCARS Process

Tickets spatially related to GIS records Buffered underground facilities group by PDF Link

Conflicts PDF Links checked

Existence File size

Ticket Status set to “Email Ready”

All scripts run in FME Server on an hourly basis

SOCARS Process

Tickets spatially related to GIS records Buffered underground facilities group by PDF Link

Investigates Trouble geocoding ticket address PDF Link issues

Not assigned to underground in GIS Too big to send via email File missing

KML of ticket location created Ticket Status set to “Email Ready”

All scripts run in FME Server on an hourly basis

SOCARS Process

Ticket Emails Sent Conflicts sent to Locating Contractors

PDF links attached Investigates sent to GIS Team

KML links attached Underground Facilities KMLs updated daily

All scripts run in FME Server on an hourly basis

SOCARS Process

Ticket Emails Processed Locating Contractors mark facilities in the field

Reply to ticket emails with Response Code Investigators manually check ticket locations

Conflicts sent to Locating Contractors Non-conflict tickets identified, SOCARS updated Missing PDF links fixed, tickets re-processed

All scripts run in FME Server on an hourly basis

SOCARS Process All scripts run in FME Server on an hourly basis

Locating Contractor Emails with Response Codes Exchange Service creates DB record Response Codes Parsed Ticket status set to “Response Ready”

Response Codes Pushed to OCTSes Web Services

Terribly Boring Python-based Internet Browser sessions

Scripts simulate users posting response codes Ticket status set to “Closed”

SOCARS Database

Timestamps OCTS Email Received Ticket Processed Email Sent Email Received Response Code Posted Ticket Closed

KPI Reports

SOCARS Benefits

Significantly reduced contractor fees Administrative fees are virtually nonexistent Contractors only invoice Sunesys for conflict tickets

Auditing trail helps alleviate legal issues Overall number of tickets are reduced because

registered plant locations are much more accurate than in the past

Combined with contractor invoices detailing time spent per ticket, invoice auditing is possible

Thank You!

Questions?

For more information: rsnyder@sunesys.com Sunesys, LLC