What metrics would you use to evaluate Cubic's OMNY contactless fare payment system?

Introduction

Evaluating the success of Cubic's OMNY contactless fare payment system requires a comprehensive approach to product metrics. To address this product success metrics challenge effectively, I'll follow a structured framework that covers core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

OMNY (One Metro New York) is a contactless fare payment system developed by Cubic Transportation Systems for the New York City metropolitan area's public transportation network. It allows riders to pay fares using contactless credit cards, mobile wallets, or OMNY cards, replacing the older MetroCard system.

Key stakeholders include:

• Riders: Seeking convenient, fast, and reliable fare payment
• Transit agencies: Aiming for efficient operations and increased ridership
• Cubic: Focused on system performance and adoption
• Merchants: Interested in potential integration opportunities

User flow:

1. Riders approach the turnstile or bus reader
2. They tap their contactless payment method (card, phone, or OMNY card)
3. The system validates the payment and grants access
4. Riders proceed through the turnstile or onto the bus

OMNY fits into Cubic's broader strategy of modernizing public transit fare collection systems globally. It competes with similar systems like London's Oyster card and Chicago's Ventra, but aims to be more open and flexible by accepting various payment methods.

Product Lifecycle Stage: OMNY is in the growth stage, having completed its rollout across the NYC subway and bus system, and now focusing on expanding features and increasing adoption.

Software considerations:

• Platform: Cloud-based backend with distributed edge computing for real-time processing
• Integration points: Payment processors, transit agency systems, and potentially third-party apps
• Deployment model: Hybrid cloud with on-premises components for critical operations