In order to simplify the tutorial, the ERPlite source code version download includes sample data (DbM_be.mdb) for Shop Floor Control. This sample data facilitates learning , without having to enter tons of data. Normal installation of ERPlite source code installs the file C:\DbM\Backend\DbM_be_sample.mdb, but the ERPlite Frontend does not link to this backend (in order to avoid overwriting your custom data). To install the sample data:
Admin > Link to Database Backend > Change > navigate to C:\DbM\Backend\DbM_be_sample.mdb
You can switch back to your custom data using a similar renaming process.
The basic shop floor configuration process is:
1. Create the Shop Floor Control Configuration Data.
ERPlite Switchboard -> Mfg Orders -> SFC Configuration
1.1 Enter the Company Time Definition (use the sample data shown below until you understand changes that you would like).
If you pick a period definition(say Months) different than the current definition for Lead Time (say days), then ERPlite will convert the leadtimes from days to Months (rounding up to the next integer for values exeedint x.5 and rounding down otherwise). In most companies, planning is done in days. Thus, if macro planning is done in months, most leadtimes will be zero. Since the purpose of macro planning is generally focussed on inventory levels and PO's for long lead time items, the fact that short leadtimes are zero doesn't impact major decisions.
Sometimes you will need to reset the lead time definition. see the companion tutorial re how to do that.
1.1.2 Enter the Calendar Definitions (only needed for MRPlitePlanner use).
1.2. Step 2: Define Labour Groups
1.3. Step 3: Define Equipment Groups
Following are two sample Equipment Groups from the sample data:
1.4 Step 4: Define Operations
The sample data assumes a simple final assembly process:
START -> ASSEMBLY->LOADTEST->FINISH
Following are the Operations definition screens for this process:
Step 4: Define Routing Lists in ItemMaster
Following is a completed routing list:
Note that the routing for the PRD1000 is a non-linear extension of the simple routing list above.
The flow is :
START->ASSEMBLY->LOADTEST-> FINISH OR REWORK and send back to LOADTEST.
The output of LOADTEST is specified as the % that FINISH and the % that go to REWORK.
In order to construct the routing list, the OPERATIONS have to have been previously defined (step 4 above). The first operation must start with START:
Then the following screen results:
Pick the first TO operation after start (say ASSEMBLY):
Note that the details of the chosen operation are displayed on the right. The Operations Name cannot be edited on this screen (greyed out), because it must be defined in an earlier step. However, you can customize the description and some other parameters of this operation.
Continue adding operations until you get the final routing list: