PORT AUTHORITY OF ALLEGHENY COUNTY

REQUEST FOR PROPOSALS for a MOBILE TICKETING APPLICATION AND SUPPORTING SERVICES RFP NO. 18-07

Vendor Sourcing Category: PROFESSIONAL SERVICES

Vendor Sourcing Sub-Category: PSITS - Pro-Information Technology PSSC - Pro Software Consulting

October 2018

Port Authority of Allegheny County 345 Sixth Avenue, Third Floor Pittsburgh, Pennsylvania 15222-2527 Main Phone Number: (412) 566-5500 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

Table of Contents 1.0 General Information ...... 6 1.1 Introduction ...... 6 1.2 Definitions ...... 6 1.3 Proposal Submission Schedule...... 9 1.4 RFP as Exclusive Basis for Proposal ...... 10 1.5 Modifications, Deviations and Irregularities ...... 11 1.6 Conditions, Exceptions, Reservations or Understandings ...... 11 1.7 Modification or Withdrawal of Proposals ...... 11 1.8 Form of Contract ...... 12 1.9 Contractor Responsibility for Subcontractors ...... 12 1.10 Adverse Interest Law ...... 12 1.11 Pennsylvania’s Right-to-Know Law ...... 12 2.0 Proposal Requirements ...... 12 2.1 General Requirements ...... 12 2.1.1 Letter of Transmittal/Proposal Requirements ...... 12 2.1.2 Diverse Business (DB) Subcontract Participation ...... 14 2.2 Overview of Proposer ...... 15 2.2.1 Description of Proposer ...... 15 2.2.2 Agent ...... 15 2.2.3 Contractor/Subcontractor Percentage of Work ...... 16 2.2.4 Joint Venture ...... 16 2.2.5 Personnel and Operations Policies ...... 16 2.3 Experience Record ...... 16 2.4 Project Work Plan ...... 17 2.4.1 Methodology ...... 17 2.4.2 Flow Chart ...... 17 2.5 Project Organization and Management Plan ...... 18 2.5.1 Description of Organization and Management Plan ...... 18 2.5.2 Project Organizational Chart/Resumes ...... 18

2 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

2.5.3 Key Personnel Guarantee ...... 18 2.5.4 Certification/License Requirements ...... 18 2.6 Summary of Costs ...... 19 2.6.1 Payment Schedule ...... 19 2.6.2 Anticipated Term of Agreement ...... 20 2.6.3 Thresholds ...... 20 2.7 Appendix ...... 21 2.7.1 Service Provider Security Information Questionnaire ...... 21 2.7.2 Financial Information ...... 21 2.7.2.1 Financial Statements ...... 21 2.7.2.2 Exceptions for Privately-Held Firms ...... 22 2.7.3 Certification of Proposer Regarding Debarment ...... 23 2.7.4 Proposer/Subcontractor Data Form ...... 23 2.7.5 Resumes ...... 23 2.7.6 Key Personnel Guarantee ...... 23 2.7.7 Affirmative Action and Equal Opportunity Policy ...... 23 2.7.8 Insurance Requirements ...... 23 2.7.9 Joint Venture Requirements ...... 23 3.0 Proposal Selection Process ...... 23 3.1 Evaluation Committee ...... 24 3.2 Proposal Evaluation Criteria ...... 24 3.3 Evaluation Procedures ...... 25 3.4 Finalization of Agreement ...... 26 3.5 Contract Award ...... 27 3.6 Failure to Execute a Contract ...... 27 3.7 Acceptance / Rejection of Proposers ...... 27 3.8 Cancellation of Procurement ...... 27 3.9 Authority Protest Procedures ...... 27 4.0 Scope of Services...... 27 4.1 General Information ...... 27 4.2 Technical Requirements ...... 28 4.3 Functional Requirements ...... 29 4.3.1 Set Up and Account Management ...... 29

3 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

4.3.2 Purchases ...... 30 4.3.3 Transit Pass Programs and Additional Functions ...... 30 4.3.4 Validation and Cancellation ...... 31 4.3.5 ADA Compliance ...... 32 4.3.6 Real-Time Service Information ...... 32 4.3.7 Features to Enhance Customer Convenience ...... 32 4.3.8 MTAS Languages ...... 32 4.3.9 Messages and Alerts ...... 32 4.3.10 Deliver Prompt and Efficient Customer Information ...... 32 4.3.11 Sales Volume ...... 33 4.3.12 Administration ...... 33 4.4 System Requirements ...... 33 4.4.1 Independent Mobile Ticketing Application System ...... 33 4.4.2 Service Design and Development ...... 33 4.4.2.1 Design Criteria ...... 33 4.4.2.2 Design Reviews ...... 36 4.4.2.3 Final Design and Configuration Documents ...... 36 4.4.2.4 Installation Plan ...... 36 4.4.3 Testing, Quality Assurance ...... 37 4.4.3.1 Beta Program ...... 37 4.4.3.2 Pilot Program ...... 37 4.4.4 Service Final Acceptance ...... 38 4.4.5 System Performance Criteria ...... 38 4.4.5.1 Testing and QA ...... 38 4.4.5.2 The MTAS (Ridership) Simple Functionality ...... 39 4.4.5.3 Communications and Power Failure ...... 39 4.4.5.4 MTAS Rider Ticket Use Experience; ...... 39 4.4.5.5 MTAS Back-office Data Integrity & Accuracy ...... 39 4.4.5.6 Back-office processed transaction data performance ...... 40 4.4.5.7 MTAS Website Performance ...... 40 4.4.5.8 Power or Network Connection Failure ...... 40 4.4.6 Security ...... 40 4.4.6.1 Cybersecurity ...... 40

4 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

4.4.6.2 System Security Information Questionnaire ...... 40 4.4.6.3 VPN Access ...... 40 4.4.7 Reporting and Settlement ...... 41 4.4.7.1 Ridership ...... 41 4.4.7.2 Trip Information Interface ...... 41 4.5 Service Levels ...... 41 4.5.1 Data Integrity and Accuracy ...... 41 4.5.2 Transaction Processing and Settlement ...... 41 4.5.3 Availability ...... 42 4.6 Program Management and Scheduling ...... 42 4.7 Training ...... 42 4.7.1 Training Documentation ...... 43 4.8 Maintenance and Support Services ...... 43 4.9 Support...... 43 4.9.1 Ownership and Exclusivity ...... 43 4.9.1.1 Website Ownership Rights ...... 43 4.9.1.2 Exclusivity ...... 44 4.9.1.3 Licensing ...... 44 4.9.1.4 Licensing Termination ...... 44 The Authority reserves the right to purchase or license for an extended period of time, take over and or operate the Service in the event the Contractor files for bankruptcy...... 44 EXHIBIT 1: Sample Agreement No. R18-07 ...... 45 EXHIBIT 2: Certification of Proposer Regarding Debarment, Suspension and Other Responsibility Matters” or the “Certification of Proposer Regarding Debarment, Suspension and other Ineligibility and Voluntary Exclusions” ...... 45 EXHIBIT 3: Proposer/Subcontractor Data Form ...... 45 EXHIBIT 4: Resume Form ...... 45 EXHIBIT 5: Summary of Costs ...... 45 EXHIBIT 6: General Requirements Checklist ...... 45 EXHIBIT 7: Proposal Evaluation Rating Sheet ...... 45 EXHIBIT 8: Service Provider Information Security Questionnaire ...... 45

5 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

1.0 General Information Port Authority of Allegheny County (Authority) provides a network of fixed route public transportation services to persons traveling within a 745-square mile area, including the City of Pittsburgh and all of Allegheny County. Operating a fleet of 700 buses, 83 light rail vehicles and the Monongahela Incline, and by sponsoring ACCESS (the nation’s largest paratransit program of its kind for senior citizens and persons with disabilities), Authority is one of the largest and most diversified public transit agencies in the United States. Authority provides bus service on three exclusive busways: the 4.3-mile South Busway; the 9.1-mile Martin Luther King, Jr. East Busway; and the 5-mile West Busway. Authority operates its light rail transit service, known as “the T”, on a 25-mile rail system. In addition, Authority owns and operates four (4) bus operating divisions, a major bus overhaul facility, a light rail vehicle maintenance facility, a light rail transportation control center, and a major service facility that supports maintenance of Authority facilities, properties, Park and Ride lots and rights-of- way.

1.1 Introduction Authority intends to enter into an Agreement, which will provide for a stand-alone Mobile Ticketing Application System (MTAS). The required Contract Services include, but are not limited to: designing, building, operating, maintaining, supporting and improving the MTAS. The Agreement will be for a three (3) year period with the option to extend the term of the Agreement up to an additional two (2) years at the sole discretion of Authority. FOR YOUR INFORMATION: Authority has introduced “ebusiness” at its website, http://ebusiness.portauthority.org, the smartest, fastest, easiest, and most efficient way to deliver and receive information regarding solicitations. All Proposers must register electronically in order to be notified of Authority solicitations and to obtain copies of RFP’s, subsequent addenda and other related information. Complete the bidder registration application with close attention to identifying the Vendor Sourcing Category and Vendor Sourcing Sub-Category to describe your organization’s interests. This RFP, including supporting documents, contains all of the information necessary to prepare and submit a Proposal. Proposers are advised to completely review this RFP and explicitly follow the instructions herein regarding the submission of a Proposal. Each Proposal shall comply with the requirements of this RFP as stated herein and all applicable federal, state and local laws.

1.2 Definitions Throughout this RFP, the following definitions shall apply: ADA: means Americans with Disabilities Act for Public Transportation systems Addendum or Addenda: means an amendment made by Authority, in writing, to the RFP.

Account-Based Ticketing (ABT): means customer, ticket product, and tariff information is stored and processed remotely and may be cloud-based.

Advertisement: means the public announcement requesting Proposals for the Agreement.

AFCS: means Automatic Fare Collection System.

6 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

Agreement: means the contract between Authority and Contractor to perform the Contract Services as set forth in the RFP.

APC: means automatic passenger counting. API: means application program interface, a set of subroutine definitions, communication protocols, and tools for building software ANSI: means American National Standards Institute (Supported by INCITS) Authority: means Port Authority of Allegheny County, 345 Sixth Avenue, Third Floor, Pittsburgh, Pennsylvania 15222-2527, acting by and through its authorized representatives. Authority IT: means Authority’s information technology software department. Beta Program: means an internal test with employees and key stakeholders on limited bus and rail lines prior to an external Pilot Program. ConnectCard: means reloadable plastic stored value smart card with a maximum of $200.00 and Ticket Products. Connectix: means non-reloadable paper Limited Use smart card, available with single-trip ticket product, weekly ticket product or 10-trip passes from any ConnectCard machine. Contractor/Vendor: These two terms may be used as one in the same and represent the: Proposer selected by Authority for award of the Agreement. Contract Services: means the Scope of Services set forth in the RFP and as finalized, through negotiations with the Contractor, and incorporated into the Agreement. CSV (comma-separated values): delimited text file that uses a comma to separate values. Diverse Business (DB): means a diverse business as defined in 74 Pa. C.S. § 303, as may be amended.

DSS: means data security standard Ebusiness: means utilization of web technology to transmit between Authority and vendors, proposers, and contractors’ information for everything from procurement to contract management in the fastest, easiest and most efficient form. Ebusiness can be accessed through http://ebusiness.portauthority.org

