IMD SolutionComputing LibraryShop main store

How-to

Using AVEVA Historian with EcoStruxure Automation Expert

Edge computing and IIoT Published 6 min read

Short answer

Yes. Automation Expert connects to AVEVA System Platform, and through that connection both InTouch OMI and AVEVA Historian work with an Automation Expert application. The Historian connection and the attributes to historize are configured in the System Platform IDE, not the EAE IDE; Asset Link automates the connection between the two environments.

On this page
  1. Can you use AVEVA Historian with EcoStruxure Automation Expert?
  2. Can EAE synchronize with an existing System Platform Galaxy?
  3. What does the Asset Link module automate?
  4. Where do you configure the Historian connection and attributes?
  5. How do you historize EAE attributes step by step?
  6. How much data will historized attributes generate?
  7. How do you verify values are reaching Historian?
  8. Which manual section documents the connection?
  9. Questions asked

Yes — AVEVA Historian runs with an EcoStruxure Automation Expert (EAE) application through EAE's supported connection to AVEVA System Platform, and both AVEVA InTouch OMI and AVEVA Historian attach through that one connection. The part that trips people up is where the work happens: the Historian connection and the attributes to historize are configured in the AVEVA System Platform IDE, not in the EAE IDE. This walkthrough covers that boundary, the Asset Link module that automates the connection, the step order, a sizing check, and the manual section that documents all of it.

Can you use AVEVA Historian with EcoStruxure Automation Expert? #

Yes. Automation Expert supports a connection to AVEVA System Platform, and both AVEVA InTouch OMI and AVEVA Historian attach to an Automation Expert application through that single connection, so you do not choose between the visualization and the historian.

Think of it as two environments with one data path. The Automation Expert project runs the control application; the supported connection to AVEVA System Platform brings the engineered objects and attributes into a System Platform Galaxy; AVEVA Historian then stores the attributes you select in that Galaxy. Nothing in this chain requires the EAE IDE to know the historian exists.

If the question underneath all this is whether the plant needs a historian at all, settle whether you need a historian or just an OPC tag server before you license anything, because the rest of this article assumes the historian is the right tool.

Can EAE synchronize with an existing System Platform Galaxy? #

Yes — Schneider Electric documents synchronizing EAE with an existing AVEVA System Platform Galaxy, with a published how-to for EAE v25.0, so a plant that already runs System Platform does not start a second Galaxy for EAE.

This matters most on brownfield sites. If OMI views or other Galaxy applications already exist, the EAE project joins that Galaxy rather than forcing a parallel one, and the Historian configuration you add later sits beside the existing applications in the same IDE. The synchronization how-to is documented for EAE v25.0, so match your release before following it.

Asset Link automates the connections between the Automation Expert environment and AVEVA System Platform, so the objects and attributes you engineer on the EAE side appear in the Galaxy without you wiring every tag by hand.

It does not configure Historian. Its job stops at the connection between the two environments: once Asset Link has created the Galaxy-side objects from the EAE project, the Historian connection and the attributes to historize are still yours to set in the System Platform IDE. On the control side, values typically leave the controller over OPC UA, and an EAE OPC UA device configuration for an M580 to AVEVA is its own documented task.

Where do you configure the Historian connection and attributes? #

In the AVEVA System Platform IDE. Both the Historian connection and the selection of which attributes historize are configured there today; the EAE IDE has no Historian configuration in the documented workflow, so do not look for it there.

Task Where it is done
Connect the EAE project to AVEVA System Platform Supported connection, automated through Asset Link
Synchronize with an existing Galaxy Documented EAE function, with a how-to for v25.0
Configure the AVEVA Historian connection AVEVA System Platform IDE
Select the attributes to historize AVEVA System Platform IDE
Historian configuration in the EAE IDE Not in the documented workflow

This split is the most common point of confusion on the integration: engineers open the EAE IDE, find no Historian screens, and conclude the combination is unsupported. It is supported; the screens are on the other side.

How do you historize EAE attributes step by step? #

Six steps, and only one of them touches the EAE side: connect the two environments, then do every Historian task in the System Platform IDE — connection, attribute selection, deployment, and a verification query against a live trend.

  1. Establish the supported connection between the Automation Expert project and the System Platform Galaxy, running Asset Link so the EAE objects and attributes appear in the Galaxy automatically.
  2. Open the AVEVA System Platform IDE on the engineering station — not the EAE IDE.
  3. Configure the AVEVA Historian connection in the System Platform IDE, pointing it at the historian server that will hold the data.
  4. Select the attributes to historize on the objects that Asset Link created in the Galaxy.
  5. Save and deploy the Galaxy application so the historization settings take effect at runtime.
  6. Query one historized attribute over the last hour and confirm fresh values before you call it done.

