WINDCHILL STEP CONNECTOR FOR AP242AFNET UPDATE
On behalf of Kedar OakSr. Director, Product Management
17/10/2018
2
FULLY INTEGRATED CONNECTED PLM
ROLE & TASK BASED
APPLICATIONS
PLATFORM
Windchill Connected(Navigate, Digital Twin, AR Design Review, Requirements)
Marketplace(Partner/OEM)
ENTERPRISE DOMAIN
APPLICATIONS
MES/ SCM
SIMULATION
ERP MRO CRMDEVICE CLOUD
MFG SUPPLIERS CUSTOMERSCONNECTED PRODUCTS
& MACHINES
CLOUD | HYBRID | ON-PREM
Source Data
Powered by:
Extend PLM: Contextualize/Synthesize/Orchestration/Engage
MBSECAD BOMREQ
& TEST
(Lifecycle Management including CAD-Data,
BOM,Change)
Windchill Core(Systems
& Software)
3
PTC FOCUS ON OPENNESS
• Active participation in
industry initiatives / Groups
• Interoperability
agreements
• Strong partners
ecosystem
4
• CPO Certification based on– Written response with supporting
artifacts
– 2 Days on site audit and interviews
• The Audit and certification criteria covered – Interoperability
– Infrastructure
– Extensibility
– Interfaces
– Standards
– Architecture
PTC AWARDED “CODE OF PLM OPENNESS” CERTIFICATE
“Openness is both in PTC strategy and people’s DNA”
The auditors from TUV Informationstechnik Gmbh
PDM functional capabilities supported by the STEP AP242 interface
Date, Author 7
Windchill 11.1 M010
PDM informationImplementation Format Level of implementation
P21- AIM XML BO M. Pilot IF test COTS
"As Designed" PDM product structure ✓ ✓ ✓
Nested PDM product structure X ✓ ✓
Assembly validation properties (* as per PDMIF) ✓ ✓ ✓
Lifecycle management ✓ ✓ ✓
Document structure X X X
Person and organization ✓ ✓ ✓
Date and Time ✓ ✓ ✓
Classification ✓ ✓ ✓
Material properties X X X
Customized PDM properties ✓ ✓ ✓
Configuration management - based on effectivities ✓ ✓ ✓
Configuration management - based on specifications ✓ ✓ ✓
8
• Support for JAVA 11
• Support future test rounds of PDMIF, tentative scope is as below
• Support for Ed2 schema.
STEP CONNECTOR FOR AP242 ROADMAP
Test Round 7 scope (Q3 Q4 2018) – Results of the Full scope of VDA UC2 Weekly Delivery Update
Cycle Use case • Multi IDs on parts
• Combined with DAIMLER Use case: Multi-lingual on part name
– CONF4: Combined scope of CONF1, CONF2, CONF3 • Create 2 files: revision eff. / occurrence effectivities
• Add more specification, categories
• Multiples versions of same part in same file
– CUST: include “real-world” UDA (from Daimler-Renault-Nissan)
– Complete “harmonization of PDM Properties / UDA v1”
Test Round 8 or 9’s Test Cases scopes (2019)– Requirements from UG:
• As-built product structure
• Visual Issue management (VIM)
• Elementary-TC of Delta Change
– Proposals from IG, taken from general experience what information is typically exchanged in industry use: • Possibly: Evolution of Test Cases of previous Test rounds
• Test multiple versions in one file, incl. part version relationship
• Nested files with Configuration management
• Sharing of documents between parts
• Handling Mirrored parts
• Versioning of ProductClass
• Approval status relationship (workflow)
• ProductConfiguration
PTC Confidential, subject to change