Fw: Shop Order Days = Bug Speculation

["Tim Armstrong" <tma@xxxxxxxxxxxxxx>]

>E-mail from Al Macintyre at Tim's PC at work.
Oops - I clicked the wrong button on Tim's e-mail & it was expressed out of
here before I could fix it - this is a common variation on the el-typo bug.
>>____________________________________________
>I broke out a sentence of Stephen's
>to emphasize a line I want to comment on.

>>
>Stephen Wrote:
>>
>>< snip >
>>>
>>>We have stepped through the scheduling engine (SFC739) - arduous task -
>and are very confused about something.
>
>>>It would seem that as the program loops from one operation to the next,
>>>regardless of work center correlation, the
>>>hours of capacity remaining from the previous operation's work center
>>>serves as the basis for the next operation's hours remaining of capacity.
>
>>>Maybe I am completely missing something, but to my simple mind
>>>this makes no sense at all.
>>>The previous operation's work center capacity remaining is
>>>irrelevant to the next work center's capacity.
>>>Can anyone shed some light on this for me?
>>>Each of our work centers has a variable amount of standard
>>>capacity and these remainder hour quantities leave us with partial days
>>>which are apparently rounded up to whole days.  I think that is why we
end
>>>up with 5 days of operation queue.
>>
>>< snip >
>
A plausible bug from what you are saying is there is a work field
= work center capacity remaining on current work center in the math.
When the program moves from one work center to another one, that value might
need to be stashed some place in case the program later needs to return to
the old work station, but in the mean time the working value for the new
work center needs to be flushed of the data from the prior work center &
refreshed with anything previously stashed from prior work on that work
station.
>
If this sounds confusing, then you understand how a computer programmer can
get confused regarding all possible scenarios that our work product ought to
handle with perfection, and/or do some code steps in the wrong sequence.
Some programers make errors in logic.  I am often bitten by the el-typo bug.
Modifying BPCS it is very eary to overlook some essential detail due to our
lack of appreciation for all the variables.
>>____________________________________________
>>Al Macintyre
>>Central Industries of Indiana, Inc.
>>We Harness Quality
>>www.cen-elec.com
>>
>>
>

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---