Re: [foxboro] Infusion with I/A series DCS
- From: "Kevin Fitzgerrell" <fitzgerrell@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 22 Jan 2008 11:58:47 +0900
OK, I think I'm getting there.
So, under InFusion, what will be the best way to provide a large
number of remote HMIs for management/supervisors/remote operators? We
normally serve around 50 simultaneous remote DMs now, and have had to
split that between 4 workstations because of the 16 DM/FV limit per
workstation. I'd prefer to have all the remote displays (at least for
management) served from a single server (easier to administer and
lower loading). Is there a way to do something like that with
InFusion? Does the web based server have lower load per instance?
Most of our users are OK with PI/Processbook for visualization, but
I'm left with the 50 or so where I require actual plant HMI.
Regards,
Kevin FitzGerrell
On 1/22/08, Johnson, Alex P (IPS) <alex.johnson@xxxxxxxxxxxxxxxx> wrote:
> Re: Just to confirm - with Infusion, each InFusion View workstation has
> it's own internal tagserver, correct? =
>
>
> Actually, each workstation has its own InFusion Application Environment
> supporting the DIObject and DAServer required to access I/A Series OM
> data. This is equivalent to a tag server in each box, but the approach
> is different.
>
>
> Re: And if I wanted to set up a traditional tagserver feeding multiple
> InTouch instances (for example to replace an old WP providing 16 DM
> instances for managers and supervisors) that is possible, but will
> require a non-standard license.
>
> I would not care to bet on how many InTouch instances can be supported
> by an InFusion Application Environment. I doubt that we test that
> configuration.
>
> In any case, a remote InFusion View/InTouch instance could get tag data
> from an IAE in a workstation using OPC.
>
>
> Re: Any word about migration tools? Either for graphics or for
> historian data?
>
> No specific migration tools are planned at this time. InTouch has to add
> a large number of features before such a tool would be practical.
>
> AIM*Historian configuration can exported today, but InFusion Historian -
> in normal mode - is configured from the IEE built control blocks by
> setting an attribute on the parameters that you want to records so I
> doubt that exporting the tag list would be of much value.
>
> AIM*Historian collected data can be exported using AIM*Oracle Export
> product. This basically puts it into a text file. I don't know if
> InFusion Historian could read that and associate with a tag.
>
>
>
> Regards,
>
> Alex Johnson
> Invensys Systems, Inc.
> 10900 Equity Drive
> Houston, TX 77041
> 713.329.8472 (voice)
> 713.329.1700 (fax)
> 713.329.1600 (switchboard)
> alex.johnson@xxxxxxxxxxxxxxxx
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
