Docstoc

Luzerne County CAD RMS RFPword

Document Sample
Luzerne County CAD RMS RFPword Powered By Docstoc
					    Request for
     Proposals

      Fo r
 Luzerne County
  Pennsylvania

Computer Aided Dispatch/
  Records Management
        System
                                                  Table of Contents
Section 1 Project Objectives and Guidelines ...................................................................... 3
  1.1 Agency Background.................................................................................................. 3
  1.2 Project Objective ....................................................................................................... 3
  1.3 Proposal Submittal .................................................................................................... 5
  1.4 Questions Regarding This Request for Proposals ..................................................... 5
  1.5 Pre-bid Conference ................................................................................................... 6
  1.6 Award Criteria .......................................................................................................... 6
  1.7 Proposal Preparation Costs ....................................................................................... 7
  1.8 Completeness of Response ....................................................................................... 7
  1.9 Compliance with Industry Regulations and Standards ............................................. 7
  1.10 Addendums to this Request for Proposals .............................................................. 8
  1.11 County Project Manager ......................................................................................... 8
Section 2 Business Terms and Conditions .......................................................................... 9
  2.1 Payment Terms ......................................................................................................... 9
  2.2 Independent Contractor Status .................................................................................. 9
  2.3 Subcontracting .......................................................................................................... 9
  2.4 Assignment of Contractual Rights .......................................................................... 10
  2.5 Insurance ................................................................................................................. 10
  2.6 Intellectual Property Management .......................................................................... 10
  2.7 Warranty ................................................................................................................. 10
  2.8 Compliance with the Law ....................................................................................... 11
  2.9 Maintenance ............................................................................................................ 11
  2.10 Licenses, Permits, and Approvals ......................................................................... 12
Section 3 General Requirements ....................................................................................... 13
  3.1 General System Specifications ............................................................................... 13
  3.2 Security Features ..................................................................................................... 13
  3.3 Configuration Diagram ........................................................................................... 13
  3.4 Training ................................................................................................................... 14
  3.5 Support and Maintenance ....................................................................................... 14
  3.6 Project Work Plan ................................................................................................... 15
Section 4 Application Software Requirements ................................................................. 15
  4.1 Functional Requirements Checklist Format............................................................ 15
  4.2 Functional Requirements Matrixes ......................................................................... 17
Section 5 Proposal Format and Guidelines ....................................................................... 37
Appendix A Hardware/Software Requirements ............................................................... 38
Appendix B Non-Collusion Affidavit……………………………………………………41




                                                                                                                                   2
Section 1 Project Objectives and Guidelines

1.1 Agency Background

The County of Luzerne is approximately 891 square miles, located in Northeast
Pennsylvania. Its population is approximately 320,000 residents.

Public safety communications are processed by the 911 Center at 100 Young
Street, Wilkes-Barre, PA where all 911 calls are routed to and dispatched from.

The dispatch center serves 49 police agencies, support for 6 additional police
agencies, 111 fire departments, and 85 ambulance services and dispatches
approximately 350,000 calls for service per year.


1.2 Project Objective

The County is seeking a modern CAD/RMS Commercial-off-the-Shelf (COTS)
integrated software solution using state-of-the-art Microsoft .NET technologies.
The primary objective of the project is to increase the overall efficiency of
information flow through the Agencies, increase safety for all responding units,
provide real time intelligence, and provide enhanced service to the community.
In order to best leverage the County‟s existing technical infrastructure and
support resources, and to ensure an abundant future labor pool, the County is
seeking solutions which are developed in its entirety using Microsoft .NET
platform. Preference will be given to vendors authorized by Microsoft
Corporation, with a designation of Gold level Partner and Certified Microsoft ISV
preferred. The vendor must demonstrate expertise in the latest .NET
technologies and development methodologies, applying them appropriately
within the proposed solution.

The system must be able to support up to 300 named and 400 concurrent users
in a diverse LAN/WAN/WLAN network environment.

In order to achieve our primary objective, the software architecture must:

      Be completely developed using Microsoft Visual Studio tools with all native
       application code written in VB.NET or C#
      Support a relational database platform operating on the Microsoft SQL
       Server 2005 or 2008 Enterprise Edition database engine
      Employ the extensive use of stored procedures within the database that
       directly leverage the benefits and performance enhancements available
       within the SQL Server environment
      Utilize ADO.NET to provide a modular and extensible data-access layer
       which isolates business logic functions from both the database and client

                                                                                    3
       application code using a business object framework in an n-tier
       implementation
      Utilize Microsoft Smart Client technology to allow the client application to
       be „single-click‟ installed, centrally managed and automatically updated
       through Web services technology
      Leverage the .NET framework on the Smart Client to provide a reliable,
       functional and feature-rich user interface which is both lightweight and
       tightly integrated with the operating system
      Support a service oriented architecture (SOA) using Microsoft Internet
       Information Services and Web services (SOAP/XML) technology to allow
       maximum integration capabilities with other back end systems and
       databases
      Be an integrated solution consisting of Computer Aided Dispatch, Records
       Management System and Mobile Data Computer

The system must utilize Web Services to provide bi-directional interfaces with:

      The State/NCIC System hosted by PA State Police
      Regional (Other Criminal Justice Information Systems)
      The US Postal Service‟s ZIP+4 address validation database
      Microsoft‟s MapPoint and/or Virtual Earth global mapping systems
      Local ESRI GIS database(s)
      State IBR (incident-based reporting) repositories including the ability to
       electronically transmit pre-validated, compliant IBR data to (Agency)
       Electronic ticketing and delivering E-Ticket data to the State
      Capability to integrate with Automated Fingerprint Identification Systems
      Intergrate with Pennsylvania's J-net
      Interface to NFIRS fire reporting system

The application software must provide the following standard modules:

      Accident Reporting with integrated CLEAN interface and barcode support
      Aided/EMS Assist Case
      Alarm Call Tracking & Billing
      Arrest
      CAD with E911, AVL, Mapping and Polygon Jurisdiction capabilities
      Case Reporting and Management
      Citation with integrated CLEAN interface and barcode support
      Diary & Activity Log
      Event/Incident integrated with CAD
      Field Interview Reporting
      Impound/Towing with automated letter generation
      Interagency Data Sharing
      Order of Protection
      Personnel including equipment inventory and training
      Property/Evidence with integrated barcode support and chain of custody
      Premise checking and reporting
                                                                                    4
      Warrant generation and service/attempt tracking

