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
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: in-progress
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's events data
System Scope: external
Main Customer: Freight Forwarders and Trade Associations
API Link: https://new.export.gov/events
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
API Link: http://www.census.gov/developers/
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
Name of system: BEA.gov
Description of system: A data 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
6.3. Ensure all new digital services follow digital services and customer experience improvement guidelines
Overall Status: in-progress
Describe Implementation:Both the OCIO Council and Web Advisory Council have been briefed on the new requirements. They are working on guidance to augment the established federal guidance (http://www.howto.gov/customer-experience/improve-digital-services). The Office of Budget will be briefed in the near future so that the requirements can be used as part of contractual language for all future procurements and service contracts, where applicable.
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
URL of Service: http://www.nauticalcharts.noaa.gov/mynoaacharts
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 BEA's 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
System Name: NOAA Coast Survey Maps
System Description: Android App for digitizing NOAA Coast Survey Maps
System Scope: external
Main Customer: Recreational boaters
URL of Service: http://www.nauticalcharts.noaa.gov/mynoaacharts
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: 21%
URL of performance data: This performace data is used internally
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 May 22, 2013 at 6:04 pm
