Migrating SIM GCM‑Based NETWORK 8000 Systems to EcoStruxure Building Operation

[Product_Support]

Issue

A site contains NETWORK 8000 systems using SIM GCM devices. Guidance is required on how to migrate these systems to EcoStruxure Building Operation (EBO), including handling SIM-based integrations that cannot be converted automatically.

Product Line

TAC IA Series, EcoStruxure Building Operation

Environment

• NETWORK 8000
• SIM GCM
• Supported GCM controllers
• EcoStruxure Building Operation AS‑P/AS‑B

Cause

SIM GCM devices are obsolete and unsupported in EBO. SIM-based firmware, proprietary logic, and nonstandard data structures cannot be parsed by Schneider Electric migration tools. This results in the need for alternate migration and integration strategies.

Resolution

1) NETWORK 8000 Device Support Matrix

The following table summarises which NETWORK 8000 devices are supported for migration, and which cannot be converted. This provides essential context before attempting any migration or using the GCM Conversion Utility.

(Reference: F‑27741‑4, March 2019)

Device Type	Supported in EBO Migration?	Notes / Rationale
GCM (Firmware 5.4A / 5.41A)	✔ Supported	Fully convertible using the GCM Conversion Utility (non‑SIM only).
MICROZONE II	✔ Supported	All firmware versions supported.
MICROFLO II	✔ Supported	All firmware versions supported.
PEM	✔ Supported	All firmware versions supported.
LIM	✔ Supported	All firmware versions supported.
GCM with CCL	✖ Not Supported	CCL is a free‑form proprietary language; cannot be mapped to EBO.
SIM GCM	✖ Not Supported	SIM‑based applications use nonstandard structures and cannot be converted.
GCS (Global Control Station)	✖ Not Supported	Supervisory workstation requiring the GCS network; not compatible with EBO.
LNC (Local Network Controller)	✖ Not Supported	Routing/supervisory node with no convertible database.
MICROZONE (Original)	✖ Not Supported	Pre‑UC/NL architecture; no convertible logic model.
PLC (NETWORK 8000 PLC products)	✖ Not Supported	Custom ladder logic; requires GCS network; no migration path exists.

---

2) Migration of Standard (Non‑SIM) GCM Databases

Supported GCM (non‑SIM) databases can be converted using the GCM Conversion Utility. This desktop utility replaces the discontinued Transition Portal and outputs an EBO‑compatible structure.

The utility is available to BMS EcoXperts and Schneider Electric employees via the EBO Community:
🔗 https://community.se.com/t5/EcoStruxure-Building-Operation/GCM-Conversion-Utility-Desktop-Version-po...

The tool is provided “AS IS”.

Conversion Requirements

• The utility outputs a 3.1‑formatted EBO file.
• You must import it into an Automation Server running a version prior to EBO 3.2.
• After import, upgrade to EBO 3.2.1 or later.

Installation summary

1. Install the GCM Conversion Utility (.msi).
2. Ensure .NET Framework updates are installed.

Operation summary

1. Launch the tool (search GCM).
2. Select the GCM backup file.
3. Start the conversion.
4. Converted output appears in the same folder as the source backup.

Note: SIM‑based content does not convert.

---

3) SIM GCM Unsupported Status

SIM GCM devices are completely unsupported in EcoStruxure Building Operation due to:

• SIM‑based firmware
• Vendor‑specific applications
• Proprietary and non‑convertible logic structures
• No UC/NL block model
• No functional equivalent inside EBO
• No viable mapping to Function Block, Script, BACnet or Modbus objects

Because of these limitations, SIM GCMs cannot be migrated using Schneider Electric tools, and their integrations must be replaced.

---

4) Handling SIM‑Based OEM Integrations

SIM GCMs commonly implemented OEM integrations for chillers, packaged units, and plant equipment. These must be re‑established using modern integration methods.

A) Third‑party Protocol Gateways

Convert OEM protocols into:

• BACnet/IP
• BACnet MS/TP
• Modbus TCP
• Modbus RTU

This is the most common migration path.

B) OEM Native Protocol Cards

Many OEM devices now support:

• BACnet/IP
• BACnet MS/TP
• Modbus

C) Custom Engineering

Where no communication interface exists:

• Use hardwired I/O
• Recreate supervisory logic in the AS‑P
• Verify alarms, scaling, sequencing

Note: Third‑party gateways are not tested or approved by Schneider Electric Product Support. Validate mappings and performance directly with the vendor.

---

Summary

• SIM GCM devices are unsupported and cannot be converted using Schneider Electric tools.
• Only non‑SIM GCMs (firmware 5.4A/5.41A) and selected field controllers are supported.
• Use the GCM Conversion Utility for supported devices.
• SIM‑based integrations require replacement communication paths via gateways, OEM cards, or custom engineering.