Logging NC with rich POD

[Former Member]

Hello,

I'm currently working with the Rich POD. I'm trying to log NC on a SFC. When i use the standard POD, I can log NC and it wil be usable as a paramater in the scripting of the route to decide whether to scrap the sfc or not. So this works correctly.

When I use the rich POD, it will automatically, after logging NC and pressing complete, go to the next 'normal operation' which is the standard script for 'done'. Though the NC is logged in NC reporting, the script does not trigger to hold the sfc. It also seems weird to me that I have to log NC and press complete in the rich POD in contrast to the standard POD.

In both cases i'm using the same route. Are there extra settings to be made for logging NC in the rich pod? I'm using the standard rich pod SUBASSY_HORIZONTAL.

Regards,

Manfred Klomp

[Former Member · Accepted solution]

This is working as expected.

I assume you are using the Log NC Reject plugin in the Rich POD. The Log NC Reject plugin does not perform any dispositioning in 5.x. The intended use of this is to log NCs when a buyoff is rejected. The SFC typically stays at the operation for the problem to be fixed and and a new buyoff request is made. This is common in a Complex Assembly scenario that is typical in Aerospace and Defense assembly.

You will need to use the Web POD if you need normal scripting or dispositioning.

[Former Member · Accepted solution]

Ok thanks for you're response!

Regards Manfred