Jump to content

gester

Member
  • Posts

    655
  • Joined

  • Last visited

Everything posted by gester

  1. i'd rather edit the mapping from the pull-down menu in the oip, the ifc pset value would be the result. but it's just my view, it'd be a question to the programmers. from my perspective the architects are not willing to go too deep into the parameters, so the oip window would be a more obvious location. rob
  2. btw, the whole direction of 4d is going to use ifc entities for the process analysis (ifcworkschedule, ifcworktask, ifcrelsequence a.s.o.). the 5d future is also connected with the likes of ifccostitem and ifccostschedule. we will _have_ to use ifc for the construction processes...
  3. you mean the psets for classification, classification 2 and 3? i think we have to specify the assignment much earlier, along with the classing system mapping. and i don't agree that we don't need it. sooner or later the construction site will require the linking of the models and their parts to physical objects (that is, if the latter ones are a part of the classification system, too). rob
  4. ifc reimport is the silliest idea to deal with the ifc format. ifc is for reference only. rob
  5. before ifc may be used as an ubiquitous communication format there should be: 1) a common language for the bom (building object models) parameters throughout the whole process, enabling passing the information from the designers to the builders and giving the feedback back to the computers and bim authoring tools 2) an understanding, that native formats are not a good way to give information on somebody's own work, because the working on the same model by everybody is not likely to come (copy rights, professional insurance, a base for liability waivers in case of ipd contracts, security to use the outcome for decades etc., let alone the freedom to use any software tool any party may choose) frog, you've addresses the second issue, but we're dealing here with the first one. besides, the germans seem to wait for the norms and standards first, then to use them in a qualified process. rob
  6. imho the best strategy would be to port vw on ios. such ipad pro it's only some 0.7 kg weight and still an almost 13" display with a9 processor. the newest windows-based pcs have a touch screen already. a mouse will disappear in the long run. and back to the topic: i've operated vw on my 13" mbpro even without retina for some years. but you have to have good eyes, jim is right. rob
  7. i've thought about it once again, and i don't think that we should mess up with uniclass strings in the table entries' names. imho way better would be to set up some user-friendly names for the classing system (like 'door-interior' or the likes) and to make either a button, or a pull-down menu in the class dialog to make a link to the proper uniclass name (which consists mostly of digits)... what do you guys think? rob
  8. @rdesign i know this paper (actually a great description of the storeys' levels), but it's not about the classing system in general in vw. if you want to implement some national construction naming convention then you have to do it with a specific classing system. to be frank the most clear one for me is the us-imperial system in vw (like 'wall-exterior-insulation' a.s.o.), but it contains no coding appearance whatsoever. that's why the initial question in this thread is justified. rob
  9. i second this question, can somebody comment on this? rob
  10. christiaan, what are the integration actions on the uk market for the vectorworks app? this will be imho required for the data mapping in the real world between the computer standards (ifc, or native ones for the time being) and the building site classification (uniclass 2015, as for the uk), right? you use the int'l (us) version with all the gsa (omniclass) legacy, or do you have your own localization? rob
  11. there is already an omniclass module for gsa space occupation classification in vectorworks, and the uniclass reference for pricing. and probably there are many more links. actually in poland there is no compatible construction classification, so if we adopt uniclass (2015, yes, christiaan ) for our construction industry, and for polish vw localisation (which is just about to appear), then the classing structure according to uniclass namings would serve us well... rob
  12. omniclass is an american system. in the uk there is uniclass2, in benelux they use either stabu or older sfb, a.s.o. all those classifications do work in the national construction industries on the building site elements' naming level, but only a few of them are compatible with buildingsmart standards for digital data mapping. those standards include the format (ifc), process protocol (idm), and the dictionary (bsdd, being both mapping matrix and the browser - a development by the catenda company from norway). the best compatibility is provided by omniclass and uniclass2. rob
  13. it's exactly what i'm thinking, all 3 points matching, thanks rob
  14. and how about exported and imported resources? this is the first thought that came to my mind... rob
  15. hi diamond, why would you want to edit the consultants' contribution? isn't it their kettle of fish? i model the representation of the geometry, and then the consultants use it as a reference for their job. what they export is the model (preferably ifc) that contains objects that have special rules and behaviours. if i convert them to vectorworks native rules and behaviour then the information intelligence gets lost, in spite of convenient 3d geometry, which is only one of the bim dimensions, by far not the most important one, if you're doing a full-fledged bim / ipd. well, it's not the vectorworks goal to collect all the branch models into a federated one. for this there is a bunch of bim management software packages (solibri model checker, tekla bimsight, navisworks, bim vision a.s.o.). again, in case you're in for bim / ipd. if you're doing small bim, then you're maybe right, then no rules apply. i've just assumed you're mentioning the architectural objects to be imported, it might then make sense. on the other hand, it's suppliers' and manufacturers' responsibility for the accuracy of the shop models that will be inserted into a federated model in a lod500 status (again, preferably in ifc format), to be calculated and simulated by bim evaluation software packages (costx, bimestimate, ecodomus, simplebim, ies ve etc.). from the bim objects' libraries bimobject.org are just creating a vectorworks interface, and from what i know they will convert all existing models and objects in their library into vwx format, too. i regard it as a temporary situation, though. in the end we'll be dealing exclusively with ifc data, and maybe then with something more sophisticated. bim level 3 assumes a unified ifc federated model where all contributions are parts in their own rights, not editable, and with very accurate more-dimensional information from every project stakeholder's expertise field. i can't imagine how other process' participants may mess around with parts of work they have no authorisation for nor knowledge of. rob
  16. no. ifc means a non-editable feature, no matter how do you mean it. please read more about the format. rob
  17. no party is authorised to change the other party's contribution, so ifc goes with this flow. there are copy rights and professional liabilities, even the subcontractors that contribute their shop models are responsible for them, even if done by other 3rd party subjects. ifc is designed to work only in one direction (not as round-tripped exchange), and used as a reference for others to do their work. what you write is a compete misunderstanding of the notion of ifc. and: the ability of dwg to be changed was its major flaw. rob
  18. 1. the full information is in the model. if the information is missing, then it lays on the modellers. ifc is able to transport what ever the other party needs. 2. editing ifc is pure bs, it isn't, and it will never be. check the specification of ifc4 and the strategy papers of your fellow countryman thomas liebich. ifc is not to be edited ! of course, you could edit its parts, as it's a text format, but it will always be on your own personal responsibility. rob edit: the archicad's ability to transform ifc into native objects while importing into the application is 'vergebliche muehe'. do you want, say, a structural engineer, or maybe even a construction bim manager to manipulate architectural or mechanical objects ????
  19. the classes structure aims at mirroring the construction national standards, anyway. what do you use for this? omniclass naming? this is not how it was supposed to be done. there's no round tripping of the ifc models ! it's just a reference for others to work with. otherwise we'd have editable ifc elements and a whole bunch of copy rights and professional insurance issues with them. rob
  20. i wouldn't do it. it's stacking up old (possible) misbehaviours. i'd model it a-new instead... rob
  21. yes, slanted walls are a must. the competitors have them already... rob
  22. another vw unique feature is for me macrobim solely in one application, from the first sketch to the initial calculations, including the site model, and concept renderings for functional-utility purposes. the best thing in it is the ability to continue the work on the project saturation, and even go back to redesign the concept. rob
  23. the class/layer system seems to be so unique that the new austrian norm (oen a 6241-1), being a preparation for the future bim norm sports the implementation of the layers alone as the main distribution channel for the elements that will be bim objects. the guys in austria don't seem to take into consideration other applications than revit, archicad or allplan, let alone the ubiquitous autocad. hopefully the coming bim norm (oen a 6241-2) which will be based on ifc and bsdd (ibim) will make this legacy obsolete.
  24. my el capitan update freezes completely, short before the login screen, no matter if i repair it or install a-new with time machine backup (there's already el cap). if i don't find any workaround, i'd have to wait for the patch 2. fortunately it's not my only computer, but one of the older ones (mid 2010).
×
×
  • Create New...