CATIA.CAA.v5 - PLM Integration Strategy

PPR W o DELMIAe rk s p a c APIs
VPM R e le a s e
APIs
PPR R e le a s e
E n te rp ris e H u b (C o n fig u re d x B O M )
D is trib u tio n W o rk flo w
APIs
PLM Integration Strategy - Overview
Mission Let applications access diverse and distributed data as if it were a single source Enable the integration of structured and unstructured data
M a n u fa c tu rin g H u b
E n g in e e rin g H u b
Page
9
ENOVIA V5 EAI Integration Strategy Roadmap
First exposure of VPM V5 product structure as PLM integration services Enable customers and service providers to build extended enterprise integrations based on EAI middleware using the exposed PLM integration services Further exposure of necessary elements of the VPM V5 product structure as PLM integration services.
2004 CAAV5 Developer Conference – Méridien Montparnasse – Paris - DASSAULT SYSTEMES – Mars 2004
Page
2
Existing Integration Capabilities
ENOVIA – PPR பைடு நூலகம்ub STEP Part 21 Adapter
CAA RADE tools provide Users with a Rapid Application Development Environment to create a unique, competitive system federating enterprise expertise
Interactive software development tools built on top of best-in-class de facto standard RADE tools Integrated software development tools covering the full software development lifecycle coverage
Existing Integration Capabilities ENOVIA – PPR Hub STEP Part 21 Adapter (STEP Interface) ENOVIA – PPR Hub SA Adapter (SAP Interface) Building Integrations using the CAA API’s Future Enterprise Integration Plans - Overview Enterprise Integration Delivery Roadmap
2004 CAAV5 Developer Conference – Méridien Montparnasse – Paris - DASSAULT SYSTEMES – Mars 2004
Page
8
PLM Solution Architecture
Other Product Eng. Apps Other Collaborative & Life Cycle Apps Other Mfg Eng. Apps
Web Apps Presentation Win Apps Presentation
PPR Services PPR Configuration
Page
PPR Modeling Objects PPR Relations PPR Connectors Enterprise Architecture
Human Resources Procurement Finance
ENOVIA
Product data
SAP R/3
ERP data Sales & Marketing
2004 CAAV5 Developer Conference – Méridien Montparnasse – Paris - DASSAULT SYSTEMES – Mars 2004 Page 5
R e le a s e C hange C o n fig u ra tio n
MiddleWare Grid Computing OS – CPU - Hardware
2004 CAAV5 Developer Conference – Méridien Montparnasse – Paris - DASSAULT SYSTEMES – Mars 2004
PLM Applications
TeamPDM VPM Navigator LCA Navigator PPR Navigator
PLM Ware
VPM CATIA W o rk s p a c e APIs
ENOVIA/ SMARTEAM
ENOVIA/ SMARTEAM APIs ENOVIA/ SMARTEAM
Supporting process based synchronization logic
Federate data belonging to enterprise hub and external systems into a single system ‘view’ Technology Use PLM integration services to expose PLM data Use exposed PLM integration services and industry leading EAI middleware (e.g. IBM WBI / ICS, WAS Foundation, or Microsoft BizTalk) to synchronize data between applications
2004 CAAV5 Developer Conference – Méridien Montparnasse – Paris - DASSAULT SYSTEMES – Mars 2004
RADE
6
PPR Business Logic
PPR Business Objects
Future Enterprise Integration Plans - Overview
Solutions
CAA API’s enable customers and service providers to build added-value applications to fulfill their company-specific needs:
Design, implement, debug and test connectors to access CRM, SCM, ERP systems Connect PPR to Legacy, CRM, SCM, ERP applications Extend the PPR model Create Portals, Authoring & Management applications
to provide real-time in place read and write access to synchronize data belonging to multiple sources
Requirements Synchronize data from enterprise hub to and from external systems and applications
PLM Integration Strategy
Enterprise Integration Strategy and roadmap for the integration of the ENOVIA V5 products within the extended enterprise
Contents
2004 CAAV5 Developer Conference – Méridien Montparnasse – Paris - DASSAULT SYSTEMES – Mars 2004
Page
4
ENOVIA – PPR Hub SA Adapter
Integration with ERP process
PPR Hub – SA Adapter (SAH) pprovides the ability to export Bill of Materials and any associated documents to SAP R/3 You may chose to implement systematic “push to SAP” on certain events such as new part creation and engineering change release, or on well-identified gates in the product lifecycle Rules can be setup permitting modification to product data to be performed only in the upstream process (ENOVIA V5) that would subsequently be propagated to downstream process (ERP)