Operations Master Setup

Yahoo Archive
1
My concern is with ensuring that the process requirements remain
intact. If they are identified by the operation code, it is easier to
see what operations are required and in what order for each process.
I tried creating templates for each process, but can't pull in
details from multiple templates or jobs. No matter which way it is
accomplished, our jobs will have 50 to 150 operations.
My question is what are the drawbacks to having 300 operations in the
system compared to 50 to 75 operations?
The consultant says you must enter setup and production times each
time you use it. Doesn't the data from the operation standards get
entered as the default? She also suggests setting up templates that
contain all of the processes, pulling it across then deleting what
you don't want.
There is also the issue of translating the existing setup (9500) &
WIP operations (345,000).


--- In vantage@yahoogroups.com, "c.chest" <c.chest@...> wrote:
>
> I side with the consultant who says it is too many operations. If
> the SBTBake operations are basically the same, you can add it to
your
> router (MOM) as many times as you want to, each time you do, it
will
> give you an operation number...10, 20, 30, etc. If there is
> something different used in the operation, you can maintain that at
> the Resource group, resource level. That's the way we do ours. We
> might have 20 different machining operations, but we just assign
one
> operation, machining and then designate which machine by the
resource
> group or resource,which then depicts what the operation is, like
> Vertical Mill would tell us it is milling. All of the costs and
> reporting information is done by the resource group/resource. I
> don't think what you're doing is wrong, just too much maintainence
in
> my opinion.
2
We have been working for 10 months to get Vantage 8 implemented, and
have had 2 consultants with differing opinions assisting us.
I would appreciate any insight into the following.
We are an electronics manufacturer and build approximately 1000
different assemblies to various customer requirements. These
assemblies are very labor intensive, up to 200 operations on a job.
Our current system is set up by processes; each process containing
several operations, and the same operation may be used more than once
in a process.
When inputting operations into Vantage, I used a process code with
the operation so that engineering can easily recognize what steps are
required for each process. I entered a total of 290 operations.
For instance, there are several bake operations (SBTBake1, SBTBake2,
SMTBake1, etc).
One consultant is telling me that this is too many operations, that I
should have only 1 operation called "Bake". The other says it is not
an issue.
Does anyone have an opinion? How will Vantage handle labor studies?
Will I be able to tell what labor belongs to which Bake process?
I appreciate any insight offered.
3
Just my 2 cents but I would tend to agree with keeping it simple and using the most generic operations possible. Then again if the standard production rates for them are wildly different you may need more. One alternative might be in the clocking out for the operator to enter a note...which if structured consistently would allow extracting which exact operation it was. Maybe even have bar coded cheat sheets for the exact operations and scan those as the entry method. Same might be true from the job setup side as far as notes or user fields. The real issue will be does the need to identify exactly which bake type flow to cost capturing or is it just to later analyze the types being used. I don't think there is any system limit on the number of operations but using the KISS principle is still a good practice.
-Todd C.


________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of gswwatch
Sent: Monday, December 08, 2008 1:49 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Operations Master Setup


We have been working for 10 months to get Vantage 8 implemented, and
have had 2 consultants with differing opinions assisting us.
I would appreciate any insight into the following.
We are an electronics manufacturer and build approximately 1000
different assemblies to various customer requirements. These
assemblies are very labor intensive, up to 200 operations on a job.
Our current system is set up by processes; each process containing
several operations, and the same operation may be used more than once
in a process.
When inputting operations into Vantage, I used a process code with
the operation so that engineering can easily recognize what steps are
required for each process. I entered a total of 290 operations.
For instance, there are several bake operations (SBTBake1, SBTBake2,
SMTBake1, etc).
One consultant is telling me that this is too many operations, that I
should have only 1 operation called "Bake". The other says it is not
an issue.
Does anyone have an opinion? How will Vantage handle labor studies?
Will I be able to tell what labor belongs to which Bake process?
I appreciate any insight offered.






[Non-text portions of this message have been removed]
4
I have seen it done both ways. The decision should be driven by what
you want to do with the data once its captured. If you want to do time
studies of each bake operation then its easier to list them separately.
Here are a couple of drawbacks to doing it this way:

1) There is a tendency for operators to charge time to the wrong bake
operation.

2) Printed travelers can get very large.

3) After you go thru all the trouble the data metrics do not get used in
a constructive way.



Mark D



________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of gswwatch
Sent: Monday, December 08, 2008 2:49 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Operations Master Setup



We have been working for 10 months to get Vantage 8 implemented, and
have had 2 consultants with differing opinions assisting us.
I would appreciate any insight into the following.
We are an electronics manufacturer and build approximately 1000
different assemblies to various customer requirements. These
assemblies are very labor intensive, up to 200 operations on a job.
Our current system is set up by processes; each process containing
several operations, and the same operation may be used more than once
in a process.
When inputting operations into Vantage, I used a process code with
the operation so that engineering can easily recognize what steps are
required for each process. I entered a total of 290 operations.
For instance, there are several bake operations (SBTBake1, SBTBake2,
SMTBake1, etc).
One consultant is telling me that this is too many operations, that I
should have only 1 operation called "Bake". The other says it is not
an issue.
Does anyone have an opinion? How will Vantage handle labor studies?
Will I be able to tell what labor belongs to which Bake process?
I appreciate any insight offered.







[Non-text portions of this message have been removed]
5
I side with the consultant who says it is too many operations. If
the SBTBake operations are basically the same, you can add it to your
router (MOM) as many times as you want to, each time you do, it will
give you an operation number...10, 20, 30, etc. If there is
something different used in the operation, you can maintain that at
the Resource group, resource level. That's the way we do ours. We
might have 20 different machining operations, but we just assign one
operation, machining and then designate which machine by the resource
group or resource,which then depicts what the operation is, like
Vertical Mill would tell us it is milling. All of the costs and
reporting information is done by the resource group/resource. I
don't think what you're doing is wrong, just too much maintainence in
my opinion.

--- In vantage@yahoogroups.com, "gswwatch" <gswwatch@...> wrote:
>
> We have been working for 10 months to get Vantage 8 implemented,
and
> have had 2 consultants with differing opinions assisting us.
> I would appreciate any insight into the following.
> We are an electronics manufacturer and build approximately 1000
> different assemblies to various customer requirements. These
> assemblies are very labor intensive, up to 200 operations on a job.
> Our current system is set up by processes; each process containing
> several operations, and the same operation may be used more than
once
> in a process.
> When inputting operations into Vantage, I used a process code with
> the operation so that engineering can easily recognize what steps
are
> required for each process. I entered a total of 290 operations.
> For instance, there are several bake operations (SBTBake1,
SBTBake2,
> SMTBake1, etc).
> One consultant is telling me that this is too many operations, that
I
> should have only 1 operation called "Bake". The other says it is
not
> an issue.
> Does anyone have an opinion? How will Vantage handle labor
studies?
> Will I be able to tell what labor belongs to which Bake process?
> I appreciate any insight offered.
>