# AI for AWS IoT SiteWise: Asset Models, Property Values and ERP Context in One Question

> Source: https://netray.co/erp-ai/aws-iot-sitewise-ai-erp
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: AI for ERP

## Short answer

AI for AWS IoT SiteWise reads asset models and property values through the SiteWise APIs, joins them with ERP orders and maintenance records, and answers plant questions in plain English with the queries shown. The model can be hosted inside the customer's AWS account or on-prem, so the choice of a managed AWS model service versus an open-weight model stays with the customer.

## Kind

platform

## Erp Family

mfg-systems

## Erp Products

- AWS IoT SiteWise

## Industries

- Manufacturing
- Food and Beverage
- Energy
- Electronics

## Region

Global

## Persona

Industrial Data Engineer

## Eyebrow

SiteWise + ERP + private LLM

## Intro

AWS IoT SiteWise models equipment as assets built from asset models, with properties of type attribute, measurement, transform or metric, arranged in hierarchies. Data arrives from OPC UA servers through a SiteWise Edge gateway or from other AWS services, and is stored in hot and cold tiers. For plants already standardised on AWS, it is a natural historian replacement.

What it does not provide is business meaning. A measurement property named Motor_Amps on an asset in a hierarchy tells you nothing about which product was running or whether a work order was late. That meaning sits in the ERP, and the join is almost always done in a spreadsheet or a one-off Athena query.

Teams on AWS have options: Amazon managed model services, or an open-weight model they host themselves. The right answer depends on data classification and cost. Plants with customer-restricted or export-controlled data often prefer a model they host in their own VPC or on-prem, and SiteWise Edge makes local processing possible.

This page describes how to put a language layer over SiteWise and ERP data, what to bound and log, and when native AWS tools are enough.

## Pain Points

### Asset models without business context

**Detail:** SiteWise hierarchies reflect the physical plant. Products, orders, customers and quality results live elsewhere, so cross-domain questions need a custom query.

### Query skills sit with a few engineers

**Detail:** Property history APIs, SQL-style queries and S3 exports are comfortable for data engineers and opaque to supervisors and quality staff.

### Hot and cold data complexity

**Detail:** Recent values and older exports sit in different tiers with different access paths, so questions spanning months need care.

### Data classification limits

**Detail:** Process parameters for controlled programs may not be allowed into a shared model service, forcing an AI design decision early.

### Cost surprises from broad queries

**Detail:** Unbounded history pulls and large model prompts both cost money. Without limits, an assistant can become an expensive way to ask simple questions.

## Use Cases

### Cross-domain Pareto of downtime

**Description:** Combine downtime-related properties with ERP production orders and product families to rank causes.

**Erp Objects:** SiteWise assets and measurements; ERP production orders, operation confirmations

**Outcome:** Rankings by product and line that were previously assembled by hand in a notebook.

### Natural-language access to asset hierarchies

**Description:** Ask for all pumps in a hierarchy with their latest values and alarm status, without knowing property IDs.

**Erp Objects:** Asset model hierarchies, properties; ERP equipment master

**Outcome:** Fewer requests to the data engineering team for lookups.

### Process drift before quality escapes

**Description:** Correlate parameter drift with lot results and scrap to identify candidates for review.

**Erp Objects:** Lot, inspection and scrap records; SiteWise measurements

**Outcome:** Candidate causes surfaced for an engineer to confirm; correlation is not proof of cause.

### Energy and utilities by product

**Description:** Allocate energy readings to production runs and report energy per unit.

**Erp Objects:** Production order times and quantities; energy metrics

**Outcome:** Per-product energy views usable in cost discussions, with alignment assumptions stated.

### Maintenance prioritisation

**Description:** Show condition metrics beside open work orders and spare stock to support scheduling.

**Erp Objects:** Maintenance orders, equipment, spares; SiteWise properties

**Outcome:** Better-informed scheduling; planners approve any order changes.

### Asset model quality checks

**Description:** Find properties with missing units, inconsistent naming, or stale data, and propose cleanup lists.

**Erp Objects:** Asset models, property aliases, data quality indicators

**Outcome:** A cleanup backlog for the data team rather than silent inconsistency.

### Shift handover summaries

**Description:** Summarise notable events, orders run and exceptions per line for the next shift.

**Erp Objects:** Production orders, shift calendars; alarm and metric values

**Outcome:** Consistent handovers, with each statement linked to a source.

## Architecture

**Overview:** An orchestrator calls SiteWise APIs with a least-privilege IAM role and reads the ERP read-only. A model hosted in the customer's VPC or on-prem plans bounded calls, with logs retained in the customer's account.

**Layers:**

#### SiteWise access

**Detail:** IAM role limited to describe and read property values and history; VPC endpoints used where available; time windows and aggregate resolutions chosen per question.

#### Asset catalogue

**Detail:** Indexed asset models, hierarchies, units and aliases so the model resolves names before querying.

#### ERP read path

**Detail:** Read-only access to orders, routings, lots and maintenance, linked to assets through an equipment key.

#### Model hosting

**Detail:** Open-weight model on GPU instances in the customer's account, or on-prem, with an optional managed model service if policy allows.

