CINXE.COM

<!DOCTYPE html>  <html lang="en"> <head>  <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge">  <meta name="HandheldFriendly" content="True"> <meta name="MobileOptimized" content="320"> <meta name="viewport" content="width=device-width, initial-scale=1.0">  <title>Action Plan - Federal Data Strategy</title> <meta property="og:title" content="Action Plan - Federal Data Strategy"> <meta name="description" content="Design and build fast, accessible, mobile-friendly government websites backed by user research."> <meta property="og:description" content="Design and build fast, accessible, mobile-friendly government websites backed by user research."> <meta property="og:url" content="/"> <link rel="canonical" href="/">   <link rel="shortcut icon" type="image/ico" href="/assets/uswds/img/favicons/favicon.ico"> <link rel="icon" type="image/png" href="/assets/uswds/img/favicons/favicon.png">  <link rel="icon" type="image/png" sizes="192x192" href="/assets/uswds/img/favicons/favicon-192.png">  <link rel="apple-touch-icon-precomposed" href="/assets/uswds/img/favicons/favicon-57.png">  <link rel="apple-touch-icon-precomposed" sizes="72x72" href="/assets/uswds/img/favicons/favicon-72.png">  <link rel="apple-touch-icon-precomposed" sizes="114x114" href="/assets/uswds/img/favicons/favicon-114.png">  <link rel="apple-touch-icon-precomposed" sizes="144x144" href="/assets/uswds/img/favicons/favicon-144.png">  <link rel="stylesheet" href="/assets/uswds/css/uswds_3.1.0.min.css?v=2024-10-15-22-41-40-+0000"> <link rel="stylesheet" href="/assets/uswds/css/uswds.min.css?v=2024-10-15-22-41-40-+0000"> <link rel="stylesheet" href="/assets/css/custom.css?v=2024-10-15-22-41-40-+0000"> <link rel="stylesheet" type="text/css" href="/assets/css/datatables.min.css"/> <script src="/assets/uswds/js/uswds.min.js?v=2024-10-15-22-41-40-+0000"></script> <script type="text/javascript" src="/assets/js/jquery-3.6.0.min.js"></script> <script type="text/javascript" src="/assets/js/datatables.min.js"></script> <script type="text/javascript" src="/assets/js/bootstrap.min.js"></script> <script type="text/javascript" src="/assets/js/jquery.csv.min.js"></script> <script type="text/javascript" src="/assets/js/csv_to_html_table.js"></script>  <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-NBXQ7P2');</script>   <script id="_fed_an_ua_tag" src="https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=GSA&subagency=TTS"></script> <body class="page-landing-page">  <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-NBXQ7P2" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>  <a class="usa-skipnav" href="#main-content">Skip to main content</a> <section class="usa-banner"> <div class="usa-accordion"> <header class="usa-banner-header"> <div class="usa-grid usa-banner-inner"> <img src="/assets/uswds/img/favicons/favicon-57.png" alt="U.S. flag"> <p>An official website of the United States government</p> <button class="usa-accordion-button usa-banner-button" aria-expanded="false" aria-controls="gov-banner"> <span class="usa-banner-button-text">Here's how you know</span> </button> </div> </header> <div class="usa-banner-content usa-grid usa-accordion-content" id="gov-banner"> <div class="usa-banner-guidance-gov usa-width-one-half"> <img class="usa-banner-icon usa-media_block-img" src="/assets/uswds/img/icon-dot-gov.svg" alt="Dot gov"> <div class="usa-media_block-body"> <p> <strong>The .gov means it’s official.</strong> <br> Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site. </p> </div> </div> <div class="usa-banner-guidance-ssl usa-width-one-half"> <img class="usa-banner-icon usa-media_block-img" src="/assets/uswds/img/icon-https.svg" alt="Https"> <div class="usa-media_block-body"> <p> <strong>The site is secure.</strong> <br> The <strong>https://</strong> ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely. </p> </div> </div> </div> </div> </section> <header class="usa-header usa-header-extended" role="banner"> <div class="usa-navbar"> <div class="usa-logo" id="extended-logo"> <a class="data-strategy-logo-link" href="/" title="Home" aria-label="Home"> <img class="data-strategy-logo" src="/assets/img/federal-data-strategy-logo-horizontal.svg" alt="Federal Data Strategy Logo"> </a> <em class="usa-logo-text"> <a href="/" title="Home" aria-label="Home"> Federal Data Strategy </a> </em> </div> <button class="usa-menu-btn">Menu</button> </div> <nav role="navigation" class="usa-nav"> <div class="usa-nav-inner"> <button class="usa-nav-close"> <img src="/assets/uswds/img/close.svg" alt="close"> </button> <ul class="usa-nav-primary usa-accordion"> <li><a class="usa-nav-link" href="/"><span>Home</span></a></li> <li> <button class="usa-accordion-button usa-nav-link" aria-expanded="false" aria-controls="basic-nav-section-two"><span>About</span></button> <ul id="basic-nav-section-two" class="usa-nav-submenu"> <li><a href="/background/">Background</a></li> <li><a href="/overview/">Overview</a></li> <li><a href="https://www.cdo.gov">CDO Council</a></li> </ul> </li> <li> <button class="usa-accordion-button usa-nav-link" aria-expanded="false" aria-controls="basic-nav-section-three"><span>Action Plan</span></button> <ul id="basic-nav-section-three" class="usa-nav-submenu"> <li><a href="/2021/action-plan/">2021 Action Plan</a></li> <li><a href="/2020/action-plan/">2020 Action Plan</a></li> </ul> </li> <li> <button class="usa-accordion-button usa-nav-link" aria-expanded="false" aria-controls="basic-nav-section-four"><span>Action Progress</span></button> <ul id="basic-nav-section-four" class="usa-nav-submenu"> <li><a href="/2021/progress/">2021 Action Progress</a></li> <li><a href="/2020/progress/">2020 Action Progress</a></li> </ul> </li> <li><a class="usa-nav-link" href="/resources/"><span>Resources</span></a></li> <li><a class="usa-nav-link" href="/news/"><span>News</span></a></li> </ul> <div class="usa-nav-secondary"> </div> </div> </nav> </header> <div class="usa-overlay"></div> <main class="usa-grid usa-section usa-content usa-layout-docs" id="main-content"> <aside class="usa-width-one-fourth usa-layout-docs-sidenav"> <nav> <ul class="usa-sidenav-list"> <li> <a href="/action-plan/" class="usa-current"> 2020 Action Plan </a> <ul class="usa-sidenav-sub_list"> <li> <a href="/action-plan/special-thanks/" class="action-plan-subheader"> Special Thanks </a> </li> <li> <a href="/action-plan/creating-a-strategy/" class="action-plan-subheader"> Creating a Strategy </a> </li> <li> <a href="/action-plan/how-we-will-get-there/" class="action-plan-subheader"> How We Will Get There </a> </li> <li> <a href="/action-plan/#agency-actions" class="action-plan-subheader"> Agency Actions </a> <ul class="usa-sidenav-sub_list"> <li> <a href="/action-plan/#action-1-identify-data-needs-to-answer-priority-agency-questions"> Action 1: Identify Data Needs to Answer Priority Agency Questions </a> </li> <li> <a href="/action-plan/#action-2-constitute-a-diverse-data-governance-body"> Action 2: Constitute a Diverse Data Governance Body </a> </li> <li> <a href="/action-plan/#action-3-assess-data-and-related-infrastructure-maturity"> Action 3: Assess Data and Related Infrastructure Maturity </a> </li> <li> <a href="/action-plan/#action-4-identify-opportunities-to-increase-staff-data-skills"> Action 4: Identify Opportunities to Increase Staff Data Skills </a> </li> <li> <a href="/action-plan/#action-5-identify-priority-data-assets-for-agency-open-data-plans"> Action 5: Identify Priority Data Assets for Agency Open Data Plans </a> </li> <li> <a href="/action-plan/#action-6-publish-and-update-data-inventories"> Action 6: Publish and Update Data Inventories </a> </li> </ul> </li> <li> <a href="/action-plan/#community-of-practice-actions" class="action-plan-subheader"> Community of Practice Actions </a> <ul class="usa-sidenav-sub_list"> <li> <a href="/action-plan/#action-7-launch-a-federal-chief-data-officer-council"> Action 7: Launch a Federal Chief Data Officer Council </a> </li> <li> <a href="/action-plan/#action-8-improve-data-and-model-resources-for-ai-research-and-development"> Action 8: Improve Data and Model Resources for AI Research and Development </a> </li> <li> <a href="/action-plan/#action-9-improve-financial-management-data-standards"> Action 9: Improve Financial Management Data Standards </a> </li> <li> <a href="/action-plan/#action-10-integrate-geospatial-data-practices-into-the-federal-data-enterprise"> Action 10: Integrate Geospatial Data Practices into the Federal Data Enterprise </a> </li> </ul> </li> <li> <a href="/action-plan/#shared-solution-actions" class="action-plan-subheader"> Shared Solution Actions </a> <ul class="usa-sidenav-sub_list"> <li> <a href="/action-plan/#action-11-develop-a-repository-of-federal-enterprise-data-resources"> Action 11: Develop a Repository of Federal Enterprise Data Resources </a> </li> <li> <a href="/action-plan/#action-12-create-omb-federal-data-policy-committee"> Action 12: Create OMB Federal Data Policy Committee </a> </li> <li> <a href="/action-plan/#action-13-develop-a-curated-data-skills-catalog"> Action 13: Develop a Curated Data Skills Catalog </a> </li> <li> <a href="/action-plan/#action-14-develop-a-data-ethics-framework"> Action 14: Develop a Data Ethics Framework </a> </li> <li> <a href="/action-plan/#action-15-develop-a-data-protection-toolkit"> Action 15: Develop a Data Protection Toolkit </a> </li> <li> <a href="/action-plan/#action-16-pilot-a-one-stop-standard-research-application"> Action 16: Pilot a One-stop Standard Research Application </a> </li> <li> <a href="/action-plan/#action-17-pilot-an-automated-tool-for-information-collection-reviews-that-supports-data-inventory-creation-and-updates"> Action 17: Pilot an Automated Tool for Information Collection Reviews that Supports Data Inventory Creation and Updates </a> </li> <li> <a href="/action-plan/#action-18-pilot-enhanced-data-management-tool-for-federal-agencies"> Action 18: Pilot Enhanced Data Management Tool for Federal Agencies </a> </li> <li> <a href="/action-plan/#action-19-develop-data-quality-measuring-and-reporting-guidance"> Action 19: Develop Data Quality Measuring and Reporting Guidance </a> </li> <li> <a href="/action-plan/#action-20-develop-a-data-standards-repository"> Action 20: Develop a Data Standards Repository </a> </li> </ul> </li> <li> <a href="/action-plan/#looking-forward" class="action-plan-subheader"> Looking Forward </a> </li> </ul> </nav> </aside> <div class="usa-width-three-fourths usa-layout-docs-main_content"> <h1 id="2020-action-plan">2020 Action Plan</h1> <p><strong>Last Updated 5/14/2020.</strong> <em>Consistent with <a href="https://www.whitehouse.gov/wp-content/uploads/2020/03/M-20-16.pdf">M-20-16 Federal Agency Operational Alignment to Slow the Spread of Coronavirus COVID-19</a>, the Federal Data Strategy 2020 Action Plan is adjusting Actions by extending several Agency target dates by one month and one Shared Solution target date by three months. In addition, in places where the Federal Data Strategy calls for Agencies to prioritize data assets and projects, the agencies are making sure to include COVID-19 response data as their highest priority. All adjustments can be viewed prominently and in detail below.</em></p> <p>The Federal Data Strategy provides a common set of data principles and best practices in implementing data innovations that drive more value for the public. Annual action plans will identify and prioritize practice-related steps for a given year, along with targeted timeframes and responsible entities.</p> <p>The 2020 Action Plan establishes a solid foundation that will support implementation of the strategy over the next decade. Specifically, the plan identifies initial actions for agencies that are essential for establishing processes, building capacity, and aligning existing efforts to better leverage data as a strategic asset.</p> <p>In addition, the 2020 Action Plan includes a series of pilot projects already underway at individual agencies and a set of government-wide efforts designed to support all agencies through the development of tools and resources.</p> <p>Annual Action Plans are developed iteratively with stakeholder feedback and input incorporated along the way. If you’d like to be notified about updates or ways to be involved, please sign up for our news updates.</p> <p><a href="/assets/docs/2020-federal-data-strategy-action-plan.pdf" class="usa-button">Download PDF - Final Federal Data Strategy & 2020 Action Plan</a></p> <p><a href="/assets/docs/2020-federal-data-strategy-framework.pdf" class="usa-button">Download PDF – Federal Data Strategy Brochure</a></p> <p><a href="/assets/docs/draft-2019-2020-federal-data-strategy-action-plan.pdf" class="usa-button">Download PDF - Draft 2019-2020 Action Plan</a></p> <p><a href="/assets/docs/2019-2020-federal-data-strategy-revisions-based-on-feedback.pdf" class="usa-button">Download PDF - Revisions Based on Feedback</a></p> <h2 id="preamble">Preamble</h2> <ul> <li><strong><a href="/action-plan/special-thanks/">Special Thanks to Our Contributors</a></strong></li> <li><strong><a href="/action-plan/creating-a-strategy/">Data, Accountability, and Transparency: Creating a Data Strategy and Infrastructure for the Future</a></strong></li> <li><strong><a href="/action-plan/how-we-will-get-there/">How We Will Get There: The Dynamic Nature of the Federal Data Strategy</a></strong></li> </ul> <h2 id="action-plan-categories">Action Plan Categories</h2> <ul> <li><strong><a href="#agency-actions">Agency Actions</a></strong></li> <li><strong><a href="#community-of-practice-actions">Community of Practice Actions </a></strong></li> <li><strong><a href="#shared-solution-actions">Shared Solution Actions </a></strong></li> </ul> <h2 id="conclusion">Conclusion</h2> <ul> <li><strong><a href="#looking-forward">Looking Forward</a></strong></li> </ul> <h2 id="agency-actions">Agency Actions</h2> <p>Six Agency Actions are identified as foundational steps to support agencies in establishing plans, processes, and priorities for better managing data assets while considering how the agency’s data assets could be leveraged to advance the agency’s mission. Because agencies have different levels of maturity in their current management and use of data, agencies are expected to have different starting points for executing the six Agency Actions. Each agency should first establish a baseline for each action by assessing the agency’s current status, and then develop and implement a plan to fully achieve each action over the course of the next year. The strategy is supported by tools and resources to aid in the execution of the Agency Actions. Resources will be posted to the repository, Federal Enterprise Data Resources, at <a href="https://resources.data.gov">resources.data.gov</a> throughout the course of the year.</p> <p>Many of the Agency Actions build on and complement efforts that are already underway in response to other requirements or laws. The graphic below maps each of the six Agency Actions to a set of relevant laws and guidance documents. While future Action Plans will make similar connections between Agency Actions and relevant laws and requirements, all Agency Actions are designed to support agencies in leveraging their data assets.</p> <p><img src="/assets/img/2020-action-plan/agency-actions.png" alt="Agency-Specific Actions" title="Agency-Specific Actions" /></p> <h3 id="action-1-identify-data-needs-to-answer-priority-agency-questions">Action 1: Identify Data Needs to Answer Priority Agency Questions</h3> <p>By September 2020, all agencies will take initial steps to identify the data needed to answer priority questions of interest to the agency.<sup id="fnref:5" role="doc-noteref"><a href="#fn:5" class="footnote" rel="footnote">1</a></sup></p> <p>For the past several years through the budget formulation process<sup id="fnref:6" role="doc-noteref"><a href="#fn:6" class="footnote" rel="footnote">2</a></sup>,OMB has encouraged agencies to develop multi-year learning agendas. A multi-year learning agenda enables agencies to systematically identify the most critical short- and long-term questions relevant to the programs, policies, and regulations of an agency. The Evidence Act now requires the development of learning agendas<sup id="fnref:7" role="doc-noteref"><a href="#fn:7" class="footnote" rel="footnote">3</a></sup>, directing CFO Act agencies to generate a multi-year learning agenda in conjunction with their strategic plans. Agencies develop learning agendas in consultation with both internal and external stakeholders, using the process to generate and organize priority agency questions that can be pursued through activities that include statistics, program evaluation, research, performance management, and policy analysis. Adopting this approach of identifying priority agency questions at the outset helps to establish a process through which an agency can allocate its statistical, performance management, research and evaluation efforts, and funding to the most critical questions that face the agency.</p> <p>This approach represents a paradigm shift in how agencies leverage data assets. Rather than constraining research based on data, the learning agenda process ensures that a research agenda starts with the priority agency questions. Once the priority agency questions have been identified, then the agency must contemplate what data are needed to answer the priority agency questions. This critical next step is also explicitly required under the Evidence Act, which states that learning agendas must include “a list of data the agency intends to collect, use, or acquire to facilitate the use of evidence in policymaking.”<sup id="fnref:8" role="doc-noteref"><a href="#fn:8" class="footnote" rel="footnote">4</a></sup> Exhibit 6 maps the process by which an agency might approach identifying data needs to answer priority agency questions.</p> <p><img src="/assets/img/2020-action-plan/data-collection-tree.png" alt="Data Collection Tree" title="Data Collection Tree" /></p> <p>The data required to answer a priority agency question might already exist — either in that agency, at another agency, or within a non-Federal entity (e.g., private firm or state/local government). The development and expansion of high-quality data inventories and data catalogs across agencies, as required by the Evidence Act and supported by Actions 6 and 17, will increase agencies’ capacity to determine whether the data required to answer priority agency questions is already collected and maintained within the Federal Government. Under circumstances where the data needed already exist, the next step would be to either directly access the data holdings, or to develop an acquisition strategy to access the needed data. Alternatively, the data required might not exist or might not be accessible because of legal or other barriers, and a new collection effort may be justified. Many agencies already have processes and procedures by which they assess the availability of data to answer priority agency questions, even if the agency does not yet have a formalized learning agenda in place.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Reporting Mechanism</th> <th>Required or Encouraged</th> </tr> </thead> <tbody> <tr> <td>Consult with key agency leaders, such as Chief Data Officers, Evaluation Officers and Statistical Officials to identify data needed to answer priority agency questions</td> <td>Completion</td> <td>September 30, 2020</td> <td>Interim Learning Agenda or FY 2022 Budget Submission</td> <td>Required for CFO Act Agencies only <br /> Encouraged for all agencies <br /> (see OMB M-19-23)</td> </tr> <tr> <td>Identify data needs for answering priority questions in the interim learning agenda</td> <td>Completion</td> <td>September 30, 2020</td> <td>Interim Learning Agenda or FY 2022 Budget Submission</td> <td>Required for CFO Act Agencies only <br /> Encouraged for all agencies <br /> (see OMB M-19-23)</td> </tr> <tr> <td>Develop a plan to engage the stakeholders needed to access or acquire the data needed to answer priority questions</td> <td>Completion</td> <td>September 30, 2020</td> <td>Interim Learning Agenda or FY 2022 Budget Submission</td> <td>Required for CFO Act Agencies only <br /> Encouraged for all agencies <br /> (see OMB M-19-23)</td> </tr> </tbody> </table> <h3 id="action-2-constitute-a-diverse-data-governance-body">Action 2: Constitute a Diverse Data Governance Body</h3> <p>All agencies were required by M-19-23 to establish an inclusive and empowered Data Governance Body (DGB) by September 30, 2019, to be chaired by the Chief Data Officer, with participation from relevant senior-level staff in agency business units, data functions, and financial management.</p> <p>By January 2020, all agencies will publish documentation related to the DGB (e.g., membership, charter, meeting cadence, and minutes) on their agency data web page (at https://[agency].gov/data) and by November 2020, all agencies will have begun enterprise-wide data governance activities such as capital planning for enterprise data assets and infrastructure, emerging priority data governance areas such as preparing data for use in artificial intelligence, and an agency data strategy or road map, or master data management program.</p> <p>The DGB should use data maturity models to assess agency capabilities (see Action 3: Assess Data and Related Infrastructure Maturity), and should also seek broad agency input before recommending data investment priorities. The DGB membership should be updated as needed.</p> <p>Agencies may refer to <em>A Playbook in Support of the Federal Data Strategy: Getting Started on Prioritizing Data Governance and Assessing Maturity</em> for guidance and support in accomplishing this action as well as Action 3.<sup id="fnref:9" role="doc-noteref"><a href="#fn:9" class="footnote" rel="footnote">5</a></sup></p> <table class="action-two-milestone-table"> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Reporting Mechanism</th> <th>Required or Encouraged</th> </tr> </thead> <tbody> <tr> <td>Publish agency data governance materials (membership, charter, meeting cadence) on [agency].gov/data web page</td> <td>Completion</td> <td>January 31, 2020</td> <td>Post to agency/data web page</td> <td>Required for all agencies</td> </tr> <tr> <td>After you complete your assessment of current staff data skills and literacy (see Action 3), dedicate staff to support DGB</td> <td>Number of FTEs dedicated</td> <td><s>September 30, 2020</s> <b>October 31, 2020*</b></td> <td>Progress Report Tool**</td> <td>Encouraged for all agencies</td> </tr> <tr> <td>Document how the DGB receives its authority</td> <td>Completion</td> <td>September 30, 2020</td> <td>Progress Report Tool**</td> <td>Encouraged for all agencies</td> </tr> <tr> <td>Put in place a data strategy or road map</td> <td>Completion</td> <td>1 activity per quarter, any order encouraged of all agencies</td> <td>Progress Report Tool** & in agency Information Resource Management Strategic Plan</td> <td>Encouraged for all agencies</td> </tr> <tr> <td>Develop a plan for capital planning for enterprise data assets and infrastructure</td> <td>Completion</td> <td>(See Above)</td> <td>(See Above)</td> <td>Encouraged for all agencies</td> </tr> <tr> <td>Adopt a master data management program</td> <td>Completion</td> <td>(See Above)</td> <td>(See Above)</td> <td>Encouraged for all agencies</td> </tr> </tbody> </table> <p>* <em>Due to government-wide focus on COVID-19 response activities, the Federal Data Strategy team has extended this target date. Read the team’s statement on our <a href="/news">News</a> page.</em></p> <p>** <em>An agency’s Chief Data Officer (CDO) is considered the main point of contact for its progress reporting and each CDO receives a unique link for the Progress Report Tool.</em></p> <h3 id="action-3-assess-data-and-related-infrastructure-maturity">Action 3: Assess Data and Related Infrastructure Maturity</h3> <p>By September 2020, all agencies will should conduct an initial maturity assessment focusing on data and related data infrastructure (e.g., organizational structures and knowledge bases, policies) to set a baseline for future improvements.</p> <p>Maturity assessments allow an organization to evaluate itself against documented best practices, determine gaps, and identify priority areas for improvement. A maturity assessment analyzes all aspects of agency policies, procedures, and operations related to data and data infrastructure, including data governance, data management, data culture, data systems and tools, data analytics, staff skills and capacity, resource capacity, and compliance with law and policy. The results of a maturity assessment feed into the data governance and management processes to inform investment decisions and to prioritize subsequent actions. A maturity assessment should be proactively communicated and explained to employees and repeated periodically, as determined by the agency, to measure progress and prioritize next steps.</p> <p>The maturity model used to conduct the maturity assessment should be chosen by the DGB established under Action 2. This assessment will identify readiness to meet other requirements of the strategy and related legal requirements and can be used to make investment decisions and to prioritize subsequent actions. Agencies may refer to <em>A Playbook in Support of the Federal Data Strategy: Getting Started on Prioritizing Data Governance and Assessing Maturity</em> for guidance and support in accomplishing this action as well as Action 2.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Reporting Mechanism</th> <th>Required or Encouraged</th> </tr> </thead> <tbody> <tr> <td>Select an operational maturity assessment model for data and data infrastructure</td> <td>Completion</td> <td><s>June 30, 2020</s> <b>July 31, 2020*</b></td> <td>Progress Report Tool**</td> <td>Required for all agencies</td> </tr> <tr> <td>Agency Chief Data Officer and other senior-level staff participate in any training or technical assistance related to maturity assessments</td> <td>Number of people attended training</td> <td>September 30, 2020</td> <td>Progress Report Tool**</td> <td>Encouraged for all agencies</td> </tr> <tr> <td>Conduct and document the outcome of the initial data maturity assessment</td> <td>Completion</td> <td>September 30, 2020</td> <td>Progress Report Tool**</td> <td>Encouraged for all agencies</td> </tr> </tbody> </table> <p>* <em>Due to government-wide focus on COVID-19 response activities, the Federal Data Strategy team has extended this target date. Read the team’s statement on our <a href="/news">News</a> page.</em></p> <p>** <em>An agency’s Chief Data Officer (CDO) is considered the main point of contact for its progress reporting and each CDO receives a unique link for the Progress Report Tool.</em></p> <h3 id="action-4-identify-opportunities-to-increase-staff-data-skills">Action 4: Identify Opportunities to Increase Staff Data Skills</h3> <p>By June 2020, all CFO Act agencies will have performed a capacity assessment to assess the coverage, quality, methods, effectiveness, of current staff data literacy and data skills. These assessments may be further leveraged by agencies to identify critical data skills, assess their staffs’ capacities for those skills, identify any gaps, and take actions to ensure that their Federal workforces are well-prepared to support evidence-building activities pursuant to M-19-23 and the Evidence Act.</p> <p>The staff data skills assessment should align with, and be a part of, ongoing human capital management efforts designed to ensure agencies have skills and competencies needed to effectively accomplish agency mission. This alignment is important since achieving parity between an agency’s data skill needs and its workforce capacity requires repeating this process over time. The assessment has four major components:</p> <ol> <li>Identify critical data skills needed for the agency</li> <li>Assess the current staff capacity for those data skills</li> <li>Perform a data skills gap analysis to prioritize the agency’s needs</li> <li>Identify and execute approaches to fill those needs</li> </ol> <p>The identification of critical data skills will naturally be informed by the determination of agency priority questions, including those gathered during the development of the learning agenda (see Action 1) and will be addressed in the agency maturity assessment (Action 3). Thoughtful consideration should also be given to identifying a minimum level of data literacy among all staff, including for those performing roles not traditionally considered data related. The agency should assess the data skills possessed by the current workforce and seek to understand data literacy rates among its staff. The gap analysis should determine how much more of each critical skill is required among staff and facilitate a prioritization of needed skills relative to available resources. Options for increasing staff skills capacity may include new analysis or other software tools, easy-to-use dashboards, additional training and educational opportunities, on-the-job rotational learning experiences, participation in data-related communities of practice, and introducing hiring and retention strategies to address gaps.</p> <p>Note: This action can also serve as one input to the capacity assessment required by CFO Act agencies under the Evidence Act, in coordination with Evaluation Officers.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Reporting Mechanism</th> <th>Required or Encouraged</th> </tr> </thead> <tbody> <tr> <td>Perform an assessment of current staff data literacy and data skills</td> <td>Completion</td> <td><s>June 30, 2020</s> <b>July 31, 2020*</b></td> <td>Progress Report Tool**</td> <td>Required for CFO Act Agencies only <br /> Encouraged for all agencies</td> </tr> <tr> <td>Conduct a gap analysis between the current staff’s skills and the skills the agency requires</td> <td>Completion</td> <td>September 30, 2020</td> <td>Progress Report Tool**</td> <td>Required for CFO Act Agencies only <br /> Encouraged for all agencies</td> </tr> <tr> <td>Based on the assessment, establish a baseline and develop a performance plan to close the identified data skills and literacy gaps</td> <td>Completion</td> <td>December 31, 2020</td> <td>Progress Report Tool**</td> <td>Required for CFO Act Agencies only <br /> Encouraged for all agencies</td> </tr> </tbody> </table> <p>* <em>Due to government-wide focus on COVID-19 response activities, the Federal Data Strategy team has extended this target date. Read the team’s statement on our <a href="/news">News</a> page.</em></p> <p>** <em>An agency’s Chief Data Officer (CDO) is considered the main point of contact for its progress reporting and each CDO receives a unique link for the Progress Report Tool.</em></p> <h3 id="action-5-identify-priority-data-assets-for-agency-open-data-plans">Action 5: Identify Priority Data Assets for Agency Open Data Plans</h3> <p>By December 2020, all agencies will identify their initial list of priority data assets for agency open data plans.<sup id="fnref:10" role="doc-noteref"><a href="#fn:10" class="footnote" rel="footnote">6</a></sup> This list will describe data assets that the agency considers especially valuable to the public interest and therefore intends to make available as open government data. Agency open data plans will include (1) processes and procedures that require data collection mechanisms created on or after January 13, 2019, facilitate open formats, and facilitate collaboration with non-Government entities (including businesses), researchers, and the public for the purpose of understanding how data users value and use government data; (2) identify methods to collect and analyze digital information on data asset usage by users within and outside of the agency, including designating a point of contact within the agency to assist the public and to respond to quality issues, usability issues, recommendations for improvements, and complaints about adherence to open data requirements within a reasonable period of time; (3) develop a process to evaluate and improve the timeliness, completeness, consistency, accuracy, usefulness, and availability of open Government data assets; and (4) includes requirements for meeting the goals of the agency open data plan, including the acquisition.</p> <p>A playbook and use cases that describe prioritization methodologies and examples of open data access to support this action will be available at <a href="https://resources.data.gov">resources.data.gov</a>.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Reporting Mechanism</th> <th>Required or Encouraged</th> </tr> </thead> <tbody> <tr> <td>Publish an Open Data Plan for sharing priority agency data assets, developed with stakeholder engagement, including data assets that support <b>COVID-19 response*</b> and AI R&D (see Action 6)</td> <td>Completion</td> <td>After OMB Open Data Plan Guidance is issued; Annually on Agency IRM Strategic Plan schedule</td> <td>Agency Information Resource Management Strategic Plan</td> <td>Required for all agencies</td> </tr> <tr> <td>Execute a process to evaluate and improve the timeliness, completeness, consistency, accuracy, usefulness, and availability of open Government data assets</td> <td>Qualitative and quantitative improvements</td> <td>December 31, 2020</td> <td><a href="https://strategy.data.gov">strategy.data.gov</a> & agency public data.json APIs</td> <td>Required for all agencies</td> </tr> </tbody> </table> <p>* <em>Due to government-wide focus on COVID-19 response activities, the Federal Data Strategy team has included COVID-19 response data assets as priority data assets for this milestone. Read the team’s statement on our <a href="/news">News</a> page.</em></p> <h3 id="action-6-publish-and-update-data-inventories">Action 6: Publish and Update Data Inventories</h3> <p>All agencies will update existing comprehensive data inventories in accordance with updated standard metadata that facilitates ingestion by <a href="https://www.data.gov">data.gov</a> and search engine optimization. At least every 90 days, all agencies will identify missing or incomplete listings in their comprehensive data inventories and ensure metadata is comprehensive for priority data assets, such as data assets included in agency Open Data Plans, identified in Community of Practice Actions 8, 9, and 10, or as identified by the Chief Data Officer Council (CDO Council).</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Reporting Mechanism</th> <th>Required or Encouraged</th> </tr> </thead> <tbody> <tr> <td>Update comprehensive data inventories for overall completeness and priority <b>COVID-19 response*</b> and AI R&D (see Action 6) data asset sprints</td> <td>Metadata quality improvements</td> <td>Minimally every 3 months, as often as possible</td> <td>Agency public data.json APIs</td> <td>Required for all agencies</td> </tr> <tr> <td>Update comprehensive data inventory to conform to standard metadata</td> <td>Completion</td> <td><s>July 31, 2020</s> <b>90 days after OMB/GSA standard metadata guidance is issued*</b></td> <td>Agency public data.json APIs</td> <td>Required for all agencies</td> </tr> </tbody> </table> <p>* <em>Due to government-wide focus on COVID-19 response activities, the Federal Data Strategy team has included COVID-19 response data assets as priority data assets for this milestone and clarified target dates based on OMB guidance dependencies. Read the team’s statement on our <a href="/news">News</a> page.</em></p> <p><a href="#main-content">Back to top</a></p> <h2 id="community-of-practice-actions">Community of Practice Actions</h2> <p>Community of Practice Actions are taken by a specific agency or group of agencies related to a common topic, usually through an established interagency council or other existing coordinating mechanism. Community of Practice Actions seek to integrate and coordinate ongoing efforts related to existing laws, regulations, and executive orders that are particularly relevant to the strategy. For this initial Action Plan, the four Community of Practice Actions included were identified as key opportunities for agencies to build upon ongoing efforts to improve and better coordinate data-related initiatives across agencies. In particular, the Community of Practice Actions included in the 2020 Action Plan capitalize on current work related to the Executive Order on Maintaining American Leadership in Artificial Intelligence, the Geospatial Data Act of 2018, the Evidence Act, and efforts related to the management and use of several financial management data assets across government. These four actions, undertaken with cross-agency collaboration, will speed and streamline the execution of existing requirements, as depicted in Exhibit 7 below.</p> <p><img src="/assets/img/2020-action-plan/community-of-practice-actions.png" alt="Community of Practice Action" title="Community of Practice Action" /></p> <h3 id="action-7-launch-a-federal-chief-data-officer-council">Action 7: Launch a Federal Chief Data Officer Council</h3> <p>By January 2020, OMB will launch, and agency CDOs will participate in, a CDO Council, as required by the Evidence Act and detailed in OMB M-19-23. The CDO Council will meet regularly, establish its priorities, and begin to develop resources as required by the Evidence Act to support CDOs in fulfilling their responsibilities under the Evidence Act. Resources may be developed in concert with the FDS team and other councils and will represent government-wide best practices for the generation, use, protection, and dissemination of data; promote and encourage data sharing agreements between agencies; and identify ways in which agencies can improve upon the production of evidence for use in policymaking. The CDO Council’s resources will reflect consultation with the public and engagement with private users of government data and other stakeholders on how to improve access to Federal data assets. In addition, the CDO Council will identify and evaluate new technology solutions for improving the collection and use of data.</p> <p>The CDO Council will share responsibility with other government-wide councils that conduct statutory, data-related activities, such as the Interagency Council on Statistical Policy (ICSP) and the Evaluation Officer Council. OMB expects that the activities of these multiple councils will be coordinated through the OMB Federal Data Policy Committee, to be established under Action 12.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Launch CDO Council</td> <td>Number of meetings held</td> <td>January 31, 2020</td> <td>OMB</td> </tr> <tr> <td>Create resources</td> <td>Number of resources published</td> <td>December 31, 2020</td> <td>CDOs</td> </tr> <tr> <td>Encourage use of resources by agencies</td> <td>Track adoption of resources by agencies</td> <td>December 31, 2020</td> <td>CDOs</td> </tr> </tbody> </table> <h3 id="action-8-improve-data-and-model-resources-for-ai-research-and-development">Action 8: Improve Data and Model Resources for AI Research and Development</h3> <p>Implementation of the Executive Order on Maintaining American Leadership in Artificial Intelligence (AI),<sup id="fnref:11" role="doc-noteref"><a href="#fn:11" class="footnote" rel="footnote">7</a></sup> is designed to improve the data and computing resources for AI research and development by February 2020. The Executive Order, issued February 2019, includes an objective to “Enhance access to high-quality and fully traceable federal data, models, and computing resources to increase the value of such resources for AI R&D, while maintaining safety, security, privacy, and confidentiality protections consistent with applicable laws and policies.” The Federal Government intends to achieve this objective by:</p> <ul> <li>Investigating barriers to access or quality limitations of Federal data and models that impede AI R&D and testing. A Request for Information (RFI) was issued as a Federal Register Notice by OMB<sup id="fnref:12" role="doc-noteref"><a href="#fn:12" class="footnote" rel="footnote">8</a></sup> inviting the public to identify needs for additional access to, or improvements in the quality of, Federal data and models that would improve the nation’s AI R&D and testing efforts.</li> <li>Addressing identified barriers by updating Federal data and source code inventory guidance for agencies to utilize in enhancing the discovery and usability of Federal data and models in AI R&D. The implementation guidance provides supports agencies in: <ul> <li>Prioritizing the data assets and models under their purview for discovery, access, and enhancement;</li> <li>Assessing the level of effort needed to make necessary improvements in data sets and models, against available resources; and</li> <li>Developing justifications for additional resources.</li> </ul> </li> <li>Incorporating updated inventory technical schema formats into Action 11 (Develop a Repository of Federal Enterprise Data Resources) and Action 5 (Identify Priority Data Assets for Agency Open Data Plans) of the 2020 Action Plan.</li> <li>Selecting pilot(s) to demonstrate how to enhance access to discoverable and useable Federal data and models, including mature, high-quality Federal training data assets.</li> </ul> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Identify barriers to access and quality limitations</td> <td>Completion of RFI</td> <td>February 29, 2020</td> <td>OMB*</td> </tr> <tr> <td>Provide technical schema formats on inventories</td> <td>Completion</td> <td>December 31, 2020</td> <td>OMB*</td> </tr> <tr> <td>Pilot demonstration of how access to data useful for AI should be enhanced</td> <td>Completion</td> <td>December 31, 2020</td> <td>CDOs</td> </tr> </tbody> </table> <p>* <em>In consultation with the National Science and Technology Council Machine Learning and AI Subcommittee and the CDO Council.</em></p> <h3 id="action-9-improve-financial-management-data-standards">Action 9: Improve Financial Management Data Standards</h3> <p>The PMA includes a series of CAP Goals that address “functional priority areas for transformation” across government, several of which address improved financial management practices. Three specific CAP Goals have been selected for inclusion in the 2020 Action Plan due to their focus on financial management data assets. By September 2020, the Federal Government, through implementation of the identified CAP Goals below, will have improved the management and use of several financial management data assets.</p> <ul> <li><strong>Getting Payments Right</strong>: CAP Goal 9 directs agencies to save taxpayer money by making payments correctly and collecting money back from incorrect payments. Agencies will accomplish this by employing strategic use of financial data and other mitigation strategies at the point in the payment process where the improper payment is occurring, and clarifying and streamlining reporting and compliance requirements to focus on actions that make a difference.</li> <li><strong>Results Oriented Accountability for Grants</strong>: Agencies will maximize the value of grant funding by applying a risk-based, data-driven framework that balances compliance requirements with demonstrating successful results for the American taxpayer.</li> <li><strong>Promote public trust in the stewardship of taxpayer dollars</strong>: The Federal Government will engage stakeholders and decision-makers to develop a draft Federal Financial Data Strategy to open, connect, and demonstrate value while promoting public trust in financial management transparency and accountability in a way that meets user needs while minimizing reporting burden and orienting the business of government around data.</li> <li><strong>The IT Spending Transparency Maturity Model</strong> will be a consensus-driven tool that will assist agencies in measuring the current and future state of their Technology Business Management (TBM) implementations. It will be developed through the Chief Information Officer (CIO) Council’s <a href="https://community.max.gov/display/Egov/CIO+Council%27s+Federal+Technology+Investment+Management+%28FTIM%29+Community+of+Practice">Federal Technology Investment Management (FTIM) Community of Practice</a> with the support of <a href="https://www.actiac.org/">ACT-IAC</a> industry volunteers.*</li> </ul> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Getting Payments Right</td> <td>Metrics related to this CAP Goal are being tracked on <a href="https://performance.gov">performance.gov</a><sup id="fnref:13" role="doc-noteref"><a href="#fn:13" class="footnote" rel="footnote">9</a></sup></td> <td>See timeline on <a href="https://performance.gov">performance.gov</a></td> <td>Getting Payments Right Executive Steering Committee</td> </tr> <tr> <td>Results Oriented Accountability for Grants</td> <td>Metrics related to this CAP Goal are being tracked on <a href="https://performance.gov">performance.gov</a><sup id="fnref:14" role="doc-noteref"><a href="#fn:14" class="footnote" rel="footnote">10</a></sup></td> <td>See timeline on <a href="https://performance.gov">performance.gov</a></td> <td>CAP Goal 8 Executive Steering Committee</td> </tr> <tr> <td>Promote public trust in the stewardship of taxpayer dollars</td> <td>Publication of draft strategy</td> <td>September 30, 2020</td> <td>Financial Data Transformation Executive Steering Committee<sup id="fnref:15" role="doc-noteref"><a href="#fn:15" class="footnote" rel="footnote">11</a></sup></td> </tr> <tr> <td>Develop an IT spending transparency maturity assessment model*</td> <td>Completion</td> <td>September 30, 2020</td> <td>CIO Council Federal Technology Investment Management Community of Practice</td> </tr> </tbody> </table> <p>* *This activity and milestone have been transferred to the 2020 Action Plan from the “<a href="https://www.performance.gov/CAP/tbm/">Improving Outcomes Through Federal IT Spending Transparency</a>” CAP Goal team.</p> <h3 id="action-10-integrate-geospatial-data-practices-into-the-federal-data-enterprise">Action 10: Integrate Geospatial Data Practices into the Federal Data Enterprise</h3> <p>By December 2020, the Federal Geographic Data Committee (FGDC), in coordination with the OMB Federal Data Policy Committee (FDPC), will improve the value of, and access to, geospatial data and services for use across the Federal data enterprise and the public through the implementation of the Geospatial Data Act (GDA). Through this action, FGDC members will coordinate with their agency DGB, their Senior Agency Official for Geospatial Information (SAOGI), and the FDPC on the use and integration of geospatial data into broader Federal efforts.</p> <p>The Federal Government, through the FGDC with input from and in partnership with representatives from state, local, and tribal governments, the private sector, and institutions of higher education, will develop the National Spatial Data Infrastructure (NSDI) strategic plan to ensure geospatial data from multiple Federal and non-Federal sources are available and easily integrated to enhance decision-making.</p> <p>The SAOGI at OMB will assist the FGDC in ensuring FGDC cross-representation on appropriate data oversight bodies to help spatially enable the Federal data enterprise. FGDC members will work with the other oversight bodies to establish a process to develop consistent identification of the spatial attributes of both spatial datasets (data with feature geometry) and non-spatial datasets with location attributes (e.g., address, coordinates, county name). This engagement will lay the foundation that enables the relating or joining of data with like spatial attributes to add contextual value and provide a catalyst for innovative data use and spatial analytics.</p> <p>The FGDC will operate an electronic service known as the GeoPlatform and provide access to geospatial data and related metadata for all National Geospatial Data Assets (NGDA), excluding public disclosure of any information that reasonably could be expected to cause damage to the national interest, security, or defense of the nation; and provide standards-compliant metadata and standards-compliant web services for all NGDA data assets, registered with <a href="https://www.data.gov">data.gov</a> and available as web services through the GeoPlatform.</p> <p>The Federal Government’s lead agencies for NGDA data assets will identify, inventory, and publish the status and standards being used for each of the NGDA data themes and content and services metadata, consistent with international standards, excluding public disclosure of any information that reasonably could be expected to cause damage to the national interest, security, or defense of the nation.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Establish the NSDI strategic plan</td> <td>Completion</td> <td>December 31, 2020</td> <td>SAOGI at OMB, FGDC, FGDC NGDA Lead Covered Agencies, GSA</td> </tr> <tr> <td>Publish a GeoPlatform providing standards-compliant web services for NGDAs</td> <td>Completion</td> <td>December 31, 2020</td> <td>SAOGI at OMB, FGDC, FGDC NGDA Lead Covered Agencies, GSA</td> </tr> <tr> <td>Engage with other relevant councils</td> <td>Number of engagements</td> <td>December 31, 2020</td> <td>SAOGI at OMB, FGDC, FGDC NGDA Lead Covered Agencies, GSA</td> </tr> <tr> <td>Publish NGDA data theme data assets with standards compliant metadata and webservice endpoints</td> <td>Percentage of NGDA data assets that are compliant</td> <td>December 31, 2020</td> <td>SAOGI at OMB, FGDC, FGDC NGDA Lead Covered Agencies, GSA</td> </tr> <tr> <td>Track NGDAs for implementation of standards</td> <td>Percentages of NGDAs with: i) metadata standards, ii) established content standards, iii) standards in process, iv) data assets not requiring standards, v) no established standards</td> <td>12 months</td> <td>SAOGI at OMB, FGDC, FGDC NGDA Lead Covered Agencies, GSA</td> </tr> </tbody> </table> <p><a href="#main-content">Back to top</a></p> <h2 id="shared-solution-actions">Shared Solution Actions</h2> <p>Shared Solution Actions are described as government-wide data services and represent discrete pilot projects or efforts led by a single agency or existing council for the benefit of all agencies. The ten Shared Solution Actions identified in the 2020 Action Plan are designed to provide government-wide direction, tools, and/or services for implementing the strategy that other agencies will be able to leverage in the future. Many of the Shared Solution Actions have received financial resources as part of the CAP Goal: <em>Leveraging Data as a Strategic Asset</em> and are already underway. Similar to the Agency Actions and the Community of Practice Actions, the Shared Solution Actions will also support agencies as they implement existing policies and laws. For example, the Curated Data Skills Catalog to be developed under Action 13 will be available for use by all agencies in support of implementation of both the Evidence Act and the Executive Order on Maintaining American Leadership in Artificial Intelligence, both of which require an assessment of staff capacity for various data-related functions. The graphic below maps each of the ten Shared Solution Actions to a set of relevant laws and guidance.</p> <p><img src="/assets/img/2020-action-plan/shared-solution-actions.png" alt="Shared Solution Actions" title="Shared Solution Actions" /></p> <h3 id="action-11-develop-a-repository-of-federal-enterprise-data-resources">Action 11: Develop a Repository of Federal Enterprise Data Resources</h3> <p>By December 2020, the General Services Administration (GSA), the Office of Government Information Services of the National Archives, and OMB will collaborate with stakeholders to develop the website <a href="https://resources.data.gov">resources.data.gov</a>, a government-wide repository of policies, standards, tools, best practices, and case studies that is required under the Evidence Act.<sup id="fnref:16" role="doc-noteref"><a href="#fn:16" class="footnote" rel="footnote">12</a></sup> This repository, titled <em>Federal Enterprise Data Resources</em>, has been established to provide centralized access to resources related to Federal data management and use in support of agencies as they seek to execute both the FDS and the requirements of the Evidence Act.<sup id="fnref:17" role="doc-noteref"><a href="#fn:17" class="footnote" rel="footnote">13</a></sup> The repository will include the following types of resources:</p> <ul> <li><strong>Case Studies</strong>: Examples of what agencies are currently implementing</li> <li><strong>Data.gov Schema</strong>: The standard metadata schema required for inclusion in <a href="https://www.data.gov">data.gov</a>, the Federal data catalog<sup id="fnref:18" role="doc-noteref"><a href="#fn:18" class="footnote" rel="footnote">14</a></sup></li> <li><strong>Federal Data Strategy</strong>: Guiding principles and best practices and associated implementation tools</li> <li><strong>Playbooks</strong>: Decision points, checklists, and questions that help organizations navigate options</li> <li><strong>Requirements</strong>: Definitions, laws, policies, and regulations</li> <li><strong>Skill Builders</strong>: Professional development resources and curriculums to improve data-related skills</li> <li><strong>Standards</strong>: Guidance on preferred technical formats, licensing, and resources related to implementing data standards</li> <li><strong>Tools</strong>: Tools available to agencies to help execute data goals</li> </ul> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Make regular updates to <a href="https://resources.data.gov">resources.data.gov</a> in response to stakeholder input</td> <td>Frequency of feature updates and site improvements</td> <td>December 31, 2020</td> <td>GSA</td> </tr> <tr> <td>Track growth and success of the site</td> <td>Number of resources available by type, resource usage</td> <td>December 31, 2020</td> <td>GSA</td> </tr> <tr> <td>Engage stakeholders to prioritize content</td> <td>Number of stakeholder engagement activities</td> <td>December 31, 2020</td> <td>GSA, the Office of Government Information Services of the National Archives, and OMB</td> </tr> </tbody> </table> <h3 id="action-12-create-omb-federal-data-policy-committee">Action 12: Create OMB Federal Data Policy Committee</h3> <p>By January 2020, OMB will establish the FDPC that will help agencies deliver on mission and effectively steward taxpayer dollars by enhancing OMB’s coordination of Federal data policy, governance, and resource considerations. OMB has statutory responsibility and coordinates many government-wide priorities and functions, many of which have a data-related dimension. The FDPC will be a mechanism to coordinate OMB’s own data policy development and implementation activities for the Federal Government, including those necessary for the executive branch to meet existing and new legal requirements as well as addressing emerging priority data governance areas such as preparing data for use in artificial intelligence. Over time, the FDPC will also provide a forum for OMB offices to address selected data issues that cross agencies or span executive councils’ responsibilities. The FDPC is responsible for government-wide management, governance, and resource priorities for data management standardization and use, including by contributing to the FDS’s annual action plans and align transformation efforts to reduce costs, duplication, and burden. The FDPC will be comprised of senior staff representing OMB’s statutory and programmatic areas, including offices responsible for evaluation, financial management, information technology, performance management, privacy, procurement, regulations, resource management, and statistical policy. The FDPC’s charter will specify roles and responsibilities. OMB’s approach to working across its functional areas will furthermore serve as a model for individual agencies to bridge their own functional silos.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Launch FDPC</td> <td>Number of meetings held</td> <td>January 31, 2020</td> <td>OMB</td> </tr> <tr> <td>Set priorities for 2020</td> <td>Completion of written priorities endorsed by membership</td> <td>March 31, 2020</td> <td>OMB</td> </tr> <tr> <td>Carry out at least 1 data policy coordination activity</td> <td>Number of data policy related memorandum and circulars updated, streamlined, or rescinded</td> <td>December 31, 2020</td> <td>OMB</td> </tr> </tbody> </table> <h3 id="action-13-develop-a-curated-data-skills-catalog">Action 13: Develop a Curated Data Skills Catalog</h3> <p>By November 2020, GSA will complete a curated data skills catalog of learning opportunities to help agencies develop competencies for managing data as a strategic asset and making data-driven decisions. This skills catalog will be aligned to Federal needs for information about existing learning providers, programs, courses, certifications and other credentials, and opportunities for employees to practice and apply new skills.</p> <p>The catalog will incorporate Federal and non-Federal stakeholder input and will be released in multiple stages to allow useful content to be available as soon as it is ready rather than in a single, delayed release. Demand for skills identified in other parts of the FDS, including Action 4, will inform the priorities for how the catalog is built.</p> <p>This resource will incorporate information about significant roles in the data ecosystem into its organization and take into account skills, experience, and responsibilities of key job functions as well as support the results of data maturity assessments agencies will do as part of Action 3.</p> <p>The contents of the catalog will initially be available to the CDOs of each agency as well as other relevant Federal communities as it is being built. Contributions to its development will be encouraged from other groups throughout the process.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Share draft catalog contents with CDOs and other stakeholders</td> <td>Completion</td> <td>February 29, 2020</td> <td>GSA</td> </tr> <tr> <td>Collect input and make revisions</td> <td>Number of stakeholder engagement activities; Improvements added</td> <td>June 30, 2020</td> <td>GSA</td> </tr> <tr> <td>Publish the catalogue on <a href="https://resources.data.gov">resources.data.gov</a></td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a>; Number of resources available in the catalog by data role</td> <td>November 30, 2020</td> <td>GSA</td> </tr> <tr> <td>Transfer responsibility for maintenance to the CDO council</td> <td>Completion</td> <td>December 31, 2020</td> <td>CDO Council</td> </tr> </tbody> </table> <h3 id="action-14-develop-a-data-ethics-framework">Action 14: Develop a Data Ethics Framework</h3> <p>By December 2020, GSA will develop a data ethics framework to help agencies systematically identify and assess the potential benefits and risks associated with the data they acquire, manage, and use. This framework is intended to help agency staff, managers, and leaders make considered data acquisition, management, and use decisions to address ethical issues they may encounter throughout the data lifecycle. The framework will be broad and flexible – outlining and describing high-level principles that can be applied to specific circumstances, such as preparing data for the responsible and ethical use of evolving technologies, including mitigating bias when developing AI and machine learning methods and systems.</p> <p>Once the completed framework and associated implementation tools are published, they will be promoted government-wide for agency use via the CDO Council, ICSP, and various other channels. Fully integrating a data ethics perspective into all aspects of agencies’ data management efforts will require substantial and long-term cultural change. It would involve staff at all levels undergoing training to support and refresh data literacy skills and reinforce protocols related to data privacy, confidentiality, and the ethical collection, use, storage, and dissemination of data. Leadership support, spearheaded by CDOs and Statistical Officials, is crucial, as is agency input into the design of tailored ethics frameworks and their implementation.</p> <p>Initial work to develop a data ethics framework has already begun with a review of data ethics frameworks developed by other countries, organizations, and advocacy groups to identify common elements and themes to inform development of a U.S. data ethics framework. Next, an inter-agency team will conduct iterative Federal and non-Federal stakeholder engagement. This process will employ a variety of consultation, design, and assessment approaches to ensure broad input into the framework, such as:</p> <ul> <li><em>Framework prototypes</em>: Creating prototypes based on ideas from various user communities on the design, construction, and structure of the framework.</li> <li><em>Open and targeted feedback</em>: Sharing draft concepts and a draft framework to enable stakeholders to meaningfully engage and provide input.</li> <li><em>Pilots</em>: Encouraging agencies to pilot a prototype framework using their own data management processes and provide specific feedback about its utility, completeness, and drawbacks.</li> <li><em>Use cases</em>: Developing use cases to illustrate the application of the framework across the data lifecycle.</li> </ul> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Initial examination of ethical issues encountered across data life cycle</td> <td> </td> <td>June 30, 2020</td> <td>GSA with CDO Council and ICSP</td> </tr> <tr> <td>Release initial data ethics framework and use cases</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>December 31, 2020</td> <td>GSA</td> </tr> <tr> <td>Transfer responsibility for review and update</td> <td> </td> <td>Ongoing every 24 months</td> <td>CDO Council, ICSP</td> </tr> </tbody> </table> <h3 id="action-15-develop-a-data-protection-toolkit">Action 15: Develop a Data Protection Toolkit</h3> <p>By December 2020, the Federal Committee on Statistical Methodology (FCSM), with direction from the ICSP, and the Department of Education will develop a data protection toolkit. The way the Federal Government provides, maintains, and uses data has a unique place in society because use of Federal data has a tremendous impact on the public, businesses, and our democratic process. This trust includes protecting or excluding private information when releasing data publicly. By developing this critical community resource, the Federal Government is demonstrating commitment to strengthening privacy and confidentially promises now and into the future.</p> <p>This action is designed to address the need to maintain confidentiality and data privacy when providing access to Federal data assets due to the threat of the growing threat of re-identification risk to individuals and businesses from combining publicly available data. Once completed, the data protection toolkit can be used by agencies to develop and implement cost-effective data protection programs. This web-based toolkit will provide a repository for best practices regarding confidentiality and data privacy practices based on existing and emerging standards in partnership with agencies, academia, and industry. The toolkit is intended to serve as a central resource for guidance, tools, and templates to help agencies avoid the unintentional release of data assets that could be used to re-identify individual people or entities.</p> <p>In addition to developing the toolkit, the FCSM will update the 2005 Report on Statistical Disclosure Limitation Methodology<sup id="fnref:19" role="doc-noteref"><a href="#fn:19" class="footnote" rel="footnote">15</a></sup>, which has served as a primary reference for agencies on approaches for maintaining confidentiality and data privacy in Federal data releases. The revision will include more detailed guidance for agencies on assessing, managing, and mitigating the risk that individuals or enterprises are re-identified.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Release initial toolkit</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>December 31, 2020</td> <td>FCSM</td> </tr> <tr> <td>Release updated Report on Statistical Disclosure Limitation Methodology</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>December 31, 2020</td> <td>FCSM</td> </tr> </tbody> </table> <h3 id="action-16-pilot-a-one-stop-standard-research-application">Action 16: Pilot a One-stop Standard Research Application</h3> <p>By March 2020, the Federal Statistical Research Data Center Program Management Office of the U.S. Census Bureau, under the direction of the ICSP, will pilot the first phase of a one-stop portal that reduces the burden on researchers requesting access to restricted Census Bureau data assets. The current process for obtaining restricted data from multiple agencies for research and evidence-building purposes is fragmented, uncoordinated, and requires following a different application process for each agency. Standardizing the application process will eliminate confusion, reduce complexity, improve the user experience, and reduce the wait time to access data, which can range from months to years.</p> <p>Agencies with active researcher access programs will collaborate with each other and their stakeholder communities to reduce the burden resulting from duplicative and non-standard access request application forms. This standard approach will assist agencies in setting consistent access protocols as required by the Evidence Act. In addition to informing future phases of this pilot, these efficiencies will improve and expand access to data for evidence-building while promoting transparency.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Create pilot portal</td> <td>Completion</td> <td>March 31, 2020</td> <td>Census Bureau</td> </tr> <tr> <td>Recruit users to try the portal and give feedback</td> <td>Number of users</td> <td>April 30, 2020</td> <td>Census Bureau</td> </tr> <tr> <td>Publish report describing success of the project and feedback that will inform future improvements</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>December 31, 2020</td> <td>Census Bureau</td> </tr> </tbody> </table> <h3 id="action-17-pilot-an-automated-tool-for-information-collection-reviews-that-supports-data-inventory-creation-and-updates">Action 17: Pilot an Automated Tool for Information Collection Reviews that Supports Data Inventory Creation and Updates</h3> <p>By July 2020, the National Center for Education Statistics (NCES) within the U.S. Department of Education will complete a pilot of an automated tool that leverages agency Information Collection Review (ICR) processes and documentation to build agency data inventories and update metadata in agency data inventories. Under the Paperwork Reduction Act,<sup id="fnref:20" role="doc-noteref"><a href="#fn:20" class="footnote" rel="footnote">16</a></sup> all agencies must undergo an ICR in order to gain approval from OMB to collect information from the public. For many agencies, a substantial fraction of data inventory items originate with an information collection.</p> <p>The automated tool generated under this action will include an electronic template and database management system that facilitates the development and standardization of the content of ICRs developed by agencies for OMB review. The template will have fields that include metadata needed in the agency data inventory that will be tagged in the underlying database. After the agency CDO certifies, and OMB approves, the ICR, the tagged items can be extracted for the agency data inventory. This automated tool will support the inventory requirements under the Evidence Act by organizing metadata captured as part of the information collection design phase into agency inventories. However, this template will only collect some of the information needed for a complete inventory. Metadata resulting from the completed collection (e.g., response rates, variable names, labels, URL for report and data) will need to be acquired through other means before the inventory update can be completed.</p> <p>This action will begin a multi-year process of deploying an automated approach to populating needed information on agency data inventories using information that is already required to approve ICRs through what has traditionally been a separate process. This project will help address public, cross-agency, and intra-agency needs for data discovery and access by leveraging these existing processes and information. In so doing, the amount of metadata generated by agencies will go beyond the minimum standards currently required,<sup id="fnref:21" role="doc-noteref"><a href="#fn:21" class="footnote" rel="footnote">17</a></sup> and better enable prospective data users to understand the degree to which an already collected data asset can meet their needs. Agency input will be used to inform development and expansion of this pilot.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Develop pilot tool</td> <td>Completion</td> <td>July 31, 2020</td> <td>NCES</td> </tr> <tr> <td>Test tool with at least two agencies</td> <td>Completion</td> <td>December 31, 2020</td> <td>NCES</td> </tr> <tr> <td>Engage stakeholders for feedback on the tool</td> <td>Number of stakeholder engagement activities</td> <td>December 31, 2020</td> <td>NCES</td> </tr> <tr> <td>Publish report describing agency tests and stakeholder input</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>December 31, 2020</td> <td>NCES</td> </tr> </tbody> </table> <h3 id="action-18-pilot-enhanced-data-management-tool-for-federal-agencies">Action 18: Pilot Enhanced Data Management Tool for Federal Agencies</h3> <p>By September 2020, GSA will have developed and piloted an improved tool for metadata management, data hosting, and API capabilities in support of open data and Federal data catalog requirements under the Evidence Act. Currently, most agencies have to identify their own solution for managing their data inventories, metadata, and APIs. This project will provide agencies with an option to use a centrally developed and hosted data management tool, designed to reduce cost and workload at any individual agency.</p> <p>GSA will create a government-wide platform pilot with a shared code base and cloud hosting that is customizable to support agency needs, leveraging <a href="https://www.data.gov">data.gov</a>’s existing open source codebase. This approach can provide agencies with a cost-effective option to manage metadata and data assets, host data assets for public access, assist in the improvement in the quality of metadata and result in increased use and improved user experience for the public and for agencies.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Demonstrate pilot and initial feature set with a pilot agency</td> <td>Completion</td> <td>March 31, 2020</td> <td>GSA</td> </tr> <tr> <td>Infrastructure/security roadmap for production platform</td> <td>Completion</td> <td>March 31, 2020</td> <td>GSA</td> </tr> <tr> <td>Achieve interoperability with continually updated Federal open data metadata schema</td> <td>Completion</td> <td>June 30, 2020</td> <td>GSA</td> </tr> <tr> <td>Develop business plan and cost model</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>June 30, 2020</td> <td>GSA</td> </tr> <tr> <td>Onboard agency customers</td> <td>Number of agencies onboarded</td> <td>September 30, 2020</td> <td>GSA</td> </tr> <tr> <td>Demonstrate increased data asset availability and improved usage</td> <td>Number of datasets and usage of data assets through platform</td> <td>December 31, 2020</td> <td>GSA</td> </tr> </tbody> </table> <h3 id="action-19-develop-data-quality-measuring-and-reporting-guidance">Action 19: Develop Data Quality Measuring and Reporting Guidance</h3> <p>By December 2020, the FCSM, under direction of the ICSP, will:</p> <ul> <li>Identify best practices for measuring and reporting on the quality of data outputs created from multiple sources or from secondary use of data assets;</li> <li>Develop documentation best practices for agencies to apply to administrative or programmatic data likely to be secondarily useful, such as for evidence building; and</li> <li>Create tools to help agencies follow practices to support effective secondary uses of data.</li> </ul> <p>Assessing the fitness for specific uses of data is critical to leveraging data effectively. Such an assessment answers the question: Does a data asset have an appropriate level of accuracy, timeliness, and relevance to support the intended use? This action facilitates such assessments by articulating best practices for reporting on the quality of data outputs. Such best practices may include, for example, documentation of a data asset’s representativeness, precision, and coherence. Consistent reporting on such elements allows stakeholders to make informed choices about their use of the data outputs. The action builds on FCSM’s past and current efforts to assess the utility of administrative data for statistical uses, measure data quality in statistical outputs, and establish best practices for reporting on data quality to the public.</p> <p>The action promotes the effective application of these data best practices by encouraging agencies that originate data to maintain metadata that supports data quality measurement. Such metadata may include, for example, information about potential and actual data providers, ways in which data is gathered, and adjustments made to the data during processing. By pairing the guidance with tools such as metadata templates, the action aims to cultivate data quality reporting in a coordinated Federal Government context.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Completion of report on best practices for reporting on output quality</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td><s>June 30, 2020</s> <b>September 30, 2020*</b></td> <td>FCSM</td> </tr> <tr> <td>Completion of metadata guidance for use by data originators</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>December 31, 2020</td> <td>FCSM</td> </tr> <tr> <td>Develop tools to aid metadata maintenance</td> <td>Posted to <a href="https://resources.data.gov">resources.data.gov</a></td> <td>December 31, 2020</td> <td>FCSM</td> </tr> </tbody> </table> <p>* <em>Due to government-wide focus on COVID-19 response activities, the Federal Data Strategy team has extended this target date. Read the team’s statement on our <a href="/news">News</a> page.</em></p> <h3 id="action-20-develop-a-data-standards-repository">Action 20: Develop a Data Standards Repository</h3> <p>By December 2020, GSA will collaborate with OMB, in consultation with the National Institute of Standards and Technology, to create a data standards repository to accelerate the creation and adoption of data standards across agencies. It will include information about the different types of existing standards of all types (e.g., metadata, content, classification), including policies related to using voluntary consensus standards, information about standards-developing organizations and communities of practices inside and outside of government, and a catalog of data standards already in use by the Federal Government. The repository will connect to <a href="https://resources.data.gov">resources.data.gov</a> and will leverage existing repositories of standards-developing methods and tools, and efforts such as the U.S. Data Federation, the National Information and Exchange Model (<a href="https://www.niem.gov">niem.gov</a>), and Federal and non-Federal partner community repositories such as the Common Education Data Standards (<a href="https://ceds.ed.gov">ceds.ed.gov</a>), Fair Sharing (<a href="https://www.fairsharing.org">fairsharing.org</a>), and Registry of Research Data Repositories (<a href="https://www.re3data.org">re3data.org</a>). The data standards repository will be designed as a user-friendly website in support of both more and less technical users.</p> <table> <thead> <tr> <th>Milestone</th> <th>Measurement</th> <th>Target Date</th> <th>Responsible Party</th> </tr> </thead> <tbody> <tr> <td>Develop repository with communities, frameworks, and schemas</td> <td>Completion</td> <td>December 31, 2020</td> <td>GSA and OMB</td> </tr> </tbody> </table> <h2 id="looking-forward">Looking Forward</h2> <p>The FDS, presented in final form in OMB Memorandum M-19-18, <em>Federal Data Strategy - A Framework for Consistency</em>, describes a ten-year vision for how the Federal Government will accelerate the use of data to deliver on mission, serve the public, and steward resources—while protecting security, privacy, and confidentiality. Fully implementing the 40 practices described in the strategy will require a sustained, iterative, and systematic effort over a ten-year period. The Action Plans produced each year will identify priority actions for a given year and incrementally build on progress from year to year, capitalizing on the successes of previous efforts, aligning with ongoing Federal Government programs and policies, and complementing new statutory requirements. In this way, the strategy recognizes the dynamic environment in which agencies must implement the strategy. The production of annual Action Plans allows the implementation of the strategy to adapt each year to adjust to new laws, requirements, and priorities that will impact agencies’ capacity to leverage data as a strategic asset.</p> <p>Future annual Action Plans will build on the 2020 Action Plan to further develop a coordinated approach to Federal data stewardship. Feedback from stakeholders has and will continue to identify key topic areas for future annual Action Plans, such as attention to data quality, increasing opportunities for safe data-sharing, increasing data literacy throughout the Federal workforce, and addressing organizational culture in support of leveraging data as a strategic asset. Future annual Action Plans will build on and expand the efforts taken by agencies to advance the mission of the FDS to leverage the full value of Federal data, in alignment with American values, for mission, service, and the public good.</p> <p><a href="#main-content">Back to top</a></p> <h4 class="footnotes" id="footnotes">Footnotes</h4> <div class="footnotes" role="doc-endnotes"> <ol> <li id="fn:5" role="doc-endnote"> <p>The provisions under Title I of the Evidence Act apply to the 24 agencies identified in the Chief Financial Officers Act of 1990 (CFO Act) in 31 U.S.C. §901(b), but OMB Memorandum M-19-23 strongly recommends participation of all non-CFO Act agencies, and sub-agencies, operational divisions, and bureaus of CFO Act agencies. Thus, this requirement is only mandatory for agencies that are subject to the Evidence Act’s mandatory requirements but encouraged for all others. <a href="#fnref:5" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:6" role="doc-endnote"> <p>President’s FY2019 Budget: Building and Using Evidence to Improve Government Effectiveness (Analytical Perspectives) <a href="#fnref:6" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:7" role="doc-endnote"> <p>Use of the terminology “learning agendas” are equivalent to the “agency evidence-building plans,” as required in the Evidence Act. 5 U.S.C. §312(a). <a href="#fnref:7" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:8" role="doc-endnote"> <p>5 U.S.C. §312(a). <a href="#fnref:8" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:9" role="doc-endnote"> <p>A Playbook in Support of the Federal Data Strategy: Getting Started on Prioritizing Data Governance and Assessing Maturity can be found in the repository at <a href="https://resources.data.gov">resources.data.gov</a>. <a href="#fnref:9" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:10" role="doc-endnote"> <p>The Evidence Act directs all agencies to develop an Open Data Plan that identifies “priority data assets, that is, any data asset for which disclosure would be in the public interest and establishes a plan to evaluate each priority data asset for disclosure on the Federal Data Catalogue, including an accounting of which priority data assets have not yet been evaluated.” See 44 U.S.C. §3506. <a href="#fnref:10" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:11" role="doc-endnote"> <p>See Executive Order on Maintaining American Leadership in Artificial Intelligence (2019) available at: <a href="https://www.whitehouse.gov/presidential-actions/executive-order-maintaining-american-leadership-artificial-intelligence/">www.whitehouse.gov/presidential-actions/executive-order-maintaining-american-leadership-artificial-intelligence/</a> <a href="#fnref:11" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:12" role="doc-endnote"> <p>See the Federal register Notice available at: <a href="https://www.federalregister.gov/documents/2019/07/10/2019-14618/identifying-priority-access-or-quality-improvements-for-federal-data-and-models-for-artificial">www.federalregister.gov/documents/2019/07/10/2019-14618/identifying-priority-access-or-quality-improvements-for-federal-data-and-models-for-artificial</a> <a href="#fnref:12" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:13" role="doc-endnote"> <p>See a full description of the CAP Goal available at: <a href="https://www.performance.gov/CAP/getting-payments-right/">www.performance.gov/CAP/getting-payments-right/</a> <a href="#fnref:13" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:14" role="doc-endnote"> <p>See a full description of the CAP Goal available at: <a href="https://www.performance.gov/CAP/grants/">www.performance.gov/CAP/grants/</a> <a href="#fnref:14" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:15" role="doc-endnote"> <p>With approval and concurrence from OMB <a href="#fnref:15" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:16" role="doc-endnote"> <p>44 U.S.C. §3511(c)(2). <a href="#fnref:16" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:17" role="doc-endnote"> <p>44 U.S.C. §3511 <a href="#fnref:17" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:18" role="doc-endnote"> <p>44 U.S.C. §3511(c)(2). <a href="#fnref:18" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:19" role="doc-endnote"> <p>See Report on Statistical Disclosure Limitation Methodology available at: <a href="https://nces.ed.gov/FCSM/pdf/spwp22.pdf">nces.ed.gov/FCSM/pdf/spwp22.pdf</a> <a href="#fnref:19" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:20" role="doc-endnote"> <p>44 U.S.C. §3501 et seq. <a href="#fnref:20" class="reversefootnote" role="doc-backlink">↩</a></p> </li> <li id="fn:21" role="doc-endnote"> <p>Government-wide metadata standards are available at <a href="https://resources.data.gov">resources.data.gov</a> <a href="#fnref:21" class="reversefootnote" role="doc-backlink">↩</a></p> </li> </ol> </div> </div> </main>  <footer class="usa-footer usa-footer-big" role="contentinfo"> <div class="usa-grid usa-footer-return-to-top"> <a href="#main-content">Return to top</a> </div> <div class="usa-footer-basic"> <div class="usa-grid"> <div class="usa-footer-logo usa-width-one-half"> <h5 class="usa-footer-logo-heading"> <img class="usa-footer-logo-img" src="/assets/img/logo-omb.png" height="40px" alt="Logo image" />  <a href="https://www.whitehouse.gov/omb/">Office of Management and Budget</a> </h5> <br /> <h5 style="margin-top: 0" class="usa-footer-logo-heading"> <img class="usa-footer-logo-img" src="/assets/img/logo-cdo.png" height="40px" alt="Logo image" />  <a href="https://www.cdo.gov">CDO Council</a> </h5> <br /> <h5 style="margin-top: 0" class="usa-footer-logo-heading"> <img class="usa-footer-logo-img" src="/assets/img/logo-gsa.png" height="40px" alt="Logo image" />  <a href="https://www.gsa.gov">General Services Administration</a> </h5> <h5 style="margin-top: 0"> </h5> </div> <div class="usa-footer-contact-links usa-width-one-half"> <h5>Contact the OMB FDS Team:<br /><a href="mailto:datastrategy@omb.eop.gov">datastrategy@omb.eop.gov</a></h5> <h5>Website managed by:<br /><a href="https://www.gsa.gov/tts">GSA Technology Transformation Services</a></h5> <h5> For Website Issues:<br /><a href="https://github.com/GSA/data-strategy/issues">Report a bug on GitHub</a> </h5> </div> </div> </div> </footer> <div class="usa-identifier"> <section class="usa-identifier__section usa-identifier__section--masthead" aria-label="Agency identifier,,,"> <div class="usa-identifier__container"> <div class="usa-identifier__identity" aria-label="Agency description"> <p class="usa-identifier__identity-domain">strategy.data.gov</p> <p class="usa-identifier__identity-disclaimer"> An official website of the Office of Management and Budget, the CDO Council and the General Services Administration. </p> </div> </div> </section> <nav class="usa-identifier__section usa-identifier__section--required-links" aria-label="Important links,,,"> <div class="usa-identifier__container"> <ul class="usa-identifier__required-links-list"> <li class="usa-identifier__required-links-item"> <a href="https://www.whitehouse.gov/omb/" class="usa-identifier__required-link usa-link">About OMB</a> </li> <li class="usa-identifier__required-links-item"> <a href="https://www.gsa.gov/website-information/website-policies#accessibility" class="usa-identifier__required-link usa-link" >Accessibility support</a > </li> <li class="usa-identifier__required-links-item"> <a href="https://www.gsa.gov/reference/freedom-of-information-act-foia" class="usa-identifier__required-link usa-link" >FOIA requests</a > </li> <li class="usa-identifier__required-links-item"> <a href="https://www.gsa.gov/reference/civil-rights-programs/notification-and-federal-employee-antidiscrimination-and-retaliation-act-of-2002" class="usa-identifier__required-link usa-link" >No FEAR Act data</a > </li> <li class="usa-identifier__required-links-item"> <a href="https://www.gsaig.gov" class="usa-identifier__required-link usa-link">Office of the Inspector General</a> </li> <li class="usa-identifier__required-links-item"> <a href="https://www.gsa.gov/reference/reports/budget-performance" class="usa-identifier__required-link usa-link" >Performance reports</a > </li> <li class="usa-identifier__required-links-item"> <a href="https://www.gsa.gov/website-information/website-policies#privacy" class="usa-identifier__required-link usa-link" >Privacy policy</a > </li> <li class="usa-identifier__required-links-item"> <a href="https://github.com/GSA/data-strategy/issues" class="usa-identifier__required-link usa-link" >Report a bug</a > </li> <li class="usa-identifier__required-links-item"> <a href="https://www.gsa.gov/tts" class="usa-identifier__required-link usa-link">Website Managed by TTS</a> </li> </ul> </div> </nav> <section class="usa-identifier__section usa-identifier__section--usagov" aria-label="U.S. government information and services,,," > <div class="usa-identifier__container"> <div class="usa-identifier__usagov-description">Looking for U.S. government information and services?</div> <a href="https://www.usa.gov/" class="usa-link">Visit USA.gov</a> </div> </section> </div> </body> </html>