Napa RFP by wangping12

VIEWS: 3 PAGES: 58

									                                         City of Seattle
                                     Request for Proposal
                                        RFP No. 1547
                             TITLE: Sonic Enterprise Service Bus
                                   Application Integration
                                       Implementation
                          Closing Date & Time: 4:00 PM, PDT 5/2/05

                        Schedule of Events                                      Date
                         RFP Release date                                     3/21/05
                   Pre-Proposal Teleconference                                 4/1/05
               Telephone Bridge Line: Contact RFP                     10:00 a.m. – 1:00 p.m.,
            Coordinator at: Message/Switch@seattle.gov                          PST

              Deadline to Submit Questions and Request                         4/20/05
                              Addenda
                   Sealed Proposal Due to the City                    5/2/05 (4:00 P.M. PDT)
                City Evaluation of Proposals, Vendor                   5/2/05 – 6/3/05 (est.)
                             Interviews
               Announcement of Successful Vendor(s)                         6/10/05 (est.)
                (Refer to Website for announcement)

The City reserves the right to modify this schedule at the City’s discretion. Notification of changes in the
          response due date would be posted on the City website or as otherwise stated herein.

   PROPOSALS MUST BE RECEIVED ON OR BEFORE THE DUE DATE AND TIME AT THE FOLLOWING
                                      LOCATION:
        If delivered by the U.S. Postal Service, it must be addressed to:

                     Vivian Uno
                     City of Seattle Purchasing and Contracting Services
                     PO Box 94687
                     Seattle, WA 98124-4687

        If delivered by any other delivery service, it must be addressed to:

                     Vivian Uno
                     City of Seattle Purchasing and Contracting Services
                     Seattle Municipal Tower
                     700 5th Ave., #4112
                     Seattle, WA 98104-5042
   Vendors are required to read and understand all information contained within this entire Proposal
   package. By responding to this RFP, the Vendor agrees to read and understand these documents.
                                     SEATTLE POLICE DEPARTMENT

                 INFORMATION DISPATCH AND REPORTING SYSTEM

                                     REQUEST FOR PROPOSAL
                                              FOR
                                  SONIC ENTERPRISE SERVICE BUS
                                    APPLICATION INTEGRATION
                                        IMPLEMENTATION



                                               TABLE OF CONTENTS



SECTION                                                                                                                 PAGE



  CHAPTER ONE – RULES OF PREPARATION

  1. INTRODUCTION AND PURPOSE ......................................................................1

  2. BACKGROUND AND SCOPE OF WORK. .......................................................1

  3. PROJECT OBJECTIVES AND SOLICITATION OBJECTIVES. ..................3

  4. MINIMUM QUALIFICATIONS. ..........................................................................4

  5. ADMINISTRATIVE REQUIREMENTS & INFORMATION..........................4

  Proposal Procedures and Process ................................................................................4

  Process Overview...........................................................................................................4

  Communications with the City .....................................................................................5

  Pre-Proposal Teleconference .......................................................................................5

  Questions .......................................................................................................................6

  Changes to the RFP/Addenda ......................................................................................6

  City Publication of Addendum and Materials .............................................................6
Requirement for Receiving Appendices / Non-Disclosure Agreement .......................6

Proposal Response Date and Location .........................................................................7

No RFP Opening – No Reading of Prices. ..................................................................7

Number of Copies Required .........................................................................................7

Certification of Proposals .............................................................................................8

Vendor Questionnaire ...................................................................................................8

Taxpayer Identification Number and W-9 ...................................................................8

Equal Benefits ...............................................................................................................8

WMBE Sub-contracting Outreach and Recruitment Commitment: ..........................9

Contract Terms and Conditions ...................................................................................9

Insurance Requirements ...............................................................................................9

Performance Bond ........................................................................................................9

Prohibition on Advance Payments .............................................................................10

Partial and Multiple Awards.......................................................................................10

All or None Bid. ..........................................................................................................10

Seattle Business Tax Revenue Consideration ............................................................10

Taxes... .........................................................................................................................10

Business Licensing......................................................................................................10

Inter-local Purchasing Agreements ...........................................................................11

Affirmative Efforts for Women and Minority Subcontracting..................................11

Proprietary Proposal Material ....................................................................................12

Cost of Preparing Proposals .......................................................................................12

Vendor Responsibility .................................................................................................12

Changes in Proposals..................................................................................................12

Errors in Proposals .....................................................................................................13
Withdrawal of Proposal ..............................................................................................13

Rejection of Proposals and Rights of Award .............................................................13

Incorporation of RFP and Proposal in Contract.......................................................13

No Gifts and Gratuities. ..............................................................................................13

Involvement of Former City Employees. ....................................................................13

No Conflict of Interest. ...............................................................................................14

Protests and Complaints .............................................................................................14

Proposal Disposition ...................................................................................................14

Negotiating is Acceptable............................................................................................14

Negotiation Time Limit and Contract Signature Response Time .............................14

6. PROPOSAL FORMAT AND ORGANIZATION .............................................14

General Format ...........................................................................................................15

Response Format.........................................................................................................15

Readability ...................................................................................................................15

7. EVALUATION PROCESS ..................................................................................15

CHAPTER TWO - CURRENT ENVIRONMENT

TECHNOLOGY OVERVIEW ...................................................................................1

Overview ........................................................................................................................1

Network Infrastructure .................................................................................................1

Hardware .......................................................................................................................1

Software – Operating Systems ......................................................................................2

Mobile Data ...................................................................................................................3

Software – Mobile Application Environment ..............................................................3

Software – Applications ................................................................................................4
CHAPTER THREE - VENDOR RESPONSE

Introduction...................................................................................................................1

Objectives of this Section ..............................................................................................1

A.      Vendor Services Overview .................................................................................2

B.      Vendor Experience ..............................................................................................7

C.      Interfaces..............................................................................................................8

D.      Warranty............................................................................................................10

E.      Financial Proposal .............................................................................................12

F.     Exceptions to Terms and Conditions ...............................................................17

CHAPTER FOUR - SPECIFICATION RESPONSE

A.         Deliverables.......................................................................................................1

B.         Training ............................................................................................................3

C.         Documentation .................................................................................................4

D.         Implementation ................................................................................................5

INDEX OF APPENDICES .......................................................................................10

APPENDICES ............................................................................................................10

A.         ADMINISTRATIVE........................................................................................10

B.         TECHNICAL ..................................................................................................11
     Chapter 1




Rules of Preparation
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation




   1
 Chapter




Rules of Preparation


1. INTRODUCTION AND PURPOSE



 Through this Request for Proposal (RFP), the City of Seattle (City) Police Department (SPD) is
 soliciting proposals for Sonic Software Enterprise Service Bus (SONIC ESB) application
 integration implementation services from interested and qualified Vendors.

 SPD has embarked on a major effort to achieve data interoperability and integration both within
 its own systems and with its many local, regional, and federal partners. These efforts are based on
 several key principles:

            Moving to standards based systems and exchanges
            Maximizing system reliability and security
            Facilitating timely access to accurate information
            Facilitating coordination and the exchange of information with other agencies and
             jurisdictions

 2. BACKGROUND AND SCOPE OF WORK.
 SPD first documented its conceptual approach to this integration and interoperability in a
 Message Switching Strategy in 2002. Central to SPD’s continuing effort is the acquisition and
 implementation of the SONIC ESB for independent message brokering ability for the many
 desired and anticipated interfaces to its CAD, RMS and Mobile systems.

 In a separate procurement process under the SPIDER Project, SPD is currently seeking to acquire
 a law enforcement technology solution comprised of four integrated applications:

 Computer Aided Dispatch (CAD)

 Mobile CAD

 Records Management System (RMS)

 Mobile RMS / Automated Field Reporting (AFR)




                                                                                                 1-1
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation


While SPD recognizes that some interfaces may appropriately remain in the “historic” mode of
“point-to-point interfaces” into the CAD or RMS applications (e.g., CAD to ANI/ALI), it is our
expectation that the majority of interfaces listed below and detailed in Appendices B.1 Interface
Profile Report and B.5 System Connection Architecture, will interface to the SONIC ESB and
from there to CAD or RMS as pictorially represented in the embedded figure (see left).

The City desires to hire a qualified Vendor to implement the SPIDER interface integration
solution (SONIC ESB), including the development and implementation of adapters/connectors
between SPD’s new Computer Aided Dispatching (CAD), Records Management System (RMS),
and Mobile System and additional information systems/switches (as listed below), to facilitate
timely and accurate data message exchanges.

        1) RMS – King County (includes former SeaKING)
        2) RMS - CAD
        3) RMS - SMTP
        4) RMS - ACCESS
        5) RMS - MDC
        6) RMS - AFR
        7) CAD - MDC
        8) CAD - ACCESS
        9) CAD - SMTP
        10) CAD – King County (includes former SeaKING)
        11) MDC - AFR
        12) MDC - ACCESS
        13) RMS - SEAJIS
        14) RMS - LINX
        15) RMS - RAIN
        16) RMS - AUTOCITE
        17) RMS - TOWS
        18) CAD - TOWS
        19) CAD- FIRECAD


