Key concepts

Runs

A run is a session within the runtime app.

This session can represent a batch, a shift, or any other period of a manufacturing process.

For a given run, Runtime tracks time in three categories: running, down, or idle. Downtime and idle time can be further broken down into reasons, which you define. Each run asks you to record key production metrics: ouput and rejects. Runs take place at locations, which you can use to map your facility.

These additional concepts are detailed below.

Running, down, and idle

At the highest level, Runtime tracks three types of time: Runtime, Downtime, and Idle time.

Running

Runtime (or Running) is considered producitve time. This is time where a process is operating as expected.

If you’re tracking manufacturing, this is time where equipment is running and producing widgets.

Running status is colored green.

Down

Downtime (or Down) is unproductive time that is unplanned. This is time where something has gone wrong in your process and probably requires intervention.

If you’re tracking manufacturing, this could be time where equipment has gone down and needs unscheduled maintenance. Another example could be time where a line has run out of materials and needs more to continue production.

Down status is colored red.

Idle

Idle time (or Idle) is unproductive time that is planned or expected. This is time where a process is paused but nothing has gone wrong.

Common examples of idle time are breaks or team meetings that require pausing production.

Idle status is colored blue.

Not started

You may see another status called Not started. This means that there’s no activity in-progress at that location.

Not started status is colored gray.

Reasons

Reasons allow you to more granularly track the root cause of downtime or idle time.

You can configure a list of reasons, and assign each reason to either down or idle. When you set a status of down or idle, you will be asked to select a reason from your list.

Reasons are optional, and you will not need to select a reason if none are defined.

Batches

Batches allow you to track products throughout their manufacturing lifecycle.

When you start a run, you can choose to assign a batch. You can track that batch across multiple locations and runs.

Each batch is tied to a unique ID that you assign. You can use any product identifier you want as the batch ID: considuer using a batch number, lot code, order number, etc.

Locations

Locations are places where you want to track time. They are the building blocks of how you configure Tendrel to represent your facility.

A location can represent an individual machine, a manufacturing line, a room in your facility, or the facility as a whole. How you set up locations will be determined by how granularly you want to track time.

When you track a run, you will start by selecting the location where work is being done. When you set a status of running, down, or idle, this status is applied to the location you selected when you started the run.

Output and rejects

When you submit a run, you will be asked to provide output and reject count produced during the run.

Output is the count of widgets produced during the run. Reject count is the count of defective widgets produced during the run.

Both fields expect a numeric input and are unit-agnostic. You can enter any number representating productivity or waste in these fields, and they will appear in dashboards.

Override times

When tracking time, you may realize that you’ve forgotten to start or end a block of time. You can adjust the start or end of a run, downtime event, or idle period, These adjustments are referred to as override times.