AWS IoT SiteWise is a managed service that simplifies accumulating, organizing, and analyzing industrial gear knowledge at scale. With AWS IoT SiteWise, clients can collect knowledge reliably from a number of amenities, construction it, and make it accessible and comprehensible with out creating further software program. With gear knowledge saved in AWS IoT SiteWise, clients can assess the efficiency of their industrial gear remotely and throughout areas. This visibility throughout industrial amenities permits clients to streamline operations, in addition to establish gaps in manufacturing and waste. As well as, AWS IoT SiteWise Edge runs on-premises, securely connecting to and studying knowledge from gear or native historian databases. On Nov twenty fourth 2021, AWS IoT SiteWise introduced three new enhancements that make it simpler to ingest gear knowledge to the cloud. Prior to those enhancements, clients needed to mannequin their gear earlier than ingesting knowledge to AWS IoT SiteWise. Now, Clients can ingest knowledge into the cloud as quickly as their gear is related to AWS IoT SiteWise. Within the weblog, we are going to cowl particulars, advantages, and finest practices for patrons utilizing AWS IoT SiteWise with disassociated knowledge ingestion.
Improved asset modeling expertise
Clients use AWS IoT SiteWise to construct fashions of their bodily operations that signify their property, processes, and amenities, which is able to assist them perceive industrial knowledge within the context of their gear. As soon as asset fashions are created, clients can outline an asset hierarchy to precisely signify relationships between gadgets and gear inside a single facility or throughout a number of amenities. Our clients inform us that modeling manufacturing operation and gear could possibly be a prolonged course of, and it adjustments and evolves over time. Now with the disassociated knowledge ingestion function, all knowledge streams will likely be ingested to the cloud with out the prerequisite of associating them to property. Clients can ingest knowledge streams by an AWS IoT SiteWise Edge gateway, AWS IoT Core, or immediately utilizing AWS IoT SiteWise batch PUT API. It additionally offers you the pliability to mannequin your manufacturing operation after knowledge ingestion. As your manufacturing setting evolves, you may adapt to adjustments and replace knowledge stream and asset affiliation with none knowledge loss. It results in a virtuous cycle of asset modeling expertise as illustrated within the virtuous cycle of asset modeling beneath.
Virtuous cycle of asset modeling
While you join gear to AWS IoT SiteWise, gear knowledge are represented as knowledge streams. Every knowledge stream represents a measurement that may be related as a property for a digital illustration of kit in AWS IoT SiteWise. An asset mannequin is a digital illustration of a sort of kit and contains a number of properties which can be measurements from the gear. Utilizing an asset mannequin, you create an asset that represents a bodily piece of kit in your manufacturing operations. You possibly can then outline hierarchies of property to arrange digital representations of kit in your manufacturing setting. With the flexibility of disassociating and re-associating knowledge streams to property, you may proceed to evolve asset modeling to signify the most recent state of your manufacturing setting. For instance, in discrete manufacturing, it’s widespread for a chunk of kit to be bodily moved to a different location. On this state of affairs, you may replace Hierarchy definitions in asset mannequin to mirror the most recent change on the manufacturing flooring. As well as, all knowledge you collected continues to be retained with no loss throughout the reconfiguration.
Enabling disassociated knowledge ingestion
Disassociated knowledge ingestion is enabled by default for brand spanking new AWS IoT SiteWise clients (AWS accounts which have by no means used AWS IoT SiteWise service). Clients with an current AWS IoT SiteWise setup can allow the function with one easy step. Within the AWS IoT SiteWise console underneath Settings, select Knowledge Ingestion, after which allow Disassociated knowledge ingestion.
Enabling the brand new knowledge ingestion mode in AWS IoT SiteWise introduces a brand new useful resource known as Knowledge stream that’s time sequence knowledge. Knowledge stream and asset at the moment are assets in AWS IoT SiteWise which you can handle independently. Clients can not disable the function since entry management to knowledge streams and property are managed independently. In the event you don’t see “Knowledge Ingestion” setting, your account has this function enabled already.
You possibly can nonetheless disable the disassociated knowledge ingestion from the gateway utilizing entry management (IAM), by writing a coverage utilizing the isAssociatedWithAssetProperty situation key. The worth offered by this situation will likely be true if the PropertyAlias is related to an AssetProperty, or in any other case false. This additionally allows a state of affairs the place one gateway is the “improvement” gateway and permits all knowledge streams, whereas one other is the “manufacturing” gateways and doesn’t permit disassociated knowledge ingestion.
The next instance IAM coverage would disable knowledge ingestion of information streams not related to any asset:
{
"Model": "2012-10-17",
"Assertion": [
{
"Sid": "PutAssetPropertyValuesPropertyAliasAllowedUnmodeledBlocked",
"Effect": "Allow",
"Action": "iotsitewise:BatchPutAssetPropertyValue",
"Resource": "arn:aws:iotsitewise:*:*:time-series/*",
"Condition": {
"StringLikeIfExists": {
"iotsitewise:isAssociatedWithAssetProperty": "true"
}
}
}
]
}Knowledge streams administration
You possibly can handle knowledge streams and get prompt suggestions on ingested knowledge streams by the AWS IoT SiteWise console. The information streams web page has pagination and configurable web page dimension to scale with a lot of knowledge streams. You possibly can filter knowledge streams by utilizing the prefix of the information stream identify or by whether or not or not knowledge streams are related to property. To make sure that all knowledge streams are related to property, clients can use the AWS IoT SiteWise console or the ListTimeSeries API to filter for disassociated knowledge streams. Then, you may affiliate these knowledge streams with property.
The next steps present how one can affiliate and disassociate knowledge streams with asset properties.
- Go to the Knowledge streams web page and choose the information streams you need to affiliate or disassociate with asset properties as proven beneath.
- Click on “Handle knowledge streams” button on high proper, and it’ll take you to “Handle knowledge streams” web page.
- On “Handle knowledge streams” web page as proven within the following picture, it is possible for you to so as to add or take away asset properties for knowledge streams.
- Clicking the “Replace” button will replace all adjustments you made, as proven in Standing column.
Enhanced entry management
While you learn or write time-series knowledge in AWS IoT SiteWise, that knowledge is a part of a Knowledge stream. AWS IoT SiteWise maintains associations between AssetProperty (a DataType in SiteWise that comprises asset property data), PropertyAlias (the alias of the property), and Knowledge Stream, offering a layer of indirection so {that a} Knowledge Stream may be moved with out having to repeat knowledge: that known as Mannequin Mutability.
A Knowledge Stream should be certain to both an AssetProperty, a PropertyAlias, or each. If an AssetProperty is certain to a PropertyAlias, they each are additionally certain to the identical Knowledge Stream. Utilizing the DisassociateTimeSeriesFromAssetProperty API, you may unbind a Knowledge Stream from its AssetProperty, in order that it’s certain solely to a PropertyAlias. Then, you may bind it to a different AssetProperty by calling the AssociateTimeSeriesToAssetProperty API. You possibly can mix this with the present potential to alter a PropertyAlias utilizing the UpdateAssetProperty API to replace your knowledge group inside AWS IoT SiteWise with full flexibility. It’s also possible to accomplish this by console as mentioned above.
The Knowledge Stream useful resource sort can be utilized with IAM to use totally different insurance policies based mostly on how the information are recognized. When recognized by PropertyAlias, a time sequence useful resource should be used. A useful resource for a time sequence seems to be much like:
arn:aws:iotsitewise:area:123456789012:time-series/<DATA_STREAM_ID>
When recognized by AssetId and PropertyId, it’s a part of an Asset Useful resource. The asset useful resource ARN (Amazon Useful resource Identify) seems to be much like:
arn:aws:iotsitewise:area:123456789012:asset/<ASSET_ID>
You possibly can configure entry management utilizing a Knowledge stream ARN and the PropertyAliasPrefix situation in order that your Gateway can solely write to Knowledge Streams matching a given prefix.
{
"Model": "2012-10-17",
"Assertion": [
{
"Sid": "PutAssetPropertyValuesAliasesSiteAPrefixOnly",
"Effect": "Allow",
"Action": "iotsitewise:BatchPutAssetPropertyValue",
"Resource": "arn:aws:iotsitewise:*:*:time-series/*",
"Condition": {
"StringLikeIfExists": {
"iotsitewise:propertyAlias": "/site-a/*"
}
}
}
]
}Mix this with Gateway assist for computerized prefixing and it turns into straightforward to isolate manufacturing unit websites from one another inside the identical account. Add within the AssetHierarchyPath situation key, and it turns into straightforward to carve out roles with minimal rights for each directors and operators.
{
"Model": "2012-10-17",
"Assertion": [
{
"Sid": "PutAssetPropertyValuesAssetsSiteBHierarchyOnly",
"Effect": "Allow",
"Action": "iotsitewise:BatchPutAssetPropertyValue",
"Resource": "arn:aws:iotsitewise:*:*:asset/*",
"Condition": {
"StringLikeIfExists": {
"iotsitewise:assetHierarchyPath": "/a1b2c3d4-5678-90ab-cdef-22222EXAMPLE/a1b2c3d4-5678-90ab-cdef-66666EXAMPLE"
}
}
}
]
}The AssetHierarchyPath is the asset’s hierarchy path. It’s a string of asset IDs every separated by a ahead slash. This situation key worth seems to be much like:
/a1b2c3d4-5678-90ab-cdef-22222EXAMPLE/a1b2c3d4-5678-90ab-cdef-66666EXAMPLE
You possibly can search for the Knowledge stream identifier by utilizing the DescribeTimeSeries API or by studying metadata exported to Amazon S3. This identifier is created when knowledge is first ingested for the Knowledge Stream, so a caller should be approved to the Useful resource arn:aws:iotsitewise:area:123456789012:time-series/* in an effort to create new Knowledge streams.
Conclusion
On this weblog put up, we outlined not too long ago launched options to ingest disassociated knowledge streams and pace up time from ingestion to cloud. With industrial gear knowledge within the cloud, you’ve flexibility to affiliate, disassociate, and re-associate knowledge streams together with your industrial property. Now, you may get began sooner to ingest and eat your industrial knowledge with AWS IoT SiteWise. To be taught extra, please go to Managing knowledge streams and How AWS IoT SiteWise works with IAM in our Person Information.
In regards to the Authors
Julie Zhao
Julie is a Senior Product Supervisor on AWS Industrial IoT crew. She joined AWS in 2021 and brings three years of startup expertise main merchandise in Industrial IoT. Previous to startups, she spent over 10 years in networking with Cisco and Juniper throughout engineering and product. She is obsessed with constructing merchandise in Industrial IoT.
Philipp Sacha
Philipp is a Specialist Options Architect for IoT at Amazon Internet Companies supporting clients within the IoT space. He joined AWS in 2015 as a normal Options Architect and moved in 2018 into the position of a Specialist within the IoT space.
John Byrne
John is a Senior SDE with AWS SiteWise and beforehand with Amazon SageMaker Floor Fact. His first job, whereas nonetheless in highschool, was at an area dial-up ISP. John has centered his 9 12 months profession at Amazon on constructing extremely obtainable, extremely scalable backend techniques.