To complete this procurement, the City seeks a Vendor (or Vendors) that will provide an effective
and carefully structured approach to implementing interfaces. In this context, implementation
refers to all efforts required to provide all requisite Adapters (Connectors), all requisite Message
Exchanges, and to prepare SPD to use the SONIC ESB effectively. Implementation efforts
include: developing, refining, documenting, testing, and implementing Adapters/Connectors and
Message Exchanges using SONIC ESB, staff training, end user and technical documentation,
project management, and warranty of implemented Message Exchanges and Connectors. As a
result of this acquisition the City expects to implement a contract(s) for SONIC ESB integration
implementation services.


                                                                                                1-2
                                        SPIDER Project – Integration Implementation Services
                                                           Chapter 1: Rules of Preparation




3. PROJECT OBJECTIVES AND SOLICITATION OBJECTIVES.


  (1)   The objectives for the message broker implementation are to:
               Meet the requirements, as defined in this procurement document.
               Advance the overall mission, goals objectives and strategies of SPD by making
                personnel more effective in responding to, fighting, and preventing crime, and
                should enhance the development of relationships in the community.
               Position SPD to take advantage of technology to improve departmental
                performance and efficiency.
               Enhance the quality, accuracy and retrievability of data and operate on the
                principles of “single point of data entry” and “single point of data query”.
               Facilitate bi-directional integration with other applications/switches to improve
                the timeliness and accuracy of information in the information exchange process.
               Increase authorized recipients’ access to appropriate information, regardless of
                the system in which the information resides through real-time data exchanges.
               Provide a high level of availability, security, and reliability.
               Implement an infrastructure that is scaleable and can be built upon for future data
                exchanges, allowing SPD to meet current and future needs without extensive
                customization.
               Develop and execute a City employee knowledge transfer plan, including
                utilization of a proven integration implementation methodology that can be
                learned by Department Staff in any integration effort.

  (2)   Objectives specific to procurement of integration implementation services include
        entering a relationship with a Vendor that:

               Is a Sonic Certified Partner
               Has a history of successful implementation of comparable projects with
                agencies of similar size and complexity as the City.
               Has a long-term commitment to business in the United States.
               Has long-term viability as a company.
               Has qualified and experienced project staff to assign to the City's project for
                the duration of the entire project.
               Shows confidence in its ability to successfully complete the work by
                invoicing only at approved milestones. Invoices shall represent the delivery
                of products or services that are of value to the City. The City expects that
                larger payments will be associated with the milestones that occur in the latter
                stages of the project.


                                                                                               1-3
                                             SPIDER Project – Integration Implementation Services
                                                                Chapter 1: Rules of Preparation



 The City desires to procure the most appropriate services within its financial means from a qualified
 Vendor, for the deliverables in Chapter 4: “Implementation and Deliverables Specification Response”



 4. MINIMUM QUALIFICATIONS.

 The following are minimum qualifications that the Vendor must meet in order to be eligible to
 submit a Proposal. Responses must clearly show compliance to these minimum qualifications in
 order to be found responsive. Those that are not clearly responsive may be rejected by the City
 without further consideration:

        Must be a Sonic Certified Partner




5. ADMINISTRATIVE REQUIREMENTS & INFORMATION.

 Proposal Procedures and Process

 This chapter details City procedures that the City has established for managing and directing the
 RFP process. The purpose of these procedures is to ensure that the City receives proposals
 through a fair and competitive process. These procedures are also designed to help Vendors
 receive fair and equitable treatment in the solicitation, receipt and review of their proposals. In
 the event of an ambiguity in the RFP, the ambiguity shall be interpreted with these purposes in
 mind.
 Process Overview

 The City will use a multi-phase selection process for this acquisition as described in the Proposal
 Evaluation section later in this Chapter. Following selection of an apparent finalist, the City will
 continue with that finalist to prepare a Statement of Work (SOW) and initiate negotiations to
 develop a Purchase Contract. As part of the negotiations phase, the City intends to engage the
 selected Vendor in a requirements effort that will be detailed enough to identify and quantify all
 known risks and consequently allocate risk to both parties in the resultant contract.

 The RFP is organized as follows:

 Chapter One - Rules of Preparation: This volume includes information regarding the
 objectives, the procurement process, the City's standard terms and conditions, and a description of
 the proposal evaluation methodology.

 Chapter Two - Current Environment: This Chapter provides information on the current state of
 SPD information technology systems, including relevant standards. Where appropriate, future
 directions are also noted.

 Chapter Three - Vendor Response: The general specification requirements for the management
 and financial proposals.


                                                                                                  1-4
                                           SPIDER Project – Integration Implementation Services
                                                              Chapter 1: Rules of Preparation


Chapter Four – Implementation and Deliverables Specification Response: This Chapter includes
detailed information and requirements for the deliverables, from development through training,
implementation, and acceptance testing.

Appendix: Additional information is provided for the benefit of the Vendors including forms
which must be completed.

Communications with the City

All Vendor communications concerning this acquisition shall be directed to the RFP Coordinator
at the RFP mailbox below. The RFP Coordinator is:
                   Vivian Uno
                   Phone: 206-684-0449
                   Fax: 206-233-5155
                   E-Mail: MessageSwitch@seattle.gov

Unless authorized by the RFP Coordinator, no other City official or City employee is empowered
to speak for the City with respect to this acquisition. Any Vendor seeking to obtain information,
clarification, or interpretations from any other City official or City employee other than the RFP
Coordinator is advised that such material is used at the Vendor’s own risk. The City will not be
bound by any such information, clarification, or interpretation. Further, any attempt by a vendor
to obtain information regarding this acquisition from anyone other than the RFP Coordinator may
be grounds for rejection of the vendor’s proposal.

The Vendor may obtain status of the project on the City website at
http://www.seattle.gov/purchasing/ and/or
http://www.seattle.gov/html/business/rfp/SPD1547/.

Pre-Proposal Teleconference

The City of Seattle will conduct an optional pre-proposal teleconference for this RFP. Vendors
that wish to submit a response to this RFP are invited and strongly encouraged to
participate in the pre-proposal teleconference. Vendors should contact the RFP Coordinator to
address any questions they might have regarding the teleconference. Vendors should also notify
the RFP Coordinator of their intention to participate in the teleconference:
                                  Phone Number: 206-684-0449
                           E-mail Address: MessageSwitch@Seattle.gov

Details regarding the pre-proposal teleconference are as follows:
         Date:                April 1, 2005
         Time:                10:00 a.m. – 1:00 p.m., PDT
         Bridge-Line          Contact the RFP Coordinator at
                              MessageSwitch@Seattle.gov to receive the
                              telephone conference bridge information

The purpose of the meeting is to answer questions potential Vendors may have regarding the
solicitation document and to discuss and clarify any issues. This is an opportunity for Vendors to
raise concerns regarding specifications, terms, conditions, and any requirements of this



                                                                                               1-5
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation


solicitation. Failure to raise concerns over any issues at this opportunity will be a consideration
in any protest filed regarding such items that were known as of this pre-proposal conference.

To get the most value from this pre-proposal teleconference, the City recommends that Vendors
have a team participate in this teleconference. For example, the conference team might include an
account executive, a project manager, and a technical expert that has significant knowledge of
Implementation of the SONIC ESB Solution.

Vendors are encouraged to submit questions or comments, or make requests for information or
clarifications prior to the pre-proposal teleconference. Vendors who have specific questions or
comments that they would like addressed at the vendor teleconference should send them to the
RFP Coordinator via e-mail (MessageSwitch@Seattle.gov) at least three (3) days prior to the
teleconference. Vendors may also ask questions, make comments, or request information during
the pre-proposal teleconference.

Questions

Questions shall be submitted electronically to the RFP Coordinator via e-mail
(MessageSwitch@Seattle.gov) no later than the date and time given on page 1. Failure to request
clarification of any inadequacy, omission, or conflict will not relieve the vendor of any
responsibilities under this solicitation or any subsequent contract. It is the responsibility of the
interested Vendor to assure that they received responses if any are issued. The City anticipates,
but does not guarantee, that answers to questions, if any will be issued no later than 7 days prior
the proposal due date.

Changes to the RFP/Addenda
A change to this RFP will be made by a formal written addendum issued by the City’s Buyer. A
change may be made by the City if, in the sole judgment of the City, the change will not
compromise the City’s objectives in this acquisition. Addenda issued by the City shall become
part of this RFP and included as part of the Contract. Addenda will be posted on the City’s RFP
website located at: http://www.seattle.gov/html/business/rfp/SPD1547/. It will be the Vendor’s
responsibility to check the City’s website for updates. The City anticipates, but does not
guarantee, that addenda, if any, will be issued no later than 7 days prior to the proposal due date.

City Publication of Addendum and Materials

The City will make notices, reminders, addenda and similar announcements available on the City
website. The City website for this RFP and related documents is:
http://www.seattle.gov/html/business/rfp/SPD1547/

It remains the obligation and responsibility of the Vendor to learn of any addenda, responses, or
notices issued by the City. Such efforts by the City to make the information available on the
website, does not relieve the Vendor from the sole obligation for learning of such material.
Requirement for Receiving Appendices / Non-Disclosure Agreement

Administrative appendices are made available to all Vendors. To access the Technical
appendices, Vendors must provide a signed Non-Disclosure Agreement (see Appendix A.4).




                                                                                                  1-6
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation


Proposal Response Date and Location

