Transit time (APS)

Production > Capacity Planning, APS > Work with APS > Transit time (APS)

Top  Previous  Next
Expand/Collapse Toggles

Transit time can be

- Transportation time from one to another place

- Drying time

- Expand lead times. In this way, urgent work orders can be squeezed in by reducing transit times in APS-calculation types or Priorities

 

Example:

Step 1 is machine a, Step 2 is machine B

When the employee is finished with Step 1, he returns the goods to a collection point.

Later, the next employee collects the goods from the collection point and starts with step 2.

This time in between is an average transit time.

 

The transit time is always the time from preview operation to next operation and is defined in the resource from preview operation.

Transit time is entered in days.

Resource calendar is not taken into account. The factory calendar is considered only if this was enabled in the Configuration wizard.

Minimum transit time is entered: Configuration wizard – Master data – Resources.

 

Configuration of operation sequence:

|--- Transit time --| |-- Planned time --| |--- Idle time--|

 

First operation has no transit time.
Example with 2 operations:

 

Plan time operation 1

Idle time operation 1

Transit time of resource of operation 1

Plan time operation 2

Idle time operation 2

 

Resource-related transit time

It is possible to define different transit times to the next resource.

Example : 1 day to Resource A and 2 days to Resource B.

Click on yellow arrow in field "Transit time". In this window it is possible to insert the target resources with the resource related transfer time.

resource_transittime

stamm_arbplatz_uebgzeit.psr

 

 

Transit time can be used to expand lead times. In this way, urgent work orders can be squeezed in by reducing transit times in APS-calculation types or Priorities

Example

You have transit time 0.5 days

With forward calculation you see: It is not possible to deliver it to the planned delivery date

Now it's possible to decrease the Transit time in APS-calculation types or Priorities

transit1

 

 

Overlapping

In case of overlapping, always the largest transit time is used. The factory calendar is considered only if this was enabled in Configuration wizard.

See Parallel Operation and Overlapping

hmtoggle_plus1Example

 

Operation sequences 1,2 and 3 are parallel: 2 hours each, A2 has a transit time of 2 hours.

Operation 4 is normal with 2 hours duration

 

A1        Start 8:00 - 12:00

A2        Start 8:00 - 12:00

A3        Start 8:00 - 12:00

Idle time A2: 12:00 - 14:00

A4        Start 14:00 - 16:00

 

 

Note:

The system works with internal cache. If you change the transit time per target resource, you must reopen the APS Graphical view.


Help URL:http://www.beascloud.net/docs/help/online_eng/index.html?transittime.htm