Running CIMPLICITY 8.2 meant operating in a specific hardware environment. It was the last generation that officially supported (though heavily optimized for Windows 7 64-bit). Typical specifications for a CIMPLICITY 8.2 server included:
You might ask: Why discuss an older version like 8.2 when GE Digital is pushing CIMPLICITY 2024? cimplicity 8.2
Perhaps the most notable aspect of Cimplicity 8.2 is its position as a "bridge" product. It arrived just as GE was launching its revolutionary Proficy Machine Edition software and beginning to shift focus toward the unified Proficy platform. While later versions would see the lines blur between Cimplicity and other Proficy components, version 8.2 maintained the classic Cimplicity architecture that veteran engineers trusted, while introducing the stability required for modern Windows operating systems. It provided a stable migration path for legacy users who were not yet ready to overhaul their entire system architecture but needed the reliability of a modern SCADA package. Running CIMPLICITY 8
One of the defining characteristics of Cimplicity 8.2 was its improved integration with the GE Fanuc hardware ecosystem, particularly the PACSystems controllers. In previous versions, configuration could sometimes be disjointed, requiring separate setups for the hardware and the SCADA interface. Version 8.2 streamlined this process, enhancing the synergy between the control layer and the supervision layer. This integration was crucial for reducing development time. Engineers could now leverage features like auto-discovery and tag import/export with greater ease, ensuring that the variables defined in the PLC logic seamlessly mapped to the Cimplicity points. This interoperability minimized configuration errors and accelerated the commissioning process for system integrators. Perhaps the most notable aspect of Cimplicity 8
For those still on CIMPLICITY 8.2 today, the pain points are becoming acute.