Problems with TrendClient object appearing in Aveva OMI.

Hello Jakob,

You might be experiencing issues with using the .NET controls within OMI as in earlier versions of the offer this wasn't a supported feature (2017).. there is a workaround to this as indicated below.

https://softwaresupportsp.aveva.com/#/knowledgebase/details/000021465?lang=en_us

There should also be a "HistoricalTrendClient" control as part of the Galaxy that can be utilized however the .NET Controls be found at the following directory, if you'd like to experiment with the documented steps above.

C:\Program Files (x86)\ArchestrA\Framework\Bin\AVEVA_Software__LLC__aaHistClientTrendControl.dll

Hi Edward, thank you so much for your help. 

One thing that keeps confusing me about the OMI,  when looking for support material and answers related to product support (which is like navigating through a jungle on the support page) , AVEVA OMI vs Intouch keeps being mixed a lot,  are they not two different types of OMI solutions?   

The article you refer to is related to Intouch. does it also apply to AVEVA OMI?   There are many cases where Intouch and OMI is mentioned either seperately or at the same time, which is confusing,  for instance, Intouch Access Anywhere seems to be the name of the solution being we use to view Aveva OMI viewapps through a web browser,  access level control in viewapp, seems to be a property called intouch access level etc.  

Is there anyone that can point me to some reading material about the difference?

Hello Jakob, 

The article provided applies to OMI, I've taken note of the discrepancies and will consult internally regarding clarifications to documentation and product support. We do have materials that available regarding product name changes that might be helpful but don't go into the detail that you may require. 

https://www.aveva.com/content/dam/aveva/documents/info/product-naming/AVEVA_Product_Naming_Transition_Guidebook_21-12.pdf

Thank you again, really appreciate this forum and being able to get support like this!

Thank you for your positive feedback, Jakob! We appreciate your participation and great questions. 

Hi Edward, need a little bit further dialogue regarding my trend issue, could you please explain the difference between the historicaltrendapp and the trendclient "solutions" (not sure I got the names right)  

The thing is that we have never been able to get a proper "trending solution" to work for our client.  We can use the trendpens, but then we had to custom make a graphical trend background with axis and timescale etc. which has never been fully satisfactory to us.

We have a lot of analog measurements in our system that the operators want to be able to trend in a easy accessible way. The approach now to get access to a proper graph is that we have a button in our viewapp, to open the historian software and there the users fetch the tags that they want to look at. 

I am now hoping to be able to fix the issue properly now that this great support forum has come to my attention 

Is there any learning material, videos etc that I can have a look at?

Hello Jakob,

As part of functional capabilities within System Platform we offer multitude of "trending" solutions out of necessity for client requirements. In short there maybe a few (lots of) options available for you to use within the application and depending on usage may provide you with maybe ~75% - 100% of requirements without customization.

A quick explanation about the "Historian Trend App" is a standalone app, which contains a set of properties that can be configured in both design and runtime. The design-time properties are set to default values that enable you to show trends in your ViewApps with minimal configuration work. Changes made to a property during run time override the value set to the same property during design time.

We also have have another app called InsightApp, which allow users to run an active Insight (Historian Client Web) browser session within a pane of a running ViewApp. The application provides visualization of data by retrieving information from Historian, it includes search functionality in which users can enter keywords into the search to retrieve relevant information.

Image of InsightApp within OMI

Image of Historian Web Client on browser

Another option which I believe you may currently be using (correct me if i'm wrong) is the Situational Awareness symbol trends, that utilize Industrial graphic pen plotting features to display information. 

Alternatively there's another option using the web widget technology in which we can create our own controls to render information. You may have seen these controls already prepackaged as part of the installation but features like carousel, web browser and qr code scanner have been built with this flexible technology.

Suggestions regarding content, there's some great information out there.. but recommend some of the following articles written from our North American partner Insource, Benjamin Davis and Mike Viteri have documented some excellent procedures on initial control implementation and dynamically assigning tags to the historical trend application.

Here are the links below:

• How to Import Historian Client Trend App in System Platform IDE
• Add Historian Client Trend tags dynamically within OMI

For more in-depth detail regarding usage of Historian Client Trend App, you can navigate to the following link, you'll be prompted to input your contact details but once you've downloaded the files you'll get 3 files as part of the zip which will include a readme, guide, and sample code (.aapkg import). Importing is not recommended (see readme)

• https://www.aveva.com/en/products/historical-trend-omi-app/