Host System Software Totalflow ( CCU) Central Collection Unit

1. Host System SoftwareTotalflow (CCU) Central Collection Unit • PC Based • Windows 95/NT • Network Capable • Functions • Collect - direct, radio, modem, etc • Archive - Long Term Audit • Reports - 14 Standard • Edit - Volume Adjustments • Alarm - Polled or Exception • Export - To Other Systems • Interactive User Interfaces

2. DDE Aware APP (Excel) SCADA System 3re PartyData Management Software Local Collection (PCCU, FS2, laptop) TAI ArchiveInterface DDE/OPC Server TotalflowHost SoftwareStructure Remote Data Communications Remote Data Communications Archive Database (binary data) Remote Data Communications Utilities Long Term Database Update Outputs DataViews Communications Server Remote Data Communications Valve Control Remote Data Communications Long Term ACCESS Databases Trending Remote Devices Voice System Alarm Monitoring Reports CONFIG Remotes Graphs Remote Data Communications System Setup Auto Scheduler Device ID Manager Device ID ACCESS Database Utilities Flow Editor

3. TDS32 - DDE/OPC Driver • 32 bit APP - Windows 95 and NT Based • FastDDE, Standard DDE, NetDDE, OPC • Communications Statistics • Polled Current Information • Collected Historical Information • Very large number of data items (32,000+) • Supports all Standard Totalflow Devices • Uses Totalflow’s Low-Power Protocol

4. DDE Server - TDS32 Excel Radio Totalflow DDE Server CPC Modem Scada Node View . . .

5. DDE Server - TDS32 Wonderware Excel Genesis DDE Server* DDE Server* DDE Server* FactoryLink Local Area Network DDE Server* CPC Modem Work Station . . . Remote Work Station File Server Wide Area Network Auto Collect CCU or WinCCU * Only one DDE Server Required per System

7. Totalflow Archival Interface- TAI • Windows DLL • Retrieve & Format Historical data • From Device (Requires WinCCU Collect) • From Laptop Files (WinCCU Laptop) • From Archive Files (including TFDATA)

8. Totalflow Archival Interface- TAI 3rd Party Application Collect User File User DLL Convert to 3rd party application’s format TAI

9. Totalflow Archival Interface and Protocol Map WinCCU32 Archive File ACCESS (locked) WinCCU32 Long Term Database Open Custom Output DLL 3rd Party Non Collection Host (i.e.. Coastal Flow) reads our Archive data FCU Original Database Proprietary TAI Open Custom Input DLL 3rd Party Collection Host (It collects, then hands off data to the WinCCU32) WinCCU32 Archive File ACCESS (locked) WinCCU32 Long Term Database Open TotalFlow Packet Protocol - Open FCU New Database Open 3rd Party Host Package. Collects Modbus register data using Modbus Protocol.(WinCCU32 is not involved). Modbus Protocol- Open FCU Modbus Registers Open 3rd Party Host Package. Collects TotalFlow database using the new TotalFlow Protocol. WinCCU32 is not involved. TotalFlow Packet Protocol - Open FCU New Database Open

10. Totalflow Archival Interface - TAI Scada View Node TAI User DLL WinCCU Scheduler Totalflow Archive Excel Collect CPC Modem Totalflow DDE Server Voice Alarm System User Phone

11. CPC - Communications Port Controller

12. WinCCU - Device ID Manager

13. Remote Comm - Get Status (Std)

14. Remote Comm - Get Status (Via Template Registers)

15. Remote Comm - Historical Data

16. Remote Comm - Historical Data

17. Remote Comm - Configure

18. Remote Comm - Direct Commands

19. Host Console - Configure (Via Template Registers)

20. Archive File - Utilities

21. Archive Files - Outputs

22. Archive File - Data Viewing

23. Long Term Database

24. Long Term Database - Graphs

25. Long Term Database - Reports

26. Long Term Database - FlowEditor

27. Long Term Database - Utilities

28. WinCCU Trending Sub-System

29. WinCCU - Trending Sub-System

30. WinCCU - Trending Sub-System

31. WinCCU - Trending Sub-System

32. Totalflow Protocol Remote Alarm Monitoring System (RAMS) • User creates alarm criteria to be monitored by the remote device(Example: AI#1 > AI#1 high limit) • These alarm criteria are downloaded to the remote device • Remote device continuously checks for the specified alarm(s)

33. Alarm Page Setup Screen

34. Monitoring Alarms by Exception The process begins with the CCU broadcasting a message to ALL devices at once. FCU FCU To all devices... If you have alarm(s), send your ID now!! FCU FCU

35. Monitoring Alarms by Exception The CCU then sets up a user specified number of timing windows. (This number is sent in the original alarm broadcast to let the remote devices know what range of time is allowed). FCU #1 FCU #2 Window 1 Window 2 Window 3 Window 4 FCU #3 FCU #4

36. Monitoring Alarms by Exception Each remote device that has an alarm condition to report, picks a random window of time and inserts its ID into it. FCU #1 FCU #2 FCU 3 FCU 2 FCU #3 FCU #4

37. Uninitiated Alarm Broadcast using Radio and Modem - Do I have an alarm? Yes - Is there anyone transmitting? No - Transmit alarm and wait for acknowledgment Radio FCU #1 Modem PC monitors the radio and modem port continuously for an alarm - Do I have an alarm? Yes - Dial the host modem - Transmit alarm and wait for acknowledgment With built-in Modem FCU #2

38. Voice Alarm Server - Call - Out Communication Server (All remote communications go through here) CCU Alarm by Polling & Alarm by Exception programs gather alarms Detected Alarms Alarm ! Voice Alarm Server 1st Callout List 2nd Callout List

39. Voice Alarm Server - Call - In Voice Alarm Server Request for current device status CCU Communication Server

40. WinCCU - Scheduler

41. WinCCU - Scheduler