Multi-Agent MTConnect Machine Monitoring Appliance
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
Pricing is scoped to the selected product, deployment, and implementation requirements.
Overview
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.
How it works
Features / architecture
Configure upstream Agents, dashboards, sections, and views.
Use standard-derived labels and definitions in configured views.
Present current and recent observations with configurable visual components.
Cycle through dashboard content on an attached plant-floor display.
Revisit a selected recent period and move its MTConnect context into an offline replay.
Shop-Connect begins at separately deployed MTConnect integrations. It is the monitoring layer, not the machine-connectivity layer.
Shop-Connect monitors multiple separately supplied MTConnect Agents; Edge-Connect performs local machine integration with an included Adapter and local Agent. Both use the Edge-Connect application.
| Decision point | Shop-Connect | Edge-Connect |
|---|---|---|
| Purpose | Monitor current and recent data from multiple MTConnect Agents with configurable, Model-Aware dashboards, unattended displays, and Program Replay. | Connect a machine, local Agent, or cell to MTConnect with the required integration components on the appliance. |
| Included components | HDMI mini-PC hardware; Edge-Connect application preinstalled; Configurable runtime-memory buffer; Program Replay with working-prototype MTConnect Exchange Package import and export | Preconfigured edge hardware; Applicable MTConnect Adapter; Local MTConnect Agent; Edge-Connect application |
| Agent scope | One or more separately deployed MTConnect Agents | Edge-Connect is normally scoped to the local machine, Agent, or cell running on its hardware |
| Connectivity responsibility | Shop-Connect consumes upstream MTConnect Agent data and does not connect directly to machines | Run the applicable Adapter and a local MTConnect Agent on preconfigured edge hardware. |
| Typical display use | Live and recent MTConnect dashboard visualizations; Views on the attached HDMI display; Views in plant-network browsers; Program Replay playback for a selected recent period; Working-prototype .mep files containing the MTConnect device model and selected observations | A local MTConnect Agent stream; Local views in the included Edge-Connect application |
| Shared visualization software | Edge-Connect application preinstalled | Edge-Connect application |
Move from current machine context into the recent observations that were available when an event occurred.
01 · Monitor
Configured timelines use MTConnect state semantics to show the recent sequence and duration of available execution observations.
02 · Investigate
Program maps align selected MTConnect observations over time so a team can examine the context present around an event.
03 · Replay and exchange
Revisit a selected recent period and move its MTConnect context into an offline replay.
Select and replay a recent time range assembled from the runtime-memory buffer and additional history still available from the upstream Agent.
Availability boundary: The replayable range depends on runtime memory, upstream Agent retention, connectivity, and the selected interval.
Export the MTConnect device model and selected observations as a .mep file, then import that package into Program Replay for offline playback.
Shop-Connect is the first TAMS product to produce this package.
Operational-data handling: Treat exported packages as manufacturing data and control their storage and access through your normal device, network, and file-handling procedures.
On-premises appliance
An HDMI mini-PC monitoring appliance with the Edge-Connect application preinstalled for visualizing data from multiple separately supplied MTConnect Agents.
The appliance is configured around the Agent endpoints, network paths, dashboards, and unattended-display requirements selected for the deployment.
Specifications
Review technical inputs and outputs, integration details, delivery paths, and qualification facts used to scope the next step.
Pricing is scoped to the selected product, deployment, and implementation requirements.
Configure upstream Agents, dashboards, sections, and views.
Included
Configure Agents, dashboards, sections, and visualizations.
Needs: Separately supplied Agent endpoints
Boundary: Shop-Connect does not create machine connectivity.
Included
Connect to Agents manually, through a guided workflow, or with Deployment Manager assistance.
Needs: Network paths to the Agent endpoints
Boundary: Automatic configuration depends on an available configured Deployment Manager registry.
Included
Show Agent connection status and dedicated Agent views.
Needs: Configured Agent connections
Boundary: A Connected state does not guarantee that every visualization has compatible data.
Use standard-derived labels and definitions in configured views.
Included
Use Model-Aware titles, template variables, and MTConnect definition tooltips.
Needs: Compatible MTConnect model and observations
Present current and recent observations with configurable visual components.
Included
Display text and value cards, gauges, orb and icon indicators.
Needs: Configured observations and views
Included
Display line, bar, doughnut, pie, polar-area, radar, time/value scatter, X/Y scatter, timeline heatmap, and program map visualizations.
Needs: Configured observations and views
Boundary: Recent history depends on upstream Agent data and the runtime-memory buffer.
Cycle through dashboard content on an attached plant-floor display.
Included
Use Auto Scroll and per-dashboard Auto Cycle for unattended displays.
Needs: Configured dashboards and display
Revisit a selected recent period and move its MTConnect context into an offline replay.
Included
Select and replay a recent time range assembled from the runtime-memory buffer and additional history still available from the upstream Agent.
Needs: A configured Agent and data available for the selected interval
Boundary: The replayable range depends on runtime memory, upstream Agent retention, connectivity, and the selected interval.
IncludedWorking prototype
Export the MTConnect device model and selected observations as a .mep file, then import that package into Program Replay for offline playback.
Needs: A selected replay range with an available device model and observations
Boundary: The MTConnect Exchange Package prototype is not currently part of the MTConnect Standard, may change, and does not imply adoption or endorsement by a standards body.; No assets, dashboard definitions, or other application configuration are claimed as package contents.
No. Shop-Connect consumes data from one or more separately supplied MTConnect Agents and integrations. Machine connectivity must already be provided upstream.
No. Shop-Connect has no database or long-term historian. It uses upstream Agent data plus a configurable runtime-memory buffer, so restarts or cache clearing can reduce the recent history available.
No. It visualizes MTConnect data, including conditions and alarms, but does not provide native alert delivery, scheduled reporting, OEE calculations, or KPI calculations.
No. It has no built-in user accounts, authentication, or permission levels. Access must be controlled through network, device, browser or kiosk, operating-system, and physical controls.
Shop-Connect is designed for multiple Agents, but supported scale is configuration-dependent. Agent behavior, dashboard complexity, retention settings, hardware, and network conditions all affect a deployment.
Program Replay lets a team select and replay a recent period assembled from Shop-Connect runtime memory and additional history still available from the upstream MTConnect Agent. The available range depends on the buffer, Agent retention, connectivity, and selected interval.
The MTConnect Exchange Package is a working TAMS prototype that stores the MTConnect device model and selected observations in a portable .mep file for import into Shop-Connect Program Replay and offline playback. Shop-Connect is the first TAMS product to produce the package.
No. The MTConnect Exchange Package is a working prototype, is not currently part of the MTConnect Standard, may change, and does not imply adoption or endorsement by a standards body.
HTTPS, antiforgery validation, input limits, and reCAPTCHA protect public form submissions. Review the safeguards.
Inspect the MTConnect adapter catalog, online validator, and implementation guides directly.
Call +1 (317) 907-8897 or email sales@tams.ai for sales, support, privacy, or security questions.