Where can I get a comprehensive list of the drawing attributes that are exposed by the piping system to OPIM when used with AutoPLANT?
The OPIM documentation says that "AutoPLANT adds a few standard drawing attributes" and lists the following attributes:
FILENAME, STYLE, DATE, TIME, PRJ_NAME, SIZE1, SIZE2, SPECMAIN, LINENUMBER, UNIT, SERVICE, NAME, ALIAS, ACTIVE
The log file from running an iso lists the following, different, set of attributes in the "system drawing attributes" section:
FILENAME, STYLE, TIME, PRJ_NAME, SIZE1, SPECMAIN, INSTANCE_ID, STORAGE_PATH, STORAGE_ROOT, LINENUMBER, UNIT, SERVICE, NAME, ACTIVE, SHEETNO, NO_SHEETS, PRESPLIT_SHEETNO, PRESPLIT_NO_SHEETS, REPOSITORY_IDENTIFIER, GRIDNAME
This Communities post reveals that you can use *(GUID) to obtain a component's COMP_ID , which doesn't seem to be documented anywhere else:
I'm trying to add attributes to my isometric and would like to have a full list of which fields are available to work with. For example: The shipping node2da.txt file includes a mapping for node 33 to AREA but AREA doesn't appear to be the name of the attribute exposed by the piping system. I realize that I could obtain the area by using a DbQuery but if that attribute is already exposed by the piping system via a different attribute name I would rather just use that.
Hello Marc,
Thanks for your question, Regarding Area you can use AREA3D attribute,
we are evaluating your further requirement and get back to you soon.
Regards,
Abhijit Bute
Hi Abhijit,
I'm not having any success using AREA3D either. I have tried the following in the textnodes.txt file:
P_AREA = *(AREA3D)
AREA_TEST = SELECT NAME FROM AREA3D WHERE NAME LIKE '$(AREA3D)' OR NAME LIKE '$(AREA)' OR NAME LIKE '$(P_AREA)'
The log file shows that this line is processed into this:
SQL = SELECT NAME FROM AREA3D WHERE NAME LIKE '' OR NAME LIKE '' OR NAME LIKE '' -> result =
Which shows that none of *(AREA3D), $(AREA3D), or $(AREA) resolve into any value so there is no result value. The only way I can return a value for area from the server is to use
SELECT A.NAME FROM AREA3D AS A INNER JOIN RELATIONSHIPINSTANCE AS R1 ON R1.ID1 = A.ID where R1.ID2='$(compID)' AND R1.RELATIONSHIPTYPE = 18
I have a feeling it is going to increase processing time if I have to do loads of joins for each iso's attributes.
Hi Marc,
Have you tried looking at the "Show Tag Data" tools? It will most likely show you the list of all tag attributes available for different types of component in an iso drawing.
Hi Tuan,
If I change my OPIM output format to dgn from dwg I can see tag data using the "Show Tag Data" tool. It only shows me tag data that I have already defined rather than all the possible tag attributes however.
I was able to determine that the tag attribute for area is actually AREAID so I am making some progress.
Marc, I'm just throwing words here (a diplomatic way of saying I've no clue what I'm talking about) but you may be able to get some information by looking at the schema of OPIM as I would imagine that would be where the interfacing between AutoPlant and OPIM happens. As a reference, the below thread was me asking about creating and mapping a custom property from OPM into OPIM:
It seems if there's a property for a component (PIPE or PIPING_NETWORK_SYSTEM as in my example) in the OPIM schema, you should be able to use it in node2da.txt mapping. Again, not sure if that's the case here, as I have no experience with AutoPlant.
Best regards,
Tuan Le
Answer Verified By: Marc Whitburn