Description This document details Pipeline and Pipe Run mapping extras. All Pipelines and Pipe Runs that are converted are actually redrawn. This is done to get a fully robust line; inline breaks, handle manipulation and angle breaks. When this is done, the Pipeline graphics are drawn from schema values. The schema mapping compensate for this. Process line class priority In APPID the Pipeline class name is stored in the PIPE_RUN.PINIT1 column. There could be multiple Pipe Runs with multiple Pipeline class names (MAJOR,MINOR,...) that belong to one Pipeline. This custom attribute can be set to determine which conversion class to use. 1 is the TOP priority. PIPE_RUN KEYTAG LINE_ID PINT1 0000000702 0000000701 MAJOR 0000000706 0000000705 MAJOR 0000000712 0000000701 MINOR 0000000715 0000000705 MINOR 0000000724 0000000705 MAJOR As seen in table above the process keytag of 000000701 has two PINT1 values MAJOR and MINOR. These are two pipe runs. The conversion needs to know which APPID class to use. In this use case it would use MAJOR. The ORDER value below for the MAJOR class is 1 which is top priority. The MINOR class ORDER value is 2. So the class with 1 is would be used APPID_CLASSES MAJOR_PIPELINE PIPELINE_MAPPING 1 APPID_CLASSES MINOR_PIPELINE PIPELINE_MAPPING 2 Mapping Pipe run Level to Element Template Map the level/layer from an APPID Pipe run to an Element OPPID Template, this allows the display to stay the same (as close as possible). These mappings are stored in the “PipeRun_Level_Template_Mapping” class. To create a mapping, find the APPID Pipe run layer. This value would be on the polyline entity in AutoCAD. Take that value in enter it in the Level node. In OPPID find a matching existing Element Template or create a new Template. These templates are stored in PIDProjectTemplates.dgnlib. Level APPID Layer ElementTemplate OPPID Element template (with level defined) PROPERTY_MAPPING MAJOR Piping\Pipeline\Major_Pipeline MINOR Piping\Pipeline\Minor_Pipeline MAJOR-NW Piping\Pipeline\Major_Pipeline MAJOR-EX Piping\Pipeline\Existing_Major_Pipeline MINOR-NW Piping\Pipeline\Minor_Pipeline MINOR-EX Piping\Pipeline\Existing_Minor_Pipeline APPID Pipeline and Pipe Runs In APPID a Pipe Runs can be drawn without a Pipeline parent. When converted to OPPID, these Pipe Runs will also not have a Pipeline parent. Below is the list of APPID Piping lines. Pipe runs types with a Pipeline MAJOR EXISTMA NEWMAJ Pipe runs types without a Pipeline MINOR EXISTMI NEWMIN Nominal Size Values and Reducers There could be issues with reducer sizes updating. This could be caused by the PIPE_RUN.NOM_DIAMETER being empty in the project data. If Sync is done DB->DGN, this value will be written from the database (NOM_DIAMETER) to the drawing (NOMINAL_DIAMETER). If the NOM_DIAMETER is empty, the reducer values will not be updated. Convert a drawing with a pipeline and a reducer Open the Project database Go to the PIPE_RUN table Examine the NOM_DIAMETER Go Back to OPPID Sync DB->DGN If PIPE_RUN.NOM_DIAMETER is empty then NOMINAL_DIAMETER property will be empty Issues with updating the reducer size will occur. Fixing the reducer size issue Open the PIPE_RUN table Enter a values in the NOM_DIAMETER field These values must match the PSZ value in decimal form ¼” = 0.25 1 = 1 2 1/2” = 2.25 See the IMPERIAL_PIPE_SIZES or METRIC_PIPE_SIZES for all the values. Open DGN Sync DB->DGN
↧