Department of Transportation

http://www.dot.gov/

Milestone 7 - May 31st 2015

OMB Review In Progress: OMB is currently reviewing the agency for this milestone. This review status indicator will change once the review is complete.

Leading Indicators

These indicators are reviewed by the Office of Management and Budget

Review Status in-progress
Reviewer Rebecca Williams
Last Updated July 23, 2015, 1:38 am EDT by Rebecca Williams

Assessment Summary

EDI: Public? Yes. Redacted/Rights? Yes. License included? 28.8%

PDL: APIs? License? [issues with crawls]

Public Engagement: Feedback Mechanism? Announcements are set up, but a clear way for citizens to engage with prioritizing data improvements does not appear on the /data or /digital-strategy pages.

Privacy & Security:

Human Capital:

Use & Impact:

Inventory Composition

Public Dataset Status

Best Practice: Department of Transportation has been highlighted for demonstrating a best practice on the Enterprise Data Inventory indicator

Status Indicator Automated Metrics
Overall Progress this Milestone
Inventory Updated this Quarter
3429 Number of Datasets
32 Number of APIs
Schedule Delivered Crawl details
14 Bureaus represented
28 Programs represented
1644 Number of public datasets
1284 Number of restricted public datasets
46 Number of non-public datasets
Inventory > Public listing
+.005% Percentage growth in records since last quarter
278 Spot Check - datasets listed by search engine
Agency provides a public Enterprise Data Inventory on Data.gov
28.8% License specified Crawl details
Status Indicator Automated Metrics
Overall Progress this Milestone
3429 Number of Datasets Crawl details
Number of Collections Crawl details
2868 Number of Public Datasets with File Downloads Crawl details
32 Number of APIs Crawl details
3071 Total number of access and download links Crawl details
Quality Check: Links are sufficiently working Crawl details
Quality Check: Accessible links Crawl details
Quality Check: Redirected links Crawl details
Quality Check: Error links Crawl details
Quality Check: Broken links Crawl details
+.005% Percentage growth in records since last quarter
100% Valid Metadata Crawl details
/data exists Crawl details
/data.json Crawl details
Harvested by data.gov
Views on data.gov for the quarter
Status Indicator Automated Metrics
Overall Progress this Milestone
Description of feedback mechanism delivered Crawl details
Data release is prioritized through public engagement
Feedback loop is closed, 2 way communication
See below Link to or description of Feedback Mechanism
http://www.transportation.gov/data

Best Practice: Department of Transportation has been highlighted for demonstrating a best practice on the Privacy & Security indicator

Status Indicator Automated Metrics
Overall Progress this Milestone
Data Publication Process Delivered Crawl details
Information that should not to be made public is documented with agency's OGC
Status Indicator Automated Metrics
Overall Progress this Milestone
See below Open Data Primary Point of Contact
Daniel.Morgan@dot.gov
POCs identified for required responsibilities
Status Indicator Automated Metrics
Overall Progress this Milestone
Identified 5 data improvements for this quarter
See below Primary Uses
Many of the uses of DOT’s data support our Agency Priority Goals in safety.
Value or impact of data
See below Primary data discovery channels
Because DOT has been making a great deal of data available to the public for many years, we find that our users are primarily finding data through our agency Web sites.
See below User suggestions on improving data usability
Users are generally satisfied with our data, and are encouraged by our recent efforts to build Web services for some of our more popular data sets – an effort we began as part of the Digital Government Strategy implementation. Users encouraged DOT to identify additional opportunities to build Web services to serve up our data. In addition, users thought it would be useful for news articles and press releases on DOT Web sites to include references to underlying data sets and encouraged DOT to make agency subject matter expert contact information as clear as possible.
See below User suggestions on additional data releases
In general, users did not have suggestions for additional agency data to release. Users did have suggestions for data sets that they would like to see State and local transportation and transit agencies make open and available.
Digital Analytics Program on /data

Automated Metrics

These metrics are generated by an automated analysis that runs every 24 hours until the end of the quarter at which point they become a historical snapshot

data.json
Expected Data.json URL http://www.dot.gov/data.json (From USA.gov Directory)
Resolved Data.json URL http://www.dot.gov/sites/dot.gov/files/docs/data.json
Number of Redirects 1 redirects
HTTP Status 200
Content Type application/json
Valid JSON Valid
Datasets with Valid Metadata 100%(3429 of 3429)
Valid Schema Valid
Datasets 3429
Datasets with Distribution URLs 84.6% (2900 of 3429)
Datasets with Download URLs 83.6% (2868 of 3429)
Total Distribution URLs 3071
Total Download URLs 3039
Total APIs 32
Public Datasets 1639
Restricted Public Datasets 1284
Non-public Datasets 506
Bureaus Represented 14
Programs Represented 28
License Specified 28.8% (987 of 3429)
Datasets with Redactions 0.0% (0 of 3429)
Redactions without explanation (rights field) 0.0% (0 of 3429)
File Size 4.77MB
Last modified Friday, 29-May-2015 14:19:19 EDT
Last crawl Sunday, 31-May-2015 00:21:38 EDT
Analyze archive copies Analyze archive from 2015-05-31
Nearby Daily Crawls
/data page
Expected /data URL http://www.dot.gov/data (From USA.gov Directory)
Resolved /data URL http://www.dot.gov/data
Redirects
HTTP Status 200
Content Type text/html; charset=utf-8
Last modified Saturday, 30-May-2015 23:52:40 EDT
Last crawl Sunday, 31-May-2015 00:20:58 EDT
/digitalstrategy.json
Expected /digitalstrategy.json URL http://www.dot.gov/digitalstrategy.json (From USA.gov Directory)
Resolved /digitalstrategy.json URL http://www.dot.gov/sites/dot.dev/files/docs/digitalstrategy.json
Redirects 1 redirects
HTTP Status 200
Content Type application/json
Valid JSON Valid
Last modified Thursday, 12-Dec-2013 17:06:46 EST
Last crawl Sunday, 31-May-2015 00:20:58 EDT
Digital Strategy

