Condition evaluation
Evaluate approved MTConnect observations using configured trigger logic.
MTConnect Condition and Event Notifications
Model-Aware Alerts
Route relevant MTConnect conditions to specified recipients and channels.
Purchasing path
Custom quote
Pricing is scoped to the selected product, deployment, and implementation requirements.
- Best for
- Plants that need notifications and shift summaries from MTConnect signals
- What you need
- Relevant MTConnect data items, trigger logic, recipients, and delivery channels
- Delivery or workflow
- On-premises alert plugins and configurable operational summaries
Overview
What Model-Aware Alerts helps your team do
On-premises plugins that use selected MTConnect signals to deliver configured notifications and operational summaries.
Route relevant MTConnect conditions to specified recipients and channels.
Notifications and summaries
Deliver scoped notifications and operational summaries.
Common uses
- Notify recipients about selected conditions
- Send configured shift summaries
- Apply custom trigger logic to MTConnect observations
How Alerts fits your MTConnect stack
Deploy Alerts after your MTConnect streams are stable. It subscribes to selected data items and executes plugin logic to trigger emails, summaries, and event notifications.
Model-Aware® technology uses patent-pending automation to generate MTConnect adapters directly from information models.
Open full-size image 
Open full-size image Machine Idle Notification Plugin
Detect idle machines by monitoring execution and process-state transitions and notify stakeholders when thresholds are exceeded.
| Data Item | Purpose |
|---|---|
| PROCESS_STATE | Primary signal for machine running/idle interpretation. |
| EXECUTION | Fallback state signal when PROCESS_STATE is unavailable. |
| CONTROLLER_MODE | Context for setup/manual states to reduce false positives. |
“Machine A has been idle for 15 minutes during Shift 2. Review setup, tooling, or queue status.”
Automatic Shift Reporting Plugin
Generate end-of-shift summaries for supervisors with counts, runtime windows, and exceptions.
| Data Item | Purpose |
|---|---|
| PART_COUNT | Shift-level production and output tracking. |
| EXECUTION | Separates active production from waiting/stop states. |
| PATH_FEEDRATE | Optional context for production trend interpretation. |
“Shift 1 summary: 128 parts completed, 86% run-state utilization, 3 extended idle windows.”
Temperature & Coolant Level Plugin
Warn operators and maintenance when machine conditions cross preventive thresholds.
| Data Item | Purpose |
|---|---|
| TEMPERATURE | Monitor spindle/critical component thermal conditions. |
| FILL_LEVEL | Track coolant reserve status before low-level events. |
| PROGRAM | Optional context to identify active job during events. |
“Machine B spindle temperature exceeded 80°C and coolant dropped below 20%. Trigger maintenance review.”
Custom plugin discovery
For custom plugins, we capture the use-case in MTConnect terms first (required data items, conditions, recipients, and business outcome), then scope implementation and validation.
Need visual monitoring instead of notification delivery?
Shop-Connect provides multi-Agent shop-floor dashboards for current and recent MTConnect data. Shop-Connect does not send native alerts; Model-Aware Alerts handles configured notification and summary delivery.
Product data
Technical details, deployment, and resources
Review the approved product facts and boundaries used to scope a deployment.
Specifications
- Inputs
- Selected MTConnect Data Items and conditions; Trigger logic; Recipients and delivery channels
- Outputs
- Configured notifications; Configured operational summaries
- Components
- On-premises alert plugins; Configured trigger and delivery rules
- Requirements
- Accessible MTConnect data; Defined conditions, recipients, and delivery channels
Integration profile
- Interfaces
- Read-only MTConnect Agent REST API responses; Configured notification and summary delivery channels
- Deployment
- On-premises alert plugins
- Data persistence
- Model-Aware Alerts is not a long-term historian; persistence depends on the configured workflow and connected systems.
- Security boundary
- Agent access, recipients, credentials, and outbound delivery are explicitly scoped for the customer environment.
- Custom integration
- Custom trigger logic and delivery channels are available through scoped plugin development.
Deployment and purchasing
Purchasing path
Custom quote
Pricing is scoped to the selected product, deployment, and implementation requirements.
Scope factors
- Data items
- Trigger logic
- Recipients and channels
- Machine and agent scope
Capabilities and explicit boundaries
Condition evaluation
Evaluate approved MTConnect observations using configured trigger logic.
Included
Evaluate selected MTConnect conditions using configured trigger logic.
Needs: Accessible MTConnect observations; Defined trigger logic
Boundary: No failure prediction or proactive maintenance model is implied.
Notifications and summaries
Deliver scoped notifications and operational summaries.
Included
Deliver configured notifications and operational summaries through scoped channels.
Needs: Defined recipients, conditions, data, and delivery channels
Boundary: Alerts is not a visual dashboard or long-term historian.
Custom integration
Apply custom trigger and delivery behavior through scoped plugin development.
Needs: Defined trigger and desired outcome
Boundary: Feasibility depends on the available MTConnect data and target channel.
Additional product limitations
- Model-Aware Alerts is not a machine connectivity product
- It does not replace a visual monitoring dashboard or long-term historian
Other Products
Model-Aware® Machine Adapters
Generate MTConnect®-ready streams directly from information models.
- Reduce manual mapping and translation layers
- Support software or Edge-Connect appliance delivery
- Scale across mixed controller environments
Edge-Connect
A physical MTConnect Adapter appliance containing the applicable equipment-specific Adapter, a local MTConnect Agent, and the Edge-Connect application on preconfigured edge hardware.
- Applicable MTConnect Adapter
- Local MTConnect Agent
- Edge-Connect application
Shop-Connect
An HDMI mini-PC monitoring appliance with the Edge-Connect application preinstalled for visualizing data from multiple separately supplied MTConnect Agents.
- Monitor current and recent data from multiple MTConnect Agents with configurable, Model-Aware dashboards, unattended displays, and Program Replay.
- Shop-Connect consumes upstream MTConnect Agent data and does not connect directly to machines
- Export the MTConnect device model and selected observations as a .mep file, then import that package into Program Replay for offline playback.
Smart Manufacturing Engineering
Hands-on engineering to implement and extend your IIoT stack.
- Connectivity architecture and database integration
- Tool-data and CAM workflow integration
- Custom AI/ML and GPT solution development
Next Steps
- Tailored to your machine connectivity needs
- Flexible deployment and licensing for your environment
- Rapid implementation with expert manufacturing support
