{"agency":"DOT","generated":"2013-05-15 16:10:34","items":[{"id":"2.1","parent":null,"text":"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.","due":"90 Days","due_date":"2012\/08\/21","fields":[{"type":"select","name":"2-1-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"completed"}],"multiple":false},{"id":"2.1.1","parent":"2.1","text":"Paragraph on customer engagement approach","due":"90 days","due_date":"2012\/08\/21","fields":[{"type":"textarea","name":"2-1-1-customer-engagement-approach","label":"Paragraph on customer engagement approach","options":[],"value":"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\u2019s 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. "}],"multiple":false},{"id":"2.1.2","parent":"2.1","text":"Prioritized list of systems (datasets)","due":"90 days","due_date":"2012\/08\/21","fields":[{"type":"text","name":"2-1-2-name","label":"System Name","options":[],"value":["Federal Railroad Administration 10 Year Accident Reports ","SaferCar.gov Recall and Complaint Data "]},{"type":"text","name":"2-1-2-description","label":"System Description","options":[],"value":["The 10-Year Accident\/Incident Report, one of the most requested reports on the Federal Railroad Administration\u2019s 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. ","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."]},{"type":"select","name":"2-1-2-scope","label":"System Scope","options":[{"label":"Internal","value":"internal"},{"label":"External","value":"external"},{"label":"Both","value":"both"}],"value":["both","both"]},{"type":"text","name":"2-1-2-customer","label":"Main Customer","options":[],"value":["Rail Stakeholders, Inspectors, Citizens","Citizens, safety stakeholders, industry "]},{"type":"text","name":"2-1-2-uii","label":"Unique Investment Identifier","options":[],"value":["021-961146316--FRAXX013: Railroad Network System","021-777552743--NHTSA020: Artemis"]}],"multiple":true},{"id":"7.1","parent":null,"text":"Engage with customers to identify at least two existing priority customer-facing services to optimize for mobile use.","due":"90 Days","due_date":"2012\/08\/21","fields":[{"type":"select","name":"7-1-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"completed"}],"multiple":false},{"id":"7.1.1","parent":"7.1","text":"Paragraph on customer engagement approach","due":"90 days","due_date":"2012\/08\/21","fields":[{"type":"textarea","name":"7-1-1-customer-engagement-approach","label":"Paragraph on customer engagement approach","options":[],"value":"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\u2019s 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. "}],"multiple":false},{"id":"7.1.2","parent":"7.1","text":"Prioritized list of systems (datasets)","due":"90 days","due_date":"2012\/08\/21","fields":[{"type":"text","name":"7-1-2-name","label":"System Name","options":[],"value":["SaferCar App","SaferBus App"]},{"type":"text","name":"7-1-2-description","label":"System Description","options":[],"value":["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",": 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"]},{"type":"select","name":"7-1-2-scope","label":"System Scope","options":[{"label":"Internal","value":"internal"},{"label":"External","value":"external"},{"label":"Both","value":"both"}],"value":["both","both"]},{"type":"text","name":"7-1-2-customer","label":"Main Customer","options":[],"value":["Citizens, safety stakeholders, industry","Citizens, safety stakeholders, industry"]},{"type":"text","name":"7-1-2-uii","label":"Unique Investment Identifier","options":[],"value":["021-777552743--NHTSA020: Artemis","021-734121151--FMCSA100: Application and Information"]}],"multiple":true},{"id":"4.2","parent":null,"text":"Establish an agency-wide governance structure for developing and delivering digital services","due":"6 months","due_date":"2012\/11\/23","fields":[{"type":"select","name":"4-2-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"in-progress"},{"type":"textarea","name":"4-2-policy","label":"Paragraph on Governance","options":[],"value":"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: \u2022 Clearly represent our mission and objectives \u2022 Incorporate stakeholder and customer feedback \u2022 Contribute to an efficient and useful digital presence. As part of the Digital Government Strategy, we\u2019re updating and formalizing the Department\u2019s Digital Governance Structure. We\u2019re making these changes within the broader context of updating the Department\u2019s entire IT Governance. "},{"type":"text","name":"4-2-link","label":"URL to Governance Document","options":[],"value":"http:\/\/www.dot.gov\/mission\/web-governance-overview"}],"multiple":false},{"id":"5.2","parent":null,"text":"Develop an enterprise-wide inventory of mobile devices and wireless service contracts","due":"6 months","due_date":"2012\/11\/23","fields":[{"type":"select","name":"5-2-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"completed"}],"multiple":false},{"id":"5.2.1","parent":"5.2","text":"Develop wireless and mobile inventory","due":"6 months","due_date":"2012\/11\/23","fields":[{"type":"text","name":"5-2-1-component","label":"Bureau\/Component","options":[],"value":["Bureau 02100 "]},{"type":"select","name":"5-2-1-inventory-status","label":"Inventory Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":["completed"]}],"multiple":true},{"id":"8.2","parent":null,"text":"Implement performance and customer satisfaction measuring tools on all .gov websites","due":"8 months","due_date":"2013\/1\/22","fields":[{"type":"select","name":"8-2-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"in-progress"}],"multiple":false},{"id":"8.2.1","parent":"8.2","text":"Implement performance measurement tool","due":"8 months","due_date":"2013\/1\/22","fields":[{"type":"select","name":"8-2-1-tool","label":"Implemented Digital Analytics Program","options":[{"label":"Yes","value":"yes"},{"label":"No","value":"no"}],"value":"yes"},{"type":"textarea","name":"8-2-1-implementation","label":"If Not, Describe Implementation","options":[],"value":"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."},{"type":"text","name":"8-2-1-percent","label":"Percent of websites covered","options":[],"value":"68"},{"type":"text","name":"8-2-1-url","label":"URL of performance data","options":[],"value":"n\/a"}],"multiple":false},{"id":"8.2.2","parent":"8.2","text":"Implement customer satisfaction tool","due":"8 months","due_date":"2013\/1\/22","fields":[{"type":"textarea","name":"8-2-2-implementation","label":"Describe Implementation","options":[],"value":"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 will continue to expand our existing Customer Service Metrics tools to collect information on additional websites. This is a significant update, which may have associated implementation costs. 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."},{"type":"text","name":"8-2-2-url","label":"URL of performance data","options":[],"value":"n\/a"}],"multiple":false},{"id":"1.2","parent":null,"text":"Ensure all new IT systems follow the open data, content, and web API policy and operationalize agency.gov\/developer pages","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"select","name":"1-2-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"in-progress"}],"multiple":false},{"id":"1.2.1","parent":"1.2","text":"Document policy for architecting new IT systems for openness by default","due":"6 months","due_date":"2012\/11\/23","fields":[{"type":"textarea","name":"1-2-1-description","label":"Describe policy","options":[],"value":"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\u2019s data inventory activities and release management capabilities. We continue to focus on Open Government and recently hosted a Datapalooza at the Department."}],"multiple":false},{"id":"1.2.3","parent":"1.2","text":"Operationalize Enterprise Data Inventory","due":"17 months","due_date":"2013\/10\/23","fields":[{"type":"text","name":"1-2-3-datasets-in-inventory","label":"Number of datasets in the Enterprise Data Inventory","options":[],"value":"Over the last year, we have more than doubled the size of our inventory of available data sets. We now have over 2,000 data sets available on Data.gov.  "},{"type":"text","name":"1-2-3-systems-in-inventory","label":"Number of systems whose datasets are in the Enterprise Data Inventory","options":[],"value":"We are currently investigating approaches for assessing information systems with data sets.  We identified data sets as part of the Regulatory Compliance plan and they are detailed in the appendixes of the plan."},{"type":"text","name":"1-2-3-datasets-potential-public","label":"Number of datasets that can be made publicly available","options":[],"value":"All of the datasets we have inventoried are publicly available."},{"type":"text","name":"1-2-3-datsets-listed","label":"Number of datasets listed on the \/data page","options":[],"value":"Our www.dot.gov\/data links to over 2000 datasets available on data.gov.    "},{"type":"text","name":"1-2-3-released-datasets-listed","label":"Number of released datasets listed on the \/data page","options":[],"value":"We currently have over 2000 data sets linked on our www.dot.gov\/data page via data.gov.    "}],"multiple":false},{"id":"2.2","parent":null,"text":"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","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"select","name":"2-2-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"completed"}],"multiple":false},{"id":"2.2.1","parent":"2.1","text":"Publish plan on future activity","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"textarea","name":"2-2-1-describe","label":"Describe policy","options":[],"value":"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:\r\n\u2022\tEstablish common data based on authoritative data sources that is interoperable across the enterprise\r\n\u2022\tProvide the capability for program managers to discover authoritative data sources for common data\r\n\u2022\tDrive DOT to create systems that are interoperable and ready to share data.\r\n\uf0a7\tData and technology standards should foster open access to and ready consumption of DOT mission services for the benefit of its customers.\r\n\uf0a7\tData and information exchange will be based on open standards.\r\n\uf0a7\tInformation sharing and protection policies will be established and referenced in information sharing agreements.\r\n\u2022\tConsist of well documented interfaces built on non-proprietary open platforms using platform independent protocols such as XML."}],"multiple":false},{"id":"2.2.2","parent":"2.1","text":"Make 2+ systems (datasets) available via web APIs with metadata tags","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"text","name":"2-2-2-system","label":"Name of system","options":[],"value":["Federal Railroad Administration 10 Year Accident Reports ","SaferCar.gov Recall and Complaint Data "]},{"type":"textarea","name":"2-2-2-description","label":"Description of system","options":[],"value":["The 10-Year Accident\/Incident Report, one of the most requested reports on the Federal Railroad Administration\u2019s 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. ","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."]},{"type":"select","name":"2-2-2-scope","label":"Scope of system","options":[{"label":"Internal","value":"internal"},{"label":"External","value":"external"},{"label":"Both","value":"both"}],"value":["both","both"]},{"type":"text","name":"2-2-2-customers","label":"Main Customers","options":[],"value":["Rail Stakeholders, Inspectors, Citizens","Citizens, safety stakeholders, industry "]},{"type":"text","name":"2-2-2-uii","label":"Unique Investment Identifier","options":[],"value":["021-961146316--FRAXX013: Railroad Network System","021-777552743--NHTSA020: Artemis"]},{"type":"text","name":"2-2-2-url","label":"API Link","options":[],"value":["https:\/\/safetydata.fra.dot.gov\/MasterWebService\/FRASafetyDataAPIs.aspx","http:\/\/www.nhtsa.gov\/webapi\/Default.aspx"]}],"multiple":true},{"id":"5.3","parent":null,"text":"Evaluate the government-wide contract vehicles in the alternatives analysis for all new mobile-related procurements","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"select","name":"5-3-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"in-progress"},{"type":"textarea","name":"5-3-policy","label":"Describe Implementation","options":[],"value":"Wireless contracts are a priority strategic sourcing area for the Department.  We have an inter-office group responsible for this initiative and once available; we plan to consider leveraging the GSA vehicle."}],"multiple":false},{"id":"6.3","parent":null,"text":"Ensure all new digital services follow digital services and customer experience improvement guidelines","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"select","name":"6-3-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"in-progress"},{"type":"textarea","name":"6-3-policy","label":"Describe Implementation","options":[],"value":"We are actively working with the all of the Department\u2019s 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.\u201d to ensure all Departmental websites meet accessibility standards. \r\nWe have also implemented Google Analytics on most of DOT\u2019s .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), \r\nWe 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. \r\nWe 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.\r\n"}],"multiple":false},{"id":"7.2","parent":null,"text":"Optimize at least two existing priority customer-facing services for mobile use and publish a plan for improving additional existing services","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"select","name":"7-2-status","label":"Overall Status","options":[{"label":"Not Started","value":"not-started"},{"label":"In Progress","value":"in-progress"},{"label":"Completed","value":"completed"}],"value":"in-progress"},{"type":"textarea","name":"7-2-policy","label":"Describe Implementation","options":[],"value":"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:\r\n\u2022\tEstablish common data based on authoritative data sources that is interoperable across the enterprise\r\n\u2022\tProvide the capability for program managers to discover authoritative data sources for common data\r\n\u2022\tDrive DOT to create systems that are interoperable and ready to share data.\r\n\uf0a7\tData and technology standards should foster open access to and ready consumption of DOT mission services for the benefit of its customers.\r\n\uf0a7\tData and information exchange will be based on open standards.\r\n\uf0a7\tInformation sharing and protection policies will be established and referenced in information sharing agreements.\r\n\u2022\tConsist of well documented interfaces built on non-proprietary open platforms using platform independent protocols such as XML."}],"multiple":false},{"id":"7.2.1","parent":"7.2.","text":"Report on services","due":"12 months","due_date":"2013\/05\/23","fields":[{"type":"text","name":"7-2-1-name","label":"Service Name","options":[],"value":["Safer Car App","SaferBus App"]},{"type":"textarea","name":"7-2-1-description","label":"Service Description","options":[],"value":["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","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"]},{"type":"select","name":"7-2-1-scope","label":"System Scope","options":[{"label":"Internal","value":"internal"},{"label":"External","value":"external"},{"label":"Both","value":"both"}],"value":["both","both"]},{"type":"text","name":"7-2-1-customers","label":"Primary customers","options":[],"value":["Citizens, safety stakeholders, industry","Citizens, safety stakeholders, industry"]},{"type":"text","name":"7-2-1-uii","label":"Unique Investment Identifier","options":[],"value":["021-777552743--NHTSA020: Artemis","021-734121151--FMCSA100: Application and Information"]},{"type":"text","name":"7-2-1-url","label":"URL of service","options":[],"value":["https:\/\/itunes.apple.com\/us\/app\/safercar\/id593086230?ls=1&mt=8","http:\/\/www.fmcsa.dot.gov\/safety-security\/saferbus\/saferbus.aspx"]}],"multiple":true}]}