COMPUTER AIDED DISPATCH, GEOGRAPHIC INFORMATION SYSTEM AND AUTOMATIC VEHICLE LOCATION FOR MACON COUNTY EMERGENCY MANAGEMENT

Transcription

1 REQUEST FOR PROPOSALS RFP# p COMPUTER AIDED DISPATCH, GEOGRAPHIC INFORMATION SYSTEM AND AUTOMATIC VEHICLE LOCATION FOR MACON COUNTY EMERGENCY MANAGEMENT ISSUE DATE: DECEMBER 23, 2011 ISSUING DEPARTMENT: MACON COUNTY FINANCE DEPARTMENT 5 WEST MAIN STREET FRANKLIN, NC PHONE: (828) FAX: (828) ATTN: LINDSAY MCCONNELL, PURCHASING AGENT lmcconnell@maconnc.org PROPOSALS WILL BE RECEIVED UNTIL JANUARY 12, 2012 AT 3:00 p.m. PROPOSALS ARE TO BE SEALED AND MAILED VIA USPS TO THE ABOVE ADDRESS OR DELIVERED TO THE PURCHASING AGENT S OFFICE LOCATED IN THE MACON COUNTY ANNEX BUILDING AT 5 WEST MAIN STREET, FRANKLIN, NC PAGE 1

2 MACON COUNTY, NORTH CAROLINA FINANCE DEPARTMENT RFP No p December 23, 2011 REQUEST FOR PROPOSALS FOR COMPUTER AIDED DISPATCH, GEOGRAPHIC INFORMATION SYSTEM AND AUTOMATIC VEHICLE LOCATION FOR MACON COUNTY EMERGENCY MANAGEMENT Pursuant to North Carolina General Statue , Macon County is requesting and will accept sealed proposals for a Computer Aided Dispatch System and GIS Mapping Display System, including all software and hardware, until January 12, 2012, at 3:00 p.m. by Lindsay McConnell, Macon County Purchasing Agent, at the Macon County Annex Building, 5 West Main Street, Franklin, NC The sealed proposals shall be opened in the office of Lindsay McConnell, Macon County Purchasing Agent, Macon County Annex Building, 5 West Main Street, Franklin, NC on January 12, 2012 at 3:00 p.m. The proposals submitted shall not be subject to public inspection until the contract is awarded. Interested parties may obtain a complete description of the Computer Aided Dispatch System including all software and hardware from Lindsay McConnell, Macon County Purchasing Agent, 5 West Main Street, Franklin, NC 28734, Phone Number (828) , anytime between Monday and Friday, 8:00 a.m. until 4:00 p.m., except holidays. Any contract resulting from a proposals received shall be awarded to the person or entity that submits the best overall proposal as determined by the awarding authority. The factors to be considered by Macon County in awarding the contract including the following: 1. Ability and experience of person or entity making the proposal to perform the conformity of that person or entity to the specifications; 2. The proposal that will be in the best interest of Macon County; 3. The quality of the workmanship of the person or entity making the proposal; 4. The equipment performance of the equipment proposed by the person or entity making the proposal and the reliability of the same; 5. Design features contained in the proposal by the person or entity making the proposal which would be advantageous to Macon County; 6. Freedom of premature obsolescence of such systems by Macon County; 7. Ease of installation removal and servicing such systems; 8. Equipment interchangeability in such systems; 9. Safety and security provisions in such systems; 10. Warranties and service contracts available in the proposal; 11. Minimum installation time of such systems; 12. Redundancy of such systems; 13. Quality of Service on such systems; 14. Service response time on such systems; and 15. Price of such systems and service, though such shall not be the only consideration. Notwithstanding the foregoing, Macon County reserves the right to reject any or all proposals. PAGE 2

3 All proposals in response to this request for proposals contained herein shall be made to Lindsay McConnell Macon County Purchasing Agent in a sealed envelope containing proposal and be marked upon the outside the following: COMPUTER AIDED DISPATCH, GEOGRAPHIC INFORMATION SYSTEM AND AUTOMATIC VEHICLE LOCATION FOR MACON COUNTY EMERGENCY MEDICAL SERVICES. The name and address of the person or entity making the proposal must be plainly marked on the outside of each envelope. MAILING INSTRUCTIONS 1. Bidder submit a complete, fully executed RFP document. 2. If mailed, proposal should be forwarded by certified U.S. Postal Service. Please address and mark your bid as shown below. MACON COUNTY PURCHASING AGENT ATTN: LINDSAY MCCONNELL 5 WEST MAIN STREET FRANKLIN, NC COMPUTER AIDED DISPATCH, GEOGRAPHIC INFORMATION SYSTEM AND AUTOMATIC VEHICLE LOCATION FOR MACON COUNTY EMERGENCY MEDICAL SERVICES 3. If forwarded other than by U.S. Postal Service, delivery must be made directly to Macon County Purchasing Agent, Macon County Annex Building, 5 West Main Street, Franklin, NC NOTE: IF MAIL OR DELIVERY BY ANY OTHER MEANS IS DELAYED BEYOND THE DATE AND HOUR SET FOR BID OPENING, PROPOSAL THUS DELAYED WILL NOT BE CONSIDERED. PAGE 3

