Leveraging Web-GIS to automate and streamline Natural Gas availability requests

Wayne MeyerManager, GISSCANA Corporation

Sahadeb DePrincipal ConsultantUtility GIS PracticeInfosys Limited

* This work had been undertaken when Sahadeb was employed with SCANA Corporation

*

Driving Force…

• Save Time - particularly on the requests that lead to no further action.

75% of the requests were non-servable.• Store Request Location for future analysis

Three pieces to the puzzle …

External Customer Facing Web Page

Implemented through Java Script and Bing Map (NO ESRI

or ArcGIS Server)

GIS Web Service

(Decision Engine)

Implemented through ArcObjects and served from an ArcGIS Server

Internal Employee Facing Web Page

Implemented through ArcGIS Server Silverlight API and Bing

Map

----- CAPTURE ----- ----- DECISION ----- ----- ANALYSIS -----

Mutually ExclusiveCollectively Exhaustive

Capture and Decision work very closely

Non – GIS Data

CAPTURE DECISION

User enters the address

Place a pushpin on the geocoded location representing

request location

User fine tunes the location dragging & relocating the pushpin

and request a decision

Buffer the point with a distance of 150’

Intersect with the Gas Main FC

Feature Count > 0

Geocode

Send a ‘Yes’

Buffer the point with a distance of 1000’

Intersect with the Gas Main FC

Feature Count > 0Send a

‘Maybe’

Send a ‘No’Receive the decision and communicate with

the user

Yes

No

YesNo

External customer facing web front end (CAPTURE)

Non – GIS Data

https://www.sceg.com/for-my-home/start-my-service/gas-availability

12

External customer facing web front end (CAPTURE)

Sahadeb De | Gas Availability at SCANA Corp

Non – GIS Data

3

4a

4b

External customer facing web front end (CAPTURE)

Non – GIS Data

3

The decision logic and the response

Radial Distance between a Location and the nearest Gas Main

Response

Less than or equal to 150 feet Yes

Between 150 feet and 1000 feet Maybe

More than 1000 feet No

The Radial versus Manhattan distance

Radial Manhattan

Storing the requests for further analysis

Non – GIS DataGIS Web Service

(Decision Engine)

Internal Employee Facing

Web Page

----- DECISION ----- ----- ANALYSIS -----

----- STORE ----- Production Geodatabase

----- COMMUNICATE -----

emailemail

Targeted communication

Gas Division Email Recipient

0 (None) Recipient 1, Recipient 2

1 (Western) Recipient 1, Recipient 2, Recipient 3, Recipient 4

2 (Southern) Recipient 1, Recipient 2, Recipient 5, Recipient 6

3 (Central) Recipient 1, Recipient 2, Recipient 7, Recipient 8

4 (Eastern) Recipient 1, Recipient 2, Recipient 9, Recipient 10

5 (Low Country) Recipient 1, Recipient 2, Recipient 11, Recipient 12

6 (Coastal District) Recipient 1, Recipient 2, Recipient 13, Recipient 14

Recipient 1

Recipient 2

Recipient 3Recipient 4

Recipient 5Recipient 6

Recipient 7Recipient 8

Recipient 9Recipient 10

Recipient 11Recipient 12

Recipient 13Recipient 14

Coastal Dist.

Low Country

EasternCentral

Western

Southern

Email to Sales with a web link to internal app

Analysis

• Search – Temporal, spatial, and decision

• Export results in excel for further analysis and share

• Group email using outlook

• Measure distance and area

Analysis

• Predefine Area of Interest• Get email notification

when a predefined number of requests come from that area

• Calculate the feasibility of growth / new business

• Use this AOI as a project boundary

10.2.1 Integration

Question?