& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Transcript
00:04
Real Time Control, or RTC, allows the state of ancillaries such as pumps, blockages, sluice gates,
00:12
and weirs to be changed according to the state elsewhere in the network.
00:16
Ancillary links that can be controlled via RTC are referred to as regulators.
00:23
For example, the flow in a conduit can be used to determine when a sluice gate should be open or closed.
00:29
In this way, it is possible to actively control flows throughout the system.
00:35
Associated with each regulator is a series of components that determine how the regulator is operated.
00:42
Several simple components can be combined to build up complex instructions.
00:48
The simplest form of RTC uses direct control, where the structure is under the direct control of the regulator.
00:56
For example, a pump can be switched on or off, depending on the level in the upstream chamber.
01:02
Detailed design of control structures can be carried out using indirect controllers to monitor the operation of weirs and gates.
01:11
For example, a node downstream from a sluice gate may be set up to check water levels.
01:18
The current value from the node can be used to decide whether the gate should be raised or lowered.
01:24
When a simulation is run, the operation of the control elements modified by RTC rules is continually checked.
01:33
At each major timestep, the simulation engine works through each of the components in turn, for each regulator.
01:41
The engine checks the ranges, combines the TRUE or FALSE outputs in any logical operators,
01:47
translates the values using the tables, and recalculates any variables.
01:52
The rules are then applied, and the operation of the regulators is modified accordingly.
01:58
The RTC Window Editor is used to view and edit the Real Time Control rules of regulators in the network.
02:06
The left side of the editor allows you to create, select and reorder objects.
02:13
The right side allows you to edit the objects and varies depending on which element of the RTC object has been selected.
02:21
As you add to the RTC, the Description box populates and presents the logic of the defined rules in plain English.
02:29
Reading through this description can help ensure that the RTC operates as you expect.
02:36
You can use the following regulator components in an RTC:
02:40
Range:
02:42
Provides a range for variables measured at a control point, such as flow or depth against which a true or false state is produced.
02:51
For example, if the input value is between the minimum and maximum specified, the range returns a logical output of TRUE;
02:60
otherwise, the result is FALSE.
03:04
Ranges are the fundamental building blocks of any RTC that you construct.
03:09
Logic Operator:
03:11
The output from up to four ranges or logic operators can be combined to give a TRUE or FALSE result.
03:19
This result can be used as the input to either another logic operator, or to a rule.
03:26
Available logic operators are AND, OR, NOT, NOR, and NAND.
03:36
Controller:
03:37
Indirectly controls a regulator to achieve a defined setpoint.
03:42
There are several types of controllers available, such as adaptive pump, incremental, and PID controllers.
03:51
Table:
03:52
Translates measured input values from the control point to new output values.
03:57
This can help you move from linear relationships to non-linear, and vice-versa.
04:03
The input values can be the output from a range, table, or variable.
04:09
Entering table data manually can be quite slow, as it must be done one row at a time.
04:16
Variable:
04:18
Allows you to combine values (from a range, table, logic operator, variable, or constant value) to derive another value.
04:28
All variables are set to zero at the beginning of a simulation.
04:33
Variable values are preserved from timestep to timestep, so you can use them to accumulate statistics.
04:40
Variable elements are processed in the order in which you enter them.
04:45
Rule:
04:46
Controls the setpoint of a regulator.
04:49
The rule type defines the way in which the rule operates on the regulator.
04:54
Rule types are Control, Position, Switch on, and Switch off.
05:00
Regulator Event:
05:02
Provides direct and indirect control of regulator structures.
05:07
Examples include weir crest levels, pump switching, or pump speed.
05:13
In InfoWorks networks, regulator events can be used instead of Real Time Control,
05:19
or to override RTC when directly controlling a regulator.
05:24
These events can also be used to provide output values for an RTC table when indirectly controlling a regulator.
05:32
Using Regulator Events instead of, or in conjunction with, RTC
05:37
can help to avoid the creation of a large number of scenarios or branched networks when editing controls.
05:45
Putting this all together, now look at the RTC Window Editor to see how two examples are constructed.
05:53
The first regulator link, Storm_tank1.1, is a variable sluice gate.
06:00
There is a defined range that monitors whether the elevation of water is above 41.000m.
06:09
The default rule for the sluice is to have a set opening of 0.000m, or to be fully shut.
06:19
When the inlet range becomes true, meaning the water level is below 41.000m at the node, then the sluice opening will be set to 0.150m.
06:33
The second example is similar, but this time, it employs a logic operator, which is reading in the Pump2On range from a global item.
06:42
This means it could be used by another regulator.
06:46
There is a default opening of 0.300m, which will initially close to 0.100m when the depth in the tank is exceeded.
06:57
If the depth in the tank is exceeded and the Pump2On condition is met, then the sluice will further close to 0.050m.
07:07
You can also read through the logic in the Description box.
Video transcript
00:04
Real Time Control, or RTC, allows the state of ancillaries such as pumps, blockages, sluice gates,
00:12
and weirs to be changed according to the state elsewhere in the network.
00:16
Ancillary links that can be controlled via RTC are referred to as regulators.
00:23
For example, the flow in a conduit can be used to determine when a sluice gate should be open or closed.
00:29
In this way, it is possible to actively control flows throughout the system.
00:35
Associated with each regulator is a series of components that determine how the regulator is operated.
00:42
Several simple components can be combined to build up complex instructions.
00:48
The simplest form of RTC uses direct control, where the structure is under the direct control of the regulator.
00:56
For example, a pump can be switched on or off, depending on the level in the upstream chamber.
01:02
Detailed design of control structures can be carried out using indirect controllers to monitor the operation of weirs and gates.
01:11
For example, a node downstream from a sluice gate may be set up to check water levels.
01:18
The current value from the node can be used to decide whether the gate should be raised or lowered.
01:24
When a simulation is run, the operation of the control elements modified by RTC rules is continually checked.
01:33
At each major timestep, the simulation engine works through each of the components in turn, for each regulator.
01:41
The engine checks the ranges, combines the TRUE or FALSE outputs in any logical operators,
01:47
translates the values using the tables, and recalculates any variables.
01:52
The rules are then applied, and the operation of the regulators is modified accordingly.
01:58
The RTC Window Editor is used to view and edit the Real Time Control rules of regulators in the network.
02:06
The left side of the editor allows you to create, select and reorder objects.
02:13
The right side allows you to edit the objects and varies depending on which element of the RTC object has been selected.
02:21
As you add to the RTC, the Description box populates and presents the logic of the defined rules in plain English.
02:29
Reading through this description can help ensure that the RTC operates as you expect.
02:36
You can use the following regulator components in an RTC:
02:40
Range:
02:42
Provides a range for variables measured at a control point, such as flow or depth against which a true or false state is produced.
02:51
For example, if the input value is between the minimum and maximum specified, the range returns a logical output of TRUE;
02:60
otherwise, the result is FALSE.
03:04
Ranges are the fundamental building blocks of any RTC that you construct.
03:09
Logic Operator:
03:11
The output from up to four ranges or logic operators can be combined to give a TRUE or FALSE result.
03:19
This result can be used as the input to either another logic operator, or to a rule.
03:26
Available logic operators are AND, OR, NOT, NOR, and NAND.
03:36
Controller:
03:37
Indirectly controls a regulator to achieve a defined setpoint.
03:42
There are several types of controllers available, such as adaptive pump, incremental, and PID controllers.
03:51
Table:
03:52
Translates measured input values from the control point to new output values.
03:57
This can help you move from linear relationships to non-linear, and vice-versa.
04:03
The input values can be the output from a range, table, or variable.
04:09
Entering table data manually can be quite slow, as it must be done one row at a time.
04:16
Variable:
04:18
Allows you to combine values (from a range, table, logic operator, variable, or constant value) to derive another value.
04:28
All variables are set to zero at the beginning of a simulation.
04:33
Variable values are preserved from timestep to timestep, so you can use them to accumulate statistics.
04:40
Variable elements are processed in the order in which you enter them.
04:45
Rule:
04:46
Controls the setpoint of a regulator.
04:49
The rule type defines the way in which the rule operates on the regulator.
04:54
Rule types are Control, Position, Switch on, and Switch off.
05:00
Regulator Event:
05:02
Provides direct and indirect control of regulator structures.
05:07
Examples include weir crest levels, pump switching, or pump speed.
05:13
In InfoWorks networks, regulator events can be used instead of Real Time Control,
05:19
or to override RTC when directly controlling a regulator.
05:24
These events can also be used to provide output values for an RTC table when indirectly controlling a regulator.
05:32
Using Regulator Events instead of, or in conjunction with, RTC
05:37
can help to avoid the creation of a large number of scenarios or branched networks when editing controls.
05:45
Putting this all together, now look at the RTC Window Editor to see how two examples are constructed.
05:53
The first regulator link, Storm_tank1.1, is a variable sluice gate.
06:00
There is a defined range that monitors whether the elevation of water is above 41.000m.
06:09
The default rule for the sluice is to have a set opening of 0.000m, or to be fully shut.
06:19
When the inlet range becomes true, meaning the water level is below 41.000m at the node, then the sluice opening will be set to 0.150m.
06:33
The second example is similar, but this time, it employs a logic operator, which is reading in the Pump2On range from a global item.
06:42
This means it could be used by another regulator.
06:46
There is a default opening of 0.300m, which will initially close to 0.100m when the depth in the tank is exceeded.
06:57
If the depth in the tank is exceeded and the Pump2On condition is met, then the sluice will further close to 0.050m.
07:07
You can also read through the logic in the Description box.
Real Time Control, or RTC, allows the state of ancillaries such as pumps, blockages, sluice gates, and weirs to be changed according to the state elsewhere in the network. Ancillary links that can be controlled via RTC are referred to as regulators.
For example, the flow in a conduit can be used to determine when a sluice gate should be open or closed. In this way, it is possible to actively control flows throughout the system.
Associated with each regulator is a series of components that determine how the regulator is operated. Several simple components can be combined to build up complex instructions.
The simplest form of RTC uses direct control, where the structure is under the direct control of the regulator. For example, a pump can be switched on or off, depending on the level in the upstream chamber.
Detailed design of control structures can be carried out using indirect controllers to monitor the operation of weirs and gates. For example, a node downstream from a sluice gate may be set up to check water levels. The current value from the node can be used to decide whether the gate should be raised or lowered.
When a simulation is run, the operation of the control elements modified by RTC rules is continually checked. At each major timestep, the simulation engine works through each of the components in turn, for each regulator. The engine checks the ranges, combines the TRUE or FALSE outputs in any logical operators, translates the values using the tables, and recalculates any variables. The rules are then applied, and the operation of the regulators is modified accordingly.
The following regulator components can be used in an RTC:
Putting this all together, look at this RTC Window Editor to see how two examples are constructed.
The first regulator link, Storm_tank1.1, is a variable sluice gate. There is a defined range that monitors whether the elevation of water is above 41.000m. The default rule for the sluice is to have a set opening of 0.000m, or to be fully shut. When the inlet range becomes true, meaning the water level is below 41.000m at the node, then the sluice opening will be set to 0.150m.
The second example is similar, but this time, it employs a logic operator, which is reading in the Pump2On range from a global item. This means it could be used by another regulator. There is a default opening of 0.300m, which will initially close to 0.100m when the depth in the tank is exceeded. If the depth in the tank is exceeded and the Pump2On condition is met, then the sluice will further close to 0.050m.
Read the Description text to see the logic of the defined rules in plain English.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.