Addendum #2 to RFP (MSG) Fire Station Alert System

Transcription

1 Addendum #2 to RFP (MSG) Fire Station Alert System The purpose of this addendum is to document discussions at the October 6, 2003 pre proposal conference. Please note the following important information: The proposal due date has been extended by one week. Proposals are due no later than 12:00 noon, pacific time on Tuesday, October 21, The following companies were represented at the pre proposal conference: Motorola Day Wireless Westnet Systems Locution Companies have the option of proposing alternate solutions (such as different installation options) if it is appropriate to do so. All companies submitting proposals are required to sign and submit this addendum with their proposal as acknowledgement of receipt. Clarification: Section 2, Scope of Work, unsquelch the radio terminology In several statements, the document states the Station Alert System will unsquelch the radio. This is a misnomer. The radio audio is always on. The correct descriptive terminology is open the audio path from the station radio. Clarification: Section 2.3 Communication Center, final paragraph, workstation terminology. The term workstation is replaced with indicator display in this section. The City requires three (3) indicator displays in the Fire Dispatch Center. The purpose of these indicator displays is to provide immediate notification to the dispatcher that the station alert failed during a dispatch so that a backup station alert can be initiated. Addendum 2 to RFP

2 Clarification: Section Remote Units, paragraph #3, cut over The City does not plan to order and install duplicate direct telephone lines Limited space and power / relay connections will not readily accommodate dual instation alert system connections The City s vision of installation, testing and cut over is as follows. 1. Meetings with Intergraph to finalize interface requirements 2. Install Station Alert System Master Controller and test interface connections. 3. Install and test in-station components at the General Services test station (The test station includes a copy of in-station City relays, P.A, radio, etc.) 4. Visit each station and pre-plan component installation. Temporary connection and testing at each station may or may not be required. The primary purpose is fit planning. 5. Immediately following City cut over to the new CAD system, install and test instation components at each Fire Station. The City s primary need is to install and connect the new in-station components in each station as quickly as possible following cut over to the new CAD system. Until installation is complete, the City will use the existing Motorola data burst system as the primary station alerting system, and will be without a back-up system. The City will ensure that City staff are available to accompany the selected contractor s installation staff as required. Work can be done at the stations between 8AM and 8PM Monday through Friday The City desires that the work at the stations be completed within 5 working days, if at all possible. Change: Section 2.4.1, paragraph #3: During the installation phase, each station will be visited to pre-plan component installation. Temporary connection and testing at each station may or may not be required. The Remote Units will then be staged at a location to be determined. During the cut over period, the existing equipment will be disconnected, removed and staged at the station by the Contractor. Sometime later, the City will dispose of the old equipment. The Remote Units will then be permanently moved inside the cabinets. The City and the selected vendor will work together to minimize the cut over period, with details to be finalized during contract negotiations. Notice: Proposers are invited to submit alternative concepts for the cut over process for evaluation by the City. A line item cost proposal should be included on the price sheet if an alternative cut over plan is proposed. Addendum 2 to RFP

3 Additional questions: 1. A question was raised by a vendor if there is a requirement for any specific sized router and/or a firewall. No. A security firewall for this project will not be required. 2. Will there be any failure notification to the Dispatcher via Intergraph? No. Intergraph will log a NAK failure from the Station Alert Controller and can generate a Supervisor notification, but the notification is not delivered to the dispatcher. 3. Can we get a copy of the User Guide for 7.7 from Intergraph? It outlines the functional features supported by Intergraph in conjunction with the Fire Station Alerting. Reference is found on page 4 of the Fire Station Alerting (I/FSA) Interface requirement document. Yes. A copy of the document, IPS to Moscad 77.doc is attached. NOTE: This is version 7.7 and the City will have version 7.8, but the basics are the same. As stated in the Interface Requirement document, Please note that the functionality stated for Moscad is very similar to other alerting systems such as Zetron, Westnet and Locution. You must sign and return this addendum with your proposal package to acknowledge receipt of this Addendum 2 to RFP Company Name Representatives Signature Representatives Name Date Addendum 2 to RFP

4 Intergraph Public Safety Moscad Fire Station Alerting Users' Guide For I/CAD version 7.7 January 08, 2002

5 Legal Notices Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. The information and the software discussed in this document are subject to change without notice and should not be considered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. Disclaimer This document contains proprietary information belonging to Intergraph Public Safety and is subject to change without notice. Intergraph Public Safety assumes no liability for inaccuracies or incompleteness. NIBRS and offense listings in this product may not be up to date. Refer to your agency s NIBRS and offense listings for the latest information. Trademarks Intergraph is a registered trademark of Intergraph Corporation. Windows and Windows NT are registered trademarks of Microsoft Corporation. NT is a registered trademark of Northern Telecom Limited. All other brands and product names are trademarks of their respective owners. ORACLE and SQL Plus are registered trademarks of Oracle Corporation. Copyright 2001 Intergraph Corporation All Rights Reserved Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties that is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization. The mathematical optimization procedure of the Konrad SE Center for Information Technology Berlin is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS or subparagraphs (c)(1) and (2) of Commercial Computer Software Restricted Rights at 48 CFR , as applicable. Unpublished rights reserved under the copyright laws of the United States. Intergraph Corporation Huntsville, Alabama

