Model objects are pre-built, self-contained, smart, model
segments that can be plugged into your models in seconds and
save you hours of modeling time. The same concept that manufacturers
have used to build products can be used to assemble simulation
models. Just as a PC manufacturer wouldn’t think of
building a power supply each and every time they needed one,
you shouldn’t have to build every aspect of a model
from scratch. Many elements are common to all models. We have
taken some of these common elements and turned them into Model
Objects that can simply be copied and pasted into your model.
All you have to do is copy, paste and connect what goes into
the object and where the output from the object goes when
it’s done.
Use the free objects already created, build your own corporate
model objects or have a custom model object built by ProcessModel,
Inc.
These Model Objects help you build models in a fraction of
the time, they work correctly right “out of the box”,
and they’re fun.
ARRIVALS |
| |
Arrivals
Weekly |
| |
|
Spreads arrivals over a week according
to a distribution. |
| |
Arrivals
Monthly |
| |
|
Spread arrivals over a one-month period to mimic
end-of-month sales spikes. |
| |
Arrivals
Quarterly |
| |
|
Spread arrivals over a three-month period to mimic
end-of-quarter sales spikes. |
| |
Arrivals
Prior to Scheduled Arrival |
| |
|
Allows for the planned arrival with the addition
of a distribution of how early or late the entity (patient/customer/truck)
arrives. |
| |
Heart
Beat of Arrivals Between 8 and 5 |
| |
|
Do you need to schedule entities to arrive on a set period
but only during certain times of the day? This Model Object
allows you to control the period between arrivals and the
hours of the day that entities will arrive. |
 |
 |