4 I. Description of Procurement Process A. Request for Proposal Macon County Government is seeking a prime vendor to provide a fully integrated single source solution; including implementation, service, training and maintenance of a Computer Aided Dispatch, Geographic Information System and Automatic Vehicle Location for Macon County Emergency Management. Pursuant to North Carolina General Statue , the contract will be awarded to the person or entity that submits the best overall proposal as defined by the awarding authority. The factors to be considered by Macon County in awarding the contract include the following: 16. Ability and experience of person or entity making the proposal to perform the conformity of that person or entity to the specifications; 17. The proposal that will be in the best interest of Macon County; 18. The quality of the workmanship of the person or entity making the proposal; 19. The equipment performance of the equipment proposed by the person or entity making the proposal and the reliability of the same; 20. Design features contained in the proposal by the person or entity making the proposal which would be advantageous to Macon County; 21. Freedom of premature obsolescence of such systems by Macon County; 22. Ease of installation removal and servicing such systems; 23. Equipment interchangeability in such systems; 24. Safety and security provisions in such systems; 25. Warranties and service contracts available in the proposal; 26. Minimum installation time of such systems; 27. Redundancy of such systems; 28. Quality of Service on such systems; 29. Service response time on such systems; and 30. Price of such systems and service, though such shall not be the only consideration. B. Interpretations and Clarifications: Requests for information or clarification of this RFP must be made in writing and addressed to Lindsay McConnell at the address, fax, or e mail address listed below, with e mail being the preferred method of communication no later than Thursday, January 12, 2012 at 10:00 am. NO EXCEPTIONS. Please reference the RFP page and topic. Lindsay McConnell Purchasing Agent 5 West Main Street Franklin, NC Phone: , Fax: E mail: lmcconnell@maconnc.org C. Submission of RFP: One (1) original and one (1) electronic copy of the proposal along with the Non Collusion Affidavit shall be submitted on or before January 12, 2012 at 3:00 p.m. to: PAGE 4

5 Macon County Purchasing Agent Attn: Lindsay McConnell 5 West Main Street Franklin, NC Sealed proposals should be clearly marked COMPUTER AIDED DISPATCH, GEOGRAPHIC INFORMATION SYSTEM AND AUTOMATIC VEHICLE LOCATION FOR MACON COUNTY EMERGENCY MEDICAL SERVICES. When received, all proposals and supporting materials, as well as correspondence relating to the RFP, shall become the property of the County. Proposals sent by fax will not be accepted. As allowed under NCGS , proposals shall not be subject to public inspection until a contract is awarded. In submitting a proposal, it is understood by the vendor that Macon County reserves the right to accept any proposal, to reject any and all proposals as non responsive and to waive any irregularities or informalities in proposals when to do so is in the best interest of Macon County. Any proposal may be withdrawn or modified by written request of the vendor, provided such request is received by the County at the designated address prior to the date and time set for receipt of proposals. If a proposal includes any propriety data or information, such data or information must be specifically identified as such on every page on which it is found. Data or information so identified will remain confidential to the extent allowed by North Carolina law and will be used by Macon County personnel solely for the purposes of evaluating proposals and conducting contract negotiations. The cost of preparing a response to the RFP will not be reimbursed by the County. After the RFP issue date, all communications between the Issuing Department and prospective Proposers shall be in writing. or facsimile questions will be accepted. Any inquiries, requests for information, technical questions, clarifications, or additional information shall be directed to Lindsay McConnell at the address, facsimile number, or on page one of this RFP. PAGE 5

6 NON COLLUSION AFFIDAVIT COMPUTER AIDED DISPATCH, GEOGRAPHIC INFORMATION SYSTEM AND AUTOMATIC VEHICLE LOCATION FOR MACON COUNTY EMERGENCY MEDICAL SERVICES 1. The signer of this document is the (Title) of (company), who is the respondent that has submitted the attached bid response. 2. The undersigned person is fully informed concerning the preparation and contents of the attached response and of all pertinent circumstances related to it, and is authorized to sign this affidavit. This affidavit is given under penalty of perjury as provided by law. 3. Such bid response is genuine and is not collusive of sham in any way whatsoever. 4. Neither the person responding nor any of its officers, partners, owners, agents, representatives, employees or parties in interest, including the signer of this affidavit, have in any way colluded, conspired, connived, or agreed, directly or indirectly, with any other respondent, firm or person to submit collusive or submit sham response in connection with the contract for which the attached response has been submitted or to refrain from responding in connection with such contract, or has in any manner, directly or indirectly, sought by agreement or collusion or communication or conference with any other responder, firm, or person to fix the price or prices in the attached response or of any other responder, or, to fix any overhead, profit, or cost to secure through collusion, conspiracy, connivance or unlawful agreement any advantage against the Board of County Commissioners, Macon County or any person interested in the proposed contract. 5. The price or prices quoted in the attached response are fair and proper and are not derived by any collusion, conspiracy, connivance or unlawful agreement on the part of the respondent or any of its agents, representatives, owners, employees, or parties in interest. Signature of Officer Subscribed and sworn to before me, this day of, 20. Notary Public My commission expires (SEAL) PAGE 6

