Description This document will outline issues that are present in Native APPID application. These issues are carried over to OPPID during the conversion. OPPID tries to handle these issues in a manner which will not disrupt appearance and content. This being said some of these issue will persist. Tie-Ins APPID Ties-Ins were structured after Instrument bubbles, but the APPID native xdata stored in a Tie-In is incomplete. The leader line xdata is not present and the OPPID conversion compensates for this. When placing a Tie-In in APPID, the first point should be on a pipe run. After placing a Tie-In in APPID, the drag bubble does not work. If a drag bubble is performed, the old leader line is left in drawing and a new one is placed: potential issue with garbage data in APPID The Tie-In database information is not formatted and populated like other components. The Number and type are not populated (TIETYPE). There is no column for populating the Number value. For instance the INSTR table columns get populated with the tag parts (INUM,ITYP,INUM). The Tie-In only populates the Tag number. The conversion mapping explicitly does not map the Tag parts (number and type). Equipment Trim The conversion on APPID parametric equipment and trim conforms all the children into the main graphics. The Trim (insulation, Internals, packed, stacking…) do not have any intelligence, so that are grouped with the parametric equipment. When APPID equipment trim is added to parametric equipment, the xdata trim children are not added to the main xdata point. It is orphaned, that is, the xdata handle knows its parent, but the parent does not know about the child. This is why I do the scanning of drawing on conversion initialization. So this example shows the child handles that are on the main element. These do not contain all the elements that make up the parametric equipment and trim. As seen below, the orphaned child element is not part of the main parent collection of children. The Child element handles are the only elements that will be grouped with the conformed component. The fix gathers orphaned xdata which then can be applied to the conformed component. So in the list there will be a key with 792 and have a collection of handles, which will contain the element id 926. Orphaned Child element To determine a Equipment Parametric, the APPID type must be defined in EQUIPMENT_PARAMETRICS_LIST in AutoPLANT_PID_Conversion.01.07.ecschema.xml Schema list that indicates which Equipment keys are to be used as parametric containers. Key value is stored in EQUIP.EINT1 Valves In DIN mode, placing a float valve actually places a float control valve Control Valves In APPID every possible valve body could become a CV. That is actually incorrect. The ones that shouldn’t be allowed to be CVs are the ones we convert to generic CV. Conversion will cloud these, see APPID Cloud Warning.docx Non-symmetric angle CVs do not have intelligence on them, indicating flow. Therefore they are converted with the APPID placement orientation. Function Indicators These Function Indicators have unintelligent text and will only be conformed. So if an instrument bubble is moved these indicators will have to be moved manually. Boost S.P. Proportional Convert Derivative d/dt Inv Derivative I/D Nozzles on Equipment Vessel Heads When a nozzle is placed on equipment in APPID and AutoNozzle is on, two blocks are inserted: the Nozzle symbol and a Run Terminator symbol. The Nozzle symbol only has a grouping link to the equipment. The Run Terminator symbol has the intelligent link to the database and is considered a Nozzle. If the nozzle is placed on a vessel head, the Pipe Run line and the Run Terminator symbol do not intersect. This causes issues in the conversion due to the fact that the conversion uses intersection scanning to determine relationships and connections. OPPID requires this. Incorrect nozzle connection Correct nozzle connection To correct this in OPPID the Pipe run must be dragged off the nozzle and then back on to the nozzle.
↧