Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations KootK on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Black box document

Status
Not open for further replies.

stecko

Aerospace
Dec 3, 2007
2

Hi All,

I am working on R16 with Enovia VPM. When I load PSN with product I receive an incident report like below.


Black box document NAME_OF_FILE ( EnoviaVPM ) is not up-to-date in ENOVIAvpm.
You need to save Black box document in ENOVIAvpm.
You need to save Black Box CATProduct in ENOVIAvpm in order to update a document to document link that isn't up-to-date.


The product does not load automatically, I need to find it on the tree, right click on it and press load.
Does anyone know what is BLACK BOX? What should I do to load such files automatically, or how to save this BLACK BOX?

Regards
 
Replies continue below

Recommended for you

The thing with Enovia VPM is that it has two modes for CatProducts, structure exposed and black box.

The structure exposed mode gives enovia the control of the CatProduct meaning that there is no physical catproduct in the system, enovia is storing a virtual catproduct in the db, the benefits with this is that you have a visible structure in enovia and that you can control and configure the contents of that assembly in enovia.

The black box on the other hand is like catia native,a physical CatProduct is stored in the system, you can't see the assembly structure in enovia and also the children can be off sync, meaning that there is newer version of it somewhere, and that you need to synchronize from catia, because catia is controlling the CatProduct.

Note that you can store black boxes inside of structure exposed assemblies both not the other way around.

To me it sounds like you have synchronization issues. If the synchronization doesn't work from Catia you can try to send out the latest version of the part you have problems with first and then the assembly, this usually works because you can't send out two different version into the same catia session.

Depending on what kind of access level you have in enovia you could also try "impacted by" (I think) on the document level of the assembly part in enovia.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor