1 / 60

Data Insights - TASS & DGE

Data Insights - TASS & DGE. Objectives Introduce terminology Conceptualize SbyC data requirements Approach Describe SbyC components Examine two “down-stream” systems TASS DGE. Doug Clough, SYNERGETICS - V1.0 6 Oct 2004. SbyC - Separation by Code. Data Insights - TASS & DGE.

carney
Télécharger la présentation

Data Insights - TASS & DGE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Insights - TASS & DGE Objectives Introduce terminology Conceptualize SbyC data requirements Approach Describe SbyC components Examine two “down-stream” systems TASS DGE Doug Clough, SYNERGETICS - V1.0 6 Oct 2004 SbyC - Separation by Code

  2. Data Insights - TASS & DGE • Objectives • Introduce terminology • Conceptualize SbyC data requirements • Approach • Describe SbyC components • Examine two “down-stream” systems • TASS • DGE

  3. Detection Facility Interrogation Site Juvenile fish bypass facility SbyC Adult fish ladder Towed array Fish trap System Overview Each site is identified by a 3-character code. The third character indicates ... A Adult site J Juvenile site For example: GRA, GRJ

  4. Juvenile Fish Bypass Facility

  5. Terminology - PIT-Tag Passive Integrated Transponder Tag Two types in PTAGIS database 400kHz 505D281A64 134.2kHz 3D9.1BF17B7A11 “ISO” Country & Manufacturer 10 unique hex characters

  6. Juvenile Fish Bypass Facility

  7. Terminology - Monitor TransceiverEnergizes the coil Coil Energizes PIT-tags as they pass through Interrogation Monitor - Two or more “coils” (antennas)- Flow continuity- High probability of detecting fish

  8. Juvenile Fish Bypass Facility

  9. Terminology - Transceiver Transceiver - “Unique” ON or OFF Transceiver - Transmitter / Receiver- Decodes Tag-ID from digital signal- Periodically energizes TimerTag Coil Three types of transceiver currently in use FS1001 Alarm & parameter reporting FS1001A Enhanced diagnostics (noise) FS1001M Multiple “coils” Single-Coil Multiplexed

  10. Terminology - Timer Tag Transceiver Timer Tag - Known PIT-code emitted periodically to signal that coil and transceiver are working properly Coil Physical Timer Tag- Actual tag mounted close to coil- Normally shunted to ground- Transceiver un-grounds to test- More likely detected than actual fish Virtual Timer Tag- Code generated by transceiver circuitry- Transceiver contains antenna emulator- Code is presented to emulator to test- Likelihood of detection similar to actual fish Type of timer-tag depends on transceiver … FS1001 Physical timer-tag at each coil FS1001A Virtual timer-tag in transceiver FS1001M Virtual timer-tag in transceiver

  11. Juvenile Fish Bypass Facility

  12. Terminology - Raw Data Stream “Raw Data” - Coil-ID - Tag-ID pairs- Timer-tags- Transceiver alarms and parameters- No time-stamps!- BPA Protocol Facility Computer Data from two or more sites processed on one Facility Computer? “As is” - Transceivers hard-cabled to Facility Computer “To be” - Raw data transmitted by TCP/IP

  13. Juvenile Fish Bypass Facility

  14. Terminology - Facility Computer Facility Computer - Logical hardware / OS platform - Fault tolerant- Supports Interrogation / SbyC software- Receives raw data from transceivers- Communicates with site PLC (if present)- Sends interrogation files to PTOC Facility Computer Data from two or more sites processed on one Facility Computer? Fault Tolerance Two PC’s - “primary” and “backup” - running DOS Windows. Backup takes over sending of files if primary fails. Two identically configured PC’s running Windows 2003 Server are constrained to run in lock-step by Marathon “High-Availability Server” software. Looks like a single machine from the console. “As is” “To be”

  15. Juvenile Fish Bypass Facility

  16. Terminology - SbyC Software Separation by Code Software ... Data from two or more sites processed on one Facility Computer? Facility Computer 2 - Consults local DB 4 - Gets time-stamp 1 - Reads raw data 5 - Writes to file 6 - Closes file, sends to PTOC and opens new file 3 - Communicates with PLC Interrogations Diagnostics PLC values Note Dave Marvin will present SbyC details Near-real time communication of transceiver diagnostics to PTOC?

  17. Juvenile Fish Bypass Facility

  18. Terminology - PLC Protocol PLC Protocol - Supports bi-directional communication between Facility Computer & PLC- Allen-Bradley Protocol Facility Computer Data-Link / Network Layer - Currently: RS232 via custom driver by Gordon Anderson (Batelle) - Future: TCP/IP over Ethernet PLC Programmable Logic Controller Diversion Requests PLC values Note Don Warf will present PLC Communication details Data from two or more sites processed on one Facility Computer?

  19. Juvenile Fish Bypass Facility

  20. Terminology - PLC Facility Computer Programmable Logic Controller - Single-board computer- Communicates with diversion gate actuators, position sensors, etc.- Implements automatic sampling at specified percentage- UI supports switching between automatic, 0%, and 100% sampling- Other uses vary by site PLC Programmable Logic Controller

  21. Juvenile Fish Bypass Facility

  22. Terminology - Diversion Gate Slide Gate If closed ... OPEN If open ... CLOSED Diversion Gate - Positioned by mechanical actuator in response to PLC command- 2- and 3-way gates are used- 2-way Slide Gate shown is common- A given gate may participate in bothSampling and SbyC activity

  23. Data Insights - TASS & DGE • Objectives • Introduce terminology • Conceptualize SbyC data requirements • Approach • Describe SbyC components • Examine two “down-stream” systems • TASS • DGE

  24. TASSTransceiver Annunciator / Statistical Summarizer Alarms displayed as “red light” Site annunciator - SLC500 comms failure Coil annunciator - Timer-tag failure Corrective actions posted to event log Transceiver parameters reported Current battery condition Noise and temperature plots vs. time

  25. TASSTransceiver Annunciator / Statistical Summarizer • Alarms displayed as “red light” • Site annunciator - SLC500 comms failure • Coil annunciator - Timer-tag failure • Corrective actions posted to event log • Transceiver parameters reported • Current battery condition • Noise and temperature plots vs. time

  26. Displays file Text entered here is posted to the site event-log forum and text file. Sets lights green Displays report

  27. TASSTransceiver Annunciator / Statistical Summarizer • Alarms displayed as “red light” • Site annunciator - SLC500 comms failure • Coil annunciator - Timer-tag failure • Corrective actions posted to event log • Transceiver parameters reported • Current battery condition (Full TASS Report) • Noise and temperature plots vs. time

  28. TASSTransceiver Annunciator / Statistical Summarizer • Alarms displayed as “red light” • Site annunciator - SLC500 comms failure • Coil annunciator - Timer-tag failure • Corrective actions posted to event log • Transceiver parameters reported • Current battery condition (Full TASS Report) • Noise and temperature plots vs. time

  29. Actual time-stamp value “Almost-same” time-stamp; actual times differ

  30. TASSTransceiver Annunciator / Statistical Summarizer • Alarms displayed as “red light” • Site annunciator - SLC500 comms failure • Coil annunciator - Timer-tag failure • Corrective actions posted to event log • Transceiver parameters reported • Current battery condition (Full Tass Report) • Noise and temperature plots vs. time

  31. http://www.ptoccentral.org/maint_op/TASS/TASS_NoiseReport_RIA_04.txthttp://www.ptoccentral.org/maint_op/TASS/TASS_NoiseReport_RIA_04.txt +/- 3-Sigma Min Mean Max

  32. Data Insights - TASS & DGE • Objectives • Introduce terminology • Conceptualize SbyC data requirements • Approach • Describe SbyC components • Examine two “down-stream” systems • TASS • DGE

  33. DGEDiversion Gate Efficiency Analyzer • Last-known PLC values • Sample rates • Switch settings • DGE Configuration File basics • How DGE replays real-world events • Last 24-hours & YTD efficiencies • Action summary by control context • Gate actions - success & failure - by hour

  34. DGEDiversion Gate Efficiency Analyzer • Last-known PLC values • Sample rates (Data > Reports > SystemGen > DGE PLC) • Switch settings • DGE Configuration File basics • How DGE replays real-world events • Last 24-hours & YTD efficiencies • Action summary by control context • Gate actions - success & failure - by hour

  35. Most recent time Most recent file Click to seechange log

  36. Note: Only changes are posted to the log file. Reflects thatB_Sample_100% switch is ON

  37. DGEDiversion Gate Efficiency Analyzer • Last-known PLC values • Sample rates (Data > Reports > SystemGen > DGE PLC) • Switch settings (Farther down the same page) • DGE Configuration File basics • How DGE replays real-world events • Last 24-hours & YTD efficiencies • Action summary by control context • Gate actions - success & failure - by hour

  38. GRA(Configured switches vary from site to site) Most recent time Most recent file Click to seechange log

  39. GOJSwitch settings govern SbyC behavior DGE tracks PLC switch settings in order to know what SbyC action (if any) should have been performed in response to a given diversion request.

  40. DGEDiversion Gate Efficiency Analyzer • Last-known PLC values • Sample rates (Data > Reports > SystemGen > DGE PLC) • Switch settings (Farther down the same page) • DGE Configuration File basics • How DGE replays real-world events • Last 24-hours & YTD efficiencies • Action summary by control context • Gate actions - success & failure - by hour

  41. persistence HashAssemblage file http://www.psmfc.org/pittag/DGE/persist/2004/GOJ/GOJ_Config.txt AST-formatted ASCII file: - Indentation captures hierarchical relationships- Designed as an “outline” to be read by people- Think of it as XML without tags Variable-name Mapping User-friendly Internal global Variable names List of Gates controlled by this Monitor Site topology

  42. http://www.psmfc.org/pittag/DGE/persist/2004/GOJ/GOJ_Config.txt (Cont’d) ControlContext Set of ControlList values at any given time Gate behavior Site topology Internal global Internal local What to do in a given ControlContext

  43. DGEDiversion Gate Efficiency Analyzer • Last-known PLC values • Sample rates (Data > Reports > SystemGen > DGE PLC) • Switch settings (Farther down the same page) • DGE Configuration File basics • How DGE replays real-world events • Last 24-hours & YTD efficiencies • Action summary by control context • Gate actions - success & failure - by hour

  44. DGE In Action Read config file and instantiate site model Set PLC variables from persistence file Establish relationships between site components

  45. DGE In Action Read interrogation file and generate DGE_Events ControlState_Event Interrogation_Event Sets a PLC variable Tag-ID Coil-ID[Diversion Request]

  46. DGE In Action Read interrogation file and generate DGE_Events ControlState_Event Interrogation_Event Sets a PLC variable Tag-ID Coil-ID[Diversion Request]

  47. DGE In Action Read interrogation file and generate DGE_Events DGE_Componentinstances propagate Interrogation_Event upstream ControlState_Event Interrogation_Event Sets a PLC variable Tag-ID Coil-ID[Diversion Request]

More Related