Praktikum Pemodelan Sistem

Practicum of System Modeling

Module of Practicum
Agenda
Basic Knowledge Advanced Knowledge

Week 1 Week 4
- Pretest - Review and Pretest
- Introduction to Promodel
- Entity and General related
- Fundamental Element of Promodel
operation statement (syntax)
- Basic setting of Promodel
- Simulation - Simulation
Week 2 Week 5
- Review and Pretest - Review and pretest
- Resource and Path Network - Attribute and Variable
- Resource related operation
statement (syntax) - Stat::Fit → Probability Distribution
- Simulation - Background graphic
Week 3 - Simulation
- Review and Pretest
Entity and Resource related
operation statement (syntax)
- Simulation
Week 4
What we are going to learn:

1.Combine
2.Group
3.Order
4.Send
Combine is an Entity-Related Operation Statement

• Accumulates and consolidates a specified

quantity of entities into an entity,
optionally with a different name.
• Unlike the GROUP statement, combined
entities lose their identities and attributes
and cannot be ungrouped later.
• Use COMBINE when several entities need
to be combined, such as when eight spark
plugs are combined in a box.

Note: COMBINE may not be used in combination with

CREATE, GROUP, UNGROUP, LOAD, UNLOAD, SPLIT
AS, or other combine statements in the same process
logic.
Group is an Entity-Related Operation Statement

• Accumulates and temporarily consolidates

a specified quantity of entities into a
single GROUP shell entity.
• The shell entity retains the same
attributes as the first entity that was
grouped into the shell. However, if the
GROUP AS statement is used, the new
shell entity does not retain any attribute
values, even if the same name is used for
the GROUP shell entity as the entities that
have been grouped.

Note: GROUP may not be used in combination

with COMBINE, CREATE, LOAD, UNLOAD, SPLIT AS,
other GROUP statements in the same processing logic,
or with conveyors. An exception to this rule is that an
UNGROUP statement may follow a GROUP statement
in the same process.
 Order - Causes the specified number of entities to be created and
placed into the system at the designated activity.

Components:
• Quantity The number of new entities to be
ordered. This field is evaluated every time the
ORDER statement is encountered, allowing the
number ordered to vary as the simulation
progresses.
• Entity The name of the new entities.
• (Activity) The destination of the new entities.
If no activity is selected, the entities will be
ordered to the current activity.
Send - Sends the specified number of a particular entity type to the
destination.
• The entities to be sent must be waiting with a SEND routing rule.
• The entity that issued the SEND command continues processing whether or not entities
of the type requested are waiting to be sent.
• If no entities are waiting to be sent, a SEND notice is automatically posted so that
entities will be sent when they become available.
• The SEND statement can model a system based on demand, rather than on entity
arrival, (called a pull system). Customer orders cause a SEND to be issued for a main
assembly. Main assembly issues SEND commands for sub-assemblies. The example
model SEND has an excellent example of this technique.
• The SEND statement can also be used as a control device to limit the amount of work-
in-progress (WIP) in certain critical areas. Quantities are only sent to the production
area when the WIP level falls below a certain point.
 Send - Sends the specified number of a particular entity type to the
destination.
Components
<expression>
The number of entities to send to the destination.
Negative values will generate an error message.
<entity name>
The type of entity to send to the destination. You
may substitute ENT() for an entity name.
<destination>
The name of the location to which the entities will
be sent. You may substitute LOC() for the location
name.
<priority>
Multiple SEND requests for the same entity type
are filled according to the longest waiting
request having the highest priority. This
expression should be a number between 0 and
999.