Effective point modeling is crucial for integrating device data with our Ontology, enabling reliable analysis and system functionality. The enhanced Point Modeling feature simplifies this process by improving visibility, reducing manual effort, and ensuring data consistency. 

The Point Modeling feature is available from the Devices Batch Update page. Follow these steps to access it:

1. Select the devices for which you want to template points.

2. Click Apply Template (Points)

3. You will see two options:

• Point Modeling

• Apply Template (Points)

4. Click Point Modeling to proceed.

Point Groups 

 When multiple devices are selected, navigating to Point Modeling will display points 

from all devices, grouped by similarities. This helps speed up the process of mapping points to our Ontology.

Note: If the devices are not yet templated, the first step is to choose the desired Canonical Type from the top-right corner of the page. If this step is skipped, the page will remain blank.

The table below will appear once you select a Canonical Type (or it will be automatically selected if any of the selected devices are already templated).

Here is how this table will look once some or all the points are mapped to our Ontology:

How Points Are Grouped
Points are grouped to allow for batch templating. The grouping is based on the following criteria:

• Kind

• Name

• Writability

• Unit (for Number points)

• Enums (for Boolean/String points)

For example, if there is a point named "AirFlow" that is part of the 30 devices you previously selected, it will appear as a point group containing 30 points.

Point Groups Overview

In the Point Groups table, several columns provide key information to help you manage and template points efficiently. Here's a breakdown of the visible columns and what they represent:

1. Point Kind

Each point group is identified by a circle icon next to its group name, indicating the point kind:

• N (blue): Number

• B (green): Boolean

• S (red): String or Enum

2. Group Name

This column displays the name of all points within the group.

3. Point Values/Enums

• For Number Points: The minimum and maximum values, along with the unit of measurement, are shown. This helps identify approximate point values, which can be useful during templating and spotting any out-of-range points.

• For Boolean/String Points: The enums for all points within the group are displayed.

4. Writability

If the points within the group are writable, a "Writable" tag will be displayed next to the group name.

5. Points

This column shows the total count of points within the group.

6. Templated

Displays the count of points that have a field assigned, indicating which points are already templated.

7. Field

For templated points, the field name is displayed along with its corresponding unit (for number points) or enums (for Boolean/String points).

8. Issue Indicators

• Duplicate Points: An icon appears if there are two or more points within a device that share the same name.

• Enum Mapping Statuses:

• Missing Enums: Indicates that Boolean/String points are missing enum values.

• Not Mapped: Enum values are not mapped to the required Ontology fields. For compatibility with FDD and FTT, Enum values must be mapped correctly.

• Partially Mapped: Some Enum values are mapped, but not all.

• Mapped: All Enum values are correctly mapped.

Group Expansion

To view the individual points within a group, click the expand icon on the right side of the row. This will display the following details for each point:

• Point Name: The name of the point.

• Point Kind: Specifies if the point is a Number, Boolean, or String/Enum.

• Writability: Indicates if the point is writable.

• Point Value and Unit: Displays the value and unit for number points.

• Enums: Shows enums for Boolean/String points.

• Field: The field assigned to the point.

• Device: The device to which the point belongs.

To enter multi-selection mode, click the Multi Select button at the top right. This will display checkboxes on the rows, allowing you to select multiple point groups. Once selected, you can:

Search, Filters, and Sorting

The following functionalities are available on the Point Groups table:

Search

The search function works in "Contains" mode, allowing you to search by point group name.

Filters

You can filter point groups based on the following criteria:

• Point Kind:

• Number

• String

• Boolean

• Writability:

• Writable

• Non-writable

• Unit:

• Units of the points

• Enum Status:

• Missing Enums

• Mapped

• Not Mapped

Sort

By default, point groups are sorted alphabetically. You can also sort by:

• Point Count: The number of points within a group.

• Template Count: The number of templated points within a group.

To access the filters, click the Filters button at the top right.

Point Groups and Point Options

When you hover over a point group, action icons will appear on the right side, allowing you to:

• Delete the Group – Permanently remove the group and all its associated points from the database.

