Docstoc

CONFIRE RFP

Document Sample
CONFIRE RFP Powered By Docstoc
					                         REQUEST FOR PROPOSALS
            The Consolidated Fire Agencies of the East Valley (CONFIRE)
                  request proposals from qualified vendors for an

                               Integrated CAD System

CONFIRE understands that respondents may have questions that cannot be answered
by the information contained within this RFP. All questions should be submitted by
email by 4:30 p.m. on June 27, 2007 to:

                                     Rick Britt
                         CONFIRE Communications Director
                               rbritt@confire.org

                          PRE-PROPOSAL CONFERENCE

  CONFIRE will conduct a Pre-Proposal Conference & Site Tour on June 13, 2007 at
   10:00 a.m. at Fire Station 203 located at 1550 N. Ayala, Rialto, CA 92376. A walk
through of CONFIRE‘s dispatch center located at 1743 W. Miro Way, Rialto, CA 92376
will occur immediately after the Pre-Proposal Conference. Prospective contractors will
    be given the opportunity to ask questions, receive clarification, or simply obtain a
            greater understanding of the project prior to proposal submission.

                        PROPOSAL SUBMITTAL DEADLINE:
                          Date: July 18, 2007 at 4:00 P.M.

                          All proposals must be delivered to:

                                   Jenny Thompson
                                     CONFIRE JPA
                                  1743 W. Miro Way
                                Rialto, CA 92376-8630

              CONFIRE reserves the right to reject any or all proposals.

 NO LATE PROPOSALS WILL BE ACCEPTED FOR ANY REASON WHATSOEVER

 ENVELOPE MUST STATE CLEARLY THAT THE ENCLOSED PROPOSAL IS FOR
                CONFIRE INTEGRATED CAD SYSTEM
                      Due Date: July 18, 2007
Request for Proposal for
Integrated CAD System



       May 17, 2007
                            Consolidated Fire Agencies of the East Valley
                                             (CONFIRE)
                                      Integrated CAD System
                                       Request for Proposals


                                                      Table of Contents


Section 1 Executive Summary ...................................................................................... 1
         1.1     Overview ................................................................................................................... 1
         1.2     Goals and Objectives ................................................................................................. 1
         1.3     Background Information ........................................................................................... 2
         1.4     Desired System .......................................................................................................... 2
Section 2 Scope of Services ......................................................................................... 3
         2.1     Project Overview ...................................................................................................... 3
         2.2     Software Systems ..................................................................................................... 3
         2.3     Interfaces .................................................................................................................. 5
         2.4     Hardware and System Software ............................................................................... 6
         2.5     Data Conversion/Migration/Transformation ............................................................ 6
         2.6     Implementation and Support .................................................................................... 6
         2.7     Site Preparation ........................................................................................................ 6
         2.8     Project Management ................................................................................................. 7
         2.9     Testing ...................................................................................................................... 8
         2.10    Documentation ......................................................................................................... 8
         2.11    Acceptance Testing .................................................................................................. 8
         2.12    Implementation Warranty......................................................................................... 8
         2.13    Post-Implementation Support ................................................................................... 8
         2.14    CONFIRE Support and Staffing............................................................................... 9
         2.15    Account Manager ..................................................................................................... 9
         2.16    Support and Maintenance ......................................................................................... 9
         2.17    Training .................................................................................................................... 9
         2.18    CONFIRE’s Responsibilities ................................................................................. 10
Section 3 Proposal Submission ................................................................................... 12
         3.1     Submission Timeline & Events .............................................................................. 12
         3.2     Proposal Due Date: ................................................................................................. 12
         3.3     Pre-Proposal Conference and Site Tour ................................................................. 12
         3.4     Proposal Submission ............................................................................................... 13
         3.5     General Format ....................................................................................................... 13
         3.6     Transmittal Letter ................................................................................................... 14
         3.7     Proof of Authority .................................................................................................. 14
         3.8     Proposer History ..................................................................................................... 14
         3.9     Clarifications and Interpretations ............................................................................. 15
         3.10    Contact with County Employees and Others ......................................................... 16
         3.11 Exceptions to the RFP ............................................................................................ 16
         3.12 Proposal Term and Validity ..................................................................................... 16
Section 4 General Conditions ...................................................................................... 17
         4.1      Purchase Alternatives ............................................................................................. 17
         4.2      Current Manufacture: ............................................................................................. 17
         4.3      Site License Option ................................................................................................ 17
         4.4      Current Version ...................................................................................................... 17
         4.5      Prior Use ................................................................................................................. 17
         4.6      Availability of Funds .............................................................................................. 17
         4.7      Requirement to Meet All Proposal Provisions: ...................................................... 17
         4.8      Proposal Retention and Award ............................................................................... 18
         4.9      Revision to the RFP................................................................................................. 18
         4.10     Use, Disclosure and Confidentiality ......................................................................... 18
         4.11     Certificate of Insurance .......................................................................................... 18
         4.12     Errors in Proposals .................................................................................................. 18
         4.13     Proposer Expenses .................................................................................................. 19
         4.14     Post-Proposal Presentations .................................................................................... 19
         4.15     Multiple Awards ...................................................................................................... 19
         4.16     Contract Negotiations.............................................................................................. 19
         4.17     No Obligation to Proceed ....................................................................................... 19
         4.18     Proposal Withdrawal and Modification .................................................................... 20
         4.19     Purchase Orders ...................................................................................................... 20
         4.20     Subcontractors......................................................................................................... 20
         4.21     Taxes ....................................................................................................................... 20
         4.22     Sample Contract ...................................................................................................... 20
         4.23     Licenses and Permits ............................................................................................... 21
         4.24     Use of CONFIRE Name ......................................................................................... 21
         4.25     Incorporated by Reference ...................................................................................... 21
         4.26     RFP Not Contractual............................................................................................... 21
         4.27     Patent Fees, Patent, Copyright, Trade Secret and Trademark Fees ........................... 21
Section 5 Supplemental Exhibits ................................................................................. 22
         Exhibit 1 - Volumes ........................................................................................................... 23
         Exhibit 2 - Service Area Overview ..................................................................................... 24
         Exhibit 3 - Fire Demand Zone Overview ........................................................................... 25
         Exhibit 4 - CONFIRE JPA Organization Chart ................................................................. 26
         Exhibit 5 - Current CAD System and Network Overview .................................................. 28
Section 6 Proposer Questionnaire Introduction ........................................................... 29
Section 7 Checklist and Proposer Services ................................................................. 30
         7.1      Checklist .................................................................................................................. 30
         7.2      Exceptions............................................................................................................... 30
Section 8 Proposer General Information ..................................................................... 31
        8.1      Contractor ............................................................................................................... 31
        8.2      Company Information ............................................................................................. 32
Section 9 Proposer References .................................................................................. 33
Section 10 Proposal/Contract Information ..................................................................... 35
        10.1     Authorized Negotiator............................................................................................. 35
        10.2     Proposal Validity ..................................................................................................... 35
        10.3     Contract Exceptions ................................................................................................ 35
Section 11 Hardware Requirements.............................................................................. 36
        11.1     Operating System .................................................................................................... 36
        11.2     System Diagram....................................................................................................... 36
        11.3     Proposed Server Configuration ................................................................................ 37
        11.4     Technical Brochures ................................................................................................ 37
        11.5     Server Capacity ........................................................................................................ 37
        11.6     Server Upgrades and Expansion .............................................................................. 38
        11.7     Concurrent Operation ............................................................................................. 38
        11.8     Reliability ................................................................................................................. 39
        11.9     Redundancy/Failover and Restore ........................................................................... 40
        11.10    System Backup ........................................................................................................ 40
        11.11    Power and Environmental ....................................................................................... 41
        11.12    Hardware Installation and Site Preparation .............................................................. 41
        11.13    Strategic Direction ................................................................................................... 42
Section 12 Mobile Data Computers ............................................................................... 43
        12.1 MDC Configuration ............................................................................................... 43
Section 13 System Software Requirements .................................................................. 45
        13.1 System Software ...................................................................................................... 45
        13.2 Security Features .................................................................................................... 46
        13.3 System Administration ............................................................................................. 47
Section 14 Proposed Application Software ................................................................... 48
        14.1     Overview ................................................................................................................. 48
        14.2     CAD Functionality .................................................................................................. 50
        14.3     Source Code ............................................................................................................ 50
        14.4     Confirmation of Requirements ................................................................................ 51
        14.5     Process Analysis ...................................................................................................... 51
        14.6     General Documentation .......................................................................................... 51
        14.7     Hardware Documentation ....................................................................................... 52
        14.8     Software Documentation ......................................................................................... 53
        14.9     System Implementation Documentation .................................................................. 53
        14.10    Application Upgrades .............................................................................................. 53
Section 15 Performance and System Acceptance ........................................................ 55
        15.1     Acceptance Periods ................................................................................................. 55
        15.2    Test Plan ................................................................................................................. 56
        15.3    Testing..................................................................................................................... 57
        15.4    Ongoing System Performance ................................................................................. 59
        15.5    System Response Times........................................................................................... 60
        15.6    System Availability ................................................................................................... 60
Section 16 Implementation and Project Management ................................................... 62
        16.1    Status Reporting ...................................................................................................... 62
        16.2    Project Management and Implementation Services .................................................. 62
        16.3    Recommended Implementation Schedule ................................................................ 63
        16.4    Time and Level of Support ...................................................................................... 63
        16.5    Support Personnel ................................................................................................... 63
        16.6    Resumes .................................................................................................................. 63
        16.7    Post-Implementation Evaluation ............................................................................. 64
        16.8    Additional Items ...................................................................................................... 64
        16.9    Implementation Requirements ................................................................................. 64
Section 17 Training Requirements ................................................................................ 65
        17.1    Overview ................................................................................................................. 65
        17.2    Training Plan ........................................................................................................... 65
        17.3    Training Documentation ......................................................................................... 66
        17.4    Training Simulation ................................................................................................. 66
Section 18 Warranty and Maintenance Requirements .................................................. 68
        18.1    General Maintenance Provisions.............................................................................. 68
        18.2    General Warranty Provisions ................................................................................... 70
        18.3    Moves, Changes and Additions ................................................................................ 71
Section 19 Experience and Implementation Approach .................................................. 74
        19.1    GIS/Geofile Approach............................................................................................ 74
        19.2    Mobile Data............................................................................................................. 75
        19.3    Report Generation/Data Output ............................................................................. 75
        19.4    Electronic Mail ........................................................................................................ 76
        19.5    Electronic Messaging ............................................................................................... 76
        19.6    Incident Management .............................................................................................. 77
        19.7    Data Conversion...................................................................................................... 77
Section 20 Interface Development Experience ............................................................. 78
        20.1    General Interface Experience/Approach ................................................................. 78
Section 21 Proposer Cost Summary ............................................................................. 82
        21.1    Hardware Costs ....................................................................................................... 82
        21.2    System Software Costs ............................................................................................. 82
        21.3    Application Software Costs...................................................................................... 83
        21.4    Implementation Costs ............................................................................................. 84
        21.5    Optional Costs ........................................................................................................ 84
21.6 Hourly Rates............................................................................................................ 85
21.7 Leasing .................................................................................................................... 85
21.8 Licensing ................................................................................................................. 85
21.9 Total One Time Costs ............................................................................................. 85
21.10 Recurring Costs Summary ....................................................................................... 86
21.11 Payment Schedule .................................................................................................... 86
Appendix A - Functional Requirements ........................................................................... 87
Appendix B - Sample Queries/Reports ............................................................................. 88
Appendix C - Public Safety Systems Agreement ............................................................. 90
Appendix D - Definitions.................................................................................................. 91
Attachment 1 - Escrow Agreement ................................................................................... 95
Attachment 2 - Correspondence........................................................................................ 96
Attachment 3 - Hardware and Network Configuration Specifications ............................. 97
Attachment 4 - Services Detail ......................................................................................... 98
Attachment 5 - Computer Software Support Agreement .................................................. 99
Attachment 6 - Preliminary Project Schedule and Personnel ......................................... 100
Attachment 7 - Preliminary Test Plan ............................................................................. 101
Attachment 8 - Preliminary Implementation Plan .......................................................... 102
Attachment 9 - Computer Hardware Maintenance Agreement ...................................... 103
                                          Request for Proposal for Integrated CAD System


Section 1         Executive Summary

1.1    Overview
The Consolidated Fire Agencies of the East Valley (CONFIRE) request a proposal for
the design and implementation of an integrated CAD System to service its five member
fire agencies and two additional contract agencies.

A detailed description of CONFIRE‘s existing CAD System is included in Section 5 -
Supplemental Exhibits. This RFP describes CONFIRE‘s overall goals and objectives for
the new CAD System and outlines the format for the desired response. While
CONFIRE has outlined the functional requirements for the new System, it does not
desire to constrain the ability of Proposers to provide the solution that will best meet the
needs of end users. Proposers are encouraged to provide their most appropriate
solution that will meet CONFIRE‘s goals and objectives as represented in this RFP.

1.2    Goals and Objectives
CONFIRE‘s current CAD System is nearing obsolescence and needs to be replaced
with a modern System that can support effective public safety call taking and
dispatching services.

Due to the importance and complexity of this project, CONFIRE is seeking a highly
experienced CAD System provider with proven experience and success in working with
public safety agencies to achieve their System objectives.

Through this procurement, CONFIRE hopes to achieve the following objectives:

      1. Improve first responder and public safety.
      2. Improve command and control at incidents.
      3. Maximize efficient deployment of fire personnel.
      4. Enhance reliability of core public safety systems.
      5. Increase overall usability, user-friendliness and flexibility of CAD.
      6. Increase the availability of timely and consistent data necessary to effectively
         manage public safety resources.
      7. Enhance system integration to increase efficient use of data by end users and
         management.
      8. Receive comprehensive training on the new systems.
      9. Increase staff access to information, subject to security level.

                                                                                 May 17, 2007
                                                                                      Page 1
                                         Request for Proposal for Integrated CAD System

      10. Minimize disruption to current operations.
      11. Deploy modular and scalable technology.
      12. Develop a service-oriented relationship with a proven CAD system provider.

1.3    Background Information
Section 5 (Supplemental Exhibits) to this RFP provides the CONFIRE JPA organization
chart, as well as anticipated transaction and user volumes for the CAD System and its
component applications, including the Mobile Data Computing System. It also
describes the existing CAD System, and provides an overview of CONFIRE services,
Fire Demand Zones and the CONFIRE 911 System and network.

1.4    Desired System
CONFIRE is seeking a turnkey replacement of the current CAD System with fully
integrated EMD priority dispatching, mobile data computers, message switching and
external System interfaces. All System components provided should be highly reliable
and fully-integrated, thereby eliminating the need for redundant data entry. All
interfaces to ancillary or external systems should also be designed and developed to
eliminate redundant data entry.




                                                                          May 17, 2007
                                                                               Page 2
                                        Request for Proposal for Integrated CAD System


Section 2        Scope of Services

2.1 Project Overview
CONFIRE intends to contract for perpetual and non-exclusive software licenses,
hardware, annual maintenance and the services necessary to implement a state-of-the-
art turnkey CAD System with fully integrated EMD priority dispatching, mobile data
computing, message switch and external System interfaces. It is CONFIRE‘s intent to
procure the best combination of software, hardware and services at the most
reasonable cost. The product provided must meet all of the functionality requirements
outlined in the proposal, as well as the design, implementation, installation, training and
software support requirements.

2.2 Software Systems
The Proposer must provide a software solution to address CAD and CAD-related
information system needs. CONFIRE expects the Proposer to provide all of the
software necessary for a fully functioning System at the time of implementation. All
proposed software versions must be generally available and deployed in a live
environment from the software manufacturer on or before the proposal deadline. The
module version for each module proposed must be identified within the Proposer‘s
responses. No mid-implementation upgrades will be considered or allowed by
CONFIRE during this project.

All System Components provided should be highly reliable and fully-integrated, thereby
eliminating the need for redundant data entry. All interfaces to ancillary or external
Systems should also be designed and developed to eliminate redundant data entry.

2.2.1 Computer-Aided Dispatch System: Replace the current PRC CAD System
      with an on-site, comprehensive CAD System that is fully-integrated with required
      interfaces.

       The CAD System should be highly reliable with the Proposer providing redundant
       System solutions (e.g., back-up server, additional off-site server, hot-standby).
       The proposed CAD should be capable of supporting a variety of fire-specific
       functions such as pre-fire planning, alarm level recommendation, premise history
       and call proximity dispatching.

       All data entry screens should support the pre-population of all available data
       based on master file information (name, vehicle, location, etc.). The replacement
       CAD System should be user-friendly by providing integrated windows
       functionality, as well as allowing for agency-defined user access to various data
       sources. In addition, the System should eliminate the need for redundant data
       entry, provide the ability to conduct real time integrated mapping for all


                                                                             May 17, 2007
                                                                                  Page 3
                                       Request for Proposal for Integrated CAD System

      dispatchers and allow for interconnections between other System components
      (e.g., RMS, E911, NetClock).

2.2.2 Mobile Data Computer System: Implement a new mobile computer System
      that integrates mobile data software with mobile hardware and all necessary
      peripherals with a comprehensive, fully-integrated mobile data solution that will
      provide field access to critical CAD data. The Mobile Data Computers will be
      required for all command level vehicles with an option to include mobile data
      computers for all vehicles. Proposers should propose all software and hardware
      to enable mobile data communications, including:

             Electronic dispatching between CONFIRE and member agency mobile
              computers
             Electronic messaging between mobile devices and other member agency
              workstations
             CAD query and reporting from MDCs
             Other functions that the Proposer considers appropriate for the MDC
              operation

2.2.3 Message Switching System: CONFIRE anticipates implementing a message
      switch system that functions as a message router and as an application
      management system. As a message router, the message switch evaluates
      messages (input data) and determines the appropriate output transmission path.
      As an application management system, it provides capabilities such as text
      messaging, unit identification, message formatting, and a single point of entry for
      queries to various local databases (CAD, MDC, etc.). The Proposer is expected
      to provide message switching software and hardware that will allow access by all
      mobile and fixed workstations to all System Components. Message switching
      functions may be integrated with the CAD System or other hardware and
      software Systems.

2.2.4 GIS/Mapping: The County currently utilizes an ESRI ArcGIS (v9.2) GIS that is
      utilized by the management and staff in the Communications Center. CONFIRE
      staff manually input information from the GIS into the CAD geofile each time
      there is a change in the GIS map layers. In addition to the street centerline layer
      that is received from the County, CONFIRE staff has created several other layers
      within the mapping features. CONFIRE would like to use the County GIS system
      to support functions including links to System geofiles, mapping of vehicle
      location and calls at CAD workstations, access to premise information such as
      ownership data and prior calls, conducting call analysis and providing CAD data.

      CONFIRE would like to take advantage of a centralized resource to support the
      geofile and geo-based data functions of the new CAD and MDC Systems. By
      maintaining a centralized GIS resource, CONFIRE will be able to leverage
      shared GIS data between member agencies and other departments based on

                                                                           May 17, 2007
                                                                                Page 4
                                        Request for Proposal for Integrated CAD System

       clearly defined data security and access privileges. In addition, CONFIRE is
       considering a comprehensive integration strategy so that it can utilize other
       agencies‘ map layers as well as potentially share GIS data with other County and
       City Departments. The Proposer is expected to provide all services and software
       that will be required in building a new geofile system.