How much data will historized attributes generate? #

At a 5-second collection interval one attribute produces 17,280 stored values per day, so 40 attributes produce 691,200 values per day — 86,400 seconds divided by 5 seconds is 17,280, times 40 attributes.

Worked example, illustrative inputs: a line with 40 attributes worth keeping, collected every 5 seconds.

  • 86,400 s/day ÷ 5 s = 17,280 values per attribute per day
  • 17,280 values × 40 attributes = 691,200 values per day
  • 691,200 ÷ 86,400 s = 8 values per second on average

That 691,200 is a ceiling: it assumes every collection stores a value. Deadband and compression on the historian suppress steady values, so measured storage lands below it — how far below depends on how much your process sits still.

Decision: 40 attributes at 5 seconds commits you to under 10 values per second, a trivial load that needs no sizing study. Change either input by two orders of magnitude — say 4,000 attributes at 1 second, which is 4,000 × 86,400 = 345,600,000 values per day, about 4,000 per second — and you size the historian server before you commit the configuration.

How do you verify values are reaching Historian? #

Query one historized attribute over the last hour from any trend or query client; a live trace with current timestamps means the chain works, and an empty or stale trace means the fault is somewhere in the chain, not in EAE itself.

Three checks, in order. Confirm the attribute is actually set to historize in the System Platform IDE — this is where a missed setting hides. Confirm the Galaxy application is deployed and the object is running. Confirm the Historian connection in that same IDE points at the right server. If the trend client cannot reach the historian at all, work through historian trend client connection failures before touching the EAE project, because a client connection problem is not an integration problem.

Which manual section documents the connection? #

Search the EcoStruxure Automation Expert User Manual for the section titled Asset Link for AVEVA Intouch OMI — that section documents the System Platform connection and the automated workflows, and it is the reference the rest of this article is built on.

Use that search string as the stable entry point for whatever release you have installed. The workflow described here is the documented one for current releases; the manual for your release is the authority on where Historian configuration lives in that release, so re-run the search after any upgrade instead of carrying the boundary forward from an older version.

Questions asked

Does EAE write to the Historian database directly?

No. In the documented workflow the Automation Expert project has no direct writer into AVEVA Historian. Values move from the controller into the Galaxy over the System Platform connection, and Historian stores what the Galaxy sends it, which is why every historization setting lives on the System Platform side. EAE only feeds the chain.

Can InTouch OMI displays show trends from this Historian?

Yes. Because InTouch OMI and the Historian connection attach to the same System Platform Galaxy, an OMI view can trend the same historized attributes without a second historian or a second data path. Build the trend against the attribute in the Galaxy, not against a separate tag database.

Will a future EAE release let you configure Historian inside the EAE IDE?

That is the stated direction, but do not plan a project against it. Until the manual for the release you run documents Historian configuration inside the EAE IDE, the AVEVA System Platform IDE remains the only documented place for the connection and the attributes to historize. Re-run the manual search after every upgrade.

Is a separate Historian license needed for this integration?

The connection documentation does not cover licensing, so treat it as a per-server question. Historian carries its own licensing regardless of where its configuration is done, and the System Platform connection does not change that. Settle licensing with your supplier before the cutover, not during it.

Keep reading

  • Explainer

    Do you need a historian or just an OPC tag server?

    No. An OPC tag server (OPC DA) supplies the current value, quality and timestamp of each item and stores nothing, so monthly figures need a historian or a SQL logger collecting from that same server. Keep a reporting client like ActiveFactory only if you also run the historian it expects.

    Edge computing and IIoT

  • Troubleshooting

    Fixing a historian device shortcut that will not appear

    A ping, an open web page and an online programming session prove IP reachability, not a working data path. When the historian drops a device shortcut, the RSLinx Enterprise tree usually holds the gateway interface instead of the controller behind it. Stop browsing and the related services, delete the interface entry, define the SLC 5/03 manually under ENI Devices at the same IP address, point a fresh shortcut at the controller icon, restart, and confirm with a live item read.

    Edge computing and IIoT

  • Explainer

    Historian data retrieval speed: what actually decides it

    An indexed historian returns a year-old sample about as fast as yesterday's, so data age is the wrong variable to optimize. Retrieval speed is set by the requested window, returned point count, retrieval mode, archive storage tier and client rendering. Benchmark candidates with identical query semantics before choosing one.

    Edge computing and IIoT