Treat the library as a vendor-neutral asset first and worry about each platform second. The mistake is authoring symbols inside each tool.
Define the standard once: the state set (the 9 motor states, valve open/closed/fault, etc.), the exact colors, the tag format (ISA-5.1 XX-NNN), and the canvas sizes. Keep the master as SVG so it's editable and scalable, and version it like code. Then export platform-specific outputs from that single source: PNG frames for Weintek's multi-state lamps, SVG/vector for Ignition and WinCC.
Because every export descends from the same master, a motor looks and behaves identically whether the operator is on the packaging line or the main plant — which is the whole point for cross-training and troubleshooting speed.
Use /catalogo/?builder=1 to author the master set with consistent colors and states, browse what others have standardized in /explore/, and follow the per-platform import notes in /integrations/weintek.html, /integrations/wincc.html and /integrations/ignition.html so the same symbol lands cleanly in each tool.
Define the standard once: the state set (the 9 motor states, valve open/closed/fault, etc.), the exact colors, the tag format (ISA-5.1 XX-NNN), and the canvas sizes. Keep the master as SVG so it's editable and scalable, and version it like code. Then export platform-specific outputs from that single source: PNG frames for Weintek's multi-state lamps, SVG/vector for Ignition and WinCC.
Because every export descends from the same master, a motor looks and behaves identically whether the operator is on the packaging line or the main plant — which is the whole point for cross-training and troubleshooting speed.
Use /catalogo/?builder=1 to author the master set with consistent colors and states, browse what others have standardized in /explore/, and follow the per-platform import notes in /integrations/weintek.html, /integrations/wincc.html and /integrations/ignition.html so the same symbol lands cleanly in each tool.