Blog

  • Archibus Software: My Hands-On Story

    I’ve lived with Archibus for four years across two companies (I even wrote up a full, hands-on breakdown right here). Office moves, lease audits, floods in the basement—yep, all of it. I ran Space, Maintenance, and a slice of Lease. I also used the mobile app during snow days, which was a whole thing. Let me explain.

    Where I used Archibus (and why)

    My last team managed three office towers, two labs, and a warehouse. About 2,100 people total. We needed one place to track space, seats, repairs, and leases. Email and spreadsheets kept breaking. People sat in the wrong spots. Work orders got lost. The fire marshal yelled once. So, we chose Archibus by Eptura. For readers wanting the source straight from the vendor, the official Archibus site lays out the modules and deployment options in detail.

    Setup week: the CAD mess I still remember

    We kicked off by loading floor plans from AutoCAD. The polylines were messy. Some rooms weren’t closed. One floor had two “Room 534” labels. Archibus, to its credit, caught the errors. But I spent a long Friday night fixing those lines, sipping cold brew. I learned to keep layers clean and names simple. It saved me later when we ran chargebacks.

    We set up SSO with Azure AD, and that went fine. The tricky part? Roles. The “Craftsperson” role threw folks. Techs got confused by the naming. We tweaked labels to “Technician” for them. Small win, big sigh of relief.

    Daily life: what clicked

    • Space: I could drag seats on the floor plan and assign people fast. It felt a bit old-school at first, but it worked. I liked the color themes—by team, by floor, by building code. Clear and calm.
    • Maintenance: We set rules so tickets hit the right shop. HVAC jobs went to HVAC, not carpentry. We tracked response and fix time. We used parts lists, too. Stock counts stopped being a guessing game.
    • Lease: Date alerts saved us. Clauses and rent steps sat in one place. I could see which suite had a weird load factor. And yes, it caught one rent error in Q3 that paid for a chunk of our license.

    If you're curious how other CAFM platforms stacked up over twelve months of use, I captured the practical wins and misses in a separate write-up you can skim here.

    You know what? The little things stood out. Like clicking a room and seeing who sat there, what team, and who had special gear. Simple, but it helped, a lot.

    Moments it actually saved my bacon

    • The 142-person shuffle: We did three move waves in six weeks. I built seating plans with distance rules (this was during the return-to-office push). HR kept changing headcounts. Archibus let me push new layouts and send move lists fast. No one lost their monitor. Well, one person did—but that was on the cart, not the software.
    • The flood on P1: A pipe burst in the garage. We marked the zone red, created 18 urgent work orders, and tracked parts and outside vendor costs. Insurance asked for proof. We printed the log and photos from the mobile app. Claim approved. I slept that night.
    • The lease clause hunt: Our finance lead needed a co-tenancy clause by noon. I searched, tagged it, and exported a PDF. That used to take me two days.

    Things that bugged me (and I told our rep)

    • The UI looks mixed. Some screens feel modern. Others feel like they came from 2013. It works, but it could look cleaner.
    • Queries get tricky fast. If you want a nice custom report, learn some SQL or bring in a partner. I got by, but I did grumble.
    • Permissions are too deep. I love control, but I clicked through six screens once just to fix one role. Felt silly.
    • Mobile offline is okay, not great. In the garage, sync lag hit us. Techs got double tickets once. We added a quick check step to avoid it.
    • It’s not cheap. It saved us money, yes. Still, small sites may feel the cost. Be clear on modules you need.

    If you’re after a third-party opinion before diving in, the detailed Archibus review on Research.com summarizes strengths, limitations, and pricing considerations.

    For shops where regulatory change control is front and center, I tested a management-of-change platform and wrote my real take here; it highlights a few gaps Archibus doesn't try to fill.

    Real results we saw (plain and simple)

    • Open work orders fell from 312 to 97 in 60 days after we cleaned routing and SLAs.
    • Average response time for urgent calls dropped from 3 hours to 1 hour, 12 minutes.
    • Seat use went from about 68% to 82% across two towers in Q2, after we fixed seating rules and closed ghost seats.
    • We caught a rent overcharge of $14,600 from a bad factor on one lease. The audit came straight from Archibus.

    Not magic. Just steady tools and a team that cared.

    Reports that helped me stay sane

    • Space chargebacks by cost center. No more hallway debates.
    • Tech performance over 30/60/90 days. I used a simple chart. No finger-pointing, just trends.
    • CapEx punch list with photos. Our project manager loved it.
    • Fire life safety roster by room. The marshal didn’t yell again.

    What surprised me

    The move tools are stronger than they look. I could plan a big shuffle, hold a draft, and share it with managers in a view-only way. People fought less because they saw the plan. Also, the lease area rules are strict, and I’m glad. It stopped messy math.

    Who I think should use it

    • Great for: Multi-site teams, busy campuses, labs, any group with a lot of seats, work orders, or lease terms to track.
    • Maybe not: A small office with one floor and a handyman. You might be fine with a light tool.

    If you're still surveying the market, check out the comparison guides over at Qusoft for a clear view of features and costs. And when you're ready to publish your own findings or boost visibility for a facilities blog, consider tapping a focused SEO playbook from 10xseo where you'll find actionable checklists, keyword research templates, and site-audit tips to help those case studies rank higher. Another shortcut I found valuable was attending a rapid-fire showcase—picture a row of five-minute demos from competing workplace-tech vendors. The Speed Dating Summit packs all those bite-sized sessions into one event, so you can leave with a vetted shortlist and zero long-winded sales pitches.

    Quick tips from my notebook

    • Clean your CAD. Close your polylines. Label rooms like a human would.
    • Keep roles simple. Rename labels your techs don’t like.
    • Start with fewer modules. Nail Space and Maintenance first. Add more later.
    • Pick three KPIs and stick with them. For us: response time, seat use, and overdue work orders.
    • Train one champion per site. Lunch-and-learn works. I used pizza and one silly trivia question to keep folks awake.

    Final take

    Archibus is not cute. It’s a sturdy toolbox. When we set it up right, it paid off—time saved, fewer fires, cleaner audits. Some screens feel old, and custom reports can be a bear. But when the pipe bursts or the VP wants a move plan by Friday, I trust it.

    Would I use it again? Yes. I already have my CAD layer checklist ready. And a fresh cold brew, just in case.

  • Pool 2D Drafting Software: What I Actually Use, Day In and Day Out

    I’m Kayla. I design pools. I also fix plans when crews call me from a hot backyard at 3 p.m. So yes, I live in 2D drawings. They get permits. They guide crews. They save me from “Wait, where does the spa spill?” calls.

    Quick note: if you ever want the stripped-down cheat sheet of programs and why I lean on each one, I stashed it in this overview of pool 2D drafting software I actually use—bookmark it for reference.

    You know what? Pretty pictures sell. But clean 2D plans build the pool.

    The quick gist

    • I used AutoCAD LT, ArcSite on iPad, SmartDraw, SketchUp + LayOut, and Vip3D plan sets.
    • I’ll share real jobs, what worked, what didn’t, and who each one suits.

    Why 2D still matters

    Inspectors want clear line types. Crews want callouts they can see in sun glare. Owners want scale. A simple 1/8" = 1'-0" plan still runs a project. It’s not cute. But it’s solid.

    What I used this year

    • AutoCAD LT (PC)
    • ArcSite (iPad)
    • SmartDraw (PC/Mac)
    • SketchUp Pro + LayOut (PC/Mac)
    • Vip3D plan sets by Structure Studios (PC)

    AutoCAD LT: rock solid, a little stiff

    I did a 16' x 32' rectangle with a 7' x 7' raised spa in Plano. The lot had a 5' utility easement. I set paper space to 1/8" = 1'-0", made layers (beam, waterline, coping, steel, gas, electric), and used blocks for skimmers and lights. My Bosch laser gave me the lot line swing. I traced it clean.

    Pros? It’s exact. Offsets and fillets hit right. The plan printed sharp at 24" x 36". The city permit tech smiled. That was a good day.

    Cons? It’s slow to learn. No field notes baked in. No quick material takeoff. And it’s not cheap. Still, when I need to show a 2% deck slope and a 12" raised beam with steps, it hits. If you’re weighing whether the full AutoCAD license is worth it, this in-depth comparison of AutoCAD and AutoCAD LT breaks down exactly where the productivity gaps show up.

    Side note: if you’re comparing price tags, the leaner cousin gets a full rundown in my no-nonsense Cadlink review.

    A small thing: I set water lines to blue. My crew says they can spot it fast, even with dust and sweat on the page.


    ArcSite on iPad: fast in the yard

    I used ArcSite for a freeform pool in Austin… July heat, shade was a joke. I traced a satellite photo, snapped to scale, and drew the pool shell with Apple Pencil. I dropped symbols for skimmers, returns, and lights. I added a gas run around the house with a simple line type. Then I shared the PDF with the builder while he was still measuring the set-back. That speed felt great.

    Good stuff: It works on site. It snaps to scale. My notes look like I wrote them, because I did. It also makes a quick quote.

    Not-so-good: Hatch fills can get chunky. Line weights can look heavy when you print big sheets. The curve tools are fine, but not as crisp as CAD arcs. And, again, it’s not cheap. For a deeper dive into where it shines (and where it stumbles), check out this comprehensive ArcSite review that gathers real-world user feedback.

    Still, when the homeowner wants to see where the tanning ledge hits the oak tree roots, I can show that right there on the driveway.


    SmartDraw: quick HOA sketches

    For a basic 30' freeform with a small Baja shelf, I used SmartDraw to make an HOA plan. It took me 20 minutes. The pool shapes library was handy. I added a north arrow, scale bar, and set back lines.

    Great for simple approvals. Not great for permits. The scale is “fine,” but line weight control is limited. Layers feel thin. I wouldn’t mark plumbing on it. But when the HOA wants a one-page plan with a few labels? It does the job.


    SketchUp + LayOut: the hybrid that grows on you

    This is my “I need sections” setup. I modeled a raised beam with two spillways, then sent views to LayOut. I made a clean plan, a wall section (beam, cap, tile, steel), and a little equipment pad view. All on one sheet. The inspector asked about weep holes. The detail showed them. We passed.

    For an alternate route in the 3D-to-2D world, my long-night verdict on Rhino 3D might help you decide whether NURBS belong in your own workflow.

    It takes some setup: layers, styles, and tags. And you must draw neat in SketchUp or your dims get off. But once the template is dialed in, the pages pop out clean.


    Vip3D plan sets: 3D to very clean 2D

    I do most 3D sales work in Vip3D. The “Construction” tools let me spin out plan sheets fast. I build the pool in 3D, then add page sets: layout, steel, plumbing, lights, equipment, and details. The hatch patterns for steel are clear. The callouts stick to the objects, which saves time. I exported a 24" x 36" set for a job in Frisco with a slot-over spillway. The spa section looked crisp. The tile line matched the step rises. The crew liked it.

    Limits? You need Windows. You also live in their text styles. It’s flexible, but not full CAD. Pricey too. But for a pool firm that sells and builds, the flow is smooth.


    Little lessons that saved me

    • Keep layers simple: beam, steel, tile, water, deck, gas, electric, lights, notes.
    • Use one scale per sheet. I use 1/8" = 1'-0" for most yards. Tight yards get 3/16".
    • Add a north arrow and a benchmark note. “Top of beam = +0'–0" at patio door.”
    • Put code notes in plain words. “Dual drains, VGB covers, 3' min between suction points.”
    • Blocks and symbols matter: skimmer, main drain, returns, vac line, autofill, handrail. Save your set and reuse it.
    • Colors help in the field. Blue for water. Red for electric. Green for gas. Grey for steel. Keep it steady across jobs.

    If you ever end up scaling these habits into full-blown facility management, my hands-on Archibus story shows how those same layer tricks hold up in a much bigger sandbox.

    Also, label the equipment pad like you mean it. Pump, filter, heater, sanitizer, check valves, unions. If I skip a label, that’s the one the plumber calls about.


    Real job snapshots

    • Plano rectangle + raised spa (AutoCAD LT): Full plan set in 4 hours. Two revisions for a side yard easement. Passed permit on first try.
    • Austin freeform with tanning ledge (ArcSite): On-site layout in 35 minutes. Marked live oak critical root zone. Saved a redesign.
    • Suburban HOA one-pager (SmartDraw): 20 minutes. Approved. We did the real permit set later.
    • Sloped lot with 12" beam step and weep holes (SketchUp + LayOut): Clear section saved a messy phone call. Tile guy texted me “Thanks.”
    • Frisco modern pool with slot spill (Vip3D plan sets): Clean pages, easy steel hatch. Foreman pinned it on the fence. No guesswork.

    Pros and Cons, the short list

    AutoCAD LT

    • Pros: Precise, prints sharp, trusted by cities.
    • Cons: Slower to learn, no field-first tools, cost.

    ArcSite (iPad)

    • Pros: Fast on site, Apple Pencil feels natural, easy share.
    • Cons: Heavy line weights at scale, curve tools so-so, cost.

    SmartDraw

    • Pros: Very quick, good for HOA and simple layouts.
    • Cons: Weak layers, limited line control, not for full permits.

    SketchUp + LayOut

    • Pros: Great details and sections, strong sheet control.
    • Cons: Setup time, must model clean, can get fussy.

    Vip3D plan sets

    • Pros: Fast from 3D to 2D, clear hatches, linked callouts.
    • Cons: Windows only, style limits, cost.

    So which one should you use?

    • Builder who needs crisp permits and tight dims? AutoCAD LT or Vip3D.
    • Sales or design in the yard with a tablet? ArcSite.
    • HOA
  • I wore the “corporate software inspector” hat for real: my hands-on take

    I’m Kayla. If you want the extended backstory, I wrote a full breakdown over here. I work in security for a mid-size company with about 2,000 laptops and desktops. I’ve used Secunia/Flexera Corporate Software Inspector (folks call it CSI) for patching the messy stuff—Chrome, Java, VLC, Adobe Reader, and all those odd little tools we forget. I lived in it for two years. I fixed things at 2 a.m. with it. I also grumbled at it. So here’s my plain take.

    If you haven’t crossed paths with the product before, Flexera’s Corporate Software Inspector (CSI) is a comprehensive vulnerability and patch management solution (resources.flexera.com) that stretches across Windows, macOS, and even Red Hat Enterprise Linux. By leveraging verified vulnerability intelligence from Secunia Research, CSI assesses more than 20,000 applications and feeds you pre-tested patch packages while sliding neatly into Microsoft System Center or WSUS for deployment (esecurityplanet.com).

    What this thing does, in simple words

    It scans your machines and tells you what software is old or risky. Then it helps you push patches. It plugs into WSUS and SCCM, so you can send updates right from your patch tools. The goal is less time hunting, more time fixing. Sounds nice, right? Most days, it is.

    Real moments from my week-to-week

    • The Chrome scramble: One morning, a big Chrome bug hit the news. CSI flagged 1,327 machines at risk. I pulled the ready-made Chrome package, tested on my “pilot ring” of 25 users, and pushed to the rest over lunch. Success rate hit 97% on the first pass. The misses? Chrome was still open. I added a little pre-script to close chrome.exe and set a post-reboot. Second pass cleaned up the rest.

    • Sneaky Java in finance: CSI found an old Java 8 in our finance group. I didn’t even know they still needed it. Turns out, one old report tool did. We made a rule to keep that exact build on those six PCs, but patched Java everywhere else. We logged the risk. We warned the team. No drama, no finger-pointing. Just facts and a plan.

    • VLC herd cleanup: A summer audit showed random VLC versions across remote staff. CSI’s agent saw laptops that lived off VPN, which helped a lot. We used the silent installer it gave us. Over three nights, we brought 400 machines to the same version. I slept better after that. I’m not kidding. (That audit felt a lot like the lab inspections I described in my QMS war story.)

    • Tiny but real: CSI caught a portable Putty exe on a field tech’s USB stick. That find started a talk about portable apps. We added a rule. We blocked repeat hits. One small catch, big ripple.

    • Noise in the call center: Back when I managed support teams, I learned through hard knocks (full story here) that agents love to park on apps all day. That lesson is why I now close Chrome pre-patch without mercy.

    The good stuff I leaned on

    • Clear risk view: It ranks issues by risk and shows what’s missing. I could brief execs with one page. No fluff. No panic.

    • Patch packages that save time: It gave me ready setups for big vendors. I liked the silent switches. I liked that I could copy and tweak. Then ship them through SCCM without starting from scratch.

    • Rings and rules: I set pilot groups, then phased rollouts. I used time windows, reboots, and pre/post scripts. It felt like steady cruise control after the first month.

    • Finds weird things: Not just Microsoft and Adobe. It spotted FileZilla, 7-Zip, and even a dusty Citrix Receiver. Those are the ones that bite you when you look away.

    • Facility surprise factor: During an office remodel, our building team relied on Archibus CAFM data. CSI still caught outdated video drivers they’d missed, proving it watches more than the usual suspects.

    Where it tripped me up

    • The console feels slow some days: Reports load fine, but policy edits take a few clicks too many. When I’m rushing, that drag shows.

    • Agent hiccups: Off-domain laptops can go quiet. If users don’t check in, scans get stale. I set grace alerts and nag emails. Still, a few slipped.

    • False flags here and there: It once flagged Java even though the browser plug-in was dead. Another time, it missed a niche video codec. Not common, but it happens.

    • Patch lag for rare apps: Big names are fast. Odd vendors can take time. I built two custom packages that I really wanted CSI to have ready. Not a deal breaker—just annoying.

    • Reboots and user pain: Silent is great till a locked file gets in the way. I learned to schedule reboots and warn folks. “Hey team, save your work after 6.” Simple notes save tickets.

    • Change-control déjà vu: While rolling out a management-of-change system, I learned that even perfect workflows choke if endpoints ignore agents—the exact same pain the CSI agent hiccups give.

    A short story of a long night

    The night before a board meeting, we had to show “exposure down by 50%.” That’s a big ask. I pulled CSI’s top risks, picked the big hitters (Chrome, Reader, 7-Zip), and ran a three-step push over 48 hours. The graph dropped. The board smiled. I drank a lukewarm coffee and tried not to. You know what? It felt good.

    Quick detour: after that caffeine-fueled marathon, a teammate and I joked about how much of our professional life now happens through screens—video calls, remote patches, virtual whiteboards. If you’ve ever wondered how deep that screen-based intimacy can go beyond the workplace, this candid breakdown of modern digital connection over at InstantChat’s blog explores the psychology of live cams, why some people find them more engaging than in-person encounters, and how you can leverage the same real-time feedback loops to strengthen any online interaction you care about.

    Still, there are days when you crave an old-school, face-to-face vibe. Central Valley locals can jump out from behind the monitor and try Speed Dating Clovis, a no-swipe-required evening where you meet a roomful of singles in minutes and leave with real eye contact, not just profile pictures.

    Who will like it, and who won’t

    • Good fit: IT shops that use WSUS or SCCM. Teams that care about third-party patching. Folks who want data they can show to leaders.

    • Meh fit: Very small teams with 50 machines and simple needs. Or places with no central patch tools yet. It can feel like a lot for a tiny setup.

    Tips I wish someone told me

    • Build pilot rings from day one. Keep one group that might break things on purpose (kidding, sort of).

    • Write simple kill scripts for common apps (Chrome, Reader, Teams). Tools love to stay open.

    • For a concise cheat-sheet on silent install switches and packaging tricks, I keep QuSoft bookmarked.

    • Agree on exceptions with app owners. Document them. Revisit each quarter.

    • Keep reports simple: top five risks, fix plan, status. Less is more when you present.

    • If you ever wrangle space data in a full-blown CAFM platform, the packaging habits you build there translate straight into third-party patching.

    • Hate repetitive typing? My test of three data entry tools taught me that even a tiny macro can shave hours off package building.

    Price, support, and the human bit

    It’s not cheap. I look at it the same way I judged ROI when I ran pay equity software for a year—time saved beats sticker shock. But the time saved on packaging and chasing bugs was real for us. Support was fine. Replies came within a day. They helped with one nasty Adobe patch loop and a detection rule tweak. I wish chat was faster, but tickets worked.

    My verdict

    CSI made my week calmer. It cut guesswork. It gave me proof. It wasn’t perfect—no tool is. The console can feel slow. Rare apps lag. Agents need love. But I shipped patches fast, shrank risk, and told a

  • Hello world!

    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!