Question 1

How does EngineeringService.net connect ControlLogix/CompactLogix PLCs to ThingWorx using FactoryTalk Edge Gateway?

Accepted Answer

EngineeringService.net typically acquires PLC data from Allen‑Bradley Logix controllers over EtherNet/IP and exposes it through FactoryTalk Edge Gateway for northbound connectivity. Depending on the architecture, data is published via OPC UA (for structured tag browsing and interoperability) or MQTT (for lightweight, event-driven telemetry). The team designs tag models, sampling rates, and buffering to avoid impacting scan times and to preserve data quality. For application integration, ThingWorx device models and properties are aligned to ISA‑95/IEC 62264 structures (equipment, lines, cells), enabling consistent dashboards and workflows. Transport security is implemented with TLS and certificate management, and network segmentation follows IEC 62443 zone/conduit principles.

Question 2

Which protocols are supported for Rockwell FactoryTalk IoT Solutions (EtherNet/IP, OPC UA, MQTT) and when should each be used?

Accepted Answer

EngineeringService.net supports EtherNet/IP for native Allen‑Bradley controller communications on the OT network, and uses OPC UA and MQTT for upstream integration. OPC UA is preferred when standardized information models, browseable namespaces, and multi-vendor interoperability are required, especially for integration with historians and enterprise systems. MQTT is often selected for scalable pub/sub architectures, cloud ingestion, and bandwidth-efficient transmission with store-and-forward patterns at the edge. In many projects, EtherNet/IP remains the PLC interface, while OPC UA or MQTT becomes the secure conduit to ThingWorx or cloud services. Designs incorporate TLS, certificates, and governance aligned to IEC 62443 and ISA-95 data structuring.

Question 3

Can you integrate Plex cloud MES/ERP with Rockwell/ThingWorx data for OEE and production reporting?

Accepted Answer

Yes. EngineeringService.net integrates Plex with the FactoryTalk/ThingWorx layer to support OEE, production counts, downtime reasons, scrap tracking, and order execution visibility. The team maps PLC-derived states and events to Plex work centers and production records, validates timing and count reconciliation, and implements robust error handling for intermittent connectivity. Where needed, edge buffering and idempotent transaction logic are used to prevent duplicate or missing records. Data models are aligned to ISA‑95/IEC 62264 to keep equipment hierarchies consistent across PLC, ThingWorx, and Plex. Analytics can be delivered through Plex Analytics and/or ThingWorx Analytics depending on reporting and predictive needs.

Question 4

What is FactoryTalk DataMosaix used for in an IIoT architecture, and do you implement it?

Accepted Answer

EngineeringService.net implements FactoryTalk DataMosaix to improve data governance and contextualization across OT and IT consumers. In practice, DataMosaix helps standardize tag naming, metadata, and asset context so that dashboards, analytics, and reporting remain stable even as control programs change. It also supports consistent data access patterns for applications like ThingWorx and enterprise reporting tools by providing a managed approach to data organization and lifecycle. Implementations typically include defining asset hierarchies, data quality rules, and integration points to historians or cloud services. The approach aligns with ISA‑95/IEC 62264 modeling and supports secure access patterns consistent with IEC 62443 design concepts.

Question 5

How do you implement predictive maintenance with ThingWorx Analytics in Rockwell FactoryTalk IoT Solutions?

Accepted Answer

EngineeringService.net implements predictive maintenance by first establishing reliable data capture at the edge (vibration proxies, motor current, temperature, cycle-time, alarms/events) and ensuring time synchronization and data quality. Engineers then build ThingWorx models and pipelines, selecting features that correlate with degradation and defining failure modes and labels based on maintenance history. ThingWorx Analytics is used for anomaly detection or predictive scoring, and results are operationalized through ThingWorx workflows and dashboards (e.g., health indices, alerts, recommended actions). Deployments include validation against real maintenance outcomes and tuning to reduce false positives. Security for data transport uses TLS and certificate management, and architectures follow IEC 62443 segmentation guidance.

Question 6

Do you support Vuforia augmented reality tied to live FactoryTalk/ThingWorx data for maintenance instructions?

Accepted Answer

Yes. EngineeringService.net develops Vuforia experiences that connect AR content to live operational data exposed through ThingWorx and the FactoryTalk edge layer. Typical use cases include guided maintenance steps with asset-specific overlays, remote expert support, and context-aware troubleshooting tied to alarms, run states, and work orders. The team links AR targets to equipment identifiers and data models aligned with ISA‑95/IEC 62264 so that instructions and KPIs remain consistent across systems. Implementations include role-based access controls and secure communications using TLS and certificates. This approach helps reduce MTTR and standardize maintenance execution while leveraging Rockwell and PTC’s integrated ecosystem.

Question 7

What cybersecurity controls do you apply for FactoryTalk Edge Gateway to cloud connectivity (CIP Security, TLS, certificates)?

Accepted Answer

EngineeringService.net designs secure IT/OT connectivity using defense-in-depth principles and IEC 62443 zone/conduit concepts. At the transport layer, TLS encryption and certificate-based authentication are implemented for OPC UA and MQTT paths to prevent interception and unauthorized publishing. Where applicable in the Rockwell environment, CIP Security capabilities are incorporated to strengthen device identity and communications on EtherNet/IP networks. The team also applies network segmentation (VLANs, firewalls, DMZ), least-privilege access, and hardening guidance for edge hosts. Deliverables typically include security architecture diagrams, certificate lifecycle procedures, and operational runbooks to support ongoing compliance and maintainability.

Question 8

What deliverables should a plant expect from an EngineeringService.net Rockwell FactoryTalk IoT project?

Accepted Answer

EngineeringService.net typically delivers a complete, supportable solution package: network and system architecture (including IEC 62443-aligned segmentation), FactoryTalk Edge Gateway configuration, tag and asset models, and documented data mappings to ThingWorx and/or Plex. Application deliverables include KPI dashboards, alarm/event workflows, and analytics outputs (ThingWorx Analytics or Plex Analytics) with defined acceptance criteria. The firm also provides commissioning procedures, test scripts, and operator/maintenance training. For operational continuity, projects include backup/restore procedures, certificate management guidance for TLS, and a handover package that enables internal teams to maintain and scale the solution. Deliverables are tailored to procurement requirements and plant standards while staying aligned to ISA‑95/IEC 62264 modeling best practices.

Rockwell FactoryTalk IoT Solutions

Key Features

Technical Specifications

Target Industries

Frequently Asked Questions

Need Engineering Support?

Specification	Details
Edge	FactoryTalk Edge Gateway
Cloud	PTC ThingWorx, Plex
Protocols	EtherNet/IP, OPC UA, MQTT
Analytics	ThingWorx Analytics, Plex Analytics
AR	Vuforia (PTC)
Security	CIP Security, TLS, certificates