POBOnline
  Home
  Subscribe
  RPLS.com Community
  eNews Subscription
  eNews Archive
  Subscription Customer Service
  Online Updates
  Latest News
  Calendar of Events
  Call for Papers
  Webinars
  Fun + Games
  New Products
  Surveying in the Headlines
  Current Issue
  Cover Story
  Features
  Columns
  Resources
  Archives
  Classified Ads
  Classified Listings
  Digital Edition Archives
  Distance Education
  Geo Locator Buyers Guide
  Industry Links
  Information Showcase
  Market Research
  POB Store
  Product Showrooms
  Product Surveys
  POB Info
  Special Collections
  GIAA Mailbag/Tool Tips
  GPS Observer Series
  Site Prep
  Surveying GIS
  Surveyor + the Law
Search in: EditorialProductsCompanies
The Data Czar: Diagramming Your Processes
by Darron Pustam, MBA, GISP
June 23, 2009

ARTICLE TOOLS
EmailEmailPrintPrintReprintsReprintsshareShare



All systems—including geographic information systems—contain individual interrelated processes. The smallest functionality affects the process itself and, as a result, the entire system. Once you have a thorough understanding of your user data needs, the next step is to begin mapping the major workflow process in your organization from beginning to end. A typical surveying and mapping firm can use the acronym STAMP as a starting point:
  • Survey – Capture raw data.
  • Transform – Convert the raw data to features.
  • Analyze – Look for relationships in the data.
  • Map – Display the data.
  • Print – Create a hardcopy of map of the data.
(To me, this is a perfect acronym for GIS. It embraces the core processes involved in the system’s creation and also confers an authoritative certification.)

Begin by drawing a circle around each of the five interior processes. Use direction arrows in between each to indicate the flow of data.

Next, look for other processes that are related to these initial five. Draw circles around each of them as well. Connect these circles to your initial five and indicate the flow of data from one circle to the next by arrows. This stage is purely conceptual, and all software and hardware requirements should be ignored. A diagram such as this one is priceless—it indicates how your organization works and how each process is dependent on the other.

In any system, when you touch one process, all the related processes are affected. As you build out your conceptual diagram, the relationships that appear will help in assigning the appropriate resources.

Remember: To build efficient and timeless processes within your organization, data must flow smoothly from process to process and do so from a single source. If we build better systems from the start, the reality of true integration of data and the relationships that lie within will be awakened.


What do you think? Please post your comments below.

Other posts in this blog:
The Data Czar: Getting Over the Ownership Mentality
The Data Czar: Breaking Down User Data Needs


Darron Pustam, MBA, GISP
dataczar@att.net
Darron Pustam, MBA, GISP, manages the Data Czars group on LinkedIn—a group that is “passionate about the efficient capture and routing of data throughout any organization.” He also consults on GIS-related issues. Pustam can be reached at dataczar@att.net.

Links

|PrintEmail
  Comments (0)Post a Comment
 

No HTML or BBCode in comments please.
 


Did you enjoy this article? Click here to subscribe to the magazine.














BNP Media
© 2010 BNP Media. All rights reserved. | Privacy Policy