../ Front ./ Stuff ./ ORCA /
English Pronouns Linux Suspend Script Fortune File

wireless u-pass system description

Please note that the source for this documentation was published on 16-Feb-1999, and was labeled as subject to change.

You can get a copy of the original file here.

From the system proposal:

Husky Cards will be distributed to staff and faculty with the transportation application inactive. Husky Cards will be distributed to students with the transportation application active. Husky Card for students will have no expiration date. The Husky Card will be issued by the Contractor to the University in bulk, with the transportation privileges enabled as noted in items 3 and 4. The University will have the ability to activate and deactivate all cards and applications on the card. The Husky Card will contain electronic purse capability that can be used for fare payment, and any additional services provided on or off campus as part of the Regional Fare Coordination System. This electronic purse can be used regardless of whether the transportation option on the Husky Card is enabled or disabled.

B.2.3 Card Blocking Process

Under certain circumstances the transportation option on the Husky Card can be blocked. There are two types of blocking that can occur:

  1. Functional Blocking This means the campus transportation option is disabled, but the Husky Card electronic purse or other applications on the card can still be used for fare payment and services. The Husky Card may be blocked at the campus office or on board the bus, ferry or at a rail/commuter rail station. As an example, a functional block would be applied when a student declines the transportation option.
  2. Card Blocking If a Husky Card is reported as lost or stolen, the next time it is used on a public transportation service the FTP will block the card. As a result, the transportation and all other applications on the card are disabled.

B.2.4 University Administration Procedures

The following describes the procedures, roles and responsibilities for the UW administration staff, the Contractor, the students and the UW staff and faculty to support the RFCS (Radio Fare Card System, a preliminary name for the ORCA project) university program.

Participant Role/Responsibilities: University of Washington

  1. Inform the Contractor in advance of the effective start date of the quarter for card issuance and updating.
  2. Issue Husky Cards to staff, faculty and students. Maintain stock of Husky Cards and request additional cards from the Contractor.
  3. Send all Husky Card program data to the clearinghouse system on a daily basis including program changes.
  4. Initiate functional and card blocks as requested.

Participant Role/Responsibilities: Contractor

  1. DAILY: Update the clearinghouse system files on receipt of card changes from the University. Compare the blocked transaction file to daily fare payment transactions that took place on the buses, rail and/or ferries. For all transactions which match, add a functional card block transaction to the daily file sent to the buses, rail and/or ferries. If the card is used again on the bus or ferry, the transportation option on the card will be disabled. Inform the University of cards that have been used for fare payment. The University can check this information and refuse to allow a student to decline the transportation option if the card has been used for fare payment. Distribute Husky Cards to the University as per contract.