All modules must support:

      Unlimited data Interlinking by associating records to other modules
      Ad Hoc Queries to isolate specific functional reports, or summary lists
      Consistent reporting tool for all functional, summary and statistical reports
      Ability to easily print, export or email any report in a variety of common
       formats
      Extensive logging of any access to or dissemination of all data
      Highly configurable and dynamic role-based security paradigm
      National Address Validation capability wherever addresses are entered
      Universal mapping and instant Lat/Long geo-coding of any location
      Master Index validation (Person, Vehicle, Location, etc. ) with duplicate
       record merge capabilities
      Comprehensive System Searching of all master indices
      System Wide Master Index Alert and Alert Management
      All reports must be bar-coded as to retrieve the electronic record
      Complete paperless capability


1.3 Proposal Submittal
Sealed proposal responses, clearly marked CAD/RMS/Mobile Communication
System Proposals are due by 4:30P.M. November 28th, 2008. 1 original and 4
paper copies including appendix B, SIGNED NON-COLLUSION AFFIDAVIT:
Must be delivered to the following address:
     Name: Mr. Greg Hunsinger
     Office: Purchasing Director
     Street Address: Penn Place Suite 203 20 N.Pennsylvania Avenue
     City, State, ZIP: Wilkes-Barre, Pa. 18701
     Telephone: (570) 820-6337
     Email: Greg.Hunsinger@luzernecounty.org

No bid may be withdrawn within 30 days of the due date.


1.4 Questions Regarding This Request for Proposals

Any questions about this proposal are to be submitted in writing by:
November 5th, 2008 by 4:00 P.M. EST.

All questions will be answered by November 14th, 2008 and will be posted on
Luzerne County's website: www.luzernecounty.org.




                                                                                   5
Questions should be directed to:

     Name: Fred J. Rosencrans or John Ankenbrand
     Office: Luzerne County 9-1-1
     Street Address: 100 Young Street
     City, State, ZIP: Hanover Township, Pa. 18706
     Telephone: (570) 826-3059
     Email: Fred.Rosencrans@luzernecounty.org or
            John.Ankenbrand@luzernecounty.org

      FAX: (570)826-3056


1.5 Pre-bid Conference

A Mandatory Pre-Proposal Conference and Site Visit for the purpose of
reviewing the RFP, answering questions and visiting the locations regarding the
requested Services will be held on Wednesday, October 29th, 2008 @ 9A.M.
Luzerne County EMA Building EOC 185 Water Street Wilkes-Barre, Pa, 18702.
Phone: (570) 820-4400. Mandatory Site Visits will be conducted from 1:00 p.m.
till 4:00 p.m. at all required locations as well. Please bring a copy of the RFP
with you at that time.

1.6 Award Criteria

Local Government’s Rights and Options.

The Local Governments reserves the following rights, which may be exercised at
the Local Government‟s sole discretion:
1. To supplement, amend, substitute or otherwise modify this RFP at any time;
2. To cancel this RFP with or without the substitution of another RFP;
3.To take any action affecting this RFP, this RFP process, or the Products and
Services or facilities subject to this RFP that would be in the best interests of the
Local Governments;
4. To request additional information;
5. To require one or more Service Providers to supplement, clarify or provide
additional information in order for the Local Governments to evaluate the
Proposals submitted;
6. To conduct investigations with respect to the qualifications and experience of
each Service Provider;
7. To waive any defect or irregularity in any Proposal received;
8. To reject any or all Proposals;
9. To award all, none, or any part of the Products or Services that is in the best
interest of the Local Governments, with one or more of the Service Providers
responding, which may be done without or without re-solicitation.
10. To discuss and negotiate with selected Service Provider (“Prime Contractor”)
any terms and conditions regarding Hardware, Project Plan, Software and
Company submitted Proposals, including but not limited to financial terms; and
                                                                                      6
11. To enter into any Agreement deemed by the Local Governments to be in the
best interest of the Local Governments, with one or more of the Service
Providers responding.

Contract award will be to a responsible Vendor, based on an analysis of the
following criteria:

A contract will be negotiated with the Vendor proposing a system that the County
determines is in its best interest. Examples of the factors the County will use in
making this determination are:

   The software conforms to software and hardware specifications in this RFP.
   The comprehensive cost of the solution, hardware, software, training, support,
    and other proposed items
   Mandatory Commonwealth of Pennsylvania-specific features including: Bi-
    directional CLEAN/NCIC interface supporting all available transactions
   Similarity of proposed system to other systems in use by other agencies the
    County may work with.
   Vendor‟s reputation with current and past users
   Availability of service and support based on support requirements in the
    functional section of this RFP.
   Quality of service and support based on the support requirements in the
    functional section of this RFP as well as references from support customers.
   Potential for system growth – scalability and the capability to support a RMS
    multiple agencies in an ASP model
   Implementation of state-of-the-art technologies and vendor history of
    technological progress



1.7 Proposal Preparation Costs

The Vendor is responsible for any costs incurred in responding to the proposal.


1.8 Completeness of Response

Failure to include in the proposal all information solicited in this Request for
Proposals may be cause for rejection of a Vendor‟s proposal.



1.9 Compliance with Industry Regulations and Standards

All contractors, during their work, construction, and equipment installation, must
meet or exceed current standards of at least the organizations listed below,
where applicable:

                                                                                     7
   Federal Communications Commission (FCC)
   Electronic Industries Association (EIA)
   Institute of Electrical and Electronic Engineers (IEEE)
   Environmental Protection Agency (EPA)
   Contractor Work Hours and Safety Standards Act
   Equal Opportunity Act
   Federal Aviation Authority


1.10 Addendums to this Request for Proposals

The County 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.

It will be the responsibility of each Vendor, prior to submitting the competitive
proposal, to contact our representative to determine if addendums were issued
and to make information in such addendums a part of their competitive proposal
solution.


1.11 County Project Manager

The County‟s Project Manager will be:

     Name: Douglas Pape
     Title: County Manager/Chief Clerk
     Organization: County of Luzerne
     Address: 200 North River Street
     City, State, ZIP Code: Wilkes-Barre, Pa. 18711
     Telephone: (570) 825-1635
     Email: Doug.Pape@luzernecounty.org




                                                                                    8
Section 2 Business Terms and Conditions

2.1 Payment Terms

Payment terms to be discussed and implement upon final choice of vendor. In
general a performance bond will be required from the selected vendor. A
minimum of 10% will be held until completion of acceptance testing.

2.2 Independent Contractor Status

