Digital Government Strategy - Milestones
| # | Milestone Actions | Timeframe (months) | |||
|---|---|---|---|---|---|
| 1 | 3 | 6 | 12 | ||
| Part A: Information-Centric | |||||
| 1. Make Open Data, Content, and Web APIs the New Default | |||||
| 1.2 | Ensure all new IT systems follow the open data, content, and web API policy and operationalize agency.gov/developer pages. Due: May 23, 2013 |
X | |||
| 2. Make Existing High-Value Data and Content Available through Web APIs | |||||
| 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. Due: August 23, 2012; Completed |
✓ | |||
| 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. [Within 6 months of release of open data policy] Due: May 23, 2013 |
X | |||
| Part B: Shared Platform | |||||
| 4. Establish Intra-Agency Governance to Improve Delivery of Digital Services | |||||
| 4.2 | Establish an agency-wide governance structure for developing and delivering digital services. [Within 3 months of release of governance guidance] Due: November 23, 2012; In Progress |
X | |||
| 5. Shift to an Enterprise-Wide Asset Management and Procurement Model | |||||
| 5.2 | Develop an enterprise-wide inventory of mobile devices and wireless service contracts. Due: November 23, 2012; Completed |
✓ | |||
| 5.3 | Evaluate the government-wide contract vehicles in the alternatives analysis for all new mobile-related procurements. Due: May 23, 2013 |
X | |||
| Part C: Customer-Centric | |||||
| 6. Deliver Better Digital Services Using Modern Tools and Technologies | |||||
| 6.3 | Ensure all new digital services follow digital services and customer experience improvement guidelines. [Within 6 months of release of improvement guidance] Due: May 23, 2013 |
X | |||
| 7. Improve Priority Customer Facing Services for Mobile Use | |||||
| 7.1 | Engage with customers to identify at least two existing priority customer-facing services to optimize for mobile use. Due: August 23, 2012; Completed |
✓ | |||
| 7.2 | Optimize at least two existing priority customer-facing services for mobile use and publish a plan for improving additional existing services. [Within 6 months of release of digital services improvement guidance] Due: May 23, 2013 |
X | |||
| 8. Measure Performance and Customer Satisfaction to Improve Service Delivery | |||||
| 8.2 | Implement performance and customer satisfaction measuring tools on all .gov websites. [Within 3 months of release of tools and guidance] Due: January 22, 2013; In Progress |
X | |||
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
2.1.0 Overall status: Completed
2.1.1 Paragraph on customer engagement approach:
The National Archives and Records Administration (NARA) sought input from both the public and staff in the prioritization of first-move candidates. A post on the NARAtions blog garnered several public comments and staff responses. Facebook posts and tweets furthered the dialog as well as a post on Today’s Document Tumblr featuring an mashup of the poster "Uncle Sam wants Your Ideas."
2.1.2 Proposed Candidates to Enable via Web Services (APIs, etc):
FederalRegister.gov
Description: Integration of the Regulations.gov API into FederalRegister.gov and its API. This integration would provide greater access to public comments and supporting documents in Regulations.gov, and improve process for submitting public comments from FederalRegister.gov into Regulations.gov.
Customers: Legal community, advocacy groups, small businesses, the general public.
FederalRegiser.gov API
Description: Expand the FederalRegister.gov API to include the "Public Inspection Desk."
Customers: Legal community, advocacy groups, small businesses, the general public.
Description: Develop an API for FDsys through the Office of Federal Register-Government Printing Office Partnership.
Customers: Legal community, advocacy groups, small businesses, the general public.
Description: Make additional National Archives records available through Wikipedia, which is accessible through the MediaWiki API.
Customers: The general public, historians, researchers, students.
Description: Make additional National Archives records available on Flickr, which is accessible through the Flickr API.
Customers: The general public, historians, researchers, students.
4.2 Establish an agency-wide governance structure for developing and delivering digital services
Overall status: In Progress
Paragraph on Governance:
The National Archives and Records Administration (NARA) will create an governance structure to support the newly created Office of Innovation in the development and delivery of digital content and data for the agency. The agency expects to name a Chief Innovation Officer to lead this effort.
URL to Governance Document: N/A
5.2 Develop an enterprise-wide inventory of mobile devices and wireless service contracts
Overall status: Completed
7.1 Engage with customers to identify at least two existing priority customer-facing services to optimize for mobile use
7.1.0 Overall status: Completed
7.1.1 Paragraph on customer engagement approach:
The National Archives and Records Administration (NARA) sought input from both the public and staff in the prioritization of first-move candidates. A post on the NARAtions blog garnered several public comments and staff responses. Facebook posts and tweets furthered the dialog as well as a post on Today’s Document Tumblr featuring an mashup of the poster "Uncle Sam wants Your Ideas."
7.1.2 Proposed Candidates to Create or Further Optimize for Mobile Use:
Description: Mobile optimize FederalRegister.gov
Customers: Legal community, advocacy groups, small businesses, the general public.
Description: Develop a mobile application based on the Daily Compilation of Presidential Documents.
Customers: Legal community, advocacy groups, small businesses, the general public.
Description: Mobile optimize Archives.gov.
Customers: The general public, veterans, historians, researchers, students.
Description: Make additional National Archives records available through Wikipedia, which is mobile optimized and available through mobile apps.
Customers: The general public, historians, researchers, students.
Description: Make additional National Archives records available through Flickr, which is mobile optimized and available through mobile apps.
Customers: The general public, historians, researchers, students.
8.2 Implement performance and customer satisfaction measuring tools on all .gov websites
Overall status:In Progress
Blogs
Facebook
Flickr
RSS Feeds
Twitter
YouTube
