Skip to content

Tools and the Toolbox

Two words we use precisely, and which are easy to mix up: a Tool is a unit of capability, and the Toolbox is where you will find the ones you own.

What a Tool is

A Tool is a modular, focused component that does one useful thing — a specific integration, a data-management job, or an analytical task. Tools run on VirtualForge, and solutions are assembled by composing them rather than by building a bespoke system each time.

A Tool is not limited to moving data around. It can carry real analytical work — a formula, an algorithm, a trained model, a proprietary method — so valuable IP becomes a capability people can invoke rather than something reimplemented in every environment that needs it. See Algorithms as Tools.

The reason to work this way is not tidiness, it is compounding. A Tool built for one customer's problem becomes available to the next, and combinations become possible that nobody designed for specifically. A one-off integration helps one customer once; a Tool keeps paying.

For you, the practical consequence is that a new requirement is more often a composition than a project. Something close to what you need usually exists already.

Tool categories

Tools fall into a small number of categories, which describe the shape of the platform even where a category is not yet populated:

Category What it does
Processors Transform, normalize, or enrich data in motion
Outputs Deliver data or events onward to an external destination
Algorithms and formulas Perform work the source systems could not — invoking custom compute and returning results into the environment you asked from

Two neighbors that are not Tools

Worth separating, because both are sometimes described loosely as Tools and both are better understood as what Tools are built on:

Why it is not a Tool
Connectors A connector brings data and metadata in from an external system — a historian, an ERP or MES, a partner platform like Seeq. That is a different job: it is what makes Tools worth having, rather than a capability you reach for directly. Connectors are tool enablers.
Data platforms A managed store such as ForgeVault is a place, not an action. It holds what Tools and connectors work with.

Neither is a lesser thing — a connector is usually the first piece of a deployment and often the largest. They are simply a different kind of piece.

Connectors are the most mature category by a wide margin, and are where most of our shipping capability lives today. What is available now is listed under VirtualForge products.

What the Toolbox is

The VirtualForge Toolbox is EEI's presence inside the environment you already work in — Seeq first. It is three things at once: a storefront for discovering and using the Tools you own, a messaging point where notifications from VirtualForge reach you in place, and a feedback channel back to us from inside the product.

In rebuild. An early version of the Toolbox shipped and was used — it was how Plot Digitizer reached its first users inside Seeq. We stopped developing it deliberately rather than extending a proof of concept, and are rebuilding it from the ground up as a near-term priority. Plot Digitizer returns with it; see VirtualForge Toolbox for the full account.

Democratizing purpose-built Tools

The Toolbox is how we intend to make purpose-built capability ordinary. Organize a set of Tools around a use case, deliver them through one familiar surface, and something that used to require a custom project becomes something you can simply be granted access to.

Discovery is the other half, and it is a real problem rather than a nice-to-have. A capability you own and cannot find is worth approximately nothing, and the moment a portfolio grows past a handful of items, "ask the vendor which tools we have" stops being an acceptable answer.

How a Tool reaches you

Tools are built against VirtualForge's plugin model, packaged, and deployed to the platform. Today that path is used by EEI's own engineers; it is designed to open to partners and third parties over time, so the platform's capability can grow faster than any single company could grow it.

The mechanics — isolation, categories, packaging, and the contribution flow — are described in plugin architecture.