Hello MelissaR, Maybe this will help - the way PowerPIDs pipeline/pipe run is configured is based on the STEP/ISO standard from years back. This is basically that every PIPELINE is actually tagged component. A PIPELINE will start with a PIPE RUN as well. As this PIPELINE is routed to different components it wil have multiple RUNS within the same PIPELINE. They are all the same tag number but different RUN numbers. If you place a reducer in the line, this is a data change component and as such will create a new RUN with smaller or larger size. This new RUN is the same LINE tag. In a sense PIPELINE defines whats inside/flowing through the pipe. The different RUNS between a start and a terminus point may be different sizes but they all have the same media or Process flowing through them. In your case I see that when ever the RUN size changes this is a new number because you have SIZE as part of the PIPELINE tag. The way PowerPID is delivered today making every line a new number when size changes will cause you issues with the database. If you: Add a Pipeline that is 6". The associated RUN is also 6". What gets tagged and written to the database is the PIPELINE. The PIPE RUN gets written along too but only into a RUN table that links the run to the line. The RUN is NOT "Tagged". If you change the RUN size you are not updating the PIPELINE - remember the PIPELINE is the tagged component. In your case where you have every size change as a new PIPELINE then you need to draw the PID in that way. Draw the line from the page edge to the pump. If you have an auxilliary pump then you need to route a NEW PIPELINE from the existing line to the Auxilliary Pump. This way both PIPELINES are unique and tagged based on their size. The issue with this metod is when reducers are added. The line already exist as XXX-XXX-6" and now you add the reducer (6 x 4) the newly created run after the reducer is now 4" and based on your tagging it is a new PIPELINE. IN this case you have not added a new line you have only changed it. This si where the inconsistanciies start. So solve this issue Bentley is making changes to how datachange components behave. In an upcoming release of PowerPID a datachange component (Reducer, Spec Break, Relief Valve, etc.) will allow for a new TAG NUMBER (NAME) when the data change component is placed. This will better suit your way of defining pipelines. This was implemented for the Power and Water industries where this process of every run, based on size, is a new tag, is the norm. To be certain - make sure not to confuse PIPELINE TAG with PIPELINE ANNOTATION. Im sure you have this figured out but I want to make sure. A PIPELINE can be tagged one way and annotated any number of other ways based on the properties associated to it and its associated PIPE RUNS. I hope this helps, Tony DeRosa Bentley Plant
↧
