1. 1 U.S. Department of Transportation Overview of the Open Source Application Development Portal (OSADP) OSADP: http://www.itsforge.nethttp://www.itsforge.net

2. 2 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP Overview  Purpose: web-based access & collaboration on source code & documentation for open source transportation applications  Objectives: □ Promote reusing of software wherever possible □ Transparent application development □ Provide complete application package □ Collaborative development  Features: □ Resources to use & download applications □ Forums for discussions on applications (e.g., collaboration) □ Platform to test (GitHub) applications before posting □ Developer uploader guide & submittal (e.g., upload)

3. 3 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP Applications  Total Number of Applications: 43  Types: □ FHWA Intelligent Transportation Systems Dynamic Mobility Applications ▪Connect vehicles to the roadside and individual devices. ▪Facilitate sharing of valuable safety, mobility, and environmental information over a wireless communications network. ▪Enable collection and dissemination of transportation data and make travel not only safer, but smarter and greener. □ Non-ITS Device Applications: ▪Facilitate prototyping and performance measurement ▪Enable data management and sharing □ Data Applications: ▪Data capture and processing □ Commercial Vehicle Applications ▪Enable safety and operations improvements

4. 4 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP and ITS Application Categories  Arterial Management  Collision Avoidance  Commercial Vehicle Operations  Crash Prevention and Safety  Driver Assistance  Electronic Payment and Pricing  Emergency Management  Freeway Management  Information Management  Intermodal Freight  Road Weather Management  Roadway Operations and Maintenance  Traffic Incident Management  Transit Management  Traveler Information

5. 5 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP Sample Applications  ITS DMA projects: Freight Advanced Traveler Information System (FRATIS), Intelligent Network Flow Optimization (INFLO), Cooperative Adaptive Cruise Control (CACC), Response, Emergency Staging, Communication, Uniform Management, and Evacuation (RESCUEME), Integrated Dynamic Transit Operations (IDTO)  Non-ITS Device Applications: Performance Measure Application, Trajectory Converter Analysis (TCA), Co-Pilot, Prototype Operational Data Environment (P-ODE), CACC-VISSIM, VISSIM External Driver Model Add-on for Connected and Automated Vehicles (VEDM-CAV), BSMDE Measures Estimation, Road Weather Performance Measures  Data Applications: Signal Phase and Timing (SPaT), Retrofit Safety Device (RSD), Connected Vehicle Dedicated Short Range Communication (CV-DSRC) message parser  Commercial Vehicle Applications: Cross-Town Improvement Program Drayage Optimization (C-TIP), Smart Roadside Initiative (SRI) mobile application for drivers and enforcement officers.  Coming soon: □ TCA 2.4 □ Multi-Modal Intelligent Signal System (MMITSS) –California □ CACC 1.2

6. 6 U.S. Department of Transportation Access the OSADP at www.itsforge.net How to Download Applications  Only registered users able to download application on OSADP  Access applications on ‘applications/download’ page  All applications download directly to your machine

7. 7 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP – Who Can Submit Tools?  Anyone can submit software, tools or applications for consideration (e.g., testing, license, documentation)  Priority for posting software & tools developed on ITS Program & FHWA sponsored projects  Other software, tools or applications are encouraged to be submitted and will be evaluated on case-by-case basis

8. 8 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP – Tool Submission Guidelines  Required: □ Source code □ Web ready documentation (e.g, 508 compliant files) □ README file (e.g., version number, description, install instructions) □ License – open source license file □ Notes files – features to release, description of data inputs & outputs □ Documentation or links to (e.g., ConOps, architecture, configuration management plan, installation and users instructions)  Optional: □ Test or sample files to run with the software □ Attribution file

9. 9 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP 2.0 DevelopmentSubsystem GitHub Users Project Admin Technical Review Release Process Collaborative App Development Environment Github Authorized Collaborators OSADP Private Repositories Portal Manager App Install / Use Public Portal Community Portal Visitors High-level project information Invitation to join community Released Apps R.n R1 R3 R2 r.n r1 r2 r3 In-development Apps RELEASE Discussion Idea exchange Feedback Comments Suggestions Become a Github user and request access to a private project Registered Users

10. 10 U.S. Department of Transportation Access the OSADP at www.itsforge.net Application Upload Process  Upload Request □ Terms and conditions □ Access Request Form  Required files: □ Source code or assets □ README.txt gives user a brief summary of the open source package □ RELEASE-NOTES.txt describes incremental difference of this release and associated instructions □ LICENSE.txt declares the license that this open source is released under □ ATTRIBUTION.txt acknowledges or gives credits to individuals, a group, or an organization that have contributed to the open source  Optional: □ User guide and/or Instructions □ Project Documentation (Final Reports or Systems Engineering documentation)

11. 11 U.S. Department of Transportation Access the OSADP at www.itsforge.net Using GitHub  GitHub is the OSADP staging environment: □ Provides flexible infrastructure for open source software collaboration & staging/vetting  OSADP uses private repositories on GitHub: □ Application uploader must be a registered GitHub user □ OSADP administrator: ▪Invite uploader to access repository to upload code ▪Review & approve applications before releasing on OSADP □ Uploader uses GitHub to: ▪Add code from their computer to repository ▪Access application source code & perform updates

12. 12 U.S. Department of Transportation Access the OSADP at www.itsforge.net Application Requirements – ITS & FHWA Projects  New applications developed on ITS or FHWA funded projects expected to be posted on OSADP: □ Be licensed under an Open Source License (Apache 2.0 preferred) □ New interface applications, code or software □ Portions of enhancements or upgrades considered new  Existing applications incorporated into ITS or FHWA funded projects need not be made open source  Documentation required to support use of applications  Other Open Source Licenses will be considered on a case-by case basis & will consider restrictions unique to each application & expected users  All OSADP users must adhere to terms & conditions in license specific to each application

13. 13 U.S. Department of Transportation Access the OSADP at www.itsforge.net OSADP – Tools Terms of Use Required open source terms and conditions captured within recommended Apache 2.0 Open Source License:  Allows: □ Download and use for free □ Incorporate software in proprietary package you create □ Make changes without having to resubmit as open source  Limits: □ May not redistribute without proper attribution □ Must include License in any redistribution including software/tool □ Must document which files were modified in any new distribution □ Must not use any Trademarks or Logos stating or implying FHWA or any organization endorses software/tool

14. 14 U.S. Department of Transportation Access the OSADP at www.itsforge.net A PACHE 2.0 O PEN S OURCE L ICENSE : O VERVIEW CanCannotMust Download and use for free Incorporate software in proprietary package you create Redistribute without proper attribution Use any Trademarks or Logos that may State that the Organization Endorses your Distribution Include License in any redistribution that includes the software Document which files were modified in any New Distribution Make changes without having to resubmit as open source Restrict use of the software

15. 15 U.S. Department of Transportation Access the OSADP at www.itsforge.net O PEN S OURCE IN THE OSADP  Case 1: New Code, Acceptable Open Source License  Case 2: New Code, Copyright Transferred to USDOT  Case 3: New or Modified Code, Signed Contributor License Agreement  Cases 2&3: The code, if accepted, will be released by USDOT under the Apache 2.0 License

16. 16 U.S. Department of Transportation Access the OSADP at www.itsforge.net Questions OSADP Questions: http://www.itsforge.net/index.php/contact/contact-us http://www.itsforge.net/index.php/contact/contact-us Jon Obenberger, PhD, P.E. Jon.obenberger@dot.gov Senior Transportation Research Engineer FHWA Office of Operations Research and Development