ILVS production reporting through Shop floor

 CMS provides specialized functionality of production reporting of ILVS through shop floor. This functionality is provided using specialized shop floor events which are aware of ILVS. These events are These events make shop floor engine aware of sequential requirements received through EDI document 866 or through broadcast.  These events are  10160, 330060, 40061,10102,40062,51061,51060.

Production Schedule vs Build Schedule

When a production order is created two types of schedules are created. One is production and the other is build schedule. When you print a manager's report you are looking at production schedule. When you print build schedule you are looking at build schedule. Production schedule represents when a production order will start and end. Build schedule represents when actually it will be build.

It is very critical to understand the difference between too as they influence the outcome of MRP, finite scheduling, white board scheduling , how production demand will be removed from the system when production is reported, inventory allocations etc.

Build schedule is represented by three tables called PLAN, FIRM and SOFT. They are not identical tables. I usually use SQL with union to get the data from them in unison.

In future I will be posting tips explaining how to configure they system to achieve desire results.

Repetitive Scheduling per shift

iVP CMS repetitive scheduler is enhanced to enable whiteboard repetittive scheduler to select a specific shift for scheduling.

Let's have a fight.

If two people fight who is gonna win? Wife of-course (and no this is not from personal experience.) If production scheduler fights with accountant about setting production run rates vs cost run rates who is gonna win? Well in case of  iVP CMS ERP both. Accountant can use 'Schedule run standard' for costing and production manager can use 'Production run rate' for scheduling. I know from my experience that some users use very high production run rate to accomplish zero costing but in my opinion this is not a good way of setting up the system. This works just because of rounding, and this is not a documented feature. As a matter of fact I am not sure who knows about it. What if a program change increase a variable length and instead of zero cost you start getting a different cost? Why not use production vs schedule run rate?

Production Scheduling

The top most way of scheduling production is manual scheduling also called 'Fixed' or 'Set' requirements. After running MRP and finite critical jobs can be 'fixed' or 'set' so that subsequent run of MRP and finite don't move them around.