About KonnectSymbols

One equipment language. Multiple ways to see the plant.

KonnectSymbols is an independent industrial design platform for building clearer HMI, SCADA, and P&ID work from a connected symbol taxonomy.

Why it exists

Teams should not have to redraw the same plant every time the visual language changes.

Industrial projects repeatedly solve the same equipment-recognition, state, tagging, and export problems. KonnectSymbols separates the shared engineering identity of an asset from its presentation, so teams can compare styles and build a more consistent shelf.

01

Operator context first

Artwork should support a decision, not compete with values, state, alarms, trends, and navigation.

02

Evidence before claims

Applied references, internal studies, and further reading are identified separately. Guidance is not presented as certification.

03

Vendor-neutral delivery

Current exports use standard SVG, PNG, ZIP, and spritesheet workflows. No vendor-native compatibility is implied.

04

One shared taxonomy

Live styles use common categories and equipment families so presentation can evolve without losing catalog structure.

How the catalog develops

Reference. Study. Draw. Validate. Ship.

  1. ReferenceIdentify official standards, project conventions, and the boundary of what can be claimed.
  2. StudyCreate internal comparison boards and define the intended visual language.
  3. DrawBuild original artwork on a shared equipment taxonomy.
  4. ValidateCheck geometry, configuration, state behavior, export output, and catalog consistency.
  5. ShipPublish only live assets and record meaningful public changes.

Independent operator

Built and operated by Kim Phung.

KonnectSymbols is independently operated in Pennsylvania, United States. This page intentionally makes no unverified employment, certification, customer, or project-history claims.

The product is not affiliated with or endorsed by ISA, IEC, ISO, or any HMI or SCADA vendor.

Public beta

Help shape the library.

Browse the catalog free, then tell us which equipment families and workflows matter most.