Wednesday, 23 August 2017
  4 Replies
  2.4K Visits
0
Votes
Undo
  Subscribe
Hi there-

In our office, we use a symbol for the POC that refers to a standard detail that shows the tap into the mainline, the water meter, the backflow preventer, quick coupler, etc. The symbol appears in the schedule with the description "Point of connection" and a detail bug. Since we started using LandFX, we have achieved this through manual edits to LandFX blocks that are wildly inefficient.

Question 1: How do we change the block that is generated by default when you are in the source data menu and hit "place" so that it is wide enough to fit the letters "POC"?

Question 2: How do we change the data attached to this block so that the description in the schedule says "point of connection" instead of "water meter [size]"?

Question 3: Is it possible for the schedule to generate detail bugs instead of text in the detail column?
Accepted Answer
2
Votes
Undo
Katherine,

Currently, when the POC type is a Meter, the description and such will state it is a meter. The only way to get it say it is a POC, is to choose a Custom POC, and then manually enter the flow and pressure available.
You will still want the Backflow symbol as well, to calculate that loss, correct?

There's a number of ways to do what you are after. Here's one:
- from the Auxiliary category of "Other", add your preferred POC description
- Create a Work Area where the POC equipment is, and then assign it the scale of 1:1
- Placing your desired equipment within that work area, it will be *tiny*
- On the other side of that work area, place your "Other" POC at full size
- So visibly on the plan, the chain of equipment in your pump station are just nearly invisible dots
- The best part -- Cut a Viewport to look at that assembly of equipment, and there is your detail reference of the equipment

There is not a way to place a detail callout (bug) in the schedule, but I don't see why this would be necessary. You can always place a Detail Callout manually next to both the POC placement as well as the schedule.

--J
If it's not a typo. What is a detail bug?

Secondly: Why not just use the standard POC (Meter symbol and information) and then have another symbol for "POC Equipment" that includes all of your ancillary equipment which could include additional isolation valves, a backflow preventer, backflow preventer enclosure, a master valve ,air and water pressure relief valves, flow sensor (or meter), and as much other ancillary equipment that you may need?
6 years ago
·
#1392
0
Votes
Undo
A detail bug is the round symbol that indicates what number and page the detail is on.

Using two symbols could be a workable option if it's not possible to get LandFX to describe the symbol the way we want in the schedule (as in question 2 above). Is that impossible?
Accepted Answer
2
Votes
Undo
Katherine,

Currently, when the POC type is a Meter, the description and such will state it is a meter. The only way to get it say it is a POC, is to choose a Custom POC, and then manually enter the flow and pressure available.
You will still want the Backflow symbol as well, to calculate that loss, correct?

There's a number of ways to do what you are after. Here's one:
- from the Auxiliary category of "Other", add your preferred POC description
- Create a Work Area where the POC equipment is, and then assign it the scale of 1:1
- Placing your desired equipment within that work area, it will be *tiny*
- On the other side of that work area, place your "Other" POC at full size
- So visibly on the plan, the chain of equipment in your pump station are just nearly invisible dots
- The best part -- Cut a Viewport to look at that assembly of equipment, and there is your detail reference of the equipment

There is not a way to place a detail callout (bug) in the schedule, but I don't see why this would be necessary. You can always place a Detail Callout manually next to both the POC placement as well as the schedule.

--J
6 years ago
·
#1394
0
Votes
Undo
Brilliant! Thank you so much!
  • Page :
  • 1
There are no replies made for this post yet.