Date specified: Wednesday, 27-Nov-2013 12:38:47 EST

Date of digitalstrategy.json file: Thursday, 12-Dec-2013 17:06:46 EST

1.2.4 Develop Data Inventory Schedule - Summary

Summarize the Inventory Schedule


The Department of Transportation (DOT) approach to ensuring all data assets from each bureau and program in the agency will be identified and accounted for in its Enterprise Data Inventory is focused on linking various information management programs together. Specifically, the DOT Enterprise Data Inventory is considered complete when each of its Operating Administrations (OAs) has accounted for all datasets that are:
•	collected under an OMB-approved Information Collection Request
•	contained in Records Disposition Schedules (RDS) and Electronic Information Systems (EIS) list
•	covered by a Privacy Act System of Records Notice (SORN)
•	associated with an information technology (IT) investment reported on the Exhibit 53
Each OA will register all datasets in the DOT metadata registry. 

The DOT Enterprise Data Inventory schedule takes a methodical approach to completing the task. Each DOT Operating Administration (OA) will review data from each of its information management programs to identify a complete list of information collections, record schedules, and IT investments that contain data. Once the list is complete, OAs will proceed with inventorying the datasets contained in those information systems. The milestones are:

1.2.5 Develop Data Inventory Schedule - Milestones

TitleDevelop OA implementation plan
DescriptionEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
Milestone DateJanuary 17, 2014
Description of how this milestone expands the InventoryEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
Description of how this milestone enriches the InventoryEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
Description of how this milestone opens the InventoryEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
TitleInventory public datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Milestone DateFebruary 28, 2014
Description of how this milestone expands the InventoryEach DOT OA will analyze the data from its information management programs to identify those that contain data and will gather any information regarding the releasability of those datasets.
Description of how this milestone enriches the InventoryEach DOT OA will analyze the data from its information management programs to identify those that contain data and will gather any information regarding the releasability of those datasets.
Description of how this milestone opens the InventoryEach DOT OA will analyze the data from its information management programs to identify those that contain data and will gather any information regarding the releasability of those datasets.
TitleInventory public datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Milestone DateApril 28, 2014
Description of how this milestone expands the InventoryUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Description of how this milestone enriches the InventoryUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Description of how this milestone opens the InventoryUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
TitleInventory mission-oriented datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable..
Milestone DateJune 30, 2014
Description of how this milestone expands the InventoryUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone enriches the InventoryUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone opens the InventoryUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
TitleInventory administrative datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Milestone DateSeptember 29, 2013
Description of how this milestone expands the InventoryUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone enriches the InventoryUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone opens the InventoryUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.

1.2.6 Develop Customer Feedback Process

Describe the agency's process to engage with customers


Engagement is a core value at DOT and is integral in our decision-making process. The Department has hosted 170 roundtable sessions throughout the country over the last year. In September 2011, DOT hosted a Public Meeting to discuss how to connect public and private organizations through a Digital Transportation Exchange designed to find innovative ways to better serve the public. In addition, with the launch of Safety.Data.gov, we played a leading role in a White House session to identify potential apps and data needs relating to Safety. The event included a Data Jam to select apps for development and to form teams to identify necessary steps. Finally, in July 2010, President Obama signed into law P.L. 112-141, Moving Ahead for Progress in the 21st Century Act (MAP-21). This legislation will transform the policy and programmatic framework for investments to guide system growth and development.  In addition to these in-person engagement methods, DOT has established an email address, opendata@dot.gov, to receive feedback from data users. We are also establishing a listserv for developers and data users to announcements about open data at DOT.

1.2.7 Develop Data Publication Process

Describe the agency's data publication process


The DOT uses our Departmental Data Release Policy (DOT Order 1351.34) as a guide for disseminating data sets. This policy addresses protections for security, privacy, confidentiality, and other traditional concerns that may warrant redaction of some information in our datasets. Identification of a data set does not mean that DOT will release the entire data set without appropriate redactions. We regularly update the DOT data inventory to reflect the Department’s data inventory activities and release management capabilities. We continue to focus on Open Government and recently hosted a Datapalooza at the Department.

The Departmental Data Release Policy sets the default state of DOT data to open by stating, DOT policy is to make data available at the most detailed level possible, subject only to the limits imposed by data quality and the need to protect national/homeland security, individual privacy, and confidentiality. Further, the policy states, DOT policy is to disseminate data as soon as possible following collection, subject only to the limits imposed by resources, technology, authority, regulation and data quality while protecting security, privacy, and confidentiality. DOT has existing processes for performing pre-dissemination reviews and public disclosure risk assessments. Regardless of the releasability of a dataset, that dataset much be registered in the DOT data inventory.