Timers

We can manage time within a simulation using timers.

Block

We can use a block to close off the flow of values for a certain amount of time. For example:

=Block(90)

This event will block the passage of any values it receives until 90 days elapses. After that, any values received will be passed along.

The timer (in this case measuring 90 days) begins the first time the event triggers.

We can think of a block as a closed valve that opens after a set number of days.

You may also pass a second (optional) argument to Block like so:

=Block(3, 'months')

This second argument can be: months, weeks, days, or years.

We can use a wait event to insert a delay measured in days, like so:

=Wait(7)

Where 7 is the number of days that should pass before the event executes.

Any value received by a wait event is passed downstream unchanged.

A wait is useful to represent a trial period, pipeline stage, or delay in receivables, for example.

You may also pass a second (optional) argument to Wait like so:

=Wait(6, 'months')

This second argument can be: months, weeks, days, or years.

📘
What's the value?
The value of a wait is measured by the sum of its flow in a given period. A wait does not have a balance.