EMV: means Europay MasterCard Visa Evaluation Committee: Authority’s staff appointed to evaluate, rank, and recommend all Proposals submitted in accordance with the criteria and methods contained in this RFP. Final Design Review (FDR): means establishes the final design and implementation schedule & Functionality. GTFS: means the General Transit Feed Specification, the common format for public transportation schedules and associated geographic information. Go Live: means the date at which the system goes live. GUI: means graphical user interface. IEC: means International Electrotechnical Commission.

7 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

INCITS: means International Committee for Information Technology Standards. ISO: means International Organization for Standards. Joint Venture: means an association of two or more businesses to carry out a single business enterprise for profit for which they combine their property, capital, efforts, skills and knowledge for the purpose of proposing on an RFP and executing an agreement as a single business entity. Maintenance and Support Services: means performing preventative and remedial services to physically repair and maintain hardware and to provide updates, upgrades and troubleshoot software bugs to provide contract defined availability levels. MMS: The Multimedia Message Service standard extends the core SMS (Short Message Service) capability, allowing the exchange of text messages greater than 160 characters in length. Mobile Ticket App Back Office Web Site: means the web portal used by Authority personnel to obtain, prepare and/or produce reports, ridership data, maintain the MTAS App and update function availability. Mobile Ticketing App Customer Facing Web Portal: means the web portal used by MTAS App customers’ additional application functions and information. Mobile Ticketing App Customer Service Web Portal: means the web portal used by Authority customer service personnel to access customer accounts and to assist with customer questions and concerns. Msec: means milliseconds as in time. MTAS or Mobile Ticketing Application System: means the mobile ticketing application system described in this RFP. MTAS App: means the mobile application provided to Authority Customers to purchase and access Ticket Products through MTAS. NIST: means National Institute of Standards and Technology. NFC: means near field communication. NTP: means Notice to Proceed. OWASP: means Open Web Application Security Project. PCI: means Payment Card Industry. Pilot Program: means a full system test with limited and self-selected individuals (both internal and external to the agency). Preliminary Design Review (PDR): means Program Planning and Information Phase. Project: means the designing, building, operations, maintaining, supporting and improving the MTAS and performing the Contract Services. Project Manager: means the individual proposed by a Proposer, and who will be responsible for the Contractor, to not only oversee the performance of the Contract Services by the Contractor, but also, who will have specific and detailed knowledge regarding Authority’s programs and contracts, and who will have overall responsibility for participating in, overseeing the strategy for, and performing the analysis of, Authority’s programs, plans, contracts and negotiations.

8 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

The Project Manager will be Authority’s direct contact, within the Contractor, regarding the performance of the Contract Services. Proposal: means a hard copy written submission, in response to the RFP, by a Proposer for the Contract Services.

Proposer: means the individual, firm, partnership, corporation, joint venture or other entity, which submits a Proposal to Authority, in response to the RFP, seeking to be selected as the Contractor.

RFP: means this Request for Proposal Number 18-07. Rider Class: means half-fare, full-fare, child-fare, senior, and other classifications Service: means the Contract Services. SMS: means short message service, commonly referred to as a “text message.” System: means the complete MTAS, including, without limitation, the MTAS App, the Mobile Ticketing App Customer Facing Web Portal, the Mobile Ticketing App Customer Service Web Portal, the Mobile Ticket App Back Office web Site and hardware and software provided by the Contractor. System Acceptance: means a status granted the Contractor to initiate the start of the warranty period. TCPA: means Telephone Consumer Protection Act Ticket Products: means each of the transit passes that are available allowing passengers to ride that can be loaded to smart cards and limited use smart cards. Also includes specialty tickets for events/activities bundled with transit passes. Touch Point: means a component such as a tag or beacon point or token that the mobile device makes electrical connection to perform an initial transaction event. UID: means Unique Identifier (Such as a token). VPAT: means Voluntary Product Accessibility Template in conjunction with the Revised 508 standards for IT accessibility (ADA) as explained via https://www.section508.gov/sell/vpat

1.3 Proposal Submission Schedule An Information Meeting for interested parties will be held on the date and time as set forth in the Advertisement. Questions generated at the Information Meeting will be answered, if necessary, in writing by Authority. Attendance is recommended but not required at the Information Meeting. However, Information Meetings will not occur at any time other than the above-designated time. The RFP and any subsequent written addendum serve as the sole basis upon which Proposers may submit Proposals. Hard copy proposals shall be submitted as indicated in the Advertisement and must be both received and time stamped by a representative of the Purchasing and Materials Management Department at or before the time for submission of proposals set forth in the Advertisement. Proposals received or time-stamped by Authority’s Purchasing and Materials Management Department after the advertised time for the submission of proposals shall be non-responsive and therefore ineligible for award and will be returned to the Proposer. Each Proposer shall be

9 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

solely responsible for assuring that its proposal is timely received and time stamped in accordance with the requirements herein.

1.4 RFP as Exclusive Basis for Proposal The RFP represents, in writing to all Proposers, the most comprehensive and definitive statement that Authority is able to make at this time as to the requirements, terms and conditions for this proposal process and performance of Contract Services. The RFP and any subsequent addendum shall serve as the sole basis upon which Proposers may submit Proposals. Proposers are advised to completely review the RFP and explicitly follow the instructions herein regarding the submission of a Proposal and the Scope of Services. Each Proposal shall comply with the requirements of the RFP as stated herein and all applicable federal, state and local laws and shall be executed by an individual legally authorized to bind the Proposer to a contract. Any information or understanding, verbal or written, which is not contained either in the RFP, or in subsequent written addenda to the RFP, shall not be considered by a Proposer in submitting its Proposal. Authority reserves the right to amend the RFP at any time. Any amendments to, or interpretations of, the RFP, shall be described in written addenda. Each addendum will be available for this RFP through ebusiness for all parties. All proposers are responsible for checking ebusiness for any addenda or notifications. Failure of any prospective Proposer to receive the addendum shall not relieve the Proposer from any obligation under its Proposal as submitted or under any requirement of the RFP, as amended by an addendum. All addenda issued shall become part of the RFP. Each Proposer shall acknowledge the receipt of each addendum in its Proposal. Failure to acknowledge receipt of an addendum in a Proposal may, at Authority’s sole option, disqualify the Proposal. If assistance is required to involve Diverse Businesses (DBs) in the Contract Services, Proposers should contact Authority's Director of Employee Relations, Mr. Eric Wells, at (412) 566-5262 or by e-mail at [email protected]. Proposers should contact Authority's Professional Services Contract Specialist, Mrs. Melissa Dunbar, at (412) 566-5286 or email MDunbar @portauthority.org for any procedural questions concerning the RFP. Only written questions or communications for the RFP will be considered for possible response. No telephone solicitations will be honored. If any questions or communications submitted necessitate a response, an addendum will be posted on ebusiness. Only written responses provided as addendum shall be official and all other forms of communications with any director, officer, employee or agent of Authority shall not be binding upon Authority. All questions relating to the RFP must be submitted as follows: Via mail or fax: Office of the Director of Purchasing and Materials Management Port Authority of Allegheny County 345 Sixth Avenue, Third Floor Pittsburgh, PA 15222-2527 Attention: Melissa Dunbar, Professional Services Contract Specialist Fax No.: 412412) 566-52865286 E-mail: [email protected]

10 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

Or via ebusiness for this RFP event. All such questions or communications and requests must be submitted by Proposers and received by Authority no later than 10 days before the due date for Proposals. Questions received after that time may not receive any response from Authority. If it should appear to a prospective Proposer that the performance of the Contract Services, or any matter relating to the RFP, is vague, ambiguous or not sufficiently described or explained in the RFP or the Scope of Services, or that federal, state or local law, ordinance, rule, regulation or other standard or requirement, then the Proposer shall submit a written request for clarification to Authority within the time period specified above.

1.5 Modifications, Deviations and Irregularities Any individual, firm, partnership, corporation, joint venture or other entity able to meet the requirements of the RFP is invited to respond to the RFP. Proposers will be bound by the provisions contained in the RFP, unless a waiver or deviation is formally issued via written addendum by Authority. As part of the process leading to the selection, if any, of the Contractor, Authority may request additions, modifications or clarifications to the Proposal. Authority will rely upon the information submitted in a Proposal if the Agreement is awarded. Authority reserves the right to waive any minor irregularities in any proposal submitted in response to the RFP and/or to reject all proposals, in its sole discretion.

1.6 Conditions, Exceptions, Reservations or Understandings Proposals’ stating conditions, exceptions, reservations or understandings (hereinafter in this paragraph “deviations”) relating to the RFP, including but not limited to proposed deviations to the RFP sample Agreement, may be rejected by Authority, in its sole discretion. Any and all deviations must be explicitly, fully and separately stated in a Proposal, setting forth, at a minimum, the specific reasons for each deviation so that it can be fully considered and, if appropriate, evaluated by Authority. PROPOSED DEVIATIONS MUST BE SET FORTH IN THE PROPOSAL AT THE TIME OF SUBMISSION IN ORDER TO RECEIVE CONSIDERATION. Any deviation found by Authority to be acceptable will be evaluated in accordance with the appropriate evaluation criteria and procedures. The submission of deviations may result in the Proposer receiving a less favorable evaluation than without the deviation.

1.7 Modification or Withdrawal of Proposals A modification of a Proposal already received by Authority will be accepted by Authority only if the modification is submitted by an individual legally authorized to bind the Proposer and received by Authority prior to the due date set forth in the Advertisement for the receipt of Proposals or as made with a requested Best and Final Offer (BAFO). All modifications shall be made in writing and submitted in the same form and manner as the original Proposal. Prior to the due date for Proposals as set forth in the Advertisement, a Proposer may withdraw a Proposal already received by Authority by submitting, in the same manner as the original Proposal to Authority, a written request for withdrawal from an individual legally authorized to bind the Proposer. By submitting a Proposal, and not properly withdrawing it prior to the due date for Proposals, a Proposer agrees that it shall keep its Proposal open and shall not withdraw its Proposal for 180 days.

11 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

This provision may not be utilized by a Proposer as a means to submit a late Proposal and, as such, does not alter Authority’s right to reject a Proposal.

1.8 Form of Contract The sample Agreement, which will be used if the Agreement is awarded, is attached hereto as EXHIBIT 1. Proposers should review the sample Agreement, which includes various requirements for the Contract Services and shall include any of its comments on the sample Agreement as part of its Proposal.

1.9 Contractor Responsibility for Subcontractors The Contractor shall be responsible for management, direction, design integration, scheduling, control, review and approval of all subcontract work and services. Moreover, the Contractor shall be responsible for assuring that all subcontract work is in conformance with the Agreement, Authority's policies, standards and criteria, and all applicable laws. All subcontracts will be subject to the review and approval of Authority. Subcontracts shall include all relevant agreement provisions identified in the Agreement.

1.10 Adverse Interest Law This RFP is subject to the Commonwealth of Pennsylvania Adverse Interest Law, 71 P.S. §776.1 et. seq. This may have implications on future procurements. It is incumbent upon potential Proposers to perform their own determinations on this matter prior to submitting a proposal.

1.11 Pennsylvania’s Right-to-Know Law Upon formalization of an Agreement with a Proposer, all Proposals and other supplemental information submitted in response to this RFP will become public records, as defined by Pennsylvania’s Right-to-Know Law, 65 Pa. Con. Stat. s. 67.101, et seq. (Law), and Authority is subject to this Law. Subject to specific exemptions under the Law, Authority is statutorily obligated to, and indeed will, make available all records deemed public in nature by the Law.

