Greetings on this glorious day!
So, it's been busy as fuck over here. I didn't even realize I had passed the six month mark at my new job.
It's been incredible working with teams of engineers to take on projects of a scope and complexity I had never imagined being involved in before... and then there are the architects.
The last time I was doing electrical design work was for the Architectural/Engineering firm that took the Revit deep dive (and prompted me to start this blog) - and while structural and mechanical got on board, it was definitely the architects running the show (despite both the president and CEO of the company being engineers).
At my current firm, engineers reign supreme. Electrical, mechanical, chemical, etc. etc. - and it's the difference between night and day. There's still been a push by some of their clients to get a-bimmin, but it's been middle fingers all the way down... and (again) there are the architects.
We employ a small handful of these guys to handle the few times we need to be responsible for some aspect of a building/structure. One of them actually worked at that A&E firm, but he's one of the exceptions to the title of this post (plus he put in a good word for me when I was applying for this job - and the project I'm currently working on with him is 100% ACAD).
And then there are the jokers that were involved in this massive demolition project that I just finished.
We spent several weeks developing our set of isolation drawings, including on-site visits, rounds of comments, in-person discussions with the people running the project. The newest drawings they had ranged from 'old' to 'ancient' - and weren't exactly 'accurate'.
Throughout the course of the project, we basically had to design the entire system - which consisted of a large switchyard, towers, poles, anda few buildings (all with systems routed through the area that needed to be preserved - but which had never been identified or documented).
The *day* we were supposed to submit our final drawings, we happened to notice that the Architect(s) responsible for providing three lousy sheets of details (as compared to our set of nearly one hundred) had not taken into account several items that they needed to show on their drawings (and which they promised on multiple occasions would be addressed).
They had spent an inordinate amount of time modeling three buildings in Revit - two of which were being demolished (including one that they lovingly detailed out various tanks and supports that were also going bye bye) - but had left important details out. They were able to rush and slap a (terrible) looking set out, (while acting affronted that they had to do it).
Fast forward a couple of weeks, and our final deliverable was our 'Native Files' - but (because the client, a government entity, are idiots) needed to be in Microstation. Technically we were supposed to use it to develop the set, but everyone (Revitards included) were like 'fuck that!'.
Apparently my firm was used to exporting stuff out to Microstation (which I honestly don't know if the client ever actually looks at), but this project was unique, in that it had an inordinate amount of linked images and .pdfs - and as it turns out, Microstation ain't so great when it comes to preserving relative links, and falls directly down on its face depending on how the original files were developed (but, in its defense, it also does a terrible job of translating lineweights and other aspects of linework, hatching, etc.)
I was able to beat my set into shape, but it required reattaching dozens of files before exporting (mainly .pdfs - which it couldn't seem to bring over if they were in model space) and then fixing countless links that were still pointing to full paths (despite being relative in the .dwg.
I was able to export some directly from ACAD, but others I had to open in Microstation and then export (to itself). There was very little information online to assist me in this task (apparently some of the things I was doing manually could be automated with bits of code, etc. - but I was disinclined to figure it out - especially considering it's unlikely to come up, at least at this scale) in tbe future.
It has options for packaging files for transmittal, which is probably fine for files developed within Microstation, but I can guarantee the result would've been comical for imported files.
Anyway, I finally get mine ready, civil engineer gets his ready... and then there were the architects.
I get an email from one of them trying to pretend their files have been ready, despite not being in the folder they belonged in (then he asked where they needed to be - in response to the same email that informed everyone where to put their files).
Even after pointing this out, they continued to put their files in the wrong place - then I tried opening one of them - only to find out they hadn't even tried to fix their links. The guy was like 'it all shows up right to me', and I had to break it to him that it was because he has *access to our server*. It didn't even work on mine because his drives were mapped to different letters.
Attempting to fix his links, most were grayed out and incapable of being changed (possibly due to having been exported from Revit. I actually opened Revit, attached a .pdf and a .png, and was stunned to find out that 'absolute' is the only path option for both. Again, there is probably a way to package for transmittal from within Revit (but no help if you are exporting). What the fuck Revit?
He kept at it for a few days (having to be prompted to communicate his progress) and finally today he was able to show me his screen where the file comes up correctly, has proper links (but still won't open correctly on mine). I said 'fuck it' and we're just going to send it.
All of the files were included, so if the client has some. Microstation whiz kid, they can fuck with it.
As far as these architects, they can stick Revit up their asses. I've heard from co-workers that they share the same superiority complex that I've come to expect from the Revit crowd (and architects were bad enough already). On one project, they had shown a roof at the wrong level - when it was pointed out, the architect smarmily said 'oh - I can fix that in seconds.... in Revit'.
What he failed to understand was that his fuckup meant that several things that had been carefully coordinated were now fucked up as well. I've mentioned this 'bull in a chinashop' mentality that the simplicity with which someone can rearrange (necessarily or unnecessarily) things in Revit leads to people not stopping and asking whether or not they *should* make a change (or how they go about it).
Add to this, the fact that when you are working in Revit, it has no way of informing you that these changes are being made until the next time you save to central, and find out you just blew a whole morning because somebody decided to move things in such a way that 'the magic of Revit' didn't just automatically make everything work perfectly.
It's been amusing being back in this industry, and seeing that the Revit prophets that said everyone would be using it (or be out of a job) continue to be shown as hacks. Now, just as then, results are what matters - not software, not some 'mindset', not some 'club' for joiners to join - results.
And from what I've seen, and continue to see - the results you get from Revit (and its cheerleaders) are total, 100%, unadulterated, dogshit.
Fuck Revit.
That is all for now. If you don't like it - consume mass quantities of phallus.
-SF
Next time: Spec'ing Electrical Shit