It is expressly understood and agreed that the proposing Vendor is an
independent contractor at all times and for the purposes of the contract. Officers,
employees, or representatives of the Vendor will not be deemed in any way to
be, and must 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 or economic increases, or paid sick or vacation leave. Solely the
vendor will be responsible for paying 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.

2.3 Subcontracting

The vendor may elect to use subcontractors for components of the project,
provided the following are observed:

      Agencies are not permitted to subcontract or assign any part of the work
       covered under the scope agreement, without the express prior to written
       consent of Luzerne County.

      The Vendor will provide documentation to the County that it, or the
       organizations selected can continue to support all hardware and software
       in the event another company or subcontractor should go out of business
       or cease to do business with the Vendor for any reason.

      Vendors securing software from another company or subcontractor must
       provide documentation to the County that the Vendor has software source
       code or has the right to obtain such code upon default of the other
       company or subcontractor.

      The vendor will provide copies of any subcontract agreements to the
       County before receiving down payment.


                                                                                  9
2.4 Assignment of Contractual Rights

It is agreed that the successful Vendor must not assign, transfer, convey, or
otherwise dispose of the contract or its rights, title, or interest in any part thereof,
without prior written notification to the County.


2.5 Insurance

The successful vendor will, prior to beginning work, provide the following
evidence of insurance:

      Comprehensive General Liability $1,000,000 / $2,000,000. Luzerne
       County named as an additional insurer.

      Automobile Liability $1,000,000. Luzerne County named as an additional
       insured.

      Errors and Omissions $1,000,000. Luzerne County named as an
       additional insured.

      Workers Compensation Statutory Coverage.

The vendor shall furnish to Luzerne County a certificate of insurance, which shall
provide that the insurance indicated therein, shall not be cancelled without at
least thirty (30) days written notice to the Luzerne County.


2.6 Intellectual Property Management

Vendor must have in place an escrow solution with a third party for Vendor‟s
source code. Luzerne County will receive Vendor‟s source code upon pre-
defined release conditions in order to maintain the Vendor‟s technology.


2.7 Warranty

The Vendor must warrant that for 365 days from the date of final acceptance (the
Warranty Period), the software‟s functionality will substantially conform to the
functional description for the software in the agreement executed between the
County with the selected Vendor, and that the digital or electronic media upon
which the software is distributed is free from defects in materials and
workmanship.




                                                                                      10
The Vendor will pass through to the County any and all warranties provided by
third parties on all third party products supplied under the agreement between
the County and the selected Vendor.

The Vendor will not be responsible for failure of the software to perform where
such failures result from use with software or hardware recommended by the
Vendor. The Vendor will not be required to warrant that the use of the software
will be uninterrupted and error free, that the software will meet the licensee‟s
needs, or that the software will operate in the hardware or system combinations
which may be selected by the County.

Any claim that the software fails to perform in accordance with the functional
description (a defect) must be made within the Warranty Period by providing
written notice during the Warranty Period to the selected Vendor together with an
explanation of the failure. The County‟s sole remedy for breach of warranty must
be the repair of the defect, or if such remedy cannot be delivered, a refund of that
portion of the license fees paid by the County.

The selected Vendor must warrant that services be performed in a workmanlike
manner in accordance with standards generally accepted in the industry. The
selected Vendor will remedy a non-conforming service, provided the County
notifies the Vendor within 30 days after the performance of the non-conforming
service. If the Vendor is unable to remedy the non-conforming service, the
Vendor will refund a portion of the purchase price directly related to the non-
conforming service.

All other warranties will be disclaimed.


2.8 Compliance with the Law

Vendors must adhere to all applicable federal, state, and local laws, ordinances,
and regulations while rendering service pursuant to any agreement entered into
as a result of this RFP.


2.9 Maintenance

Software maintenance and support must be available on a 24x7 basis, with
agency personnel having access to support technicians. Vendors will offer in
their bid document a yearly maintenance contract for software support to begin
upon acceptance of the system. Vendors certify they can provide a response to
the county within three hours drive time if needed.




                                                                                 11
2.10 Licenses, Permits, and Approvals

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 wireless connectivity, where
applicable.




                                                                                  12
Section 3 General Requirements

3.1 General System Specifications

   All equipment must be of current design and manufacture.
   All equipment must meet or exceed the applicable standards of the Institute of
    Electrical and Electronics Engineers, Electronic Industries Association and
    the Federal Communications Commission and will confirm to the specification
    of local network providers with respect to audio levels, frequencies, and
    control voltages to be impressed upon communications infrastructures.
   Equipment design and construction will be consistent with good engineering
    practice, and will be executed in a neat and professional manner.

3.2 Security Features

The proposed software must include the following security features:

   Encryption – The application software must operate under applicable CJIS
    security policy standards.VPN connections must utilize a minimum 128bit
    encrypted end to end connection.
   Passwords – The application software must only allow user access via
    entering of a valid user name and password. All successful and attempted
    log-ins must be recorded in the logging system.
   Active Directory Services - The software must support integration with
    Microsoft Active Directory Server for user administration.
   User Audit Trail – The application software must maintain a record of all user
    log-ins identified by unit and/or name, user name, date, time, Windows
    computer name, Windows domain name, and Windows user account name.
   Reports Audit Trail – the application software must keep logs of all reports
    viewed, printed, emailed, or modified. It must also keep logs of all records
    modified. Logs must be sorted in the operational SQL database and have the
    ability to be kept indefinitely, according to agency standard operation
    procedures.


3.3 Configuration Diagram

Vendors must include in their proposals applicable diagrams depicting the
application and systems architecture as well as configuration of the proposed
system.




                                                                                13
3.4 Training

Vendors must include in their proposals a description of the training provided with
the application software, including location, methodology, course outlines,
durations, prerequisites for training, and a listing of the training materials
provided. The training should use a combination of train-the-trainer
methodologies for user training and direct instructor led training for
administrators. Also first level technical training for a minimum of 5 people must
be included.

Vendors must specify costs for training in their pricing.


3.5 Support and Maintenance

Vendors must include in their proposal a description of the support and
maintenance service being offered which should include:
 Call Center Support
         - An Electronic Help Desk system: The ability for the County to
            submit and track the County‟s help desk service requests
            electronically
         - Remote technical support and telephone technical support for the
            County‟s designated System Administrator(s) or designee
         - The ability to generate all reports concerning prior support and or
            service request
         - Electronic reporting capabilities
         - Knowledge based search criteria, i.e. date ranges, key words, end
            user, etc.
 24x7 Support
         - 24x7 Remote monitoring of all critical components (hardware and
            software) for the County‟s CAD/RMS/Mobile Communications
            software solution.
         - 24x7, 30 minute response for Mission Critical issues. The County
            and the vendor will jointly develop definitions and criteria for critical
            and non-critical issues.
         - Service facility within 3 hours drive time for site response.
 Remote installation of software patches or updates need to be provided when
  deemed necessary and upon updates to the application
 The capability to provide the county with an updated electronic inventory of
  hardware and license counts at any given time. Vendor must have the ability
  to provide these services remotely.