2.0 Proposal Requirements

2.1 General Requirements

2.1.1 Letter of Transmittal/Proposal Requirements Proposals should be submitted with two major components: (1) Letter of Transmittal: One original separate from the bound proposals and a copy bound in each copy of the Proposal. This Letter of Transmittal shall be no greater than two pages in length and shall contain the following: (a) Statement as to the name, title, address, telephone, fax number(s) and e- mail address of the individual(s) with authority to bind the Proposer in contractual matters. The Letter of Transmittal shall be signed by such individual. (b) Statement as to the name, title, address, telephone and e-mail address of the individual to be contacted in the event that the Proposer is selected for an interview.

12 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

(c) Statement as to the address and legal form of the Proposer. If the Proposer is a corporation, the Proposer shall identify its state of incorporation. If a joint venture is being proposed, provide the above information for all participating firms. (d) Statement that includes the following: “This Proposal, and any BAFO, shall remain in effect for and not be withdrawn for 180 days after the due date for the Proposal or the BAFO.” (e) Statement acknowledging receipt of each and every Addendum, by Addendum number and date, that Authority may issue to the RFP. (f) Statement acknowledging that any information provided with or otherwise attached to the Proposal that the Proposer may deem confidential or proprietary in nature may be subject to disclosure under Pennsylvania's Right-to-Know Law. The Proposer shall include the following acknowledgment and release in its Letter of Transmittal: “(Name of Proposer) acknowledges the requirements and potential applicability of the statutory requirements set forth in PENNSYLVANIA'S RIGHT-TO-KNOW LAW, “65 P.S. §§ 67.101 et seq. Accordingly, if the attached Proposal or any other material provided to Authority pursuant to this RFP process contains any reference to material being confidential, proprietary or restricted, in any manner, this Letter of Transmittal officially advises Authority and acknowledges that the stated limitations on such identified material are hereby rescinded and are null and void, to the extent that Authority determines that it is required to disclose such materials pursuant to a valid request for such information.” (2) Proposal Requirements: The Proposal should be a comprehensive, accurate and effective presentation. The Proposal should be in a ring binder or spiral bound along the left long side, without unnecessary frills, fancy bindings or other decorative or extraneous materials. Attachments such as brochures, promotional literature, etc., shall not be included. (a) One original of the Proposal hand signed and nine (9) hard copies of the Proposal shall be submitted. (b) The Proposal shall also include an appendix, which shall be at the end of the proposal document. The appendix shall only contain material, which is explicitly requested to be included in the Appendix. (c) No more than 50 pages, each numbered consecutively at the bottom, shall be contained within the Proposal. The page limit shall not include the Appendix material. Proposals containing more than the stated number of pages may be rejected by Authority. (d) The font size for all material prepared in response to this RFP shall not be less than 10 pt. 8. (e) The Proposal should be contained on 8-1/2” x 11” paper with foldouts from this as may be required.

13 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

(f) The Proposal shall be organized in the following fashion using tabs as numbered separators for each section for the hard copy and, if applicable, identifying page separators for each section for the electronic copy: Cover: Containing RFP title and Proposer's name. Letter of Transmittal: Copy of letter previously described. Table of Contents: Section 1 Overview of Proposer Section 2 Experience Record Section 3 Project Work Plan Section 4 Project Organization and Management Plan Section 5 Summary of Costs / Cost Proposal Appendix The Appendix which shall only contain the materials that are required by the RFP to be included in the Appendix.

2.1.2 Diverse Business (DB) Subcontract Participation DB’s are particularly invited to submit Proposals to perform the Contract Services outlined in the RFP, either as a Proposer of or part of a joint venture. It is the policy of Authority that DBs shall have the maximum opportunity to participate in the performance of contracts and subcontracts, and the Proposer agrees: (1) To make a good faith effort to ensure that DBs have the maximum opportunity to participate in the performance of the Agreement. In this regard, the Proposer shall take all necessary and reasonable steps to ensure that DBs have the maximum opportunity to compete for and perform work for the Contract. The Proposer shall not discriminate on the basis of race, color, creed, age, disability, religion, sex, age or national origin in the award and performance of subcontracts under the Agreement. (2) Failure of the Proposer to carry out the above requirements shall cause the Proposer to be non-responsive and ineligible for award. Following the award of the Agreement, if the Contractor fails to carry out the above requirements, the Contractor shall be in breach of the Agreement which may result in termination of the Agreement by Authority or such other remedy as Authority deems appropriate or as otherwise provided by law and/or in the Agreement. The Proposer shall submit with its Proposal, the following: a) Name and address of DB firms that will participate in the Contract; b) A description of the work that each DB will perform; and c) The anticipated percentage of participation for each DB firm. The Proposer shall perform upon the request of Authority, the following:

14 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

(1) In order to demonstrate that good faith efforts were made by the Proposer to secure DB participation, the Proposer shall submit the following information to Authority when requested: a) The names, addresses and telephone numbers of DBs that were contacted; b) A description of the information provided to DBs regarding Contract Services to be performed; and c) A statement of why additional agreements with DBs were not reached. (2) The Proposer shall make a good faith effort to assist the DBs contacted that need assistance in obtaining lines of credit and insurance. (3) The Proposer/Contractor shall make a good faith effort to replace a DB subcontractor with another DB. The good faith effort shall be directed at finding another DB to perform, at least, the same amount of work for the Agreement as the DB that was terminated. (4) The Contractor shall make a good faith effort to provide DB subcontractors with the opportunity to perform work added to the Agreement. (5) The Contractor shall be required to make a good faith effort to identify additional opportunities for DB participation, if work, which the Contractor originally intended to have performed by a DB, is reduced or eliminated as a result of an Agreement change. The Proposer/Contractor shall meet with Authority at Authority’s request to discuss the DB plan. The purpose of the meeting is to consider whether the DB commitment of the Proposer/Contractor is in compliance with the Agreement. At the meeting, the Proposer/Contractor will have an opportunity to present information pertinent to its compliance with the applicable requirements.

2.2 Overview of Proposer This section shall contain the following information, unless otherwise specifically noted. Proposer shall include the required information in this section in the “Overview of Proposer” section of its Proposal.

2.2.1 Description of Proposer A concise description of the Proposer including organizational structure, subsidiary companies, identification of principals or parent companies, length of time in business, office locations and size and overall number of personnel by discipline. If the Proposer is a joint venture, the Proposer shall furnish this information for each entity forming the joint venture and clearly indicate the reason for the joint venture as it directly applies to this Project. Proposer shall also provide a general overview description of its proposed subcontractors.

2.2.2 Agent A requirement of the Agreement is that the Contractor shall maintain, during the duration of the Agreement, an agent in Allegheny County, Pennsylvania authorized to accept notice and service of process on behalf of the Contractor and the Proposer shall so acknowledge and agree.

15 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

2.2.3 Contractor/Subcontractor Percentage of Work The Proposer shall provide, in its Proposal, a statement as to the percentage of work that will be performed by the Proposer. The Proposer shall identify all of its proposed subcontractors (including but not limited to hosting providers) in its Proposal, and must identify a) the tasks they will perform, b) the percentage of the work to be performed by each subcontractor, c) their qualifications to perform the work, and d) the reason the tasks are to be subcontracted.

2.2.4 Joint Venture If the Proposer is a Joint Venture, the Proposer shall include a copy of any written contract or agreement, which exists between the entities forming the joint venture in the Appendix.

2.2.5 Personnel and Operations Policies A statement of the Proposer's personnel and operations policies relative to:

(a) Classifications of personnel normally billed directly to client including wage ranges (or rates) by discipline. If rates by discipline are used for billing purposes, provide an explanation as to the basis by which the rates are established.

(b) Expenses normally billed directly to the client such as per diem rates, mileage rates, computer, reproduction and communication charges.

(c) Current overhead rate (if billings are made on a cost basis) including its components and identification of the most recently performed external and annual audit report.

(d) If the Proposer utilizes an option in addition to, or other than, an hourly fee structure, Proposer shall note what personnel or operations policies will not be affected by the alternative fee structure (such as mileage rates, reproductions costs, etc.)

2.3 Experience Record This section shall contain the following information, unless otherwise specifically noted. Proposer shall include the required information in this section in the “Experience Record” section of its Proposal. Proposer shall provide complete, concise and accurate descriptions of the Proposer's and its subcontractors experience in providing services similar to those as outlined in Section 4 of this RFP, the Scope of Services. Particular emphasis should be placed on those projects and services performed by Proposer's and its proposed subcontractors’ offices, employees and staff to be assigned to the Project. The Proposer’s actual role on the identified projects, or in performing the services, shall be clearly described. The Proposer's and its proposed subcontractors’ qualifications and ability to perform all identified Contract Services should be clearly discussed. The Experience Record, as defined in Section 3.2 herein below, should include three (3) references of relevant work directly applicable to the Contract Services, and should be contract specific and include the following: (a) Contact name, contract title, address, telephone number and e-mail address of the client's project manager or contracting officer;

16 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

(b) The status of the contract or services and of the Proposer's or its proposed subcontractors’ work on the contract or services; (c) The Proposer's and its proposed subcontractors’ specific involvement in the contract or services; (d) The Proposer's or its proposed subcontractors’ project manager and staff on the identified projects that will be used, by Proposer or its proposed subcontractors, to support or perform the Contract Services; and (e) The contract value of the identified projects and the Proposer's or its proposed subcontractors’ percentage of the work for the projects. (f) The speed of which the contract was executed to when the mobile application was fully deployed. (g) Number of clients that have activated mobile ticketing applications Authority may contact any or all firms listed in Section 2.3 regarding the quality of work, timeliness of work and general overall services provided by Proposer. Authority furthermore reserves the right to contact other clients of Proposer not listed in the Proposal for additional information on the Proposer’s past experience and performance. If the Proposer is a joint venture, furnish the above information for each entity forming the joint venture and specifically note any contract previously worked on by each entity forming the joint venture as a team, providing client references and telephone numbers.

2.4 Project Work Plan This section shall contain the following information, unless otherwise specifically noted. Proposer shall include the required information in this section in the “Project Work Plan” section of its Proposal.

2.4.1 Methodology Proposer shall identify its plan and methodology for the performance of the tasks identified under Section 4. The Project Work Plan, as defined in Section 3.2 herein below, should include a detailed description of the methodology for accomplishing required work tasks and their interrelationships. Any substantive and/or procedural innovations used by the Proposer on similar projects that are applicable or can be tailored to the Contract Services should also be identified. The work tasks to be wholly or partially performed by subcontractors, particularly DB subcontractors, should be identified in the Project Work Plan. If the Proposer is a joint venture, please describe the work tasks to be performed by each firm.

2.4.2 Flow Chart This Work Plan shall include a flow chart which explains the sequencing and interrelationships of the work tasks graphically for all work tasks on the Project. The Work Plan flow chart shall be keyed to time and the work tasks outlined in Section 4.

17 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

2.5 Project Organization and Management Plan This section shall contain the following information, unless otherwise specifically noted. Proposer shall include the required information in this section in the “Project Organization and Management Plan” section of its Proposal.

