The Information Systems Office of the City of Pittsburgh, is soliciting
proposals from qualified firms for Internet Access for the City
of Pittsburgh. Please submit a proposal which responds to the
materials outlined in the attachment. If you are interested,
the deadline for submission of written proposals is 5:00 p.m.
on Friday, July 12, 1996.
Any questions which you may have concerning the request for proposals
should be addressed to:
Howard A. Stern, Assistant Director
City Information Systems Office
City of Pittsburgh
Public Safety Building, 4th Floor
100 Grant Street
Pittsburgh, PA 15219
(412) 255-2152
(412) 255-2355 - fax
Any questions which you may have concerning the technical specifications
of the proposal should be addressed to:
Dennis Moul, Unix Network Administrator
City Information Systems Office
City of Pittsburgh
Public Safety Building, 4th Floor
100 Grant Street
Pittsburgh, PA 15219
(412) 255-2167
(412) 255-2355 (fax)
d m m (at) c i t y - n e t (dot) c o m (Internet E-Mail)
http://www.city-net.com/~dmm (WWW)
Thank you for your consideration, and we look forward to hearing
from you.
Sincerely yours,
Steven J. Schmitt
Director
1.0 GENERAL
1.1 Purpose
1.2 General Scope of Proposed Services
2.0 BACKGROUND
2.1 City Information Systems
3.0 "INTERNET ACCESS" REQUIREMENTS AND SPECIFICATIONS
3.1 General Requirements and Specifications
3.2 Connectivity Architecture
3.2.1 Component I - T1 Service
3.2.2 Component II - T1 Leased Line to ISP Point of Presence
3.2.3 Component III - (2) CISCO Routers
3.2.4 Component IV - (2) Sun Ultra 1 Workstations
3.2.5 Component V - Solstice Firewall-1 Software
4.0 RFP RESPONSES
5.0 VENDOR QUALIFICATIONS
6.0 INSTALLATION AND TRAINING SERVICES
6.1 Installation and Training Services
6.2 Documentation Available at Time of Installation
6.3 Delivery and Payment
6.4 Training
6.5 Maintenance and Customer Support Services
7.0 CONTRACTUAL CONDITIONS
7.1 Rights of Assignment
7.2 Financial Terms and Conditions
7.3 Contractual Terms and Conditions
7.4 Guarantee of Functionality
7.5 Insurance
7.6 Worker's Compensation
7.7 Indemnity
7.8 Patent Indemnity
7.9 Third Party Liability
8.0 AFFIRMATIVE ACTION AND ANTI-DISCRIMINATION
8.1 Minority and Women's Business Enterprise Participation
8.2 Anti-Discrimination
8.3 Debarment
8.4 Statement of Affiliation
9.0 RESPONSE, EVALUATION AND SELECTION PROCEDURES
9.1 Proposal Format and Contents
9.2 Modifications
9.3 Cost Estimates
9.4 Vendor Qualifications and Selection Criteria
9.5 Selection Criteria
9.6 Selection Procedure
9.7 Selection Schedule
9.8 Choice of Features
9.9 Right to Change Process, Terms and Conditions, Specifications, Criteria for Selection and
Reject Bids
1.0 GENERAL
1.1 PURPOSE
The purpose of this Request For Proposals (RFP) is to provide
secure, high-speed, transparent, dedicated access to the Internet
from any TCP/IP device on the City of Pittsburgh's internal Local
Area Network.
1.2 GENERAL SCOPE OF PROPOSED SERVICES
City Information Systems (CIS) has undertaken a systematic program
to provide Internet resources to City employees, and to develop
the infrastructure needed to provide traditional services to City
residents and businesses via the Internet. By this RFP CIS is
seeking to obtain an environment with which it can A) provide
high quality Electronic Mail and World Wide Web services to City
employees, enabling access to information and communications that
can help them better perform their job functions; and B) develop
and deploy Internet services to improve the communication between
City residents/businesses and the various departments in the City.
2.0 BACKGROUND
2.1 CITY INFORMATION SYSTEMS
The Office of City Information (CIS) is responsible for the planning,
acquisition, installation and support of the City's proprietary
and open computing environment. Additionally, CIS performs systems
analyses, researches industry offerings, develops applications,
trains users and serves as systems integrators to departments
for solutions concerning their data processing and information
management needs.
3.0 "INTERNET ACCESS" REQUIREMENTS AND SPECIFICATIONS
3.1 GENERAL REQUIREMENTS AND SPECIFICATIONS
"Internet Access" is defined in this context as the
routing of packets between the City's internal network and the
Internet, along with the support infrastructure to perform this
task in a secure and efficient manner. It explicitly does not
include higher level services such an World Wide Web servers,
electronic mail, File Transfer Protocol (FTP), interactive login
(Telnet), and shell accounts for users. This RFP addresses primarily
the lower three layers of the seven-layer OSI model (Physical,
Data Link, and Network). Implementation of the architecture described
in this proposal will enable the City to provide of its own accord
the higher level services described above.
The City's internal Local Area Network is composed of Intel based
PC's and servers, Unix workstations, and a few specialized mainframe
interconnect devices. There are a total of approximately 1,200
nodes. It is assumed that the number of internal hosts will grow
by at least 25% per year, and the system should be able to support
the growth of the next two years without requiring any upgrades.
Thus, the connectivity architecture needs to be able to support
at least 1,800 TCP/IP hosts on the internal network.
3.2 CONNECTIVITY ARCHITECTURE - 5 COMPONENTS
The connectivity architecture is divided into five separate functional
components. They are as follows:
Component I T1 service provided by Internet Service Provider (ISP)
Component II T1 leased line to ISP Point of Presence (POP)
Component III (2) Cisco routers
Component IV Sun Ultra 1 workstations
Component V Solstice Firewall-1 software
Each of these components will be described in detail in the following
pages. A diagram of the system is shown in Figure 1.
3.2.1 COMPONENT I - T1 SERVICE
Description:
The Internet Service Provider will be the interconnection between
the City network and the Internet as a whole. The T1 line from
the City will terminate at the ISP's Point of Presence (POP),
and the ISP will route all outbound traffic from the City to the
rest of the Internet, and inbound traffic from the Internet to
the City. The ISP will also provide Secondary DNS, backup Mail
Exchanger services, a full NNTP USENET News feed, and 24x7 live
person technical support for troubleshooting and network operations.
Specific Requirements:
| Accept a full-speed clear channel T1 connection from the City of Pittsburgh | ||
| Route inbound and outbound TCP/IP packets between the City of Pittsburgh and the Internet, using the City's existing registered netblock of IP addresses
(205.141.128-191) | ||
| T3 or higher upstream connection, or multiple upstream connections | ||
| Documentation of upstream and downstream connectivity, so that overcommit percentage can be calculated | ||
| 24x7 Network Operations Center, phone answered by live person | ||
| No additional charges for technical support, troubleshooting, problem resolution | ||
| Single point of contact for all connectivity-related issues (ISP handles both their own services and T1-line issues) | ||
| Documented internal network design to minimize downtime (redundant equipment, backup power supplies, switchover plans, etc.) | ||
| Provide Secondary DNS service for the City domain name (CITY.PGH.PA.US) and any subdomains | ||
| Provide a full NNTP USENET News feed | ||
| Provide backup Mail Exchanger (MX) services for situations when the City's own mail server is out of operation | ||
| Assist in procurement and management of a domain name for the City (CITY.PGH.PA.US) | ||
| No restrictions on downstream connections that the City may wish to provide to affiliated or other organizations | ||
| Supply references to at least two organizations in the Greater Pittsburgh area that currently have T1 or higher connections from this ISP and are willing to discuss the service they have received from the ISP |
3.2.2 COMPONENT II - T1 leased line to ISP Point of Presence
Description:
The T1 line interconnects the City's network to the ISP's Point
of Presence. This will be a clear-channel T1 circuit (1.544Mbps).
| Full-speed clear channel T1 connection between the City of Pittsburgh and the ISP's Point of Presence | ||
| Single point of contact for all connectivity-related issues (ISP handles both their own services and T1-line issues) | ||
| Line Termination Equipment (e.g. CSU/DSU's) with proper interfaces for ISP and City router connections | ||
| Printed documentation for operation, configuration, programming, etc. of all components, e.g. CSU/DSUs. (CD-ROM based documentation is not sufficient) | ||
| Minimum 1-year support for all components (e.g. CSU/DSUs), including: hardware troubleshooting, repair, and replacement; no-fee technical support; and all software upgrades, bug fixes, documentation changes, etc. at no charge. |
3.2.3 COMPONENT III: - (2) CISCO Routers
Description:
One CISCO router connects the City's internal network to the near
side of the firewall, and the other connects the far side of the
firewall to the CSU/DSU drivers for the T1 line to the Internet.
This configuration provides a very high degree of security and
flexibility in implementing security policies.
| exterior screening router has proper interface to connect to CSU/DSU for leased line, and 10BASE-T interface to connect to firewall | ||
| interior screening router has two 10BASE-T interfaces, one to connect to firewall and one to City internal network. | ||
| both routers support TCP/IP routing with all major routing protocols. Support for other network protocols (IPX, NETBEUI, AppleTalk, etc.) or WAN interfaces (X.25, etc.) is not required. | ||
| CISCO IOS software current version | ||
| sufficient performance in each router to handle wire-speed Ethernet (10Mbps) in and out while applying Access Control Lists (ACL) of some complexity | ||
| Printed documentation for router operation, configuration, programming, etc. (CD-ROM based documentation is not sufficient) | ||
| Minimum 1-year support including: hardware troubleshooting, repair, and replacement; no-fee technical support; and all software upgrades, bug fixes, documentation changes, etc. at no charge. |
3.2.4 COMPONENT IV: (2) Sun Ultra 1 Workstations
Description:
This is the hardware platform on which the firewall software will
run. One computer acts as the Management Station, running the
management and logging software. The second computer acts as the
Firewall Station, and performs the actual filtering and inspection
of packets. The Firewall Station will have separate connections
to the City internal network and the T1 link to the Internet.
Any traffic passing between these two networks will go through
the firewall, which will inspect all traffic and enforce City
network security policies. See Figure 2 for an illustration of
how the Management and Firewall Stations interact.
In addition, any City Internet servers (World Wide Web, E-mail,
FTP, etc.) will be attached to the firewall system via an individual
Ethernet connection. Since different sets of rules can be applied
to different Ethernet ports, the firewall will be able to enforce
the security policies with a sufficient granularity to prevent
any interaction between servers in the event that any one of the
servers is compromised. See Figure 3 for a representation of
how this would be configured. This is a conceptual diagram only,
and not meant to represent the specific location of connectors
on the rear panel of a Sun Ultra 1/170E.
Component IV: (2) Sun Ultra 1 Workstations (continued)
| Both stations (Firewall & Management): | ||
| (2) 2.1 GB Internal hard drives | ||
| 128MB RAM | ||
| Standard TurboGX graphics | ||
| Internal Quad-speed 644MB SunCD CD-ROM drive | ||
| Sun 8mm DAT tape drive | ||
| Sun Internal floppy drive | ||
| Solaris operating system software License and Media (current version) | ||
| Standard Sun accessories (keyboard, mouse, mousepad, etc.) | ||
| Printed documentation for hardware and software (CD-ROM based documentation is not sufficient) | ||
| Minimum 2-year support including no-fee technical support and all software upgrades, bug fixes, documentation changes, etc. at no charge. | ||
| Management station only: | ||
| Sun Ultra 1 Workstation Model 140 | ||
| Sun 20" color monitor | ||
| Firewall station only: | ||
| Sun Ultra 1 Workstation Model 170E | ||
| (2) Sun Quad Ethernet SBUS cards | ||
| Sun 17" color monitor |
3.2.5 Component V: - Solstice Firewall-1 Software
Description:
The Firewall-1 software provides a comprehensive platform for
implementing security policies and applying them to communications
between the City's internal network and the Internet. A fine degree
of control can be exercised over the nature and origin of these
communications. Firewall-1 retains the performance advantages
of packet-filtering gateways, while using Stateful Multi Layer
Inspection (SMLI) to transparently achieve application proxy-style
control over both stream based (TCP) and datagram (UDP) connections.
Firewall-modules reside on the Firewall station and the Management
station. The Firewall station runs those modules that perform
the actual interception, inspection, control, and logging of packets,
while the Management station runs the GUI used to implement the
security policies and analyze and store log file information,
The Management station also creates and installs Access Control
Lists (ACLs) for the routers in order to provide a consistent
implementation of security policy among both the Firewall station
and the routers. Firewall-1 has the capability to control multiple
firewalls from a single Management station, using a consistent
rule base and centralized logging facilities. This provides an
ideal expansion path as the City's level of integration with the
Internet increases.
Current City plans do not call for the implementation of a Virtual
Private Network (VPN) architecture; as a consequence, the Solstice
Firewall-1 software in this RFP is not required to contain the
VPN/encryption features.
| Solstice Firewall-1 Unlimited Internet Security Center (current version) | ||
| (2) Solstice Firewall-1 Single Router Security Modules (current version) | ||
| Printed documentation for all software modules (CD-ROM based documentation is not sufficient) | ||
| Minimum 2-year support including no-fee technical support and all software upgrades, bug fixes, documentation changes, etc. at no charge. |
4.0 RFP RESPONSES:
Responses to this RFP should include the purchase, installation,
and configuration of all the required elements described herein.
The contract will be awarded to a single entity whose response
addresses all the elements of this RFP. That entity will be responsible
for the successful implementation of the project, and required
to coordinate the efforts of other entities (specified in the
response) performing separate pieces of the overall project.
Responses should include one-year support for Components I, II,
and III (ISP, T1, routers), and two-year support for Components
IV and V (Sun Ultras and Firewall-1). Additional consideration
will be given to the proposal that demonstrates a clear and cost-effective
upgrade path for moving to connection speeds above T1.
5.0 VENDOR QUALIFICATIONS
The vendor must demonstrate in the written proposal an established
base of customers in high speed dedicated Internet Services and
must have experience in the installation and implementation of
internet services. The vendor must provide a partial listing
of existing customers. This listing must include for each customer
a name, organization, address, and phone number of a person to
contact for a reference as to vendor and application performance.
6.0 INSTALLATION, TRAINING, DELIVERY AND PAYMENT
This analysis, if selected, will be conducted on site at the user's
location by qualified vendor personnel. As part of the pre-installation
analysis vendor personnel review operations and define technical
requirements. Following the pre-installation analysis, vendor
personnel will compile and document the results for user approval
prior to installation.
6.1 INSTALLATION AND TRAINING SERVICES
The vendor will offer one or more experienced Installation Specialist(s)
to travel to the user's location(s) to set up the communication
lines, service, test all service functions and train personnel
in software operations.
6.2 Documentation Available at Time of Installation
The vendor must provide a complete set of professionally published
manuals and other system documentation (including software user's
guides and operating system reference manuals) at the time of
installation. At least one copy of all documentation must be
supplied in hard copy format. CD-ROM or other electronic formats
may be used for additional copies beyond the first.
6.3 Delivery and Payment
The vendor must deliver and install a "turn-key" internet
service within 90 days after the awarding of the contract. Payment
will not be made until the service has been fully implemented
and accepted by the City.
6.4 Training
The vendor will make available the following services:
Instructors must display qualifications that demonstrate their
ability to meet the requirements of this RFP.
6.5 MAINTENANCE AND CUSTOMER SUPPORT SERVICES
The vendor will make available a consultation service on a toll
free or local access line. This service will provide same day
response to questions about support regardless of previous training.
7.0 CONTRACTURAL CONDITIONS
7.1 Rights of Assignment
The City Information Systems Office reserves the right to award
different portions of the project to different firms if upon review
of the proposal it concludes that this would allow more effective
and economical completion of the project. The City Information
Systems Office is not obligated to accept the lowest-cost proposal.
7.2 Financial Terms and Conditions
The vendor will submit monthly invoices to City Information Systems
Office for service and lease line charges, and will be paid in
conjunction with City policies and procedures.
7.3 Contractual Terms and Conditions
The contract for this project will be with the City of Pittsburgh
and with Vendor and will be administered by the Director of City
Information Systems for the Information Systems office. The Director
of Information Systems will make the final approval of the appointment
of the vendor to this service contract.
7.4 Guarantee of Functionality
The vendor guarantees, by responding to this RFP, an operational
system as described in the RFP, the proposal, and any and all
representations submitted with, reference by, or provided pursuant
to the proposal. This guarantee is not restricted by any other
term, condition, disclaimer, warranty, or guarantee.
7.5 Insurance
The City requires vendors to maintain liability insurance, with
the City as additional insured. The minimum required coverage
is not determined until after the contract is awarded and the
final scope of services is settled, but the amounts typically
are:
Public Liability Each and Property Damage Occurrence Aggregate Bodily injury, including death $500,000 $1,000,000 Property damage $500,000 $ 100,000
7.6 Worker's Compensation
The vendor must certify that it has accepted the provision of
the Worker's Compensation and Occupational Disease Acts, as amended
and supplemented, insofar as the work covered by the contract
is concerned, and that it has insured its liability thereunder
in accordance with the terms of said Acts or has duly filed a
proper certificate of exemption from insurance with the Pennsylvania
Department of Labor and Industry.
7.7 Indemnity
The vendor must agree to indemnify, save and hold harmless, and
defend the City, its officers, agents and employees against liens,
charges, claims, demands, losses, costs, attorney's fees, judgments,
liabilities and damages of every kind and nature whatsoever arising
by reason of the performance of the third party contractor, its
employees, representatives, or against any obligations under the
contract.
7.8 Patent Indemnity
The contractor shall indemnify and at all times keep the City
indemnified against any action, claim, suit, or demand, costs
or expenses arising from or incurred by reason of any infringement
of alleged infringement of any patent, design, trademark or name
copyright or other protected right, in respect or any materials,
goods, articles, services, equipment, machinery, plant or thing,
system or method of performing, using, fixing, working or arrangement
used or fixed or supplied by the vendor.
7.9 Third Party Liability
Nothing under this agreement shall be construed to grant any rights
or interests in this agreement to anyone other than the City and
the vendor, and all duties and responsibilities undertaken pursuant
to this agreement shall be for the sole and explicit benefit of
the City and the contractor and not for the benefit of any other
party.
8.0 AFFIRMATIVE ACTION AND ANTI-DISCRIMINATION
8.1 Minority and Women's Business Enterprise Participation
Minority Business Enterprise (MBE) and/or Women Business Enterprise
(WBE) participation is requested in all City of Pittsburgh contracts.
Such participation may be demonstrated by utilization of MBE/WBE
firms through the use of subcontracts with such firms in support
services, supplies, etc.
The vendor shall include in the proposal a plan on how and to
what extent the MBE/WBE participation will be utilized. Along
with the plan, the following documents from Appendix A must be
completed and submitted with the proposal:
MBE/WBE Solicitation and Commitment Statement
Bidder's Previous History
MBE/WBE Solicitation and Commitment Statement - Additional information
In order for the proposed MBE/WBE participation to be considered,
a copy of a current MBE/WBE certification for the vendor or subcontractor
must be submitted with the proposal. Only ceritifications by
the City of Pittsburgh, County of Allegheny, Pennsylvania Department
of Transportation (PennDot), the Commonwealth of Pennsylvania
- Department of General Services, or other recognized government
entity will be accepted.
The goals suggested by the City of Pittsburgh for the MBE and/or
WBE utilization are 25 percent MBE and 10 percent WBE of the dollar
volume of the contract.
8.2 Anti-Discrimination
The vendor must conform with the applicable sections of the Pittsburgh
Code: Title Six - Conduct and Article V -Discriminaion.
8.3 Debarment
Vendor will warrant that it is not prohibited from ultimately
entering into an Agreement with the City by reason of disqualification
under Subsection (b) of Section 161-22 of the Pittsburgh Code.
An affidavit certifying compliance with this Section is attached
in APPENDIX A and will be incorporated into and made a part of
an Agreement.
8.4 Statement of Affiliation
The Vendor shall file a Statement of Affiliations with the City
of Pittsburgh Board of Ethics within thirty (30) days of the Execution
of an Agreement. The statement of Affiliation shall include:
A) A description of any contractual or other business relationship with the City or any of its department, agencies, boards, commissions or authorities, including the value of the contract or business relationship entered into during the three (3) calendar years previous to the execution of the Agreement.
B) The vendor's qualifications and experience which shall be
applied to the performance of the Agreement.
C) An identification of the Contractor's principals, including
the names and addresses of all owners or partners or shareholders
and officers, or, if the Consultant is a public corporation, the
officers, the members of the Board of Directors, and shareholders
holding more than three (3) percent of the corporate stock.
The Statement of Affiliations shall be filed in accordance with
any rules of procedures established by the Board of Ethics.
9.0 RESPONSE, EVALUATION AND SELECTION PROCEDURES
9.1 Proposal Format and Contents
Proposals should explain Vendor's recommended choice of techniques
for each task in Section 3.0 Scope of Services, and the rationale
behind his/her choice, and should include in particular the following:
Personnel, their task assignments in this project, and their
qualifications, including the professional/instructional qualifications
of teaching personnel that demonstrate their ability to fulfill
the requirements of this project.
The experience and capabilities of the Vendor in performing projects
of this type.
A description of the procedures and topics to be developed and
an outline for training ideas.
Complete documentation for the use of software.
Estimated costs (see 9.3)
9.2 Modifications
Where a firm would recommend modifications of changes in the provisional
technical or operational specifications, these should be clearly
noted.
9.3 Cost Estimates
The cost section of the proposal shall contain the following,
clearly identified subsections:
Total Bid Price - the total bid prices for all application services,
including but not limited to software, software modifications,
training, support, equipment, travel, room, board and supplies
and other items needed for the completion of the contract excepting
those specifically stated to be the vendor's responsibility in
the RFP.
Itemized Costs - itemized costs for each task or service provided
must be explicitly stated.
Additional Rates - rates for additional service options that are
not part of the contract and the conditions under which they are
invoked should be explicitly stated.
Maintenance Contract - the vendor must submit maintenance payment
information for hardware for a one (1) year period.
9.4 Vendor Qualifications and Selection Criteria
Firms must be capable of performing and properly completing each
of the items specified in this request for proposal. A proposal
will not be acceptable from any firm that does not submit complete
information on the qualifications and performance of its organization.
Information shall include statement setting forth the proposed
organization's business and technical program, its financial resources,
description of equipment and personnel available for the project,
previous experience in software development and training; and
other information deemed pertinent to this project.
9.5 Selection Criteria
The firm will be selected on the basis of:
Compliance with the selection criteria and process specified
in this section,
The extent to which written proposal addresses items specified
in Scope of Services section of this request,Cost and merits of
the proposed work program,
Qualifications and capabilities of the vendor and its personnel,
Possibly, an interview (non-reimbursable) with the representative
of the firm.
9.6 Selection Procedure
This request for proposals will be advertised in newspapers of
general circulation in the Pittsburgh Area on Sunday, June 23,
1996. The RFP will be mailed Friday, June 21,1996 to pre-selected
firms known to City Information Systems as offering services in
the field of Internet Services.
Firms having questions about the request for proposal may submit
them in writing to Howard Stern, Assistant Director, City Information
Systems, Public Safety Building, 4th Floor, 100 Grant
Street, Pittsburgh, Pennsylvania 15219.
Proposals should be sent by certified mail or any other means
that guarantees a signed receipt.
Proposals must be received at City Information Systems Office,
City of Pittsburgh, Public Safety Building, 4th Floor,
100 Grant Street, Pittsburgh, PA 15219, by 5:00 p.m., Friday,
July 12, 1996.
Each firm shall submit three (3) copies of its proposal.
After initial review and discussion of the proposals, City Information
Systems may interview those firms that it selects as finalists.
Any oral interviews with the finalists would be conducted in the
City Information Systems office. Firms invited to the oral interview
will not be reimbursed for travel, or other costs associated with
the visit. Interviews will last not more than one hour, of which
the first 15 minutes will be set aside for the firm's presentation
and the remainder devoted to questions and discussion.
So that the development and implementation of the internet services
may begin quickly, the City Information Systems office will make
its final selection and notify the firm selected as soon as possible
after the interviews. Notification may be delayed, however, pending
enactment of a City Council Resolution authorizing expenditures
for this project.
9.7 Selection Schedule
DAY DATE TASK Sunday June 23, 1996 Project advertised & mailed to known consultants Friday July 12, 1996 Deadline for receipt of Proposals, 5:00 p.m. Friday July 19, 1996 Short list selected. July 19-26, 1996 Interviews of short-listed firms Friday July 26, 1996 Proposal negotiations: by telephone Friday August 2, 1996 Final selection pending City authorization
9.8 Choice of Features
This RFP is intended to give respondents guidance as to the features
and capabilities that the City Information Systems office expects
to find necessary or useful in serving its needs. However, the
City Information Systems office may at its sole discretion choose
to make use of different features and capabilities if the City
determines that they would more effectively serves its interests.
Selection and Reject Bids
The City Information Systems office reserves the right at its sole discretion to change the process, schedule, terms and conditions, specifications, and criteria for selecting a proposal or awarding a contract. The City Information Systems office reserves the right to reject any and all proposals.