GIS- Management

8/13/2019 GIS- Management

1/24

GIS: The Management

Perspective


2/24

GIS Management

Management decisions are the single mostimportant component inherent in creating asuccessful GIS

Management has the big picture perspective Budget

User expectations

Planning

Technical implementation

I am yet to hear about a single GIS project thatfailed due to technical considerations


3/24

Some general keys to success

Organization

Justification


4/24

Organization of the study/people

Emphasize your talent and ideas.

Give the reviewer an idea of how your

project is going to function on a daily basisProvide milestones for the implementation

Emphasize project quality and uniqueness


5/24

A word about need based

arguments

Who are you more inclined to fund:

My department is a mess and I need this cool

software and analysis system to straighten itout, but I dont have the money to make it work

Were doing an excellent job but have some

innovative ideas we would like to implement.

Heres our plan. Will you help us dosomething new and exciting?


6/24

Selling points

Emphasize advantages of GIS to individual users and entireorganization

Require high level of competency by all participants

Ensure high level of management commitment from all management

levels in the organizationRequire participation in team building and team participation within &

between departments

Ensure minimum data quality and access for all users

Require development team to set realistic expectations

Minimize time between user needs assessment and availability ofuseful products.

Develop positive attitude toward change within organization

Ensure level of technology is appropriate for intended uses

Highly visible Pilot Project that is successful


7/24

GIS Development CycleNeeds Assessment

Creation of an implementation plan

Develop a theoretical framework

Survey of Available Data

Survey of GIS Hardware and Software

Detailed Database Planning and Design

Database Construction

Pilot Study/Benchmark Test

Review/modify the original plan

Acquisition of GIS Hardware and Software

GIS System Integration

GIS Application Development

GIS Use and Maintenance


8/24

The Needs Assessment

This is the single most important element in

GIS development

Must consider 3 factors:Who are the users?

What is the end product?

Who is going to manage the GIS (oversight)? Accountability

Fiscal responsibility


9/24

Basis for Needs Assessment

Describing their needs to the GIS analysts

Learning what the GIS will be capable of

accomplishing for themUnderstanding the nature of the GIS

development cycle - the time involved and

the costs.


10/24

The implementation plan

Define the scope of the project

Spatial boundaries

End productsParticipants/users

Create project goals and timelines

Assign responsibilities


11/24

Develop a theoretical framework

Sketch out how things will work

Work flow

Data flowQuality assurance

Documentation

Procedures!!!!

Training and consensus building


12/24

Survey available data

DO NOT RE-INVENT THE WHEEL!!!

Become familiar with the origin of data

Maricopa County Association of Governments puts out

a street layerThey get it from ESRI

ESRI gets it from TIGER line files

TIGER line files originate from the Census

The Census gets them from ADOT, MCDOT, andmunicipal government

Get out there and look to see whos producingdata


13/24

Survey of hardware and software

Do not just limit software search to GIS packages

Include all of the software being used by

prospective userssee if it can integrate

Likewise for hardwaremost municipalities and

organizations use many different platforms

TALK TO VENDORS AND GET ON SITE

DEMONSTRATIONS


14/24

Detailed database planning and

design

For our purposes well always base things

upon an RDBMS

Many ways to diagram, but well useEntity-Relationship (ER) diagrams

For GIS, its best to construct ER diagrams

based upon cardinality


15/24

Cardinalitythe GIS application

of an RDBMS

Attributes can be single or multi-valued.

Species is a single-valued attribute of

FOREST-STAND

FACILITY has an attribute called PointId

which is the identification for the spatial

location of instances of the entity. It is possible

for a given facility to span two distinct pointloocations.


16/24

Cardinality contd

Entity-entity relationships are described by

cardinality which may be:

One to one. A FOREST can have only one

MANAGER and a MANAGER can have only oneFOREST

Many to one. Many FACILITIES may be contained

within one FOREST

Many to Many. The relationship water_supply mayhave many entries and may be connected to many

entriesFACILITIES, FOREST, etc


17/24

Diagram Characteristics

Boxes represent entities

Ovals represent attributes

Diamonds represent relationshipsNote how cardinality is depicted

Key attributes are underlined

Multi-valued attributes are in double ovals


18/24

Entity-Relationship (ER)

DiagramsA Conceptual Model


19/24

Exercisework in pairs10

minutes

Choose whose job you want to model

Pick a feature that matches each geometrytype (point, line). For example

For FD points, pick hydrants and pump stations

For FD lines, pick streets and water mains

For FD polygons, pick service areas and zoning

Sketch an ER diagram similar to the oneshown for your job


20/24

Database Construction:

Additional Considerations

What will be the source for each data item?

How will sharing be arranged? . . purchase? . . license? . .other agreement?

Who will own the data?How will new GIS data be integrated with existing datafiles (legacy systems)?

Who will be responsible for updates to the data?

How will the cost of the data (creation and maintenance)be allocated?

Who will provide public access to the data?

Who will be responsible for data archiving and retention?. . of the original? ..of copies?


21/24

Pilot Study/Benchmark Test

Pick a subset that is representative of all

assets/arenas to be incorporated in the GIS

Involve all parties and usersDog and pony showGET FEEDBACK!


22/24

Review and modify

Review and modify plan

Achieve buy-in

Do not move forward until pilot studycomplete and all users are satisfied


23/24

Purchase hardware and software

Talk to your purchasing folks up front

Learn the purchasing rules

Competitive bidscreate equalizers


24/24

Roll it out

System integration

Subsequent application development

Use and maintenance

Documents

GIS- Management