Database Management

For an operation to be successful many items need to be tracked in some type of database or software system. These systems are often used by manufacturing, engineering, and even management to track an event or project that all three groups (and more) have a stake in.  If one person is in charge of input and output of the database (including management report outs) then if is a straightforward process as long as you can depend on that person.

Database management requires keeping status current
(Courtesy: 8u.fotomiser.com)

The problem comes when you have many people tasked to keep status on a project.  I have been personally involved in several of these scenarios and it is always a struggle to keep the database updated on a regular level.  One such program required the engineers to track data set releases and provide revised  estimated completion dates (ECDs)  if scheduled events were going to be late.  As the focal for the database, I would often have to track down particular engineers and extract a new ECD and input it into the database for them.  It was a lot of extra work which was unnecessary if the engineers were more diligent.

There are several things that could have been done better to help the process go better:

• Have management emphasis (and enforce) the importance of keeping databases current with the latest information.  Employees will focus on providing updated information if management is keeping emphasis on timely updates.  Management must not just send e-mails out requesting updates; they need to personally talk to those who are tardy on their inputs.
• If several groups use the database, assign one person in that group to be responsible for ensuring updates are happening.  It is pointless for one single person to be responsible for inputs of hundreds of users.  Break the task up and get help.
• Schedule daily stand up meetings to allow those who are tardy to explain to upper management why they haven't kept up.  I guarantee that this will ensure the database is current.

(Courtesy: www.gettyimages.co.uk)