![]() ![]() The result was a drawing identical in appearance with sequential and loop numbers preserved, but all of the tags were unique due to acquiring a new area designation. Blank drawings were created with the project’s template file, updated with the area designation in the drawing properties and then populated by pasting the copied contents of the entire source drawing. ![]() Tanks or other P&ID objects could be replicated onto separate drawings with a simple copy-clip and paste action. Upon insertion, they were immediately tagged with the new area number while retaining the existing sequential number. When set up to automatically acquire that area designation to populate the tag itself, tags remained unique when copied between drawings as long as each drawing had a unique area designation property. It is common to prefix tag numbers with an area designation, be it system, drawing number or area number. To mitigate these errors and reduce database audits, users were encouraged to hold off tagging components until all copies of the untagged blocks were placed. However, this visual cue was not always provided when copying between drawings and too often, duplicate tags were not identified or updated. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |