Cancel
Showing results for 
Search instead for 
Did you mean: 

Pulling same MU type to reduce changeover

 

 

 

1.PNG 

 

 

 2.PNG

 

 

 There are 3 parts that should be processed in the sequence M1- (M2 or M3)

The first Entity of Part 1 i.e Part 1.1 is processed in M2 and part 1.2 would be processed in M3.But I want to the MU Part1.2 to be processed in M2 only  to reduce changeover times. What should be the Exit Strategy of M1

7 REPLIES

Re: Pulling same MU type to reduce changeover

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor
you could use the exit strategy MU attribute (string)
You can use the name of the MU to assign a fixed successor number.
Steffen Bangsow
freelance simulation specialist  
web: www.bangsow.eu
mail: steffen@bangsow.net

Re: Pulling same MU type to reduce changeover

Sorry Sir, I feel my question was ambiguous .( I will elaborate it again as follows) 

The logic should be such that each type of entities are processed on  the same station to reduce setup changeovers. If MU attribute used in exit strategy ,then it will have a  fixed sucessor

For eg. Suppose consider the part 2.1 exits from M1 , now it can enter either M2 or M3  (based on their availabilty) .If suppose part 2.1 enters M3 , then part 2.2 should necessarily enter M3 . If later, part 3.1 exits from M1 , it should have the liberty to enter either M2 or M3 .Similarly part 3.2 should also follow the same path as part 3.1.

Re: Pulling same MU type to reduce changeover

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

you could try an exit control;

- check if one of the successors is setup for the MU (name) --> if yes --> waituntil  this successor is empty

--> if not wait for the first empty machine

 

see help isSetUpFor

 

Steffen Bangsow
freelance simulation specialist  
web: www.bangsow.eu
mail: steffen@bangsow.net

Re: Pulling same MU type to reduce changeover

Sir , I have tried to build a exit control using the command isSetupfor but its not working .Can you help me with it 

Re: Pulling same MU type to reduce changeover

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

this could be the exit control of M1

 

-- is setup for the MU (color) --> if yes --> waituntil  this successor is empty

--> if not wait for the first empty machine
if M2.isSetupFor=@.color then
	waituntil M2.empty and M2.operational 
	@.move(M2)
elseif M3.isSetupFor=@.color then
	waituntil M3.empty and M3.operational 
	@.move(M3)
else
	waituntil (M3.empty and M3.operational) or (M2.empty and M2.operational)
	if (M3.empty and M3.operational) then
		@.move(M3)
	else
		@.move(M2)
	end
end
Steffen Bangsow
freelance simulation specialist  
web: www.bangsow.eu
mail: steffen@bangsow.net

Re: Pulling same MU type to reduce changeover

Genius
Genius

I hve a similar problem and was trying to use the isSetupFor function. But I have a question after reading this reply

if M2.isSetupFor=@.color

 

Here we have compared the isSetupFor with the MU Attribute. When I use it, it always returns the MU Name.

How can I get the isSetupFor to return an attribute(like color in this case)? 

 

This would really help me a lot.

Re: Pulling same MU type to reduce changeover

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor
you need to select in the station, tab set-up

set-up depends on: user defined attribute --> color

The the set-up will take place, if the value of the color attribute changes
Steffen Bangsow
freelance simulation specialist  
web: www.bangsow.eu
mail: steffen@bangsow.net