7 MACON COUNTY GOVERNMENT EMERGENCY MEDICAL SERVICES 1. INTRODUCTION AND BACKGROUND The Computer Aided Dispatch, Geographic Information System and Automatic Vehicle Location system shall use state of art technology. No part of the proposed operating system shall be in testing mode, all components must be fully functional. The contract will be a firm fixed price contract. Macon County encompasses approximately 515 square miles with a population of approximately 33,922. It includes the Town of Franklin and the Town of Highlands. Public safety communications are processed by Macon County Dispatch, which is a division of Macon County Emergency Services. The center is located in Franklin at 104 East Main Street. The dispatch center serves 3 police agencies, 11 fire departments and 1 ambulance service and dispatches approximately 30,000 calls for service annually Project Objectives Macon County is seeking proposals for a seamlessly integrated Computer Aided Dispatch (CAD), Geographic Information System (GIS) and Automatic Vehicle Location (AVL) system. The proposed system must be capable of servicing a multi organizational/multijurisdictional Public Safety Answering Position (PSAP) and be customizable to the individual user. The proposed system must utilize a Windows platform and have an Application Programming Interface (API) available to enable existing Mobile and Records Management System (RMS) providers to develop bi directional interfaces to the CAD/GIS/AVL system. The proposed system must be able to interface to a system and include ANI/ALI and TDD data transfer. The proposed system must be able to interface with third party paging and alerting systems, as well as call question protocol applications. The proposed system must provide a one way interface to the State/NCIC system and must include a robust reporting module to allow agencies to extract statistical data for each agency by incident, time, date or unit. The following standard modules are required: Be on the Lookout (BOLO) Help/Online Book Paging/Faxing Master Vessel Index Wrecker/Tow Rotation Reports Vehicle File Pre fire Plans Command Line Entry Hydrants System Status Management GIS Based Event Analysis Routing GIS Imaging Warrants Master Name Index Dynamic Routing Car Chase Map Based Tow Rotation The following table describes the desired specifications of the system for the County: Software Total Number of System users: 20 Number of Full CAD Dispatch positions: 6 Number of CAD Administrator positions: 3 PAGE 7

8 Number of CAD View only positions: 1 Training Number of call takers and/or dispatchers to be trained: 16 Number of administrators to be trained: 4 Number of users to be trained on view only workstations: 0 Number of administrators to be trained on view only workstations: Proposal Costs All costs incurred by the Firm in preparing the proposal, or costs incurred in any other manner in responding to this proposal will be solely the responsibility of the Firm. All material and documents submitted by the Firms in response to this RFP become the property of Macon County and will not be returned Open Procurement The County reserves the right to lease and/or purchase more or less of each item or service at the unit price offered in the Vendor's system, unless the Vendor specifically and explicitly limits the response in this regard. The County reserves the right to negotiate with Vendors regarding variations to the original proposal(s) that may be in the best interest of the County. Proposals shall remain firm for thirty (30) days from opening Compliance with Industry Regulations and Standards During their work, construction and equipment installation, all contractors must meet or exceed current standards of the organizations and guidelines listed below: Federal Communications Commission (FCC) Electronic Industries Association (EIA) Institute of Electrical and Electronic Engineers (IEEE) American National Standards Institute (ANSI) The Environmental Protection Agency (EPA) Contractor Work Hours and Safety Standards Act Equal Opportunity Act Federal Aviation Authority (FAA) 1.5. Addenda to this RFP The Agency will not be responsible for oral interpretations given by any of its employees, representatives or others. The issuance of a written addendum is the only official method whereby interpretation, clarification or additional information can be given. If any addenda are issued to this RFP, the County will attempt to notify all prospective Vendors who have secured the RFP. However, it will be the responsibility of each Vendor, prior to submitting the competitive proposal, to contact the County s Point of Contact to determine if addenda were issued and to make such addenda a part of its competitive proposal. 2. Business Terms and Conditions 2.1. New Equipment, Software Version PAGE 8

9 The County shall accept only new equipment and the latest version of software and/or operating systems. Used and/or remanufactured equipment will not be accepted Vendor Commitment The Vendor must offer maintenance and upgrades for the operational software and hardware at its then current public released level during the term of the contract or any subsequent maintenance contracts with the County, pursuant to this RFP Payment Terms Following is the County s schedule for payments to the Vendor. 1. Initial Payment: The County will pay the Vendor a payment of 70 percent (70%) of software, services and first year software and equipment maintenance and 100 percent (100%) of the equipment and third party software amounts for the subsystem. 2. Installation Payments: Upon delivery and installation of the software and equipment of each subsystem published on the order form, the County shall be 20 percent (20%) of the software, services, and first year software and equipment maintenance amount. 3. Final Payment: The County shall make full and final payment on the order form upon the beginning of productive use of the subsystem for the remaining ten percent (10%) of software, services, and first year software and equipment maintenance amount for each subsystem placed into production, plus any unpaid amount. 4. Other Potential Milestones: a. Upon order the County will pay the Vendor 50 percent (50%) of custom interfaces and other customizations. b. Upon the beginning of productive use the County will pay the Vendor the remaining 50 percent (50%) of custom interfaces and other customizations. c. Upon order the County will pay the Vendor 100 percent (100%) of change orders Independent Contractor Status It is expressly understood and agreed that the proposing Vendor is an independent contractor at all times and for all purposes hereunder. Officers, employees or representatives of the Vendor will not be deemed in any way to be and shall not hold themselves out as employees, servants, representatives or agents of the County and will not be entitled to any fringe benefits of the County such as, but not limited to, health and accident insurance, life insurance, longevity, economic increases or paid sick or vacation leave. The Vendor will be solely responsible for payroll wages, for the withholding and payment of all income and social security taxes to the proper federal, state and local governments and for providing workers compensation and unemployment insurance of the Vendor Assignment of Contractual Rights It is agreed that the successful Vendor shall not assign, transfer, convey or otherwise dispose of the contract or its rights, title or interest in any part thereof, without prior PAGE 9

10 written notification to the County. All subcontractors providing on site services must be approved by the County Statement of Time A period of time, unless stated as a number of workdays, shall include Saturdays, Sundays, and holidays Non discrimination in Employment and Affirmative Action During the performance of this contract, the Vendor agrees as follows: 1. The Vendor will not discriminate against any employee or applicant for employment because of race, religion, color, sex or national origin, except where religion, sex or national origin is a bona fide occupational qualification reasonably necessary to the normal operation of the Vendor. The Vendor agrees to post, in conspicuous places available to employees and applicants for employment, notices setting forth the provisions of this non discrimination clause. 2. The Vendor, in all solicitations or advertisements for employees placed by or on behalf of the Vendor, will state that such Vendor is an equal opportunity employer. 3. Notices, advertisements and solicitations placed in accordance with federal law, rule or regulation shall be deemed sufficient for the purpose of meeting the requirements of this RFP Qualifications of Proposers The County may make such reasonable investigations as deemed proper and necessary to determine the ability of solicited and unsolicited Proposers to perform the work. Proposers must furnish the County all such information and data for this purpose as may be requested. The County reserves the right to inspect Proposers' physical plants prior to award to satisfy questions regarding Proposer capabilities. The County further reserves the right to reject any proposal if the evidence submitted by or investigations of such Proposer fails to satisfy the County that such Proposer is properly qualified to carry out the obligations of the contract and to complete the work contemplated herein Compliance with the Law Vendors shall adhere to all applicable federal, state and local laws ordinances and regulations while rendering services pursuant to any Agreement entered into as a result of this RFP Maintenance Software maintenance support is expected to be available on a hotline or similar capability so that County personnel may contact support technicians. A secure highspeed Internet connection is required for software troubleshooting. Vendors will offer a yearly maintenance contract for software support to begin upon acceptance of the system in their bid document. It is preferred that software maintenance annual prices quoted in the proposal will be firm for one year from date of acceptance Licenses, Permits and Approvals PAGE 10

11 The Vendor will obtain and pay for all permits, licenses and approvals necessary for them to perform their contracted services. The Vendor will comply with all of the laws ordinances, rules orders and regulations relating to performance of work. It is the County s responsibility to obtain and pay for FCC and other licenses they are required to obtain. The Vendor can assist the County in this process, if agreed to for the project, but in an advisory capacity only. 3. Proposal Format The proposal must contain the following sections, in the order and format described: Table of Contents: 1. Executive Summary 2. Company Profile 3. Response to Technical Requirements 4. Description of the Proposed System Software and Minimum System Requirements. 5. Project Management Services 6. Training Services 7. Maintenance, Warranty and Support information. 8. References. Provide at least three (3) reference sites of similar systems with contact name, phone number, address, applications installed, population served and date of installation. 9. Price Proposal. Include comprehensive, itemized pricing for each element of Proposer s bid. 4. Technical Requirements The Vendor s proposed application software must be capable of meeting the mandatory requirements as set forth in the application software checklists provided in this section. The County prefers that all proposed software be currently developed and installed in other jurisdictions. While some modification of the proposed software may be required on the part of the Vendor to meet the County s requirements, the County will not consider options where new system development is proposed for entire modules. The intention of the County is to purchase commercial off the shelf (COTS) software that has a high degree of functionality. When packages do not precisely meet the County s requirements, the Vendor must state the costs and schedule to update the packages to meet the County s specifications. The cost of all modifications to the Vendor s software must be included in the proposal cost submitted to the County. Modifications to the software must be made in such a way that the County will not be prevented from implementing future releases of the Vendor s software Functional Requirements Checklist Format Vendors are required to complete and submit all application software checklists included in this section. Each Vendor s application software will be evaluated based on the information in the checklists. These checklists will be included, along with the rest of the RFP, in the contract with the Vendor. Acceptance of the system will be contingent upon the Vendor s delivering software that includes all the features promised by the Vendor. PAGE 11

12 4.2. Mandatory Requirements The following requirements are MANDATORY features that must be available in the proposed system Response Codes The Vendor must use the following codes when completing the application software requirements matrix. For each feature listed, the Vendor must include one of the following codes in the Code column. When the PF or CD code is used, the Vendor must also include an explanation of the planned feature or custom development in the Exceptions section that follows the matrix. These exceptions must refer to the section and requirement number. SF Standard feature of the proposed software, currently available and installed at customer sites. PF Planned feature of the standard software, available in a future release. CD Feature will be provided as an agency specific custom developed option. NA This feature is not available and there is no plan to provide it. Vendors must complete the following general requirements questionnaire for the proposed application software. Apply a single response code, refer to instructions page for each feature listed. Blanks will be considered non responsive and are cause to remove the vendor from consideration CAD Requirements Item # Requirement Code General Specifications All equipment must comply with any and all applicable Federal Communications 1 Commission Regulations, Part 68 and Part 15, sub part J. All equipment must have been in service providing service to a client within the 2 Continental United States for a minimum of six (6) months. The system must be capable of complete dial up remote diagnostics and maintenance. 3 The vendor must offer a single point of contact for reporting troubles with E equipment, Logging Recorder, CAD and the mapping application. The vendor must offer software upgrades at no additional cost for the duration of the 5 maintenance agreement. 6 All training must be completed using the agencies data. The vendor must collect and load the agencies CAD data, including units, status codes 7 and event codes. The CAD system must be capable of a wide range of networking and communications options for the use of Local Area Networks using TCP/IP and asynchronous 8 communications. The CAD system must interface seamlessly to the other systems, including VoIP phone 9 system, VoIP radio system, and the IP based recorder. General CAD Functionality The CAD software package must provide computer aided dispatching and unit update windows, available units and stations inventory windows, active units status windows 9 and active calls windows. The CAD system must allow users to change color schemes within windows to add to 10 ease of use. PAGE 12

13 The CAD system must allow users to customize windows, including resizing and 11 repositioning windows, changing sort options and hiding or viewing columns. The system must allow users to change and save their window attributes and changes 12 (including window size and position, visible columns and column order) 13 Changes to window attributes and views must be permission based. The CAD system must allow for a default dispatcher profile in order to allow 14 agencies to maintain consistency in views of CAD screens The CAD software must be supplied with an E9 1 1 interface to allow easy entry of basic 15 call information into the system and to eliminate redundant data entry. The CAD system must allow for one click removal of location information auto filled 16 from E interface is not the location of the incident. The CAD system must be able to take Phase II Latitude/Longitude information and 17 recommend the nearest physical address. The CAD system must be able to take re bid Phase II information and recommend an 18 updated address to the user. The software must automatically assign an incident number to each CAD call. These 19 numbers must be comprised of the four digit year and a sequential number. The CAD system must allow case (OCA) numbers to be manually assigned on incidents 20 where desired. The CAD system must allow for multiple case/run numbers to be assigned to an 21 incident The system must allow for automatic case number/run number generation based on 22 disposition code The CAD system must allow Run or Department numbers to be automatically assigned 23 on dispatch. The CAD system must allow for each department to utilize its own set of case/run 24 number and allow numbers to be rolled monthly or yearly. 25 The software must support both field entry and command line entry of data. The CAD system must maintain a complete call detail record for each event and must be compatible with the incident reporting and records management subsystem. 26 The CAD system must track units during non emergency or routine functions that take 27 up a unit s time, such as time spent in court or in the squad room. The CAD system must automatically assign a priority to an incident based on the event 28 code utilized. The CAD system must allow for the assigned/default priority to be agency/organization 29 specific. 30 The CAD system must allow for at least nine call priorities. The CAD system must allow for the entry of an incident disposition when an incident is 31 closed. The CAD system must allow for an incident disposition to be changed after the incident 32 has been closed for any period of time. The CAD system must allow for a disposition to be required before the incident can be 33 closed. The CAD system must provide a list of disposition codes to be displayed when entering 34 a disposition code. The CAD system must provide a list of event codes (complaint types, incident types) to 35 be displayed upon demand when entering a new incident. The CAD system must allow entry of future calls. These pending calls are reported to the users at a pre determined time. The system will then alert the operator of the call 36 status and requirements. PAGE 13

14 37 38 The CAD system must allow multiple CAD functions to be in progress at the same time. The CAD system must provide function key access for frequently used screens and functions. The CAD system must provide an interactive help function with computer initiated 39 dialogues such as menu selections or Windows based point and click functions. 40 The CAD system must provide online access to complete help documentation. 41 The CAD system must provide context sensitive online help. 42 The CAD system must allow a closed CAD incident to be re opened. 43 The CAD system must maintain a file of all calls received. The CAD system must have a module to allow users to enter (back in) calls and data 44 after system downtime (Catch Up module). The CAD system must have the ability to log users off automatically after a predetermined 45 period of inactivity. The CAD system will allow users to track government mandated statistics (collect 46 Racial Profiling data). 47 The CAD system will require dates to be entered in an MMDDYYYY format. 48 The CAD system requires a military (24 hour) time format. 49 The CAD system will function in a single or multi jurisdictional environment. The CAD system must allow users to search and view jail inmate information when 50 applicable. The CAD system, where used simultaneously with EMD, must upgrade or downgrade 51 events based on information from EMD. The CAD system, where used simultaneously with EMD, must include EMD comments 52 in CAD narratives. The CAD system, where used simultaneously with EMD, must allow for the coexistence of CAD and EMD event codes: to either allow or prevent EMD codes 53 overwriting CAD codes. The CAD system, where used simultaneously with ProQA, must provide a narrative 54 reason if and when a ProQA session is terminated. The CAD system, where used simultaneously with ProQA, must include ProQA 55 questions as part of other CAD details. The CAD system, where used simultaneously with EMD, must allow restriction of EMD 56 functionality to users, as determined by management. 57 The CAD system must allow units to be logged in by unit #, badge # and radio. 58 The CAD system must allow for multiple personnel to be logged into one unit. The CAD system must allow dispatcher to view personnel information associated with 59 unit occupants. 60 The CAD system must allow dispatchers to search for officers by skills The CAD system must allow dispatchers to search vehicle ID numbers for personnel 61 information 62 The CAD system must allow paging of units (manually and automatically). The CAD system must transmit CAD incident numbers as part of alphanumeric pages The CAD system must allow faxing of incident details (manually and automatically). The CAD system must have the ability to exclude specific incident detail information 65 when faxed. The CAD system must have the ability to restrict users from manually entering a fax 66 number that is not defined in the system. 67 The CAD system must interface with TDD (Terminal Device for the Deaf) systems. PAGE 14

