Apex Imaging Services Turns Facility Condition Data Into Capital Intelligence with Quickbase

The Solutions

A Centralized Facilities Condition Assessment Platform Built in Quickbase

Quandary Consulting Group designs and develops a centralized Facilities Condition Assessment application using Quickbase as the core application and data platform.

Rather than simply digitizing an existing form, Quandary structures the solution around the lifecycle of facility data.

Information captured during an assessment becomes part of a persistent asset record. Asset records connect to locations and clients. Condition information contributes to asset scoring and lifecycle analysis. Cost information rolls into funding categories and capital planning. Reporting gives stakeholders a portfolio-level view of where future investment is likely to be required.

The result is a connected model that moves from: Facility → Location → Asset → Condition → Lifecycle → Cost → Capital Plan

This distinction matters because Apex is not simply collecting more data. It is creating a structured way to turn field and facility information into decisions.

Building a Structured Asset System of Record

At the center of the platform is a structured asset repository.

Quandary configures Quickbase to capture and manage information such as asset type, make, model, serial number, condition, location, and related attributes. Assets are then organized around clients, locations, building structures, and zones so that users can move from a portfolio-level view down to an individual piece of equipment.

Instead of maintaining separate spreadsheets for different facilities or assessment projects, Apex gains a consistent data structure across the portfolio.

The architecture also supports manual and CSV-based imports, allowing existing facility and asset information to enter the platform without requiring teams to recreate every record manually.

This creates a reusable source of facility intelligence rather than another one-time assessment dataset.

Connecting Condition Assessments to Asset Lifecycle

Knowing that an asset exists provides limited value without understanding its condition, Quandary structures the application so asset conditions can be assessed, categorized, and connected to the expected lifecycle of the underlying equipment.

• Quickbase becomes the operational layer connecting an asset's physical condition with the information required to plan for its future.
• Degradation model templates establish a framework for relating observed conditions to expected asset lifecycle and asset scoring.

This allows Apex to move beyond a binary question of whether an asset is currently functional; instead, teams gain a framework for understanding where an asset sits in its lifecycle and what that condition means for future planning.

An aging rooftop HVAC unit, for example, is no longer simply an item on an assessment report. It becomes an asset with a location, condition, expected lifecycle, projected cost, and potential capital requirement.

When this model is applied across hundreds or thousands of assets, individual observations begin to form a portfolio-level investment picture.

Turning Asset Data Into Capital Planning Intelligence

This is where the application becomes particularly valuable.

Quandary connects asset information with projected costs, funding categories, capital plans, and forecast reporting so Apex can begin translating facility conditions into financial requirements.

Asset costs roll into client-level funding categories, allowing users to analyze expected investment across different areas of the portfolio. The solution also supports capital planning and spend reporting based on actual survey conditions.

Instead of asking teams to manually combine condition reports with separate financial models, the system creates a direct relationship between what exists in the field and what the organization may need to fund.

For decision-makers, this changes the conversation from, “We have 147 assets rated in poor condition;" to “These assets represent a concentrated capital requirement across these locations and funding categories.”

This allows facilities and capital-planning teams to evaluate investment requirements across locations, asset categories, and planning periods while maintaining traceability back to the individual assets driving those requirements.

Creating a Visual Record of Asset Condition

Facility condition data often requires more than fields and numbers; photographic evidence gives teams additional context about what assessors see in the field, so Quandary enables users to attach images directly to asset records within Quickbase.

The application provides locally stored asset photos with defined expiration and deletion policies, along with the ability for users to export images for longer-term external retention.

This gives stakeholders additional evidence when reviewing an asset without requiring them to physically visit every facility and for distributed portfolios, this type of visibility significantly improves collaboration between assessors, facilities teams, project managers, and capital-planning stakeholders.

Designing Access Around the People Who Use the Data

Not every user needs the same information; Quandary implements role-based access controls in Quickbase so permissions can reflect different responsibilities and user groups.

This becomes increasingly important as the platform expands.

Facility teams can work with detailed asset information. Managers can focus on exceptions and portfolio performance. Leadership can review capital requirements and planning information without navigating the underlying operational detail.

The broader roadmap also anticipates internal and client-facing roles, allowing the architecture to support increasingly scalable access as adoption grows.

How Quandary Delivered the Platform

Quandary did not approach the engagement as a fixed application build in which every requirement must be determined before development begins, instead, the team used an Agile Kanban delivery model, creating a shared backlog in which Apex and Quandary continuously prioritize development requirements. Work progresses through development, unit testing, user acceptance testing, feedback, and subsequent planning cycles.

This approach is particularly valuable for an operational application because users often discover what they truly need once they begin interacting with real workflows and data.

Quandary combined:

• Quickbase architecture and data modeling to establish relationships among clients, locations, assets, conditions, costs, and capital planning.
• Native and custom Quickbase development to create the application, workflows, forms, tables, permissions, calculations, and reporting environment, including both native and custom Quickbase development and consulting.
• Business process design to translate Apex's Facilities Condition Assessment methodology into a scalable digital workflow.
• Agile development and testing to continuously refine functionality as requirements become clearer.
• User acceptance support to validate that the system works in the context of real Apex processes before individual work items are accepted.
• Scalable architecture to create a foundation that can expand as Apex introduces additional reporting, integrations, predictive capabilities, or client-facing functionality.

The result is not simply an application that stores FCA information, it is an operational architecture for managing the information behind facilities investment decisions.

Technology Used

Quickbase

Quickbase serves as the central application and data layer for the Facilities Condition Assessment solution. Quandary used the platform to create the relational structure connecting clients, locations, zones, asset types, assets, conditions, scoring, degradation models, costs, funding categories, and capital-planning information.

The application uses native Quickbase forms and tables for asset management, role-based permissions for access control, CSV imports for legacy and recurring data loads, photo attachments for supporting evidence, and reports that transform individual asset records into broader planning information.

The schema of the application design makes the strategy particularly clear: Assets/Equipment sits at the center of a much larger relational model, connecting facility information to conditions, scores, projected costs, work history concepts, warranties, locations, and capital plans.

Jira + Agile Kanban

Jira supports the development backlog and delivery process.

Quandary and Apex jointly prioritize work, while the Kanban methodology keeps development focused on high-value requirements and allows newly discovered needs to enter the backlog as the application evolves.