Engineering Procedures

Yahoo Archive
1
If you have employee turnover, this will/may not work. If you have major product lines/product groups that you sell, then you could categorize as such.

Joe Rojas <jrojas@...> wrote: We decided to create and ECO group for each engineer using the first
letter of their first name followed by there last name.

I did understand the "Tabulated Drawings/Parts" question.

The question of rev changes is related to your requirements. Are you FDA
regulated?

We need to create a new REV when every there is a change that effects
Form, Fit, or Function to the end product.

If we wanted to update the resource used for an operation or change
operation standards we would not create a new REV.

Thanks,

Joe Rojas

IT Manager

TNCO, Inc.

781-447-6661 x7506

jrojas@...

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Knowlton,Keith
Sent: Wednesday, November 01, 2006 9:04 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Engineering Procedures

Below are some concerns the Engineering Department has addressed. If
anyone has some feedback please respond. We have not fully implemented
Vantage 8.0 and would like to get these issues straighten out before
fully implementing. Most of these concerns have solutions, but we are
looking for any tips that would help us come up with a better system.

ECO Group ID needs to be defined. Should we use names, numbers, or other
ID's?

Tabulated Drawings/Parts. How do we update drawing rev's on each
individual tabulated part in Vantage?

Do we make new revisions on parts & MOMs every time there is a change or
do we keep changing the initial revision?

TIA,

Keith Knowlton
<mailto:keith.knowlton@...
<mailto:keith.knowlton%40ameridrives.com> ?subject=Ameridrives>

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

[Non-text portions of this message have been removed]
2
Below are some concerns the Engineering Department has addressed. If
anyone has some feedback please respond. We have not fully implemented
Vantage 8.0 and would like to get these issues straighten out before
fully implementing. Most of these concerns have solutions, but we are
looking for any tips that would help us come up with a better system.

ECO Group ID needs to be defined. Should we use names, numbers, or other
ID's?

Tabulated Drawings/Parts. How do we update drawing rev's on each
individual tabulated part in Vantage?

Do we make new revisions on parts & MOMs every time there is a change or
do we keep changing the initial revision?

TIA,

Keith Knowlton
<mailto:keith.knowlton@...?subject=Ameridrives>




[Non-text portions of this message have been removed]
3
We decided to create and ECO group for each engineer using the first
letter of their first name followed by there last name.



I did understand the "Tabulated Drawings/Parts" question.



The question of rev changes is related to your requirements. Are you FDA
regulated?

We need to create a new REV when every there is a change that effects
Form, Fit, or Function to the end product.

If we wanted to update the resource used for an operation or change
operation standards we would not create a new REV.



Thanks,

Joe Rojas

IT Manager

TNCO, Inc.

781-447-6661 x7506

jrojas@...



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Knowlton,Keith
Sent: Wednesday, November 01, 2006 9:04 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Engineering Procedures



Below are some concerns the Engineering Department has addressed. If
anyone has some feedback please respond. We have not fully implemented
Vantage 8.0 and would like to get these issues straighten out before
fully implementing. Most of these concerns have solutions, but we are
looking for any tips that would help us come up with a better system.

ECO Group ID needs to be defined. Should we use names, numbers, or other
ID's?

Tabulated Drawings/Parts. How do we update drawing rev's on each
individual tabulated part in Vantage?

Do we make new revisions on parts & MOMs every time there is a change or
do we keep changing the initial revision?

TIA,

Keith Knowlton
<mailto:keith.knowlton@...
<mailto:keith.knowlton%40ameridrives.com> ?subject=Ameridrives>



[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
4
On Nov 1 2006, Knowlton,Keith wrote:

>ECO Group ID needs to be defined. Should we use names, numbers, or other
>ID's?

Our ECO Group ID's match our ECO numbers (so we create a new ID for every
ECO). (So our ECO group ID matches the ECO number two fields below
it--redundant I know, but it works for us). Takes 2 seconds to create a new
ID so it's not a big deal regardless of what you choose.


>Tabulated Drawings/Parts. How do we update drawing rev's on each
>individual tabulated part in Vantage?

Not exactly sure what you are asking here. I came up with two
interpretations of your question. If I'm compleltely off base, let me know
where I went wrong and I'll take another stab at it.

Interpretation 1: Do you have a revision for the drawing and a revision for
each tabulated part on that drawings so that you need to control two
revisions? If that is the case, you can create a 2nd revision field to
track the drawing revision. Or, using the existing revision field, do
something like A-A (drawing rev-part rev), then if you rev the part you'd
go to A-B, and if you then rev'd the drawing you'd go to B-C, etc.

Interpretation 2: The other way I read your question is---I have a ton of
tabulated parts on this drawing and I need to change the revision on them
all--can you do a revision update for the entire family of parts? The
answer is no (at least not without some programming). You have to add
revisions one part at a time...


>Do we make new revisions on parts & MOMs every time there is a change or
>do we keep changing the initial revision?

This depends on how much traceability you need.

* Not much needed: If you just keep making changes on the initial revision,
your only history will be in the change log, if you have that turned on and
are tracking whatever fields you need.

* Some traceability needed: If you make a new revision for major changes
(fit form function), you will have some useful history. One example of
where this is helpful is if you change a material. If you make the switch
on an existing revision level rather than changing the level, that old part
will no longer be linked to anything. Sometimes we end up with some
residual inventory and it takes some extra work to figure out what we even
had it for because the "where used" won't work. If you had changed the
revision, the "where used" on the old material will show that it had been
used on an obsolete revision of the part.

* Major traceability: Revisions and versions. You would do a revision
change for major stuff (fit, form, function changes), and a version change
for non-engineering type stuff (typo's, rate changes, etc.) So your
revision level would be something like A.1 (revision.version).


We've been on 8.0 for quite a while and have spent a lot of time looking at
these very things (we are changing our part number and revision level
systems within the next few months and spent a lot of time researching and
debating our options), so if you have any other questions, let me know.

--
Amy O'Malley
Manufacturing Process Engineer
Synovis Interventional Solutions
Lino Lakes, Minnesota
omaLL004@...
5
I just got out of meeting discussing these issues. What you have
outlined is very close to what we have decided on. Your interpretation 2
of tabulated drawings was right. We may be doing some programming to
solve that problem.

We did decide on keeping all revisions the same, regardless of how many
changes we make. As you said we're going to use the audit log to trace
prior changes. We also have ECO's that track the changes, I think that
will be good enough. Thank you and I will keep you mind when I run
across problems.

Thanks,

Keith Knowlton
<mailto:keith.knowlton@...?subject=Ameridrives>



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Amy OMalley
Sent: Wednesday, November 01, 2006 3:21 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Engineering Procedures



On Nov 1 2006, Knowlton,Keith wrote:

>ECO Group ID needs to be defined. Should we use names, numbers, or
other
>ID's?

Our ECO Group ID's match our ECO numbers (so we create a new ID for
every
ECO). (So our ECO group ID matches the ECO number two fields below
it--redundant I know, but it works for us). Takes 2 seconds to create a
new
ID so it's not a big deal regardless of what you choose.

>Tabulated Drawings/Parts. How do we update drawing rev's on each
>individual tabulated part in Vantage?

Not exactly sure what you are asking here. I came up with two
interpretations of your question. If I'm compleltely off base, let me
know
where I went wrong and I'll take another stab at it.

Interpretation 1: Do you have a revision for the drawing and a revision
for
each tabulated part on that drawings so that you need to control two
revisions? If that is the case, you can create a 2nd revision field to
track the drawing revision. Or, using the existing revision field, do
something like A-A (drawing rev-part rev), then if you rev the part
you'd
go to A-B, and if you then rev'd the drawing you'd go to B-C, etc.

Interpretation 2: The other way I read your question is---I have a ton
of
tabulated parts on this drawing and I need to change the revision on
them
all--can you do a revision update for the entire family of parts? The
answer is no (at least not without some programming). You have to add
revisions one part at a time...

>Do we make new revisions on parts & MOMs every time there is a change
or
>do we keep changing the initial revision?

This depends on how much traceability you need.

* Not much needed: If you just keep making changes on the initial
revision,
your only history will be in the change log, if you have that turned on
and
are tracking whatever fields you need.

* Some traceability needed: If you make a new revision for major changes

(fit form function), you will have some useful history. One example of
where this is helpful is if you change a material. If you make the
switch
on an existing revision level rather than changing the level, that old
part
will no longer be linked to anything. Sometimes we end up with some
residual inventory and it takes some extra work to figure out what we
even
had it for because the "where used" won't work. If you had changed the
revision, the "where used" on the old material will show that it had
been
used on an obsolete revision of the part.

* Major traceability: Revisions and versions. You would do a revision
change for major stuff (fit, form, function changes), and a version
change
for non-engineering type stuff (typo's, rate changes, etc.) So your
revision level would be something like A.1 (revision.version).

We've been on 8.0 for quite a while and have spent a lot of time looking
at
these very things (we are changing our part number and revision level
systems within the next few months and spent a lot of time researching
and
debating our options), so if you have any other questions, let me know.

--
Amy O'Malley
Manufacturing Process Engineer
Synovis Interventional Solutions
Lino Lakes, Minnesota
omaLL004@... <mailto:omaLL004%40umn.edu>






[Non-text portions of this message have been removed]