Business Model

"A key component of the success of any project
is the clear and unambiguous definition
of the business objectives and requirements."

Structure

Sequoia’s generic Business Model provides the essential core elements of an Integrated Ticketing System within a framework which facilitates Sequoia and the Client working together to achieve the particular Business Model which meets the specific needs of The Client.The model describes the detailed interactions between:

  • Regulatory bodies
  • Issuers (Card, Application, Product)
  • Financial “Clearing” bodies
  • Transit Operators (with particular accommodation of their multiple tiers of involvement)
  • Acquirers (Sales, Operator, Merchant)
  • Cardholders

These detailed interactions are addressed within the contexts of:

  • Card/Application/Product Management
  • Clearing, Settlement and Reconciliation
  • Transaction Validation and Processing
  • Claims and Adjustment Management
  • Actionlist Management
  • Security Domain Requirements
  • Incorporation into environments with “legacy” components

Outputs from the model include:

  • Roles and Responsibilities:
    • Identification of scheme Roles
    • Mapping of scheme Responsibilities to Roles
    • Identification of KPI/SLA Requirements
    • Identification of Operating Policy requirements
    • Identification of Operating Procedure requirements
  • Detailed Functional Requirements (presented as the “Requirements Database” of the methodology)
  • Detailed Functional Design (presented as ”Use Cases” of the methodology)
  • Comprehensive mapping of Requirements to Design
  • Identification and definition of Reports
  • Performance Requirements. (presented as the “Supplementary Specification” of the methodology)

Timeliness

Failure to identify and describe the business relationships at a sufficiently early stage in a project will, almost invariably, lead to later re-work, and hence, additional project cost and delay.Sequoia’s Business Model mitigates this risk: A generic Roles and Responsibilities Matrix and generic Business Requirements across the generic roles of an ITS provide the foundation to catapult the project into establishing the business framework early in the timeline.