EVENTS SPECIFICATION

  Windows interface:  Events can be installed on Windows 2000, XP, Vista,
	or 7 operating systems.  

  Unlimited tags:  Events will allow you to make as many inputs and outputs as
	necessary in the full version.  Tags are assigned modbus inputs.  The 64/64
	version allows 64 inputs and 64 outputs.

  Form editor:  Events has three sets of component toolbars for making custom
	form displays.  The toolbars include  display components, background
	components and control components.  The form editor allows the user to
	modify existing displays by adding new components or deleting components.
	You can make as many displays as needed for your system.

  Communications:  Events serial communications includes the Modbus binary
	protocol and the ALERT protocol.  Modbus is used with Modbus RTUs or PLCs
	that can be configured as a Modbus Slave.  The ALERT protocol is used with a
	receiver decoder that outputs data in an ALERT format.

  Web Server:  The web server engine build web pages from each display form in
    the project. These web pages are updated in real time on the web by sending 
	data only using AJAX.  The web server can also accept commands from the 
	browser if the user has passed the security input for each page.  The web
    server is very easy to set up and enable.  The user does not have to know
    HTML to use this feature.  	

  Defined sensors:  New sensors can be defined from existing sensors.  Defined
	sensors can use an if-then-else equation, a lookup table (level vs flow), a
	complex numerical equation, a capture statement (capture the time of the
	last transmission), or just be used to change the sensor name or add a local
	set point.  Defined sensors can be used in  alarm setup and can be logged in
	the database.

  Alarm processing:  Each sensor can be assigned multiple alarm set points
	with alarm actions for each event.  Actions include logging the alarm,
	speaker sounds, blinking the application, showing the alarm form, and
	messages.  A message can play any number of wave files for voice alarm
	messages.  Current and historical alarms can be shown or printed at any
	time.

  Statistics:  Events provides a statistical table for daily maximums,
	minimums, and averages for any sensor in the system.  Events stores 7 days
	of statistical information and then overwrites the older statistical files.
	Statistical data can also be logged the the database.

  Security: Events has a log on and off password security for five main
	program areas.  The user must be logged on and have permission to change
	communications, modbus setup, files & alarms, forms and passwords.  Events
	automatically logs off after one hour of no use.

  Change log:  Events keeps a change log to monitor changes made to forms, set
	points and other modifications to your program.  The log can be viewed and
	printed at any time.

  Importing modbus:  Events uses a spreadsheet table for specifying your
	modbus inputs and outputs.  You can use the import menu item if you are
	using a RUG9 master RTU.  By importing the modbus array, you eliminate input
	errors between your master RTU and Events.

  Database:  Events allows each sensor or device to be stored in multiple
	databases.  You can setup on-change databases as well as on-time databases.
	On-time databases are good for reports and historical trends.  On-change
	databases store each sensor as it changes.
	
  MySQL Database:  Events can be enabled to write data files to a folder.  A
    separate application will read these file and write the data to MySQL.
    This option provides a long term interface to historical data storage.	

  Networking:  Networking is included in the full version of Events.  Events
	can be networked on a local area network.  Network commands are sent once
	from the client to the server and then the server updates the client with
	the data requested on a timed basis (i.e. every 15 seconds).  One client can
	receive updates from multiple Events servers for updating several processes
	on one machine.  Each full version of Events can be either a network server
	or client or both.  The networking will work on any Microsoft networks and
	should be tried on other network configurations.

  Reports:  Events provides a report editor that can pull data from real time
	sources or can pull historical data from your databases.  The report editor
	also can accept graphic images (form snapshots or trends).  Users can make a
	reports by changing font color, font sizes, adding images, inserting titles,
	subtitles, dates, times, and data placeholders.  Data placeholders ( =[1] )
	are assigned sensor names, SQL statements or local tags such as datetime.
	Users can run the report, preview it, print it, save it, and set the
	scheduler to print the report when needed.

  Scheduler:  Events provides a powerful scheduler that triggers tasks on time
	or on an event.  The scheduler is used to output HTML files and text files
	of your data as needed.  Triggers include three types of timers, click
	events on your forms, alarm events, receive status changes, transmit sensor
	changes, or defined sensor events.

  HTML output:  Events can build HTML web pages of your forms, historical
	data, historical trends, alarms, statistics and reports.  You set your
	scheduler to output your forms every 15 minutes, while alarms and reports
	are triggered on change.  Events will update your users on your network
	without additional networking costs. 

  CSV output:  The scheduler can also output comma delimited data and tab
	delimited data for other programs.  These files can be appended to or
	overwritten as required.
  
  Additional Features	
  1. FTP scripts
  2. Email scripts
  3. Export data to MySQL Database application
  4. Open PDF files
  5. Open Text Files, CSV Files
  6. Triggers for FTP, Email, Reports, Open files, etc...
  7. Trigger Hyperlinks from Events
  8. Button triggers, Image triggers..
  9. Label triggers, Special Label triggers, Annunciator triggers, Global Alarm Button triggers, Define sensors that can trigger
  10. Export data report includes ALERT data..
  11. Tri-level Annunciator (On, Off, Fail)
  12. Statistic Reports by groups.
  13. Get & Read FTP Files
  14. Images have OnClick to show forms and other documents
  15. Place historical sensors in Events (datetime, value)
  16. Watch for System Shutdown and Close Safely
  17. Improved IE7 compatibility
  18. Added OnChgMin to database setting.  Record OnChg and OnMinute like the trends do.
  19. Make Rain Button into a label by putting 'flat' in tagname.
  20. Added RainGrid (Multiple Rates displayed) from 15 minutes to 1 Day... 15,30,45,1Hr,2,3,6,12 and 1 Day.  See Rate of Change for any analog sensor.
  21. Added acknowledge button that can be toggle from web browser.
  22. Modified Web Login based on each session.  Administrators add user through security settings.
  23. Added color to HOA and ON/OFF buttons, changed trends so you could sort the data from newest to oldest and back. HOA updates faster from web.
  24. iPhone fix for virtual keyboard