Vendors must specify costs for annual support and maintenance in their pricing.




                                                                                   14
3.6 Project Work Plan

Vendors must include in their proposals a detailed work plan comprising of major
phases and tasks. Activities should be delineated within each task and a Gantt
or similar chart delineating the project schedule should be included.

Section 4 Application Software Requirements
The Vendor‟s proposed application software must meet the mandatory
requirements as set forth in the checklists provided in this section.

The intention is to purchase commercial-off-the-shelf (COTS) software, which
provides a high degree of functionality, reliability and performance capabilities.

When application components do not precisely meet the County‟s requirements,
the Vendor must state the costs and approximate timeline required to update
their solutions to meet the specifications.

The cost of all modifications to the Vendor‟s software must be included in the
proposal cost submitted. 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.


4.1 Functional Requirements Checklist Format

Vendors are required to complete and submit all 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 proposal and the RFP, in the contract with the Vendor. Acceptance of
the system will be contingent upon the Vendor delivering software that includes
all features promised by the Vendor.

Requirement Codes

The following codes are used by the County to indicate the relative importance of
each application module feature. The designated code for each requested
feature is listed in the REQ Code column.

M       This feature is considered mandatory and will be used to determine
        the extent to which a Vendor meets the minimum requirements


D       This feature is considered desirable and will be used in the overall
        evaluation of the Vendor‟ software

                                                                                     15
Availability Codes

The Vendor must use the following codes when completing the County‟s
application software checklists. For each feature listed, the Vendor must put one
of the following codes into the Avail column.

  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.


  NA      This feature is not available and there is no plan to provide it.




                                                                               16
4.2 Functional Requirements Matrixes

Vendors must complete the following matrixes for the proposed application
software. Apply an availability code from the list above for each feature named.


 FEATURE DESCRIPTION                               CODE       AVAIL      COST
 GENERAL ARCHITECTURE AND DESIGN
 Application Software must be fully developed
 using the Microsoft Visual Studio.NET
 Integrated Development Environment (IDE)            M
 with all native application code written in
 VB.NET or C#
 Proposed solution must support a relational
 database platform operating on the Microsoft
                                                     M
 SQL Server 2005/2008Enterprise Edition
 database engine
 Proposed solution must employ the extensive
 use of stored procedures within the database
 that directly leverage the benefits and             M
 performance enhancements available within
 the SQL Server Enterprise environment
 Proposed solution must use Microsoft
 ADO.NET to provide a modular and
 extensible data-access layer that isolates
 business logic functions from both the              M
 database and client application code using a
 business object framework in an n-tier
 implementation.
 Proposed solution must use Microsoft Smart
 Client technology to allow the client
 application to be „single-click‟ installed,         M
 centrally managed and automatically updated
 through Web services technology
 Proposed solution must leverage the .NET
 framework on the client device to provide a
 reliable, functional and feature-rich user          M
 interface that is both lightweight and tightly
 integrated with the operating system
 Proposed solution must support a service
 oriented architecture (SOA) using Microsoft
                                                     M
 Internet Information Services (IIS) and Web
 services (SOAP/XML) technology




                                                                                17
FEATURE DESCRIPTION                                      CODE         AVAIL   COST
Application Architecture



FEATURE DESCRIPTION                               CODE        AVAIL       COST
Systems Architecture
The Vendor‟s solution must be designed
around a Web Services integration model,
utilizing SOAP, XML, WSDL and UDDI
                                                     M
technologies to provide extensible, invokable
interfaces to both internal and external
resources throughout the system.
Solution must leverage .NET remoting
capabilities to manage version control,
                                                     M
software updates, and offline functional
elements.
Application software must perform network
detection and respond appropriately,
                                                     M
providing dynamic access only to available
resources.
Solution must support an Application Service
Provider (ASP) operational model by
                                                     M
providing single-click installation, automated
distribution and centralized administration.
 The Data Access Tier must provide mapping                M
 between the object oriented business logic, and the
 relational data in the database.
The Business Logic tier must include all business         M
rules, data validation, manipulation, processing, and
security implementation for the application.
 The data management tier, provided by the SQL            M
 Server RDBMS must be normalized to third normal
 form and may only be invoked by the software‟s
 business logic (via the data access tier).




                                                                                 18
FEATURE DESCRIPTION                                   CODE   AVAIL   COST
GENERAL FUNCTIONAL REQUIREMENTS
Application software must support unlimited
data interlinking by associating records to            M
existing records in other modules
Application software must provide ad hoc
queries to isolate specific functional reports, or     M
summary lists
Application software must provide a consistent
reporting tool for all functional, summary and         M
statistical reports
Application software must support printing,
exporting, or emailing of any generated report
                                                       M
in a variety of formats including .pdf, .rtf, .xls,
.tif, and .html files
Application software must provide extensive
logging of any access to or dissemination of           M
data
Application software must leverage a highly
configurable and dynamic role-based security           M
paradigm
Application software must provide national
address validation and correction capability
                                                       M
wherever addresses are entered in the
software
Application software must provide universal
mapping and instant lat/long geo-coding of any         M
location
Application software must leverage Master
Index validation (person, vehicle, location)           M
throughout the system
Application software must provide a
mechanism for merging master index records
                                                       M
where multiple entities are determined to be a
single person/vehicle/location
Master index merge function must allow a user
to select from all available existing attributes to    M
assign to the new master record
Application software must provide
comprehensive system searching of all Master           M
Indices, narrative and user involvement
Application software must support system-
wide Master Index alert assignment and                 M
management
Application software must support unlimited
                                                       M
photo imaging so that users can capture
                                                                            19
FEATURE DESCRIPTION                                CODE   AVAIL   COST
images of suspects, property, accident scenes,
and crime scenes and link them to a record
Solution must link mug shots to a person‟s
                                                    M
Master Index Record
Solution must provide color or black and white
                                                    M
print capabilities.
Solution must provide unlimited storage for
                                                    M
multiple images within all modules
Solution must capture images via video, digital
                                                    M
