Senseforce 2.0 Manual
  • Welcome to Senseforce 2.0
  • SF MQTT API
  • SF Edge
    • Edge Package Overview
    • Edge Installation
      • Using the SF Edge Service installer in command shell
      • Headless SF Edge Servie execution
    • Edge Configuration
      • Which Plugins to load (appsettings.xml)
      • Edge Data Routing (EventDefinition.xml)
      • OTA configuration (otasettings.xml)
      • Edge Logging
      • Input plugins
        • SQL Plugin
        • SQLite Plugin
        • OPC UA Plugin
          • OPC UA server browser
        • SIEMENS S7/SINUMERIK Plugin
          • Creating connection definition file
        • S7 Plugin
        • REST Plugin
        • TCP Listener Plugin
        • XML File Parsing Plugin
        • Heidenhain Plugin
      • Output Plugins
        • MQTT Plugin
        • SQLite Plugin
    • Edge Compute plugins
      • Creating compute plugins
      • Using compute plugins
  • SF Edge Asset Management
    • Edge version repository
  • SF Platform
    • Navigation
      • Overview Screen
    • Dataset Builder
      • Filters, Aggregations and Groupings
      • Functions of the Formula Editor
      • Additional Settings
      • Special Events
      • FAQ and Troubleshooting
    • Script Editor
      • Details of the Script Editor
      • Installed Packages
      • Working with Timestamps
        • Working with Timestamps in Python
        • Working with Timestamps in R
      • FAQ and Troubleshooting
    • Widgets
      • Text
      • Headline
      • Image
      • Progress Bar & Gauge Chart
      • Table
      • Map
      • Line, Bar, Scatter and Area Chart
      • Pie Chart
      • Gantt Chart
      • Histogram
      • Overview
      • Log
      • Default colors and color conditions
      • FAQ and Troubleshooting
    • Dashboards
      • Dashboard Filters
      • Favorites
      • Data Drilldown & Widget Interaction
      • Editing multiple dashboard widgets
      • Time Zones
      • Synchronized Zooming
      • Sharable Dashboard URL
      • Multi-chart layout options
      • Default sort for table widgets
      • Releases
      • Reporting
      • FAQ and Troubleshooting
      • Applying zoom to global timestamp filter
      • Optimise the layout for different devices
    • Machine Master Data
      • Dimensions
      • Instances
      • Things
      • Use Case
      • FAQ and Troubleshooting
    • Automation
      • Trigger
      • Scheduling overview
      • Actions
      • Test your Automation
      • Zapier integration (necessary internal steps)
      • Zapier integration
      • Subscriptions
      • FAQ and Troubleshooting
    • Event Schema Management
      • Importing a Event Schema
      • FAQ and Troubleshooting
    • Virtual Events
      • Creating a Virtual Event
      • Scheduling Overview
      • Permissions and Data Access
      • FAQ and Troubleshooting
    • Details modal for elements
    • Copy / Duplicate elements
    • Whitelabeling
    • Edge Device Management
    • Element History
    • Public API
      • Get your access token
      • Endpoints
      • Debugging scripts
      • FAQ and Troubleshooting
    • User & Group Management
      • FAQ and Troubleshooting
    • Active Directory & SSO Setup
Powered by GitBook
On this page

Was this helpful?

  1. SF Platform
  2. Machine Master Data

Use Case

PreviousThingsNextFAQ and Troubleshooting

Last updated 3 years ago

Was this helpful?

Let us consider some weather stations which are connected to Senseforce via the SF Edge client. They regularly send data about the weather like temperature, wind speed, humidity, etc. However, it doesn't send any metadata which could tell us information such as the station type, location, date of installation, etc. We have this information in the table below:

Weather Station

Location

Type

Installed

WS1

Dornbirn

Medium

2015-03-01

WS2

Feldkirch

Small

2014-03-01

WS3

Imst

Medium

2016-03-01

In its current format, this information is not very useful. If we had a link between this information and the data from the stations, we could do things like filter out results from specific station types, or aggregate all the data from a specific location. This is where Machine Master Data comes in.

We start by creating a dimension called "Location", which will store details like the station's latitude and longitude. We could store these details directly in the "Weather Station" dimension that we are going to create next, however, this type of information sounds like it will be useful for other dimensions as well.

Now that we have our Location dimension, we create our "Weather Station" dimension using "Location" as a subdimension.

We can now create the instances for our weather stations. We fill out the fields in the Instance editor, clicking the "Location" field to reveal its sub-fields. If we have already created the Instance for the location we want to set, we could use the dropdown on the right side of the "Location" field to use this existing value.

After we have repeated this process for the other two weather stations, we can apply the instances to their corresponding things. In the clip below, WS1 is applied to the thing "MqttNetPerformanceTest15".

Before we can see our changes in the Dataset Editor, we need to publish our machine master data.

Now we can use the extra information we have about our weather stations in our datasets!