How to inject historical/timestamped data from SmartConnector into a single Trend Log in EBO?

[Luffybzh]

Hello everyone,

I am currently working on integrating historical energy data (previous day's index/consumption) into EcoStruxure Building Operation (EBO), and I would really appreciate some guidance or insights on the best way to achieve this (via SmartConnector, SEAL, etc.).

Current Architecture:

• I have developed a Custom Processor in SmartConnector that runs automatically every morning.

• This processor retrieves the previous day's data from an external API, parses/translates it, and sends it to my MSSQL database (which is already connected to EBO).

• In parallel, SmartConnector pushes these values to EBO via an EWS connection.

The Problem: Currently, the data comes through as unique "real-time points" inside EBO's Hardware folder (1 point created for each value). While yesterday's values are successfully added every morning, they act as instantaneous variables rather than source-historical data, making them unusable for proper chronological analysis. Furthermore, I would like to centralize all these timestamped values from the previous day into a single Trend Log.

My Goal: I am looking for the best way to have my morning automation retroactively populate a Manual Trend Log (or any other suitable Trend Log type) with the corresponding [Timestamp + Value] pairs, so that the history builds up properly inside EBO (and becomes visible within my MSSQL database as a result).

My Questions:

1. Is there a specific feature or Provider within the SmartConnector SDK (such as the EBO Provider with a historical write method) capable of pushing timestamped values directly into a Trend Log, without going through standard EWS variables?

2. Would it be wiser to use SmartConnector to generate an EBO-formatted XML file on the server, and then use a SEAL script or an EBO Scheduled Task to import that file into a Manual Trend Log?

3. In your experience, what is the best practice or most robust approach for this specific use case?
   
   Thank you in advance for your help and suggestions!

[CraigEl]

@Luffybzh I might be missing some of the broader context here, particularly around the need to preserve historical timestamps in a single Trend Log.

If the primary goal is to get external data into EBO and have it trended, would it be simpler to pull the data directly from the source API using Web Services (Script Program / Function Block)? That approach typically aligns better with how EBO expects data to be ingested and trended natively.

[KarimHussain · Accepted solution]

Hi @Luffybzh,

We just published our developer documentation which has this exact pattern implemented. You can see a working example in this project:
SmartConnector/examples/SmartConnector.GridStatusExtension at main · SchneiderElectricBuildings/Smar...

If you want to just zoom in to the Trend Log population and backfill, have a look at these two classes:

• SmartConnector/examples/SmartConnector.GridStatusExtension/BackfillPlanner.cs at main · SchneiderEle...
• SmartConnector/examples/SmartConnector.GridStatusExtension/GridStatusProcessor.cs at main · Schneide...

Let me know if you need any further guidance.

Best regards,

Karim