15 The CAD system must allow media files to be attached to CAD incidents and viewed. The following files must be supported: Windows Media Player files; Image files such as 68.tif,.jpg, etc.; Adobe.pdf files and Microsoft Word files (.doc). The CAD system must provide validation to ensure entry of proper two letter state 69 abbreviations, where used. The CAD system must allow for export of rip and run prints to remote printers on the 70 network. 71 Rip and run prints must be configurable. The CAD system must allow for export of data in ASCII format for use in third party 72 applications. 73 The CAD system must provide support for a minimum of five (5) unit types. The system must provide a system status management/coverage plan module that will utilize agency defined coverage plans to display unmanned EMS posts and resource 74 allocation. The system must alert users when EMS posts are unmanned (or resources have fallen 75 below system status/coverage plan requirements). The system will make recommendations for resource relocation based on the EMS 76 system status coverage plan. The system must allow users to relocate resources to EMS posts by drag and drop 77 functionality. Users must have the option to display the current EMS resource allocation/post 78 coverage at all times. The CAD system will recommend units for dispatch by considering the current EMS 79 post coverage. The CAD system must provide the ability to view in the traffic stop module previous 80 CAD incidents related to a particular vehicle. 81 The CAD system must allow multiple traffic stop screens to be open simultaneously. The CAD system s unit log must provide documentation of activities performed and the 82 identity of the user responsible for each activity. The CAD system will automatically determine the priority of the incident based upon 83 the incident type. 84 The CAD system will color code events in the active events display by priority. All CAD stations will be updated with new status information automatically and 85 immediately. 86 The CAD system must allow users to add information to an incident at any time. The CAD system must distinguish an in progress type incident from other pending 87 incidents. The CAD system must allow dispatchers to view/access narratives from the Narratives Viewer window for viewing, editing, adding information or sending to other CAD users. Feature will provide users the ability to quickly view all narratives for all calls. 88 The CAD system will allow users to be set up as call takers only and restrict such users 89 from dispatcher functions The CAD system must provide users the ability to stack or assign low priority calls to a 90 busy unit. The CAD system will allow units to be assigned to calls through drag and drop 91 functionality (clicking on a unit ID and dragging it to the call to be dispatched on). 92 The CAD system will allow dispatchers to have the ability to update unit statuses. The CAD system must provide the ability to place all units in a station out of service or 93 off duty at one time. The CAD system must provide the ability to place all units in a station in service or on 94 duty at one time. PAGE 15

16 The CAD system must allow users to place a unit en route or on scene after notification 95 from the unit even if the unit was not dispatched. The CAD system must allow users to view unit history/log information from command 96 line or function key Users must have the ability to view the CAD incident from the unit log when a CAD 97 incident number is displayed The CAD system must differentiate between active (dispatched) and pending (nondispatched) calls in the system monitor Users must be able to toggle between pending and active calls. 100 The CAD system must have a separate pending calls window. The CAD system must allow a dispatcher to control a single incident and units assigned to the incident, with the single incident being the only one showing on their monitor. 101 The CAD system shall allow for incidents to be stacked or held for a particular unit and 102 will distinguish the held call in the pending calls window. The CAD system shall allow for incidents to be re opened from CAD history screen and 103 CAD Inquire screen The CAD system must allow for duplicate incidents to be merged and all information is 104 transferred to the incident remaining open. When duplicate call exists in CAD history, there must be a visual indicator for the 105 dispatcher When entering an incident a pop up must appear to alert the dispatcher they are about 106 to cancel entry of the incident. The CAD system must allow users to quickly select any call from the display for 107 updating. The CAD system must allow units to be added as assisting (backup) units on a call after 108 it has been dispatched. The CAD system must automatically send a call back to the pending call queue if all 109 assigned units are preempted from that call. The CAD system must alert users of the existence of standard operating procedures 110 based upon call type and location. The CAD system must allow administrators to develop specific lists of questions for users to ask callers based upon event types. These questions must automatically 111 appear when a call with that event type is placed. 112 The CAD system must allow for handling of calls for towing service. The CAD system must allow for assignment of wrecker companies from a rotating wrecker company assignment table and must allow for automatic assignment of the 113 next company in a user defined rotation. The CAD system must allow for multiple wrecker rotation areas, each with their own 114 rotation order and type of rotation selection. The CAD System must track a history of all wrecker companies and their status on a 115 wrecker incident. The CAD system must allow for a wrecker to be returned to the wrecker assignment 116 list out of sequence and be used as the next up wrecker The CAD system must allow for assignment of wrecker companies outside of the rotation (owner s request) to accommodate callers requesting a specific wrecker 117 company. The CAD system must allow dispatchers to search for wrecker incidents by tag number, 118 make, model or color, owner name or wrecker company. 119 Partial or wildcard searching of wrecker information is required. The CAD system must provide the auto populate basic vehicle information into the 120 wrecker incident. PAGE 16

