Need help on design of db

S

Steve

I am fairly new to designing db's and I did one db for my company for fun and they liked it so much they want another one. Problem is I am having trouble getting the idea down on paper so I can start. Here is the situation:

This department issues their product to our other plants. The product are not marked by any type of serial number so they are just bulk issued. They may issue 100 one day and then only return 50 the next day. (very sporadic) Some items may never return, maybe 1% of total usage. So....
First,
they have 21 diffferent products but they are tricky because they are resuable items so they can be issued as either "brand new/refurbished" or "used". I also have to note whether some of either of those use any "new item".
Second,
after the other plants use them, they must return them in the system. The returns are placed into 5 categories - "Good for reuse", "Need to be refurbished for reason 1", "Need to be refurbished for reason 2", "Lost due to Reason 3", Lost due to Reason 4"

I have played around with a couple of ideas but none of them really feel right to me. The employees are used to typing all the issue information into an excel spreadsheet that has the products down the side and the "Brand new" and "used" in the columns 2 and 3. So I was trying to keep it looking the same for them so it is not too confusing.

After I gather the data, I need to give them a daily qty at the plants as well as end-of-month information regarding usage and time spent working on each product.

Any help would be greatly appreciated
your truly,
"Staring at the computer"
Steve
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top