Improvement in the LOGICs in ACC to import BCF status inside ISSUES

[sara_kashbur]

ACC, once importing aBCF inside Issue Tab, THAT IS UPDATING AN EXISTING ISSUE FROM BCF, ACC Issue is not reading correctly the value 'Open' of the BCF Status.

Note: This occurs not at the first import (new issue) but in the update of an existing Issue. This happens only in the case of Status Open, while in case of status Close, the issue status is updated reading the BCF Status.

The same situation happen in case of other Status related to BCF imported inside ACC Issues, such as In Review or Pending, but those are not considered as meaninfull use cases since not standard BCF Statues and not impacting the General Checking workflows  using BCF.

Saipem faced the missing of integration of  BCF ‘Open’ Status inside ACC Issue as a very impactful dysfunction on workflows.

Here below you can find the details of our workflow and issue and the list of attachments:

A98-C-0100_WP_V1_ifc and 2BCFs.zip

A98-C-0100_WP_V2_ifc and 1BCF.zip

[sara_kashbur]

Additional experience on the BCF 'file import' task, make me realize that - as stated in the ACC on line guideline - the system can import a BCF only if there are component included in the BCF itself.

This is an other major limitation of the system, since this will avoid the import of any BCF that is the updating of an rule base check results in a third party sofware, that is obviously the most used case when I import a BCF in ACC (if I have to perform visual analisys I can do them direcrly in ACC by the viewer and than generate directly the issue in ACC).

What happen is the following:

1st iteration of checks: I run the checks on ifc in a third party tool, I generate  a BCF with some problems identified by the objects and this BCF is sucefully imported inside ACC as Issue with Open Status;

My modeler checks the issues and update the model accordingly;

2nd interation of checks: I run the checks on the ifc of the emended models. The system is not finding the previous errors since emended, so the BCF is updated with the status close , with no object associated anymore. When I try to import the BCF updated in ACC, this is not imported anymore: conclusion even if the status  close is supported in ACC, this cannot be updated in ACC!

In my opinion, the possibility to update an issue status based on the BCF Identifier would be a great benefit for the business in all the cases where the BCF is used to mange the comments.

Currently ACC supported solution is too limited and required to many manual activity in the managing of the BCF to be used in a real project process, that probably for all sector where the interoperability is a mandate (like italian pubblic administration or BIG companies like mine that use multiple softwares and many subcontractors/stakeholders) or ACC adoption could be strongly restricted and other plartform can be evaluated to manage project process.