Automatic Fare Collection-Knowledge Tree

As a junior AFC engineer, I am designing an AFC learning program for myself.

To learning anything, you need to start with a structure--a knowledge tree--to help you have a big picture of the "thing"--technic, system, language, etc. So that you will not get lost in merely one part of the picture---at the end you are competent of the original thing you want to learn.

I Structure of AFC:
1. System Design of AFC
      1.1 Business Model--product and fare structure
          1.1 Fare scheme
          1.2 Payment method
          1.3 Validation Policy
          1.5 Patron management
                1.5.1 Patron profile
                1.5.2 Concession policy & blacklist
      1.2 Media and Cash management
      1.3 AFC Architecture
      1.4 AFC interface
2. Media and Reader Design
      2.1 Smart card Fundamental
      2.2 Payment system design
      2.2 NFC as Media
3. Data management
      3.1 Data structure design
      3.2 Database management-data protection, backup, data storage policy
      3.3 API Design
4. System Management
      4.1 Account management
      4.2 Mode and alarm
      4.3 Parameter management
5. Inter-operability
      5.1 Inter-operation model design
      5.2 Inter-operation data exchange
      5.3 Inter-operation application management
      5.4 Inter-operation protocol
6. Case Study

From now on, I will blog according to the program above, avoid to post specific technic and try to learn AFC as a system.