2.5.1 Description of Organization and Management Plan A detailed description of the Proposer's Organization and Management Plan, which shall be established to perform the Contract Services. The Organization and Management Plan shall clearly identify the Proposer’s proposed Project Manager and key personnel associated with each work task and for the entire period covered by the Agreement. The plan shall also describe the involvement of DB subcontractors in the Project. If the Proposer is a joint venture, the company or firm affiliation of each staff member must be identified.

2.5.2 Project Organizational Chart/Resumes A Project Organizational Chart shall be furnished which graphically depicts the above “Project Organization and Management Plan”. The proposed Project Manager and all other key personnel identified for this Project shall be identified on the Project Organizational Chart and further on an individual Staff Résumé form, a copy of which follows as EXHIBIT 4 (identifies minimum information required on Staff Résumés for each proposed individual). Each Staff Résumé form shall be complete, concise and accurate, featuring all relevant job experience over the past 10 years. The Proposer may provide more than one Résumé per page in its Proposal. The Proposer shall include the required Résumés in this section in the Appendix. Résumés shall not exceed a total of 20 pages.

2.5.3 Key Personnel Guarantee A Key Personnel guarantee letter signed by the Proposer's President, Chief Executive Officer or Chief Operations Officer guaranteeing that the Project Manager and key personnel identified for this Project shall be assigned to the Contract Services, throughout the term of the Agreement, unless their employment is terminated. If applicable, a key personnel guarantee letter signed by the Subcontractor’s President, Chief Executive Officer or Chief Operations Officer guaranteeing that the key personnel identified for this Project shall be assigned to the Contract Services, throughout the term of the Agreement, unless their employment is terminated. Proposer and its subcontractor(s) shall identify the key personnel by name and proposed position for this Project in its key personnel guarantee letter. Proposer shall include the required key personnel guarantee letter(s) requested in this section in the Appendix.

2.5.4 Certification/License Requirements The Proposer shall include any applicable certifications/licenses of its key staff or suppliers such as security and payment card industry certifications.

18 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

2.6 Summary of Costs This section shall contain the following information, unless otherwise specifically noted. Proposer shall include the required information in this section in the “Summary of Costs” section of its Proposal. The Summary of Costs shall be furnished utilizing the sample form(s), which follows as EXHIBIT 5. This Summary of Costs shall be keyed to the required Project work tasks. Work to be wholly or partially performed by subcontractors should be so identified.

2.6.1 The Summary of Costs Development. The Summary of Costs must be developed as follows: a. Design and Implementation Cost The Proposer must set forth all costs for the design and implementation of the MTAS (total costs payable per the defined milestone payments). Payment for services completed for the design and implementation portion of the Contract Services shall be based on successful and satisfactory completion of the “milestones.” b. Recurring fixed monthly/annual cost (operations, customer service, maintenance, warranty, licensing, design updates and fixes, etc.) The recurring fixed monthly and/or annual costs for the operation, customer service, licensing, design updates and fixes of the complete MTAS System shall remain the same for the entire three-year term, unless modifications and/or enhancements to the System have been made and both parties agree to the new terms, conditions and costs. c. Operational transaction fees and/or requested revenue per transaction fees. . Note that “free” fare products, such as for senior citizens, are exempt from payment or fees for use of the MTAS. . Note that transactional fees shall be subject to negotiated fare capping or leveling targets. The Authority is aware that Proposers may have a variety of financial models that they may wish to propose for a project of this type. In order to align Proposals with the Authority’s expectations, all Proposals must show the total cost of implementation and ongoing operational use of the MTAS. Proposers may also discuss in their Proposals alternative methodology for compensation for the MTAS App usage such as the following: 1. Implementation costs with a one-time lump sum transaction fee payment and per transaction fees. 2. No Implementation costs with per transaction fees only that covers all compensation. 3. Implementation costs with per transaction fees including annual/monthly lump sum payments.

Within the Summary of Costs, the Proposer shall also list items for consideration by Authority that will result in a cost reduction for the Contract Services. Such

19 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

items should be of the type that would result in a reduced cost while maintaining the required level of quality without reducing the functionality of the services being requested. Items proposed may include, but not be limited to, risk mitigation, alternative payment plans, variations to warranties or other items.

The Contractor shall be solely liable for the payment of all sales, international, federal, state, local or other taxes and duties applicable to the completion of the Contract Services.

2.6.2 Anticipated Term of Agreement The term of the Agreement for the Service is anticipated to be three years with an addition two-year option period.

2.6.3 Thresholds The Authority shall not be responsible for ensuring any minimum sales or use volume associated with the MTAS . However, to evaluate all Proposals using the same ridership data, Authority requires Proposers to utilize the ridership report data provided below. Proposers are to assume a fixed level of effort (LOE) through the rollout of the MTAS App, as the baseline assumption. If there is no off-the-shelf solution to fulfill the requirements, then the LOE will need to reflect an assumption of an agile approach to development and implementation. Proposers should also note the requirement that the App shall be downloadable at no cost to the public. Fare Products Sold Annually

Ticket Vending Retail Unit Cost Product Machine Service Center Partner Web Total ($) Total Cost ($) 10 trip FF 21,397 0 0 0 21,397 $25.00 $534,925.00 10 trip half fare 70 8 17 44 139 12.50 1,737.50 Annual 0 359 0 51 410 1,072.50 439,725.00 Day Pass 108,858 98 0 0 108,956 7.00 762,692.00 Full Fare single trip 435,346 0 0 0 435,346 2.50 1,088,365.00 Full fare single trip with Xfer 268,036 0 0 0 268,036 3.50 938,126.00 Monthly Pass FF 35,369 16,888 8,427 17,447 78,131 97.50 7,617,772.50 Monthly Pass HF 1,230 2,720 774 305 5,029 48.75 245,163.75 Weekly Pass FF 222,203 23,184 87,858 11,347 344,592 25.00 8,614,800.00 Weekly Pass HF 3,822 1,786 1,413 171 7,192 $12.50 89,900.00 $20,333,206.75

20 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

Fare Products Sold Annually via Corporate Web Services Product Units Total Value ($)

10 trip FF 0 $0.00 10 trip half fare 0 0 Annual 0 0 Day Pass 0 0 Full Fare single trip 104,123 260,307.50 Full fare single trip with Xfer 199,490 698,215.00 Monthly Pass FF 66,042 6,439,095.00 Monthly Pass HF 738 18,450.00 Weekly Pass FF 0 0 Weekly Pass HF 0 0 $7,416,067.50

2.7 Appendix This section shall contain the following information, unless otherwise specifically noted. Proposer shall include the required information in this section in the “Appendix” section of its Proposal.

2.7.1 Service Provider Security Information Questionnaire The Proposer is required to complete the questionnaire provided in EXHIBIT 8.

2.7.2 Financial Information The Proposer will be required to present, in sufficient detail to Authority, financial records for Authority to review the financial condition of the Proposer, in order for Proposer to be considered eligible for award of the Agreement with Authority for the required services. Any financial information presented shall be prepared in accordance with United States Generally Accepted Accounting Principles (G.A.A.P.). If the Proposer is a publicly-held firm, the financial information of the Proposer shall be included in its Proposal (separate statements for each entity forming a joint venture). If the Proposer is a privately-held firm, the Proposer may either provide its financial records with its Proposal (separate statements for each entity forming a joint venture), or it may defer making such financial records available for inspection by Authority until after Authority has informed the Proposer that it has been short-listed for consideration for award of an Agreement.

2.7.2.1 Financial Statements For either publicly-held or privately-held firms, the financial information to be provided shall include, if available: (a) Independently Audited Financial Statements Independently audited financial statement (either a certified audit or review) that includes a balance sheet, statement of income and expenses (profit and loss), and statement of cash flows for the two most recently completed financial years, including notes to the statements; For privately held companies, if independently audited financial statements are not available, then

21 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

(b) Financial Statements Not Independently Audited If not independently audited, then either: (i) a compilation of financial statements performed by an independent accountant that includes a balance sheet, statement of income and expenses (profit and loss), and statement of cash flows for the two most recently completed financial years. If such statements are not available, then: (ii) an internally prepared financial statement, including a balance sheet and statement of income and expenses (profit and loss) for the two most recently completed financial years, certified as true and correct by the president and chief financial officer of the Proposer, in either case, to include credit references or other financial documentation as may be required in order to portray the financial soundness of the Proposer to Authority’s satisfaction. In addition, the Proposer must certify in writing that there have been no material changes in the company's financial condition or events that could have a material impact on the company's financial condition subsequent to the last audit or date of reporting period on the financial statements. Any such changes in financial condition or subsequent events must be fully disclosed in writing and signed by the president and chief financial officer.

2.7.2.2 Exceptions for Privately-Held Firms (a) For a privately held firm, which elects to not include its financial records with its Proposal, such Proposer will be required to submit financial records as specified above, within three business days of being requested to do so by Authority. (b) If Proposer is not willing to permit copies of such financial records to be retained by Authority, the Proposer will be required to attend a meeting, to be scheduled at the convenience of Authority, to enable Authority to review said financial records. Proposer agrees that Authority may document, for Authority records, its review and assessment of Proposer’s financial condition and such financial records, including, without limitation, taking notes about data contained in the financial records relative to Authority’s review. (c) In the event that the Proposer does not have any cash flow documentation for preceding years of operation, Authority will accept current bank references (including a bank contact name and contact details) in lieu of a cash flow statement. (d) In cases where independently audited financial statements are not presented, then signed copies of the Proposer’s Federal Income Tax filings, including all applicable schedules pertinent to the Proposer’s filing return, are required to be submitted along with the compilation or internally prepared statements.

22 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

2.7.3 Certification of Proposer Regarding Debarment The “Certification of Proposer Regarding Debarment, Suspension and Other Responsibility Matters” or the “Certification of Proposer Regarding Debarment, Suspension and other Ineligibility and Voluntary Exclusions”, whichever is appropriate, for the Proposer (EXHIBIT 2). A Proposal which does not include the required Certification may be considered non- responsive and ineligible for award of the Agreement.

2.7.4 Proposer/Subcontractor Data Form Proposer/Subcontractor Data Form the “Proposer/Subcontractor Data Form” (EXHIBIT 3) for Proposer and all its subcontractors.

2.7.5 Resumes See Section 2.5.2 of the RFP.

2.7.6 Key Personnel Guarantee See Section 2.5.3 of the RFP.

2.7.7 Affirmative Action and Equal Opportunity Policy The Proposer's corporate Affirmative Action and Equal Opportunity policy statement posting, when required by law. The posting shall be signed and dated and shall state the original date of adoption of this policy statement.

2.7.8 Insurance Requirements A statement that includes the following: “The insurance coverage, as required by Exhibit 1 of the sample Agreement, can be obtained and will be carried without reservation or exclusion should (Name of Proposer) be awarded an agreement according to the RFP”.

2.7.9 Joint Venture Requirements If the Proposer is a joint venture, the Proposer shall include a written statement explaining how the joint venture will fulfill the requirements of the Agreement which explanation shall fully set forth and identify the responsibility of each entity forming the joint venture for performing the Contract Services and providing the insurance required by the Agreement.

3.0 Proposal Selection Process Proposals will be evaluated, negotiated, selected and any award made in accordance with the criteria and procedures described below. The approach and procedures are those, which are applicable to a competitively negotiated procurement whereby proposals are evaluated to determine which Proposal, if any, is most advantageous to Authority. Discussions and negotiations may then be carried out with Proposers determined to be reasonably susceptible of being selected for award of the Agreement after which BAFOs may be requested. Authority, however, may select a Proposal for award without any discussions or negotiations or request for any BAFOs. Subject to Authority’s right to reject and or all Proposals, the Proposer, if any, will be selected whose Proposal is found to be most advantageous to Authority, based upon consideration of the criteria discussed below.

23 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

3.1 Evaluation Committee Authority will establish an Evaluation Committee for the RFP. The Evaluation Committee will initially determine the responsiveness of each Proposal, evaluate all Proposals, determine the responsibility of each Proposer, score the Proposals, conduct meetings and assist in selecting the Proposer, if any, that may be awarded the Agreement.

3.2 Proposal Evaluation Criteria The following is the criteria by which Proposals from responsible Proposers will be reviewed and evaluated for purposes of determining which is most advantageous for Authority and to make any selection of a Proposal for potential award of the Agreement. Any exceptions, conditions, reservations or understanding explicitly, fully and separately stated as a Proposal deviation and which does not cause Authority to reject a Proposal will be evaluated according to the evaluation criteria and/or sub criteria, which they affect. The criteria, and their respective definitions, to be used in reviewing and evaluating the Proposals and used to establish a score for the Proposals is as follows: (1) DB Utilization: Each Proposal will be evaluated based upon the proposed use of DBs by the Proposer. (2) Experience Record and References: The following, as well as the other information identified in Subsection 2.3 to be supplied by the Proposer will be used to evaluate each Proposer’s experience and qualifications to perform the Contract Services. (a) Sufficient financial strength and resources to finance the Contract Services and complete the Agreement in a satisfactory and timely manner as measured by the Proposer’s supplied financial statement. (b) Evidence that the Proposer has human and physical resources sufficient to perform the Agreement within the time specified. (c) Evidence of a satisfactory experience, performance and integrity on similar contracts and meeting specifications and warranty provisions. (d) Evidence of sufficient capabilities to perform the Agreement, which will include the Proposer’s size, the Proposer’s commitment to further work of this nature, and the Proposer’s ability to bring adequate people to staff the Agreement. (3) Project Work Plan/Concept/Ease of Use: The Proposal will be evaluated based on the Proposer’s proposed approach to perform the Agreement, proposed schedule and proposed quality assurance and training plans and project team, as well as the other information identified in Section 2.4 to be supplied by the Proposer. (4) Project Organization/Management Plan: The Proposal will be evaluated based on the experience and background of the proposed personnel as well as the other information identified in Section 2.5 to be supplied by the Proposer. (5) Project Manager/Staff Resumes: The Proposal will be evaluated based on the experience and background of the proposed Project Manager(s) as well as the other information identified in Section 2.5 to be supplied by the Proposer. (6) Speed to Deploy: The proposal will be evaluated based on the Proposer’s ability to complete the MTAS and install any required hardware to start the internal test, pilot test and complete the full launch of the MTAS.

24 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

(7) Summary of Costs: The Proposal will be evaluated based on the information submitted as part of the Summary of Costs as identified in Section 2.6 The information submitted for each criterion will be scored on a scale of zero to ten. The score for the various criteria will then be multiplied by the weighted factors set forth for the criteria on the Proposal Evaluation Rating Sheet (EXHIBIT 7).

3.3 Evaluation Procedures (1) Proposals will be reviewed for complete conformance with the instructions and requirements of the RFP. Proposals that do not comply with the referenced instructions and requirements and do not include the required information may be rejected as insufficient and will not be further considered. Authority reserves the right to request a Proposer to provide any missing information and make corrections. Submittal of a Proposal shall signify that the Proposer has accepted the whole of the Agreement, except such conditions, exceptions, reservations and understanding explicitly, fully and separately stated in the Proposal. Such conditions, exceptions, reservations or understanding which do not result in the rejection of a Proposal are subject to evaluation under the criteria set forth in Section 3.2. (2) Authority will select for award, if any, the highest ranked Proposal from a responsible Proposer, qualified pursuant to the RFP, which does not render the procurement financially infeasible and is determined to be the most advantageous to Port Authority based upon consideration of the Proposal and the evaluation criteria set forth in Section 3.2. (3) The following will be the steps for reviewing and evaluating the Proposals: (a) Proposals will not be publicly opened. All Proposals and evaluations will be kept confidential throughout the evaluation, negotiation and selection process, until award, if any, of the Agreement. (b) Proposals will be reviewed and evaluated by Authority’s Evaluation Committee to determine the responsiveness of a Proposal to the requirements of the RFPs and the responsibility of a Proposer. Any Proposals found not to be responsible, will not be further considered for award of the Agreement. Final determination of the responsiveness of a Proposal will be made upon the basis of the Proposal. Final determination of a Proposer’s responsibility will be made on the basis of the Proposal, any information submitted upon Authority’s request, information submitted in a BAFO, information resulting from Authority’s inquiry of Proposer’s references and Authority’s knowledge and investigation of the Proposer. Authority’s determination in regard to the responsiveness of a Proposal and the responsibility of a Proposer shall be final and binding on the Proposer. (c) Each Proposal from a responsible Proposer found to be in compliance with the RFP requirements will be evaluated in accordance with the criteria set forth in Section 3.2. Each Proposal will be examined by Authority's Evaluation Committee for compliance with the stated requirements in Section 2 and as outlined in EXHIBIT 6. The evaluation will be undertaken (Preliminary Rating) utilizing the Proposal Evaluation Rating Sheet (EXHIBIT 7). (d) After the Preliminary Rating, the responsible Proposers whose Proposals are determined by Authority to still be reasonably susceptible of being selected for award of the

25 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

Agreement may be requested by Authority to respond, in writing, to certain questions. Each such Proposer may also be invited for a private interview and discussion with Authority to discuss answers to written or oral questions, to assure responsiveness of its Proposal and to discuss its Proposal. In the event that any such Proposal contains conditions, exceptions, reservations or understandings to any requirements of the Agreement, said conditions, exceptions, reservations or understandings may be discussed during these meetings. Authority, however, shall have the right to reject any and all conditions, exceptions, reservations and/or understandings. Any Proposer failing to do so may cause Authority to reject such Proposal. (e) After any interviews have been completed, each responsible Proposer whose Proposal is determined to still be reasonably susceptible of being selected for award of the Agreement may be afforded the opportunity to amend its Proposal and make a BAFO. The request for BAFOs, if any, will include: (i) Notice that all prior discussions and negotiations are to be included in the BAFO; (ii) Notice of any changes to the RFP; (iii) Notice that this is the opportunity for submission of a BAFO; (iv) A common date and time for submission of written BAFOs; (v) Notice that is any modification to a BAFO is submitted, it must be received by the date and time specified for the receipt of BAFOs and is subject to the late submissions, modifications and withdrawals of Proposals provisions of the RFP; and (vi) Notice that if a Proposer does not submit a BAFO, Authority may consider its Proposal non-responsive and ineligible for award of the Agreement. Any modifications to the initial Proposal made by a Proposer in its BAFO shall be expressly modified in its BAFO. BAFOs will be evaluated by Authority according to the procedures, requirements and criteria set forth in Section 3.2 (Final Rating). Authority will make the appropriate adjustments to the initial scores for each criteria, which has been affected by any Proposal modifications made by the BAFOs. Authority will then choose for potential award of the Agreement, the Proposer, if any, whose Proposal Authority finds to be most advantageous to Authority based upon the evaluation criteria.

3.4 Finalization of Agreement Authority will meet, as necessary, to finalize the proposed Agreement with the responsible Proposer, which submits the Proposal, which is determined to be most advantageous to Authority based upon the evaluation criteria. In the event that Authority cannot finalize a satisfactory Agreement with the highest rated responsible Proposer, discussions will be terminated with that Proposer and Authority may then proceed with meetings to finalize the proposed Agreement with the next highest rated Proposer. The above process may continue until a satisfactory contractual arrangement with a Proposer has been reached. Also, a responsible Proposer may be requested to submit a copy of the Proposer’s EEO Policy and Program and EEO-1 form for the current and previous year.

26 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

3.5 Contract Award The proposed Agreement resulting from discussions described in Section 3.4 will be ultimately presented to the Chief Executive Officer of Authority for review and recommendation to Authority's Board for approval. Authority's staff is not empowered to enter into a contract without the formal authorization of Authority’s Board.

3.6 Failure to Execute a Contract Failure of the Proposer to whom the Agreement is awarded to promptly execute the Agreement shall be cause for cancellation of the award. The Proposer, by submitting a Proposal, agrees to, and shall, reimburse Authority for all damages arising from said default.

3.7 Acceptance / Rejection of Proposers Authority reserves the right to reject any or all Proposals. Authority also reserves the right to make an award to a Proposer whose Proposal it judges to be most advantageous to Authority, without conducting any written or oral discussions with any Proposer or the solicitation of any BAFOs. Authority reserves the right to consider any specific Proposal which is conditional or not prepared in accordance with the instructions or requirements of this RFP to be non-responsive. Authority reserves the right to waive any defects, or minor informalities or irregularities in any Proposal, which, in Authority’s sole discretion, has not materially affected the Proposal.

3.8 Cancellation of Procurement Authority reserves the right to cancel the procurement and not award the Agreement for any reason whatsoever, at any time, before the Agreement is fully executed and approved on behalf of Authority.

3.9 Authority Protest Procedures Any actual or prospective Proposer who is aggrieved in connection with the solicitation or award of the Agreement may file a protest with Authority. The procedures for submitting such protests are available at Authority’s website at www.portauthority.org by following the links “Company Info & Projects”, “Doing Business”, “Procurement”, “Purchasing Information,” and “Bid Protest Procedures.”

4.0 Scope of Services

4.1 General Information The Contract Services consist of furnishing Authority with a fully implemented, managed and hosted account-based MTAS (also referred to herein as the “Service”). The MTAS will include a mobile application as well as a Web site for customer and Authority account management. The solution will be designed, built, operated and maintained by the Contractor. Direct integration into the current fare collection system is not required but data from the MTAS App will need to be joined with the fare collection data and added to the ridership database maintained by Authority IT. The MTAS App will provide Authority customers with the ability to buy and validate Ticket Products. The Service shall also provide the Authority with a MTAS App back office Web site with secure access to ridership data, customer usage data, Ticket Product sales, customer account

27 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

information and system status and performance information. The Web site shall allow the Authority to assign a customer class to a specific account and device, enabling restricted, reduced fare ticket product to be purchased by that user. The Service shall be scalable and able to incorporate new technologies to improve fare collection, trip planning, wayfinding, customer service and customer satisfaction. The Service includes design, development, testing, implementation, operation, maintenance and, support required for a turn-key mobile ticketing app. Specifically, the Service shall include, but not be limited to, setting up accounts by the customers, purchasing and completing payment, validation of purchased Ticket Product, review of purchases and Ticket Product use through the MTAS App. The MTAS App shall provide Authority’s customer service the ability to see the customer’s purchases, Ticket Product usage, and account data though a web portal for trouble shooting complaints and allow Customer Service to remedy issues by loading or unloading fare products to the app. The Contractor shall work with the Authority to identify the information and reports needed for ridership reporting. The Mobile Ticket App Back Office Website shall provide this information based on written, agreed upon criteria. The Authority will provide trip and route information needed by the provider to extract the ridership data. The Contractor shall also provide customer data such as the locations of the boarding and exiting vehicles and stations. The MTAS shall provide the necessary validation features so that it can work on bus boarding and in a cashless, proof of payment bus and/or rail system, with paid zones on high platform stations and boarding at street level. A solution to validate a Ticket Product by an attendant at high traffic bus stations shall be included but will not be required at the time of the full launch of the MTAS App. The Service will be operational and functional 24 hours per day, 7 days per week and 365 days per year. The Authority has approximately 700 buses, 84 rail vehicles, 2 inclines and up to 75 off-board validators at 25 platform locations. Seventeen (17) current off board locations with 24 validators currently exist.

