<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratmliso.xsl"?>
<StrategicPlan xmlns="urn:ISO:std:iso:17469:tech:xsd:stratml_core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ISO:std:iso:17469:tech:xsd:stratml_core http://xml.govwebs.net/stratml/references/StrategicPlanISOVersion20140401.xsd"><Name>Data Coalition Comments on the Federal Data Strategy Draft Action Plan (USBC-2019-0001)</Name><Description>While there is much promise in the current strategy, the draft action plan misses important
opportunities to promote effective implementation over the next year of the Foundations for
Evidence-Based Policymaking Act, the OPEN Government Data Act, and the Confidential
Information Protection and Statistical Efficiency Act.2 The absence of intentional actions that
focus on key provisions of the Evidence Act is a major shortcoming of the draft strategy. The
Data Coalition strongly recommends that the administration incorporate additional action
items to reflect priorities for the data community in new legal requirements established with
bipartisan support by Congress and signed by the president in January 2019.</Description><OtherInformation>Our attached comments [documented as goals and objectives in this StratML rendition] include targeted suggestions to ensure the Action Plan aligns with the Evidence Act,
among other recommendations.
The Data Coalition and its members look forward to continuing to support the development
and implementation of this important strategy. </OtherInformation><StrategicPlanCore><Organization><Name>Data Coalition</Name><Acronym>DTC</Acronym><Identifier>_01e6f880-88a1-11e1-816a-08f08bba6d9d</Identifier><Description> The Data Coalition is America’s premier voice on data policy and
advocates for government information to be high quality, accessible, and useful. In most cases,
this means transforming data to be standardized, open, and machine-readable information.
Based in Washington D.C., the Data Coalition members include a broad cross-section of the
data industry, including technology and data analysis companies, public sector consulting firms,
and non-profit organizations.</Description><Stakeholder StakeholderTypeType="Person"><Name>Nick Hart, Ph.D.</Name><Description>CEO</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Christian Hoehner</Name><Description>Should you have additional questions about our
comments, please contact the Data Coalition’s Senior Director for Policy, Christian Hoehner
(christian.hoehner@datacoalition.org).</Description></Stakeholder></Organization><Vision><Description/><Identifier>_89e1caa2-bb21-11e9-99fa-fa1dec758c7b</Identifier></Vision><Mission><Description>To provide comments on the Draft 2019-2020 Federal Data Strategy (FDS) Action Plan. </Description><Identifier>_89e1cd36-bb21-11e9-99fa-fa1dec758c7b</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>Organizational Identifiers</Name><Description>Establish a work group to address organizational identifiers.</Description><Identifier>_89e1ce76-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Companies</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Nonprofits</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Non-Federal Entities</Name><Description/></Stakeholder><OtherInformation>1 - RECOMMENDATIONS FOR NEW COMMUNITY ACTIONS -- 
ESTABLISH A GOVERNMENT-WIDE ORGANIZATIONAL IDENTIFIER WORKING GROUP
The federal government currently uses more than 50 organizational identifiers for companies,
nonprofits, and other non-federal entities.3 Because the same entity, or organization, is
identified differently by multiple federal agencies, entity matching can be excessively time
consuming and resource intensive for developing regulatory analysis, implementing regulations,
conducting investigations, implementing contracts, or collecting information for oversight and
accountability purposes. The U.S. government previously conducted a working group to study
the issue, though little progress has been made to adopt common identifiers over the past
decade, notwithstanding global efforts -- in conjunction with some U.S. federal agencies -- to
develop, adopt, and implement non-proprietary identifiers. For example, the Legal Entity
Identifier (LEI), is a global standard that could be further considered for application across
federal agencies alongside existing non-interoperable identification codes.4
In 2016 OMB convened the Employer Data Matching Workgroup which included fourteen
representative federal agencies. The working group was charged with documenting the issues
in “matching and uniquely identifying establishments and firms within and between data sets
and over time,” identifying potential solutions to these challenges, and making
recommendations to “improve the Federal government’s ability to identify and match unique
firms and establishments (and the relationship between the two) within and across Federal
data sets.”5 The working group also produced an inventory of various agency data resources used for identifying and monitoring U.S. employers.
The FDS should include an Action Item which leverages and extends the initial steps to improve
common entity identifiers. This could include an additional study on the disparate identification
codes currently in use and a feasibility study on a full transition to a common nonproprietary
federal entity identifier such as the LEI.</OtherInformation><Objective><Name/><Description/><Identifier>_89e1cf70-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator/><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Evidence Act</Name><Description>Fully implement the Evidence Act.</Description><Identifier>_89e1d074-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>2 - RECOMMENDATIONS FOR EVIDENCE ACT IMPLEMENTATION
The draft Action Plan should take steps to address core requirements and provisions of the
Evidence Act, including a number of provisions that appear to be omitted altogether from the
draft Action Plan. </OtherInformation><Objective><Name>CDOs</Name><Description>Provide guidance for CDO designations.</Description><Identifier>_89e1d16e-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>CDOs</Name><Description/></Stakeholder><OtherInformation>PROVIDE GUIDANCE FOR AGENCY-BY-AGENCY CDO DESIGNATIONS
The deadline in the Evidence Act to identify new Chief Data Officers is July 13, 2019. To date,
OMB has not yet issued implementation guidance for how agencies should approach
appointments, staffing, or infrastructure related to what will be a new role in more than 100
federal agencies. The Data Coalition strongly recommends that OMB prioritize the issuance of
guidance to implement this important role, along with the corresponding enhancements the
designated leaders will provide for managing privacy risks and improving data quality, access,
and use. In particular, the Coalition recommends that the guidance clearly delineate and
reaffirm the Evidence Act’s intent that, generally speaking, CDOs serve as officials that are
distinct and separate from Chief Information Officers and Chief Financial Officers. Guidance
would also be useful for agencies seeking insights about how to appropriately resource the new
function, including:
• Staffing and training an appropriate workforce;
• Identifying and sharing models and best practices for CDOs to acquire analytic platforms
and tools
• Organizing the CDO to best fit within appropriate organization structures, including
where FITARA funding may be appropriate for supporting implementation
• Further delineation of the eligibility requirements for CDOs, as explicated in the OPEN
Government Data Act. </OtherInformation></Objective><Objective><Name>CDO Council</Name><Description>Establish and empower the CDO Council.</Description><Identifier>_89e1d268-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder StakeholderTypeType="Organization"><Name>CDO Council</Name><Description/></Stakeholder><OtherInformation>ESTABLISH AND EMPOWER THE CDO COUNCIL
In addition to guidance on the CDO positions and roles, we strongly recommend OMB include
an Action Item addressing the establishment and empowerment of the statutory CDO Council. 
In particular, the CDO Council’s roles should be appropriately connected to the proposed OMB
Council and the agency Data Governance Committees. </OtherInformation></Objective><Objective><Name>Evaluation Officers &amp; Statistical Officials</Name><Description>Issue guidance on the establishment of evaluation officers and statistical officials.</Description><Identifier>_89e1d376-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>2.3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Evaluation Officers</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Statistical Officials</Name><Description/></Stakeholder><OtherInformation>ISSUE GUIDANCE ON THE ESTABLISHMENT OF EVALUATION OFFICERS AND
STATISTICAL OFFICIALS
Title 1 of the Evidence Act includes provisions that aim to bolster government’s capacity to use
data and to engage in evidence-based policymaking. The Draft Action Plan should include
actions that recognize the need to designate evaluation officers and statistical officials, as well
as to create respective policies and practices for evaluation as outlined by the Evidence Act. The
administration has notably included other references to the importance of the evaluation
function and key statistical activities in government-wide guidance and planning documents,
but the data strategy must be clearly connected to these critical users of government data.6</OtherInformation></Objective><Objective><Name>Advisory Committee</Name><Description>Establish an advisory committee on data for evidence-building.</Description><Identifier>_89e1d47a-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>2.4</SequenceIndicator><Stakeholder StakeholderTypeType="Organization"><Name>U.S. Commission on Evidence-Based Policymaking</Name><Description/></Stakeholder><OtherInformation>ESTABLISH THE ADVISORY COMMITTEE ON DATA FOR EVIDENCE-BUILDING
When the U.S. Commission on Evidence-Based Policymaking issued its unanimous
recommendations to Congress and the President in 2017, it suggested the establishment of the
National Secure Data Service as a modern shared service for data linkage activities.7 The
Evidence Act includes the creation of an advisory committee to further explore and make
recommendations on how to go about achieving the Evidence Commission’s vision. The
President’s FY 2020 Budget also includes references to the establishment of a data service.
Initial steps can be undertaken, including the creation of the advisory committee, to ensure
effective implementation of such a new entity. The Data Coalition recommends the action plan
includes a specific action item that makes progress on developing the National Secure Data
Service as a targeted strategy for improving access to data while strengthening existing privacy
protections.</OtherInformation></Objective><Objective><Name>Data Protection</Name><Description>Codify OMB Statistical Policy Directive No. 1 to protect data in a manner
that enhances public trust.</Description><Identifier>_89e1d588-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>2.5</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ISSUE A NOTICE OF PROPOSED RULEMAKING ON THE CODIFICATION OF
STATISTICAL POLICY DIRECTIVE NO. 1
Title III of the Evidence Act includes a recommendation from the Commission on Evidence-Based Policymaking to codify OMB Statistical Policy Directive No. 1. The Data Coalition
recommends that OMB immediately initiate the regulatory process to ensure SPD1 is reflected
in administrative law as soon as possible. As new approaches for data management, curation, access, and use emerge, government agencies must take steps to ensure the American public
can trust government to safely and securely steward this information. The codification of SPD1
represents an important set of guidance for federal agencies about protecting data in a manner
that enhances public trust.</OtherInformation></Objective></Goal><Goal><Name>Actions</Name><Description>Strengthen the proposed actions.</Description><Identifier>_89e1d858-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>3 - STRENGTHENING PROPOSED DRAFT ACTIONS</OtherInformation><Objective><Name>Data Council</Name><Description>Create a data council.</Description><Identifier>_89e1d984-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 1 - CREATE AN OMB DATA COUNCIL
The Data Coalition applauds OMB’s recognition of the need to better coordinate data policy
across government. Importantly, Action 1 builds on a suggestion from the Commission on
Evidence-Based Policymaking that OMB may need to reorganize to better manage data policies
moving forward.8 In implementing the OMB Data Council, the Data Coalition recommends
leveraging the new CDO Council, the White House Data Fellows, and coordinate as appropriate
with federal agencies tasked with government-wide data functions.</OtherInformation></Objective><Objective><Name>Training &amp; Credentialing</Name><Description>Develop a data science training and credentialing catalog.</Description><Identifier>_89e1da9c-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 2 - DEVELOP A CURATED DATA SCIENCE TRAINING AND CREDENTIALING
CATALOG
Ensuring a strong workforce for data science and analysis is an important aspect of a successful
long-term Federal Data Strategy. The effort to develop a catalog of training and credentialing
programs should focus on the task and operational function of employees, link to the CDO
Council infrastructure, and be updated routinely (e.g., every six months) to maintain relevance. </OtherInformation></Objective><Objective><Name>Data Ethics</Name><Description>Develop a data ethics framework.</Description><Identifier>_89e1dbbe-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 3 - DEVELOP A DATA ETHICS FRAMEWORK
The Data Coalition applauds the inclusion of the ethics framework as part of the plan. Ensuring
that data are ethically and responsibly used is essential to the success of evidence-based
policymaking and informed decision-making in our society. To that end, the Data Coalition
encourages that the ethics framework reflects decision points and directives that are mapped
to specific examples to improve the salience for practitioners and the American public. This
could be done, for example, along each of the lifecycle stages of data management articulated
in the Federal Data Strategy. The ethics framework should involve a transparent and
participatory development process, and include periodic updates based on public input. </OtherInformation></Objective><Objective><Name>Data Protection</Name><Description>Develop a data protection toolkit.</Description><Identifier>_89e1dcd6-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.4</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 4 - DEVELOP A DATA PROTECTION TOOLKIT
The Data Coalition appreciates the development and application of a data protection toolkit,
including efforts to update Statistical Working Paper 22 with corresponding guidance to federal
agencies. The Evidence Act requires federal agencies to better monitor and assess the risk of re-identification of confidential records; the data protection toolkit will be an essential resource as
agencies are implementing these new requirements. The Data Coalition suggests that the
toolkit be closely developed in concert with the ethics framework (Action 3). </OtherInformation></Objective><Objective><Name>Resources &amp; Tools</Name><Description>Develop a repository of Federal data strategy resources and tools.</Description><Identifier>_89e1ddee-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.5</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 5 - DEVELOP A REPOSITORY OF FEDERAL DATA STRATEGY RESOURCES AND
TOOLS
The Coalition is pleased to see the emphasis placed on the establishment of a repository as
required by the OPEN Government Data Act’s (P.L. 115-435, Title II) Section 3511(c)(2)
requirement for a “Repository”. As the Act requires, the repository should also include, or point
to, established schema standards to facilitate greater harmonization across federal data assets
(as the law states, the Repository should include “an online repository of tools, best practices,
and schema standards to facilitate the adoption of open data practices across the Federal
Government”). Since data standards are essentially agreed upon processes and rules for
describing and recording the format and meaning of data so that it can be shared, exchanged,
and ultimately understood, it would be appropriate to consider standards for inclusion in the
Repository as a means to support the goals of open data, data sharing, and harmonization.9
Additionally, the Repository’s inclusion of data standards and relevant schemas will support
such specific FDS Practices as “5. Prepare to Share”, “20. Leverage Data Standards”, “25.
Coordinate Federal Data Assets”, and “29. Design Data for Use and Re-Use.”10</OtherInformation></Objective><Objective><Name>Research</Name><Description>Pilot and one-stop standard research application.</Description><Identifier>_89e1df24-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.6</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Researchers</Name><Description/></Stakeholder><OtherInformation>ACTION 6 - PILOT A ONE-STOP STANDARD RESEARCH APPLICATION
The proposed researcher application portal reflects an important privacy enhancement and
burden reduction provision in the Evidence Act. The pilot should take efforts to ensure the
benefits of proposed projects are clearly delineated and available for review by the American
public. In addition, the pilot could consider approaches for qualified researchers and users to
more efficiently apply to add qualified research assistants or appropriate support personnel for
projects.</OtherInformation></Objective><Objective><Name>Data Inventory</Name><Description>Pilot an automated data inventory tool.</Description><Identifier>_89e1e050-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.7</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 7- PILOT AN AUTOMATED INVENTORY TOOL FOR DATA.GOV AND ACTION