6 MOSCAD - FIRE STATION ALERTING Table of Contents REVISION HISTORY... II INTRODUCTION... 1 OPERATIONAL OVERVIEW... 1 SYSTEM REQUIREMENTS... 1 SOFTWARE REQUIREMENTS... 1 HARDWARE REQUIREMENTS... 1 INSTALLATION... 1 STARTING FIRE STATION ALERTING... 2 DATABASE CONFIGURATION... 2 Example Database Configuration... 3 I/CAD CONFIGURATION... 3 Changes to the Logon Deployment Properties and Unit Deployment Dialog Boxes... 4 Configuration Record Definition... 4 CADDBM CONFIGURATION... 6 CADDBM Dialog Boxes... 6 CADDBM Configuration Record Definition... 6 REGISTRY VALUES... 7 MOSCAD PACKET DESCRIPTION... 8 CONNECTION TO MOSCAD... 8 i

7 INTERGRAPH PUBLIC SAFETY Revision History Version Date Author Major Section Changed and Description ii

8 MOSCAD - FIRE STATION ALERTING Introduction Fire Station Alerting is a software interface between I/CAD and Moscad. It provides a method for I/CAD to send audible alerts to fire stations. Operational Overview The primary task of the Fire Station Alerting interface is to send I/CAD-generated unit dispatch notifications to the Moscad system. Fire Station Alerting monitors I/CAD network traffic receiving all packets related to units assigned to Moscad. These network packets are used to determine when notification of I/CAD unit dispatch needs to be sent to Moscad. System Requirements Fire Station Alerting requires the following software and hardware. Software Requirements Fire Station Alerting is dependent on the following software: I/Listener CADDBM Hardware Requirements Fire Station Alerting can be run on any computer using an Intel Pentium processor with 64 or more megabytes of memory, 10 or more megabytes of free disk space, and appropriate network hardware. Installation Use the following steps to install the Fire Station Alerting interface software. To install the Fire Station Alerting application: 1. From Explorer, access the CD drive. 2. Double click on setup.exe. 3. To finish the installation of Fire Station Alerting, follow the prompts provided by the setup program. 1

9 INTERGRAPH PUBLIC SAFETY Note: Fire Station Alerting may also be installed from a network drive. Network installation is the same as described above except that the location of setup.exe will be a path starting with the letter that represents the network drive. Starting Fire Station Alerting Fire Station Alerting is designed to run under Interface Service Manager (ISM). Set up Fire Station Alerting to start after the I/Listener. Specify the moscad configuration. A typical entry for moscad is: c:\win32app\ingr\fsa\fsaserver using the program argument /c: moscad. Do not check State Support. See the Interface Service Manager documentation for further information on installation and execution of interfaces. Database Configuration Fire Station Alerting requires modification of the I/CAD database. Add a new column, bay, to the I/CAD def_unit, lineup, and cd_units tables. Create a new table, fs_alert. To create the new columns and table in the I/CAD database, use the SQL script IFSALERT_ORA.SQL if your I/CAD database is Oracle or IFSALERT_MSS.SQL if your I/CAD database is SQL Server. These SQL scripts are delivered with the application. Initial entry of data into these new columns is done using RADO Interactive Utility (RADO). The new bay column is used to map individual units to an alert address, which is defined in the fs_alert table. The bay column contains a character string that consists of up to two characters. The station and bay columns are used in a database join to the fs_alert table. Typical implementation of bay starts with the number 1 representing the first bay in the station. A maximum of 99 bays is available per station. Multiple units may be assigned to the same bay. The fs_alert database table contains four columns. These columns are station, bay, alert_address, and type. Station and bay are used together to look up a unit s alert address. Alert_address is a three-character string that contains the address for alertable units. This address is defined by the Moscad system. Typical addresses in the Moscad system are 011, 012, 013, 014, 021, 022, 023, and 024 where the first two characters represent the station and the last character represents the bay. Alert addresses for a particular system are set up during hardware installation. They may be determined by consulting with the hardware installer. The type column, a user-defined string up to six characters, allows use of multiple alerting systems at the same time. A typical value for the type column is Moscad. The only rule for the type column is that it must be the same for all alert_addresses assigned to a specific alerting system. Example: All alert_addresses entries used by the Moscad system should use Moscad as their type. 2

