Calculation Performance

Only production orders not yet annotated in SIGASFC are calculated in Machine Load. If the filter adds an order that is already started, it displays the message 'Production Order already started on Shop Floor, therefore you cannot calculate it'.

If the split is allocated or more than one Split exists for the same operation, they are deleted and generated again.

If a production order uses alternative script, it displays a message indicating you cannot use this production order in machine load when the Shop Floor is active: 'When SIGASFC is active, you may not calculate production orders that have alternative scripts'.

The machine load calculates by the beginning or by the end, thus the dates saved are the same for both earlier start and later start fields.

Calculation Completion

When you finish the machine load calculation, the table SH8 (Allocated Operations) is updated with date, time and machine allocated for each operation. Updates to shop floor tables occur as shown below.

Using as example the order 00024601001 for 100 parts, the machine load is executed and generates the following allocations:

When you submit data for SFC tables, the system checks how many records exist for each order of production plus operation. For operation 01, six records exist; thus, six splits exist, as shown below:

• For each record of production plus operation, a split is created in SIGASFC. Using the above example, six splits (five divisions) are generated for order 00024601001 operation 01, using allocation quantities (H8_QUANT) and the allocated machine (H8_RECURSO).
• When no setup exists, the start date/time is used as earlier start date/time and later start date/time.
• Using the end date/time to complete the earlier end date/time and later end date/time.
• Check the split as calculated via machine load: CYY_LGCGMQ = Yes.
• Once you update the allocation dates also in the operation, considering all allocations made for it, placing the start of the first allocation as the start of the operation and the end of the last allocation as the end of the operation.

Considering the aforementioned rules, the records are created as follows:

Split

Operation

These data are also updated in the SHY table (Operations x Order) with the same information as that updated on SFC operations (CY9).

When the allocation record has setup, field H8_SETUP is filled out with the number of gantt positions, as shown below:

You need to calculate the date and time the setup starts. Following the rules:

• To calculate setup time, use function Bit2Tempo, passing as parameter the field H8_SETUP. The function returns the time in format HH:MM.
• When the allocation record has setup, consider the start of setup as the start of allocation (H8_DTINI, H8_HRINI).
• The date and time production starts is equal to that calculated based on the previously calculated setup time.
• Check the split as calculated via machine load: CYY_LGCGMQ = Yes.
• You must also update the operation.

Considering these rules, the records become as follows:

Split

Operation

Change Estimated Delivery Date

It changes the delivery date of the production order and copies the information to the Shop Floor.

Procedures:

Doing machine load:

1. In the Machine Load Maintenance window, enter the data to run the machine load.
2. Execute it.
3. When the integration with the SIGASFC is active, the production orders still receiving some production annotation do not figure in the calculation.
4. The allocation made is for the Split of SIGASFC; thus, each machine allocated for an operation generates an allocation of a Split. In case the machine load allocates three machines for the same operation, the system generates three splits, one for each machine.
5. In case the production order has an alternative script, the calculation of this order cannot be performed.
6. The splits calculated receive a mark in the Split through field Machine Load (CYY_LGCGMQ).