Skip to main content

Documentation Portal

How to set up a Generic ODBC data source?

Generic ODBC provider is a Plant Integrations built-in provider, which enables access to historian repositories and databases via ODBC. All parameters used for connecting and retreiving data from the historian repositories, are stored in Plant Integration’s configuration database and can be defined either in ConfigHub or directly via Plant Integrations/database endpoints.

Largely, every configuration requires the following steps:

  1. Establish a connection to the repository through the correct driver and connection string

  2. Configure general parameters

  3. Write and test the queries to extract data from the repositories

Concepts
Overview

Open Database Connectivity (ODBC) is a widely accepted application programming interface (API) for database access. It is based on the Call-Level Interface (CLI) specifications from Open Group and ISO/IEC for database APIs and uses Structured Query Language (SQL) as its database access language.

ODBC is designed for maximum interoperability - that is, the ability of a single application to access different database management systems (DBMSs) with the same source code. Database applications call functions in the ODBC interface, which are implemented in database-specific modules called drivers. The use of drivers isolates applications from database-specific calls in the same way that printer drivers isolate word-processing programs from printer-specific commands. Because drivers are loaded at runtime, a user only has to add a new driver to access a new DBMS; it is not necessary to recompile or relink the application.

Drivers

Drivers are libraries that implement the functions in the ODBC API. Each is specific to a particular DBMS; for example, a driver for Oracle cannot directly access data in an Informix DBMS. Drivers expose the capabilities of the underlying DBMSs; they are not required to implement capabilities not supported by the DBMS. For example, if the underlying DBMS does not support outer joins, then neither should the driver. The only major exception to this is that drivers for DBMSs that do not have stand-alone database engines, such as Xbase, must implement a database engine that at least supports a minimal amount of SQL.

Drivers need to be installed by the customers on the same server as Plant Integrations. If Plant Integrations is installed on the same server as the historian, chances are that the ODBC driver for the historian is already installed and available for Plant Integrations. You can configure user and system-wide ODBC connections using the “ODBC Data Sources” application in Windows.

Connection strings

The ODBC connection string typically has four/five major parts based on keywords: the driver, the server address, the database name, and a user name and password.

An ODBC connection string has the following syntax:

connection-string ::= empty-string[;] | attribute[;] | attribute; connection-string empty-string ::= attribute ::= attribute-keyword=attribute-value | DRIVER=[{]attribute-value[}] attribute-keyword ::= DSN | UID | PWD | driver-defined-attribute-keyword attribute-value ::= character-string driver-defined-attribute-keyword ::= identifier

where 

  • character-string has zero or more characters; 

  • identifier has one or more characters;

  •  attribute-keyword is not case-sensitive;

  •  attribute-value can be case-sensitive; and the value of the DSN keyword does not consist only of blanks.

The Driver keyword names which driver ODBC is used for this connection, the DSN (Data Source Name) keyword names the data source, the UID and PWD keywords specify the user ID and password for the server. 

Examples of Connection strings
SQL Server 2019 

Standard security

Driver={ODBC Driver 17 for SQL Server};Server=myServerAddress;Database=myDataBase;UID=myUsername;PWD=myPassword; 

Connecting to a SQL Server instance

Driver={ODBC Driver 17 for SQL Server};Server=serverName\instanceName;Database=myDataBase;Trusted_Connection=yes; 

Using a non-standard port

Driver={ODBC Driver 17 for SQL Server};Server=myServerName,myPortNumber;Database=myDataBase;UID=myUsername;PWD=myPassword; 

Connect via an IP address

Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword; 

Notice

DBMSSOCN=TCP/IP is how to use TCP/IP instead of Named Pipes. At the end of the Data Source is the port to use. 

1433 is the default port for SQL Server

Attach a database file on connect to a local SQL Server Express instance 

Driver={ODBC Driver 17 for SQL Server};Server=.\SQLExpress;AttachDBFileName=c:\dir\\mydb.mdf;Database=dbName;Trusted_Connection=yes; 

SQLite 3 

Standard

Driver={SQLite3 ODBC Driver};Database=full-path-to-db;UID=myUsername;PWD=myPassword; 

IP21

Standard

DRIVER={AspenTech SQLplus};HOST=myServerName;MAXROWS=1000000

Creating a Generic ODBC data source

To integrate with and ingest data from a database that supports ODBC, a Data Source of provider type “Generic ODBC” can be added and configured in ConfigHub. 

To do so, navigate to Data > Data Sources in the left side menu. Choose the "Add data source" option, which will open a wizard. In the first step, choose a name and select “Generic ODBC” from the Provider dropdown.  This will add two new options to fill in:

  1. Capabilities: tick the box for each capability you intend to activate

  2. Connect via: which Plant Integrations you will use to connect to the database

Selecting the capabilities for the data source with the given checkboxes will define the additional steps in the wizard to complete, grouped in the following sections:

  • Connection details -  Configure all properties related to the connection that will be established with the data source

  • Provider details - Configure properties that are shared by more than one capability

  • Time series details – Configure properties relevant to time series data

  • Asset details - Configure properties relevant to asset data

  • Context details - lists properties relevant to context data

GenODBC_data_source_details.png
Configuring Generic ODBC provider
Provider properties

The Generic ODBC provider uses provider properties to configure every aspect of the provider, this includes queries, credentials and date formats.

Table 10. Connection details

Property

Required

Capability

Remarks

Connection string

yes

Time series

Asset

Event

Connection string used to connect to the underlying data source. When the same keywords are used in the connection string and the driver properties, the values from the driver 

properties are overwritten by the values from the connection string. Same logic applies for credentials : Username (UID) and passwords (PWD) from driver properties are overwritten 

by username and password from connection string and theses are overwritten by the username and password provider properties.

Notice

Advanced: When the Odbc driver does not support the UID or PWD keywords, but use Username and Password instead, you can specify these as dummy keywords in the 

driver properties and those will then be overwritten by the username and password provider properties specified in config hub.

Driver properties

no

Time series

Asset

Event

Driver properties are used as an additional way to add keywords and their values to the connection string. Driver properties are seen as more general properties and will be overwritten 

by values specified in the connection string.

Username

no

Time series

Asset

Event

A convenience field to enter the username used to establish a connection to the database. This information can also be specified in the connection string and driver properties.

Password

no

Time series

Asset

Event

A convenience field to enter the password used to establish a connection to the database. This information can also be specified in the connection string and driver properties.

Warning

Driver properties and Connection string are not encrypted, password however is encrypted.

Parallel connections 

yes

Time series

Each data source has 2 queues: one interactive - plot calls, one non-interactive - index calls, batch calls etc. Parallel connections determine how many connections each queue

 has to the connector. By default there are 2 parallel connections to the connector.



GenODBC_connection_details.png

Table 11. Provider (shared) details 

Property

Required

Capability

Remarks

DateTime format

no

Time series

Event

An optional format your time series data is stored in. The format should be expressed in .NET syntax: 

https://learn.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings

Timezone

no

Time series

Event

An optional timezone your time series data is stored in. Default is UTC.

The list of supported values are defined by the operating system of Plant Integrations. To get this list you can use the following command:

Timezone_PowerShell_ODBC.png

Notice

The second line for each time zone is the identifier that can be used, e.g. “Pacific Standard Time“

Delimiter

no

Asset

Event

Delimiter used to separate a multi string column/ field in the provider. The default is comma (,)

Asset Capability

  • To parse data values of type STRING_ARRAY.



GenODBC_provideer_details.png

Table 12. Time series capability properties

Property

Required

Remarks

Tag list query

yes

A query used by TrendMiner to create tags. A query needs to be provided that will, given your database schema and tables.

Example: 

select id, name, type, description, units from source

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • name 

    • Name of the tag.

    • Mandatory.

  • type 

    • Type of a tag. Without additional mapping, type must be one of the following tag types:

      • ANALOG 

      • DIGITAL 

      • DISCRETE 

      • STRING 

    • Optional, if the column is not in the query, the default type ANALOG is used.

    • Custom types can be returned here but then a type mapping must be added as well.

  • description 

    • Description of a tag.

    • Optional, can be empty or null value.

  • units 

    • Unit of measurement for the tag.

    • Optional, can be empty or null.

Index query

yes

A query used by TrendMiner to ingest time series data for a specific tag. The query is expected to return a ts (timestamp) and a value.

Important

The results should be sorted ascending on timestamp, if not they will be sorted by the provider.

Variables:

  • {ID} 

    • The id as returned by the tag list query.

  • {STARTDATE} 

    • TrendMiner will ingest data per intervals of time. This denotes the start of such an interval.

    • The value is formatted (string) using the format specified in the DateTime format provider property.

  • {ENDDATE} 

    • TrendMiner will ingest data per intervals of time. This demotes the end of such an interval.

    • The value is formatted (string) using the format specified in the DateTime format provider property.

  • {INTERPOLATION} 

    • Interpolation type of a tag, which can be on of two values:

      • LINEAR 

      • STEPPED 

  • {NUMBEROFINTERVALS} 

    • The number of intervals to return. It can be used to optimize a query to return the expected number of points.

  • {INDEXRESOLUTION} 

    • Index resolution in seconds. It can be used to optimize a query to return the expected number of points.

Example:

select ts, value from source where id={ID} and ts>={STARTDATE} and ts<={ENDDATE} order by ts asc

Columns:

  • ts 

    • Timestamp of the value.

    • Passed using the format specified in the DateTime format provider property.

  • value 

    • Value at the specified timestamp.

Internal plotting

no

If this option is selected TrendMiner will use interpolation if needed to plot the tag on the chart on specific time ranges. If this value is not selected and no plot query is provided,

TrendMiner will plot directly from the index.

Plot query

no

A query used by TrendMiner to plot time series data for a specific tag. The query is expected to return a ts (timestamp) and a value.

Important

The results should be sorted ascending on timestamp, if not they will be sorted by the provider.

Variables:

  • {ID} 

    • The id as returned by the tag list query.

  • {STARTDATE} 

    • TrendMiner will ingest data per intervals of time. This denotes the start of such an interval.

    • The value is formatted (string) using the format specified in the DateTime format provider property.

  • {ENDDATE} 

    • TrendMiner will ingest data per intervals of time. This demotes the end of such an interval.

    • The value is formatted (string) using the format specified in the DateTime format provider property.

  • {INTERPOLATION} 

    • Interpolation type of a tag, which can be on of two values:

      • LINEAR 

      • STEPPED 

  • {NUMBEROFINTERVALS} 

    • The number of intervals to return. It can be used to optimize a query to return the expected number of points.

  • {INDEXRESOLUTION} 

    • Index resolution in seconds. It can be used to optimize a query to return the expected number of points.

Example:

select ts, value from source where id={ID} and ts>={STARTDATE} and ts<={ENDDATE} order by ts asc

Columns:

  • ts 

    • Timestamp of the value.

    • Parsed using the format specified in the DateTime format provider property.

  • value 

    • Value at the specified timestamp.

Digital state query

no

If tags of type DIGITAL are returned by the tag list query, TrendMiner will use this query to ask for the stringValue, intValue pairs for a specific tag to match a label with a number.

Variables:

  • {ID} 

    • The id as returned by the tag list query for tags with type DIGITAL.

Example:

select stringValue, intValue from source where id={ID}

Columns:

  • stringValue 

    • Possible value of a digital tag.

  • intValue 

    • A numeric representation of a possible value of a digital tag.

Type mapping

no

If types differ from what TrendMiner uses and one wants to avoid to overcomplicate the query, a type mapping can be entered here. It can contain multiple lines and expect per line the value 

to be representing a custom type followed by a ; and a TrendMiner type. During the execution of the tag list query TrendMiner will then use this mapping to map the custom values returned in 

the query to TrendMiner tag types.

customTypeA;ANALOG customTypeB;DIGITAL customTypeC;DISCRETE customTypeD;STRING

Prefix

no

An optional text can be entered here that will be used to prefix the tag names in TrendMiner. 

Warning

Value cannot be changed.

Tag filter

no

An optional regular expression to be entered. Only tags with names that match this regex will be retained when creating tags (using the tag list query).



GenODBC_time_series_details.png

Table 13. Asset capability properties

Property

Required

Remarks

Root asset query

yes 

This query needs to return details for a specific asset record.

Example:

select id, type, name, parentId, description, dataType, dataValue from source where parentId is NULL

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • type 

    • TrendMiner can handle asset of type ASSET or ATTRIBUTE. This column must be on of these two values.

    • Mandatory.

  • name 

    • Name of the asset.

    • Mandatory.

  • parentId 

    • The identifier of the parent, which should be null in case of a root asset.

  • description 

    • Description of the asset.

    • Optional, can be empty or null value.

  • data type 

    • TrendMiner can ingest four different types of data in case the asset is of type ATTRIBUTE. This column will impact on how the data value column will be interpreted/read:

      • STRING data value is interpreted as text

      • STRING_ARRAY comma delimited string

      • NUMERIC

      • DATA_REFERENCE

    • Optional, can be empty or null or not a specified as column.

  • data value 

    • This column will either be interpreted as text (STRING), a collection of text (STRING_ARRAY), a number (NUMERIC) , or a reference to a Tag (DATA_REFERENCE).

    • Optional, can be empty or null or not a specified as column.

    • Supports following underlying data types:

      • STRING

      • DOUBLE

      • FLOAT

      • INT

      • LONG

Asset query

yes

This query is responsible for returning all top level elements from the asset tree structure.

Variables:

  • {IDS} 

    • A list of identifiers of assets for which the query must return data, should be used in an “IN-clause“ since, it will be replaced by any (as specified) number of parameters in the query:

      select ... where id in (?,?,?,?)

Example:

select id, type, name, parentId, description, dataType, dataValue from source where id in ({IDS})

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • type 

    • TrendMiner can handle asset of type ASSET or ATTRIBUTE. This column must be on of these two values.

    • Mandatory.

  • name 

    • Name of the asset.

    • Mandatory.

  • parentId 

    • The identifier of the parent, which should be null in case of a root asset.

  • description 

    • Description of the asset.

    • Optional, can be empty or null value.

  • data type 

    • TrendMiner can ingest four different types of data in case the asset is of type ATTRIBUTE. This column will impact on how the data value column will be interpreted/read:

      • STRING data value is interpreted as text

      • STRING_ARRAY comma delimited string

      • NUMERIC

      • DATA_REFERENCE

    • Optional, can be empty or null or not a specified as column.

  • data value 

    • This column will either be interpreted as text (STRING), a collection of text (STRING_ARRAY), a number (NUMERIC) , or a reference to a Tag (DATA_REFERENCE).

    • Optional, can be empty or null or not a specified as column.

    • Supports following underlying data types:

      • STRING

      • DOUBLE

      • FLOAT

      • INT

      • LONG

Asset children query

yes 

This query needs to return the ids of the direct descendants of this asset.

Variables:

  • {ID} 

    • The id of the asset for which the direct descendants need to be queried.

Example:

select id from source where parentId={ID}

Columns:

  • id 

    • The identifier for each direct descendant asset, like a primary key in a database table.

    • Mandatory.



GenODBC_asset_details.png

Table 14. Event capability properties

Property

Required

Remarks

Events query

yes

This query is responsible for returning events from the source database. Context items will be generated based on these events.

Variables:

  • {CURSOR} 

    • A unique and sorted value that is used in the cursor based pagination implementation.

  • {LIMIT} 

    • The maximum number of records the query should return.

  • {AFTER} 

    • The date after which the events must be returned.

    • String formated using DateTime format provider property.

  • {AFTER:ToUnixTimeMilliseconds} 

    • The date after which the events must be returned, in epoch time (milliseconds).

    • Numeric (Long).

  • {AFTER:ToUnixTimeSeconds} 

    • The date after which the events must be returned, in epoch time (seconds).

    • Numeric (Long).

  • {BEFORE} 

    • The date before which the events must be returned.

  • {BEFORE:ToUnixTimeMilliseconds} 

    • The date before which the events must be returned, in epoch time (milliseconds).

    • Numeric (Long).

  • {BEFORE:ToUnixTimeSeconds} 

    • The date before which the events must be returned, in epoch time (seconds).

Example:

select id, name, type, occurred_at, modified_at, components, state, description, keywords, grouping_key from Event where occurred_at > {AFTER} and occurred_at < {BEFORE} and id > coalesce({CURSOR}, 0) limit {LIMIT}

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • name 

    • Name of the event.

    • Mandatory.

  • type 

    • The identifier of the type of the event (as specified in the type/types query).

    • Mandatory.

  • occurred_at 

    • The timestamp when the event occured.

    • Parsed using the fomat specified in the DateTime format provider property.

    • Mandatory

  • modified_at 

    • The timestamp when the event was modified.

    • Parsed using the fomat specified in the DateTime format provider property.

    • Mandatory

  • components 

    • A list of component (asset) identifiers separated by the Delimiter (',' by default).

    • Mandatory, can be empty or null value.

  • state 

    • The state for this event record

    • Mandatory, can be empty or null value.

  • description 

    • Description of the event.

    • Mandatory, can be empty or null value.

  • keywords 

    • A list of keywords associated with the events, separated by the Delimiter (',' by default)

    • Mandatory, can be empty or null value.

  • grouping_key 

    • The identifier of the object which raised the event, all events of the same object should have the same grouping_key.

    • Optional

Event by id query

yes

This query is responsible for returning a specific event from the source database.

Variables:

  • {ID} 

    • The id of the event which need to be queried.

Example:

select id, name, type, occurred_at, modified_at, components, state, description, keywords, grouping_key from Event where Id = {ID}

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • name 

    • Name of the event.

    • Mandatory.

  • type 

    • The identifier of the type of the event (as specified in the type/types query).

    • Mandatory.

  • occurred_at 

    • The timestamp when the event occurred.

    • Parsed using the format specified in the DateTime format provider property.

    • Mandatory

  • modified_at 

    • The timestamp when the event was modified.

    • Parsed using the fomat specified in the DateTime format provider property.

    • Mandatory

  • components 

    • A list of component (asset) identifiers separated by the Delimiter (',' by default).

    • Mandatory, can be empty or null value.

  • state 

    • The state for this event record.

    • Mandatory, can be empty or null value.

  • description 

    • Description of the event.

    • Mandatory, can be empty or null value.

  • keywords 

    • A list of keywords associated with the events, separated by the Delimiter (',' by default).

    • Mandatory, can be empty or null value.

  • grouping_key 

    • The identifier of the object which raised the event, all events of the same object should have the same grouping_key.

    • Optional

Types query

yes

This query is responsible for returning a list of possible event types from the source database.

Variables:

  • {CURSOR} 

    • A unique and sorted value that is used in the cursor based pagination implementation.

  • {LIMIT} 

    • The maximum number of records the query should return.

Example:

select id, name, color, startstate, endstate, states, fields from eventtype where Id > coalesce({CURSOR}, 0) limit {LIMIT}

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • name 

    • Name of the type.

    • Mandatory.

  • color 

    • A color for this event type record. It will be used in the Gantt chart view of ContextHub.

    • Mandatory, can be empty or null value.

  • startstate 

    • The name of the start start.

    • Optional, can be empty or null value.

  • endstate 

    • The name of the end state.

  • states 

    • A list of the possible state, separated by the Delimiter (',' by default).

    • The first item in the list must be the start state.

    • The last item in the list must be the end state.

  • fields 

    • A list of custom field identifiers for this event, separated by the Delimiter (',' by default).

    • Optional, can be empty or null value.

Type by id query

yes

This query is responsible for returning an event type from the source database.

Variables:

  • {ID} 

    • The id of the event type which need to be queried.

Examples:

select id, name, color, startstate, endstate, states, fields from Type where id = {ID}

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • name 

    • Name of the type.

    • Mandatory.

  • color 

    • A color for this event type record. It will be used in the Gantt chart view of ContextHub.

    • Optional, can be empty or null value.

  • startstate 

    • The name of the start start.

    • Optional, can be empty or null value.

  • endstate 

    • The name of the end state.

  • states 

    • A list of the possible state, separated by the Delimiter (',' by default).

    • The first item in the list must be the start state.

    • The last item in the list must be the end state.

  • fields 

    • A list of custom field identifiers for this event, separated by the Delimiter (',' by default).

    • Optional, can be empty or null value.

