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
| Title | Develop OA implementation plan |
|---|
| Description | Each 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 Date | January 17, 2014 |
|---|
| Description of how this milestone expands the Inventory | Each 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 Inventory | Each 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 Inventory | Each DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs. |
|---|
| Title | Inventory public datasets |
|---|
| Description | Using the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry. |
|---|
| Milestone Date | February 28, 2014 |
|---|
| Description of how this milestone expands the Inventory | Each 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 Inventory | Each 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 Inventory | Each 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. |
|---|
| Title | Inventory public datasets |
|---|
| Description | Using the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry. |
|---|
| Milestone Date | April 28, 2014 |
|---|
| Description of how this milestone expands the Inventory | Using 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 Inventory | Using 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 Inventory | Using the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry. |
|---|
| Title | Inventory mission-oriented datasets |
|---|
| Description | Using 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 Date | June 30, 2014 |
|---|
| Description of how this milestone expands the Inventory | Using 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 Inventory | Using 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 Inventory | Using 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. |
|---|
| Title | Inventory administrative datasets |
|---|
| Description | Using 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 Date | September 29, 2013 |
|---|
| Description of how this milestone expands the Inventory | Using 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 Inventory | Using 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 Inventory | Using 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.