To add time series properties to an existing object type, follow the Choose existing object type path in the setup assistant. Proceed to the section on how to set up time series properties for next steps.
To create a new object type, you must first have a time series object type backing dataset. If you do not already have a dataset matching this desired schema, then you will need to create one in Pipeline Builder.
While it is possible to create a new object type as an ontology output in Pipeline Builder, we recommend creating the time series object type backing dataset in Pipeline Builder and then following the setup assistant to create the new object type. Follow the steps below to prepare the dataset in Pipeline Builder.
Before creating a new time series object type, you must first have a time series object type backing dataset. The following instructions describe how to create a time series object type backing dataset in Pipeline Builder.
Start with the dataset containing information about the objects (for example, the Machine information in the image below):
Add a Concatenate strings
transformation in Pipeline Builder.
_
).temperature
).Name this new column to easily identify it as the series ID for this specific series (for example, temperature
or temperature_series_id
).
Avoid manually creating each new series ID column by creating a dataset that has each series name as a column name via a join. Once you have this single dataset, follow these instructions:
Add an Unpivot
transformation.
series_name
.series_value
.Add a concatenate strings
transformation to generate the series ID.
_
).series_name
as the first input.machine_id
in the screenshot below).Name this new output series_id
.
Join the series ID columns back to your object type backing dataset.
Your object type must be in Object Storage V2 to back a time series property with multiple time series syncs.
Since sensor data is often powered by multiple data sources, it can be challenging to normalize and transform all sensor data within one dataset. Sometimes, it is not possible to do this because some sensors hold categorical data and others contain numerical data; different data types cannot exist within one time series sync. To avoid the need to transform and unify all sensor data into one time series dataset, you can link a time series property to multiple time series syncs. To do this, you must have a column of qualified series IDs on your object type backing dataset. Create a qualified series ID by following the steps below. Note that you will need to create your time series sync before following these steps.
Create time series reference values
transformation. Use the series ID column as the Series identifier and select the appropriate time series sync as the Time series sync RID. Name the new column qualified_time_series_id
or similar.The resulting dataset should look like the example below. The seriesId
corresponds to the series identifier in the sync dataset, and the syncRid
corresponds to the RID of the sync that stores that series.
Once you have prepared your time series object type backing dataset, follow the path in the setup assistant to Create a new object type. This path will redirect you to the Ontology Manager object creation setup assistant where you will select the new dataset as your backing datasource. Upon completion of the assistant dialog, you will be ready to set up time series properties.
If you launch the object creation setup assistant directly from the Ontology Manager home page (that is, not from the time series setup assistant), the assistant will not redirect you to the new object type’s Capabilities tab upon completion.