Every MES and SCADA vendor of consequence now ships some flavor of built-in historian. Opcenter has one, AVEVA has one baked into its System Platform stack, Ignition ships Tag Historian as a module you can turn on with a few clicks, and GE Vernova’s Proficy line sells its historian both standalone and bundled with its MES tools. The pitch is consistent across all of them: why pay for and integrate a second system when the one you already bought does time-series storage too?
For a line running under 200 tags, that pitch is often right. But “often” is doing a lot of work in that sentence, and the point where it stops being right isn’t a vendor’s pricing tier — it’s a function of tag count, sample rate, retention requirements, and how many different tools need to query that data. This is a framework for figuring out which side of that line you’re on.
What “bundled” actually means, mechanically
A bundled historian module is, functionally, a time-series database that ships pre-wired into your MES or SCADA’s tag structure, security model, and licensing. Ignition’s Tag Historian writes to a SQL-based store (historically MySQL or a similar relational backend, with newer versions supporting more purpose-built options) and ties directly into the platform’s tag tree — you historize a tag by checking a box. AVEVA’s and Opcenter’s bundled options work similarly: the historian is a module or component of the broader platform rather than a separately licensed, separately administered product.
A standalone historian — AVEVA Historian sold on its own, Proficy Historian as a dedicated deployment, Canary, PI System — is architected from the ground up for one job: ingest high-frequency time-series data, compress it efficiently, and serve it back fast to whatever queries hit it, whether that’s a SCADA client, a reporting tool, an MES, or a data science notebook. It usually runs on its own server, has its own licensing model (often by tag count or by data source), and has its own upgrade and backup cadence independent of the MES.
Where the real differences show up
Compression fidelity
This is the one practitioners underrate until they need to zoom into a trend six months old and find it’s been decimated into a jagged approximation of reality. Purpose-built historians use mature swinging-door or boxcar-backslash compression algorithms tuned over decades, with configurable exception and compression deadbands per tag. Bundled modules increasingly offer similar compression, but the maturity and tunability vary a lot by product and by how long that module has existed. If you’re logging analog values that matter for SPC or quality investigations — furnace temperature, fill weight, torque — ask specifically what compression algorithm is used, what the default deadband is, and whether it’s tunable per tag. Don’t accept “it compresses data” as an answer.
Query performance at scale
At 100–200 tags with a few users pulling trends in a SCADA client, almost any historian — bundled or standalone — performs fine. The failure mode shows up when a second consumer enters the picture: a BI tool pulling hourly aggregates for a management dashboard, an OEE calculation engine polling for shift totals, or an engineer running a long-range query across a year of data for a capability study. Relational-backend historians (common in some bundled modules) can bog down under those concurrent, wide-range queries in a way that dedicated time-series engines, built to serve exactly that pattern, generally don’t.
Cost per tag — and what’s actually being counted
Standalone historians are usually licensed by tag count or data source, and that licensing is a real, visible line item — which makes it easy to (wrongly) conclude bundled is “free.” It isn’t. The bundled historian’s cost is folded into the MES/SCADA license tier, often gated by the same tag-count breakpoints that govern the rest of the platform. The honest comparison isn’t “free module vs. paid product” — it’s “cost embedded in a platform tier you may already need to buy” vs. “a separately scoped line item you can size independently.” For a genuinely small line, embedded almost always wins on total cost. As tag count climbs toward the multi-thousand range across several lines, standalone licensing frequently becomes the cheaper path per tag, because dedicated historian pricing tends to scale better at volume than MES platform tiers do.
Migration and lock-in
This is the underdiscussed risk. A bundled historian’s data model is usually tightly coupled to that MES’s tag naming, asset model, and sometimes its proprietary storage format. If you outgrow the MES, or the vendor relationship sours, or you get acquired and inherit a different corporate standard, pulling years of historized data out cleanly and remapping it into a new system’s asset hierarchy is a real project — sometimes a bigger one than migrating the MES configuration itself. A standalone historian, especially one built around open access methods like OPC UA or SQL-queryable stores, is inherently more portable because it was never assumed to live and die with one MES.
A decision tree keyed to plant size, not vendor tiers
- Under ~100 tags per line, single line or a handful of similar lines, one consumer of the data (operators and a plant manager): use the bundled module. The integration savings and single-vendor support relationship outweigh anything a standalone historian buys you at this scale.
- 100–200 tags per line, multiple lines, but still one or two systems consuming the data: bundled is still usually fine — check compression tunability and confirm the vendor’s query performance claims against your actual reporting workload before committing, not after.
- Approaching or over 200 tags per line, multiple lines, and more than two systems need the data (MES, BI, quality, corporate reporting): start evaluating standalone. This is the zone where query contention and compression limitations of bundled modules most often surface as real operational pain rather than theoretical risk.
- Multi-plant, corporate historian standardization already in place, or an explicit multi-year data retention/compliance requirement: standalone, almost without exception. Corporate IT will eventually want one historian standard across sites, and it’s cheaper to be there early than to migrate later.
The honest bottom line
In our assessment, the “bundled is always inferior” narrative that standalone historian vendors sometimes push is overstated for the audience this article is written for. A single line under 200 tags, run by a lean plant IT team, is exactly the use case bundled modules from Ignition, Opcenter, and Proficy’s MES-integrated offerings were built to serve well — and paying for a second system to manage at that scale is often a self-inflicted complexity tax. The judgment call gets harder, not easier, as you scale past that point, and the mistake we’d flag most often isn’t picking bundled — it’s picking bundled without ever pressure-testing compression settings and query performance against your actual future workload before you’re three years into a data retention habit you can’t cheaply migrate out of.
This article was written with the assistance of artificial intelligence. While we aim for accuracy, the information may be incomplete, out of date, or incorrect, and should be independently verified before you rely on it for any decision. It is provided for general information only and does not constitute professional advice.
