CITY OF PHOENIX STREET TRANSPORTATION DEPARTMENT …bids.centerdigitalgov.com/NAV_KCC_ 11-21-2007_...

CITY OF PHOENIX STREET TRANSPORTATION DEPARTMENT

REQUEST FOR PROPOSAL (RFP)

ITS WIRELESS PROJECT

RFP ISSUE DATE 8:00 A.M. (M.S.T.) ON NOVEMBER 21, 2007

PRE-PROPOSAL CONFERENCE

2:00 P.M. (Arizona Time) ON DECEMBER 6, 2007 City of Phoenix Personnel Building

135 North Second Street, First Floor Test Room Phoenix, AZ 85003

DEADLINE FOR RECEIVING PROPOSAL

1:00 P.M. (Arizona Time) ON DECEMBER 19, 2007 City of Phoenix - Street Transportation Department

Attn: ITS WIRELESS PROJECT RFP 200 West Washington Street, 5th Floor

Phoenix, AZ 85003-1611

PROPOSAL OPENING 1:00 P.M. (Arizona Time) ON DECEMBER 19, 2007 City of Phoenix Street Transportation Department

200 West Washington Street, 5th Floor Phoenix, AZ 85003-1611

CONTACT PERSON Ms. Joyce Dreyer, Management Services Division City of Phoenix Street Transportation Department

200 West Washington Street, 5th Floor Phoenix, AZ 85003

(602) 534-1622

This RFP can be made available in Braille, large print, audio tape, or cassette tape upon request. Contact the Street Transportation Department at 602-262-6284 if you would like any of these services. Our TTY phone number is 602-256-4286.


RFP FOR ITS WIRELESS PROJECT

September 26, 2007 Page 2 of 56

TABLE OF CONTENTS

SECTION PAGE I. INTRODUCTION

A. Overview...............................................................................................5 B. Glossary................................................................................................6

II. BACKGROUND

A. Background...........................................................................................8

III.... M/W/S/DBE COMMITMENT A. M/W/S/DBE Commitment .....................................................................9

IV. FEDERAL FUNDING

A. Federal Funding....................................................................................9 V. SCOPE OF WORK

A. Functional Requirements Overview ......................................................9 B. Physical Location and Environment....................................................11 C. Equipment Installation.........................................................................12 D. Traffic Controller Interface ..................................................................13 E. Security Requirements........................................................................13

VI. EXISTING EQUIPMENT

A. Traffic Signal Controllers.....................................................................15 B. Remote User Laptop Computers ........................................................15 C. IP Closed Circuit Television Camera (CCTV) .....................................16 D. Autoscope CCTV CODEC ..................................................................16 E. Miscellaneous ITS Equipment ............................................................16

VII. PROFESSIONAL SERVICES

A. Tasks to be Completed.......................................................................16 B. Testing ................................................................................................17 C. Training...............................................................................................20 D. Warranty .............................................................................................21 E. Extended Warranty .............................................................................21 F. Technical Support Requirements........................................................22

VIII. TECHNICAL PROPOSAL FORMAT

A. Introduction............................................................................................22 B. Submission Requirements.....................................................................23




IX. EVALUATION OF PROPOSALS A. Evaluation Process................................................................................28 B. Evaluation Criteria .................................................................................29 C. Schedule ...............................................................................................30

X. OFFEROR RIGHTS

A. Offeror Rights .....................................................................................30 B. City Reservation of Rights ..................................................................31 C. Late Proposals Not Considered ..........................................................31 D. Inconsistency or Error in the RFP .......................................................31 E. Offeror Errors or Omissions ................................................................31 F. Addenda .............................................................................................31 G. Offeror Incurred Costs ........................................................................32 H. Modification or Withdrawal of Proposal...............................................32 I. Offeror Certification.............................................................................32 J. Exceptions ..........................................................................................32 K. City’s Right to Disqualify for Conflict of Interest ..................................32 L. Warranties ..........................................................................................33 M. Covenant Against Contingent Fees ....................................................33 N. Gratuities ............................................................................................33 O. Affirmative Action in Employment ....................................................34 P. Order of Precedence...........................................................................35 Q. Protest of Award .................................................................................35 R. Offeror Inquiries ..................................................................................35 S. News Releases...................................................................................36

XI. GENERAL TERMS AND CONDITIONS

A. Compliance with Laws ........................................................................36 B. Federal-State-City Excise Taxes ............................................................... 36 C. Tax Responsibility Qualification … .....................................................37 D. Non-Waiver of Liability ........................................................................37 E. Indemnity Clause ................................................................................37 F. Offset Provisions.................................................................................38 G. Applicable Laws..................................................................................38 H. Organization Employment Disclaimer.................................................38 I. Method of Payment.............................................................................39 J. Liens ...................................................................................................39 K. Remedies............................................................................................39 L. Transactional Conflicts of Interest.......................................................39 M. Delay in Exercising Contract Remedy.................................................39 N. Quality and Acceptability of Work .......................................................39 O. Confidentiality of Information ..............................................................40 P. Fund Appropriation Contingency ........................................................40 Q. Insurance ...........................................................................................40




XI. ATTACHMENTS AND EXHIBITS

Attachment A –Project Location Map..........................................................44 Attachment B – System Requirements .......................................................45 Attachment C – Financial Proposal.............................................................49 Attachment D – Affirmative Action Form and Instructions...........................51




I. INTRODUCTION A. OVERVIEW The City of Phoenix (City) is seeking proposals from qualified individuals or firms to provide equipment, implementation assistance, training, and maintenance assistance for a new mesh wireless/fiber optic hybrid communication system (Wireless WAN) for the City which shall be primarily used to transmit data bi-directionally between traffic signal controllers and the City’s Traffic Management Center (TMC). The wireless WAN is also required to be capable of providing a secure method in which other applications and user groups can co-exist on the network without interfering with the Wireless WAN’s primary traffic management function. The initial phase of the ITS Wireless Project will encompass twenty (20) intersections located in the City of Phoenix within the geographic boundaries of E. Camelback Rd, 60th St., E. Indian School Rd., and N. 32nd St. The system shall be required to have a mesh architecture which includes; remote user access, wireless point-to-point, wireless backhaul, and fiber optic backhaul links to provide reliable data transmission service and protect the City’s traffic signal system wireless network against unintentional and/or malicious intrusions. The optimum proposed system would be scalable with little or no operational disruption to the network, self-configuring, and provide access for the greatest number of future remote employee users while maintaining a high level of security. The Wireless WAN is not intended nor required to be a primary system for life-safety communication. The City would like to utilize this project to become self-sufficient in the installation, configuration, and maintenance of the wireless WAN. The Proposer shall be required to provide all materials required to implement the Wireless WAN. City forces will provide all labor to install the materials and the Proposer shall provide on the job training for City employees in the design, installation, operation, troubleshooting, and configuration of the ITS Wireless WAN. The Proposer shall also be required to provide guidance and on the job training to the City during the design, RF survey, testing, and troubleshooting phases of the ITS Wireless project. Upon successful performance of the ITS Wireless Project, the City intends to increase the coverage area of the ITS Wireless Project to provide wireless communications to approximately 59 additional intersections. There are sufficient City forces available to perform all of the physical installation work required to expand the wireless network to the 59 intersections which are beyond the project limits of this RFP. It is the City’s intention to purchase equipment and utilize on-call remote and/or on-site technical assistance from the successful Proposer to facilitate the 59 intersection expansion.




B. GLOSSARY

Addressable Port

A data port that can be assigned a unique ID number which monitors data traffic on the network and only responds to data packets containing the port’s unique ID number

AES Advanced Encryption Standard – A NIST standard for encrypting data using a block cipher

ANSI Acronym for the American National Standards Institute

Authenticate Verifying the source and integrity of a transmitted message to ensure that the contents of the message have not been tampered with or sent from an unauthorized source.

Data Throughput

The data transmission speed of a communications link in bits or bytes per second calculated by subtracting overhead bits for network control and security from the aggregate link speed.

dBm A measurement of power in decibels using 1 milliwatt as a reference point. A signal level of 1 milliwatt is equivalent to 0 dBm.

Dedicated Bandwidth

A portion of a network’s data transmission capacity that is reserved solely for one user or group which can not be utilized by any other users of the network.

Directional Antenna

An antenna that receives and radiates electromagnetic energy in a focused narrow beam. (i.e. Yagi Antenna)

DoS (Denial of Service)

A network condition where excessive user requests for service exceed network backhaul point capacity causing data traffic and remote user access to be severely slowed or completely interrupted

EIA Acronym for Electronic Industries Alliance

Ethernet Term which is generally accepted to be synonymous with the IEEE 802.3 networking standard

Fault Tolerant

Method of providing reliable communication service by detecting network component failure, overload, and loss of signal conditions and automatically re-routing data from the compromised unit to a properly functioning unit.

FCC

Acronym for Federal Communications Commission which is a U.S. government agency that regulates interstate and international communications including wire, cable, radio, TV and satellite.

Full-Duplex Term for data communication protocol which permits the transmission and receiving of data simultaneously.

IEEE Acronym for Institute of Electrical and Electronics Engineers IEEE 802.11a/b/g

IEEE standard for wireless local and metropolitan area networks




IEEE 802.11i IEEE standard for security and privacy of data across wireless local and metropolitan area networks

IEEE 802.3 IEEE standard for wired local and metropolitan area networks

IP Address Internet Protocol address which is comprised of four numbers (0-255) separated by decimal points which provides a unique numeric label for each element connected to the network.

ITD City of Phoenix Information Technology Department ITS Intelligent Transportation System LAN Acronym for Local Area Network

Latency

Amount of elapsed time required to receive a data packet after it has been transmitted. Includes time added from the transmission medium, security protocols, authentication, encryption, and overhead.

MAC Address

Acronym for Media Access Control address which is a unique serial number permanently stored into Ethernet network equipment by the equipment manufacturer.

Mbs Acronym for a data transmission rate of one million bits per second

NEMA Acronym for National Electrical Manufacturers Association

NEMA 4X NEMA rating for equipment enclosures which protect equipment from damage from falling rain, splashing water, hose-directed water, corrosion, and windblown dust and rain.

Omni-Directional

