HVTT11 International heavy vehicle symposium Electronic Work Diary for Heavy Vehicle Fatigue monitoring in Australia Shaun Talko Senior Engineer March 2010 1 HVTT11 – EWD FOR FATIGUE IN AUSTRALIA Agenda 1. 2. 3. 4. 5. 6. 2 Why an electronic work diary Approach / project schedule Requirements PWD Considerations Next steps WHY AN ELECTRONIC WORK DIARY? A paper work diary: DRIVER OPERATOR AUTHORITY IS SINGLE USE IS NOT TRUSTWORTHY CAN CONFLICT WITH ELECTRONIC DATA IS EVIDENTIARY IS PORTABLE IS STANDARDISED 3 COURTS APPROACH S P E C 4 P O L I C Y PROJECT SCHEDULE 5 REQUIREMENTS FOR EWD 6 PAPER WORK DIARY PROCESS DESIGN PURCHASE DELIVER RETAIL REPLACE IDENTIFICATION AUTHENICATION READABLE WRITABLE TECH-FREE UNBREAKABLE INTEROPERABLE RELIABLE 7 LOW INTEGRITY PWD vs EWD? PAPER WORK DIARY ELECTRONIC WORK DIARY Allocation Allocation Authentication (signature) Authentication (electronic) Records – no deletion Records – security Records - difficult to change System - Tamper evident Records duplication (paper) Records duplication (electronic) Always operational EWD is ‘looked after’ Interoperable – same for all users Interoperable - storage and format Portable diary 8 Portable records PWD vs EWD? Equivalent • Possible? • What would this achieve? • Each has strengths / weakness Not Equivalent • Recording of time • Recording of location 9 EWD AND IAP? Different Specifications 10 EWD IAP work and rest periods access compliance REGULATORY APPLICATIONS APPLICATIONS Access Fatigue Speed Core platform 12 Mass PERFORMANCE BASED Philosophy • Performance based requirements (output driven) • Prescribed only where necessary • Available for industry 13 PRESCRIPTION? MULTIPLE STATES MULTIPLE AGENCIES MULTIPLE OFFICERS MULTIPLE OPERATORS MULTIPLE VEHICLES EWD 14 TRANSITION? PAPER WORK DIARY COMMERCIAL ELECTRONIC SYSTEMS TRANSITIONAL EWD PILOT 15 EWD REFINE NEXT STEPS 1. APPROVAL FROM AUSTROADS 2. CONSULTATION – IN EACH PARTICIPATING STATE 3. FINALISATION OF SPECIFICATION 16 GENERAL Questions and discussion Shaun Talko shaunt@tca.gov.au 17