Autoplant LDT - Line Designation Table

[Aplant Monkey]

Has anyone been able to produce a valid LDT with this program. We can get it to run a line list but it won't allow us to show the To's and From's which pretty much renders this product useless.

Any help would be appreciated.

[dave]

What do you run your reports out of? Canned SP software (AP data manager) or crystal reports?

[Aplant Monkey]

Smart Plant runs all reports right in Excel. It reports everything in .xls format

[dave]

And are those dumb reports? Is there any canned templated reporting functionality?

[Aplant Monkey]

They are not entirely "dumb" you actually have quite a bit of flexibilty. There are background Macros running, you can also set up SQL queries to run and report out to .xls The standard templates are included with the package. but having said that they all needed tonnes of customization which is fairly heavy in it's process. We are still trying to get the LDT right. Intergraph created this LDT that does not report To's and From's. All must be inputted manually at first then you run some macro that updates as necessary. Really doens't work though.

[dave]

Is the to/from data tracked to begin with?
Does it report the data after you fill it out manually?

Sounds like AP inst. datasheets? Linked cels and all that...?

[Aplant Monkey]

It is not even tracked to begin with. I believe there is some mechanism that will allow it but the functionality is not there yet. Once you manually enter the T/F's the macro is "supposed" to update it..... ya right.This is only one of many problems associated with this program. Live happy while you work with AP even with all of its problems. :P

[dave]

"happy" he says...

[tim]

You have to lean Llama (Logical Model Automation) to Get To/From information of each PipeRun.

[Aplant Monkey]

what the heck is that?

it even sounds crazy. which the way intergraph works would not surprise me.

can you help me out with this?

[tim]

This is quote from Intergraph's Automation Course Labs. If you want to know c) Solution. Pay Intergraph! AAAHHHHH!!!! That's the way of Intergraph!!



40. IDENTIFY ITEMS CONNECTED TO A PIPERUN
a) Purpose
To traverse the relationships from LMConnector to LMSymbol
b) Problem Statement
Place a piperun between two nozzles and place two valves on it. Populate the ItemTag of the piperun with a value (eg. unit1100-GCD). Retrieve the piperun by filtering for the piperun’s ItemTag. Identify all of the items connected to the ends of the connectors of the piperun.

[dave]

monkey, specifically what data are you trying to get out of the line list?

[Aplant Monkey]

a simple to and from would be nice without having to manually input the thing. IG has come out with a macro to do it but it sucks. branch lines have become a problem as well. the main thing is to get a valid to and from list, after all that is what a LDT is for

[louchesse]

We had to completely rewrite the code for the LDT to work with from and tos...

[dave]

we rewrote a lot of it but still use the same basic framework. Did you guys start from scratch?

[louchesse]

no we used the template that came with the package and edited it.

[dave]

Yeah I think that's how a lot of people do it. I've no idea why they released it double stacked like they did.

About your to/from, did you guys find a way around the way the lines are reported? For example - say you have a process line (001) with process line (002) T's into it in the middle. You have caps at both ends of 001. The report will report on 001 - From Cap1 to 002 - next line (same row) - From 002 to Cap2.

It should read: From Cap1 to Cap2

Have you found a work around for this?

[dave]

we found a work around by identifying if the connector was a branch. If it is then it is skipped.