Embed Size (px)
Citation preview
Interoperable Enterprise Content Management
iECMAIIM Kick-off Meeting
Paul Fontaine DOT
Mike Connor Adobe
Cornelia Davis Documentum
Co-Chairs iECM
AIIM Introduction
Welcome - Betsy Fanning The Customer View - Paul Fontaine Overview - Mike Connor Architecture Considerations - Duane Nickull Metadata Interoperability - Cornelia Davis JSR-170 for iECM - David Nuescheler Discussion - All
E-Gov & DOT – Paul Fontaine
My Role E-Government Lead Working Relationships Experience
iECM - Business Problem iECM – Interest and Support
Federal IT Spending $68B
U.S. Federal Government spending on IT products and services will increase at a compound annual growth rate of 8.5 percent, from $45.4 billion in fiscal year 2003 to $68.2 billion in FY 2008, ... Homeland-security and e-government initiatives top the list of priorities.
Input - Federal IT Market Forecast 2004-2009
Why iECM?Stovepipes Cripple Us!
ElectronicElectronicPublishingPublishing
CollaborationCollaboration
FormsFormsManagementManagement
RecordsRecordsManagementManagement
WebWebContentContent
ManagementManagement
DocumentDocumentManagementManagement
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
DOT PMA E-Government Projects
Grants.gov Business Gateway Recruitment-One-Stop Integrated Procurement Records Management International Trade Data System Web Content Management Document Management Correspondence Management (CCMS) Rulemaking
QuickTime™ and aTIFF (Uncompressed) decompressor
are needed to see this picture.
Horizontal Stovepipes
Recruitment
Finance
Grants
Procurement
Training
Use CasePublic Health
Use Case Criminal Investigation Multiple Agencies, Multiple Departments, Multiple Records Systems – One Job
Electronic Case Jacket
Written Reports
Allways Airlines
Carlo Giles
Vision – Global Information Sharing
Information in Motion - Requirements
Package Manage Workflow Transport PeopleInformation
Intelligent Information Information should know how to…
Act on itself Present itself Classify itself Route itself Protect itself Leverage new & existing services and standards
Within the context of who’s using it what they are doing and where they are.
The iECM Architecture & Services
Create/ AcquireCreate/ Acquire
Organize/ Process
Organize/ Process
Store/ Retrieve
Distribute/ Publish
Distribute/ Publish
Rules / Event Management
Archive/ DestroyArchive/ Destroy
Secure / Authenticate / Administer
IECM Web Services / SOA Architecture
Search / Find
Format
Front End Processes
Back End / Desktop
Applications
External Processes
ECM Systems
Process Services
Infrastructure / Service Bus
Integrate / Orchestrate
Capture, share, and leverage metadata
Authoring
Visualization
Transformation
Publication
StagingAssembly
Collaboration
Security
Meta data RepositoryData Model / Services
Rules Engine
OntologyServices XMP Services
Policy / Security
XMP
XMP
Data Services
Data Store
Goals
Discuss architecture requirements and concepts
Present proposed architecture process and methodology
Examine proposed architecture Form iECM Architecture working group
Architecture Goals
Document Requirements as input; map to a reference architecture.
Define scope and paradigm for technical infrastructure.
Remain agnostic to implementation detail (programming language, O/S etc.).
Define a core set of services. Constrain protocols and specifications to ensure
interoperability within iECM environment.
Proposed Architecture Process
Specific architecture proposals
Service Oriented Architecture (SOA): Based on web services standards. Use OASIS SOA Reference Model as guide.
Facilitates multiple, concurrent implementations.
Not reliant on any proprietary standards or protocols.
Message Oriented, event driven and composable architecture.
OASIS SOA RM - draft
Architecture scope – phase I
IECM Service Oriented Architecture
Core iECM Services and Patterns
Federated Search Content Retrieval Content Management Security Services
Optional Services and Patterns
Transformation Validation
iECM Process Management Process Management is outside initial scope. Rationale: need to define core services first before
defining management of services.
SOA Layer
POA Layer
References
OASIS SOA RM TC – http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm
AIIM iECM Announcement - http://www.aiim.org/article-pr.asp?ID=29666
Architecture Working Group – dnickull#adobe.com (replace # with @)
Introduction
Summary
Use Cases
IntroductionIntroduction
Introduction: Information/Content Management
Information Management is achieved through a set of services on a body of content that enable or streamline business processes.
Traditionally ECM systems have operated in a centralized information store and services model.
Evolving business needs as well as the requirement to manage ever expanding volumes of data through automated means are calling for an architecture where both content and processes are distributed.
Tried and true data models still apply. Files + metadata. Self-describing content.
Self-describing content
Which is the corn? Open the can. What does it cost? Ask the clerk. How many calories? Ask Delmonte How does the store automatically
manage inventory? You can’t
MetaData Standards and Extensions
Standardized labeling allows multiple vendors to consistently represent information to consumers
Extended labeling for LOB uses
Self-describing Content
Introduction
Summary
Use CasesUse CasesUse Cases
Use Case: Information Lifecycle Management Management of files on the storage platform with goals of optimizing
storage, meeting compliance objectives, etc. Deduplication Tiered storage Retention Data protection
ILM technology sits between the storage system and applications. Current state of the art makes deductions based on a very limited
set of attributes available for all files; size, create date, modify date, …
A richer, yet standardized, metadata set greatly enhances the ability to appropriately manage an asset.
How do we make sure the metadata exists for all content? “Centralized” data dictionary, schema management Distributed data validation
How do we make sure that ILM appliances understand supplied metadata?
LegalFinancial Marketing
Metadata in Information Management
Content is categorized via metadata
Use Case: Extra-repository ECM
Rules EngineAuthoring
Application
Data Dictionary
Repository
Validation Service
Schema Service
Search Service
Schema centrally managed and accessible from authoring application
Data validation and enforcement during creation – supports full information lifecycle management
Metadata drive contextual and automatic search of relevant materials
Full object definition supports in line external evaluation
Easier or automatic entry into repository
LegalFinancial Marketing
Each SLO group contains the Service Parameters
Business Critical
Mission Critical
Compliance
Retain =5 yrsDedup = Not AllowedProtection = offsite
Retain =1 yrsDedup = Not AllowedRTO / RPO = 99.99%Protection = offsite
Retain = use Corp def’nDedup = AllowedProtection = backup
Metadata in Information Management
Content is categorized via metadata
Actions performed on information objects (including metadata)
Interoperable Enterprise Content Management
Source: AIIM IECM Proposal (Paul Fontaine, FAA and Mike Connor, Adobe)
Compo
nent
ized
Interoperability – a start…
Application
Application
Web
Service
Web
Service
Web
Service
SOAP
<Envelope>
</Envelope>
SOAP
<Envelope>
</Envelope>
Decoupled Services
Interoperability – … continued
Application
Application
Web
Service
Web
Service
Web
Service
SOAP
<Envelope>
</Envelope>
SOAP
<Envelope>
</Envelope>
Decoupled Services
AND
Decoupled DATA
iECM and Intelligent AuthoringConstructing proof of concept
Included in Interoperable ECM talk: Momentum Barcelona May 23-26
Expanded at Momentum Las Vegas, OctoberPress ReleaseAIIM IECM committee
Adobe’s Extensible Metadata Platform (XMP) “The eXtensible Metadata Platform is Adobe’s description format
for network publishing. This new framework is an electronic labeling system for files and components of files, designed so that computers can read and understand the labels, and populate the information automatically into the right fields in databases, respond to software agents, or interface to intelligent manufacturing lines, just to name a few of the implications.” (XMP whitepaper)
Standardizes an XML format for metadataPackages metadata with file contents
iECM and Intelligent Authoring (cont)
Demo flow:User creates new InDesign documentUser provides base metadata values (departmental
affiliation, document type and customer)Departmental affiliation and document type determine
additional schema elementsData validationAn image is pulled into the document
Comes from public libraryIncludes embedded metadata including IPR values
Metadata from image is absorbed by containing documentMetadata from containing document is propagated down to
the image fileTransparent or one-click ECM check-in ILM processing (categorization and actions)
SummarySummarySummary
Introduction
Use Cases
Enterprise Content Management is Changing
It’s an evolution.
Becoming more distributed Becoming ILM
The need for cross application data use is driving a fundamental architectural change that is pushing some functionality down into infrastructure. in particular, the metadata functions.
Introduction to JSR-170 for iECM
What is JSR-170?
„ The API should be a standard, implementation independent, way to access content bi-directionally on a granular level within a content repository. “
http://www.jcp.org/en/jsr/detail?id=170
RepositoryA
ApplicationA
API A
RepositoryC
ApplicationC
API C
RepositoryD
ApplicationD
API D
RepositoryB
ApplicationB
API B
Challenges: State of the EnterpriseIsolated Content, Proprietary Repositories
Repository A
Application A
API A
Repository C
Application C
API C
Repository D
Application D
API D
Repository B
Application B
API BStandard API
One API removes the Silos
Challenges: Standard API for Content Repositories (JSR-170)
Repository A
Application A
API A
Repository C
Application C
API C
Repository D
Application D
API D
Repository B
Application B
API BStandard API
Consolidation, Single Repository
Content Repository Infastructure
Solution: Content Repository ExtremeThe only production JSR 170 product
Industry StandardJSR 170: Content Repository for JavaTM technology API
Specification LeadDavid Nuescheler, Day Software, Inc.
Expert GroupApache Software Foundation Art Technology Group Inc.(ATG) BEA Systems Day Software, Inc. Documentum, Inc. Filenet Corporation Fujitsu Limited Hewlett-Packard Hummingbird Ltd. IBM Macromedia, Inc. Mediasurface Ltd.Myers, James D. Novell, Inc. OracleSAP AG SAS Institute Inc. Software AGStellent, Inc. Sun Microsystems, Inc. Venetica CorporationVignette
Java Standardization
Specification to be finalized by H1/2005
Reached “Proposed Final Draft” 11-feb-2005
Current Status of Process
Outside the scopeCategory (A) [Consensus unreachable / low
priority]:
Outside the scope of the JSR-170 Specification but part of every Content Repository Products (eg. Jackrabbit).
No Repository Administration No Workspace & Nodetype Mgmt No Access Control & User Management
Outside the scopeCategory (B):
Outside the scope of the JSR-170 Specification because it should be implemented in the Application Layer.
JSR-170 is a Content Repository API, NOT a CMS API No Workflow, No GUI, No Languages No Semantic Information Model
Java Content Repository
(1) The obvious ...
SCMDM
WCM
The Promise of ECM
…
Java Content Repository
(2) Beyond obvious ...
SCMDM
“Far beyond” ECM…
NetworkFS
RDBMSReplacement
XMLDatabases
DAM
Directory(LDAP) WCM
…
…
…
JSR-170 and iECM
Enterprise Content Repository Server
JSR-170 API
JSR-170 to iECM
iECM Content Client
Application
iECM
iECM – The Technology iECM is an SOA environment
Leverages existing standards work & technology Services layer for exchange / mgt of content
Easy to create and manage content rich business processes across multiple domains Accelerates ECM adoption up, down & across organizations Reduces project costs, maintenance and risks
Powerfully capitalizes on promise of SOA Move the industry into leadership role in software industry Opens doors to significant opportunities at project, enterprise
and cross enterprise / industry domains Answers analysts– “What services do you provide & consume?”
But that isn’t what’s most important to me!
Why iECM is Important
Enables Government to Fulfill its Mission E-Government (Presidents Management
Agenda) Citizen Centric Results Oriented - Efficiency and Effectiveness Market Driven
iECM enables Global Information Sharing iECM = Information, where, when & how
needed!
iECM Centers of Excellence / PilotsInteraction with a World Wide IECM Community of Practice
Government Industry ISV’s SI’s Standards Groups Working Groups Major Project and
Program Managers
Real World RequirementsThought LeadersReal ProjectsInteroperability TestingBest Practice Development
WhitepapersForumsConferences
RelationshipsInsight
Market Relevance
iECM Roadmap
Conceive
Q2
Investigate Validate
Q4
Requirements & Design
2005
DevelopRun
2006Q3
Concept Evaluation Technical Development
Information In Motion
Case-based workflows Documents & forms,
driven by web-services and encompassing
business rules, ad-hoc workflow
•Mortgage application•Collaborative case folders•Criminal Investigation•Benefits Management & Administration
Case-based workflows Documents & forms,
driven by web-services and encompassing
business rules, ad-hoc workflow
•Mortgage application•Collaborative case folders•Criminal Investigation•Benefits Management & Administration
Distributed Workflow Text & Multimedia
information to guide local & remote personnel
through workflow, with interactive services for Logistics, Reporting,
Ordering
Distributed Workflow Text & Multimedia
information to guide local & remote personnel
through workflow, with interactive services for Logistics, Reporting,
Ordering
Information ApplicationReal-time information
client, secure, personal information discovery and
action
Information ApplicationReal-time information
client, secure, personal information discovery and
action
iECM - Interoperable Enterprise Content Management
For Immediate Release
ACTIVITY INITIATED TO STANDARDIZE INTEROPERABLE ENTERPRISE CONTENT MANAGEMENT (iECM)
AIIM, the international enterprise content management standards developer announces a new standards activity. A service oriented architecture for Interoperable Enterprise Content Management (iECM). IECM, will address the growing need to interoperate and manage enterprise content related systems seamlessly across organizational and system boundaries.
- Christopher Baum, Research Vice President, Public Sector, Gartner, Inc.
In an environment with a myriad of content management systems and styles, this standard would be the basis for a solution“
"Brand Niemann, US Federal CIO Council, Emerging Components Group
I am very pleased to see the iECM standards effort approved and launched. We will work with the team to facilitate interoperability, trial pilots and education across government.“
Frank Gilbane, Bluebill Advisors and The Gilbane Report
"The IECM standards activity is critical to addressing one of the biggest information technology challenges - integrating diverse applications and the information that they process
Open Standard / Open Source
Initiators – Paul Fontaine, USDOT, Mike Connor & Duane Nickull, Adobe, Betsy Fanning AIIM
Interest & Support Customer Support
Fed CIO Council Executive Office of the President (OMB) DOD, Interior, Justice, Courts Parliaments – EU, Switzerland, Netherlands Italy - CNIPA – Italian Egov, DOT Germany - Bund Online – eRecords France – MOD, Health
Analysts Gartner, Gilbane
Standards Groups JSR-170, C30 Committee, OASIS TC on SOA & more
Vendor Community - Initial Adobe, Documentum, Microsoft, HP & more coming
Business Benefits Customers
Information Sharing Infrastructure - Scalable, maintainable, agile Efficient automation of information centric workflows & process Focus budget on new business needs instead of maintenance
ECM Vendors Increased Market Size – Larger / Smaller projects Increased Sales Opportunities – Easier to integrate & to create client solution Increased return on development and professional services $ Magic Quadrant
ECM SI’s More consulting projects Larger scale projects – Enterprise / Industry Information Sharing Replicable Solutions – lower risk – faster time to market
AIIM Increase Business Value & Vitality of ECM Global program of vital importance PR magnet for major business and industry publications
Feasibility
Timing - Right place, time, solution for market Customer interests, standards, SOA, Analysts, Enterprise
Architectures
Technically – not hard Composition of working Group
Real business problems, projects & deadlines
Focus – Extensibility, Core functionality – not edge cases
Accelerating customer awareness and demand – possible legislative requirements
iECMInformation SharingFor The Next Decade
Let’s
Roll
