Subject: Re: Routing Logic From: Bryce Martin Date: Wed, 7 Dec 2011 08:16:52 -0500 List-archive: List-help: List-id: BPCS ERP System List-post: List-subscribe: , List-unsubscribe: ,

Al,
I think the biggest challenge for him will be setting the negative move
time properly based on how long the operation before it takes to complete
a piece. Any negative move time greater than -1 will work for the second
operation but it won't be able to be less than -1 since that is the point
at which it will put the second operation's release date before the
release date of the shop order (most likely from his description).

Now that I think a bit more, I actually think its related to the release
date of the previous operation.... so you could essentially set the move
times of all operations to -1 to have them all start at the "same" time
(since BPCS doesn't do interday scheduling you can only get as fine as the
date, not the time). I think this is about as close as he will be able to
get. Trying to use fractional move/queue time here could be really tricky
if he's using Pieces per Hour for his basis since the amount of time it
takes to make the first piece and get it to the next workcenter could vary
depending on the item being acted upon...

Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777

"Al" <macwheel99@xxxxxxxxxx>
Sent by: bpcs-l-bounces@xxxxxxxxxxxx
12/06/2011 04:12 PM
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>

To
"'BPCS ERP System'" <bpcs-l@xxxxxxxxxxxx>
cc

Subject
Re: [BPCS-L] Routing Logic

In earlier versions of BPCS,

If you need 261 units, and not have BPCS schedule 270 to be made, then you
can define 261 within the item planning where with MRP you can schedule
based on discrete 270 needed, or in quantities like 261 which are relevant
to production realities. We do this for raw material ordering, where some
quantity is a price break.

You can put a negative number in the move time, to allow for overlap.

You can have additional description and-or notes, to describe what happens
between data collection operations
In our routings, we often have as the last step of non-reporting line,
where
in the factory this work is to be moved to, when it is finished. We also
have modified our shop paperwork to aid other flow ... what end customer
is
this for, identify parts list needed to do this step, information to help
quality inspectors

You can duplicate define a cluster of machines as being a fake machine
which
is really the five.
You can refrain from routing to specific machines, and instead route to
work
centers, where at run time, the factory uses whatever machines they

You have to be careful with reporting operations out of sequence,
depending
on how items are coded, because BPCS can sometimes compute what must have
been the missing operations. We do not want that to happen. We only want
it to record precisely what we reported, and we do sometimes have labor
tickets keyed in, in a sequence other than how the work was sometimes
done,
such as when we are tracking repairs.

When people report quantity made greater than quantity needed for an
operation, BPCS automatically says that operation is complete. This can
be
a nuisance when reporting for scrap.
When people make an error reporting some operation as complete, because
THEY
did their work, unaware of need for other people to do their share, BPCS
won't actually purge an order until all inventory transactions needed are
done. Sometimes we decide enough is enough. The order was for 10,000. We
made 9.990. It is not worth setup to get the extra 10, we can let that be
carried over to next production run. To get that to close out properly,
we
(1) downsize the quantity needed to make for the order (2) post a zero
time
labor ticket on first operation, then BPCS labor processing goes thru each
operation in sequence, updating that if we made at least the new quantity,
that operation is now closed (3) we check of any operation is still open.

-
Al Mac
-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Eriq Lorilla
Sent: Monday, December 05, 2011 3:01 AM
To: 'BPCS ERP System'
Subject: [BPCS-L] Routing Logic

Hi,

I am new in the manufacturing concept and we are trying to reconcile the
routing of our client.
Does anybody knows how to route 5 operations/machines simultaneously.

Example we have 261 units as orders and we will route it in 5
operations/machines. The problem is we can't route it simultaneously in
ERPLX where after the first operation for the first unit, it will go
directly to next operation. It should run one after the other. And the
first
machine should get the next unit.

On the set up we have, the first operation finish first the 261 units
before
it goes to the next.

Regards,
Eriq

As an Amazon Associate we earn from qualifying purchases.