1.0 INTRODUCTION

2.0 GETTING STARTED

3.0 DATABASE MANAGEMENT

4.0 PAGER

5.0 DATA DISPLAY

6.0 HYDROLIC ANALYSIS AND FORECASTING

7.0 ALARM MANAGEMENT

8.0 WEB TOOLS

9.0 TOOLS

10.0 MANUAL ACTIVITIES

11.0 ADDENDUM

1.0 INTRODUCTION

1.1 BACKGROUND

DEC Data Systems develops environmental data acquisition and control software for the 32-bit Windows environment. The basic DataWise® software package is able to collect, analyze, and manipulate data from most types of telemetry currently on the market. Also, custom programming and system programming can be done to incorporate new data acquisition modules and analyses, and to display routines and screens to suit your unique needs.

DEC Data Systems personnel have been working in the data acquisition and control industry for over 25 years, with expertise in meteorology, hydrology, and real-time computer programming. Their hands-on experience includes hydrologic modeling for watersheds, channel routing, and reservoir management, using the SSMA model and various other hydrologic routing models. DEC Data Systems understands the complex system requirements for successful environmental data acquisition and database management. This expertise is reflected in the DataWise® software product.

 

1.2 SYSTEM OVERVIEW

The DataWise® software general-purpose package was designed for and optimized to run under all 32 bit Windows operating systems. DataWise® software provides you with the following functions, which are further described in their respective Chapters:

• Data Acquisition
• Database Management
• Data Display
• Realtime Controls
• Hydrologic Analysis and Forecasting
• Alarm Management
• Web Tools
• Support.

 

1.3 USER KNOWLEDGE

To use the DataWise® system, the primary user should have a good working knowledge of Windows-based, personal computer systems/workstations, particularly Windows NT or Windows 2000. The user should also have a good knowledge of the types of functions you want the DataWise® database to perform. That is, you should have a plan, which defines the following:

• Functions to be performed: Data acquisition functions, ALERT management, sensor management, alarm management.
• Types of sensors used.
• Types of data you want to collect and record.
• How you want the data displayed: raw, tabular, graphically, drawings/maps.
• How much manipulation you want to do to the data: statistical analysis, rules based.
• How often and on what basis you want alarms to occur: regular reporting, out-of-limit notification, interrupt.

To help you (where needed), each chapter will start by listing data you must have on hand to perform the steps in that chapter.

 

1.4 DOCUMENT OVERVIEW

This document is a Users’ Manual with explanation of DataWise® and steps on how to work through and with the program. The document is organized initially by startup and set up activities and by major functions. Following that is progressively more detailed information, such as detailed explanations of specific areas and system diagnostics. This is a "Foundation" Users’ Manual. For each customer’s specific implementation, DEC Data Systems engineers can provide an addendum to this document for unique implementation. Your system may have such an addendum or you may request an addendum be developed for you by contact DEC Data Systems. Specifically, information may be found as described below.

CHAPTER 2 How to install, set up, and get started using DataWise®, including configuring sensors and stations.

CHAPTER 3 Database Management

CHAPTER 4 Pager

CHAPTER 5 Data Display

CHAPTER 6 Hydrologic Analysis and Forecasting

CHAPTER 7 Alarm Management

CHAPTER 8 Web Tools

CHAPTER 9 Tools

CHAPTER 10 Manual Activities

 

1.5 DOCUMENT CONVENTIONS

This Users’ Manual is set up to be easy to use and easy for you to understand the commands and functions you are asked to perform. To aid in this goal, the following standard set of conventions is used.

• The document is designed to be printed on a color printer or copied on a color copier machine.
• All primary commands are in larger font, all caps, bold and in red; for example, INSTALL DataWise®.
• All secondary commands are in Arial, all caps, bold, and black; for example, CLICK on OK.
• All menu selections are in larger font, title case, bold, and green; for example, CHOOSE Start >Run.
• All directories, files, folders and/or paths for finding a particular file is in Arial, lowercase, italics, bold, and light blue; for example, GO TO c:\dw\utils\menu.exe.
• Notes of special interest to you on a given topic are centered on the page and in italics.

1.6 FREQUENTLY ASKED QUESTIONS   Are there any issues transferring data from the Datawise native binary format to another database in the event of a system migration? All data in the DataWise native database can be easily transferred to any relational database in which an ODBC connection can be made. Known databases that can be used are MS-SQL, Oracle, Access, and MySQL. All data in the DataWise native database can also be easily transferred to a HEC-DSS. Additionally, data can be exported to text files in a variety of formats suitable for importing to various databases.   What is involved in configuring the Datawise system to perform back up to an external DB? The following steps are all performed from a menu-driven, DataWise Dialog: 1) Specify an ODBC data source name. 2) Specify the sensors for which it is desired to store data into the external DB. 3) Specify the form in which the data is to be stored. That is, a) in raw data form as it is received, b) in processed form after it has been converted to engineering units, c) whether period values for rainfall should be stored (e.g, 15-minute rainfall, hourly rainfall, etc.) Note that data for a single sensor can be stored in multiple ways. Once the above steps are performed, data transfer to an external DB is automatic and performed in real-time unless the user specifies that it should be done periodically at some user-specified interval or on demand.   How often do you need to migrate data to an external DB that is used for queries? DataWise can be configured to: 1) “migrate” data to an external DB in real-time so that whatever data is in the native DataWise data base is also in the external DB at all times. 2) “migrate” data to an external DB at any user-specified interval. 3) “migrate” data to an external DB on demand. The preferable way is usually to populate an external DB in real-time so that at any time the external DB is queried it will contain up to date data.   Why does Datawise store data to a binary database? (Advantages and Disadvantages) Advantages: 1) Relational databases are not efficient in storing un-evenly spaced time series data, which is what data in an ALERT / IFLOWS system is. This becomes especially true as the time series becomes long. The native DataWise database is highly optimized for rapid handling of long time series data for multiple sensors. As a point of interest, even though the U.S. Army Corps of Engineers has invested heavily in optimizing the Oracle RDB for storing time series data for its hydrologic operations, the non-RDB HEC-DSS still outperforms the optimized Oracle RDB by nearly two orders of magnitude. 2) The DataWise native database has been optimized for detecting and correcting erroneous data (which can and does occur in ALERT systems). 3) The DataWise native database is optimized for detecting sensor data that has gone into user-specified alarm conditions and for performing some external function when alarm conditions occur. Disadvantages: Clearly, accessing the native DataWise database cannot be performed directly using standard RDB methods. If DataWise did not populate external databases, this could be considered a significant disadvantage. However, since DataWise can easily maintain a “parallel” data set in a RDB, the disadvantages are relatively minor.   Who helps us establish proper backup procedures for the Datawise base station? DEC DataSystems personnel provide this service as part of the support provided when DataWise is purchased.   Could you review the process for creation and modification of display maps for the base station? 1) Select the type of map background for placing sensor data on. Up to 100 different maps can currently be supported in DataWise. Map backgrounds can either be raster graphics (e.g., .bmp, .jpg, .gif files) or vector graphics. If using a raster graphic map background, the user must specify the coordinates (latitude / longitude) of the map boundaries. 2) For each map to be displayed, specify the sensors to be displayed on the map. Sensor positions are initially determined by their coordinates although sensors can be re-positioned on a map-by-map basis if desired.   Review the analysis capabilities of the base station. What applications will we be able to transfer data to and what special configuration requirements will need to be met to make them work? Analysis capabilities include, but are not limited to: 1) Tabular data in fixed-format displays (static or realtime) 2) Tabular data in user-specified format displays (static or realtime) Note that a wide range of statistical analysis can be performed on any tabular data value before it is displayed. 3) Tabular reports displaying statistical analysis of rainfall data including maximum observed intensities for various time periods, hourly, daily, monthly, and yearly rainfall reports. 4) Time series plots of data from single or multiple sensors. Plots can be either static or dynamic. 5) “Animated graphics” displays in which users can design their own graphic displays (maps, schematics of weather stations, etc.) These screens can contain a wide range of “widgets” including gages, dials, thermometers, stream cross-sections, time series plots, simple text values. All displays update in realtime. 6) Extensive mapping capabilities including isohyetal maps which display rainfall similar to radar intensity maps. Note that all displays that are also available remotely either through the DataWise client software or via a standard browser.   What is required to integrate QPF data into the base station for the generation of alerts? A connection to a data stream (e.g. NOAA-port) that contains NWS-QPF data.   How does the station handle visual alerts? What do they look like? DataWise generated alarms (alerts) can be delivered in numerous ways, from visual alerts on computer screens to text messages to controls of an external device. Station visual alerts can be delivered to not only the master DataWise base station but also to every computer on the network running the DataWise client software or every computer with a browser pointed to the DataWise Web server. Visual alarms can be customized or standard. In standard mode, an alarm display will pop up over the top of any and all applications currently running. The display provides a tabular list of all sensors in alarm condition and clicking on a specific sensor in the list will show the reason for the alarm condition. If a map is being displayed and the map contains a sensor that is in alarm condition, the sensor data will turn red. Note that an audible sound can be associated with an alarm. The sound can be customized to execute any desired .wav file on a sensor / condition by sensor / condition criterion or just a standard alarm tone.   Does the station log both meteorological and administrative alerts that are triggered? All alarms (alerts) are logged.   How do we access the logs? Through standard DataWise displays.   NWS alerts what is required to configure the station to ingest data from the NWS? Would there be firewall issues associated with collection or transfer of data from outside sources? Through the TCP/IP socket mechanism over the internet using NOAA-port or something equivalent. DataWise comes standard with software to ingest such information. A port will need to be opened through the firewall.   Integration with web and GIS. DataWise comes standard with a Web server which allows access to all displays, both tabular and graphic (including realtime updating graphic) displays, using a standard browser. The DataWise Web server code can be modified / customized by any web programmer if desired. GIS integration has been done through a RDB. Best to talk about this on the phone or in person.

 

 

2.0 GETTING STARTED

This chapter explains what data you need to get started, how to install DataWise® and how to create a database and how to configure the database for your system. It also tells you how to start and run the program. Because this is the foundation for DataWise® successfully running with your system and providing the critical functions you need, it is very important that you set up the system completely and accurately. Before ever installing DataWise® or working with the database, you will need to know what DataWise® needs to operate successfully and to know that your system meets these needs. You must also have data about your system with you as you sit down to configure DataWise®. Section 2.1 explains what you will need to install and configure DataWise® successfully. Throughout the remainder of this chapter, for each task, the User’s Manual reiterates what data you will need to perform tasks in that section.

 

2.1 WHAT YOU NEED

Before getting started, and to configure DataWise® for use, you will need to have the following:

• Windows NT 4.00, Windows 2000, Windows XP or Windows Vista installed on your computer.
• Minimum of 512MB of available RAM or 1GB if using Vista.
• Minimum of 250MB of available hard-disk space.
• A working knowledge of how to work in Windows-based applications.

In addition, DataWise® is distributed on CD-ROM or Zip disks (herein called the install disk). Therefore, you must have a CD-ROM or Zip Drive.

To follow the steps in this section for installing, running and configuring DataWise®, you will need the following data about your system close at hand.

• List of Sensors for which you are collecting data.
• If you are using an ALERT system, you need to have a list of the sensors, IDs, and types of sensors, which the ALERT system is using.
• If you are not using an ALERT system, you will need to know what types of sensors you are using and how many. You will need to develop your own numbering scheme for ID, sensor name and sensor abbreviation.
• You will also need to know the engineering factors needed to take raw data received from a sensor and convert it to engineering units. For example, some equipment may send in a raw value of 123 for river level and the level is actually 1.23 feet; therefore, you would need to divide by 100. Or sometimes some equipment is not capable of sending a large enough number to represent the actual value it is measuring so you might have to add a constant value to it. The real value may be 101.23 feet. But you would get 123, so you would have to divide by 100, then add 100. This data must be obtained from the hardware vendor documentation or field technician.
• Types of Alarms you want, including information on timing (how often) and to which sensors you want them to apply. You will need to know how your want the Alarms to take affect (visual, auditory, paging, etc.).
• Types of stations in your system and which sensors are associated with a given station.
• Types of communication media (for example, whether you use telephone, radio, or hardwire communications media).

 

2.2 INSTALL DATAWISE®

DataWise® can be loaded from a CD-ROM or Zip disk (herein called Installation Disk).

To install DataWise®, place your Installation Disk in the appropriate drive then follow the steps below to install DataWise®.

INSTALL DataWise®.	CHOOSE Start >Run. SELECT the appropriate Drive letter for your CD-ROM or other drive which contains your DataWise® installation disk.
		DOUBLE CLICK on the file labeled dwinstall.exe.                 NOTE if you get this message saying " TZ Environment Variable Not Set ”, you may continue with the installation, then follow instructions in Section 2.3 for setting the TZ Environment Variable.   SELECT the Drive where you want DataWise® installed.   CLICK on New DataWise® Install.
	CLICK on Yes to continue with the installation.       DataWise® will then be installed on your system.

The DataWise® installation program does not automatically create a shortcut. To create a shortcut, follow the steps below.

 

CREATE A SHORTCUT to the Main DataWise® Menu	GO TO c:\dw\utils\menu.exe
	CLICK the right mouse button on the menu.exe file.
	SELECT New Shortcut. A Shortcut to the menu file is created at the bottom of the folder.
	CLICK & DRAG the Shortcut to your desktop.

 

 

 

2.2.1 INSTALLING DATAWISE® AS A SERVICE

INSTALLing DataWise® as a Service From Start / Stop Screen	CLICK the on the Start/Stop System icon on the Main DataWise® screen. The Start/Stop screen is displayed.
	SELECT the desired DataWise® Service State: Automatic if you want DataWise® to start at system boot up and continue to run whether or not users are logged in. Manual if you prefer to start the service manually. Disabled if you want to disable the service. Not Installed if you do not want DataWise® to run as a service.     An information screen will appear saying, "Service Put into Automated Mode" if you selected Automatic. DataWise® will now start up at system boot. "or" "Service Put into Manual Mode" if you selected Manual. In this case you will need to start the service manually.
	SELECT the "When running DataWise® As a Service" method desired. The preferred method should be to run under the Local System account. There are times when this is not possible, and those cases are if DW must connect to a relational database OR must access network resources. In that case, if DataWise® is running as a service it must run under an account that has access to the required resources. CLICK on the "Save" button to save your selection.

INSTALLing DataWise® as a Service Manual Setup	Bring up a "command prompt" and change directories to \DW\Utils EXECUTE "installdwservice -install [d=drive]" Where drive is the drive on which DataWise® is installed (default drive is C:\)
	CHOOSE Administrative Tools then Services from the Control Panel.
	RIGHT CLICK on "DataWise" to set the properties to be: Startup type to Automatic Logon as Local System Allow the service to interact with the desktop
DataWise® will now be installed as a service. It will start at system boot up time and continue to run whether or not users are logged in. Alarms will be properly generated and displayed.

 

 

2.3 RUN DATAWISE®

To run DataWise® the first time, follow the steps below. If running under Windows NT, XP, or 2000 this step is unnecessary provided the TZ Environment Variable has been set. If it has not been set then go to Control Panel > System > Advanced. Click on Environment Variables. Under System Variables, click on New. For Variable name enter TZ. For Variable Value enter time zone variable in this format. First 3 characters are the time zone name (ex. PST for Pacific Standard Time). Next is the # of hours earlier that your time zone is from Greenwich Time. Next if you want to automatically change to and from Daylight Savings time, you must enter the abbreviation for your local daylight savings time zone, ex. PDT for Pacific Daylight Time, EDT for Eastern Daylight Time or MDT for Mountain Daylight time, etc. For example, if you are on Pacific Standard Time and want to change automatically to and from Daylight Savings Time, you would enter PST8PDT for the variable value. If running under any other operating system follow the steps below.

RUN DataWise® for the first time.

DOUBLE CLICK on the menu Shortcut you created. This will open the program to the Set Time Zone Variable screen. CLICK on Yes. the Set Time Zone screen will be displayed.   ENTER your correct Time Zone Variable. This allows DataWise® software to compute the difference between GMT and local time. .

 

After this first setup, to run DataWise® at any time, follow the steps below.

RUN DataWise®.	DOUBLE CLICK on the menu Shortcut you created. This opens the program to the Main DataWise® Menu, shown below. On the menu is a series of 11 icons. The last icon looks like an alarm clock. This is the Start/Stop System icon.
	CLICK the on the Start/Stop System icon. The Start/Stop DataWise® screen is displayed.



CLICK on the Push To Start button. You get the following message if done correctly: DataWise® is Running. CLICK on Exit, but DataWise® continues to run even after exiting. NOTE To stop DataWise®, you must go back into the Main DataWise® Menu, CLICK on Stop/Start icon; and SELECT Push to Stop.

 

 

2.4 CONFIGURE DATAWISE®

After DataWise® has been installed, there are five basic tasks (each with an associated set of steps) to initially configure DataWise® to function with your system.

• Define Data Collection Sources
• Define Sensors
• Define Simple Sensor Alarms (Note, simple and complex alarms may be set up initially or may be added at a later time).
• Define Stations

Steps for these five basic tasks are provided in the following sections. Each section will tell you what data you will need available to configure the system for that task.

 

2.4.1 DEFINE DATA COLLECTION ACTIVITIES

Defining your collection sources correctly is critical to make DataWise® work effectively. You also will need to become familiar with the Real-time Data Collection Task Editor, shown below, which is the primary tool for defining data collection activities.

DEFINE Data Collection Sources.

From the Main DataWise® Menu Choose Configure > Data Collection Activities. This starts the Real-time Data Collection Task Editor.

Before giving you the steps needed to define data collection sources (in section 2.4.1.5), the following subsections breakdown and give you an overview of the major functions of the Real-time Data Collection Task Editor. These include:

• Process Description (Enabling, Editing) - Most of the process descriptions are fairly straightforward and require simple explanations. Therefore, these are described in subsection 2.4.1.1.
• Process Description - GOES Data Collection Methods (Enabling, Editing) - While listed as a Process Description, GOES Data Collection Methods, is more detailed to configure and is, therefore addressed in its own subsection, 2.4.1.2.
• Hot Stand-by/Task Lists to Edit - Hot Stand-by/Task Lists to Edit are for those users who have redundant or back-up systems as well as their main system. If you do not have a redundant system, you may skip this subsection (2.4.1.3).
• Custom Command - Custom Command and Custom Command Argument are for users who wish to design and add functions to interface with DataWise®. If you are not adding custom applications to DataWise®, you may skip this subsection 2.4.1.4.

Subsection 2.4.1.5 contains the steps for using the information in subsections 2.4.1.1 through 2.4.1.4 to configure DataWise® for data collection activities for your system.

 

2.4.1.1 Process Descriptions

The first column of the screen is the Process Descriptions. Below the screen is a brief description of each of the processes listed under Process Description. Notice the second column labeled Enabled. Grayed out items are activities that are always started and cannot be disabled. When you set up your system, only click on those functions required by your system configuration.

Note

All Inter-Process Communication (IPC) occurs through either the named pipe of socket mechanism.

Below is an explanation of each of the items in the Process Description column.

• Database Manager – performs all reading/writing of the real-time sensor database.
• Data Filing Manager – performs all real-time data acquisition processes pass acquired data to this process for filing into the real-time database. This process is responsible for ensuring data is properly inserted (time-sequenced wise) into the database, and that older data is properly stored in the long-term (or archived) database. In addition, this program is responsible for the checking of simple alarm criteria.
• Real-time Data Updating – allows many custom displays and applications to be informed when new date is received by DataWise®. This process receives requests from applications that wish to receive such data and then distributes incoming data to all processes that requested it.
• Incoming Data Buffering – during periods of high volumes of data being received, temporarily buffers incoming data before being passed on to the Data Filing Manager.
• Alarm Manager – responsible for the distribution of alarms to the proper destinations as specified by the System Manager.
• Statistical Manager – computes statistics on data from the real-time and historical database for use in all tabular and graphical displays; thus, providing consistent results for all applications.
• Scheduler – allows periodic execution of programs to be scheduled (i.e., reports, data transfers, etc.).
• Pager – allows pager messages to be generated and distributed based upon sensor alarms.
• Real-time Equations – allows derived sensor values to be computed based on instantaneous values from one or more observed sensors.
• Statistical Equations – allows derived sensor values to be computed based on time averages.
• ALERT Data Collection – allows configuration of the system to collect ALERT data on one or more ports.
• Network Station Manager – allows communication (telephone, radio, etc.) with all supported RTUs, DCPs, data loggers, etc.
• Automatic Station Interrogation – must be run together with the network station manager. This process controls the timed interrogation of all remote stations.
• Headwater Forecasting – enables headwater forecasting to be performed using the Sacramento Soil Moisture Accounting Model.
• Channel/Reservoir Forecasting – enables channel and reservoir forecasting using various channel and reservoir routing techniques.
• Map Display – allows you to configure an interface to a wall display.
• Rules Based Expert System –
• Campbell Loggernet – interfaces to Campbell Loggernet base station software.
• GOES Data Collection Methods – enables reception of DOMSAT data (see Section 2.4.1.2 for more information on this process).

The third column is for Debug. Debug allows debug messages to go to the system diagnostics screen. In Tools, you can go to the diagnostic screen and see output from the debug screen. There are different debug messages for each process.

• In ALERT, you will see if the port receiving data is operating correctly or if there are errors.
• In Satellite, the system tells if communications with the satellites are functioning, if data is coming in and what data is arriving. If no data is coming in, the system will advise there is a problem.
• In Telephone Dial-up, the system will advise if the modem is working and if it is connecting at the right speed.

 

 

2.4.1.2 Process Descriptions – GOES Data Collection Methods

Note

If you are not using DOMSAT in your system, proceed to the steps in Section 2.4.1.3. If you are using DOMSAT, read this section carefully before continuing.

The last process to be configured from the Real-time Data Collection Task Editor is GOES Data Collection Methods. GOES is extremely complex; however, if you are using it, you must configure it at this time to ensure proper operation of your system. Before configuring your system for DOMSAT, become familiar with the GOES Data Collection Setup screen shown below and the following discussions of its fields. Note that some of these fields are configuring receiving data and some are configuring [output] data to be sent to other stations or users.



• Raw Data via Socket Options Field – allows DataWise® to act as a data director (that is, it receives a steady stream data, extracts messages, and passes it onto other points via sockets without processing). The socket numbers are TCIP/IP numbers.
• SHEF-Encoded out Serial Port Options – allows DataWise® to send SHEF (standard hydrologic exchange format) encoded data out serial ports to other users. This is a standard data format, which is available to most users and allows others to receive your data, have an ability to decode it and use it in other ways.
• SHEF Data via Socket Options – allows DataWise® to send SHEF-encoded data out socket ports. You may select both Serial Port and Socket Port options at the same time. You may also store SHEF data in a file in a directory.
• Vitel DRGS – allows a user to receive data through a Vitel direct read-out ground station (i.e., via a GOES system).
• Data By Sensor ID via Sockets – allows decoded data to be passed out through a socket in ASCII strings.
• Battery Data via Sockets – For all DCP's received, if battery data is transmitted in message, then it is extracted and sent to specified socket.
• Sutron DRGS – allows a user to receive data through a Sutron direct read-out ground station (i.e., via a GOES system).
• High Sierra Electronics DRGS - allows a user to receive data through a High Sierra Electronics direct read-out ground station (i.e., via a GOES system).
• Store only defined DCPs – DOMSAT allows you to receive all transmissions from DCPs in the Western Hemisphere. DataWise® allows you to keep a log of DCPs. You may keep all the DCPs or you may keep just DCPs associated with the stations defined in your system. This function is enabled via a toggle switch. (Note: This is a circular file. If you choose all, the history is shorter because as new data comes in, it will replace the oldest data.) This allows you to view your transmissions for efficiency or problems.
• SHEF Output to GMT – This allows you to output the time tag in GMT instead of local time.
• Exit and re-start on error – If the EICON card (which receives the DOMSAT data) exhibits failures, DataWise® automatically stops the card, exits the system and restarts. The system log keeps a record of restarts. To review for possible errors, check the system log. (See Section 5.9 for viewing system log.)

 

 

 

2.4.1.3 Hot Stand-by/Task Lists to Edit

Note

If you are not set up with a redundant system, proceed to the steps after this discussion. If you are set up for redundancy, read this section carefully before continuing.

In addition to the processes you configure using the Realtime Data Collection Task Editor, this editor allows you to configure another very important function: setting your system up for redundancy or Hot Stand-by. The Hot Stand-by and Task List to Edit fields of the Task Editor screen are used together to configure DataWise® for redundancy as shown on the screen below.

Hot Standby is part of the computer back-up functions and, when configured, allows a hot stand-by system to take over if the master fails. Task List to Edit allows you to specify the master/slave relationship within your system.   Note If you have a stand-alone system, ONLY SELECT Master (Stand-Alone) and go to Section 2.4.1.5.

As with any computer and communication mechanism, there is always the possibility (albeit fairly remote) that either the computer or communications for data acquisition will fail. To provide for a computer or communication failure, DataWise® can be configured to operate in a Hot Stand-by and/or redundant database environment. The system is designed to function as follows:

• One computer is designated as the master and one as the slave. Communications between the two is over a standard Ethernet LAN using both the socket and named pipe mechanisms. At all times, both computers maintain active databases. Under normal operating conditions the databases are maintained in an identical state. Every write to the database on the master is mirrored on the slave. The tasks to be performed in the system as a whole can be divided between the two computers in nearly any way desired.
• The simplest and most straightforward configuration is for the master to perform all data acquisition, controls, and alarming functions and for the slave to solely maintain a mirrored database. Then, in the case of the failure of the master, the slave will smoothly begin performing all functions previously being performed by the master.
• The most complex case would be one in which both the master and slave perform all functions identically and concurrently and check with each other at every step to verify that the same data, alarm, and control is being collected and/or produced. Differences are resolved and then the master carries out any control or alarm. If the master fails, the slave is already performing all functions and continues to do so with no break in system functionality.
• For ease in maintenance and to keep the radio and telephone communications to a minimum, the District’s network will be configured in the simplest manner. This will provide the District with a completely redundant database and failover to the slave in one minute should the master fail.

For the SWFWMD, failover works as follows:

• In normal operating conditions, the District’s master (SCADASRV1) acts nearly like a standalone system except in the following ways:
• A network connection is made between the master and the slave (SCADASRV2) so that every write to the database on the master is mirrored on the slave.
• A network connection is made between the master and the slave over which the master keeps the times of the two computers synchronized and to generally keep track of the state of the slave. If communications with the slave are lost or the slave appears to be malfunctioning the master generates an appropriate alarm and attempts to re-establish communications. No other functions being performed by the master are affected.
• Failures in SCADASRV1’s data communication equipment are handled as follows:

 

