PAC
Protocol Adaptive Connector
Bring PLCs, controllers, meters and sensors into one governed real-time data stream.
The problem
Factories contain multiple equipment generations, brands, networks and serial interfaces. Point definitions, byte order, quality and disconnection handling are often buried in individual projects.
The outcome
Consolidate connectivity, point mapping, transformation, quality and buffering into a reusable edge capability.
Operational context
From heterogeneous equipment to one governed data entry point.
PAC identifies devices and protocols, then normalizes addresses, data types, byte order, quality and connection state into a governed real-time stream.
- 01120+ industrial protocolsSupport Modbus, OPC UA, Siemens, Mitsubishi, Omron, Allen-Bradley, Keyence and more than 120 industrial protocol and product families.
- 02Protocol discoveryUse network and serial probes to identify likely device protocols and shorten the survey before deployment.
- 03Point governanceNormalize data types, address areas, scaling, byte order, transformation rules and last-value caching.
Core capabilities
From product module to reusable operational capability.
The codebase includes multi-vendor drivers, protocol discovery, point transformation, upstream buffering and related tests. Compatibility must still be verified against actual models, firmware and communication conditions.
120+ industrial protocols
Support Modbus, OPC UA, Siemens, Mitsubishi, Omron, Allen-Bradley, Keyence and more than 120 industrial protocol and product families.
Protocol discovery
Use network and serial probes to identify likely device protocols and shorten the survey before deployment.
Point governance
Normalize data types, address areas, scaling, byte order, transformation rules and last-value caching.
Offline resilience
Buffer outbound data in a disk-backed queue during interruptions and resume transmission when connectivity returns.
Data and responsibility flow
Every step stays visible, verifiable and governable.
- 01Discover devices and protocols
- 02Create drivers and point mappings
- 03Normalize values, timestamps and quality
- 04Publish to TagBus and buffer at the edge when disconnected
Use cases
Start with one high-value loop.
- Connect existing production equipment
- Integrate PLC data across vendors
- Collect energy meters and environmental sensors
- Govern equipment data before cloud delivery
Responsibility boundary
PAC does not replace the real-time control or safety loops of a PLC. Every write remains subject to authorization, allowlists and field safety conditions.
Current technical baseline: The codebase includes multi-vendor drivers, protocol discovery, point transformation, upstream buffering and related tests. Compatibility must still be verified against actual models, firmware and communication conditions.