The document presents a use case for automating the process of suppliers submitting documents to an ENOVIA V6 2015 system. It describes a product called the ENOVIA Document Uploader that was developed to mass upload documents and metadata from a spreadsheet into ENOVIA. Key benefits include reducing manual effort, eliminating data errors, and improving the user experience for managing supplier documents. The solution demonstrates how it extracts metadata and files from a spreadsheet, maps the attributes, and loads the content and associated metadata into ENOVIA. Future enhancements are discussed such as improved file management and making the tool web-based.

1. Presented By: ArcherGrey
Date: July, 2016

2. Outline
• Overview
• Use Case 1
• Product Uploader to ENOVIA V6 2015 - Demo
• Questions & Answers
• Next Steps
7/26/2016 ArcherGrey Proprietary & Confidential 2

3. SUPPLIER / VENDOR
DOCUMENT SUBMITTAL
Use Case – Example
7/26/2016 ArcherGrey Proprietary & Confidential 3

4. Key Business Needs – Value Prop
1. Vendors / Suppliers submit response / request – can produce
large number of documents and metadata to be created or
updated in ENOVIA – automation and proper data handling
2. Many different systems contain Vendor / Supplier
information – Doc Control must capture content, create or
update information in PLM & associate relative document –
automate and control source
3. No automation in this process, risk & time consumption is
very high – reduce time & risk
4. Improve user experience !!!
© 2015 PLM Technology Inc.

5. ENOVIA DOCUMENT
UPLOADER
Developed as a framework to support mass uploading and updating of
objects and supporting data.
7/26/2016 ArcherGrey Proprietary & Confidential 5

6. The Solution
PLM Document Uploader
PLM
Capabilities :
• One time and UI mapping of attributes
for Admins.
• Auto population of content document
files (TXT, DOC, XLS) files into PLM
system.
• Extract meta data from Excel
spreadsheet and correctly represent
that attribute data in PLM.
• Associate documents specified in
spreadsheet in PLM system to Vendor
Doc.
• Server side logic to handle error
messaging and exceptions.
• Update metadata and content data
within PLM.
Challenges Addressed :
• Reduced ’s manual effort in creating
objects and attaching content docs.
• Eliminate risk of data corruption /
incompatibility of content files.
• Address overwhelming manual task
while editing existing objects.
• Eliminate manual upkeep and
tracking change or creation process
for supplier interaction.
© 2015 PLM Technology Inc.

7. Current State
• Simple Installation
• Design Based on Service Model
• Autonomous Operation / Web-Capable
• Multiple and Complex Data Scenarios
• Accepts Spreadsheet Input Files
• One File - multiple types and relationships
• Supports ENOVIA number generator
• Supports transactions
• Multiple Independent Instances…Yes
7/26/2016 ArcherGrey Proprietary & Confidential 7

8. File System
Source has entry row within Excel
spreadsheet having a unique
Attribute and File Name to be
loaded.
The data is parsed then loaded in ENOVIA. Error message if the Attribute and
File Name columns are not present in the input file. If the values of Attribute
or File Name is blank, the row will be ignored and an error will be reported in
log file.
The attributes and
content file will be
properly represented
in the ENOVIA V6
2015 application.
Extraction
Transformation
Layer
© 2015 PLM Technology Inc.
How it works
Mapping file
Note : Only admins can define the attribute
mapping. Users do not have to modify the
attribute mapping every time. Attribute mapping
is a onetime admin activity.
Note : If Vendor Document object exists with same
attribute and file name, the metadata will be
updated. If Vendor Document object does not exist
a new Vendor Document object will NOT be
created. An error message should be added to the
log file
.

9. Future Work
PLM Data Interface
PLM
Capabilities :
One-time and/or on-going
• Extract data, either staged or
externally stored data
• Cleanse data through proper
scrubbing and error handling
• Transform data into downstream
business
• Load into new PLM system
• Serve corporate needs by offering
web service based data access
• Automatically synch data between
various sources and destinations
Challenges Addressed :
• Preserve valuable historical
information that could otherwise
get lost in transition from PDM to
PLM
• Eliminate User frustration due to
poorly executed transition
• Avoid unnecessary re-keying of
existing data
• True integration with single-sign-on
Share
Point
Old
PDM
© 2015 PLM Technology Inc.
9

10. Considered Future Enhancements
• More Sophisticated File Management
• Dashboard Displays
• Useable as Client or Server
• Web-Based Control
• Multiple OS (Windows, Mac, Linux, etc.)
• Other Platforms (PLM Flex, SAP, …?)
• Live Code Updates
• Integrated Toolsets (Connector Model)
7/26/2016 ArcherGrey Proprietary & Confidential 10

11. Questions & Answers
Please contact brion.carroll@archergrey.com
Thank You
For the opportunity to present
7/26/2016 ArcherGrey Proprietary & Confidential 11