Hi Paul,
We used to do this the way Tim describes when we were on 6.1 (using the
operation documents for the operation). It was really difficult to manage.
The pain starts in quoting, when now the quoters can't just choose "Braze",
they have to know exactly which brazing procedure to use... and the pain
continues from there...you could only select one document per operation, so
in areas the you could have several combinations of processes (like
cleaning and packing) you had to write combination documents for every
variation you used. It was agony from quoting to engineering to production.
We solved all of this madness by switching to 8.0 :-)
We eliminated all of our "Procedure specific" operations and went to a
general operation (i.e. clean, pack, weld), like normal companies, which
made our quoters estatic.
We then added 5 fields to each operation with pull-down menus listing all
of our procedures. So in engineering workbench, the engineer can select up
to 2 set-up procedures and 3 operational procedures per operation, which
made our engineers estatic.
These selections are printed on our job travelers under each operation so
the operators and supervisors know which procedures to train on and
reference while performing that operation, which made the supervisors and
operators really happy.
Because of this, our procedures can now be fairly modular--We used to have
a "clean and pack" procedure and a "clean" procedure and a "pack"
procedure. We can now eliminate the "Clean and pack" and just call out both
procedures we need (once again, fewer documents to write = happy
engineers).
We also have reports we can run when we need to do revision changes that
list all the parts that use that procedure.
As you may have sensed, as an engineer I was pretty excited about this
change...and this is just the beginning of the cool, useful stuff we are
doing in 8.0...
Amy O'Malley
Manufacturing Process Engineer
Synovis Interventional Solutions
8.00.806D
We used to do this the way Tim describes when we were on 6.1 (using the
operation documents for the operation). It was really difficult to manage.
The pain starts in quoting, when now the quoters can't just choose "Braze",
they have to know exactly which brazing procedure to use... and the pain
continues from there...you could only select one document per operation, so
in areas the you could have several combinations of processes (like
cleaning and packing) you had to write combination documents for every
variation you used. It was agony from quoting to engineering to production.
We solved all of this madness by switching to 8.0 :-)
We eliminated all of our "Procedure specific" operations and went to a
general operation (i.e. clean, pack, weld), like normal companies, which
made our quoters estatic.
We then added 5 fields to each operation with pull-down menus listing all
of our procedures. So in engineering workbench, the engineer can select up
to 2 set-up procedures and 3 operational procedures per operation, which
made our engineers estatic.
These selections are printed on our job travelers under each operation so
the operators and supervisors know which procedures to train on and
reference while performing that operation, which made the supervisors and
operators really happy.
Because of this, our procedures can now be fairly modular--We used to have
a "clean and pack" procedure and a "clean" procedure and a "pack"
procedure. We can now eliminate the "Clean and pack" and just call out both
procedures we need (once again, fewer documents to write = happy
engineers).
We also have reports we can run when we need to do revision changes that
list all the parts that use that procedure.
As you may have sensed, as an engineer I was pretty excited about this
change...and this is just the beginning of the cool, useful stuff we are
doing in 8.0...
Amy O'Malley
Manufacturing Process Engineer
Synovis Interventional Solutions
8.00.806D
On May 24 2006, Tim Mendoza wrote:
>The main complication is that the operation codes are limited to small
>number of characters.
>
>My thought was to set them up like this:
>
>(OPCODE) (Description)
> BRA1 = Braze per 91547-P6231
>
> That way if you needed to change any routing using that process, you just
> extract ALL routings from the "partopr" table that have that operation
> code in them.
>-----Original Message-----
>From: Paul Pachniak [SMTP:paul.pachniak@...]
>Sent: Tuesday, May 23, 2006 2:32 PM
>To: Vantage Group List (E-mail)
>Subject: [Vantage] Operation Specification
>Anyone have any suggestions or comments as to how they are dealing with
>operation specs in Vantage?
>Paul E. Pachniak
>Accounting Manager
>Ace Precision Machining Corporation