E-Squared Engineering

 CVO Fair Info

Home
Up   

Fair Information Principles for ITS/CVO

The following principles pertain to privacy issues facing the deployment of ITS in the trucking and motorcoach industry.  They have been copied from the ITS America website and are presented in their entirety.

E-Squared Engineering

-------------------------------------------------------------------------------------

Fair Information Principles for ITS/CVO

These fair information principles were prepared in recognition of the importance of protecting individual privacy in implementing Intelligent Transportation Systems (ITS) for Commercial Vehicle Operations (CVO). They have been adopted by the ITS America CVO Technical Committee.

These principles represent values and are designed to be flexible and durable to accommodate a broad scope of technological, social, and cultural change. ITS America may, however, need to revisit them periodically to assure their applicability and effectiveness.

These principles are advisory, intended to educate and guide transportation professionals, policy-makers, and the public as they develop fair information and privacy guidelines for specific ITS/CVO projects. They are not intended to supersede existing statutes or regulations. Initiators of ITS/CVO projects are urged to publish the fair information principles that they intend to follow. Parties to ITS/CVO projects are urged to include enforceable provisions for safeguarding privacy in their contracts and agreements.

 

FIP #1: Privacy

The reasonable expectation of privacy regarding access to and use of personal information should be assured. The parties must be reasonable in collecting data and protecting the confidentiality of that data.

FIP #2: Integrity

Information should be protected from improper alteration or improper destruction.

FIP #3: Quality

Information shall be accurate, up-to-date, and relevant for the purposes for which it is provided and used.

FIP #4: Minimization

Only the minimum amount of relevant information necessary for ITS applications shall be collected; data shall be retained for the minimum possible amount of time.

FIP #5: Accountability

Access to data shall be controlled and tracked; civil and criminal sanctions should be imposed for improper access, manipulation, or disclosure, as well as for knowledge of such actions by others.

FIP #6: Visibility

There shall be disclosure to the information providers of what data are being collected, how they are collected, who has access to the data, and how the data will be used.

FIP #7: Anonymity

Data shall not be collected with individual driver identifying information, to the extent possible.

FIP #8: Design

Security should be designed into systems from the beginning, at a system architecture level.

FIP #9: Technology

Data encryption and other security technologies shall be used to make data worthless to unauthorized users.

FIP #10: Use

Data collected through ITS applications should be used only for the purposes that were publicly disclosed.

FIP #11: Secondary Use

Data collected by the private sector for its own purposes through a voluntary investment in technology should not be used for enforcement purposes without the carrier's consent.


Date approved by the Board of Directors: April 22, 1999


Note: These guiding principles address only issues of privacy and data control. They do not address all issues related to concepts of operations or interoperability. These issues are addressed in separate guiding principles.

------------------------------------------------------------------------

If you have any questions concerning these guiding principles, send us an email.  If we can’t answer your questions, we’ll tell you who can.  (see the home page for contact information)

 

...helping you experience tomorrow's technology - today...

Home ] Up ]

Send mail to E-Squared Engineering Webmaster with questions or comments about this web site.
Copyright © 1999 E-Squared Engineering - Photos are not to be copied/used without permission from E-Squared Engineering
Last modified: November 23, 2004