Digital Government Strategy Report for the Department of Commerce
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: To ensure future information systems and services comply with the Federal Digital Strategy and Open Data Policy (M-13-13, May 9, 2013) and to modernize existing systems to leverage APIs, Commerce will integrate digital strategy and open data requirements and guidance to existing processes and workflows. As such, the Office of the Chief Information Officer will examine and validate projects to ensure they include a digital strategy component for open data and interoperability and address the open data requirements.
1.2.4. Develop Data Inventory Schedule - Summary
Summarize the Inventory Schedule: During 2013, the Department of Commerce focused its Open Data efforts on establishing a framework to enhance, enrich, and open, to the extent practicable, its Enterprise Data Inventory (EDI) and to ensure the Department and its component bureaus are prepared to identify, correctly document, and submit to the Office of Management and Budget (OMB) on November 30, 2014 a comprehensive EDI. In so doing, Commerce has already achieved several internal milestones that lay the groundwork for the Department future Open Data efforts and position Commerce to meet OMB Open Data requirements.
1.2.5. Develop Data Inventory Schedule - Milestones
Title: Milestone 1 - Expand and Open EDI
Description: The Department of Commerce will initially focus on expanding and opening its Enterprise Data Inventory. To this end, the Open Government Senior Leaders, in collaboration with Agency CIOs, Data Stewards, and the Data.gov Points of Contact, will continue to work with Commerce Office of Open Government and Privacy to identify, prioritize and submit additional public, non-public, and restricted-public datasets to the Department. In addition, the Open Government Senior Leaders and Data.gov Points of Contact will continue the development of an Open Data process and guidance that expedite the publication of its datasets in the future. At the end of Q1, Commerce will submit an updated EDI to OMB. Over the second quarter, from February 28 to May 31, Commerce and its component bureaus will continue to input into its EDI additional datasets. The Department will also continue to collaborate with its Data Stewards to update its customer feedback and outreach efforts. At the end of Q2, Commerce will submit an updated EDI to OMB.
Milestone Date: February 28, 2014
Title: Milestone 2 - Enrich EDI and Public Datasets
Milestone Date: May 31, 2014
1.2.6. Develop Customer Feedback Process
Describe the agency's process to engage with customers: Questions or input for Commerce data can be submitted through our U.S. Department of Commerce Open Government Portal. - http://opencommerce.ideascale.com/
1.2.7. Develop Data Publication Process
Describe the agency's data publication process: Data owners identify data sets that are currently not public, but they believe should be. In consultation with the Office of Chief Information Officer, Office of Privacy and Open Government and the Office of Public Affairs, these data sets are then placed in a publicly-accessible website. The metadata is also entered into our CKAN system to be integrated into the data catalog .json.
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: In addition to informal discussions with internal and external stakeholders, we have posted an entry on our blog (http:www.commerce.gov/blog/2012/08/08/commerce-department-needs-your-input-digital-strategy) soliciting feedback. We have also used a Facebook poll and daily tweets to drive traffic. Several stories have been written about our outreach and have also driven traffic to the blog post.
2.1.2. Prioritized list of systems (datasets)
System Name: Export.gov API
System Description: An API that will allow developers access to Export.gov events data
System Scope: external
Main Customer: Freight Forwarders and Trade Associations
System Name: Census API
System Description: Additional economic and demographic data
System Scope: external
Main Customer: Users of economic and demographic data such as realtors, economic professionals,
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: in-progress
2.2.1. Publish plan on future activity
Describe policy: Commerce.gov will publish a content API and BEA will publish a data API by the end of Q3 2013
2.2.2. Make 2+ systems (datasets) available via web APIs with metadata tags
Name of system: Commerce.gov
Description of system: A content API
Scope of system: external
Main Customers: Public
4.2. Establish an agency-wide governance structure for developing and delivering digital services
Overall Status: in-progress
Paragraph on Governance: Commerce is currently working within existing frameworks to strengthen communication and oversight of digital products
URL to Governance Document: http://osec.doc.gov/webresources/doc_web_policies_best_practices.htm
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
Inventory Status: in-progress
5.3. Evaluate the government-wide contract vehicles in the alternatives analysis for all new mobile-related procurements
Overall Status:
Describe Implementation:
6.3. Ensure all new digital services follow digital services and customer experience improvement guidelines
Overall Status: in-progress
Describe Implementation: New systems must be approved via various internal reviews. The Commerce Web Advisory Committee recently published a best practice guide for the various reviews to use as a scorecard against new efforts.
7.1. Engage with customers to identify at least two existing priority customer-facing services to optimize for mobile use.
Overall Status: in-progress
7.1.1. Paragraph on customer engagement approach
Paragraph on customer engagement approach: In addition to informal discussions with internal and external stakeholders, we have posted an entry on our blog (http:www.commerce.gov/blog/2012/08/08/commerce-department-needs-your-input-digital-strategy) soliciting feedback. We have also used a Facebook poll and daily tweets to drive traffic. Several stories have been written about our outreach and have also driven traffic to the blog post.
7.1.2. Prioritized list of systems (datasets)
System Name: NOAA Coast Survey Maps
System Description: Android App for digitizing NOAA Coast Survey Maps
System Scope: external
Main Customer: Recreational boaters
System Name: Census mobile app
System Description: Census will develop an additional mobile app
System Scope: external
Main Customer: Citizens and users of demographic data
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: Both Commerce.gov and BEAs API are in a testing environment with the hopes to deliver by end of Q3 2013.
7.2.1. Report on services
Service Name: Commerce.gov
Service Description: Ensuring mobile-optimization of Commerce.gov
System Scope: external
Primary customers: Citizens with mobile devices
8.2. Implement performance and customer satisfaction measuring tools on all .gov websites
Overall Status: completed
8.2.1. Implement performance measurement tool
Implemented Digital Analytics Program: yes
If Not, Describe Implementation: Google Analytics code has been shared with Commerce.gov team. Working through security and legal concerns
Percent of websites covered: N/A
URL of performance data: N/A
8.2.2. Implement customer satisfaction tool
Describe Implementation: Commerce is still working through possible solutions to measure customer satisfaction across all websites.
URL of performance data: N/A
Last updated July 7, 2014 at 3:43 pm
