Use Resources as shared assets in a process flow

Use Resources as shared assets within your process flow.


Tutorial resources

These downloadable resources will be used to complete this tutorial:


00:03

In FlexSim, a shared asset is an asset that can be utilized by multiple entities or processes within your model.

00:11

Shared assets help you manage dependencies within your process flow

00:15

and allow you to set specific criteria for how the shared asset can be used.

00:20

There are four main types of shared assets, one of which is Resources.

00:24

A Resource is an asset with a limited supply that can be acquired by a token and then released.

00:30

This is useful, for instance, if you need to ensure that a Resource completes a task or series of tasks before being acquired by another token.

00:40

Examples of Resources include machines, workers or operators, vehicles, or specialized tools.

00:48

Here, a model and a ProcessFlow have been set up to illustrate how a Resource is used.

00:54

The process shown must be completed in a specific order.

00:57

The operator takes the item from the queue to Processor1, then Processor2, then Processor3, and finally, to the sink.

01:09

However, the operator cannot be interrupted when a new item enters the queue.

01:13

To avoid interruption, the operator is set up as a shared Resource.

01:18

In the ProcessFlow, you can see that each token represents an item entering the model.

01:24

Click the Resource activity to view its properties.

01:28

Here, the Reference is set to Operator1, with a Count of 1.

01:33

This means that the operator can only handle one item at a time.

01:37

Back in the ProcessFlow, you can see that new items enter the queue and wait to acquire the Operator1 Resource.

01:44

Once a token acquires the Resource, it completes the entire task sequence shown.

01:49

The Resource is then released for the next token.

01:53

In the Resource Quick Properties, note that you can also define the order in which awaiting tokens will acquire the Resource

01:59

by using a Default Query or Queue Strategy.

02:04

Now you can use a Resource as a shared asset in your model

02:07

to control what happens when the asset has a limited supply or needs to be accessed by multiple entities or processes.

Video transcript

00:03

In FlexSim, a shared asset is an asset that can be utilized by multiple entities or processes within your model.

00:11

Shared assets help you manage dependencies within your process flow

00:15

and allow you to set specific criteria for how the shared asset can be used.

00:20

There are four main types of shared assets, one of which is Resources.

00:24

A Resource is an asset with a limited supply that can be acquired by a token and then released.

00:30

This is useful, for instance, if you need to ensure that a Resource completes a task or series of tasks before being acquired by another token.

00:40

Examples of Resources include machines, workers or operators, vehicles, or specialized tools.

00:48

Here, a model and a ProcessFlow have been set up to illustrate how a Resource is used.

00:54

The process shown must be completed in a specific order.

00:57

The operator takes the item from the queue to Processor1, then Processor2, then Processor3, and finally, to the sink.

01:09

However, the operator cannot be interrupted when a new item enters the queue.

01:13

To avoid interruption, the operator is set up as a shared Resource.

01:18

In the ProcessFlow, you can see that each token represents an item entering the model.

01:24

Click the Resource activity to view its properties.

01:28

Here, the Reference is set to Operator1, with a Count of 1.

01:33

This means that the operator can only handle one item at a time.

01:37

Back in the ProcessFlow, you can see that new items enter the queue and wait to acquire the Operator1 Resource.

01:44

Once a token acquires the Resource, it completes the entire task sequence shown.

01:49

The Resource is then released for the next token.

01:53

In the Resource Quick Properties, note that you can also define the order in which awaiting tokens will acquire the Resource

01:59

by using a Default Query or Queue Strategy.

02:04

Now you can use a Resource as a shared asset in your model

02:07

to control what happens when the asset has a limited supply or needs to be accessed by multiple entities or processes.

Was this information helpful?