Incoming Jobs at Combiner with different ItemTypes from Source

Question

question

Herwina Richelle Andres asked Nov 3, '16 Herwina Richelle Andres commented Nov 5, '16

Incoming Jobs at Combiner with different ItemTypes from Source

I would like to ask as to how do I control the inputs of the port 2 of the combiner?

As shown from the snapshot, Source_Job contains the arrival schedule of the jobs to be processed by InPROCESS. There are 5 jobs of three different itemtypes, each having different quantities.

1. On PRE

I am trying to accept the jobs in the same sequence as stated in the Arrival Schedule. A change in itemtype would require a different resource (technician) and would take longer PRE time (20 minutes). Else, it would use call for the operator and will take 10 minutes.

It is important to track how many itemtype changes that occurred within the period. GlobalVariable?

2. On InPROCESS

Each ItemType would have a different processing time.

Global Table: InPROCESS and POST

3. On POST

Each ItemType would have a different POST time

Global Table: InPROCESS and POST

Thank you for the help!

Best,

Herwina Richelle Andres

Software Version:

FlexSim 7.5.4

combiner itemtype input port

source-job.jpg (59.3 KiB)

lot-flow-1-plane-customstate-2.fsm (40.3 KiB)

· 2

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Sam Stubbs ♦ commented · Nov 04, 2016 at 07:18 PM

I am uncertain what you mean by itemType changes. Could you clarify a little?

0 ·

Herwina Richelle Andres Sam Stubbs ♦ commented · Nov 04, 2016 at 10:15 PM

Hi @Sam Stubbs.

It would be on the sequence of the job being processed.

From the snapshot above for the source, there are 5 jobs with 3 itemtypes (2, 3 and 4).

Job 1, Item Type 2 will be followed by Job 2 Item Type 3. Since the Item Type has changed, I would be calling a technician to do the set-up. Therefore 1 count on Item Type change.

On Job 4, Item Type 4 followed by Job 5 Item Type 4, No Item Type change has occured, therefore no count.

I am still studying the model that Brandon has done, but I believe it has covered the rules of incoming ItemTypes.

Thank you!

0 ·

Answer 1 · 2016-11-04T13:00:33Z

Brandon Peterson answered Nov 4, '16 Herwina Richelle Andres commented Nov 5, '16

Herwina,

Here is a modified version of your model. I believe that it is doing everything that you need it to do except for tracking the number of itemtype changes per period. I think that @Sam Stubbs will be able to help you out with that.

I hope this helps,

Brandon

lot-flow-1-plane-customstate-v7-5-4-mv-1.fsm (39.9 KiB)

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Herwina Richelle Andres commented · Nov 05, 2016 at 11:57 AM

lot-flow-1-plane-customstate-2-itemtype.fsm

Hi @Brandon Peterson

Thank you for helping me out. I have some questions though on the method used and have additional conditions that I would like to be included in the model that may be off the topic of ItemTypes. I will just include them in here as well.

1. On PRE

The sequence of jobs coming in and the quantity of each are correct. Also, calling the technician for ItemType changes and Operator on non-ItemType change is working correctly.

I have added to set the state of the container to OnSETUP when it is the technician processing and EAA_PRE when it is the Operator.

Now, I need to ensure that if the resource is busy when picked, the state of PLANE17 would be WaitForOp_EAA_PRE for Operator or WaitForTech_SETUP for the technician.

2. On InPROCESS

I have added a MTBF and MTTR specific to processing state and would require the assistance of Technician. State should be OnREPAIR. Should the technician be busy when picked, state should be WaitForTech_REPAIR.

Another thing is to mimic MTBF and MTTR but rather than in units of time, it would be in units of each entity. Mean Units Between Assist (MUBA). It would stop processing and call the operator for a certain period of time before it resumes processing.

3. On POST

This is an ItemType concern. Queue4 is like the staging area after processing where it would wait for all the units of the specific job to be finished processing before everything moves to POST. On Exit at Queue4, it would trigger the source pallet to open its output to send a pallet to POST. OnExit at sourcepallet, the output should be closed again.

This ensures that the WaitForOp_EAA_POST does not get fired when the pallet has arrived early at POST.

Thank you so much for the help!

0 ·

lot-flow-1-plane-customstate-2-itemtype.fsm (45.7 KiB)

question