Ensuring data inventories with appropriate metadata exist is a critical aspect of protecting
privacy and confidentiality of microdata in the long-term. The Data Coalition appreciates the
inclusion of a pilot activity for rapidly advancing the development of the data inventory
requirement in the Evidence Act and OPEN Government Data Act.</OtherInformation></Objective><Objective><Name>Data Catalogs</Name><Description>Pilot standard data catalogs.</Description><Identifier>_89e1e172-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.8</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>8 - PILOT STANDARD DATA CATALOGS FOR DATA.GOV
Ensuring data inventories with appropriate metadata exist is a critical aspect of protecting
privacy and confidentiality of microdata in the long-term. The Data Coalition appreciates the
inclusion of a pilot activity for rapidly advancing the development of the data inventory
requirement in the Evidence Act and OPEN Government Data Act.</OtherInformation></Objective><Objective><Name>AI</Name><Description>Improve data resources for AI research and development.</Description><Identifier>_89e1e2bc-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.9</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 9 - IMPROVE DATA RESOURCES FOR AI RESEARCH AND DEVELOPMENT
The Data Coalition strongly supports Action 9 to improve data resources for the research and
development of artificial intelligence.</OtherInformation></Objective><Objective><Name>Financial Management</Name><Description>Improve financial management data standards.</Description><Identifier>_89e1e3e8-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.10</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 10 - IMPROVE FINANCIAL MANAGEMENT DATA STANDARDS
This Action should also address the continued implementation of the Digital Accountability and
Transparency Act (DATA Act; P.L. 113-101). OMB should work with the U.S. Treasury Bureau of
the Fiscal Service to create a consolidated set of recommendations addressing remaining data
quality issues. Specifically, a plan should be developed to examine award systems maintained
externally to agency financial systems which USAspending.gov relies on for spending
information. Recommendations should be developed to assure these systems more closely
integrate with legally established DATA Act management guidance, reporting processes, and
data standards.
The FDS should also outline how the Administration can further leverage the U.S. Treasury
maintained DATA Act Information Model Schema (DAIMS) to facilitate more automated
integration with other federal performance and budget reporting. For instance, OMB’s June
2018 memorandum on “Appendix A to OMB Circular No. A-123, Management of Reporting and
Data Integrity Risk”11 outlines a number of Financial and Non-Financial federal reporting areas
which could integrate relevant data elements defined in the DAIMS data model to facilitate
automated integration and informative connections across different areas of federal reporting.
Future federal reporting requirements should leverage modern standard-setting best practices
to incorporate schema, taxonomy, and ontology into the data standard models. Federally
maintained data standards should seek to specify the relationships and hierarchies between
data elements (e.g., program activity, budget function, CFDA, Treasury Account, etc.), relevant
technical specifications (e.g., text structure parameters, appropriate metadata such as time
parameters), and data quality validation rules.</OtherInformation></Objective><Objective><Name>Geospatial Data</Name><Description>Improve geospatial data standards.</Description><Identifier>_89e1e51e-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.11</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 11 - IMPROVE GEOSPATIAL DATA STANDARDS
The U.S. Census Bureau has routinely demonstrated the value of applying geospatial data to
improve the quality and efficiency of data collection activities. The Data Coalition supports
inclusion of a targeted action for the geospatial data community to develop critical standards
and support implementation of the Geospatial Data Act.</OtherInformation></Objective><Objective><Name>Governance</Name><Description>Constitute a governance body.</Description><Identifier>_89e1e668-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.12</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 12 - CONSTITUTE A DIVERSE DATA GOVERNANCE BODY
The Coalition is pleased to see the emphasis placed on the agency Data Governance Body. It
would be appropriate for the OMB Data Council to provide recommended models for the
agency CDOs to establish these governance bodies based on the agencies that have already
established such committees. Agency data governance bodies should have an expectation to
interface with the CDO Council to share similar mission related data challenges and best
practices across the government (e.g., grant making and federal assistance, regulatory
enforcement, information collections and statistical analysis, R&amp;D, fund administration, etc.).</OtherInformation></Objective><Objective><Name>Data &amp; Infrastructure</Name><Description>Propose a model for how the CDO can assess data and related infrastructure maturity.</Description><Identifier>_89e1e79e-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.13</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 13 - ASSESS DATA AND RELATED INFRASTRUCTURE MATURITY
This action should propose a model for how the CDO can accomplish this work while leveraging
existing resources maintained by the agency CIO. A data maturity assessment model, such as
the internationally recognized Data Management Capability Assessment Model (DCAM)12,
should be recommended to agencies to assure a consistent approach and manner for
expressing the findings. The CDO Council should be encouraged to establish a Working Group to
consider thematic results which might require coordinated, government-wide projects or
resources. Additionally, the GSA team responsible for the Repository should be integrally
involved in this process.</OtherInformation></Objective><Objective><Name>Skills</Name><Description>Assess staff data skills to ensure the government’s workforce can meet emerging data needs.</Description><Identifier>_89e1e8de-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.14</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 14 - IDENTIFY OPPORTUNITIES TO INCREASE STAFF DATA SKILLS
The assessment of staff data skills is an important attribute of ensuring government’s workforce
can meet emerging data needs. To support agencies in conducting such assessments,
consideration could also be given to including additional questions as a supplement to the
annual Federal Employee Viewpoint Survey.</OtherInformation></Objective><Objective><Name>Key Questions</Name><Description>Connect data needs to learning agendas and evidence-building plans.</Description><Identifier>_89e1ea46-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.15</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>ACTION 15 - IDENTIFY DATA NEEDS TO ANSWER KEY AGENCY QUESTIONS
This action must be clearly connected to the learning agendas and evidence-building plans
required of agencies by the Evidence Act and articulated in OMB Circular A-11. The action plan could also articulate that the August 2020 deadline is intended to precede the final submission
of interim learning agendas, due to OMB in September 2020.13
The Evidence Commission’s recommendation for establishment of a learning agenda indicated
that a key benefit is the identification of knowledge gaps, then determinations of how to align
existing data resources (including potential sharing of data) and new data collection activities to
address key questions. Agency leaders must ensure the development of learning agendas14 and
identification of data needs is not limited to currently collected data or data ‘owned’ by a single
agency or organizational unit.
The development of learning agendas should also involve stakeholder feedback beyond the
government agency. The Data Coalition and its members look forward to supporting
meaningful progress on this action.</OtherInformation></Objective><Objective><Name>Priority Data</Name><Description>Consider the priority data identified by the Evidence Commission as a starting point for engagement with stakeholders.</Description><Identifier>_89e1eb90-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>3.16</SequenceIndicator><Stakeholder StakeholderTypeType="Organization"><Name>Evidence Commission</Name><Description/></Stakeholder><OtherInformation>ACTION 16 - IDENTIFY PRIORITY DATASETS FOR AGENCY OPEN DATA PLANS
Efforts to implement this action should consider the priority data identified by the Evidence
Commission as a starting point for engagement with stakeholders.15 The Data Coalition and its
members recognize that it would be infeasible for all eligible information to be made accessible
as open data over the next year, and we strongly encourage agencies to prioritize
implementation of this provision of the OPEN Government Data Act, in consultation with key
stakeholders and data users.
In addition, the Data Coalition strongly recommends that the administration prioritize enabling
improved access to income and earnings data, with supporting privacy and confidentiality
protections.16 Devising strategies to improve open data access for some components of this
information and ensuring these data are captured in enhanced data inventories will be a critical
component to successfully using this information to determine whether a vast number of
federal programs are achieving their intended outcomes.</OtherInformation></Objective></Goal><Goal><Name>Resources</Name><Description>Reallocate required resources.</Description><Identifier>_89e1ecda-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>5 - COMMENTS ON IMPLEMENTATION RESOURCES
Without question the actions in the Draft Action Plan will require resource reallocations across
government to be fully successful.</OtherInformation><Objective><Name>Funding</Name><Description>Request additional FY 2020 funding to support the establishment, organization, and empowerment of new leadership positions.</Description><Identifier>_89e1ee56-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Chief Data Officers</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Chief Evaluation Officers</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Statistical Officials</Name><Description/></Stakeholder><OtherInformation>The Data Coalition recommends OMB issue an additional FY
2020 budget request to Congress to support the establishment, organization, and 
empowerment of new leadership positions, including the Chief Data Officers, Chief Evaluation
Officers, and Statistical Officials, in addition to developing and apportioning any necessary
reprogramming or reallocations in the current fiscal year. Such a request should be based on
OMB’s assessment of the resource needs in the short-term.</OtherInformation></Objective><Objective><Name>Evidence Act</Name><Description>Encourage agencies to assess resources needs for implementing the Evidence Act.</Description><Identifier>_89e1f0a4-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>4.2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>As part of the Action Plan and upcoming budget guidance for the FY 2021 budget, OMB should
also encourage agencies to assess resources needs for implementing the Evidence Act. The
Data Coalition strongly recommends agencies share resource requests with OMB for the
FY2021 Budget when submitting annual requests to OMB in September 2020; we further
strongly recommend OMB develop a pool of resources or a new targeted interagency budget
account that can be used for supporting targeted needs in the FY2021 budget process.</OtherInformation></Objective><Objective><Name>Circular A-25</Name><Description>Explore potential updates to OMB Circular A-25 to ensure fee mechanisms align with the current guidance.</Description><Identifier>_89e1f202-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>4.3</SequenceIndicator><Stakeholder StakeholderTypeType="Organization"><Name>U.S. Commission on Evidence-Based Policymaking</Name><Description/></Stakeholder><OtherInformation>OMB should also direct the new OMB Data Council to explore potential updates to OMB
Circular A-25 to ensure fee mechanisms align with the current guidance, consider development
of Evidence Incentive Funds as recommended by the U.S. Commission on Evidence-Based
Policymaking,17 and consider how government can apply flexibilities in procurement processes
to achieve additional efficiencies.18</OtherInformation></Objective></Goal><Goal><Name>Other Issues</Name><Description/><Identifier>_89e1f388-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>5</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>6 - OTHER GENERAL COMMENTS