2.2.5 Automatic Vehicle Location (AVL): CONFIRE is also considering the
      feasibility of implementing an Automatic Vehicle Location (AVL) System that
      would be integrated with the mapping application within the CAD and Mobile
      Systems. AVL is not used currently by CONFIRE and the member agencies.
      CONFIRE is requesting that Proposers provide, as an option, recommendations
      and costs related to the implementation of an AVL System that would be installed
      in conjunction with the CAD System.

2.3 Interfaces
In addition to the integration of the proposed System Components, the Proposer will be
responsible for providing interfaces to key CONFIRE and external systems. Table 1
below provides an overview of existing and future interfaces expected in the new
System.

Table 1. System Interfaces
 Applications Requiring      Data
      CAD Interface        Movement                       Description/Function
Existing Interfaces
Vesta E911 (CAD)          One-way     Import of ALI/ANI information to CAD and integrated
                                      mapping applications.
NetClock                  Two-way     Provides time synchronization for all Systems.
Station Alerting (SIMS)   One-way     Radio interface for fire station tone/voice alert
Bio-Key RMS               One-way     Automatically transfer all relevant CAD incident and related
                                      data to the RMS. Ability for CAD to send queries to the
                                      RMS database and receives returned responses.
Alphanumeric Paging       One-way     Wireless text messaging service
Planned Interfaces
GIS/Integrated Mapping    Two-way     Interface with existing County GIS database to support
                                      maintenance of CAD map, upload of CONFIRE and its
                                      member agency map layers and shared data with other
                                      departments.
Incident Management       One-way     Interface with a consolidated multiple agency-wide System
                                      that will allow access to the Homeland Security
                                      Department‘s National Fire Incident Reporting System
                                      (NFIRS).
San Bernardino County     Two-way     Transfer all relevant CAD incident and related data between
Sheriff CAD System                    CONFIRE‘s proposed CAD and San Bernardino County
(Tiburon)                             Sheriff‘s Tiburon CAD Systems.
AMR CAD System            One-Way     Transfer all relevant CAD incident and related data to AMR‘s
(Geac)                                Geac CAD System. Ability to send EMS dispatches to
                                      AMR.




                                                                                   May 17, 2007
                                                                                        Page 5
                                       Request for Proposal for Integrated CAD System

2.4 Hardware and System Software
The Proposer will supply all necessary server, System management and workstation
hardware and System software to ensure that the application software provided by the
Proposer will perform at their optimum capabilities for CONFIRE end users. All
proposed hardware and System software should be non-proprietary commercial off-the-
shelf. It is the expectation of CONFIRE that the proposed pricing for all hardware and
System software will be highly competitive and consistent with State of California
vendor agreements. With the exception of specialized high availability, continuous
operation CAD hardware, CONFIRE considers servers and desktop devices as
commodities. CONFIRE typically acquires such standard devices at a significant
discount, and thus reserves the right to purchase hardware from sources other than the
Proposer.

2.5 Data Conversion/Migration/Transformation
CONFIRE currently maintains data within their existing CAD and BIO-Key RMS
systems. CONFIRE is considering whether or not to pursue a cost-effective means of
populating the new CAD System with critical legacy data. Proposers should propose a
plan for the analysis and conversion, migration, or transformation of these data into the
proposed System. If data conversion, migration, or transformation is recommended,
then the proposals should also include specific methodology for assessing and/or
converting the designated data files to the new CAD System. Proposals should include
a proposed data conversion approach and all associated costs. The plan must include
project scope, analysis of requirements, alternative approaches, recommended method,
and implementation process.

2.6 Implementation and Support
The Proposer, with appropriate involvement from CONFIRE employees, must perform
all tasks required to implement the proposed System, including all configuration and
construction of interfaces where required.

2.7 Site Preparation
The Proposer shall provide and represent that minimum and maximum electrical
requirements, as well as all other permitted ranges of environmental variations, are
satisfactory for operation of the System. The Proposer shall be responsible for visiting
the CONFIRE and member agency facilities to obtain information to determine what is
necessary to fully prepare the installation site. Upon completion of site preparation by
CONFIRE, the Proposer shall inspect the premises and notify CONFIRE in writing that
CONFIRE and its member agencies have complied with such requirements. The cost
of any physical or environmental alteration or modification required for the successful
installation, operation, and/or maintenance of the System (either by the Proposer or
CONFIRE and its member agencies) that is attributable to incomplete or erroneous site


                                                                           May 17, 2007
                                                                                Page 6
                                        Request for Proposal for Integrated CAD System

specifications provided by the Proposer shall be borne by the Proposer at no cost to
CONFIRE and its member agencies.

2.8 Project Management
The contracting firm will be responsible for applying project management methodologies
in the areas of project planning, resource management, project monitoring, production
control, configuration management, quality assurance, test plan, conversion plan,
training plan, implementation methodology, post-implementation support, and
documentation (work plan, quality assurance, configuration management, requirements,
fit gap analysis, general and detailed System design, test plan, training plan, and user
manual).

2.8.1 The Proposer must propose a comprehensive project plan showing time and
      resources required to accomplish tasks. The plan should include three major
      phases: planning, implementation, and post-implementation. The contractor must
      employ professional project management software such as Microsoft Project. All
      time expended by project participants must be tracked.

2.8.2 The Proposer shall provide a Project Manager who, along with CONFIRE‘s
      Project Manager, will be responsible for coordinating the following:

2.8.3 Project plan development and implementation, project status reporting, and any
      sub-contractor work

2.8.4 System changes and modifications requested to the project plan

2.8.5 All technical, educational, documentation, and support services

2.8.6 During the course of the project, until final System acceptance, the contracting
      firm‘s Project Manager will:

             Attend monthly status meetings

             Submit monthly status reports, covering such items as:
                 o   Progress of work being performed
                 o   Milestones attained
                 o   Resources expended
                 o   Problems encountered
                 o   Corrective action taken

             Participate in weekly project status conference calls




                                                                           May 17, 2007
                                                                                Page 7
                                        Request for Proposal for Integrated CAD System

2.9 Testing
The implementation must include adequate provisions for functional, performance, and
reliability testing. This includes development of all test plans and parallel testing, if
appropriate, to assure that the System delivers the expected results.

2.10 Documentation
Documentation must be developed to support the software and CONFIRE‘S business
processes. Any software tools or utilities that are desirable to tune, test, maintain or
support the System must be specified. Any tailoring or configuring must be documented
and delivered to CONFIRE. At a minimum, the contracting firm shall provide CONFIRE
with the following:

         User documentation
         Configuration documentation
         Interface documentation
         Data dictionaries
         Database setup and maintenance
         Entity relationship diagrams
         Report creation and maintenance
         Ad hoc reporting System documentation

2.11 Acceptance Testing
Satisfactory completion of a mutually agreed-upon acceptance test for each stage of the
implementation is required. This acceptance test will include a confirmation of each
functional requirement identified in this RFP, in addition to standard acceptance
procedures that CONFIRE may require.

2.12 Implementation Warranty
CONFIRE also requires a warranty for implementation services (e.g., work products,
developed modifications, and System configuration) for a minimum of 18 months after
the formal System acceptance date. The contractor will warrant to its responses to the
functional requirements included in this RFP, and will agree to attaching its responses
to any contract reached with CONFIRE.

2.13 Post-Implementation Support
The contractor and its implementation team, with appropriate involvement from
CONFIRE employees, must provide ongoing support for 90 days after the date of
successful implementation in a production environment. Upon completion of the 90 day
period, if there are no outstanding issues, CONFIRE will provide formal acceptance of
the System.



                                                                            May 17, 2007
                                                                                 Page 8
                                        Request for Proposal for Integrated CAD System

2.14 CONFIRE Support and Staffing
The Proposer must recommend a plan for continuing support by CONFIRE employees,
including a description of skill requirements and staffing requirements for ongoing
System support.

2.15 Account Manager
Proposer will provide CONFIRE with an Account Manager who will be the single point of
contact throughout the Proposer‘s relationship with CONFIRE. The Account Manager
may be subjected to background checks before being allowed access to CONFIRE
Systems and information. CONFIRE reserves the right to request a change in Account
Manager personnel if CONFIRE feels the relationship is not progressing smoothly.

2.16 Support and Maintenance
The software manufacturer must provide telephone support up to twenty-four hours per
day, seven days per week including holidays. Telephone response time must not
exceed one hour for critical problem calls (as categorized by CONFIRE). The software
manufacturer must provide a problem escalation procedure that assures appropriate
management contacts can be made in the event that the support response is not
effective. This procedure must include the designation of a single point of contact for
the problem resolution.

The CAD System must be fully functional 24 hours/day and 365 days/year. The vendor
will be responsible for maintaining all components of the CAD, including, but not limited
to, hardware, software, and network interfaces. CONFIRE expects that the vendor will
be the single point of contact for all problems relating to the CAD.

2.17 Training
CONFIRE recognizes that the involvement, understanding and commitment of
employees are key to the successful implementation of the proposed System.
CONFIRE employees will assist in all key process design and configuration decisions.
The Proposer is expected to provide the following types of training programs:

2.17.1 A training program for CONFIRE‘s core project implementation team. The
       program should include the training necessary to understand the overall System
       architecture, interface configurations, data import/export capabilities, workflow
       configuration options, etc.

2.17.2 A training program for application administrators. The program should include
       the training necessary to configure, tailor, monitor, and administer the technical
       and functional aspects of System.




                                                                             May 17, 2007
                                                                                  Page 9
                                         Request for Proposal for Integrated CAD System

2.17.3 A training solution to support the training of end-users in the functionality of the
       various proposed System components. To support the training of end users,
       CONFIRE envisions the use of a ―train-the trainer‖ approach accompanied by
       computer-based training.

2.17.4 Post-implementation training for on-going end-user training of the initial System,
       as well as for future version releases. Again, CONFIRE envisions the use of a
       ―train-the trainer‖ approach accompanied by computer-based training.

2.18 CONFIRE’s Responsibilities
2.18.1 CONFIRE will provide the following System Components:

          Local and wide area network infrastructure
          Wireless data infrastructure
          CAD Workstations

2.18.2 Access to Facilities. CONFIRE shall provide access to facilities for installation
       of the System.

2.18.3 Project Management. CONFIRE will appoint a Project Manager who shall be
       responsible for review, analysis and acceptance of the Vendor‘s performance
       and the coordination of the project personnel, equipment, vehicles and facilities.
       The Project Manager shall be empowered to make decisions with the authority to
       bind CONFIRE with respect to the work being performed under this Contract.
       The Project Manager will coordinate, review and communicate the project
       selection and implementation to the Vendor‘s primary point of contact. The
       Project Manager shall identify, communicate and submit all contractual and
       financial obligations to the appropriate governing body for approval and
       acceptance.

2.18.4 Site Preparation: CONFIRE shall prepare at its own expense the System
       installation sites in accordance with the requirements of the selected Vendor‘s
       Proposal.

2.18.5 Network Installation: CONFIRE shall install and certify all necessary network
       infrastructures as required by the selected Vendor for the installation of the
       System provided under the terms of this Contract.

2.18.6 Manage the Installation: CONFIRE shall have responsibility for managing the
       installation of the System on behalf of CONFIRE.

2.18.7 Provide Review Services: CONFIRE shall review and provide input into the
       development of detailed System documentation and respond to each document
       within a timely manner.


                                                                               May 17, 2007
                                                                                   Page 10
                                      Request for Proposal for Integrated CAD System

2.18.8 Provide Project Related Information as Required by the Proposer: Provide
       day-to-day information and data concerning CONFIRE operations and activities.
       If CONFIRE‘s response is inadequate or the request is major in scope, then the
       Proposer shall make a written request specifying the desired response time, and
       CONFIRE‘s Project Manager shall provide written response within that time, if
       reasonable, or specify when such response shall be forthcoming.

2.18.9 Manage the Change Order Process: Advise the selected Vendor of any
       changes in CONFIRE‘s requirements and initiate change orders as specified in
       this Contract.

2.18.10 Coordinate Resources as Required: Provide personnel for file editing, table
      building, obtaining source documents and other necessary tasks in a timely
      manner, and for maintaining CONFIRE-owned equipment.

2.18.11 Provide Computer Time and Supplies: Provide and make available all
      necessary access to computers and supplies required for System operation and
      maintenance.

2.18.12 Perform Backups as Required: Perform backup functions on an ongoing
      basis as specified in System documentation.

2.18.13 Provide Communication Line(s) for External Sources: Provide all
      communication line(s) required for use with selected Vendor‘s application
      software, interfaces, and secure support line.

2.18.14 Attend Training: Includes selected Vendor‘s application software, System
      administration, and database training.




                                                                         May 17, 2007
                                                                             Page 11
                                        Request for Proposal for Integrated CAD System

Section 3        Proposal Submission

3.1   Submission Timeline & Events
CONFIRE has established the following tentative timeline for the administration of this
project. These dates are subject to amendment at CONFIRE‘s discretion.

              RFP Released                                     5/17/2007
              Last date to submit questions for response        6/4/2007
              at pre-proposal conference
              Pre-proposal Conference & Site Tour              6/13/2007
              Last date to submit questions and                6/27/2007
              requests for clarifications and
              interpretations
              Proposals Due                                    7/18/2007
              Vendor Selection                                 9/18/2007


3.2 Proposal Due Date:
Wednesday, July 18, 2007 - No later than 4:00 PM Local Time. The time and date
proposals are due shall be strictly observed.

3.3 Pre-Proposal Conference and Site Tour
A Pre-Proposal Conference & Site Tour (Conference) will be held to address initial
Proposer questions and review the relevant facilities. The Conference will be held on
Wednesday, June 13, 2007 at 10:00 a.m. at:

      Rialto Fire Station 203
      1550 N. Ayala
      Rialto, CA 92376

Attendance at the pre-proposal conference is strongly suggested, but not mandatory.
Immediately following the Conference, a tour of the Comm Center will be conducted.
This will be the only opportunity to tour the agency‘s facilities.

Proposers are expected to raise any questions or issues they have concerning the RFP
document at this point in the process. In order for questions to be answered at the
Conference, they should be submitted via email to Rick Britt (rbritt@confire.org) at least
five (5) business days in advance of the Conference. Questions not submitted in
advance of the conference may be asked, but may or may not be answered at the
conference itself.




                                                                            May 17, 2007
                                                                                Page 12
                                       Request for Proposal for Integrated CAD System

CONFIRE does not intend to issue minutes or notes from the Conference, however,
written clarifications or addenda will be issued as deemed necessary by CONFIRE.
CONFIRE will e-mail a list of the final questions and the official answers to all known
recipients of the RFP (include your e-mail address in any inquiries). Proposers shall
note that only written answers provided will be binding. These answers shall represent
CONFIRE‘s official position and supersede any previous oral statements made during
the Conference or at any time by CONFIRE staff.

3.4   Proposal Submission
3.4.1 Offers and modifications must be enclosed in sealed packages and have the
      following identifying information on the outside:

      A. Name and address of Proposer
      B. Closing Date and Time
      C. RFP Title

3.4.2 Responses to this RFP should be submitted as follows:

          CONFIRE
          Attn: Jenny Thompson
          1743 W. Miro Way
          Rialto, CA 92376-8630

3.4.3 Responding vendors should submit their proposals under two separate covers: 1)
      Technical Proposal and 2) Cost Proposal. The Proposer must submit one (1)
      signed unbound original, nine (9) additional bound hard copies, and one (1)
      electronic copy of each proposal part. The Cost Proposal should be sealed and
      submitted separately from the Technical Proposal.

3.4.4 CONFIRE shall be free to distribute these materials to the selection team and
      others involved in the selection process.

3.4.5 Additional copies of submitted proposals may be requested by the evaluation
      team at a later date.

3.4.6 An authorized representative of the Proposer must sign the proposal. The
      proposals containing the original signatures should be clearly marked ―Originals.‖

3.5 General Format
3.5.1 Hard copies of the proposals should be presented in a professional manner such
      as spiral bound or professional grade folder/three ring binder. Foldouts that
      contain charts, spreadsheets, and oversize exhibits are permissible. Tabs or
      other separators should serve to divide major sections of the proposal. Manuals
      and other reference documentation may be bound separately.

                                                                          May 17, 2007
                                                                              Page 13
                                       Request for Proposal for Integrated CAD System

3.5.2 The Proposer should sufficiently address each item presented in the RFP in
      accordance with the directions found herein. Each item is expected to be
      addressed or the proposal may be judged as ―non-responsive.‖ Answers should
      be clear, sufficiently detailed and specific to CONFIRE.

Proposals shall be based only on the material contained in the RFP. In addition to the
main document, this includes written responses to questions as well as any other official
amendments/addenda published by CONFIRE concerning the acquisition. Each
Proposer must be thoroughly familiar with all requirements of this RFP. The failure or
omission to examine any form, instrument or document shall in no way relieve
Proposers from any obligation in respect to this RFP.

3.6 Transmittal Letter
The Proposer should submit a formal transmittal letter on official company letterhead
that contains the following:

      A. Statement of Interest: This statement should indicate your firm‘s general
         interest and capability to perform the project. It should also include a brief
         summary of any information that you feel might be especially important to
         CONFIRE.

      B. Statement of Proposal Life: The proposal must have a proposal life of at
         least one hundred eighty (180) days from the date of the RFP due date. This
         shall represent the time during which the proposal is a firm offer and a
         contract may be entered into.

      C. Contact Person: Please include the name, title, address, telephone number,
         fax number and e-mail of the key contact person for any questions regarding
         your proposal.

      D. Signature of Authorized Representative: An authorized representative of
         the firm must sign the proposal.

3.7 Proof of Authority
      If the successful Proposer is a corporation, formal proof of the authority of the
      officer signing the Proposal to bind the corporation should be submitted with said
      proposal. A copy of the corporate resolution or minutes can be adequate proof.

3.8   Proposer History
The Proposer must be a ―responsible‖ Proposer that is both ethically and financially in
good standing within the industry, as determined by CONFIRE. If the Proposer has had
a contract terminated for default during the past three (3) years, this fact should be
disclosed in the RFP response along with the Proposer‘s position on the matter(s). If

                                                                            May 17, 2007
                                                                                Page 14
                                        Request for Proposal for Integrated CAD System

the Proposer has experienced no such terminations for default in the past three years,
then it should so indicate in the appropriate sections of the Proposer Questionnaire.

3.9   Clarifications and Interpretations
In order to ensure that all participants receive correct information regarding this RFP,
CONFIRE has designated the following contact for administrative issues and technical
questions:

      Rick Britt
      Communications Director
      rbritt@confire.org

