Posts Tagged ‘PLM’

Navigating the Product Structure with Ease – Structure Browser & Where Used

February 20, 2013

MarcL: Modern solutions must allow users of the PLM solution to browse both up and down product structures with ease.  How is this accomplished in Aras?

Peter Schroer: The configuration modeler in the core of Aras Innovator is an implementation of Directed Graphs, meaning the relationships all have an implied direction.  Business rules for edit, create and delete use the direction to enforce good configuration management practices. The user interface can easily walk the user up and down the configuration graphs. This is so common that there are 2 pre-defined navigation browsers called Structure Browser (down view) and Where-Used Browser (up view) to provide a quick look at two common views of the Product Structure.

See additional information in Structure Management for Complex Products in Aras, Complex PLM Structure Multi-Views in Aras, PLM Product Structure Management Functionality in Aras and Making PLM Product Structure Accessible.

 

PLM_Alpha_Structure_Browser_1

PLM_Alpha_Where_Used_1

ERP, Item Masters and Data Attribute Federation Between ERP-PLM in Aras

May 22, 2012

MarcL: How is Object Approval capability linked to the ERP system so that specific item / material masters (e.g. parts, BOMs, components, packaging, part numbers, etc.) can be automatically setup by the PLM solution?

Peter Schroer:

The recommended best practice is to use Aras Innovator to master the definitions of Parts, Materials, BOMs, and packaging and then upon release, these data are uploaded to the corporate ERP system(s).

At the beginning of a project it is normal to use a one-time export and batchload from ERP to PLM to create the initial data set.

Links between PLM and ERP follow a “federated architecture” in which not all data is 100% replicated.

For example,  cost, inventory, kit-code data within the ERP might be useful information for a PLM user to see within the PLM screens (and use in Workflow business logic).

The Aras approach is to federate the 2 data sources so that data that is mastered in the ERP is linked to (web services) rather than copied periodically into the PLM.

In this way,  a single form within PLM may contain data from multiple data-sources,  but the end-user is not aware of IT architecture decisions.

The user sees all information they need to perform a task on one screen and can act/edit it, and Aras does not care whether IT has decided to actually store the data in PLM.

For additional information on these capabilities see posts tagged ‘Federation’.


%d bloggers like this: