The Evolution of Facilities Software Implementation

And now for a post from my professional life.

I’ve been thinking a lot lately about how facilities software implementation is changing.

For years, the work centered on implementing a single platform end‑to‑end. To be clear, this approach can still deliver real value. Organizations managing their real estate and facilities workflows with clipboards and spreadsheets will see powerful results when they (carefully) implement a comprehensive central platform.

There are not as many organizations that look like this today as there were a decade ago. Lately the clients I work with are more likely to be mature in some areas and need help in others. They want to figure out how to work AI into their processes and analytics, how to connect their ERP systems to maintenance and real estate without alienating their employees, and how to integrate GIS, content management, identity management, and other solutions they already know and trust into something coherent. So my role is shifting from an implementer to something broader: product-managing a cohesive facilities intelligence ecosystem built from many moving parts.

Some components already live in production at the client’s site. Others come bundled inside traditional IWMS suites. Though “point solution” has been a dirty word in my industry for years, the most impactful pieces are often tools that solve one problem exceptionally well. Telling a different story–one you may have heard, about simplification through consolidation, or “tearing down silos”–is probably misleading the client and sending them down a path that is more likely to result in costly failure than success.

The challenge, or, better put, the opportunity, is designing how these pieces fit together. It’s no longer about “rolling out a system.” It is about curating a connected experience that delivers results quickly, minimizes friction, and proves its value to end‑users without heavy change management or months of training. The product should be sticky, like the best smartphone app. It should reveal itself, surfacing the right affordances and the right data in different ways to those who need it. It should be attractive and minimal. It should get out of the way and just work.

Implementing facilities software, then, is equal parts product development, systems engineering, process engineering, and project management, aimed at delivering a product that will exist for as long as a piece of heavy equipment; manage millions or billions of dollars in assets, including critical life-safety systems; integrate into the daily life of hundreds or thousands of people; and make up a significant part of the ongoing budget of the customer. It’s an awesome responsibility, an exciting challenge, and a thoroughly engrossing problem.

I wont solve the problem tonight, but I know that the future of IWMS isn’t monolithic. It is modular, integrated, intelligence‑driven, and deeply user‑centered. I’ve got some more posts in mind that build on this theme. Stay tuned.

Help! My TRIRIGA GIS Query isn’t working

TRIRIGA/MREF GIS Queries must Include GIS Latitude and Longitude and these must be labeled “Latitude” and “Longtitude.”

This is a quick note in case anyone is struggling with the same problem I encountered caused today.

Here’s the scenario.

  1. You’ve got a GIS portal section in TRIRIGA/MREF.
  2. You’ve created the GIS Map record that powers the section.
  3. You’ve set up the extent, configured your basemap(s), connected to one or more data sources for layers.
  4. You’ve created a “GIS Query” record to display TRIRIGA data on the map.

For most of you, it probably just works. Congratulations! If you’re a grug brain like me, though, read on.

No matter what you do, the map doesn’t work! It’s so broken, in fact, that the portal is unstable and your browser reports that the page is unresponsive.

If that’s you, what now?

The TRIRIGA documentation says it plainly enough: “Queries must include display columns that are labeled Longitude and Latitude. The Latitude and Longitude fields pinpoint the item on the map.”

After spending a couple hours today troubleshooting a GIS query, let me make it even more plain.

  • Make sure your query includes the Location Business Object and (of course) the correct association string.
  • Add the triGisLatitude and triGisLongitude fields from the Location BO to the query.
  • Label these fields Latitude and Longitude. This step is important! The fields are called “GIS Latitude” and “GIS Longitude” on the BO, and that won’t work.

Save the query, reload the portal, and voila!

Now I must confess what I did. Learn from grug.

grug see GIS query has longitude and latitude but TRIRIGA locations have no latitude and longitude data

this bad — it mean no TRIRIGA points on map

grug see GIS layer from ESRI includes ID

grug think user need way to open TRIRIGA record when they see something interesting on map

grug see “Show Table” on map viewer and see that records can be opened from the table

grug get idea

maybe user click on “Show Table,” find what they need with ID, and open record that way

this not great, but only option

grug change query to show data shown on GIS layer

grug think user no longer need latitude and longitude on query because these always blank

grug delete latitude and longitude from query because efficiency good

now portal no work and browser mad at grug when page load

grug try fix many ways until stop and eat lunch

maybe read documentation will help, grug think, but it only help a little

after few more tries, grug find answer and then write answer here

If this helped you, hello from the past! If you’re inclined, leave me a comment.