Emerson Exchange 365

Multiple historians

I'm looking for the best solution so this is more of a discussion than a question. I have 3 sites that are remotely located and connected by an ethernet backhual or a dark fiber lease.. TBD.. nevermind that for now. Main site will have a Proplus serve as the CH. Each of the 3 sites will have a workstation. The concern is if or when we have an issue communicating between sites, the proplus would not be collecting all of the data at the other sites. So we have a gap. That's not good as there will be some critical instruments that must have records in order to get paid. My thought was to have each workstation with the built in 250 CH points collect a few of those critical points to have a store locally. SO, you'd have the main historian on the proplus. And then each workstation would collect a number of critical points. 

Maybe there is a better way to go about this.

I'm looking for how i can set this up because it seems that CH wants to dictate by control strategy area. So, I wouldn't necessarily be able to separate data to the workstation historians by module. It seems to me i would have to create additional control strategies called... "SITE1_CRITICAL" and "SITE2_CRITICAL".. and assign the areas like that.

It's probably a workable solution. But, I would like to get some feedback.  Thanks

TreyB

• 4 Jan 2024 3:46 PM
• Cancel

2 Replies

• Andre Dicaire

  

  • 4 Jan 2024 5:31 PM

  You should have separate Plant Areas for each location. that allows you to assign modules based on their site. The Main CH can be assigned all the areas, the local workstations would only need their area modules. You can have more areas based on process units and such, but i'd say you should be set up with plant areas per site.
  
  You can also assign additional History tags to these workstations if you need more than 250 tags. If you want to stick with the free 250, you do need to have a plant area that has no more than 250 history tags assigned. So this would drive you to add a Plant area in each location to which you would assign modules with history for collection in the workstation. The rest would only be collected in the main CH server. I'd call these Site1_History and Site2 History.
  
  The additional History licensing comes in 1000 tag increments up to 3250 history tags on a workstation. That should allow you to leave plant areas as needed and all history in each site collected locally. This feature was added specifically for this type of setup to avoid the need for an App Station in each area. It also allows a PK Standalone with history to be integrated and to continue collecting history on the local HMI after it is integrated to DeltaV.

  Andre Dicaire

  • Cancel
• TreyB

  

  • 4 Jan 2024 7:21 PM

  In reply to Andre Dicaire:

  okay, so that's what i was saying. Sounds good. Thanks

  • Cancel