Building the Model: Advanced Elements > Modeling Tips > Creating Pull Systems

Creating Pull Systems

Types of Pull Systems

A pull system is a system in which locations produce parts only on downstream demand. There are two types of pull systems:

The first method, that of limited buffer sizes, is quite easily to model using ProModel. By simply defining limited capacity locations, a preceding location will not send parts until capacity is available. This method works fine for most pull systems. The second method, triggering part movement, based on more distant downstream demand requires use of the SEND statement to trigger part movement.

 

There are additional ways to model pull systems using ProModel. As you review the modeling requirements of your own pull system, you should verify that these constructs will satisfy your needs.

 

This section shows how to use the SEND statement to model a pull system. The diagram below shows the pull system we will model. Orders for finished goods arrive at the OrderQue. The arriving order triggers the release of a unit from the location Stores. The order continues to wait at OrderQue until the unit goes through Processes 1 and 2. At Process_1, Unit processes for two minutes. At Process_2, Unit processes for four minutes. Finally, the Unit joins to the requesting order waiting in the OrderQue.

Creating the Pull System

Now let's examine the ProModel steps to build this pull system.

  1. Define four locations: Stores, Process_1, Process_2, and OrderQue.
  2. Define two entities: Order and Unit.
  3. Define the processing as shown previously.
  4. Define the arrivals. Schedule Units to arrive at location Stores. Schedule Orders to arrive at location OrderQue.
  5. The entity Order “drives” the system by sending Units to Process_1 to fulfill the order. In the operation logic at OrderQue, use the SEND statement to send a Unit to Process_1 from location Stores. A corresponding SEND rule must be used as a Routing Rule for Unit at Stores.
  6. After the SEND statement in the operation logic at the OrderQue, use a JOIN statement to join a Unit to an Order. A corresponding JOIN rule must be used as a Routing Rule for Unit at Process_2.
  7. Place the processing times for the Unit at Process_1 and Process_2.

When you finish, the processing and routing should appear as shown below.

Process Table and Routing Table

Entity

Location

Operation (min)

 

Output

Destination

Rule

Move Logic

Unit

Stores

 

1

Unit

Process_1

SEND 1

 

Unit

Process_1

WAIT 2

1

Unit

Process_2

FIRST 1

MOVE FOR .5

Unit

Process_2

WAIT 5

1

Unit

OrderQue

JOIN 1

MOVE FOR .5

Order

OrderQue

SEND 1 Unit TO Process_1

JOIN 1 Unit

1

Order

EXIT

 

 


© 2012 ProModel Corporation • 556 East Technology Avenue • Orem, UT 84097 • Support: 888-776-6633 • www.promodel.com