camera, or scanner
Solution must include spell check in all
modules that contain free-form, narrative or        M
memo text fields
Solution must provide universal barcode
scanning capability to scan drivers‟ licenses       M
and registrations in all applicable modules
Solution must provide universal barcode
scanning capability to scan printed reports for
                                                    M
the quick retrieval of records in all applicable
modules
All system pick-lists must be configurable          M
Systems Interfaces
Solution must support an integrated, bi-
directional interface with the CLEAN/NCIC
                                                    M
system hosted by the Pennsylvania State
Police
Solution must support a unidirectional (query)
interface into the U.S. Postal Service ZIP+4        M
address validation database
Solution must provide a unidirectional (query)
interface to Microsoft‟s MapPoint and/or Virtual
                                                    M
Earth global mapping systems at minimum
covering Eastern half of PA if not all of PA .
Solution must provide unidirectional (query)
                                                    M
interface into local ESRI GIS database(s)
Solution must include interagency data sharing
capabilities utilizing Web Services with any        M
other system provided by the Vendor
Solution must include the ability to extend
interagency data sharing capabilities to
systems provided by other Vendors utilizing         M
Web Services

Standard Reports
Solution must provide data collection and
                                                    M
output forms for the Pennsylvania State
                                                                         20
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
Department of Motor Vehicles Traffic Ticket.
Solution Must provide data collection and
output forms for the Commonwealth of                 M
Pennsylvania Department of Motor Vehicles.
Solution Must provide data collection and
output forms for the Pennsylvania Standard           M
Incident Report.
Solution must include standard reports for all
                                                     M
module functional records
Application software must provide standard
                                                     M
statistical reports
All functional reports must be bar coded for
                                                     M
record retrieval
Solution must provide reporting tool for
(Agency) to create its own reports as                M
necessary
Solution must provide interface to J-net             M
Solution must provide interface to NFIRS             M
APPLICATION MODULE REQUIREMENTS
Accident/Crash Module
Application must support scanning of drivers
                                                     M
licenses to populate driver fields
Application must support the population of
                                                     M
driver fields from master name index
Application must support the population of
                                                     M
driver fields from CLEAN query responses
Application must support scanning of vehicle
                                                     M
registrations to populate vehicle fields
Application must support the population of
                                                     M
vehicle fields from master vehicle index
Application must support the population of
                                                     M
vehicle fields from query responses
Application must automatically generate and
                                                     M
print the Pennsylvania accident form
Application must provide for unlimited storage
                                                     M
of digital photos with the Accident record
Solution must attach accident photos to the
                                                     M
accident record and be able to print
Application must provide an integrated
accident scene diagramming tool to populate          M
report
The software must keep a detailed audit log of
all activity associated with any Accident
record, including the creation, retrieval,           M
modification, deletion, printing or dissemination
of data
                                                                          21
FEATURE DESCRIPTION                                  CODE   AVAIL   COST
The application must provide ad hoc query and
                                                      M
reporting of Accident information
Aided/EMS Assist Case
Application must collect and track medical
                                                      M
aided cases
Application must allow a multiple person data
                                                      M
collection for aided cases
Application must collect and maintain taken by
                                                      M
data
Application must collect and maintain taken to
                                                      M
data
Application must collect and maintain
                                                      M
Illness/Injury data
The system must keep a detailed audit log of
all activity associated with any Aided Case
record, including the creation, retrieval,            M
modification, deletion, printing or dissemination
of data
Application must provide ad-hoc query and
                                                      M
reporting of aided case data
Alarm/Billing
Application must create and track Alarm
                                                      M
response calls
Application must generate warnings, billing
                                                      M
information, statistics
Application must validate addresses                   M
Application must create and maintain alarm
                                                      M
manufacture information
Application must create and maintain unlimited
                                                      M
contact names for each alarm location
Application must maintain alarm type data             M
Application must maintain alarm cause data            M
Application must allow configurable false alarm
threshold setting to automatically trigger billing    M
process
Application must create and maintain text of
                                                      M
alarm notification letter
Application must create and maintain alarm
                                                      M
company information
Application must create and maintain alarm
                                                      M
installer information
Application must automatically maintain alarm
                                                      M
activity data
Application must automatically create alarm
                                                      M
activity bills
Application must maintain all alarm financial         M
                                                                           22
FEATURE DESCRIPTION                                CODE   AVAIL   COST
account information to enforce agency
response policies in accordance with violation
fee payments
The system must keep a detailed audit log of
all activity associated with any Alarm record,
                                                    M
including the creation, retrieval, modification,
deletion, printing or dissemination of data
Application must provide ad hoc query and
                                                    M
reporting of alarm information




                                                                         23
FEATURE DESCRIPTION                               CODE   AVAIL   COST
Alert/Notification
Application must provide system-wide
configurable alerts for people, vehicles and
                                                   M
locations, wherever referenced throughout the
system
Arrest
Application must provide complete arrest
                                                   M
processing of subjects
Application must collect all NIBRS statistics
and apply business logic to ensure proper data     M
is collected and coded appropriately
Application must provide for address validation
and geo-coding of Arrest locations for crime       M
analysis functions
Application must provide specific DUI/DWI
related information sufficient to populate the
                                                   M
Pennsylvania Arrest and DUI/DWI Supporting
Deposition forms
Application must provide specific
fingerprint/Miranda related information
                                                   M
sufficient to populate the Pennsylvania Arrest
and fingerprint processing
Application must provide automated
                                                   M
generation of the Pennsylvania Arrest Report
Application must provide automated
generation of the Pennsylvania DUI/DWI             M
Supporting Deposition Form
Application must provide automated
generation of the Pennsylvania Adult State         M
Fingerprint Card
Application must provide automated
                                                   M
generation of the Federal FBI Fingerprint Card
System must provide the capability to generate
an automated arrest report from the Case
                                                   M
module and vise versa without having to
retype particulars
System must provide the capability to code all
arrest records for electronic IBR submission to    M
the Commonwealth of Pennsylvania.
System must provide the capability to
associate Arrest records with other Arrests, as
                                                   M
well as unlimited Cases, Events, Warrants,
Citations
The application must provide a mechanism for
                                                   M
classifying and sealing Arrests from view by
                                                                        24
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
users without appropriate permissions
The system must keep a detailed audit log of
all activity associated with any Arrest record,
                                                     M
including the creation, retrieval, modification,
deletion, printing or dissemination of data
System must provide the ability to Print arrest
forms, court information, and all other pertinent    M
reports
Application must provide the ability to print
                                                     M
crime and statistical reports
Application must provide ad hoc query and
                                                     M
