The document discusses integration options for connecting Aras Innovator to other systems. It outlines Aras' integration platform capabilities and technologies like flat file, AML-lite, WSDL, EAI/ESB, and IOM API integration. Examples of packaged CAD integrations and a sample integration scenario are also provided. Users are directed to Aras resources for help with integration and development.

1. BEDIFFERENT ACE 2012 I NTERNATI O NAL
Copyright © 2012 Aras. All Rights Reserved. aras.com

2. ACE 2012
INTERNATIONAL
Integration Basics
Nathan Brown
Director of Product Management
Aras www.aras.com
Copyright © 2012 Aras. All Rights Reserved. aras.com

3. 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

4. Integration Landscape
Authoring Systems Enterprise Systems
MCAD
ERP
EDA
Electrical
Aras Innovator CRM
Software Concept Design Development Launch Manufacture Support
Firmware Phase-Gate Program Management
Authoring Compliance Enterprise
Configuration Management Contract
Integ. Platform Integ. Platform
Document Mgt Deliverables
MS-Office File Vault
Desktop Publishing Quoting Requirements
Management
&
Traceability
Sales
Configurator
BOMs & Parts
AVL / AML
Qualified
Suppliers
Manufacturing
Planning Maintenance
Repair &
Overhaul
Graphic Design Reports & FMEA CAPA
Dashboards Process Flows Control Manufacturing Deviations
Corrective Actions Execution &
Plans
Waivers
Simulation
CAM
Legacy ERP Systems
CAPP
Digital Factory
Ideation PLM / PDM
Requirements Mgt. Sales Configurator
Collaboration
Legacy Systems
Costing
Compliance
PLM Legacy /
Point Solution
Copyright © 2012 Aras. All Rights Reserved. Slide 4 aras.com

5. 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

6. 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

7. Example: CAD Integration
Aras Innovator
1
CAD Data Part BOM
CAD MCAD 2
System
Software
ECAD
3
 Successful CAD integrations require a well-
1
defined integration platform CAD data managed in Aras
2 Automated Part BOM updates from CAD
 Aras is actively enhancing these core features
3
and working with partners to promote best Enterprise change management with CAD
data visibility
practices
Copyright © 2012 Aras. All Rights Reserved. Slide 7 aras.com

8. Example: Process Best Practices
Mechanical CAD
Save Update BOM
Mechanical
components
• Single combined Part BOM
• Automated updates by CAD Connectors
• Clear ownership by discipline
Electronic CAD • Access to CAD content from Parts
• Ability to make manual updates
Circuit board
and components
Save Update BOM
Parts List
Software Design
Software
components
Save Update BOM
Manually-added
components
Slide 8
Copyright © 2012 Aras. All Rights Reserved. aras.com

9. 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

10. 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
EAI/ESB
WSDL
Flat File AML-lite
Copyright © 2012 Aras. All Rights Reserved. Slide 10 aras.com

11. 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

12. 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

13. 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 TXT
<AML/> Innovator Server
<AML/> Response
OUT
Federation
IOM API
EAI/ESB
WSDL
Flat File AML-lite
Copyright © 2012 Aras. All Rights Reserved. Slide 13 aras.com

14. 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
<XML/> IN
Request
Innovator Server
xslt <AML/> Response
xslt <AML/>
OUT
Federation
IOM API
EAI/ESB
WSDL
Flat File AML-lite
Copyright © 2012 Aras. All Rights Reserved. Slide 14 aras.com

15. 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
Request
Integration Web
Code
<XML/> <XML/>
Service <AML/> Innovator Server
<AML/> Response
OUT
Federation
IOM API
EAI/ESB
WSDL
Flat File AML-lite
Copyright © 2012 Aras. All Rights Reserved. Slide 15 aras.com

16. EAI/ESB Integration
 You can create web services for Aras items and expose through WSDL
 Specific item properties and actions must be defined, and remain static
Enterprise Service Bus
Other System <XML/>
Aras Innovator
IN
Request
Integration Web
Code
<XML/> <XML/>
Service <AML/> Innovator Server
<AML/> Response
OUT
<XML/>
Federation
IOM API
EAI/ESB
WSDL
Flat File AML-lite
Copyright © 2012 Aras. All Rights Reserved. Slide 16 aras.com

17. 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
IOM IOM
IOM Request
Code <AML/> Innovator Server
API <AML/> Response
API
API OUT
API
Federation
IOM API
EAI/ESB
WSDL
Flat File AML-lite
Copyright © 2012 Aras. All Rights Reserved. Slide 17 aras.com

18. 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 Web
Aras Innovator
<AML/>
Service
IN
Integration
IOM
Code Request
IOM
IOM
<AML/> Innovator Server
API <AML/> Response
Integration API
<XML/>
API OUT
Code
API
Federation
IOM API
EAI/ESB
WSDL
Flat File AML-lite
Copyright © 2012 Aras. All Rights Reserved. Slide 18 aras.com

19. 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
 item
Search, display and update external data
 Single, consistent user interface
 Expose data stored in legacy systems
Copyright © 2012 Aras. All Rights Reserved. Slide 19 aras.com

20. 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

21. 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
Innovator
Server
Method Code
Integration IOM TXT TXT
IOM IOM <AML/> <AML/>
Code API
API
API
<AML/>
API
 Legacy MRP system only
accepts flat-file input
 Write Aras method code to
 Sales Configurator system is extract BOM information via
able to output BOM
<AML/>
AML and convert to necessary
configurations in XML format format
 Transform XML to AML via  Transfer file to polled directory
XSLT, and submit directly to <XML/>
xslt location on MRP server for
Innovator server processing
 End result is configured BOMs
per configurator output Sales Configurator
Copyright © 2012 Aras. All Rights Reserved. Slide 21 aras.com

22. 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

23. ACE 2012
INTERNATIONAL
Questions?
Nathan Brown
Director of Product Management
Aras www.aras.com
Copyright © 2012 Aras. All Rights Reserved. aras.com