Inputs
- Machine or controller data
- Equipment-specific configuration
- Plant network configuration
Local MTConnect Machine Integration Appliance
Edge-Connect
Connect a machine, local Agent, or cell to MTConnect with the required integration components on the appliance.
Purchasing path
Custom quote
Pricing is scoped to the selected product, deployment, and implementation requirements.
- Best for
- Plants that want preconfigured machine connectivity at the edge
- What you need
- Machine/controller inventory, network architecture, and rollout scope
- Delivery or workflow
- Preconfigured on-premises hardware and software scoped to a local machine, Agent, or cell
Overview
What Edge-Connect helps your team do
A physical MTConnect Adapter appliance containing the applicable equipment-specific Adapter, a local MTConnect Agent, and the Edge-Connect application on preconfigured edge hardware.
Connect a machine, local Agent, or cell to MTConnect with the required integration components on the appliance.
Common uses
- Add MTConnect connectivity at a machine
- Host a local equipment Adapter and Agent
- Deploy integration components in a machine or cell network segment
How it works
From manufacturing inputs to a usable outcome
Product components
- Preconfigured edge hardware
- Applicable MTConnect Adapter
- Local MTConnect Agent
- Edge-Connect application
Outputs
- A local MTConnect Agent stream
- Local views in the included Edge-Connect application
Features / architecture
Capabilities and integration profile
Local machine integration
Package the equipment integration components on preconfigured hardware.
Local Agent stream
Expose the integrated equipment through the included Agent.
Local visualization
Use the included Edge-Connect application for local views.
- Interfaces
- Equipment-specific controller interface; Read-only local MTConnect Agent REST API
- Deployment
- Preconfigured on-premises appliance at a machine or cell
Local machine integration architecture
Connect a machine, local Agent, or cell to MTConnect with the required integration components on the appliance.
- Machine or controller dataEquipment interface approved for the deployment
- Applicable MTConnect AdapterTranslates equipment data
- Local MTConnect AgentExposes the local MTConnect stream
- Edge-Connect application and downstream consumersProvide local views and use the Agent stream
What your team supplies
- A supported or qualified machine/controller interface
- Approved machine and plant network access
- Deployment scope for the local machine, Agent, or cell
Included integration components
- Preconfigured edge hardware
- Applicable MTConnect Adapter
- Local MTConnect Agent
- Edge-Connect application
The included Edge-Connect application is the same visualization software used by Shop-Connect. On Edge-Connect, it accompanies the local Adapter and Agent; it does not turn Edge-Connect into the multi-Agent monitoring appliance.
Shop-Connect vs. Edge-Connect
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 |
Shop-Connect
- Purpose
- Monitor current and recent data from multiple MTConnect Agents with configurable, Model-Aware dashboards, unattended displays, and Program Replay.
- 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
- Agent scope
- One or more separately deployed MTConnect Agents
- Connectivity responsibility
- Shop-Connect consumes upstream MTConnect Agent data and does not connect directly to machines
- 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
- Shared visualization software
- Edge-Connect application preinstalled
Edge-Connect
- Purpose
- Connect a machine, local Agent, or cell to MTConnect with the required integration components on the appliance.
- Included components
- Preconfigured edge hardware; Applicable MTConnect Adapter; Local MTConnect Agent; Edge-Connect application
- Agent scope
- Edge-Connect is normally scoped to the local machine, Agent, or cell running on its hardware
- Connectivity responsibility
- Run the applicable Adapter and a local MTConnect Agent on preconfigured edge hardware.
- Typical display use
- A local MTConnect Agent stream; Local views in the included Edge-Connect application
- Shared visualization software
- Edge-Connect application
Specifications
Specifications, delivery, and operating boundaries
Review technical inputs and outputs, integration details, delivery paths, and qualification facts used to scope the next step.
Specifications
- Inputs
- Machine or controller data; Equipment-specific configuration; Plant network configuration
- Outputs
- A local MTConnect Agent stream; Local views in the included Edge-Connect application
- Components
- Preconfigured edge hardware; Applicable MTConnect Adapter; Local MTConnect Agent; Edge-Connect application
- Requirements
- A supported or qualified machine/controller interface; Approved machine and plant network access; Deployment scope for the local machine, Agent, or cell
Integration profile
- Interfaces
- Equipment-specific controller interface; Read-only local MTConnect Agent REST API
- Deployment
- Preconfigured on-premises appliance at a machine or cell
- Data persistence
- The local Agent and included application provide their configured current/recent data behavior; long-term storage requires a downstream system.
- Security boundary
- Machine access, plant-network placement, permitted ports, service identities, and browser access are scoped with the customer.
- Custom integration
- The selected Adapter and equipment interface determine available data; additional context requires scoped integration work.
Delivery Options
Purchasing path
Custom quote
Pricing is scoped to the selected product, deployment, and implementation requirements.
Scope factors
- Machine and controller inventory
- Network architecture
- Rollout scope
Capabilities and explicit boundaries
Local machine integration
Package the equipment integration components on preconfigured hardware.
Included
Run the applicable Adapter and a local MTConnect Agent on preconfigured edge hardware.
Needs: Supported or qualified machine interface; Approved local network access
Boundary: Coverage depends on the selected Adapter and controller interface.
Local Agent stream
Expose the integrated equipment through the included Agent.
Included
Expose the resulting local MTConnect Agent stream.
Needs: Configured Adapter and Agent
Boundary: Normal scope is the local machine, Agent, or cell running on the appliance.
Local visualization
Use the included Edge-Connect application for local views.
Included
Provide local visualization through the included Edge-Connect application.
Needs: Configured application and local access
Boundary: Edge-Connect is not the multi-Agent Shop-Connect monitoring appliance.
Additional product limitations
- Edge-Connect is normally scoped to the local machine, Agent, or cell running on its hardware
- It is not the multi-Agent Shop-Connect monitoring appliance
- Supported equipment and data coverage depend on the selected Adapter and controller interface
Downloads and resources
Supported Equipment Catalog
Review machine and controller records that can be scoped for an Edge-Connect deployment.
Frequently asked questions
What is included in an Edge-Connect deployment?
Edge-Connect packages the applicable Machine Adapter, a local MTConnect Agent, preconfigured hardware, and the Edge-Connect application for the scoped machine, Agent, or cell.
What information is needed to scope Edge-Connect?
TAMS needs the machine and controller identity, available source interface, required data, installation location, network constraints, and rollout scope.
How is Edge-Connect different from a software Machine Adapter?
A Machine Adapter is the equipment-specific integration software. Edge-Connect adds the local Agent, hardware, application, and deployment package.
Can Edge-Connect operate without internet access?
The on-premises appliance can operate without internet access when the scoped Adapter and licensing path support offline-ready deployment. Plant-network requirements still apply.
How is Edge-Connect different from Shop-Connect?
Edge-Connect performs local machine integration and includes an Adapter and local Agent. Shop-Connect monitors multiple separately supplied Agents and does not connect directly to machines.
Next Steps
- Tailored to your machine connectivity needs
- Flexible deployment and licensing for your environment
- Rapid implementation with expert manufacturing support
