Data Collection/Operation Completion

Yahoo Archive
1
Have your person creating jobs watch for this and swith the operation to be
6 pieces per hour or 1 fixed hour, etc...

Patrick J. Winter
Information Services Manager
sSc Specialty Screw Corporation
Vantage 3.00.614, Progress 8.3A

-----Original Message-----
From: Ben Roush [mailto:broush@...]
Sent: Friday, September 29, 2000 01:13 PM
To: vantage@egroups.com
Subject: [Vantage] Data Collection/Operation Completion


I was wondering if anyone has had this problem and what they are
doing to resolve it.
We have jobs that have production rates of like 10,000 pcs an hour,
and the customer orders 6 pieces, thus making the est.prod. 0.00 hrs.
When the operator runs the setup on the job, finishes the setup, it
marks the operation complete, and it automatically marks the
production job operation complete as well. So when the operator tries
to clock in to production, they will get an alert that the operation
has already been completed, when it really hasn't. Keep in mind that
this is NOT a "RARE" situation for us. I contacted Epicor (Craig) on
my situation and this is what they had to say.

"I tested this again, using a setup, and you are correct, reporting
setup complete will flag the job as complete. However, this only
happens when the estimated production hours is 0.00. Technically
this would be a bug in the software, but since the cause of it
(10,000 pcs/hour - 6 pc job??) is a rare situation, it is doubtful
that development will devote the resources to fix it. My
recommendation is to not report the setup as complete in this
situation."

We had another conversation with him and he said "that it probably
wouldn't be on the top of there priority list to fix." That
statement bothers me. Large initial investment and yearly maintence
fees topping 25K, come on... it is important.



We no longer allow attachments to files. To access/share Report Files,
please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)
2
I was wondering if anyone has had this problem and what they are
doing to resolve it.
We have jobs that have production rates of like 10,000 pcs an hour,
and the customer orders 6 pieces, thus making the est.prod. 0.00 hrs.
When the operator runs the setup on the job, finishes the setup, it
marks the operation complete, and it automatically marks the
production job operation complete as well. So when the operator tries
to clock in to production, they will get an alert that the operation
has already been completed, when it really hasn't. Keep in mind that
this is NOT a "RARE" situation for us. I contacted Epicor (Craig) on
my situation and this is what they had to say.

"I tested this again, using a setup, and you are correct, reporting
setup complete will flag the job as complete. However, this only
happens when the estimated production hours is 0.00. Technically
this would be a bug in the software, but since the cause of it
(10,000 pcs/hour - 6 pc job??) is a rare situation, it is doubtful
that development will devote the resources to fix it. My
recommendation is to not report the setup as complete in this
situation."

We had another conversation with him and he said "that it probably
wouldn't be on the top of there priority list to fix." That
statement bothers me. Large initial investment and yearly maintence
fees topping 25K, come on... it is important.
3
For these extremely short run operations, couldn't you modify the
production standard to a fixed hours like .01 hours. This would at least
prevent the setup entry from marking the operation as complete. Yes, I know
this could skew your shop schedule somewhat but if you are really doing a
setup before the job, what's an extra 36 seconds of schedule time mean? Just
my .02 worth.
Regards
Jim Stetter


-----Original Message-----
From: Ben Roush [mailto:broush@...]
Sent: Friday, September 29, 2000 2:13 PM
To: vantage@egroups.com
Subject: [Vantage] Data Collection/Operation Completion


I was wondering if anyone has had this problem and what they are
doing to resolve it.
We have jobs that have production rates of like 10,000 pcs an hour,
and the customer orders 6 pieces, thus making the est.prod. 0.00 hrs.
When the operator runs the setup on the job, finishes the setup, it
marks the operation complete, and it automatically marks the
production job operation complete as well. So when the operator tries
to clock in to production, they will get an alert that the operation
has already been completed, when it really hasn't. Keep in mind that
this is NOT a "RARE" situation for us. I contacted Epicor (Craig) on
my situation and this is what they had to say.

"I tested this again, using a setup, and you are correct, reporting
setup complete will flag the job as complete. However, this only
happens when the estimated production hours is 0.00. Technically
this would be a bug in the software, but since the cause of it
(10,000 pcs/hour - 6 pc job??) is a rare situation, it is doubtful
that development will devote the resources to fix it. My
recommendation is to not report the setup as complete in this
situation."

We had another conversation with him and he said "that it probably
wouldn't be on the top of there priority list to fix." That
statement bothers me. Large initial investment and yearly maintence
fees topping 25K, come on... it is important.


We no longer allow attachments to files. To access/share Report Files,
please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go
to www.egroups.com, login and be sure to save your password, choose My
Groups, choose Vantage, then choose Files. If you save the password, the
link above will work the next time you try it.)



[Non-text portions of this message have been removed]
4
Ben,

God strike me dead for saying this but I think I agree with Craig/EPICOR's
assessment. To specify a run standard of 10,000 pieces per hour and then
have a customer order 6 pieces on a make to order basis seems like a pretty
unusual situation to me.

Let's see: 6 pieces divided by 10,000 pieces/hr = 0.036 minutes or 2.16
seconds ... did I do that right ?

Not to ask a stupid question but why would you put a job on the floor that
takes 2.16 seconds ? Doesn't the paperwork take more time than the job ?

At any rate, here's my suggestion - After you copy the Routing to the job -
change the run standard from 10,000 pieces per hour to a "Fixed Time"
increment and put in 1 minute for the production time. That should give
the system something to chew on so that the production standard is not ZERO.

Do you really go to the trouble of setting up a machine just to do one 2.16
second job ?

Can I ask what your business is and why you run jobs like this ?

Please don't be offended by this ... No offense intended !

Todd Anderson
J. Rubin & Co.


-----Original Message-----
From: Ben Roush [mailto:broush@...]
Sent: Friday, September 29, 2000 1:13 PM
To: vantage@egroups.com
Subject: [Vantage] Data Collection/Operation Completion


I was wondering if anyone has had this problem and what they are
doing to resolve it.
We have jobs that have production rates of like 10,000 pcs an hour,
and the customer orders 6 pieces, thus making the est.prod. 0.00 hrs.
When the operator runs the setup on the job, finishes the setup, it
marks the operation complete, and it automatically marks the
production job operation complete as well. So when the operator tries
to clock in to production, they will get an alert that the operation
has already been completed, when it really hasn't. Keep in mind that
this is NOT a "RARE" situation for us. I contacted Epicor (Craig) on
my situation and this is what they had to say.

"I tested this again, using a setup, and you are correct, reporting
setup complete will flag the job as complete. However, this only
happens when the estimated production hours is 0.00. Technically
this would be a bug in the software, but since the cause of it
(10,000 pcs/hour - 6 pc job??) is a rare situation, it is doubtful
that development will devote the resources to fix it. My
recommendation is to not report the setup as complete in this
situation."

We had another conversation with him and he said "that it probably
wouldn't be on the top of there priority list to fix." That
statement bothers me. Large initial investment and yearly maintence
fees topping 25K, come on... it is important.


We no longer allow attachments to files. To access/share Report Files,
please go to the following link: http://www.egroups.com/files/vantage/
<http://www.egroups.com/files/vantage/>
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)