EII Thoughts

1
EII Thoughts Observations

• Mike Evanoff, Technical Director
• ManTech International
• Tuesday, June 29th 2004

2

• We will post slides and information from this
  workshop at the following site
• www.meiim.com

3
Workshop brief - outline

• Value Proposition
• Ingredients of EII
• Integration Server
• Methodology
• Vendor overview various approaches
• Ontology, MDA, XML, etc.
• Profusion of Metadata
• Closing thoughts

4
Introduction

• Personal Introduction
• Historical perspective
• Overview of Brief

The problems that exist in the world today
cannot be solved by the level of thinking that
created them. -- Albert Einstein.
5
EII Setting the Stage

• The problem of enterprise data access has been
  solved (circa mid-late 90s)
• The problem of enterprise information usage
  remains unsolved
• There is an increasing need to bring together the
  enterprise data such that the data can
  transformed into actionable information, which
  can then be used to enable new and innovative
  business processes
• Must be assured of the authenticity, meaning, and
  context
• Must operate in a timely to near real-time mode
• Must be more manageable and provide reduced TCO
  vis-à-vis traditional techniques in place today

6
DoD / Fed IT Environment Observations

• Decentralized management structure
• Driven first by politics, then by business /
  technology needs
• Supposed to embrace commercial best practices,
  reduce redundancies, and develop / maintain
  enterprise architectures collaboratively
• There are too many disconnected COIs with their
  own sets of cultural peculiarities
• Jargon, vocabularies, etc.
• Not agile, not responsive
• Sometimes we cant see the forest because of the
  trees!

7
Interoperability 30,000 ft ViewObservations
from the ground up

• 30k ft - Large Enterprise
• 20k ft - Enterprise
• 10k ft - Multiple COIs
• 5k ft - Community of Interest (COI)
• 1k ft - Multiple Application Systems
• 100 ft - Application System
• 10 ft - Info (Context Semantics)
• 1 ft - Data (Content, Format, Syntax)

LacksConsistency
Traditional EAI Apps
Overlooks
Focuses on
Information Data Semantics (for a given
Context)
8
Enterprise Information Interoperability (EII)

• EII represents a breakthrough approach to
  enabling interoperability within and across large
  and complex enterprises such as DoD
• EII represents discipline and a commercial
  marketspace and tools
• The EII approach to achieving semantics-based
  enterprise information interoperability supplants
  that of traditional EAI
• EII addresses both the physical and, more
  importantly, the logical aspects of information
• Metadata is at the core of EII
• Design-time metadata is used to capture the
  semantics and context within a shared purview for
  the enterprise
• Run-time metadata is used facilitate application
  integration and information sharing in a
  rigorous, formalized, repeatable, and computable
  manner

9
General Value Proposition
10
Five Essential Ingredients of EII

• Methodology
• To provide a way to capture and preserve the
  meaning of data and the pertinent contextual
  information in a rigorous, formalized,
  repeatable, and computable manner
• Metadata Management Approach (Ontology, Model
  Driven, etc.)
• Formal specification of how to express semantics
  and context for a particular domain of interest
• Supporting COTS tools
• Technical architecture framework
• User community

11
MEIIM Methodologywww.meiim.com

• Setting up teams
• Project Planning
• Deisign Discovery
• Implementation
• Continuous Improvement

12
Existing Project Plan
Project Management
VERSION 9-1
Initial Project Planning
Project
Updated Project Plan
Plan
Cross functional team comprised of
Industry/Government and ManTech e-IC, with
Internal / External Subject Matter Experts, and
Alliance Partners
Functional Process Working Group
Systems/Technical Working Group
Interoperability Working Group
1. Planning
Current Architecture
2. Design Discovery
Detailed Design
(20 80 rule)
3. Implementation
Target Architecture
Information InteroperabilityEngineering
Development
Detailed Discovery
Risks and Dependencies
Physical Data Mapping
QA,Test Debug
Interoperability Strategy
Requirements Specification
Logical / Virtual Modeling
Organizational Policy Goals
Interoperability Demonstration
Interoperability Engineering
Legal Considerations
Relate Logical to Physical
Evaluate Accept
Interoperability Specification
Security Policy
Optimize
Refine Requirements
Configuration Management
MEIIM
Deployment, training, and support
ManTech Enterprise Information Interoperability
Methodology
Enterprise InformationInteroperability Solution
13
Some Take Aways regarding EII Methodologies

• Externalizing
• To know it exists
• To represent it in an unambiguous, formalized,
  and computable manner
• Interoperability Engineering
• Physical mapping
• Logical mapping
• Relating Logical to Physical

14
Metadata Management Approach

• Ontology
• Model Driven
• W3C Approaches

15
Evolution of Data Access from standalone Apps of
the 1950s 60s to the connected Enterprise of
today
EII will standardize info usage for the
enterprise!
EII TierArchitecture

• Client / User Agent
• App Server
• Integration Server
• Enterprise Data Stores(i.e. DBMS, etc.)

3 Tier has standardized data access
Application Data Access
3 TierArchitecture
Data Access via RDBMS

• Client / User Agent
• App Server
• DBMS Server

Data Access via DBMS
Data Access via File Sys
Time
16
Some EII and Related Vendors

• www.metamatrix.com
• www.networkinference.com
• www.microsoft.com/biztalk
• www.unicorn.com
• www.compositesw.com
• www.webmethods.com
• www.tibco.com
• www.metaintegration.net
• www.iwaysoftware.com
• www.contivo.com
• www.modulant.com
• and others . . .

17
Profusion of Metadata

• Use service portfolio
• you cant reuse what you cant find
• Profusion of XML Schemas
• WSDL is out of control
• Metadata is key but no single solution exists
• Metadata is spiraling out of control at several
  levels backbone, process auto, workflow, app
  level, bam, etc.
• EAI backbone
• Process automation
• Workflow
• Application level, etc.

18
QA time?
19
Enterprise Information Interoperability
EII
Design Time Data Strategy
Virtual / Logical Model
Incremental Implementation
EII
Loosely-coupled
Transport
Security
XML Technology
Non-invasive
Validation
Interoperability
A breakthrough approach to enabling
interoperability within and across large and
complex enterprises.
EII achieves interoperability by operating at the
logical level of information exchange. EII
focuses on the meaning and context of data and
identifies and resolves conflicts that might
affect communication between people,
organizations, and applications that generate or
process the information.
ManTechs e-ICs interoperability team is focused
on researching, developing, and implementing EII
technologies to help streamline enterprise
interoperability infrastructures. For more
information on projects the team is currently
involved with, please visit http//www.dcnicn.com/
xmledicentral/ or http//www.dcnicn.com/mh-60_elit
e_phase_ii/.