<p>TECHNICAL SPECIFICATIONS: SIREN CONTROLLER</p><p>Damian Barker January 2016 Contents</p><p>1. System Definition...... 3 2. General Alert Dissemination Method Requirements...... 4 3. CAP and Atom File Formatting...... 5 4. Custom Parameters...... 6 4.1. Inhibit Parameter...... 6 4.1.1. Inhibit Parameter Description and Methodology...... 6 4.1.2. Structure...... 6 4.1.3. Format:...... 6 5. Siren Controller Technical Specifications...... 7 6. Installation Details...... 11 1. System Definition</p><p>The Siren Controller is a Common Alerting Protocol (CAP) v1.2 device which will poll at least two defined CAP sources for CAP alerts and activate either an electromechanical or voice capable siren if required. 2. General Alert Dissemination Method Requirements</p><p>The requirements in this section are applicable for ALL dissemination methods. Where differences are necessary for an individual dissemination method this will be indicated in the section titled “Siren Controller Technical Specifications.”</p><p>(a) Devices receive CAP v 1.2 alerts by “POLLING” the CAP servers and processing the ATOM file containing the list and URI’s of active alerts. The format of the ATOM file is described in section titled “CAP AND ATOM FILE FORMATTING”</p><p>(b) Devices will process unique CAP messages and disregard any identical duplicated alerts which may be received from multiple CAP server sources.</p><p>(c) Devices must be able to poll a list of at least two (2) CAP servers for active alerts at least once every sixty (60) seconds. Where an alternate polling interval is required the individual technical specifications will indicate this.</p><p>(d) Devices will be designed to use a dynamic IP address (such as common with ADSL internet service) and must include self contained Dynamic DNS services if required.</p><p>(e) Devices will be designed to utilise standard ADSL internet access with standard RJ45 interfaces.</p><p>(f) Devices will keep a completely auditable log of all alerts received, disseminated and disregarded.</p><p>(g) Devices will be fully compatible with the requirements set out in the section titled “CUSTOM PARAMETERS” in this document.</p><p>(h) Devices will feature a web interface accessible from the internet (with appropriate security and authentication) from which all dissemination options can be configured.</p><p>(i) Devices will implement all necessary self diagnostic and internet connectivity status tests and a reporting facility via an HTTP “GET” or “POST” mechanism of device status. A HTTP response of “OK” indicating normal function and “FAIL – xxxxxxx” where xxx is an error code defined in user documentation or a textual description of an error condition if a malfunction or otherwise unexpected condition arises. 3. CAP and Atom File Formatting</p><p>(a) CAP alerts generated by the CAP Server describe the affected area by using the geospatial CAP polygon and circle elements as well as defined geocode values to define alerting zone definitions. The list of geocodes can be expanded at any time using the Administration interface to define new alerting zone definitions.</p><p>(b) CAP messages containing sensor or other operational data not intended for public dissemination is identified by populating the CAP scope element with a value of “Private.” Such messages are NOT included in the general publication Atom index. </p><p>(c) CAP messages containing technical information about alerting device or system status or errors are identified by populating the CAP status element with the value of “System.” Such messages are NOT included in the general publication Atom index.</p><p>(d) The Atom-formatted index entry block for each alert on the CAP Server publication interface includes the following elements: </p><p> i. The Atom link element includes the URL of the corresponding CAP XML file in the href attribute. ii. The Atom title element contains the value of the CAP message’s headline element. iii. The Atom updated element contains the value of the CAP message's sent element. \ iv.The following CAP elements are included in the Atom file with a namespace prefix of “cap” (which prefix is bound in the XML preamble to the OASIS CAP 1.2 namespace):</p><p>A. status B. msgType C. language D. category E. urgency F. severity G. certainty H. areaDesc I. geocode </p><p>(e) In the case of CAP messages containing an expires element, the message is considered unexpired until after the latest expires time in any included CAP info block. If no expires element is present in a CAP message that message is considered unexpired until one hour after its sent time value. 4. Custom Parameters</p><p>The following CAP parameter values must be supported by the alert dissemination device for this application.</p><p>4.1. Inhibit Parameter 4.1.1. Inhibit Parameter Description and Methodology</p><p>The inhibit parameter is included to provide the utmost granularity of alert dissemination methods to be activated for a particular alert. The presence of a “TRUE” inhibit parameter in an alert for a particular dissemination mechanism means that mechanism will NOT activate regardless of any other activation criteria being met. The absence of an inhibit parameter or a value of false indicates that the dissemination method will determine its activation based on its filters, i.e. normal operation. 4.1.2. Structure</p><p>The inhibit tag is a parameter value in CAP. 4.1.3. Format:</p><p><Parameter> <Valuename>inhibit-siren</Valuename> <Value>True / False <Value> </Parameter> 5. Siren Controller Technical Specifications</p><p>Table 1: Showing the Siren Controller Technical Specifications 1 2 3 S/N Specifications Specifications Notes, remarks, ref Feature Offered to documentation Description</p><p>1 General Description The device monitors CAP 1.2 sources for CAP alerts and based on user defined activation “filters” and custom parameters activates the siren in one of two modes “test mode” or “alert mode”.</p><p>2 Function Uses its LAN connection to receive CAP 1.2 and CAP 1.1 alerts (either pulled from a server by the unit or pushed to the device or both). It will then use internal “filters” and custom parameters as described to determine the required action. </p><p>The device must have a configuration option in its administrative interface to specify whether it is controlling (i) an electromechnical siren or (ii) a voice coil equipped siren.</p><p>CASE 1:</p><p>If it is configured to control an electromechanical siren :  Activate the siren in “test” or “alert” mode.</p><p> In test mode: Close relay (RELAY1) contact for a duration of 10 seconds. Open relay (RELAY1) contact for a duration of 5 seconds. Repeat once. Configuration values for both relay close and open periods as well as the number of times to repeat the sequence will be user adjustable via the web interface.</p><p> In alert mode : Close relay (RELAY1) contact for a duration of 25 seconds. Open relay (RELAY1) contact for a duration of 10 seconds. Repeat 3 times. Configuration values for both relay close and open periods as well as the number of times to repeat the sequence will be user adjustable via the web interface</p><p>CASE 2: </p><p>If it is configured to control a voice coil equipped siren :</p><p> Activate the siren in “test” or “alert” mode.</p><p> Generate an audio alert based on the data in the CAP message by fetching attached audio using information in the CAP message, OR generate audio using internal Text to Speech software based on data in the CAP message.</p><p> Switch device Line Out to internal device output. </p><p> CLOSE relays (RELAY1 and 2) </p><p> PLAY the EAS tones over device internal output and Line Out (Use the United Stated national EAS tones: see http://transition.fcc.gov/pshs/services/e as/)  PLAY the generated audio alert via device internal output and Line Out  PLAY EAS “end of message” tone via device internal output and Line Out.  OPEN relays (RELAY1 and 2)  Switch device Line Out to Line in (audio pass through : this is the default state) </p><p> In “test mode” the above procedure is performed once for each alert received.</p><p> In “alert mode” the above procedure can be repeated multiple times for each alert received as long as the alert is not expired. The amount of times the procedure is repeated and the delay between each repetition can be configured via the administration interface on the device. 3 System Feed As described in section titled “General Alert Dissemination Method Requirements”</p><p>4 Activation Criteria User can define criteria for the incoming (filter) CAP message to determine if it qualifies for warning by selecting the following CAP parameters, using a simple user interface screen:  Status  msgType (one or more)  info.eventCode (SAME=a SAME event codes, multiple codes can be selected for multiple options)  info.urgency (minimum and above)  info.severity (minimum and above)  info.certainty (minimum and above)  areaDesc (multiple entries can be selected for multiple options)  area.polygon (describes coverage polygon, incoming messages will be filtered by comparing areas. Multiple polygons can be listed locally and may appear in the incoming message.)</p><p>The filters will be used to determine the activation of two profiles, “test” and “alert” as described above.</p><p>Required Equipment Equipment to be provided with all 5 components ready to install, in a self install kit. Installation will be done by local staff. Telephone support will be required by the provider under this RFQ, and should be included for at least two hours. Protocol of activating CAP 1.1 and CAP 1.2 XML file with digital 6 message signature based software. The unit will report the results of a downloaded message: download ok, passed filter, activation result (audio played successfully, what audio file was used and all other relevant information.)</p><p>7 Network 100Mb Base-T LAN support, RJ45 Connectivity connector. </p><p>8 USB connectors 1 USB connector (facilitate external devices or flash drive firmware upgrade etc).</p><p>8 Memory Totally solid state memory storage for reliable operation – no hard disk drive. </p><p>9 Audio channels Stereo relay with broadcast quality</p><p>10 Unit Control Web-Based control – all settings and functions can be performed from anywhere on the internet, including initiating or forwarding alerts, and changing configuration.</p><p>11 Audio interfaces Internal speaker (stereo mix or mono is acceptable)</p><p>Line Out. (Line Out feed out via stereo broadcast quality switch.)</p><p>Audio Line In. (broadcast quality stereo)</p><p>12 Other External Two (2) Single Pole Single Throw solid Outputs state relays that are electrically suitable and rated to switch on and off a standard 40w 120V AC incandescent bulb. </p><p>12 Security HTTPS/SSL/digital signature security.</p><p>12 Log files Text and audio logs are available via the web interface page. 6. Installation Details</p><p>The installation of the Siren controller will be performed by the equipment vendor with assistance provided by local contractors. </p><p>The equipment vendor is responsible for the installation, initial configuration and testing of all equipment to be installed under this RFQ and will :</p><p>(1) Provide an installation document detailing installation and configuration procedure, required local resources as well as resources provided by the vendor for use during the installation procedure.</p><p>(2) Work closely with local contractors during the installation phase in order to build in country capacity regarding installation and maintenance procedures.</p><p>(3) Provide a detailed test plan which demonstrates the fulfillment of all technical operation requirements in this RFQ at least one month before scheduled installation.</p><p>(4) Install and configure devices as necessary during the agreed upon installation timeframe.</p><p>(5) Provide both electronic and hard copies of installation, maintenance and configuration manuals.</p><p>(6) Produce a test report detailing the results of the testing of the installed equipment as specified in the test plan.</p><p>(7) Provide support by telephone and or email for a maximum of twelve (12) hours over a period of three (3) months immediately following the installation of devices.</p><p>The intended recipient is responsible for the overall coordination and scheduling of the installation processes and will :</p><p>(1) Schedule the installation in conjunction with the equipment vendor and beneficiary countries.</p><p>(2) Provide and organise accommodation and local transportation to and from installation sites where necessary for equipment installers.</p><p>(3) Assume responsibility for auditing the installation and test processes and ensuring installation meets the desired standards and operability. (4) Assume responsibility for securing written agreements with all involved entities to facilitate the installation process.</p>