9
1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

Embed Size (px)

Citation preview

Page 1: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

1

WWHistorian - AmplaIntegration with OPC HDA

Arthur Almeida

Page 2: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

2Confidential Property of Schneider Electric

Summary

> Test Scenario> Softwares> 1st Test – Shutdown Historian Server> 2nd Test – Broken Network Connection between InTouch and WWHistorian> 3rd Test – Shutdown Ampla Server> 4th Test – Broken Connection between Ampla and WWHistorian Server> Results

Page 3: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

3Confidential Property of Schneider Electric

AmplaProtocolo OPC-HDA

Intouch Server

OP

C

Server

OP

C C

lient

OP

C H

DA

S

erv

er

WW HISTORIAN

Protocolo Suitelink

Test Scenario

Store

Forw

ard

12 34

Page 4: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

4Confidential Property of Schneider Electric

Softwares

> Virtual Machines> Windows Server 2008R2> SQL Server 2012 SP1

> Wonderware Intouch 2014 R2> Wonderware Historian 2014 R2> Integration Objects OPCHDAServer for InSQL 1.3.0> Ampla 6.1 MR2

Page 5: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

5Confidential Property of Schneider Electric

1st Test – Shutdown Historian Server

> When WWHistorian server is offline (shutdown) Ampla recognizes error and does not capture the data.

> Connecting the WWHistorian server again, Ampla reads the updated status “good” of HDA Server and captures the data properly. But considering data backfilling for the period communication was off, it is done the wrong way: first, the value is kept frozen for the whole period. After some minutes, values are correctly updated (not frozen anymore). But at this point, as the status of the frozen value was “good”, Ampla already read it and considered it to write into its database and also for calculations, and it does not consider the updated values.

Page 6: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

6Confidential Property of Schneider Electric

2nd Test – Broken Network Connection between Client and WWHistorian> Ampla does not identify any error connection in Historian Server, so it captures the

last value written in WWHistorian.> When broken connection is restablished, there is no backfilling in Ampla history

values.> This happens because OPC HDA Integration reads the status of WWHistorian Server

and not the data sources configured in WWHistorian. So if one data source shows problem but WWHistorian keeps working, Ampla doesn't read any status if error.

Page 7: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

7Confidential Property of Schneider Electric

3rd Test – Shutdown Ampla Server

> When Ampla server is shutdown and returns later, Ampla reads the data and make fill back with no problems - with proper data.

> The backfilling period that Ampla considers is the same as configured in SampleStream at Ampla.config file.

Page 8: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

8Confidential Property of Schneider Electric

4th Test – Broken Connection between Ampla and WWHistorian Server> When we break the network connection between WWHistorian and Ampla, OPC HDA

Client shows error and Ampla stops capturing the data. Restoring the network connection, Ampla collects all data from the period connection was broken.

> It is important to highlight that, if the period of broken connection is longer than the period defined in Ampla’s SampleStream, Ampla won’t fill back the difference between those periods.

Page 9: 1 WWHistorian - Ampla Integration with OPC HDA Arthur Almeida

9Confidential Property of Schneider Electric

AmplaProtocolo OPC-HDA

Intouch Server

OP

C

Server

OP

C C

lient

OP

C H

DA

S

erv

er

WW HISTORIAN

Protocolo Suitelink

Results

Store

Forw

ard

Ampla will retrieve data correctly when fails on this point

Ampla will NOT retrieve data correctly when fails on this point. Data on WWHistorian and Ampla will be different.