Re: Routing Logic -- BPCS-L

Hi Eriq,

As you described the routing here, I can understand that each
operation processes only one unit at a time. If you have a shop order
of 10 units, the 10 units will go to each operation one at a time. And
the first unit completed at the last operation, waits for the other 9
units to be completed. Am I right?

If you want to make a routing, the setup time, operation time, move
time, and queue time is based per shop order and not per unit.

So, if you have a shop order with 10 units, the setup time and move
time and queue time will be the same as the shop order with one unit
only for each operation. But the operation time is computed based on
the time spent per unit and then multiplied by the number of units.

Therefore, when you want to setup a routing, consider only the
critical workstations.
Those operations which contributes for a particular output is
considered one workstation although you have 5 different smaller
operations.

So,for your example, this is considered one workstation. The next
workstation will process the whole shop order one at a time too with
smaller operations.

Simultaneous operations will only happen if you have part A going to
Operation1, and Part B going to Operation2, then they are assembled in
Operation 3. That is another scenario. It is not the same as the one
you described as all the units will go from Operation 1 up to
Operation 5.

Hope this idea helps.

Regards,

Xu Xen

On 12/10/11, bpcs-l-request@xxxxxxxxxxxx <bpcs-l-request@xxxxxxxxxxxx> wrote:

Send BPCS-L mailing list submissions to
bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of BPCS-L digest..."

*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. Re: Routing Logic (Eriq Lorilla)

----------------------------------------------------------------------

message: 1
date: Fri, 9 Dec 2011 10:27:07 +0800
from: "Eriq Lorilla" <eriq.l@xxxxxxxxxxxx>
subject: Re: [BPCS-L] Routing Logic

Thanks for all the ideas.. The easiest way is to do parallel routing. The
posting will be doing the actual reporting..

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bud North (PHOENIX)
Sent: Thursday, December 08, 2011 12:06 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] Routing Logic

Eriq,

I guess I'm having trouble with the word simultaneous as it's used in your
scenario. Webster defines simultaneous as 'existing or occurring at the
same time, exactly coincident. Ex. The two events were simultaneously
scheduled to start at 10 AM.' This sounds more like parallel than what you
are describing below. What you describe is overlap or send ahead - that is
if I understand your example below correctly.

What I understand you want is:
Operation 1 - starts day 1, hour 1, minute 1 Operation 2 - starts day 1,
hour 1, minute 2 (or whatever time it takes to complete the first unit) The
way BPCS handles this is with negative move and/or queue. However, the
smallest increment of move and queue that can be entered is a single decimal
of days - which means 1/10 of a day.
I think another reply asked about what basis code you are using on the
routing. Using the 'P' basis code may be of some help. You say you can
produce 261 unit in a day. You could translate that into pieces per hour
and try negative .1 day of queue and see what happens.
As far as capacity, if you say you can product 32.62 pieces per hour using
basis code 'P' (this equates roughly to 261 pieces in an 8 hour day) and if
you're capacity is 8 hrs, then if you have an order for 270, BPCS should
schedule the completion the following day.

Bud North, CPIM
Phoenix Business Consulting
Cell: 508-572-9701
Email: bnorth@xxxxxxxxxxxxxxxx

Eriq states:
Please see below for the scenario I am trying to reconcile:

I have 5 operations which are machine dependent. This will be a continuous
process that means after the first unit on the first operation, it will go
to the second machine/operation and the first machine will process the next
unit. This will be going up to the fifth operation.

If the 5 operation/machine can finish 261 units in a day, that means the
shop order will schedule it in a day. The problem with the -1 move days, it
does parallel scheduling for 5 machines/operation. It means that it will run
the operation at same time and not simultaneously. And if I have more than
the capacity per day of that 5 operation which is more than 261, for example
270 units. It will still schedule the shop order in a day since the
operations are running at same time and it does not compute for the
simultaneous operation time.
Does anyone have idea on defining the routing simultaneously?