Proposers may submit a written request for clarification on any portion of this RFP. If a
Proposer discovers any significant error, ambiguity, conflict, omission or other
deficiency in the RFP, the Proposer should request modification/clarification in writing.
The deadline for all questions and requests for clarifications or interpretations is
Wednesday, June 27, 2007 and should be directed via e-mail to Rick Britt. CONFIRE
shall not be obligated to respond to questions or requests for clarification or
interpretations not received by the stated deadline.

If CONFIRE determines a clarification is needed, an official addendum to the RFP will
be issued. CONFIRE shall not be obligated to respond to requests not received on a
timely basis. Proposer shall not be allowed to take advantage of any errors in or
omissions found in the Request for Proposals. Full instructions will be given if such
error or omission is discovered and timely called to the attention of the CONFIRE point
of contact mentioned above in a timely manner.

Any supplemental instructions or changes will be in the form of written addenda to this
solicitation. Any addenda will be made available at the CONFIRE website to all
prospective Proposers, prior to the due date for submittal of proposals. It shall be
presumed that the Proposer has received any addenda so issued and such addenda
shall become a part of the proposal submittal. This solicitation can be downloaded from
the CONFIRE‘s website at: http://www.confire.org

Proposers who have not obtained this proposal solicitation document directly from
CONFIRE shall be responsible for immediately notifying CONFIRE to receive all written
addenda on a timely basis. Proposers who do not so notify CONFIRE and submit
proposals without receipt of all addenda issued may be deemed to have submitted
proposals not responsive to this solicitation.

If any person contemplating submitting a proposal to the items or services listed herein
is in doubt as to the true meaning of any part of this Request for Proposals, he/she may
submit to CONFIRE representative(s) identified above, a written request for an
interpretation or correction thereof.


                                                                            May 17, 2007
                                                                                Page 15
                                         Request for Proposal for Integrated CAD System


Any interpretation or correction by CONFIRE will be made only by addendum, duly
issued by CONFIRE representatives identified above. Copies of such addenda will be
electronically delivered to those persons who have received a copy of the RFP.

3.10 Contact with County Employees and Others
In order to ensure a fair and objective evaluation, all correspondence regarding this
RFP should be addressed only to the individual listed on the RFP cover page. If your
company is currently providing services or equipment to the CONFIRE, you are
permitted to conduct your normal business; however, discussion of this RFP with
CONFIRE employees is prohibited without prior consent.

Proposers failing to adhere to this policy risk having their proposal disqualified.

3.11 Exceptions to the RFP
Proposers are to follow the format of the RFP in preparing responses. Any exceptions
taken to the RFP or CONFIRE‘s contract terms and conditions should be explicitly
stated.

CONFIRE is receptive to solutions or alternatives the Proposer feels will more cost
effectively meet its needs. Alternatives should be clearly identified in your response
where applicable.

3.12 Proposal Term and Validity
Proposals submitted shall remain valid for a period of 180 days after receipt.
CONFIRE reserves the right to reject any and all proposals or any part of any proposal.
CONFIRE also may waive minor defects or technicalities, at its sole discretion, or to
solicit new proposals on the same project or a modified project.

Proposals may be modified or withdrawn by an authorized representative of the
Proposer or by formal written notice prior to the date and time specified for submission.
Proposals submitted will become the property of CONFIRE after the proposal
submission deadline.




                                                                              May 17, 2007
                                                                                  Page 16
                                        Request for Proposal for Integrated CAD System

Section 4        General Conditions

4.1 Purchase Alternatives
CONFIRE reserves the right to purchase more or less of any item proposed at the unit
price offered unless specifically limited in a Proposer‘s response. CONFIRE reserves
the right to procure hardware, software, or components through alternative, 3rd party or
other resources at a lower cost, as approved for compatibility by the successful
Proposer.

4.2 Current Manufacture:
All hardware and software furnished under this specification should be standard
products of manufacturers regularly engaged in the production of such equipment. All
hardware and software must be of the manufacturer‘s latest design. All material and
equipment offered must be new and unused.

4.3 Site License Option
The Proposer should provide the ability for CONFIRE to purchase site licenses for all
System Components proposed. Site license costs versus user licenses should be
proposed as an option and clearly identified in Proposer‘s Cost Proposal.

4.4 Current Version
The Proposer ―packaged‖ application and System software shall be the most current
publisher or Proposer version, as of date of contract. The System proposed should be
operational in two (2) or more Proposer locations as of the date of the proposal. Beta
test versions will be not acceptable.

4.5 Prior Use
CONFIRE reserves the right to use hardware and software furnished under this
proposal prior to final acceptance. Such use shall not constitute acceptance of the work
or any part thereof by CONFIRE.

4.6 Availability of Funds
In the event that sufficient funds are not available for the project, CONFIRE reserves the
right to negotiate the scope of this Contract, delay implementation, reject all proposals,
or award another type of contract other than that required in this RFP.

4.7 Requirement to Meet All Proposal Provisions:
Each Proposer should respond to all of the specifications and proposal terms and
conditions. By virtue of the proposal submission, the Proposer acknowledges

                                                                            May 17, 2007
                                                                                Page 17
                                         Request for Proposal for Integrated CAD System

agreement with and acceptance of all provisions of the specifications except as
expressly qualified in the proposal.

4.8 Proposal Retention and Award
CONFIRE reserves the right to determine and waive non-substantial irregularities in any
proposal, to reject any or all proposals, to reject one part of a proposal and accept the
other, except to the extent that the proposals are qualified by specific limitations, and to
make award as the interest of CONFIRE may require.

4.9    Revision to the RFP
CONFIRE may modify or amend this RFP at any time. If it becomes necessary for
CONFIRE to revise any part of this RFP, an addendum will be provided to all Proposers
in receipt of the original RFP.

4.10 Use, Disclosure and Confidentiality
All documents submitted, as part of the proposal will be deemed confidential during the
evaluation process. Proposals will not be available for review by anyone other than the
Evaluation Team.

Following award of contract, all proposals become public documents and are available
for public view through CONFIRE upon written request. Any areas of your proposal that
include proprietary or confidential information should be clearly identified as such so
that those areas can be excluded from public view. Pricing cannot be considered
proprietary information

4.11 Certificate of Insurance
Proof of insurance is not required to be submitted with your proposal, but will be
required prior to the CONFIRE's award of the contract. Types of insurance that will be
required for this project are Workers Compensation, Errors and Omission Liability and
Professional Liability. As proof of insurance coverage, the successful Proposer will
include the insurance certificates as an addendum to the signed contract. Specific
insurance requirements are listed in the Public Safety Systems Agreement attached to
this RFP.

4.12 Errors in Proposals
Proposers will not be allowed to change or alter their proposals after the deadline for
proposal submission. CONFIRE reserves the right, however, to correct obvious errors
such as math errors in extended pricing (not unit pricing). This type of correction may
only be allowed for ―obvious‖ errors such as arithmetic, typographical, or transposition
errors.

                                                                              May 17, 2007
                                                                                  Page 18
                                         Request for Proposal for Integrated CAD System

4.13 Proposer Expenses
By submitting a response to this RFP or participating in the process, each Proposer
agrees that all of its related expenses are its sole responsibility, and that CONFIRE will
not be responsible for any costs whatsoever incurred by the Proposer in connection with
or resulting from the RFP process, including but not limited to costs for preparation and
submission of proposals, travel/per diem, attending interviews, providing presentations
or demonstrations, and participating in contract negotiation sessions.

4.14 Post-Proposal Presentations
As part of the selection process CONFIRE may require a Proposer to provide one or
more formal presentations to CONFIRE to further explain or clarify their proposed
solution. Any presentation will be at a time and place to be determined by CONFIRE
staff. The Proposer will be notified in advance of the specifics if such a presentation is
required. The commencement of discussions or the scheduling of presentations does
not signify a commitment by CONFIRE to execute an agreement or to continue
discussions with the Proposer.

4.15 Multiple Awards
CONFIRE may award a contract to a single Proposer; or, at its option, may award
contracts to multiple Proposers if deemed to be in the best interest of CONFIRE.

4.16 Contract Negotiations
CONFIRE will use the requirements set forth in the RFP as the basis for proposal
evaluations. After identifying one or more responsible Proposers who appear to be
most advantageous to CONFIRE, CONFIRE may enter into contract negotiations with
the Proposer(s). If at any time the contract negotiations are judged to be ineffective,
CONFIRE may cease all activities with a Proposer and begin/continue contract
negotiation and preparation activities with another Proposer, and the process may
continue until a contract is executed. As a part of this process, CONFIRE may obtain
―best and final offers‖ from all Proposers judged to be finalists. CONFIRE reserves the
right to cease all contract negotiation activities at any time and reject all proposals if
such action is determined by CONFIRE to be in its best interest.

4.17 No Obligation to Proceed
CONFIRE is under no obligation to proceed with this project or any subsequent project,
and may cancel this RFP at any time without the substitution of another, if such
cancellation is deemed in the best interest of CONFIRE. Furthermore, CONFIRE may
reject any and all proposals, to waive any irregularities or informalities in a proposal,
and to issue a new or modified RFP, if it is found to be in the best interest of CONFIRE.


                                                                             May 17, 2007
                                                                                 Page 19
                                       Request for Proposal for Integrated CAD System

4.18 Proposal Withdrawal and Modification
CONFIRE may allow a Proposer representative bearing proper authorization and
identification to sign for, receive, and withdraw the Proposer's unopened proposal prior
to the submission deadline. A Proposer wishing to modify its proposal may do so by
withdrawing the initial submission and then submitting a modified proposal prior to the
deadline.

4.19 Purchase Orders
The Proposer shall furnish no services, equipment, materials or labor unless a properly
executed order is received from CONFIRE directing the supply of the same.

4.20 Subcontractors
CONFIRE requires a comprehensive solution from a Prime Contractor with legal, project
management and financial responsibility for all hardware, software, integration and
implementation services. One consolidated response with all cost items included in the
cost summary shall be submitted.

As such CONFIRE intends to contract with one prime contractor who will be solely
responsible for contractual performance and who shall be the sole point of contact for
CONFIRE with regards to contractual matters. In the event the prime contractor utilizes
one or more subcontractors, the prime contractor will assume all responsibility for
performance of services by the subcontractor(s).

CONFIRE must be named as a third party beneficiary in all subcontracts. As requested
in Section 8.1, a list of all subcontractors proposed to take part in the performance of
the contract (at its outset) shall be provided to CONFIRE for approval prior to contract
execution. This request may require that sufficient financial or background information
be provided. To the degree available, this information should be included in an
Appendix with the proposal response.

4.21 Taxes
Unless otherwise specified in this solicitation document, Proposers shall include, and be
responsible for, paying all taxes, which shall be applicable to the sale of goods or
services.

4.22 Sample Contract
The selected Proposer will enter into contract negotiations with CONFIRE. To expedite
this process, CONFIRE‘s Public Safety Systems Agreement is included in Appendix C.
This document will be the basis of the contract negotiated with the successful Proposer.



                                                                           May 17, 2007
                                                                               Page 20
                                       Request for Proposal for Integrated CAD System

Any exceptions to CONFIRE‘s contract terms and conditions should be explicitly
identified in Proposer‘s submittal; unless an exception is noted, CONFIRE‘s standard
terms will be considered acceptable to the Proposer.

4.23 Licenses and Permits
The successful contractor shall furnish CONFIRE upon request any and all
documentation regarding necessary licenses, permits, certifications and/or registrations
required by the laws or rules and regulations of the County of San Bernardino, other
units of local government, the State of California and the United States. The Proposer
certifies that it is now and will remain in good standing with such governmental agencies
and that it will keep its licenses, permits, certifications and/or registrations in force
during the term of the agreement.

4.24 Use of CONFIRE Name
Upon entering an agreement, the successful contractor agrees not to use the name of
CONFIRE in relation to the agreement in commercial advertising, trade literature or
press releases to the extent without the prior written approval of CONFIRE.

4.25 Incorporated by Reference
This Request for Proposal (RFP) distributed by CONFIRE, including any other required
terms, will be incorporated by reference and made a part of any resulting contract,
except that any material approved by CONFIRE as confidential will not be publicly
disclosed.

4.26 RFP Not Contractual
Nothing contained in this Request for Proposals shall create any contractual relationship
between the Proposer and CONFIRE.

4.27 Patent Fees, Patent, Copyright, Trade Secret and Trademark Fees
Each Proposer shall include in the price bid any patent fees, royalties and charges on
any patented article or process to be furnished or used in the prosecution services
described in the Contract.




                                                                           May 17, 2007
                                                                               Page 21
                                        Request for Proposal for Integrated CAD System

Section 5        Supplemental Exhibits

Exhibit 1 provides anticipated transaction and user volumes for the project.
Exhibit 2 provides a service area overview of CONFIRE.
Exhibit 3 provides an overview of the CONFIRE Fire Demand Zones.
Exhibit 4 provides an organizational chart of CONFIRE.
Exhibit 5 provides an overview of the existing CONFIRE network.




                                                                           May 17, 2007
                                                                               Page 22
                                       Request for Proposal for Integrated CAD System

Exhibit 1 - Volumes
Exhibit 1 presents volume information for sizing the processing and storage
requirements of the new System. A 15% growth projection has been assumed for the
given five-year period. The proposed System should be sized to meet the performance
standards for the projected volumes plus a margin for unexpected volume growth.

Proposers are responsible for providing all hardware, peripherals and software
applications with sufficient capacity and performance capabilities to support the volumes
noted below. The selected Proposer will assume any costs associated with increasing
the System capacity as required to support the specified volume requirements noted
below within a five-year period after Final Acceptance.

Table 2. Transaction Volumes
                           CONFIRE                          Current      Projected 2012
Service area (square miles)                                 13,364           16,604
Service population                                          737,466        1,324,652
Number of agencies served                                      8               14
Number of fire stations                                        83             110
Number of Fire Demand Zones                                  1,829           2,200
Current CONFIRE environment:
Call takers                                                    2               8
Dispatchers                                                   18              26
Supervisors                                                    4               4
Extra help                                                     7              12
Number of CAD workstations                                    10              12
Fire incident counts                                        85,465          158,958
Concurrent usage requirements
CAD (entry)                                                   10              16
CAD (read-only)                                                5              50
Mobiles                                                        0              50




                                                                           May 17, 2007
                                                                               Page 23
                                    Request for Proposal for Integrated CAD System

Exhibit 2 - Service Area Overview




                                                                     May 17, 2007
                                                                         Page 24
                                    Request for Proposal for Integrated CAD System

Exhibit 3 - Fire Demand Zone Overview
Fire Demand Zones are available for download on the CONFIRE website.




                                                                       May 17, 2007
                                                                           Page 25
                                                                        Request for Proposal for Integrated CAD System

Exhibit 4 - CONFIRE JPA Organization Chart


                                                                          Rick Britt
                                                                       Communications
                                                                          Director


                                      Dispatch Support                                                       Jenny Thompson
                         Cliff Ellis, ESD II - Quality Assurance                                              Staff Analyst II
                         Mike Weston, ESD II - CAD Support                                                 Administration/Budget



                                                                                                                 Debbie Sisson
                                                                                                                 Fiscal Clerk I




     Dave Dowling                                                                    Alec Martinez               Robert McLaughlin            Thomas Clark
                                           Ingrid Johnson
  Dispatch Operations                                                             System Administrator          System Administrator      Programmer/Analyst III
                                          GIS/911 Manager
       Manager                                                                        Infrastructure              Desktop Support          Application Support


                                                                                                                 Tami King ASA I
                              GIS Techs                    Brian Acosta               Vacant PAI                Richard Bonilla AST
                                                                                  Karen Mathews ASA I                                     Yvonne Robbins BSAIII
                            Edward Solis                  911 Coordinator                                       Jevita Webster AST
                                                                                    Dave Medlin CT                                           Brian Kaura PA I
                          Terrance Vigilance                                                                    Raymond Bell AST
                                                                                   Josh Stephens CA                Vacant AST




       E Shift
Johanna Van Steel CT

       F Shift                   Bonnie Curtis               Karon Humphreys                  Sue Hood                          Tom Barnes
 Theresa Shirmer CT            A Shift Supervisor            B Shift Supervisor            C Shift Supervisor                 D Shift Supervisor

      Extra Help
 Michael Petrich ESD I
 Alfred Jackson ESD I                                      Otto Schramm ESD I
                             Vanessa Meyer ESD I
Steven Lehnhard ESD I                                       John Tucker ESD I            Van Swanson ESD I                   Carol Castronovo ESD I
                              Diane Boyles ESD I
   Sean Morse ESD I                                        Melissa Beeson ESD I          Bonnie Owen ESD I                   Abby Hutcherson ESD I
                              Leigh Frasier ESD I
  * Lynda Luna ESD I                                        Tim Franke ESD I              Krista Powell ESD I                  Cara Martin ESD I
                               Toni Natali ESD I*
     Vacant ESD 1                                          Donna Mueller ESD I           Julie Cornwall ESD 1                 Jaimie Vilches ESD I
                             Christine Hardy ESD I
     Vacant ESD 1
       Vacant CT
       Vacant CT




                                                                                                                                         May 17, 2007
                                                                                                                                             Page 26
                 Request for Proposal for Integrated CAD System


CONFIRE Organizational
      Structure


         Board of Directors
     Councilmember from City of Rialto
   Councilmember from City of Redlands
  Councilmember from City of Loma Linda
     Councilmember from City of Colton
Board Member from County of San Bernardino




     Administrative Committee
        Fire Chief from City of Rialto
      Fire Chief from City of Redlands
     Fire Chief from City of Loma Linda
        Fire Chief from City of Colton
Board Member from County of San Bernardino




             Communications
                Director




                                                  May 17, 2007
                                                      Page 27
                                                 Request for Proposal for Integrated CAD System

                  Exhibit 5 - Current CAD System and Network Overview

                                                                           Radio
                                                                                         Sunset Site
                                                                                          Redlands
                    CAD Link
                                                      ISD
                                                 San Bernardino
                                                      CAD

                                                                              Radio
                                                                              Paging
                       Sunpro RMS                                                      Keller Peak Site
                                          SIMS                    Paging               Running Springs




 CommCenter
Dispatch Center                                                             Radio
     Rialto                       Radio           ISD - Rialto              Paging
                                                   Radio and
                                                                                       Stawberry Peak
                                                    Paging
                                                                                       Site - Crestline
                                                  Equipment




                                                                            Radio
                                                                                        Little Mountain
                                                                                           Site - San
                                                                                          Bernardino



                         Frame Relay
                            Circuit
      WAN                                         Fire Station
   Frame-Relay                                                              Radio
                                                  CAD Printer
      Cloud                                                                             Various other
                                                                                            Sites




                                                                                       May 17, 2007
                                                                                           Page 28
                                       Request for Proposal for Integrated CAD System

