Aras Innovator
Overview
Aras Innovator is a PLM tool (Product Life Cycle Management) that focuses on the life cycle of physical products, such as parts, from the introduction phase, to growth, to maturity and finally decline. Within this world, businesses need software to guide them through each phase efficiently while ensuring high quality and centralized data. Aras is able to do this while executing rapidly on an interconnected system and ensuring that information flow from product concept to retirement is integrated between multiple teams across multiple departments.
Connector Setup Details
This section describes the basic steps needed to prepare your Aras instance for use with Viz.
Minimal User Permissions & Viz User
We recommend that you create a new user within your external tool, to be used only for Viz. This is the user information you will enter when setting up your tool connection within Planview Viz. By creating a new user, you will ensure that the correct permissions are granted.
In general, your Viz user account should have sufficient permissions to read artifacts in your tool.
Your user should have a secure password or token. Please be aware that Viz will not allow you to save a tool connection utilizing a weak password/token, such as 'tasktop.'
Connecting to the Aras Repository
Standard Authentication
Required Fields:
- Location/Connection URL
- Example Format: https://hostname:port/InnovatorServer
- Username
- Password
- Database
- The database named specified in InnovatorServerConfig.xml
Supported Artifacts
Supported Work Items
|
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
PRs (Problem Reports) |
Any supported repository version: |
Yes |
|
ECRs (Engineering Change Reports) |
Any supported repository version: |
Yes |
|
Parts |
Any supported repository version: |
Yes |
|
Simple ECOs (Engineering Change Orders) |
Any supported repository version: |
Yes |
|
Express ECOs (Engineering Change Orders) |
Any supported repository version: |
Yes |
|
Express EDRs (Engineering Document Reviews) |
11.0SP15+ (with add-on Product Engineering 11R4+ installed) |
Yes |
|
Affected Item |
Any supported repository version: |
Yes |
Supported Containers
|
Containers that can be modeled as Flow Items |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
N/A |
|
|
|
Containers used to define which artifacts are included in an Artifact Set |
||
|
N/A (entire tool is used as container) |
Any supported repository version: |
N/A |
Supported Field Types
Planview supports configuring rule-based modeling (i.e., conditional modeling) using the field types shown below
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not function properly.
|
Field Type |
How is field type referenced in the repository? |
Sample Repository Fields Supported |
|---|---|---|
|
|
String, Multilingual String, Foreign, Sequence, Text |
ID, Title, Name, Revision |
|
|
List, Filter List |
Unit, Cost Basis, Priority, Severity, Change Type |
|
|
Multi Value List |
|
|
|
Boolean |
Changes, Released, Fast Track |
