Friday, May 24, 2019

So High I Have To Look Down To See The Cloud

Shazbot!

I know it's probably a little silly to complain about web-based applications while using a web-based application that stores my information... someplace...  but for the last three days we've been unable to use the software that some genius determined was the best choice for managing all of our project/time tracking, billing, etc. thanks to an 'update' that has left the system completely non-functional.

We started receiving messages that the system would be down for 'maintenance' a while back, and sure enough, when the day came, it was down.  Then it was down the next day, and another.  Now, if this were a piece of software running on our server, maintained by our IT people, we would simply have drug them out from in front of their Linux boxes and told them to do their fucking jobs - or be beaten with blunt objects.

As it stands, someone, somewhere, with no vested interest in helping us (or preventing blunt force trauma to their faces) is dicking around, with god knows what, for god knows how long.  Attempts at contacting them resulted in the standard runaround - starting with 'we're getting it back up ASAP', to 'here - try this non-functional link that we tried to make as a workaround'.

They FINALLY get around to fixing whatever was keeping us from being able to log on, but they've apparently discontinued support for Microsoft Explorer (which I have no love for, but I liked have a dedicated browser shortcut that took me straight to the login.  No problem though - I just switched to using Edge (which I had avoided like the plague).

I even used an online icon maker to upload an image of the software companies logo and used it for the shortcut, so it's easy to find - but oh my god is it slower than shit now (same on Firefox and Chrome).  They made the interface a little prettier, which is probably part of the reason it's so fucking slow - but I was able to get everything done that I needed to.

Now I get to waste my time doing a more detailed version of a detail that I already have done (on a project that I could issue today as soon as I complete some calculations - but that will probably take at least another day).  Basically, we are showing a block diagram of all of the devices in the system on the circuits they are on (more or less just a duplicate of my floor plans - sans floor plans, and in a more orderly fashion).

What this client wants (and has gotten in the past) is a point-to-point wiring diagram showing every single goddamned wire connection to every single goddamned device in the building so that even an idiot could understand it.  Normally I'm all for idiot-proofing things, but in this particular case, if someone doesn't already know how to wire these devices, they have no business being anywhere the fuck near these kinds of systems.

I've probably mentioned it before - but in the past, when I was designing electrical distribution systems (and avoiding Revit like the plague) there was a certain amount of deference to what we called 'means and methods' on the part of the electricians who would install the systems I was designing.

The assumption was that the electrician already knew how to electrician, and didn't need their dick held for them.  Obviously, this wasn't always the case, but as long as we got our design intent across, and our specifications addressed all of the necessary situations, then they could go out and install everything based on their professional skills and knowledge.

Now.  There would still be the occasional project where some dickless fuck (often a Revit using dickless fuck) would get involved, couldn't grasp the concept of 'partially schematical drawings' and would start requiring us to provide unnecessary levels of detail (without, of course, paying the requisite fees for said unnecessary levels of detail).

For example - I would always coordinate with our civil engineering team to make sure my service entrance conduits/equipment were located in accordance with all local codes, did not interfere with other systems (such as water/sewer/drainage/etc.) and in most cases, the utility company and/or electricians would install it exactly as shown.

On the other hand - when showing wiring within the building, a schematic was sufficient to show circuits, switching, etc. - and the electrician was responsible for determining the best, neatest, and/or most efficient way to route conduits throughout the building.  Some people couldn't grasp the concept that if we did show all of our conduits - and they got out in the field and found that (for whatever reason) the conduit could not be run as shown, it would result in a costly change order.

Unfortunately, that wouldn't stop them from trying to suck us into the hell that mechanical engineers are forced to endure when it comes to showing systems like HVAC and plumbing that DO require extensive levels of detail and coordination in order for them to function - or that structural/architectural needed to show for their systems/buildings to be built properly.

Anyway, for this client, redundant levels of detail is what they do.  It wastes everyone's time - especially when they start making (typically unnecessary) changes and they have to flow through all of the layers of detail - so instead of taking five minutes to update a set of drawings, it will take several hours (and guarantee something will be missed).

Having it automated seems like it would be a dream come true - but in the whole time I was exposed to Revit, I never once saw someone design an 'automated' system that didn't break after even minor modifications were made to it (often at the very last second - resulting in a lot of manually filling out schedules, sketching things in 2d, or otherwise 'faking it in' out of desperation.

As always, the problem tended to be that the claims made by the software 'developer' about their program's ability to be fluid enough to handle changes were undermined by the fact that they could not predict the kinds of changes that would be made - often way beyond the time that major changes should be being made, which would cause problems for anyone, regardless of what software they were using - but which were exacerbated by the fact that everything was so relentlessly interlocked.

Demonstrations would show how adjustments could be made, and other things would 'magically' update - but these were obviously very carefully orchestrated and tested 'cut scenes' rather than reflecting the 'in game' reality (to borrow a gaming metaphor).  In reality, these interlocking systems are delicate, temperamental, and rarely (if ever) respond well to random changes.

It's one of the reasons why it's difficult for someone who doesn't have experience to design and modify these types of systems as they evolve - because a seemingly minor change to a floor plan can actually have catastrophic effects on the design of other systems.  I would always joke that if they moved (or deleted) a wall - it was going to be the linchpin of the entire fucking design.

While I might be able to salvage most of the layout, I would have to make decisions based on what was going to be the fastest fix, rather than what would've been the best choice if the changes to the layout had been made prior to me starting my design.  For example, the project I am wasting my time detailing out consists of two quonset hut style buildings - one is a 90K s.f. building (768' long), while the other is about half the size.

We designed both, but it turned out that the first one had been being constructed, and conduits/junction boxes had already been installed (much of it in-slab), based on an inferior design from someone who obviously had zero experience designing these types of systems - so we had to go back and modify our design, resulting in it being retarded and inefficient - and if I had designed it in Revit, I would be FUCKED.

Instead, it only took a few hours of thought and sketching in CAD to give the salesman something to take back out and review on-site, get approval, and then a few more hours to complete (with the exception of the stupid point-to-point connection diagram - but even that will only take a little while). 

Relentlessly,

-kullfuckS

P.S. - I just read last night about Autodesks dismal quarterly earnings.  The first article I read was trying to downplay it, but the next laid it bare.  As always - Fuck 'em.

Next Time: The Derpth Annual Revderps Award

No comments:

Post a Comment