Section 6        Proposer Questionnaire Introduction

Section 7 through Section 20 establishes the format and basic content for proposals in
response to this RFP.

All responses should be submitted in the provided Word document or its copy.
Indicate your response after each question, within the provided table or directly where
indicated. You may add rows or attachments as necessary. These questions are
intended to assist CONFIRE in better understanding the System proposed as well as
the Proposer‘s approach to meeting the current and future needs of CONFIRE.

Section 7 provides a checklist of additional materials requested to be supplied by the
  Proposer(s). There is also a checklist to indicate the products and/or services to be
  provided by each Proposer.
Section 8 is a questionnaire to supply general information about each company that is
  a party to the proposal. A separate questionnaire shall be completed for each
  Proposer.
Section 9 requests reference information for each proposing Proposer.
Section 10 contains requirements for certain proposal information and also indicates
  specific required contractual guarantees.
Section 11 defines the requirements for hardware and provides a format for Proposers
  to describe their approach.
Section 12 requests information on mobile data computer configurations.
Section 13 requests information for System software proposed and related capabilities.
Section 14 requests a summary of the applications proposed, and specifies
  documentation requirements for the application software.
Section 15 defines the requirements for performance, System acceptance and testing
  and provides a format for Proposers to describe their approach.
Section 16 requests specific information about the implementation and project
  management services proposed.
Section 17 defines the requirements for training and provides a format for Proposers to
  describe their approach.
Section 18 defines requirements for warranty, maintenance and services and provides
  a format for Proposers to describe their approach.
Section 19 requests information on the Proposers‘ experience and proposed approach
  for supporting existing, proposed, and potential CONFIRE Systems and devices.
Section 20 requests information on the Proposers‘ experience and proposed approach
  for developing System interfaces.



                                                                           May 17, 2007
                                                                               Page 29
                                           Request for Proposal for Integrated CAD System

Section 7         Checklist and Proposer Services

7.1    Checklist
The following checklist has been included to ensure Proposer compliance with the
required RFP responses. Indicate whether each item specified is included in your
response, and cross reference the page where the item is located.

                      Item                     Included (Yes/No)    Proposal Location
Audited Financial Statements
Reference List
System Diagram
Hardware Technical Brochures
Training Plan
Data Conversion Strategy
System Diagram
Implementation Schedule
Project Team Resumes
Acceptance Test Plan
Hardware and Software Contracts and Licenses
Hardware and Software Maintenance
Agreements
Extended Reference Listing



7.1.1 If any of the above requested items are not included, explain.

7.2    Exceptions
Note any exceptions taken to the RFP requirements, terms or conditions. All exceptions
should be documented here regardless of whether referred elsewhere in your proposal.

7.2.1 Please stipulate the RFP Section and page number as well as a description of
      the exception.




                                                                             May 17, 2007
                                                                                 Page 30
                                                 Request for Proposal for Integrated CAD System

Section 8            Proposer General Information

Complete a copy of this Section for each Contractor, Sub-contractor.

8.1     Contractor
Provide the following information for each Contractor:

Prime Contractor (Y/N)

Local Address Serving CONFIRE:




Headquarters Address:




Contractor Representative:

             Name                                     Title                         Telephone/E-mail




Describe briefly this Contractor‘s roles and responsibilities in conjunction with this proposal:




                                                                                              May 17, 2007
                                                                                                  Page 31
                                              Request for Proposal for Integrated CAD System

8.2      Company Information

1. For how many years has the company provided public safety systems?              Years

2. How many employees does the company have?

      Nationwide (Total)                                                           Employees

      In office serving CONFIRE                                                    Employees
3. What was the Prime Contractor‘s annual gross revenue and net profit %
during the last previous three fiscal years?


                             Annual Gross Revenue                    Net Profit
Fiscal Year 2006

Fiscal Year 2005

Fiscal Year 2004

Provide a copy of the company‘s latest audited financial statements. Attached?       (Y/N)



8.2.1 Provide the following for at least one bank reference:

Bank Name:

Address:




Phone:

Contact:

Dunn & Bradstreet Number:




                                                                                  May 17, 2007
                                                                                      Page 32
                                       Request for Proposal for Integrated CAD System

Section 9        Proposer References

Complete a copy of this section for each Proposer, Sub-contractor.

Each Proposer or Subcontractor included in the proposal is to complete the reference
list as indicated for the ten most similar sites that have implemented similar hardware
configurations and software applications proposed by the Proposer. It is preferred that
references be for System implementations that have occurred within the past three
years. In addition, attach a complete list of installed sites with agency contact
information (name, position, telephone number).




                                                                          May 17, 2007
                                                                              Page 33
                                                                                                           Integrated CAD System



      Agency Name,           Configuration   Approximate    Operational    Installation   Multi-           Number of      Key
      Address, Contact,      Installed       Service Area   Applications   Dates          Jurisdictional   Agencies       Interfaces
      Title, Phone Number,                   Population                                   (Yes/No)         Served
      E Mail
1.


2.


3.


4.


5.


6.


7.


8.


9.


10.




                                                                                                                       May 17, 2007
                                                                                                                           Page 34
                                       Request for Proposal for Integrated CAD System


Section 10 Proposal/Contract Information

10.1 Authorized Negotiator
Provide the following information on the Proposer‘s authorized negotiator:

      Name/Title
      Contact Address
      Phone Number
      E-mail

10.2 Proposal Validity
10.2.1 For what length of time is your proposal valid? (Minimum 180 days)

10.3 Contract Exceptions
CONFIRE‘s contract as presented in Appendix C will act as the contract for this System.
The successful Proposer will be required to sign a contract with CONFIRE for this
engagement. The contract as presented in Appendix C will serve as the contract for
each of these agencies.

10.3.1 Unless exceptions to that contract language are noted here, the Proposer is
       presumed to have accepted the Appendix C contract. List any section number(s)
       and exception(s). Include suggested wording for any exceptions taken.




                                                                             May 17, 2007
                                                                                 Page 35
                                      Request for Proposal for Integrated CAD System

Section 11 Hardware Requirements

This section contains the minimum hardware requirements that the Proposer should
meet. Proposers should use these requirements as a baseline when responding to the
RFP; higher standards are acceptable and will be evaluated on a cost-benefit basis.

CONFIRE anticipates that the proposed software will operate independently of the
proposed hardware platform and reserves the right to use agency provided hardware.

Section 11 of the Proposal should include two subsections:

          a. A text document containing responses to the requirements listed herein.
             All responses should be submitted on this document or its copy. Indicate
             your response after each question. If you add attachments, be sure to
             reference them for easy access.

          b. Required attachments.

11.1   Operating System
CONFIRE requires a solution for the proposed CAD, MDS and message switch servers
that are capable of supporting real-time applications, and supported by the CPU
hardware manufacturer. CONFIRE requires licenses for the operating Systems. All
proposals must provide the name and version number of the proposed operating
system. Proposals that incorporate any proprietary or non-standard components must
provide justification for the component and a detailed integration approach.

11.1.1 Does the Proposer understand and agree to the Operating System statement
       above? If there are exceptions to the Operating System statement indicate
       which items you are taking exception to and provide any recommended
       alternatives.

11.2 System Diagram
Provide a diagram of the proposed System design. The diagram should include an
overall representation of the servers, network, peripherals and all mobile data
components. All Proposer supplied items listed in Hardware Costs should be included
in the diagram.

11.2.1 Is a diagram of the proposed System design attached? Where is the proposed
       System design located?




                                                                         May 17, 2007
                                                                             Page 36
                                        Request for Proposal for Integrated CAD System

11.3 Proposed Server Configuration
Provide the following information on the proposed servers. Additional tables should be
created for each server proposed.

                                              CAD              MDS              Other
 Quantity
 Mfg/Model
 Processor Type/Speed
 Main Memory
 Disk Storage
 Disk Controller (Types)
 Multi-media Devices
 Network Interface
 Power Supply
 Backup Media Type/Capacity
 Operating System Software
 Recommended Total/Concurrent Users


11.4 Technical Brochures
Provide technical brochures for the recommended System hardware. All Proposer
supplied items listed in Hardware Costs should be included in the diagram.

11.4.1 Are the technical brochures included in the proposal? Where are the technical
       brochures located?

11.5 Server Capacity
      CPU: The capacity of servers proposed for CPU processing must support the
       requirements and processing performance characteristics for the volumes
       described in Section 5, Exhibit 1 (Volumes) for at least five years from the date of
       overall Final Acceptance.
      Direct Storage Access: Sufficient direct access storage for file query data
       retention for volumes described in Section 5, Exhibit 1 (Volumes).
      Current and Future Capacity: Sufficient main memory, disk capacity, and
       processing capability to facilitate the System applications and peripheral devices
       currently in use, as well as expansion capabilities to support future growth
       requirements.
      Multitasking: Sufficient capacity to support multitasking for simultaneous
       processing of software applications and System components without System
       degradation.



                                                                             May 17, 2007
                                                                                 Page 37
                                        Request for Proposal for Integrated CAD System

      Additional Workstations: Sufficient capacity to support additional workstations
       and remote locations.

11.5.1 Does the Proposer understand and agree to the server capacity issues
       mentioned above? Indicate any exceptions and provide any recommended
       alternatives.

11.5.2 Describe the capacity expansion of each of the proposed servers? (e.g., RAM,
       CPU/storage, etc.)

11.5.3 Note any limitations or potential costs associated with supporting future capacity
       expansion.

11.6 Server Upgrades and Expansion
11.6.1 Indicate the maximum expansion capabilities for each of the proposed servers.
       Complete a table for each server.

                          Server(s)                          Maximum Expansion
        #/Type of Processors

        Main Memory

        Input/Output

        Disk Storage

        Recommended Number of Total/Concurrent     <Total Users>/ <Concurrent Users>
        Users


11.6.2 Describe the expandability of any proposed peripheral devices.

11.6.3 Describe the role in expansion provided by the Proposer as well as tasks
       required of CONFIRE.

11.6.4 Describe any impact (e.g., interference to normal operations, system shutdown)
       to systems that will occur during server upgrades and/or expansions?

11.7 Concurrent Operation
All System components (e.g., CAD, Mobile) should operate concurrently. If several
software applications utilize the same data server, the System should be configured to
assure priority workstation response for CAD.

11.7.1 Does the Proposer understand and agree to the Concurrent Operation statement
       above? If there are exceptions to the Concurrent Operation statement indicate
       which items you are taking exception to and provide any recommended
       alternatives.



                                                                             May 17, 2007
                                                                                 Page 38
                                        Request for Proposal for Integrated CAD System

11.8 Reliability
      Server redundancy is required to meet the performance requirements stated
       in Section 15. Higher levels of reliability (i.e., fault-tolerance) that are
       cost-effective, will be favorably considered during Proposer evaluation. The
       proposed CAD, MDS and Message Switch Systems should be configured to
       meet the stated performance criteria. All costs associated with higher degrees of
       reliability should be clearly indicated as pricing options. The Systems should
       respond immediately, seamlessly and automatically to an unexpected hardware
       or software failure. Parallel processing is not required, but the Systems must
       continue processing without server failure should any one component fail within
       the CAD, MDS or Message Switch Systems.

      Raid 5 and hot swap disks are required along with dual controllers to the storage
       disks/array. The CAD, MDS and Message Switching servers will have at a
       minimum two processors capable of assuming each others operations should
       one fail. Servers must also have redundant components such as power supply,
       fan, controller, and network cards.

      The proposed System should provide an architecture that will allow the Proposer
       to guarantee System availability initially and during the life of any license and
       maintenance contract. The System will be considered available based upon the
       following conditions:

          o Installed hardware and software have power applied and are operating
            correctly based on manufacturer specifications.

          o All functions and interfaces necessary for the processing and
            management of calls for service and the management resource are
            operating correctly.

          o All functions necessary for creating, editing or searching for a record
            maintained by the CAD Systems are operating correctly.

      Seven day, twenty-four hour operations for all Systems are critical (preferred up-
       time of 99.999%).

11.8.1 Describe how these requirements will be met.

11.8.2 Describe the System backup and recovery methodology.

11.8.3 Identify the amount of anticipated System downtime, for any reason, during a
       year of operation.




                                                                            May 17, 2007
                                                                                Page 39
                                         Request for Proposal for Integrated CAD System

11.9 Redundancy/Failover and Restore
11.9.1 Describe the proposed method of providing a highly available, redundant
       System, specifically addressing how failure of each of the following components
       is handled:

             Servers
             Processors
             Disk Storage
             Power supply (UPS)

11.9.2 As an option, CONFIRE is interested in securing pricing for a fully replicable CAD
       System, including all System software and server hardware that can be used in
       the event of a catastrophic incident at the primary PSAP. Describe your
       recommended solution, and provide associated pricing in Section 21.

11.9.3 What degree of user intervention is required to activate the redundant System
       Component in each of the above cases?

11.9.4 How much time is required until operations commence on the backup System
       Component?

11.9.5 Proposed equipment should enable a full or partial restoration of all data files.
       Describe your proposed process to restoring data files.

11.9.6 What steps, degree of user intervention and time is required to return operations
       to the primary CAD?

11.9.7 Describe the method of restoration of all data files.

11.9.8 Describe the tasks required by CONFIRE personnel and the level of technical
       knowledge required to restore tasks.

11.9.9 Has the proposed approach been installed at other sites? Where?

11.10 System Backup
Proposed equipment should enable a full backup of CAD within two (2) hours. All
System components should remain fully operational when the backup is occurring,
without any effect to the live operation.

11.10.1 Describe the tasks required by CONFIRE personnel and the level of technical
        knowledge required to perform backup.

11.10.2 Are all System functions (inquiry and update) available during backup? If not,
        please explain the level of availability of System functions during backup.




                                                                             May 17, 2007
                                                                                 Page 40
                                        Request for Proposal for Integrated CAD System

11.10.3 Explain any restrictions on access or System functions during this process.

11.10.4 Can the System perform incremental backup (i.e., only data/files updated since
        last backup)? (Yes/No)

11.10.5 Can the System back up specified files or applications (as opposed to complete
        disk image)? (Yes/No)

11.10.6 Can full backup be performed unattended? (Yes/No)

11.10.7 Can full backup be scheduled to occur automatically without System or System
        Component downtime or administrative personnel on scene? (Yes/No)

11.10.8 Explain any other backup capabilities or restrictions.

11.11 Power and Environmental
11.11.1 Although CONFIRE has an operational computer room, provide all the
        necessary power conditioning and backup capacity (UPS requirements)
        needed to support the proposed server configuration. Describe the
        manufacturer and model equipment proposed to address the UPS
        requirements. Include the capacity of the proposed equipment as well as the
        quantity to be included.

11.11.2 Specify the number and type of each power outlet that is required for the
        proposed server configurations.

11.11.3 Specify the air conditioning requirements in BTUs for the proposed servers.

11.12 Hardware Installation and Site Preparation
The Proposer will be responsible for central site and mobile hardware installation. This
includes all network connections.

11.12.1 Describe the CAD System hardware installation services to be provided with
        this proposal.

11.12.2 Describe the Mobile System hardware installation services to be provided with
        this proposal.

11.12.3 Describe any environmental requirements for both the proposed CAD and
        Mobile System hardware.

11.12.4 Is there any specific preparation necessary to ensure success of the CAD and
        Mobile installation?




                                                                           May 17, 2007
                                                                               Page 41
                                       Request for Proposal for Integrated CAD System

11.12.5 State the delivery lead time (from date of contract signing) in number of days
        for CAD System hardware.

11.12.6 State the delivery lead time (from date of contract signing) in number of days
        for Mobile System hardware.

11.13 Strategic Direction
CONFIRE‘s intended direction for information systems is supported by the following
elements:
      Open Systems Standards
      Windows-like Operating Systems
      Client/Server Architecture
      Relational Data Base Management Systems (RDBMS)

CONFIRE wishes to ensure that all proposed Systems will be compatible with current
standards as noted above at the time of implementation and into the future (e.g., future
versions of Microsoft products).

11.13.1 Describe the approach for meeting these desired capabilities.




                                                                           May 17, 2007
                                                                               Page 42
                                       Request for Proposal for Integrated CAD System

Section 12 Mobile Data Computers

CONFIRE is considering installing a total of 50 MDCs in command level vehicles (i.e.,
Chief and Battalion Chiefs‘ command vehicles) throughout San Bernardino County.
Eventually, CONFIRE intends to expand the usage of MDCs to all fire and EMS
vehicles.

Complete this Section in the table provided in Subsection 12.1.

12.1 MDC Configuration
Identify the recommended configuration for MDCs to guarantee the optimum
performance of the proposed application software. Include the following:




                                                                          May 17, 2007
                                                                              Page 43
                                               Request for Proposal for Integrated CAD System

                      Component                                    Configuration
Mfg/Model
Dimensions
Unit Weight
Construction Materials
Military Specifications
Vibration Specifications
Shock Mounting
Display Description/NIT/Size
Operating System Software
Processor Type/Speed
CPU/Hard Drive/RAM
Floppy Drive (External/Internal)
CD-ROM Drive (External/Internal)
Expansion Ports (Number, Type)
Port Protection
Input/Output (PS, PCMCIA, Serial, Parallel, etc)
Keypad (Description, Options)
Spillproof, Waterproof (Y/N)
Function Keys (Number, Programmable – Y/N)
Operating Temperature – Display
Operating Temperature – CPU
Battery Life
Modem Description
Indicator Light
Incoming Message Indicator
Emergency Button
Touchscreen (Y/N)
Data Input
Frequency Bands Supported
GPS Supportability
Network Options
Mounting Options/Configuration
Software Compatibility
Warranty
Accessories
Additional Features
Price Per Unit Without Options
Price Per Unit With Options




                                                                                   May 17, 2007
                                                                                       Page 44
                                       Request for Proposal for Integrated CAD System


Section 13 System Software Requirements

This section contains the minimum System software requirements that the Proposer
should meet. Proposers should use these requirements as a baseline when responding
to the RFP; higher standards are acceptable and will be evaluated on a cost-benefit
basis.

CONFIRE anticipates that the proposed software will operate independently of the
proposed hardware platform and we reserve the right to use agency provided hardware.

All responses in this section should be submitted on this document or its copy. Indicate
your response after each question. You may use as much space as necessary. If you
add attachments, be sure to reference them for easy access.

13.1 System Software
CONFIRE prefers that the CAD System software be state of the art technology, support
fire-specific functionality and represent the most current version in production at the
time of installation. CONFIRE prefers that all software proposed be operational in at
least two (2) production locations as of the date of the proposal. Ideally, all software
proposed should be operational in a multi-jurisdictional Fire/EMS dispatch environment
similar to CONFIRE.

List all System software proposed or available with the System. Additionally, indicate
whether the software will be included as standard or optional with this System. All
System software required to implement proposed Systems must be included and
identified in the Proposer Cost Summary (Section 21).

Operating System

13.1.1 Name

13.1.2 Release Level

Database management System (DBMS)

13.1.3 Name

