Digital Government Strategy Report for the Department of Transportation
2.1. Engage with customers to identify at least two existing major customer-facing services that contain high-value data or content as first-move candidates to make compliant with new open data, content, and web API policy.
Overall Status: completed
2.1.1. Paragraph on customer engagement approach
Paragraph on customer engagement approach: Engagement is a core value at DOT and is integral to 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. We have created dialogues with the public around the new legislation through five webinars. We are hosting additional sessions over the next couple of weeks. Our engagement efforts have identified clear themes and areas for improved collaboration and data transparency. DOT’s number one priority is safety. Safety has also emerged as the most important issue for many of our stakeholders. Therefore, we have chosen to prioritize safety apps and APIs such as car safety information; rail injury reports; and information on railroad crossings.
2.1.2. Prioritized list of systems (datasets)
System Name: Federal Railroad Administration 10 Year Accident Reports
System Description: The 10-Year Accident/Incident Report, one of the most requested reports on the Federal Railroad Administration’s website, provides historical statistics on rail-related train accidents, injuries and fatalities, highway-rail crossing collisions and operational information. We will create an API to render all this information in a user-interactive dashboard program.
System Scope: both
Main Customer: Rail Stakeholders, Inspectors, Citizens
Unique Investment Identifier: 021-961146316--FRAXX013: Railroad Network System
System Name: SaferCar.gov Recall and Complaint Data
System Description: The National Highway Transportation Safety Administration will make vehicle safety data available in API format. Specifically, we will create an app with safety-related complaints about motor vehicles and motor vehicle equipment, including vehicle make, model and year. We will also create an API with recall data for vehicle products that have safety-related defects or do not comply with federal motor vehicle safety standards.
System Scope: both
Main Customer: Citizens, safety stakeholders, industry
Unique Investment Identifier: 021-777552743--NHTSA020: Artemis
7.1. Engage with customers to identify at least two existing priority customer-facing services to optimize for mobile use.
Overall Status: completed
7.1.1. Paragraph on customer engagement approach
Paragraph on customer engagement approach: 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. We have created dialogues with the public around the new legislation through five webinars. We are hosting additional sessions over the next couple of weeks. Our engagement efforts have identified clear themes and areas for improved collaboration and data transparency. DOT’s number one priority is safety. Safety has also emerged as the most important issue for many of our stakeholders. Therefore, we have chosen to prioritize safety apps and APIs such as car safety information; rail injury reports; and information on railroad crossings.
7.1.2. Prioritized list of systems (datasets)
System Name: SaferCar App
System Description: DOT created a user-friendly iOS smartphone product to streamline access to information on SaferCar.gov, including vehicle 5-star safety ratings; vehicle defects; and the Child Safety Seat Locator. The app will also allow consumers to search and submit vehicle complaints
System Scope: both
Main Customer: Citizens, safety stakeholders, industry
Unique Investment Identifier: 021-777552743--NHTSA020: Artemis
System Name: SaferBus App
System Description: : Federal Motor Carrier Safety Administration developed an android version of their iOS application that provides users to search for Bus Company Operating Authority and Insurance, view Bus Safety Performance Records and Bus Company Safety Results. Users can also report a complaint
System Scope: both
Main Customer: Citizens, safety stakeholders, industry
Unique Investment Identifier: 021-734121151--FMCSA100: Application and Information
4.2. Establish an agency-wide governance structure for developing and delivering digital services
Overall Status: in-progress
Paragraph on Governance: At the Department of Transportation (DOT), we strive to deliver digital information in useful and customer friendly ways across a variety of digital channels. Our goal is for all digital content to: • Clearly represent our mission and objectives • Incorporate stakeholder and customer feedback • Contribute to an efficient and useful digital presence. As part of the Digital Government Strategy, we’re updating and formalizing the Department’s Digital Governance Structure. We’re making these changes within the broader context of updating the Department’s entire IT Governance.
URL to Governance Document: http://www.dot.gov/mission/web-governance-overview
5.2. Develop an enterprise-wide inventory of mobile devices and wireless service contracts
Overall Status: completed
5.2.1. Develop wireless and mobile inventory
Bureau/Component: Bureau 02100
Inventory Status: completed
8.2. Implement performance and customer satisfaction measuring tools on all .gov websites
Overall Status: in-progress
8.2.1. Implement performance measurement tool
Implemented Digital Analytics Program: yes
If Not, Describe Implementation: The Department of Transportation is in the process of implementing the Digital Analytics Program Google Analytics solution on all Departmental websites. The majority of the main DOT websites have implemented the code and the remainder will be implemented over the coming months.
Percent of websites covered: 68
URL of performance data: n/a
8.2.2. Implement customer satisfaction tool
Describe Implementation: We are currently collecting customer satisfaction data on approximately half of our websites, including the main DOT.gov website. The OCIO is providing guidance to our component OAs as they incorporate the Customer Satisfaction metrics on their websites. We continue to expand our existing Customer Service Metrics tools to collect information on additional websites. . Some of our OAs will be working with our procurement office to acquire the appropriate tools and we are looking into enterprise wide solutions. In some cases, they may also need to engage the Paperwork Reduction Act Clearance process. The OCIO will continue to work with the website owners to ensure implementation on all sites. This is a significant update, which may have associated implementation costs. Recently, an additional Operating Administration began collecting customer satisfaction data.
URL of performance data: n/a
1.2. Ensure all new IT systems follow the open data, content, and web API policy and operationalize agency.gov/developer pages
Overall Status: in-progress
1.2.1. Document policy for architecting new IT systems for openness by default
Describe policy: The DOT uses our Departmental Data Release Policy (DOT Order 1351.34) as a guide for disseminating high-value 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 high-value 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.
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.
2.2. Make high-value data and content in at least two existing, major customer-facing systems available through web APIs, apply metadata tagging and publish a plan to transition additional high-value systems
Overall Status: completed
2.2.1. Publish plan on future activity
Describe policy: We are modernizing existing systems to leverage web APIs by establishing standards in our EA and evaluating all new systems and substantial modernization efforts against the future architecture. Our future architecture contains the following characteristics:
• Establish common data based on authoritative data sources that is interoperable across the enterprise
• Provide the capability for program managers to discover authoritative data sources for common data
• Drive DOT to create systems that are interoperable and ready to share data.
Data and technology standards should foster open access to and ready consumption of DOT mission services for the benefit of its customers.
Data and information exchange will be based on open standards.
Information sharing and protection policies will be established and referenced in information sharing agreements.
• Consist of well documented interfaces built on non-proprietary open platforms using platform independent protocols such as XML.
2.2.2. Make 2+ systems (datasets) available via web APIs with metadata tags
Name of system: Federal Railroad Administration 10 Year Accident Reports
Description of system: The 10-Year Accident/Incident Report, one of the most requested reports on the Federal Railroad Administration’s website, provides historical statistics on rail-related train accidents, injuries and fatalities, highway-rail crossing collisions and operational information. We created APIs to render all this information in a user-interactive dashboard program.
Scope of system: both
Main Customers: Rail Stakeholders, Inspectors, Citizens
Unique Investment Identifier: 021-961146316--FRAXX013: Railroad Network System
API Link: https://safetydata.fra.dot.gov/MasterWebService/FRASafetyDataAPIs.aspx
Name of system: SaferCar.gov Recall and Complaint Data
Description of system: The National Highway Transportation Safety Administration made vehicle safety data available in API format. Specifically, we created an app with safety-related complaints about motor vehicles and motor vehicle equipment, including vehicle make, model and year. We also created an API with recall data for vehicle products that have safety-related defects or do not comply with federal motor vehicle safety standards.
Scope of system: both
Main Customers: Citizens, safety stakeholders, industry
Unique Investment Identifier: 021-777552743--NHTSA020: Artemis
API Link: http://www.nhtsa.gov/webapi/Default.aspx
5.3. Evaluate the government-wide contract vehicles in the alternatives analysis for all new mobile-related procurements
Overall Status: in-progress
Describe Implementation: Wireless contracts are a priority strategic sourcing area for the Department to increase efficency and effectiveness. We have an inter-agency group responsible for this initiative and once available; we plan to consider leveraging the GSA vehicle.
6.3. Ensure all new digital services follow digital services and customer experience improvement guidelines
Overall Status: in-progress
Describe Implementation: We are actively working with the all of the Department’s Web and new media leads through our Web Community of Interest (COI) to disseminate best practices and provide opportunities for training and discussion. Through our Web Community of Interest, we have regular meetings with representatives from each of the DOT Operating Administrations. We have also established an accessibility working group with web and business representatives from each of the DOT Operations Administrations. This working group is identifying challenges and potential solutions to addressing accessibility goals on an enterprise level.” to ensure all Departmental websites meet accessibility standards.
We have also implemented Google Analytics on most of DOT’s .gov domains. We have developed custom reports for many offices to ensure they are using the analytics to the fullest extent possible. We are also pursuing an enterprise approach to customer feedback based on the American Customer Satisfaction Index (ACSI),
We have redesigned our DOT.gov website on an open-source Content Management System. The website makes use of responsive design. This enables the site to adapt to virtually any screen size. The design also includes enhanced user experience features, accessibility checkpoints and workflow. We have made this Content Management System available across the Department, and are planning to migrate other DOT websites to this platform. As additional websites take advantage of this new platform, the websites will benefit from these shared enhancements.
We are also actively using our internal communications portal to promote standards and guidance. We have developed content and style guides, and we communicate regularly across the Department on the importance of best practices, such Plain Language. We offer Content Management System (CMS) users regular tips for improving their content and the usability of their websites.
7.2. Optimize at least two existing priority customer-facing services for mobile use and publish a plan for improving additional existing services
Overall Status: in-progress
Describe Implementation: We are optimizing existing systems for mobile use by establishing standards in our EA and evaluating all new systems and substantial modernization efforts against the future architecture. Our future architecture contains the following characteristics:
• Establish common data based on authoritative data sources that is interoperable across the enterprise
• Provide the capability for program managers to discover authoritative data sources for common data
• Drive DOT to create systems that are interoperable and ready to share data.
Data and technology standards should foster open access to and ready consumption of DOT mission services for the benefit of its customers.
Data and information exchange will be based on open standards.
Information sharing and protection policies will be established and referenced in information sharing agreements.
• Consist of well documented interfaces built on non-proprietary open platforms using platform independent protocols such as XML.
7.2.1. Report on services
Service Name: Safer Car App
Service Description: DOT created a user-friendly iOS smartphone product to streamline access to information on SaferCar.gov, including vehicle 5-star safety ratings; vehicle defects; and the Child Safety Seat Locator. The app will also allow consumers to search and submit vehicle complaints
System Scope: both
Primary customers: Citizens, safety stakeholders, industry
Unique Investment Identifier: 021-777552743--NHTSA020: Artemis
URL of service: https://itunes.apple.com/us/app/safercar/id593086230?ls=1&mt=8
Service Name: SaferBus App
Service Description: Federal Motor Carrier Safety Administration developed an android version of their iOS and updated their iOS application that enables users to search for Bus Company Operating Authority and Insurance, view Bus Safety Performance Records and Bus Company Safety Results. Users can also report a complaint
System Scope: both
Primary customers: Citizens, safety stakeholders, industry
Unique Investment Identifier: 021-734121151--FMCSA100: Application and Information
URL of service: http://www.fmcsa.dot.gov/safety-security/saferbus/saferbus.aspx
Last updated November 11, 2013 at 12:38 pm