RFID Interoperability Best Practice Guideline ITS Canada Annual Conference & General Meeting Toronto 2013 May 26 to 29
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Who is the Guideline for? You should be interested in this document if you have an operation that makes use of person identifi cation, such as cross-border travel or validating eligibility for a reduced fare payment. You should pay attention to this document if you have a standalone operation that makes use of vehicle identifi cation, such as commercial vehicle credentialing, vehicle access control, or vehicle-based payment. You should seriously review this document if you have an operation that makes use of vehicle identifi cation and shares customers with other operations, within the same application or across applications. ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 2
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE What Applications Use Vehicle RFID? Verifying Commercial Vehicle Credentials Granting Vehicle Access to Facilities Golden Ears Bridge $ Assigning Vehicle Charges for Use of Facilities ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 3
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE How are Vehicles Identified? Customer Declaration License Plate Image On-Board Unit ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 4
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE RFID in British Columbia Protocol Application Example Source: BC MoTI ASTM v6 Weigh2Go BC transponders, consistent with use throughout North America. Port Mann Bridge and Golden Ears Bridge uses multi-protocol readers that include ASTM v6. Source: TransCore ATA (ISO 10374) Rail car identifi cation system used throughout North America. Source: Source: ISO 18000-6B FAST border initiative between US-Canada, US-Mexico - enhances CBSA TransCore trade fl ow and security to identify low-risk commercial vehicles by using eGo tags and RFID embedded FAST ID cards. NEXUS border initiatives - enhance border crossing time for low-risk area residents/frequent travellers between US-Canada borders using ID cards embedded with ISO 18000-6B compliant RFID. ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 5
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE RFID in British Columbia Protocol Application Example Source: TI Corp ISO 18000-6C Port Mann Bridge TReO decals for toll collection. Multi-protocol readers for Title 21 and ASTM v6 as well. There are also several applications in BC using 6C for indentifi cation of persons. Source: TransLink Title 21 Golden Ears Bridge Quickpass transponders for toll collection. Milti-protocol readers for ISO 18000-6C and ASTM v6 as well. Source: TagMaster 2.45GHz Used by Vancouver Airport to record the number of taxi trips to the airport terminal. ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 6
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Why are Vehicles Identified? Vehicles are identifj ed in order to look up related information. Interoperability concepts extend beyond vehicle identifj cation to include which data are shared, the method of sharing, Account – generally for accumulating and the frequency of sharing. For data for multiple vehicles; transportation applications, typical vehicle related information includes: Owner / operator / responsible person with contact details; Transaction record – location and time of each passage or access; OBU (vehicle) status – eg. valid / Account balance and payment invalid for specifi c application, history when applicable; on a security watch list; Commercial vehicle approval status Vehicle characteristics – eg. size, – e.g. clearance certifi cates, last axles: often mapped to a category; weigh station results; Vehicle license plate – for possible Goods / Trailer Manifest. validation with images; ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 7
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE What is the Nature of Related Information? Private (e.g. commercial vehicle credentials, toll customer payment credit card) Shared (e.g. vehicle characteristics, customer status) Public (e.g. aggregated vehicle information like travel time) ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 8
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Why Interoperability? Onboard Device A c c o u n t POWER OF ONE Phone Number • One onboard device (per vehicle) • One account • One phone number to call ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 9
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Implementing Interoperability There are essentially three layers of interoperability: Physical: The physical layer refers to the OBU and RSE devices and the extent to which these are interoperable between facilities. To say that two facilities or agencies have physical interoperability Convenience assumes that customers have one device Business Process per vehicle, which can be read at either Interoperability agency’s facilities. ce: Back offi ce interoperability Back Offi - Back Offi ce involves the establishment of agreements Cost between agencies for sharing OBU status Interoperability and transactions, and subsequently settling payments if applicable. - Complexity Physical Interoperability Business: At the business layer, agencies agree to operate under coordinated business rules to improve their effi ciency as well as simplicity for the customer. ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 10
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Physical Interoperability Scenarios Single Protocol RSE & OBU AGENCY A AGENCY B FACILITY FACILITY RSE TYPE RSE TYPE 1 1 CUSTOMER CUSTOMER CUSTOMER CUSTOMER WITH AGENCY A OBU WITH AGENCY B OBU WITH AGENCY A OBU WITH AGENCY B OBU OBU TYPE OBU TYPE OBU TYPE OBU TYPE 1 1 1 1 ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 11
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Physical Interoperability Scenarios Multi-Protocol OBU AGENCY A AGENCY B FACILITY FACILITY RSE TYPE RSE TYPE 1 2 CUSTOMER CUS CUSTOME CUSTOMER CUSTOMER CUSTOMER CUSTOMER WITH AGENCY A OBU WITH AGENCY B OBU WITH AGENCY B OBU WITH AGENCY A OBU WITH AGENCY B OBU OBU TYPE OBU TYPE OBU TYPE OBU TYPE OBU TYPE 1 / 2 1 / 2 ½ 1 / 2 1 / 2 ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 12
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Physical Interoperability Scenarios Multi-Protocol RSE AGENCY A AGENCY B FACILITY FACILITY RSE TYPE RSE TYPE 1 / 2 1 / 2 CUSTOMER CUSTOMER CUSTOMER CUSTOMER WITH AGENCY A OBU WITH AGENCY B OBU WITH AGENCY A OBU WITH AGENCY B OBU OBU TYPE OBU TYPE OBU TYPE OBU TYPE 1 2 1 2 ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 13
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Physical Interoperability Scenarios Two Protocols in Parallel AGENCY A AGENCY B FACILITY FACILITY RSE RSE RSE RSE TYPE TYPE TYPE TYPE 3 1 3 1 CUSTOMER CUSTOMER CUSTOMER CUSTOMER WITH AGENCY A OBU WITH AGENCY B OBU WITH AGENCY A OBU WITH AGENCY B OBU OBU TYPE OBU TYPE OBU TYPE OBU TYPE 3 1 3 1 ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 14
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Implementing Interoperability There are essentially three layers of interoperability: Physical: The physical layer refers to the OBU and RSE devices and the extent to which these are interoperable between facilities. To say that two facilities or agencies have physical interoperability Convenience assumes that customers have one device Business Process per vehicle, which can be read at either Interoperability agency’s facilities. ce: Back offi ce interoperability Back Offi - Back Offi ce involves the establishment of agreements Cost between agencies for sharing OBU status Interoperability and transactions, and subsequently settling payments if applicable. - Complexity Physical Interoperability Business: At the business layer, agencies agree to operate under coordinated business rules to improve their effi ciency as well as simplicity for the customer. ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 15
IBI GROUP RFID INTEROPERABILITY BEST PRACTICE GUIDELINE Back-Office Interoperability Scenarios Multiple Back Offi ce and Customer Service / Peer-to-Peer Connection AGENCY A AGENCY B CUSTOMERS OF CUSTOMERS OF FACILITY FACILITY AGENCY A / B AGENCY A / B TOLL TRANSACTIONS TOLL TRANSACTIONS CUSTOMERS CUSTOMERS REGISTERED REGISTERED OBU STATUS OBU STATUS WITH AGENCY WITH AGENCY A B I OB N N O F O I B T T R I A N L M M L E M / A R S T O E T I A O F T N A P T N T T A E I N S Y M E / M L E M L E N Y I N T B A T P AGENCY A AGENCY B TOLL OLL TRANSACTIONS BO / CSV BO / CSV FINANCIAL SE SETTLEMENT ITS CANADA ANNUAL CONFERENCE & GENERAL MEETING TORONTO 2013 MAY 26 TO 29 16
Recommend
More recommend
