<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><StrategicPlan><Name>What's really needed for data-driven government</Name><Description>While poor data quality, the challenges of pulling and integrating data from legacy IT systems and the difficulty of persuading stakeholders to embrace open data can all be stumbling blocks to a data-driven government, there are proven ways local governments can improve data governance.</Description><OtherInformation>The Local Government Association and Nesta, both U.K.-based, studied the ways local governments were using data, describing challenges and projecting success factors. The entities worked together during 2016 to review and analyze  data practices of local councils to see how local authorities could better use their data.In their case studies, they found several common issues facing data projects in local governments and described ways to combat these issues. Some of these common issues [are documented as goals in this StratML rendition]</OtherInformation><StrategicPlanCore><Organization><Name>Government Computer News</Name><Acronym>GCN</Acronym><Identifier>_adf688ca-c951-11e6-b00c-459cb8ca98f4</Identifier><Description/><Stakeholder StakeholderTypeType="Person"><Name>Kathleen Hickey</Name><Description>Reporter</Description></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>Local Government Association</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>Nesta</Name><Description/></Stakeholder></Organization><Vision><Description/><Identifier>_adf689f6-c951-11e6-b00c-459cb8ca98f4</Identifier></Vision><Mission><Description>To help local governments improve data governance.</Description><Identifier>_adf68aa0-c951-11e6-b00c-459cb8ca98f4</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>Data Standard, Quality &amp; Integration</Name><Description>Implement data standards and improve data quality for integration.</Description><Identifier>_adf68bc2-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Lack of data standards (or poor data quality) hindering data integration -- In every case study, some or all of the data was unusable. In some instances this was because of data entry errors, mainly because the staff members inputting the data were not the primary data users and did not understand the importance of accurate data. In other cases, data was collected in ways that made it hard to integrate with other information. Data was not routinely checked for quality."The case studies confirmed that poor data quality is likely to be a feature of most, if not all, local government data projects," the researchers said.Furthermore, data in legacy systems of one agency did not always follow the same data standards as at another agency, making integration difficult. In most cases, researchers said, the problem was due to "how values were represented, data categories and fields, or how the data is organized."  In some cases it was because data standards had not been adopted systematically.Solution: Researchers recommended finding where problems with data quality originate and putting the onus on the data owners to improve the data quality. Dashboards also can help expose where poor data quality is linked to data input methods.  As data quality and access increases, the number of people needed for data extraction and reporting is reduced.</OtherInformation><Objective><Name>Problem Identification</Name><Description>Find where problems with data quality originate.</Description><Identifier>_adf68c58-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Responsibilities</Name><Description>Put the onus on data owners to improve the data quality.</Description><Identifier>_adf68cee-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Data Owners</Name><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Dashboards</Name><Description>Use dashboards to expose where poor data quality is linked to data input methods.</Description><Identifier>_adf68d8e-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>1.3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Data Extraction &amp; Reporting</Name><Description>Increase data quality and access in order to reduce the number of people needed for data extraction and reporting.</Description><Identifier>_adf68e42-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>1.4</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Information Governance &amp; Data Sharing</Name><Description>Improve information governance and data sharing.</Description><Identifier>_adf68ed8-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Poor information governance and data sharing -- Legal and cultural hurdles regarding information governance are unavoidable, researchers said. These issues should not be seen as an insurmountable barrier, though. In every project studied, team members found ways to legally share information in accordance with current legislation.Solution: Researchers recommended embedding decisions about sharing data into new systems. Additional best practices include developing information governance protocols for responsible data sharing based on specific-use cases and creating a team manager to drive data integration/use projects. These data-sharing decisions should be based on a balanced risk assessment that “weighs privacy concerns against the risk to the organization or individual of not sharing,” they said. Data should not be collected where there is no apparent, immediate use for it. Instead, all data projects should start with a problem that can be solved by data, then determine which data and analysis might help solve it. The system should record who is using the data to better track if the data is being used inappropriately. There should also be a data inventory that is published as metadata.</OtherInformation><Objective><Name>New Systems</Name><Description>Embed decisions about sharing data into new systems.</Description><Identifier>_adf68f82-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Information Governance Protocols</Name><Description>Develop information governance protocols for responsible data sharing based on specific-use cases.</Description><Identifier>_adf69022-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Data Integration/Use Managers</Name><Description>Create a team manager to drive data integration/use projects.</Description><Identifier>_adf690cc-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Data Integration/Use Managers</Name><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Risk Assessment</Name><Description>Base data-sharing decisions on a balanced risk assessment that weighs privacy concerns against the risk to the organization or individual of not sharing.</Description><Identifier>_adf69176-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.4</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Collection</Name><Description>Refrain from collecting data where there is no apparent, immediate use for it.</Description><Identifier>_adf69220-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.5</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Projects</Name><Description>Start data projects with a problem that can be solved by data.</Description><Identifier>_adf692ca-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.6</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Solutions</Name><Description>Determine which data and analysis might help solve problems.</Description><Identifier>_adf693b0-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.6.1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Usage</Name><Description>Record who is using the data to better track if the data is being used inappropriately.</Description><Identifier>_adf69586-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.6.2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Data Inventory</Name><Description>Provide a data inventory published as metadata.</Description><Identifier>_adf69644-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>2.6.3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Legacy IT Systems</Name><Description>Improve interaction with legacy IT systems.</Description><Identifier>_adf69702-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Difficulty working with legacy IT systems -- Pulling data from legacy IT systems is difficult, particularly when there is poor quality architecture and systems. Data from legacy systems may be in the same format as that in other systems, creating additional integration issues. Solution: Researchers recommended software to "broker between multiple legacy systems" that can integrate data from several sources into a single data repository that can reduce duplicative efforts, facilitate processes and increase data accuracy. Organizations should also devote resources to work with legacy systems and create a data dashboard to more easily understand issues, improve prioritization, decrease decision-making bottlenecks and expose data quality issues.</OtherInformation><Objective><Name>Data Brokerage Software</Name><Description>Use software to broker data among legacy systems to integrate data into a single data repository to reduce duplicative efforts, facilitate processes and increase data accuracy.</Description><Identifier>_adf697b6-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Data Dashboard</Name><Description>Work with legacy systems and create a data dashboard to more easily understand issues, improve prioritization, decrease decision-making bottlenecks and expose data quality issues.</Description><Identifier>_adf6986a-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Resistance</Name><Description>Break down resistance to open data.</Description><Identifier>_adf69928-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>Resistance to open data -- Oftentimes teams were nervous about potential negative reactions from revealing the poor quality of their data. Additionally, once data was integrated and open, it was sometimes difficult to get some employees to use the data -- usually for cultural reasons.Solution: Researchers recommended actively engaging potential data users, creating partnerships with interested communities to better solve challenges faced by the local public sector. Publishing full, raw datasets, creating an open-data portal with multiple datasets with a user-friendly interface are also recommended. The data should be machine readable in a standard open format and use an application programming interface wherever possible. Data should be routinely updated, preferably automatically. It should also be analyzed to determine if it is consistent across the enterprise and achieving its purpose of solving the issue for which it was intended. Historic data that is no longer used should be retired.</OtherInformation><Objective><Name>Engagement &amp; Partnerships</Name><Description>Engage potential data users, creating partnerships with interested communities to better solve challenges faced by the local public sector.</Description><Identifier>_adf699dc-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Publication</Name><Description>Publish full, raw datasets, creating an open-data portal with multiple datasets with a user-friendly interface are also recommended.</Description><Identifier>_adf69a90-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Machine-Readability</Name><Description>Publish data in an open standard, machine-readable format.</Description><Identifier>_adf69b6c-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4.2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>APIs</Name><Description>Provide an application programming interface.</Description><Identifier>_adf69c34-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4.2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Updating</Name><Description>Routinely update data, preferably automatically.</Description><Identifier>_adf69cf2-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4.2.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Analysis &amp; Intentions</Name><Description>Analyze data to determine if it is consistent across the enterprise and achieving its purpose of solving the issue for which it was intended.</Description><Identifier>_adf69dba-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4.2.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Archival</Name><Description>Retire historic data that is no longer used.</Description><Identifier>_adf69e82-c951-11e6-b00c-459cb8ca98f4</Identifier><SequenceIndicator>4.2.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2016-12-22</StartDate><PublicationDate>2016-12-23</PublicationDate><Source>https://gcn.com/articles/2016/12/22/data-governance-challenges-solutions.aspx?s=gcntech_231216</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>
