Release Entity to Next Shift

This feature is no longer part of ProcessModel

Model objects are no longer part of ProcessModel. They were prebuilt sample models in the legacy software that you opened and copied the pieces you needed from into your own model. The technique shown here is now built into ProcessModel.

LegacyHow this worked in the previous version

When you need to pass entities to the next shift coming on-line, rather than have the entity wait for the same resource who started to work to return the next day to finish the work.

Where to Find the Model Object

The following model object can be found in the model objects directory:

• Shift - Release Entity to Next Shift, 2 Shifts.
• Shift - Release Entity to Next Shift, 3 Shifts.

Difficulty Level

• Ease of Use: Moderate
• Ease of Modification: Moderate

How to Use the Model Object

• Open your model: Open your model or create a new blank model.

• Insert the Model Object into your model: Locate the model object Release Entity to Next Shift, # Shifts and select the insert button.

• Move the cursor to the point of insertion and left mouse-click. The upper left corner of the model object will be inserted at the location of the mouse-click.

• Define values:

• **Define **the values for scenario parameters s_First_Shift_Start, s_No_Start_Zone, s_Shift_Length, s_Shifts, s_Res#, s_Weekend_Start, and **s_Weekend_Minutes **based on the information provided under the heading Scenario Parameters below. The values for these Scenario Parameters must be provided before the simulation start.

• **Define **the activity time **a_PTR **in the **Process1 **action logic.

Note: Initial activity time is assigned to the a_PTR attribute at the beginning of the Process1 action logic. Then attributes, variables, and scenario parameters are compared to determine how to use the remaining shift time, which resource to GET or FREE, and when.

• **Define **the starting shift number **v_Shift **in the Shift Timer action logic.

Note: A trigger is needed to act as a shift clock, initialize starting variable values, and to assign which shift is currently being used.

Note: The resource must be freed before the shift ends in order to release the entity for processing by the next shift.

• Update objects: Copy the Process1 action logic to the activity/activities in your model where you need to pass “in-process” entities to the next shift.

• Completion: The model object is now integrated into your model, you should now be able to save and then simulate the model.

Controls Usage

Attributes:

• a_PTR: Do not change. Processing Time Remaining (initially the total activity time as a new entity enters the activity).

Variables:

• v_No_Shifts_Time: Do not change. Amount of time, in minutes, between the end of the last shift and the start of the first shift the next day.

• v_Shift: Do not change. Current shift. 1st shift is always the first shift that starts at or after midnight Monday morning.

• v_TLOS: Do not change. Time Left On Shift.

• v_Current_Resource_Available: Do not change. Number of resources currently available.

• v_DayOfWeek: Do not change. Day of the week (Monday = 1).

Scenario Parameters:

• s_First_Shift_Start: User input required. Time, in minutes, after midnight Monday morning, when 1st shift starts.

• s_No_Start_Zone: User input required. Clean up time before shift ends.

• s_Shift_Length: User input required. Duration, in minutes, of one shift.

• s_Shifts: User input required. Number of shifts in a day.

• s_Res1: User input required. First, second, or third resource name.

• s_Weekend_Start: User input required. Day of the week when the weekend starts (default is 6 or Saturday), 0 = no weekend s_Weekend_Minutes = Number of minutes in the weekend (default 2880).