Maintains revision synchronization between items and associated Engineering Collaboration (EC) Design objects.  Keeps the design object’s Revision label in sync with the corresponding item revision.  PX's are triggered by state changes in the ECO workflow.

Incorporates items that are included as affected items of Change Orders.

Triggers upon entry to a workflow state.  Commonly associated to a Submitted or Review state of a workflow, ensuring that attachments are incorporated prior to the release of a change, whereby preventing inadvertent changes prior to release.

Checks each Affected Item on a change order and incorporates those that are not already incorporated.  Logs actions to the History table for the change order.

Customer, as a business practice, populates the Change object’s effectivity and obsolete dates to be the same as the release date for the Change object.

Upon entry into the first release status encountered in the workflow, reads release date for Engineering Change (EC), populates the release date into effective and obsolete date fields.  Error log recorded on object's history tab.

Run as a Part object post-create event to populate the description of the newly created part, based upon 3 attributes assigned to the Item (Subclass, Catagory, and Modifier)

Upon item creation, the user completes required fields, clicks the Create button and the final description is created.

Example:

User attempts to create an Item and completes required fields.

• User selects subclass:            Document
• User selects category (cascade list):    490-PROC\DIODE ST\OPERATION
• User enters a modifier:            INSPECTION AND REPAIR

User clicks the Create button and the PX executes in the background.

• Final Description: PROC,DIODE ST,OPERATION,INSPECTION AND REPAIR

Agile then displays the created record for the user with the new description in place…which may be further modified by the user depending on roles/privileges available.  Any characters in the full description that exceed the description field length will be truncated (240 characters allowable in Agile).

Automatically assigns Approvers/Observers to any workflow status.

The signoff matrix combines an Excel spreadsheet, based off a specific format which is maintained by the customer and a custom extension which actively polls the spreadsheet for true/false values and updates a target workflow status with Approvers/Observers.

The spreadsheet contains:
•    Workflow Name
•    Workflow Status
•    Affected Item subclass
•    Affected Item BU (Business Unit)
•    Affected Item Category
•    …and up to 2 additional variables.

Against each criteria line, the following additional values will be present
•    Approvers
•    Observers

Any workflow status level may be used.  When a workflow enters a Review/Released status type, the application will poll the spreadsheet for matching criteria.  When true, all corresponding Approvers/Observers against true criteria change to signed-off.

Allows the customer to update the spreadsheet with any new criteria lines as updates to existing workflows or new workflows added in the future.

(Contact us for pricing)

Runs from a Part’s Action Menu via a Change Order’s workflow state change.

If launched from a change order, reviews each Part Class affected item as if launched from the part itself.  Starting with the top-level part (which could be the part from which the application was launched or the affected item on a change), drills down in the part’s multilevel bill-of-material (BOM) and calculates the rolled-up compliance, beginning with the lowest level subassemblies all the way back up to the original top level.

The ChangeCAST to ACS service provides connectivity from Agile ACS to the existing ChangeCAST based ERP adapter by utilizing the Domain Systems toolkit to parse, translate and format the ACS output files to match the existing ChangeCAST output file format.  This service provides a static java based application that runs on a scheduled basis to process aXML output files being produced by Agile ACS.

The toolkit will parse and translate the aXML output files to produce ‘AGL’ format output files that conform to the customer’s ERP adapter requirements, and are ready to use by the existing ERP adapter with no further changes required.

Data translations provided by ChangeCAST are duplicated in the toolkit to support upper-case, lower-case, truncation, conditional logic, substitution, etc. Also supported are single/multiple output files, horizontal/vertical format, field and text delimiter specifications, etc.

Transfer protocols such as network drives and ftp are also supported.