Data Strategy - Goals and Benefits
-
Upload
john-larsen -
Category
Documents
-
view
93 -
download
0
Transcript of Data Strategy - Goals and Benefits
Federal AviationAdministrationABA EA
Data is a critical organizational asset• Most organizations understand they must better manage data
to achieve their missions• However, common data problems continue to exist for many
organizations due to poor data management:– Redundant data– Data not easily accessible– Poor data quality– Lack of knowledge of what data is available– Data silos– Inconsistent reports– Data standards non existent, not understood, or not followed– Private databases used by stealth applications– No responsibility for data– No central meta data repository
• Poor data quality increases the cost of doing business• A data strategy is lacking for these organizations
Federal AviationAdministrationABA EA
A data strategy is needed to manage data as a strategic asset
Goals drive; governance controls; structure defines; and services enable data strategy.
Business &Data Goals drive
Information Sharing/Exchange
(Services)
Information Sharing/Exchange
(Services)
Governance
Data Strategy
Data Architecture(Structure)
The Rule: All 3 pillars are requiredfor an effectivedata strategy.
“Managing Data as a National Asset” – Federal Data Architecture Subcommittee
Federal AviationAdministrationABA EA
Goals of a Data Strategy
• Make data visible: Users and applications can discover the existence of data assets through catalogs, registries, and other search services
• Make data accessible: Data assets are made available to any user or application except when limited by policy, regulation, or security
• Enable data to be understandable: Users and applications can comprehend the data, both structurally and semantically, and readily determine how the data may be used for their specific needs
• Enable data to be trusted: Users and applications can determine and assess the authority of the source because the pedigree, security level, and access control level of each data asset is known and available
• Support data interoperability: Many-to-many exchanges of data occur between systems, through interfaces that are sometimes predefined or sometimes unanticipated
Federal AviationAdministrationABA EA
Required practices for a successful Data Strategy
• Data governance to establish enterprise-wide decisions regarding an organization’s information holdings.
• Data architecture is an element of an enterprise architecture that describes how data is processed, stored, and utilized by an organization and its applications
• Information Sharing Architecture to describe technology considerations for government agencies to participate in global information sharing communities
Federal AviationAdministrationABA EA
Elements of a Data Strategy Framework
Governance
Data Transfer Standards
PedigreeAuthoritative Sources
Security/Protection Data
Discovery DataInventory
Definitions/SemanticsStructure
Syntax
Data Architecture (Structure)
Information Sharing/Exchange
(Services)OversightPolicy & Procedures
Processes and PracticesEducation/Training
Issue ResolutionMetrics/Incentives
Access ServicesBrokering
Shared SpacesData Catalogs
Data Registries
Communities of InterestSearch
Mediation
“Managing Data as a National Asset” – Federal Data Architecture Subcommittee
Data Strategy
Federal AviationAdministrationABA EA
Mapping data goals to elements of the Data Strategy framework
Visible
Understandable
Trusted
Interoperable
Responsive
Institutionalized
Data Goals:
Shared SpacesAccess Services
Data Catalogs
Communities of InterestSearch
Data Registries
Inventory
Metrics/Incentives
Policy & Procedures
Processes and PracticesEducation/Training
Discovery Data
StructureDefinitions/Semantics
PedigreeSyntax
Education/Training
Oversight
Authoritative SourcesSecurity/Protection DataData Transfer Standards
BrokeringMediation
Go
verna
nce
Data A
rchitectu
reIn
form
ation
Sh
aring
Accessible
“Managing Data as a National Asset” – Federal Data Architecture Subcommittee
Federal AviationAdministrationABA EA
FEA DRM provides guidance in developing the components of a data strategy
• Classifies data and information with respect to how it supports the business of the organization
• Provide a consistent categorization and description of data to facilitate data sharing and integration across LOBs and agencies
Data Sharing
Query Points and Exchange Packages
Query Points and Exchange Packages
Data Description
DataData
Data Context
TaxonomiesTaxonomies
How do I exchange the data?
What does the data mean?
How do I find the data and access
it?
Based on FEA DRM Version 2.0
FEA Data Reference Model Framework
Federal AviationAdministrationABA EA
FEA DRM Value Proposition• Provide a structure that drives consistency in standards
of data exchange.– Allow organizations/agencies to share data in common formats
with common definitions• Address the need for semantic understanding of
agency/government information.– Facilitate common understanding of data context by including
descriptive data that conveys the overall intent and use of data.• Provide an index of government information that can
facilitate the exchange of electronic information. – Provide classifications of government data that allows general
users (citizens) to locate information with ease.• Define requirements for establishing standard information
exchange formats that can be shared across government. – Enable the collaborative development of information exchange,
defining policies for development, storage, and use throughout agency/government.
Federal AviationAdministrationABA EA
Mapping Data Strategy to the DRMData Contextenables…
Data Contextenables…
Data Descriptioncaptures…
Data Descriptioncaptures…
Data Sharingguides…
Data Sharingguides…
Governance
Data Transfer Standards
PedigreeAuthoritative Sources
Security/Protection Data
Discovery DataInventory
Definitions/SemanticsStructure
Syntax
Data Architecture (Structure)
Information Sharing/Exchange
(Services)OversightPolicy & Procedures
Processes and PracticesEducation/Training
Issue ResolutionMetrics/Incentives
Access ServicesBrokering
Shared SpacesData Catalogs
Data Registries
Communities of InterestSearch
Mediation
“Managing Data as a National Asset” – Federal Data Architecture Subcommittee
Data Strategy
Federal AviationAdministrationABA EA
A requirement for information needed to advance
ABA/FAA capabilities is documented
FEA DRM Use Case Example
What business function does this process/activity fall under ?
Are there data components that I can use or combine to
satisfy my data requirements ?
If leveraging data, can I accesswhat already exist or do I need to duplicate or bring into my own
environment to modify and use it ?
What Access Channels can be Used to access the Data
Component (e.g. web services,Portal, Data Warehouse) ?
What Service Components are being used to manipulate the
data ?
Data Sharing
Query Points and Exchange Packages
Query Points and Exchange Packages
Data Description
DataData
Data Context
TaxonomiesTaxonomies
How do I exchange the data?
What does the data mean?
How do I find the data and access it?
Data Sharing
Query Points and Exchange Packages
Query Points and Exchange Packages
Data Description
DataData
Data Context
TaxonomiesTaxonomies
How do I exchange the data?
What does the data mean?
How do I find the data and access it?
Do the business objects exist ?
Yes
No
Data Sharing
Query Points and Exchange Packages
Query Points and Exchange Packages
Data Description
DataData
Data Context
TaxonomiesTaxonomies
How do I exchange the data?
What does the data mean?
How do I find the data and access it?
Data Sharing
Query Points and Exchange Packages
Query Points and Exchange Packages
Data Description
DataData
Data Context
TaxonomiesTaxonomies
How do I exchange the data?
What does the data mean?
How do I find the data and access it?
Technical Reference Model
SLA’s
Service Reference Model
Data Reference Model
Business Reference Model,Performance Reference Model
Create Data, add to registry Exhibit 300’s. Buy, Build, Borrow
Federal AviationAdministrationABA EA
ABA Data Strategy Key Findings• FAA and ABA lacks an overarching data strategy• Piecemeal approaches to data management exist only at
the project level, resulting in issues such as:– No data standards, procedures, policies– No enterprise wide conceptual/logical data model– No coordinated approach for data sharing
• Redundant data sources through data replication• Data sharing between applications and LOBs is difficult
– Inconsistent reports due to multiple private data sources• Users do not know which data to trust
• Data management issues are being addressed with technology rather than with a comprehensive data strategy (i.e. better reporting solution is being investigated)
• ABA must develop a data strategy that focuses on data as an enterprise asset
Federal AviationAdministrationABA EA
The ABA EA effort will fill in some of the data strategy gaps• ABA Conceptual Data
Model– Provide a common taxonomy
for describing data assets across the Financials LOB
• System to Data Mapping– Know what data is created and
read by each system
• Business Process to Data Mapping
– Know what data is required to support a business process
• System Data Exchange Matrix
– Highlight the characteristic of the data exchanges between systems