CITY OF LOS ANGELES

CALIFORNIA

ERIC GARCETTI MAYOR

DATE: May 16, 2016 TO: All Prospective Proposers Attached is a copy of a request for proposal (RFP) for a qualified firm to provide LATAX Code Modernization Services to the City of Los Angeles. All proposals shall be submitted in accordance with the requirements set forth in this document. A Proposers’ Conference will be conducted at 10:00 am, on Thursday, June 9, 2016 at: 200 N. Spring St. (Use Main St. Entrance) City Hall, Room 152 A/B Los Angeles, California 90012

ATTENDANCE AT THIS CONFERENCE IS MANDATORY in order to complete the “Good Faith Effort” outreach requirement of the City’s Business Inclusion Program. Failure to complete all tasks of the “Good Faith Effort” provision of the Business Inclusion Program will render your bid non-responsive and will result in its rejection. Refer to Appendix F for further information regarding this requirement. The purpose of the conference is to provide assistance to prospective proposers in the interpretation of this RFP, its scope, or any other terms and conditions. The City will make a presentation and respond to proposers’ questions. The City requests prospective proposers to submit their questions for the Proposers’ Conference in writing to Carl Sampson at the address listed below no later than 5:00 pm, Thursday, June 2, 2016. Questions may also be sent via e-mail to carl.sampson@lacity.org. Written responses to questions will be distributed to all proposers in attendance at the Conference and to other proposers upon request. The City will respond only to questions that are submitted in writing to ensure that all proposers are treated equally during the RFP process. Proposals and questions shall be delivered to: Carl Sampson, Director of Systems Office of Finance, LATAX / Systems Division 1200 West 7th St., 7th Floor Los Angeles, CA 90017.

CLAIRE BARTELS DIRECTOR of FINANCE

CITY TREASURER

OFFICE OF FINANCE

200 N. SPRING ST.

ROOM 101 – CITY HALL

LOS ANGELES, CA 90012

______

(213) 978-1516

The City will receive and respond to vendor questions after the Proposers’ Conference up and until 5:00 p.m. on, Tuesday, June 30, 2016. Responses to any vendor submitted questions will be in writing and will be posted on the LABAVN website for all vendors to review. No proposal will be accepted after 5:00 p.m. on, Thursday, July 28, 2016. The City reserves the right to extend the deadline for response to this RFP and to waive any informality in procedure should such action be deemed in the best interest of the City. All written communications should be directed to the address above. Thank you for your interest in this project.

Sincerely,

Claire Bartels Director of Finance / City Treasurer

Attachment

REQUEST FOR

PROPOSAL

LATAX Code Modernization

City of Los Angeles

Office of Finance

May 16, 2016

4

PROPOSER CHECK LIST – REQUEST FOR PROPOSAL

LATAX Code Modernization

Proposer Name / Legal Business Name: _____________________________________________

Forms to be completed and included with proposal except where indicated to be uploaded to the

City’s Business Assistance Virtual Network (BAVN) Site:

Proposer Initial Form Description

____ Appendix A – Standard Provisions For City Contracts

____ Appendix B – Contractor Responsibility Ordinance (CRO) Forms

____ Appendix C – Child Support Obligation Compliance Form

____ Appendix D – Service Contract Worker Retention and Living Wage

Ordinances

____ Appendix E – Americans With Disabilities Act Compliance Form

____ Appendix F – Business Inclusion Program (uploaded to BAVN)

____ Appendix G – Statement of Non-Collusion Form

____ Appendix H – Workforce Residence Information Form

____ Appendix I – City of LA Contract History Form

____ Appendix J – Bidder Certification Form CEC 50

____ Appendix K - Confidentiality Agreement / Loyalty Oath

____ Appendix L – Campaign Contribution Limitations – CEC Form 55

____ Appendix M – First Source Hiring Ordinance Forms

____ Appendix N – Client Reference Listing

____ Appendix O – Local Business Preference Program

____ Slavery Disclosure Ordinance (uploaded to BAVN)

____ Affirmative Action / Equal Employment Opportunity Forms (uploaded to

BAVN)

____ Equal Benefits Ordinance (EBO) Forms (uploaded to BAVN)

____ One (1) clearly identified original and five (5) clear copies of the complete

proposal package

____ One (1) electronic / CD version of the complete proposal package in MS

Word or Adobe PDF format.

5

TABLE OF CONTENTS I. Introduction and Background 8 II. Scope of Services 9

Current Technical Environment 10 III. Proposer’s Conference 19 IV. Deliverables 19 VI. Contents of Proposal 20 A. Cover Letter 21 B. Business Organization 21 C. Project Personnel 21 D. Sec. 21.17 Confidentiality Character of Information 22 E. Prior Experience 22 F. Statement of the Program 22 G. Project Approach and Work Plan 22 H. Technical Requirements 23 I. Project Management 25 J. Cost 26 K. Proposal Addendum 26 L. Additional Information 26 M. Omissions and/or Deviations 27 VII. Proposal Requirements 27 A. Contract Term 27 B. Standard Provisions 27 1. Indemnification 28 2. Insurance 28 3. Business Tax Registration Certificate 28 C. Contractor Responsibility Ordinance 28

D. City Affirmative Action Program and 28 Non-Discrimination Requirements E. Business Inclusion Program and Outreach 29

F. Service Worker Retention and Living Wage 29 Ordinance Compliance G. Equal Benefits Ordinance 30 H. Slavery Disclosure Ordinance 30 I. Prior Contracts with the City 30 J. Affidavit of Non-Collusion 30 K. Disposition of Proposals and Disclosure of Information 31 L. Withdrawal of Proposal 31 M. Required Copies and Deadline for Submission 31 Of Proposal

6

N. Mandatory Protest Provisions 32 O. Child Support Ordinance 33 P. Americans with Disabilities Act 33 Q. Workforce Information 33 R. Confidentiality Requirements 34 S. Bidder Campaign Contribution Limitations 34 T. First Source Hiring Ordinance 35 U. Local Business Preference Program Ordinance 35 VIII. Selection Criteria 35

IX. Required Contract 36 X. Acceptance of Terms and Conditions 36 XI. Rejection of Responses to RFP 37 XII. Financial Responsibility 37 APPENDIX A Standard Provisions for City Contracts (Rev. 03/09) Exhibit 1 – Insurance Requirements APPENDIX B Contractor Responsibility Ordinance APPENDIX C Certification of Compliance with Child Support Obligations

APPENDIX D Service Contract Worker Retention and Living Wage Ordinances

APPENDIX E Certification of Compliance with the Americans with Disabilities Act

APPENDIX F Business Inclusion Program APPENDIX G Non-Collusion Affidavit APPENDIX H Workforce Residence Information Form APPENDIX I Prior City Contract History Form APPENDIX J Municipal Lobbying Ordinance and Bidder Certification – CEC Form 50 APPENDIX K City of Los Angeles – Confidentiality Agreement / Loyalty Oath APPENDIX L Bidder Campaign Contribution Limits – CEC Form 55

APPENDIX M First Source Hiring Ordinance