13.1.4 Release Level

Other Systems

13.1.5 Communications protocol

13.1.6 Languages/development tools



                                                                           May 17, 2007
                                                                               Page 45
                                        Request for Proposal for Integrated CAD System

13.1.7 Utility/report writer programs

13.1.8 Administrative Tools

13.2 Security Features
CONFIRE requires that application security be tightly controlled at all levels. System
access should be controlled by user ID, role and workstation/device. System access
and functionality should be limited to, at a minimum, ―view,‖ ―inquiry‖, ―create,‖ ―edit,‖
―print,‖ ―send,‖ ―delete‖ of records and files. A comprehensive audit trail of all System
transactions by user ID, workstation, role, last action (e.g., inquiry, update, deletion),
time and date should be available and easily retrievable. Security profiles should be
definable by work group (e.g., dispatcher) as well as individual. CONFIRE prefers that
data access and operational permissions can be applied to the data element level within
all application modules. Detailed security and System access requirements are
included in the Functional Requirements Section (See Appendix A).

13.2.1 Describe the proposed approach to supporting CONFIRE‘s security
       requirements.

13.2.2 Define the role of System Administration in developing and maintaining security
       profiles. Include the process for changing individual profiles to support personnel
       movement.

13.2.3 Describe to what level of depth security and permissions may be controlled within
       an application module (i.e., restricting specific data elements from view within a
       CAD window).

13.2.4 Describe what security functions proposed are supported by security with the
       application software versus those provided by System software or the operating
       System.

13.2.5 Describe how audit trails are generated and what information is provided.
       Include any limitations or constraints to meeting CONFIRE‘s audit trail
       requirements.

13.2.6 Describe how the proposed System manages unsuccessful log-on attempts.
       Include CONFIRE‘s ability to establish the number of attempts allowed and the
       reporting or alerting mechanism used to communicate unauthorized access.

13.2.7 Describe what security functions are required in order to maintain data integrity in
       the CAD System.

13.2.8 Describe how the proposed security will prevent the tampering of historical data.

13.2.9 In addition to the windows-based security can the proposed security provide non-
       windows based security? Describe how the security functions will operate in a




                                                                             May 17, 2007
                                                                                 Page 46
                                       Request for Proposal for Integrated CAD System

      non-windows environment? Are there any differences in security for non-
      windows compared to windows-based security?

13.2.10 What type of virus protection strategy will be provided for the proposed CAD
      and MDC Systems? Describe any tasks that may be required of CONFIRE to
      address Proposer‘s virus protection strategy.

13.3 System Administration
13.3.1 What periodic System management functions should be performed to maintain
       System performance? How much System administrator time is needed per
       week?

13.3.2 What are your recommendations for staffing? Include in your recommendation
       the types of positions as well as the level of each position.

13.4 Site License
13.4.1 Does Proposer provide a site license option for all system components
       proposed? (Yes/No) If yes, please describe your recommended site license
       option(s) for CONFIRE. Include proposed costs in Section 21.5 (Optional Costs).




                                                                          May 17, 2007
                                                                              Page 47
                                      Request for Proposal for Integrated CAD System

Section 14 Proposed Application Software

This section contains the minimum proposed application software requirements that the
Proposer should meet. Proposers should use these requirements as a baseline when
responding to the RFP; higher standards are acceptable and will be evaluated on a
cost-benefit basis.

Section 14 of the Proposal should include two subsections:

          a. A text document containing responses to the requirements listed herein.
             All responses should be submitted on this document or its copy. Indicate
             your response after each question. If you add attachments, be sure to
             reference them for easy access.

          b. Required attachments.

14.1 Overview
The following charts require the Proposer to summarize key modules concerning the
CAD/MDC Application Software and interfaces proposed. Proposer shall provide all
information for each application.




                                                                         May 17, 2007
                                                                             Page 48
                                                                    Request for Proposal for Integrated CAD System


                                                                    Development                                 No. of
                                              Package               Language or   Operational   Date First       Sites
                     Application               Name     Developer    Tool Used      Status      Installed      Installed
CAD System
CAD
Geofile and Geofile Maintenance
EMD Priority Dispatching
Required Interfaces
VESTA (E911)
NetClock
Fire Station Alerting (SIMS)
Alphanumeric Paging
BIO-Key RMS
GIS/Integrated Mapping
Incident Management System
Geac CAD (AMR)
Tiburon CAD (San Bernardino County Sheriff)
Required Mobile Data System
MDC Messaging for Command Level Vehicles
(e.g., unit-to-unit, workstation-unit, etc)
Optional Mobile Data System
MDC Messaging for All Vehicles (e.g.,
unit-to-unit, workstation-unit, etc)
AVL
Mobile Mapping
Others
(Describe)




                                                                                                             May 17, 2007
                                                                                                                 Page 49
                                               Request for Proposal for Integrated CAD System
14.2 CAD Functionality
Identify if the System software supports the following fire-specific functionalities.
Indicate by a letter code if the proposed CAD software supports the functions in this
proposal (C), an alternative is recommended (A), or is not available (N) with this
System. If included (C) or if an alternative is recommended in this proposal, any
additional costs beyond the System software should be identified in the cost section.

                                         Function                    Code
                 Call priority dispatching
                 Proximity/closest unit dispatching
                 Real-time street networking
                 Strike team formation
                 Pre-fire planning
                 Control burn permit tracking
                 Alarm level recommendations
                 Call type classification based on time of day
                 Integrated info files
                 Centralized rostering
                 Premise history


14.3 Source Code
CONFIRE requires that the source code be made available at least through an escrow
type arrangement.

14.3.1 Does the Proposer make the source code for its Application Software available to
       its customers? (Yes-Source code supplies with System/No-Source code not
       available)

14.3.2 Is the source code available through the mandatory escrow type arrangement?
       (Yes/No)

14.3.3 Describe any limitations for access.

14.3.4 Is the source code available through direct purchase? If yes, show costs
       separately.

14.3.5 Is the source code available through other arrangement(s)? If yes, please
       describe.

14.3.6 Is programming documentation provided along with the source code?

                                                                                May 17, 2007
                                                                                    Page 50
                                       Request for Proposal for Integrated CAD System
14.3.7 Is source code provided for customized software?

14.4 Confirmation of Requirements
CONFIRE requires a design review process and approval to confirm the proposed
software meets all defined user requirements prior to commencing software
implementation or modifications for each application component.

14.4.1 Describe your proposed approach to confirming requirements/determining the
       modifications necessary to meet CONFIRE‘s specifications?

14.4.2 What is the process for development, delivery and acceptance of required
       modifications?

CONFIRE intends to confirm all System functionality prior to acceptance. Each specific
System function agreed to as part of the final contract should be tested and tracked
from original documentation (e.g., proposal to contract to ATP) by the selected
Proposer. The selected Proposer is required to document that each RFP requirement is
included in the final System design, acceptance test plan and System documentation.

14.4.3 Describe how base System functionality as well as customized functionality will
       be tracked, documented, and tested prior to Component Acceptance and Final
       Acceptance.

14.5 Process Analysis
CONFIRE would like to leverage the selected Proposer‘s experience working with
agencies that have successfully implemented its Systems. CONFIRE prefers that the
Proposer engage in a detailed process review to clarify current operations and process
development to effectively plan for future operations using the proposed System.
CONFIRE feels that the most benefits can be gained from the new Systems by
reviewing existing operations and evolving processes to leverage the capabilities of the
System.

14.5.1 Describe your approach to supporting process analysis/development in
       conjunction with your proposed System. Identify any associated costs that
       should be considered.

14.6 General Documentation
The Proposer should be able to supply comprehensive hard and soft copy
documentation for the System to cover the following subjects:
      System use
      System administration (hardware and software)

                                                                           May 17, 2007
                                                                               Page 51
                                       Request for Proposal for Integrated CAD System
      Database setup and maintenance
      Data dictionaries that include entity-relationship modeling and diagrams
      Interface and API design, use and maintenance

The System documentation should be consistent with the instructions supplied by the
online help for the proposed Software Applications.

14.6.1 Did you provide at least three original copies of documentation describing the
       use of the System, and its administration within the proposal? (Yes/No) If yes,
       where is the documentation located? If no, will you be able to provide during
       project implementation a minimum of three original copies of documentation
       describing the use of the System and its administration?

14.6.2 Will you provide authority to copy documentation for internal use as necessary?
       (Yes/No)

14.6.3 Proposers should provide a printed database schematic and data dictionaries to
       assist CONFIRE with site-specific fields and support for the System. Is this
       information included? (Yes/No) Where is this information located?

All documentation should be customized to include CONFIRE-specific requirements or
any functionality developed during the implementation process.

14.6.4 Are quick reference guides, cheat sheets, and FAQs provided? (Yes/No)

14.6.5 Would you be willing to provide a complete set of user documentation for finalist
       evaluation? (Yes/No)

14.7 Hardware Documentation
CONFIRE requires that the Proposer provide documentation for all equipment proposed
as part of System configuration. The Proposer should provide one electronic and at
least three hard copies of all documentation from equipment manufacturers and all
other Subcontractors. Technical brochures for all proposed hardware and peripherals
should be included in the proposal.

14.7.1 Are one electronic and at least three hard copies of all documentation from
       equipment manufacturers and all subcontractors included? Where is this
       information located?

14.7.2 Are technical brochures for all proposed hardware and peripherals included?
       Where are the brochures located?




                                                                           May 17, 2007
                                                                               Page 52
                                        Request for Proposal for Integrated CAD System
14.8 Software Documentation
The proposal should include a list and description of the software that is required to
operate the proposed hardware/software configuration including, but not limited to:

      Systems management
      Operating software
      Application Software manual
      Application System tutorial
      Hardware operations
      Table relationship diagrams
      Tables and keys with descriptions
      Fields showing what table is used for values
      Values in tables that are cross-referenced to other tables

14.8.1 Is a list and description of the software that is required to operate the
       hardware/software configuration proposed included in the proposal? (Yes/No)
       Where is the list and description located?

14.8.2 Is sample documentation available? (Yes/No) Where is sample documentation
       located?

14.9 System Implementation Documentation
Prior to implementation, the Proposer should provide an Engineering Plan including
Systems design, architectural plan, and integration scheme for any installed
components with clearly identified interface points for other Systems. It is anticipated
that the delivery of these documents will be indicated as milestones in the Project
Schedule.

14.9.1 Does the Proposer understand and agree to provide an Engineering Plan prior to
       System implementation?

14.9.2 How many days before System implementation will the Engineering Plan be
       provided to the CONFIRE project manager?

14.10 Application Upgrades
14.10.1   Are remedial software fixes for errors provided as part of a scheduled
          program? (Yes/No)

14.10.2   How often are enhancements typically provided?

                                                                             May 17, 2007
                                                                                 Page 53
                                        Request for Proposal for Integrated CAD System
14.10.3   Are updates provided to meet legislative (including local, state and federal)
          changes? (Yes/No)

14.10.4   Is there an additional charge for these updates? (Yes/No)

14.10.5   Is there an additional charge for new releases? (Yes/No)

14.10.6   Is installation of new releases mandatory? (Yes/No)

14.10.7   If you are proposing customized applications, will customized applications be
          upgraded along with the standard applications?

14.10.8   What will be the process to upgrade customized applications?

14.10.9   How long is maintenance continued for older releases?

14.10.10 Is new or updated documentation supplied with upgrades/new releases?
         (Yes/No)

14.10.11 How many hours of installation assistance are provided with updates at no
         charge?

14.10.12 If additional installation assistance is required for updates, what is the hourly
         charge?

14.10.13 What other installation assistance for updates is provided?

14.10.14 How many hours of conversion assistance are provided with updates at no
         charge?

14.10.15 If additional conversion assistance is required for updates, what is the hourly
         charge?

14.10.16 What other conversion assistance for updates is provided?

14.10.17 How many hours of training assistance are provided with updates at no
         charge?

14.10.18 If additional training assistance is required for updates, what is the hourly
         charge?

14.10.19 What other training assistance for updates is provided?

14.10.20 Outline customer notification process, including timeline for installation fixes,
         upgrades, and new releases.

14.10.21 Describe the delivery process options for installation fixes, upgrades, and new
         releases.

                                                                             May 17, 2007
                                                                                 Page 54
                                       Request for Proposal for Integrated CAD System

Section 15 Performance and System Acceptance

The following are the performance, acceptance and testing requirements that should be
met by the selected Proposer. It is anticipated that Proposers will use these
requirements as a baseline when responding to this RFP. Higher standards are
acceptable and will be evaluated on a cost-benefit basis. Proposers are asked to
respond after each question or directly where indicated. You may use attachments or
add additional space as necessary. Proposers are asked to note any exceptions to
requirements in Section 7.2.

Acceptance will occur in phases as various milestones identified in the implementation
plan and agreed to by CONFIRE are reached. The Proposer‘s implementation plan
should clearly define the hardware and software deliverables, tasks or other criteria
associated with each milestone.

Section 15 of the Proposal should include two subsections:

          a. A text document containing responses to the requirements listed herein.
             All responses should be submitted on this document or its copy. Indicate
             your response after each question. You may use as much space as
             necessary. If you add attachments, be sure to reference them for easy
             access.

          b. Required attachments.

15.1 Acceptance Periods
The following specifications apply to the requirements for CONFIRE‘s acceptance of the
Proposer‘s proposed System:

      System Component Acceptance Period: At the completion of each phase,
       indicating a System Component is operational and available to CONFIRE for
       testing, an Acceptance Test will be conducted for 30 consecutive calendar days.
      Final Acceptance Period: After all System Components are integrated,
       operational and available to CONFIRE for testing, an additional Acceptance Test
       will be conducted for 30 consecutive calendar days.
      Reliability Period: At the successful completion of each System Component
       Acceptance Period, indicating that the component is ready for live operations, a
       Reliability Test will be conducted.
      When all System Components have been successfully installed and integrated,
       an additional Reliability Test will be conducted.




                                                                           May 17, 2007
                                                                               Page 55
                                        Request for Proposal for Integrated CAD System
15.1.1 Do you agree to the required acceptance period criteria? (Yes/No) Clarify any
       exceptions.

15.1.2 How much time have you allotted for System Component Acceptance Testing?

15.1.3 How much time have you allotted for the Final Acceptance Test Period?

15.2 Test Plan
Provide a sample test plan. CONFIRE will use the test plan to evaluate the Proposer‘s
testing approach as well as its compliance with CONFIRE‘s testing requirements. The
final test plan will be approved by CONFIRE.

15.2.1 How are each of the functional specifications contained in the RFP to be tested?

15.2.2 How is additional functionality not contained in the RFP but ultimately included in
       the System to be tested?

15.2.3 How will you verify integration of System and System components?

15.2.4 How does Proposer plan to verify and demonstrate the elimination of redundant
       data entry within the CAD system? The verification and demonstration testing
       should include CAD interfaces.

15.2.5 Will Proposer provide a scenario test that allows for the System (all integrated
       hardware/software components) to operate under a simulated test situation?

15.2.6 What tasks are to be performed by CONFIRE versus Proposer personnel?

15.2.7 CONFIRE has determined the following severity level designations for failed
       operations:

             Level 1 — System or System Component cannot be turned live until
              problem is resolved.
             Level 2 — System or System Component may be turned live, but will not
              be accepted until problem is resolved.
             Level 3 — System or System Component may be turned live, System or
              System Component may be accepted; problem will be added to a punch
              list and final payment will not be made until problem is resolved.

      In the event that a Level 1 problem occurs, is corrected by the Proposer, then
      subsequently fails on two (2) additional occasions within the test period,
      CONFIRE has the right to be refunded all previous payments under the contract.

15.2.8 Do you agree to the required test plan criteria? (Yes/No) Clarify any exceptions.


                                                                            May 17, 2007
                                                                                Page 56
                                        Request for Proposal for Integrated CAD System
15.2.9 Does the Proposer understand and agree to refund all previous payments under
       the contract to CONFIRE if a Level 1 problem is not corrected on the third
       attempt?

15.2.10 Description of how problems will be corrected with associated maximum
      correction?

15.2.11 Description of how problems will be corrected with restart of testing?

15.2.12 Is a sample test plan attached? (Yes/No)

15.2.13 Where is the sample test plan located?

15.3 Testing
During the System Component Acceptance, Final Acceptance, and Reliability Periods,
the proposed application components will undergo a live test, using all requirements
stated in the RFP and any additional functionality developed and documented during
design sessions with the Proposer, and will include Regression Testing. In addition, the
performance and capacity of the System will be tested based on the volume
requirements stated in this RFP. The following tests of the Systems are anticipated
during the Acceptance Periods as defined above:

      Functional Acceptance Testing: During the Functional Acceptance Test Plan
       (ATP) the Proposer will demonstrate the operation of each proposed or required
       feature, function and interface in a live environment based on the test plan that
       will be approved by CONFIRE prior to contract signing. Should any feature,
       function, or interface fail, the problem will be corrected by the Proposer and the
       Acceptance Period will restart upon correction.

15.3.1 Does Proposer agree to the required Functional Acceptance Testing criteria?
       (Yes/No) Clarify any exceptions.

      Performance Testing: The purpose of the Performance Test is to demonstrate
       and document, as necessary, the performance requirements as stated in this
       RFP. This Performance Test should be conducted on CONFIRE‘s System at the
       CommCenter and must be conducted for a period not less than 30 days. To
       pass the Performance Test, the proposed System or System Component must,
       for 30 consecutive calendar days, perform successfully, in accordance with the
       performance requirements stated in this RFP. Should any System Component
       fail to meet the performance criteria for any reason, the problem will be corrected
       by the Proposer and the Acceptance Period will restart upon correction.

15.3.2 Does Proposer agree to the required Performance Testing/Stress Testing
       criteria? (Yes/No) Clarify any exceptions.


                                                                            May 17, 2007
                                                                                Page 57
                                        Request for Proposal for Integrated CAD System
      A second component of the performance test will be to demonstrate the
       capability of the System or System Component to handle peak volumes. For this
       purpose a Stress Test will be designed and applied by the Proposer to simulate
       full capacity utilization of the Communications Center. Stress test parameters
       and processes should be included in the sample test plan provided by all
       Proposers.

