Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Feb 24 2011, 2:49 PM EST (current) | sdrevik | 6 words added, 421 words deleted |
| Feb 24 2011, 2:48 PM EST | sdrevik |
Changes
Key: Additions Deletions
Purpose
This module’s main purpose is to improve on the function of the existing E-DAS / DigiTrend data integration system, by allowing an AirVision central to “poll” a site PC running AV-Trend.Typical User AirVision administrator would set up polling as an automatic functionAirVision administrator would manually “download” or “upload” configurations from site node. The site node would not need to start an upload by itself. System Requirements Both Central and the AV-Trend / Site Node system would be required to be running SQL Server 2008 (SQL 2005 not supported for this function)Broadband IP connection to the site Current Digi-Trend Function Minute data files are stored in a file with name coded to Site ID, Julian Day, and Year.File is native format for minute data, so data can be loaded into E-DAS directory and is immediately available.There is no process to sync Aux/Hourly data, Central generally polls the same logger on its own.Annotation files must be transferred manually or through Procomm Script.There is no handling for sending a subset of E-DAS config to DigiTrend PC, other than copying all the files Goal AirVision Functions - Polling Provide for a scheduled polling task to poll an AirVision Site Node much aspage ithas wouldbeen amoved logger, with designation of data types and average intervals:Average Data including Annotations, Flags, CodesCalibration DataILS ChangesPower FailureAlarm LogSample Data, Composite Data (for Site Nodes, not for AV-Trend)Central to track last successful poll time (like it does for loggers) The ability for a site to “push” its data via FTP might be useful??Authentication Communications should begin with a ‘handshake’ using a shared key between the Central and the side node, unique to each site. The listener should not respond to requests if the keys don’t match.(simple hashed text string, like our password storage?)Also verify DBS schema versions? Goal AirVision Functions – Configuration Management Allow for the user to synchronize the configuration (all that relates to a particular site) and overwrite a site nodes’ existing configurationIn the case of conflict, Central settings take priority. Other Considerations AV Site Nodes to be depicted in the Server Config as a child of the Site for sites with IP route only (no modems!!)Listener PortPasswordSpecial Handling of initial downloadIf no config exists, allow password to be downloaded HERE.
Desirable Features Provide a post-sync log of any differences between the configurations.Allow for a “test” mode, where no changes are made, but the difference report is generated.
This module’s main purpose is to improve on the function of the existing E-DAS / DigiTrend data integration system, by allowing an AirVision central to “poll” a site PC running AV-Trend.Typical User AirVision administrator would set up polling as an automatic functionAirVision administrator would manually “download” or “upload” configurations from site node. The site node would not need to start an upload by itself. System Requirements Both Central and the AV-Trend / Site Node system would be required to be running SQL Server 2008 (SQL 2005 not supported for this function)Broadband IP connection to the site Current Digi-Trend Function Minute data files are stored in a file with name coded to Site ID, Julian Day, and Year.File is native format for minute data, so data can be loaded into E-DAS directory and is immediately available.There is no process to sync Aux/Hourly data, Central generally polls the same logger on its own.Annotation files must be transferred manually or through Procomm Script.There is no handling for sending a subset of E-DAS config to DigiTrend PC, other than copying all the files Goal AirVision Functions - Polling Provide for a scheduled polling task to poll an AirVision Site Node much aspage ithas wouldbeen amoved logger, with designation of data types and average intervals:Average Data including Annotations, Flags, CodesCalibration DataILS ChangesPower FailureAlarm LogSample Data, Composite Data (for Site Nodes, not for AV-Trend)Central to track last successful poll time (like it does for loggers) The ability for a site to “push” its data via FTP might be useful??Authentication Communications should begin with a ‘handshake’ using a shared key between the Central and the side node, unique to each site. The listener should not respond to requests if the keys don’t match.(simple hashed text string, like our password storage?)Also verify DBS schema versions? Goal AirVision Functions – Configuration Management Allow for the user to synchronize the configuration (all that relates to a particular site) and overwrite a site nodes’ existing configurationIn the case of conflict, Central settings take priority. Other Considerations AV Site Nodes to be depicted in the Server Config as a child of the Site for sites with IP route only (no modems!!)Listener PortPasswordSpecial Handling of initial downloadIf no config exists, allow password to be downloaded HERE.
Desirable Features Provide a post-sync log of any differences between the configurations.Allow for a “test” mode, where no changes are made, but the difference report is generated.
