Common Payment System (CPS) System Requirements
Common PaymentSystem (CPS) SystemRequirements1
SPEAKERSMANDY BISHOP, PEProgram Manager,City of Columbusmkbishop@columbus.govANDY WOLPERT, PEProject Manager,City of ColumbusADWolpert@Columbus.govALEX KAVANAGH,Technical Lead,HNTBAkavanagh@hntb.com2
TODAY’S AGENDA01 PURPOSE OF THIS WEBINAR 02 03 Share concept development activities from Smart Columbus with stakeholdersWEBINAR CONTENT Smart City Challenge and Smart Columbus Program Overview Smart Columbus Common Payment System Project Overview Smart Columbus Common Payment System Requirements Technical Details Discussion How to Stay Connected Stakeholder Q&AWEBINAR PROTOCOL All participant lines have been muted during the webinar in order to reduce background noise Questions are welcome via chatbox during the Q&A Section The webinar recording and presentation materials will be posted on the Smart Columbus website3
CHALLENGEAND PROGRAMOVERVIEW4
40 MILLION78 APPLIEDCOLUMBUS WONVISION:To empower our residents to live their best lives through responsive, innovativeand safe mobility solutions.MISSION:To demonstrate how an intelligent transportation system and equitable access totransportation can have positive impacts on every day challenges faced by cities.OUTCOMES:Safety, Mobility, Opportunity, Environment, Agency Efficency, Customer Satisfaction5
CPSOVERVIEW6
PROBLEM STATEMENT & CHALLENGES Disconnected mobile appsand payment options Lack of a comprehensiveplatform to plan, book, andpay Unbanked users must relyon cash for transportationoptions Public agencies faceobstacles when requestingtrip data from MobilityProviders77
CONCEPT FOR PROPOSED SYSTEM Pay for all transportationservices using a single account Ability to register multiplepayment methods Integration with COTA’s backoffice Fund CPS accounts usingprepaid debit cards or cash atCOTA TVMs IVR System Use the OS share anonymoustrip and payment data88
SYSTEMREQUIREMENTS9
SYSTEM REQUIREMENTS TECHNICALWALKTHROUGHDevelopment Process1. Break down the system intofunctional group categories2. Develop the technicalrequirements for systemcomponents3. Link requirements with userneeds, constraints andinterfaces as described by theConOps1010
Step 1CPS Back Office(CPS)Interface 15.1, 15.2, 15.3, 15.4COTA Back-Office(COTA)Interface 12.1, 12.2AdministrationCentral FareManagement SystemPCI ComplianceSoftwareDevelopment KitNotifications andAlertsInterface 8.1Transit Vehicle OnBoard FareManagementPayment DeviceReaderInterface 7.1Payment Device(PAYD)Break down thesystem into majorsystem componentsInterface 13.1, 13.2Point of Sale Terminal(POS)Mobility ProviderCentral Systems(MPCS)Provider CentralManagement SystemPayment DeviceInformationEPM Central System(EPMCS)Interface 6.1Reloadable SmartCardTerminal PaymentManagementInterface 16.1, 16.2Shared AccountProcessingIVR ProcessingCOTA On-BoardPayment Equipment(FBOX)Major System ComponentsCPS Back-OfficeValidationMobility ProviderPayment Equipment(MPE)Provider PaymentManagementInterface 17.1, 17.2Interface 5.1Interface 4.1COTA Back-OfficePersonal InformationDevice(PID)Operating SystemParking CentralManagement SystemPersonal Information DeviceReportingInterface 3.1, 3.2, 3.3Guest AccountsInterface 11.1, 11.2, 11.3, 11.4Provider AccountsInterface 2.1, 2.2Traveler AccountsIncentives andRewardsCPS PaymentProcessingInterface 19.1, 19.2City of Columbus(CITY)Smart ColumbusOperating System(OS)Interface 10.1, 10.2Parking Operator ApplicationCPS Web Portal(WEB)WebsitePortal Request forPaymentInteractive Voice Response SystemCPS Landing PagesPayment BrokerIVR System(IVR)Anonymous Trip andPayment DataSmart Mobility HubsApplication PaymentDevice (QR code, barcode, NFC, activationcode, BLE)Mobility Provider Central SystemsMobility Provider EquipmentMMTPA Request forPaymentInterface 9.1, 9.2Interface 18.1, 18.2Interface 20.1Financial Centers(FIN)FIN PaymentProcessingThird-Party Users(THRD)IVR System Requestfor PaymentAnalyticsUser FeedbackPublic APIsCPS Landing PagesInterface 1.1, 1.2Interface 21.1, 21.2Event Parking Management CentralSystemPoint of Sale TerminalsEPM Request forPaymentSmart Mobility Hubs(HUBS)MMTPA Request forPaymentThird-Party UsersOutside of CPSscopeFareboxCPS Landing Pages11
SYSTEM REQUIREMENTSRequirement NameAvailability and nterfaceInformation ManagementLife Cycle ePhysicalPolicy and RegulationSecurityStorage and TransportStep 2Develop the technical requirements for system componentsRequirement Description (EPM Central System)In the event that the service for which the funds are being held is not realized, the hold onthe funds shall be removed and credit restored to the Traveler account as necessary.Verification MethodThe CPS shall be fully compliant with Payment Card Industry (PCI) standards,including ensuring that all customer credit card payments completed using thesystem shall avoid any access to or storage of credit card numbers on any Cityor COTA-operated computers.InspectionDemonstrationTestAnalyzeThe CPS shall be capable of integration with COTA's back-office account-based system,allowing users to associate any COTA-issued fare product with a registered CPS account.12
SYSTEM REQUIREMENTSUser nt 2Constraint 3DescriptionNFC IntegrationCPS AccountPayment MediaPay OnceExisting Fare ProductsMobile TicketingOperations andMaintenanceFuture Growth andMaintainabilityComplianceStorage of Sensitive DataReimbursementSecurity and EncryptionDescriptionThe MMPTA/CPS system must integrate with COTA's newFare System. It is necessary for COTA's new Fare Systemvendor to develop modules for the Operating System andadhere to open data and open architecture designprinciples.Mobility Providers must be willing to integrate with theOperating System through open standards and to acceptthe CPS as payment method.Step 3Requirement Description(Interactive Kiosk)COTA shall be responsiblefor managing COTA fareinformation and will makefare information availableto the 3-V01CPS-IX2844-V01Link the requirementswith user needs,constraints andinterfaces asdescribed by theConOpsSource ElementCPSCOTACPSCOTADestination ElementCOTACPSCOTACPS13
REQUIREMENTS BY THE NUMBERS 350 Requirements 35 Subcomponents Shared Accounts, Administration, PCI Compliance, Notifications, etc. 17 Requirement Types Functional, Performance, Interface, Data, Security, etc. 14 Functional Groups CPS Back-Office, COTA Back-Office, Personal Information Device, etc. 5 Levels of Importance Shall, Shall Not, Should, Should Not, May 4 Verification Methods Inspection, Demonstration, Test, Analysis14
SYSTEMREQUIREMENTSDISCUSSIONPANEL15
DISCUSSION PANELMICHEAL D. CARROLLChief Information Officer,Central Ohio Transit AgencyROBERT JAMESLead Systems Engineer,HNTB CorporationBRIAN KINGTechnical PM,Smart ColumbusOperating SystemALEX KAVANAGHTechnical Lead,HNTB Corporation16
SYSTEMREQUIREMENTSDISCUSSIONSUBJECT MATTER EXPERTS PANELThree categories of requirements based on major systemcomponents: Payment Processing (Back-Office) Hardware (Farebox, POS, TVM) Operating SystemFor each category: Description Example requirements DiscussionSummary and Lessons Learned17
PAYMENT PROCESSING (BACK-OFFICE)Sub-Components Shared AccountsPayment ProcessingAdministrationPCI ComplianceSoftware DevelopmentKit Payment DeviceInformation Reporting Guest AccountsProvider AccountsTraveler AccountsPCI ComplianceIncentives and RewardsIVR ProcessingCOTA Central FareManagement System18
PAYMENT PROCESSING (BACK-OFFICE)REQUIREMENTSREQ IDDescriptionCPS-FN2500-V01 The CPS shall provide back-end integration with COTA's fare management system.CPS-FN2559-V01 The CPS shall be capable of integration with COTA's Back Office account-based system, allowing Users to associate anyCOTA-issued fare product with a registered CPS account.CPS-FN2560-V01 The CPS shall be capable of integration with COTA's smart card.CPS-FN2561-V01 The CPS shall be capable of integration with COTA's fare subsidy programs.CPS-FN2564-V01 The CPS shall provide landing pages for integration with the MMTPA to pay for multimodal trips.CPS-FN2565-V01 The CPS shall provide landing page for integration with the EPM application to pay for parking.CPS-FN2591-V01 Integration with the MMTPA shall provide a seamless User experience for the Traveler by not requiring a separate logonto the MMTPA.CPS-FN2488-V01 The CPS shall allow travelers to utilize existing COTA period pass products, which permit journeys within the COTAnetwork, subject to time restrictions.CPS-FN2644-V01 Payment transactions shall be processed in real-time through the CPS.CPS-FN2645-V01 The CPS shall provide access to landing pages allowing Travelers to pay instantly without being redirected away from theapp to complete the transaction.CPS-FN2646-V01 The CPS shall provide landing pages to manage Traveler and Provider accounts.CPS-FN2730-V01 All virtual fare product interfaces presented on the PID shall be configurable by authorized City/COTA individuals.CPS-FN2491-V01 When applying virtual transfer credits toward a multi-leg transit trip, the remainder of the cost of the trip shall be takenfrom the Traveler account (stored cash value).CPS-FN2500-V01 The CPS shall provide back-end integration with COTA's fare management system.CPS-FN2506-V01 Administrative accounts shall include fine-grained permission levels (e.g., View Only, Limited Access, and Full Control)19
PAYMENT PROCESSING (BACK-OFFICE)TOPICS1. Integration with the COTA is a critical partof the CPS project. What does integrationlook like? What COTA systems will theCPS be integrated with?2. The CPS will ultimately be owned andadministered by an NGO. How does thisalign with COTA’s vision for the CPS?20
PAYMENT PROCESSING (BACK-OFFICE)TOPICS3. How will payment processing andreconciliation with the various serviceproviders be handled?4. Several requirements identify thecollection of PII data. How will this data bemanaged to ensure privacy?21
HARDWARE (FAREBOX, POS, TVM)Sub-Components: Transit Vehicle On-BoardFare Management Payment Device Reader Point of Sale TerminalPayment Management Mobility Provider PaymentManagement22
SAMPLE HARDWARE (FAREBOX, POS, TV)REQUIREMENTSREQ scriptionThe CPS may integrate with the contactless RFID reader (compliant with ISO 14443 Type A and B standard) of existingCOTA fareboxes for NFC-enabled mobile devices.The CPS shall integrate with COTA's existing fareboxes to allow recognition of a mobile app presenting a ticket ID viaan optical barcode on the device screen, or (if supported by the device) through NFC.Activating an e-ticket shall cause the ticket to expire from the Traveler account.If the mobile device of the Traveler is NFC enabled, and compliant with ISO 18092/ISO 21481, the device shallbroadcast the same unique serial number that is encoded in the QR code.The CPS shall be capable of digitally rendering optical codes (mobile e-tickets) for optical scanning at provider readerequipment.Mobile e-tickets shall be machine readable 2D optical code compliant with ISO-15415, encoding the unique serialnumber.Mobile e-tickets shall serve to create the identifier used to validate and track the ticket and associated transactions inthe system.COTA fareboxes shall manage COTA fare information on transit vehicles.COTA fareboxes shall provide traveler fare collection interface on transit vehicles.COTA fareboxes shall provide COTA fare collection data.COTA fareboxes shall provide COTA payment device interface.The CPS shall generate QR code, bar code, NFC, BLE or activation code, as appropriate.The CPS shall generate QR code, bar code, NFC, BLE or activation code, as appropriate.The CPS shall provide an interface between POS and CPS to allow users (e.g. unbanked users) to load cash at COTAticket vending machines (TVMs) to fund a Traveler account.23
HARDWARE (FAREBOX, POS, TVM) TOPICS1. The SyRS includes several requirements focusedon hardware functionality (i.e., Bluetooth andNFC transponders). Does Columbus have plansto install hardware as part of the project? Howwill the CPS interface with existing COTAfareboxes?2. How will unbanked users, or users who prefer topay with cash, use the system?24
OPERATING SYSTEMSub-Components Payment BrokerAnonymous DataAnalyticsUser FeedbackPublic APIs25
SAMPLE OPERATING SYSTEMREQUIREMENTSREQ 42-V01CPS-DR2647-V01CPS-DR2775-V01DescriptionThe payment broker in the OS shall provide a shared account ledger.The payment broker shall not maintain PCI data. The CPS Back-Office will maintain this sensitive information in asecure environment.The payment broker shall receive payment information from the MMTPA through CPS landing pages.The payment broker shall receive payment information from the EPM application through CPS landing pages.The payment broker shall not maintain PCI data. The CPS Back-Office will maintain this sensitive information in asecure environment.The payment broker shall receive payment information from the MMTPA through CPS landing pages.The payment broker shall receive payment information from the EPM application through CPS landing pages.Data posted to the OS shall have PII obfuscated so that it may be available to third-party users.Third-party users shall be given access into the Operating System for anonymous trip and payment data.City of Columbus users shall be given access into the OS for performance measurement data and reports.Third-party users shall be given access into the Operating System for anonymous trip and payment data.The CPS shall provide anonymous payment data to the OS for storage in accordance with OS practices.The storage time of anonymous payment data in the OS shall be configurable up to a maximum of 10 years by theCity/COTA.26
OPERATING SYSTEM TOPICS1. What is included in the shared account ledger andhow does it work?2. Will Service Providers be expected to add users tothe shared accounts ledger? How will this work forlarge TNCs, for example?3. Describe how the Payment Broker works.27
OPERATING SYSTEM TOPICS4. How is Columbus proposing to use open datastandards? How can other agencies benefit fromwhat Columbus is doing?5. How do you plan to capture anonymous data? Howwill it be shared? What types of reporting will beavailable?28
SUMMARY / LESSONS LEARNED1. Prioritize early engagement with transportation providers2. Shared account vs. single pay system3. Fare System Upgrade4. Requirements development5. Sustainability and social equity6. Agile project development29
UPCOMING MILESTONESSystem Requirements SpecificationDecember 2018CPS Release 3November 2019Release RFP/Procurement/NTPDecember 2018 – March 2019MMTPA/CPS Go LiveJanuary 2020Vendor AgreementsMarch 2019 – January 2020Data CollectionJanuary 2020 – January 2021CPS Release 1June 2019CPS Release 2September 201930
SCHEDULE31
COMMENTSPublic comment period open for the CPS SystemRequirements: November 21- December 5, 2018 Where to find it: View the System Requirements at: https://smart.columbus.gov/projects Click Comment Payment System Direct link to file: SCC-BSysReq CPS DRAFT 20181022 for USDOT.PDF How to comment: Please email comments to: kldepenhart@columbus.gov Subject line: CPS Comments Include your contact information State whether or not you represent a vendor interest32
HOW TO STAY CONNECTEDUSDOT SMART CITY CHALLENGEPROGRAM INQUIRIES:Kate Hartman, Chief - Research,Evaluation and Program Management Intelligent Transportation Systems Joint Program OfficeKate.Hartman@dot.govUpcoming Smart Columbus Webinars: Overview of Emerging Technologies:Connected Electric AutonomousVehicles and Truck Platooning –1/30SMART COLUMBUS INQUIRIES:Alyssa Chenault, CommunicationsProject Manageranchenault@columbus.govWebinar recording and materials will be available at itsa.org and smart.columbus.gov33
SIGN UP FOR EARN MOREColumbus.gov/smartcolumbus@SmartCbus34
QUESTIONS?35
TOPICS – SYSTEM BOUNDARIES The boundaries for the system of interest are not welldefined and there appear to be several requirementsfocused on systems outside the boundaries of theproposed system (i.e., requirements about COTA FareSystem). Are COTA and the SCOS part of the CPS system? It isnot clear what your system boundary is. CPS-FN2500-V01 – “The CPS shall provide back-endintegration with COTA's fare management system.” Need more details, what will be integrated? What specific datawill be shared, etc.37
TOPICS – OPERATION AND OWNERSHIP Who is responsible for operations and administration ofthe CPS? The requirements include several activitiesthat will require staff to support day-to-day operations?Who will be doing this? And please note that the contextdiagram and “Users” don’t define an entity responsiblefor this functionality. For example: Who is going to be responsible for disputes, etc.? Who will be responsible for providing help to Travelers? Who will be running reports, etc.?38
TOPICS – HARDWARE The SyRS includes several requirements focused on thefunctionality of hardware (i.e., Bluetooth and NFCtransponders) that appears to be installed in various vehicles(e.g., TNCs, buses, etc.) or in other places. Is Columbus planning to deploy BLE transponders to supporttransactions? Is Columbus planning to deploy NFC transponders to supporttransactions? Is Columbus planning to deploy contactless transponders to supporttransactions? Is this project planning to deploy Fareboxes as part of this project? CPS-FN2562-V01 – Do POS terminals currently allow cashto be added? Does the POS terminal issue a pre-paid cardfor the unbanked?39
TOPICS – SHARED LEDGER / DATA BROKER CPS-FN2468-V01 – “The payment broker in the OSshall provide a shared account ledger.” What is included in the shared account ledger? Need moredetails. Recommend establishing parent/child requirements thatdescribe what is included in the shared account ledger CPS-FN2514-V01 – “Providers shall have the ability toadd Users to the shared accounts ledger in the OS, sothat Travelers can access other modes oftransportation.” It’s not clear what this means. Why would Uber be addingusers to the ledger? I’m confused.40
TOPICS – ANONYMOUS DATA Line 201 – “The broker will be responsible for directingpayment requests to the CPS payment processor andfor capturing anonymous trip and payment data foranalytics.” It is not clear how anonymous payment data can be collected(payments need to be tied to an account). What are Columbus’plans to anonymize this type of data?41
TOPICS – IVR SYSTEM CPS-FN2636-V01 – “The CPS shall be capable ofgenerating a phone number for use by the Traveler toinitiate a trip via the IVR system.” I’m confused. Why does a phone number need to begenerated and what is the Traveler expected to do with thephone number to initiate a trip? CPS-FN2637-V01 – “The CPS shall be capable ofgenerating a trip code for use by the Traveler to initiate atrip via the IVR system.” Once the traveler gets a trip code from the IVR, what do theydo with it? How would I pay for a mobility service (i.e.,bikeshare) with this code?42
CPS-FN2730-V01 All virtual fare product interfaces presented on the PID shall be configurable by authorized City/COTA individuals. CPS-FN2491-V01 When applying virtual transfer credits toward a multi-leg transit trip, the remainder of the cost of the trip shall be taken from the Traveler account (stored cash value).
Product Viscosity in Centipoise Water 1 cps Milk 3 cps SAE 10 Motor Oil 85 - 140 cps Castor Oil 1,000 cps Karo Syrup 5,000 cps Honey 10,000 cps Chocolate Syrup 25,000 cps 275 Ketchup 50,000 cps Sour Cream 100,000 cps Shortening 1,200,000 cps . Epoxy and Urethane compounds can be heated to reduce viscosity however there are other .
CPS Spark and CPS Pulse Pads CPS Pulse Pads can answer true/false, yes/no, numeric, answer series and multiple-choice questions (up to 10 answer choices depending on the delivery mode), answer sequence, short answer (up to 20 characters), and essay questions (up to 140 characters). CPS Spark Student Response Pads can answer true/false, yes/no
4 payment options available to sars clients 5 4.1 payment option 1 - using efiling to make your payment 5 4.2 payment option 2 - payment at a sars branch 7 4.3 payment option 3 - using the internet to make electronic payment 9 4.4 payment option 4 - bank payments (at one of the relevant banking institutions) 10 4.5 foreign payments 11
Activate in the MOTOTRBO CPS 6.0 or later. Once activated, the CPS can connect to an unlimited number of repeaters, one at a time. Portable, Mobile and Repeater Customer Programming Software (CPS) Package - MOL download only version. Software Package includes CPS, Air Tracer, Tuner, RDAC, MNIS MCDD, DDMS and the MOTOTRBO System planner.
Employee esoure Guide Notes Emailing CPS Employees To email a CPS colleague within the CPS GroupWise email system, simply type in the employee's name or, in some cases, the department's name, in the "To" section on the email form. The name will pop in,
CPS 5.5 - CPS 185 . 5
Cyber-Physical Systems (CPS) Synopsis of Program: Cyber-physical systems (CPS) are engineered systems that are built from, and depend upon, the seamless integration of computation and physical components. Advances in CPS will enable capability, adaptability, scalability, resiliency, safety, security, and usability that will expand the horizons .
rate for 12C-ions was in the range of 6–13 9 106 cps and varied with the composition analysed (e.g. 7.5 9 106 cps for calcite, 6.9 9 106 cps for end-member dolomite and 12.7 9 106 cps for high-Fe ankerite (Fe# 0.789); session S13 data). The baseline of the Faraday cup (1011 Ω resisto