</OtherInformation><Objective><Name>Co-Implementation</Name><Description>Ensure a collaborative and participatory process for co-implementers of key
government data activities.</Description><Identifier>_89e1f4e6-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>5.1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>State Governments</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Local Governments</Name><Description/></Stakeholder><OtherInformation>STATE AND LOCAL GOVERNMENT PARTICIPATION
The action plan appears to skirt the issue of the role state and local governments play in
supporting federally-funded but locally-implemented programs. Additional attention should be
given to ensuring a collaborative and participatory process for co-implementers of key
government data activities.</OtherInformation></Objective><Objective><Name>Responsibilities</Name><Description>Identify leaders who can be held responsible for achieving the goals.</Description><Identifier>_89e1f644-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>5.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>IDENTIFY “RESPONSIBLE INDIVIDUALS”
The draft action plan appropriately identifies agencies the actions will be assigned to. However,
as we have learned through decades of implementing management activities in government,
such as the Government Performance Results Act Modernization Act of 2010, a more effective
strategy is to identify individual senior leaders who can be held responsible both inside
government and publicly for achieving the intended goal.19</OtherInformation></Objective><Objective><Name>Performance Metrics</Name><Description>Include well-articulated and well-defined measures.</Description><Identifier>_89e1f7d4-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>5.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>PERFORMANCE METRICS
We applaud the intent to include metrics through which the American public can hold the
Executive Branch accountable for achieving the individual actions in the draft plan. However,
the draft action plan includes numerous performance metrics for individual actions that fail to
satisfy basic measurement criteria as articulated in OMB Circular A-11.20 In several instances,
the measures are largely misaligned with the stated action or offer mere binary determinations
for whether an action was achieved. For example, in Action 1 for the creation of an OMB Data
Council, the establishment of the Council itself is less important than whether the group
achieves activities of value. With an increased focus in government on achieving meaningful
outcomes, the measurements should include well-articulated and well-defined measures. </OtherInformation></Objective><Objective><Name>Deadlines</Name><Description>Specify deadlines for completion or progress on individual actions.</Description><Identifier>_89e1f93c-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>5.4</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>TIMELINES
To improve accountability for the final action plan, we recommend in lieu of relative
timeframes, that the action plan include specific deadlines for completion or progress on
individual actions.</OtherInformation></Objective><Objective><Name>Legal Alignment</Name><Description>Delineate how the actions align with new legal obligations in the Evidence Act and other statutory authorities.</Description><Identifier>_89e1faa4-bb21-11e9-99fa-fa1dec758c7b</Identifier><SequenceIndicator>5.6</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation>LEGAL OBLIGATIONS
As noted throughout these comments, more attention can be given to expressly delineating
how the actions align with new legal obligations in the Evidence Act and other statutory
authorities. This could minimally be achieved by listing the statutory authority at the end of
each action in addition to the “supported practice” statement.</OtherInformation></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2019-07-08</StartDate><PublicationDate>2019-08-09</PublicationDate><Source>https://www.datacoalition.org/wp-content/uploads/2019/07/DataCoalition.CommentOnFederalDataStrategy.Phase3_.07-08-19-FINAL.pdf</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>