Term used to describe an antenna that receives and radiates electromagnetic energy in all directions.

PCMCIA Acronym for Personal Computer Memory Card International Association

QoS Quality Of Service - A defined level of performance in a data communications system which gives real time data priority over non-real time data.

Remote User

Streets Transportation Department employee with a laptop computer equipped with a wireless NIC used to access to the traffic signal network from any of the wireless backhaul locations

RF Acronym for Radio Frequency

Scalable

Term for a network that is expandable and can accommodate an increase in users and capacity by adding network equipment without necessitating redesigning or replacing existing network equipment.




Self-configuring

Method of network operation where wireless backhaul and satellite radios automatically discover adjacent neighboring radios and form wireless links with neighbors that maximize network performance and establish new links with other neighbors if the performance of its currently connected link fails or degrades.

Session Hijacking

Method used to obtain network access by unauthorized persons by causing a legitimate user to be disconnected from the network and then capturing and mimicking the identity of the disconnected user.

SSID Acronym for Service Set Identifier which is a text string name assigned to wireless network access points which is broadcast to user PCs with compatible wireless equipment.

Static IP A method of manually assigning an IP address to a device that is stored in the device’s memory.

TCP Acronym for Transmission Control Protocol which is a network transport protocol which ensures that all data at the receive end of a transmission is error free and intact.

10/100/1000BaseT

IEEE standard for 10Mbps, 100Mbps, and 1000Mbps data rate transmission using unshielded twisted-pair copper cables.

Transceiver Network device that contains both a transmitter and receiver which permits simultaneous sending and receiving of data.

UDP Acronym for User Datagram Protocol which is a method of packaging and transmitting data over an Ethernet network without using flow control or error checking.

WAN Acronym for Wide Area Network

II. BACKGROUND

The primary user of the wireless WAN is the Street Transportation Department which is responsible for planning and providing for the safe, efficient and convenient movement of people and goods on city streets by responding to transportation needs in relation to street capital improvement planning, street maintenance and pavement management, traffic engineering, traffic signal construction and maintenance, and traffic safety coordination. Secondary users of the wireless WAN may include any other City of Phoenix Department.




III. M/W/S/DBE COMMITMENT The City of Phoenix Street Transportation Department is committed to utilizing qualified Minority-Owned, Women-Owned, Small and Disadvantaged Business Enterprise (M/W/S/DBE) firms for professional services contracts.

IV. FEDERAL FUNDING This project is funded by Federal aid and City funds.

V. SCOPE OF WORK

A. FUNCTIONAL REQUIREMENT OVERVIEW. The selected Proposer shall provide on the job training and guidance to City employees in the design, installation, configuration, troubleshooting, and operation of the ITS wireless WAN and shall furnish all required materials to implement a geographically distributed wireless mesh network that is centrally managed and supported from the Street Transportation Department. All installation labor shall be provided by City forces under the guidance of the selected Proposer. The ITS Wireless WAN supplied by the selected Proposer shall, at a minimum, comply with the following:

1. Utilize radio frequencies which DO NOT require FCC licensing.

2. Utilize existing fiber optic cable connection and existing 100Mbps layer 2

Ethernet switches located at E. Indian School Rd./44th St. and E. Camelback Rd./N. 32nd St. to facilitate a fiber optic backhaul to the Traffic Management Center (TMC), located on the 6th Floor of Phoenix City Hall. All fiber optic backhaul equipment and cabling is existing.

3. Proposed equipment shall be in current production and may be standards based or proprietary. Proposed equipment is required to provide IEEE 802.11a/b/g compatibility.

4. Furnish five (5) wireless PCMCIA network interface cards (NIC) to the City to be installed in City owned laptops. The NICs shall be compliant with IEEE 802.11 a/b/g as required to provide remote users with connectivity to the traffic signal WAN via any wireless backhaul point. The NICs shall support hardware based encryption compliant with IEEE 802.11i 128bit Advanced Encryption Standard (AES).




5. Proposed equipment shall provide IEEE 802.3 full-duplex, Auto-negotiating, 10/100 Mbps compatible interfaces at each traffic signal controller.

6. Proposed equipment shall be in current production and may utilize standards based or proprietary components. Proposed equipment is required to provide security by transmitting all data end-to-end using hardware based IEEE 802.11i 128bit Advanced Encryption Standard (AES) compliant equipment.

7. Provide a method of allocating a portion of bandwidth that shall be dedicated to communications between the TMC and the traffic signal controllers. The network should be able to assign priorities to user groups and be able to dynamically allocate unused network capacity from higher priority users to lower priority users when excess capacity in the higher priority group is available.

8. Support multiple fiber optic cable backhaul points which shall enable network legs to be backhauled to the City traffic signal LAN, located in the TMC, to increase network capacity and number of remote users.

9. Be scalable by adding capacity to existing installations without the need to replace previously installed equipment to increase the number of remote users or intersections.

10. Equipment shall be designed to be installed outdoors within the Phoenix, Arizona metropolitan area without environmental conditioning and mounted on existing traffic signal poles, mast arms, and traffic signal controller cabinets. The installation shall be required to be performed without “breaking ground” and may utilize existing power sources and conduits.

11. Provide standalone wireless point-to-point or point-to-multipoint satellite

link which shall be mounted on the traffic signal control cabinet. All required transceiver and antenna equipment shall be required to be located within or on the existing traffic signal controller cabinet. This is to be used at locations where the installation of cables within existing conduits and signal poles is not feasible.




B. PHYSICAL LOCATION AND ENVIRONMENT

1. The intersections included in the project are categorized in the following manner:

a) Wireless Backhaul – Intersection is desired to be part of the wireless backhaul

b) Satellite – Intersection is required to be part of the Wireless WAN and may or may not be part of the wireless backhaul. This intersection may require the use of a standalone wireless bridge. Satellite locations are not intended to be used as network access points for remote users.

c) Fiber Backhaul – Intersection is the transition point from Wireless transmission to transmission over fiber optic cable. Controller at this location is not connected to the Wireless Network.

d) Remote User – Streets Transportation Department employee with a laptop computer equipped with a wireless NIC used to access to the traffic signal network from any of the wireless backhaul locations.

2. Intersection Locations and Proposed Category (See Appendix A)

1) E. Indian School Rd/ N. 56th St. - Wireless Backhaul 2) E. Indian School Rd/ N. 48th St. - Wireless Backhaul 3) E. Indian School Rd/ N. 47th St. - Satellite 4) E. Indian School Rd/ N. 44th St. - Fiber Backhaul 5) E. Indian School Rd/ N. 40th St. - Wireless Backhaul 6) E. Indian School Rd/ N. 38th St .- Satellite 7) E. Indian School Rd/ N. 36th St. - Wireless Backhaul 8) E. Indian School Rd/ N. 32nd St. - Satellite 9) E. Lafayette Blvd./ N. 56th St. - Satellite 10) E. Campbell Ave./ N. 44th St. - Satellite 11) E. Campbell Ave./ N. 40th St. - Satellite 12) E. Campbell Ave./ N. 36th St. - Satellite 13) E. Campbell Ave./ N. 32nd St. - Satellite 14) E. Camelback Rd./ N. 60th St. - Satellite 15) E. Camelback Rd./ N. 56th St. - Wireless Backhaul 16) E. Camelback Rd./ N. Arcadia Dr. - Wireless Backhaul 17) E. Camelback Rd./ N. 44th St. - Wireless Backhaul 18) E. Camelback Rd./ N. 40th St. - Wireless Backhaul 19) E. Camelback Rd./ N. 36th St. - Satellite 20) E. Camelback Rd./ N. 32nd St. - Fiber Backhaul




C. EQUIPMENT INSTALLATION

1. Equipment shall only be mounted on existing traffic signal poles, mast arms, combination traffic signal/luminaire poles, and inside traffic controller cabinets. The contractor may use existing traffic signal poles and existing conduits as cable raceways with prior approval of the City. The contractor shall provide drawings which show the type, size, and proposed destination of each cable the contractor desires to have installed in existing infrastructure at each intersection. City forces shall determine if the proposed installation is feasible and notify the contractor of its findings. If the proposed installation is deemed feasible by the City, the contractor shall furnish the cables to the City to be installed by City forces.

2. No external environmental control devices shall be allowed to be installed. All equipment shall have an operating temperature range of -20°C to +55°C with 0-95% Humidity, non-condensing.

3. All housings for equipment mounted on traffic signal poles, mast arms, or combination traffic signal/luminaire poles shall be rated NEMA 4X. A drawing of the proposed equipment housing is required to be provided in the Proposer’s response to this RFP.

4. It is preferred that a minimal amount of equipment be located within the

controller cabinet due to limited or no space available and the non-uniformity of available space from intersection to intersection.

5. Installation shall not involve trenching or excavating.

6. All proposed equipment shall be capable of being powered by both

120VAC and 240VAC which is existing in traffic signal poles, luminaires, and controller cabinets. Traffic signal equipment cabinets are only equipped with a 120VAC power source.

7. The Proposer shall submit power requirements for each intersection to the

City who shall determine if adequate power is available to meet the contractor’s requirements. The power connection shall be such that failure of the wireless equipment for any reason shall not interfere with the operation of the traffic controller or signal heads.

8. Existing traffic signal poles and mast arms may be used as cable

raceways with the approval of the City. Cables and or conduits shall not be allowed to be installed on the exterior of the traffic signal poles or cabinets.




9. Intersections shall not be taken out of service during installation. All traffic control required by City Policy and Standards shall be followed.

10. All field connections to traffic controller equipment shall be performed by a

representative of the Street Transportation Department. Selected Proposer shall provide instruction and guidance to the Street Transportation Department representative in the connection of WAN equipment to the traffic signal controllers.

11. All wireless equipment and associated cabling installation shall be

performed by a representative of the Street Transportation Department. Selected Proposer shall provide instruction and guidance to the Street Transportation Department representative in the installation of the wireless equipment and associated cabling.

12. Any antennas installed on the tops of cabinets shall be vandal proof low

profile “Hockey Puck” types. Installation shall be done in a manner that absolutely prevents any ingress of moisture or other contaminants.

13. Antennas between intersections may be directional or omni-directional.

D. TRAFFIC CONTROLLER INTERFACE

1. The current traffic controllers are capable of communicating with the central computer via a 10Mbps Ethernet interface.

2. All equipment proposed by the Proposer shall automatically reset, maintain its configuration settings, and be ready for communications within 60 seconds following any power interruption regardless of the nature of the power failure or interruption(s).

3. All field devices proposed by the Proposer shall survive the NEMA TS2-2003 surge and transient testing along with the CALTRANS TEES surge and power interruption testing. If additional protection is required, it must be supplied by the Proposer.

E. SECURITY REQUIREMENTS

1. The Proposer’s security options for the Wireless WAN will be a major factor in the evaluation of Proposals. The traffic controllers are not capable of supporting any security protocols currently available; therefore, it is required that the equipment proposed by the Proposer authenticate




the source of and encrypt the commands sent to the traffic signal controllers.

2. The traffic controllers transmit and receive data via an RJ45 10Mbps Ethernet port, but do not have the capability to authenticate the data transmission source nor the ability to encrypt data. The wireless network is required to transmit all data end-to-end between the traffic controller and the central computer using a hardware based IEEE 802.11i 128bit Advanced Encryption Standard (AES) secure interface.

3. The wireless network is required to authenticate that the source of all data transmissions to the traffic signal controller is from the TMC. Authentication capability is mandatory for every data interface.

4. The wireless network is required to support the data transmission requirements listed in Section IV.A while maintaining the secure connection.

5. The Proposer is required to document all security capabilities of the proposed system equipment and identify the security options the Proposer shall be implementing for the Wireless WAN. At a minimum, the Proposer shall address each of the network security items listed below providing detail pertaining to method of protection, cost of implementing, effect on network availability, latency, and throughput.

a) Protection of the Service Set Identifier (SSID) label.

b) Prevent unauthorized users from authenticating and associating with a wireless backhaul.

c) Intrusion detection capability.

d) MAC addresses filtering capability.

e) Data Encryption method used.

f) Detection of malicious Access Points acting as relay stations between authorized remote users and wireless backhaul Points.

g) Remote user and wireless backhaul Point equipment’s handling of denial of service (DoS) situations such as overloading the resources of the wireless backhaul Point with service requests from unauthorized users, electromagnetic interference, and continuous transmission of dissociation and/or de-authentication frames to mobile users.




h) Prevention of session hijacking.

i) Proposer shall provide information on network security features contained within IEEE 802.11i which are supported by the Proposer’s system. Proposer shall also indicate which features shall be implemented by the Proposer along with the cost of implementing, effect on network availability, latency, and throughput.

VI. EXISTING EQUIPMENT The ITS wireless WAN shall be designed with sufficient capacity to accommodate the bandwidth requirements of the following ITS devices:

A. TRAFFIC SIGNAL CONTROLLERS

1. Data Communications - RJ45, IEEE 802.3 10BaseT

2. Transmits 85 bytes1 of data to the TMC every second

3. Receives 50 bytes1 of data from TMC every second

4. Wireless network can not add more than 50ms of total latency to the total data transfer time

1 Note: Data figures are for transmission over an unsecured Ethernet network. Proposer shall consider the additional overhead introduced by the security requirements when designing the Wireless WAN

B. REMOTE USER LAPTOP COMPUTERS

1. Pentium III or higher CPU

2. Windows 2000, Windows XP

3. 128MB RAM

4. Available PCMCIA Slot for Wireless Network Interface




C. IP CLOSED CIRCUIT TELEVISION CAMERA (CCTV)

1. 480 Line Resolution, 30 frames per second

2. Bit rate requirement– 1.5Mbps (located along major streets with 1 mile spacing)

D. AUTOSCOPE CCTV CODEC

1. Fixed B&W cameras used for vehicle detection at approximately 50% of intersections

2. Four (4) cameras at each intersection requiring a combined approximate bandwidth of 2Mbps.

E. MISCELLANEOUS ITS EQUIPMENT

1. Signal Pre-emption

a. Bit rate requirement– 19.2 Kbps

2. Conflict Monitor

a. Bit rate requirement– 19.2 Kbps

VII. PROFESSIONAL SERVICES A. TASKS TO BE COMPLETED The selected Proposer, prior to providing equipment, must complete the following tasks:

1. Assist and train City forces in performing an RF survey of the Project area. Proposer shall provide all required test instruments.

2. Review and comment on the suggested wireless intersection types proposed in Appendix A – Project Location Map

3. Develop installation details including equipment mounting details, power requirements, proposed use of existing conduit, equipment mounting locations, equipment lists, RF path loss calculations, expected area of coverage for remote users, and expected data throughput and latency between each location and the TMC. This plan shall be submitted to the City for review and approval.




4. Develop detailed training plan. This plan shall be submitted to the City for

review and approval prior to commencing any design or installation assistance activities.

5. Provide forty eight (48) hours notice prior to any anticipated need for the

presence of City Staff.

6. Prior to beginning implementation activities, provide an installation schedule with accurate dates. The City has tentatively set February 1, 2008 as the start date of the implementation of the ITS Wireless Project. The schedule shall cover a two week period and shall be updated at the end of each work week and submitted to the City Project Manager prior to the beginning of the next work week.

7. Identify Traffic Management Center access, installation, and testing needs and provide a written request to the City Project Manager a minimum of five (5) working days in advance to ensure that proper arrangements can be made.

8. Provide any proposed upgrades or changes to the City’s wired LAN in City Hall to the Project Manager and ITD at least fourteen (14) days prior to any scheduled modification. Modifications must be approved in writing by both ITD and the Street Transportation Department Project Manager before any modifications are made. No modification to the City LAN shall be made without a representative of both ITD and Street Transportation Department present. All hardware and software must conform to City standards and specifications where applicable, and installation shall conform to standard City procedures where applicable.

9. Provide on-call remote technical support via telephone and provide on-

call on-site technical support.

B. TESTING The selected Proposer shall perform Post Installation testing and System Acceptance Testing on the fully installed network.

1. Post Installation Testing

The selected Proposer shall develop Post Installation test procedures for each item listed below. At a minimum, the test procedures shall define the test areas, test conditions, test methods, required test equipment, test set up, and expected results. All testing results and performed modifications




and repairs shall be documented in a report delivered to the City Project Manager by the selected Proposer.

a. Perform an RF survey at each transceiver location to measure the

level of interference at each channel frequency used by the transceiver. The test shall be performed during hours of peak public wireless usage (Monday thru Friday between 10am and 3pm Arizona Time).

b. Measure transceiver input and output power at each location.

Measurements shall be taken at the connection point between the antenna and the transceiver.

c. Measure Bit Error Rate (BER) between the TMC and each intersection

to demonstrate that it is not greater than the equipment manufacturer’s specifications for the measured received power level of the link under test.

d. Measure maximum achieved bit rate between the TMC and each

intersection.

e. Measure data throughput for both UDP and TCP traffic using 100 byte packets and 1000 byte packets between the TMC and each intersection with system operation parameters set to the same values that will be used when the system will be put into operation.

f. Measure the round-trip delay for 100 byte UDP packets between the

TMC and each intersection with system operation parameters set to the same values that will be used when the system is put into operation.

g. Measure coverage area and performance for remote users at

Intersection #13 which shall include:

1) A map of the area around the wireless backhaul which defines the coverage area for remote users shall be provided. Coverage area shall be determined by plotting points around the wireless backhaul where the measured RF field strength is at the minimum required level for proper operation between remote user devices and the wireless backhaul. The number of test points shall be sufficient to accurately chart the coverage area.

2) Verify proper operation for different field strengths by measuring

the received power level and the corresponding data rate




achieved at that signal level. Compare the results to the equipment manufacturer’s specifications for data rates at specific received power levels to demonstrate proper operation and set up.

Manufacturer Specification Measured Results

Data Rate (Mbps)

Received Power Level (dBm)

Data Rate (Mbps)

Received Power Level (dBm)

h. Demonstrate that network redundancy is as described herein.

i. Demonstrate that the power interruption and transient characteristics of equipment meet the requirements described herein.

2. System Acceptance Test

System Acceptance Testing shall be performed after successfully completing the Post Installation Test. The System Acceptance Test shall have a duration of 30-days and shall verify that each traffic signal on the ITS Wireless WAN is accurately and reliably communicating with the traffic signal system control software at the TMC. The traffic signal control system software communicates with each traffic signal once per second. The traffic signal control system will monitor communications with each traffic signal controller connected to the wireless WAN on a 24 hour, 7 day week basis and generate logs documenting successful and unsuccessful communication attempts with each traffic signal controllers. During the 30-Day SAT Test, City staff will review the communication logs generated by the traffic signal control software on a daily basis on City work days and notify the Contractor of any failures.

The System Acceptance Test shall be considered successful if the average communication success rate of all intersections is 95% or better over the entire 30-Day test period.

If an intersection’s communication success rate drops below 95% during any 24 hour period, the test will be suspended and the Contractor shall be notified of the failure(s). The Contractor shall troubleshoot the failure(s) and shall report the cause of the failure(s) and any required corrective measures to the Street Transportation Department Project Manager. After all necessary repairs have been completed, the 30-Day test shall resume and the test period shall be extended by the number of days required to troubleshoot and correct the problem.




If more than three (3) intersections fail to achieve a communication success rate of 95% during any 24 hour period or any one intersection’s communication success rate falls below 80%, the 30 Day test shall be stopped and the Contractor shall be notified of the failure(s). The Contractor shall troubleshoot the failure(s) and shall report the cause of the failure(s) and any required corrective measures to the City Project Manager. After all necessary repairs have been completed, the 30-Day test will be restarted and the duration of the test period shall be extended by 30 days from notification by the Contractor that the network is operating properly.

After the 30-Day System Acceptance Test is successfully completed, the twelve (12) month warranty period shall begin.

C. TRAINING

1. It is the City’s intent to become self-sufficient in the design, installation, configuration, operation, testing, troubleshooting, and maintenance of the wireless WAN and is a key objective of the ITS Wireless Project. The Proposer’s training plan will be an important part of the proposal evaluation process.

2. The Proposer shall provide hands on training for City employees in the

design, installation, configuration, testing, troubleshooting, and maintenance of the ITS Wireless Network. The training shall be provided on the job and shall be conducted during the design, installation, testing, configuration, and maintenance phases of the project. The Proposer shall incorporate the training requirements identified herein into the project schedule submitted with the Proposer’s proposal.

3. The Proposer shall provide network operation, monitoring, and remote

device management training for Street Transportation Department network administrators. The training shall consist of both classroom and hands on instruction. Training shall be performed by the Proposer within the City of Phoenix, AZ. The City will provide a room for the Proposer to use while conducting the training.




4. The Proposer shall submit an outline showing the logical sequence of activities the Proposer’s team will follow in designing, installing, configuring, maintaining, training, and testing the ITS Wireless Project. Along with the outline, the Proposer shall include a brief description of the type of on the job training and classroom training that shall be provided by the Proposer during each activity.

D. WARRANTY

The selected Proposer shall be required to provide warranty service for the proposed system during the entire installation phase and for a minimum of twelve (12) months of operation. The warranty period shall begin after all twenty (20) intersections have successfully completed the thirty (30) day acceptance test. The twelve (12) month warranty period shall commence for intersections added to the network, which are not included in the initial twenty (20), on an individual intersection basis after the intersection successfully completes its thirty (30) day acceptance test. This warranty service shall cover any and all hardware, software and services provided and/or installed by the selected Proposer to maintain reliable operations.

E. EXTENDED WARRANTY

1. Depot Repairs: The proposal shall include a cost for depot repair services

that shall cover all equipment provided as part of the system. The price quoted shall be complete and shall assume that the City either delivers the defective equipment to a depot within the City limits or ships the unit to the service center in shipping cartons or containers provided by the service center. The service center shall repair or replace the unit and return it to the City’s maintenance shop within ten (10) working days of receipt. The price quoted shall list two different costs: an exchange and a depot repair; under the depot repair, the defective unit shall be repaired or replaced at the service center’s option. Under the exchange repair, the service center shall immediately ship a replacement unit to the City concurrent with the City’s shipment of the defective unit to the service center. Prices quoted shall be a per unit cost including all shipping; prices quoted shall be effective for a period of 3 years after the end of the warranty and may be adjusted annually by an amount up to the cost-of-living index based on the Phoenix metropolitan area. The cost of the extended depot warranty shall be considered during the evaluation of the cost proposals only and shall only be included in the cost proposal.




2. Extended Warranty: The proposal shall include a cost estimate for extending the warranty for a 12-month period after the initial system warranty as described above. This extended warranty service shall cover any and all hardware, software and services provided and/or installed by the selected Proposer to maintain reliable operations for a period of 12 months. The City shall have the option of renewing this warranty on an annual basis for up to three additional years. The proposal shall state the cost for each additional year assuming a 12 month contract.

F. TECHNICAL SUPPORT REQUIREMENTS

1. During the contract period, the contractor shall be required to respond to remote technical assistance requests by the City on a five (5) business day (Monday thru Friday), 7am to 4pm (Arizona time), 52 week basis (excluding City holidays).

2. A qualified Technical Support Specialist shall respond via telephone within one (1) hour after the Proposer receives a remote technical support request from the City.

3. The Proposer shall have a qualified Technical Support Specialist on-site within seventy-two (72) hours after the Proposer receives an on-site technical support request from the City.

4. The contractor shall furnish to the City a stock of spare equipment equal to

10% of the total quantity of each type of equipment supplied (minimum of one (1)) as listed in the Proposer’s Financial Proposal to meet the maintenance performance requirement.

VIII. TECHNICAL PROPOSAL FORMAT

A. INTRODUCTION

The following guidelines are provided to ensure the equitable evaluation of all Proposals. Proposals should be prepared and organized per the instructions outlined in this section. Potential Proposers are advised to read this RFP in its entirety. Failure to read and/or understand any portion of this RFP shall not be cause for waiver of any portion of the RFP or resulting agreement. A checklist is provided at the end of the submission requirements detailed below to ensure there is a clear understanding of what is expected to be submitted in the proposals.




B. SUBMISSION REQUIREMENTS

The items to be included in the submission are detailed in the numbered items below. The page limits described next to each item must be strictly adhered to or the submission will not be considered responsive. An original plus seven copies (total of eight) of the proposal must be submitted to the City of Phoenix Street Transportation Department; RFP “ITS Wireless Project”; ATTN: Ms. Joyce Dreyer, Management Services Division, 200 West Washington Street, 5th Floor; Phoenix, AZ 85003-1611; no later than 1:00 p.m. Arizona time on December 19, 2007.

Offeror Responsibility It is the responsibility of each Offeror before submitting a proposal to:

• Examine thoroughly the Proposal document and other data

identified in the Proposal document.

• Consider applicable laws that may affect cost, progress, performance, or furnishing of the work.

• Study and carefully correlate Offeror’s knowledge and observations

with the proposal document and other related data.

Promptly notify the City of all conflicts, errors, ambiguities, or discrepancies which an offeror has discovered in or between the Proposal document and such other related documents.

1. Letter of Transmittal (1 single-sided page)

Proposer shall provide a one-page Letter of Transmittal that is signed by an individual authorized to bind the Offeror. The proposal shall include the name of the Proposer, contact person, title, address, telephone number, facsimile number, and e-mail address of the individual with authority to contractually bind the company and who may be contacted during the period of the contract. The Letter of Transmittal must also provide the expiration date of the Proposer’s City of Phoenix Affirmative Action registration.

2. Proposal (10 double-sided pages or 20 single-sided pages)

A. Qualifications and Experience Statement

Proposer shall provide sufficient documentation to show that Proposer has provided equipment, implementation, training, and maintenance




for a minimum of five (5) wireless mesh systems, three (3) of which must have been used in a traffic signal system and/or an ITS application, comparable to the City’s environment and similar in size to the system required by this RFP, that have been operational for a minimum of one (1) year. This documentation is to include the name of the owner, reference name and contact information, and system information related to the size of the deployment and the type of environment. The Proposer shall submit all proposed partners, equipment suppliers, sub-contractors, and team members and shall describe the role each member will have in implementing the ITS Wireless Project. It is highly desirable for a team to have direct experience in the design and implementation of wireless traffic signal and/or ITS systems. It is the City’s intent to solicit firms with practical experience in the installation of a wireless network in a traffic signal system and/or an ITS environment. The use of traffic engineering firms as contract managers does not meet the traffic signal system/ITS experience requirement. In Appendix A of the submission, Proposer shall provide résumés (not to exceed 2 pages per resume) of proposed professional services staff that will be utilized for deployment of the City of Phoenix, Street Transportation Department ITS Wireless Project. Proposer may also include organizational charts showing key persons/firms that were involved in previous wireless traffic signal and/or ITS application projects submitted to document Proposer’s experience on this type of project.

B. System Configuration and Design

Proposer shall provide a system design document that outlines the hardware and software required to implement the ITS Wireless WAN. The design document shall include network diagrams, equipment data sheets, and related information. The Proposer shall also include a description of what would be required to add capacity to a wireless backhaul and transform a satellite location into a wireless backhaul. Proposer should also discuss their firm’s plans on upgrading their wireless backhaul equipment to IEEE 802.11n when the standard is released.

C. Initial Implementation Plan

Proposer shall submit a detailed project plan for initial implementation with its Proposal. The plan shall include project mission and objectives. Proposer shall submit descriptions of Proposer’s work




process or approach to achieving each objective and descriptions of deliverables.

The initial implementation plan shall include specific details for installation, testing, training, recommendations for system operations, and anticipated network performance (minimum and maximum data rates).

D. System Requirements

The requirements contained in Appendix B were developed by City staff and other organizations that participated in defining how the ITS Wireless Network would be used and determined what features and capabilities need to be present to serve the needs of the City. Proposers must recognize that the requirements may not be complete and requirements may be added, modified or reduced in the review phase of the selected Proposer’s detailed design submittal.

It is intended that the requirements contained within this RFP illustrate the operational requirements of the fully implemented ITS Wireless WAN. Any elements that may have been omitted must be brought to the attention of the City for clarification prior to the submission of the Proposer’s proposal. By submission of a proposal, the Proposer acknowledges that his/her system shall include all equipment and services necessary to deploy a complete and operational system even if some details may have been inadvertently omitted from this RFP.

Proposer must respond to the City’s requirements using the table provided in Appendix B. Every numbered/lettered line item shall have a response. Responses shall follow the capability codes provided in the attachment. The absence of a response in the Proposer Response Column for any line item shall be assumed to mean the Proposer cannot satisfy the requirement. Proposer comments that require additional pages and/or narrative explanation may be inserted into the body of the table, or attached to the table, and must be properly referenced to the requirement by requirement section letter/number. Comments that encompass multiple requirements must be repeated for each requirement.




The Proposer may add an Appendix D to their submission to include a drawing of the proposed wireless equipment housing.

E. Training

The Proposer shall submit an outline showing the logical sequence of activities the Proposer’s team will follow in assisting the City in becoming proficient in the design, installation, configuration, operation, troubleshooting, maintenance, and testing the ITS Wireless Project. Along with the outline, the Proposer shall include a brief description of the type of on the job training, and classroom training that shall be provided by the Proposer during each activity.

F. Proprietary and Open Standards Based Equipment

Proposer shall identify, in Appendix B, each piece of equipment as being either open standards based or proprietary. For all proprietary equipment the Proposer shall detail any licensing requirements associated with the installation and use of the equipment. This shall include any and all license agreements, license fees, recurring costs, etc.

G. Other Information (if Applicable)

Proposer shall provide information about the proposed equipment pertaining to distributors, manufacturer representatives, support staff, and technicians who are located in the Phoenix, AZ area.

Proposer shall provide any other information that would be helpful in evaluating Proposer’s ability to successfully fulfill the requirements contained herein.

3. Pricing Proposal

A. Pricing Proposal

Proposer shall submit a separate financial proposal based on unit pricing. Unit pricing is required and will be cause for rejection if not supplied. Appendix C provides an example format for the pricing sheet. All fees quoted in the section shall be firm and fixed for the full contract period and any extension.




B. Proprietary Equipment

All licensing and royalty fees associated with items identified as proprietary shall be included in Appendix C under the item to which the license(s) or royalty fee(s) apply.

C. Warranty

Proposer shall submit with its Proposal its warranty identifying the items within the Proposer’s warranty that meet the requirements described herein, including a cost estimate for extending the warranty period beyond the end of the contract period. The Proposer shall also include a list of depot repair costs for both repair and exchange.

D. Maintenance

Proposer shall submit with its Proposal a maintenance plan, including maintenance schedules, equipment life expectancy, and firmware/software updates. The Proposer shall include all associated costs with each of the aforementioned items in the unit price of the applicable piece of equipment listed in the Pricing Proposal.

4. Subcontractors and Partners (3 single-sided pages)

Proposer shall provide a list of any and all subcontractors and partners to be used, including any Minority-Owned, Woman-Owned, Small and/or Disadvantaged Business Enterprise firms, if applicable and shall describe the role each member will have in implementing the ITS Wireless Project.

5. Submission Checklist 1. Transmittal letter including the City of Phoenix Affirmative Action

expiration date (1 page) 2. Proposal (20 pages to include only the following):

a. Qualifications and Experience Statement b. System Configuration and Design c. Initial Implementation Plan d. System Requirements e. Training




f. Other Information 3. Subcontractors and Partners (3 pages) 4. Appendix A: Resumes for key personnel (limited to 2 pages per

resume) as well as any project organizational charts Proposer may include

5. Appendix B: Proprietary and Open Standards Based Equipment (6 pages) – use table provided in Appendix B of this RFP

6. Appendix C: Financial Proposal 7. Appendix D: Equipment Housing Diagram (optional submission

item) 8. An Original and 7 Copies

IX. EVALUATION OF PROPOSALS

A, EVALUATION PROCESS

The City anticipates receiving responses from a number of highly qualified Proposers. To ensure that each Proposer is evaluated fairly and comprehensively, a structured approach to evaluation shall be used by an evaluation panel comprised of representatives from various City Departments and outside Consultants. After evaluating all submissions, the City may ask some or all of the firms that submitted a Response to provide additional information or to participate in interviews. Upon completion of the evaluation process, the Street Transportation Department may assign a detailed scope of work to the selected firm. Initial evaluations shall be based upon the effectiveness of the perceived performance as it relates to the City’s requirements. The City’s determination as to whether the Proposer is qualified and responsible shall be based on the information furnished by the Proposer in the submission requirements, as well as from other sources determined to be valid by the City. The City shall not be bound to award the agreement to the lowest (dollar) Proposer. All firms that provide an RFP Response will be notified when a selection is made. The firms under consideration for this RFP will be evaluated by an Evaluation Committee to consider the firm’s ability to provide the




requested hardware, software, and services. The Street Transportation Department reserves the right to request supplemental information that the Evaluation Committee deems necessary to make a selection.

B. EVALUATION CRITERIA

The following criteria have been established to assist the City in determining which Proposer will provide the best quality of service to the City at reasonable rates:

Evaluation Criteria

Experience and qualifications of the Contractor and proposed team members in providing these services on similar projects. It is required that the Proposer have wireless experience with traffic signal and/or ITS systems. For each comparable project, provide the project description, role of the firm, award date (note if pending), construction cost estimate, and percent of work currently completed. List a reference for each project. Provide resumes for key team members (project organizational charts are optional). 200 Points System technical requirements 200 Points Training plan including the outline and description of the type of on the job training and classroom training that will be provided by the Proposer. 200 Points

Understanding of the project by the Contractor, including discussion on the team’s proposed implementation plan, and system configuration. Contractor shall describe intended project management methods, quality control plan, and how the project will be coordinated with City staff. 150 Points Financial Proposal 100 Points Maintenance, Warranty, Service and Support 100 Points Overall evaluation and opinion of the team’s capability to provide the required services. (This is to be determined by the selection committee members. No submittal response is required.) 100 Points Principal office location and local office work role. Identify each team members’ home office and the percent of work to be performed at the local office. 50 Points Total Points 1,100 Points




C. SCHEDULE

A selection committee shall evaluate each proposal according to the above criteria. The panel may elect to, but is not required to interview the highest scoring Proposers. The following tentative schedule has been prepared for this project.

RFP release November 21, 2007 Pre-submittal conference December 6, 2007 Proposal due date December 19, 2007 Evaluation Panel Meets January 2007 Proposer Interview (If needed) TBD

The City will enter into negotiations with the selected firm and execute a contract upon completion of negotiation of fees and contract terms for City Council approval. If the City is unsuccessful in negotiating a contract with the best-qualified team, the City may then negotiate with the second or third most qualified team until a contract is executed, or may decide to terminate the selection process.

X. OFFEROR RIGHTS A. OFFEROR RIGHTS

All materials submitted in response to this Request for Proposal become the property of the City upon delivery to the City and shall be appended to any formal documentation that would further define or expand the contractual relationship between the City of Phoenix and the Offeror. Each Offeror, as an express condition for the City's consideration of such proposal, agrees that the contents of every other proposal are confidential and proprietary, and waives any right to access to such proposals. No submission or supporting documentation will be returned to Offeror.

The foregoing provision shall not apply to the proposal of the Offeror to whom an award is made or recommended, or to the proposal of any Offeror contesting, protesting or otherwise challenging an award or recommendation.

Offerors submitting proposals should recognize that the City is a public body and, as a public body, the City is subject to the disclosure requirements of Arizona Public Records Law and must abide by public record laws. Neither party shall be liable for disclosures required by law.




B. CITY RESERVATION OF RIGHTS

This RFP does not commit the City of Phoenix to award a contract or to pay any costs incurred in the preparation of a proposal to this request. The City reserves the right to accept or reject any or all proposals received as a result of this request, to negotiate with any qualified sources, or to cancel in part or in its entirety this RFP. The lowest priced proposal will not necessarily be selected. The City specifically reserves the right to reject any or all proposals, or any part thereof; to accept any proposal or any part thereof; or to waive any defects or informalities in a proposal. Any Offeror objecting to the rejection of a proposal, or portion thereof, must submit a written protest stating the reasons for the protest to Joyce Dreyer, City of Phoenix-Street Transportation Department, 200 West Washington-5th Floor, Phoenix, AZ 85003 no later than 5:00 p.m. Phoenix time of the 10th calendar day following release of the City’s “Intent to Award” letter.

C. LATE PROPOSALS NOT CONSIDERED

Proposals received after the stipulated due date and time will not be considered.

D. INCONSISTENCY OR ERROR IN THE RFP

Any Offeror believing that there is any ambiguity, inconsistency or error in the RFP shall promptly notify the City in writing of such apparent discrepancy. Failure to so notify the City by the RFP submission due date will constitute a waiver of claim of ambiguity, inconsistency or error.

E. OFFEROR ERRORS OR OMISSIONS The City is not responsible for any Offeror's errors or omissions. F. ADDENDA

The City of Phoenix shall not be responsible for any oral instructions given by any employees of the City of Phoenix in regard to the proposal instructions, specifications or proposal documents as described in this RFP. Any changes will be in the form of an addendum, which will be furnished to all Offerors who are listed with the City as having received the Request for Proposal, or to any other Offeror who requests an addendum.




G. OFFEROR INCURRED COSTS

The Offeror shall be responsible for all costs incurred in preparing or responding to this RFP. All materials and documents submitted in response to this RFP become the property of the City and may not be returned after the proposal submission deadline.

H. MODIFICATION OR WITHDRAWAL OF PROPOSAL

A proposal may not be modified, withdrawn or canceled by an Offeror for sixty (60) days following the proposal submission deadline and each Offeror so agrees in submitting the proposal. Proposals may be withdrawn, altered and/or resubmitted at any time prior to the submission deadline.

Notice of withdrawal of proposal prior to submittal date must be in writing and must be signed by the Offeror.

I. OFFEROR CERTIFICATION

By submission of a proposal, the Offeror certifies that the Offeror has not paid or agreed to pay any fee or commission, or any other item of value contingent on the award of a contract to any employee, official or current contracting consultant of the City.

J. EXCEPTIONS

It is the intent of the City to award a contract on a fair, competitive basis. For this reason, the City may view the notation of any "Exception" in response to any material conditions or requirement of the RFP as an attempt by the Offeror to vary the terms of the RFP which, in fact, may result in giving such Offeror an unfair advantage over other Offerors. For this reason, the City will, at its option, not allow exceptions to any material requirement if, in the opinion of the City, the exceptions alter the overall intent of this RFP, unless the exception would be of material benefit to the City.

K. CITY'S RIGHT TO DISQUALIFY FOR CONFLICT OF INTEREST

The City reserves the right to disqualify any Offeror on the basis of any real or apparent conflict of interest that is disclosed by the proposal submitted or any other data available to the City. This disqualification is at the sole discretion of the City. Any Offeror submitting a proposal herein waives any right to object to the City’s exercise of this right, now or at any




future time, before any body or agency, including but not limited to, the City Council of the City of Phoenix, or any court.

L. WARRANTIES

The Contractor represents and warrants that the Contractor is fully aware of this Contract's requirements and intended uses of the products and services to be provided by the Contractor to the extent that they are described in the Contract. For each service or product described in the "Scope of Work," the Contractor warrants that the Contractor shall perform it: 1) in a workmanlike manner, and 2) according to its current description contained in the Contract. Each party represents and warrants that it has the right to enter into this Contract and there are no outstanding assignments, grants, licenses, encumbrances, obligations, and/or agreements which relate to the products or services (whether written, oral, or implied) which are inconsistent with this Contract and the rights transferred herein.

The Contractor further represents that the City's use of the products as contemplated herein does not and will not infringe any patent, copyright, or other proprietary right of any third party, and there is currently no actual or threatened suit by any such third party based on an alleged violation of such right by the Contractor.

M. COVENANT AGAINST CONTINGENT FEES

The Offeror warrants that no person or selling agent has been employed or retained to solicit or secure the contract upon an agreement or understanding for a commission, percentage, brokerage, or contingent fee, excepting bona fide employees or bona fide established commercial or selling agencies maintained by the Offeror for the purpose of securing business.

For breach or violation of this warranty, the City of Phoenix shall have the right to annul the Contract without liability or in its discretion to deduct from fees or payments due the Offeror the commission, percentage brokerage or contingent fee.

N. GRATUITIES

The City may, by written notice to the Offeror, terminate the right of the Offeror to proceed under the Contract upon one (1) calendar day notice, if it is found that gratuities in the form of entertainment, gifts or otherwise were offered or given by the Offeror, or any agency or representative of




the Offeror, to any officer or employee of the City with a view toward securing or amending, or the making of any determinations with respect to the performance of such contract. In the event of such termination, the City shall be entitled to pursue the same remedies against the Offeror as the City could pursue in the event of default by the Offeror.

O. AFFIRMATIVE ACTION IN EMPLOYMENT

In order for your proposal to be considered, your firm must comply with Phoenix City Code, Chapter 18, Article V, as amended, Affirmative Action Program. Failure to comply with the reporting requirements of this ordinance will result in your proposal being rejected. Firms are also responsible for maintaining their eligibility during the life of any proposal and failure to do so may result in termination of the proposal. A form has been included within this RFP package (Attachment D) to assist you in complying with the ordinance. Any questions in regard to this Affirmative Action Program should be directed to the Affirmative Action Compliance Section of the Equal Opportunity Department, (602) 262-6790.

The City of Phoenix extends to each individual, firm, vendor, supplier, contractor and subcontractor an equal opportunity to compete for City business and strongly encourages voluntary utilization of disadvantaged, small and/or minority-owned or women-owned businesses to reflect both industry and community ethnic composition.

Any contractor in performing under this contract shall not discriminate against any worker, employee or applicant or any member of the public because of race, creed, color, religion, gender, national origin, age or disability, nor otherwise commit an unfair employment practice. The Contractor will take affirmative action to ensure that applicants are employed, and that employees are dealt with during employment, without regard to their race, creed, color, religion, gender, national origin, age or disability.

Such action shall include, but not be limited to, the following: employment, upgrading, promotion, demotion or transfer; recruitment or recruitment advertising; layoff or termination; rates of pay or other forms of compensation; and selection for training, including apprenticeship. The Contractor further agrees that this clause will be incorporated in all subcontracts entered into with suppliers of materials or services and all labor organizations furnishing skilled, unskilled and union labor, or who may perform any such labor or services in connection with a contract resulting from this RFP. This clause shall also be incorporated into all job




consultant agreements or subleases in any way pertaining to Contractor's performance under the contract.

P. ORDER OF PRECEDENCE

In the event of conflict, the following precedence shall prevail: (1) terms and conditions set forth in the body of contract, (2) provisions set forth in referenced documents, (3) requirements and provisions set forth in this RFP; (4) the proposal submitted by the contractor in response to this RFP.

Q. PROTEST OF AWARD

Protests of the Department’s decision shall be made in writing and received by the City within ten (10) days from the date on which the notice of rejection is mailed or faxed to the Offeror. Protests shall be delivered to:

City of Phoenix Street Transportation Department Joyce Dreyer, Management Services

200 West Washington, 5th Floor Phoenix, AZ 85003

The City retains the right to reject all protests not filed within this time or those found to be without merit.

R. OFFEROR INQUIRIES

Any questions that arise relating to this RFP shall be directed, in writing or emailed, to:

City of Phoenix – Street Transportation Department

Joyce Dreyer, Management Services 200 West Washington, 5th Floor

Phoenix, AZ 85003 Phone: (602) 534-1622

[email protected]

To be considered, written inquiries shall be received at the above address by 5:00 P.M. (M.S.T.) on December 5, 2007. Written inquiries may be either emailed or faxed to (602) 495-2016 (and then mailed). Questions/inquiries received by December 5, 2007, will be addressed at the preproposal meeting.




No informal contact initiated by Offerors on the proposed service will be allowed with members of the City's staff from the date of distribution of this RFP until after the closing date and time for the submission of proposals. All questions concerning or issues related to this RFP shall be directed to the individual indicated above and will be addressed at the preproposal meeting. If time permits, additional questions and discussion will be allowed at the preproposal meeting. No formal report or minutes will be issued from the preproposal meeting.

S. NEWS RELEASES

News releases pertaining to this service or any part of the subject shall not be made without prior approval of the City of Phoenix.

XI. GENERAL TERMS AND CONDITIONS

Any Offeror entering into a contract with the City must agree to a number of general terms and conditions. If an Offeror cannot agree to any of the stated general terms and conditions, its proposal must clearly state the reason for any such non-compliance.

The submission of a proposal herein constitutes the agreement of any Offeror that any contract to be drawn as a result of an award herein will be prepared by the City of Phoenix. The submission of a proposal shall further constitute the agreement of each Offeror that it will not insist on the use of standard contract agreements, documents or forms, and that it waives any demand for the use of its standard agreements. Pursuant to City Charter, the language of the contract(s) to be executed will be drafted under the supervision of the City Attorney of the City of Phoenix and shall be the controlling document.

A. COMPLIANCE WITH LAWS

In performing this Contract, the Contractor shall comply with all applicable laws, ordinances, rules, regulations, and codes of Federal, State and local governments, including, but not limited to, the Arizona Worker's Compensation Act and all Federal and State tax laws. Because the Contractor will be acting as an independent contractor, the City assumes no responsibility for the Contractor's acts.

B. FEDERAL - STATE - CITY EXCISE TAXES

The City of Phoenix is exempt from Federal Excise Tax, including Federal Transportation Tax. Exemption certificates will be furnished upon request. Sales or leases to the City are not exempt from State of Arizona or City of Phoenix Transaction Privilege or Privilege License Taxes.




C. TAX RESPONSIBILITY QUALIFICATION

The successful Offeror may be required to establish, to the satisfaction of the City, that any and all fees and taxes due the City of Phoenix or the State of Arizona for any License or Transaction Privilege Taxes, Use Taxes or similar excise taxes are currently paid (except for matters under legal protest).

Any Offeror submitting a proposal agrees that the submission of the proposal constitutes a waiver of the confidentiality provisions contained in the City of Phoenix Finance Code and any similar confidentiality provisions contained in the statutes of the State of Arizona relative to State Transaction Privilege Taxes or State Use Taxes.

Any Offeror submitting a proposal further agrees that the submission of a proposal hereunder is, and shall constitute, a written authorization to the Finance Department of the City of Phoenix and to the State Department of Revenue of the State of Arizona to release tax information relative to Arizona Transaction Privilege Taxes, Arizona Use Taxes, City of Phoenix Privilege License Taxes and City of Phoenix Use Taxes to the procuring agency in order to assist the Department and the City in evaluating such Offeror's qualifications as a responsible contracting party under the proposal submitted.

D. NON-WAIVER OF LIABILITY

The City of Phoenix, as a public entity supported by tax money, in execution of its public trust, cannot agree to waive any lawful or legitimate right to protect the public treasury and the right of the taxpaying public to recover amounts lawfully due it. Therefore, any Offeror submitting a proposal herein agrees that it will not insist upon or demand any statement whereby the City agrees to limit in advance or to waive any right the City might have to recover actual lawful damages in any court of law under applicable Arizona law. The City may agree to liquidated damages in lieu of certain delay damages.

E. INDEMNITY CLAUSE

Contractor shall indemnify, defend, save and hold harmless the City of Phoenix and its officers, officials, agents, and employees (hereinafter referred to as “Indemnitee”) from and against any and all claims, actions, liabilities, damages, losses, or expenses (including court costs, attorneys’ fees, and costs of claim processing, investigation and litigation) (hereinafter referred to as “Claims”) for bodily injury or personal injury (including death), or loss or damage to tangible or intangible property




caused, or alleged to be caused, in whole or in part, by the negligent or willful acts or omissions of Contractor or any of its owners, officers, directors, agents, employees or subcontractors. This indemnity includes any claim or amount arising out of or recovered under the Workers’ Compensation Law or arising out of the failure of such contractor to conform to any federal, state or local law, statute, ordinance, rule, regulation or court decree. It is the specific intention of the parties that the Indemnitee shall, in all instances, except for Claims arising solely from the negligent or willful acts or omissions of the Indemnitee, be indemnified by Contractor from and against any and all claims. It is agreed that Contractor will be responsible for primary loss investigation, defense and judgment costs where this indemnification is applicable. In consideration of the award of this contract, the Contractor agrees to waive all rights of subrogation against the City, its officers, officials, agents and employees for losses arising from the work performed by the Contractor for the City.

F. OFFSET PROVISIONS

The Contractor shall recognize and be required to abide by the provisions of the City Charter of the City of Phoenix, which require and demand that no payment be made to any contractor as long as there is any outstanding liquidated undisputed obligation due to the City and direct that any such obligations be offset against any payment due the Contractor as vendor under such contract.

G. APPLICABLE LAWS

Any and all legal disputes arising under the contract or out of the proposal herein shall be tried according to the law of the State of Arizona and the Contractor shall agree that the venue for any such action shall be in the State of Arizona, County of Maricopa.

H. ORGANIZATION EMPLOYMENT DISCLAIMERS

Any contract entered into as a result of this RFP will not constitute, create, give rise to or otherwise recognize a joint venture, agreement or relationship, partnership or formal business organization of any kind between the parties, and the rights and obligations of the parties shall be only those expressly set forth therein. The Contractor will agree that no persons supplied by it in the performance of the contract are employees of the City and further agrees that no rights to the City's civil service, retirement or personnel rules and benefits accrue to such persons.

The Contractor shall be responsible for all salaries, wages, bonuses, retirement, withholdings, workers' compensation, unemployment




compensation, other benefits, taxes and premiums appurtenant thereto concerning such persons provided by such Contractor in the performance of the contract, and contractor shall save and hold the City harmless with respect thereto.

I. METHOD OF PAYMENT

Payment will be made only after submission of proper documentation to City of fees due to Offeror.

Payment of any invoice shall not preclude City from making claims for adjustment of any item or service found not to have been in accordance with the Contract, Specifications, or the scope of work.

J. LIENS

The Contractor shall hold the City harmless from any claims for supplying labor or material to the Contractor in the performance of the work required under the Contract.

K. REMEDIES

The City shall have, in addition to the remedies provided herein, all remedies afforded by the Uniform Commercial Code as adopted by the State of Arizona. Contractor shall have, subject to the limitation imposed by the terms of this Contract, all remedies afforded by the Uniform Commercial Code as adopted by the State of Arizona.

L. TRANSACTIONAL CONFLICTS OF INTEREST

The Offerors acknowledge that any contract resulting from this RFP submittal is subject to cancellation by the City pursuant to the provisions of Section 38-511, Arizona Revised Statutes.

M. DELAY IN EXERCISING CONTRACT REMEDY

Failure or delay by the City to exercise any right, power or privilege shall not be deemed a waiver thereof.

N. QUALITY AND ACCEPTABILITY OF WORK

The Street Transportation Department Director is responsible for determining the quality and acceptability of any work performed under the contract.




O. CONFIDENTIALITY OF INFORMATION

The Offeror shall treat all information furnished by the City and the results of the project hereunder as confidential. The Offeror shall not disclose such information to others without the prior written consent of the City's authorized representative.

P. FUND APPROPRIATION CONTINGENCY

The Offeror recognizes that any agreement entered into shall commence upon the day first provided and continue in full force and effect until termination in accordance with its provisions. The Offerors herein recognize that the continuation of any agreement after the close of any given fiscal year of the City of Phoenix, which fiscal years end on June 30 of each year, shall be subject to the approval of the budget of the City of Phoenix providing for or covering such agreement item as an expenditure therein. The City does not represent that said budget item will be actually adopted, said determination being the determination of the City Council at the time of the adoption of the budget.

Q. INSURANCE

Contractor and subcontractors shall procure and maintain until all of their obligations have been discharged, including any warranty periods under this Contract are satisfied, insurance against claims for injury to persons or damage to property which may arise from or in connection with the performance of the work hereunder by the Contractor, his agents, representatives, employees or subcontractors. The insurance requirements herein are minimum requirements for this Contract and in no way limit the indemnity covenants contained in this Contract. The City in no way warrants that the minimum limits contained herein are sufficient to protect the Contractor from liabilities that might arise out of the performance of the work under this Contract by the Contractor, his agents, representatives, employees or subcontractors and Contractor is free to purchase such additional insurance as may be determined necessary. 1. MINIMUM SCOPE AND LIMITS OF INSURANCE - Contractor

shall provide coverage with limits of liability not less than those stated below:

a. Commercial General Liability – Occurrence Form




Policy shall include bodily injury, property damage and broad form contractual liability and XCU coverage. • General Aggregate $2,000,000 • Products–Completed Operations Aggregate $1,000,000 • Personal and Advertising Injury $1,000,000 • Each Occurrence $1,000,000

i. The policy shall be endorsed to include the following additional insured language: "The City of Phoenix shall be named as an additional insured with respect to liability arising out of the activities performed by, or on behalf of the Contractor".

b. Automobile Liability

Bodily Injury and Property Damage for any owned, hired, and non-owned vehicles used in the performance of this Contract.

Combined Single Limit (CSL) $1,000,000 i. The policy shall be endorsed to include the following

additional insured language: "The City of Phoenix shall be named as an additional insured with respect to liability arising out of the activities performed by, or on behalf of the Contractor, including automobiles owned, leased, hired or borrowed by the Contractor".

c. Worker's Compensation and Employers' Liability

Workers' Compensation Statutory Employers' Liability

Each Accident $100,000 Disease – Each Employee $100,000 Disease – Policy Limit $500,000

i. Policy shall contain a waiver of subrogation against the City of Phoenix.

2. ADDITIONAL INSURANCE REQUIREMENTS: The policies are to

contain, or be endorsed to contain, the following provisions:

a. On insurance policies where the City of Phoenix is named as an additional insured, the City of Phoenix shall be an additional insured to the full limits of liability purchased by the Contractor even if those limits of liability are in excess of those required by this Contract.




b. The Contractor's insurance coverage shall be primary insurance and non-contributory with respect to all other available sources.

c. Coverage provided by the Contractor shall not be limited to the liability assumed under the indemnification provisions of this Contract.

3. NOTICE OF CANCELLATION: Each insurance policy required by

the insurance provisions of this Contract shall provide the required coverage and shall not be suspended, voided, canceled, reduced in coverage or endorsed to lower limits except after thirty (30) days prior written notice has been given to the City. Such notice shall be sent directly to (City of Phoenix-Street Transportation Department, Attn. Joyce Dreyer, 200 West Washington-5th Floor, Phoenix, AZ 85003) and shall be sent by certified mail, return receipt requested.

4. ACCEPTABILITY OF INSURERS: Insurance is to be placed with

insurers duly licensed or approved unlicensed companies in the State of Arizona and with an “A.M. Best" rating of not less that B+ VI. The City in no way warrants that the above-required minimum insurer rating is sufficient to protect the Contractor from potential insurer insolvency.

5. VERIFICATION OF COVERAGE: Contractor shall furnish the City

with certificates of insurance (ACORD form or equivalent approved by the City) as required by this Contract. The certificates for each insurance policy are to be signed by a person authorized by that insurer to bind coverage on its behalf.

All certificates and endorsements are to be received and approved

by the City before work commences. Each insurance policy required by this Contract must be in effect at or prior to commencement of work under this Contract and remain in effect for the duration of the project. Failure to maintain the insurance policies as required by this Contract or to provide evidence of renewal is a material breach of contract.

All certificates required by this Contract shall be sent directly to

(City of Phoenix-Street Transportation Department; Attn: Joyce Dreyer; 200 West Washington- 5th Floor; Phoenix, AZ 85003). The City project/contract number and project description are to be noted on the certificate of insurance. The City reserves the right to require complete, certified copies of all insurance policies required by this Contract at any time. DO NOT SEND




CERTIFICATES OF INSURANCE TO THE CITY'S RISK MANAGEMENT DIVISION.

6. SUBCONTRACTORS: Contractors’ certificate(s) shall include all

subcontractors as additional insureds under its policies or Contractor shall furnish to the City separate certificates and endorsements for each subcontractor. All coverages for subcontractors shall be subject to the minimum requirements identified above.

7. APPROVAL: Any modification or variation from the insurance

requirements in this Contract must have prior approval from the City of Phoenix Law Department, whose decision shall be final. Such action will not require a formal contract amendment, but may be made by administrative action.




APPENDIX A – PROJECT LOCATION MAP




APPENDIX B - SYSTEM REQUIREMENTS

No.: This column indicates a unique number/letter for each requirement. A separate response is expected for each requirement. Description: The description identifies required equipment, capabilities, and or functions. Proposer Response: Using the coding scheme described below, please enter a 2 (Standard), 1 (Optional), 0 (Not Available): • Standard is to be indicated if the equipment offered by the Proposer “out of the box” meets or exceeds the requirements identified within this RFP. • Optional is to be indicated if the equipment offered by Proposer, other than the base system configuration, meets or exceeds the requirements identified within this RFP with an accessory or available option. In addition, the accessory or option must be currently available and in current production. • Not Available is to be indicated if the requirement is beyond the ability of the proposed equipment to meet the requirements identified within this RFP or not currently available as an optional feature or accessory. Proprietary Response: Using the coding scheme described below, please enter a P (Proprietary) or NP (Non-Proprietary): • Proprietary is to be indicated if the item proposed contains any of the following:

Uses technology, materials, or manufacturing methods which are unique making the item interoperable only with other products from the same company.

Modifications or external components are required to make the item interoperable with similar equipment from other vendors.

Protected by patents, copyrights, or trademarks which are not royalty free.

• Non-Proprietary is to be indicated if all of the following apply:

The holder of a software product’s license, patent, copyright, or trademark allows the use, duplication, and modification of source code by the end user without the payment of royalties or licensing fees.

Equipment must be interoperable with equipment from other manufacturers and operate according to standards developed by organizations such as IEEE, ANSI, EIA, etc.




If a 1 is entered in the Proposer Response column, enter the name of the option or accessory in the Comments column. If a feature/requirement is not met, enter the name of the feature/requirement and indicate “Not Supported” in the Comments column. Include sufficient information in the Comments column (or an attachment) to clarify that all requirements are met (failure to do so may result in a lower score).

Section A – Network General Requirements

No. Description Proposer Response

Proprietary Response Comments

A1 Radio Equipment Uses Unlicensed Frequencies and is IEEE 802.11a/b/g Compliant

A2 Proposer has installed (5) wireless WAN systems which have been in operation for a minimum of (1) year

A3 Controller interfaces are IEEE 802.3 10/100 BaseT Compliant

A4

Proposer has implemented (3) wireless WAN systems used for traffic signal and or ITS systems which have been in operation for a minimum of (1) year

A5

Network is A. Fault Tolerant B. Self-configuring C. Mesh configuration

A6 Network is Scalable

A7

Capable of Dedicating Bandwidth to Specific User groups (State the maximum number of user groups that bandwidth can be dedicated to)

A8 Capable of Integrating and Combining Multiple wireless backbone Segments on a Fiber Backbone to Increase Capacity

A9 All Outdoor Equipment Installations Compliant with Environmental Requirements

A10 All Equipment and Cabling can be Installed per the Guidelines of the RFP

A11 Outdoor Equipment can be Powered from both 120VAC and 240VAC

A12 No Excavation or Trenching is Required




for Installation

A13 Traffic Signal Operation shall not be Disrupted During Implementation

A14 Latency Added by the Network shall not exceed 50ms

Section B – Equipment Requirements



B1

PCMCIA Network Interface Card (NIC) is compliant with IEEE 802.11a/b/g & IEEE 802.11i 128 bit AES and utilizes hardware based encryption

B2 Wireless Backhaul Transceiver B3 Wireless Satellite Transceiver B4 Fiber Backhaul Wireless

Transceiver

B5 Antenna B6 Traffic Controller Interface Section C – Security Requirements



C1 Proposed equipment is compliant with IEEE 802.11i 128 bit AES hardware based encryption

C2 Protect SSID Label C3 Prevent Unauthorized

Authenticating and Associating

C4 Intrusion Detection Capability C5 MAC Address Filtering C6 All wireless links are encrypted

using IEEE 802.11i 128 bit AES

C7 Detection of Malicious Access Points

C8 Denial of Service Situations (DoS) C9 Prevent Session Hijacking




Section Z – Additional Proposer Items



Z1 Z2 Z3




APPENDIX C – FINANCIAL PROPOSAL

The following table is provided as an example price proposal. Proposers may recreate the table for inclusion in their price proposal. Pricing shall include all optional features that are being provided as part of this proposal. For each main component that shall be provided as part of his bid, the Proposer shall detail the individual sub-components required for each main component to function per the requirements of this RFP. Quantity, unit price and extended price as shown in the example below shall be provided by the Proposer for each main component and each sub-component. Prices shall be inclusive of all equipment, materials, supplies, labor, ancillary items, etc to provide a complete and functional system. Pricing shall be valid for the duration of the contract plus an additional twelve (12) months after final acceptance.

MATERIALS AND INSTALLATION TRAINING Unit Price

Training Main Item Quant Unit Materials Install Configure Test

Extended Price

Lead Time

Wireless Backhaul 10 EA $1,000 $500 $100 $50 $16,500 Sub-items

Omni Antenna 20 EA $100 $0 $0 $0 $2,000 802.11g radio 20 EA $400 $0 $0 $0 $8,000




WARRANTY

Quantity Item Unit Unit Price

1 12-Month initial warranty Lump Sum

1 Extended warranty (12) Month term Lump Sum

1 Depot Repair option (Provide individual unit price for each item in Appendix C, “Network Equipment” table )

Each

1 Depot Replace option (Provide individual unit price for each item in Appendix C, “Network Equipment” table )

Each

PRICING SUMMARY TABLE Sub-Totals

MATERIALS

DESIGN SERVICES

TRAINING SERVICES

INITIAL WARRANTY

Grand Total




APPENDIX D – AFFIRMATIVE ACTION FORM

If currently in compliance, do not resubmit this form.

CITY OF PHOENIX EQUAL OPPORTUNITY DEPARTMENT

COMMUNITY AND BUSINESS RELATIONS DIVISION Suppliers, Contractors, and Lessees wishing to enter into a business relationship with the City of Phoenix, must comply with either Article IV or V of Chapter 18 of the City Code, as appropriate. Compliance is achieved by submission of the affirmative action reporting forms as indicated below:

Individuals or Firms Who Employ Fewer Than 15 people: Complete only Part D

Your Company will be eligible to do business with the City for 24 months after the date our office receives the completed form.

Firms Who Employ 15 or More People: 1. Employer Information Report (Part A) 2. Employer EEO Workforce Profile (Part B) 3. An Affirmative Action Plan (Part C)

Your Company will be eligible to do business with the City for 12 months from the date our office receives the completed form.

These reports must be completed accurately and on file with the Equal Opportunity Department prior to bid opening, proposal submission, response to a request for quotation, response to a request for qualification or the date set forth as part of any other request-response process initiated by the City.

The above referenced reports must be submitted to:

Equal Opportunity Department Community and Business Relations Division

251 W. Washington Street Phoenix, AZ 85003-2107

Failure to comply with the affirmative action requirements outlined in the Articles will result in your being considered ineligible for any City business. Questions may be directed to the City of Phoenix Equal Opportunity Department, Community and Business Relations Division at V/(602) 262-6790, TDD/534-1557, FAX 534-1785. Thank you for your cooperation.




City of Phoenix EQUAL OPPORTUNITY DEPARTMENT

COMMUNITY AND BUSINESS RELATIONS DIVISION

PHOENIX CITY CODE AFFIRMATIVE ACTION REQUIREMENTS PART A: EMPLOYER INFORMATION REPORT

PLEASE PRINT OR TYPE

Firm Name:_________________________________________________________________________________

Local Street Address_______________________________________________________________________________ City__________________ State_____________________ Zip__________________ Local Mailing Address:_______________________________________________________________________________ (If different than above) City___________________________ State________ Zip___________ Corporate Mailing Address:_______________________________________________________________________________ (If different than above ____________________ City______________State ______ Zip __________ Previous Address_______________________________________________________________________________ City ________________ State__________________ Zip____________ Corporate Telephone:_________________________Local_____________________ Telephone:__________________________ FAX#______________________________ Type of Business:______________________________________________________________________________ (Examples; Electrical Contractor, Lessee, Computer Sales, Architect, or Office Supplies) Name, title and telephone number of company’s Equal Employment Opportunity Officer/person responsible for this report: Corporate Officer:____________________________________TelephoneNumber:_____________________________ Local Officer:____________________________________Telephone Number:_______________________ So that your record may be properly cross referenced in our file, please indicate in the space provided below other company names used. Failure to provide this information could result in your loss of City business. ______________________________________________________________________ ______________________________________________________________________




CONTINUE TO PART B PART B: EMPLOYER EQUAL EMPLOYMENT OPPORTUNITY (EE0) WORKFORCE PROFILE


Instructions: Do you have employees in the Phoenix metropolitan area? (includes Phoenix, Tempe, Mesa, Chandler, Scottsdale, Paradise Valley, Glendale, Peoria, Tolleson, Litchfield, Avondale, Buckeye and Goodyear).

Yes-Report only Phoenix Metro employees from your most recent payroll. If this is Less Than 15, use Part D, the Certificate of Less Than 15.

No-Report all Corporate employees from your most recent payroll. Your latest Federal EEO-1

may be substituted.

NUMBER OF EMPLOYEES

MALE

FEMALE

JOB CATEGORIES

OVERALL TOTALS (SUM OF COL. B THRU K) A

WHITE

(NOT OF HISPANIC ORIGIN)

B

BLACK


C

HISPANIC

D

ASIAN OR PACIFIC

ISLANDER E

AMERICAN INDIAN OR ALASKAN NATIVE

F

WHITE


G

BLACK


H

HISPANIC

I

ASIAN

OR PACIFIC ISLAND

ER J

AMERICAN INDIAN

OR ALASKAN NATIVE

K Officials and Managers

Professionals

Technicians

Sales Workers

Office and Clerical

Craft Workers (Skilled)

Operatives (Semi-Skilled)

Laborers (Unskilled)

Service Workers

TOTALS

FIRM NAME_________________________________________________________________________________




CONTINUE TO PART C

PART C: AFFIRMATIVE ACTION PLAN

PLEASE PRINT OR TYPE Instructions: If your firm has an Affirmative Action Plan, please submit a copy. If not, please complete a plan on your company letterhead utilizing the outline below. Your firm will be reviewed by city staff to determine if you are complying with your plan.

AFFIRMATIVE ACTION PLAN In order to comply with the Affirmative Action reporting requirements of Article IV or V of Chapter 18 of the Phoenix City Code, and to ensure equal employment opportunity, the following measures will be taken:

1. Equal and fair treatment will be provided to all employees regardless of race, color, religion, national origin, gender, age or disability.

2. A complete up-to-date workforce profile which records employees by race or ethnicity, gender, and job classification will be maintained and annual reports will be submitted to the City of Phoenix Affirmative Action Division.

3. All employees will be advised at time of employment that the firm is an Equal Opportunity / Reasonable Accommodation Employer and that hiring, promotion or demotion is based only on the individual’s qualifications and ability to perform the work.

4. The firm will cooperate with and support apprenticeship training programs based on strict non-discrimination.

5. The firm has appointed ________________________to serve as the Equal Employment Officer who is authorized to supply reports and represent this firm in all matters regarding this affirmative action plan.

6. The name, address and phone number of the Equal Employment Officer will be posted in a conspicuous place or places. This Officer will be responsible for:

a. Seeking to utilize minorities, females and disabled individuals to the same degree as all others, based on the following factors.

(1) Percentage of minorities, females and disabled individuals in the company’s workforce as compared with the labor market in the area.

(2) Local availability of minorities, females and disabled individuals having the skills we employ.

(3) Availability of promotable minorities, females and disabled individuals in our company.

(4) Existence of training institutions to train minorities, females and disabled individuals in the area.

(5) The internal skills training our company offers for minorities, females and disabled individuals.

b. Supervision of periodic audits of employment practices including: (1) applicant flow (2) promotion (3) training.




c. Contacts with recruitment sources for qualified minorities, females and disabled

individuals. Notification to employees regarding promotions or vacancies to ensure

equal opportunity.

d. Instruction of all supervisory personnel regarding their responsibility for equal

employment opportunity and non-discrimination requirements.

e. Periodic reviews with all supervisory personnel to ensure that the program is being implemented at all levels.

SIGNATURE AND TITLE_________________________________________________________________________________ FIRM NAME_________________________________________________________________________________ DATE________________________________




PHOENIX CITY CODE AFFIRMATIVE ACTION REQUIREMENTS

PART D: EMPLOYER OF FEWER THAN 15


Instructions: If your firm employs 14 or fewer employees, complete & return only this form.

CITY OF PHOENIX EQUAL OPPORTUNITY DEPARTMENT COMMUNITY AND BUSINESS RELATIONS DIVISION 251 W. WASHINGTON STREET PHOENIX, AZ 85003

If you have any questions or require assistance, contact the Community and Business Relations Division at:

V/(602) 262-6790 * TDD / 534-1557 * FAX 534-1785 Firm Name:_________________________________________________________________________________ Street Address:_______________________________________________________________________________ City ________________________ State_____ Zip___________ Mailing Address:_______________________________________________________________________________ City ________________________ State___________ Zip___________ Corporate Mailing Address:_______________________________________________________________________________ City __________________________ State _______________ Zip____________ Telephone No.:________________________________________________ FAX #________________________________________ Previous Address:_______________________________________________________________________________ City _____________________________ State _____ Zip____________ So that your record may be properly cross referenced in our file, please indicate in the space provided below, other company names used. Failure to provide this information could result in your loss of City business. ______________________________________________________________________________________ ______________________________________________________________________________________ In accordance with Chapter 18 of the Phoenix City Code, Article IV or V, I hereby certify that the above-named individual or firm currently employs (insert number of employees). ____________________________________________________________________ PRINT NAME OF PERSON RESPONSIBLE FOR THIS REPORT. ____________________________________________________________________ SIGNATURE ___________________________________________________________________ TITLE ___________________________________________________________________ DATE

Date post:	14-Jul-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

CITY OF PHOENIX STREET TRANSPORTATION DEPARTMENT …bids.centerdigitalgov.com/NAV_KCC_ 11-21-2007_...

Documents