AWS IoT SiteWise Connector

Content Type: Module
Categories: Connectors,AWS,Internet-of-Things

Overview

AWS IoT SiteWise is a managed service that lets you collect, model, analyze, and visualize data from industrial equipment at scale. With AWS IoT SiteWise Monitor, you can quickly create web applications for non-technical users to view and analyze your industrial data in real time. You can gain insights about your industrial operations by configuring and monitoring metrics such as mean time between failures and overall equipment effectiveness (OEE). With AWS IoT SiteWise Edge, you can view and process your data on your local devices.

The connector provides the following actions:

  • BatchGetAssetPropertyValue
  • BatchGetAssetPropertyValueHistory
  • BatchPutAssetPropertyValue
  • DescribeAsset
  • DescribeAssetModel
  • DescribeAssetProperty
  • DescribeProject
  • GetAssetPropertyAggregates
  • GetAssetPropertyValue
  • GetAssetPropertyValueHistory
  • ListAssetModels
  • ListAssetRelationships
  • ListAssets
  • ListAssociatedAssets
  • ListPortals
  • ListProjectAssets
  • ListProjects

For more information about our AWS Connector strategy, please see the Mendix Evaluation Guide

Documentation


Please see the documentation on Mendix Docs.


 

Releases

Version: 2.1.0
Framework Version: 9.24.2
Release Notes: - Upgraded the AWS IoT SiteWise Connector to Mendix 9.24.2. - Upgraded the AWS IoT SiteWise Connector sdk to version 2.27.17 to be in line with the AWS Authentication Connector. - Improved handling of enumerations in the java code.
Version: 2.0.0
Framework Version: 9.18.0
Release Notes: - Connector updated to work with Authentication Connector 3.0 and newer versions - New java action to be able to find nearest second JA_FindNearestSecond added
Version: 1.1.0
Framework Version: 9.18.0
Release Notes: - BatchPutAssetPropertyValue action was added to the connector. This action can by used to input information into an asset’s property
Version: 1.0.1
Framework Version: 9.18.0
Release Notes: Fixed a bug where the dependencies did not bundle as expected