Mantech eIC Enterprise Information Interoperability Workshop

1
Mantech e-IC Enterprise Information
Interoperability Workshop

• June 29th 2004
• Group 1

2
Current As-Is Environment
Email
Supplier
Payment System
CSV File
Requisition System
Widget Procurement System
Supplier
Manual Entry into
Web-Based Purchasing Interface
Supplier
Access DB File
Customers
3
As-Is Architecture

• Vendor Side
• Deliver catalog data in ad-hoc fashion (email,
  CSV File, Excel Spreadsheet)
• Order notification via WPS
• Customer Side
• Web portal interface for purchasing
• Ordering fulfilled based on quantity required,
  price, and delivery schedule

4
Obstacles

• Resistance to change
• Cultures fragmented
• Must overcome Works as-is mindset (look beyond
  man-hour savings for automating data entry)
• Business rules and meaning of underlying data are
  hard coded
• Differences in stakeholder terminology
• Business rules in the buyer community vary
• Mapping is point-to-point

5
Assumptions

• No Big Bang approach, support legacy systems
• Global Environment
• Must be Expandable
• Vendor interface should be net-enabled
• Customer interface should remain web-based
• One class (commodity) can have many items
• Assume no ERP system interfaces

6
Objectives

• Reduce TCO
• Use Metadata consistently
• Minimal Intrusion to legacy system
• Flexible environment
• Future-resistant
• Utilize emerging industry best practices

7
Proposed System (Architectural View)
Payment
Supplier
Widget Procurement System
Map Into
Supplier
Requisition
Common Information Model (CIM)
Supplier
Proposed Inventory Management System
OWL, ISO 11179, XML Schema, UML, OOetc
8
The Key is a Common Information Model

• Multilevel Model
• - Can also be ontology driven
• Is Object Oriented
• Hierarchical
• Defines classes
• Has business rule engine
• Has semantic layer
• Utilizes semantic mediation

9
Additional Functionality

• Ability to publish metadata to authorized users
• Ability to track and query metadata to track
  actual data using semantic discovery
• Structured Standard Mapping (Tables -gt Classes,
  Columns -gt Attributes)

10
Proposed System (Functional View)
Procurement Contracting
Order Processing
Invoice Payment
Supplier Portal
Buyer Portal
E-Marketplace
Price Determination
Supplier Procurement
Buyer Procurement
Supplier Inventory Management
Buyer Inventory Management
Shipper
As-Is
To-Be
11
Metrics

• Better addressing of customers needs (reduce
  lead time for acquisition and increase inventory
  turnover)
• Value of seamless data exchange within/across ALL
  stakeholders
• Reduction in time to add new interfaces
• Electronic updates result in more timely and
  accurate information
• Cost of implementing CIM (upfront costs) versus
  significant downstream benefits

12
Objectives Revisited

• Reduce TCO
• - Interfaces less costly to maintain and augment
• - Seamless data visibility for all stakeholders
• - Increase inventory turnover
• - More correct data
• - Reduced lead time for procurement
• Use Metadata consistently
• - Outcome of using a Common Information Model
• Minimal Intrusion to legacy system
• - Yes, map to existing database is sufficient,
  but can be augmented as needed

13
Objectives Revisited

• Flexible environment
• - Map once, reuse many
• - Authoritative sources responsible for data
  integrity
• - Ease of adding new interfaces/suppliers
• Future-resistant
• - Utilizing open standards
• - Architecture scales easily as interfaces and
  users increase
• Utilize emerging industry best practices
• - Is being used in industries such as insurance,
  banking, health care