I have come to the conclusion that despite there being a phasing attribute in AECOSIM there is no scope to leverage this in the application other than as an output.
In the event that we have modelled an existing building it appears the only way to manage the removed and retained elements is to put them in sperate files. Does anyone else have a better way to do this?
Ironically I have tried using named groups to knock out existing to demolish but the space flood tool sees the walls that are in the existing to demolish named group, see image (the green area is a space flood). Annoying really... I know its been said before, but named groups would be great if they were properly integrated with AECOSIM.
I had understood that space floods were going to be improved to flood only on the plane identified, is there a timescale for this to happen - I thought it was meant to have been doen for AECOSIM.
Unknown said:Ironically I have tried using named groups to knock out existing to demolish
How are you doing this? Sounds interesting...
Simply put within the existing model you have element in an existing to be retained group and an existing to be demolished group. When you attach the file as a reference it is possible to attach a named group within a file. Sounds great until you realise that AECOSIM ignores the namedgroups.
R
I'll have a look thanks Travis.
No problem. Also note that these definition files can be overridden at the dataset or project level where you could add additional properties into the definition and have them magically appear in all catalogs with that definition associated with it.
-travis
Has there been some progress on this fasing-status field possibility for better control of drawings? Best Practice?
Travis this kind of fits to the other discussion we are having concerning level names..
Do I add more level names - ex. Demo, Exiting, etc.
Or do I Create for Parts Demo-Beam, Existing Bean new Beam
Or do I change the DG for each as needed.
It would seem this should be a policy decision: All options done work one solution that you can ignore does.
I would think the DG version is the correct way to go as it give DEMO, EXISTNG, NEW to all as needed without having to create 3 or 4 versions of virtually the same thing.
If I could tag all elemets as DEMO in Phasing and then in the extraction a Rule for Demo as to what symbology I would change. (Level, style, wt, color) then it would be golden.
I don't know that I need a toggle to ignore as I have reference files for that.
I can do most of this with reference files - the problem ahs been where parts unify or not across reference files.
Ustn since 1988SS4 - i7-3.45Ghz-16 Gb-250/1Tb/1Tb-Win8.1-64bEric D. MilbergerArchitect + Master Planner + BIMSenior Master Planner NASA - Marshall Space Flight CenterThe Milberger Architectural Group, llc
ABD / Mstn is going past CAD modeling and becoming an 'Information' modeling tool.... in many ways.
Mstn:
1. Level attribute: as a key to symbology i.e. transparency, priority, rendering materials etc. One to one mapping, with some flexibility using overrides and dgnlibs. > Demo_level
2. Element Templates: attribute attached to individual element as key to levels + symbology. Nesting > Demo_Element_Template
3. Tags: attribute attached to individual elements. Sets allow some heirarchal organisation. No immediate link to display system.
4. DB Links: attribute attached to individual elements. No immediate link to display system without vertical.
5. Named Groups: attribute attached to individual elements. Some display control; using Item Sets.
6. Items: Mstn EC schema... i-model transformer-type tool inside Mstn in future?
7. Rendering materials: oppportunity to assign/attach material as a proxy for other information.? Could deal nicely with exceptions or variations by using attachments.
8, Named Expressions?
ABD:
1. Family and Parts: attribute attached to individual element as key to levels + symbology... plus unifier parts, compound cell 2d resymbolisation, centrelines, cut resymbolisation, fill etc.
a. Definition b. symbology c. annotation d. structural data e. quantity reporting f. prices g. specification text h. analytical i. rendering .... Will compound walls be defined in the DGS some day?
2. DataGroup System: attribute attached to individual element as key to application and user defined attributes.
3. IFC/Cobie which uses both DGS + F+P... Could be used to produce i-model with the desired keys for filtering? Export with the Phasing attribute mapped to a level and cut your sections/drawings from the i-model?
4. ...?