What does TechnologiX do for substations and switchgear?
TechnologiX GmbH transfers the existing secondary systems documentation of municipal utilities and grid operators into Engineering Base and brings it up to the actual as-built state. For new builds and conversions, TechnologiX designs the secondary systems and the protection and control from the circuit diagram to the wiring diagram of the protection cabinet, in line with the standards and in one shared data model.
Can TechnologiX transfer ELCAD and RUPLAN data into Engineering Base?
Yes. TechnologiX GmbH migrates substation and secondary systems documentation from legacy systems and formats such as ELCAD, RUPLAN and PDF into Engineering Base. This includes on-site as-built reconciliation, incorporating red-line mark-ups and undocumented changes, and uniform equipment designation across all substations.
Which standards does TechnologiX apply to secondary systems?
TechnologiX GmbH structures substation documentation in accordance with IEC 81346 (plant structure and reference designation), IEC 81355 (classification of documents, successor to IEC 61355), IEC 61082 (structure of electrotechnical documents) and IEC 61850 (protection and control). On request, TechnologiX also implements company-specific designation guidelines.
Does TechnologiX design protection and control in accordance with IEC 61850?
Yes. TechnologiX GmbH defines protection and control in accordance with IEC 61850 in the same Engineering Base data model as the secondary systems hardware. This creates a continuous chain from the circuit diagram to the device configuration, without manual transfer between tools.
Is TechnologiX tied to specific protection device or control system manufacturers?
No. TechnologiX GmbH advises on secondary systems and protection and control independently of specific protection device or control system manufacturers.
How does TechnologiX assure the quality of substation documentation?
At TechnologiX GmbH, quality assurance is an integral part of the process. It includes revision and change management, review and release workflows according to the four-eyes principle or your own rules, consistent versioning with a unique revision index, an impact analysis before every change and regular reconciliation of documentation with what is actually installed.