#### Logging and approval

**Detail:** Calls, prompts and answers stored in customer-controlled logging; state changes need human approval.

## Deployment Options

### Inside the customer's AWS account

**Fit:** AWS-standard organisations

**Detail:** Model and orchestrator in a private VPC with endpoints to SiteWise; data stays in the account.

### SiteWise Edge with on-prem inference

**Fit:** Plants needing local processing

**Detail:** Edge gateway keeps data local; the model runs on a plant server and queries local data and the ERP.

### Hybrid

**Fit:** Mixed estates

**Detail:** Recent data local, historical exports in the cloud, with a single question layer over both.

## Compliance

### The AI layer reads data from a defined zone with no write path to the control network.

**Framework:** IEC 62443

### Controlled data stays inside infrastructure the customer designates; model choice is made with the classification in mind.

**Framework:** ITAR / EAR (customer obligation)

### IAM least privilege, CloudTrail-style audit, and customer-managed keys.

**Framework:** SOC 2 / ISO 27001 customer controls

### Personal data such as operator IDs minimised before prompts; retention configured by the customer.

**Framework:** GDPR

## Integration Notes

- Create a dedicated IAM role with read-only SiteWise permissions and no wildcard resource access.
- Use asset property aliases and the describe APIs to build a catalogue; refresh it on a schedule.
- Choose aggregate resolution deliberately when requesting history to avoid huge raw pulls.
- For long ranges, query exports in S3 using a controlled query service rather than live API paging.
- Align timestamps to ERP time zones and shift calendars explicitly.
- Check current SiteWise API names and limits in AWS documentation, since the service evolves.

## Product Fit

### Custom build

**Why:** SiteWise is an AWS service, so the work is an IAM-scoped connector, catalogue and private model hosting.

### DataRay

**Why:** Useful where the answer also spans databases and documents such as inspection reports alongside the SiteWise data.

## Engagement

### Assessment

**Duration:** 1-2 weeks

**Deliverables:**

- Asset model review
- Data classification decision
- ERP join key plan
- Cost guardrails

### Build

**Duration:** 2-4 weeks

**Deliverables:**

- IAM roles and endpoints
- Asset catalogue
- Bounded query tools
- ERP read views

### Pilot

**Duration:** 3-5 weeks

**Deliverables:**

- Selected lines live
- Evaluation set
- Source-shown answers
- Logging

### Scale

**Duration:** 2-4 weeks

**Deliverables:**

- More assets and sites
- Cost monitoring
- Runbook
- Model sizing review

## Buyer Questions

- Which IAM permissions does the assistant need, and are they read-only?
- Does any data go to a managed model service, and can we choose?
- How are hot and cold tiers queried and bounded?
- How do we cap query and inference cost?
- How is the asset-to-ERP join maintained?
- Can it run with SiteWise Edge on-prem?
- Where are logs stored and who can read them?
- When is a QuickSight or Athena dashboard enough?

## Faq

### Can I use Amazon managed models instead of a self-hosted one?

**Answer:** Yes, if your data classification and contracts allow it. Managed services reduce operations effort, while self-hosted open-weight models give more control over data location and cost at high volume. The orchestration, bounded queries and ERP integration are the same either way, so the model choice can be revisited later.

### How does the assistant avoid expensive queries?

**Answer:** Each tool enforces time windows, aggregate resolution and row limits, and the orchestrator applies per-user budgets. Long-range questions are routed to exports rather than live API paging. Cost reporting by user and question type helps tune limits, which matters because both data scans and model tokens cost money.

### Does it replace Athena or QuickSight dashboards?

**Answer:** No. Dashboards remain best for stable, shared views. The assistant handles ad hoc questions that cross SiteWise and ERP data. If a question recurs weekly, the right outcome is often a dashboard built from the assistant's validated query.

### Can it run on-prem with SiteWise Edge?

**Answer:** SiteWise Edge supports local data processing, and a plant-hosted model can query local data and a read-only ERP replica. Cloud-only features and long history remain in AWS, so a hybrid design is common. The trade-off is operating GPU hardware locally.

### How reliable is the ERP join?

**Answer:** As reliable as the mapping between asset IDs and ERP equipment or work centers, and the timestamp alignment. Both need an owner. The assistant can flag unmapped assets and ambiguous matches so the data team can fix them rather than guessing silently.

### Will it change data in SiteWise or the ERP?

**Answer:** Not by default. The IAM role is read-only, and any proposed action, such as a maintenance request, is drafted for a person to approve in the ERP. Controller-facing writes are out of scope.

### Is this worth it for a small AWS footprint?

**Answer:** If only a few assets stream and the standard console views answer the questions, probably not. The case strengthens when many sites or lines have varied models, and engineers regularly spend hours combining SiteWise history with ERP records.

## Search terms

aws iot sitewise ai, sitewise generative ai, sitewise erp integration, sitewise asset model llm, iot sitewise natural language query, sitewise edge on-prem ai, aws iot sitewise sap integration, sitewise private llm, aws industrial data ai manufacturing, sitewise property history api, aws iot sitewise chatbot, sitewise netsuite integration

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json