Posts Tagged ‘solution studio’

Item Tracking, Status and Exception Reporting in Aras

May 21, 2012

MarcL: PLM solutions need to provide tracking, status, and exception reports and the reports should be able to be tailored to specific needs such as selected release level and specific attributes. There should also be the ability for reporting by exceptions, in particular on missing or incomplete objects belonging to a predefined set.

Peter Schroer:

Aras Innovator out-of-the-box includes default settings and tools for the Administrator to configure the level of history and audit trails that will be tracked, by Item Type.

For example a Part may have history of every transaction (view, update, create, etc) and audit trails supporting complete traceability,    while a Product Release Plan only has tracking of edit events.

These rules can be changed and updated at any time.

The Aras Innovator platform also provides a set of standard events for the solution developer to hang business rules (tests for exceptions, etc).

The most common approach is to link the exception testing to Lifecycle State changes,  and the exception testing can result in either just a message to the user, or a forced roll-back of the lifecycle status change until the exceptions are resolved.

This is all standard OOTB functionality in Aras Innovator.

We provide training on how to set-up, administer and customize these capabilities as well.

For additional information on these capabilities see the previous post ‘Business Intelligence, Custom Reports and Secure Reporting in Aras’ or check out the Posts Tagged ‘Reporting’ and ‘Administration’.

Advertisements

%d bloggers like this: