Vol 2 - No 1

Data Management Strategies: Going Beyond the Model

Written by Marco Cecala

Created on Monday, 30 January 2012 19:29

A 532Kb PDF of this article as it appeared in the magazine—complete with images—is available by clicking HERE

One of the big advantages of our magazine is the talent. Industry leading experts are always providing the user with newer and better ways to build data. As my role at Take-off Professionals has progressed from full time data building to some data and more management, I get a chance to work with our customers in a different capacity.

Once a job has been built and the data looks right, it is shipped to the field and work begins. Experience has shown me that there are many pitfalls after the data is completed. This article will deal with the most common issues I see and how to correct them.

Incorrect Information
It can be 85% plans or just a job that left the engineer too quickly to catch some issues. Either way, you have some problems that need addressing. The obvious issues have been fixed, but there are some things that need questions answered. You have 2 choices, wait for the answers or send an incomplete job into the field.

Temporary Files
In a perfect world, we would be able to get the job finished, leave it alone for two days and give it a final review before letting the field have it. These conditions only exist in our dreams. You are always rushed to get things done quickly, regardless of what you have to work with.

A file that represents rough grading or a portion of the job is not the worst thing in the world. It gives the field a chance to get started and buys you some valuable time. The most important thing to remember is everyone needs to know the condition of the file.

The surface pictured here has a big hole in it. Plain enough to see you cannot do anything here. Another answer is to hatch the area as an avoidance zone. Either way, be sure the field knows they are not dealing with a completely finished file of the entire job.

The best surface may still need some explaining. We use the vacation method. "You can be on vacation; I can look at the job in the field and not need to call anyone with questions" That means I really can go on vacation and will not return to angry co-workers who did not understand my data.

We find the best way to address the critical issues in a model is to put notes on the screen so the field can see them when they load the job. Not in an email. Not over the phone or directly after the safety briefing. On the screen. No need to write a novel, I hate to type. I'm sure that delights our clients, the screen notes are clear and to the point. This data collector screen shot is an example.

This kind of information is not only critical, but is difficult to remember and now easy to find. Sure the layer can be turned off, but you did your part to inform the user what to expect.

Data Revisions
Every project has a life cycle. Changes are a part of this and need to be handled efficiently. The reasons you are sending a new file to the field are countless. The important thing to keep in mind is that everyone needs to be sure what you did and that they are current. Our experience shows over 90% of the data issues we see are due to the field having outdated surface and/or line work files.

We have all been there, back in the analog days we were working on a project and were told what we were doing was wrong. We failed to receive the updated plans or changes. Electronically this is more difficult to spot; I always used to be on the lookout for fresh paper with no coffee stains. It always meant something new just happened.

In our electronic world the easiest way to eliminate problems is to use dates. Make sure all files you send and receive have the date on them. Nothing more involved is required. When a question comes in from the field, verify the correct files are in use. This will greatly reduce the problems with revisions.

Incorrect Information
Sometimes the information on the plans will be incorrect. Things move fast and sometimes changes are being made to sheet 3 of the plans while the first two are plotting. The approach to handling the situation will make the difference in your relationship with the engineer.

The first thing to remember is that both of you want one thing; the job to get done quickly and correctly. With that in mind, here are a couple points.

Obvious Issues
Reversed numbers, a curb 3 feet too high. We have seen these obvious errors and experienced data builders don't make an issue. If it's obvious, fix it and note it. Include it in an email to the engineer as a courtesy.

Items needing clarification
Never ask a question you don't know the answer to. Keep that in mind and you will be a partner to the engineer not a thorn in their side. Use your experience to look at the intent of the design and propose a fix. After all this is your project and you have a vested interest in its successful completion.

Marco Cecala is the owner of Take-off Professionals in Arizona and is a nationally-known expert and teacher of CAD, automated surveying and machine guidance

A 532Kb PDF of this article as it appeared in the magazine—complete with images—is available by clicking HERE

 

[ Back ]