Can Graphisoft please add timeline status to all elements in Archicad?

[matjashka]

How hard would it be to add a "lifespan" property to all elements in Archicad, which would define when the element comes into existence and when it's being removed from the model?

This would enable having a flexible multi-phase project approach, where the display of an element like wall or window would also depend by the point in time when the plan "snapshot" is taken.

Now, some will say that this is already possible by simply using a combination of Layers, Properties and Graphic Overrides, but that combination unfortunately does not address complex interactions like presence of openings in a wall during a particular time span, which is otherwise addressed by Renovation Filter.

The Renovation filter already implements a narrow idea of was/is/will-be, but a TIME factor would allow for creating user-defined "milestones" (example: completion of construction phase), where each milestone would automatically recognize the timeline of a particular element, and be able to automatically assign a was/is/will-be status similar to Renovation.

Any View in the View Map would have an extra "Timeline" group of settings: when in time are we viewing the model, how far into the past, how far into the future, alongside Layer Combination, MVO, GO, etc.

It's been emphasized before that BIM should also factor the lifespan of a building, so what I'm proposing isn't totally out the official party line.

Well, I hope it makes sense.

[poco2013]

---

@matjashka wrote:

Just curious about how your Python script could be applied to a set of Construction Documents.

---

I assume, based on your request, it would just set the visibility of elements consistent with whatever phase or date you have applied to the elements. Then you would create a view (snapshot) and place that on the layout(s)  

[gdford]

Personally I think the approach should be similar to the way graphic overrides are set up..
I am currently working on a 3-phase project and I have resorted to layer sets and graphic overrides for each phase. It is a bit of a nightmare with all of the variables of existing conditions to remain and to demo during different phases, and the demo of new temporary phased work during different future phases. I keep getting the feeling the by using classifications and something like the graphic override system this process could be improved... I really think that if graphic overrides could control visibility then this sort of thing would be a piece of cake.
My vote would be that the best action Graphic could take to deal with this matter is to give graphic overrides the ability to control visibility.

[matjashka]

Gary,

The problem with things like overrides and layers is that they are logical means to organize and display information.

A timeline property actually adds information that can further be organized and displayed. In this context, graphic overrides won't really accomplish anything.

Typically, timelines have been a construction management problem but with multi-phase projects the "fourth dimension"=time becomes very real and much needed. Only then we can think how to use Overrides to illustrate this.

Cheers.

[gdford]

I disagree - If graphic overrides could control visibility of elements combined with the use of custom classifications to control the "Time" phases, and Properties to add the time data, I am certain I could put together a fairly sophisticated multi-phased set of plans that would let me build drawings and schedules to show anything that needs to be shown.
Please elaborate why this would not be the true.

The biggest issue is that annotation cannot be assigned classifications or properties so we are stuck again with layers to control the presentation of the data on the plan. Just an FYI, the introduction of the piss-poor renovation feature, as cool as it is, required the modification of an obscene amount of code. Graphisoft has no desire to add much more to that feature. They would be better off to scrape the existing engine, forgo backward compatibility and build a new product from scratch that is truly an accessible database engine. Someone is going to do this and they will capture the market from both revit and archicad .

[matjashka]

Gary,

You mentioned the visibility component as part of Overrides - well, an on/off switch would be convenient, BUT:

Overrides tweak how we see the model on a superficial level. Layers are more serious because they dictate both physical "presence" in the model AND interactions between elements both present and hidden. Overrides have nothing to do with presence.

My timeline idea is related to presence not visibility. Time not only dictates existence but also potentially a location of a particular element, which layers can't do and overrides should not.

We work on historic preservation projects where existing elements are being re-installed in new locations, and it's not hard to imagine that also new elements can change their location in next phase.

Of course, separation of presentation and model in archicad is a complete trainwreck (majority of support calls that I deal with are about confused presentation), and Overrides are like a final coat of paint to make up for that.

But _visibilty_ should not be confused with _presence_ in time and space, if that explains my position.