The iECM:What is in it for you?

Agenda

• ECM Requirements• 3 Approaches to ECM• iECM What is it?• iECM for you

ECM functions to be standardized

Requirements/Use Cases

• Regulatory Compliance– Records Management– Freedom of Information Act– E-Government Act– Presidential Directives

Requirements/Use Cases

• Federal E-Government Requirements– Presidents Management Agenda (PMA) initiatives– Federal Enterprise Architecture– Citizen-centric, results oriented, market based– Simplify and unify, maximize IT investments

Vertical Stovepipes

Travel

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Travel

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Travel

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Travel

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Horizontal Stovepipes

Recruitment

Finance

Grants

Procurement

Training

Three Approaches

• Standardization• Integration• Interoperability

Standardization

• Select the “best” product for the enterprise, migrate everyone/everything to that product.

Standardization

• Advantages– Simplified Support– Simplified contracting– Simplified infrastructure

• Disadvantages– Everyone compromises

requirements– No single product meets all

needs– Migration of existing

applications/data– Vendor dependence– Change management– External interfaces– Not an option for cross-

enterprise applications

Integration

Build connections between each application/business process

Content Rep.

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Content Rep.

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Content Rep.

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Content Rep.

Forms

Records Mgt.

Training

Procurement

Recruitment

Grants

Finance

Rulemaking

Integration

• Advantages– Relatively quick

development for high priority projects

• Disadvantages– High development costs for

custom work– Proprietary nature of EAI

products– High Maintenance costs– Nx integrations

Interoperability

• Every application (component) is fully compatible with any other application (component) and can perform any business function on any information anywhere on the network.

Interoperability

• Advantages– Vendor independence– Interface with any system– Optimize external ISP

options– Minimal integration

costs/complexity– Minimize program life cycle

costs– Minimize system

implementation costs/time– New functionality

possibilities

• Disadvantages– Requires coordination of

multiple stakeholders• Vendors

• End Users

• Systems integrators

• Etc.

… New Approach

• This is NOT EAI! This is not about connectors!• Instead, it is about standardizing content management components

and capabilities so that applications can utilize those components ubiquitously across all content stores.

Cross-CMS Applications

iECM - What is it?

• Interoperable Enterprise Content Management (iECM) is a consortium of vendors, customers and systems integrators that will create an interoperability framework that enables information sharing across organizational and system boundaries.

What is the Goal?

• Global access to and processing of “information”• Increased effectiveness of IT investments• Increased Citizen/Customer Service

What is iECM framework?

• The iECM framework describes the relationship between all of the dependent variables in a multifarious information management system to facilitate the implementation of a fully interoperable system.

Requirements

InteroperableSolution

iECM - What is it doing?

• Develop Technical Reference Model• Collaborate with related standards initiatives• Identify/Develop best practices for

interoperability• Facilitate engagement of all stakeholders

(vendors, integrators, end users, academia, etc.)• Pilot implementations

How to Achieve interoperability

• Widespread Implementation of Standards

• Vendor Commitment• Customer Commitment

Content Management Services

• Library Services• Business Process

Management• Content Distribution

Services• Appropriate level of

granularity

• Related Standards:– BPEL– ICE– XForms– …

Domain and Data Model

• If we do not address metadata standards we will still have a “one-off” problem.

• Related Standards– RDF– OWL– XML Schema– ADO– SDO– Variety of ontologies:

• PRISM• Dublin Core• …

– …

Semantic search continuum

Controlled Vocabulary

StrongSemantics

Taxonomy

ER Model

DB Schema, XML Schema

Topic Map

Conceptual Model

First Order Logic

Relational Model, XML

RDF/S

UMLOWL

Description Logic

WeakSemantics

Semantic Interoperability

Structural Interoperability

Syntactic Interoperability

Modal Logic

Thesaurus

Glossary

Logical TheoryIn

crea

sin

g M

etad

ata

Increasing Search Capability

Recovery Discovery Intelligence Question Answering Reasoning

List

Axiology

Source: Dr. Leo Obrst, Mitre, Mills Davis, TopQuadrant

Component Descriptions

• What are the concrete manifestations of the components of the iECM ecosystem? How are they accessed?

• Not separate from CM services or data models

• Will support varying levels of service sophistication

• Related Standards– UDDI– ebXML– WebDAV– HTTP– SOAP– WebServices– JAVA (JCR)

iECM Technical Deliverables

• iECM Reference Model including at least:– Content management services– Information Models– Schema for describing artifacts in the iECM

environment

• Best practices that instantiate the iECM reference model with existing technologies and standards.

• A web services instantiation of the iECM reference model.

iECM: Time for the next level

• iECM is needed to allow organizations to better use and manage their content

• Now is the time for contributions from all segments of the ECM market

• Call to action:– Visit the web site for more information: h

ttp://www.aiim.org/standards.asp?ID=29284• Contact…

Betsy Fanning, AIIM (bfanning@aiim.org)

• Eric Stevens, Outreach Chair (eric.stevens@hummingbird.com) or

• Paul Fontaine FAA, Paul.R.Fontaine@faa.gov

Thank you!

Paul Fontaine

Federal Aviation Administration

Office of the CIO

Paul.R.Fontaine@faa.gov