Manufacturing Processes Database?

  • Thread starter Thread starter Dustin K. Osburn
  • Start date Start date
D

Dustin K. Osburn

Good morning,

I've been tasked with creating a database to store various
manufacturing processes for different boats. I'm coming to the
realization that a database may not be the best solution for what my
company is wanting, but I was hoping for some input from those more
knowledgeable than myself. I myself am relatively new to Access, and
this is a little more complicated than a DVD collection.

Essentially what I need to do is create instruction manuals, with
photographs, on how to build our boats. We currently have
approximately 12 models, where the only similarities are the general
stages of production. I've been unable to find common points to
really base tables / fields on. The current thinking is that we can
document all of these processes and store them in a database where the
information can be pulled up by supervisors for their new employees,
dealers for warranty repairs in the field, etc.

Bear in mind that this idea was put forward with very little
technical consideration, hence my post. I'm coming to be of the mind
that we would be better served putting together an InDesign (or
equivalent program) template, inserting the text / photos, save as PDF
and then catalog the lot of them via a webpage / Excel.

Any assistance one way or the other would be greatly appreciated.

Cheers,
Dustin
 
Tables:
Boats
ConstructionSteps

for the record; databases allow for multiple people to read / edit a
document.. you might need to write a little bit of code; but I mean..
having your information in a database is _ALWAYS_ more handy than
storing it in a PDF
 
Dustin K. Osburn said:
Essentially what I need to do is create instruction manuals, with
photographs, on how to build our boats. We currently have
approximately 12 models, where the only similarities are the general
stages of production. I've been unable to find common points to
really base tables / fields on. The current thinking is that we can
document all of these processes and store them in a database where the
information can be pulled up by supervisors for their new employees,
dealers for warranty repairs in the field, etc.
Click to expand...

I would agree with you that given the non commonality of data along
with the text and photo's you'd be best off producing a manual and not
a database.

Now one thing to consider might be an internal Wikipedia. That is a
Wikipedia run on your own servers accessible only in your internal
network. Once you have the manuals in place let every one of your
employees update the manual. With those little details that make the
difference been a decent product and a good product.

For example I heard that one olive processing plant found that their
product became sub standard after one guy retired. After six months
they contacted the guy and discovered that he had been changing 50
cent rubber washers after every week rather than the manufacturers
recommended six months.

So someone has a slightly better technique for doing something or a
safety warning of some sort. "On a cold day ensure that you keep the
shop door close for an hour after doing this ..."

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
I would agree with you that given the non commonality of data along
with the text and photo's you'd be best off producing a manual and not
a database.

Now one thing to consider might be an internal Wikipedia. That is a
Wikipedia run on your own servers accessible only in your internal
network. Once you have the manuals in place let every one of your
employees update the manual. With those little details that make the
difference been a decent product and a good product.

For example I heard that one olive processing plant found that their
product became sub standard after one guy retired. After six months
they contacted the guy and discovered that he had been changing 50
cent rubber washers after every week rather than the manufacturers
recommended six months.

So someone has a slightly better technique for doing something or a
safety warning of some sort. "On a cold day ensure that you keep the
shop door close for an hour after doing this ..."

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm
Click to expand...

An internal Wiki is an interesting idea that I hadn't thought of, I
don't think that letting everyone update it directly would work as not
everyone is "company minded", but a change request form similar to the
ones we use for engineering changes would work just as well. Thanks
for that idea Tony.

- Dustin
 
Hi Dustin,

Like Tony I feel that a relational database isn't the best starting
point.

I'm not sure InDesign is the best for this sort of thing either. If
information management and multi-format output (print, web, PDF...) are
more important than fancy layout, I'd suggest you look hard at Adobe
FrameMaker.
 
Hi Dustin,

Like Tony I feel that a relational database isn't the best starting
point.

I'm not sure InDesign is the best for this sort of thing either. If
information management and multi-format output (print, web, PDF...) are
more important than fancy layout, I'd suggest you look hard at Adobe
FrameMaker.
Click to expand...

John,

FrameMaker looks ideal for what I'm trying to do, I'm downloading the
Trial now to check it out. Thanks for your input!

- Dustin
 
Dustin K. Osburn said:
An internal Wiki is an interesting idea that I hadn't thought of, I
don't think that letting everyone update it directly would work as not
everyone is "company minded", but a change request form similar to the
ones we use for engineering changes would work just as well. Thanks
for that idea Tony.
Click to expand...

You're welcome. However forms <shudder>. Ok, give certain
employees, including foremen, the ability to directly make changes.
Keeping in mind that foremen aren't paid for their typing ability or
ability to write coherent sentences. <smile> You may want to have
some clerical help where the ham fisted boys can wonder over and tell
the long suffering clerk what to type and where.

Also wikis can track who has made what changes and when.

I'm a great fan of some sort of spontaneity.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Access Data Projects can 'auto-magically keep track of who made a
change and when'

WIKIPEDIA?

jesus ****ing christ, kids

of COURSE you should use a database

I mean; what happens when you want to reuse some logic from one report
to another?

you have two copies of it in a word doc?

ROFL

what a crappy strategy; databases aren't that complex dude... maybe if
you knew how to work them you wouldn't be stuck at Jiffy Lube
 
Back
Top