Conditional Based Maintenance and Control By acquiring the real-time data, the AM system can determine when the equipment is running and automatically count the runtime hours. or time schedule, Once the count reaches the manufacturer-specified limits, the AM system can immediately alert the maintenance crew for service.       Typical operation example      * System shown with Web server and  PLC Controller

The AM system can incorporate alarms from the automation system to help identify malfunctioning instruments. By capturing these alarms, the system can quickly determine if the number of alarms for a specific instrument has exceeds a preset limit over a period of time. The AM system can then inform the user that the equipment should be inspected, automatically triggering a Notification via email, text message, etc. Traditional preventative maintenance is that all maintenance is scheduled on a periodic, regular basis regardless of equipment usage and operating condition. Thus, equipment that is rarely used receives the same amount of maintenance as frequently used equipment. As well, equipment that is used under harsh operating conditions is maintained as little as equipment that operates under ideal conditions. Consequently, some equipment is maintained too often, thereby increasing maintenance costs unnecessarily, and yet other equipment suffers undue wear-and-tear while waiting for its scheduled maintenance.

Setup 

The webpage can be accessed by opening your internet browser (Internet Explorer, Firefox, Safari, …) and entering the IP address of your Network.  Multiple unit selection, Your specific device can be identified by using the IP Address field selection on your network Single unit zone programming: The Zone Programming page displays a link for each of the six Zones, as well as a link for Battery and Power monitoring. Note that the battery back-up option (FGD-AM) is required for power monitoring. A description of each parameter is described below. Name: Enter a name for the sensor you are monitoring which describes its purpose and/or location. The name will appear on the Summary screen as well as on alarm messages. Type: Choose the type of sensor you are connecting to the Zone input. For temperature sensors choose either degrees F or C.

Users

The AMWEB allows you to have up to 8 Users. Each User can have up to 4 contact (e-mail, SMS Text Message, or SNMP trap)

Event and Data Log History. The Event Log is a time-stamped list of system events such as System Startup, Alarm Detection, Message Delivery, … The Data Log contains time stamped records of the input values. The logging rate is configured on the Zone programming screen for each input. The query results can be viewed on screen within your browser or they can be exported to other file formats (TXT, CSV, XML) for use within other programs, such as Excel.

Event Log Query
Select Event Log from the top of the screen. Select a particular Zone to narrow your query results to events associated with a particular Zone or choose All to see all event types in the Event Log. You can narrow the results from a particular time period by selecting the Mode drop-down. This gives you options to choose events from the Previous 24 Hours, the Last 7 days, the Current Month or you can select a Custom time period. When you choose Custom the Start Time and End Time fields will become active. Enter the start and end times for your query. Next, choose the maximum number of records you want returned for your query, the choices are 25, 50, 100 and All. Finally, click the View Data button to display the results. Alternatively you can Export the results to a file for viewing in another program. Choose the Export file format from the drop-down list (XML, CSV, TXT) and click the Export button to
create a file.

Datalog Query
Select Data Log from the top of the screen. Select a particular Zone to narrow your query results to a particular Zone or choose All to see samples from all Zones. Next, choose whether you’d like to view All samples, all Normal samples, or specifically samples that exceeded the alarm limits. You can narrow the results from a particular time period by selecting the Mode drop-down. This gives you options to choose events from the Previous 24 Hours, the Last 7 days, the Current Month or you can select a Custom time period. When you choose Custom the Start Time and End Time fields will become active. Enter the start and end times for your query. Next, choose the maximum number of records you want returned for your query, the choices are 25, 50, 100 and All. Finally, click the View Data button to display the results. Alternatively you can Export the results to a file for viewing in another program. Choose the Export file format from the drop-down list (XML, CSV, TXT) and click the Export button to create a file Data-log

Alarm Notification Process

Easy Access via IP to each individual machine When a zone exceeds the programmed alarm limit (or if a contact changes state) the AMWEB will start its alarm recognition timer and the Status on the Summary screen will change from OK to Waiting, to indicate that the zone may become an alarm if the fault condition exceeds the programmed recognition time. If Zone Alarm Delivery is disabled, the zone status will immediately change to Alarm. If the fault becomes an alarm, the AMWEB will display the Status as either High, Low or Alarm, in red, to indicate that an alarm exists and the Last Alarm time-stamp will update to reflect the time of the alarm.

Once an alarm meets the recognition time, the AMWEB will check to see if the Zone Alarm Delivery Schedule is enabled. If it is, then alarm processing continues. If the Zone Alarm Delivery Schedule is or becomes disabled, alarm processing will be cancelled.
Next, the unit will check the programmed Users and corresponding Contacts to see if alarm messages should be delivered. First, the unit will locate all Users set to Escalation Priority 1. Then it will check to see if the User is Enabled. Any Users that are not Enabled will immediately be discarded from receiving the alarm message. Next the unit will check the User Alarm Delivery Schedule. If the User Alarm
Delivery Schedule is enabled then alarm processing continues, if not, alarm processing to this User will be suspended until either the Alarm Delivery Schedule becomes enabled or the alarm condition clears. If the Alarm Delivery Schedule becomes enabled the AMWEB Web will proceed to check the Contact programming to see if alarm messages should be sent. Note that if a User is Disabled while the alarm condition still exists, then alarm message processing will be canceled for that User.The MWEB will now check to see if any Contacts are enabled. Any Contacts that are not Enabled will immediately be discarded from receiving the alarm message. Next, the unit will check the Contact Alarm Delivery Schedule. If the Contact Alarm Delivery Schedule is enabled then the alarm message will be sent, if not, alarm processing to this Contact will be suspended until either the Alarm Delivery Schedule becomes enabled or the alarm condition clears. If the Contact Alarm Delivery Schedule becomes enabled the AMWEB will proceed to send the alarm message.
Alarm delivery continues until there are no more users to contact or the alarm no longer exists. Notes on Alarm Escalation If no alarm message(s) can be delivered to an Escalation Priority 1 User due to a disabled status, the AMWEB  will proceed to Escalation Priority 2 Users, and so on, until it can immediately deliver its alarm message. If any Users below the current Escalation Level become enabled at a later time as the result of a schedule change, and the alarm still exists, then those Users/Contacts will receive the alarm message at that time.