Job Traveler Operations

Yahoo Archive
1
vantage@yahoogroups.com wrote:
> Mark,
>
> Thanks for the suggestion. I just tried this and it comes
> close to what we need. It is complicated by the fact that
> this is a traveler for a configured part. I'm going to take a
> look at the report that Todd has created and see if I can get
> any closer to a report by Operation.
>

No problem. Just an FYI, you can create sub-assemblies with the Product
Configurator as well.

Mark W>
2
Has anyone created a Job Traveler that associates the parts for each Operation with each Operation, and then prints each Operation on a separate page(s)?
We are moving into a new line where we would like to run parallel Operations within a Job and the current Job Traveler doesn't lend itself to this type of assembly.
The only solution we have so far is to print multiple copies of the Job Traveler.

Thanks,

Dave
8.03.407C P
3
Hi Dave,

> We are moving into a new line where we would like to run
> parallel Operations within a Job and the current Job Traveler
> doesn't lend itself to this type of assembly.
> The only solution we have so far is to print multiple copies
> of the Job Traveler.

It sounds like a good candidate for sub-assemblies. If you can work on four
items at once then make each a sub-assembly in the MOM. The traveler can
print a page for each sub-assembly (with its own MOM) and one master job for
final assembly.

Mark W.
4
I have one like that but it is CR 8.5 for Vantage 6.10. Each oper is on its own page with lots of other stuff like check-off grids and notes for the operation. I also added a sub-report that shows the operation on a list in relation to the preceding or following operations (current oper is highlighted) so operators can see where the parts go next. I also split all the shipment release info off onto a separate report for shipping so as to not clutter the manufacturing side. As a job packet proceeds through the shop each operation takes its page and sends the rest forward. When an operation is complete that card goes with the parts and eventually all the cards catch up at shipping. Operator notes written on the cards are then reviewed before the next job for that part.

If you're interested in it as a starting place for converting for 8.03.400 contact me off-list. You would likely have to start with the canned 8.x version and just use mine as an example for changes due to the source data differences between DBF and XML.
-Todd C.


________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of ofcwiz
Sent: Wednesday, July 15, 2009 9:39 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Job Traveler Operations




Has anyone created a Job Traveler that associates the parts for each Operation with each Operation, and then prints each Operation on a separate page(s)?
We are moving into a new line where we would like to run parallel Operations within a Job and the current Job Traveler doesn't lend itself to this type of assembly.
The only solution we have so far is to print multiple copies of the Job Traveler.

Thanks,

Dave
8.03.407C P





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

Thanks for the suggestion. I just tried this and it comes close to what we need. It is complicated by the fact that this is a traveler for a configured part. I'm going to take a look at the report that Todd has created and see if I can get any closer to a report by Operation.

Thanks,
Dave

--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
> Hi Dave,
>
> > We are moving into a new line where we would like to run
> > parallel Operations within a Job and the current Job Traveler
> > doesn't lend itself to this type of assembly.
> > The only solution we have so far is to print multiple copies
> > of the Job Traveler.
>
> It sounds like a good candidate for sub-assemblies. If you can work on four
> items at once then make each a sub-assembly in the MOM. The traveler can
> print a page for each sub-assembly (with its own MOM) and one master job for
> final assembly.
>
> Mark W.
>