17 The CAD system must allow users to track/store impound, hold and release 121 information. The CAD system must provide a pre formatted input screen for quick entry of officerinitiated traffic stops. 122 The CAD system must provide a Function key for quick access to entry of traffic stops. 123 The CAD system must automatically query NCIC for vehicle registration on all methods 124 of traffic stop entries The CAD system must allow dispatchers to enter data on vehicles involved in incidents. 125 The CAD system must allow dispatchers to search for vehicles involved in prior incidents by VIN number, tag number, make, model or color. Partial or wildcard 126 searching of vehicle information is required. 127 The CAD system will allow users to place a call on hold in order to take another call. The CAD system will allow users the ability to save partially completed calls for service, which the user will then be able to retrieve and finish processing in any order. 128 The CAD system must allow users to enter a narrative of unlimited length on incidents The CAD system must allow users to add to a narrative as an incident progresses. The CAD system must allow a setup option that limits editing of narratives to the 131 creator of the narrative only. 132 The CAD system must include spell checking for narratives. 133 The CAD system must allow users to add to a narrative after an incident is closed. The CAD system must alert users of possible duplicate calls based upon incident 134 location. The CAD system must alert users of possible duplicate calls based upon user defined 135 radius search. 136 The CAD system must allow for the tracking and billing of false alarms. The CAD system must allow users to send messages to users or groups of users of their 137 choice. The CAD system must allow users to send mail to external users (through MS Outlook) 138 from the CAD mailbox. 139 The CAD system must allow users to forward and reroute messages. The CAD system must allow users to send messages to mobile units if interfacing with 140 MDTs. The CAD system will allow users to inquire into past CAD incidents via a form where 141 they can input search variables. The CAD system must allow users to inquire into past CAD incidents with partial data or 142 wildcard searches. The CAD system will allow users immediate access to summary or detail on all incidents 143 visible on their screens. 144 The CAD system will allow for an unlimited number of active incidents. The CAD system will allow users to enter data of any sort into a Book File where they 145 can call it up quickly for reference. The CAD system will allow users to enter Pre Fire Plans based on building names, 146 addresses or locations. The CAD system must allow users to monitor in progress events with real time 147 updates. The CAD system must allow users to save/wait incomplete calls for service in order to 148 process higher priority calls. 149 Incomplete calls for service must be accessible to all users. PAGE 17

18 The CAD system must provide a way to identify if the reporting party has requested 150 contact with responders. The CAD system must allow users to enter a situation found code for calls for 151 service. Timers The CAD system must utilize event and unit status timers to monitor units as a call 152 progresses. The system must notify the operator of overdue conditions. The CAD system must provide an initial check back after a period of time between when a unit first arrives on scene to when the software must first prompt the 153 dispatcher to check on the unit s condition. 154 The CAD system must provide the ability to reset timers after any status change. 155 The CAD system must provide for timers based on event priority. The CAD system must provide both an audio and visual indicator when a timer has 156 expired. 157 The CAD system must provide dispatch to enroute timers. 158 The CAD system must provide the ability to assign a timer to any status code. 159 The CAD system must provide for station timers. 160 The CAD system must provide the ability to view all expired timers. The CAD system must provide the ability to view all units and stations that have an 161 associated timer regardless if the timer has expired. Alerts and Warnings 162 The CAD system must make visual alerts to the user when BOLO warnings occur. The CAD system must make visual alerts to the user when hazard warnings occur at a 163 specific incident location. The CAD system must make visual alerts to the user when previous incident history at a 164 specific location is available. The CAD system must make visual alerts to the user when place/landmark information 165 is available for an incident at a specific location. The CAD system must make visual alerts to the user when pre fire information is 166 available for an incident at a specific location. The CAD system must make visual alerts to the user when hydrant information is 167 available for an incident at a specific location. The CAD system must make visual alerts to the user when directions to an incident s 168 specific location are available. The CAD system must make visual alerts to the user when warrant information is 169 available for an incident s specific location. The CAD system will alert a user upon attempt to log off if a pending call remains 170 incomplete in that user s stacked (pending) call queue. 171 The CAD system will visually alert a user if a new message has been received. The CAD system will, optionally, visually alert users when narratives are added to an 172 incident of relevance to them. When units are logged en route to a hospital location that has been closed or a 173 diversion to another hospital exists, users must be alerted in CAD 174 The system will alert users to hydrants in the area when available. When an incident is upgraded to a traffic pursuit, the CAD system will alert all 175 positions. The CAD system must allow different audible alerts to be assigned to different 176 messages based upon the type of the messages. The CAD system must allow different audible alerts to be assigned to different 177 messages based upon the priority of the messages. The CAD system must filter the Alerts list so alerts are grouped by incident and color 178 coded to correspond with a unit's status. PAGE 18

19 Logins/Security The CAD system will require a login and password in order to gain entry to the 179 software package. The CAD system must have the ability to lock a user out of the system if they have 180 exceeded the set number of logon attempts. The CAD system will require the login identification to become part of the CAD incident record for all calls created and modified. All data entered will be stamped with the 181 user s login identification. The CAD system must allow Administrators to be able to select the resource types for which call takers and dispatchers will be responsible by geographic area, agency type, 182 special group or any combination of these. The CAD system must allow that only calls in the dispatch group assigned to or being monitored by the call taker/dispatcher will appear in that user s call queue when they 183 are automatically routed by the system. The CAD system must provide a method of viewing changes to a closed incident, 184 including the name of the user implementing the change. The CAD system must provide an audit trail to track changes and additions made to an 185 incident or unit status. MSAG/GIS Functionality The CAD system must utilize an on line Master Street Address Guide and geographic reference feature to insure that appropriate emergency response resources are 186 dispatched to legitimate addresses. The CAD system must automatically determine the response zone, police zone and 187 jurisdiction based on a verified incident location. The CAD system must allow that upon entry of the incident location, an automatic look up in the geographic database must verify the given incident location as a valid 188 address. The CAD system must notify the call taker or dispatcher if the address does not verify 189 against the MSAG/Geo file. The CAD system must allow the call taker or dispatcher to enter an address that does 190 not verify against the MSAG/Geo file. The CAD system must allow the entry of Directions to a location which will be visible 191 upon demand and upon a new incident at that location. 192 The CAD system must allow for alias street names such as abbreviations The CAD system must allow for multiple aliases for street names, intersections, 193 commonplace names, landmarks, or street/highway route numbers. The CAD system must allow for a display of the nearest high and low cross streets 194 upon MSAG/Geo validation. 195 The CAD system must display the nearest mile marker upon MSAG/Geo validation. The CAD system must allow the user to enter a location as a commonplace or business name (place/landmark). The system must automatically connect the commonplace or 196 business name with an exact address. The CAD system must allow common place name entries to include an apartment or 197 building number. The CAD system will provide a Soundex type look up for street names, road and 198 highway names, intersections and place/landmark names. The CAD system must allow the user to input the correct location if the E9 1 1 location 199 automatically sent is not correct. The CAD system must allow the user to enter partial street names to speed up the 200 location entry and verification process. The CAD system must search for all possible matches that include directional's, types, 201 or suffixes, even if these are not entered. PAGE 19

20 The CAD system must log location entries that do not validate against the MSAG yet are saved as the correct address by the user. The CAD system must provide address verification for and acceptance of invalid addresses, number ranges, street names, intersections, mile markers, rural routes and places/landmarks. When dispatching to a street that occurs in multiple cities, the CAD system must display a list of all matching streets for each city. Command Line Entry The CAD system must allow the ability to invoke Command Line entry with a single keystroke. The CAD system must allow the Command Line entry window to be removed from the screen if the call taker/dispatcher does not wish to use it. The CAD system must allow command line entry users to scroll through and reselect previous command line entries with the use of a mouse or the keyboard. The CAD System s Command Line entry will consist of a command identifier followed 208 by data parameters. 209 The CAD system will provide a help display for Command Line functions. 210 The CAD system must allow a dispatcher to select an incident for dispatch. 211 The CAD system must allow multiple command lines to be open simultaneously. Unit/Equipment Recommendation The CAD system must provide automatic unit recommendation for an event based on 212 the event type and the zone, beat and response planning and availability. Based on the nature code and location, the CAD system must provide appropriate 213 recommendations on the agency that must be dispatched. The CAD system must allow dispatchers to override unit recommendation when 214 required. The CAD system must allow units dispatched on a busy status (house checks, etc.) to 215 be eligible for recommendation on higher priority incidents. The CAD system will have the ability to recalculate Unit Recommendations if the 216 incident type, incident location or incident priority change. 217 The CAD system has the ability to recommend multiple units. 218 The CAD system must have the ability to recommend Fire units. The system must allow units to be labeled with a minimum of 20 unit types/attributes 219 or equipment identifiers. The CAD system must allow for alpha numeric character unit types that are up to characters each. 221 The CAD system must have the ability to recommend EMS (Rescue) units. The CAD system has the ability to recommend units of multiple types if necessary (Fire 222 and Law, for example) on the same incident. The CAD system must have the ability to recommend the appropriate units or 223 apparatus based upon the type and location of the incident. The CAD system must allow for specific recommendations (response line ups such as 1 ALS unit) for each class or units/organization based on time of day and day of week The system must allow for differing response line ups/recommendations based on geographic location, for the same event type. The CAD system must allow for the recommendation of mutual aid depending on the incident type, incident location and type of equipment necessary. The CAD system must allow for specific unit type/apparatus recommendations for each class or organization of units on the same incident. The CAD system must display the primary zones recommended for the incident in the system monitor window. PAGE 20