We do not use Job Traveller anymore, just once a while for a quick
Job.
We creates small program (connect through ODBC) to print the Tag
(letter size), we call WIP tag. This tag will be printed when
Operator report labor qty. The tag will show the qty and the next
workcenter. This WIPtag combines with our Dispatch Report.
We want to use the tag in the Data Collection but It does not have
the next WorkCeter information.
Job.
We creates small program (connect through ODBC) to print the Tag
(letter size), we call WIP tag. This tag will be printed when
Operator report labor qty. The tag will show the qty and the next
workcenter. This WIPtag combines with our Dispatch Report.
We want to use the tag in the Data Collection but It does not have
the next WorkCeter information.
--- In vantage@yahoogroups.com, "Jasper Recto" <jrecto@l...> wrote:
> Just a question on how other companies do this.
>
> Lets say you have job traveler for 100 parts and it's at the first
operation. After the first 25 parts are completed, they transfer
those parts to the next operation. What do you do with the
traveler? Do you send it to the next operation? Do you leave it
with the 1st? What happens if the job splits to several operations?
What do other companies do?
>
> Thanks,
> Jasper
>
>
>
>
> [Non-text portions of this message have been removed]