4.2 Regional Systems The Authority has five regional partners, Butler Transit Authority, Fayette Area Coordinated Transit, Mid Mon Valley Transit Authority, Freedom Transit Authority (Washington City) and Westmoreland County Transit Authority. The individual regional partners may execute a separate agreement with the Contractor. The apps shall be kept separate for each agency and settlement for product sales and any associated fees shall be settled individually with each regional partner. MTAS App shall know the region that the App user is located when using the mobile App to purchase and activate ticket products. The MTAS App should default to the transit agency for the location detected. The user shall have the ability to change to a partner agency to buy additional passes if needed. Any location within Allegheny County shall default to the Authority when buying or activating a Ticket Product.

4.3 Technical Requirements The MTAS shall be an account-based mobile ticketing fare system incorporating at least two fare validation methods, fare validation equipment as needed, web-based customer portal, Mobile Ticket Back Office Web Site and any additional software and communication devices required for the MTAS to fully function. The MTAS back office shall provide Authority’s customer service

28 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

personnel the information required to allow complete investigation for customer complaints and allow for reconciliation of those complaints. The price provided in the quote shall include support for the Authority and to report MTAS issues and errors for remediation. The Contractor shall work with Authority to implement the MTAS to be compatible with the current AFC system but can remain as a standalone system. Any hardware that would need to be mounted to the farebox or validators would need to be done using existing and open mounting holes or brackets and not interfere with moving parts within the equipment. The Contractor shall provide: 1. All MTAS configurations, application software, system hardware and set up, MTAS App back office Web site with unlimited license use for Customer Service uses as applicable, training and support costs related to the MTAS. This includes but is not limited to any third-party costs associated with the MTAS hardware and software, integration, implementation, routine maintenance and issue resolution, pass purchases and day-to- day functionality. The Proposal must identify any equipment installation actions required by the Authority. See following sections for output needs. 2. Spare parts to the Authority that can be swapped out for defective of failed units in a quantity to not disrupt service during and part exchanges that would take place. 3. MTAS compatible with all supported versions of iOS and Android. 4. MTAS shall be able to validate Ticket Product use if Wi-Fi or cellular data is temporarily not available. Data transmission shall be sent to the MTAS App back office web site once communications are re-established. 5. Any necessary open source and open standards documents needed to incorporate the mobile application into other mobile applications to allow pass purchases to appear near seamless. 6. Option for operator display to show fare validation of Ticket Product. 7. Options for integration with various other transportation provided services such as Pittsburgh Bike Share and other ride share services. 8. A receipt via email or text to the user for the Ticket Products purchased through the MTAS. 9. The Authority’s customer service phone number that can be touched to dial if the user has questions or requires help. All personal and customer data collected by the Contractor shall belong to the Authority. The Contractor shall have no claim, right, title or interest to or in the data collected and has no right to use, assign or sell the data without explicit written consent of the Authority.

4.4 Functional Requirements The MTAS shall include, but not be limited to the following functions and features:

4.4.1 Set Up and Account Management 1. MTAS shall enable customers to set up an account through the app.

29 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

2. The MTAS App shall update relevant settings (i.e., screen brightness, audio levels), based on the capabilities of the mobile device platform, when the mobile ticketing App is opened. The terms, conditions and licensing requirements shall contain the approval of the mobile device user upon setup of the account. Should the customer disable a needed mobile function before or after opening the app, the app shall warn the customer that the function needs to be active to use the MTAS App. The MTAS App shall not allow a user to choose or activate Ticket Products to validate if required services are disabled. 3. Authority shall be able to assign customer classes to accounts, enabling qualified customers to purchase full and reduced fare Ticket Products or receive a senior pass.

4.4.2 Purchases 1. Ability to purchase and send Ticket Products between customers using text messages and other delivery vehicles, through the MTAS App or Mobile Ticket App Customer Web Site, in compliance with the TCPA. 2. The ability for tickets to be sent to a customer by the Authority using text messages and other delivery vehicles, through the app or Mobile Ticket App back office Web site. Text messaging shall comply with TCPA laws, rules and regulations. 3. The MTAS App and Ticket Product purchase mechanisms shall be user-friendly allowing users to intuitively purchase, use and to interact with all customer facing end devices. 4. The MTAS shall allow the Authority to add passes for special events through the MTAS. Those tickets shall be available for immediate validation on end devices. 5. The MTAS shall provide customers with all of the fare products and fare policy rules available in the current AFC system. See products in section 2.6. 6. The Contractor and Authority shall have the ability to update the Services to reflect changing prices and fare policies and new Ticket Products without additional charges to the Authority. 7. The MTAS shall provide the customer with a receipt for Ticket Products purchased through the app and on the website.

4.4.3 Transit Pass Programs and Additional Functions The MTAS App shall provide various pass program options to the Authority for implementation during the contract period. As new Ticket Products are developed, they shall be available as an option for the Authority to implement if so desired. The transit pass programs as Ticket Products available through the MTAS App should include:

1. University Pass – For use by an institution to manage passes for students to ride. Access to the pass can be turned off individually by the university. Billing based on a per ride basis can be completed. 2. Employer Pass – An employer can be given an account and manage passes for their employees. Sales transactions are completed through the various payment options offered by the app provider or invoiced by the agency. 3. Social Services – Social service agency can send a pass to their customer and an invoice generated by the agency for billing purposes.

30 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

Promotional passes should be available as Ticket Products for the Authority to send free passes to riders’ mobile devices. This should be able to be completed through a batch list as to avoid sending out individual passes one at a time to a mobile device.

The MTAS App should also have the ability for third party retail partners to sell mobile tickets at their store, allowing cash customers to buy a Ticket Product. Discount code use through the MTAS App should also be available for riders. These functions are not a requirement for the full launch, but shall be available within one year from a contract execution.

The Authority has a partnership with Pittsburgh Bike Share that allows ConnectCard holders to tap their Card on the rental kiosk to obtain a free 15 minutes use of the bike for free. The Contractor shall meet with the bike share provider and the Authority to review how this can be accommodated as Ticket Products through the MTAS App.

4.4.4 Validation and Cancellation 1. MTAS must allow customers to validate Ticket Products quickly and easily, provide clear usage and validation messages to fare inspectors and access expired Ticket Product use information. 2. The ability for the customer to choose free children rides while validating a full fare, half fare or senior pass. The free children ridership shall be recorded with the pass use in a single validation. This functionality shall be available for the full public launch of the MTAS App. 3. The ability to validate a Ticket Product purchased in the MTAS App in the proximity of fareboxes and high platform validators, although there does not need to be any integration with these AFC devices. 4. The ability for a fare inspector to visually see that a Ticket Product was validated, along with usage data that includes date, time, vehicle/station number, Ticket Products types and multiple validations from a single screen, without the use of a hand held validator. 5. The MTAS App shall include a countdown timer once validated, and a way to verify that the validated screen is not just a screen shot or video. 6. Email, MMS, or SMS text receipt sent to the customer (as a customer-selected option) upon completing the pass purchase. 7. The ability to validate mobile passes using either Bluetooth and/or NFC technology. 8. The app or hardware shall provide visual and audio cues during the validation in the proximity of the farebox and validator. 9. An external screen that can be mounted or located at or near the farebox operator screen, to show the validation of a Ticket Product, bust be available for the full public launch of the MTAS App. 10. If the validation function for the Ticket Product is not working properly at the farebox, the Ticket Product should be able to be used as a flash pass to ride as a backup for fare payment.

31 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

11. The MTAS App shall not require operators to manually register any validation or customer information when using the MTAS App.

4.4.5 ADA Compliance The System shall be in compliance with the U.S. Department of Transportation’s ADA requirements. In compliance with the Information and Communication (ICT) Final Standards and Guidelines around the revised standards of section 508, Contractor will include current VPAT documentation.

4.4.6 Real-Time Service Information The MTAS App and website shall provide the Authority with real-time customer information for fare product purchases, fare payment and an application interface to the existing TrueTimeSM System providing bus, rail scheduling and location mapping information (presently implemented by the Authority). The Authority will provide a real-time API key. The RFP proposal respondents are also encouraged to access the Authority’s provided “Developer Resources” page for GTFS files. This information shall be provided on a customized dashboard to be created in conjunction with Authority’s requirements, and in electronic reports that will be delivered on a configurable periodic basis to Authority personnel.

4.4.7 Features to Enhance Customer Convenience As future functions, the Authority may want to incorporate the ability to link the MTAS to other transportation provider apps such as bike share services, ride share services or other Mobility as a Service (MaaS) apps. The Authority may want to have the MTAS link incorporated to transit planning apps such as “Transit” and “Transit Stop” or “Google Maps”. The proposed MTAS system shall have the ability to incorporate these types of ride share services and planning apps if requested during the term of the contract. After full implementation of the MTAS, Authority may look to incorporate their paratransit service ride payments into the MTAS. The proposed MTAS shall have the flexibility to build this function into the MTAS as a future change order.

4.4.8 MTAS Languages The Services require that the MTAS and all applications and documentation are provide in American English. Authority may choose to add different languages for the Services at a future time. The Contractor shall advise Authority of the languages which are working in its app and if any other languages could be added to the app as a future capability. The additional languages that Authority may choose to activate shall be included in the provider’s cost proposal.

4.4.9 Messages and Alerts The MTAS App shall have the ability to allow Authority to send short messages and alerts to users in cases when it feels that situations require a customer alert or emergency. This can be sent as a text message or in-app notifications and must comply with the TCPA.

4.4.10 Deliver Prompt and Efficient Customer Information The Mobile Ticket App Back Office Web Site reports shall provide data on ridership and customer use habits. The data shall contain the Rider Class for the trips taken.

32 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

4.4.11 Sales Volume The MTAS shall provide an unlimited number of Ticket Products sales and usage transactions 24 hours per day, 7 days per week and 365 days per year.

4.4.12 Administration The MTAS shall have a web interface providing the ability to easily access MTAS App usage, extract data and make changes to accounts and Ticket Products. The Service shall have security in place to create user accounts with passwords and various levels of access such as role-based administration rights. There shall be no limit on the amount of users that can access the Mobile Ticket App Back Office Web Site.

4.5 System Requirements

4.5.1 Independent Mobile Ticketing Application System The MTAS shall be coexisting with, but can be functionally independent from the existing AFCS.

4.5.2 Service Design and Development The MTAS App shall be branded for the Authority. The Contractor shall take the requirements contained within this Scope of Services and develop an initial flow design. Contractor shall provide an on-site design team meeting with Authority’s designated personnel to review and refine and complete the initial app flow design. A design review shall be conducted with key Authority staff and the Contractor for approval of the design. For an existing MTAS App being offered by the Contractor, a design review and approval is required for customizable web and app features. New functions not available in the existing app shall be developed per requirements contained within this Scope of Services with the Contractor providing on-site design team meetings with Authority to review, refine and complete the application flow design for such functions.