15.3.3 Does Proposer agree to the required Testing criteria? (Yes/No) Clarify any
       exceptions.

      Reliability Testing: The Reliability Test will be conducted at the successful
       implementation of each System Component and again when all System
       Components have been successfully implemented for the designated period.
       The purpose of the Reliability Test, as part of the overall System acceptance
       requirements, is to demonstrate the operational capability and reliability of the
       System and System Components. In order to complete the Reliability Test
       successfully the following must occur:

       o All Systems and System Components must demonstrate full availability for
         the full duration of the Acceptance Period.
       o Should any System or System Component fail three times during the testing
         phase you will replace the failing System or System component, without
         charge to CONFIRE.
       o System and System Component performance will continue to meet the
         Functional requirements of the contract, as tested or verified by CONFIRE
         personnel at any time.
       o System and System Component performance will continue to meet the
         Performance requirements of the contract, as tested or verified by CONFIRE
         personnel at any time.

       In the event that the System or any System Component falls below the required
       availability mark, the Reliability Test will be stopped. At this time the Proposer
       should correct any deficiencies in preparation for a retest. If the deficiencies are
       of such severity that the retest cannot be initiated within 15 days of the initial
       failure, the Proposer should prepare a Correction Plan for submittal to CONFIRE
       for approval that details the reason for the failure and proposed correction.

       The Proposer will have three opportunities to complete the Reliability Test over a
       period of 120 days. If the Proposer fails to successfully complete the test in this
       time period, then at CONFIRE‘s option:
          o The Contract between the Proposer and CONFIRE may be terminated as
            specified in the Contract.




                                                                             May 17, 2007
                                                                                 Page 58
                                        Request for Proposal for Integrated CAD System
          o The Proposer will upgrade the System and implementation team with
            whatever resources are necessary to bring the System into compliance, at
            no cost to CONFIRE.

       CONFIRE will notify the Proposer of the successful completion of each test.
       Upon successful completion of the Functional, Performance, and Reliability Tests
       and achievement of all milestones as specified in the contract and CONFIRE will
       issue a notice of Final Acceptance.

15.3.4 Does Proposer agree to the required Reliability Testing criteria? (Yes/No) Clarify
       any exceptions.

15.4 Ongoing System Performance
The following specifications describe the performance requirements for the Proposer‘s
System following CONFIRE‘s formal acceptance of the System and throughout the life
of the Contract between CONFIRE and Proposer:

      During the warranty and contract periods, the hardware and software
       components of the System must remain fully operational and available for use by
       meeting the required System response times and availability.
      The initial System hardware and software configuration should provide for all
       current and future volumes as described in this RFP (Section 5, Exhibit A,
       Volumes)
      The hardware and software provided should meet the capacity expectations
       stated in the RFP and continue to meet functional, reliability, and performance
       requirements of this RFP for a period of five (5) years from Final Acceptance.

In the event that the System or any System Component fails to meet any requirements
of this RFP after acceptance and during the warranty period the Proposer must take
appropriate steps to correct the problem and bring the System or System Component
back into compliance with the performance and reliability requirements at no cost to
CONFIRE.

15.4.1 Do you agree to the required ongoing System performance criteria? (Yes/No)
       Clarify any exceptions.

15.4.2 State the proposed reliability to be provided.

15.4.3 Does the System accommodate the call for service volumes and other applicable
       sizing parameters as specified in the RFP? (Yes/No)

15.4.4 Does the System function effectively from all workstations (fixed and wireless)?
       (Yes/No)


                                                                           May 17, 2007
                                                                               Page 59
                                       Request for Proposal for Integrated CAD System
15.4.5 Does the System allow all files and tables to be updated on-line without
       adversely affecting System performance? (Yes/No)

15.4.6 Does the System allow necessary back-ups to be done online without adversely
       affecting System operations, and without lockouts for updates? (Yes/No)

15.4.7 Does the System complete queries to interfaced databases without adversely
       affecting the any proposed System Component? Such inquiries will not tie up or
       lock up the workstations? (Yes/No)

15.5 System Response Times
Response time is defined as the time elapsed between depressing the enter key and
the appearance of the data requested on the next screen. Describe below the
methodology used to estimate System response time, the estimated response times of
your proposed configuration, and under what conditions the stated response times will
or will not be met. The System response time should not exceed the response times
defined below when operating at three (3) times the expected initial volumes.
Response times should be achievable during all other System activities (e.g., report
generation, System backup, etc). Note that CONFIRE intends to use response time
representations and guarantees in the final contract.


 Activity                                                Maximum Response Time
 CAD — Transactions                                      1 second
 CAD — Transactions with validation                      2 seconds
 CAD — External database queries                         5 seconds
 MDC — Transaction                                       1 second
 MDC — Transactions with validation                      2 seconds
 MDC — Query; external database                          5 seconds

The System is expected to experience no degradation. Any function proposed that
might result in System degradation must be specifically noted.

15.5.1 Will you provide the above response time guarantee for CAD? (Yes/No)

15.5.2 Will you provide the above response time guarantee for MDC? (Yes/No)

15.5.3 Are there any function(s) proposed that will cause degradation in either the CAD
       or MDC System?

15.6 System Availability
The following specification defines both System availability and the method by which it
is calculated, as it is used in other sections of this RFP:

                                                                           May 17, 2007
                                                                               Page 60
                                        Request for Proposal for Integrated CAD System
      The System will be considered available for use only when each of the following
       conditions are met:
          o Installed hardware and software have power applied and are operating
            correctly based on manufacturer specifications
          o All functions and interfaces necessary for the processing and
            management of calls for service and the management resource are
            operating correctly
          o All functions necessary for creating, editing or searching for a record
            maintained by the CAD Systems are operating correctly
      System availability will be expressed as a percentage of the maximum expected
       availability over a given period. The System must be available 7 days per week,
       24 hours per day.
      Scheduled down time for System upgrades will not be construed as Hours
       System Unavailable
      The percentage availability for any period will be calculated as follows:

                 (Total Hours in Period – Hours System Unavailable) x 100
                                   Total Hours in Period

15.6.1 Will you meet the noted System uptime guarantees? (Yes/No)

15.6.2 Describe the guaranteed uptime of the proposed System, the methodology to be
       used in measuring availability and under what conditions or circumstances
       availability guarantees will or will not be met.

15.6.3 State how the proposed System will guarantee System availability.




                                                                             May 17, 2007
                                                                                 Page 61
                                        Request for Proposal for Integrated CAD System

Section 16 Implementation and Project Management

16.1 Status Reporting
During the course of the project, until final System acceptance, a representative of the
selected Proposer will:
      Attend monthly status meetings
      Submit monthly status reports, covering such items as:
          o Progress of work being performed
          o Milestones attained
          o Resources expended
          o Problems encountered
          o Corrective action taken
      Participate in weekly project status conference calls

16.1.1 Does the Proposer understand and agree to attend monthly status meetings,
       submit monthly status reports and participate in weekly project status conference
       calls to the CONFIRE project manager and/or project team? Indicate any
       exceptions to the status reporting.

16.2 Project Management and Implementation Services
16.2.1 CONFIRE requires that the Proposer take responsibility for providing extensive
       project management and implementation services. Provide details about the
       nature and extent of project management and implementation services to be
       provided during this project.

16.2.2 Who will be the designated project manager?

16.2.3 Will the Proposer maintain a project schedule? (Yes/No) If yes, describe the
       methodology used.

16.2.4 Will the Proposer coordinate hardware installation and training? (Yes/No) If yes,
       describe how Proposer will coordinate hardware installation and training.

16.2.5 Will the Proposer problem solve and troubleshoot all products and services?
       (Yes/No) If yes, describe the proposed problem solving and troubleshooting
       process.

16.2.6 Will the Proposer monitor issues related to the project? (Yes/No) If yes, describe
       the process the Proposer will use to monitor issues.


                                                                            May 17, 2007
                                                                                Page 62
                                        Request for Proposal for Integrated CAD System
16.2.7 Will the Proposer prepare project status reports and attend status meetings?
       (Yes/No) If yes, describe the frequency and format.

16.2.8 Describe in detail any additional Project Management and Implementation
       Services provided by Proposer.

16.3 Recommended Implementation Schedule
16.3.1 Discuss any recommendations for implementation regarding priorities and
       phasing. List any assumptions used in your recommended schedule.

16.3.2 Attach a proposed project implementation schedule through completion of
       implementation. The schedule shall be based upon the number of months after
       contract signing and should represent ―not to exceed‖ or guaranteed Delivery
       Dates. The project should be in significant detail, and include all Proposer tasks,
       agency work steps and project milestones.

16.3.3 Is a proposed project schedule attached? (Yes/No) Where is the proposed
       project schedule located?

16.3.4 If so, detail your reasoning, experience and provide pricing information.

16.4 Time and Level of Support
CONFIRE will require 24 hour support from cutover to acceptance for both CAD and
MDC.

16.4.1 Detail the amount of time and level of support you will provide. Include all costs
       (if not already included) in the Proposer Cost Summary in Section 21.

16.5 Support Personnel
16.5.1 Provide a list of the names, positions, on site hours per month and duration of
       assignment for all Proposer personnel that may be assigned to the project.

16.6 Resumes
Attach resumes showing experience, including specific CAD engagement assignments,
and educational qualifications of personnel to be assigned to the project. Individuals
proposed for work on this project may be subject to background checks and additional
screening by CONFIRE.

16.6.1 Are resumes attached for the project manager and each project team member?
       (Yes/No)

16.6.2 Where are the resumes located?


                                                                            May 17, 2007
                                                                                Page 63
                                        Request for Proposal for Integrated CAD System
16.7 Post-Implementation Evaluation
16.7.1 Describe your post-implementation evaluation process.

16.8 Additional Items
16.8.1 Indicate any additional items recommended or required for this implementation,
       e.g., supplies, special equipment. Make sure that all costs are included in the
       appropriate cost section (Section 21).

16.9 Implementation Requirements
16.9.1 Indicate the resource requirements CONFIRE should meet/provide for a
       successful implementation. Include in a table format the activity/task, duration,
       resources, staff hours per month and any comments on the activity/task as it
       relates to implementation of the proposed Systems.




                                                                            May 17, 2007
                                                                                Page 64
                                            Request for Proposal for Integrated CAD System


Section 17 Training Requirements

17.1 Overview
The following are the training requirements that should be met by the selected
Proposer. It is anticipated that Proposers will use these requirements as a baseline
when responding to this RFP. Proposers are asked to note any exceptions to
requirements in Section 7.2.

The quantity and quality of training proposed will be a key factor in evaluating
Proposers. The general training approach desired will be of System Administrators,
supervisors and key support personnel. The proposed training plan should be designed
and conducted to provide complete familiarization in all proposed hardware and
software. A comprehensive training plan should be included as an attachment with your
proposal.

17.1.1 Is a training plan attached? (Yes/No)

17.1.2 Where is the training plan located?

17.1.3 Summarize the key elements of your training approach.

17.2 Training Plan
The training plan proposed should include:

      Types of training classes that will be provided with assumed participants (e.g.,
       roles, functional areas).
      Number of participants for each class
      Prerequisites for all participants
      Length of each class in hours
      Total number of trainer hours proposed

All training should be conducted onsite (any training that requires off-site participation
must be specifically noted). The training plan should be flexible enough to allow
CONFIRE to make adjustments to the participants or curriculum to achieve the greatest
benefit for the training hours provided.

Refresher training is preferred but not required. Indicate in your training plan if refresher
training is provided and, if so, note any additional costs.




                                                                              May 17, 2007
                                                                                  Page 65
                                         Request for Proposal for Integrated CAD System
17.2.1 Does the Proposer understand and agree to the proposed training plan? Explain
       any exceptions to the training plan and provide any alternatives.

17.2.2 Is a copy of a proposed training plan provided? If so, where is it located in the
       proposal?

17.3 Training Documentation
All training material should meet the following requirements:

      Training materials should be provided three (3) weeks prior to the start of any
       training course.
      Training materials must be for the version of the software that will be deployed.
       Training materials for previous/older versions of software is unacceptable.
      Training materials should be customized by the Proposer to include functionality
       defined in this RFP and any functionality that is developed through the
       implementation process.
      All training material will be provided in electronic format for unlimited duplication
       by CONFIRE and its member agencies.
      A minimum of three (3) hardcopies of all training material will be provided.

17.3.1 Does the Proposer understand and agree to provide all training documentation
       as presented above? Explain any exceptions and provide recommended
       alternatives if available.

17.4 Training Simulation
A training System should be proposed that will allow users to simulate live operations
for all proposed System Components without degrading System performance. A
simulated System or training database should be provided to CONFIRE as soon as
possible after contract signing to allow CONFIRE personnel to familiarize themselves
with each System Component. A minimum of two workstations is preferred.

17.4.1 Indicate your approach for meeting this requirement.

17.4.2 Discuss your proposed approach to providing System, Software Application and
       System Administration training, taking into account the number of potential users
       and the wide range of functions.

17.4.3 How many on-site and off-site application software training hours are included in
       this proposal? Itemize by application module (Specify the number of proposed
       Trainer hours (by Proposer Personnel) provided in the ‗Hours‖ column).



                                                                               May 17, 2007
                                                                                   Page 66
                                         Request for Proposal for Integrated CAD System
Description of Training          Recommended Number of Persons              Hours
                                                                  On-Site      Off-Site


TOTAL

17.4.4 Identify the hardware and System software training included in this proposal
       (Specify the number of proposed Trainer hours (by Proposer Personnel) provided
       in the ‗Hours‖ column).

Description of Training          Recommended Number of Persons              Hours
                                                                  On-Site      Off-Site
Hardware operations and System
management:


System software:


Other:




17.4.5 Identify optional classes or training available but not included in this proposal.

17.4.6 Note the specific type, duration, and location of any refresher/follow-up training
       included in your proposal. Also, identify training that could be made available but
       is not included, as well as any associated costs.

17.4.7 It is anticipated that a final training plan will be developed jointly between the
       selected Proposer and CONFIRE to include training formats (e.g.,
       train-the-trainer, end user training), locations, time frames, curriculum, etc.
       Describe your role and associated tasks in supporting the development of the
       final training plan. Describe your proposed participation for both train-the-trainer
       and end-user training. Address the level of flexibility CONFIRE will have in
       determining how to best use the training hours proposed.




                                                                              May 17, 2007
                                                                                  Page 67
                                      Request for Proposal for Integrated CAD System

Section 18 Warranty and Maintenance Requirements

This section contains the minimum warranty guidelines and maintenance and service
requirements that Proposers should meet. Proposers should use these requirements
as a baseline when responding to the RFP; higher standards are acceptable and will be
evaluated on a cost-benefit basis.

CONFIRE anticipates that the proposed software will operate independently of the
proposed hardware platform and we reserve the right to use agency provided hardware.

Section 18 of the Proposal should include two subsections:

          a. A text document containing responses to the requirements listed herein.
             All responses should be submitted on this document or its copy. Indicate
             your response after each question. If you add attachments, be sure to
             reference them for easy access.

          b. Required attachments.

Proposers are asked to note any exceptions to requirements in Section 7.2.

18.1 General Maintenance Provisions
The following requirements are applicable to all maintenance and repair services
supplied by Proposers or Proposers‘ subcontractors, both under and outside of the
warranty:

18.1.1 Is a copy of the warranty included in the proposal? (Yes/No) Where is the
       warranty located in the proposal?

18.1.2 Is a copy of the maintenance and service agreement included in the proposal?
       (Yes/No) Where is the agreement located in the proposal?

18.1.3 Will the proposed CAD and MDC Systems include a minimum first year
       warranty after acceptance; and an option for five years support and
       maintenance?

18.1.4 Will the Proposer offer the purchase of one or more additional years of support
       and maintenance?

18.1.5 Will the Proposer offer the purchase of other specified ongoing services on a
       year-by-year basis?

18.1.6 Will the Proposer offer the purchase of a five-year support Contract?


                                                                         May 17, 2007
                                                                             Page 68
                                        Request for Proposal for Integrated CAD System
18.1.7 Will the Proposer offer hardware and software support 24 hours a day, 7 days a
       week?

18.1.8 Will the Proposer or Manufacturer provide all labor necessary to maintain the
       hardware System in good operating condition and in conformance with the
       manufacturer‘s specifications and performance requirements?

18.1.9 Will the Proposer or Manufacturer provide equipment and other materials
       necessary to maintain the hardware System in good operating condition and in
       conformance with the manufacturer‘s specifications and performance
       requirements?

18.1.10 Will the Proposer or Manufacturer cover expenses necessary to maintain the
        hardware System in good operating condition and in conformance with the
        manufacturer‘s specifications and performance requirements?

18.1.11 Indicate from where the hardware support will come.

18.1.12 Indicate the process for identifying hardware issues and assignment of
        completion correction to ensure appropriate accountability.

18.1.13 Will the Proposer offer System Software and Application Software updates for
        corrections as part of the price for maintenance and warranty?

18.1.14 Will the Proposer offer enhancements and refinements as part of the price for
        maintenance and warranty?

18.1.15 Will the Proposer offer additional purchased capabilities as part of the warranty,
        which begins after acceptance, and as part of the price for maintenance for
        those years in which CONFIRE has purchased maintenance from the
        Proposer? Will the manufacturer‘s support also be offered?

18.1.16 Will the Proposer provide software necessary to maintain the System and
        System Components in good operating condition as part of the warranty for
        year one, and as part of the price for maintenance, for those years in which
        CONFIRE has purchased maintenance from the Proposer?

18.1.17 Will the Proposer provide other materials necessary to maintain the System
        and System Components in good operating condition as part of the warranty for
        year one, and as part of the price for maintenance, for those years in which
        CONFIRE has purchased maintenance from the Proposer?

18.1.18 Will the Proposer assume all expenses necessary to maintain the System and
        System Components in good operating condition as part of the warranty for
        year one, and as part of the price for maintenance, for those years in which
        CONFIRE has purchased maintenance from the Proposer?


                                                                            May 17, 2007
                                                                                Page 69
                                       Request for Proposal for Integrated CAD System
18.1.19 Will the Proposer provide maintenance to include the provision of the
        Proposer‘s most recent version of all software?

18.1.20 Will the Proposer provide maintenance to include any customization, including
        customized interfaces, provided by either the Proposer or its subcontractor(s)?

18.1.21 Will the Proposer include services necessary to support the provider‘s most
        recent software release?

18.1.22 Will the Proposer include supplemental training and documentation necessary
        to support the provider‘s most recent software release?

18.1.23 Will the Proposer include hardware updates for the purpose of correcting errors
        as part of the warranty in year one, or as provided by the manufacturer
        (whichever is greater), and as part of the price for maintenance for those years
        in which CONFIRE purchases maintenance from the Proposer?

18.1.24 Will the Proposer include routine updates as part of the warranty in year one, or
        as provided by the manufacturer (whichever is greater), and as part of the price
        for maintenance for those years in which CONFIRE purchases maintenance
        from the Proposer? Will Manufacturer support also be offered?

18.2 General Warranty Provisions
The following requirements are applicable to all maintenance and repair services
supplied by Proposers or proposed subcontractors under warranty:

      The entire CAD System solution as proposed in this RFP should include a first
       year warranty (for Proposer-supplied hardware and software). The warranty
       should conform to contractually agreed specifications, and protect against any
       defects or damage caused by Manufacturers, Proposers, or proposed
       subcontractors, in the System‘s equipment or software. A five (5) year support
       agreement will also be offered.
      24x7 maintenance hardware and software maintenance should be provided as
       part of the one-year warranty.
      The one-year warranty should begin (for products accepted in phases) at the
       point that the CAD System is formally accepted by CONFIRE, as defined in
       Section 15 (Performance Requirements and System Acceptance).
      If the Proposer is unable to perform under these guidelines then a separate
       provider of CONFIRE‘s choice will be used and the repair costs passed on to the
       Proposer.




                                                                           May 17, 2007
                                                                               Page 70
                                          Request for Proposal for Integrated CAD System
