Scheduling in 9.05.700C

Yahoo Archive
1

Good morning Manasa,

 

We are somewhat in the same position in that labor is our major constraint.  What we are planning on doing is creating a “Planned Job” once we receive a PO from our customer.  On the “Planned Job” we will load up the number of hours per Resource Group (Work Center) that we quoted / estimated.  We will also load up any long lead items (must be stock items) to enable Purchasing to get a jump on the demand.  Once the Drawing package Job is received from Drafting/ Engineering, then Production Control will build the jobs with the actual routings, times, materials, etc.  Immediately prior to Releasing the “Final Job”, Production Control will delete the “Planned Job”.

 

While we have tested the process, we have not fully implemented Epicor to see the true net results.  We are hoping to use the Planned order for Rough Cut Capacity planning.  It appears that Epicor in its scheduling tries to find a time slot for the total hours per work center / resource group.  In the original estimate (planned job) we may have 100 total hours go across a particular work center.  Once the final job is released, these 100 total hours could be broken down into 25 individual assemblies taking an average of 4 hours.  In the Planned job Epicor tries to find a block of 100 hours.  When the final order  is entered, Epicor tries to find 25 blocks of time.  Everyone needs to realize that the Planned Job is a Rough estimate.  It is similar to trying to put large rocks into a jar.  Once you break the rock into smaller pieces, more material can fit into the jar.  We are continually looking out how we can break the rocks into finer pieces and refine the Planned order to more closely replicate the Final order.

 

I don’t know if this helps, but it is the best solution that we were able to come up with.  We go Live across all plants in a couple of weeks.  We’ll know more then.

 

J

Ron

 

Ron Brown

Process Manager

Tank Connection

3609 N. 16th St.

Parsons, KS 67357

Office: 620-423-3010 ext. 158

Email: rbrown@...

 

 

            

NOTICE: This email and any attachments are considered confidential and intended for the addressee only. If you have received this email in error, please notify the sender as soon as possible and delete this email. If you are not the intended addressee, any dissemination, distribution or copying of this message is strictly prohibited by law.


2

Quick question for the group on scheduling:

Background: When we create a job we schedule our operations first to give us a heads up  on an approximate due date.  We do this because we are more labor intensive than we are material constrained so we need to know what our capacity issues will be ahead of time.

Issue:  When we first create the job we will change our resources on the ops then schedule.  Then we add the materials (this can take about a week depending on the job).  When we schedule it again we lose our resources we originally added to the ops.

When we talked to Epicor on this it was a company issue (meaning it was our issue and there was nothing Epicor could do for us).

I am wondering if anyone else does something similar and had a workaround that we could use?

Manasa