• If serial port communications between SCADASRV1 and its primary CTU are correctly functioning but radio communications between the primary CTU and remote RTUs have failed, then the master performs the following procedures:
• An alarm is generated indicating failure of CTU1.
• The ID of CTU1 is changed from 1000 to 400.
• The ID of CTU2 is changed from 500 to 1000 (assuming the serial port communications with it are functional). This also requires that the line number for all RTU-0850’s be changed from 1 to 2. This function is performed automatically at the time CTU2’s id is changed from 500 to 1000.
• An attempt is made to communicate through CTU2 to one or more of the District’s repeaters. If successful, the system continues in this state until communications with CTU1 are restored, at which time the system reverts to its previous state.
• If CTU2 is also found to be non-functional or fails while it is in active backup mode, then SCADASRV1 instructs SCADASRV2 to become the master and SCADASRV1 takes on the role of slave, thus reversing their roles.
• If serial port communications between SCADASRV1 and its primary CTU fails, then the SCADASRV1 performs the following procedures:
• First, an alarm is generated indicating failure in communications with the primary CTU.
• Then, since the state of the primary CTU is not determinable through serial port communications, it must be determined if the primary CTU is still communicating with the radio network. If it is, its ID must be set from 1000 to some other value that will not conflict with the secondary CTU when its ID is set to 1000. To do this, the master attempts to communicate with the primary CTU through the secondary CTU over the radio network through one of the District’s repeaters (actually, if the first repeater fails, a secondary path is tried). If the primary CTU is alive, SCADASRV1 will reset its id to 400 and then set the id of the secondary CTU to 1000. The master also changes the line numbers for all RTU-0850s from 1 to 2. Again, the system will continue in this state until communications with CTU1 are restored, at which time the system will revert to its previous state. If the master is unable to communicate with the primary CTU in this method, an assumption is made that the master CTU is non-functional and the secondary CTU has its id changed from 500 to 1000 and it then takes on the role of the primary CTU.
• Again, if CTU2 is also found to be non-functional or fails while it is in active backup mode, then SCADASRV1 instructs SCADASRV2 to become the master and SCADASRV1 takes on the role of slave, thus reversing their roles.
• If either modem 1 (Operating on DataWise® line 3) or modem 2 (Operating on DataWise® line 4) becomes inoperable, an alarm is generated enunciating the problem. All stations being interrogated on the modem that fails will be interrogated on the remaining modem. In the case that both modems fail, then SCADASRV1 instructs SCADASRV2 to become the master and SCADASRV1 takes on the role of slave, thus reversing their roles.
• In normal operating conditions, the District’s slave (SCADASRV2) performs only two functions:
• Over the network connection established between its database manager and the master’s, it maintains a database identical to the master’s.
• Over the network connection between the master and the slave, the slave monitors the health of the master. If the connection is broken or communications with the master fail for any reason, the slave prepares to failover and assume the responsibilities of the master. First, the slave transforms itself into a stand-alone mode and generates an appropriate alarm. Then, it attempts to communicate with the master over the CTU-0850 radio link to attempt to verify if the master is really still running and it is just the LAN that failed or if the master is really down. If the slave is able to properly communicate with the master over the radio network, then it will not go into failover mode but will continue to monitor the master through the radio system. If no communications with the master through the radio are possible then the slave assumes that the master has failed and then immediately goes into failover mode, taking over all functions previously being performed by the master.
• Before taking over the radio data acquisition duties, SCADASRV2 will attempt to determine if either of the CTUs attached to SCADASRV1 is still functional and has an id of 1000. If a functional CTU with id of 1000 is detected, SCADASRV2 will set that id to 450, since it has no clear way of knowing if the active CTU on SCADASRV1 was the primary or secondary.
• On recovery from a failure of the master, the database on the master must be re-synchronized with that on the slave. Therefore, when the master recovers from a failure, it first goes into a mode where the slave continues to act as the master until the databases are re-synchronized and then at that point the system will revert to its normal state.

 

 

2.4.1.4 Custom Commands

The Custom Command and Custom Command Arguments work together to allow you to develop your own software and integrate it into the DataWise® system.

Custom Command allows you to write your own application and integrate them into DataWise®. You may define this application or DEC Data Systems® will create the interface for you.	Custom Command Arguments tell the system from which port to access the outside data defined by the customer.

 

 

 

2.4.1.5 Steps for Configuring Data Collection Activities

Now that you are familiar with the Real-time Data Collection Screen, follow the steps below to Define Data Collection Sources.

 

 

 

DEFINE Data Collection Sources.	CLICK on the DataWise® shortcut. The Main DataWise® Menu screen is displayed.
	Choose Configure > Data Collection Activities. This starts the Real-time Data Collection Task Editor.
ENABLE and EDIT Processes you wish to activate by CLICKing on the boxes in the Enabled column. Choices allow you to configure DataWise® for each of the processes selected. Note The grayed out processes are totally self-configured.	CLICK on the Enabled box for Scheduler. Note You only need to enable Scheduler to get set up and only if you need to schedule execution of activities. You can also schedule functions using non- DataWise® applications. Later you may configure the Scheduler from the Main DataWise® Menu. Steps are provided in section 9.11
	CLICK on the Enabled box for Pager. Note You only need to enable Pager to get set up. The Pager Manager is required only if you desire to contact personnel via an alphanumeric pager when an alarm condition occurs. Later you may configure the Pager from the Main DataWise® Menu. Steps are provided in section 4.0.
	CLICK on the Enabled box for Real-time Sensor Equations. Note You only need to enable Real-time Sensor Equations to get set up. Real-time Sensor Equations are needed only when you want to compute derived sensor data values. This is done in real-time as data is received. Later you may configure the Real-time Sensor Equations from the Main DataWise® Menu. Steps are provided in section 3.2.1.
	CLICK on the Enabled box for Statistical Equation Computations. Note You only need to enable Statistical Equation Computations to get set up. As with Real-time Sensor Equations, Statistical Equations are used to compute derived sensor values, such as daily or hourly averages. Enable this option only if you need to perform this function. Later you may configure the Statistical Equation Computations from the Main DataWise® Menu. These steps are provided in section 3.2.2.
	CONFIGURE the software for ALERT Data Collection by following the steps below: CLICK on the Enabled box for the ALERT Data Collection item. CLICK on Edit for the ALERT Collection item to specify communication ports to receive ALERT data. The Define ALERT Data Collection Activities screen is displayed. For each Com Port used do the following: CLICK on Add the AddAlertPort screen is displayed.
	SELECT a port from the Com Ports field. SELECT the Baud Rate for the selected port. CHECK Sensor Mapping if you want to store data under a different ID number (when a duplicate sensor ID number is coming from different serial ports). CLICK on the Edit Mapping File button to bring up the Sensor Mapping File screen, which allows you to update sensor mapping.       CLICK on Add to add a sensor mapping entry CLICK on Edit to edit a sensor mapping entry. CLICK on Delete to delete an entry.                       CHECK Valid Sensor Checking to configure your system to prevent ALERT data from being erroneously stored in a database for non-ALERT sensors. CLICK on the Edit Checking File button to the right to bring up the Configure Valid ID screen.       Use this screen to define valid ALERT Sensors IDs by Individual ID or Range. CLICK on Save and Done to return to the AddAlertPort screen.       CHECK the HSE Transmitter Enabled box to enable High Sierra Electronics transmitters Note Add as many ALERT ports as needed in this manner. ALERT data can be collected simultaneously on up to 255 ports at a time, with separate baud rates for each port. CLICK on OK to return to the Define ALERT Data Collection Activities screen.   CHECK Alarm on no data and SELECT the number of desired minutes before alarm on no data. CLICK on Configure outgoing ALERT data to bring up the Configure Outgoing Ports screen.   CLICK on Add, Edit, or Delete to add, edit, or delete IP Address and associated port. CLICK on SAVE and Done to return to the Define ALERT Data Collection Activities screen.     CLICK on Configure UDP connections to bring up the UDP screen.           CLICK on Add, Edit, or Delete to configure IP addresses to accept UDP (User Datagram Protocol) datagrams from.   CLICK on OK to return to the Define ALERT Data Collection Activities screen.   CLICK on Save and Done to return to the Realtime Data Collection Task Editor screen.
	CONFIGURE the software for Network Station Manager. CLICK on the Enabled box for the Network Station Manager.
	CLICK on the Edit box for the Network Station Manager. The Network Station Manager Ports screen is displayed. Ports Available: SELECT a port from the Ports box and CLICK on Add; this shifts port to Ports Used. Ports Used: ports selected are displayed. Baud Rate: SELECT a Baud Rate from the pull-down menu for selected port. Choices are from 110 to 115200. Port Type: SELECT a Port Type from the pull down menu. Choices are: Direct – used for ports, which are hard wired directly from the computer to the RTU. This does NOT include SM-0850. RTU-0850 – used only when communicating with a Sierra-Misco RTU-0850. Modem – used for data collection via dial-up modems. Slow – used for RTU-0850 protocol over satellite links where response is significantly slower than over a direct connection. Radio Modem - Teledesign Radio Modem - ESTeem Sutron SSP Modbus Serial Modem Pseudo Leased Line GPRS (Sockets) GPRS Direct Connect CHECK Enable Debug Log if desired. CHECK Enable Sockets if desired. SELECT Wait time in seconds. CLICK on OK to save your changes and return to the Real-time Data Collection Task Editor.
	CONFIGURE the software for Automatic Station Interrogation. CLICK on the Enabled box for Automatic Station Interrogation.
	CLICK on Edit box for Automatic Station Interrogation. The Automatic Interrogation Properties screen is displayed. ENTER the Wait time (minutes) using the up/down arrows. This is the time before beginning the automatic interrogation cycle. ENTER the Cycle time (minutes) using the up/down arrows. This is how often to check if it is time for a station to be automatically interrogated. CHOOSE the Type of polling you want by clicking one of the choices shown. CLICK on the Immediate Interrogations box if you want the system to not wait until the next scheduled interrogation. DataWise® goes through and looks for all the stations that have not been interrogated recently. CLICK on Use local station manager if desired. CLICK on Poll Stations from List if you want to poll stations from a defined list. CLICK on Edit Polling List to edit this list. The Editing File \DW\Config\auto_poll.cfg screen is displayed. Select the stations to be polled from the list of defined stations. CLICK on Save to save your changes and Done to go back to the Automatic Interrogation Properties screen. CLICK on Disable multi-socket polling if you want to disable multi-socket polling. CLICK on OK to save your changes and go back to the Real-time Data Collection Task Editor.
	CLICK on the Enabled box for Headwater Forecasting. Currently, this option (automated headwater forecasting) enables the periodic execution of the Sacramento Soil Moisture Accounting (SSMA) model for computing watershed runoff. In many cases, the SSMA is all that is required. In more complex situations, routing may be required. CLICK on the Edit box for Headwater Forecasting. The Forecast Options screen is displayed. SELECT the Frequency to Check and Wait time for execution. SELECT the Number of days back to restart. Note Headwater Forecasting is configured elsewhere in DataWise®. See Section 6.1.
	CLICK on the Enabled box for Channel/Reservoir Forecasting. In situations where simple watershed modeling is not sufficient to accurately model the hydrology, channel/reservoir modeling needs to be implemented. The channel routing currently is being used in a layer K&L method. CLICK on the Edit box for Channel/Reservoir Forecasting. The Forecast Options screen is displayed. SELECT the Frequency to Check and Wait time for execution. Note Channel/Reservoir Forecasting requires Headwater Forecasting to be enabled. Channel/ Reservoir Forecasting is configured elsewhere in DataWise®. See Section 6.2.
	CONFIGURE the software for Map Display. This is used if you want your system to communicate with a wall map. CLICK on the Enabled box for Map Display.
	CLICK on Edit box for Map Display. The Map Display Port Setup screen is displayed. Ports: SELECT a port from the Ports box and CLICK on Add; this shifts port to Ports Used. Ports Used: To remove a port, SELECT a port by HIGHLIGHTing it and CLICKing on Remove; this shifts the selected port to the Ports box. CLICK on OK to save your changes and go back to the Real-time Data Collection Task Editor.
	CONFIGURE the software for Rules-Based Expert System. CLICK on the Enabled box for Rules-Based Expert System.
	CLICK on the Edit box for the Rules-Based Expert System. The Expert Options screen is displayed. CLICK on Default; to select the default Expert Rules file. Or CLICK on Browse to browse for another file. SELECT the Rule Evaluation Frequency in seconds. CHECK Execute on change of state only if this is desired. CHECK the Enable Debug Output if desired. CLICK on OK to save your changes and return to the Real-time Data Collection Task Editor.
	CONFIGURE the software for Campbell Loggernet. CLICK on the Enabled box for Campbell Loggernet Interface.
	CLICK on the Edit box for Campbell Loggernet Interface. The Campbell Loggernet Configuration screen is displayed. ENTER Username (this is set up with the supplier providing you the Campbell Loggernet software). ENTER Password. (Leave this blank unless your system administrator has given you a password.) SELECT the Cycle Time (minutes) (how often you want to look for new data) by using the pull-down arrows. SELECT the Retrieval Period (minutes) (how far back you want to go to search for data). ENTER the Socket Port Number (this is the port the Loggernet software is set up to communicate on. It’s configured from the Loggernet software by the system administrator. SELECT Concurrent Interrogations if desired.
	CONFIGURE the software for GOES Data Collection Methods. CLICK on the Enabled box for GOES Data Collection Methods. CLICK on the Edit box for GOES Data Collection Methods. The GOES Data Collection Setup screen is displayed.
	SELECT the option which applies to your system by CLICKing on the Active box for that option. Choices are: Raw Data via Socket Options SHEF-Encoded out Serial Port Options SHEF Data via Socket Options Vitel DRGS: If you have a Vitel system, click Active on Vitel DRGS and disable DOMSAT. This allows you to receive data only through Vitel’s downlink, which comes via serial port. You must specify a Comm Port and Baud Rate. If you click Active, but do not disable DOMSAT, you may receive data from both sources. Data by Sensor ID via Sockets Battery Data via Sockets Sutron DRGS: If you have a Sutron system, click Active on Sutron DRGS and disable DOMSAT. This allows you to receive data only through Sutron’s downlink which comes via serial port. You must specify a Comm Port and Baud Rate. If you click Active, but do not disable DOMSAT, you may receive data from both sources.
	High Sierra Electronics DRGS: If you have a High Sierra Electronics system, click Active on High Sierra Electronics DRGS and disable DOMSAT. CLICK on Click to Edit Configuration to allow configuration of the High Sierra DEMODS. (As shown here)         Domsat via Eicon or Sangoma: Store only defined DCPs: SHEF Output to GMT: Exit and re-start on error:
CONFIGURE the Hot Stand-by and associated Task List to Edit capability.	If you do not have a redundant system or if the Hot Stand-by (Slave) computer has failed, SELECT Master (Stand-Alone). Note DataWise® defaults to Master (Stand-Alone) if a Hot Stand-by condition is not defined.       SELECT Master when: Your system has both a Master computer and a Hot Stand-by or Slave computer, Both systems are operational, You are configuring the Master computer. The Master and Slave computers are continuously communicating via the LAN to check on each other’s health. DataWise® keeps the Master and Slave databases synchronized. Also, the Master keeps the Slave clock synchronized to its own clock every five seconds. If the Master computer fails, DataWise® automatically reconfigures to Slave (Stand-alone). When you CLICK on Master, DataWise® reconfigures the Real-time Data Collection Task Editor to let you edit the tasks for the Master in a Hot Standby configuration. SELECT Slave (Stand-Alone) when you are configuring your Slave computer to set it up in case of failure of the Master. If the Master fails, DataWise® reverts to Slave (Stand-alone). SELECT Slave when both the Master and Slave are operating correctly and when you are updating or configuring Slave functions, which are performed when Slave is in Hot Standby (waiting to take over for Master but operating correctly). If the Slave fails, DataWise® reverts to Master (Stand-alone).
CONFIGURE the Debug capability for each of the Processes you have enabled.	CliCK on the box in the Debug column for Process Descriptions for which you wish to activate debug capability.
CONFIGURE Hot Standby if applicable to your system.	CliCK on Redundancy Enabled if you have a Hot Standby system.
	CliCK on Edit Configuration. The Hot Standby Configuration screen is displayed. ENTER the name of your Hot Standby Primary Server. ENTER the name of your Hot Standby Backup Server. CliCK on OK.
CONFIGURE Custom Command	ENTER the command you have defined to execute your custom application. Note For most locations, the standard DataWise® set up will work and this will not be applicable. Also, there are no format limitations, but the command has to be to call an executable program and the program must reside in the \dw\utils directory.
	ENTER the Custom Command Arguments. This is only needed if a custom command is used.
	CLICK on Save and then Done when all data collection activities have been satisfactorily specified.

 

 

 

2.4.2 DEFINE SENSORS

Sensors must be defined in the database before incoming data can be stored. To define sensors, you will need to have the following information available.

• You will need to understand the type of telemetry you are using.
• If you are using an ALERT system, you need to have a list of the sensors, IDs and types that the ALERT system is using.
• If you are not using an ALERT system, you will still need to know what types of sensor you are using and how many. Then you can make up your own numbering scheme for ID, sensor name and sensor abbreviation.
• For each sensor, you will need to know the engineering factors needed to take raw data received from a sensor and convert it to engineering units. For example, some equipment may send in a raw value of 123 for river level and the level is actually 1.23 feet; therefore, you would need to divide by 100. Or sometimes equipment is not capable of sending a large enough number so you might have to add a constant value to it. The real value may be 101.23 feet. But you would get 123, so you would have to divide by 100, then add 100. This data must be obtained from the hardware vendor documentation or, depending on the hardware, this can be custom; however, you will need to know your custom engineering factors.
• For each sensor, you should have a longitude and latitude. If not properly entered, most mapping functions will not display the sensor.
• For each sensor, you must know the cycle size, maximum jump between consecutive readings (basically used to filter out bad data and especially important in ALERT systems which often send erroneous data and large jumps in frequency of interrogation/reporting).

Note:

In an ALERT system, sensors report an identifier (0-8191) and a data value (0-4095). The sensor ID that is transmitted by an ALERT transmitter is the ID that the data will be stored under in DataWise® unless a sensor mapping files was defined.

 

To define sensors, follow the steps below.

DEFINE a new sensor.	START DataWise® and CHOOSE Configure > Sensors from the Main DataWise® Menu. The Define Sensors screen is displayed. ENTER the first sensor ID number in the Sensor ID field. For non-ALERT systems, you may define your own sensor ID. The sensor ID is numeric and can be any number from 1 to 32,000. ALERT sensors can only send up to 8191 for sensor ID and you must use the ID defined for the ALERT sensor unless sensor mapping has been defined.
	ENTER the first sensor name. You may provide your own sensor names. Sensor names may be alphanumeric and up to 20 characters. ENTER an abbreviation for the first sensor. Sensor abbreviations are short names to be associated with the sensor. You may define your own sensor abbreviation. Sensor abbreviations may be alphanumeric and up to 8 characters.
	ENTER the Type of sensor being defined by SELECTing from the drop-down list, which includes: Stream_Gage_Float Temperature_Sensor Precipitation_Gage Wind_Run Wind_Sensor Relative_Humidity Barometric_Pressure Stream_Gage_PT HEC1_Flows Stream_Sonic_Reader Wind_Speed/Direction Wind_Direction Repeater_Battery_Charge RTU 850_Battery Gate_Position Temperature_Sensor_Air Temperature_Sensor_Water Road_Conductivity Peak_Wind Gate_Status_Bits Gate_Control_Output_Ports Advanced_Warning Wind_Speed   Note DataWise® comes with standard set of sensor types. New sensor types can be defined by CHOOSing File > Add/Edit Sensor Types. (See Section 3.1 on Sensor Management.)
	ENTER the Multiplier used to convert raw data into engineering units. CLICK on the Multiplier button to enter this term as a Multiplier or Divisor. For example, some equipment may send in a raw value of 123 for river level and the level is actually 1.23 feet; therefore, you would need to divide by 100. Note Calibrated data is computed from the following equations: y = 1/a * x + b Where a and b are the engineering conversion terms.
	ENTER the Adder term used to convert raw data into engineering units. This depends on how the remote units report data versus how you want to see your data. Usually the adder is zero, except for stream water level, for which you almost always need an adder. ENTER the Sensor Latitude. CLICK on North/South to correctly specify the hemisphere. ENTER the Sensor Longitude. CLICK on North/South to correctly specify the hemisphere. ENTER the Cycle Size (sometimes referred to as the raw range). This is especially important for ALERT systems in which data is transmitted in raw integer form. This value specifies the maximum valid raw data value + 1. For example, for an ALERT rain gage, the value is 2048. The value for an 8-bit analog sensor would be 256.
	ENTER the Max Jump. This is also especially important in an ALERT system in which there is a chance for missing or corrupted data. This value specifies the maximum allowed jump in consecutive sensor readings. Jumps larger than this value are treated as invalid data. In an interrogated system with error checking, this value is not very important and should be set to a very large value (or 0). ENTER the frequency at which the sensor is expected to report. If gaps in the record exist that are larger than this, then those periods are treated as missing data periods in plots and statistical reports. ENTER Optional Information. Only used in special application, not in regular DataWise® applications. ENTER HECDSS Parameters. These are used only when one or more HECDSS databases is being populated, otherwise they can be ignored. CLICK on OK when all fields have been satisfactorily filled into save the values in the database.

 

 

2.4.3 DEFINE SIMPLE SENSOR ALARMS

You may configure alarms, simple or complex, at any time. Defining alarms is not a mandatory setup function and does not need to be done at this time. Section 7.0 has a complete set of steps for defining and managing alarms. Basic set up for simple alarms is included in this set up section.

DataWise® supports an extensive array of alarm evaluation and alarm response functions. DataWise® supports up to 32,000 different types of alarm actions to be taken when an alarm occurs. Alarm actions can range from simply beeping and flashing on a computer screen to providing automated paging, faxing, or e-mail. The actions can also be as complex as actually controlling pumps and gates.

DataWise® comes standard with alphanumeric paging support for most known pagers. Supporting software is provided for any currently unsupported pager protocol. DataWise® alarm handling functions include Dectalk as well as many of the more modern speech synthesizer cards.

Alarms fall into two basic categories: Simple Alarms and Complex Alarms.

• Simple Alarms are based on conditions occurring at a single sensor. An example of a simple alarm condition is rainfall rate at a given sensor above preset conditions or water level above a certain level and still rising.
• Multiple Alarms allow multiple alarms to be set on a single sensor.
• Complex Alarms are based on conditions occurring at multiple sensors. Complex alarm conditions are actually implemented using an Expert System that has been incorporated into DataWise®. In this system, alarm conditions are entered as "IF, THEN, ELSE" statements. Very complex alarm conditions can be implemented in this manner. An example of a complex alarm evaluation would be requiring high rainfall rates at several rain gauges and the water level at one or more stream gauges above some value and the water level still rising.

To define simple sensor alarms, you must have the following data available for each sensor alarm you want to set:

• Sensor ID (to which you want to associate an alarm).
• The Upper Limit, the value at which the sensor reading crosses in the positive direction.
• The Lower Limit, the value at which the sensor reading crosses in the negative direction.
• The Rate of Rise, the change in sensor value in a positive direction. This includes:
• Amount of rise, which is the change in sensor value in a positive direction.
• Time period, linked to amount of rise is the length of time in which rise must occur to generate the alarm,
• Threshold, value at which you want the system to start checking "amount of Rise, in designated Time limit.
• The Rate of Fall, the change in sensor value in a negative direction. This includes:
• Amount of fall.
• Time period.
• Threshold.
• No Report Alarm Criteria, which is very useful in recognizing failed sensors.

For each of the above, you must:

• Define the Alarm Value,
• Choose Activate When, to display a drop-down list of :
• Never, disables actions without changing criteria—valuable during device installation and maintenance.
• Met, When you want the alarm to activate as the sensor reading crosses upper limit in a positive direction.
• Reset, when you want the alarm to activate when sensor reading crosses upper limit in a negative direction.
• Both, when you want the alarm to activate when the sensor reading crosses upper limit in a positive or negative direction.
• Define the Action, including alarm action options of 0: console alarm – audible and visual. 1:-16: user defined alarms that must be customized to meet the user’s application. One of which can be a pager (pager software is supplied in DataWise®).
• SELECT from the defined alarm actions, which allows selection from a drop-down menu. These include:
• 0 – Console – DataWise® provides a standard warning program, which always goes to the console. This is associated with a visual alarm which comes up to override any other work you are doing.
• 1 – 16 – user defined title – You may create your own warning program, DEC Data Systems may be contacted to create a program for you, or you may use one of many custom programs already developed (for example, pager and various dial-up alarms), all of which must be executed based on the program name. See Section 7.0 on Alarm Management for directions on creating your own warning programs or using a program other than that provided automatically with DataWise®.
• Define the Deadband, the value at which the alarm must exceed the alarm limit to reactivate the alarm.

To define simple sensor alarms follow the steps below. Repeat these steps for each alarm.

 

NOTE

DataWise® must be running to define sensor alarms. Ensure DataWise® is running before following the steps below.

DEFINE Simple Sensor Alarms. Note DataWise® must be running to define sensor alarms.		CHOOSE Configure > Sensors from the Main DataWise® Menu. If DataWise® is not running, the system will ask you if you want to start DataWise®. CLICK on OK. You must go back and START DataWise® after CLICKing OK.
				Once DataWise® is running and you CHOOSE Configure > Sensors from the Main DataWise® Menu, the Define Sensors screen is displayed. CHOOSE Alarms > Simple. The Simple Alarms screen is displayed.
				CLICK on Sensor or Group for a single sensor or a group of sensors, SELECT Sensor ID which should already be defined (section 2.4.2) or Group Name. Previously defined groups or sensors will be selectable from the pull-down menu. CLICK on Group Preferences to define a group. The Group Alarms screen is displayed.     CLICK on Add to add a new group. The Creating Group screen is displayed.                                  TYPE in the new Group Name and SELECT the Sensor Type from the list of available sensor types.   CLICK on OK to return to the Group Alarms screen   CLICK on EDIT to edit the selected Group or DELETE to delete a group of sensors. To ADD sensors to a selected group, HIGHLIGHT the group you wish to add sensors to in the Defined Alarm Groups field. SELECT the sensor from the list of Defined Sensors. CLICK on ADD. The added sensor will then be shown in the Sensors in Group field. You may select Add All to add all sensors to the group.   To Remove a sensor from a selected group, HIGHLIGHT the group you wish to remove a sensor from. SELECT the sensor from the Sensors in Group field. CLICK on Remove. The sensor will be removed from that group. You may select Remove All to remove all sensors from a selected group. CLICK on Save and Done to save changes and return to the Simple Alarms screen.   ENTER Upper Limit Alarm Criteria, by completing the following: ENTER Upper Limit Alarm Value. For example, if your system is looking at water level, you will need to know the high water level which is critical to your environment. Note If you want to use multiple Upper Limit Alarms, you will need to follow steps in section 7.5 to configure this for a complex alarm. SELECT Upper Limit Activate from the pull down menu. Choices are Never, Met, Reset, and Both. ENTER Upper Limit Action: 1 to 16. The system allows up to 16 alarm actions. Only the first of the 16 is fixed—this goes to the system console. Examples of other alarm actions are alarming to a pager or voice synthesizer. You may define these to meet your system setup. SELECT Upper Limit Select from the pull down menu. Choices are 0 Console or 1 through 16 if you have a user defined alarm program and this has been defined in DataWise®.
	ENTER Lower Limit Alarm Criteria, by completing the following: ENTER Lower Limit Alarm Value critical to your environment. Note If you want to use multiple Lower Limit Alarms, you will need to follow steps in section 7.5 to configure this for a complex alarm. SELECT Lower Limit Activate from the pull down menu. Choices are Never, Met, Reset, and Both. ENTER Lower Limit Action: 1 to 16. The system allows up to 16 alarm actions. Only the first of the 16 is fixed—this goes to the system console. Examples of other alarm actions are alarming to a pager or voice synthesizer. You may define these to meet your system setup. SELECT Lower Limit Select from the pull down menu. Choices are 0 Console or 1 through 16 if you have a user defined alarm program and this has been defined in DataWise®.
			ENTER Deadband AlarmValue, the value at which the alarm must exceed the alarm limit to reactivate the alarm. ENTER Rate of Rise Alarm criteria, by completing the following: ENTER Rate of Rise data for Amount of Rise by: FILLing in the Amount of Rise Alarm Value critical to your environment. SELECTing the Amount of Rise Activate When from the pull down menu. Choices are Never, Met, Reset, and Both. ENTERing in the Amount of Rise Action: 1 – 16. The system allows up to 16 alarm actions. Only the first of the 16 is fixed—this goes to the system console. Examples of other alarm actions are alarming to a pager or voice synthesizer. You may define these to meet your system setup. SELECTing the Amount of Rise Select. Choices are 0 Console or 1 through 16 if you have a user defined alarm program and this has been defined in DataWise®. ENTER the Rate of Rise Time Period by ENTERing a number for the time period you want for the rate of change in the first box and then SELECTing from a pull down menu for the period. Choices are Seconds, Minutes, Hours and Days. ENTER Rate of Rise Threshold.
				ENTER Rate of Fall Alarm criteria, by completing the following: ENTER the Amount of Fall for the Rate of Fall by: ENTERing the Amount of Fall Alarm Value critical to your environment. SELECTing the Amount of Fall Activate When from the pull down menu. Choices are Never, Met, Reset, and Both. ENTER Amount of Fall Action: 1 – 16. The system allows up to 16 alarm actions. Only the first of the 16 is fixed—this goes to the system console. Examples of other alarm actions are alarming to a pager or voice synthesizer. You may define these to meet your system setup. SELECTing the Amount of Fall Select. Choices are 0 Console or 1 through 16 if you have a user defined alarm program and this has been defined in DataWise®. ENTER Rate of Fall Time Period by ENTERing a number for the time period you want for the rate of change in the first box and then SELECTing from a pull down menu for period. Choices are Seconds, Minutes, Hours and Days. ENTER Rate of Fall Threshold.
			ENTER No Report Alarm criteria, by completing the following: Note This lets you define how long you are willing to go without sounding an alarm. ENTER No Report Time Period (under Alarm Value column) by ENTERing a number in the first box and then SELECTing from a pull down menu for period. Choices are Seconds, Minutes, Hours and Days. SELECT No Report Activate When from the pull down Menu. Choices are Never and Late. ENTER No Report Action: 1 – 16. . Only the first of the 16 is fixed—this goes to the system console. Examples of other alarm actions are alarming to a pager or voice synthesizer. You may define these to meet your system setup SELECT No Report Select. Choices are 0 Console or 1 through 16 if you have a user defined alarm program and this has been defined in DataWise®.
			CLICK on OK to save the values in the database.
			CLICK on Exit to close the screen.

Note

New alarm values are immediately valid.

 

 

2.4.4 DEFINE MULTIPLE ALARMS

This involves knowledge of DataWise® commands and requires custom work by DEC Data Systems for setting up multiple alarms. Consult Don Colton at DEC Data Systems for further information.

DEFINE Multiple Alarms.		CHOOSE Configure > Sensors from the Main DataWise® Menu. The Define Sensors screen is displayed.
				CHOOSE Alarms > Multiple. The Define Multiple Alarms screen is displayed.
				SELECT the Evaluation Frequency. This sets the frequency of evaluation on all defined alarms. CLICK on Sensor or Group for a single sensor or a group of sensors, SELECT Sensor ID which should already be defined (section 2.4.2) or Group Name. Previously defined groups or sensors will be selectable from the pull-down menu. CLICK on Group Preferences to define a group. The Group Alarms screen is displayed.     CLICK on Add to add a new group. The Creating Group screen is displayed.           TYPE in the new Group Name and SELECT the Sensor Type from the list of available sensor types. CLICK on OK to return to the Group Alarms screen       CLICK on EDIT to edit the selected Group or DELETE to delete a group of sensors. To ADD sensors to a selected group, HIGHLIGHT the group you wish to add sensors to in the Defined Alarm Groups field. SELECT the sensor from the list of Defined Sensors. CLICK on ADD. The added sensor will then be shown in the Sensors in Group field. You may select Add All to add all sensors to the group.     To Remove a sensor from a selected group, HIGHLIGHT the group you wish to remove a sensor from. SELECT the sensor from the Sensors in Group field. CLICK on Remove. The sensor will be removed from that group. You may select Remove All to remove all sensors from a selected group. CLICK on Save and Done to save changes and return to the Multiple Alarms screen.

SELECT Maximum or Minimum and INPUT a value in the corresponding EDIT field. ENTER a Deadband if desired OR SELECT Rate Of Change, Positive or Negative and INPUT a value for the AMOUNT of change PER time period. ENTER the Threshold amount. This is the level that must be reached before being concerned. SELECT an Action from the drop-down list. This should already be defined using Define Sensors > Alarms > Add/Edit Alarm actions as described in Section 2.4.5. CLICK on Set. CLICK on New to define another alarm for that sensor. CLICK on Delete to delete the selected alarm. When finished with that sensor CLICK on Save. Repeat steps above for another sensor then CLICK on Save and Exit when finished defining alarms for all desired sensors.

 

 

2.4.5 ADD OR EDIT ALARM ACTIONS

CHOOSE Configure > Sensors from the Main DataWise® Menu, the Define Sensors screen is displayed. CHOOSE Alarms > Add/Edit Alarm Actions. The Alarms Actions screen is displayed.         To Add an alarm action to be taken for any given port, HIGHLIGHT the available alarm from the list of Available alarms. CLICK on the Enabled box for the desired Action/Port #. The alarm description and executable will now be displayed in the Selected Alarms field.

To add or edit the list of Available Alarms CLICK on the Edit Available Alarms button. The Add/Edit Available Alarms box is displayed. ENTER a valid Alarm Program and a Description. CLICK OK to return to the Alarm Actions screen.     CLICK on Save and Done to save changes and return to the Define Sensors screen.

 

 

2.4.6 DEFINING CUSTOM ALARM TEXT FILES

This application is used for defining text files to be displayed on the screen for custom alarms. In order to use this you must first have a custom alarm defined for the port on which you want to create the text file as described in section 2.4.5.

CHOOSE Configure > Sensors from the Main DataWise® Menu, the Define Sensors screen is displayed.   CHOOSE Alarms > Define Custom Alarm Text. The Define Alarm Action Text Files screen is displayed.   SELECT the Alarm Action Number (Port) for the desired Alarm Action text file you wish to edit. TYPE in the message you would like to have displayed on the alarm screen. CLICK on the correct Save as button depending on which text file you are editing. Selecting Save as Instructions on Alarm Message will allow you to edit the message that will be displayed on the main alarm display screen when an alarm is activated. Selecting Save as Help on Alarms file will allow you to edit the message which will be displayed when the HELP button is pushed on the main alarm display screen. This can be an in depth instruction file telling the user what to do in case of an alarm.

 

 

2.4.7 DEFINE STATIONS

DataWise® supports the following types of stations:

• GOES Stations, including GOES NOS Tide Gage
• SM0850
• VX1100/0850
• Campbell CR10
• Handar 555
• Handar 560
• LARC (Handar 540)
• Sutron 8200 (Dialup)
• ALERT Systems
• VX1100
• VX1100 Dialup
• MCC Master Station.

Of these many types of stations, your system probably only uses a small subset. DataWise® has been configured for your system to include the station types in your system. If other station types are added to your system, contact DEC Data Systems. In DataWise®, each station type has its own setup screen. Appendix B in the Datawise Users Manual contains a complete list of station type screens and steps for setting these up. Refer to Appendix B to set up the types of stations in your system.

Before moving through the Define Stations steps, it is important that you review some basic information about defining stations. There is space in the database for 9,999 stations. The Station Setup Menu is quite extensive, see below, with 11 separate functions (each with its own icon); the twelfth icon is Exit.

Note

When you click on an icon, the icon function is listed at the bottom of the menu.



 

The Station Setup Menu functions include:

• List – Once you have defined stations or if you have imported from another database, List will show you the list of stations in the database for your systems. The list includes Station ID, Name, Type, and Last Interrogation Time.
• Add – Allows you to enter station number and station type. (The station name is entered when you Edit Station.) If you want to add a new type of station, contact DEC Data Systems®, as this will require a change to the program.
• Edit – Allows you to select a station by number and change name, type, communication parameters and other pertinent information about the station.
• Delete – Allows you to select a station and delete it.
• Setup Interrogation– Allows you to select a station and setup or change interrogation frequency and order.
• Set Last Time – This is not required unless you want to reset the interrogation time to a previous time; otherwise DataWise® maintains this for you.
• Add Control – This requires special telemetry equipment and additional software is required from DataWise®. If this is not active on your system, it is not required.
• Edit Control – This requires special telemetry equipment and additional software is required from DataWise®. If this is not active on your system, it is not required.
• Delete Control– This requires special telemetry equipment and additional software is required from DataWise®. If this is not active on your system, it is not required.
• Lock Setup – This requires special telemetry equipment and additional software is required from DataWise®. If this is not active on your system, it is not required.
• Expand Database – Allows you to expand the number of stations in the database.

Before following the Define Stations steps in this section, you should know:

• The ID assigned to each station. Some stations report by ID and you will have to use the ID to talk with it. Some stations only report by ASCII string, which means the ID can be anything you want.
• The types of stations in your configuration, and which stations are associated with which station type.
• The number of stations in your configuration.
• The interrogation frequency you want for each station, if it is a station which can be interrogated. You will need to know which stations may be interrogated and which may not (for example GOES stations may not).
• Sensors associated with each station and how each sensor is identified. Each station has a different way each sensor is attached to it. Each station can have up to 64 sensors attached to it.

Follow the steps below to define stations, expand the number of stations, and edit data associated with stations in your database.

DEFINE Stations.		CHOOSE Configure > Stations from the Main DataWise® Menu. The Station Setup Menu is displayed. If there is no station database established, DataWise® prompts you to expand the database.
		CHOOSE File > Expand Database from the Station Setup Menu or CLICK on the Expand Database icon. The Expand Station Database screen is displayed. ENTER the size that represents the total number of stations you anticipate using. Use at least 100 stations regardless of whether your system has less stations. Note The size can be expanded at a future time if current size becomes too small.
		CLICK on OK to update database station size and exit.
ADD Stations.		CHOOSE Configure > Stations from the Main DataWise® Menu. The Station Setup Menu is displayed.
		CHOOSE Stations > Add from the Station Setup Menu or CLICK on the second icon. The Add Station screen is displayed. ENTER the station ID (numeric from 1 to 32,000).
		CHOOSE the type of station from the drop-down list. You will see a list of stations usable with your software package. The list grows and/or changes over time. Note There are many types of stations and each has its own setup screen. Appendix B in the Datawise Users Manual contains a complete list of station screens and steps for setting these up. Refer to this Appendix to set up the types of stations in your system.
		CLICK on OK to add the station. Note Stations will not be functional until the parameters are properly defined by EDITing Stations.
EDIT Stations.		CHOOSE Configure > Stations from the Main DataWise® Menu. The Station Setup Menu is displayed.
		CHOOSE Stations > Edit from the Station Setup Menu or click on the third icon. The Edit Station Parameters/ Select Station screen is displayed. SELECT a station by entering its ID or by double CLICKing on the station from the pull-down list or HIGHLIGHTing the selection.
		CLICK on Edit. The [type] Station Setup screen is displayed. Note For each Station Type, a slightly different Station Setup screen is displayed. The one at the left is the box for an ALERT Station. Appendix B contains a complete description of all Station Type Setup screens. These steps will continue with an example of setting stations for an ALERT system. If not already completed, ENTER Station Name. If applicable to the type of station, ENTER Phone Number; otherwise, ENTER None. SELECT the Station Line # as defined by the network station manager setup by clicking on the up/down arrows until the desired number is displayed. SELECT the Comms Timeout by clicking on the up/down arrows until the desired number is displayed. This is the time you can reasonably expect a response before assuming connection will not be made. If you only have one repeater, you may want to set this at just a few seconds. If the communication must go through several repeaters, you may want to set this for minutes. SELECT the Maximum Tries by clicking on the up/down arrows until the desired number is displayed.
DEFINE which Sensors are at selected stations.		CLICK on Number of Sensors at bottom of the Alert Station Setup screen. This will bring up the Define ALERT Sensors screen. ADD an available sensor by following the steps below: HIGHLIGHT the desired sensor from the Sensors Available list. CLICK on Add. CLICK on OK when all the sensors for that particular station have been selected REMOVE a sensor associated with a station by following the steps below: HIGHLIGHT the desired sensor from the Sensors at Station list. CLICK on Remove. CLICK on OK when all the relevant stations have been removed.
DEFINE sensors for interrogated stations.		CHOOSE Configure > Stations from the Main DataWise® Menu to get to the Stations Setup Menu.   CHOOSE Interrogation > Setup from the Station Setup Menu or CLICK on the 5th icon which looks like a clock. The Define Station Interrogation Times screen is displayed.
		ENTER the station interrogation criteria by performing the following: SELECT a station by highlighting a station from the Select Station list. ENTER your desired Interrogation Frequency. SET Interrogation Base Time. This allows the interrogation time to be off set from the hour, according to the number of minutes entered. SET Absolute Interrogation Times. This restricts interrogation times to times you specify. ENTER Interrogation Order. The default is the order in which you defined the stations. If a different order is needed, enter the numbers to reflect the new order. If you give multiple stations the same order number, then DataWise® will interrogate in order of the station number starting with the lowest. Note The system will show the Last Interrogation Time; however, you may change this to an earlier time to manually force the system to re-interrogate. CLICK on OK.
SET Last Interrogation Time. This allows you to go back in time to retrieve old data from a station. This is very useful for automated interrogation stations.			CHOOSE Interrogation > Set Last Time from the Station Setup Menu. The Set Last Interrogation Time screen is displayed. This shows you the Station ID, Name, Type and Time of Last Interrogation. You may choose to update by a selected station or by a selected type of stations. ENTER date and time you want to set last interrogation in format mm/dd/yy hh:mm:ss.
	CHOOSE specific stations, all stations or all stations of the same type: To CHOOSE specific stations, HIGHLIGHT desired station or stations. CLICK on Update all stations selected. You will get an Update Confirmation screen as shown here. To CHOOSE all stations. CLICK on Update all stations. You will get an Update Confirmation screen as shown here. To CHOOSE all stations of a certain type, HIGHLIGHT station type from the right pull-down menu. CLICK on Update all stations of type selected. You will get an Interrogation Update Query screen as shown here. CLICK on Done to return to the Station Setup screen.

 

 

2.4.8 SHEF Configuration

Introduction

Once the sensor configuration information has been input into DataWise® and the system is collecting data, SHEF-encoded data can be transferred via the FTP mechanism to any other computer that the DataWise® data acquisition computer is able to connect to. The following documentation uses the ftp.exe that comes standard with Windows to perform the transfer.

2.4.8.1 SHEF Encoding Configuration

To configure DataWise® to transfer SHEF data via FTP, Select the "SHEF Encoding Configuration" item from the "Configure" pull-down list on the main DataWise® menu. (Figure 1.)



Figure 1. Main DataWise® menu with "SHEF Encoding Configuration" item selected.

 

Once selected, the "SHEF Configuration" screen shown in Figure 2 will be displayed.



Figure 2. Setup FTP Transfer of SHEF-Encoded Data

 

STEP 1: Setting up the ShefMap.cfg file.

To Add sensors for which data will be sent Highlight a sensor from the list of defined sensors then Select Add. The dialog box shown in Figure 3 will be displayed.



Figure 3. Adding a sensor to list.

Enter the correct SHEF ID

Enter the PEDTSEP where;

• PE - Physical Element – (two characters) This is the only portion of the PEDTSEP that is mandatory. Examples are river stage, precipitation increment, power generation, discharge;
• D - Duration code – (one character), examples are instantaneous, hourly, daily;
• T - Type or basic category of the data: Forecast - F, Historical - H, Observed - R, Processed - P, Contingency - C.
• S - Source Code – (one character which further defines the type code, indicating how values were created or transmitted), examples are satellite telemetry, land radio, visual observer;
• E – Extremum Code – (one character) examples are daily maximum, daily minimum, hourly minimum.
• P - Probability code – (rarely used) examples are 5% or 95% probability of exceedance.

Enter the Add term if it applies. Then Click OK. The new sensor will be displayed in the list of defined sensors for sending SHEF data. After all desired sensors have been added, Click Save from the SHEF setup screen . This will save the list of sensors to a file named \DW\Config\ShefMap.cfg. Note: YOU MUST PERFORM THIS STEP FIRST TO SET UP A CONFIGURATION FILE CONTAINING YOUR LIST OF SENSORS TO SEND IN SHEF FORMAT.

 

You may edit this file by Highlighting the sensor then selecting Edit. The Edit screen will appear as shown in Figure 4. Select Save from the SHEF setup screen to save any changes made to this file.



Figure 4. Editing a sensor.

You can also delete a sensor from this file by Highlighting the sensor and Selecting Delete or Exclude a sensor by Highlighting the sensor and Selecting Exclude. The sensor will now appear in the Excluded Sensors box. You will be able to include them again by highlighting that sensor and selecting Include. Select Save from the SHEF setup screen to save any changes made to this file.

 

You can also enable or disable accumulated Precip. Rollover for all precip sensors by clicking on the Enable Accumulated Precip. Rollover for All or Disable Accumulated Precip. Rollover for All button.

To Manage Precip. Rollover Cycle, Click on this button. The Rollover screen will be displayed. Use the options below to Edit or Reset cycles on selected or all sensors.



 

Select Save from the SHEF setup screen to save any changes made to this file.

 

 

STEP 2: Setting up the FTP Configuration.



 

SCROLL to the Target Number and enter the target name or Select from the list of Defined SHEF Targets. If you select from the list of defined targets the stored values will fill in automatically.

SELECT either FTP SHEF Data or Store SHEF Data in a file. CHECK Use Secure FTP for a secure data transfer. If you choose to store data in a file, unnecessary fields will be X'd out.

ENTER the FTP Address (This is the bottom portion of SHEF Setup screen).

ENTER the Login ID.

ENTER a Password.

ENTER the Execution Frequency in minutes.

ENTER the Time Zone specification (default is C for Central Time).

CHECK Use Header File if this applies – this is the filename containing product header (default is none). CLICK on Edit to edit this file.

ENTER the Output File.

ENTER the Directory on Target computer.

CHECK Append Date/Time to filename if you wish to have the date and time attached to the filename.

CHECK Include Out-of-Period data if you would like this option.

ENTER an Additional Command in this field if desired.

CLICK on Save to save the configuration and set up a scheduled function.

CLICK on Test to manually test this program. You must CLICK Save first in order to test this ftp transfer.

 

 

2.4.8.2 SHEF Decoding Configuration

To configure DataWise® to decode SHEF data, Select the “SHEF Decoding Configuration” item from the “Configure” pull-down list on the main DataWise® screen.



Once selected, the “Configure SHEF Decoder” screen shown below will be displayed.



CLICK on Add, Edit or Delete to configure each of the following: Directories to Monitor, Socket Connection to Monitor, SHEF to Sensor ID Mapping, and SHEF Products to Process.

CLICK on Save and Exit to return to the main DataWise® screen.

 

 

2.4.8.3 Manual SHEF Configuration

Note: If your system requires a more complex setup follow the manual setup instructions listed below:

Once the sensor configuration information has been input into DataWise® and the system is collecting data, SHEF-encoded data can be transferred via the FTP mechanism to any other computer that the DataWise® data acquisition computer is able to connect to. The following documentation uses the ftp.exe that comes standard with Windows to perform the transfer, however, with minor modifications to the procedure, most any FTP program that allows unattended batch processing of command will work fine. The process consists of creating a couple of batch files and using the DataWise® scheduler.

Step 1. Create a file containing the list of sensors for which to generate SHEF-encoded data. While not necessary, the file is usually placed in directory \DW\Config and named \DW\Config\shefMap.cfg. It is a simple text file, but if it is created using the notepad.exe program, be sure the extension .txt is not appended. The file will contain one line for each sensor and can contain as many lines as desired. The format of each line is:

SensorID SHEF_ID PE [Add term]

 

Where: SensorID is the DataWise sensor ID

SHEF_ID is the "Handbook 5" ID

PE is the Physical element

Add term is an optional argument that allows a value to be added to the sensor

reading (often used for stream gages) to adjust for different datums

Examples are:

2901 ALPA3 PCIRPZZ

2902 BCCA3 PCIRPZZ

2904 CFEA3 PCIRPZZ

5805 DEWA3 PCIRRZZ

"or"

103 CCST2 HG

104 CCST2 HG

105 MCFT2 PC

108 MCFT2 HG

109 LGCT2 HG

110 LGCT2 PC

114 CCBT2 HG

115 CCBT2 PC

118 CCBT2 HG

120 HCCT2 PC

123 HCCT2 HG

125 CCWT2 PC

128 CCWT2 HG

130 CBAT2 PC

133 CBAT2 HG

139 TUKT2 HG

140 TUKT2 PC

149 TUKT2 HG

150 TUKT2 PC

159 BMDT2 HG

160 BMDT2 PC

170 CNBT2 PC

173 CNBT2 HG

174 CNBT2 HG

179 PRLT2 HG

180 PRLT2 PC

189 UCCT2 HG

This file will be used by the DataWise® application "send_shef_data.exe" to generate the SHEF-encoded data file. This program is a character-based batch application with the following command line arguments:

send_shef_data.exe in=inputfile out=outputfile [s=tstep] [tz=timezone] [h=headerfile]

Where inputfile = name of file containing ID's for which to generate SHEF products

(e.g., \DW\Config\shefMap.cfg)

outputfile = name of file in which which will contain SHEF products

(i.e., \temp\shefdata.txt)

tstep = time period to generate data for (minutes)

timezone = time zone specification

(default is C for Central Time)

headerfile = filename containing product header

(default is none)

Step 2. Create a file containing FTP batch commands for automatically logging into and transferring SHEF-encoded data to the target computer. While this file can have any name and can reside anywhere on the DataWise® computer, it is convenient to place the file in directory \DW\Config and name it shef_ftp_commands.cfg. The structure of the file is:

loginID

password

ftp command1

ftp command2

…

ftp command3

bye

A typical file is:

my_login_id

my_password

cd SHEFdir

lcd \temp

put shefdata.txt

bye

Where "my_login_id" is the username, "my_password" is the password, the command "cd SHEFdir" changes the directory on the target computer to a location where the SHEF encoded products should be placed, the command "put shefdata.txt" transfers the text file containing SHEF encoded data to the target computer, and the command "bye" ends the FTP session.

Step 3. Create a batch file containing commands to generate the SHEF-encoded data and FTP it to the target computer. This file can reside anywhere. It will be used for testing only. The contents of the file should be something like the following:

send_shef_data.exe in=\DW\Config\shefMap.cfg out=\temp\shefdata.txt s=60

ftp –s:\DW\Config\shef_ftp_commands.cfg ftp.mytarget.gov

For discussion purposes, name the file \DW\Utils\sendshef.bat

Now, executing the file \DW\Utils\sendshef.bat should perform the desired functions of generating a file containing SHEF encoded data and FTP’ing to the target computer. Running it from a DOS command prompt is best for testing. Once the batch commands are correct, the process can be automated.

Step 4. Insure the DataWise® scheduler is running by going to the "Configure" pull-down menu from the main DataWise® screen and check the "Scheduler" box as shown below.



Next, from the DataWise® "Tools" pull-down menu, select "Schedule Functions". A screen similar to the one below will be shown:



Click on the "Add" button. The screen will change to something like below:



Click on the Edit button and fill in the edit field as shown below:



Hit "OK"

 

The screen will become



Now, with the "SHEF Transfer" command name highlighted, copy the contents of the file \DW\Utils\sendshef.bat to the "Command Contents" area. The area should look as shown below:



Set the desired execution frequency, hit the "Save" button and then "Done". Restart DataWise®.

 

 

2.4.9 ODBC / RDB Configuration

 

Introduction

In addition to maintaining its own proprietary database (documentation is available upon request) and the HECDSS database, DataWise® has the ability to populate any ODBC-compliant relational database (RDB). The standard DataWise® RDB module provides four methods of populating an RDB; 1) In a periodic mode in which data is stored into the RDB at regular intervals, ranging from 1 minute to 1 day. New data is continually inserted into the database, resulting in long timeseries of data for each sensor. 2) In a periodic mode in which data is stored into the RDB at regular intervals, ranging from 1 minute to 1 day. New data for a sensor replaces any existing data for the same sensor in the database, resulting in only the most current reading for each sensor. 3) In a realtime mode, analogous to 1) above, except data is stored as it is received, time-tagged to the nearest second, also resulting long timeseries of irregularly time-stamped data for each sensor. 4) In a realtime mode, analogous to 2) above, except data is stored as it is received.

 

2.4.9.1 Configuring DataWise® To Store Data in a Relational Database

To configure DataWise® to store data in a relational database, select the "ODBC / RDB Configuration" item from the "Configure" pull-down list on the main DataWise® menu (Figure 1).



Figure 1. Main DataWise® menu with "ODBC/RDB Configuration" item selected.

 

Once selected, the "ODBC/RDB Configuration" screen shown in Figure 2 will be displayed.



Figure 2. "ODBC/RDB Configuration" screen.

The edit fields are defined as follows:

Data Source: Name of the ODBC data source that connects to the target Relational Data Base.

Username: The username if access to the Data Source requires logging in (leave blank if logging in not required).

Password: The password if access to the Data Source requires logging in (leave blank if logging in not required).

 

A list of all sensors defined in the DataWise® database is shown in the list-box on the right. The sensors desired for populating the target Relational Database (RDB) are shown in the list-box on the left. To add a sensor to the list-box on the right, select the desired sensor from the list on the left and click the "Add" button. The dialog shown in Figure 3 will be displayed.