18.2.1 Does the Proposer understand and agree to the general warranty provisions
       mentioned above? Explain any exceptions to the general warranty provisions
       and provide any alternatives.

18.2.2 Will the Proposer cover expenses to repairs made under warranty, including
       parts, software, labor, travel expenses, meals, lodging and any other costs
       associated with the repair?

18.2.3 Will Proposer cover repair costs for work it is unable to perform based upon
       warranty guidelines?

18.3 Moves, Changes and Additions
18.3.1 Will the Proposer propose a System where CONFIRE will be able to make
       routine hardware moves, additions, feature changes and perform similar
       administrative tasks internally?

18.3.2 Will Proposer provide the capability of providing technicians to perform these
       tasks upon request by CONFIRE for the life of the warranty and maintenance
       contracts?

18.3.3 Will Proposer guarantee that the changes for such normal work will not exceed
       the normal rate you have in effect for your other customers at that time?

18.3.4 Complete the warranty and maintenance matrix below based on your proposed
       approach. For services proposed within the matrix include all costs in the
       ―Hardware,‖ ―System Software‖ and ―Application Software‖ sections of Section 21
       as appropriate. Complete one matrix per Proposer offering warranty/
       maintenance services.


                                                       Hardware and       Application
                      Proposed Services               System Software      Software
       What is the length of the warranty (months)?
       Does warranty begin from installation or
       acceptance?
       24x7 Warranty & Maintenance coverage
       (Required)
       What are the days/hours of maintenance
       coverage (after the warranty expires)?
       Warranty/Maintenance Services:
       Telephone Support (Y/N)?
       Normal hours of telephone support operations
       (Pacific Time)?
       Toll Free ―800‖ number (Y/N)?
       Remote dial up software diagnostics (Y/N)?
       Electronic Help and Problem Reporting (Y/N)?
       Remote dial up software update (Y/N)?


                                                                           May 17, 2007
                                                                               Page 71
                                             Request for Proposal for Integrated CAD System
       Updates and enhancements included (Y/N)?
       How often are enhancements provided?
       User group membership (Y/N)?
       Newsletter (Y/N)?
       Service/support response time (hours)
       Via secure network access — Average
       Via secure network access — Guaranteed
       On site — Average
       On site – Guaranteed
       Hardware Preventive Maintenance (PM)
       Included as part of agreement (Y/N)?
       If yes, what is scheduled interval for PM (days)?
       Does PM require the System to be taken down
       (Y/N)?
       If so, for how long (on average)?
       On Call After Hours Services
       Hourly rate for service personnel
       Minimum hours charged
       How long will you guarantee support of
       equipment/ software proposed (number of
       years)?


18.3.5 What is the escalation procedure provided with your proposed
       warranty/maintenance services?

18.3.6 Does your proposal provide 24 x 7 support? Describe the duration proposed
       and associated costs.

18.3.7 Have you ever dropped support of a third party component? If so, what is your
       procedure for doing so, and how much notice do you give customers?

18.3.8 Will you guarantee a fixed maintenance cost for hardware? (Yes/No) If yes, for
       how many years?

18.3.9 Will you guarantee a fixed maintenance cost for software? (Yes/No) If yes, for
       how many years?

18.3.10 Describe the obligations of CONFIRE following a new release/major redesign of
        an application.

18.3.11 Is there mandatory installation of the new release? (Yes/No) If yes, how soon?
        (months)

18.3.12 Is there an additional charge for the new release? (Yes/No)

18.3.13 Is conversion assistance provided, if necessary? (Yes/No)

18.3.14 Is new documentation supplied? (Yes/No)


                                                                              May 17, 2007
                                                                                  Page 72
                                       Request for Proposal for Integrated CAD System
18.3.15 Is additional training provided? (Yes/No)

18.3.16 Is maintenance continued for the old release? (Yes/No) If yes, how long?

18.3.17 Describe the service coverage provided under the warranty period.




                                                                        May 17, 2007
                                                                            Page 73
                                        Request for Proposal for Integrated CAD System

Section 19 Experience and Implementation Approach

This section is intended to provide Proposers with an opportunity to describe previous
experience working in environments and with Systems similar to those proposed.
Indicate your response after each question on this document. You may use as much
space as necessary. If you add attachments, be sure to reference them for easy
access.

19.1 GIS/Geofile Approach
CONFIRE would like to take advantage of a centralized data source that will support the
geofile and geo-based functions of the new CAD and MDC Systems as well as
potentially leverage shared data between agencies based on clearly defined data
security and access privileges. In addition, CONFIRE would like the ability to update
the GIS/Geofile in real-time by appropriate personnel.

19.1.1 Describe your proposed approach for geofile development. Include the process
       for obtaining/developing a new geofile as well as the proposed services, roles
       and responsibilities of CONFIRE personnel and services to be provided by the
       Proposer. In addition, provide a recommended time commitment schedule.

19.1.2 Describe the process for generating and maintaining the System geofile as well
       as the recommended approach for adding map layers that CONFIRE deems
       appropriate.

19.1.3 What level of effort is required to build and maintain the geofile? What services
       are being proposed to support this effort?

19.1.4 Does the proposed System provide the ability for GIS integration?

19.1.5 Describe your approach to integrating with the County‘s existing GIS. Include if
       your geo-based products are consistent with the County‘s GIS standards and, if
       not, any constraints to support integration.

19.1.6 Does your proposed System require CONFIRE to build and support a separate
       geofile for CAD?

19.1.7 Are you currently supporting sites that have operational Phase II wireless E911
       Systems? Describe some of these sites that are taking advantage of the
       capabilities offered by Phase II wireless. Provide contact information for any
       sites referenced.

19.1.8 Describe how the proposed System supports geofile updates (both daily/routine
       and major uploads).



                                                                            May 17, 2007
                                                                                Page 74
                                        Request for Proposal for Integrated CAD System
19.1.9 Describe your approach to integrating with the County GIS in support of
       information sharing with other agencies. Include how security is applied and data
       access is managed.

19.1.10 Describe how the proposed System will support real-time mapping (both
      automated daily/routine and major uploads).

19.1.11 Identify the time required for the proposed System to produce map displays.

19.1.12 Describe in detail the location validation process.

19.1.13 Describe your approach to using a geofile to support your proposed CAD
      System.

19.1.14 Indicate the number of hours required for agency personnel to perform indexing
      tasks.

19.2 Mobile Data
At the present time there are not any mobile data devices in any of CONFIRE‘s member
or contract agency vehicles. CONFIRE is requesting that mobile data hardware and
software be installed in command level vehicles with an option to install MDCs in all fire
and EMS units at a later date.

19.2.1 Discuss your experience and recommendations regarding the use of MDCs.

19.2.2 Discuss your experience and recommendations regarding installation of mobile
       data hardware and software.

19.2.3 Provide recommendations on how you will be able to achieve optimal operability
       in a variety of terrain and weather conditions (e.g., mountains, canyons, desert,
       snow storms, rain, etc).

19.2.4 Which CAD features and functions, if any, are unavailable to field users
       accessing CAD via MDCs?

19.2.5 Discuss your experience working with PDAs and other handheld devices. Do
       you currently have sites that are operational with any of your Software
       Applications running on handheld devices? Describe your recommendations for
       using handheld devices in conjunction with your proposed Software Applications.

19.3 Report Generation/Data Output
CONFIRE requires CAD query and report generation capabilities to all authorized
System users. These capabilities should allow non-technical users to generate queries,
reports and statistical data based on any selected data within the CAD System and

                                                                            May 17, 2007
                                                                                Page 75
                                        Request for Proposal for Integrated CAD System
user-defined parameters (e.g., date range, location, responding unit, staffing). Users
should have the ability to schedule and/or automatically generate regularly needed
reports and be available to designated personnel.

19.3.1 Does the proposed System include an ad hoc query and reporting utility?

19.3.2 Describe your experience and approach to providing standard and ad hoc query
       and report generation capabilities. Note if these capabilities are an integral part
       of your System or provided via a third party application. Also include the training
       approach for supporting CONFIRE‘s technology preferences and ad hoc query
       and reporting requirements.

19.4 Electronic Mail
CONFIRE is interested in expanding its CAD electronic mail capabilities.

19.4.1 Does the proposed System include electronic mail distribution?

19.4.2 Describe how information from the CAD application can be distributed via an
       existing e-mail System. Include your approach and experience working with
       standard and web based e-mail Systems and any limitations.

19.5 Electronic Messaging
As part of the proposed CAD System CONFIRE would like the Proposer to provide real-
time electronic messaging within its CAD application.

19.5.1 Does the proposed System include electronic messaging?

19.5.2 Describe how messages can be distributed in a CAD workstation-to-CAD
       workstation environment via an existing electronic messaging System. Include
       your approach and experience working with standard and web based CAD-to-
       CAD electronic messaging Systems and any limitations.

19.5.3 Describe how messages can be distributed in a CAD workstation-to-MDC/MDC-
       to-CAD workstation environment via an existing electronic messaging System.
       Include your approach and experience working with standard and web based
       CAD workstation-to-MDC/MDC-to-CAD workstation electronic messaging
       Systems and any limitations.

19.5.4 Describe how messages can be distributed in a MDC-to-MDC environment via
       an existing electronic messaging System. Include your approach and experience
       working with standard and web based MDC-to-MDC electronic messaging
       Systems and any limitations.



                                                                            May 17, 2007
                                                                                Page 76
                                       Request for Proposal for Integrated CAD System
19.6 Incident Management
Each member agency operates it own incident management System. Due to the lack of
agency-wide accessibility and data sharing between the member agencies CONFIRE is
interested in exploring a consolidated multi-agency System that will be fully integrated
with the CAD System.

19.6.1 Does the proposed System include a multi-agency incident management
       application?

19.6.2 Describe your experience and approach to providing a multi-agency incident
       management application. Provide detailed information on the System that you
       are planning to implement with the proposed CAD System. What options will be
       available?

19.6.3 Can the proposed incident management application be accessed from both the
       CAD and MDC Systems?

19.7 Data Conversion
CONFIRE is considering whether to implement a data conversion process for its PRC
CAD files.

19.7.1 What would be your recommendation for implementing a data conversion of
       critical files for the proposed CAD System?

19.7.2 If you are recommending data conversion, describe your approach to providing
       analysis to current data structures for data conversion.

19.7.3 Detail your experience converting data systems similar to those currently in use
       by CONFIRE.

19.7.4 Provide a detailed description of your data conversion strategy addressing
       CONFIRE‘s current environment and conversion needs. Reference and explain
       all proposed costs and potential additional future costs necessary to complete
       the data conversion effort (All costs should be noted in Section 21 (Costs).

19.7.5 Describe any recommended alternatives to directly converting existing data (e.g.,
       data warehousing) including previous experience and proposed costs.




                                                                           May 17, 2007
                                                                               Page 77
                                        Request for Proposal for Integrated CAD System

Section 20 Interface Development Experience

The following questions are intended to provide Proposers with an opportunity to
describe previous experience developing the interfaces required in this RFP. Proposers
should indicate the specific approach for interface development, tools or applications
used to support the interface, all costs associated with interface development (include
comprehensive interface costs in Section 21 (Costs) as well as any assumptions,
constraints or considerations.

20.1 General Interface Experience/Approach
20.1.1 Does the proposed solution provide the ability to interface with existing systems
       by universal automated and manual data imports?

20.1.2 Describe your approach to integrating your software with varying and new
       technologies as they become available?

20.1.3 Describe your approach and experience providing seamless integration between
       the proposed System components. Include any constraints that limit data access
       between components and anywhere within the proposed System components
       redundant data entry may be necessary. Note the specific sites that have
       successfully deployed integrated components based on the versions proposed.

20.1.4 Describe your specific experience providing CAD interfaces for inquiry and
       update capabilities to MDC users.

20.1.5 Describe the proposed message switching software/hardware design/
       configuration. Identify how it will operate including how it will be used by CAD
       and MDC users. Describe on which server(s) it is located. CONFIRE does not
       require a separate message switch hardware solution.

20.1.6 Describe the proposed approach and your specific experience supporting the
       following Systems interfaces. Specific functional requirements are noted in
       Appendix A (Functional Requirements).

      Include any assumptions or constraints (e.g., communications protocol) to
      successfully completing the interface(s). Note whether the interface deployment
      is ―O‖ — Operational, ―U‖ — Under Development, ―X‖ — Not Available. Describe
      the services being provided and any assumptions regarding working with the
      interfacing agency or organization to develop the interface.




                                                                            May 17, 2007
                                                                                Page 78
                                             Request for Proposal for Integrated CAD System
Required Interfaces
Vesta E911         Import of ALI/ANI information to CAD and integrated mapping applications. This is
                   currently an existing interface used by CONFIRE.
Number of Sites    Date Initially         Operational Status Interface to CAD    Language or Tool
                   Installed                                  or Message Switch Used


Proposed Approach/Assumptions/Constraints:




BIO-Key RMS        Automatically transfer all relevant CAD incident and related data to the RMS. This
                   is currently an existing interface used by CONFIRE.
Number of Sites    Date Initially         Operational Status Interface to CAD         Language or Tool
                   Installed                                    or Message Switch Used


Proposed Approach/Assumptions/Constraints:




NetClock           Two-way interface that will provide time synchronization for all Systems. This is
                   currently an existing interface used by CONFIRE.
Number of Sites    Date Initially         Operational Status Interface to CAD         Language or Tool
                   Installed                                   or Message Switch Used


Proposed Approach/Assumptions/Constraints:




                                                                                       May 17, 2007
                                                                                           Page 79
                                             Request for Proposal for Integrated CAD System
Station Alerting   One-way radio interface for fire station paging. This is currently an interface to the
(SIMS)             existing PRC CAD.
Number of Sites    Date Initially       Operational Status Interface to CAD            Language or Tool
                   Installed                                    or Message Switch Used


Proposed Approach/Assumptions/Constraints:




Alphanumeric       One-way radio interface for wireless text messaging service. This is currently an
Paging             interface to the existing PRC CAD.
Number of Sites    Date Initially          Operational Status Interface to CAD     Language or Tool
                   Installed                                  or Message Switch Used


Proposed Approach/Assumptions/Constraints:




GIS/Integrated     Two-way interface with existing County GIS to support maintenance of CAD map,
Mapping            upload of CONFIRE map layers and shared data with other departments.
Number of Sites    Date Initially       Operational Status Interface to CAD       Language or Tool
                   Installed                                 or Message Switch Used


Proposed Approach/Assumptions/Constraints:




                                                                                         May 17, 2007
                                                                                             Page 80
                                             Request for Proposal for Integrated CAD System
Tiburon Sheriff    CONFIRE is interested in obtaining the ability to enjoy seamless two-way interface
CAD System         between their new CAD System and the San Bernardino County Sheriff‘s Tiburon
                   CAD System indicated in the Interface Functional Requirements sections of
                   Appendix A.
Number of Sites    Date Initially      Operational Status Interface to CAD          Language or Tool
                   Installed                                   or Message Switch Used


Proposed Approach/Assumptions/Constraints:




Geac AMR CAD       CONFIRE is interested in obtaining the ability to enjoy a seamless one-way
Systems            interface from their new CAD System to AMR‘s GEAC CAD System indicated in the
                   Interface Functional Requirements sections of Appendix A.
Number of Sites    Date Initially         Operational Status Interface to CAD       Language or Tool
                   Installed                                   or Message Switch Used


Proposed Approach/Assumptions/Constraints:




                                                                                      May 17, 2007
                                                                                          Page 81
                                        Request for Proposal for Integrated CAD System

Section 21 Proposer Cost Summary

This section requires a detailed breakdown and summary of costs for the proposed
Systems in the following categories:

      Hardware
      System Software
      Application Software
      Implementation Costs
      Optional Costs
      Total One Time Costs
      Recurring Costs

All costs must be thoroughly detailed. Proposals should be for a fixed price solution.
Costs should be unbundled and separately listed. Proposers should fill out all
appropriate cost pages. Proposals that do not detail specific costs on the forms
provided in this section may be considered non responsive. All cost pages should be
filled out completely.

21.1 Hardware Costs
List all hardware required (servers, workstations, and purchase costs (excluding
installation and freight) and annual maintenance expense. The total dollar figures from
this section should agree with the Hardware total in the Proposer Cost Summary. The
―Annual Maintenance Cost‖ should represent the average maintenance cost for years
two (2) through six (6).

                                                                             Annual
                                                          Total Purchase   Maintenance
   Component Description      Make/Model, Part #    Qty        Cost           Cost



                                   Subtotal


21.2 System Software Costs
List all System software being proposed for the System including total costs and annual
maintenance expense (excluding installation). The total System software cost dollar
figure should agree with the System software total in the Proposer Cost Summary. The
―Annual Maintenance Cost‖ should represent the average maintenance cost for years
two (2) through six (6).


                                                                           May 17, 2007
                                                                               Page 82
                                             Request for Proposal for Integrated CAD System

                                                                                   Annual
                Description              Release/Level            Cost        Maintenance Cost


                                             Total Costs


21.3 Application Software Costs
List all Application Software being proposed including total package cost, customization
cost, and annual maintenance expense for each application (excluding installation).
The total dollar figure should agree with the Application Software total in the Proposer
Cost Summary. The ―Annual Maintenance Cost‖ should represent the average
maintenance cost for years two (2) through six (6).

                                 Number of                 Customization               Annual
                       Package                  Package                    Total
  Application                       User                    Modification             Maintenance
                        Name                     Cost                      Cost
                                  Licenses                     Cost                     Cost

CAD System
CAD
Geofile and
Geofile
Maintenance
EMD Priority
Dispatching
CAD Subtotal
Mobile Computer System Components
MDC Messaging
(Command level
vehicles) (e.g.,
unit-to-unit,
workstation-unit,
etc)
Optional MDC
Messaging (All
vehicles) (e.g.,
unit-to-unit,
workstation-unit,
etc)
Mobile Subtotal
System Interfaces*
Vesta E911
BIO-Key RMS
NetClock
Station Alerting
(SIMS)
Alphanumeric
Paging
GIS/Integrated


                                                                                   May 17, 2007
                                                                                       Page 83
                                                   Request for Proposal for Integrated CAD System

                                      Number of                    Customization                       Annual
                       Package                        Package                            Total
   Application                           User                       Modification                     Maintenance
                        Name                           Cost                              Cost
                                       Licenses                        Cost                             Cost

Mapping
San Bernardino
County Sheriff
CAD System
(Tiburon)
AMR CAD
System (Geac)
Interface Subtotal

* Assumes all costs associated with development, testing and deployment of the defined interface


21.4 Implementation Costs
Describe and list all other costs that would be associated with implementation of your
System. Costs not identified will not be accepted in a final contract.

                                     Item                                                           Cost
Installation of Hardware/Software/Applications                                                     $<xxx>
System Integration of Hardware/Software/Applications                                               $<xxx>
Project Management of Hardware/Software/Applications                                               $<xxx>
Training of Hardware/Software/Applications                                                         $<xxx>
Geofile Build                                                                                      $<xxx>
Data Conversion                                                                                    $<xxx>
Out of Pocket Expenses (Travel, Per Diem, etc.)                                                    $<xxx>
Other: (describe)                                                                                  $<xxx>
Total Implementation Costs                                                                         $<xxx>


21.5 Optional Costs
Describe and list all optional cost items that could be associated with implementation of
the System.

                                   Optional Items                                                   Cost
Incident Management System                                                                         $<xxx>
AVL/Mobile Mapping                                                                                 $<xxx>
Site Licenses                                                                                      $<xxx>
(Other Items)                                                                                      $<xxx>
                                                                                                   $<xxx>
Total Optional Costs                                                                               $<xxx>




                                                                                                   May 17, 2007
                                                                                                       Page 84
                                             Request for Proposal for Integrated CAD System
21.6 Hourly Rates
21.6.1 What hourly rates are proposed as part of this contract? These rates should be
       guaranteed for at least one year from date of contract signing. In addition,
       present rates for each of the following below:

                                      Item                                   Rate/HR
      Analyst                                                                $<xxx>
      Programmer                                                             $<xxx>
      Project Manager                                                        $<xxx>
      Trainer                                                                $<xxx>
      Data Conversion                                                        $<xxx>
      Other                                                                  $<xxx>
                                                                             $<xxx>

21.7 Leasing
CONFIRE is interested in exploring a leasing arrangement for the life of the contract in
addition to flexible payment terms.

21.7.1 Describe your approach to offering financing options and what specific services
       are included as a result of each option.

21.8 Licensing
Include copies of your standard contract and/or licensing agreements for the following:

21.8.1 Hardware Purchase/Lease – Included? (Yes/No) Where located in proposal?

21.8.2 Hardware Maintenance – Included? (Yes/No) Where located in proposal?

21.8.3 Software Purchase/License – Included? (Yes/No) Where located in proposal?

21.8.4 Software Maintenance – Included? (Yes/No) Where located in proposal?

21.9 Total One Time Costs
Provide a summary of all one-time costs for the proposed System. Any subtotals
carried forward to this page should agree with the corresponding detail pages.

                                   Item                                   One Time Cost
Hardware                                                                     $<xxx>
System Software                                                              $<xxx>
Application Software                                                         $<xxx>
Implementation                                                               $<xxx>
Total Not To Exceed One Time Cost (Excluding Options)                        $<xxx>
Subtotal One Time Cost (Options)                                             $<xxx>
Total Not To Exceed One Time Cost (Including Options)                        $<xxx>


                                                                              May 17, 2007
                                                                                  Page 85
                                             Request for Proposal for Integrated CAD System
21.10 Extended Maintenance and Service Warranty Costs
21.10.1 Provide a five year cost schedule that presents the annual cost for an extended
      maintenance and service warranty.

21.10.2 Provide a one time cost for an extended maintenance and service warranty
      over a 5 year period.

21.11 Recurring Costs Summary
Provide a summary of all recurring costs for the proposed System. Any subtotals
carried forward to this page should agree with the corresponding detail pages.

                                     Item                                 One Time Cost
Hardware Maintenance                                                         $<xxx>
System Software Maintenance                                                  $<xxx>
Application Software Maintenance                                             $<xxx>
Other Recurring Costs                                                        $<xxx>
Total Annual Recurring Costs (Excluding Options)                             $<xxx>
Subtotal Recurring Costs (Options)                                           $<xxx>
Total Annual Recurring Costs (Including Options)                             $<xxx>

21.12 Payment Schedule
Proposers are requested to include a copy of their proposed payment schedule.

21.12.1 Is a payment schedule included? (Yes/No) Where is the payment schedule
      located?

21.12.2 In addition to the responses above, Proposers may attach their own cost sheets
      if all requested information is clearly identified. Are cost sheets included?
      (Yes/No) Where are cost sheets located in proposal?




                                                                              May 17, 2007
                                                                                  Page 86
                                     Request for Proposal for Integrated CAD System

Appendix A - Functional Requirements
See separate Microsoft Excel attachment.




                                                                      May 17, 2007
                                                                          Page 87
                                          Request for Proposal for Integrated CAD System

Appendix B - Sample Queries/Reports
The selected System is expected to be able to produce the following queries/reports as
programmed by the Proposer prior to final System acceptance. Additionally, CONFIRE
may request additional queries/reports once the system functionality and interfaces
have been fully developed by the Proposer.

                                    Query/Report Name
 Calls Received By City By Day Of Week
 Calls Received By Dispatch Group By Day Of Week
 Calls Received By Fire Demand Zone By Day Of Week
 Calls Received By Map By Day Of Week
 Calls Received By Incident Type By Day Of Week
 Calls Received By Selected Incident Type By Day Of Week
 Incidents Received By Incident Group By Day Of Week
 Incidents By City By Incident Group By Day Of Week
 Incidents By Dispatch Group By Incident Group By Day Of Week
 Incidents By Fire Demand Zone By Incident Group By Day Of Week
 Incidents By Map By Incident Group By Day Of Week
 Incidents By City By Shift By Incident Group By Day Of Week
 Incidents By Dispatch Group By Shift By Incident Group By Day Of Week
 Incidents By Fire Demand Zone By Shift By Incident Group By Day Of Week
 Incidents By Map By Shift By Incident Group By Day Of Week
 Average Response Time By Priority By Day Of Week For Urban Area
 Average Response Time By Priority By Day Of Week For Rural Area
 Average Response Time By Priority By Day Of Week For Desert Area
 Average Response Time By Priority By Day Of Week For Mountain Area
 Average Response Time By Priority By Hour By Day Of Week
 Average Response Time By Shift By Priority By Day Of Week
 Average Response Time By Shift By Priority
 Average Response Time By City By Shift By Priority By Day Of Week
 Average Response Time By Dispatch Group By Shift By Priority By Day Of Week
 Average Response Time By Fire Demand Zone By Shift By Priority By Day Of Week
 Average Response Time By Map By Shift By Priority By Day Of Week
 Average Response Time By City By Priority By Day Of Week
 Average Response Time By Dispatch Group By Priority By Day Of Week
 Average Response Time By Fire Demand Zone By Priority By Day Of Week
 Average Response Time by Map By Priority By Day Of Week
 Activity Summary Report By Source
 Activity Summary Report By City
 Activity Summary Report By Dispatch Group
 Activity Summary Report By Fire Demand Zone
 Activity Summary Report By Map
 Calls By Incident Group By Date By Hour Of The Day Scatter Diagram
 Calls By Date By Hour Of The Day Scatter Diagram
 Incidents By Date By Hour Of The Day Scatter Diagram


                                                                                 May 17, 2007
                                                                                     Page 88
                                       Request for Proposal for Integrated CAD System
                                   Query/Report Name
Response Time Analysis
Incident Queuing Analysis
Phone and Dispatch Activity
Workload Analysis
Units Fielded Analysis
Travel Time Analysis
Incident History Off-Line Search
Unit History Off-Line Search




                                                                        May 17, 2007
                                                                            Page 89
                                    Request for Proposal for Integrated CAD System

Appendix C - Public Safety Systems Agreement
Public Safety Systems Agreement has been provided in a separate Attachment.




                                                                     May 17, 2007
                                                                         Page 90
                                        Request for Proposal for Integrated CAD System

Appendix D - Definitions
As used in this RFP, unless the context otherwise requires, the following terms shall
have the meanings set out below:
      AD HOC - concerned with a particular end or purpose, formed or used for a
       specific or immediate problem or need.
      ASSUMPTION - fact or statement (as a proposition, axiom, postulate, or notion)
       taken for granted
      AUTOMATIC VEHICLE LOCATION (AVL) – determines the geographic location
       of a vehicle that is overlaid on a CAD mapping program. The location
       coordinates are transmitted via radio and are usually determined using a GPS
       device installed on the vehicle.
      CAD - Computer Aided Dispatch
      CALENDAR DAY - every day shown on the calendar.
      CONFIRE - Consolidated Fire Agencies of the East Valley.
      COUNTY - the County of San Bernardino, California.
      CONTRACTOR, PRIME CONTRACTOR, PROPOSER, or VENDOR - any
       individual, partnership, corporation or joint venture potentially used by CONFIRE
       to perform the services described in this RFP.
      DATA - factual information (as measurement or statistics) used as a basis for
       reasoning, discussion, and calculation.
      DATA CONVERSION - the modification of data structures to comply with new or
       different requirements for the data, changing from one file type to another.
      DATA ELEMENT – the fundamental data structure in a data processing System.
       Any unit of data defined for processing is a data element; for example,
       ACCOUNT NUMBER, NAME, ADDRESS and CITY. A data element is defined
       by size (in characters) and type (alphanumeric, numeric only, true/false, date,
       etc.). A specific set of values or range of values may also be part of the
       definition. Technically, a data element is a logical definition of data, whereas a
       field is the physical unit of storage in a record. For example, the data element
       ACCOUNT NUMBER, which exists only once, is stored in the ACCOUNT
       NUMBER field in each customer record and in the ACCOUNT NUMBER field in
       each order record.
      DELIVERY DATES - all project tasks and associated dates as defined by the
       CONFIRE-approved Project Schedule.
      ERROR - any failure of the SOFTWARE to conform in all material respects to the
       functional specifications that are set forth or defined in this Contract.
      FINAL ACCEPTANCE - that date on which all of the following have taken place:


                                                                           May 17, 2007
                                                                               Page 91
                                     Request for Proposal for Integrated CAD System
       o All hardware, software and System components purchased and/or
         licensed to CONFIRE under the terms of this Contract have been
         successfully installed, tested and accepted by CONFIRE;
       o All software modifications have been successfully completed, tested, and
         accepted by CONFIRE;
       o All user documentation provided to CONFIRE is verified to be complete
         and current with the Systems installed;
       o All user and Systems management training has been completed;
       o All tasks, sub tasks, or components thereof that relate either directly or
         indirectly to this Contract have been completed by the CONTRACTOR;
         and,
       o CONFIRE executes a FINAL ACCEPTANCE document stating that all
         terms and conditions of this Contract have been successfully completed
         by the CONTRACTOR. For purposes of this Section, the terms ―tested
         and accepted‖ shall mean tested and accepted in accordance with the
         testing and acceptance criteria as described in this Contract.
   GRAPHICAL USER INTERFACE (GUI) - An interface that has pictures as well
    as words on the screen. With windows, icons, pull-down menus, and the mouse,
    the graphical user interface is easier to learn and work with.
   HARDWARE - Hardware products that are obtained from hardware
    manufacturers by the Contractor and re sold or licensed to CONFIRE under the
    terms of this Contract.
   INCIDENT MANAGEMENT SYSTEM (IMS) – Defines the roles and
    responsibilities of fire and EMS personnel as well as recommends incident
    operating procedures.
   INTEGRATED - a System where data is entered once and is, thereby, available
    in other application modules within CAD, RMS, and MDS without re-keying.
   INTERFACE - the connection and interaction between hardware, software and
    the user. Users "talk to" the software. The software "talks to" the hardware and
    other software. Hardware "talks to" other hardware. All this is interfacing. It has
    to be designed, developed, tested and redesigned; and with each incarnation, a
    new specification is born that may become yet one more de facto or regulated
    standard.
   NATIONAL FIRE INCIDENT REPORTING SYSTEM (NFIRS) – Managed
    through the Homeland Security Department the United States Fire Administration
    gathers and analyzes information as well as provides reports on fire incidents.
    NFIRS has two objectives, with the first to help state and local governments
    develop fire reporting and analysis capabilities. The second objective is to collect
    data from local governments in order to more accurately assess and combat the
    fire problem at the national level.
   PROPOSAL - the document submitted by Proposers in response to this RFP.



                                                                         May 17, 2007
                                                                             Page 92
                                     Request for Proposal for Integrated CAD System
   PROPOSER APPLICATION SOFTWARE - all or any portion of the Proposer‘s
    computer software programs proposed.
   PROPOSER PERSONNEL, PROJECT MANAGER, or TRAINER - personnel
    resources provided by the Proposer or its sub-contractors to support the
    implementation of any element defined and acquired through this RFP.
   QUERY- to interrogate a collection of data such as records in a database in order
    to obtain lists of records that match the search criteria, count items or sum
    amounts. Also often called a "search."
   REAL TIME - as fast as required. A real time System must respond to a signal,
    event or request fast enough to satisfy some requirement. Real time often refers
    to process control and embedded Systems.
   SEARCH - to uncover, find, or come to know by inquiry or scrutiny to look or
    inquire carefully.
   SERVICES - the professional and technical work provided by the Proposer to
    effect the implementation of hardware and software, and the provision of training
    and documentation for those elements.
   SOFTWARE - all of the software, collectively, proposed to meet the requirements
    of this RFP.
   SOURCE CODE - the original code from which the final object (machine
    language or final) code of the computer software programs proposed is derived.
   SUB-CONTRACTOR - any individual, partnership, corporation or joint venture
    engaged by the PRIME CONTRACTOR to perform SERVICES. All assigned
    contract services for this project will be governed by the same rules and
    regulations outlined in this RFP, be based on approval of CONFIRE and be the
    sole responsibility of the PRIME CONTRACTOR.
   SYSTEM - the totality of the prescribed hardware configuration or software
    elements, including subsystems, servers, workstations, applications and
    operating software, and any other element defined and acquired through this
    RFP, except services.
   SYSTEM COMPONENT - any subset of the entire SYSTEM proposed (e.g.,
    CAD, MDC).
   SYSTEM DOWNTIME - the time during which a computer is not functioning due
    to hardware, operating System or application program failure.
   THIRD PARTY APPLICATION SOFTWARE or THIRD PARTY SOFTWARE -
    APPLICATIONS shall mean any software product that is purchased or licensed
    from any source external to the Contractor, e.g., distributor, re seller, personal
    computer software supplier or System software supplier, and re-sold or licensed
    to CONFIRE under the terms of this Contract.
   UNIT BASED DISPATCH - the System should recommend one or more fire
    apparatus (single resources) based on apparatus kind (defined as specific

                                                                         May 17, 2007
                                                                             Page 93
                                Request for Proposal for Integrated CAD System
classification of apparatus based on overall function) and type (defined as a
specific kind of apparatus which meets predetermined performance
specifications based on apparatus capabilities and associated staffing) from a
user defined list. System should be able to recommend apparatus closes and
most directly routable to a specific scene location based on known quarters,
operational area, or AVL position.




                                                                   May 17, 2007
                                                                       Page 94
                                        Request for Proposal for Integrated CAD System

Attachment 1 - Escrow Agreement
CONTRACTOR agrees to deliver in a sealed package a copy of the Source Code for
the computer software supplied, pursuant to the terms of this Agreement, to Escrow
Agent, ____________________________________________________.
The sealed package containing the Source Code shall be so marked. If any
modifications are contracted in the future, Source Code for these modifications shall be
placed in escrow and marked with the name of CONFIRE.
In the event CONTRACTOR ceases doing business, becomes insolvent or is unable to
support the software for any reason, or a bankruptcy proceeding is filed by or against
CONTRACTOR, and such proceedings are not dismissed within 60 days, or fails to
meet its obligations for providing software support as defined in Exhibit F (Computer
Software Support Agreement), the Escrow Agent, upon the written demand of
CONFIRE, shall release the Source Code to CONFIRE, provided that the Escrow Agent
shall first give CONTRACTOR written notice of such demand.
The release of the Source Code by the Escrow Agent to CONFIRE shall be solely for
the purpose of enabling CONFIRE to use and maintain the software for their own
internal use, and CONTRACTOR hereby grants to CONFIRE a paid up, royalty free,
non exclusive license to use and modify the Source Code for such purposes and for no
other. Under no circumstances shall CONFIRE be authorized to use such software or
license others to use the same for any purpose other than the internal needs of
CONFIRE.
The responsibilities of the Escrow Agent are limited solely to the receipt and custody of
the sealed packages containing the Source Code, the receipt of any notices from
CONFIRE relating to the items in 3 above and the delivery of the sealed packages
containing the Source Code to CONFIRE as contemplated by this Agreement.
Within 30 days of Final Acceptance or full payment, whichever is later, CONTRACTOR
agrees to deliver Source Code for the installed version of the products to the Escrow
Agent. CONTRACTOR will require that Escrow Agent to notify CONFIRE in writing
within 30 days of receipt of the Source Code.
CONTRACTOR will update Source Code no less frequently than annually, or at each
new release of the Source Code, at its expense, after the initial delivery of Source Code
to the Escrow Agent.
CONFIRE may verify the validity of Source Code at their expense at any time.
CONFIRE shall assume responsibility for any CONTRACTOR expenses associated
with the verification process.
Source code may also be purchased as an option.




                                                                            May 17, 2007
                                                                                Page 95
                                    Request for Proposal for Integrated CAD System

Attachment 2 - Correspondence
All correspondence generated between the CONFIRE and Proposer to be attached in
chronological order.




                                                                     May 17, 2007
                                                                         Page 96
                                     Request for Proposal for Integrated CAD System

Attachment 3 - Hardware and Network Configuration Specifications
(Proposer to attach with Proposal)




                                                                      May 17, 2007
                                                                          Page 97
                                     Request for Proposal for Integrated CAD System

Attachment 4 - Services Detail
(Proposer to attach with Proposal)

Project Management
Onsite Days                                 # of Trips




Hardware/Software Installation
Onsite Days                                 # of Trips




Training
Classes/Subjects      # Students       Students/Class     Hours/Days      Total
                      to be                               Class           Hours/
                      Trained                                             Days




Other Services




                                                                       May 17, 2007
                                                                           Page 98
                                     Request for Proposal for Integrated CAD System

Attachment 5 - Computer Software Support Agreement
(Proposer to attach with Proposal)




                                                                      May 17, 2007
                                                                          Page 99
                                     Request for Proposal for Integrated CAD System

Attachment 6 - Preliminary Project Schedule and Personnel
(Proposer to attach with Proposal)




                                                                      May 17, 2007
                                                                         Page 100
                                     Request for Proposal for Integrated CAD System

Attachment 7 - Preliminary Test Plan
(Proposer to attach with Proposal)




                                                                      May 17, 2007
                                                                         Page 101
                                     Request for Proposal for Integrated CAD System

Attachment 8 - Preliminary Implementation Plan
(Proposer to attach with Proposal)




                                                                      May 17, 2007
                                                                         Page 102
                               Request for Proposal for Integrated CAD System

Attachment 9 - Computer Hardware Maintenance Agreement
(To be provided by Proposer)




                                                                May 17, 2007
                                                                   Page 103

				
DOCUMENT INFO