I n t e g r i t y - S e r v i c e - E x c e l l e n c e
United States Air Force
AV SOA Conference
22 Oct 09
Acquisition Domain
Data Governance
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Why Do We Care?
We get dazzled by tools … and there’s always a new one
We create and fund programs to spiral out systems with ever increasing functionality … often impressive
All of that is useful … and can be powerful
But only if it ultimately provides reliable information to decision makers
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Why Do We Care?
We get dazzled by tools … and there’s always a new one
We create and fund programs to spiral out systems with ever increasing functionality … often impressive
All of that is useful … and can be powerful
But only if it ultimately provides reliable information to decision makers
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Why Data Governance?
Allow authoritative, relevant, accurate, and consistent
information to be provided to decision makers at all levels
Establish trust in the information by enabling a clear understanding of what can be expected from the
information
Data update frequency
Data age
Data definition
Role access
How it can be appropriately used
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Our Data View
5 SMART Functional System Functional System Functional System PM PM PM PEO SAE Functional System Program Specific System(s) Program Specific System(s) Program Specific System(s)
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Our Data View
6 SMART Program Specific System(s) Program Specific System(s) Program Specific System(s) Functional System Functional System Functional System PM PM PM PEO SAE Functional System AV SOA Database
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Our Data View
7 SMART Program Specific System(s) Program Specific System(s) Program Specific System(s) Functional System Functional System Functional System PM PM PM PEO SAE AV SOA Database EV Repository
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Our Data View
8 SMART Program Specific System(s) Program Specific System(s) Program Specific System(s) Functional System Functional System Functional System PM PM PM PEO SAE AV SOA Database EV Repository
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Air Force Take on Governance
Information & Data Management Strategy (IDMS)
Issued from SecAF and CSAF
Focus on domain ownership of data
Directed creation of “Data Panels”
Led to the creation of the Transparency IPT
Chaired personally by SecAF
Focus on a standard information structure (SIS)
Effort coordinated by an Enterprise Vocabulary Team (EVT)
Strong push to service oriented architecture (SOA)
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
TIPT Governance Structure
SECAF
Transparency Integrated Product Team
AF/A1 Personnel AF/SG Health Services AF/A2 ISR AF/A3/5 Operational SAF/FM Financial Transparency Enablement Personnel Transparency COI Education and Training COI Health Services Transparency COI ISR COI C2 Space Situational Awareness COI AF Mobility and Transportation COI Flight Scheduling COI Flight Scheduling Global Force Management COI GFM DI
COI Coordination Panel
Process Analysis
Enterprise Information Space
Integration and Test Framework
Clean Audit Enterprise SFIS SAF/AQ Acquisition Program Management COI Sourcing/ Contracting COI Science and Technology COI Readiness COI Depl Readiness Service AF/A4/7 Logistics and Installations LIMS Data Panel
COI COCOM57 Real Property Accountability Enterprise RPIM Active AF COI TIPT/CoI Support Sub-IPT Project Joint COI SAF/XC WF Integration Time Sensitive Targeting COI Technology Asset Mgmt COI ATO UID Air Operations COI Enterprise Vocabulary Team
FMIP Integrated Air & Missile Defense COI
Strike JEFX08 COI Jt Meteorological & Oceanographic COI Force Presentation COI Test and Evaluation COI Systems Engineering COI Product Support COI Requirements Development COI Acquisition Domain Data Panel
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Objective
Accelerate AF efforts in delivering authoritative information to decision makers at all levels
Improve AF Information availability and quality
Realize warfighter cross-service information requirements
Implement the DoD-wide information priorities
Transparency: an attribute that ensures that the process of transforming data into information used for decision making is traceable, auditable, and demonstrably proven … making it authoritative (trustable)
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Standard Information Structure
Object Model
Conceptual model(s) of COI domain (e.g., UML, ER, or OO models)
COI Glossary
Includes mapping of terms to data elements Includes synonym sets or thesaurus
Semantic Model
COI concept hierarchy and logical relations; (e.g., Taxonomies, Ontologies)
Business Rules
Constraints on COI information (e.g., Authorization Rulesets)
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Governance Structure
13 Data Panel Program Office Domain Knowledge System Knowledge Alignment DVTAir Force COI Coordination Panel ADS Analy s is Acquisition Domain Reference Group Acquisition CIO
TIPT – Transparency IPT T2 – Tools & Training Council
ADWG – Acquisition Domain Working Group DRT – Domain Requirements Team
DVT – Domain Vocabulary Team COI – Community of Interest
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Authoritative Data Sources
A recognized or official data production source with a designated mission statement or source/product to publish reliable and accurate data for subsequent use by customers.
An authoritative data source may be the functional combination of multiple, separate data sources.
Source: DoD Directive Number 8320.03, March 23, 2007
Complexity:
Information assets consist of overlapping atomic units make defining a single ADS complex
Trade-offs between timeliness and computational efficiency make defining a single ADS complex
I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Governance Concerns
ADS governance
Where can authoritative information be found?
Can other sources be used?
Service Level Agreement construct
How often can a consumer expect information to be updated?
What will the consumer need to do to use it?
Data cleanliness construct
What level of cleanliness can be expected by a consumer?
Data access construct
What roles have access to what information?