Our path to PDM Enablers

1
Our path to PDM Enablers

• Steve Baunach
• Chief Technical Officer
• Inso Corporation
• PDM Division

2
Agenda

• Who is Inso
• Business Drivers
• Solution Strategy
• Summary

3
Inso Corporation
history of innovative solutions and successful
customers

• In support of our customers success, Insos
  solutions enable large corporations to manage,
  exchange and deliver information.

4
Who is Inso

• 90M (1999E), publicly traded company
• 500 employees worldwide
• Three Divisions
• eBusiness Technologies - Internet information
  management and personalized delivery
• Information Exchange - Information access and
  conversion technologies
• Product Data Management Division - Manage and
  distribute information required to design and
  manufacture a product
• Inso acquired Sherpa Corporation in 12/98

5
Business Drivers
Tomorrow - Accommodate
Agile Adaptive Affordable
Yesterday - Control Reduce Cost Reduce Cycle
Time Improve Quality
6
Enterprise Information Backbone
Next -generation PDM systems ... can provide
users with the integration needed to achieve an
enterprise view of the entire product definition
and development process AMR Research July 1998
All Enterprise Personnel
Partners, Suppliers
Customers
Product Lifecycle Backbone
Internet Infrastructure
7
The Evolution of Product Development
Competitiveness (source Gartner)
1990s
2000s
1980s
Market size
Margin
Competitive Focus
Market share
Lower costs
Product Development Strategy
Innovation
Time to market
Productivity
Technology Focus
Leveraging intellectual capital
Data sharing
Serial design process
Process Focus
Inter-enterprise collaboration
Concurrent engineering
Organizational Focus
Departmental
Project teams
Agile market teams
8
Product Lifecycle Management
Market
Develop
Purchase
Build
Support
BOM Drawings Specifications
BOM Manufacturing Instructions
Installation Maintenance Instructions
Specifications Product Options
Specifications Drawings
Product Information Backbone
Manage and Distribute Intellectual Capital
Mechanical Designs
TechnicalPublications
Software
Electrical Designs
Manufacturing Instructions
Specifications
Data Creation Tools
9
Supporting Many User RolesChange Management
10
System Requirements

• Out-of-the-Box Applications
• Easy to Learn
• Easy to Enhance and Maintain
• Fits with evolving IT infrastructure
• Operates in a globally distributed enterprise

11
Component Based ApplicationsBuild a town not a
high rise

• High-rise (single customizable application)
• requires detailed planning of the whole thing
• hard to change once its built
• not useful until its all done
• Building a town (component based applications)
• start with simple components
• add new components as the towns needs grow
• replace components as early ones become outdated

12
Zoning Rules
13
The classic case for a standardPoints of
Integration
Mfg. Systems
SAP
QAD
Applicon Frame
EDS IMAN
PTC Intralink
Dassault CDM
SDRC TDM
Eng. Data
Office Auto.
CADkey
Work Group

• Test Results
• Spec.s
• . . . .

• MS Office
• Access
• . . . .

EDS UG
PTC Pro/E
Dassault CATIA
Applicon Bravo
SDRC Ideas
14
Product Information Backbone
Mfg. Systems
SAP
QAD
Product Information Backbone
Enter- prise
SherpaWorks
Applicon Frame
EDS IMAN
PTC Intralink
Dassault CDM
SDRC TDM
Eng. Data
Office Auto.
CADkey
Work Group

• Test Results
• Spec.s
• . . . .

• MS Office
• Access
• . . . .

EDS UG
PTC Pro/E
Applicon Bravo
SDRC Ideas
Dassault CATIA
15
Standard PDM Object Models
PDM2(supplier)
PDM1
STEP OMG
STEP OMG
CAD1 Data Mgr.
CAD3 Data Mgr.
CAD2 Data Mgr.

• STEP - International Standard
• AP 203, AP 214, PDM Schema
• OMG - Object Management Group
• PDM Enablers

16
Why the PDM Enablers team worked

• Manufacturing users are pragmatic
• Four major PDM vendors involved
• It is possible to agree to interfaces at some
  reasonable level
• Leveraged other standards
• Leveraged each other

17
Next Steps

• PDM Enablers implementation is part of the
  SherpaWorks roadmap for 2000
• Working with vendors and customers to drive other
  implementations
• Apply PDM object model to XML for business to
  business exchange

18
Summary

• Agile, Adaptive, Affordable
• It is the internet age and the bottom line counts
• Why standards
• Companies need a common set of terms to exchange
  information efficiently
• Why OMG
• Leverage best-in-class talent of similar
  interests
• Why Now
• Critical mass of frameworks exist
• Need domain oriented information models