Subject: Re: Routing Logic From: "Eriq Lorilla" Date: Tue, 6 Dec 2011 11:47:57 +0800 List-archive: List-help: List-id: BPCS ERP System List-post: List-subscribe: , List-unsubscribe: ,

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.

As an Amazon Associate we earn from qualifying purchases.