Start with the Beginning: Database Design III
Guess what!
Information you lust for is laying around in other corners of your organization.
Imagine a resume database that updates each week without you pestering a single person for an update.
Where is the information?
Heck, accounts receivable knows who bills out to which client and project. Payroll may also know, but start sniffing in accounts payable. What is the route used to create invoices? Is there a place (or several) where a report could be generated that would transfer data to your resume database?
You going to finish that sandwich?
Be sure to ask about all the fields of data they track. There might be some goodies like technical area or client type you could tap into.
Imagine a resume that ends with a stream of notes of additional projects on which this person has worked, reminding them of EVERYTHING when they are ready to write up some paragraphs for the next proposal they participate in. Imagine being able to search resumes to match people to the location or client.
Imagine a project summary database that is error free because the skeleton of data automatically comes over from your accounting with the client’s name, project name and number, location, and list of personnel working on the project? You’d just be left scanning the list of personnel to find someone to write out the details when a project seems needed for a proposal. Poor baby.
You are almost ready to start talking to vendors, but not quite yet!
Reader (RSS)
Email