Issues to Consider When Starting Gis Project Gis Day

8/6/2019 Issues to Consider When Starting Gis Project Gis Day

1/59


2/59

SM

Issues To Consider In

a GIS Project1. Identify Your Objectives

2. Technical Considerations

3. Who Will Create the GIS?4. Designing a GIS

5 . Data Needs, Design and Capture

6. Analyzing the Data and Presenting the Results

7. Project Life Cycle


3/59

SM

Issue 1:

Identify Your Objectives


4/59


5/59

SM

What Is the Needfor a GIS?

How can GIS technology be implementedeffectively to streamline existing functions?

How can it change the way a particular goal

is achieved?

Issue 1: Identify Your Objectives


6/59

SM

What Are the Final

Products of a GIS? Presentation of quality maps and map books

Working maps

Internet maps

Reports and charts

A system that ties multiple facets into an easy to

use application that allows all users to access thedata they want and need from a central location



7/59

SM

Who Is the Intended Audience? Decision Makers/Management

Technicians

Planners

Engineers

System Operators

Customers

Public



8/59

SM

What Is the Primary

Use of the Data?

Facility Locating Customer Locating

System Inventory

Analysis of Your System



9/59

SM

Will the Data Be Used

for Other Purposes?

Modeling the System

Phase Tracing

Outage Management

Staking Sheet Generation

Driving Directions



10/59

SM

What are the Requirements ofThese Other Purposes?

Additional Software Quality Updated Data

Good Data Management

Customization



11/59


12/59

SM

Do You Plan to Start Small

Then Expand?

Start with a circuit, substation or predefined area

then expand from it Convert whole systems starting with a specific

device

What is the expansion schedule or timeline? What are the most critical areas?

Issue 1: Identify your Objectives


13/59

SM

Issue 2:

Technical Issues


14/59

SM

What Computing EnvironmentAre You Using?

Windows NT, 2000, XP

Unix Workstation

Mixed Environment

Issue 2: Technical Issues


15/59


16/59

SM

Key Factors in Choosing

a Vendor Stability

Leadership in the Industry

Integration of Existing Legacy Systems Partnerships or Long Term Alignments

Development

Flexibility

Open Architecture

Customizable Out of the box software should do 75% of what you want it to do

Cost and Maintenance Agreements



17/59

SM

Key Factors in Cost

Hardware

Software

Upgrades

Software Maintenance Agreements

Conversion

Development

Ability to Drive Technology Change Organizational Size and Position of Resources

Scope Change

Revisions



18/59

SM

Other Technical Issues How many people are responsible for making

changes to the data?

Single editor Multiple editors at one location

Multiple editors accessing a server

Who will be accessing the data?

Single user

Multiple users at one location

Several users at different locations using the internet



19/59

SM

Issue 3:

Who Will Create the GIS?


20/59

SM

In-House

Consultant

Combination of In-House employees and

Consultants

Issue 3: Who Will Create the GIS

Who Will Create the GIS?


21/59

SM

In-House Set up a GIS Steering Team

Leaders and managers.

Experts in the areas you want to incorporate.

Dedicate the people to do the work Implications

Will the employees only be dedicated to the GIS?

Do you have to hire new people to replace those

working on the GIS? Will dedicating the employees to GIS hinder thejobs of other employees?

Do they really want to work on the GIS?

Are there people trained to do GIS work?



22/59

SM

Consultant Set up a GIS Steering Team

Dedicate a Contact Person


Key member of the GIS Team

Knowledge of all parts of the system

Available throughout the process

Passionate about the project


23/59

SM

Consultant


Choose the Consultant

Has extensive knowledge of GIS and the electric

utility Capable of doing what you want them to do

Visit with them to see what they have done

Ask others about the consultant - references


24/59

SM

Consultant Set up Timeline of Deliverables


Area check copies Initial conversion completion

Updates

System integration and takeover


25/59

SM

Combination of In-HouseEmployees and Consultants Set up a GIS Steering Team

Determine Who Does What Only Work on What Has Been Agreed Upon

Agree on Timelines and Deliverables and

Remember the Goals

Work Together Not Against Each Other

Correspond Frequently



26/59


27/59


28/59

SM

Objectives of Design Results in a Well-Constructed Operational Database

That:

Satisfies objectives and supports organizational requirements Contains all necessary data but no redundant data

Organizes data so that different users can access the same data

Accommodates different views of the data

Distinguishes which applications maintain the data from which

applications access the data

Appropriately represents, codes and organizes graphical features

Issue 4: Designing a GIS


29/59

SM

Benefits From Good DesignAlthough Time Consuming Increased flexibility of data retrieval and analysis

Increased likelihood of users developing

applications Decrease time in attributing data

Data that supports different users and uses

A system that readily accommodates future

functionality Minimized data redundancy



30/59


31/59

SM

Data Modeling Model the Users View of Data

