Download
Skip this Video
1 / 30
The Vocabulary Driven Value Chain - PowerPoint PPT Presentation
- 188 Views
- Uploaded on
The Vocabulary Driven Value Chain. DoD CoI Forum July 31, 2007. Agenda. Introduction: The Vocabulary of this briefing Why Are We sharing? What We Need To Succeed Our Current State How we are sharing now Current Challenges Our Future State Target Capability
Download Presentation 
An Image/Link below is provided (as is) to download presentation
PowerPoint Slideshow about 'The Vocabulary Driven Value Chain' - tannar
An Image/Link below is provided (as is) to download presentation
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.
While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Agenda
- Introduction:
- The Vocabulary of this briefing
- Why Are We sharing?
- What We Need To Succeed
- Our Current State
- How we are sharing now
- Current Challenges
- Our Future State
- Target Capability
- The Vocabulary-Driven Triple Threat
- Where do CoIs fit in?
- Getting There:
- What Is the Vocabulary Driven Value Chain?
- What is the CoIs’ role?
- What is the EVT’s role?
- Six Major Milestones
- Keys To Success
The Vocabulary of This Briefing
- Semantic: The meaning of some “symbol”. Semantics relate symbols (e.g. terms) to the concepts that they represent
- Example: What does the term tank mean?
- Context: Terms surrounding a term or passage that clarify its meaning
- Example: gas tank vs. armored tank
- Ontology: An information map that specifies the contextual semantics of information
- Service Oriented Architecture (SOA):technology that enables information exchange without reengineering legacy systems
Why Are We Sharing?
- Air Force Information Strategy, SECAF & CSAF, August 2002
- https://afkm.wpafb.af.mil/ASPs/DocMan/DOCDisplay.asp?Filter=OO-AQ-ID-EW&DocID=29679
- DoD Net-Centric Data Strategy Memorandum, ASD/NII, May 2003
- https://afkm.wpafb.af.mil/ASPs/DocMan/DOCDisplay.asp?Filter=OO-EA-AF-SP&DocID=285404
- Air Force Information and Data Management Strategy Policy, SECAF & CSAF, 3 March 2004
- https://afkm.wpafb.af.mil/ASPs/DocMan/DOCDisplay.asp?Filter=OO-SC-AF-04&DocID=115325
- DoD Directive 8320.2, Data Sharing in a Net-Centric Environment, 2 December 2004
- https://afkm.wpafb.af.mil/ASPs/DocMan/DOCDisplay.asp?Filter=OO-SC-AN-11&DocID=229248
It is “NOT” just about data sharing, this is only the means to an end…
It “IS” about providing FIRST TO ACTION CAPABILITY
- Transforming enterprise data into ACTIONABLE INFORMATION
- Being the first to action depends on being FIRST TO KNOW
What We Need to Succeed
“What we don’t know can hurt us, but what we think we know, but don’t can
be fatal to an organization”
-Data quality expert, Larry English
What will it take to achieve first to “know” capability?
- “Share” what we know: Information that is…
- relevant
- accessible
- easy to find
- available on demand
- “Understand” what we share: Information that is…
- delivered in a usable form
- delivered in context
- expressed in a known “vocabulary”
- organized for mission support
- “Trust” what we understand: Information that is…
- current
- complete
- authoritative
- reliable
Agenda
- Introduction:
- The Vocabulary of this briefing
- Why Are We sharing?
- What We Need To Succeed
- Our Current State
- How we are sharing now
- Current Challenges
- Our Future State
- Target Capability
- The Vocabulary-Driven Triple Threat
- Where do CoIs fit in?
- Getting There:
- What Is the Vocabulary Driven Value Chain?
- What is the CoIs’ role?
- What is the EVT’s role?
- Six Major Milestones
- Keys To Success
How are we sharing now?
- Point to point sharing
- Not scalable, unnecessary rework, not authoritative
- Centralize everything
- costly, time consuming, brittle, does not accommodate change
- Standard data exchange models
- Limited sharing value, imposes a common structure, inflexible, does not accommodate change
Current Challenges
- “Share” what we know
- Relevant: fragmented, redundant, buried in irrelevant information
- Accessible: scattered among disconnected systems with different access rules
- Findable: must know in advance which pieces of information are in which systems
- Available: information that we are authorized to use is trapped in systems that we don’t know about or can not access.
- “Understand” what we share
- Usable: must evaluate, filter, and restructure information before we can use it.
- Delivered in context: Must guess about the semantics because there is no way to preserve intended context.
- Known “vocabulary”: Must learn the vocabulary of every system that we use and how to translate between vocabularies
- Organized for mission support: Reconfiguring information for a different context requires building new or modifying existing systems.
- “Trust” what we understand
- Current: don’t know if there is more current information available elsewhere
- Complete: don’t know if there are pieces of information missing
- Authoritative: don’t know the authoritative source of the information, e.g. who created, modified or reused it.
Agenda
- Introduction:
- The Vocabulary of this briefing
- Why Are We sharing?
- What We Need To Succeed
- Our Current State
- How we are sharing now
- Current Challenges
- Our Future State
- Target Capability
- The Vocabulary-Driven Triple Threat
- Ontologies
- Governance
- SOA
- Getting There:
- What Is the Vocabulary Driven Value Chain?
- What is the CoIs’ role?
- What is the EVT’s role?
- Six Major Milestones
- Keys To Success
Target Capability
- “Share” what we know
- Relevant: direct users to a single source of authoritative information
- Accessible: authorized users, must have a central point of access for authoritative information
- Findable: locating the information that we need with no system specific knowledge
- Available: information must be available on-demand, enterprise wide to authorized applications and users regardless of where the “pieces” are stored
- “Understand” what we share
- Usable: deliver in a form that enables users to concentrate on making use of, rather than making sense of information
- Delivered in context: the intended context information must be preserved for the entire information life cycle.
- Known “vocabulary”: Must be able to retrieve information using known vocabulary, regardless of the vocabulary of the source systems.
- Organized for mission support: semantics must be abstracted from source systems so that information can be repurposed without requiring manual reconfiguration or source system modification.
- “Trust” what we understand
- Current: ensure currency by directing the user to a single authoritative source.
- Complete: What we need to know can be quickly packaged from modular pieces of information.
- Authoritative: Authority of information is predefined by the CoI and its history is traceable.
TheVocabulary Driven Triple Threat
Making information actionable, is more about business processes and governance than technology
- Vocabularies
- organized to support AF business processes
- provide the semantics for building ontologies
- Governance and Support
- Transparency Integrated Product Team (TIPT): ensures consistent implementation of AF Net-Centric Compliance
- Sub-IPTS: TIPT subteams organized by functional area
- CoI Coordination Panel: Manages CoI activities
- EVT provides technical support to CoI Coordination Panel and its CoIs
- Service Oriented Enterprise Migration
- Loose coupling
- Lower Cost
- Less Rework
- Rapid Development cycles
- Optimizes reuse
attended
is associated
Organization
Event
occurs at
is owned by
Location
OntologiesBecause it provides a “consistent path” to information and preserves its context…
Sub-IPT
TIPT/CoI Support
COI Coordination Panel
Active AF COI
Joint COI
Project
Transparency
Integrated Product Team
Process
Transparency
Enablement
AF/A4/7
Logistics and
Installations
SAF/AQ
Acquisition
Enterprise Information Space
SAF/XC
WF Integration
Integration and Test Framework
LIMS Data Panel
COI
Clean Audit
Air Operations
COI
COCOM57
Enterprise
SFIS
ATO UID
Global Force
Management COI
Deployment COI
AF/A1
Personnel
AF/SG
Health Services
AF/A2
ISR
AF/A3/5
Operational
SAF/FM
Financial
Time Sensitive
Targeting COI
GFM DI
Depl Readiness
Service
Program
Management
& Oversight COI
Real Property
Accountability
Enterprise RPIM
Technology Asset
Mgmt COI
Personnel
Transparency COI
ISR COI
Sourcing COI
Integrated Air &
Missile Defense COI
C2 Space Situational
Awareness COI
Education and
Training COI
Science and
Technology COI
Strike
JEFX08 COI
AF Mobility and
Transportation COI
Health Services
Transparency COI
Jt Meteorological &
Oceanographic COI
Flight Scheduling
COI
Flight Scheduling
Force Presentation
COI
TIPT Governance StructureSOA
- Rapid delivery of capability due to re-use of existing
- “Services”
- “Standard Interfaces”
- “ CoI Vocabularies”
- Cost to deploy and sustain capability slashed
- Short development cycles and re-use
- Standard interfaces mitigates need to continually rewrite interfaces to associated systems (80% of software sustainment)
- Delivers information now!
- Desktop access to all exposed data in the format required
- Negates the requirement to build large client server systems or huge data storage warehouses
Agenda
- Introduction:
- The Vocabulary of this briefing
- Why Are We sharing?
- What We Need To Succeed
- Our Current State
- How we are sharing now
- Current Challenges
- Our Future State
- Target Capability
- The Vocabulary-Driven Triple Threat
- Ontologies
- Governance
- SOA
- Getting There:
- What Is the Vocabulary Driven Value Chain?
- What is the CoIs’ role?
- What is the EVT’s role?
- Six Major Milestones
- Keys To Success
CoI
Analyze
Domain
Develop
Vocabulary
Designate
Information
Assets
Capture
Rules
Develop
Ontology
Develop
Services
What is the Vocabulary Driven Value Chain?A CoI-centric methodology for implementing a semantically aware service oriented enterprise
What Is the CoI’s Role?
Primary role is to manage the “value chain” for your mission area
- Serve as subject matter experts throughout the process
- Develop a vocabulary that represents your subject area (AKA Standard information structure (SIS))
- Identify single source for authoritative pieces of information (AKA information assets) and their source systems.
- Ensure that the SOA implementation supports business processes and semantics
- Collaborate with other CoIs to promote cross CoI vocabulary sharing and reuse
What is the EVT’s Role?
AF Enterprise Vocabulary Team
- Mission: To provide guidance and support for AF CoI goals and the vocabulary development process
- Provide expertise on managing the “value chain”
- Training
- Vocabulary Development
- Time and task management
- SAF/XC – CoI Liaison
Keys to Success
- Data Discipline
- TIPT for governance
- COIs for execution
- Process Discipline
- Policy Directives, AFIs, TTPs, etc.
- AFOS21: continuous process improvement and new technology exploitation
- IT Discipline and Mission Assurance
- Centralized management of federated environment
- Applied at all levels – from the communications pipes through the delivery of information
Questions?
Contact Information:
Mary Parmelee
AF EVT Team Lead
MITRE supporting Warfighting Integration and CIO (SAF/XC)
1101 Wilson Boulevard, Suite 1020
Arlington, Virginia 22209
mary.parmelee.ctr@pentagon.af.mil
Mobile: 571-334-5935
Learn More:
- AF Information & Data Management Strategy - Implementation CoP: https://wwwd.my.af.mil/afknprod/ASPs/CoP/OpenCoP.asp?Filter=OO-SC-AF-DM
MDE
MDE
MDE
MDE
Structural &
Semantic
Metadata
Structural &
Semantic
Metadata
Structural &
Semantic
Metadata
Structural &
Semantic
Metadata
Structural &
Semantic
Metadata
Service
Metadata
Service
Metadata
Service
Metadata
Service
Metadata
Service
Metadata
Discovery
Metadata
Discovery
Metadata
Discovery
Metadata
Discovery
Metadata
Discovery
Metadata
Enterprise Enclave ModelJoint Perspective
What is a
JFACC View?
Coalition, e.g.
DCGS
D
M
Z
TRUST
RELATIONSHIP
ADCON
Enclave
Wargaming
Enclave
JFACC
Intranet
TRUST
RELATIONSHIP
Air Force for
Reach back
TRUST
RELATIONSHIP
OPCON/TACON
Enclave
TRUST
RELATIONSHIP
TRUST
RELATIONSHIP
JAOP AOD
Enclave
DMZ
TRUST
RELATIONSHIP
OPG
Enclave
TRUST
RELATIONSHIP
D
M
Z
D
M
Z
Internet
OSD for enterprise
Services, e.g. DTS
Family
Retirees
Industry
Pilot Core
Data Service
DIMHRS
Service Authentication
Service Invocation
Pilot
Data
Request for
Qualified Pilots
Qualified Pilot
Dashboard
Qualified Pilot Data
Pilot Object Data
Portal
Qualified Pilot
Aggregation
Service
Flight Object Data
Service Authentication
Service Invocation
Flight Training
Core Data Service
ARMS
User Authentication
User Query
Flight
Data
Service Authentication
Service Invocation
Discovery
Service
Data Authorization
Data Query
Metadata
Catalog
Asset
ID
Vocab
Tag
Vocab
Tag
Vocab
Tag
Aggregation
Service ID
End Users
COIs
Aggregation
Service ID
Catalog Record
Metadata Tags
Metadata
Registry
Vocabularies
Vocabularies
MDE
WSDL
Data Exposure Example:Individual Health ReadinessPIMR
- Readiness Vocabulary
- Event (tag:event)
- Begin Date (tag:eventBegins)
- End Date (tag:eventEnds)
- Task (tag:task)
- Due Date (tag:due)
- Tasking Authority (tag:taskingAuthority)
- Immunization Status (tag:immunizationStatus)
- Name (tag:name)
- Held By Person (tag:heldBy)
- Description (tag:description)
Medical Event
Time
Patient
Doctor
Databases
Medical
Readiness
Overall Status
* Immunization Status
* PHA Status
AF COP
Vocab XSD
displays
User visibility to current health status for Total Force
SOA Modularity:Exposed Data Payloads
- PIMRRequest
22 lines
1 business object
PIMRPayload
22 lines
1 business object
HS
183 lines
9 business objects
DRS
38 lines
3 business objects
A1
47 lines
4 business objects
DDMS
38 lines
1 business object
EVT
46 lines
6 business objects
COI vocabulary effort enables 80% automated code generation
Modular approach improves reuse and flexible user response
Reduced development costs and automated information transmission
Barriers to SOA Implementation
- Acquisition Force Transformation
- Shift our technical development paradigm from systems to SOA
- Educate our SPOs/PMOs on the process
- Acquire SOA skills from small, agile contractors
- Agile Service Delivery
- Big Ugly – Re-engineer AF Acquisition Processes
- Dynamic Testing – Re-engineer AF Testing Processes
- Initial Investment
- Subject Matter Experts for upfront vocabulary work
- Support to functionals to expose their data
- Support Acquisition Community for centralized configuration management
- Transition to a centrally managed, end-to-end, capability based, federated infrastructure
AF COI Coordination Panel
- Panel Activities
- Alignment/Enterprise CM of COI vocabularies
- Vocabulary Training for COIs
- Coordination with DOD, Joint, Service COI activities
- Guidance on COI activities
- Technical Support – Enterprise Vocabulary Team (EVT)
- Core Team
- Road Team
- Expanding to charter C2 Data Harmonization Panel in support of JFCOM C@ Portfolio Management
Key SOA Principles
- Communities of Interest (COIs)
- Identify and define information to expose
- Select Authoritative Data Sources (ADS)
- ADS Owner
- Resource and implement services to expose data
- Limited and controlled implementation of data warehouses, data marts, and persistent data stores
- Limited build of new systems and applications
- Reuse of services from across AF and DOD enterprises
- No new point to point interfaces shall be built
- Scalability will be achieved through the creation of capability-based enclaves
