Information
- Manufacturer: NC4 (310 606 4444)
- Product: Risk Center
- Type: Alarm Receiver
Supported Features
- Event Receipt
- With Location Data
Components and Communication
Component | Location | Outgoing communication | Incoming communication |
---|---|---|---|
SMTP Receiver Service | Sureview Server | N/A | 25 TCP |
Sureview Configuration
Alarm Configuration
Step One - Add the NC4 System to Sureview
- Create a new site in Sureview called 'NC4 System'.
- Add an NC4 device to that site (include the IP address of the NC4 System but leave the other options blank). Note there is a 50 Character limit on the device title.
- In the alarms tab (within the device setup) add any alarm responses you require. We recommend adding at least one 'Default' alarm type.
- Make a note of the 'SMTP Server Address' displayed in the summary report, as this is your 'S' number email address that the NC4 must be set to send alarms to.
Step Two - Add the individual asset sites/devices
- Create the site for the NC4 asset (if it does not already exist).
- Add an NC4 device to the relevant site making sure to set the 'Asset Name' of the device/site (e.g. 'New York Facility' or 'NY Metro Site').
- Add the alarm responses that you require, again we recommend adding at least one 'Default' alarm type.
Step Three - Configure NC4
Follow Manufacturer Instructions
- Configure the NC4 system to send emails to the 'S' number email address (retrieved from step one - 4).
- Configure the NC4 system to use the Sureview Server IP address (or NLB address) as the 'SMTP Server address'.
Alarm Event Types
Sureview is able to decode and assign separate responses (priority, actions, title, etc) for the following NC4 event types.
Note: Any unmatched event types will be triggered with the “UNKNOWN” event type.
BOLO Food Advisory Homeland Security Advisory Meteorological Advisory Planned Event Public Safety Advisory Travel Advisory Air Travel Delay. Airliner Crash Airport Closure Emergency Landing Helicopter Crash Plane Crash 1 Alarm Fire 2 Alarm Fire 3 Alarm Fire 4 Alarm Fire 5 Alarm Fire 6+ Alarm Fire Brush Fire Explosion High Rise Fire Industrial Fire Manhole Fire Structure Fire Vehicle Fire Wildfire Earthquake Tsunami Volcano Biohazard Chemical Spill Explosive Materials Fuel Spill Fumes Hazmat Response Natural Gas Leak |
Oil Spill Radioactive Material Unknown Substance Avian Influenza Boil Water Advisory Public Health Public Health Advisory Quarantine Fuel Disruption Power Outage Rolling Blackout Sewage Problem Telecom Outage Water Main Break Evacuation Flooding Hurricane Hurricane Conference Call Ice Storm Storm Tornado Tropical Cyclone Tropical Storm Typhoon Weather Advisory Labor Action Bank Robbery BOLO Bomb Threat Bombing Civil Unrest Explosive Device Hostage Situation Insurgent Attack Military Operation Planned Protest Police Activity |
Disturbance Explosion Protest Public Safety Advisory Riot Robbery School Lock-Down Suspicious Activity Suspicious Device Suspicious Package Violent Crime Bridge Collapse Building Collapse Mine Accident Partial Collapse Roof Collapse Structure Collapse Tunnel Collapse Unsafe Structure Bio-Terrorism. Bombing Chemical Terrorism Explosion Homeland Security Advisory Nuclear Device Terrorism Advisory Threat Advisory Level Maritime Accident Motor Vehicle Accident Public Transportation Disruption Public Transportation Strike Roadway Closure Subway Incident Tanker Truck Accident Tractor Trailer Accident Train Accident TRANSPORTATIONVEHICLEFIRE |
Troubleshooting
No Alarms Coming in - Check SMTP Receiver logs for the following :
Data source error - Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.
This error indicates that 1 or more of the Device Titles is greater than 50 characters, causing and error which prevents the alarm entering the system.
Comments
0 comments
Please sign in to leave a comment.