Proposals must be received into the City Purchasing Offices no later than the date and time given
on page 1.

    a) Responses should be in a sealed box or envelope clearly marked and addressed with the
        RFP Coordinator, RFP title and number. If RFP’s are not clearly marked, the Vendor has
        all risks of the RFP being misplaced and not properly delivered. The RFP Coordinator is
        not responsible for identifying responses submitted that are not properly marked.

    c) The RFP response may be hand-delivered or must otherwise be received by the RFP
       Coordinator at the address provided, by the submittal deadline. Please note that delivery
       errors will result without careful attention to the proper address.

         If the proposal is delivered by the U.S. Postal Service, it must be addressed to:

                     Vivian Uno
                     City of Seattle Purchasing and Contracting Services
                     PO Box 94687
                     Seattle, WA 98124-4687

         If the proposal is delivered by any other company, it must be addressed to:

                     Vivian Uno
                     City of Seattle Purchasing and Contracting Services
                     Seattle Municipal Tower
                     700 5th Ave., #4112
                     Seattle, WA 98104-5042.

    b) The Vendor has full responsibility to ensure the proposal arrives to the City Purchasing
         Office within the deadline. The City assumes no responsibility for delays caused by the
         US Post Office or any other delivery service. Postmarking by the due date will not
         substitute for actual receipt of response by the date due. Proposals will be opened after
         the due date and time. Responses arriving after the deadline may be returned, unopened,
         to the Vendor, or may simply be declared non-responsive and not subject to evaluation,
         or may be found to have been received in accordance to the solicitation requirements, at
         the sole determination of Purchasing.

No RFP Opening – No Reading of Prices.

The City of Seattle does not conduct a bid opening for RFP responses. The City requests that
companies refrain from requesting proposal information concerning other respondents until an
intention to award is announced, as a measure to best protect the solicitation process, particularly
in the event of a cancellation or re-solicitation. With this preference stated, the City shall
continue to properly fulfill all public disclosure requests for such information, as required by
State Law.

Number of Copies Required
Vendor shall provide the following copies of their proposal:


                                                                                                  1-7
                                           SPIDER Project – Integration Implementation Services
                                                              Chapter 1: Rules of Preparation



   One (1) paper original (marked as Original)
   Three (3) paper copies
   One (1) disk (3.5 inch floppy or CD) containing an electronic version of the Vendor’s
    proposal
   Three (3) full sets of reference materials associated with the proposed system (If reference
    materials associated with the proposed system(s) are provided)

Certification of Proposals
The Vendor shall certify that its proposal meets mandatory requirements, contains required
documents, and is valid until the City completes award and contract signature with a winning
Vendor. Appendix A.6 contains the Proposal Certification form which must be submitted with
vendor’s proposal. The Proposal Certification form in Appendix A.6 must be signed by an
authorized person to bind the Vendor. The City may require proof from the Vendor that the
person or persons who signed the certification is/are in fact authorized to make this commitment.
Vendor’s Certification must remain valid until City completes award. Should any Vendor object
to this condition, the Vendor must provide objection through a question and/or complaint to the
Buyer prior to the proposal due date.

Vendor Questionnaire
The Vendor is to supply complete and submit the Vendor Questionnaire (Appendix A.8) as part
of the submittal. If failing to do so or information is incomplete, the City may request the Vendor
to supply the missing material, and provide a due date for response. Failing to respond to such
request in the due date given, the City may reject the submittal as not responsible or the City may
waive missing information as immaterial to award.

Taxpayer Identification Number and W-9

Unless the apparently successful Vendor has already submitted a fully executed Taxpayer
Identification Number and Certification Request Form (W-9) to the City, the apparently
successful Vendor must execute and submit this form prior to the contract execution date. A
copy of the Taxpayer Identification Number and Certification Request Form (W-9) is available in
Appendix A.10. The Vendor may execute the W-9 and provide it with their proposal.

Equal Benefits

Vendors are to submit an Equal Benefits Form (Attachment A.3) with their proposal. If not
submitted, the City may immediately request submittal and retains the right to reject the Proposal
as an issue of responsibility. If a Vendor does not offer Equal Benefits and does not intend to do
so, this does not automatically eliminate the Vendor from award consideration. However, failure
to submit the Form itself can result in finding of not responsible.
Equal Benefit forms are mandatory per Seattle Municipal Code 20.45. Compliance to the Equal
Benefits statements made by the Vendor is required through the duration of the Contract. If the
Vendor indicates that the Vendor provides Equal Benefits, and then fails to continue offering
such benefits compliant to SMC 20.45 throughout the duration of the contract, this can be cause
for termination of the contract. Equal Benefit Forms may be audited at any time prior to contract
award or at during the contract.



                                                                                                   1-8
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation


Information about the Equal Benefit requirements is available at the City website:
http://www.cityofseattle.net/contract/equalbenefits/default.htm
Notwithstanding anything seemingly to the contrary herein, Vendors may contact Sheila Prieur,
the City of Seattle Equal Benefits Manager (206-733-9583), for information regarding this
requirement. All other questions regarding this RFP must be directed to the City’s RFP
Coordinator.
WMBE Sub-contracting Outreach and Recruitment Commitment:

If Vendor will be subcontracting elements of the work in its proposal, Vendor shall provide a
discussion of the affirmative efforts that the Vendor proposes to achieve women and minority
business participation, Consistent with SMC 20.42. This response shall be evaluated for
commitment to such opportunities. Upon agreement with the City, the response shall be
incorporated within the contract as a contract obligation. (See Appendix A.9)

Contract Terms and Conditions

Vendors should carefully review the terms and conditions and respond to each section as
instructed in Appendix A.7. Vendors should assume full compliance to the City’s terms and
conditions in submitting a proposal. Submittal of a response will serve as agreement to all the
City terms and conditions as attached. However, Vendors may request exceptions as part of their
submittal. The City will consider exceptions proposed by the Vendor and may agree to such
exceptions as part of contract negotiations. Exceptions requested by Vendors should be
substantially similar to the City terms and conditions.
.

Insurance Requirements

Insurance requirements presented in the Contract Terms and Conditions are mandatory. Vendors
are encouraged to immediately contact their Broker to begin preparation of required insurance
documents, in the event that the Vendor is selected as a finalist. Vendors may elect to provide the
requested insurance documents within their submittal. The successful Vendor must provide proof
of insurance to the City in reply to the Intent to Award letter. Contracts will not be executed until
all required proof of insurance has been received and approved by the City.

 Vendors shall respond to all inquiries by the City for insurance documents and/or corrections to
those documents to meet the needs of the City, in a prompt manner. Vendors shall be allowed
five (5) business days to provide documents and/or corrections following receipt of the Intent to
Award or other request by the City. The City retains the right to reject the Proposal and proceed
to the next finalist if the successful Vendor fails to respond within the deadlines.

Performance Bond
The successful Vendor will be required to furnish a contract (performance), bond or a letter of
credit as approved by the City, in an amount equivalent to or less than the contract price plus
sales or use tax, at the time the Contract is signed and returned to the City. The contract bond
percentage may be negotiated with the successful Vendor. The approved bond form as well as
instructions and Principal Identification form are included for information as Appendix A.1, A.2
and A.5.




                                                                                                 1-9
                                              SPIDER Project – Integration Implementation Services
                                                                 Chapter 1: Rules of Preparation


Prohibition on Advance Payments

State law prohibits the City from paying in advance for goods and services. No request for early
payment, down payment or partial payment of a deliverable will be honored. Payment shall be
made only upon receipt/acceptance of deliverables. Maintenance may be paid up to one year in
advance provided that should the City terminate early, the amount paid shall be reimbursed to the
City on a prorated basis. All other expenses are payable net 30 days after receipt and acceptance
of satisfactory compliance.

Partial and Multiple Awards

Unless stated to the contrary in the Scope of Work, the City reserves the right to name a partial
award, in the best interest of the City. Vendors are to prepare proposals given the City’s right to
a partial award. If Vendor is submitting an All or None offer, such offer must be clearly marked
as All or None. Further, the City may eliminate an individual line item when calculating award,
in order to best meet the needs of the City, if a particular line item is not routinely available or is a
cost that exceeds the City funds. For Proposals, the City may negotiate with the successful
Vendor, to provide a scope of work that best meets the City needs.



All or None Bid.

All or None bids do not generally apply to an RFP. However, should a Vendor be submitting an
All or None offer, such stipulation must be clearly marked in the proposal, or the City may utilize
the City right to otherwise conduct a partial award. The City may calculate proposals based on a
partial award.


Seattle Business Tax Revenue Consideration

SMC 3.04.106 (H) authorizes that in determining the lowest and best proposal, the City shall take
into consideration the tax revenues derived by the City from its business and occupation or utility
taxes and its sales and use taxes from the proposed purchase. Businesses         that are located and
licensed within the Seattle City limits are eligible for Seattle tax consideration for purposes of
calculation of low offer. This shall be equivalent to a reduction of the cost for purposes of
evaluation only, of .0088.

Taxes.

The City is exempt from Federal Excise Tax (Certificate of Registry #9173 0099K exempts the
City). Washington state and local sales tax will be an added line item.

Business Licensing

As required by laws and regulations, successful Vendor shall furnish a valid UBI number and
Seattle Business license. All costs for any licenses and permits shall be borne by the Contractor and
not charged separately to the City.




                                                                                                    1-10
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation


Inter-local Purchasing Agreements

This is for information only, and shall not be used for evaluation. The City has entered into Inter-
local Purchasing Agreements with other governmental agencies, pursuant to RCW 39.34. By
submitting a proposal, the Vendor agrees to sell additional items at the offer prices, terms and
conditions, to other eligible governmental agencies that have such agreements with the City. The
City of Seattle accepts no responsibility for the payment of the purchase price by other
governmental agencies. Should the Vendor require additional pricing for such purchases, the
Vendor is to name such additional pricing upon Offer to the City.

Affirmative Efforts for Women and Minority Subcontracting

Under SMC 20.42.010, the City finds that minority and women businesses are significantly
under-represented and have been underutilized on City Contracts. Additionally, the City does not
want to enter into agreements with businesses that discriminate in employment or the provision of
services. The City intends to provide the maximum practicable opportunity for increased
participation by minority and women owned and controlled businesses, as long as such businesses
are underrepresented, and to ensure that City contracting practices do not support discrimination
in employment and services when the City procures public works, goods, and services from the
private sector. The City shall not enter into Contracts with contractors that do not agree to use
Affirmative Efforts as required under SMC Chapter 20.42 or violate any provisions of that
chapter, or those requirements given below.

As a condition of entering into a contract with the City, Vendors must agree to take affirmative
efforts to assure equality of employment, and subcontracting opportunities when subcontracting is
required to fulfill the work required within the scope of work for the Contract. Such affirmative
efforts may include, but are not limited to, establishing employment goals for women and
minorities and establishing goals for subcontracting to Women and Minority Businesses.

Contractors entering into Contracts shall actively solicit the employment of women and minority
group members. For Contracts that require subcontracting in order to fulfill the scope of work,
Contractors shall actively solicit bids for subcontracts to qualified, available, and capable Women
and Minority Businesses to perform commercially useful functions. At the request of the City,
Contractors shall furnish evidence of the Contractor's compliance with these requirements to
document: 1) Affirmative Efforts to employ women and minority group members; 2) Affirmative
Efforts to subcontract with Women and Minority Businesses on City Contracts; and 3) the
Contractor’s non-discrimination in the provision of goods and services.

The City provides assistance to Vendors that desire to bid on, or have been awarded a City
Contract, to comply with these equal opportunity, non-discrimination, and affirmative efforts
provisions. Should an interested Vendor desire assistance or information, in recruiting, tutoring,
and training or otherwise preparing potential employees and subcontractors, the Vendor may
contact Bobby Forch at 684-0722.

Terms and conditions for affirmative efforts in subcontracting and employment are within the
Contract Terms and Conditions. Vendors are encouraged to review those obligations and be
aware of them as a condition of bidding.




                                                                                               1-11
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation


Proprietary Proposal Material

The City requests that companies refrain from requesting public disclosure of proposal
information until an intention to award is announced, as a measure to best protect the solicitation
process, particularly in the event of a cancellation or resolicitation. With this preference stated,
the City shall continue to properly fulfill all public disclosure requests for such information, as
required by State Law.

Vendors should understand that any records (including but not limited to bid or proposal
submittals, the Agreement, and any other contract materials) they submit to the City become
public records under Washington State law (See RCW Chapter 42.17, the Public Disclosure Act,
at http://www.leg.wa.gov/wsladm/rcw.cfm). Public records must be promptly disclosed upon
request unless a statute exempts disclosure. Exemptions from disclosure include trade secrets and
valuable formulas (See RCW 42.17.260(1), RCW 42.17.310(1) (h), and RCW Ch. 19.108).
However, public-disclosure exemptions are narrow and specific. Vendors are expected to be
familiar with any potentially-applicable exemptions, and the limits of those exemptions.

Vendors are obligated to separately bind and clearly mark as “proprietary information” any
proposal records they believe are exempted from disclosure. The body of the proposal may refer
to these separately-bound records. Vendors should mark as “proprietary” only that information
they believe legitimately fits within a public-disclosure exemption. The City may reject
solicitation responses that are marked proprietary in their entirety.

If the City receives a public disclosure request for records that a Vendor has marked as
“proprietary information,” the City will notify the Vendor of this request, and will postpone
disclosure briefly to allow the Vendor to file a lawsuit under RCW 42.17.330 to enjoin disclosure.

The City has no obligation to assert an exemption from disclosure. If the Vendor believes that its
records are exempt from disclosure, the Vendor is obligated to seek an injunction under RCW
42.17.330. By submitting a Proposal the Vendor acknowledges this obligation; the Vendor also
acknowledges that the City will have no obligation or liability to the Vendor if the records are
disclosed.
Cost of Preparing Proposals

The City will not be liable for any costs incurred by the Vendor in the preparation and
presentation of proposals submitted in response to this RFP including, but not limited to, costs
incurred in connection with the Vendor’s participation in demonstrations and the pre-proposal
conference.
Vendor Responsibility

 It is the Vendor responsibility to examine all specifications and conditions thoroughly, and comply
fully with specifications and all attached terms and conditions. Vendors must comply with all
Federal, State, and City laws, ordinances and rules, and meet any and all registration requirements
where required for contractors as set forth in the Washington Revised Statutes.
Changes in Proposals

Prior to the Proposal submittal closing date and time established for this RFP, a Vendor may
make changes to its Proposal provided the chance is initialed and dated by the Vendor. No
change to a Proposal shall be made after the Proposal closing date and time.


                                                                                                 1-12
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 1: Rules of Preparation




Errors in Proposals

Vendors are responsible for errors and omissions in their proposals. No such error or omission
shall diminish the Vendor’s obligations to the City.


Withdrawal of Proposal

A submittal may be withdrawn by written request of the submitter, prior to the proposal due date
and time. After the due date and time, the submittal may be withdrawn only with permission by
the City. A withdrawal of a proposal after the proposal due date and time is a serious and
terminating step, and should not be requested unless the Vendor is fully assured that this is a
necessary and permanent action of the part of the Vendor. If a Vendor withdraws a proposal, the
City retains the right to eliminate that vendor from the Vendor list for future solicitation of the
same or similar product or services. All requests for the withdrawal of proposals shall be
submitted in writing to the RFP Coordinator.

Rejection of Proposals and Rights of Award

The City reserves the right to reject any or all proposals at any time with no penalty. The City
also has the right to waive immaterial defects and minor irregularities in any submitted proposal.

Incorporation of RFP and Proposal in Contract

This RFP and the Vendor’s response, including all promises, warranties, commitments, and
representations made in the successful proposal, shall be binding and incorporated by reference in
the City’s contract with the Vendor.

No Gifts and Gratuities.

Businesses must not offer gifts, gratuities, loans, trips, favors, special discounts, work, or
anything of economic value in conjunction with City business practices. It is also unlawful for
anyone to offer another, to influence or cause him or her to refrain from submitting a Proposal.
Vendors must strictly adhere to the statutes and ordinances for ethics in contracting and
purchasing, including RCW 42.23 (Code of Ethics for Municipal Officers) and RCW 42.52
(Ethics in Public Service). This is applicable to any business practice, whether a contract,
solicitation or activity related to City business.



Involvement of Former City Employees.

Upon receiving an intention to award, Vendor shall promptly notify the City in writing of any
person who is expected to perform any of the Work and who, during the twelve months
immediately prior to the expected start of such Work, was an official, officer or employee.
Vendor shall ensure that no Work related to a contract awarded as a result of this RFP is
performed by such person, to the extent that such work is disallowed by the City.



                                                                                                1-13
                                              SPIDER Project – Integration Implementation Services
                                                                 Chapter 1: Rules of Preparation


 No Conflict of Interest.

 Vendor confirms that Vendor does not have a business interest or a close family relationship with
 any City elected official, officer or employee who was, is, or will be involved in Contractor
 selection, negotiation, drafting, signing, administration or evaluating Contractor performance.
 Should any such relationship exist, Vendor shall notify the RFP Coordinator in writing, and the
 City shall make sole determination as to compliance.
 Protests and Complaints

 The City has rules to govern the rights and obligations of interested parties that desire to submit a
 complaint or protest to this RFQ process. Please see the City website at
 http://www.seattle.gov/purchasing/ for these rules. Interested parties have the obligation to be
 aware of and understand these rules, and to seek clarification as necessary from the City
 Proposal Disposition

 All material submitted in response to this RFP shall become the property of the City upon
 delivery to the RFP Coordinator.
 Negotiating is Acceptable

 Any conditions and provisions that a Vendor seeks shall be a part of the proposal.
 Notwithstanding, nothing herein shall be interpreted to prohibit the City from introducing or
 modifying contract terms and conditions during negotiation of the final contract
 Negotiation Time Limit and Contract Signature Response Time

 The City has significant and critical time lines which frame this initiative. The City shall initiate
 contract negotiations with the apparent successful Vendor. If the City determines that contract
 development is not proceeding within a reasonable period of time, the City may terminate the
 negotiation process. Upon such termination, The City may then proceed to the next apparent
 successful Vendor.

 The City requires the apparent successful Vendor to sign and return the Contract, insurance
 within an acceptable form, and all associated materials within fifteen (15) days after the Contract
 and notice of such materials has been given. If the Apparent Successful Vendor fails to return
 such materials within fifteen (15) business days, the City may elect to cancel the original award
 and proceed to the next highest ranked eligible Vendor.


6. PROPOSAL FORMAT AND ORGANIZATION



6. OSAL FORMAT AND ORGANIZATION
 Each complete proposal shall contain the following:
          Proposal certification
          Deliverables proposal
          Management proposal
          Financial proposal


                                                                                                   1-14
                                             SPIDER Project – Integration Implementation Services
                                                                Chapter 1: Rules of Preparation


            Vendor Questionnaire
            WMBE Subcontracting Outreach and Recruitment Commitment (if Applicable)
            Acceptance, or modification, of City’s standard agreement
            Equal Benefits Form
            W-9 Form (if included)

 General Format

 Proposals should be prepared on standard 8 ½” by 11” paper. The pages should be printed
 double-sided. The final copies should be bound with tabs identifying and separating each major
 section. Financial proposals should be bound and sealed in a separate volume. Confidential
 proprietary information should be bound and sealed in separate volume. Foldouts are permissible,
 but should be kept to a minimum. Manuals, reference material, and promotional materials must
 be bound separately.

 Response Format

 For the management proposal, each specification, including the section designator shall be
 restated in the proposal and followed by the Vendor’s response. The specification responses in
 the management and deliverables proposal should follow the numerical sequence set forth in the
 RFP.
 Readability

 Vendors are advised that the City’s ability to evaluate proposals is dependent in part on the
 Vendor’s ability and willingness to submit proposals which are well ordered, detailed,
 comprehensive, and readable. Clarity of language and adequate, accessible documentation is
 essential.


7. EVALUATION PROCESS

 The City will evaluate Vendors and their respective proposals in accordance with the following
 process and consistent with the evaluation criteria set forth in this section under the subheading
 Evaluation Ranking. The City is committed to a fair and competitive process and the City
 reserves the right to be flexible and modify the process as reasonable to make a selection.
            Step 1: General Information. Proposals will be reviewed by the City’s Purchasing
             Services Section for compliance with the Administrative Requirements provided.
             Only those proposals that comply with the requirements will be evaluated.
            Step 2: Detailed Review Written proposals (including financial proposals) will be
             reviewed and evaluated by an Evaluation Committee. The Evaluation Committee
             will be comprised of City Staff that will include representatives from the City’s
             Police Department. The Evaluation Committee will rank proposals based on the
             evaluation criteria listed in the Proposal Ranking Section that follows. Vendor
             Proposals that cluster within a competitive range in the opinion of the Evaluation
             Committee shall remain active and continue to Step 3.



                                                                                                 1-15
                                              SPIDER Project – Integration Implementation Services
                                                                 Chapter 1: Rules of Preparation


            Step 3: Vendor Interviews: The City shall conduct a finalist Vendor Interview with
             those Vendor(s) whose proposal(s) remain active following the detailed review. The
             interview(s) will be structured as follows:
             1.      Each finalist Vendor will be scheduled for a 2 – 3 hour interview with the
                     City.
             2.      Each finalist Vendor will receive an agenda, with the intended
                     dialog/questions that will be asked of each finalist.
             3.      Each finalist will be offered and opportunity to submit questions to the City
                     in advance of the interview.
             4.      All finalists will be provided with available documents relevant to the
                     interface integration. Requests for information from the finalist(s) must be
                     directed to the Project Coordinator. City responses to requests for
                     information will be distributed to all finalist Vendors.
             5.      Components of the finalist interview will include:
                     Presentation by Vendor
                     City question and answer session
             6.      The finalists’ proposed key project personnel must participate in the finalist
                     interview.
            Step 4: Reference Checks: The City will conduct reference checks for the finalist
             Vendor(s).
            Step 5: Apparent Successful Vendor. Based on the aforementioned evaluation
             processes, the evaluation committee will produce a ranking of the finalist Vendors.
             This information and the committee recommendation will be forwarded to the
             Steering Committee for a final decision. The Steering Committee and the City
             Director of Purchasing Services will review the ranking of the Vendors submitted by
             the evaluation committee. They will evaluate any other findings or factors deemed
             appropriate for this procurement and then select and announce the apparent
             successful Vendor.
            Step 6: Negotiations. The City will initiate contract negotiations with the apparent
             successful Vendor.

The apparent successful Vendor will work with the City’s project staff to develop a Statement of
Work (SOW), and clarify requirements to the level of detail that will reduce uncertainty to a
minimal level. The SOW and the requirements work will become part of the contractual term for
performance by the Vendor.

The Contract will be executed upon the Vendor’s satisfactory completion of negotiations. If
negotiations cannot be completed to mutual satisfaction within 90 calendar days or in an otherwise
reasonable time frame in the opinion of the City, then the City retains the sole option to terminate
negotiation. In such an event, the City reserves the right to name another apparent successful
Vendor and restart with the new Vendor or to terminate the RFP process.




                                                                                                       1-16
                                           SPIDER Project – Integration Implementation Services
                                                              Chapter 1: Rules of Preparation


Review of the proposals will consist of a multi-phase process. This process is designed to ensure
fairness while minimizing schedule demands and evaluation/proposal costs. The process is
intended to ensure the best proposal at reasonable cost is selected.

Evaluations are based only upon the quality of the proposed solution described in response to this
solicitation, not any previously submitted materials.

Points of Clarification: Throughout the evaluation process, the City reserves the right to seek
clarifications from any Vendor.

Contacting References and Other Sources: The evaluation committee may contact the client
references of the Vendors or other sources in addition to those specifically provided by the
Vendor, at any time to assist the City in understanding the product; although the City anticipates
completing reference checks in Step 4 of the process for those proposals that remain active.




                                                                                               1-17
     Chapter 2




Current Environment
                                                SPIDER Project – Integration Implementation Services
                                                                   Chapter 2: Current Environment




2
Chapter




Current Environment
 Technology Overview

Overview

This Chapter provides information on the current state of SPD information technology systems,
including relevant standards. Where appropriate, future directions are also noted.


Network Infrastructure

The City of Seattle maintains an extensive WAN throughout the City. The SPD portion of the WAN
connects to 17 locations throughout the City.

       Physical             The core network is Gigabit Ethernet over fiber. Connectivity to
                            major sites is generally 1000BaseFx; to minor sites is either
                            100BaseFx or T-1. Connectivity to desktops is 100BaseT FDX on
                            CAT5e copper.
       Protocol             TCP/IP on Ethernet
       Routers/Switches Cisco. 4 major data centers. Hubs and unmanaged consumer-
                            product switches prohibited.
       Remote Access        No dial-in; no ISDN/DSL
       Wireless             Conversion to Sprint CDMA recently completed. 802.11, AX.25
                            is effectively prohibited.


Hardware

      SPD supports over 1000 desktops on its WAN. In addition, we support over 300 mobile units
      over the wireless network, and an additional 100+ non-wireless laptops.



                                                                                                 2-1
                                          SPIDER Project – Integration Implementation Services
                                                             Chapter 2: Current Environment



     Desktop       Current Standard: New Purchase - Pentium-IV 2.0 – 2.8 GHz - 512 MB RAM
                   – DVD - 40 GB Hard Drive –WinXP

                   Current Minimum Configuration for existing computers: Pentium-400 -
                   64MB RAM (128 MB Recommended) - 1.3GB HD Win2k or Win XP

                   Future Direction: - Intel – Microsoft, N-1 for Desktop OS, N-2 for MS Office
                   Productivity Suite.
     Laptop        Current Standard: New Purchase: Pentium IV 1.5 GHz, 512mb Ram, DVD

                   Current Minimum Configuration for existing laptop: Pentium, 16MB Ram,
                   1 GB HD

                   Future Direction: - Intel – Microsoft, N-1 for Desktop OS, N-2 for MS Office
                   Productivity Suite.
     Mobile        Current Standard: L-3COM – PIII-600, 128mb Ram, 10GB HD, Ethernet,
     Computer –    12.1” LCD Touch Screen, 800x600
     Vehicles
     Mobile        Current Standard: Panasonic TB-28, PIII-600 MHz, 128 MB RAM, 20 GB
     Computer –    HHD, Win 2K
     Laptop
     LAN Servers   Current Standard: WinTel based servers. 3 year lifecycle.

                   Future Direction: Dell, cabinet density only, minimum 2.2GHz CPU w/2MB
                   minimum RAM. 3 year lifecycle. Possibility of Sun, IBM, or other Unix
                   platform. NAS and SAN with fiber switched fabrics across separate datacenters.



Software – Operating Systems

     Network       Current Standard: Mixed levels of Cisco IOS with data centers trunked to allow
                   DEC LAT (non-routable) protocol between CAD and RMS. Network segmented
                   from City via Firewall. No ingress to Police network from City Intranet or Public
                   Internet.

                   Future Direction: Most current Cisco IOS available. Retire DEC LAT.
                   Installation of Network and Host-based Intrusion Detection/Intrusion Prevention
                   Systems (IDS/IPS)
     Server        Current Standard: Microsoft NT 4.0 domain with W2k and W2k3 members.
                   VMS on CAD and RMS. McAfee VirusShield.

                   Future Standard: W2k3 Active Directory. Possible entrance of Linux/Unix for
                   either CAD or RMS. McAfee VirusShield.
     Desktop       Current Standard: W2k Professional, with appearances of W9x and Windows
                   XP. Some Novell clients for access to City systems. Microsoft SMS 2.0 Clients.
                   McAfee AV.

                   Future Standard: XP Professional with some Novell clients for access to City
                   systems. Microsoft SUS 2k4 Clients. McAfee AV.
     Mobile        Current Standard: Windows XP.
     Computers
                   Future Standard: XP Professional



                                                                                                     2-2
                                            SPIDER Project – Integration Implementation Services
                                                               Chapter 2: Current Environment




Mobile Data

     CDMA            Current: SPD uses 1xRTT based CDMA in vehicles and laptops. Supplier is
                     Sprint.
                     Contact:
                     Linda M Baily
                     Desk 206-850-9790
                     lbaily01@sprintspectrum.com

                     Future: SPD plans to upgrade along the CDMA line. However there is no
                     schedule on this upgrade path.


Software – Mobile Application Environment

     Netmotion       Netmotion middleware. “Wireless middleware” provides IP data transport. A
                     combination of VPN, Proxy and “guaranteed” data delivery system. See
                     embedded files for more detail. Also see www.netmotionwireless.com

                     Contact:
                     Juan Ramos
                     Sales Engineer
                     (206) 691-5621 Work
     Mobile CAD,     Mobile CAD, RMS and Field Reporting 2000 enterprise edition. Client system
     RMS and Field   management: Deliver applications, and patches to applications; Automatically
     Reporting       update files and data on client; Change configuration settings on clients. More
                     information on this product is at: www.mobileautomation.com

                     Contact:
                     Bruce Temesy
                     Director of Strategic Partner Development
                     Mobile CAD, RMS and Field Reporting, Inc.
                     310.265.8577 office
                     btemesy@mobileautomation.com
     Aether          Current Standard: SPD uses a heavily modified version of Aether Packet
                     Cluster Server (PCS) and Packet Cluster Mobile (PCM). Briefly the current SPD
                     CAD is interfaced to an Aether created module called the translator. The translator
                     then uses PCS/PCM to drive a user interface that is used instead of PCM. See the
                     attached file (below: CAD_MDC_Screens) for screen snapshots of SPD client.
                     More information on Aether is located at www.aethersystems.com.

                     Contact:
                     Cathleen Crowley
                     Sales Account Manager
                     Northwest Territory
                     Aether Systems, Inc.
                     p: 408-997-8405
                     c: 978-985-1245
                     f: 781-240-6034
                     ccrowley@aethersystems.com
                     www.aethersystems.com



                                                                                                       2-3
                                               SPIDER Project – Integration Implementation Services
                                                                  Chapter 2: Current Environment



                        Future Standard: SPD is interested in replacing Aether solution with a solution
                        that has similar functionality.


Software – Applications

     Client             Current Standard: Visual basic, Office 2000, Access 97

                        Future Standard: SPD’s preference is to move toward web based systems.
     Work Group         Current Standard: Access 97
     (<10 users)
     database/backend   Future Standard: Access XP or above
     Department         Current Standard: Oracle 8i and above.
     Wide
     database/backend   Future Standard: Oracle 9i and above. SPD will consider other database servers
                        given a valid set of supporting arguments that show reliability, scalability,
                        security, standardization and flexibility
     Citywide           Current Standard: Sonic Enterprise Service Bus
     Integration
     Solution




                                                                                                          2-4
      SPIDER Project – Integration Implementation Services
                         Chapter 2: Current Environment




   Chapter 3


Vendor Response




                                                       2-5
                                            SPIDER Project –Integration Implementation Services
                                                                 Chapter 3: Vendor Response




3
Chapter




Vendor Response

Introduction

This Chapter provides the framework for Vendors to supply information to the City
regarding their company, proposed solution and pricing. Vendors are required to respond to
all questions in one of two ways:
              Provide information where requested directly in the spaces indicated; or
              Provide information requested in an attachment: The attachment must include
               a reference to the RFP page number and item number.


Adherence to the overall format of the RFP is required. Vendors who omit responses
may be deemed unresponsive and risk being eliminated.




Objectives of this Section

The Vendor’s response to the specifications in this Chapter will help the City determine the
Vendor’s ability to:
              Successfully implement the proposed project as planned.
              Assign qualified and experienced team members for the duration of City’s
               project.
              Demonstrate confidence and willingness to deliver the scope of work required
               by the City.




                                                                                            3-1
                                            SPIDER Project –Integration Implementation Services
                                                                 Chapter 3: Vendor Response




A.   Vendor Services Overview

Prime Contractor Responsibility: If a proposal includes equipment, materials, or services
available from others, it is mandatory for the Vendor to act as “Prime Contractor” for the
procurement of all products proposed. In this role, the Prime Contractor must be the sole
point of contact with regard to contractual issues including payment of any and all charges
resulting from the purchase of the proposed software, and services. The Prime Contractor
must take full responsibility for the entire project described in this RFP document, including
configuration, installation, development, planning, deployment and acceptance testing of all
items proposed. The Prime Contractor must also provide maintenance and warranty for its
products and pass through warranties of other Vendors

Contractor Information
                      Company Name:
                      Location of Office
                      Serving the City during implementation:




                      Headquarters Address:




                      Representative(s) – Please highlight the authorized negotiator:
                Name                Title             Telephone           Email




                                                                                              3-2
                                            SPIDER Project –Integration Implementation Services
                                                                 Chapter 3: Vendor Response



Describe general types of products and Services offered by the Company:

_____________________________________________
_____________________________________________
_____________________________________________

Summary Company Information


Question                                              YES      NO      Additional Information
1. Are you a Certified Sonic Partner?                                  Date Certified:


If Yes, provide the date Certified
2. Do you have a demonstrated track record with
application integration broker solutions?


If Yes, please provide references in the
Vendor Experience Section 3.B
3. Do you have a demonstrated record in
government consulting?


If yes, please provide references in the
Vendor Experience Section 3.B


4. Do you have a demonstrated record in Law,
Safety & Justice consulting?


If yes, please provide references in the
Vendor Experience Section 3.B




                                                                                            3-3
                                                  SPIDER Project –Integration Implementation Services
                                                                       Chapter 3: Vendor Response



Question                                                    YES      NO      Additional Information
5. Is there any pending or resolved litigation                               Attachment
between the company and any client in the past 5                             Name/Location:
years?


If Yes, attach list with a description of the nature and
resolution of the litigation.
6. Has your company had any contracts cancelled                              Attachment
or terminated for non-performance or any other                               Name/Location:
client-initiated action?


If Yes, please attach a description of the issue, and
the location:




Detailed Company Information


Information Requested                                       Response
1. Length of time in Business.
2. Number of operational implementations of
SONIC ESB application integration solutions the
company has completed for public safety agencies.
3. Number of full time employees supporting
application integration software using JCA and
JMS.
4. Percentage of employees in integration,
customer support, and sales/marketing for
application integration software.




                                                                                                  3-4
                                            SPIDER Project –Integration Implementation Services
                                                                 Chapter 3: Vendor Response



Information Requested                                 Response
5. Length of time in business of implementing
application integration software using JCA and
JMS. (years)
6. Number of clients for who company has
implemented application integration solutions using
JCA and JMS.




Financial Company Information:


Information Requested                                 Response
Provide a copy of the company's financial             Attachment
statements for the last two years.                    Location/Name:
Provide Dun & Bradstreet number
Gross revenue for prior fiscal year (in US Dollars)
Percentage of gross revenue generated by
implementing application integration software
using JCA and JMS.




                                                                                            3-5
                                                                                     SPIDER Project – Integration Implementation Services
                                                                                                           Chapter 3: Vendor Response

B.     Vendor Experience

Instructions: Vendors wishing to submit proposals shall have supplied public or private entities for a minimum of three (3)
continuous years prior to the submission of this proposal. Further, in the past three (3) years, the Vendor must have successfully
implemented an integration solution using JCA and JMS in at least three organizations. All such implementations must be operational
as of the date of the proposal submission. Please provide the following information for each reference, (expand table and include as an
attachment as necessary). Attached? Y/N___ Attachment name/location:___________
                                                                                                       Contract
                                                                                                       Value at:
                                                                                                       1. Contract
Name, OrganizationTtype,                                                                               Signing        Contract and
Address, Contact, Title,       Interfaces Implemented,         Integration   General Type of Message   2. Cut Over    Implementation
Phone Number, email            Scope of Product and Services   Software      Exchange (e.g. Court)     3. Presently   Dates




                                                                                                                                       3-7
                                             SPIDER Project – Integration Implementation Services
                                                                   Chapter 3: Vendor Response




C.      Interfaces

Please fill in the requested information in the columns next to the interfaces the company has
successfully implemented.
First            Second           Priority    Integration            Client Site(s)
System           System                       Software
RMS              King County      Core &
             –   (includes        Basic
                 former
                 SeaKING)
RMS              CAD              Core &
             –                    Basic
RMS              SMTP             Core &
             –                    Basic
RMS              ACCESS           Core &
             –                    Basic
RMS              MDC              Core &
             –                    Basic
RMS              AFR              Core &
             –                    Basic
CAD              MDC              Core &
             –                    Basic
CAD              ACCESS           Core &
             –                    Basic
CAD              SMTP             Core &
             –                    Basic
CAD              King County      Core &
             –   (includes        Basic
                 former
                 SeaKING)



                                                                                              3-8
                                   SPIDER Project – Integration Implementation Services
                                                         Chapter 3: Vendor Response



First        Second     Priority    Integration            Client Site(s)
System       System                 Software
MDC          AFR        Core &
         –              Basic
MDC          ACCESS     Core &
         –              Basic
RMS          SEAJIS     Future
         –

RMS          LINX       Desired
         –
RMS          RAIN       Desired
         –
RMS          AUTOCITE   Desired
         –
RMS          TOWS       Desired
         –
CAD          TOWS       Desired
         –
CAD          FIRECAD    Desired
         –




                                                                                    3-9
                                           SPIDER Project – Integration Implementation Services
                                                                 Chapter 3: Vendor Response




D.   Warranty

Vendor must warranty all components and business process data exchanges developed in this
body of work for a minimum of 180 days.


Warranty Support


Please describe post-implementation support during the warranty period, including the
following:
Length of Warranty Period?
       Months _____
Transition from implementation team to another party (if appropriate)?
       Months _____
___________________________________________________________________________
___________________________________________________________________________


Describe all parties with which the City would be working.
       _____________________________________________________________________
___________________________________________________________________________


Response procedures for priority vs. non-priority calls
___________________________________________________________________________
___________________________________________________________________________


Hours of service:
       _____________________________________________________________________
___________________________________________________________________________




                                                                                          3-10
                                            SPIDER Project – Integration Implementation Services
                                                                  Chapter 3: Vendor Response



Remote site support:
       _____________________________________________________________________
___________________________________________________________________________


Describe the procedures for trouble notification:
___________________________________________________________________________
___________________________________________________________________________


Describe the procedures for customer initiated trouble reporting, status tracking and
correction:
       _____________________________________________________________________
___________________________________________________________________________


Describe any software or hardware used to assist in technical troubleshooting (indicate any
costs in pricing forms):
___________________________________________________________________________
___________________________________________________________________________




                                                                                           3-11
                                            SPIDER Project – Integration Implementation Services
                                                                  Chapter 3: Vendor Response




E.   Financial Proposal

Objectives: The objectives of the Financial Proposal Specifications are to provide the Vendor
with instructions and formatting information for the preparation of the Financial Proposal.
The Financial Proposal response will allow the City to:
Fairly compare the financial proposals from each Vendor
Better understand the Vendor’s overall proposal
Determine what the best SONIC ESB Integration Implementation Service options are, based
on funds available and project costs
Adjust volumes and services using the financial information provided without requiring the
Vendor to resubmit the entire financial proposal
Allow the option for the City to directly purchase 3rd party software and hardware as required


Budget: The overall budget, including all required hardware, Vendor supplied software, 3rd
party supplied software, including enhancements, installation, interface, labor, training, data
conversion and professional services is $1.25 M.


Financial Proposal Preparation Instructions:
Financial Proposal Packaging: The Vendor should prepare a separate Financial proposal
volume. This volume should be sealed separately.
Proposal Forms: The Vendor must use the Financial Proposal Bid form to propose a SONIC
ESB Integration Implementation Services. The Bid Form is embedded at the end of the
Financial Proposal section.
Effective Dates for Pricing: The total system prices and other costs quoted in this proposal
must be valid until the City completes an award decision and has successfully negotiated a
contract to signature. Should any Vendor object to this condition, the Vendor must object
through the protest process prior to the bid closing date, as described elsewhere herein.
During contract period, pricing shall remain firm and fixed for the initial term of the contract.
During the term of this contract, should the contractor enter into pricing agreements with
other customers providing greater benefits or pricing, contractor shall immediately amend the


                                                                                             3-12
                                             SPIDER Project – Integration Implementation Services
                                                                   Chapter 3: Vendor Response



contract to provide similar pricing to the City if the contract with other customers offers
similar usage quantities and similar conditions impacting pricing. Contractor shall
immediately notify the City of any such contracts entered into by the Contractor.


Hardware and Software Buyback: Hardware and Software Buyback: Should the system
fail to meet the City final acceptance test case requirements, the Contractor will be
required to repurchase any hardware and software specified in the Contractor’s
response that was purchased by the City from the Prime Contractor and any
subcontractors and third party suppliers. Notice shall be provided to the Contractor of
the City’s intent to employ this condition. The City may collect such payment from the
Contractor using that approach considered in the best interest of the City, including but not
limited to submitting an invoice to the Contractor for the repurchase, or to withhold payment
of any amount due from the City to the Contractor, or may evoke the Contract Bond for such
pay-back, or may take other action considered necessary for the City to enforce this
condition.


Bid Form Instructions
Clarity: The Vendor should be as specific as possible. The Vendor should indicate if the
cost of a specific deliverable is included within the cost of another line item. For example, if
the cost of a peripheral is included in the price of a PC, please include the peripheral as a line
item and indicate that it is included in the PC line item cost.
Column Item Formatting: Vendors should take care to place the pricing information in the
proper column. The columns are set up as follow:
Column A: Item descriptions
Columns B: Quantities proposed
Columns C: Unit price of items proposed
Columns D: Extended price (automatically calculated)
Columns E: Annual maintenance price proposed
Columns F: Remarks to be noted by vendor




                                                                                              3-13
                                            SPIDER Project – Integration Implementation Services
                                                                  Chapter 3: Vendor Response




Row Item Formatting: The Vendor should take care to limit proposed row items to the
following categories:
Vendor supplied software
Server Hardware and Software
Third party software
Data Network (to be provided by City)
Connectors
Interfaces (Exchanges)
Training
Professional services




Adding, Modifying and Deleting Row Items: Within each of the categories, the City has
listed certain row items as a sample to help clarify the format. The Vendor should feel free
to add, modify, or delete row items within each category to present a complete financial
proposal.
Categories Instructions: Cells highlighted in yellow in the Bid Proposal Form contain self-
calculating mathematical formatting. No entries are required or shall be made by Vendor in
these highlighted cells.
Vendor Supplied Software: The Vendor supplied software price should include a site
license for all Vendor server and client software for the entire system; with every module
listed. The modules may be priced individually or together, or in a combination thereof.
Server Hardware and Software: The Vendor supplied hardware price should include all
servers needed to support the system with an architecture that provides for load balancing
and fail-over. It should also include test, training, and quality assurance systems.
Third Party Software: The third party software price should include all software not owned
by the Vendor that is required for the system to work. Please include the company name,
what is proposed and the cost.




                                                                                             3-14
                                             SPIDER Project – Integration Implementation Services
                                                                   Chapter 3: Vendor Response



Data Network: The City has an extensive data network and transmission system that may be
utilized by the Vendor to connect the proposed system. The City will work with the
successful Vendor to design the required data network. Therefore, Vendors do not need to
propose a data network for the system.
Connectors: The connector price should include the price for connection to each systems
listed on the bid form. Please note that City may choose not to concurrently implement all the
proposed connectors.
Exchanges (Interfaces): The interface price should include the price for each interface listed
on the bid form. Please note that the City may choose not to concurrently implement all
proposed interfaces. Therefore each interface cost should be self-contained and inclusive of
testing. If there are dependencies of previous exchanges (interfaces), please indicate in the
remark column.
Training: The training price should include all classes. For each class provide the unit
price/cost per class in the unit cost column. Also, please provide number of students per class
in the description column.
Professional Services: The professional service price should include the price for each
professional service listed on the bid form. If the cost of a line item has been included
previously, so indicated.
Cost Breakdown: Vendors shall provide a cost breakdown for staffing services and
expenses associated with the SONIC ESB Integration Implementation. Please provide below,
the hourly rate for the Vendor’s Project Manager, the Vendor’s Programmer, and the
Vendor’s Installer:
Project Manager_________
Programmer____________
Installer________________
Bid Form: Double click the icon below to open the Financial Proposal Bid form. This
embedded Excel file contains the required formulas and categories needed to complete the
financial proposal.
Clarity: The Vendor should be as specific as possible. The Vendor should indicate if the
cost of a specific deliverable is included within the cost of another line item. For example, if



                                                                                            3-15
                                             SPIDER Project – Integration Implementation Services
                                                                   Chapter 3: Vendor Response



the cost of a peripheral is included in the price of a PC, please include the peripheral as a line
item and indicate that it is included in the PC line item cost.




                                                                                              3-16
                                           SPIDER Project – Integration Implementation Services
                                                                 Chapter 3: Vendor Response




F.   Exceptions to Terms and Conditions

Please describe in detail any exceptions to RFP terms and conditions.




                                                                                          3-17
                    Chapter 3: Vendor Response




        Chapter 4




   Implementation and

Deliverables Specification

        Response
                                             SPIDER Project – Integration Implementation Services
                                                             Chapter 4: Specification Response




4
Chapter




Specification Response
   A. Deliverables

Vendor must describe in adequate detail how their firm will meet the following deliverables
if selected by the City. All deliverables will be provided to the Project Manager for review
and final acceptance.

Vendor should include a description of their recent experience in this area. Vendor must
include a description of their approach, the number of resources and the estimated number of
hours to complete each item.

City prefers all responses to each deliverable to be on a separate page, appropriately titled.
Vendor is to use no more than two pages per response per deliverable item. A decreasing
value will be applied for all responses more than two pages:



       1.      An adapter/connector and message exchange development methodology that
               is iterative, replicable and documented. This methodology must be applied to
               the development, documentation, testing, user acceptance, deployment and
               maintenance of the initial Adapters/Connectors and Message Exchanges as
               well as future Adapters/Connectors and Message Exchanges.

       2.      Contractor must follow a mutually agreed upon skills transfer methodology to
               teach the City staff the necessary skills needed to continue developing
               message exchanges, maintain the rules repository, and update system
               configuration, rules, or message exchanges and develop additional
               adapters/connectors.




                                                                                                 4-1
                                  SPIDER Project – Integration Implementation Services
                                                  Chapter 4: Specification Response


3.   Develop, document, test and implement the SPIDER identified
     Adapters/Connectors using SONIC ESB or a mutually agreed upon
     complementary tool or combination of tools.



4.   Develop, document, test and implement the SPIDER identified Message
     Exchanges using SONIC ESB or a mutually agreed upon complementary tool
     or combination of tools.



5.   Ownership of the code and associated documentation developed for all
     contracted Interface Adapters/Connectors and Message Exchanges will reside
     solely with the City.


6.   Document your firm’s guaranties, warranties and product maintenance for all
     Adapters/Connectors and Message Exchanges implemented as part of this
     RFP.


7.   Develop, document and execute an iterative and replicable technical testing
     plan that includes unit test, integration testing and user acceptance testing.


8.   Document a “roadmap” with resource requirements and timetable for
     achieving the, Technical Development, Security Program Development and
     Execution, Testing, Program/Project Management and System Operations &
     Maintenance for all data exchanges using the shared methodology and
     templates provided by the successful candidate. The resources and time
     estimate should have a confidence level of plus or minus 10%, and must
     include a list of assumptions used to develop the estimates.




                                                                                      4-2
                                            SPIDER Project – Integration Implementation Services
                                                            Chapter 4: Specification Response


   B. Training


Vendor must describe what specific types of classes and training City staff needs to facilitate
a skills transfer from the Vendor as required in this RFP.




       Training Plan


       Please complete the following table describing your training approach for each
       skillsets/position relevant, (e.g. Business Analyst, Application Developer, System
       Administrator, etc.).


        Position                 Responsibilities       Training               Hours         of
                                                        Course(s) /            training
                                                        Location               provided




                                                                                             4-3
                                        SPIDER Project – Integration Implementation Services
                                                        Chapter 4: Specification Response


C. Documentation


  1.      Please identify and briefly describe all proposed
          documentation deliverables:




  2.   Describe how and in what form the documentation is made available to users.
       That is, is it on CD, the web, hardcopy, etc?




                                                                                         4-4
                                           SPIDER Project – Integration Implementation Services
                                                           Chapter 4: Specification Response


   D. Implementation


Based on the Deliverables in Chapter 4, provide a summary of the proposed system
implementation approach. The elements included in the Vendor’s response should be:

       1.     Implementation Approach


       Please describe your approach to implementation addressing the following areas:

             System development and documentation.
             System implementation and integration: Describe your approach to
              installation and rollout of the system.
             System Test Plan: Identify the process through which the system is evaluated
              in order to ensure that appropriate unit testing, system integration testing and
              user acceptance testing is conducted and that required and expected
              functionality has been implemented. The Test Plan should specifically
              address how the integration and interface testing will be conducted on live
              systems. The plan must also include an estimate of the time needed for
              testing, and the number of resources required for testing.
             System acceptance: Identify the criteria and metrics used to determine
              whether or not the system has been adequately implemented.
             Staff Mentoring


       2.    Project Timeline


              a.     Please provide the Vendor’s projected timeline for completion of all
                     Interfaces identified as Core/Basic.


              b.     Please provide the Vendor’s projected timeline (following completion
                     of all Core/Basic Interfaces) for the Interfaces identified as Desired
                     and Future.



                                                                                              4-5
                                      SPIDER Project – Integration Implementation Services
                                                      Chapter 4: Specification Response




3.   Implementation Work Plan


 Please provide a detailed project implementation plan that includes a Gantt chart
 showing each task with associated beginning and ending dates.



4.   Implementation Team Resources

     a.   In an attachment, describe how you propose to supplement the City’s project
          team. Describe the project organization for implementation, including:

          (1) Project organization chart clearly illustrating lines of authority

          (2) Number of resources, the role of each individual, and expected duration
               and cost of service for each individual

          (3) Identification of the (Prime) Vendor project manager responsible for
               day-to-day operations for the project and on-site activities

          (4) Identification of the technical lead for the project, who will play the
               primary hands-on leadership role in all technical aspects of the project

                           Attached? Y/N___ Attachment name/location:___________

     b.   Include a resume and three (3) references from previous clients for each
          member of the proposed implementation team. Resumes shall include the
          following information:

          (1) Current position with the Vendor/subcontractor

          (2) Years with the company(s)

          (3) Project position to be staffed

          (4) Education

          (5) Work experience, including past positions with the
               Vendor’s/subcontractors company(s)



                                                                                        4-6
                                      SPIDER Project – Integration Implementation Services
                                                      Chapter 4: Specification Response


          (6) Technical skills and qualifications relevant to the project

          (7) Specific description of experience in working with the proposed
               system, including experience in system design, installation, support,
               training, or management

               Attached? Y/N___ Attachment name/location:___________

     c.   The Vendor agrees to have all staff and any subcontractors submit to a
          background screening by SPD and successfully pass it before they can start
          work on the project

                                                            Vendor agrees? Y/N ______

     d.   The Vendor will warrant that any key staff members, including the Project
          Manager, identified by the Vendor and accepted by the City shall be
          dedicated to the City’s project as that person’s primary assignment

                                                             Vendor agrees? Y/N ______

     e.   The Vendor will warrant that any change in assigned key staff, including the
          Project Manager, is subject to prior City approval in writing.

                                                             Vendor agrees? Y/N ______

     f.   Define the required City staff and related training during implementation,
          testing and recurring support of the proposed solution: Include the role,
          specific task assignments and estimated hours for each task.



5.   Project Organization Chart


 Please provide an organization chart that depicts your team’s organization and the
 anticipated relationships between the team and the City.

6.   Statement of Work




                                                                                       4-7
                                     SPIDER Project – Integration Implementation Services
                                                     Chapter 4: Specification Response


During the contract negotiation period the City and the Vendor will work together to
develop the Statement of Work (SOW). Prior to contract signature the City must
receive and approve a completed SOW from the Vendor.
                Vendor Agrees to this process? Y/N___________


7.   Change Order Process


     a.   Acceptable Change Orders: The City will consider a change order only if
          the City has requested a change to the functionality of the system.

                                                           Vendor agrees? Y/N ______

     b.   Unacceptable Change Orders: Product configuration does not constitute a
          change order. The configurations are dependent on the knowledge and
          design complexity of the Vendor’s system. Assisting the City to get the
          most out of the system is the Vendor’s responsibility. It is incumbent upon
          the Vendor to make sure the City users are well trained in the capabilities of
          the systems so that they may work with the Vendor to define proper
          configurations from the user’s perspective

                                                       Vendor agrees? Y/N ______


8.   Cutover Plan
     a.   In a separate attachment, please describe the Vendor’s cutover
          plan/approach for the Interfaces.

                           Attached? Y/N___ Attachment name/location:___________

                         Vendor commits to this process, and provisions? Y/N ______

     b.   In the Cut Over Plan attachment, please describe what contingency plans
          and problem resolution measures the Vendor will have in place during
          cutover.

                           Attached? Y/N___ Attachment name/location:___________


                                                                                       4-8
                                         SPIDER Project – Integration Implementation Services
                                                         Chapter 4: Specification Response


9.   Certification, System and Acceptance Testing

     a.       The selected Vendor is expected to jointly develop mutually agreeable
              system certification, acceptance and testing procedures. Please describe your
              approach to such procedures.

     b.       Provide the exact transaction response times for your proposed system,
              assuming that the City uses your minimum hardware specifications. These
              shall be used as the basis for the response time testing and acceptance.
              Response time for data retrieval shall be measured from the point of issuing
              the request (pressing the enter key) to displaying the record at the client.



              Transaction                                                    Response
                                                                               Time

                                                                   
               Simple update and/or indexed query (single transaction)

               Complex update and/or query (multiple transactions) 

               Address verification                                    




                                                                                             4-9
 INDEX OF APPENDICES

APPENDICES

A.   ADMINISTRATIVE

     A.1   Contract Bond Form




     A.2   Contract Bond Instructions




     A.3   Equal Benefits Declaration and Worksheet




     A.4   Nondisclosure Agreement




     A.5   Principal Identification Form




     A.6   Proposal Certification




     A.7   Terms and Conditions




                                                      10
                                                                 Seattle Police Department
                                                          Chapter 4: Functional Response

       A.8      Vendor Questionnaire




       A-9      WMBE Sub-Contracting Outreach and Recruitment Commitment




       A.10 W-9 Form


          G:\Purchasing\
       Keeper of the Forms\IRS-W9.pdf

       A.11 W-9 Letter




B.     TECHNICAL

Please Note: Technical Appendices will be made available to a vendor only after the City
has received the signed original Nondisclosure Agreement (NDA): Administrative Appendix
A.4.



       B.1      Interface – SPD System Profile Report
       B.2      Sonic Enterprise Service Bus Software Specifications
       B.3      Attribute Definitions
       B.4      Interface Diagrams
       B.5      System Connection Architecture
                B.5.1 Read Me
                B.5.2 Business Exchanges Descriptor
                B.5.3 Event Type Grouping


                                                                                      4-11
                                             Seattle Police Department
                                      Chapter 4: Functional Response

B.5.4 Event Type Catalogue
B.5.5 ACCESS System Connection Architecture
B.5.6 King County (includes former SeaKING) System Connection
      Architecture
B.5.7 SeaJIS System Connection Architecture
B.5.8 CAD System Connection Architecture
B.5.9 RMS System Connection Architecture
B.5.10 MDC System Connection Architecture
B.5.11 AFR System Connection Architecture




                                                                  4-12

								
To top