Setup registration of stop when no production, only start after an amount of production has happened

Introduction

  • This guide describes how to setup the registration of stop, when there is no production and have the stop only end if an a certain amount of production has happened within a certain period. This is used when one doesn't have one or more signals describing the state of the unit. In this case one can approximate the state based on production signals.

Setup

Go to the Configuration->Data source page:

Select the unit you wish to setup the registration for(The units here are examples and are different from yours):

Click the Add button:

Select Stop when no production, X Count before start:

Click Save, to add the event server:

Configuration of Stop when no production, X Count before start

  • Name: The name of the event server, that is collecting the data.
  • Small stop time: This is how long a small stop can last in seconds. A stop is consisted a small stop as long as it hasn't lasted longer than this period.
  • Small Stop Reason: This is the stop reason that is used with small stops.
  • DIAP Tags: The DIAP tags is where the production counts are collected from. The structure of the name is  [DIAP]-[PLC]-[Tag]
  • Stop reason: This is the stop reason that is used, when the stop has lasted longer than Small stop time.
  • Inactive time: This is how much time has to pass in seconds after the last production activity from the DIAP Tags, for considering the production stopped.
  • Initial stop time: This is how long the stop initially is when a stop is generated.
  • Min Production count before stop ends: This is how much the production count must register, before the stop ends.
  • Time limit within the production count must be: This is the period in seconds, that the production count must have happened within, for the stop to end.

DIAP tag data type

  • Type: Double

The expected data type is decimal numbers like : 0.0, 0.1,1.0, 1.2

Example - Initial stop time:

A unit has had its last production activity 40 seconds ago, the Inactive time is set to 30 seconds and the initial stop is set to 10 seconds. This means that the production is considered to be stopped for seconds: 

 

Stops ends on the date time of the first production with the Time limit

When the condition of Min Production count before stop ends and Time limit within the production count must be have been meet, then the stop will end on the first production's date time of the productions that was within the time limit. (See Example - Time limit within the production count must be:)

Example - Time limit within the production count must be:

Min Production count before stop ends and Time limit within the production count must be is used to specify how much production must have happened and how fast it should have happened.

Say that you set Min Production count before stop ends to 3 and Time limit within the production count must be to 10 seconds, this will mean, that the stop will only end if there has been a production of 3 or more and the first and last production was within 10 seconds of each other.

 

 

Example - Configuration of Stop when no production, X Count before start

Select a name for the event server, that is collecting the data. Here we called it "production_activity count 3 within 10 sec before start":

Set how long a small may last in seconds. Stops that last to this period and not longer, are consisted small stops. Here we sat it to 30 seconds:

Select a small stop reason, when a small stop is created, it uses this stop reason. Here we used "Small stop":

Select the DIAP tags, where the data comes from. Here we selected "DIAP-00237 - Standalone sensors - Inductive sensor 1" and "DIAP-00200 - Standalone sensors - Inductive sensor 1":

(You can type in this box to quicker search for the tag):

Select the stop reason, that will be used, when the stop has lasted longer than Small stop time. Here we selected "Operator stop":

Select the stop reason, that will be used, when the stop has lasted longer than Small stop time. Here we selected "Operator stop":

Set how much time in seconds since the last production activity, for the production to be considered stopped. Here we sat it to 30 seconds:

Set how long the stop start to be in seconds, when the production is stopped:

 When you are done, the configuration should look something like this(But with your values):

Click Save to save the configuration:

Now you have a configuration for checking production activity on one or more DIAP tags to approximate the state.

Start collecting data

When you have made your configurations in the Data source, then you need to start the event server for the configuration, so the data get collected.

Go to the Configuration -> Data source status page:

Select your unit:

Click the switch for the event server with the configuration:

Then the light turns green and the Last run timestamp is updated, when your event server has run your configuration for the first time:

That it. Now your configuration are done and you are collecting data.