OCC Digital Strategy

1. Make Open Data, Content, and Web APIs the New Default

1.1 Issue government-wide open data, content, and web Application Program Interface (API) policy and identify standards and best practices for improved interoperability (OMB)

This can be found here: Project Open Data

18F also has API resources here: Developer Program

1.2 Ensure all new IT systems follow the open data, content, and web API policy and operationalize agency.gov/developer pages (OCC)

Describe Policy: The OCC is working diligently to institutionalize and operationalize the development of IT systems as applicable with openness by default. We are implementing activities to ensure information is managed as an asset across the enterprise. Through the use of Software Development Lifecycle processes, we ensure that are development activities are consistent and reusable throughout the enterprise as well as secure within the data architecture and lifecycle. Activities included in the current implementation are the collection of business requirements, use of open data architectures, user centered design, documented naming standards, data modeling, security architect meetings, dataset publishing support processes, and an enterprise repository of requirements and code. We will continue enhance our development processes through Continuous Improvement as part of our Agile Scrum Development.

Overall Status: In Progress

1.2.3 Governance Tools

The OCC is considering an agency-wide API Strategy building upon 18F's API standards and using api.data.gov's API management platform. In addition, APIs produced by the OCC should be described using one of the common API definition formats (such as Odata, OpenAPI, Swagger, API Blueprint, and RAML). The strategy is being finalized and an agency-wide communication plan is being developed. This communication plan will include Standard Operating Procedures (SOPs) that require API developers to register dataset APIs.

Status: In Progress

1.2.4 Develop Data Inventory Schedule

Summarize the Inventory Schedule: The OCC is working on completing an Enterprise Dataset Inventory.

1.2.5 Develop Data Inventory Schedule - Milestones

Title: Provide reports to programs to identify metadata holes.
Description: OCC uses its registry of IT Systems to identify datasets that may not be cataloged.
Milestone Date: Ongoing
Description of how this milestone expands the Inventory: This milestone allows OCC to identify and catalog new datasets that were not identified in the original 2013 Treasury data call.
Description of how this milestone enriches the Inventory: This milestone brings new and important datasets into the OCC's Data Inventory.
Description of how this milestones opens the Inventory: This milestones provides additional datasets that are publicly available through both occ.gov and data.gov.

1.2.6 Develop Customer Feedback Process
Describe the agency's process to engage with customers: OCC interacts with the public on its data in numerous ways including public meetings/forums, feedback links on websites, webinars, FOIA Online, mailboxes, and help desks.

1.2.7 Describe the agency's data publication process:

• Identify: The data set for public publication will be identified based on inputs from the data owner community and the data consumer community. Engaging with the data consumer (also referred to as the customer) using the process outlined in the "Customer Engagement Process" section helps to determine the data sets and the fields that compose the data set.
• Review: The data set must be reviewed by relevant officials from
  • Business Data Owner and System Owner.
  • Office of Privacy and General Counsel.
  • Security.
• Publish: Create metadata for the data set, provide data context description.

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 (OCC)

Overall status: Complete

2.1.1 Paragraph on customer engagement approach
The OCC discussed possible customer-facing high-value data sources with customers to identify two first-move candidate datasets.

2.1.2 Prioritized list of first-move candidate datasets
System Name: Enforcement Actions Search
System Description: Database of OCC enforcement actions
System Scope: OCC enforcement actions
Main Customer: Public and internal users

System Name: Community Reinvestment Act (CRA) Evaluation Search
System Description: Database of OCC CRA evaluations
System Scope: OCC CRA evaluations
Main Customer: Public and internal users

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 (OCC)

Overall status: In Progress

2.2.1 Publish plan on future activity
Describe policy: Treasury will work with the OCC to identify additional candidates for APIs or datasets.

2.2.2 Make 2+ systems (datasets) available via web APIs with metadata tags
Name of system: TBD
Description of system: TBD

2.3 Expand Data.gov to include a web API catalog that centrally aggregates web APIs posted on agencies' /developer pages (GSA)

Completed May 23, 2013: https://www.data.gov/developers/apis

3. Establish a Digital Services Innovation Center and Advisory Group

3.1 Establish a Digital Services Innovation Center to improve the government's delivery of digital services (GSA)

Established June 23, 2012 (inactive)

3.2 Convene a Digital Services Advisory Group to provide input on priorities for the Innovation Center activities and recommend government-wide best practices, guidance, and standards (OMB)

Complete: https://obamawhitehouse.archives.gov/digitalgov/advisory-group

3.3 Release government-wide bring-your-own-device (BYOD) guidance based on lessons learned from successful pilots at federal agencies (OMB)

Complete:

https://obamawhitehouse.archives.gov/digitalgov/bring-your-own-device

3.4 Identify shared and open content management system solutions (GSA)

Completed February 23, 2013: https://federalist.18f.gov/

3.5 Provide support to help agencies develop web APIs (GSA)

Completed February 23, 2013: https://api.data.gov/ and https://www.digitalgov.gov/2013/04/30/apis-in-government/

3.6 Launch a shared mobile app development program (GSA)

Completed May 23, 2013: https://digital.gov/topics/mobile

4. Establish Intra-Agency Governance to Improve Delivery of Digital Services

4.1 Recommend guidelines on agency-wide governance structure for developing and delivering digital services and managing data (OMB)

Complete:

https://obamawhitehouse.archives.gov/digitalgov/digital-services-governance-recommendations

4.2 Establish an agency-wide governance structure for developing and delivering digital services (OCC)

Overall status: In progress

• Paragraph on governance: OCC has a number of governance policies, procedures, and standards that guide the development and delivery of digital services. These policies, procedures, and standards are available on the OCCnet intranet site. Additional policies, procedures, and standards will be posted on OCCnet and/or occ.gov as they become approved.

5. Shift to an Enterprise-Wide Asset Management and Procurement Model

5.1 Establish government-wide contract vehicle for mobile devices and wireless service (GSA)

Overall status: Complete

5.2 Develop an enterprise-wide inventory of mobile devices and wireless service contracts (OCC)

Overall status: Complete

5.2.1 Develop wireless and mobile inventory
Bureau/Component: Telecom
Inventory Status: Complete

5.3 Evaluate the government-wide contract vehicles in the alternatives analysis for all new mobile-related procurements (Treasury)

Overall status: Complete
Describe Implementation: The General Services Administration (GSA) held a User Kickoff Meeting on June 27, 2013, to discuss use of the newly awarded Federal Strategic Sourcing Initiative (FSSI) contract vehicles and published the GSA FSSI User Guide on February 14, 2014. Treasury continues to work closely with GSA to determine the most effective and cost efficient strategy for department-wide use of the FSSI awards, consistent with expiration of current contract performance periods. On final determination of our transition strategy, Office of the Procurement Executive (OPE) will issue related formal procurement policy; it remains the department's intent to use the GSA FSSI contract vehicles provided they offer the anticipated value. OPE has collaborated with Bureau Chief Procurement Officers (BCPOs) and with the Office of the Chief Information Officer to facilitate the appropriate internal analysis and planning. In the interim, Treasury has continued its focus on leveraging existing internal contracts for wireless services to provide the greatest value for current services.

5.4 Develop models for the delivery of commercial mobile applications into the federal environment (OMB)

5.5 Set up a government-wide mobile device management platform (GSA)

Overall status: Complete

6. Deliver Better Digital Services Using Modern Tools and Technologies

6.1 Recommend guidelines for improving digital services and customer experience (OMB)

Complete: https://www.digitalgov.gov/resources/guidelines-for-improving-digital-services/

6.2 Update the dot gov domain guidance and procedures to help ensure all new digital services meet improvement guidelines and provide support to agencies (GSA)

Complete: https://www.gsa.gov/policy-regulations/policy/information-integrity-and-access/gov-domain-services

6.3 Ensure all new digital services follow digital services and customer experience improvement guidelines (OCC)

Overall Status: In progress
Describe Implementation:

• Establish digital government innovation group to enhance and modernize department wide digital services.
• Implement website metrics collection tools analyze the data generated by these tools.
• Implement customer engagement process.
• Implement data publication process.

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 (OCC)

Overall status: Complete

7.1.1 Paragraph on customer engagement approach:

Describe Implementation: Citizen engagement is a hallmark of programs throughout the OCC. The OCC interacts with the public on its data in numerous ways including public meetings and forums, feedback links on websites, webinars, FOIA Online, mailboxes, and help desks. We also strive to include state, local, and tribal governments in our engagement efforts through workgroups and exchange network governance groups where we are working out common standards, terminology, and data collection methodology. In addition, the OCC uses Google Analytics to determine datasets that are most frequently accessed and considered high-value by the public. These datasets are then highlighted on our website and targeted for quality improvement efforts.

7.1.2 Prioritize your list of systems (datasets)
System Name: Enforcement Actions Search
System Description: Database of OCC enforcement actions
System Scope: OCC enforcement actions
Main Customer: Public and internal users

System Name: Community Reinvestment Act (CRA) Search
System Description: Database of OCC CRA evaluations
System Scope: OCC CRA evaluations
Main Customer: Public and internal users

7.2 Optimize at least two existing priority customer-facing services for mobile use and publish a plan for improving additional existing services (OCC)

Overall status: Complete
Describe Implementation: The OCC optimizes its public-facing websites for mobile devices.

7.2.1 Report on services
System Name: occ.gov
System Description: The primary public-facing website of the OCC
System Scope: External
Primary customers: General public, bankers, other federal agencies, OCC employees
URL of service: https://www.occ.gov

System Name: helpwithmybank.gov
System Description: The primary public-facing OCC website for current and potential financial service customers
System Scope: External
Primary customers: General public
URL: https://www.helpwithmybank.gov

System Name: careers.occ.gov
System Description: The primary public-facing OCC website for individuals interested in working for the OCC
System Scope: External
Primary customers: General public
URL: https://careers.occ.gov

8. Measure Performance and Customer Satisfaction to Improve Service Delivery

8.1 Identify tools and guidance for measuring performance and customer satisfaction on digital services (GSA)

Complete: https://www.digitalgov.gov/services/dap/dap-digital-metrics-guidance-and-best-practices/

8.2 Implement performance and customer satisfaction measuring tools on all .gov websites (OCC)

Overall status: Complete

8.2.1 Implement performance measurement tool

Implemented Digital Analytics Program: Yes

In order to preserve the integrity and effectiveness of the OCC's performance metrics, the OCC is operating an agency-managed Google Analytics implementation. The OCC also complies with the government-wide implementation of Google Analytics.

If not, describe implementation: NA
Percent of websites covered: 100%
URL of performance data: NA

8.2.2 Implement customer satisfaction tool

Describe implementation: The OCC does not currently have a customer satisfaction tool on any of its public-facing websites. The OCC will explore a tool for this purpose that will allow it to make improvements to the sites.

URL of performance data: NA

Contact Us to ask a question, provide feedback, or report a problem.