APPENDIX N Client References List

7

APPENDIX O Local Business Preference Program

8

CITY OF LOS ANGELES

REQUEST FOR PROPOSAL

LATAX CODE MODERNIZATION

I. Introduction and Background

A. Intent The Office of Finance currently utilizes an in-house system solution, LATAX, to manage all of the tax and permit operations for the department. The LATAX system will require certain application server components and/or programming code to be migrated from the current EA Server / PowerBuilder framework to newer technologies to ensure on-going vendor support of these critical system components. This RFP is being issued to seek those services and solutions to perform this technology migration. B. General Overview The Office of Finance (Finance), pursuant to the City Charter, is the tax collector for the City and is responsible for collecting and enforcing the various tax ordinances of the City. Finance is also responsible for the collection and enforcement of various permit fees that are under the jurisdiction of the Police, Fire, and other Departments.

The City of Los Angeles Office of Finance currently administers the tax and permit collections

for over 600,000 active accounts. The tax and permit activities include but are not limited to

the following:

Business Tax

Parking Occupancy Tax

Transient Occupancy Tax

Utility Taxes (such as Electric, Gas, Communications)

Police Permits (including Alarm)

Fire Permits

Tobacco Retailer Permits

The City of Los Angeles Office of Finance communicates to tax and permit holders through a

variety of correspondence including but not limited to the following:

Renewal Statements for all taxes (Annually, Quarterly, or Monthly)

Renewal Statements for all permits (Annual)

Billing and Assessment Statements for underpaid accounts

Estimated Assessment Statements for non-reporting accounts

9

Overpayment Notices for accounts which payments exceed liabilities

The tax and permit processing system needs to support the daily work activities of

approximately 350 Office of Finance employees located at 3 work locations as well as

provide public access to web services on a 24-hour / 7-day basis.

C. Schedule

For purposes of the RFP, the term “Respondent” means the entity providing a written submission to this RFP. The estimated schedule for the RFP process is as follows:

RFP Release 5/16/2016

Submittal of Questions for Proposer’s Conference 6/2/2016

Proposer’s Conference 6/9/2016

Last Day to Submit Questions Prior to Bid Response 6/30/2016

All Proposals Due 7/28/2016

City may modify the RFP or the RFP response process at any time. Any changes in the process or updates to the schedule above will be posted on the LABAVN at www.labavn.org. If a determination is made that a clarification or change to the RFP document is required, or if the City obtains additional information that the City deems may be useful to Respondents, a written addendum will be posted on the website noted above. The City will respond to any vendor submitted questions in writing and will be posted on the LABAVN website for all vendors to review. Respondents are responsible for obtaining all RFP materials. An entity interested in receiving notice of changes should register as a vendor on the LABAVN specifying NAICS Code 541511 or 541512.

II. Scope of Services

This RFP seeks vendor solutions for migrating three-tier client/server systems developed with

PowerBuilder and EA Server to a different application server and/or programming

environment.

10

A. Description of Desired Solution

The City is looking specifically for a vendor that can provide all of the services and any

related products to migrate the current LATAX system to a new technical environment

including:

Migration to .Net (C#) or Java

Conversion to a browser-based application, with the same look and feel in the

end-user experience as the existing LATAX application

Continued use of the existing Oracle 12c database and LATAX data model

Seamless interaction with the existing LATAX functionality in the web subsystem

(ColdFusion and JSP). This subsystem will not be converted as part of the

project, but the functionality must be retained and integrated with the converted

system.

Continued role-based security at the same levels as in the existing application

(Screens, buttons).

All calculations must produce the same results as the existing system – (eg.

Penalty & Interest).

B. On-going System Support

The City is not seeking solutions which include outsourced staffing solutions or a delivered

environment requiring on-going support from the development firm. The City will utilize

existing staffing resources for on-going development and support of the delivered solution.

C. Proposed Schedule Plan and “Proof of Concept”

The City is seeking a proposed schedule plan which would include the delivery of a prototype

or “proof of concept” which would demonstrate that the vendor’s ability to convert a small

subsection of the LATAX system into the new technical environment. This initial prototype

would validate the approach utilized for the modernization project and provide a

representative sample of the end product deliverable. Successful completion of this initial

prototype would enable the project to continue through all phases of the planned scope of

work while significant defects in the delivery of the prototype may result in the end of the

engagement prior to work on the full migration project. Failure of the contractor selected to

deliver such a functioning "proof of concept" deliverable, as described more fully in Section

IV(B) of the "Deliverables" section of this RFP, would result in the City's termination of the

Agreement resulting from this RFP. Contractor would not continue to perform under the

Agreement after such a failure of "proof of concept" in deliverable B, and no payments would

be due and payable by City for any of the enumerated deliverables which were not

successfully delivered by contractor prior to the time of termination of the Agreement.

11

D. Current LATAX Technical Environment The current LATAX technical environment consists of the following:

1. LATAX is a distributed (n-tier) tax collection software running in a Sybase (now SAP) EAServer (Ver 5.5) environment using Oracle Database (Ver 12c) as a backend. LATAX also refers to a suite of applications that includes a desktop client, batch programs and several web applications.

2. The existing platform supports 400+ desktop users and about 250,000+ taxpayers on the web during e-filing season. The application is highly scalable.

3. LATAX’s busiest period is the business tax renewal season, which runs from January 1 through first week of March each year. 75% of annual business tax renewals were filed online in 2016, adding to the increased activity by system users in the Office of Finance. The permit renewal season (October through December) is also a higher than normal period.

4. The core application contains about 5000 objects written in PowerBuilder (Ver 12.5)

and Java (Ver 1.5.0_22). 85% of these are deployed on the in EA Server and 15% make up the client side. LATAX Oracle (12c) database contains about 1200 objects. All business rules are implemented on the server side in EAServer.

5. LATAX Client is a 32-bit Windows desktop application written in PowerBuilder (Ver

12.5) and deployed to about 400 users in different departments inside the city of Los Angeles. The user desktops run on Windows 7 x64 machines.

6. The server environment in production comprises of 10 EAServers with four of them

setup in a cluster for load balancing/failover. Each production EAServer runs on a Windows server (2008 R2 x64 Standard edition) VM in a VMWare environment. Each VM is currently assigned 2 vCPU (2.5GHz) and 5GB memory.

7. LATAX batch programs share the same business rules as the client applications.

LATAX has a robust 24/7 batch processing production environment for performing Case processing, General Ledger Distribution (GLD), Penalty and Interest (PNI), Payment processing, Correspondence processing, Lockbox processing for financial and non-financial transactions and six major interfaces. The LATAX support team supports 60 Annual jobs, 5 Quarterly, 76 Monthly, 33 Weekly and 438 daily jobs. BMC’s Control-M 7.0 Scheduling System is utilized for performing dependency oriented processing across AIX Unix, Linux and Windows platforms.

8. The LATAX suite of applications also include several small to medium sized web applications written in JSP and ColdFusion. These also use the business rules in PowerBuilder.

9. LATAX uses CORBA IIOP protocol for most components. LATAX client, the batch

program and the web applications communicate to the LATAX server code through

12

CORBA. We also use SOAP and REST for some external web services used to validate addresses in LATAX.

10. As PowerBuilder is a single threaded environment, LATAX uses Java wherever there

is a need for multi-threading. Several functions including Batch programs (External Interfaces), Address Validation/Geocoding services, Stored Procedure adapters and several server side functions are written in Java and deployed and accessed as CORBA components in EAServer.

11. The application is implemented using several frameworks including a Client side

framework and a Server side framework built by Unisys. Both of these are built on top of EA Framework (EAF), a framework built by Cynergy Systems and distributed by Sybase earlier. There is no support or documentation for these frameworks, but we have the full source code. The EAF uses a service based architecture (similar to PFC).

12. LATAX contains a few dynamically executed workflows (Case Processor, Pay Processor, and Correspondence). LATAX includes a workflow designer for the CASE processor.

Case and Pay Process are currently run as Service components in EA

Server. They are started at server startup and wake up every 5 minutes (configurable) to process cases and payments.

The metadata for the workflows including node names, corresponding rules and the objects to execute are stored in database tables.

13. LATAX Correspondence module allows users to use Word templates to create

correspondences. This uses OLE to fill up the Word bookmarks with data from the database tables.

In order to maintain the templates and bookmarks from inside LATAX, the System Admin module includes the following functionalities:

Query Manager, Bookmark Manager and Template Manager

LATAX Desktop Client

14. Screens in LATAX are called Views. A View is assembled dynamically with layouts and buttons using metadata stored in database tables (as shown). A layout corresponds to a Datawindow. There can be a maximum of 8 such layouts in a view.

LATAX contains several popup windows which are assembled in the same

way as above. All popup windows are modal windows.

13

LATAX contains several Search windows; It is assembled dynamically using the metadata stored in the database as well; also, we can set limit to the number of rows returned.

Buttons are associated with the individual layouts. Some buttons may also

be inside the Datawindow. Button processing logic is also delegated to Service objects.

LATAX Security is tied into this dynamic building of views to allow access by roles.

15. LATAX screen may contain the following (PowerBuilder) controls:

MDI Window Menu Datawindow Edit Mask Single Line Edit Multi Line Edit Dropdown List Dropdown Datawindow

16. LATAX utilizes session and global variables to communicate across the screens. For

example an Account Number looked up in Registration module, is carried over into several other modules as well, so users don’t have to type it again.

17. The application currently utilizes an INI file for the client application settings. Code to

use Registry settings exists as well.

14

Figure 1 A sample LATAX screen and parts

LATAX Server

18. Most of LATAX components participate in a distributed transaction managed by

Jaguar, the Transaction processor (TP Monitor) inside EAServer. We leave the control to Jaguar (using Auto-demarcation). In some cases, LATAX code will take control of the transaction (using SetComplete/setAbort functions).

Also, in order to isolate transactions within a component, some EAServer components are split into an update_helper, which then re-invokes another instance of the calling object. For example,

15

Figure 2 Isolating transactions in LATAX

Note: Some programs use Java stored procedure to achieve similar isolation.

19. LATAX components are created through the PowerBuilder function, CreateInstance. The Client side invokes them through the Connection object and server side components through the TransactionServer object.

The components are typically set to be pooled and concurrency for load balancing. We use EA Server’s object pooling for some of the heavily used components.

20. All Database (SQL) operations in LATAX application, including Datawindow/Datastore

retrievals, happen on the server side. We use EA Server’s connection caches for this. No database connectivity code or Transaction object (SQLCA) exist on the client side.

21. LATAX uses varied logging techniques. There is a custom logger built in Java that is

used by most of the components. Batch programs write directly to log files in PowerBuilder code (using Filewrite function). We also use Log4J, in some modules. Some of the logs end up in a Database table as well.

Database

22. LATAX uses Oracle 12c for the backend. The total production database size is over

158GB. There is one production instance, one reporting instance (copy of production), and various copies for development and testing. We have up to 1600 database objects including Tables, Views, Sequences and Stored Programs (Procedures, Functions, Packages, Triggers). Stored programs in LATAX are written in PL/SQL and Java.

LATAX calls Oracle stored procedures, functions and packages from PowerBuilder code. They are executed either directly (embedded SQL) or through the Transaction object (RPCFunc) or through a stored procedure interface written in Java.

23. LATAX currently uses 2 types of Database connections – OCI for the PowerBuilder

components and JDBC for all Java components. We use 10g drivers to connect to Oracle 12c database, because of limitations in EAServer.

16

DataWindow Specifics

24. As mentioned, all data operations occur on the server side. LATAX uses Datawindows and Datastores (and Embedded SQL) to get data from the database.

Datawindows are distributed in nature. Datawindows (and Datastores) are retrieved on the server side and synchronized to client side Datawindow controls (using PowerBuilder functions, SetFullState and GetFullState).

25. Datawindow objects are typically SQL based. But there also several external

Datawindows. LATAX uses mostly, Grid and Freeform style Datawindows. 26. LATAX has inherited and customized the Datawindow control. Functions like, header

sort (click header to sort by column), hovering tooltips, a notes popup, dropdown calendar have been added to the customized Datawindow (ancestor) control in LATAX.

27. Some Datawindows inside LATAX are used more as a spreadsheet, where another

Datawindows feeds the metadata and the data. 28. Any treeview structure that is visible in LATAX is essentially painted using a

Datawindow to simulate the look (not Treeview Datawindow) using Datawindow expressions on a hide/show properties.

29. LATAX Dropdown Datawindows are cached using a (custom) Java Cache Manager.

Each time a user requests a dropdown, it is added to the cache. A refresh will clear the cache completely.

30. Here are some other Datawindow features/functions used in LATAX:

Datawindow objects in LATAX have computed columns, computed fields

in them. We also use Datawindow expressions and validations in some areas.

LATAX uses global/session variables and/or functions inside the Datawindows.

LATAX uses Modify functions throughout to change the look and feel of GUI, enabling/disabling fields.

LATAX uses Datawindow Filters and sorting while presenting data to the user.

Miscellaneous

31. The application has built in security model. Users and roles are created and stored

inside the database. Views and buttons are shown/hidden or enabled/disabled based on security roles assigned to the user. System Administration views contain screens to manage System Security.

17

32. LATAX uses PowerBuilder external functions (in windows or other DLLs)

Example:

Here is an external function LATAX uses to compress arguments and objects:

Function integer compress ( Ref blob dest, Ref ulong destLen, Ref blob src, ulong srcLen ) Library "zlibwapi.dll"

Following functions are used in Renewal Estimated View:

FUNCTION ulong FindWindowA(ulong classname,string windowname) LIBRARY "User32.dll" alias for "FindWindowA;Ansi" FUNCTION ulong SetForegroundWindow (ulong hWnd) Library "USER32.DLL"

33. LATAX code also overrides some system (PowerBuilder built-in) functions. For

example today and now are overridden, so we can change “System date” used by the application. This is critical for testing some of the workflows.

34. LATAX has been developed over a time period by different developers, with varying

standards and methodologies. Some of the identifiers in LATAX code may not follow PowerBuilder standards. For example you may even see something like ls_account_number, ls_accountnumber, sometimes in the same code.

35. LATAX uses several parameters from various formats. Here are some of the sources:

INI file (client side settings, including servers to connect to) Properties files ( as used by some Java components) Component Properties (used to load system wide settings) Static/lookup tables in Database(for system wide and/or batch settings) The framework that LATAX is based on, uses XML internally to pass (serialize)

a variable list of arguments to and from server side components. It may also be compressed using ziplib.

18

Figure 3 LATAX Production Server Environment

19

The City is willing to provide source code of the current LATAX System to prospective bidders to aid in their development of a proposal response subject to their acceptance of the City’s Non-Disclosure Agreement requirements and meeting the qualifications and experience outlined in section E. on page 22. The City reserves the right to not distribute this source code to entities not deemed as sufficiently qualified for this proposed scope of work.

III. Proposer’s Conference A Proposers’ Conference will be conducted at 10:00 am on Thursday, June 9, 2016 at: City Hall – Room 152 A/B 200 N. Spring St. (use Main St. Entrance) Los Angeles, California 90012 ATTENDANCE AT THIS CONFERENCE IS MANDATORY in order to complete the “Good Faith Effort” outreach requirement of the City’s Business Inclusion Program. Failure to complete all tasks of the “Good Faith Effort” provision of the Business Inclusion Program will render your bid non-responsive and will result in its rejection. Refer to Appendix F for further information regarding this requirement. The purpose of the conference is to provide assistance to prospective proposers in the interpretation of this RFP, its scope, or any other terms and conditions. The City will make a presentation and respond to proposers’ questions. Proposers are requested to submit in writing, any questions for discussion at the conference no later than 5:00 pm, Thursday, June 2, 2016 to: Carl Sampson, Director of Systems Office of Finance, LATAX / Systems Division 1200 West 7th St., 7th Floor Los Angeles, CA 90017.

Questions may also be sent to Mr. Sampson by e-mail at carl.sampson@lacity.org. Written responses to questions will be distributed to all proposers in attendance at the Conference and to other proposers upon request. The City will respond only to questions that are submitted in writing in order to ensure that all proposers are treated equally during the RFP process.

IV. Deliverables Deliverables that shall be provided as part of this scope of work shall include, and not necessarily be limited to, the following:

A. Project Plan that is maintained throughout the project.

20

B. Prototype or “proof of concept” for a subset of LATAX functionality which demonstrates the approach and end product deliverable. The scope of the “proof of concept” will be a mutually agreed subset of functionality including both batch and end-user view components and shall be delivered within four months of the start of project work. Includes a successful build and operational technical infrastructure to demonstrate the functioning converted code. Failure to deliver this functioning “proof of concept” would result in termination of this agreement with no payments for any deliverable items outside of A. and B. of this section.

C. Fully executing code developed in .NET (C#) or Java which provides the

full functionality of the LATAX System verified by a user acceptance test conducted by City staff.

D. The full set of source code utilized to generate the executable(s) and

instructions for build and deployment.

E. Complete instructions and support for setting up and configuring underlying infrastructure on which the converted code will run.

F. Unit testing and System Integration Testing for all converted code using a

subset of LATAX data using test scripts provided by the City’s LATAX section.

G. Support during User Acceptance Testing and Implementation.

H. Knowledge Transfer that includes:

1. Documentation on the infrastructure to run the code on,

including an infrastructure diagram. 2. Project specific documentation for any deployment tools

such as IDE, as well as procedures for compilation of program code and performing code deployments.

3. Documentation of the libraries, frameworks, and any API’s utilized in the new code environment including a breakdown of converted code by functional area.

4. Documentation on the design and operation of any functional areas replaced with new solutions instead of converted, such as correspondence, screen view definition architecture, or workflow process.

5. Documentation and/or training for creating new modules using the new software and infrastructure.

I. Six months of post-production support that includes support during peak

operating usage the following December through March after implementation.

21

VI. Contents of Proposal Proposals shall be organized generally as described below. You should note the various attachments that must be submitted with your proposal. Failure to follow these guidelines may cause your proposal to be considered non-responsive.

A. Cover Letter

The cover letter of each proposal shall be limited to one page. The letter must include the name, title, address, and telephone number of the person or persons who will be authorized to represent the proposer. The letter must be signed by a company officer authorized to bind the company to all commitments made in this proposal.

B. Business Organization 1. State the full name and address of your organization and, if

applicable, any branch or district office that will be managing the Program.

2. Indicate whether you operate as an individual, partnership, or

corporation. If a corporation, include the State in which you are incorporated.

3. Provide copies of any license(s) and/or registration(s) which

indicate that your firm is licensed and/or registered to operate in the State of California and the City of Los Angeles.

4. The contractor shall provide a summary of relevant historical

background information of the contractor as a firm or other entity and a copy of its most recent financial statements. If the proposal includes subcontractors, this requirement is also applicable to those organizations. Documentation submitted will be used as an indicator of the ability of the contractor (and subcontractors, if any) to provide the requested services over the full term of the contract.

C. Project Personnel

The contractor must be able to demonstrate capability and appropriate experience of key personnel that will be assigned to implement and manage this program. Key program personnel including project management and support personnel shall be identified by name and title, and include a statement of the program areas for which they will be responsible. Resumes for these key personnel are required to be submitted as well as those of other employees the contractor will be employing to perform the required services. The City shall have the right to conduct background verifications on all personnel

22

directly assigned to the Program, including the key personnel noted above. The City will reserve the right to approve any changes in key personnel. Such approval will not be unreasonably denied. The same requirements will apply to any subcontractors. The contractor should also identify the anticipated work site for all personnel during the duration of this project whether that be on-site or at a vendor work location. Due to the nature of the work involved and the confidentiality of data and programming processes the City is seeking a contract partner which will have work performed predominately within the United States of America.

D. Los Angeles Municipal Code - SEC. 21.17 - CONFIDENTIAL CHARACTER

OF INFORMATION OBTAINED – DISCLOSURE UNLAWFUL.

“It shall be unlawful for the Director of Finance or any person having an administrative duty under the provisions of this Article or Article 1.6 to make known in any manner whatever the business affairs, and operations of, or the nature, amount or source of income, profits, losses, expenditures, net worth, or any particular thereof, or any other information set forth in any statement or return or obtained by an investigation of records and equipment of any person required to obtain a business tax registration certificate or sales or use tax permit, or pay business, sales or use tax or any other person visited or examined in the discharge of official duty, or to permit any statement or return, or copy of either, or any book containing any abstract or particulars thereof to be seen or examined by any person…” All personnel that are involved in the Program will be required to execute City Confidentiality Statements and acknowledge that misuse of confidential information is prohibited under LAMC Section 21.17 as detailed below. A sample Office of Finance confidentiality agreement is attached for reference (see Appendix K).

E. Firm Qualifications, Experience and References

Provide a narrative describing the firm’s qualifications to perform the project work, including past (relevant) experience and at least three client references where PowerBuilder EA Server conversions were performed. Please include contact names and information about the project. Please identify any projects that involved an equivalent level of complexity and scale in relation to the effort detailed in this RFP.

F. Statement of the Program

State succinctly your understanding of the Program being contracted for by the City and presented in this Request for Proposal.

G. Project Approach and Work Plan

Provide a narrative which shows your firm’s understanding of the project’s requirements and documents a logical technical approach to the project scope of work. Include a general work plan as well as the proposed approach to undertaking the

23

scope of work described earlier in this RFP.

Using the scope of services presented in this RFP, propose a work plan detailing major tasks and subtasks and the work to be conducted in each.

If specific project team members or vendors are critical to specific tasks, identify where they will be utilized and/or committed.

Identify appropriate assumptions and considerations that could impact the scope and timeline for completing each task.

Clearly identify any deliverables or resources which the City would need to provide and when those deliverables or resources would need to be provided on the proposed work plan.

H. Technical Approach

The proposed solution must provide the functionality described in section II, Description of Desired Solution. For each item listed below, provide details on how the proposed solution will satisfy it, explain if there are any assumptions or caveats to that, and include any additional details as requested:

1. Describe the high-level approach to performing the conversion process, including which steps are computer-generated, and which are manual work, and what percent of the overall work is anticipated in each category.

2. The converted system must have the same look and feel to users as the current LATAX, as described in section II, description of Desired Solution above.

3. The converted system must work seamlessly with the existing Oracle 12c Database and Data model.

4. Which language is your proposed solution based on - .Net(C#) or Java? If you feel both could satisfy the requirements, provide the following details for each, and any reason you would recommend one over the other:

● Any prerequisites that must be satisfied before LATAX code can be ported to a .Net (C#) and/or Java environment.

● The .Net (C#) and/or Java version level you recommend for this solution

● The OS and other software, including version numbers, you recommend for this solution

● The server specs you recommend for this solution, and the quantity of app servers to handle the concurrent volume.

24

● Any frameworks or 3rd party software, along with their versions and licenses, required for your solution.

● How your conversion process will replace or augment existing frameworks/API (EAF for example) already used in LATAX code base.

● List all the interfaces and protocols to be implemented in your migrated solution.

If you feel neither .Net (C#) nor Java would satisfy the requirements, and you recommend a different language, describe why, and provide the details above for the recommended language.

5. Delivered code must follow current industry standards for the target platform. Provide the following details for each language recommended in #4, above.

● List out your firm’s standards for the recommended language platform.

● Specify how will the identifier (variables, functions) names be handled in the converted code? Will the case of the identifier names, and special characters used in naming in PowerBuilder, cause any issues for the converted system?

● Provide sample code (~ 100 lines) from a conversion that your company performed for a previous customer from PowerBuilder to the recommended target language, as an example. We would like to see both the original PowerBuilder code and the converted .Net (C#) or Java code.

6. In converting the LATAX client to a browser-based solution that keeps the complexity and versatility of the current user interface implemented in PowerBuilder:

● Specify the techniques and libraries/frameworks that will be used in the conversion.

● If you recommend against a browser-based solution, describe why and provide the details of your recommended alternative.

7. The LATAX client currently assembles its views (screens) dynamically at run-time, using meta-data in the database tables. Application Security is also tied into this. Pop-up and Search windows are built similarly.

● Specify how you will be able to maintain the dynamic nature of the existing view architecture in the new platform.

● If you believe it is not possible to retain the dynamic nature of the existing view architecture, describe why and provide the details of your recommended alternative for managing application security.

25

8. Describe how Datawindows and Datastores will be handled in your converted product?

9. Describe how you will convert all the PowerBuilder controls to the new environment? Include an explanation on how you will convert Edit Masks and Drop-down Datawindows.

10. As mentioned in Section II item 16, LATAX retains session information. For example, the Account Number the user selected on one screen is available throughout the application. Describe how you will implement this in the converted system. Also, describe how System wide parameters and local parameters will be handled in your solution.

11. The Correspondence module in LATAX works with Word Templates and Bookmarks to generate notices and correspondences. For this it currently uses OLE. (See Section II item 13 for more details). Describe how the converted system will retain this functionality. If cannot, describe why and your recommended alternative.

12. LATAX batch programs (processing large volumes of data) share the same business rules as the client applications; those rules are written in PowerBuilder and run inside EAServer as CORBA components, optimized using Object pooling. Describe how the batch jobs would continue to share this code in the converted system, and confirm that the converted system can interact with Control-M for job scheduling.

13. Existing web programs written in JSP & ColdFusion, which provide online self-service to the public, share some of the same business rules as the client applications. Describe how LATAX web programs will continue to share this code in the converted system.

14. Describe how the proposed solution will handle the custom Workflows, as detailed in Section II item 12.

15. LATAX uses distributed transactions as listed in Section II item 18. Describe how the proposed solution will handle distributed transactions.

16. Describe how the proposed solution will handle External Functions, as listed in Section II item 32.

17. Describe the format you will be able to provide the “Unused Objects” report in, before and again after conversion. This is to help the City identify any dead code and/or dangling functionality.

18. Delivered code must be unit tested at the Function level before delivery to the City. Describe your testing process.

26

19. Describe the release and deployment process.

I. Project Management

Describe how your firm intends to manage all aspects of the work to be performed, including schedules for completion of tasks/subtasks, procedures for scheduling and cost control. J. Cost Provide pricing and cost information. All responses should include a proposed payment schedule itemizing all deliverable payment amounts and dates. All costs including any travel-related costs should be identified and proposals should state this fact clearly. Depending on the plans designed in the RFP responses there may be some alterations to the deliverables and/or payment schedule set forth in the final resulting agreement. The City is seeking costs for two possible target environments .NET (C#) and Java.

K. Proposal Addendum

All requirements listed below must be strictly adhered to and all applicable signed statements pertaining to the following must be submitted:

1. Contractor Responsibility Ordinance (See Appendix B) 2. Nondiscrimination – Equal Employment Practices - Affirmative Action

(See Section VII D.) 3. Certification of Compliance With Child Support Obligations (See

Appendix C) 4. Service Contract Worker Retention and Living Wage Ordinance

Compliance (See Appendix D) 5. Certification regarding Compliance with the Americans With Disabilities

Act (See Appendix E) 6. Business Inclusion Program (See Appendix F) 7. Certification of Compliance With Equal Benefits Ordinance (See Section

VII G) 8. Slavery Disclosure Affidavit (See Section VII H) 9. Non-Collusion Affidavit (See Appendix G) 10. Workforce Residence Information (See Appendix H) 11. Prior City Contract History Form (See Appendix I)

12. Bidder Certification – CEC Form 50 - Compliance with Municipal Lobbying Ordinance (See Appendix J)

13. City of Los Angeles – Confidentiality Agreement / Loyalty Oath (See Appendix K)

14. Bidder Campaign Contribution Limits – CEC Form 55 (See Appendix L) 15. First Source Hiring Ordinance (See Appendix M) 16. Local Business Preference Program (See Appendix N )

27

L. Additional Information

Any other information that you believe will be essential to a complete evaluation of your proposal should be clearly stated. If you have no additional information, this section of your proposal should consist of the following statement: "There is no additional information we wish to present."

M. Omissions and/or Deviations

Any omissions and/or deviations from this proposal must be listed with complete explanations. Proposals will be considered for materials or services deviating from the specifications if such products comply substantially with the specifications. Each deviation from the specifications must be stated in a letter attached to your proposal. If provisions of the specifications restrict bidder from bidding, bidder may request in writing that the specifications be modified. Such request must be received by the Office of Finance Contract Contact at least fifteen (15) working days before the RFP due date. All bidders will be notified by Addendum of any approved change in the specifications. The City of Los Angeles shall be the sole determiner of substantial compliance with the specification. Failure to submit or disclose deviations from the RFP specifications will make your proposal non-responsive.

VII. Proposal Requirements This section sets forth provisions, which will be incorporated into any contract awarded pursuant to the RFP and also identifies the forms, certifications, requests for information, and affidavit which must be completed and returned with the proposal. Failure to provide the information requested and/or to submit the necessary forms may result in the proposal being deemed non-responsive.

A. Contract Term

The Office of Finance, subject to the approval of the City Council, anticipates negotiating a contract with a duration of up to three years.

B. Standard Provisions The selected Proposer will be required to enter into a written contract with the City of Los Angeles in a form approved by the City Attorney. A copy of this RFP with all attachments and the successful proposal will remain on file and will constitute a part of the contract. However, the City reserves the right to further negotiate the terms and conditions of the contract with the selected contractor. The final contract offer of the City may contain additional terms or terms different from those set herein. The

28

“Standard Provisions for City Contracts (Rev, 03/09)” attached as Appendix A, will be incorporated into the contract and are not subject to negotiation. These provisions include, but are not limited to, the following:

1. Indemnification

The Contractor will be required to indemnify the City in accordance with the provisions set forth in PSC-20 of the Standard Provisions for City Personal Services Contracts.

2. Insurance

The Contractor will be required to provide insurance in accordance with the Insurance Requirements, Appendix A - Exhibit 1, attached to the Standard Provisions for City Contracts. Proof of Insurance will be required prior to contract execution and does not need to be returned with the response to this RFP. 3. Business Tax Registration Certificate

Prior to execution of a contract, the selected Proposer shall be required to demonstrate compliance with the City’s business tax laws by acquiring/maintaining one of the following: Business Tax Registration Certificate, Vendor Registration Number, or Certificate of Exemption. The Certificate or Registration Number must remain in force during the entire period of the contract.

C. Contractor Responsibility Ordinance

Bidders/Proposers are advised that any contract awarded pursuant to this procurement process shall be subject to the provisions of Los Angeles Administrative Code Section 10.40 et seq., Contractor Responsibility Ordinance (CRO). Bidders/Proposers shall refer to Appendix B, “Contractor Responsibility Ordinance,” for further information regarding the requirements of the Ordinance. All Bidders/Proposers shall complete and return, with their proposal, the Responsibility Questionnaire included in the Appendix. Failure to return the completed Questionnaire may result in a Bidder/Proposer being deemed non-responsive.

D. Nondiscrimination, Equal Employment Practices and Affirmative Action

Program Requirements

Bidders/Proposers are advised that any contract awarded pursuant to this procurement process shall be subject to the applicable provisions of Los Angeles Administrative Code Section 10.8.2., Non-discrimination Clause.

29

Non-construction services to or for the City for which the consideration is $1,000 or more shall comply with the provisions of Los Angeles Administrative Code Sections 10.8.3., Equal Employment Practices Provisions. All Bidders/Proposers shall complete and upload, the Non-Discrimination/Equal Employment Practices Affidavit (two (2) pages) available on the City of Los Angeles’ Business Assistance Virtual Network (BAVN) residing at www.labavn.org prior to award of a City contract valued at $1,000 or more. Non-construction services to or for the City for which the consideration is $100,000 or more [over the term of the contract] shall comply with the provisions of Los Angeles Administrative Code Sections 10.8.4., Affirmative Action Program Provisions. All Bidders/Proposers shall complete and upload, the City of Los Angeles Affirmative Action Plan (four (4) pages) available on the City of Los Angeles’ Business Assistance Virtual Network (BAVN) residing at www.labavn.org prior to award of a City contract valued at $100,000 or more. Bidders/Proposers opting to submit their own Affirmative Action Plan may do so by uploading their Affirmative Action Plan onto the City’s BAVN. Both the Non-Discrimination/Equal Employment Practices Affidavit and the City of Los Angeles Affirmative Action Plan Affidavit shall be effective for a period of twelve months from the date it is first uploaded onto the City’s BAVN. Bidders/Proposers seeking additional information regarding the requirements of the City’s Non-Discrimination Clause, Equal Employment Practices and Affirmative Action Program may visit the Bureau of Contract Administration’s web site at http://bca.lacity.org.

E. Business Inclusion Program and Outreach

All Bidders/Proposers shall comply with the City’s Business Inclusion Program requirements, identify sub-contracting opportunities and outreach to Minority Business Enterprises (MBE), Women Business Enterprises (WBE), Small Business Enterprises (SBE), Emerging Business Enterprises (EBE), Disabled Veteran Business Enterprises (DVBE), and Other Business Enterprises (OBE) sub-consultants. Requirements must be completed on the Business Assistance Virtual Network (BAVN), www.labavn.org. (See Appendix F: Instructions for Performing BIP Outreach).

F. Service Worker Retention and Living Wage Ordinance Compliance

Unless approved for an exemption, contractors under contracts primarily for the furnishing of services to or for the City and that involve an expenditure in excess of $25,000 and a contract term of at least three (3) months, lessees and licensees of City property, and certain recipients of City financial assistance, shall comply with the provisions of Los Angeles Administrative Code Sections 10.37 et seq., Living Wage Ordinance (LWO) and 10.36 et seq., Service Contractor Worker Retention Ordinance (SCWRO). Bidders/Proposers shall refer to Appendix D, “Living Wage Ordinance and Service Contractor Worker Retention Ordinance” for further information regarding the requirements of the Ordinances. Bidders/Proposers who believe that they meet the

30

qualifications for one of the exemptions described in the LWO List of Statutory Exemptions shall apply for exemption from the Ordinance by submitting with their proposal the Bidder/Contractor Application for Non-Coverage or Exemption (Form OCC/LW-10), the Non-Profit/One-Person Contractor Certification of Exemption (OCC/LW-13) or the Small Business Exemption (Form OCC/LW26A). These exemption forms are available on the Bureau of Contract Administration website at http://bca.lacity.org/index.cfm. The List of Statutory Exemptions are included in Appendix D.

G. Equal Benefits Ordinance

Bidders/Proposers are advised that any contract awarded pursuant to this procurement process shall be subject to the applicable provisions of Los Angeles Administrative Code Section 10.8.2.1, Equal Benefits Ordinance (EBO). All Bidders/Proposers shall complete and upload, the Equal Benefits Ordinance Affidavit (two (2) pages) available on the City of Los Angeles’ Business Assistance Virtual Network (BAVN) residing at www.labavn.org prior to award of a City contract valued at $5,000. The Equal Benefits Ordinance Affidavit shall be effective for a period of twelve months from the date it is first uploaded onto the City’s BAVN. Bidders/Proposers do not need to submit supporting documentation with their bids or proposals. However, the City may request supporting documentation to verify that the benefits are provided equally as specified on the Equal Benefits Ordinance Affidavit. Bidders/Proposers seeking additional information regarding the requirements of the Equal Benefits Ordinance may visit the Bureau of Contract Administration’s web site at www.bca.lacity.org.

H. Slavery Disclosure Ordinance Unless otherwise exempt, in accordance with the provisions of the Slavery Disclosure Ordinance, any contract awarded pursuant to this RFB/RFP/RFQ will be subject to the Slavery Disclosure Ordinance, Section 10.41 of the Los Angeles Administrative Code. All Bidders/Proposers shall complete and upload, the Slavery Disclosure Ordinance Affidavit (one (1) page) available on the City of Los Angeles’ Business Assistance Virtual Network (BAVN) residing at www.labavn.org prior to award of a City contract. Bidders/Proposers seeking additional information regarding the requirements of the Slavery Disclosure Ordinance may visit the Bureau of Contract Administration’s web site at www.bca.lacity.org.

I. Prior Contracts With The City

All proposers must include a list of all contracts with the City for the past ten (10) years using the Prior City Contract History form attached as Appendix I. J. Affidavit of Non-Collusion

31

As required by Los Angeles Administrative Code section 10.15(d), proposers shall complete and return with the proposal, a notarized affidavit of non-collusion signed by a person(s) authorized to bind the proposer (see Appendix G), which states in part that:

1. The proposal is genuine, not a sham or collusive; 2. The proposal is not made in the interest of or on the behalf of any person

not named in the proposal; 3. The Proposer has not directly or indirectly induced or solicited any

person to submit a false or sham proposal or to refrain from proposing; 4. The Proposer has not in any manner sought by collusion to secure an

advantage over any other proposer. K. Disposition of Proposals and Disclosure of Information

The City reserves the right to retain all proposals submitted and the proposals will become the property of the City of Los Angeles. All proposals received will be considered public records potentially subject to disclosure under the Public Records Act (California Government Code Section 6250 et seq.). Proposers must identify any material they claim is exempt from disclosure under the Public Records Act. Any Proposer claiming such an exemption must identify the specific provisions of the Public Records Act that provide an exemption from disclosure for each item that the proposer claims is not subject to disclosure under said Act. In the event that such exemption is claimed, the proposer must then state in the proposal that he or she will defend, indemnify and hold harmless the City, its officers and employees from any action brought against the City for its refusal to disclose such material to any party making a request therefore. Failure of a Proposer to include such a statement shall constitute a waiver of proposer’s right to exemption from disclosure.

L. Withdrawal of Proposal

Each proposal must contain a statement that the proposal shall remain firm for a period of one hundred twenty (120) calendar days following the deadline date for submission of proposals to the Office of Finance, which date is noted in the cover letter and body of this RFP.

M. Required Copies and Deadline for Submission of Proposal.

Proposers must supply all information requested in the format prescribed by this RFP. One clearly identified original and five (5) clear copies of the proposal are required. Additionally, please provide one (1) electronic / CD version as well in MS Word or Adobe PDF format. The proposal shall be addressed to:

Carl Sampson, Director of Systems

32

Office of Finance, LATAX / Systems Division 1200 West 7th St., 7th Floor Los Angeles, CA 90017.

No proposal will be accepted after 5:00 P.M. on Thursday, July 28, 2016. The City reserves the right to extend the deadline for response to this RFP and to waive any informality in procedure should such action be deemed in the best interest of the City. In the event this date is changed, those who have been sent the RFP will be notified in writing. The City may require oral presentation of the proposals by the proposers to a review committee. The City reserves the right in its sole discretion to determine the timeliness of all proposals, extend the submission deadline and/or to reject all proposals.

N. Mandatory Protest Provisions: Any protest as to the RFP documents or matters or procedures referred to therein must be submitted in detail and in writing and postmarked within 5 calendar days after the issuance of the RFP to the public. The RFP is considered issued when posted to the Los Angeles Business Assistance Virtual Network at http://www.labavn.org/. All persons submitting quotations in response to this RFP will be notified of the City’s intended award by mail. Any protest regarding the City's intention to award a contract which results from this RFP process must be submitted in detail and in writing and be postmarked within 7 calendar days of the postmark date of the City’s notification letter concerning the City's intention to award a contract that results from this RFP process.

Any protest, whether relating to the RFP or to the eventual awarding of a contract resulting from this RFP process, shall contain a full and complete statement specifying in detail the grounds of the protest and the facts in support thereof. All protests must include the following information:

1. The name address and telephone of the person representing the

protesting party; 2. The name of the involved RFP; 3. A detailed written statement of the legal and factual grounds of the

protest, including copies of relevant documents and an indication as to what specific portions of the documents form the basis of the protest;

4. A statement as to the form of relief requested; and 5. Any evidence as to why the RFP should not issue, or in the event of a

protest concerning a contract award, any reasons or evidence as to why a contract award should not be made according to the City's plans;

6. If applicable, a request that a hearing with the Director of Finance, or her designee, be set within 7 calendar days of the actual receipt by the City of the protest or, in the alternative, a statement that the protester waives such hearing.

7. A request that the Directory of Finance, or her designee, issue a decision either sustaining or denying the protest.

33

All protests, whether relating to the RFP or a resulting contract award, must be in writing and sent via certified mail to:

Claire Bartels Director of Finance / City Treasurer Office of Finance 200 N. Spring St., Room 220, Mail Stop 766 Los Angeles, California 90012

The procedure and time limits set forth in this Section are mandatory and are the sole and exclusive remedy available in the event of protest. Failure to comply with these procedures shall constitute a waiver of any right to further pursue the protest, including filing a Government Code claim or legal proceedings. The City will only consider protests by or against any Proposer(s) who appear to have a substantial and reasonable prospect of receiving an award if the protest is denied or sustained, as applicable.

Protests meeting the above criteria will be reviewed by the Director of Finance, or her designee. Protesting parties requesting a hearing will be notified of the time and date of a hearing within seven (7) calendar days of the actual receipt of the written protest with the Director of Finance or her designee. Protestors requesting a hearing will be given the opportunity to present their arguments to the Director of Finance, or her designee. The Director of Finance, or her designee, will hear and consider the contents of any written protest and/or any arguments made at the time of the hearing, and will issue by mail a decision in writing to the protester that either denies or sustains the protest within 5 calendar days. The decision of the Director of Finance, or her designee, shall be final.

O. Child Support Ordinance

This Contract is subject to the Child Support Ordinance, Los Angeles Administrative Code Section 10.10 et seq. Proposers shall complete and return with their proposal, the Certification of Compliance with Child Support, which is attached hereto as Appendix C.

P. Americans with Disabilities Act

The City is a covered entity under Title II of the Americans with Disabilities Act, 42 U.S.C.A. Section 12131 et seq. Proposers shall complete and return with their proposal, the Certification Regarding Compliance with the Americans with Disabilities Act which is attached hereto as Appendix E.

Q. Workforce Information

The policy of the City of Los Angeles is to encourage businesses to locate or remain in the City. Therefore, the City Council requires all City departments to gather

34

information regarding the headquarters address and other information on the employees of vendors contracting with the City. The following information shall be included with the proposal (see Appendix H):

1. Headquarters address of your company.

2. Total workforce. 3. Percentage of the total workforce residing in Los Angeles. 4. Percentage of total workforce working in Los Angeles. 5. The address of any branch office(s) within the City of Los Angles. 6. Workforce in each City of Los Angeles branch office. 7. Percentage of workforce in each City of Los Angeles branch office

residing in the City of Los Angeles. 8. Percentage of workforce assigned to each branch office in the City of

Los Angeles.

R. Confidentiality Requirements

As previously mentioned, all information received from Taxpayer or City files shall be regarded as confidential under Section 21.17 of the Los Angeles Municipal Code and may not be disclosed without written permission of the City’s representative. Any information received by the contractor from the City shall not be released to or used for the benefit of any clients or employees of the contractor or any other person(s) without written permission of the City’s representative. All personnel that are involved in the Program will be required to execute City Confidentiality Statements and acknowledge that misuse of confidential information is prohibited under LAMC Section 21.17 as detailed below. A sample Office of Finance confidentiality agreement is attached for reference (see Appendix K). S. Bidder Campaign Contribution Limitations

Persons who submit a response to this solicitation (bidders) are subject to Charter section 470(c)(12) and related ordinances. As a result, bidders may not make campaign contributions to and or engage in fundraising for certain elected City officials or candidates for elected City office from the time they submit the response until either the contract is approved or, for successful bidders, 12 months after the contract is signed. The bidder's principals and subcontractors performing $100,000 or more in work on the contract, as well as the principals of those subcontractors, are also subject to the same limitations on campaign contributions and fundraising. Bidders must submit CEC Form 55 (provided in Appendix L) to the awarding authority at the same time the response is submitted. The form requires bidders to identify their principals, their subcontractors performing $100,000 or more in work on the contract, and the principals of those subcontractors. Bidders must also notify their principals and subcontractors in writing of the restrictions and include the notice in contracts with subcontractors. Responses submitted without a completed CEC Form 55 shall be deemed non-responsive. Bidders who fail to comply with City law may be subject to penalties, termination of contract, and debarment. Additional information regarding

35

these restrictions and requirements may be obtained from the City Ethics Commission at (213) 978-1960 or ethics.lacity.org. T. First Source Hiring Ordinance Unless approved for an exemption, contractors under contracts primarily for furnishing of services to or for the City, the value of which is in excess of $25,000 and a contract term of at least three (3) months, and certain recipients of City Loans or Grants, shall comply with the provisions of Los Angeles Administrative Code Sections 10.44 et seq., First Source Hiring Ordinance (FSHO). Bidders/Proposers shall refer to Appendix M, “First Source Hiring Ordinance” for further information regarding the requirements of the Ordinance.

All Proposers shall complete and upload the First Source Hiring Ordinance Affidavit (one (1) page) available on the City of Los Angeles’ Business Assistance Virtual Network (BAVN) at www.labavn.org prior to award of a City contract. The First Source Hiring Ordinance Affidavit shall be valid for a period of twelve months from the date it is first uploaded onto the City’s BAVN. Proposers seeking additional information regarding the requirements of the First Source Hiring Ordinance may visit the Bureau of Contract Administration’s web site at http://bca.lacity.org.

U. Local Business Preference Program Ordinance The Local Business Preference Program Ordinance (Los Angeles Administrative Code Section 10.47) establishing the Local Business Preference Program for the City’s procurement of goods, equipment and services, including construction, when the contract involves an expenditure in excess of $150,000 is available as Appendix N, and incorporated herein by reference, If you believe you are qualified or can be provisionally qualified as a Local Business please indicate that in your proposal.

VIII. Selection Criteria Each proposal must meet all requirements included in Section VII and be evaluated according to the criteria set out below:

A. Tier I Evaluation

Proposers will be evaluated and rated based on the response provided in Section VI above. Proposers may be requested to provide written clarifications regarding proposed services as an additional step in the Tier I process. The written clarifications will be incorporated into the Tier I evaluation herein. Proposals will be evaluated based on a combination of the following:

36

Proposal Quality, Responsiveness and Technical Solution

Comparable Experience and Successful Migrations of Similar Systems

Evaluation of Key Personnel

Fee for Services A short list consisting of the top proposers in terms of scores shall be established. Proposers on the short list shall advance to Tier II of the process as outlined below.

B. Tier II Evaluation

Proposers with the top scores after completion of the Tier I evaluation will be required to participate in a series of presentations and discussions and any relevant demonstrations with the City Proposal Review Team regarding all proposed services, deliverables and commitments contained in the proposal. Proposers shall identify references as specified in Section VI subsection E. Proposers shall not initiate any contact with the City to clarify or explain their proposals unless requested to do so by the City. Proposers may not attend demonstrations or presentations made by their competitors. Oral presentation agenda and scripts, if applicable, shall be provided to the Proposers prior to the appointed presentation dates. This process allows the City to more thoroughly evaluate company expertise, qualifications, operations and services deemed by the City to be in its best interests.

C. Basis of Award and Selection

Subject to the provisions herein, contract awards will be made to the overall best value proposal, as determined by the City in its sole discretion, with the appropriate consideration given to the evaluation factors stated herein. Ultimately, the contract award decision will take into account the Proposer’s technical capability to meet the requirements of the RFP in a timely manner on a cost effective basis.

IX. Required Contract The selected Proposer will be required to enter into a written contract with the City of Los Angeles in a form approved by the City Attorney. A copy of this RFP with all attachments and the successful proposal will remain on file and will constitute a part of the contract. However, the City reserves the right to further negotiate the terms and conditions of the contract with the selected contractor. The “Standard Provisions for City Contracts (Rev. 03/09)” (Appendix A) will be incorporated into the contract and are not subject to negotiation.

37

X. Acceptance of Terms and Conditions

Submission of a proposal pursuant to this RFP shall constitute acknowledgement and acceptance of all terms, conditions, and content set forth in this RFP.

XI. Rejection of Reponses to RFP

The City reserves the right to withdraw this RFP at any time without prior notice and the right to accept or reject any and all responses to it. The City may also reject the proposal of any proposer who has failed to timely and satisfactorily perform any contract with the City. The City makes no representation that any contract will be awarded to any person or firm responding to this RFP.

XII. Financial Responsibility All costs incurred in responding to this RFP shall be borne by the proposer. The City shall not, in any event, be liable for any pre-contractual expenses incurred by the proposer in the preparation and/or submission of its proposal.