Identify organizational functions

Determine data needed to support functions

Organize data into local groups

Define Objects and Relationships

Identify and describe objects Specify relationships between objects

Document model in diagram



32/59

SM

Data Modeling Select Geographic Representation

Represent data with discreet features

Points, Lines and Polygons


Characterize continuous phenomena with rasters


33/59

SM

Data Modeling

Match Data to Spatial Elements

Determine geometry type of discrete features

Specify relationships between features

Implement attribute types for objects



34/59

SM

Data Modeling

Organize Database Structure

Organize system of features Define topological associations

Assign coordinate systems

Define relationships, rules and domains



35/59


36/59

SM

Data Design

Identify the Spatial Data Needed

Land-base

Facility

Determine the Required Feature Layers

Roads, Municipals, Water features, Parcels

Conductor, Transformer, Consumer, Poles

Issue 5: Data Design Needs and Capture


37/59

SM

Data Design How Current Must the Data Be?

For planning, the most current data may be required

For general mapping, data may be a few years old

What Data Do I Have?

Digital

Paper records Is it in a usable format?

Can it be converted?



38/59

SM

Data Acquiring Where can I Get Missing Data From?

Government entities (DOT, DNR, LMIC, County,

and Municipal) Other utilities

Other consultants

GPS

Aerial photos

DRG's (digital raster graphics)



39/59

SM

Data Acquiring

How Much Are We Willing to Pay for Data?

Most entities charge for data

Most entities request data sharing agreements

When Do You Need the Data?

Off-the-shelf" data sets can be acquired in one to two

business days

Custom sets may take weeks to prepare



40/59

SM

Data Acquiring

Will You Need Periodic Data Updates and How

Frequently?

Complete replacements

Transactional updates (changes only)

It is best to negotiate a maintenance schedule with

the initial data license



41/59


42/59


43/59

SM

Choosing the Attributes Choose the Attributes Each Feature Needs.

Identifiers of Cooperative or Company

Identifiers of substation Identifiers of circuit

Identifiers of device (Must have a UNIQUE ID such as Device

# or Account #)

Very Important. Make sure there is a non-

duplicate unique ID for every device in order totie to other software or data

Issue 5: Data Design Needs and Capture Continued


44/59


45/59

SM

Data Representation Grid System


Joe Smith is located at: T

101 R 32

Section 01

Grid 8

Sub grid 6

ID = 10132010806

i d d


46/59

SM

Data Representation Real World Coordinates

XY or Latitude Longitude

Each feature has it own real-world coordinate


I 5 D D i N d d C


47/59

SM

Data Representation Choose the Way You Want to Represent The Data

Color

Symbology g h j k w r Annotation or Labels Name NameName NAME

Offsets of Features


I 5 D D i N d d C


48/59

SM

Automation of Data Converting existing data from other systems and

formats into the same format

Digitizing data from paper Adding GPS data

Data entry of attributes

Creating topology and connectivity


I 5 D t D i N d d C t


49/59

SM

Automation of Data

Putting additional spatial data into real world

coordinates

Join adjacent data sets Updating data sets

Verifying data with GPS

Perform QA/QC Correct locations Correct attributes

Connectivity


I 5 D t D i N d d C t


50/59

SM

Conversion Issues

Keep project goals in mind

Do not add additional requirements until initial requirements

are met

What you put in is what you get out of a GIS

Stick with one software or vendor until conversion is

completed



51/59

SM

Issue 6:

Analyzing the Data

and Presenting the Results

I 6 A l i th D t d P t th R lt


52/59

SM

Analyzing Data

Referred to as Spatial Modeling

A Model is a Representation of Reality To:

Simulate a process Predict an outcome

Analyze a problem

Models in a GIS

Connectivity Tracing up stream and down

Proximity calculations

Common ancestor finding

Issue 6: Analyzing the Data and Present the Results


53/59



54/59

SM

Training Users

In-House

Software Vendors

Consultants

Conferences

Internet Classes

Local Colleges and Vocational Schools



55/59

Issue 7: Project Life Cycle Issues


56/59

SM

GIS perceived as only a automated mapping tool to replacemanual mapping

People do not want to change

Inadequate quality control Cannot access system or data

Poor project implementation

Unrealistic expectations

Poor training

Failure to plan on how to maintain the GIS data andoperations

Project cost overrun Scope change, adding premature detail

Problems That Might

Cause a GIS to Fail

Issue 7: Project Life Cycle Issues


57/59

SM

Conclusions

When Starting a GIS

Identify your objectives for the project

Examine software, hardware and vendors Determine who will create the GIS

Determine the design

Determine data needs & how to acquire

Train users

Stay focused on the goals


58/59

SM

These steps and Planning as a Team to

meet the Goals will help insure a GISthat will be Useful to all users as well as

Cost Effective to the company.


59/59

Documents

Issues to Consider When Starting Gis Project Gis Day