When we start a document review process on the portal (where the comments and document review tools are located), we send the code reservation to the contractor, who will send to us the document in review (0).

This document will be commented on by the TAG Engineering team, which may request changes. (Portal Side)

For that, the doc control will send the commented document to the contractor, requesting the fulfilment of the requests.

Once corrected, the document will be sent back to doc control as a new revision (A) and a new revision process will be carried out by the Engineering team.

Suppose the document under review A is approved. In this case, doc control will request the submission of one more review by the contractor, review B, with the status "Released by TAG".

Upon receiving the revision (B), the doc control will send the document directly to Meridian Power, since the document does not need further verification.

The problem observed refers to the fact that Power only recognizes the revision (B), losing all the history of versions (0 and A) and all the history of adjustment requests, impacting in the loss of fundamental information for the projects, lessons learned etc.

It is not feasible for documents to have to go through the Portal and Power flows due to the lack of integration between them.

The correct thing is that both environments talk to each other and that Power recognizes the entire review process carried out in the Portal and, of course, records the review history intelligently.