Compose industrial
systems from living
parts.
Holonisphere is a browser-native authoring environment for animated process diagrams. Templates know how they connect. Diagrams know how to react to live plant data. Output is a single portable SVG that runs anywhere.
An authoring environment where every
component is aware of its context.
Most diagramming tools treat shapes as decoration. Holonisphere treats them as parts of a system. A pipe knows when it’s unwired. A valve knows which way fluid travels through it. A tank knows the tag that feeds its level. Animation, behavior, and validation all fall out of that awareness.
Holonic templates
Pipes, valves, tanks, agitators — every part is both a finished component and a reusable building block. Drop one on the canvas and it brings its connection logic, its orientation behavior, and its label bindings with it.
Tag-driven animation
Bind any visual property — appearance, fill, stroke, rotation, position, level — to a live tag value. The diagram becomes a real-time view of the plant, not a static reference drawing.
Portable SVG output
The animated rules are embedded directly in the SVG. No runtime, no framework, no licence server. A single file opens in any browser and runs the way it ran in the editor.
The whole is a part. The part
is a whole.
The word holon comes from Arthur Koestler: a thing that is simultaneously complete in itself and a member of something larger. A cell is a holon. An organ is a holon. A person, a team, a department — all holons. Every level is autonomous, every level is composed.
Industrial systems work the same way. A valve is a finished assembly with its own internals. A skid is a finished unit built from valves, pumps, sensors. A plant is a network of skids. Holonisphere is built on this idea from the canvas up — there are no “primitive shapes” that aren’t also reusable, and no “assemblies” that can’t be opened and edited.
The payoff is practical. A template authored once carries its connection rules everywhere it’s placed. A change to the master template propagates. A complex assembly can be lifted whole into a new project. The diagram you author and the diagram a control engineer reads three years later are the same artefact at different scales.
Animation rules travel
with the artefact.
The SVG that comes out of Holonisphere carries its behavior embedded as a small JSON block. Open the file in any browser and the rules run. Hand it to an engineer with no Holonisphere installed and the file still tells the truth.
A pipe knows when it’s incomplete.
Each component declares appearance rules against connection state, tag values, or option overrides. The rules are declarative, inspectable, and revision-controllable as plain text inside the SVG file.
A horizontal pipe body shows by default. When the diagram is wired vertically, the vertical body takes over. A disconnected end pulses red. Nothing in the rendering engine knows about “pipes” specifically — it just runs the rules.
{ "version": "1.0", "rules": { "#pipe_body_h": [{ "type": "appear", "source": "me.conn.group.vertical.connected", "invert": true }], "#pipe_err_left": [{ "type": "appear", "source": "me.conn.Left.missing" }], "#pipe_id_h": [{ "type": "text", "source": "me.opt.tag" // instance override }] } }
People who build the
diagrams behind the plant.
Automation engineers
Authoring HMI overlays, P&ID derivations, and live status diagrams from tag systems.
System integrators
Building reusable component libraries that propagate across many client projects and revisions.
Plant operators
Embedding live diagrams in dashboards, incident reports, and remote monitoring screens.
IEC 61131 / 61499 developers
Pairing functional block program logic with diagrammatic representations of the controlled system.