PTC Windchill ESI 9.x Architecture presented by Sreeni from GAIN ( Gandhavalla Informatics Pvt Ltd)

1. Presented by: Sreeni

2. ESI (Windchill PDM Link) – Details
•Reducing manual work.
•Improving of business process speed.
•Reduce Maintenance Costs of distributed
systems
•Create an Extensible and scalable
platform for handling multiple data files
•Reduce turn around time and improve
productivity by eliminating redundant
processes
•Reduce operating cost for transaction
processing
• Any publish history mismatch between
PDM Link and ERP results in publish
failures.
• Not covering all use case blue prints
during implementation results in publish
failures during production.
•Some use cases could not be
implemented due to constraints in PLM
and ERP systems (this can be minimized
during Gap analysis).
•Some use cases could not be
implemented due to constraints in PLM
and ERP systems (this can be minimized
during Gap analysis).
•ESI upgrade involves lots of manual
process and requires a test run after each
upgrade / migration. (ESI upgrade
generally happens when SAP is upgraded)
•Requires high hardware investment.
•Internalization and localization has
practical implementation issues.
• Automated part numbering through SAP
• Automated ECN numbering through SAP
•Configuration and customization
required for Prototype publishing
•Configuration and customization
required for Pre Release
•Configuration and customization
required for sending options / variants
•Customization required to handle part
numbers starting with *step etc
•Custom BAPIs to handle custom
attributes and business conditions.
•Effectivity handling in ESI to meet
business requirement
•Content view customization
The Objective The Challenges GAIN’s Solution

3. ESI (Windchill PDM Link) – Details
•Reduced 70% of manual work.
• Integrated Business Solution using Re-
usable components via SOA based
architecture
• Business Process Automation via
Websphere Process Server with the
Versioning support
• Reduced Throughput time via Business
Process to automate the manual processes
and rules engines
• Asynchronous Processing via IBM
Message Queue Series
• Windchill PDM Link 9.1
• EMS
• TIBCO BW 5.4
• TIBCO SAP R/3 Adapter 5.6
• TIBCO Admin 5.5
•Java
•JCO 2.1
• Oct 2009 to Jan 2010 Detail Design
• April 2010 to Dec 2010 Development
and testing
• 1 Tibco onsite
•7 Windchill
The Benefits The Technology The Statistics

4. ESI (Windchill PDM Link) – Architecture
Info*Engine
EAI Core Services
Transa
ction
Mgmt
Error
Handlin
g
Messa
ge
Loggi
ng
WC to
ERP
Cross-
Refere
ncing
ERP
Defaul
ting
ERPMapper
Common
Business
Object
(CBO)
(ERP
Neutral
Represen
tation of
WC
Objects)
WindchillMapper
TibcoERP
Adapter
Adapter
Config
EAI
Business
Logic
(Support
Transacti
ons with
ERP
System
thru
Adapter)
JMSQueues
SOAPEncoding/Decoding
Tibco Core Components –
BusinessWorks, Rendezvous, Enterprise
for JMS, Repository
WCESIServices
SOAP
Encoding/Decoding
PDMLink9.0
WC Objects
Parts
BOMs
DOCs
ECNs
SAP Objects
Materials
BOMs
DOCs
Change Masters
ERPAPI
ERP
ApplicationLogic&
dB
ERP SystemESI MiddlewareWindchill
JMSQueues

5. ESI (Windchill PDM Link) – Architecture
Windchill
(Info*Engin
e)
JMS
(Queues)
CBO
SAP
ECN
Materi
al
BOM
Doc
EBL
SAP R/3
Adapter
(BAPIs)
ECN
Part
BOM
Doc
User Rel Obj Event Parse Event
Send RequestDataReq
Response
Result
Response
Parse Response
Parse
Respon
se
Send
Result
Parse Result Response
TIBCO Business Works
RPC/Quer
y
Gen
Respon
RPC/Upda
te
Gen
Result
CBO
Map CBO
AP
I
De
f
Re
f