Group Multi-Plant · One Privatized Platform to Manage All PC-Based and Dedicated Controllers Across Sites
For group enterprises operating multiple plants and cross-regional equipment, a privatized industrial Internet platform centrally manages APM-G220 and AIS-G160, letting headquarters O&M experts remotely access any factory and any device through one interface, with scripts and protocol templates reused across plants.
Core Solution for This Scenario
I. Industry Pain Points
Typical challenges in equipment O&M and data collection for group enterprises / multi-plant / cross-regional O&M.
- A group's multiple plants are spread across different cities or even different countries; industrial PCs, DCS, servers, and large numbers of PLCs / CNCs / injection-molding machines / robots all require O&M, yet lean teams cannot be stationed everywhere.
- When equipment fails, local staff operate blindly or wait for engineers to fly in — slow response and high cost.
- Plants mix many equipment brands and systems, preventing unified management and reuse of O&M know-how.
- O&M maturity varies by plant, making standardization hard to roll out and driving up cross-plant travel costs.
An automotive-components group operates five domestic production bases across East China, South China, and Southwest China. Its headquarters IT and process-engineering teams are based in East China, while each base's MES industrial PCs, CNC programming stations, and AOI re-inspection stations are scattered along the production lines. Every commissioning required travel — process engineers averaged 80+ travel days per year, with travel costs alone exceeding ¥200,000 and a 3–5 day response cycle. After deploying the G220 + G160 combination, a single DVS platform now manages all PC-based controllers and dedicated controllers across the five bases; cross-plant remote support rose to over 70%, travel costs dropped 60%, and commissioning response shrank from days to hours.
II. Solution
With AIXOT's non-intrusive gateway portfolio, build a "screen layer + protocol layer" dual-source data closed loop.
- Deploy G220 (PC / industrial PC / DCS / server) and G160 (PLC / CNC / injection-molding machine / robot) on key equipment at each plant, all connected to the group's unified privatized industrial Internet platform.
- Headquarters O&M experts can remotely access any factory and any device through a single browser interface — regardless of city, brand, or system.
- The platform supports centralized multi-gateway management: device list, online status, grouping, permissions, operation logs, and shared script libraries; a script validated at Plant A can be pushed directly to the same model at Plant B, enabling know-how reuse and standardization.
- Unified inspection, alarms, and audit across plants — compliance covered plant-wide in one pass.
III. Implementation Steps
An actionable path from interface inventory to a standardized closed loop.
- Inventory equipment across all plants and assign G220 / G160 access points by control type
- Privatize the industrial Internet platform at group headquarters; plant gateways connect via dedicated / private network
- Build a device–gateway–plant topology view and a tiered permission matrix
- Develop a parameter-tuning script library and protocol template library, supporting cross-plant push and reuse
- Define a unified remote O&M SOP and regular inspections, with centralized audit logging
IV. System Integration and Data Connectivity
Standardized integration points with MES / SCADA / PLC / quality systems.
- Integrate with each plant's MES / SCADA via RESTful API / industrial-protocol automated triggers
- Integrate with the O&M approval system: remote access requires a ticket / approval, with least-privilege permissions
- Integrate with CMDB: device–gateway topology syncs automatically
- Integrate with unified monitoring / alarms: anomalies from multiple plants are unified and dispatched centrally
V. Value and Quantified Metrics
Measurable benefits delivered by the non-intrusive solution.
VI. Deployment Boundaries and Compliance Red Lines
Compliance and Applicable Boundaries
For sensitive-industry plants such as semiconductor, defense, and finance, 4G must not connect to the public network and must be deployed over a dedicated network / VPN; 4G may serve as emergency backup at non-sensitive plants. The G220 applies only to PC-based master controllers; dedicated controllers are handled by AIS-G160.
VII. Frequently Asked Questions (FAQ)
Common questions for the group enterprise / multi-plant / cross-regional O&M scenario.
Can equipment across different cities be managed from one platform?
Yes. Each plant's gateways connect to the group's privatized platform via dedicated / private network, and headquarters accesses all equipment remotely through one interface.
Can O&M know-how be reused across plants?
Yes. A parameter-tuning script or protocol template validated at Plant A can be pushed directly to the same model at Plant B, achieving standardization and know-how reuse.
How are sensitive-industry plants deployed?
At plants in semiconductor, defense, finance, and similar industries, 4G must not connect to the public network and must be accessed via a dedicated network or VPN; non-sensitive plants may use 4G for emergencies.
How are operations uniformly audited?
Operation logs and protocol data from all plants are stored centrally, so a single audit covers the entire domain.
In the "group enterprise / multi-plant / cross-regional O&M" scenario, which brands of CNC, PLC, and injection-molding machines can the G160 protocol gateway connect to?
The AIS-G160 ships with a 500+ industrial-device protocol driver library and is verified to support CNC systems such as FANUC, Siemens, Mitsubishi, and SYNTEC; PLCs such as Siemens, Mitsubishi, OMRON, Delta, and Inovance; and injection-molding brands such as Hongxun, Keqiang, Mirle, and Chen Hsing. For specific supported models, see the "Device Compatibility" list on this page; some legacy devices require on-site confirmation of Ethernet-port or expansion-module conditions.
Related Scenarios and Products
CNC Machine Tool Brands and Models Supported by G160
The AIS-G160 ships with a 500+ industrial-device protocol driver library and offers native brand support for dedicated controllers — CNC, injection-molding machines, robots — that generic gateways struggle to connect. Below are the mainstream verified brands and models available for data acquisition (some models require on-site confirmation of interface conditions).
| Brand | Supported Models / Comms Conditions |
|---|---|
| FANUC | All systems with an Ethernet port can communicate; systems without an Ethernet port require on-site confirmation of whether an expansion module can be added |
| SYNTEC | System version 10.116.16X or later |
| Mitsubishi | E70, M70, M700, E80, M80, M800 |
| BROTHER | Systems with an Ethernet port |
| SIEMENS | 828D, 828DSL, 840DSL, 808D/808DSL (Ethernet-capable) |
| Haas | Full Ethernet series / full serial series |
| KND | Systems with an Ethernet port |
| GSK | All Ethernet-capable systems; 988 series, 25imc, etc. |
| Other Ethernet-Capable Brands | HNC, Mazak, HEIDENHAIN, HNC, etc. can also be connected via the edge gateway |
PLC (Programmable Logic Controller) Brands and Models Supported by G160
The AIS-G160 ships with a 500+ industrial-device protocol driver library and offers native brand support for dedicated controllers — CNC, injection-molding machines, robots — that generic gateways struggle to connect. Below are the mainstream verified brands and models available for data acquisition (some models require on-site confirmation of interface conditions).
| Manufacturer / Brand | Typical Series & Models | Comms | Protocol / Driver |
|---|---|---|---|
| Siemens | S7-200 (PPI), S7-300/400 (MPI), S7-200 Smart, S7-1200, S7-1500, LOGO! | Serial / Ethernet | S7 PPI, MPI, S7comm, Modbus TCP |
| Mitsubishi | FX0/FX1/FX2, FX3U/3G, Q series (Q00J/Q00/Q02/Q02H/Q06H/Q12H/Q25H, QnU Q00U~Q26U, QnA/A series), FX3U-ENET, FX5U, QJ71E71 | Serial / Ethernet | Mitsubishi MC, MELSEC, SLMP |
| Rockwell AB | Micro800 | Ethernet | EtherNet/IP |
| LS | XGT, XGB, XBC-DN32U | Serial / Ethernet | Proprietary protocol |
| Modbus | Standard Modbus devices | Serial / Ethernet | Modbus RTU / ASCII / TCP / RTU over TCP |
| Schneider | Full range | Serial / Ethernet | Modbus RTU / TCP |
| Power Utility Protocols | Power utility terminals | Serial / Ethernet | IEC 60870-5-101, DNP3.0, IEC 60870-5-104 |
| HollySys | LE/LK220, LK210 | Serial / Ethernet | Modbus RTU |
| THIN | XD/XL, XC | Serial / Ethernet | Modbus TCP |
| Inovance | H1U/H2U, H3U, H5U | Serial / Ethernet | Modbus |
| OMRON | CJ/CS, CV, CP | Serial / Ethernet | OMRON FINS, Ethernet TCP |
| FATEK | Full range | Serial / Ethernet | Proprietary protocol |
| Delta | DVP, AS228T | Serial / Ethernet | Modbus RTU / TCP |
| Panasonic | FPX, FP | Serial / Ethernet | MEWTOCOL_COM |
| Haiwell | Full range | Serial | Modbus RTU / ASCII |
| Kewei | LP series | Serial | Modbus RTU / proprietary protocol |
| Meters / Environmental / Building Automation | Smart meters, environmental monitoring, building-automation devices | Serial / Ethernet | CJ/T188, DL/T645 (2007/1997), HJ212, BACnet MS/TP, BACnet IP |
| OPC UA | Software/devices supporting OPC UA | Ethernet | OPC UA |
Injection-Molding Machine Brands and Models Supported by G160
The AIS-G160 ships with a 500+ industrial-device protocol driver library and offers native brand support for dedicated controllers — CNC, injection-molding machines, robots — that generic gateways struggle to connect. Below are the mainstream verified brands and models available for data acquisition (some models require on-site confirmation of interface conditions).
| Brand | Typical Models | Data Collected |
|---|---|---|
| Hongxun | AK618/AK628/AK668/A380/A80/A580, TECH/TECH1/TECH1H/TECH2/TECH2H/TECHHYB, PILOT3/3A/3AH, PILOT5530/5531/5580, 5530/5531/TECH580 (two-color/three-color), CP6K/CP7K | Process parameters, SPC data |
| Chen Hsing | AI-01/02, CPC6.0 (in progress); Ai01/Ai02/Ai11/Ai12/CPC03/CPC06/CPC07/CPC09/MPC6/MPC7 | Process parameters, SPC data |
| Baojiexin | PS660/PS360/PS860; PS860/PS660/PS560/MS300/MS500/MS700/ML200B/ML300B/ML600B/MK100/MK116/MK110/MK150/MK1030 | Process parameters, SPC data |
| Eastone | IA621/A501/A701/A921/IV3100/IV3200/HTAO7Y | Process parameters, SPC data |
| Keqiang | T6F3/T6F2/T6F5; T6F3/T6F5/A6T5/TECHTOP3/T6H3/TECHTOP5 | Process parameters, SPC data |
| Mirle | MK350/500, MK380/580, 9118; 9118/MX1/MK300/500/380/580 | Process parameters, SPC data |
| Megmeet | MCP6000, MPC303, MPC600 | Process parameters, SPC data |
| KEBA | Ethernet-type (system version below 2.0, on-site development); 1075/CP051/CP052/CP053/CP054 | Process parameters, SPC data |
| Toshiba | V7/V8/V9/TS1000 | Process parameters, SPC data |
| Nissei | NEX/PNX | SPC data |
| JSW | jswJ100ADS / AD | SPC data |
| FANUC | ROBOSHOT α-iA (Ethernet, on-site development) | SPC data |
| STAR / Easthone | Ethernet-type / serial-type (on-site development) | — |
| Inovance / Haitai / Sumitomo | Serial / Ethernet (on-site development) | — |