Location: A location is a physical place where something is processed or stored.

For example: a line, a cashier, a raw materials warehouse (up to 30).

Entities: An entity is what is processed or stored within the location.

For example: in a queue, the customers are the entities.

Path networks: it is used to paint the route where the entities or the
resources.

Resources: Resources are used to transport entities or to process them within the
location.

e.g. foreman; operator, a truck

Process: the process is where the route through which the entities pass is defined.

Arrivals: in the arrivals is where everything that enters the model is defined.

Shift (work shift): I define the work shift to locations or resources

Attributes: attributes are used to differentiate entities of the same type.

Example:

Global variables: they are used to validate a model. In simulation, they are known as variables of
state. A state variable is one such that if I take a picture of the model, everything that...
countable is a state variable.
Endogenous and exogenous variables.

I cannot change the processing times.

Arrays: arrays are matrices to store information.

Macros: These are the macros of Excel

Subroutines: subroutines are fragments of code that are executed when the user does so.
require

More elements: (Arrival cycles): The arrival cycles are used to model demand.
depending on the time of day.

That table of functions is used to create functions.

customized.

(user distributions): These are what we call the empirical ones.

(External files): it is used to send information from promodel to a file

Plan or to import information from a file to
promodel.
 (Streams): it is the random number generator you have
promodel.

General information: this is where we give titles to models and define units of time.
distance and where we can place the statement of the model.

Cost: this is where I give a cost per hour or per use for the locations or resources.
Background graphics: it is to embellish the model, to make it look nice in another way.

Simulation

Run: Run the model

Save and run: save and run.

Options: this is where we define the simulation time, whether it runs on a calendar, where
we enable or disable the animation among other things.

Model parameters: it is used to parameterize the model

Scenarios: I keep changing the parameters and changing the scenarios:

SimRunner: optimize the model.

Outputs

Tools.

Search expression: search and replace.

Graphic editor: This is where I import the images.

Stat:fit is a statistical package that has a model framework.

3D model: for the latest versions.

Options: it is basically for configuring the saving options.

Customize: to create custom menus.

Window -> is useless for anything

Help -> users usually do not read the help.

We are going to create a new model

Build->general information->Model notes(statement of what we are going to develop)

We always go for build

The band is the tail, double click and we change it to cake.

1. Locations
2. The third column is super important (capacity)

Capacity: it is the number of entities that the location can process simultaneously.

number of identically identical locations that the system has

DTs: Dead times (it helps me to schedule breaks)

Clock: clock stop (A clock stop is one that occurs periodically at the
same time). E.g.: breakfast.

stops per entry (a stop per entry is one that occurs each time the
location has processed a certain number of entities). For example: each time the machine processes
10,000 pieces then we carry out maintenance (a stop is made)

Usage stop: A usage stop is one that occurs whenever the location has
adjusted certain effective operation time

A setup stop is one that occurs when there is a change of entity in the
location. Example: I am organizing and piece and I need to process piece two, so I prepare
the machine.

Called: it is not documented in the help

Stats -> series of tempo (by default not touched)

By default it works FIFO

Notes: this is for you to document the model

Graphics

New: it means that if this is selected, everything I place in the layout will be new.

00(Counter) location counter: it is used to know how many entities are being processed.
currently inside the location. NOTE: DOES NOT ACCUMULATE

Gauge (Level Indicator): used to model tanks

Conv/Que (conveyor belt): by default, a conveyor belt is always created.

If we are going to work with queues, we need to change the status.

Label: It is used to name the locations in the layout.

Status: It serves to visually control the simulation in the following way: if the
the blue light means the location is empty or there is leisure, if the light is green it means that the
Location is working or in operation, if the light is magenta it is because there is a blockage, if the light
this red light is because there is a stop for the clock, for entry or for use, if the light is red
turquoise blue is because there is a stop for setup, if the light is white it is because it is a
location of multiple capacity.

Entity indicator (Entty spot): it is used to see the entity within the location when executing the
model.

Region (Fictional location): is also known as temporary storage.

WHEN I PLACE THE METER, STATUS LIGHT, AND LABEL, I HAVE TO REMOVE THE
CHHULO A NEW, if I don't take off the chulo it's going to be a new location

Build entities
Speed(): the speed of the entities must always be zero
Arrivals
Inf(inity)
USER DISTRIBUTIONS ARE ALWAYS CUMULATIVE
Frequency, right click
I ALWAYS HAVE TO SPECIFY THE TIME UNIT IN THE FREQUENCY
ARRIVALS -> Arrivals() min
Build -> process and routing
Process->routing
Enter in process and the output disappears

Click the hammer

Wait, button me, user distribution

Option simulation, time only, runtime

At start: pause
are dead times, are the stops
% percentage of blocking -> in a simulation model the locations cannot have
locks. If there is a lock, the model is bad.
Failed arrivals -> when the entity wants to enter but cannot.
Entity activity -> all statistics appear but of the identity
Exits 1502, they remained in the system, 1 on the server, 359 in the queue.

Average time in the system -> 561 min

Move logic -> time between locations

Entities will always have locks.

States of the entity

VETELL: 3.2
VETServ: 4

Validation of the model for the next class

STEPS TO VALIDATE A MODEL

1. Create the global variable (I need to count everything that goes into the model)
Build->variables(global)->double click to change color
total arrivals
2. Increment the global variable
Build->process->operation(click on the operation tab)->click on the hammer(standing)
INC)->identify button (we select the created global variable)->increment it
global variable
3. Create the random number generator
Build->more elements->stream->stream#(name we are going to give to stream and
it must be a number)->seed is an integer between 0 and 99)->reset(yes)
4. Associate the variable with the distribution
Build->arrivals->frequency Arrivals(1) min
 5. Validate the model (run the model at least 20 times) changing the seed each time.
run 30 times

6. Find the mean and the standard deviation of the total arrivals

To find the deviations in Excel =STDEV, the mean =AVERAGE

7. Find the limits
8. Calculate the expected value of the distribution
9. Conclusion. (in simulation it is binary, it is good or it is bad)

It's good if the expected value is the expected value, if not we start to have
problems. In conclusion, the model is bad.
Conclusion the model is good

Path networks: they serve to move the entities or for the resources to
move -> default type (passing allows one to get ahead of another)
T/S -> time (tme)
Paths
Interfaces

An arrival cycle always lasts 24 hours, that is to say, we have the time column in hours.
that you number from 1 to 24

The frequency of an arrival cycle is 24 hours (frequency)

The normar (right-click frequency) -> distribution functions

When it comes to networks, it's move on (in move logic)

The norm is that there is no operation in the queues.

Whenever they work with arrival cycles, the simulation must be run under a schedule.
Simulation options -> calendar date
The model needs to be run for a long time, that's why we run it for a month.
Queue 4 8638 and server 4

Cola 4 average contents 0.4

Cola 4 1 person vg count

Server 4 1 current contents

Resources
Operator, the operator's house is n1
Resources should always be told to return home if they are empty.
If the network speed and distance are changed, the option will be modified.

Otherwise no

Move with to move with resources

Time is used when people model static resources.
In the end, we give thenfree to release the resource.

O
Assembly in Promodel is a join
The main piece is the one that contains the secondary one.

Calendar date I know when I have arrival cycles

So that the worker can operate at all the stations.

So that the operator and the forklift go together
Priority

Priorities are assigned with an integer number between one and 999.
The higher the number, the higher the priority.

MOVE WITH Operator,1 THEN FREE priority 1