|
ROUTING LOGIC |
| |
Learning
Loop |
| |
|
Recursive entries by the same entity results in
a different probability of success. |
| |
Conditional
Routes |
| |
|
Use attributes on the entity to determine the outcome
of a decision. Many of these decisions can be combined
to route an entity through an entire model. A relatively
simple model can have thousands of parts, each with
unique routing. |
| |
Conditional
Route Example |
| |
|
An example for the model object above. |
| |
Renege
Routes |
| |
|
Normal renege routes work well unless a resource
is being used that is not available 100% of the time.
Use this object when resources are attached to the activity
for which the renege takes place. |
| |
Alternating
Route |
| |
|
Sends entities to the next activity in turn. If
the next activity is busy it looks at the next in turn. |
| |
|
|
ACTIVITY PROCESSING |
| |
Decreasing
Production Time |
| |
|
The more people in line, the shorter the processing
time. |
| |
Setup
Time |
| |
|
A new simplified method for modeling set-up time for many
different entities, with distinct setup times. The construct
is smart enough to recognize that if the same entity arrives
as the previous then no setup is needed. This model object
is easy-to-use and yet powerful and simple. |
| |
Percent
of Time |
| |
|
This model object should be used when you have an
activity where the total time spent at an activity
in not all "processing" time. |
| |
|
|
BATCHING/UNBATCHING |
| |
End
of Day Batching 1 |
| |
|
Used to create “short batches” or to close a batch
even though the specified batch size was not reached.
You may specify any time of the day (or multiple times
during the day) to “take what you have” and move to
the next activity. |
| |
End
of Day Batching 2 |
| |
|
Used to create a batch of the items remaining at
the end of the day, even if the batch size is larger
than the specified batch size. |
| |
Batching
for Multiple Entity Types |
| |
|
Use this object to batch multiple entity types at
a single activity. Each type of entity may have its
own batch size. |
| |
|
|
RESOURCES |
| |
Release
Entity at the End of Shift |
| |
|
This model object gives greater control on the release
of a resource from working on an entity. Used especially
for entities with long processing times (usually multiple
shifts) |
| |
Release
Entity to Next Shift - 2 Shifts |
| |
|
Allows work to be passed from one shift to another
rather than having the same resource complete the work
the following day. |
| |
Release
Entity to Next Shift - 3 Shifts |
| |
|
Same as above but with three shifts that will share
work. |
| |
Changing
Priorities |
| |
|
In many process situations the priority for getting a
resource changes throughout the day. The emphasis may switch
based on time of day or other factors. The Changing Priorities
model object allows you to quickly impellent a method of changing
the work emphasis based on a variety of conditions. |
| |
Multitasking |
| |
|
This model simulates a resource"multitasking"within
a single activity -- the resource works on one entity for
awhile, then switches to another for awhile, and so on.
|
| |
|
|
ASSEMBLY |
| |
Assemble
Different Subcomponents |
| |
|
Gives each parent entity the ability to specify
how many assemblies will be attached. For example, Type
1 requires 1 hard drive while Type 2 requires 2 hard
drives, etc. |
| |
|
|
KANBAN SYSTEMS |
| |
Kanban
Model Object One
Kanban
Model Object Two
Kanban
Model Object Three - NOTE:
You will need to download all three of these before
installing number one. |
| |
|
A building block for Kanban systems. This object
has several parts in the single model. |
| |
Kanban
Squares |
| |
|
A simple Kanban square system. |
| |
|
|
DIGITAL CLOCKS |
| |
Digital
Clock |
| |
|
Provides a simple digital clock to show the hour
and minute of the day along with an AM/PM indicator.
This is used because not everyone can quickly translate 542 hours into the hour of the day during
the simulation. Black face plate with white numerals. |
| |
Digital
Clock and Day - Blue/White |
| |
|
A more detailed digital clock with the hour and
minute of the day and the day of the week. Blue face
with white numerals. |
| |
Digital
Clock and Day - Black/Orange |
| |
|
Same as above with a black face and Orange numerals. |
| |
Digital
Clock and Day - Gray/Black |
| |
|
Same as above with a gray face and black numerals. |
| |
Digital
Clock and Day - White/Black |
| |
|
Same as above with a white face and black numerals. |
| |
|
|
DASHBOARD COMPONENTS |
| |
Dashboard
for WIP - Meter |
| |
|
This Dashboard object allows you to set levels for the
display meter to change. This object is a tremendous asset
during presentations to illustrate system status. |
| |
Dashboard
for WIP - Large Oval |
| |
|
This Dashboard object allows you to set levels for the
display oval to change color. |
| |
Dashboard
for WIP - Rounded Square |
| |
|
This Dashboard object allows you to set levels for the
display rounded square to change color. |
| |
Dashboard
for WIP - Square |
| |
|
This Dashboard object allows you to set levels for the
display square to change color. |
| |
|
|
LOGISTICS |
| |
Five
Docks |
| |
|
Use this Model Object in a situation where you have
five or fewer docks to receive and unload trucks. The
object holds the truck until everything is unloaded,
then allows the next truck to enter. |
| |
Ten
Docks |
| |
|
Same as above, but for ten or fewer docks |
| |
Fifteen
Docks |
| |
|
Same as above, but for fifteen or fewer docks |
| |
|
|
SPECIALTY |
| |
Airport
Bus System |
| |
|
This Model Object consists of three parts: a terminal
layer, a bus storage layer, and a bus stop layer that
can be duplicated as many times as needed. With this
object a detailed bus stop system could be developed
in minutes. |
| |
Airport
Tram |
| |
|
In any situation where you have a transport system
with two trams or buses only two possible stops. |
| |
Hour
and Daily Trigger |
| |
|
Use this model object when an event needs to be
triggered at a specific hour of the day or day of the
week timer is needed. This simple model can be used
to trigger events or the collection of data at certain
times during the week. |
| |
Hold
for Meeting |
| |
|
Holds processing for required approval meetings.
Meetings may take place daily, weekly, monthly, or quarterly. |
| |
Verify
Distribution |
| |
|
Use this model object to verify the return values
you would get from a distribution. This object will
not be pasted into the model but rather be used to check
distribution for validity. |