At a former company, we decided to do this.  We found out that if you used
a complete verision of Adobe Acrobat Writer, you could create a word
document and convert it into a .pdf format that was an order of magnitude
smaller than the same file that was scanned in.  Consequently, we also had
the test houses provide their reports in electronic format and converted
them to .pdf file.

Daniel Mitchell
Product Safety Engineer
Condor DC Power Supplies, Inc.





"Grasso Charles (Chaz)" <[email protected]> on 03/03/2000
10:36:03 AM

To:   "'Bruce Touzel'" <[email protected]>, Scott Douglas
      <[email protected]>
cc:   [email protected] (bcc: Dan Mitchell/CondorDC)

Subject:  RE: Technical Documentation





Excellent thought - and one that we are moving to.
There are a couple logistical issues that need resolving..
1) one problem there is that
we would have to employ 2 persons fulltime to
perform all the necessary library functions
2) the transmittal of the data (the files can attain several
megabytes) is non trivial. Webdownlaads can take a L..O..N..G
time and email systems typically puke on the file size.

-----Original Message-----
From: Bruce Touzel [mailto:[email protected]]
Sent: Friday, March 03, 2000 10:37 AM
To: Scott Douglas
Cc: [email protected]
Subject: Re: Technical Documentation



why don't you just scan-in your documents and post them on the internal
company
server so that anyone can get it if needed ?

thx
bruce

Scott Douglas wrote:

> I guess I want to toss my 2 cents in here. I am probably going to be
found
> out in left field but here's what I do with all this stuff. I keep a 3
ring
> binder where I store copies of all of the safety agency certifications
and
> notices of compliance from the EMC test house. I also keep a copy of the
> Declaration of Conformity in the book. I keep one copy of this binder in
our
> UK office, one copy here in my office and one copy here in Document
Control
> (here being our US factory). In addition to the binders, I keep one file
> cabinet in Document Control where I store all safety and EMC test
records.
I
> am now adding copies of component proofs to this file cabinet. I do not
> store schematics, fabrication or assembly drawings. Neither do I store
user
> manuals or reference manuals. Tech Pubs and Drafting store all these
> documents and drawings.
>
> Should the need arise, anyone can ask our UK office for a document and
that
> request will be passed on to me. If that request ever comes in, I will go
to
> Document Control and arrange  to collect the necessary paperwork. I am
> certainly not going to create a file of duplicate documents that I have
to
> update on an every day basis. So it would seem that my TCF or whatever
else
> you want to call it is actually scattered all over our factory, each
> function keeping their own records. About the only thing I did to these
> other document storage processes was to add the 10 storage requirement to
> their ISO 9001 procedures. One other thing I did was to insert myself in
the
> ECO process such that I sign off on every change order to a tested and
> released product. That way, I won't miss anything.
>
> So far, it seems to be working with minimal fuss. The few requests I have
> had were from non-European countries for test records, specifically from
> South Africa, Australia and Russia. I am sure somebody will tell me I am
way
> out there and really non-compliant. But since I test and certify to
product
> specific (ITE) standards, I do not need to keep "TCF's or whatever else"
at
> a test house / notified / competent body. Therefore, I will not keep such
a
> file here either. I will deliver whatever documents to whomever requests,
it
> may take a few days, but I will deliver. If that is not in keeping with
the
> spirit and intent, then somebody better lock me up.
>
> Scott
> [email protected]
> ECRM Incorporated
> Tewksbury, MA  USA
>
> -------------------------------------------
> This message is from the IEEE EMC Society Product Safety
> Technical Committee emc-pstc discussion list.
>
> To cancel your subscription, send mail to:
>      [email protected]
> with the single line:
>      unsubscribe emc-pstc
>
> For help, send mail to the list administrators:
>      Jim Bacher:              [email protected]
>      Michael Garretson:        [email protected]
>
> For policy questions, send mail to:
>      Richard Nute:           [email protected]


-------------------------------------------
This message is from the IEEE EMC Society Product Safety
Technical Committee emc-pstc discussion list.

To cancel your subscription, send mail to:
     [email protected]
with the single line:
     unsubscribe emc-pstc

For help, send mail to the list administrators:
     Jim Bacher:              [email protected]
     Michael Garretson:        [email protected]

For policy questions, send mail to:
     Richard Nute:           [email protected]


-------------------------------------------
This message is from the IEEE EMC Society Product Safety
Technical Committee emc-pstc discussion list.

To cancel your subscription, send mail to:
     [email protected]
with the single line:
     unsubscribe emc-pstc

For help, send mail to the list administrators:
     Jim Bacher:              [email protected]
     Michael Garretson:        [email protected]

For policy questions, send mail to:
     Richard Nute:           [email protected]







-------------------------------------------
This message is from the IEEE EMC Society Product Safety
Technical Committee emc-pstc discussion list.

To cancel your subscription, send mail to:
     [email protected]
with the single line:
     unsubscribe emc-pstc

For help, send mail to the list administrators:
     Jim Bacher:              [email protected]
     Michael Garretson:        [email protected]

For policy questions, send mail to:
     Richard Nute:           [email protected]

Reply via email to