________________________________________
From: bpcs-l-bounces@xxxxxxxxxxxx [bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of
bpcs-l-request@xxxxxxxxxxxx [bpcs-l-request@xxxxxxxxxxxx]
Sent: Tuesday, December 06, 2011 1:00 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 9, Issue 185

Send BPCS-L mailing list submissions to
bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of BPCS-L digest..."

*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. Re: Routing Logic (Roger.Henady@xxxxxxxxxx)
2. Routing Logic (Bud North (PHOENIX))
3. Re: Routing Logic (Eriq Lorilla)
4. Re: Routing Logic (Mark Sabol)
5. Re: Routing Logic (Bryce Martin)

----------------------------------------------------------------------

message: 1
date: Mon, 5 Dec 2011 12:15:15 -0600
from: Roger.Henady@xxxxxxxxxx
subject: Re: [BPCS-L] Routing Logic

The total hours required is correct. The costing will account for all
the time.

Are you trying to schedule start date / completion date?
There is a move time field. You can use < move > to overlap
operations. Problem this is a fixed number of time not PPH.

Does anybody knows how to route 5 operations/machines simultaneously?

If all 5 happen simultaneously like in a cell / continues flow.
You could create a work center that represents the cell (all 5 steps).
Then adjust the number of operators to calculate labor hours.

If all happen in a flow do you really want to report at each step?

Roger Henady

From: Bryce Martin <BMartin@xxxxxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Date: 12/05/2011 09:57 AM
Subject: Re: [BPCS-L] Routing Logic
Sent by: bpcs-l-bounces@xxxxxxxxxxxx

Eriq,
I haven't had a chance to deeply look at your particular scenario in LX yet,
but there isn't anything in BPCS that keeps track of each individual Unit of
a shop order. You basically just report what has been completed.
So you can report on any of the operations some quantity completed. When
the total quantity for an operation has been completed you mark that
operation complete. The next operation is still open and the difference
between the Needed vs Finished is the outstanding - obviously. So it
would look something like this....

SO creation - No work completed yet.
OP1 - Req = 261 Fin = 0
OP2 - Req = 261 Fin = 0
OP3 - Req = 261 Fin = 0
OP4 - Req = 261 Fin = 0
OP5 - Req = 261 Fin = 0

First piece on OP1 completed.
OP1 - Req = 261 Fin = 1
OP2 - Req = 261 Fin = 0
OP3 - Req = 261 Fin = 0
OP4 - Req = 261 Fin = 0
OP5 - Req = 261 Fin = 0

Second piece on OP1 completed.
OP1 - Req = 261 Fin = 2
OP2 - Req = 261 Fin = 1
OP3 - Req = 261 Fin = 0
OP4 - Req = 261 Fin = 0
OP5 - Req = 261 Fin = 0

Third piece on OP1 completed.
OP1 - Req = 261 Fin = 3
OP2 - Req = 261 Fin = 2
OP3 - Req = 261 Fin = 1
OP4 - Req = 261 Fin = 0
OP5 - Req = 261 Fin = 0

Fourth piece on OP1 completed.
OP1 - Req = 261 Fin = 4
OP2 - Req = 261 Fin = 3
OP3 - Req = 261 Fin = 2
OP4 - Req = 261 Fin = 1
OP5 - Req = 261 Fin = 0

Fifth piece on OP1 completed.
OP1 - Req = 261 Fin = 5
OP2 - Req = 261 Fin = 4
OP3 - Req = 261 Fin = 3
OP4 - Req = 261 Fin = 2
OP5 - Req = 261 Fin = 1

There isn't anything to keep you from starting on the next operations just

because the first one hasn't been completed for the total quantity.

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

"Eriq Lorilla" <eriq.l@xxxxxxxxxxxx>
Sent by: bpcs-l-bounces@xxxxxxxxxxxx
12/05/2011 04:01 AM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>

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

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

--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.

CONFIDENTIALITY: This e-mail is for the sole use of the intended
recipient(s) and may contain confidential and/or privileged information.
Distribution of any kind is strictly prohibited. If you are not the intended
recipient, please contact sender via reply e-mail, and then discard.

------------------------------

message: 2
date: Mon, 5 Dec 2011 17:28:36 -0500
from: "Bud North (PHOENIX)" <bnorth@xxxxxxxxxxxxxxxx>
subject: [BPCS-L] Routing Logic

Eriq,

Bryce is correct regarding the 'reporting of production'. However, your
question asks 'how to route 5 operations/machines simultaneously'. This
suggests you are trying to figure out a way to perform parallel scheduling
of the 5 operations. You do provide information in the 2nd paragraph
referencing first operation for the first unit, going directly to next
operation - which would contradict parallel scheduling and be more like
overlap scheduling, also referred to as send ahead. I have created a kind
of white paper on some findings regarding BPCS work center scheduling logic
that I'd be happy to forward directly to you as an attachment if requested.

The net is that normal BPCS scheduling logic for start and due date
calculations for use in capacity planning and work center scheduling uses
linear scheduling - meaning operation 1, then operation 2, then operation 3,
and so on. If you want operation 2 to start before operation 1 finishes
(overlap or send ahead) the use of some combination of negative queue and/or
move time allows this to be accomplished from a scheduling perspective.
Likewise, parallel scheduling (operation 1 and operation 2 start on the same
date and complete on the same date) can also be accomplished using negative
queue and/or move.

The calculation of start and end dates using any of the 3 methods (linear,
overlap, parallel) don't prevent you from reporting hours/quantities as they
are completed as Bryce indicates.

Hope this helps.
Regards, Bud

Bud North
PHOENIX Business Consulting, Inc.
Cell: 508-572-9701
Email: bnorth@xxxxxxxxxxxxxxxx

__________ Information from ESET Smart Security, version of virus signature
database 6686 (20111205) __________

The message was checked by ESET Smart Security.

http://www.eset.com

------------------------------

message: 3
date: Tue, 6 Dec 2011 11:47:57 +0800
from: "Eriq Lorilla" <eriq.l@xxxxxxxxxxxx>
subject: Re: [BPCS-L] Routing Logic

Hi,

I appreciate all replies.
Please see below for the scenario I am trying to reconcile:

I have 5 operations which are machine dependent. This will be a continuous
process that means after the first unit on the first operation, it will go
to the second machine/operation and the first machine will process the next
unit. This will be going up to the fifth operation.

If the 5 operation/machine can finish 261 units in a day, that means the
shop order will schedule it in a day. The problem with the -1 move days, it
does parallel scheduling for 5 machines/operation. It means that it will run
the operation at same time and not simultaneously. And if I have more than
the capacity per day of that 5 operation which is more than 261, for example
270 units. It will still schedule the shop order in a day since the
operations are running at same time and it does not compute for the
simultaneous operation time.
Does anyone have idea on defining the routing simultaneously?

Regards,
Eriq

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bud North (PHOENIX)
Sent: Tuesday, December 06, 2011 6:29 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Routing Logic

Eriq,

Bryce is correct regarding the 'reporting of production'. However, your
question asks 'how to route 5 operations/machines simultaneously'. This
suggests you are trying to figure out a way to perform parallel scheduling
of the 5 operations. You do provide information in the 2nd paragraph
referencing first operation for the first unit, going directly to next
operation - which would contradict parallel scheduling and be more like
overlap scheduling, also referred to as send ahead. I have created a kind
of white paper on some findings regarding BPCS work center scheduling logic
that I'd be happy to forward directly to you as an attachment if requested.

The net is that normal BPCS scheduling logic for start and due date
calculations for use in capacity planning and work center scheduling uses
linear scheduling - meaning operation 1, then operation 2, then operation 3,
and so on. If you want operation 2 to start before operation 1 finishes
(overlap or send ahead) the use of some combination of negative queue and/or
move time allows this to be accomplished from a scheduling perspective.
Likewise, parallel scheduling (operation 1 and operation 2 start on the same
date and complete on the same date) can also be accomplished using negative
queue and/or move.

The calculation of start and end dates using any of the 3 methods (linear,
overlap, parallel) don't prevent you from reporting hours/quantities as they
are completed as Bryce indicates.

Hope this helps.
Regards, Bud

Bud North
PHOENIX Business Consulting, Inc.
Cell: 508-572-9701
Email: bnorth@xxxxxxxxxxxxxxxx

__________ Information from ESET Smart Security, version of virus signature
database 6686 (20111205) __________

The message was checked by ESET Smart Security.

http://www.eset.com

--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.

------------------------------

message: 4
date: Tue, 6 Dec 2011 08:08:29 -0500
from: Mark Sabol <msabol@xxxxxxxxxxxxxxxx>
subject: Re: [BPCS-L] Routing Logic

Bud,
I'd be interested in you white paper.

Mark Sabol
Flanders Corporation

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bud North (PHOENIX)
Sent: Monday, December 05, 2011 5:29 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Routing Logic

Eriq,

Bryce is correct regarding the 'reporting of production'. However, your
question asks 'how to route 5 operations/machines simultaneously'. This
suggests you are trying to figure out a way to perform parallel scheduling
of the 5 operations. You do provide information in the 2nd paragraph
referencing first operation for the first unit, going directly to next
operation - which would contradict parallel scheduling and be more like
overlap scheduling, also referred to as send ahead. I have created a kind
of white paper on some findings regarding BPCS work center scheduling logic
that I'd be happy to forward directly to you as an attachment if requested.

The net is that normal BPCS scheduling logic for start and due date
calculations for use in capacity planning and work center scheduling uses
linear scheduling - meaning operation 1, then operation 2, then operation 3,
and so on. If you want operation 2 to start before operation 1 finishes
(overlap or send ahead) the use of some combination of negative queue and/or
move time allows this to be accomplished from a scheduling perspective.
Likewise, parallel scheduling (operation 1 and operation 2 start on the same
date and complete on the same date) can also be accomplished using negative
queue and/or move.

The calculation of start and end dates using any of the 3 methods (linear,
overlap, parallel) don't prevent you from reporting hours/quantities as they
are completed as Bryce indicates.

Hope this helps.
Regards, Bud

Bud North
PHOENIX Business Consulting, Inc.
Cell: 508-572-9701
Email: bnorth@xxxxxxxxxxxxxxxx

__________ Information from ESET Smart Security, version of virus signature
database 6686 (20111205) __________

The message was checked by ESET Smart Security.

http://www.eset.com

--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.

------------------------------

message: 5
date: Tue, 6 Dec 2011 08:22:51 -0500
from: Bryce Martin <BMartin@xxxxxxxxxxxx>
subject: Re: [BPCS-L] Routing Logic

Eriq,
What are the workcenters' Basis code?

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

"Eriq Lorilla" <eriq.l@xxxxxxxxxxxx>
Sent by: bpcs-l-bounces@xxxxxxxxxxxx
12/05/2011 10:47 PM
Please respond to
BPCS ERP System <bpcs-l@xxxxxxxxxxxx>

To
"'BPCS ERP System'" <bpcs-l@xxxxxxxxxxxx> cc timbpcs@xxxxxxxxx Subject
Re: [BPCS-L] Routing Logic

Hi,

I appreciate all replies.
Please see below for the scenario I am trying to reconcile:

I have 5 operations which are machine dependent. This will be a continuous
process that means after the first unit on the first operation, it will go
to the second machine/operation and the first machine will process the next
unit. This will be going up to the fifth operation.

If the 5 operation/machine can finish 261 units in a day, that means the
shop order will schedule it in a day. The problem with the -1 move days, it
does parallel scheduling for 5 machines/operation. It means that it will run
the operation at same time and not simultaneously. And if I have more than
the capacity per day of that 5 operation which is more than 261, for example
270 units. It will still schedule the shop order in a day since the
operations are running at same time and it does not compute for the
simultaneous operation time.
Does anyone have idea on defining the routing simultaneously?

Regards,
Eriq

-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bud North (PHOENIX)
Sent: Tuesday, December 06, 2011 6:29 AM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Routing Logic

Eriq,

Bryce is correct regarding the 'reporting of production'. However, your
question asks 'how to route 5 operations/machines simultaneously'. This
suggests you are trying to figure out a way to perform parallel scheduling
of the 5 operations. You do provide information in the 2nd paragraph
referencing first operation for the first unit, going directly to next
operation - which would contradict parallel scheduling and be more like
overlap scheduling, also referred to as send ahead. I have created a kind
of white paper on some findings regarding BPCS work center scheduling logic
that I'd be happy to forward directly to you as an attachment if requested.

The net is that normal BPCS scheduling logic for start and due date
calculations for use in capacity planning and work center scheduling uses
linear scheduling - meaning operation 1, then operation 2, then operation 3,
and so on. If you want operation 2 to start before operation 1 finishes
(overlap or send ahead) the use of some combination of negative queue and/or
move time allows this to be accomplished from a scheduling perspective.
Likewise, parallel scheduling (operation 1 and operation 2 start on the same
date and complete on the same date) can also be accomplished using negative
queue and/or move.

The calculation of start and end dates using any of the 3 methods (linear,
overlap, parallel) don't prevent you from reporting hours/quantities as they
are completed as Bryce indicates.

Hope this helps.
Regards, Bud

Bud North
PHOENIX Business Consulting, Inc.
Cell: 508-572-9701
Email: bnorth@xxxxxxxxxxxxxxxx

__________ Information from ESET Smart Security, version of virus signature
database 6686 (20111205) __________

The message was checked by ESET Smart Security.

http://www.eset.com

--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.

--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.

--- This message (including any attachments) is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential, and
exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us and destroy
this message immediately. ---

------------------------------

--
This is the BPCS ERP System (BPCS-L) digest list To post a message email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.

End of BPCS-L Digest, Vol 9, Issue 185
**************************************

__________ Information from ESET Smart Security, version of virus signature
database 6689 (20111206) __________

The message was checked by ESET Smart Security.

http://www.eset.com
--
This is the BPCS ERP System (BPCS-L) mailing list To post a message email:
BPCS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/bpcs-l.

------------------------------

--
This is the BPCS ERP System (BPCS-L) digest list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/bpcs-l.

End of BPCS-L Digest, Vol 9, Issue 188
**************************************