intellibackground2.jpg
‹#›
Definition of Open Data/Open Source
Why?  Philosophy: Gather once, reuse many times
•Cost savings
•Better quality, higher reliability, more flexibility, lower cost.
•Open systems vs. proprietary systems
How?
•Use of Open Source Licenses – Granting rights in support of a balance between collaboration and commercialization
•Acquisitions – Identifying requirements and restrictions/limitations in contract language
•Use of ITS Standards
•
Let me talk a little about why we are doing this and how we plan to implement it.  I think our objective is evident to those who have pursued open data/ open source before.  If done right, we provide ourselves with cost savings, faster development time, and more robust products.  Additionally, we – meaning all of us and users and consumers – benefit from new and innovative applications that are open and can be used anywhere, at any time.

So, to do this right, we need to think about how we use licenses, how we acquire data and code, and how we ensure the use of ITS standards.  The important points for each of these, we think, are listed on this slide: getting the balance right with regard to rights and licenses, ensuring that there are no or limited (for good purpose) restrictions on any data that will reside in these environments, and getting agreement on the use of ITS standards.

The following presentations will address some of these issues, and we want to hear your thoughts on these subjects after the presentations.  Before we move on, I want to highlight some of our initial analysis.

With that in the background, the rest of our panel presenters will discuss how Open Data and/or Open Source has worked for their programs and agencies.