10 MOSCAD - FIRE STATION ALERTING Example Database Configuration The following table contains a typical database configuration example. Def_unit fs_alert Unid station bay Station bay alert_address Type n101 North10 1 North Moscad n102 North10 2 North Moscad n103 North10 3 North Moscad n105 North10 4 North Moscad n111 North11 1 North Moscad n115 North11 2 North Moscad n121 North12 1 North Moscad Pump3 North12 2 North Moscad Truck2 North12 3 North Moscad Med1 NorthM1 1 NorthM Moscad Squad2 NorthR1 1 NorhtR Moscad I/CAD Configuration To allow the user to access the bay database column, I/CAD configuration changes are required. These configuration changes are needed to allow the I/CAD user to alert a unit at a station other than the unit s default station. Note: The implementation support person who installs I/CAD should make these modifications. Add the Bay field to the Unit Properties - Deployment dialog box. Use CADDBM to modify the "cad" configuration records definition for the Unit Properties - Deployment dialog box (IDD_unit deployment). Changes to the I/CAD configuration are required to allow the user access to the bay database column. These configuration changes are needed to allow the I/CAD user to alert a unit at a different station other than the unit s default station. You can assign a new alert address is created by giving it a new station and bay in the on the Unit Properties - Deployment page. The configuration records definition, Logon Deployment (logon_dp) page, and Unit Properties - Deployment (unit_deployment) page must be modified. Note: These modifications should be done by the implementation 3

11 INTERGRAPH PUBLIC SAFETY Changes to the Logon Deployment Properties and Unit Deployment Dialog Boxes A new field, Bay, and the text description for this field, must be added to the Logon - Deployment Properties (logon_dp) and Unit Deployment (unit_deployment) dialog boxes. The following example illustrates adding the Bay field to the Unit Deployment dialog box. Configuration Record Definition To make configuration changes, use CADDBM and complete the following steps. 1. Select Agency > Configuration Records Definition. 2. Select the Set Name of "cad". 3. Add the following IDs: ID Column Data Type Form Gadget Label Row 201 bay C Logon_dp Field_number bay C Logon_dp Field_number bay C NULL Column 4

12 MOSCAD - FIRE STATION ALERTING ID Column Data Type 205 bay C NULL Form Gadget Label Row 237 bay C Logon_dp Field_number bay C Unit_deployment Field_number 0 0 Column 5

13 INTERGRAPH PUBLIC SAFETY CADDBM Configuration To allow the user access to the bay database column, CADDBM configuration changes are also required. Use CADDBM to change the configuration definition for the Update Lineup Records dialog box. Once you have updated the configuration definition, edit the Update Lineup Records dialog box and add the Bay field. Note: The implementation support person who installs I/CAD should make these modifications. CADDBM Dialog Boxes A new field, Bay, and the text description for this field, must be added. The following example illustrates adding bay to the Update Lineup Records (IDD_Lineup2) dialog box. CADDBM Configuration Record Definition To make configuration changes, use CADDBM and complete the following steps. 1. Select Agency > Configuration Records Definition. 6

14 MOSCAD - FIRE STATION ALERTING 2. Select the Set Name of "caddbm". 3. Add the following IDs: ID Column Data Type Form Gadget Label Row Column 143 bay C NULL 144 bay C NULL 148 bay C NULL 151 bay C CSlineup2 Field_number bay C CSlineup2 Field_number -1 0 Registry Values Registry values are shown in the following table. Registry Value Default Value Description AckReads 1 The number of characters to read from Moscad while looking for an acknowledgement (ACK). By default, one character is read before a timeout. AlertOnlyIfAQ 0 If set to 1, turns on Alert Tones only if the unit being alerted is Available in Quarters. AllowDuplicates 0 Multiple units per bay. Must be 0 for alerting hardware that supports unit status changes. A value of 0 means that duplicates are not allowed while 1 means duplicates are allowed. BaudRate 9600 The baud rate of the Moscad port. DataBits 8 Data bits used by Moscad. DebugLevel 0 Programmer debug mode. Valid values are 0, 1, 2, 3, 4, or 5. A debug value of 0 turns debug mode off. GuidStr The guid that represents the Alerting com object in use. The user should not alter this value. InitUnitStatus 0 Determines whether to set the status of all units during initialization. LogFile c:\temp\mos.log Failure conditions are written to this log file. NoXON 1 This is to set hardware flow control. A zero (0) means use hardware flow control. A one (1) turns off hardware flow control. Parity N Parity used by Moscad. 7

15 INTERGRAPH PUBLIC SAFETY Registry Value Default Value Description N = no parity, e = even parity Port com1 The port to which the cable from Moscad is connected. PortTimeOut 3 The time, in seconds, to wait while trying to read a character from the port. The default is three seconds. StopBits 1 The number of stop bits used by Moscad. TextPrinting 0 Set to 0 (zero) for Zetron (disabled). XmitRetries 3 The number of times a packet should be retransmitted to Moscad before failing. ZetronMoveUp 1 Set to 0 (zero) to disable this function. Set to 1 to enable this function. Moscad Packet Description Packets sent from Fire Station Alerting to Moscad are of the following format. <STX>ssB<ETX> ss = The two digit station number from 01 to 99. B = The one digit bay number. Moscad responds with an ACK when a packet is properly received or with a NAK when there is a problem. When a NAK is received, the Fire Station Alerting interface retransmits the original packet. The number of NAK-driven retransmits is limited by the XmitRetries registry value. If the number of XmitRetries is exceeded, the current packet is disregarded and Fire Station Alerting continues with the next dispatch received. Connection to Moscad The Fire Station Alerting interface connects to Moscad by a standard RS232 serial cable. 8