Figure 3. Dialog to add a sensor

 

To add a sensor as described in 1) in the Introduction, click on the "Periodic" type of sensor data, select the frequency (in minutes) and make sure the "Current Data Only" box is Unchecked. To store data as described in 2) in the Introduction, proceed as in 1) except check the "Current Data Only" box. To store real-time data with history, as in 3) in the introduction, check the "Realtime" radio button and make sure the "Current Data Only" box is unchecked. To store only the most recent real-time data, proceed as above and check the ‘Current Data Only" box.

 

Note that the same sensor can be selected multiple times, as long as different storage methods or criteria a specified.

 

 

2.4.9.2 Relational Database Structure

 

For storing data with a history (As described in the Introduction as type 1 or 3), DataWise® creates a table in the specified database named either sxxxx_tttt or rxxxx_tttt where "xxxx" is the sensor ID and tttt is the storage interval in minutes (or 0000 if realtime data is being stored. For example, if sensor 2455 were being stored on a 15-minute period, the table name would be s2455_0015. Each table contains two columns, T_TIME (of type DATETIME) and T_DATA (of type FLOAT). Column T_TIME contains the time stamp of the data and column T_DATA contains the data value. A table name starting with an "s" indicates calibrated data, while with a "r" indicates raw data.

 

For storing data with no history ((As described in the Introduction as type 2 or 4), DataWise® creates a table in the specified database named CurrentData. This table contains five columns, labeled T_SENSOR (type integer), T_INTERVAL (type integer), T_TIME (type datetime), T_DATA (type float), and T_RAW (type integer). There will be one row in the table for each defined sensor, with the columns for each sensor containing the sensor ID, the storage interval (or ZERO if realtime), the time stamp of the data, the data value, and a raw/calibrated flag.

 

2.4.9.3 Enabling the Process to Populate the RDB

 

Before data will actually be stored in a RDB, you must add alert_odbc to the list of custom commands using Configure, Data Collection Activities from the main DataWise® menu as described in section 2.4.1.4. No command line arguments are necessary. You must also have created a relational database and given it a name using Control Panel, Administrative Tools, Data Sources.

 

 

 

2.4.10 SCHEDULE FUNCTIONS

The Scheduler allows you to schedule commands to be act periodically, vice NT’s limitation of not allowing you to schedule in less than a day. There are commercial packages, which will allow you to do this. If you already have one or have a preference, these may be used; however, DataWise® provides this capability.

For example, should you wish a report to go out to someone each morning at a certain time, schedule will allow you to set up the report and the execution time of the report and to send the report.

 

Follow the steps below to schedule functions.

SCHEDULE functions.	CHOOSE Configure > Schedule Functions from the Main DataWise® Menu. The Schedule Activities screen is displayed. CLICK on Command Name and then CLICK on Add. A new command is added to the Command Name box. DataWise® numbers this 1 Command 1. If a command already exists, DataWise® numbers it the next sequential number. For example, 2 Command 2 would be added to the screen shown opposite.
	CHANGE the name of a command. HIGHLIGHT the Command Name. CLICK on EDIT. The Edit Command Name screen is displayed. ENTER a name in the Command Name box. CLICK on OK to return to the Schedule Activities screen.
	ENTER the Command Contents. The Command Contents must be a valid batch file command. ENTER the Execution Frequency by using the arrows to scroll through the desired number and units (Minutes, Hours, or Days). ENTER the Time Offset (hhmm) in hours and minutes. ENTER up to 12 Absolute Times (format hhmm). CLICK on Save to save your changes. CLICK on Done to return to the Main DataWise® Menu. At the bottom of the screen are Some Available Commands to choose from. CLICK on any of the buttons to view one of the available commands.

 

2.4.11 IFLOWS Configuration

Implementing the IFLOWS Backbone Communications in DataWise®

Introduction

The full IFLOWS backbone communication protocol has been implemented in the DataWise® software suite. The first step in implementing the IFLOWS interface is to set the IFLOWS network ID of the local computer. To do this, follow the steps listed below.

CHOOSE Configure > IFLOWS Configuration from the Main DataWise® Menu. The IFLOWS Main Menu is displayed. CLICK on Define Network ID’s button. The Define Network SID’s screen will be displayed.   CLICK on Add, Edit, or Delete to configure the list of Site ID’s (Network ID’s). Once the desired ID’s (including your own) have been entered, CLICK on Save to return to the IFLOWS Main Menu screen.   CLICK on the Set Local ID button. The Set Local Network Address screen is displayed.           ENTER the Current Local Address. CLICK on OK.

 

 

 

 

 

2.4.11.1 IFLOWS Network Sensor Configuration

 

The precipitation data sent around the IFLOWS backbone is not the same as the raw ALERT data being received at a base station. Raw ALERT data is an integer number that represents the accumulated rainfall at a site. IFLOWS precipitation data is 15-minute incremental data. Because of this, IFLOWS network precipitation data must be treated in a different manner from ALERT data. Before defining network sensor ID’s, the following line must be added to the file \DW\Config\devtype.cfg

60 IFLOWS_PCP Netpcp inches inch in 100.00 0.00 20 -1

All IFLOWS network precipitation gages must be defined as this type of sensor. When network data is transmitted on the IFLOWS backbone, the location originating this data is flagged by an integer number in a manner similar to the way ALERT data is. This number may or may not be the same as the ID of the gage that actually transmitted the number in ALERT format. DataWise® allows data for an ID received over the IFLOWS backbone to be stored into a different ID in the DataWise® database. For example, assume that the ID for a precipitation sensor on the IFLOWS network is 2011 but it is desirable to store all network data in sensor ID’s above 10000, say 12011. Then, as shown in Figure 4a, a sensor with an ID of 12011 is defined as type IFLOWS_PCP. From the "IFLOWS Menu", click on "Specify Network Gages" and Network ID 2011 and map it into DataWise ID 12011 (Figure 4b). This will result in any data being received with an ID of 2011 over the IFLOWS network being stored in the DataWise® database with an ID of 12011. Note that for IFLOWS precipitation gages, the frequency should be set to 15 minutes due to the nature of the network data.



Figure 4a. Sensor setup for IFLOWS network sensor 2011 being filed as DataWise® sensor 12011.



Figure 4b. Mapping the IFLOWS Network ID 2011 into DataWise ID 12011

To store data in the DataWise® database under the same ID as received on the IFLOWS network, simply set the DataWise® ID to the same as the Network ID. Care must be taken, however, to not store IFLOWS network data in the same ID as data being received directly in ALERT format as the data values are not compatible. If data is being received both locally and over the backbone on the same ID, the network ID must be changed OR the sensor ID’s of the locally collected must be mapped into a different number.

Once a network sensor has been defined, it can be treated as any other sensor in the DataWise® database. In summary, the IFLOWS Network ID is the value in the "Abbrev" field while the ID under which to store the data is in the "Sensor ID" field.

 

2.4.11.2 ALERT Sensor Configuration for an IFLOWS Network

Before IFLOWS Network data can be generated and transmitted over the network, the raw data from which network data is computed (usually data transmitted in ALERT format) must be stored in the DataWise® database. One of the capabilities of DataWise® is that data received in ALERT format under one ID can be stored in the DataWise® database under another ID. This "mapping" of one ID to another is performed as follows:

Choose Configure > Data Collection Activities from the Main DataWise® Menu. This starts the Real-time Data Collection Task Editor.   Make sure the ALERT Data Collection is enabled, then CLICK on the EDIT button to the right. The Define ALERT Data Collection Activities screen will be displayed.     In this display, ALERT data is being received on port com4, the baud rate between the decoder and the computer is 9600, sensor mapping is enabled, and other fields are disabled.

Defining a mapped sensor 12000 to be sent out on the IFLOWS backbone as 2000.

Use the Add, Edit, and Delete buttons to configure the ALERT data collection and to setup the mapping of one sensor ID to another. CLICKing the Add or Edit button will bring up the Add Comm Port to ALERT Data Collection Tasks screen. To map a received sensor ID into another ID before storing into the database, make sure the Sensor Mapping box is checked and CLICK on the Edit Mapping File button. The Sensor Mapping File screen will be displayed. This screen shows a list of sensor ID’s that will be mapped for data received on the specified port only. CLICK on Add, Edit, or Delete to map received ID’s into the desired ID before storing into the Datawise® database. Sensor ID’s not listed to be mapped will be stored under the ID’s they were received on. Using this example, Sensor ID 12000 can be defined and configured to be transmitted out on the IFLOWS backbone as sensor 2000 by setting the "Abbrev" field to 2000net. The net suffix must be added to cause the data to be transmitted over the backbone.

 

 

 

 

 

 

 

 

 

2.4.11.3 Adding the IFLOWS Backbone Communications Functionality

Choose Configure > Data Collection Activities from the Main DataWise® Menu. This starts the Real-time Data Collection Task Editor. CLICK on the Add button under Custom Command to bring up the Add/Edit Custom Applications screen.     SELECT the IFLOWS network management option as shown here.   CLICK on the button labeled Click to select this application. The "iflows_manager.exe" application will be in the Application or Program Name field.     ENTER the appropriate command line arguments. CLICK on OK.             The iflows_manager.exe functionality will have been added to DataWise® as shown here.

 

2.4.12 USGS Data Configuration

DataWise® can retrieve data from a USGS Web Site in interactive and automated modes. Before USGS can be retrieved, some configuration must be performed. To do this follow the steps listed below.

CONFIGURE DataWise® to Retrieve Data From a USGS Web Site. CLICK on the Configure from the Main DataWise® Menu. SELECT USGS Data Configuration.     The Configure USGS <-> DataWise® Interface screen is displayed. The fields shown in the list box on the left are: USGS ID: an identifier for a station assigned by the agency to identify a site. Parameter: a number that identifies a physical element (e.g., 00060 = discharge, 00065 = Water Level) SensorID: the DataWise sensor ID in which to store data. Use the Add, Edit, and Del buttons to configure the data to be retrieved. Test the retrieval using the tools in the Data Retrieval box. Control whether data will be filed in the DataWise® database during testing by Checking or Unchecking the File Retrieved Data box. To configure DataWise® to automatically retrieve USGS data, SELECT Configure > Schedule Functions from the Main DataWise® Menu.   For complete instructions on using the Schedule Functions application, see Section 2.4.10. The figure below shows DataWise® configured to retrieve the last one day of USGS data every hour. Specify the number of days to retrieve using the n= argument.

 

3.0 DATABASE MANAGEMENT

DataWise® provides extremely rapid access to both recent and historical data in the database, even under the load of multiple users simultaneously accessing the database.

Sensor Reception: DataWise® supports a database size of up to 32,000 sensors with an unlimited storage for each sensor.

Database Interface: The DataWise® database should not be considered "proprietary" in the classical sense of being closed, since it easily interfaces to commercial databases, such as Microsoft Access, and its structure is well documented.

The DataWise® database server is a multi-threaded, client/server application, designed to support many concurrent users. It was designed from the ground up and written to support true networking. All users on the network (whether on a LAN or dial-up) can access the database and all associated displays and functions, provided they have the appropriate permission.

Handling Failover: The DataWise® database server supports multiple layers of "hot standby" failover, meaning that if a primary computer fails then one of the backup computers automatically takes over the functionality of the failed computer. During times of normal functioning, all computers in the "hot failover" scheme maintain identical databases.

Exporting Data to ODBC: DataWise® supports the open database connectivity standards. This allows you to store sensor data in a commercial database of your choice (such as Oracle or SQL).

 

3.1 SENSOR MANAGEMENT

Once a sensor has been defined, data values for this sensor can be stored in the database. For an ALERT system, this is all that is required. For interrogated systems, more information must be defined (see the Defining Stations, section 2.4.7).

Follow the steps below to add, delete, or change sensors and define sensor types.

DEFINE a new Sensor Type.		CHOOSE Configure > Sensors from the Main DataWise® Menu. The Define Sensors screen is displayed.   CHOOSE File > Add/Edit Sensor Types. The Edit/Create New Sensor Types screen is displayed.
	SELECT a type similar to the desired new type by HIGHLIGHTing a sensor on the pull down menu. CLICK on New. The Edit Sensor Type Definition screen is displayed. Note If you want to define a new sensor type similar to one in your database, then you should select that sensor type. If not, DataWise® will choose a template and will automatically enter data into the Edit Sensor Type Definition screen.
	ENTER in the fields to accurately define new sensor type. ENTER the Sensor Type Name, which is the name according to function or type of data collected. Sensor names may be alphanumeric and up to 20 characters. SELECT the Sensor Type from the pull-down list. This is a fixed list. This determines how the sensor behaves and is very important. The Sensor types available include:   Water Level Sensor, used for float-type devices only. You may only have one sensor type defined. Incremental Rainfall, used for tipping bucket rain gages. You may only have one of these sensor types defined. Event Uni-directional, used for gauges which only report in one direction, such as wind travel, which occurs after a certain prescribed criteria has been met (for example, after 1 km has been met). You may have as many of these sensor types as you want. Non-event Uni-directional, also used for gauges which only report in one direction, but which are on a time basis. You may have as many of these sensor types as you want. ALERT Wind run/direction, a special sensor used only in ALERT systems which reports wind and travel in one data transmission. You may only have one of these sensor types defined. IFLOWS Net Precipitation, used only in IFLOWS systems and contains 15 minute rain fall values. You may only have one of these sensor types defined. Analog Bi-directional, the most common type of sensor, such as a temperature sensor which can go up or down. This is an analog sensor measuring a voltage. It sends a voltage in and DataWise® converts it to engineering units. You may have as many of these sensor types as you would like defined; for example, one for temperature, one for barometric pressure, etc. Status Sensor, used to monitor or control digital signals at an I/O point. You may only have up to 100 status sensors types. ENTER the Sensor type abbrev (your choice of an abbreviated name for the sensor). Sensor abbreviations may be alphanumeric and up to 8 characters. Note If you are doing hydrologic forecasting in metric units, the rainfall abbreviation must be mm. ENTER the Sensor unit (unit of measurement for that sensor). ENTER the Units abbrev (an abbreviation of the unit name). This is maximum 20 characters and may be alphanumeric. ENTER the Default divide term. The Default divide term is the "a" in the equation. y = x/a + b This equation converts raw data into engineering units. ENTER the Default add term. The Default add term is the "b" in the equation below. y = x/a + b ENTER the Default cycle size, which is the raw data range of the sensor (if unknown, enter -1). CLICK on OK.
EDIT an existing Sensor Type.		CHOOSE Configure > Sensors from the Main Menu. The Define Sensors screen is displayed.
					CHOOSE File > Add/Edit Sensor Types. The Edit/Create New Sensor Types screen is displayed. SELECT the desired sensor from the drop-down list by HIGHLIGHTing it on the pull down menu. Choices include the entire set of sensors you previously defined.
Note At any time, to view a list of defined sensors, CHOOSE Tabular Data > Sensor List from the Main DataWise® Menu or CLICK on the first icon. A list of defined sensors is displayed.	CLICK on Edit. The Edit Sensor Type Definition screen is displayed. MODIFY in the fields to accurately reflect changes to the sensor type. ENTER changes to the Sensor type name, which is the name according to function or type of data collected. Sensor names may be alphanumeric and up to 20 characters. ENTER changes to the Sensor type. (Refer to adding sensor type above for a list of available types.) ENTER changes to the Sensor type abbrev (your choice of an abbreviated name for the sensor). Sensor abbreviations may be alphanumeric and up to 8 characters. ENTER changes to the Sensor unit (unit of measurement for that sensor). ENTER Units abbrev (an abbreviation of the unit name). ENTER the Default divide term. The Default divide term is the "a" in the equation below. y = x/a + b This equation converts raw data into engineering units. ENTER the Default add term. The Default add term is the "b" in the equation below. y = x/a + b ENTER the Default cycle size, which is the raw data range of the sensor (if unknown, enter -1). CLICK on OK.
EDIT Sensor Data. Data in the sensor database can be edited, if desired, through a graphical-based database edit.			CHOOSE Edit > Edit Sensor Data from the Main DataWise® Menu. The Edit Sensor Database screen is displayed.
	SELECT the sensor to edit from the Select Sensor drop-down list. The actual data values are displayed in the list box on the left and a time series plot of the data is displayed in the plot on the right. Use the buttons to Insert new data, Edit or Delete existing ones, or Search for data at a specified time in the database. Insert new data. Edit sensor data. Delete existing ones. Search for data at a specified time in the database. CLICK on Save. Note Edited data is not stored in the database until the Save button is pushed. CLICK on Exit.

 

 

 

3.2 EQUATIONS MANAGEMENT

 

3.2.1 REAL-TIME SENSOR EQUATIONS

Real-time equations are used to compute information derived from one or more sensors in real time (as data is being received). Follow the steps below to work with Real-time Equations.

DEFINE a Real-time Equations.

CHOOSE Configure > Real-time Equations from the Main DataWise® Menu. The Text Editor screen is displayed as shown below. This work must be done in the text editor by reading and answering questions. DataWise® has examples built into the text editor to help you complete this.



 

 

 

3.2.2 STATISTICAL EQUATIONS

Statistical equations are used to compute values received over time (and are not done in real time). Follow the procedures below to define statistical equations.

LIST Statistical Equations.

CHOOSE Configure > Statistical Equations from the Main DataWise® Menu. The Database Statistical Equations screen is displayed.       CLICK on List Statistical Equations. The dbsift.cfg file will be displayed.

EDIT a Statistical Equation.

CHOOSE Configure > Statistical Equations from the Main DataWise® Menu. The Database Statistical Equations screen is displayed.     CLICK on Edit Statistical Equations. The Select Statistical Equation screen will be displayed.   Here you can Insert, Add, Edit or Delete a Statistical Equation.     CLICK on Done when you are finished making changes. You will be prompted to restart the system.   CLICK on Yes, No, or Cancel to return to the Database Statistical Equations screen.

 

 

3.2.3 HSE VIRTUAL ICE SENSOR

In order to activate virtual ice sensor computations a custom realtime DataWise® application must be enabled from the Configure > Data Collection Activities on the Main DataWise® Menu and sensors must be defined using Configure > Sensors from the Main DataWise® Menu.

Note

For in depth instructions on configuring HSE Ice Sensors, see Datawise Manual Appendix C

CHOOSE Configure > HSE VIRTUAL ICE SENSOR from the Main DataWise® Menu. The Virtual Ice Sensor Setup screen is displayed. SELECT a sensor from the Defined Ice Sensors drop-down list. Each Virtual Ice sensor requires 2 other sensors to computer conductivity and temperature. ENTER the Conductivity Sensor ID or HIGHLIGHT Edit field and SELECT from the Defined Sensors list box. ENTER the Temperature Sensor ID or HIGHLIGHT Edit field and SELECT from the Defined Sensors list box. ENTER the Dry Threshold. ENTER the # of Readings Above Threshold. This is the number of readings that match the threshold reading before assuming dry state. CHECK the Alarm on entering dry state if this is desired. CHECK the Alarm on leaving dry state if this is desired.   ENTER the Wet Threshold. ENTER the # of Readings Below Threshold. This is the number of readings that match the threshold reading before assuming wet state. ENTER the Drop in Conductivity Within 1 hr. CHECK the Alarm on entering wet state if this is desired. CHECK the Alarm on leaving wet state if this is desired.   ENTER the Rise in Conductivity to Enter Ice State and corresponding Time Period in minutes. ENTER the Threshold Temperature. CHECK the Alarm on entering ice state if this is desired. CHECK the Alarm on leaving ice state if this is desired. SELECT the desired Actions on Alarm. These alarm actions should already be defined in Define Sensors > Alarms > Add/Edit Alarm actions as described in Section 2.4.5. CLICK on Save and Exit to return to the Main DataWise® Menu.

 

 

3.3 RE-CALIBRATING SENSOR DATA

Engineering conversion terms are specified for a sensor when it is first defined in the database. In many cases these terms will never need changing; however, for some types of sensors (i.e., water level sensors) changes in the engineering conversion terms may be occasionally necessary. This is especially true for telemetry systems such as ALERT self-reporting systems in which the sensor data is transmitted as an unsigned, integer number. The sensor database keeps a history of the changes made to the engineering conversion terms and the times for which the various conversion terms are valid. Re-calibrating sensor data allows you to make a change in a sensor’s conversion terms. To re-calibrate sensor data, follow the steps listed below.

Follow the steps below to re-calibrate sensor data.

RE-CALIBRATE Sensor Data.	CHOOSE Edit > Re-Calibrate Sensor Data from the Main DataWise® Menu. The Re-Calibration of Sensor Data screen is displayed. Information being displayed in the screen includes: The sensor whose conversion terms are being examined, The date/time range of the data, A list of all of the current engineering conversion terms for selected sensor. SELECT the sensor to be re-calibrated from the Select drop-down list. List choices are all sensors defined in your database.
	CLICK on Plot. A plot similar to the one shown is displayed. Note Right or left clicking on the mouse buttons will scroll through the database. This can also be done by selecting the "Forward" or "Backward" menu items from the Movement pull-down menu.
	To CHANGE the period being displayed. CHOOSE Options > Change Display Period. ENTER a new Start Time and a new End Time. CLICK on OK.
	The plot of the new time period is displayed. Note The dashed vertical line shows the location of a change in the sensor’s engineering conversion term. CHOOSE Movement > Return.
CHANGE the engineering conversion terms for a specified time period.	CHOOSE Edit > Re-Calibrate Sensor Data from the Main DataWise® Menu. The Re-Calibration of Sensor Data screen is displayed.   CHOOSE Plot. The Plot screen is displayed.
	CHOOSE Options > Re-calibrate. The Re-calibrate Sensor Data screen is displayed.             CHANGE the conversion terms and the time period so they are valid.   CLICK on OK. The plotted sensor data is re-displayed.
	At this point, the re-calibrated data has not been stored into the database and the plot will show both the re-calibrated and original data sets. When the re-calibration terms are satisfactory, CHOOSE Options > Accept Re-calibration
	CLICK Yes to save the data. The re-calibrated data is stored in the database at that time.

 

 

 

 

 

 

3.4 RATING TABLES

Rating tables are used to convert a measured sensor reading or value of one type, say water level, into another value (often not measured) of a different type, say flow. Rating tables are referenced by numbers and are assigned to sensors. Follow the steps below to create and configure rating tables.

 

 

CREATE a New Rating Table.	CHOOSE Configure > Rating Tables. The Define/Edit Rating Tables screen is displayed.       CHOOSE File > Create a New Table. The Edit a Rating Table screen is displayed.
	CHOOSE the table by filling in the text fields and by using the appropriate Edit, Insert, and Delete buttons. Rating Table Fields include: Name: contains the name of the Table. Units: defines the units of the rated parameter. Abbr: the abbreviated units of the rated parameter. Type: select the type of observed sensor that is using the table. Interpolation method: determines the method that is used to calculate values of the rated parameter that fall between the points that have been entered in the table. Extrapolation Allowed: if checked, then rated values for observed data that exceed the largest value in the table is computed. Otherwise, the largest defined rated value is used in cases where the observed values that exceed the largest value in the table.
	CLICK on OK to save new correctly defined table.
	CLICK on Done.
EDIT an Existing Rating Table.	CHOOSE Configure > Rating Tables. The Define/Edit Rating Tables screen is displayed.         CHOOSE File > Edit a Table. The Edit a Rating Table screen is displayed.
	ENTER the Table options. Rating Table Fields include: Name: contains the name of the Table. Units: defines the units of the rated parameter. Abbr: the abbreviated units of the rated parameter. Type: select the type of observed sensor that is using the table. Interpolation method: determines the method that is used to calculate values of the rated parameter that fall between the points that have been entered in the table. Extrapolation Allowed: if checked, then rated values for observed data that exceed the largest value in the table is computed. Otherwise, the largest defined rated value is used in cases where the observed values that exceed the largest value in the table.
	CLICK on OK to save new correctly defined table.
	CLICK on Done.
IMPORT an Existing Table.	CHOOSE Configure > Rating Tables. The Define/Edit Rating Tables screen is displayed.         CHOOSE File > Edit a Table. The Edit a Rating Table screen is displayed.
	CLICK on Import From a Text File. The Import screen is displayed. DataWise® requires you to enter the file containing the rating table to be imported. You may do this by entering the system path and file name or browsing to find and select the required file.   CLICK on OK to save the import or Cancel to return to the Edit a Rating Table screen without saving changes.
	CLICK on Import From a DSS File. The Import a Rating Table from a DSS File screen is displayed.         ENTER a filename or BROWSE to find the HEC-DSS filename. CLICK on Click for a list of tables in DSS for a list of Available Rating Tables to be displayed. When you have selected the file CLICK on Import.
DISPLAY an Existing Rating Table.	CHOOSE Configure > Rating Tables. The Define/Edit Rating Tables screen is displayed.     CHOOSE File > Display a Table. The Display a Rating Table screen is displayed, which includes a box containing the defined rating tables in your system.
	SELECT the table to be displayed.     CLICK on OK. A table, similar to the one shown is displayed.
	Note Toolbar at the top provide options for: Font, Copy, Print, Print as Text, Save, and Exit.   CLICK on the sixth icon showing a Door to Exit back to the Display a Rating Table screen.
DISPLAY a List of Existing Rating Tables.	CHOOSE Configure > Rating Tables. The Define/Edit Rating Tables screen is displayed.
	CHOOSE File > List Tables or CLICK on the List Tables icon. The List Existing Tables screen shows a listing of defined rating tables (top list box) and the bottom list box shows the sensors that use the highlighted rating table.
ASSOCIATE a Sensor with a Rating Table. A sensor may be associated with a rating table so that the rated values can be computed from observed sensor value. This will enable the system to compute rated values from sensor values.	CHOOSE Configure > Rating Tables. The Define/Edit Rating Tables screen is displayed.
	CHOOSE File > Link/Unlink Sensors. The Link/Unlink Sensors and Rating Table screen is displayed. SELECT the desired sensor from the drop-down list on the left. The current table linked to it is displayed. SELECT from the list of defined rating tables.
	CLICK on Assign. This will link the sensor with the Target Rating Table. Note To unlink a sensor: CLICK on Remove. CLICK on OK to confirm any changes or Cancel to exit without saving changes.
TEST a Rating Table.	CHOOSE Configure > Rating Tables. The Define/Edit Rating Tables screen is displayed.     CHOOSE Test > Measure to Rated or Rated to Measure, or CLICK on the related icon. The Rated Values from a Table or the Table Values from a Rated Table screen is displayed
	Measure to Rated allows you to enter an observed or measured value and the rated value is computed. Rated to Measured allows you to enter a rated value and returns the measured value.

 

 

3.5 EXPORTING TO A COMMERCIAL DATABASE

Exporting data to a commercial database is easily done. The methods used depend upon which database you will be exporting the data to and generally requires custom work by DataWise® programmers. Contact DEC Data Systems for specific help on this subject.

 

 

4.0 PAGER

DataWise® supports alarm notification via alphanumeric pagers. Most commercial pagers are supported. The DataWise® paging software consists of three software modules:

• The actual paging/dialing software (executable module dwpager.exe) which resides in directory \dw\realtime.
• The paging configuration software (executable module pconfig.exe) which resides in directory \dw\utils.
• The warning program that is executed when an alarm condition is detected. This program is distributed as warning_ttyx.exe and resides in directory \dw\utils. A seldom-used program (page.exe) is also included. Although it is rarely used, it needs to be included in directory \dw\utils.
• To make the paging alarm system functional, an alarm port (or, more correctly, an alarm action number ranging from 0 to 15) must be selected. For example, if the alarm port is 2, then, the program warning_ttyx.exe must be copied into warning_tty2.exe.
• Once the above has been complete, you may define the alarm conditions for each sensor following standard steps in section 2.4.3, and include the alarm port for the pager at that time.
• Using the pager configuration program, you then configure which pager numbers are to be called for each sensor.
• Also using the pager configuration module, you must also ensure that the pager logon dialog is correct.

The following subsections provide steps for pager configuration, selecting sensors for paging, sending a test page, and viewing a log of pager activity.

 

4.1 CONFIGURING PAGERS

Before beginning to configure DataWise® to page upon alarms, you will need to know the parameters set by the paging company for your pager. The paging company should provide most of the parameters summarized below. Parameters can also be determined by calling the number provided by the paging company using terminal emulation software and testing with trial and error.

Note

Hyperterm is generally not satisfactory for this, because it does not correctly handle odd or even parity.

 

Parameters for which you will need data before configuring DataWise® to work with your pager include:

• Modem: port, which is attached to the modem which will be used to call the paging company (e.g., com1). DataWise®can handle up to 255 communication ports.
• Baud rate: usually from 1200 to 9600 baud.
• Parity: whatever the paging company sets, but usually this is odd.
• Data Bits: if even or odd parity, this is 7; if no parity, this is 8.
• Stop Bits: always 1.
• Pager Company Phone Number: the number dialed to send an alphanumeric page.
• Timeout period: the time (in seconds) allowed for carrier to be established with the paging company’s modem once the number has been dialed.
• Modem Setup String: any desired or required modem initialization string.
• Message Prompt: the prompt the paging company sends to indicate it is waiting for the message to be sent to the pager. Typical examples are "Enter Message" or "Enter Alphanumeric Page."
• Pager ID/User Name: the Pager ID is assigned by the pager company. The Pager ID is numerical and is usually a pager number, similar to a telephone number; however, often you may not enter hyphens between numbers or you may have to use the hyphen. It is important to know the format required by your pager company. The User Name is arbitrary and used only internally by DataWise®. Currently, the User Name cannot contain spaces. This must be alphanumeric, limited to 20 characters, and is just how you want to identify that person.

Once you have this information in hand, follow the steps below to configure DataWise® for paging on alarms.

CONFIGURE a pager for paging upon alarms.	CHOOSE Configure > Pager from the Main DataWise® Menu. The Pager Configuration screen is displayed.
	CHOOSE Pager Configuration > General Parameters from the pull-down menu. The Parameters screen is displayed. ENTER the Log File: The name of the file in which a log of pager actions is to be kept. ENTER the Printer on which pager failures are printed. You may leave this blank and this will not cause a problem, but you will not be able to print. ENTER the Modem port, which is attached to the modem that will be used to call the paging company. ENTER the Baud rate to match the paging company requirements. ENTER Parity to match the paging company requirements. ENTER Data Bits to match the paging company requirements. ENTER Stop Bits to match the paging company requirements. ENTER Pager Company Phone Number, which is dialed to send an alphanumeric page. ENTER the Timeout (in seconds) allowed for carrier to be established with the paging company’s modem once the number has been dialed. ENTER Modem Setup String (any desired or required modem initialization string).
	CLICK on Add to add a Pager ID/User Name. ENTER the Pager ID/User Name. The Pager ID is assigned by the pager company. The User Name is arbitrary and used only internally by DataWise®. Currently, it cannot contain spaces.   CLICK on Edit to edit a Pager ID/User Name after highlighting the desired entry. CLICK on OK.
	CLICK on Save. CLICK on Done.

 

 

4.2 SELECTING SENSORS FOR PAGING

SELECT sensors for paging.	CHOOSE Configure > Pager from the Main DataWise® Menu. The Pager Configuration screen is displayed.
	CHOOSE Pager Configuration > Sensors from the pull-down menu. The Sensors screen is displayed. From the List of All Sensors Defined, SELECT the sensor you wish to be paged when an alarm occurs by HIGHLIGHTing and CLICKing on Add (or you may just DOUBLE CLICK on the highlighted sensor). This adds the sensor to Sensors on which to page list. CLICK on the sensor just added to the list. The two list boxes at the bottom of the screen show: The Paging List for Sensors selected. The List of Pagers to Select From (that is, the list of available pagers). ADD pager numbers by CLICKing on the pagers in the list on the right, List of Pagers to Select From.
	REMOVE pagers by clicking on the left list, Paging List for Sensors. DataWise® will ask you to verify that you want to delete the selected pager.
	CLICK on Save. If you do not, DataWise® asks if you want to save changes. CLICK on Yes to ensure changes are accepted by DataWise®. CLICK on No if you do not want the changes saved. CLICK on Done to exit to the Pager Configuration screen.

 

 

4.3 SENDING A TEST PAGE

To send a test page, follow the steps below.

SEND a test page.

CHOOSE Configure > Pager from the Main DataWise® Menu. The Pager Configuration screen is displayed.

CHOOSE Pager Configuration > Manual Page from the pull-down menu. The Manual Page screen is displayed. ENTER a test message in the Enter Message Below box. ADD pager numbers by CLICKing on the pagers in the list on the right, Pagers Available. DataWise® moves the pager to Pagers Selected. REMOVE pagers by clicking on the left list, Pagers Selected. DataWise® will ask you to verify that you want to delete the selected pager. CLICK on Send. All pagers in the Pagers Selected list will be paged. If you want to know you are successful in sending the page, go to the Pager Log (see steps below). CLICK on Exit to go back to the Pager Configuration screen.

 

The system is now set up for paging upon alarms attached to the sensors defined to work with your pager.

 

 

4.4 VIEWING A LOG OF PAGER ACTIVITY

To send a test page, follow the steps below.

VIEW a log of pager activity.	CHOOSE Configure > Pager from the Main DataWise® Menu. The Pager Configuration screen is displayed.
	CHOOSE Pager Configuration > View Log from the pull-down list. The \DW\Log\Plog.log screen is displayed. DataWise® gives you an error message that the \dw\log\plog.log does not exist if you have never sent a page. DataWise® will automatically create this file with the first page or attempted page. CLICK on the X box to return to the Pager Configuration screen.

 

 

 

5.0 DATA DISPLAY

DataWise® provides a variety of data output and display functionality falling into two categories, tabular and graphical.

• Tabular Displays - DataWise® provides several types of tabular reports with and without statistical calculations. Reports can also be generated suitable for importing into spreadsheets. In addition, real-time updating of commercial spreadsheets is supported.
• Graphical Displays - DataWise® provides several types of graphical data displays:
• Standard static time series plots.
• Animated time series plots that update in real-time.
  (In both type of plots, vertical and horizontal axis are user-scaleable.)
• Animated maps with bitmap and/or vector background:
• Isopleth analysis of all data types.
• Zoom-down capabilities.
• GUI-based on-screen control functions (equivalent to the old DataCommand GTview) that are common in SCADA environments.

The following sections provide steps for working with maps in DataWise®. In all cases DataWise® must be running.

 

5.1 SINGLE SENSOR DATA DISPLAY

To display data for a single sensor, you will need to know the following information.

• Amount of time (start, stop and limit) you want the data displayed. This will be in the format mm/dd/yy hh:mm:ss and must be entered for earliest time and latest time.
• The type of data you want displayed. Choices include:
• Outliers: You may choose to either ignore or display Outliers.
• Raw Data: By default DataWise® gives you data in engineering units; however, you may ask to see raw data by this selection.
• Rated Values: If you have defined a Rating Table assigned to the sensor for which you are reviewing data, then you can ask for Rated Values to be displayed also with this selection.
• Alarms: If any data values are in an alarm condition, this will identify that the data value is in an alarm state.
• Spreadsheet format: If you request Spreadsheet format, DataWise® gives you a file with a format suitable for importing into a spreadsheet.

 

Note

To display data for a single sensor, you must have the sensor defined in the database or you receive an error message.

 

To display data for a single sensor, follow the steps below.

DISPLAY data for a single sensor.

CHOOSE Tabular Data > Single Sensor Display from the Main DataWise® Menu. The Single Sensor Data Display screen is displayed. CLICK on the sensor you wish to display. CLICK on Preferences. The Define Display Preferences screen is displayed.

SELECT the display preferences you want to see associated with the selected sensor. ENTER Newest Data To Display: the date and time to which you want to see data displayed. ENTER Oldest Data To Display: the oldest date and time from which you want to see data displayed (start). ENTER Time Period: total time range taken from Newest Data To through Oldest Data To; or, if you enter a time period in format (e.g., 5d, 5h), DataWise® adjusts the Oldest Data To field to reflect the Time Period entered. CLICK on Reset to automatically update Newest Data (will go to the current time) and the Oldest Data To (will go to beginning of time in the NT clock which is 1970) fields to the current date and time.

CHOOSE from the Sensor Types to List to change the sensor type. All sensor types you have defined in your database will be available. CHOOSE from the Click to Show list by CLICKing on each of the boxes for data you want displayed. Choices include: Outliers: Raw Data: Rated Values: Alarms: Spreadsheet format: To define a format other than those already specified in DataWise® and chosen by the above steps, CLICK on Set Display Format. The Self Format screen is displayed. ENTER the format specifications in the bottom box following the instructions in the Instructions (top) box. CLICK on Save to save your display Format Specifications. DataWise® takes you back to the Define Display Preferences screen.

CLICK on OK. DataWise® takes you back to the Single Sensor Data Display screen. Data from selected sensor is displayed. CLICK on Display to view the report. CLICK on Exit to return to the Main DataWise® Menu.

 

 

5.2 TABULAR REPORTS

DataWise® gives you a structure for working with Statistical Reports and, also, provides you with the capability to customize tabular reports. The following subsections provide steps for working with Statistical Tabular Reports and Customized Tabular Reports.

 

5.2.1 STATISTICAL TABULAR REPORTS

Statistical Tabular Reports allow the display of sensor data in tabular form with a wide range of statistical calculations available to be applied to the data. Tabular reports can be generated either from predefined groups of sensors or from sensors selected at report generation time. Statistical Tabular Reports are in a predefined structure of rows and tables.

To define Statistical Tabular Reports you must know which sensors you want grouped together and which statistics you want applied. The following is a list of statistics you can use.

• def: Default value for the sensor type.
• inst: - Instantaneous value closest to time period.
• last: - Last reported data value in the period.
• max: - Maximum reported data value in the period requested.
• min: Minimum reported data value in the period requested.
• lmax: - Largest maximum value at time of maximum report in period.
• dif: - Difference in the readings (e.g., incremental precipitation).
• mean: - Mean of values in period requested.
• skew: - Skewness of values in period requested.
• coskw: - Coefficient of skewness.
• chr: - Cooling hours from a base.
• cdd: - Cooling days from a base.
• run: - Status runtime (bit on).
• vol: - Volume computation from rate.
• tinst: - Time of the instantaneous value.
• tlast: - Time of the last data value in the period requested.
• tmax: - Time of the maximum data value in the period requested.
• tmin: - Time of the minimum data value in the period requested.
• lmin: - Value at time of minimum.
• sum: - Sum of values in period.
• var: - Variance of values in period.
• std: - Standard deviation of period values.
• rain: - Rainfall computation in the period selected.
• hhr: - Heating hours from a base.
• hdd: - Heating days from a base.
• racm: - Storm rainfall computation.
• cnt: - Count of entries in period.
• comp: - Display compass direction.
• rate: - Rated value, only if a rating table is assigned tot he sensor.
• deltap: - Subtract base from value.
• deltan: - Subtract value from base.

Follow the steps below to define and create Statistical Tabular Reports.

DEFINE groups of sensors for Statistical Tabular Report.		CHOOSE Tabular Data > Tabular Reports or CLICK on the Tabular Reports icon on the Main DataWise® Menu toolbar. The Sensor Statistical Report screen is displayed. CLICK on Preferences. The Define Groups screen is displayed. Note If no groups are shown in the Select Group menu, you must add a Group.
	To ADD a sensor group: CLICK on Add. Group 1 is displayed in the Select Group menu (left box). Note If you have groups already in the Select Group menu, the next sequential group number will be assigned. For example, if you have 41 groups already in the menu, CLICKing on Add, will add Group 42 to the menu. DOUBLE CLICK on the group just added or CLICK on Edit. The Edit Group Name screen is displayed. TYPE the desired Name for the new group. CLICK on OK to save the change. DataWise® takes you back to the Define Groups screen. Verify the change was made by checking the group number under the Select Group menu.
	CHANGE sensors in a group or ADD sensors to a group by following the steps below. SELECT which group you want to work with from the Select Group menu by SCROLLing to and HIGHLIGHTINGing your chosen sensor group. The sensors assigned to that group are shown in the Group Listing menu (right top box). If no sensors are assigned to the group, then no sensors will show in the Group Listing menu. SELECT the desired sensors from the Sensors Available menu (left lower box) by HIGHLIGHTing the sensor. ADD sensors by CLICKing on Add or by DOUBLE CLICKing on the chosen sensor. The Select Sensor Statistic screen is displayed. ADD the default statistic shown by CLICKing on Add. Or you may DEFINE the desired statistic(s) to be applied to the sensor by CHOOSing a statistic from the pull-down Select Statistic menu. This statistic can also be modified at a later time. When you have selected a sensor statistic, CLICK on OK to save the selection DataWise® takes you back to the Define Groups screen. Duplicate these steps until you have defined all sensors in a group, all groups you need for your system, and all related statistics. When done, CLICK on Save and then Finish to save the selection and return to the Sensor Statistical Report screen.
GENERATE and DISPLAY a Tabular Report.	CHOOSE Tabular Data > Tabular Reports or CLICK on the Tabular Reports icon on the Main DataWise® Menu toolbar. The Sensor Statistical Report screen is displayed. CLICK on either Display By Group or Display By Sensor. If displaying by group, SELECT the group from the Enter Group to Display pull-down menu. If displaying by group you will have the option of selecting Static or Realtime Display. If displaying by sensor, SELECT as many sensors as desired. ENTER the ending date in the Ending Date field. The format is mm/dd/yy. This should be the last date for which you want your report. ENTER the ending time in the Ending Time field. The format is any time in a 24-hour clock. ENTER the time step in the Time Step field. The format is a number followed by minutes, hours, or days. ENTER the number of time steps in the Number of Steps field. The format is numeric.
			CLICK on Static Display if displaying by sensor or either Static Display or Realtime Display if displaying by group. If Static is selected you will see a screen with a basic DataWise® Tabular Report for your chosen sensors or group of sensors as shown to the left.         If Realtime Display is selected you will see an Alert-style display as shown here. Realtime Display is only available for the Group option.
			CLICK on Totals, Additional Statistics, Std Dev, and Show questionable data boxes and then CLICK on OK to display additional data as shown in the sample report below.



CLICK on the X box to leave the Tabular Report screen and return to the Sensor Statistical Report screen. Note Icons at the top of the Tabular Report provide options for: Font, Copy, Print, Print as Text, Save and Exit Icons at the top of the Realtime Display provide options to display the data horizontally, vertically, to change the group displayed or time intervals.

 

 

 

 

 

5.2.2 CUSTOM TABULAR REPORTS

I. Introduction – Custom Format Report Templates

DataWise® provides a powerful tool for producing text reports in a custom format chosen by the user. To produce customized reports, the user must currently edit a series of text files, either with some text editor such as notepad, or from the "Custom Reports" item which is accessed from the "File" pull-down menu on the main DataWise® screen.

Custom format report template files are stored in directory \DW\Rpt\Tpt and are named reporttmpl1.tpt, reporttmpl2.tpt, and so on up to reporttmpl99.tpt where the number in the name is the report group number.

Custom format report group names are stored in file \DW\Rpt\Cfg\reportgname.cfg with the report group names stored on separate lines.

Sensors to be displayed in each custom format report are stored in file \DW\Rpt\Cfg\reportgroup.cfg with the sensors for each report group stored on separate lines.

Custom format report time files are stored in directory DW\Rpt\Cfg and are specified in file DW\Rpt\Cfg\reporttimes.cfg.

All text entered into a template file except report descriptors (described later) is printed in the report output. Report lines can be up to 512 characters in length. Each end of line in the template file prints a newline character unless the line ends with a percent (%) character. In this case, the next line overwrites this line. Only non-blank characters change information already printed on the previous line.

Custom format report descriptors are character strings in report template files that are translated into sensor data values, period data and time information, or other DataWise® database information. Report descriptors start with the percent (%) character and are followed by the descriptor name and its arguments. Percent characters are printed by coding two percent characters %%.

A sample custom report template file is shown below, followed by an actual report generated from the file.

Lavaca-Navidad River Authority

%-gname %0date[N].8.2./ %0time[N].4.2

Sensor ID %devnum[*].7

Date/Time of %devlrptd[1].5.2./ %devlrptd[2].5.2./ %devlrptd[3].5.2./ %devlrptd[4].5.2./ %devlrptd[5].5.2./ %devlrptd[6].5.2./

LastRpt. %0devlrptt[1].4.2 %0devlrptt[2].4.2 %0devlrptt[3].4.2 %0devlrptt[4].4.2 %0devlrptt[5].4.2 %0devlrptt[6].4.2

Precipitation %uabbr[*].7

%missing" _____"%

Last 10 min %data[*][1].7.2

Last 30 min %data[*][2].7.2

Last 60 min %data[*][3].7.2

For 24 hours

Ending at %0time[4].4.2 %data[*][4].7.2

Since %0time[5].4.2.TB %data[*][5].7.2

%0time[6].4.2.TB Thru %0time[6].4.2.S.TE %data[*][6].7.2

%0time[7].4.2.TB Thru %0time[7].4.2.S.TE %data[*][7].7.2

%0time[8].4.2.TB Thru %0time[8].4.2.S.TE %data[*][8].7.2

%0time[9].4.2.TB Thru %0time[9].4.2.S.TE %data[*][9].7.2

%0time[10].4.2.TB Thru %0time[10].4.2.S.TE %data[*][10].7.2

Since %0time[11].4.2.TB %data[*][11].7.2

%0time[12].4.2.TB Thru %0time[12].4.2.TE %data[*][12].7.2

%0time[13].4.2.TB Thru %0time[13].4.2.TE %data[*][13].7.2

%0time[14].4.2.TB Thru %0time[14].4.2.TE %data[*][14].7.2

%0time[15].4.2.TB Thru %0time[15].4.2.TE %data[*][15].7.2

Lavaca-Navidad River Authority

Sample Rainfall Report 03/01/05 1155

Sensor ID 101 201 301 401 501 601

Date/Time of 3/01/05 3/01/05 3/01/05 3/01/05 3/01/05 3/01/05

LastRpt. 11:39:15 11:33:10 11:30:03 11:33:10 11:50:16 11:52:37

Precipitation in in in in in in

Last 10 min 0.00 0.00 0.00 0.04 0.04 0.00

Last 30 min 0.04 0.04 0.04 0.08 0.08 0.08

Last 60 min 0.16 0.16 0.16 0.16 0.16 0.12

For 24 hours

Ending at 1100 0.51 0.43 0.43 0.43 0.79 0.79

Since 1100 0.16 0.12 0.12 0.16 0.12 0.12

1000 Thru 1100 0.08 0.16 0.12 0.12 0.12 0.08

0900 Thru 1000 0.04 0.08 0.04 0.04 0.04 0.04

0800 Thru 0900 0.08 0.04 0.12 0.12 0.63 0.67

0700 Thru 0800 0.31 0.16 0.16 0.16 0.00 0.00

0600 Thru 0700 0.31 0.00 0.00 0.00 0.00 0.00

Since 1100 0.16 0.12 0.12 0.16 0.12 0.12

0500 Thru 1100 0.51 0.43 0.43 0.43 0.79 0.79

2300 Thru 0500 0.00 0.00 0.00 0.00 0.00 0.00

1700 Thru 2300 0.00 0.00 0.00 0.00 0.00 0.00

II. Report Descriptor Format

 

Report descriptors are character strings that follow a percent character in a custom report template file. The report descriptor format includes prefix characters, the descriptor name, device and period index lists and print parameters. Report descriptors can be prefixed by list delimiter, justification, padding, blank zeroes and plus sign flags. Descriptors can be followed by devices and period index lists, and field width and precision, output format and separator flags. The general descriptor format is:

%XJPZ+desc[...][...].W.P.F.S

 

where:

 

X - List delimiter flag

J - Justification flag

P - Padding flag

Z - Blank zeroes flag

+ - Plus sign flag

desc - Descriptor name

[...] - Device index list

[...] - Period index list

W - Field width

P - Field precision

F - Format flag

S - Separator

 

NOTE: The space taken by a report descriptor in the template file is not the amount of space its translation takes in the report output.

 

List delimiter flag: The list delimiter flag is used to separate a list of descriptor output:

 

[space] - Append a space

[Comma] - Append a comma

None - Use global flag (default is no delimiter)

 

 

Justification flag: Descriptor output can be justified left, right, or centered:

 

L - Justify left

R - Justify right

C - Justify center

[Dash] - Justify left (obsolete)

None - Use global flag [default is justify right]

 

 

Padding flag: Descriptor output can be padded to field width:

B - Blank pad

0 - Zero pad

N - No padding

None - Use global flag (default is blank padding)

 

 

Blank zeroes flag: Zero data values can be replaced by blanks (spaces):

 

Z - Blank zero data values

b - Blank zero data values (obsolete)

None - Use global flag (default is no zero blanking)

 

Plus sign flag: Prefix positive data values with a plus sign (+):

 

+ - Prefix positive data values with a plus sign

None - Use global flag (default is no plus sign)

 

Descriptor name: Type of output (see following section)

 

 

Sensor index list: Report descriptors that refer to sensors in the sensor list. This reference is called the sensor index. The sensor index is enclosed in brackets [...], and is a number between one and the number of sensors in the sensor list. It is not the actual sensor number. Sensor index one refers to the first sensor in the list:

 

For example, if a descriptor displays data for sensor index two (2) and the sensor list contains the following sensor ID’s and statistical parameters:

1035/rain 1055/rain 1065/rain ...

 

the report would display rainfall data for sensor 1055.

 

Reverse sensor index: A report descriptor is provided that reverses sensor index numbering to last sensor to first sensor (i.e. sensor index 1 is last in the sensor list).

 

Period index list: Report descriptors that refer to period defined for the report by command line arguments or a time file (see next section). This reference is called the period index. The period index is enclosed in brackets, [...], and is a number between 1 and the number of periods in the period list. Period list 1 refers to the first period in the list.

 

For example, if report command arguments define the period time step as 1 hour, the number of periods as twelve (12), and the ending time as 1600, the report period time ranges from 0400 to 1600. The first period index 1 is the time period from 0400 to 0500. The second period index 2 is the time period from 0500 to 0600.

 

Reversing period index: A report descriptor is provided that reverses period index numbering to last period to first period (i.e. period index 1 is the last period).

 

Index ranges: A descriptor may specify more than one sensor or period index. In the following examples the index range is 1 though 5.

 

Individual indices are separated by commas (,0:

 

[1,3,5] - Selects indices 1, 3, and 5.

 

An index range lists the start index, a dash (-), and the end index:

 

[1-3] - Selects indices 1, 2, and 3.

 

A star (*) and the number following the end index in a range set the range index increment:

 

[1-5*2] - Selects indices 1, 3, and 5.

 

A star (*) alone selects all indices defined:

 

[*] - Selects all indices: 1, 2, 3, 4, and 5.

 

Printing of multiple indices extends to the right on the report output line. Separation between index values is done with padding or the descriptor list delimiter character.

 

Line repeat with automatic index increment: An empty index range, [], uses the next index number from the sensor or index list until the end of the list is reached. When the output line is repeated, the index number is incremented [or decremented if the index is reversed.].

 

 

Increment index number within a line: Use [+#] to increment the index number by # counts. Use [-#] to decrement the index number by # counts.

 

 

Field width: Field width defines the number of spaces the translation uses in the report output. If the field width is less than the output width, the output is truncated based on the justification flag. If the field width is greater than the output width, the output is padded based on the justification, padding, blank zero and plus sign flags.

 

 

Field precision or text string length: Precision is the number of digits displayed to the right of the decimal point for data output. It is the number of characters printed for a text string output.

 

Format flags:

 

Format flags to display period date are:

 

A - American format (MM/DD/YY)

E - European format (DD/MM/YY)

I - International format (YY/MM/DD)

None - Use global flag (default is American format)

 

Format flags to display water year period begin and end dates are:

 

WB - Beginning of water year

WE - End of water year

 

 

Format flags to display the month in the date are:

 

A - Month name (JANUARY, FEBRUARY, ...)

S - Month abbreviated name (JAN, FEB, ...)

W - Month number (1-12)

 

 

Format flags to display the day of the week for the date are:

 

A - Day of week name (SUNDAY,MONDAY,...)

S - Day of week abbreviated name (SUN,MON,...)

W - Day of week number

None - Use global flag (default is day of week)

 

 

Format flags to display the period ending or period beginning time are:

 

TE - Use time at end of period

TB - Use time at beginning of period

None - Use global flag (default is day of week)

 

 

Format flags to display the wind direction are:

 

D - Display wind direction in degrees (0-360)

C - Display wind direction in compass headings (N,NNW,NW,...)

None – Use global flag (direction in degrees)

 

 

 

Separator: Separator character for date and time elements and latitude / longitude (default is none):

 

Use a separator of / or – or . or , for date elements

Use a separator of : or – or . or , for time elements

Prefix hexadecimal character codes with a backslash, \

 

 

III. Report Descriptors

Custom report descriptors are character strings that are translated into sensor data values, period date and time information, or other DataWise® database information. They are redefine default descriptor flag values and index numbering,

 

 

Report global parameter descriptors: The following report setup descriptors have been provided to change or restore the default report parameters. Default states are starred (*):

 

 

highdev - for sensor lists, start with the last sensor

* lowdev - for sensor lists, start with the first sensor

highperiod - for period lists, start with the last period

* lowperiod - for period lists, start with the first period

* devicefirst - for lists, increment sensor index first

periodfirst - for lists, increment period index first

justifyleft - left justify in field

* justifyright - right justify in field

justifycenter - center in field

* padblank - blank pad the field

padzero - zero pad field

padnone - no padding

lankonzero - blank field for zero value

prefixplus - prefix positive values with a + (plus sign)

@delimit - use character @ as the list delimiter (default is none)

valwidth.W.P - data value field width = W, precision = P

strwidth.W.P. - string field width = W, limit = P

* dateamer - print date in American format (MM/DD/YY)

dateeurope - print date in European format (DD/MM/YY)

dateintrnl - print date in International format (YY/MM/DD)

* monthnum - print month as number

monthalpha - print month name (JANUARY, FEBRUARY,...)

monthshort - print abbreviated month name (JAN,FEB,...)

* winddeg - print wind direction degrees

windcomp - print wind direction compass headings (N,NNE,...)

 

 

Report default setup at start of template: Report default descriptors can be used at the start of a template to redefine the default list behaviors and format flags. This simplifies the coding of other descriptors later. For example, to print data values for sensor index 1 and list periods from last to first, use

 

%highperiod%

%data[1][*].8.2

 

Prevent newline on default setup line: Note that the trailing % after the highperiod descriptor prevents a newline from printing for the report setup descriptor line. Terminate any line with a % to prevent a newline.

 

 

Sensor data descriptor: The sensor data descriptor prints data values for a list of sensors and a list of periods. The format is:

 

%WJPZ+data[...][...].W.P.F

 

The W, J, P, Z, and + flags override the global print flags. The sensor list is specified in the first set of brackets while the period index list is specified in the seconds set. The W and P parameters override the global field width and precision. The F parameter overrides the global print of wind direction in degrees or compass heading.

 

Sensor data descriptor examples:

 

Example 1. To print the data value for sensor index 1, period 2, with field width 8 and precision 2 use:

 

%data[1][2].8.2

 

A data value of 512.357 would print as __512.36 where the _ represents a space.

 

Example 2. To print the data values for sensor index 1, periods 1 through 4, field width 8, data precision 2, and left justify use:

 

%Ldata[1][1-4].8.2

 

Data values 0, 1.5, 2.3, and 8.7 for periods 1, 2, 3, and 4 would be printed in 8 character fields as:

 

0.00 1.50 2.30 8.70

 

Example 3. To print the data values for sensor indices 1, 2, and 3 for period 2, field width 8, data precision 2, print plus signs and blank zeroes use:

 

%+Zdata[1-3][2].8.2

 

Data values 0.15, 0.00, -1.10 for indices 1, 2, and 3 would print in 8 character fields as:

___+0.15 -1.10

 

Example 4. To print the data values for sensor index 1 for all periods, field width 8, precision 1, no padding and comma list delimiter, use:

 

%,Ndata[1][*].8.1

 

Data values 101.50, 99.36, 97.61 for sensor index 3 and periods 1 through 3 would print as

 

101.5,99.4,97.6

 

 

Sensor parameter descriptors: Sensor information descriptors, info, print database information for a list of sensors. Period numbers are not provided:

 

devlrptd - Print the sensor last report date

devlrptt - Print the sensor last report time

devlrptv - Print the sensor last report value

devnum - Print the sensor ID number

devtype - Print the sensor type name

lat - Print the sensor latitude

long - Print the sensor longitude

name - Print the sensor’s name

shorttype - Print the sensor type abbreviation

stalintd - Print the station’s last interrogation date

stalintt - Print the station’s last interrogation time

stanum - Print the station number for this sensor

staname - Print the station name for this sensor

tag - Print the sensor tag name

units - Print the sensor type units

unit - Print the sensor type unit

uabbr - Print the sensor type unit abbreviation

 

 

The descriptor format is:

 

%XJPZ+info[...].W.P.F.S

 

The X, J, P, Z, and + flags override the global print flags. The sensor index list is provided in the set of brackets. The W and P parameters override the global field width and precision. The F parameter overrides the global date and time format. The S parameter defines the separator character.

 

Sensor information descriptors example. To print the sensor ID with a field width of 4, the tagname with a field width of 8 left justified, sensor name and type with no padding (no field width is required) for sensor index 1, use the following:

 

%devnum[1].4 %-tag[1].8 %Nname[1] %Ndevtype[1]

 

Assuming that sensor index 1 is sensor ID 545, the tagname is WPZ545, the name is Woodland, and the sensor type is Precipitation Gage, then the output would be:

 

_545 WPZ545 Woodland Precipitation Gage

 

 

Sensor unit abbreviation descriptor example: To print the data value for sensor index 1, period index 1, field width 8, precision 2, followed by its units and then abbreviated units in parentheses, use:

 

%data[1][1].8.2 %Nunits[1] (%Nuabbr[1])

 

If the data value is 103.35, units are feet and abbreviated units are ft, then the output would be:

 

__101.35 feet (ft)

 

 

 

Sensor last report date, time, and value descriptor example. To print the sensor index 1 last report date, time, and value with the following specifications:

 

Date field width of 8, field limit of 2, zero padding, and a slash separator.

 

Time field width of 8, field limit of 2, zero padding, and a colon separator.

 

Data field width of 8 and precision of 2.

 

Use the following …

 

%0devlrptd[1].8.2./ %0devlrptt[1].8.3.: %devlrptv[1].8.2

 

A last report date / time / value of May 9, 2004 at 13:09 of 6.53 will be output as:

 

05/09/04 13:09:00 6.53

 

 

Station number, last interrogation date, and time descriptor example. To print the station number, station name, and last interrogation date and time for sensor index 1 with the following specifications:

 

Date field width of 8, field limit of 4, zero padding, and a slash separator.

 

Time field width of 4, field limit of 2, zero padding, and no separator.

 

Station number 101 with a name of Bobcat and last interrogation date / time of June 13,2004 at 10:00 would print as:

 

_101 Bobcat 06/13/04 1000

 

Note that a date field width of 4 will print the full year. The month and day elements are limited to 2 characters. A time field width of 4 and no separator prints the hour and minute only.

 

Latitude / Longitude descriptor example. To print the station latitude and longitude for sensor index 1 with a field width of 10, zero padding, prefixed with a plus sign and a period separator, use the following:

 

%+Zlat[1].10.2.. %+Zlong[1].10.2..

 

A station with latitude of 36:23:04N and longitude of 100:13:57W would print as

 

_+36.23.04 +100.13.57

 

Note that latitude and longitude printing ignores the field precision. Use selected padding (i.e. zero padding) of latitude/longitude elements (degrees, minutes, seconds). Padding to the full field width always uses blank padding. If the plus sign prefix is selected, northern latitude and western longitude values are printed with a plus sign (+), while southern latitude and eastern longitude values are printed with a minus sign (-). If the plus sign prefix is not selected the latitude and longitude have the hemisphere letters appended as follows:

 

36.23.04N +100.13.57W

 

 

 

 

Period date and time descriptors. Period date and time descriptors print date and time information for a list of periods. Sensor index numbers are not provided. The following is a list of descriptors:

 

date - Print the period date: month, day, and year

time - Print the period time: hour, minute, and second

year - Print the period year number

month - Print the period month number

day - Print the period day number

hour - Print the period hour number

minute - Print the period minute number

second - Print the period second number

juld - Print the julian day (days since Jan 1 at 00:00:00)

julh - Print the julian hour (hours since Jan 1 at 00:00:00)

julm - Print the julian minute (since Jan 1 at 00:00:00)

juls - Print the julian second (since Jan 1 at 00:00:00)

dminute - Print the period minutes since start of day

dsecond - Print the period seconds since start of day

tstep - Print the period time step

 

The descriptor format is:

 

%XJPZ+time[…].W.P.F.S

 

The X, J, P, Z, and + flags override the global print flags. The period index list is provided in the set of brackets. The W and P parameters override the global field width and date/time element precision. The F parameter overrides the global date and time format. The S parameter defines the separator character.

 

 

Period date and time descriptor examples.

 

Example 1. To print with the following specifications:

 

Period index 1 date with a field width of 8, element precision of 2, zero padding, with a slash (/) separator.

 

Period index 1 time with a field width of 8, element precision 2, zero padding, and a colon (:) separator.

 

%0date[1].8.2./ %0time[1].8.2.:

 

A date of march 14,2005 and time of 08:35 prints as:

 

03/15/05 08:35:00

 

Note that the default date format is American, which displays as MM/DD/YY.

 

Example 2. To print the above in European format (DD/MM/YY) but with a comma (,) separator, use

 

%0date[1].8.2.E.,

 

The output (date only) from "Example 1" would be

 

15,03,05

 

Example 3. To print the above in International format (YY/MM/D) but with a period (.) separator, use

 

%0date[1].8.2.I..

 

which results in the following output:

 

05.03.15

 

Period month format example. To print the period index 1 date using the full month name, no padding (field width is ignored), with a space separator, use

 

%Ndate[1].8.4.A.A

 

which will result in the following output:

 

March 15 2005

 

 

Period date and time element examples.

 

Example 1. To print period index 1 date elements individually with the following specifications,:

 

Abbreviated month name, the day number, and 4-digit year number, use

 

%month[1].3.3.A.S %0day[1].2 %year[1].4.4

 

Then, March 15, 2005 would print as

 

MAR 15 2005

 

Example 2. To print the period index 1 time elements individually with the following specifications:

 

Print the hour, minute, and seconds with zero padding

 

%0hour[1].2 %0minute[1].2 %0second[1].2

 

Then, a time of 16:05:22 would be output as

16 05 22

Group and system name descriptors. Group names are read from the file \DW\Rpt\Cfg\reportgname while system names are read from the file \DW\Cfg\sysname.cfg.

 

gname - Print the group name

sysname - Print the system name

 

The descriptor format is:

 

%XJPname.W.P

 

The X, J, and P flags override the global print flags. The W and P parameters override the global field width and string limit.

 

For example, the print the system name left justified in 30 characters followed by other text and on the next line print the group name centered in 40 characters, surrounded by brackets and limited to 20 characters, use the following:

 

%Lsysname.30 my text

[%Cgname.40.20]

 

A system name "Sacramento City ALERT System" and group name "Precipitation Group Example" would print as:

 

Sacramento City ALERT System my text

[ Precipitation Group ]

 

 

 

 

Overwriting lines using the no newline descriptor: The % character alone at the end of a line prevents a newline from being printed. Use this descriptor to overlay a line with following lines. Overlaying lets you line up columns since descriptor width does not necessarily match the actual print width. When overlaying, blanks on the following lines do not change the previous line’s information. For example, if the following descriptors are used:

 

%devnum[1].4%

%name[1].20%

 

and if device index 1 specifies sensor 20 with a name of Pleasant Hill, then the output will be

 

__20 Pleasant Hill.

 

 

Missing data descriptor. The missing data descriptor allows a string to be defined which will be printed when data is missing. The descriptor is followed by quotes surrounding the string to be printed. For example, to print dashes (-) for missing data, specifying

 

%missing"-----"%data[*][1].8.2

 

will output

 

____1.01 2.70 ----- 4.11

 

when the data fields are 1.01, 2.7, missing, and 4.11

 

 

Period date day of week example:

 

To print period index 1 date as day or week, followed by the abbreviated day of week in parentheses, use:

 

%day[1].8.8.A.A (%day[1].3.3.A.S)

 

The output for a date of March 15, 2005 would be:

 

_TUESDAY (TUE)

 

 

Special period flags: The following special period flags may be used instead of period index numbers:

 

N - Use the current date and time

F - Use the first period date and time

L - Use the last period date and time

P - Use the date / time passed on the command line

 

For an example, to print the current date and time, specify

 

%0date[N].8.2./ %0time[N].8.2.:

 

which will output

 

03/17/05 11:38:04

 

 

Period start and end time example. All periods in the list have start and end times. By default, the period end time is printed for report descriptors. Use the TB format flag to print the start time. For example, to print the start and end times for period index 1 separated by dashes (-) use:

 

%0time[1].4.2.TB-%0time[1].4.2.TE

 

For a period with a start time of 09:00 and end time of 10:00, the above will print:

 

0900-1000

 

Period time step example. Period time steps can be printed with the tstep descriptor. For example, to print a data value for sensor index 1 and period index 1 then follow with the time step and the text "rainfall", use

 

%data[1][1].8.2 %Ntstep[1] rainfall

 

which will output

 

____1.04 1hour rainfall

 

when the data value is 1.04 and the time step is 1 hour.

 

 

 

Statistical analysis descriptors. Statistical analysis of report data values can be printed for a list of sensor and/or period indices using the following stat descriptors:

 

sum - Print the sum

dif - Print the difference

mean - Print the average

max - Print the maximum

min - Print the minimum

count - Print the count of non-blank (non-zero) values

dmax - Print the date of the maximum

dmin - Print the date of the minimum

tmax - Print the time of the maximum

tmin - Print the time of the minimum

 

 

Index ranges for analysis. The index range selects the index values to use in the statistical analysis. In the following examples, the index range is 1 through 5.

 

If individual indices are separated by commas (,):

[1,3,5] - Analyze indices 1, 3, and 5

 

If two indices are separated by a dash (-),

[1-3] - Analyze indices 1, 2, and 3

 

If an index range increment is specified, it is done as follows:

[1-5*2] - Which states that indices 1 through 5 should be analyzed in steps of 2, or analyze indices 1, 3, and 5

 

If a * alone is specified:

[*] - Then all indices are analyzed

 

 

Printing multiple statistical analyses. Printing of multiple statistical analyses to the right on the report output line is done by providing a multiple print increment value. This value is provided after the index range following a bar (|) character. The multiple print increment value is added to the index numbers for the next analysis and print. Index numbers are incremented until the last index number is passed.

 

For example, if the index range is 1 through 10 and the analysis is to do two indices at a time (1 and 2, 3 and 4, 5 and 6, 7 and 8, 9 and 10), the starting indices are 1 and 2 and the increment value is 2:

 

[1-2][2] - Analyze indices 1 and 2, print, then increment by 2 to analyze indices 3 and 4, print, and so on.

 

To print sums of period data values for sensor index 1 in groups of 31 periods, use the following:

 

%sum[1][1-31][31].5.1

 

The first analysis would sum and print periods 1 – 31, the second would sum and print periods 32-62, and so on.

 

To print the difference between period 1 and 2 data values:

 

%data[1][1].6.2 - %data[1][2].6.2 = %dif[1][1-2].6.2

 

Period 1 and 2 data values of 937.04 and 935.01 would print:

 

937.04 – 935.01 = 2.03

 

To print the mean of all period data values for each sensor starting with sensor index 1:

 

%mean[1][1][*].5.1

 

If sensor index 1 had data values 1.0, 2.0, 3.0, 4.0, 5.0 and sensor index 2 had values 3.0, 4.0, 5.0, 6.0, 7.0 the descriptor would print:

 

__3.0 5.0

 

To print the maximum, date and time of the maximum, minimum, and date and time of the minimum:

 

%max[1][*].5.1 %0dmax[1][*].8.2./ %0dmax[1][*].4.2

%min[1][*].5.1 %0dmin[1][*].8.2./ %0dmin[1][*].4.2

 

If sensor index 1 had data values 2.0, 1.5, 3.0, 4.0, 3.5 for period date 11/23/2004 and times 10:00, 09:00, 08:00, 07:00, 06:00, then the output would be:

 

4.0 11/23/04 0700

1.5 11/23/04 0900

 

To print the count of non-zero data values to indicate the number of days having rainfall use:

 

%count[1][*].5.0

 

Then, if the monthly rainfall were computed as non-zero for 7 days, the output would be:

 

____7

 

 

Computational descriptors: Arithmetic constants can be used to adjust sensor or statistical analysis data values using the following computation descriptors:

 

add# - Add # to the following sensor data value

sub# - Subtract # from the following sensor data value

mul# - Multiply # times the following sensor data value

div# - Divide # into the following sensor data value

 

The descriptor format is:

 

%comp#%data... or %comp#%stat...

 

Example 1. Add 0.5 to the data value of sensor index 1 and subtract 0.03 from the data value of sensor index 2 for period index 1 data:

 

%add0.5%data[1][1].5.2 %sub0.03%data[2][1].5.2

 

A data value of 20.4 for the sensor index 1 and 20.4 for sensor index 2 would print:

 

90. 20.37

 

Example 2. Multiply 2.5 times the data value of sensor index 1 and divide 2.0 into the data value of sensor index 2 for period 1 data:

 

%mul12.5%data[1][1].5.2 %div2.0%data[2][1].5.2

 

If the data value for the sensor in sensor index 1 is 2.0 and 2.0 for the sensor in sensor index 2 then the above would output:

 

_5.00 1.00

 

Repeating lines while incrementing sensor or period indices: The special descriptor %* at the beginning of a line in a template file will repeat the line for all sensors or periods in the lists. Each time the line is repeated the sensor or period index is incremented. Select sensor index or period index incrementing for repeat lines by leaving the brackets empty.

 

Usually only one list index is incremented when the line is repeated. The other index is individually selected or listed to repeat across the line. If both the sensor and period indices are incremented, the sensor index is incremented first by default (devicefirst descriptor). After the line has been repeated for all sensors in the list, the sensor index is reset and the period index is incremented. Select period index incrementing first with the periodfirst descriptor.

For an example, to repeat a line for all sensors in the list that prints the sensor ID, name, and data values for all periods, use the following:

 

ID NAME %otime[*].8.2

%*%devnum[].4 %-name[].5 %data[][*].8.2

 

If there are three sensors in the list 101, 201, 301 with names Name1, Name2, Name3 and four time periods ending at 08:00, 09:00, 10:00, and 11:00, then the output would be:

 

__ID NAME 080000 090000 100000 110000

_101 Name1 1.01 1.02 1.03 1.04

_201 Name2 2.01 2.02 2.03 2.04

_301 Name3 3.01 3.02 3.03 3.04

 

By default, repeating line indices start with the first index and increment (lowdev and lowperiod descriptors). To start with the last index and decrement, use the highdev and highperiod descriptors. For example, when printing the period data, time, and value for sensor index 1 on date 11/01/1996 at times 08:00, 09:00 and 10:00 with values 1.01, 1.02, and 1.03 using

 

%lowperiod%

%*%0date[].8.2./ %0time[].8.2.: %data[1[[].8.2

 

would print starting with the first period index:

 

11/01/96 08:00:00 1.01

11/01/96 09:00:00 1.02

11/01/96 10:00:00 1.03

 

and

 

%highperiod%

%*%0date[].8.2./ %0time[].8.2.: %data[1][].8.2

 

would print starting with the last period index:

 

11/01/96 10:00:00 1.03

11/01/96 09:00:00 1.02

11/01/96 08:00:00 1.01

 

 

IV. Custom Format Report Time Files

Custom format report time files define time periods for reports as offsets from the report starting or ending time. The time periods do not have to have the same time step. Time files must reside in directory \DW\Rpt\Cfg. There are two methods of specifying time files. One way is by name in which the time file for a report is named in a certain way. Time file for report 1 would be named reporttime1.cfg, for report 2 reporttime2.cfg, etc. Another method of specifying time files is by storing their names in file \DW\Rpt\Cfg\reporttimes.cfg. If done in this way, each line contains the name of a time file with the file for report 1 being on line 1, report 2 on line 2, etc. If specified in this manner, then reports without a time file must have the string "xxx" on the line that would normally specify their time file.

 

Structure of time files. Custom report time files contain a header line followed by time period offset lines, an example of which is shown below. The first line in a time file is a header specifying the time file type, offset direction from the start or end time, and the time rounding factor as follows:

 

type direction rounding

 

Currently, only the "relative" time file type is supported, which states that the period offsets are relative to the start or end time.

 

The time file offset the direction specifies whether the period offsets are relative to the start or end time. If the direction is specified as "start", then time periods are offset from the report start time, while if specified as "end" they are offset from the report end time.

 

Time file rounding factors are used to force the report to begin or end on an even time boundary. By default, report time periods are computed to the nearest second from the start or end times. If the start or end time does not end on at even time step (e.g. 1 hour), then the rounding factor can be used to adjust (round down) the start or end time before computing time periods.

 

For example if a report end time is 11:55:15 and the report period times are to be displayed to he nearest minute, use a 1 minute rounding factor to adjust the end time to the last minute as follows:

 

relative end 1m

 

Time period offset lines are used to define period start and end times. These lines can have up to four fields (note that only the first two are required) with the following format:

 

firstoffset secondoffset rounding limit

 

For relative time files using period offsets from the start time, the period offsets are added to the adjusted report start time. The firstoffset defines the period start time and the secondoffset the period end time.

 

For relative time files using period offsets from the end time, the period offsets are subtracted from the adjusted report end time. firstoffset defines the period end time and the secondoffset the period start time.

 

Time period offsets are expressed as a time count followed by the full singular, plural, or abbreviated time units:

 

second(s) or s

minute(s) or m

hour(s) or h

day(s) or d

month(s) or months

year(s) or y

 

______________________________________________________

Relative end 1m

0m 10m

0m 30m

01 1h

0d 1d 1h

0h h

0h 1h 1h

1h 2h 1h

2h 3h 1h

3h 4h 1h

4h 5h 1h

0h h

0h 6h 1h

6h 12h 1h

12h 18h 1h

18h 24h 1h

_____________________________________________________________

 

 

 

Time period offset example from report end time. In a "relative" time file with the offset direction from the "end" time and a rounding factor of 1 minute, 1m, define four periods ending at the adjusted report end time and starting 10 minutes, 30 minutes, 1 hour, and 1 day earlier. Make the 1 day period end at the last hour.

 

relative end 1m

0m 10m

0m 30m

0h 1h

0d 1d 1h

 

Note that 0m, 0h, and 0d are all the same offset from the end time. If the report end time was 04/07/2004 at 11:55:15, the period start and end times would be:

 

04/07/2004 11:45:00 to 04/07/2004 11:55:00

04/07/2004 11:25:00 to 04/07/2004 11:55:00

04/07/2004 10:55:00 to 04/07/2004 11:55:00

04/06/2004 11:00:00 to 04/07/2004 11:00:00

 

Rounding the period back to the last time unit. If no time count is provided, just the time units, the period offset is rounded back to the last time unit. For example, to define a time period ending at the report end time and starting at the last hour, use:

 

0h h

or

0h hour

 

If the report end time was 04/07/2004 at 11:55:15, the period start time and end time would be

 

04/07/2004 11:00:00 to 04/07/2004 11:55:00

 

Several time periods with same time step. To define several time periods going back in time with the same time step, make the next time period firstoffset equal to the previous period secondoffset. For example, to define 5 one hour periods:

 

0h 1h 1h

1h 2h 1h

2h 3h 1h

3h 4h 1h

4h 5h 1h

 

If the report end time was 04/07/2004 at 11:55:15, the period start and end times would be:

 

04/07/2004 10:00:00 to 04/07/2004 11:00:00

04/07/2004 09:00:00 to 04/07/2004 10:00:00

04/07/2004 08:00:00 to 04/07/2004 09:00:00

04/07/2004 07:00:00 to 04/07/2004 08:00:00

04/07/2004 06:00:00 to 04/07/2004 07:00:00

 

 

Time period offset example from report start time. In a "relative" time file with offset direction from the "start" time and a rounding factor of 1 month, 1month, define 31 periods for each day of the month followed by a period for the entire month. Limit the last 3 daily periods to the length of the month since not all months have 31 days:

 

relative start 1month

0d 1d

1d 2d

2d 3d

3d 4d

4d 5d

...

27d 28d

28d 29d 1d month

29d 30d 1d month

30d 31d 1d month

0month 1month

 

If the report start time was between 02/01/1996 at 00:00:00 and 02/29/1996 at 23:59:59 or the report end time was between 02/01/1996 at 00:00:01 and 02/29/1996 at 24:00:00, the report time periods would be:

 

02/01/1996 00:00:00 to 02/01/1996 24:00:00

02/02/1996 00:00:00 to 02/03/1996 24:00:00

02/03/1996 00:00:00 to 02/04/1996 24:00:00

02/04/1996 00:00:00 to 02/05/1996 24:00:00

02/05/1996 00:00:00 to 02/06/1996 24:00:00

...

02/28/1996 00:00:00 to 02/28/1996 24:00:00

02/29/1996 00:00:00 to 02/29/1996 24:00:00

* 03/01/1996 24:00:00 to 03/01/1996 24:00:00

* 02/29/1996 24:00:00 to 02/29/1996 24:00:00

02/01/1996 00:00:00 to 02/29/1996 24:00:00

 

Note that the second and third to last periods are starred (*). These periods are past the end of the month limit (29 days in February in leap years) and so they have been set to the same start and end period time .. a zero length period. Zero length periods call the application to print missing data strings for any descriptor listing the period number. Therefore, a report printing daily values for a month would print 29 daily data values, 2 blank strings (not zeroes), and the monthly total.

 

 

 

5.3 DATA ARCHIVING

The native DataWise® database is composed of two parts. A realtime part which holds the most recent 10,500 data values reported from a sensor and a historical or archived part into which data older than the last 10,500 reports is stored. The archived database has essentially unlimited storage. Storage of data into the historical (or archived) database is automatic. No manual intervention is required. Manual archiving and retrieving is provided by this program but is rarely if ever needed.

SPECIFY Archive drive first.

CHOOSE Tabular Data > Data Archiving on the Main DataWise® Menu. The Archive/Retrieve/View Archived Data screen is displayed. CLICK on Specify Archive Drive to select the drive where the archived data resides.       The Specify location of ARCHIVE files screen is displayed. Key in the correct letter of the drive on which archives reside. CLICK OK to return to the Archive/Retrieve/ View Archived Data screen. .

VIEW Archived data.

CHOOSE Tabular Data > Data Archiving on the Main DataWise® Menu. The Archive/Retrieve/View Archived Data screen is displayed. CLICK on View Sensor Data to view archived data. The View Archived Data screen is displayed.       SELECT the sensor from the Sensor drop-down list. SELECT the month from the Month drop-down list. SELECT the year from the Year drop-down list. CLICK on View raw data if you wish to view raw data, otherwise you will see converted data values. CLICK on OK.

 

 

 

 

	The Archived data report for selected month and year is displayed.
ARCHIVE Sensor data.	CHOOSE Tabular Data > Data Archiving on the Main DataWise® Menu. The Archive/Retrieve/ View Archived Data screen is displayed.   CLICK on Archive Sensor Data to archive data. The Archive screen is displayed.

 

 

 

SELECT the sensor from the Sensor drop-down list. SELECT the month from the Month drop-down list or SELECT Archive all months if you wish to archive an entire year. SELECT the year from the Year drop-down list. SELECT Archive data for all sensors if you wish to archive data for all sensors for the month and year specified. The default Directory is drive:\ARCHIVE with drive being the letter of the drive where DataWise® resides.     CLICK on Archive. The Completion, Archiving Done screen is displayed. Click on OK then EXIT to return to the Archive/Retrieve/ View Archived Data screen.

 

 

 

RETRIEVE Archived data.

CHOOSE Tabular Data > Data Archiving on the Main DataWise® Menu. The Archive/Retrieve/View Archived Data screen is displayed.   CLICK on Retrieve Archived Data to retrieve or put data back into the database. The Retrieve Sensor Data screen is displayed. SELECT the sensor from the Sensor drop-down list. SELECT the month from the Month drop-down list or SELECT Retrieve all months if you wish to retrieve an entire year. SELECT the year from the Year drop-down list. SELECT Retrieve data for all sensors if you wish to retrieve data for all sensors. ENTER the Directory where the data resides. The default is Drive:\ARCHIVE with Drive being the directory where DataWise® resides.   CLICK on Retrieve. The Completion, Retrieving Done screen is displayed. Click on OK then EXIT to return to the Archive/Retrieve/ View Archived Data screen.

 

 

5.4 MAPS

Sensor data can be plotted on maps in either dynamic or static form and using either historical or real-time data. DataWise® provides you with the option to work with sensor maps or data maps. The following sections explain how to define a map and how to display sensor and contour maps.

 

5.4.1 DEFINING MAPS

Before a map can be displayed, the sensors to be displayed on it and the map background itself must be defined. Map backgrounds can be either standard Bitmap files or Vector Maps, which can be produced from Geographic Information System (GIS) systems (such as, Arcinfo). There are two types of maps, one of which the data values are just plotted on the map and the other which use color and shading to produce a contour map such as isopleth analysis. Most users prefer the contour maps.

Bitmap map backgrounds must be stored in directory \dw\bitmaps. Maps are numbered. Map background 1 must be named: mapbackground1: map1.bmp - mapbackground 2: map2.bmp, etc.

Vector map backgrounds must be stored in directory \dw\param. Vector maps are also numbers. Vector map background 1 must be named mapbkgnd1.par, etc.

Before building maps, you must obtain a suitable map background (such as, a bitmap from a map source, or vector map from Arcinfo). DataWise® can provide maps for you as a custom service. Contact DEC Data Systems if needed.

Other things you will need to know are the latitude/longitude of your map(s) and the latitude/longitude of your sensors (which should have been defined in section 2.4.2 Defining Sensors when you configured DataWise®.

Follow the steps below to define a new sensor map.

DEFINE a new sensor map.	CHOOSE Edit > Define/Edit Maps from the Main DataWise® Menu. The Define Maps screen is displayed.     CHOOSE File > Add/Edit Map from the Define Maps screen. The Edit Map screen is displayed.
	ENTER Map Name (alphanumeric, limited to 40 characters) and coordinates: North, South, East and West. CLICK on Add. When you add a new map, it is automatically added to the list shown. CLICK on Copy boundaries from map if you would like to copy coordinates from a previously defined map. CLICK on Save. CLICK on X to return to the Define Maps screen.
EDIT an existing sensor map. Note You cannot edit map backgrounds. These must be imported as described in the beginning of this section (5.4.1.).	CHOOSE Edit > Define/Edit Maps from the Main DataWise® Menu. The Define Maps screen is displayed. CHOOSE File > Add/Edit Map. The Edit Map screen is displayed. SELECT a map to edit from the drop-down list. This is a list of all maps, which are in your database to date. ENTER new coordinates: North, South, East and West. CLICK on Save. CLICK on X to return to the Define Maps screen.
	ADD sensors to a map. CHOOSE Edit > Define/Edit Maps from the Main DataWise® Menu. The Define Maps screen is displayed. CHOOSE File > Select a Map from the Define Maps screen. The Select Map screen is displayed.
	SELECT a map to edit from the drop-down list by HIGHLIGHTing the map. CLICK on OK. This will take you back to the Define Maps screen.
	CHOOSE Sensors > Add/Delete Sensors. The Add/Remove Sensors in Map screen is displayed. Note The top list displays those sensors currently defined for the map. The bottom list displays all sensors in your database. HIGHLIGHT the sensor you want to add from the bottom list. CLICK on Add. If the sensor coordinates are defined (that is, does not show UNDEFINED in the Longitude/Latitude column), the Rated Value Confirmation screen is displayed. If you want to use the rated value, CLICK on Yes. The sensor moves to the top list showing it will be active on your chosen map. It also shows RATED in the Sensor Type column. If you do not want to use the rated value, CLICK on No. The sensor moves to the top list showing it is active on your chosen map. The sensor type is displayed in the Sensor Type column indicating that rated value was not chosen. Note If the sensor is already included in the top list (added to the chosen map), DataWise® will advise you. If the sensor coordinates are UNDEFINED, the Latitude/Longitude Not Defined screen is displayed. CLICK on OK. The sensor will not be moved to the top box indicating it is not active on the chosen map. Note You must go to the Edit Sensor procedure, section 2.4.2, to define sensor values. When finished adding sensors to the chosen map, CLICK on Done. You return to the Define Maps screen.
	REMOVE sensors from a map by CHOOSing Sensors > Add/Delete Sensors from the Define Maps screen. The Add/Remove Sensors in Map screen is displayed. Note The top list displays those sensors currently defined for the map. The bottom list displays all sensors in your database. HIGHLIGHT the sensor you want to remove from the top list. CLICK on Remove. The Delete Confirmation screen is displayed. If you want to delete the highlighted sensor, CLICK on Yes. The sensor will be moved to the bottom list. If you do not want to delete the sensor highlighted, CLICK on No. The sensor will not be moved to the bottom list. When finished removing sensors from the chosen map, CLICK on Done.

 

5.4.2 DISPLAYING SENSOR MAPS

Sensor data can be plotted on maps in either dynamic or static form and using either historical or real-time data. Most new backgrounds are bitmap files. Vector maps are included to allow you to keep your investment in old Enhanced ALERT or Data Command maps you may have.

Note

This section is discussing non-contour maps. See Section 5.4.3 for steps on displaying contour maps.

Map Options include:

• White Background: applicable to Vector Maps only. If it is selected, the map background is white; otherwise, the background is black. White Background does not apply to contour maps.
• Sensor Units: allows the abbreviated sensor units, as well as sensor values, to be displayed on the map.
• Time Step: used to specify the time period which a map is displayed. Choices include minutes, hours, or days.
• Ending Date/Time: is the valid time of the map. For example, you may want to see a map with data from a year ago. You may specify the valid time of map. By default, DataWise® will bring up current time data.
• Number of Periods: allows the user to specify the number of maps, which can be scrolled through, each with a time step specified in the Time Step field.
• Real-time Updating: allows the map to update in real-time at Update Interval minutes.
• Fixed Start Time: this allows a map to display a time period, which increases in length instead of staying fixed at the initial Time Step interval.
• Update Interval: allows you to set the frequency at which a map updates.

Follow the steps below to display sensor maps.

DISPLAY a sensor map.	CHOOSE Graphical Data > Maps or CLICK on the Maps icon (looks like a map and is 7th from top) on the Main DataWise® Menu. The Graphic Maps Setup screen is displayed. SELECT the desired map (by number and description) from the pull-down box. Note The map must have been previously defined as described in the steps for "Defining Sensor Map, above."
	CHOOSE the desired type of map background by either CHECKing or un-CHECKing the Vector Map box. Un-checked, a bitmap background will be used. CLICK on the box for the White Background for Vector Maps only. CLICK on the box for Sensor Units to display abbreviated sensor units as well as sensor values on the map. SCROLL to or TYPE in the Time Step to specify the time period (numeric), which a map will display. SELECT Minutes, Hours, or Days from the pull-down menu. ENTER Ending Date/Time in format mm/dd/yy xxxx. This is the valid time of the map. SCROLL to or TYPE in the Number of Periods to specify the number of maps which you want to be scrolled through, each with a time step specified in the Time Step field. CHECK Real-time Updating to format the map to update in real-time at Update Interval minutes. CHECK Fixed Start Time to set a map display time period which increases in length instead of staying fixed at the initial Time Step interval. ENTER the Update Interval (numeric). CLICK on Data Color to change the color on the sensors and sensor data. CLICK on Alarm Color to change the color on sensors associated with alarms CLICK on Text Color to change the text color of the map values. CHECK Opaque or Transparent to change the Data Values Background. CHECK Opaque or Transparent to change the Text Background. Note You may also change colors by using the file menu as discussed below. CHECK Show Sensors Only to display only the sensor locations on the map. You may then CLICK on any sensor number on the map to display the Show Data screen with data values. CHECK Full Screen Map to display a full screen map CLICK on Set Font to change the font
	CLICK on Start to display the DataWise® Map screen. The map shown is a typical precipitation map.
	CLICK with left mouse button on any sensor reading on the map to display the ShowData screen. Actual data values are shown.
NOTE If the map is updating in real-time, the time series plots also update. NOTE If more than one time period has been specified, scroll through them by clicking on the top window bar, right for forward in time, left for backwards.	CHOOSE a File > [option] depending on what you want to do. Options are: Print. Save to File. Data Color: changes the color on the sensors and sensor data. Alarm Color: changes the color on sensors associated with alarms. Text Color: changes the text color of the map values. White Background: toggles the map between a white and black background. Exit: takes you back to the Graphic Maps Setup screen. CLICK on X to leave the Graphic Maps Setup screen and again to return to the Main DataWise® Menu.

 

Note:

You may create a batch file to capture graphic maps files by creating a command line, similar to that shown below. It can be used in Scheduler to create maps automatically.


dwgmap d=mm/dd/yy t=hhmm s=lh g=map +old +white -s File = xxx.gif

 

• dwgmap – Program name other than contour maps.
• d=mm/dd/yy – Date
• t=hhmm – Time
• s=lh, s=1d, or s= – Time Step (hours, days, ?)
• g=map# -- Map number (user defined)
• +old -- For Vector Maps only; leave off otherwise
• +white -- For White Background
• -s -- To Leave Off Sensor Units
• file = xxx.gif, xxx.jpg, or xxx.bmp -- File Name (must be a gif, jpg, or bmp file); will make a map and write to a file which can be viewed on the Web.

 

5.4.3 DISPLAYING CONTOUR MAPS

Sensor data can be plotted on maps in isohyetal form in either dynamic or static form and using either historical or real-time data. The data required for the contour map is very similar to sensor maps, above. The screen, too, is similar, except that the screen contains no vector map option. Follow the steps below to display a contour or isohyetal map.

DISPLAY a contour or isohyetal map.	CHOOSE Graphical Data > Contour Maps on the Main DataWise® Menu. The Graphic Maps Setup screen is displayed.
	SELECT the desired map (by number and description) from the pull-down box. Note The map must have been previously defined as described in the steps for "Defining Sensor Map, above."
	CLICK on the box for the White Background for Vector Maps only. CLICK on the box for Sensor Units to display abbreviated sensor units as well as sensor values on the map. SCROLL to or TYPE in the Time Step to specify the time period (numeric), which a map will display. SELECT Minutes, Hours, or Days from the pull-down menu. ENTER Ending Date/Time in format mm/dd/yy xxxx. This is the valid time of the map. SCROLL to or TYPE in the Number of Periods to specify the number of maps which you want to be scrolled through, each with a time step specified in the Time Step field.
	CHECK Real-time Updating to format the map to update in real-time at Update Interval minutes. CHECK Fixed Start Time to set a map display time period which increases in length instead of staying fixed at the initial Time Step interval. ENTER the Update Interval (numeric). CLICK on Data Color to change the color on the sensors and sensor data. CLICK on Alarm Color to change the color on sensors associated with alarms. CLICK on Text Color to change the text color of the map values. CLICK on Opaque or Transparent for the Data Background and Text Background. To set up the Custom Map Colors for the Rain Rate Color Indicators SELECT a desired group number and ENTER a name. ENTER the reading in which you wish to assign a color to. CLICK on the color box to the left of the corresponding reading. The Color screen is displayed. This allows you to customize the color you want to appear for a corresponding reading. After desired color is selected CLICK on OK. Repeat these steps for all readings you wish to assign a color. ENTER a Threshold. CLICK on Save to save that color scheme. CHECK the Use Custom Colors box to apply one of these color schemes. CLICK on Set Font to change the font
	CLICK on Start to display a DataWise® [Contour] Map. CLICK with left mouse button on any sensor reading on the map to display the ShowData screen. Actual data values are shown on the left and a time series plot on the right. CHOOSE a File > [option] depending on what you want to do. Options are: Print. Save to File. Change Grid Size. Exit: takes you back to the Graphic Maps Setup screen. CLICK on the X box to leave the Graphic Maps Setup screen and return to the Main DataWise® Menu.

 

 

Note:

You may create a batch file to capture graphic maps files by creating a command line, similar to that shown below. It can be used in Scheduler to create maps automatically.




dwgmapcontour d=mm/dd/yy t=hhmm s=lh g=map +old +white -s File = xxx.gif

 

• dwgmapcountour – Program name—contour maps only.
• d=mm/dd/yy – Date
• t=hhmm – Time
• s=lh, s=1d, or s= – Time Step (hours, days, ?)
• g=map# -- Map number (user defined)
• +old -- For Vector Maps only; leave off otherwise
• +white -- For White Background
• -s -- To Leave Off Sensor Units
• file = xxx.gif, xxx.jpg, or xxx.bmp -- File Name (must be a gif, jpg, or bmp file); will make a map and write to a file which can be viewed on the Web.

 

 

 

5.5 TIME SERIES PLOTS

Data from up to four sensors can be plotted at one time. Graphs may be viewed in two different plotting packages: Old and New Style. The following sections describe steps to create old style and new style plots.

 

5.5.1 TIME SERIES PLOTS IN OLD STYLE

The following is a sample of an Old Style plot. The names of the sensors correspond to the colors. The Sensor name is shown. The sensor number is shown with a bar through it. The vertical axis is the data value. The horizontal value is the time.



 

Follow the steps below to plot data in Old Style.

 

PLOT data in Old Style.	CHOOSE Graphical Data > Graphs Old Style or CLICK on the Graph icon (5th from the top) on the Main DataWise® Menu. The Plot screen is displayed.
			CHOOSE Setup > Select Sensors from the Plot screen menu. The Sensors screen is displayed. ENTER the data fields shown in the screen to specify the parameters of the graph. ENTER Sensor ID number or choose from sensor menu box at lower left. CLICK on the Plot Rated Value box for each sensor if the sensor has an associated rating table (such as a water level sensor).
	CLICK on the Plot As Histogram box for each sensor entered, often used to plot rainfall data. CLICK on the Inverted Plot box for each sensor entered. This causes the scale to go from top to bottom. SELECT the desired Statistic for each sensor from the pull-down menu. ENTER the Ending Date/Time that you want the clock to stop. The format is mm/dd/yy xxxx (four digit numeric based on a 24-hour clock. SELECT a Time Step by CLICKing on the arrows for the pull-down menu. SELECT the Period Displayed by CLICKing on the arrows for the pull-down menu. This is the time length in days shown at the bottom of the plot. SELECT the Days to Scroll by CLICKing on the arrows for the pull-down menu. This is the number of days you want to scroll and view. CLICK on Update plot automatically and select time increment if you want to update automatically at given time intervals.
		CLICK on OK to see the plot based on the data you defined above. CHOOSE File > Print and/or File > Save to file options to record the plot. The plot can either be printed or saved as a file in .bmp, .jpg, or .gif formats. Note CLICKing the left or right arrow keys will cause the plot to scroll through all requested data. Note If you CLICK on the X box to exit the plot, DataWise® takes you back to the Main DataWise® Menu. If you want to return to the Sensors screen to adjust data or view other plots, CHOOSE Setup > Select Sensors from the Plot screen menu. CLICK on the X box or CHOOSE File > Exit to return to the Main DataWise® Menu.

 

 

5.5.2 TIME SERIES PLOTS IN NEW STYLE

Follow the steps below to plot data in New Style.

PLOT data in New Style.			CHOOSE Graphical Data > Graphs New Style or CLICK on the Bar Graph icon (6th from top) on the Main DataWise® Menu toolbar. The Sensor Plot screen is displayed.
			CLICK on Sensors > Sensors. The Select Sensors to Plot screen is displayed. ENTER the data fields shown in the screen to specify the parameters of the graph. ENTER Sensor ID number or choose from sensor menu box at lower left. Note To enter sensors easily, it is best to jot down the sensor IDs and enter them in the Sensor ID fields. Otherwise, you must CLICK on the Sensor ID field BEFORE highlighting a sensor from the box below. Do not click on the Sensor name field to do this.
			CLICK on the Separate box for one of sensors 2 through 4 to control which sensor is shown on the right axis. CLICK on the Plot Rated Value box for each sensor if the sensor has an associated rating table (such as a water level sensor). CLICK on the Plot As Histogram box for each sensor entered, often used to plot rainfall data.
		CLICK on the Inverted Plot box for each sensor entered. This causes the scale to go from top to bottom. SELECT the desired Statistic for each sensor from the pull-down menu. ENTER the Ending Date/Time that you want the clock to stop. The format is mm/dd/yy xxxx (four digit numeric based on a 24-hour clock. SELECT a Time Step by CLICKing on the arrows for the pull-down menu. SELECT the Period Displayed by CLICKing on the arrows for the pull-down menu. This is the time length in days shown at the bottom of the plot. SELECT the Days to Scroll by CLICKing on the arrows for the pull-down menu. This is the number of days you want to scroll and view.
			CLICK on OK to view plot. A plot similar to the figure shown is displayed. USE the icons at the top of the screen to Print, Save to File, or change most plot parameters. Note If you CLICK on the X box to exit the plot, DataWise® takes you back to the Main DataWise® Menu. If you want to return to the Select Sensors to Plot screen to adjust data or view other plots, CHOOSE Sensors > Sensors from the Sensor Plot screen menu.
	Note Click on any Icon to see all tools listed on tabs, with examples and additional details of each function. CLICK on the X box or CHOOSE File > Exit to return to the Main DataWise® Menu.

 

 

 

5.6 VIEWING ANIMATED GRAPHICS

The DataWise® "Animated Graphics" application allows the display of data in a wide variety of graphical formats. Historical or real-time data can be displayed.

For in depth instructions on using the Graphic Design Tool see Section 9.11 Graphic Design Screen

Animated Graphics screens are stored as text files with extension .tpt and reside in directory \DW\Templet. The DataWise® Graphic Design Tool is used to develop these animated graphic screens, however, the text files that describe the screens can be manually editing with a text editor. The commands are listed in Appendix A in the Datawise Users Manual. The program to display animated graphics screens is accessed by selecting the "View" pull-down menu from the main DataWise® screen and selecting "Animated Graphics" as shown in Figure 1, or by clicking the "Animated Graphics" button on the main DataWise® menu. Figure 1. Displaying animated graphics screens   The default screen displayed is "ctrlpanel.tpt". Other screens can be displayed by selecting them from the "File" pull-down menu of the animated graphics screen. The animated graphics display program, \DW\Utils\overview.exe can be started with one runtime option, that being the name of the templet to show at startup time. New screens can be designed or existing screens modified by selecting the "Graphic Screen Design" menu item from the "Tools" pull-down menu (Figure 2) as described in Section 9.11 Graphic Design Screen . Figure 2. Selecting "Graphic Screen Design"

 

 

 

 

 

 

5.7 PRECIPITATION REPORTS

DataWise® provides an extensive suite of precipitation analysis routines, collectively referred to as Precipitation Reports. Five different types of reports can be generated.

• The Hourly (Annual) Report produces a report of hourly rainfall data (by month) for the number of months requested.
• The Annual Maximum Report produces a report of rainfall intensities for various time periods according to the number of months selected.
• The Daily Report produces the daily rainfall for a year (or for the number of months selected).
• An Hourly (Month) Report produces a report showing the hourly rainfall by month for each month selected. Also contained in the report are the maximum rainfall intensities for various time periods.
• The Yearly (Multiple) report enables you to view yearly precipitation reports over a period of years.

Subsections 5.7.1 through 5.7.6 give you steps for creating each of these precipitation reports.

Before viewing any of the five types of precipitation reports DataWise® provides, you must create a group of sensors. Precipitation reports can be produced for groups of predefined sensors or from sensors selected at report generation time.

The following steps explain how to create groups of sensors for precipitation reports.

CREATE groups of sensors for Precipitation Reports.	CHOOSE View > Precipitation Reports from the Main DataWise® Menu. The Precipitation Reports screen is displayed.
	CHOOSE File > Edit Groups. The Edit Sensor Group screen is displayed. To CREATE a new group, follow the steps below: CLICK on Add at the top of the screen next to the Select Group box. DataWise® adds a group and sequentially numbers it after the last group number. (If no groups are defined, DataWise® numbers it Group 1.) Or CLICK between two groups in the Select Group box and CLICK on Insert. The new group is inserted at that point and is given the next sequential group number. All other groups are renumbered sequentially. To RENAME a new group, HIGHLIGHT the group and CLICK on Edit. The Edit Group Name screen is displayed. ENTER a name of your choice in alphanumeric format (special characters allowed) and limited to 22 characters. CLICK on OK to return to the Edit Sensor Groups screen. HIGHLIGHT the new group. SELECT sensors from the Sensors defined box in the lower right of the screen by HIGHLIGHTing them. CLICK on Add after each selection. Selected sensors are shown in the Sensors in group box in the lower left of the screen. Note If you make a mistake, SELECT the sensor you do not want and CLICK on the Remove box. DataWise® asks you to confirm that you want the sensor deleted. CLICK on Yes to confirm.   REPEAT these steps until all new groups and associated sensors have been added. CLICK on OK to return to the Precipitation Reports screen.
	To CHANGE an existing group: SELECT a group from the Select Group box at the top left of the screen. SELECT the sensors you want added to the group from the Sensors defined box in the lower right. CLICK on Add after each selection. Selected sensors are shown in the Sensors in group box in the lower left of the screen.   Note If you make a mistake, SELECT the sensor you do not want and CLICK on the Remove box. DataWise® asks you to confirm that you want the sensor deleted. CLICK on Yes to confirm. REPEAT these steps until all new groups and associated sensors have been added. CLICK on OK to save changes to the sensor group definition.

 

5.7.1 CREATE AN HOURLY (ANNUAL) REPORT

The following is an example of an Hourly (Annual) Report as it looks from your screen.



 

Follow the steps below to create an Hourly (Annual) Report.

CREATE an Hourly (Annual) Report.		CHOOSE View > Precipitation Reports from the Main DataWise® Menu. The Precipitation Reports screen is displayed.
		CHOOSE Reports > Hourly (Annual). The Annual Monthly Precipitation Report screen is displayed. ENTER data requested to define the parameters of the report. CLICK By Group or By Sensor under the Create Report box at the top of the screen. If you chose By Group for the report, SELECT a group from the pull-down list in the Group Name box. The sensors in that selected group are shown in the Sensor ID Name pull-down box to the right of the screen. If you chose By Sensor(s) for the report, SELECT a sensor from the pull-down list in the Sensor ID Name box.
	SELECT a starting Month from the pull-down list. SELECT the Year for which you want the report from the pull-down list. SELECT the Number of Months to be included in report from the pull-down list. CLICK on Output to file if you want to save as a file instead of viewing on your monitor. CLICK on OK to view an Annual Monthly Precipitation Report (similar to the one shown above). Note The toolbar at the top of the Report screen provides options for Change Font, Copy to Clipboard, Print, Print as Text, Save as, and Exit.
	CHOOSE File > Exit or CLICK on the Exit icon or on the X box to return to the Annual Monthly Precipitation Report screen. CHANGE your entries to create a new report by following the steps above OR CLICK on the X box to return to the Precipitation Reports screen.

 

 

5.7.2 CREATE AN ANNUAL MAXIMUM RAINFALL REPORT

The following is an example of an Annual Maximum Rainfall Report as it looks from your screen.



 

Follow the steps below to create an Annual Maximum Rainfall Report.

 

 

CREATE an Annual Maximum Rainfall Report.	CHOOSE View > Precipitation Reports from the Main DataWise® Menu. The Precipitation Reports screen is displayed.
	CHOOSE Reports > Annual Max. The Annual Maximum Rainfall Report screen is displayed. ENTER the edit fields to define the parameters of the report. CLICK on By Group or By Sensor under the Create Report box at the top of the screen. If you chose By Group for the report, SELECT a group from the pull-down list in the Group Name box. The sensors in that selected group are shown in the Sensor Name pull-down box to the right of the screen. If you chose By Sensor(s) for the report, SELECT a sensor from the pull-down list in the Sensor Name box.
	SELECT a starting Month from the pull-down list. SELECT the Year for which you want the report from the pull-down list. SELECT the Number of Months to be included in report from the pull-down list. CLICK on 5/10-minute durations if you want to see shorter periods of data and if telemetry systems support real-time data acquisition (such as for ALERT systems). CLICK on Output to file if you want to save as a file instead of viewing on your monitor. CLICK on OK to view an Annual Maximum Rainfall Report similar to the one shown above. Note The toolbar at the top of the Report screen provides options for Change Font, Copy to Clipboard, Print, Print as Text, Save as, and Exit. CHOOSE File > Exit or CLICK on the Exit icon or on the X box to return to the Annual Maximum Rainfall Report screen. CHANGE your entries to create a new report by following the steps above OR CLICK on the X box to return to the Precipitation Reports screen.

 

 

5.7.3 CREATE A DAILY PRECIPITATION REPORT

The following is an example of a Daily Precipitation Report as it looks from your screen.



 

Follow the steps below to create a Daily Precipitation Report.

 

 

CREATE a Daily Precipitation Report.		CHOOSE View > Precipitation Reports from the Main DataWise® Menu. The Precipitation Reports screen is displayed.
		CHOOSE Reports > Daily Report. The Daily Precipitation Report screen is displayed. ENTER the edit fields to define the parameters of the report. CLICK on By Group or By Sensor(s) under the Create Report box at the top of the screen. If you chose By Group for the report, SELECT a group from the pull-down list in the Group Name box. The sensors in that selected group are shown in the Sensor ID Name pull-down box to the right of the screen. If you chose By Sensor(s) for the report, SELECT a sensor from the pull-down list in the Sensor ID Name box.
	SELECT a Starting Month from the pull-down list. SELECT the End Year for which you want the report from the pull-down list. SELECT the Number of Months to be included in report from the pull-down list. CLICK on Output to file if you want to save as a file instead of viewing on your monitor. CLICK on OK to view a Daily Precipitation Report similar to the one shown above. Note The toolbar at the top of the Report screen provides options for Change Font, Copy to Clipboard, Print, Print as Text, Save as, and Exit. CHOOSE File > Exit or CLICK on the Exit icon or on the X box to return to the Daily Precipitaiton Report screen. CHANGE your entries to create a new report by following the steps above OR CLICK on the X box to return to the Precipitation Reports screen.

 

 

5.7.4 CREATE AN HOURLY (MONTH) REPORT

The following is an example of an Hourly (Month) Report as it looks from your screen.



 

Follow the steps below to create an Hourly (Month) Report.

 

 

CREATE an Hourly (Month) Report.	CHOOSE View > Precipitation Reports from the Main DataWise® Menu. The Precipitation Reports screen is displayed.
	CHOOSE Reports > Hourly (Month). The Hourly Precipitation Report (One Month Period) screen is displayed. ENTER the edit fields to define the parameters of the report. CLICK on By Group or By Sensor(s) under the Create Report box at the top of the screen. If you chose By Group for the report, SELECT a group from the pull-down list in the Group Name box. The sensors in that selected group are shown in the Sensor ID Name pull-down box to the right of the screen. If you chose By Sensor(s) for the report, SELECT a sensor from the pull-down list in the Sensor ID Name box.
	SELECT a starting Month from the pull-down list. SELECT the Year for which you want the report from the pull-down list. CLICK on 5/10-minute durations if you want to see shorter periods of data and if telemetry systems support real-time data acquisition (such as for ALERT systems). CLICK on Output to file if you want to save as a file instead of viewing on your monitor. CLICK on OK to view an Hourly Precipitation Report similar to the one shown above. Note The toolbar at the top of the Report screen provides options for Change Font, Copy to Clipboard, Print, Print as Text, Save as, and Exit. CHOOSE File > Exit or CLICK on the Exit icon or on the X box to return to the Hourly Precipitation Report (One Month Period) screen. CHANGE your entries to create a new report by following the steps above OR CLICK on the X box to return to the Precipitation Reports screen.

 

 

5.7.5 CREATE A YEARLY (MULTIPLE) REPORT

The following is an example of a Yearly (Multiple) Report as it looks from your screen.

Note

This report is not computed off of the real-time database. This was an add-on capability. You must manually create some configuration files for this to work correctly. If you need this report, contact DEC Data Systems before trying to create this report.



 

Follow the steps below to create a Yearly (Multiple) Report.

 

 

CREATE a Yearly (Multiple) Report.	CHOOSE View > Precipitation Reports from the Main DataWise® Menu. The Precipitation Reports screen is displayed.
	CHOOSE Reports > Yearly (Multiple). The Multiple Year Precipitation Report screen is displayed. ENTER the edit fields to define the parameters of the report. CLICK on By Group or By Sensor(s) under the Create Report box at the top of the screen. If you chose By Group for the report, SELECT a group from the pull-down list in the Group Name box. The sensors in that selected group are shown in the Sensor ID Name pull-down box to the right of the screen. If you chose By Sensor(s) for the report, SELECT a sensor from the pull-down list in the Sensor ID Name box.
	SELECT a Start Year from the pull-down list. SELECT the End Year for which you want the report from the pull-down list. SELECT a Starting Month from the pull-down list. SELECT the Number of Months to be included in report from the pull-down list. CLICK on Output to file if you want to save as a file instead of viewing on your monitor. CLICK on OK to view a Multiple Year Precipitation Report similar to the one shown above. Note The toolbar at the top of the Report screen provides options for Change Font, Copy to Clipboard, Print, Print as Text, Save as, and Exit. CHOOSE File > Exit or CLICK on the Exit icon or on the X box to return to the Multiple Year Precipitation Report screen. CHANGE your entries to create a new report by following the steps above OR CLICK on the X box to return to the Precipitation Reports screen. CHOOSE File > Exit or CLICK on the X box to return to the Main DataWise® Menu.

 

 

 

5.7.6 CREATE A DAYS WITH PRECIPITATION REPORT

The following is an example of a Days with Precipitation Report as it looks from your screen.



 

Follow the steps below to create a Days with Precipitation Report.

CREATE a Days with Precipitation Report.

CHOOSE View > Precipitation Reports from the Main DataWise® Menu. The Precipitation Reports screen is displayed. CHOOSE Reports > Days with Rain. The Count screen is displayed. ENTER the edit fields to define the parameters of the report. CLICK on By Group or By Sensor(s) under the Create Report box at the top of the screen. If you chose By Group for the report, SELECT a group from the pull-down list in the Group Name box. The sensors in that selected group are shown in the Sensor ID Name pull-down box to the right of the screen. If you chose By Sensor(s) for the report, SELECT a sensor from the pull-down list in the Sensor ID Name box. SELECT a Starting Month from the pull-down list. SELECT the End Year for which you want the report from the pull-down list. SELECT the Number of Months to be included in report from the pull-down list. CLICK on Output to file if you want to save as a file instead of viewing on your monitor. CLICK on OK to view a Days with Precipitaton Report similar to the one shown above. Note The toolbar at the top of the Report screen provides options for Change Font, Copy to Clipboard, Print, Print as Text, Save as, and Exit. CHOOSE File > Exit or CLICK on the Exit icon or on the X box to return to the Multiple Year Precipitation Report screen. CHANGE your entries to create a new report by following the steps above OR CLICK on the X box to return to the Precipitation Reports screen. CHOOSE File > Exit or CLICK on the X box to return to the Main DataWise® Menu.

 

 

 

 

5.8 VIEWING POLLING LOG

This program allows a user to view a record of all data collection activities.

VIEW Polling Log

CHOOSE Logs > Polling Log from the Main DataWise® Menu. The View Polling Log screen is displayed.   CLICK on Refresh to purge contents of log file. CLICK on Exit to return to the Main DataWise® Menu.

 

 

 

5.9 VIEWING SYSTEM LOG

This program allows a user to view a log of all dates and times DataWise® was started and stopped.

CHOOSE Logs > System Log from the Main DataWise® Menu. The Start/Stop Log screen is displayed.       CLICK on Purge Log to purge contents of log file. The Save dialog box is displayed.   CLICK on Yes if you wish to save contents of log to a file. The Save As dialog box is displayed.   CLICK on Save. The file will be stored in \DW\Log in the format of SysStrt.mm.dd.yyyy.

 

6.0 Hydrologic Analysis and Forecasting

DataWise® comes standard with headwater forecasting modules based on the Sacramento Soil Moisture Accounting model. Additional modules are available to provide interfaces to HECIF. In addition, various channel and reservoir routing models are included as part of the basic system. Use of this software requires hydrological back ground and operation of the model is covered in SACRAMENTO SOIL MOISTURE ACCOUNTING MODEL by ROBERT J. C. BURNASH & LARRY FERREL, U.S.NATIONAL WEATHER SERVICE, SACRAMENTO RIVER FORCAST OFFICE, SACRAMENTO, CALIFORNIA.

 

 

6.1 HEADWATER FORECASTING

The Headwater Forecasting Model uses the code developed by the National Weather Service.

		CHOOSE Models > Watershed Model from the Main DataWise® Menu. The SSMA Parameter Definition screen is displayed. SELECT a Watershed from Watershed list Box. If you select an Undefined the program will define it.   CHECK the Forecasting Active Box to turn on all headwater forecasting. Unchecking will turn all headwater forecasting off.   CLICK on DELETE to delete a selected forecast point. CLICK on ENGLISH for units in inches or METRIC for units in millimeters. CLICK on Disabled or Active in the Status box to disable or enable a selected point.   SELECT a Time Step by scrolling up or down in the Time Step edit field to choose how often the model will run. You must select from one of the available time steps.   ENTER the size of the basin in the Drainage Area field.   ENTER the Mean Daily Potential Evapo-transpiration for each month. This is the average Evapotranspiration per day for that month, in inches if English units checked or millimeters if Metric checked.
	To complete the remaining parameters refer to documentation on the Sacramento Soil Moisture Accounting Model for a complete definition. UZTW - Upper zone tension water. Enter value for capacity and contents. UZFW - Upper zone free water. Enter value for capacity and contents. LZTW - Lower zone tension water. Enter value for capacity and contents. LZFWS - Lower zone free water supplemental. Enter value for capacity and contents. LZFWP - Lower zone free water primary. Enter value for capacity and contents. ADIMP - Additional Impervious. ADIMC - Additional Impervious contents. PFREE - Percolation parameter - rate of percolation. UZK - Upper zone drainage rate coefficient. LZSK - Lower zone supplemental coefficient. LZPK - Lower zone primary coefficient. REXP - Shape of percolation curve.
		CLICK on Precip from the SSMA Parameter Definition screen. The Precipitation Sensors screen is displayed. SELECT the Sensors you wish to use to compute the mean basin rainfall. The formula for mean basin rainfall is as follows. Mean basin precip = å (WT(I) x SIG(I) x RAIN(I)) / å SIG(I) Where WT(I) = Weight of Ith Sensor, SIG(I) = Significance of Ith sensor, RAIN(I) = period rainfall for the Ith sensor. CLICK on Add and the sensor will appear in the box on left with the following values. Weight - Used to a scale factor that when multiplying X rainfall at the sensor, gives an estimate of mean basin rainfall. Significance - Measure of the relative importance of the site compared to other sites. In Use - Yes means site will be used in computation of mean basin rainfall. This can be turned on or off. CLICK on Edit to change the values listed above. CLICK on Delete to delete a selected sensor.     CLICK on Unitgraph from the SSMA Parameter Definition screen. The Unitgraph screen is displayed. See documentation on Sacramento Soil Moisture Accounting Model for complete instructions.             CLICK on Import to browse to select a file. The Import from File screen is displayed. See documentation on Sacramento Soil Moisture Accounting Model for complete instructions.   CLICK on Insert to insert a unitgraph entry. The Edit / Add Untigraph Entries screen is displayed. See documentation on Sacramento Soil Moisture Accounting Model for complete instructions. CLICK on Delete to delete a unitgraph entry.   CLICK on Save to save and exit.       CLICK on Routing from the SSMA Parameter Definition screen. The Routing screen is displayed. See documentation on Sacramento Soil Moisture Accounting Model for complete instructions on this screen.               CLICK on OK to return to the SSMA Parameter Definition screen.               After all entries are correct CLICK on Save then Exit to return to the Main DataWise® Menu.

 

 

 

 

 

 

 

6.2 CHANNEL/RESERVOIR FORECASTING

The Channel/Reservoir Forecasting Model routing is based on a layered K&L method.

		CHOOSE Models > Channel / Reservoir Model from the Main DataWise® Menu. The Routing Initialization screen is displayed. CHECK the Channel / Reservoir System Enabled box to produce a forecast by routing model. Routing Model will not run if unchecked. CLICK on Enabled to define a river system then ENTER its name in the River System Edit field. CLICK the numbered button under Edit to define the parameters for the new river system. The River System screen is displayed. CHECK a numbered box under Options if you want to produce a forecast for a rainfall scenario for that number. These are precipitation scenarios that are defined using Models > Precipitation Scenarios. See following section 6.3.If no boxes checked, it will only produce a report with no additional rainfall. For each forecast point you want to define CLICK disabled. The Reservoir Query screen will be displayed.   CLICK Yes for a reservoir or No for a Channel. If you CLICK No you will have a new CHANNEL button under Routing Parms on the River System screen. If you CLICK Yes you will have 2 new buttons RESERVOIR and INFLOW.   CLICK on the Inflow button next to the CHANNEL button to bring up the Inflow Select screen to define inflows for that point.     CLICK on the Upstream Headwater Inflows to define each upstream headwater inflow. The Upstream Headwater Inflows screen will appear.
	SELECT the Upstream Headwater Inflow Point by scrolling up or down below the # sign. ENTER the Lag. This is the delay in minutes from where headwater is being forecast to where the channel forecast point is. ENTER the Multi-plication Scale Factor Usually 1, if larger it is meant to take into account uncalibrated or ungaged local inflows. ENTER the ID#. This is the sensor ID # of the water level device at the headwater point. Can be blank. CHECK Adjustment Flag if you want the forecast adjusted based on what is being observed at the upstream forecast point. CLICK on OK to bring you back to the Inflow Select screen. CLICK on Downstream Headwater Inflows to define each downstream headwater inflow. The Downstream Headwater Inflows screen will appear.
	SELECT the Downstream Headwater Inflow Point by scrolling up or down below the # sign. ENTER the Lag. This is the delay in minutes from where headwater is being forecast to where the channel forecast point is. ENTER the Multi-plication Scale Factor Usually 1, if larger it is meant to take into account uncalibrated or ungaged local inflows. ENTER the ID#. This is the sensor ID # of the water level device at the headwater point. Can be blank. CHECK Adjustment Flag if you want the forecast adjusted based on what is being observed at the upstream forecast point. CLICK on OK to bring you back to the Inflow Select screen. CLICK on Upstream Mainstem Inflows to define each upstream mainstem inflow. The Upstream Mainstem Inflows screen will appear.
	SELECT the River # and Forecast Point # on river by scrolling up or down on scrollbar. ENTER the Lag. This is the time in minutes it takes water to get from where it is upstream to where you are forecasting at. ENTER the Sensor ID#. This can be blank. CHECK Adjustment Flag if you want the forecast adjusted based on what is being observed at the upstream forecast point. CLICK on SAVE then CANCEL to bring you back to the Inflow Select screen. CLICK on Downstream Mainstem Inflows to define each downstream mainstem inflow. The Downstream Mainstem Inflows screen will appear.     SELECT the River # and Forecast Point # on river by scrolling up or down on scrollbar. ENTER the Lag. This is the time in minutes it takes water to get from where it is upstream to where you are forecasting at. ENTER the Sensor ID#. This can be blank. CHECK Adjustment Flag if you want the forecast adjusted based on what is being observed at the upstream forecast point.   CLICK on SAVE then CANCEL to bring you back to the Inflow Select screen.   CLICK on DONE to bring you back to the River System screen.         CLICK on CHANNEL to input Routing Parameters. The Configure Routing Parameters screen will appear.                 Input the desired Routing Parameters. For Layer - Metric is cubic meters per second, English is cubic feet per second.                 If you CLICKED YES on the Reservoir Query screen, you will have 2 buttons. RESERVOIR and OUTFLOW.   CLICK on the Inflow button next to the RESERVOIR button to bring up the Inflow Select screen to define inflows for that point. See above Instructions under Channel to define inflows. CLICK on the RESERVOIR button to bring up the Reservoir Routing / Reservoir Configuration Choice screen. CLICK on the Routing Parameters button to bring up the Configure Routing Parameters screen.     Input the desired Routing Parameters. For Layer - Metric is cubic meters per second, English is cubic feet per second.   CLICK on OK to return to the Reservoir Routing / Reservoir Configuration Choice screen.   CLICK on the Reservoir Configuration button to bring up the Reservoir Configuration screen. If no Gated Outflows - UNCHECK. If there are gated openings then you need to have a sensor defined for each gated opening that measures how far open the gate is. To do this CHECK Gated Outflows then CLICK on the Edit Configuration button for Gated Outflows. The Gated Outflow Configuration screen will appear.

		ENTER the Sensor Number and Elevation at bottom of gate for each Gate.   CLICK on the OK to return to the Reservoir Configuration screen.
	CHECK Un-Gated Spillways then CLICK on the Edit Configuration button for Un-Gated Spillways.       The Spillways screen is displayed.

		ENTER the Rating Table Number for the spillway or "None" and Elevation at the bottom of spillway for each spillway. You will need to have previously entered rating tables for each spillway being used. To do this use Configure Rating Tables. CLICK on the OK to return to the Reservoir Configuration screen.
	CHECK Hydro-Electric Generation Outflows then CLICK on the Edit Configuration button for Hydro-Electric Generation Outflows.   The Hydropower screen is displayed.       ENTER a Sensor Number in the edit field for each Generator. Each generator needs to have a sensor associated with it. In the Outflow Determined By Field: CHECK Power Generated by Turbine if you have a sensor that measures the power being generated by that turbine and sensor must have a rating table associated with it that converts power being generated by the turbine to flow going through the turbine. CHECK Flow Passing Through Turbine if you have a sensor that just measures the flow going to the turbine, usually a manually input sensor. ENTER Tailwater Sensor if tailwater needs to be taken into account. CLICK on OK to return to the Reservoir Configuration screen. CHECK Lake Surface Evaporation then CLICK on the Edit Configuration button for Lake Surface Evaporation. The Lake Surface Evaporation screen is displayed.     CHECK Monthly or Weekly in the Evaporation Specification field. For each month or week, depending on which is checked, ENTER the daily amount of evaporation off the lake. ENTER the Rating Table #.     CLICK on Save then Cancel to return to the Reservoir Configuration screen.           CLICK on OK then DONE to return to the River System screen.     CLICK on the OUTFLOW button to bring up the Configure Routing Parameters screen.                     ENTER desired Routing Parameters.   CLICK on OK to return to the River System screen.             CLICK on Save then Done to return to the Routing Initialization screen then Save then Exit to return to the main DataWise® Menu.

 

 

 

6.3 PRECIPITATION SCENARIOS

 

CHOOSE Models > Precipitation Scenarios from the Main DataWise® Menu. The Define Forecasted Precipitation screen is displayed. CLICK on a Case to define a precip. scenario. Ex. What if it rains this much in this much time. For each headwater point, you can define up to 5 cases.   The Case # Precipitation Scenarios screen will appear. ENTER the Amount of Rain and Time period in which it will occur for each period. CLICK on OK to return to the Define Forecasted Precipitation screen then Exit to return to the main DataWise® Menu.

 

 

 

 

7.0 ALARM MANAGEMENT

DataWise® supports an extensive array of alarm evaluation and alarm response functions. DataWise® supports up to 32,000 different types of alarm actions to be taken when an alarm occurs. Alarm actions can range from simply beeping and flashing on a computer screen to providing automated paging, faxing, or e-mail. The actions can also be as complex as actually controlling pumps and gates.

DataWise® comes standard with alphanumeric paging support for most known pagers. Supporting software is provided for any currently unsupported pager protocol. DataWise® alarm handling functions include Dectalk as well as many of the more modern speech synthesizer cards.

Alarms fall into two basic categories: Simple Alarms and Complex Alarms.

• Simple Alarms are based on conditions occurring at a single sensor. An example of a simple alarm condition is rainfall rate at a given sensor above preset conditions or water level above a certain level and still rising.

Note

Section 2.4.3 of this User’s Manual provides instructions for defining Simple Sensor Alarms.

• Complex Alarms are based on conditions occurring at multiple sensors. Complex alarm conditions are actually implemented using an Expert System that has been incorporated into DataWise®. In this system, alarm conditions are entered as "IF, THEN, ELSE" statements. Very complex alarm conditions can be implemented in this manner. An example of a complex alarm evaluation would be requiring high rainfall rates at several rain gauges and the water level at one or more stream gauges. Subsection 7.5, below, provides steps for defining Complex Alarms.

The remaining subsections give instructions for other alarm management activities, including:

• Viewing Alarms
• Email Alarm Configuration
• Contact Closure Alarms
• Testing Alarms
• Defining Complex Alarms

 

 

 

7.1 VIEWING ALARMS

Whenever alarm conditions are met for a sensor, an alarm is generated and an entry in the system’s alarm log is generated. Follow the steps below to view alarms.

 

VIEW Active Alarms.	CHOOSE Tabular Data > Alarms from the Main DataWise® Menu. The Alarm Display screen is displayed. Note This same screen is automatically displayed when an alarm is generated.
	CHOOSE View Alarms > Active Alarms from the Alarm Display screen menu. If your system has no active alarms, DataWise® displays the No Alarms screen. If you have active alarms, a list is displayed on the Display screen. The top list box contains the list of currently active alarms.   HIGHLIGHT an alarm from the top list. The bottom box shows a detailed description of the cause of the alarm, such as its time of occurrence, and when and if it was acknowledged and by whom. Note CLICK on Alarm Off to turn the audible portion off; this does not acknowledge the alarm. CLICK on Acknowledge to turn the alarm off and acknowledge it.   CLICK on Finish to return to the Alarm Display screen
VIEW Historical Alarms.	CHOOSE Tabular Data > Alarms from the Main DataWise® Menu. The Alarm Display screen is displayed.
	CHOOSE View Alarms > Historical Alarms. The Historical screen is displayed. If your system has no historical alarms, DataWise® displays the No Alarms screen.. If you have historical alarms, a list is displayed on the Historical screen. The top list box contains the list of currently active alarms, showing the Type and Cause of the alarm, including sensor ID, sensor Name, and Date and Time of occurrence.. HIGHLIGHT an alarm from the top list. The bottom list shows a detailed description of the cause of the alarm, such as its time of occurrence, and when and if it was acknowledged and by whom.
	CLICK on Change log files to import a saved log file from an earlier session. The Open screen is displayed. From this screen you may select the required file. CLICK on Cancel or on the X box to return to the Historical screen. CLICK on Okay or on the X box to return to the Alarm Display screen. CLICK on X box to return to the from the Main DataWise® Menu.
Print Alarm Files.	CHOOSE Tabular Data > Alarms from the Main DataWise® Menu. The Alarm Display screen is displayed.
	CHOOSE View Alarms > Print Alarms from the Alarm Display screen. The Print Alarms screen is displayed. SELECT the Alarm, Sensor and details you wish to print then SELECT OK     SELECT PRINT from the generated log file to send it to the printer.
CHANGE Wave Sounds.	CHOOSE Tabular Data > Alarms from the Main DataWise® Menu. The Alarm Display screen is displayed. SELECT Wave Sounds > Import Wave File. The Open screen is displayed.
	Here you can BROWSE to find wave files to associate with specific alarm conditions. SELECT the sound you prefer and CLICK on Open. This will import the selected wave file, making it available for linking to a specific alarm condition.       SELECT Link Wave Files to link a selected wave file to a specific sensor and alarm condition. The Wave Files screen will be displayed.         HIGHLIGHT the Sensor, Alarm Action and Wave File you wish to play for the selected alarm condition. CLICK on ADD. Do this for as many sensors/alarm actions as you wish then CLICK Save and Done to return to the Alarm Display screen.
PURGE Alarms.	CHOOSE Tabular Data > Alarms from the Main DataWise® Menu. The Alarm Display screen is displayed.
	CHOOSE Purge > Purge Log. The Purge confirmation screen is displayed. CLICK on Yes to save the current log. The Save As screen is displayed. ENTER a filename or SAVE to the filename DataWise® provides. CLICK on Cancel or on the X box to return to the Alarm Display screen. CLICK on the X box to return to the from the Main DataWise® Menu.

 

 

7.2 EMAIL ALARM CONFIGURATION

This allows a DataWise® user to set up an email address file to be used to send notifications if an alarm occurs on a specific alarm action or port. In order for this to work you must also set up an alarm action for each port for which you set up an email address file. This is set up under Define Sensors -> Add/Edit Alarm Actions as described in section 2.4.5. Also, to use this feature you must install SendmimePro on your server. Contact DEC Data Systems for information on obtaining and installing this program.

CHOOSE Configure > Email Alarms Configuration from the Main DataWise® Menu. The Email Alarms Configuration screen is displayed. SELECT an Alarm Action #. This is the port on which an action will be taken if an alarm occurs. CHECK Bypass MTA if you want to bypass Server Address and send mail directly from Sender Address to Email Address list. ENTER the Server Address (SMTP). ENTER the Sender Address. ENTER the Email Addresses of the contacts to be notified if an alarm occurs. CLICK on Save and Done to store this information in a file and return to the Main DataWise® Menu. To DELETE an Email Address File for an alarm action, SELECT the Alarm Action #. CLICK on the Delete button. You will get a Delete Confirmation message box. CLICK on Yes to continue with the delete or No to cancel.   CLICK on Done to return to the Main DataWise® Menu.

 

 

 

7.3 CONTACT CLOSURE ALARMS

This allows a DataWise® user to set up a control for an action to be performed if an alarm condition occurs on a specific alarm action or port. Examples of this could be to turn on a light, siren, strobe, etc.

CHOOSE Configure > Contact Closure Alarms from the Main DataWise® Menu. The Contact Closure Configuration screen is displayed.                   SELECT an Alarm Action #. This is the port on which an action will be taken if an alarm occurs. SELECT the Digital I/O Port. SELECT the Contact closure time in milliseconds.

 

 

7.4 TESTING ALARMS

This is often used to test a new alarm added to the system to ensure it has been connected correctly. To change a voice alarm telephone number, follow the steps below.

TEST Alarms.		CHOOSE Tools > Test Alarms from the Main DataWise® Menu. The Test Alarms screen is displayed. CHOOSE the alarms you wish to test. SELECT the Alarm Port from the pull-down menu. This sends the alarm to the specified location. CLICK on System Condition or Sensor ID in the Alarm By box.
	CHOOSE the System Condition you want to test. CHOOSE the Sensor ID to choose the sensor you want to test. CLICK on either Data Value or Keyword to Specify Alarm Cause. If you CLICK on Data Value, ENTER the value in the Data Value field. If you CLICK on Keyword, SELECT a value from the pull-down Keyword menu. The Date/Time of Alarms is automatically generated by DataWise® or you may ENTER a value in mm/dd/yy hh:mm:ss format. CLICK on OK to generate an alarm. The Alarm Display screen will come up. If the Alarm Display screen is already up, the data on the screen will be updated. SELECT View Alarms > Active Alarms to see the alarm just generated. CLICK on Acknowledge to turn the alarm off. CLICK on Finish to return to the Alarm Display screen. CLICK on Exit to return to the Main DataWise® Menu.

 

 

 

 

7.5 DEFINE COMPLEX ALARMS

Definition of complex alarms requires the use of text editor and knowledge of commands. Contact DEC Data Systems for specific help on this subject.

 

 

 

8.0 WEB TOOLS

DataWise® provides the tools to create static and interactive maps, plots, and tabular data on user's web pages.

This allows a user to view their data from an off-site location by dialing in or through the internet or intranet. These access capabilities are through any browser and no client software is required.

 

8.1 BROWSER INTERFACE

 

INSTALLing DataWise® Web Server

FROM the DataWise® Install Screen.   CLICK on Install DataWise® Web Server.       You will see a series of status screens as shown here while it is being installed. This will take some time.   After the install is complete you should be able to bring up the browser interface : Insure that DW is running. Bring up a browser, either Netscape or Internet Explorer. Enter the URL http://localhost/perl/DWReports.pl You should get the browser interface. On a network or dial-in, the user should replace localhost with the computer name or IP address. You can now control which reports are available by editing the configuration file: Apache2\Perl\Dwreports.cfg

 

 

9.0 TOOLS

9.1 START/STOP SYSTEM - See Section 2.3 Run DataWise®

 

 

9.2 SET DATABASE SERVER

When DATAWISE® is first installed the database server is set automatically. If you ever need to change the database server, then follow the instructions below.

RUN DataWise® for the first time.

CHOOSE TOOLS > Set Database Server from the Main. DataWise® menu. The Set Database Server Now screen is displayed. If it is the same computer CLICK on Reset Server. and the computer name will be entered into that field. If you are a node on a LAN, ENTER the computer name of the server running DataWise®. Note If you are a terminal using NT or 2000, you have a choice of connecting with Named Pipes or Sockets. If you are running a DataWise® server on NT, Named Pipes is the default and cannot be changed. If the remote terminal is running Windows 95 or 98, you may only connect using the Sockets mechanism. CLICK on OK. This creates a file (\dw\config\dbase_server.cfg), which tells the system who you are and where to look for the server. This is a text file you may edit manually, if you want. Most users will not need to do this. .

9.3 MAP SERVER ACCESS

This application is used only by clients, not by users on the DataWise® server itself. This application allows the client to map a remote drive on the server to a local drive on the client's computer, thus allowing clients to access files on the server. The client MUST have an account on the server to function.

MAP Server Access.             &