AWS IoT SiteWise utilization

Hi bogdan.

imposes a maximum ingestion rate limitation of 10 values per second for each asset

Per asset property, not per asset. An asset can have many properties.

SiteWise is designed to suit industrial use cases, such as factories and manufacturing. It's optimized to support near real-time operational dashboards for monitoring and alerting. To me, that's a big driver for its selection; if you want near real-time dashboards of sensor data, SiteWise can be a great choice, in terms of both performance and cost (and regardless of whether it's industrial data). For instance, it will generally be cheaper to serve such dashboards from SiteWise than from Timestream.

SiteWise can ingest data streams without any models or assets defined. Where customers do define models, iterative changes are not uncommon. I don't know enough about your use case to understand why each household would have unique models and hierarchy; that is surprising to me.

The effort in creating models and assets is well worth it if you will use features like transforms, aggregations and formulae. If you don't use these, and the focus is more on visualization and monitoring, then you may consider to only ingest the raw data streams. A lesser form of contextualization can be achieved by careful design of data stream aliases.