Best way to store products on Univ GSM-1?

Hook it up to a server and only allow read access to the operators for the files. Then if changes have to be made it will take the appropriate person to overwrite the file and save it to the server drive.

Russ

reply »

"Wondering if there's an easy solution to save a product along with component database to disk, and load the product directly from there?"

The program that you have on your GSM should be the last known good program right? So why would you want to save it on a disk (unless it is for your monthly back up) just to reload it again? if you load programs that way, you will then have two programs to update if a change is needed. is harder to control.

I an authorized person is making changes to your programs or component databases, then just password protect the editing. That way only authorized personnel will be allowed to make changes to it.

In our case, every program that is created has a program name, e.g. 10000, then followed by the latest ECN that applies to that program 10000 (12345) with the ECN in parenthesis. That is our GSM program number.

Once the operator is ready to run, he/she will load a program directly from the machine and if the ECN on the program does not match the ECN on the BOM ( have QC verify his program) then that means that the program needs to be updated, then the person authorized to make changes is notified.

Again, we only backup programs and databases for emergencies (computer has failed beyond repair)

Make the changes on the machine and password protect the editing on programs and databases.

.

reply »

I agree that using floppy's would be too much hassle, especially with updates and such. Turn on your security system on the GSM and create System and Operator logins. Create a password for System and nothing for Operator. Then in order to make changes, you have to log in. They can still view. Just be sure to log out whenever you are done. You're monthly backups should be sufficient to restore products. You can choose which products you would like to backup and restore also.

reply »

Thanks for all the responses! I definitely agree, I don't like the idea of using floppies, either - and our HD is WELL, and regularly, backed up. While I both program and operate the machine, mgmt is insistent on this method.

I ended up just copying both the product data & component db to disk, renaming the component db to equal the product, and changing the comp. db in the product mgr. Slow, tedious, and overkill - yes, but they said jump, and that's how high I'm going. :)

Thx again.

reply »