• Clear Field – Unassigns the current field from the group without deleting any points.

• Change Field – Opens the right-side panel, where you can assign a different field to the group

When a point group is expanded, hovering over an individual point reveals several options:

• Delete Point – Removes the point from the database permanently.

• Clear Field – Unassigns the field from the point without deleting it.

• Edit Field – Allows you to modify the assigned field.

• View Path – Hovering near the point name displays an icon; hovering over this icon reveals the point’s path within the data source (folder structure).

If a point group contains points that are not yet templated, a blue refresh icon will appear. Clicking this icon will apply the assigned field to all untemplated points within the group.

Remove Ontology or Remove Devices

In the top-right corner, under the three dots icon, you’ll find two additional options:

• Remove Ontology: Clears all related Ontology mappings from the selected devices, allowing you to reset and start the templating process from scratch.
  
  

• Remove Devices: Remove the devices you previously selected in the Devices Batch Update from the modeling process.

Mapping Points to Ontology

To map points to our Ontology, click on a row, and the compatible Ontology fields will appear on the right side. The fields will be displayed as a raw list and are:

• Filtered by the selected point kind

• Filtered by unit category for number points

• Sorted by most used (based on historical usage from the KODEs database)

To map a point group to Ontology, simply hover over the desired field and click the Apply button.

Note: Fields are sorted by most used to ensure that the most relevant field is at the top of the list.

Search, Filters, Sorting, and Grouping

The fields list offers the following functionalities, accessible via the three dots icon:

Search

• Works in "Contains" mode.

• Supports multi-word searches (e.g., searching "dis air set" will find discharge_air_flow_setpoint).

Filters

• Filter fields by:

• Field Kind

• Unit Category

Sort

• Sort fields by:

• Most Used

• Alphabetically

Grouping

• Group fields by Ontology Groups or leave them Ungrouped.

Editing the Field

You can modify the properties of an Ontology field, including:

• Display Name: Customize how the field name appears.

• Unit: Adjust the unit of measurement.

• Precision: Defines how much a value must change for KODE to log it in the database during data collection.

• Default on Graph: Determines whether the point will be trended by default in Device Details.

‘Multi’ Fields

In cases where multiple points within the same device should share the same field—such as Cooling or Heating stages—our Ontology allows variations by adding a suffix or prefix.

Fields that support this multi-functionality are marked with a chevron on the right side.

To add variations, you should click on it and the field will get expanded to show if there are any current variations and allow you to add more by clicking the ‘+’ icon.

Then, you can hover over the variations and map the variation on the point. The field will still be the same but on the display name, you will see a number to indicate the suffix or prefix.

Enum Mapping

For non-numeric sensor values, Ontology fields use standardized outputs. For example, the Occupancy Mode field expects values like "Occupied" and "Unoccupied", but raw points may report them differently (e.g., "Occ/Unocc", "1/0", "On/Off"). Enum mapping aligns these variations, ensuring consistency for FDD, FTT, and BBI.

Mapping Enums

After templating a Boolean or String point, click the enum mapping icon on the right side of the row to open the mapping popup:

• Bold values represent the enums from the point.

• Radio button values are the required enums for the Ontology field.

• Click a required value to map it to the point’s enum.

• If None is selected, the enums are not mapped.

Writability Mapping

For writable points, you must also map writability. Features like FTT, which can override points automatically, depend on this mapping to apply the correct enum value.

You can map enums in batch by selecting multiple point groups and clicking the Map Enum button at the bottom of the page.

This will display all selected point groups and their enums on a single page, allowing for quick mapping and review. While each point group must be mapped individually, having them all in one place simplifies the process.

Review Templating

The Review Templating feature provides an overview of all templated devices, helping you identify similarities and discrepancies.

Key Features:

• Aggregated Fields: This shows how many devices contain each field.

• Filtering: Select fields to filter devices that include them.

• Discrepancy Detection: Use "Does not Contain" mode to find devices missing selected fields.

• Issue Filters:

• Missing Enum Mapping – Devices with unmapped enums.

• Duplicate Fields – Devices with multiple points assigned to the same field.