While on-site, the Contractor shall complete an onsite evaluation for each vehicle type/customer services center in the Authority’s fleet/facilities and, review the high platform stations containing validators, to create an installation plan for hardware. This plan will include placement of equipment and installation needs.

4.5.2.1 Design Criteria The MTAS App shall be available for download, free of charge, by the Authority’s customers. It shall be available for all supported versions of iOS and Android.

Customers shall be required to set up their account through the MTAS App.

Customers shall have the ability to buy single and multiple Ticket Products directly through the MTAS App, using a credit or debit card, PayPal, Apple Pay or Google Wallet. All fare products available through the current AFCS shall be available for purchase through the MTAS. The MTAS App shall have the ability to pay for multiple riders, within one transaction, at fareboxes when entering the

33 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

vehicles or at validators on high platform stations. The mobile app shall have the ability to email a receipt for Ticket Products purchased through the MTAS App.

The MTAS App shall have a feature so that Ticket Products can be purchased by one person and sent to another user via text message (in strict compliance with the TCPA) or other delivery vehicle.

The MTAS App shall have the ability to account for free youth riders with a paying adult. This feature will be required for the full launch of the MTAS App.

The MTAS App shall have the ability to validate passes using Bluetooth technology and NFC. The MTAS App shall be able to be validated while a customer is inserting cash into the farebox or using their ConnectCard. There shall be visual and audio cues from the MTAS App or the reader equipment once the Ticket Products has been validated. The MTAS shall count and track ridership separately from the farebox. An external screen, which can be mounted near the farebox operator control unit, to show Ticket Products validation, shall be included in the proposal as an additional option. No operator counting shall be required to track mobile Ticket Product ridership. Validation of Ticket Products shall be completed independent of Wi-Fi signal strengths or cell coverage. In the event of a loss in cell coverage while the customer is trying to validate his or her Ticket Product, the MTAS App shall store the transaction event for later transmission once coverage has been restored and allow access to ride.

Once a Ticket Product has been validated, the MTAS App shall have the information needed for a fare inspector to visually verify that a ticket product was validated properly. The information displayed on the validated ticket screen shall include a countdown timer, the date validated, the time the validation started, the vehicle number or station that the Ticket Product was validated at, the fare product used and the number of other Ticket Products validated (if multiple rides were paid for). A handheld reader shall not be required for verifying the use of a Ticket Product. The mobile Ticket Product shall contain a feature so that it can be easily demonstrated that the Ticket Product is not a screen shot or video clip.

The MTAS App shall provide Authority customer service with the data needed to review complaints and to make accurate judgments on misuse or fraudulent use. Authority customer service shall be able to make adjustments to customers’ mobile device in real time.

The MTAS App shall have the ability for Authority customer service to assign a rider class to an eligible customers’ account, to allow that rider access to purchase reduced fare Ticket Products or be given a senior pass. As an example, the MTAS App account will allow Authority customer service to select an option for senior who can then be given a Ticket Product to ride for free. The rider class shall be able to be unassigned in the case where the customer is no longer eligible for reduced fare.

34 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

Vehicles shall not require any additional uploads to exchange ridership recorded from mobile Ticket Product use. Ridership shall be recorded in real time.

The MTAS App shall allow the Authority to add and remove Ticket Product for special events as needed. Once added, Ticket Product shall be available for purchase and use immediately. The MTAS shall allow the Authority to create a code that the customer can use during payment to discount a Ticket Product up to the full price of the Ticket Product. This function shall be available at the Authority request, within one year of the full MTAS App launch.

The MTAS App payment services must be and remain compliant with the latest PCI-DSS rules, regulations and terms and conditions during the term of the Agreement. Contractor’s application shall be listed as a Validated Payment Application as defined by the PCI Security Standards Council. Contractor shall complete annual revalidation of payment application as required by the PCI Securities Standards Council so that Contractor’s application remains a Validated Payment Application for the duration of Agreement with Authority.

The MTAS App, reader and Mobile Ticketing App Customer Facing Web Portal must comply with the latest ADA laws, rules and regulations, including but not limited to the Information and Communication (ICT) Final Standards and Guidelines around the revised standards of section 508, as documented through a VPAT

The MTAS App shall have the ability to provide fare capping as specified by the Authority. This function will not be active for the full launch. It may be requested anytime within the term of the Agreement upon board approval.

The System shall have the ability to be updated by the Contractor or Authority to change pricing or business rules as enacted by the Authority’s board. Updates for price changes and business rule updates that cannot be completed in or to the System by Authority personnel shall be completed by the Contractor at no additional cost to the Authority. The MTAS App shall be able to include the regional partner’s ticket products should they request to participate. The App shall designate between the regional partner’s ticket product sales. The Contractor shall complete all settlements with each regional transit authority independent of, and without cost to, the Authority.

The MTAS App and website shall not limit the number of users during a given period. The Mobile Ticket App Back Office Web Site shall not limit the number of Authority personnel who can log in to complete Authority day-to-day business.

Based on the capabilities of the mobile device platform, the MTAS App shall make necessary changes to the phone setting as needed to when opening the MTAS App per terms and conditions agreed upon by Authority and the Contractor and provided by the Contractor during account setup. These settings

35 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

shall include, but not be limited to setting the volume to the max setting, turning on Bluetooth when opening the MTAS App, activating the Bluetooth capability and/or NFC reader when validating Ticket Products, turning on the phone’s location and turning on cellular data to allow communications over cellular network. Should the customer disable a mobile function needed to validate payment, the MTAS App shall inform the customer what functions need to be running to use the MTAS App, turn them on or give the user a chance to turn them on. The app shall not allow a user to validate or utilize Ticket Products if required services are disabled by the user.

The Contractor shall provide the System, including hardware, software, all configurations, set up, web portals, all required licensees, training and Authority employee support related to the Service. This includes but is not limited to any third party costs associated with the Service hardware and software, integration, implementation, routine maintenance and issue resolution, Ticket Product purchases and day-to-day functionality.

The Contractor shall provide the Authority with spare parts that can be swapped out for defective or failed units, at a quantity level not to disrupt service. Failed parts can be exchanged and stock replenished. Stock should be based on past failures experienced at agencies currently running a similar system.

The Contractor shall provide any necessary open source codes and open standards documents needed to incorporate their app into other existing apps that would allow Ticket Product purchases to be completed from a third-party app.

The Contractor shall have no right to use or sell Authority customer information obtained through the MTAS App or website without explicit consent of the Authority.

4.5.2.2 Design Reviews A Preliminary Design Review (PDR) for custom applications or configurable functions shall be conducted to review the initial flow design, updated screens and installation plan documents. Once these documents have been approved by Authority, it will become the foundation for the design work and Service implementation. Written acceptance of the final design will come from the Authority Project Manager and Contractor after a Final Design Review (FDR) and shall commence the development of the Service, providing a complete and comprehensive solution for the Authority’s customers and employees.

4.5.2.3 Final Design and Configuration Documents Contractor shall supply copies of the final design electronically in both Microsoft Word version 2016 or compatible and PDF format.

4.5.2.4 Installation Plan Contractor’s Project Manager shall work closely with Authority to develop an appropriate installation plan that will minimize inconvenience to Authority’s

36 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

operations and customers. The installation plan shall be detailed including tasks, task owners, expected duration, task sequence, test plans, etc.

4.5.3 Testing, Quality Assurance

4.5.3.1 Beta Program A beta test (Beta Program) will be performed using Authority employees and key stakeholders prior to the start of an external Pilot Program. The Authority will define specific and limited bus and rail lines for this Beta Program. The Contractor shall work with Authority to develop adequate test procedures and provide a testing plan to the Authority Project Manager for approval at least 14 (fourteen) days prior to the start of the Beta Program. Contractor will provide testing materials and training to Authority’s selected staff. The Beta Program will include the following components: • Fully functioning MTAS App; • Complete installation of equipment on the designated bus and rail vehicles to fully use all features of the MTAS App; • Fully functioning MTAS App back office Web site to access data and troubleshoot complaints; • Fully functioning Mobile Ticketing App Customer Service Web Portal. The Beta Program is designed to test the function and reporting elements of the System, the MTAS App and impacts on operations. Once the Beta Program is verified by Authority as operating properly, the Authority will begin a Pilot Program, as described below.

4.5.3.2 Pilot Program A “Pilot Program” for the System will be conducted in revenue service using a select group of the general public prior to a full implementation. The Contractor and Authority will work collaboratively on a Pilot Program lasting for a mutually agreed upon time period on mutually agreed upon routes and locations. The Pilot Program is designed to test the function and reporting elements of the system, the MTAS, impact on operations and to determine if the MTAS is acceptable to its customers. At the conclusion of the Pilot Program, the Authority, its designated stakeholders and the Contractor will evaluate the pilot test results and comments to determine the apps effectiveness on the Authority’s operations. Items such as, but not limited to, the following will be evaluated: • Participant feedback on MTAS App usage and customer facing devices; • Data collected from Mobile Ticket App Back Office Web Site by Authority project team and its local external stakeholder advisory groups; • Customer service troubleshooting;

37 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

• System failure rates; and • Customer comments and concerns. System updates to fix findings will be reviewed by the Contractor. The Contractor shall provide the Authority with the fixes that can be corrected and identify which fixes cannot be addressed, along with alternatives and options. Based on available changes, the Authority will decide whether full System implementation will be pursued.

4.5.4 Service Final Acceptance Full Deployment will only occur after the resolution of system updates identified in the Pilot Program, along with all equipment being fully installed, to the satisfaction of the Agency. Final Acceptance will occur after the conclusion of 30 days of uninterrupted service, as determined by the Authority, after Full Deployment.

4.5.5 System Performance Criteria The System must perform to the following requirements. It is the intention of the Authority, in some cases, to leave the performance criteria somewhat vague or absent, so that the Contractor can propose alternative performance criteria that would be mutually agreed upon with the Authority.

4.5.5.1 Testing and QA The System will consist of the following functionality (This is not a comprehensive list but, a list of the prime functional features to give the Contractor a better understanding of the testing and quality expectations being set by the Authority). Each of the features/functions listed below will have a critical timing criterion that the Contractor shall perform too: • MTAS App communication between the app and the vehicle or equipment for validation (Validation over a connected vehicle network shall not exceed 500 Msec, validation completed over a rider’s mobile device network shall not exceed 3 seconds), • MTAS App rider GUI interface function selection (Not to have more than 3 steps after opening the MTAS App), • MTAS App rider pre-selected single fare type, ready to validate Ticket Products (Not to have more than one step), • MTAS App rider transaction acceptance. If there is a vehicle network connection delay, validation shall not to exceed 1 second before access. If there is a rider’s mobile device connection delay, validation shall not exceed 3.5 sec before access is granted, • Mobile Ticketing App Customer Service Web Portal rider registration (Should not take more than 6 steps (entry points will be greater)), • Mobile Ticketing App Customer Service Web Portal rider access (Should not take more than 5 seconds to present “Home Page”) unless internet communications or carrier network is down,

38 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

• Customer service help for riders with mobile device issues (Submitted via voice, text or email (The Contractor will handle all incoming calls within 8 hours)), • Contractor’s back-office reconciliation and settlement (Not to take more than 24 hours for any transaction event), • Rider registration (Contractor shall allow the rider to register via either the Mobile Ticketing App Customer Service Web Portal or through the MTAS App).

Note: The Authority will not register riders onto the MTAS database to prevent dual personal data storage and handling that may increase security risk.

4.5.5.2 The MTAS (Ridership) Simple Functionality The Authority’s requires that the System offers a simple and intuitive operational rider experience that promotes rider adoption of the mobile application and use. The Authority will review the MTAS App in advance of any customer issuance to ensure easy and intuitive use for the riders.

4.5.5.3 Communications and Power Failure In the event of a major power or network connection failure greater in duration than 30 minutes, in no case will the Mobile Ticketing App Customer Service Web Portal be down for more than 2.0 hours. It is the responsibility of the Contractor to make adequate system backup provisions to accommodate such events.

4.5.5.4 MTAS Rider Ticket Use Experience; For connected vehicles, no transaction period shall exceed 500 Msec from point of application start (the period in which the rider’s smart device is recognized by the entrance device (tag or token) and validation is made). The Authority recognizes the possibility of a mobile carrier’s extended response delay. In this occurrence, the MTAS AppApp must default to the rider’s benefit and grant acceptance within 1 second. If, the rider’s record shows multiple carrier delayed response occurrences at no fault of the overall MTAS, this is to be reported to the Authority for further action to be taken with the rider. For the MTAS communicating over a rider’s mobile device, no transaction period should exceed 3 seconds from the point the mobile device is recognized and validation is made. For an extended response delay of a mobile device network, the MTAS App must default to the rider’s benefit and grant acceptance within 3.5 second.

4.5.5.5 MTAS Back-office Data Integrity & Accuracy Transaction and revenue information/data shall have an accuracy rate of no less than 99.7% over any given period of 24 hours. The Authority understands that a very limited number of transactions may not clear and show-up until the next day. Once these transactions are accounted for, the revenue accounting should result in a 99.9% accuracy.

39 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

4.5.5.6 Back-office processed transaction data performance All transaction processing for settlement shall be performed within a 24-hour period of the transactions time stamped occurrence. All transactions that occur on a given day should be settled within that same day settle processing cycle and a report made available by the next morning before 7:00 AM ET.

4.5.5.7 MTAS Website Performance The Mobile Ticketing App Customer Service Web Portal shall be designed in a manner that is intuitive to the ridership/users/operators to encourage MTAS early adoption. The Mobile Ticketing App Customer Service Web Portal must be operating 99.5% of the time on a 24-hour basis, excluding scheduled downtimes. Availability of the Mobile Ticketing App Customer Service Web Portal is vital to the adoption and continued use of the mobile application. In the event of an unforeseen power or connectivity failure/outage in excess of 30 minutes, (a “documented event”), the operating percentage will be acceptable for a given weeks’ period of 99.0% All calculated operating percentages will be based on a week’s period of 7 calendar days, starting on any selected calendar day of the Authority’s discretion for auditing purposes.

4.5.5.8 Power or Network Connection Failure In no case, during a power or communications failure of greater than 30 minutes, will the Mobile Ticketing App Customer Service Web Portal be down for more than 2.0 hours. It is the responsibility of the Contractor to make adequate system backup provisions to accommodate such events.

4.5.6 Security The MTAS shall comply with best practices for security, data integrity and data privacy, including, but not limited to:

4.5.6.1 Cybersecurity The System shall comply with current PCI-DDS Standards and with the National Institute of Standards and Technology (NIST) framework (currently v1.1) and with the Open Web Application Security Project (OWASP) testing guide. Contractor’s application shall be listed as a Validated Payment Application by the PCI Security Standards Council. Contractor shall complete annual revalidation of payment application as required by the PCI Securities Standards Council so that Contractor’s application remains a Validated Payment Application for the duration of Agreement with Authority

4.5.6.2 System Security Information Questionnaire The Contractor shall complete the System Security Information Questionnaire in Section 2.7.1 and provide responses as a part of its response to this RFP.

4.5.6.3 VPN Access If required, the Authority shall make available, at Authority’s expense, VPN access at each Authority site for online accessibility.

40 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

4.5.7 Reporting and Settlement Standard and ad hoc reports are essential to the Authority in providing ridership data, helping customer service issues and settling accounting records. The Service shall have the capability of logging details about the mobile app use in order to provide reporting to the Authority staff. The reports shall be user friendly. Data shall be available for a period of 12 months. Report requirements will be defined during the development process and will include, but not limited to: 1. Daily route ridership report 2. MTAS App utilization 3. Aggregated ridership boarding and exiting data 4. Ridership use 5. Sales

4.5.7.1 Ridership Authority currently uses APCs to report ridership. When APCs are not available, the farebox usage and MTAS App validations will be used for ridership reporting. The Contractor shall provide a report the shows route ridership for given dates and times and vehicles. This shall be available in both PDF and CSV formats. This data will be loaded into a SQL database by Authority IT. The Authority will provide the necessary trip and vehicle data to the Contractor to use as a cross reference to extract the ridership data required.

4.5.7.2 Trip Information Interface The mobile app shall have the ability to record where a customer has entered and exited a vehicle or station, without the customer having to tap on and off for each trip. Aggregated trip data shall be accessible through the Mobile Ticket App Back Office Web Site, and include but not be limited to chart boarding locations, exit locations, travel patterns, Ticket Products purchases and ticket product activation data. The data shall be available as a PDF and CSV format, or one that can be imported into Excel. Authority shall have access to database information for creating custom queries.

4.6 Service Levels

4.6.1 Data Integrity and Accuracy Transaction and revenue information/data shall have an accuracy rate of no less than 99.7% over any given period of 24 hours. The Authority understands that a very limited number of transactions may not clear and show-up until the next day. Once these transactions are accounted for, the revenue accounting should result in a 99.9% accuracy.

4.6.2 Transaction Processing and Settlement All transaction processing for settlement shall be performed within a 24-hour period of the transactions time stamped occurrence. All transactions that occur on a given day should be

41 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

settled within that same day settle processing cycle and a report made available to Authority by the next morning before 7:00 AM ET.

4.6.3 Availability Availability of the System is vital to its adoption and continued use. In the event of an unforeseen power or connectivity failure/outage in excess of 30 minutes, (A documented event), the operative percentage will be acceptable for a given weeks’ period of 99.999% All operative calculated percentages will be based on a week’s period of 7 calendar days, starting on any selected calendar day of the Authority’s discretion for auditing purposes. After the public launch of the MTAS App, if the Contractor fails to provide the required “Level of Availability” for the Services per period, Authority shall have the following remedies that reflect the reduced availability achieved by the Contractor, and may make the following deductions from the payments due the Contractor, per the applicable monthly pay period.

Service Short-fall Remedy/Deduction

1. A reduction in the total compensation for the applicable month of 3% of Level of Availability less than 99.999% but total sales within the calendar month. greater than or equal to 99.9% availability 2. A reduction in any recurring monthly fee within one calendar month of 5% in which the monthly shortfall occurred.

1. A reduction in the total compensation Level of Availability less than 99.9% but greater for the applicable month of 4% of than or equal to 99.0% availability within one total sales within the calendar month. calendar month 2. A reduction of any recurring monthly fee of 10% in which the monthly shortfall occurred. 1. A reduction in the total compensation Level of Availability below 99.0% of the for the applicable month of 5% of required availability within one calendar total sales within the calendar month. month 2. A reduction of any recurring monthly fee of 15% in which the monthly shortfall occurred.

4.7 Program Management and Scheduling Contractor shall provide a timeline for system design, build and implementation within 7 days of Authority’s “Notice to Proceed” (NTP). System build, design and implementation associated tasks shall begin within 15 business days of the NTP and take no longer than an additional 90 days (120 days’ maximum project duration) from NTP.

4.8 Training The Contractor shall propose a training plan for Authority review and approval.

42 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

4.8.1 Training Documentation Contractor shall supply any and all training documentation including manuals electronically in either a Microsoft-based document or PDF format. Authority shall have the right to print unlimited copies of the manuals or other training documents for initial and future internal training and support of the service.

4.9 Maintenance and Support Services Maintenance and Support Services shall begin upon the start of the Beta program and shall extend to the termination date of the Agreement. MTAS App update releases will be delivered via the app store. Software releases for included hardware will be loaded electronically through a transfer basis. All software releases that contain new features and/or functionality shall be included in the Service during the life of the contract. Authority’s decision to enable new features that are not relevant to the Authority’s operations and business rules, will be done so at its discretion. Contractor warrants that the Services will be performed in a professional manner in accordance with reasonable commercial standards. Support software, including diagnostic routines as well as support tools, test equipment and documentation which may be supplied by Contractor for purposes of this Agreement are and shall, at all times, remain the exclusive property of Contractor. Maintenance and Support Services apply to at least two (2) most current Software releases. The Contractor should have staffing available via voice, email or text, to Authority customers who have specific functional issues with the mobile ticking App. Limited vendor contact with customer issues are anticipated with day to day rider issues handles thought the Authority Customer Service department.

4.10 Support The Contractor shall propose a support plan for Authority review and approval to ensure the System is fully operational 24 hours per day, 7 days per week and 365 days per year.

4.10.1 Ownership and Exclusivity

4.10.1.1 Website Ownership Rights As the Authority desires the MTAS and associated website to be an external service, the Contractor shall own, operate and maintain the MTAS System. This ownership is inclusive of all responsibility for domain name ownership, credit/debit processing related fees, chargeback liability due to provider application errors, PCI and/or EMV requirements, local, state and federal law requirements, as well as all other responsibilities inherent with ownership. As a part of this Agreement, the Contractor shall provide for the Authority, the mobile application and web related services that enable the sale, purchase and load of Ticket Products. The Services shall be provided to the Authority for the term of the Agreement. The sale of the Ticket Products shall be provided as part of the Services from this MTAS and website. The Contractor shall provide the Authority, for its approval, with detailed information and descriptions for

43 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

any proposed visual, functional and other changes, before they are implemented.

4.10.1.2 Exclusivity Although the Contractor will own, operate and maintain the mobile application and website, the Contractor shall not have exclusive rights to provide the Services. The Authority reserves the right to contract with multiple contractors for any point in time for the duration of the Agreement.

4.10.1.3 Licensing The Contractor shall license the MTAS and the System to the Authority under the terms identified in the Agreement. In summary, the Contractor shall provide the Authority with the following: a. Unrestricted license to use within the Authority system and to configure the MTAS System for the duration of the period of performance. b. Unrestricted license for the direct or indirect distribution of the mobile applications and/or System for the period of performance, c. Unrestricted license to use the interfaces, APIs and/or other mechanisms from which to build, adapt and/or develop ancillary related Authority related services, such as parking, bike share, travel information, etc.

4.10.1.4 Licensing Termination The Authority reserves the right to purchase or license for an extended period of time, take over and or operate the Service in the event the Contractor files for bankruptcy.

44 Port Authority of Allegheny County RFP No. 18-07 – Mobile Ticketing Application and Supporting Services

EXHIBIT 1: Sample Agreement No. R18-07

EXHIBIT 2: Certification of Proposer Regarding Debarment, Suspension and Other Responsibility Matters” or the “Certification of Proposer Regarding Debarment, Suspension and other Ineligibility and Voluntary Exclusions”

EXHIBIT 3: Proposer/Subcontractor Data Form

EXHIBIT 4: Resume Form

EXHIBIT 5: Summary of Costs

EXHIBIT 6: General Requirements Checklist

EXHIBIT 7: Proposal Evaluation Rating Sheet

EXHIBIT 8: Service Provider Information Security Questionnaire

45