reporting of Arrest information
Computer Aided Dispatch
Application must include a Computer Aided
Dispatch (CAD) module as an integrated
                                                     M
component of the core software. This module
may NOT be a separate interfaced application.
CAD must inherently share Event data with the
RMS modules. No duplication or passing of            M
Event data between systems is acceptable
The application must support complete
integration with the RMS modules supporting
                                                     M
all Master Index searching, address validation,
and user/personnel actions
The application must provide for the control,
receipt, management, and logging of all 911          M
phone calls.
The application must enable computer-
controlled emergency unit dispatching and            M
status updates.
The application must allow users to view real
                                                     M
time unit status and event status monitors.
The application must provide a shift
management/unit assignment tool to manage            M
response resources on a shift by shift basis
The application must maintain detailed unit
                                                     M
history
The application must provide the ability to
assign one or more available units to any
                                                     M
Event using drag and drop or command line
entry

The application must support dynamic
ascending and descending sorting of Event
                                                     M
and/or Unit listings by any displayed column
The application must provide configurable            M
                                                                          25
FEATURE DESCRIPTION                                CODE   AVAIL   COST
notification timers for any type of call and any
status type within each call type to allow
dispatchers to be reminded of status checks
The application must support visual and/or
audible notification of location alerts, timer
                                                    M
threshold expiration and specific Event
procedures
The application must provide a command line
help utility containing a list of available         M
commands
The application must support the ability to
perform response management functions via
                                                    M
mouse, command line or touch screen where
available
The application must provide AVL capabilities       M
The application must provide an integrated pin
mapping function to instantly generate a map
                                                    M
of all validated, or selected active call
locations
The application must provide a voiceless
dispatch functionality to allow automated
routing of Event and Unit Status data to the        M
vehicle where supported by a wireless
infrastructure
The application must allow users to update
their Event status and information from the         M
vehicle as applicable where supported
Case Reporting and Management
Application must allow for the complete
collection of data for Pennsylvania Incident        M
reporting.
Application must collect all NIBRS statistics
and apply business logic to ensure proper data      M
is collected and coded appropriately
System must provide the capability to code all
arrest records for electronic IBR submission to     M
the Commonwealth of Pennsylvania.
Application must provide for address validation
and geo-coding of Case locations for crime          M
analysis functions
Application must provide automated
                                                    M
generation of Pennsylvania Incident Report.
System must provide the capability to generate
an automated Case report from the Arrest
                                                    M
module and vise versa without having to
retype particulars
                                                                         26
FEATURE DESCRIPTION                                CODE   AVAIL   COST
System must provide the ability to assign
                                                    M
configurable solvability factors
System must provide the capability to
associate Case records with other Cases, as         M
well as unlimited links to any main module
The Case module must collect subject/suspect
                                                    M
information and apply to Master Person Index
The Case Module must support the unlimited
collection of Charges associated with a case        M
as selected from the Law file library
The system must include a comprehensive
database capable of containing all applicable       M
laws of the Commonwealth of Pennsylvania.
The Case module must support the unlimited
collection of involved officers as related to a     M
Case
The Case module must support the unlimited
collection of involved persons as related to a      M
Case
The Case module must support the unlimited
collection of involved property as related to a     M
Case
The Case module must support the unlimited
collection of involved weapons as related to a      M
Case
The Case module must support the unlimited
collection of involved vehicles as related to a     M
Case
The Case module must support the unlimited
                                                    M
collection of image/photos as related to a Case
The Case module must support the unlimited
collection of witness/victim statements as          M
related to a Case
The Case module must support the unlimited
collection of detective follow-up/narrative         M
records as related to a Case


The application must provide a mechanism for
classifying and sealing cases from view by
                                                    M
users without appropriate permissions
The system must keep a detailed audit log of
all activity associated with any Case record,
                                                    M
including the creation, retrieval, modification,
deletion, printing or dissemination of data.
Application must provide ad hoc query and           M
                                                                         27
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
reporting of Case information.
Citation Module
The application must allow users to enter
summons, navigation tickets, and appearance          M
tickets in both online and offline mode.
The system must support the generation of
citation numbers, storage of pick-list values,
                                                     M
and law file updates for use on the client
device during periods of disconnected use
Any citations generated while disconnected
must immediately and automatically be
                                                     M
transferred to the database upon reconnection
to the network
The system must support the importing of
parking tickets from a handheld parking ticket       M
system
Application must support scanning of drivers
                                                     M
licenses to populate driver fields
Application must support the population of
                                                     M
driver fields from master name index
Application must support the population of
                                                     M
driver fields from CLEAN query responses
Application must support scanning of vehicle
                                                     M
registrations to populate vehicle fields
Application must support the population of
                                                     M
vehicle fields from master vehicle index
Application must support the population of
                                                     M
vehicle fields from CLEAN query responses
Application must automatically generate and
                                                     M
print the Pennsylvania Traffic Ticket
Application must provide for unlimited storage
                                                     M
of digital photos with the Citation record
Solution must attach accident photos to the
                                                     M
Citation record
Application must provide for pre-filling of
location, officer and court information for          M
population on the ticket
Application must provide for the searching of
the entire Pennsylvania Law file to select           M
violations and append to the citation
The application must allow the assignment of
default Court of appearance along with the
                                                     M
automated management and assignment of
court dates
The system must keep a detailed audit log of
                                                     M
all activity associated with any Citation record,
                                                                          28
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
including the creation, retrieval, modification,
deletion, printing or dissemination of data
Application must provide ad hoc query and
                                                     M
reporting of Citation information
Diary/BOLO
The application must provide a system-wide
notification mechanism for broadcasting BOLO
                                                     M
information, or specific shift, geographical or
time sensitive messages to users
The system must keep a detailed audit log of
all activity associated with any Diary record,
                                                     M
including the creation, retrieval, modification,
deletion, printing or dissemination of data
Application must provide ad hoc query and
                                                     M
reporting of Diary information
Event
The application must capture and log all
                                                     M
Event/Incident related data as described below
The Event module must collect specific
                                                     M
information related to caller and caller location
The Event module must collect specific
information related to event/incident location
                                                     M
which may either be the same or different than
the caller location at the discretion of the user
The Event module must collect
                                                     M
Date/Timestamps for all transactions
The Event module must support the unlimited
collection of Narrative, with spell check            M
functionality
The Event module must support the unlimited
                                                     M
collection of Involved Persons information
The Event module must support the unlimited
                                                     M
collection of Involved Vehicle information

The Event module must support the unlimited
collection of Involved Property information          M
The Event module must support the
generation of Alarm Events in accordance with        M
Alarm/Billing module requirements above
The system must support the ability to search
master indices for location, person, vehicle,        M
etc. information and append as necessary.
The system must support nationwide validation
of addresses for any location or subject
                                                     M
address associated to a call regardless of
whether the address originated from E911,
                                                                          29
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
master index search, or manual entry
System must provide the capability to
associate Event records with other Events, as
                                                     M
well as unlimited Arrests, Cases, Warrants,
Citations
The system must keep a detailed audit log of
all activity associated with any Event record,
                                                     M
including the creation, retrieval, modification,
deletion, printing or dissemination of data
Application must provide ad hoc query and
                                                     M
reporting of Event information
Field Interview
The application must allow users to collect
                                                     M
data and generate Field Interview Reports
The system must support address validation
                                                     M
and geo-coding of location of Field Interview
The Field Interview module must support the
                                                     M
unlimited collection of involved persons data
The Field Interview module must support the
                                                     M
unlimited collection of involved vehicles data
The Field Interview module must support the
unlimited collection of images or photographs        M
as associated to a field interview record
The Field Interview module must support the
                                                     M
unlimited collection spell-checked narrative
The system must provide the ability to link
                                                     M
Field Interview records with Events
The system must keep a detailed audit log of
all activity associated with any Field Interview
record, including the creation, retrieval,           M
modification, deletion, printing or dissemination
of data
Application must provide ad hoc query and
                                                     M
reporting of Field Interview information
Impounds
The application must provide an Impound
module to capture and store all vehicle              M
impound and towing information
The system must support address validation
                                                     M
and geo-coding of location of impound
The Impound module must capture pertinent
vehicle, owner and operator information              M
pertaining to an impound record
The Impound module must capture and
maintain detailed vehicle inventory and              M
condition data
                                                                          30
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
The Impound module must capture towing
information including tow company, time, date        M
and location of impounded vehicle
The Impound module must support the
unlimited collection of images or photographs        M
as associated to a Impound record
The Impound module must support the
                                                     M
unlimited collection spell-checked narrative
The system must provide the ability to link
Impound records with other Impounds as well
                                                     M
as Accidents, Arrests, Events, Cases, as
necessary
The Impound module must provide the ability
to capture and maintain detailed release
                                                     M
information including to whom the vehicle was
released, and authorizing officer
The System must provide the capability to
generate a bar-coded impound letter to be            M
sent to the owner of the vehicle
The system must keep a detailed audit log of
all activity associated with any Impound
record, including the creation, retrieval,           M
modification, deletion, printing or dissemination
of data
Application must provide ad hoc query and
                                                     M
reporting of Impound information
Interagency Data Sharing
The system must provide an integrated
module to support the sharing of data with
                                                     M
other systems via an SOA Web Services
based interface
The Interagency Data Sharing module must
inherently support the sharing of person data        M
with other systems provided by the Vendor
The Interagency Data Sharing module must
optionally support the sharing of person data
                                                     M
with systems provided by other 3rd party
vendors as applicable
The Interagency Data Sharing module allow
users to select which systems they wish to           M
query and enter variable search parameters
The Interagency Data Sharing module must
provide a dynamic, real time display of status
                                                     M
of each external query, and alert the user
immediately to system unavailability
The Interagency Data Sharing module must             M
                                                                          31
FEATURE DESCRIPTION                                CODE   AVAIL   COST
return with a list of all records meeting the
search criteria and allow the user to select
which person(s) they wish to gather details on
The Interagency Data Sharing module must
provide comprehensive rap sheet information
                                                    M
on the selected individual(s) in accordance
with external systems security paradigm.
The Interagency Data Sharing module must
allow the user to generate a detailed rap sheet
                                                    M
report including all information retrieved from
selected external system(s)
Orders of Protection
The system must allow the capture and
recording of court generated orders of              M
protection (OOP)
The OOP module must provide detailed
information on Court of issue and issuing
                                                    M
Judge, as well as order date and time and
effective from, and to dates
The OOP module must provide detailed
respondent information as integrated with the       M
Master Person Index
The OOP module must allow for the capture of
information on unlimited petitioners as             M
pertaining to a single order
The system must provide the ability to link
OOP records with Events, Cases or Arrests as        M
applicable
The OOP module must provide a configurable
OOP type list allowing the agency to record         M
specific mandates of protection orders
The system must generate alerts to users
throughout the system when a flagged OOP            M
respondent is queried from another module
The system must keep a detailed audit log of
all activity associated with any OOP record,
                                                    M
including the creation, retrieval, modification,
deletion, printing or dissemination of data
Application must provide ad hoc query and
                                                    M
reporting of OOP information
Personnel
The system must contain an integrated
Personnel module for tracking all attributes of     M
employees of the agency
The Personnel module must integrate with the
                                                    M
role-based security paradigm to tightly couple
                                                                         32
FEATURE DESCRIPTION                                CODE   AVAIL   COST
user accounts to Personnel records
The Personnel module must provide the ability
to record and attach a digital signature file to    M
each employee‟s record
The Personnel module must provide the ability
to track all employee commendations issued          M
by the agency
The Personnel module must provide the ability
to track detailed and unlimited employee            M
contact information
The Personnel module must provide the ability
to track all employee assignments and
                                                    M
geographical postings within the agency for
the extent of their career
The Personnel module must provide the ability
to track all employee previous employment           M
records
The Personnel module must provide the ability
to track all employee equipment issued by           M
type, make model, and dates of issue/return
The Personnel module must provide the ability
to track all employee medical information           M
including blood type and allergies
The Personnel module must provide the ability
                                                    M
to track all employee military service records
The Personnel module must provide the ability
to track all employee licenses held and             M
effective dates
The Personnel module must provide the ability
to track all employee skills and education
including certifications, formal education,         M
informal skills and languages spoken, read
and written
The Personnel module must provide the ability
to track all employee training records including    M
class dates, certification earned and type
The Personnel module must provide the ability
to track unlimited emergency contact                M
information for every employee
The System must provide the capability to
secure confidential Personnel information from
                                                    M
view by any user/group within the system as
necessary
The System must provide the ability to digitally
                                                    M
store and use a Personnel members signature
The system must keep a detailed audit log of        M
                                                                         33
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
all activity associated with any Personnel
record, including the creation, retrieval,
modification, deletion, printing or dissemination
of data
Application must provide ad hoc query and
                                                     M
reporting of Personnel information
Property
The System must support an integrated
Property and Evidence management system
for the complete and accurate impound,
                                                     M
storage, processing and chain of custody
tracking for any physical item related to law
enforcement activity
The Property module must support complete
barcode integration using uniquely coded
                                                     M
labels which are generated and maintained by
the system
Property items must be able to be categorized
and tracked individually or as a component of        M
a larger group of items
All Property items must support the ability to
be inherently associated with other Property
                                                     M
records, as well as any Event, Case, Arrest,
etc. record type
The System must provide the capability to
utilize the bi-directional CLEAN interface to
                                                     M
enter or search stolen property through the
CLEAN system
System must provide the ability to request and
track lab analysis of materials through the          M
integrated Case Module
The Property module must support the
unlimited collection of image/photos as related      M
to an item
The Property module must support the
unlimited entry of narrative text as related to      M
an item
The Property module must support the
complete management and configuration of all
pick-list values such as type, status, location,     M
etc. as determined by the systems
administrator
The System must provide the ability to print
                                                     M
bar-coded property invoices and image reports
The System must provide the ability to
                                                     M
generate form letters indicating status of
                                                                          34
FEATURE DESCRIPTION                                 CODE   AVAIL   COST
property to owners
The System must fully manage the release of
property including time/date and reason for
                                                     M
release, as well as owner information and
releasing authority
The System must maintain a complete audit
trail for each property item entered into the
system indicating it‟s classification as
evidence, and any movement of the item,              M
including use in court, processing in labs,
transfer of facilities or storage locations and
final disposition
The system must also keep a detailed audit
log of any activity associated with Property
records including the creation, retrieval,           M
modification, deletion, printing or dissemination
of data
Application must provide ad hoc query and
                                                     M
reporting of Property invoice information
Premise Check
The System must support an integrated
Premise module for the automated directed            M
patrol of uninhabited homes and or businesses
The Premise Module must provide address
validation and the ability to geo-code any           M
location
The Premise module must support the
unlimited collection of Contact Person
                                                     M
information including integration with Master
Persons Index
The Premise Module must capture and
maintain a comprehensive list of all activity        M
performed at the specified location
The Premise Module must provide the ability
to associate unlimited Event and or Alarm            M
records to any record as applicable
The system must keep a detailed audit log of
all activity associated with any Premise record,
                                                     M
including the creation, retrieval, modification,
deletion, printing or dissemination of data
Application must provide ad hoc query and
                                                     M
reporting of Premise information
Warrants
The System must provide an integrated
Warrant Module for the management and                M
tracking of all Warrant documents as issued by
                                                                          35
FEATURE DESCRIPTION                                   CODE   AVAIL   COST
an authorized Court of Law
The Warrant Module must provide integration
with all Master Indices including the ability to
                                                       M
search Pennsylvania Law file for selecting
associated charges
Warrant Status and Type pick-lists must be
completely configurable by Agency                      M
Administrators
The Warrant module must collect detailed
subject information including mug-shot data as         M
integrated into the record
Warrant Subject address entry must support
National address validation and mapping                M
functionality to assist in the location of subjects
The Warrant module must collect detailed
information on issuing Court of Law, Judge             M
and Bail information as applicable
The Warrant Module must provide the ability to
associate unlimited Event, Case, Arrest, etc.          M
records to any Warrant record as applicable
The Warrant module must support the
generation of bar-coded form/warning letters,          M
Criminal Summons‟ and Warrants of Arrest
The system must allow court personnel
specific access to the RMS to issue and
                                                       M
manage warrants without providing full access
to the System
The System must support automated alerts in
all applicable modules to users when a subject         M
is queried in the system
The system must keep a detailed audit log of
all activity associated with any Warrant record,
                                                       M
including the creation, retrieval, modification,
deletion, printing or dissemination of data
Application must provide ad hoc query and
                                                       M
reporting of Warrant information




                                                                            36
Section 5 Proposal Format and Guidelines
At a minimum, a Vendor‟s proposal must include the following:

Cover Letter
         - Sign by an official of the organization authorized to negotiate for the
             company and so stated.
         - Indicate the timeframe that the proposal and pricing are valid.
         - Indicate RFP Number and Name

Table of Contents

Section I Executive Summary

Section II Point-by-Point Response to RFP Sections

Section III Pricing

Section IV Detailed Functional Description of Proposed Application
Software

Section V – Project Team
         - Name and describe project roles for project team, including
            subcontractors
         - Provide resumes for key personnel
         - Provide organization chart for project team, including
            subcontractors

Section VI – References
         - Provide at least three reference projects that are completed.
         - Provide scope of project; start and end dates; application software
             provided; name, title, address, telephone, and email of customer
             reference.

Appendix A – Minimum Requirements for Computer Hardware

Appendix B – Non-Collusion Affidavit




                                                                               37
Appendix A Hardware/Software Requirements
The vendor must supply the minimum and recommended requirements for
computer hardware, software, and peripherals, to include the following:


    Server: 2 Redundant
    Server Software
    Workstation Requirements
         1. 911 Center- 6 call takers, 1 supervisor position, 12 dispatch positions, 2
            training positions. All Positions must be full function if needed.
         2. 911 Back-up facility- 4 CAD positions and 3 Call taker positions.
         3. 55 Police stations/ County agencies to be determined
         4. Police vehicles- 55 Mobile data solutions
         5. 111 Fire/EMS work stations.
    Required Hardware
    Other Hardware
    Other Software
    Failover, Redundancy Software/Hardware Systems




                                                                                   38
Appendix B

         NON-COLLUSION AFFIDAVIT

                         Luzerne County Public Safety
                         Countywide RMS/CAD Project
                             Request for Proposal
                                October, 2008




By submission of this proposal, The vendor certifies that:

   a) This proposal has been submitted, independently, without collusion with
      other vendors or with any competitor or potential competitor.
   b) This proposal has not been knowingly disclosed and will not be knowingly
      disclosed, prior to the opening of proposals for this project, to any other
      vendor, competitor or potential competitor.
   c) No attempt has been, or will be made to induce any other person,
      partnership or corporation to submit or not to submit a proposal.
   d) The person signing this affidavit certifies that he has fully informed himself
      regarding the accuracy of the statements contained in this certification,
      and, under the penalties of perjury, affirms the truth thereof, such
      penalties being applicable to the vendor as well as to the person signing in
      its behalf.



                           SIGNED _____________________________

                           PRINTED_____________________________

                           TITLE       _____________________________

             COMPANY NAME              _____________________________




                                                                                 39

				
DOCUMENT INFO
xumiaomaio xumiaomaio http://
About