Fields query

yes

This query is responsible for returning a list of possible custom fields from the source database.

Variables:

  • {CURSOR} 

    • A unique and sorted value that is used in the cursor based pagination implementation.

  • {LIMIT} 

    • The maximum number of records the query should return.

Example:

select id, name, type, placeholder, options from Field where Id > coalesce({CURSOR}, 0) limit {LIMIT}

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • name 

    • Name of the type.

    • Mandatory.

  • type 

    • The type of the field, possible values:

      • STRING

      • NUMERIC

      • ENUMERATION

    • Mandatory.

  • placeholder 

    • A placeholder will be displayed in ContextHub’s event creation form.

    • Optional, can be empty or null value.

  • options 

    • A list of possible values separated by the Delimiter (',' by default).

    • If type is ENUMERATION this value is required.

Field by id query

yes

This query is responsible for returning a custom field from the source database.

Variables:

  • {ID} 

    • The id of the field which need to be queried.

Example:

select id, name, type, placeholder, options from Field where Id = {ID}

Columns:

  • id 

    • A unique identifier for each row returned by the query, like a primary key in a database table.

    • Mandatory.

  • name 

    • Name of the type.

    • Mandatory.

  • type 

    • The type of the field, possible values:

      • STRING

      • NUMERIC

      • ENUMERATION

    • Mandatory.

  • placeholder 

    • A placeholder will be displayed in ContextHub’s event creation form.

    • Optional, can be empty or null value.

  • options 

    • A list of possible values separated by the Delimiter (',' by default).

    • Mandatory if type is ENUMERATION.

Event fields query

yes

This query is responsible for returning custom field values for specific event.

Variables:

  • {ID} 

    • The id of the event for which the fields need to be queried.

Example:

select fieldId, value from source where eventId = {ID}

Columns:

  • fieldId 

    • The unique identifier of custom field definition (provided in the Fields query).

    • Mandatory.

  • value 

    • The value of the field.

    • Mandatory.



GenODBC_event_details.png
Example queries (Sqlite)

Below we provide some example queries that can be used in the Generic ODBC provider for the sqlite odbc drivers.

TIME SERIES CAPABILITY
Tag list query
select id, name, type, description, units from source
Index query
select ts, value from source where id={ID} and ts >= {STARTDATE} and ts <= {ENDDATE} order by ts asc
Plot query
select ts, value from source where id={ID} and ts >= {STARTDATE} and ts <= {ENDDATE} order by ts ascselect ts, value from source where id={ID} and ts>={STARTDATE} and ts<={ENDDATE} order  by ts asc
Digital state query
select stringValue, intValue from source where id={ID}
ASSET CAPABILITY
Root asset query
select id, type, name, parentId, description, dataType, dataValue from source where parentId is NULL
Asset query
select id, type, name, parentId, description, dataType, dataValue from source where id in ({IDS})
Asset children query
select id from source where parentId={ID}
EVENT CAPABILITY
Events query
select id, name, type, occurred_at, modified_at, components, state, description, keywords, grouping_key from Event where occurred_at > {AFTER} and occurred_at < {BEFORE} and id > coalesce({CURSOR}, 0) limit {LIMIT}
Event by id query
select id, name, type, occurred_at, modified_at, components, state, description, keywords, grouping_key from Event where Id = {ID}
Types query
select id, name, color, startstate, endstate, states, fields from eventtype where Id > coalesce({CURSOR}, 0) limit {LIMIT}
Type by id query
select id, name, color, startstate, endstate, states, fields from Type where id = {ID}
Fields query
select id, name, type, placeholder, options from Field where Id > coalesce({CURSOR}, 0) limit {LIMIT}
Field by id query
select id, name, type, placeholder, options from Field where Id = {ID}
Event fields query
select fieldId, value from source where eventId = {ID}

In this section: