Slides aras plm software integration basics

BEDIFFERENT ACE 2012 I NTERNATI O NAL

Copyright © 2012 Aras. All Rights Reserved.

aras.com

ACE 2012 INTERNATIONAL

Integration Basics Nathan Brown Director of Product Management Aras www.aras.com

Copyright © 2012 Aras. All Rights Reserved.

aras.com

Agenda  Integration Landscape  Packaged Integration Offerings

 Aras Integration Platform Capabilities  Aras Integration Technologies

 Example Integration Scenario  Where to go for Help

Copyright © 2012 Aras. All Rights Reserved.

Slide 3

aras.com

Integration Landscape Enterprise Systems

Authoring Systems MCAD EDA Electrical Software Firmware

Concept

Design

Development

Launch

Manufacture

Support

Phase-Gate Program Management Authoring Integ. Platform

MS-Office Desktop Publishing Graphic Design

ERP CRM

Aras Innovator

Quoting

Reports & Dashboards

Compliance

Configuration Management

Document Mgt File Vault

Requirements Management & Traceability

Sales Configurator

FMEA

BOMs & Parts

Process Flows

Contract Deliverables

AVL / AML

Enterprise Integ. Platform

Manufacturing Planning

Qualified Suppliers

Control Plans

CAPA Corrective Actions

Manufacturing Execution

Maintenance Repair & Overhaul

Deviations & Waivers

Simulation CAM CAPP Digital Factory Ideation Requirements Mgt.

Legacy ERP Systems

PLM / PDM Sales Configurator Collaboration Costing Compliance

Legacy Systems

PLM Legacy / Point Solution Copyright Š 2012 Aras. All Rights Reserved.

Slide 4

aras.com

Packaged Integration Offerings  Many packaged integrations are available for Aras:  MCAD  EDA  Electrical  Software  Firmware  ERP Systems  Microsoft Office

 Other PLM / PDM Systems  SharePoint & Other Collaboration Systems

Copyright © 2012 Aras. All Rights Reserved.

Slide 5

aras.com

CAD Connector Suite MCAD Connectors

EDA Connectors

 Dassault Systèmes

 Mentor Graphics

 CATIA V5 / V4

 DxDesigner / DxDatabook

 SolidWorks

 PADS PCB

 Siemens PLM Software

 Cadence

 NX

 Allegro

 Solid Edge

 OrCAD

 PTC

 Altium

 Pro/ENGINEER

 Designer

 CoCreate

 Protel Capture

 Autodesk

 Zuken

 Inventor

 CADSTAR

 AutoCAD

 CR5000/3000

prepackaged CAD connectors are 3rd party add-ons; additional connectors also available Copyright © 2012 Aras. All Rights Reserved.

aras.com

Example: CAD Integration Aras Innovator 1

CAD Data

CAD System

Part BOM

MCAD

2

Software

ECAD

 Successful CAD integrations require a welldefined integration platform  Aras is actively enhancing these core features and working with partners to promote best practices

Copyright © 2012 Aras. All Rights Reserved.

Slide 7

3 1

CAD data managed in Aras

2

Automated Part BOM updates from CAD

3

Enterprise change management with CAD data visibility

aras.com

Example: Process Best Practices Mechanical CAD

Save

Electronic CAD

Update BOM

• Single combined Part BOM • Automated updates by CAD Connectors • Clear ownership by discipline • Access to CAD content from Parts • Ability to make manual updates Update BOM

Save

Mechanical components

Circuit board and components

Parts List

Software Design Update BOM

Save

Software components

Manually-added components

Copyright © 2012 Aras. All Rights Reserved.

Slide 8

aras.com

Aras Integration Platform Capabilities  Aras provides additional capabilities to address the needs of common

integrations  Based on input from customers and partners

 Event model  The Aras Event model provides great flexibility for controlling integration behaviors, for example: • On promotion to Released state  send Part to ERP • OnAfterVersion  go update viewable in other system

 Data structures  Standard CAD Document data model

 Special APIs  CheckoutManager for bulk file download

 Process best practices  CAD change process

Copyright © 2012 Aras. All Rights Reserved.

Slide 9

aras.com

Aras Integration Technologies  We will be reviewing the following technologies: 1. Flat File Integration 2. AML-lite Integration

3. WSDL Integration 4. EAI/ESB Integration 5. IOM API Integration 6. Federation Integration

 These are roughly in order of capability and effort

to implement

Federation IOM API

Flat File

AML-lite

Copyright © 2012 Aras. All Rights Reserved.

WSDL Slide 10

EAI/ESB aras.com

It’s Always AML…  Every integration method is fundamentally AML input and

output behind the scenes Aras Innovator IN

<AML/>

Request

Innovator Server

<AML/>

Response

OUT

Copyright © 2012 Aras. All Rights Reserved.

Slide 11

aras.com

It’s Always AML…  Every integration method is fundamentally AML input and

output behind the scenes Aras Innovator IN

<AML/>

Request

Innovator Server

<AML/>

Response

OUT

Copyright © 2012 Aras. All Rights Reserved.

Slide 12

aras.com

Flat File Integration  Use method code in Innovator to convert flat file to AML, or vice versa

 Can be client or server side

Other System

Aras Innovator Method Code

IN Request

TXT <AML/>

TXT

Innovator Server

<AML/>

Response

OUT

Federation IOM API Flat File

AML-lite

Copyright © 2012 Aras. All Rights Reserved.

WSDL Slide 13

EAI/ESB aras.com

AML-lite Integration  If the system can produce or consume XML, then transform it to AML

using xslt, and communicate directly with the Innovator server

Other System

Aras Innovator IN

<XML/>

Request

Innovator Server

xslt xslt

<AML/>

<AML/>

Response

OUT

Federation IOM API Flat File

AML-lite

Copyright © 2012 Aras. All Rights Reserved.

WSDL Slide 14

EAI/ESB aras.com

WSDL Integration  You can create web services for Aras items and expose through WSDL

 Specific item properties and actions must be defined, and remain static

Other System

WSDL

Aras Innovator IN

Integration Code

<XML/>

<XML/>

Web Service

Request

<AML/>

Innovator Server

<AML/>

Response

OUT

Federation IOM API Flat File

AML-lite

Copyright © 2012 Aras. All Rights Reserved.

WSDL Slide 15

EAI/ESB aras.com

EAI/ESB Integration  You can create web services for Aras items and expose through WSDL

Other System Integration Code

<XML/>

<XML/>

Enterprise Service Bus

 Specific item properties and actions must be defined, and remain static

Aras Innovator IN <XML/>

Web Service

Request

<AML/>

Innovator Server

<AML/>

Response

OUT

<XML/>

Federation IOM API Flat File

AML-lite

Copyright © 2012 Aras. All Rights Reserved.

WSDL Slide 16

EAI/ESB aras.com

IOM API Integration  IOM is the Aras Innovator API

 It has full access to all item types, plus special platform calls like

CheckoutManager, plus convenience functions

Other System

Aras Innovator IN

Integration Code

IOM

IOM

IOM API API API API

Request

<AML/>

Innovator Server

<AML/>

Response

OUT

Federation IOM API Flat File

AML-lite

Copyright © 2012 Aras. All Rights Reserved.

WSDL Slide 17

EAI/ESB aras.com

Federation Integration  You can use multiple interface types (WSDL, IOM)  It has full access to all item types, plus special platform calls like

CheckoutManager, plus convenience functions  Allows for real-time data exchange

Other System Integration Code

Web Service

<AML/>

IN IOM IOM

Integration Code

Aras Innovator

IOM API API API API

<XML/>

Request

<AML/> <AML/>

Innovator Server Response

OUT

Federation IOM API Flat File

AML-lite

Copyright © 2012 Aras. All Rights Reserved.

WSDL Slide 18

EAI/ESB aras.com

Federation  Federated properties  Display important values from other systems inside Innovator

 Federated ItemTypes



 Entire item is stored in another system, but acts just like a native Innovator itemdisplay and update external data Search,

 Single, consistent user interface  Expose data stored in legacy systems

Copyright © 2012 Aras. All Rights Reserved.

Slide 19

aras.com

Summary of Technologies  Use the Flat File approach only if the other system is limited

to that  Both the AML-lite and IOM API approaches allow for any

Innovator operation to be accomplished  The IOM API approach provides most if not all of the

functionality of a standard web service. However, it does not provide a discoverable web service in the traditional sense – there is no WSDL.  For a more traditional web services integration, use either

the WSDL or EAI/ESB approaches

Copyright © 2012 Aras. All Rights Reserved.

Slide 20

aras.com

Example Integration Scenario  Build API to API integration

between graphic design system and IOM  Create functions to create

Document items, transfer files, and trigger PDF generation

Aras Innovator

Graphic Design

Legacy MRP Method Code

IOM IOM

IOM

<AML/>

<AML/> API API API API

TXT

TXT

<AML/>

Integration Code

Innovator Server

 Legacy MRP system only

accepts flat-file input  Write Aras method code to

 Sales Configurator system is

 Transform XML to AML via

XSLT, and submit directly to Innovator server  End result is configured BOMs

per configurator output Copyright © 2012 Aras. All Rights Reserved.

extract BOM information via AML and convert to necessary format

<AML/>

able to output BOM configurations in XML format <XML/>

 Transfer file to polled directory

xslt

location on MRP server for processing

Sales Configurator Slide 21

aras.com

Where to go for help  Aras Technology page  http://www.aras.com/technology/integration-federation.aspx

 Aras Partner pages  http://www.aras.com/partners/

 Aras Community Forums  http://www.aras.com/community/forums/

 ‘Developing Solutions’ Training  http://www.aras.com/university/training-classes.aspx

 Programmer’s Guide  API Reference Copyright © 2012 Aras. All Rights Reserved.

Slide 22

aras.com

ACE 2012 INTERNATIONAL

Questions?

Nathan Brown Director of Product Management Aras www.aras.com

Copyright © 2012 Aras. All Rights Reserved.

aras.com