Entegrity Standardizes Commissioning and Solar O&M at Scale With Bluerithm
Introduction
Entegrity is an energy services, sustainability, and solar development company that delivers innovative, sustainable solutions to optimize building performance. The company offers energy savings performance contracting (ESPC), solar development and commissioning, and professional services such as building testing and consulting. They operate nationally in K-12 schools, higher education, commercial, industrial, healthcare, and government facilities. With 10+ years in business, 70+ employees, and a performance rate of hundreds of projects annually, Entegrity needs scalable processes and dependable documentation to support delivery teams, clients, and long-term asset obligations.
Tracey Caldwell Onsite at a Solar Project
To meet those demands, Entegrity uses Bluerithm as a centralized system for commissioning execution, reporting, issue management, and long-term records. Entegrity’s teams use Bluerithm broadly—new construction commissioning across their portfolio, solar commissioning checklists that transition into operations and maintenance (O&M), and ESPC-related work where existing equipment conditions and recurring issues require strong traceability.
Bluerithm frees up teams to spend less time assembling reports and more time solving problems. Beyond day-to-day efficiency, Bluerithm has become a durable recordkeeping system for Entegrity, supporting warranty calls, troubleshooting, and long-term Solar Service Agreements (SSA) lasting 18+ years.
The Challenge: Scaling Commissioning Execution and Long-Term Documentation
Before adopting Bluerithm, Entegrity had tried other commissioning software solutions, but still felt the pressure of manual workflows—paper checklists, printed documentation, and spreadsheets. The driver was straightforward: efficiency. When teams manage large amounts of equipment and repeated commissioning tasks across projects, manual systems become slow, inconsistent, and difficult to audit.
“Bluerithm replaced printed checklists and spreadsheets with a more efficient way to manage large equipment counts and standardized workflows.” – Tracey Caldwell, ESPC Commissioning and Solar Commissioning Service Leader, Entegrity
Entegrity also faces challenges that are common to organizations with a broad portfolio:
1) Consistency Across Many Project Types
Commissioning delivery varies—new construction vs. existing buildings vs. solar arrays vs. ESPC retrofits—but Entegrity seeks as much standardization as possible. With many projects and stakeholders, repeatable templates, consistent naming, and uniform reporting structures are essential for scale.
2) Stakeholder Coordination and Contractor Participation
Commissioning depends on collaboration—owners, design teams, contractors, and commissioning authorities. In many organizations, contractor checklist participation can be low, which forces commissioning teams to chase completion and manually reconcile status.
3) Field Documentation That Holds Up Over Time
Entegrity supports projects where equipment conditions, existing issues, and repairs matter long after turnover. When warranty calls occur—or when persistent failures reappear—teams need timestamped documentation, photos, and linked issue histories to understand what changed and when.
4) Long-Term Solar O&M Obligations (18+ Years)
For solar service agreements (SSAs), Entegrity must maintain asset-level documentation over decades. This requires a system that doesn’t just “finish” at project closeout. It must support repeated inspections and maintenance entries year after year, tied to the same equipment and historical context.
Why Bluerithm: A Platform That Replaces Scattered Tools With a Structured System of Record
Entegrity chose Bluerithm primarily for efficiency and scalability compared with manual tools. But the deeper fit is that Bluerithm maps to how Entegrity actually works:
- Projects are equipment-centric.
- Work must be assigned and tracked.
- Reporting must be assembled without duplicating effort.
- Issues need to be connected to equipment and locations for troubleshooting.
- Photos and artifacts need to be easy to capture, find, and trust later.
Entegrity builds out projects in Bluerithm initially and then uses the software through construction, site visits, issue tracking, and final reporting—ultimately serving as a long-term record of what happened across the entire project lifecycle.
Implementation Approach: Standardize First, Then Scale Across Teams and Services
Entegrity’s usage follows a pattern that is common among high-performing commissioning teams: establish a standardized project structure and templates, then replicate them at scale.
Step 1: Build Projects and Equipment From Templates
When a new project starts, Entegrity builds it out in Bluerithm by adding equipment and assigning work templates to that equipment.
Step 2: Integrate Reporting Early to Eliminate Duplicate Effort
A key detail is that Entegrity attaches reporting requirements early. For commissioning, one of the first reporting deliverables is a commissioning plan. Entegrity pairs this plan with the work created in Bluerithm so reporting and execution remain aligned—reducing duplicated documentation and rework later.
Step 3: Onboard Project Teams With Kickoff Meetings
As projects enter construction, Entegrity holds kickoff meetings to familiarize project teams with Bluerithm and add them to the project environment. Importantly, other team members can focus on work assigned to them without being overwhelmed by irrelevant tasks.
Step 4: Use Field Workflows for Site Visits, Issues, and Evidence
During site visits, Entegrity uses Bluerithm for site visit reporting and issue tracking. Contractors can be added to issues and provide responses and photos directly in the platform, streamlining communication and keeping evidence attached to the right equipment and context.
Step 5: Close Out With Final Reporting—Then Retain as a System of Record
Once project work is complete, Entegrity compiles final reports in Bluerithm. The outcome is a single place where project work status (“not started” → “in progress” → “complete”), issues, and final reporting live together.
How Entegrity Uses Bluerithm Day-to-Day
Entegrity’s day-to-day usage can be grouped into six core workflows.
1) Project Buildout and Progress Visibility
Entegrity builds out projects by adding equipment and work, then uses Bluerithm’s completion tracking to monitor progress. Tracey and her team finds value in the percent completion and overview-level summaries which help them understand status over time.
“Bluerithm gives us the ability to see the percent completion on our work items. And then the overview page gives us a summary and rundown of the work on the project and how it’s been completed over time. It helps us keep track.” – Tracey Caldwell
Why that matters: across large portfolios, progress needs to be visible without hunting through spreadsheets or chasing updates. The platform provides a consistent way to know what is done, what is pending, and what needs attention.
2) Standardized Templates and Repeatable Delivery
Entegrity prioritizes standardization—acknowledging every project is different, but emphasizing consistency wherever possible. Tracey builds solar and ESPC projects from templates and uses standardized project organization conventions so teams can filter, search, and replicate effective structures.
Why that matters: a standardized structure increases speed, reduces onboarding time for new staff, and improves quality because deliverables are less dependent on individual habits.
3) Reporting Integration (Commissioning Plans Through Final Reports)
Entegrity’s approach to reporting is integrated rather than separate. Early reporting artifacts (like commissioning plans) are paired with the execution work so documentation stays current. At closeout, final reports are compiled within the same system that tracked the work in the first place.
Why that matters: many teams spend significant time reconstructing history at the end of a project. Integrating reporting throughout reduces that burden and improves accuracy.
4) Issue Tracking Tied to Equipment and Location
A particularly valuable workflow for ESPC and existing-building projects is linking issues to equipment and work. In an existing building with legacy equipment, having a list of prior issues connected to a location becomes a strong troubleshooting tool—especially when the same problems recur.
Why that matters: troubleshooting often fails when historical context is fragmented. A linked issue history helps teams see patterns, isolate root causes, and avoid repeating the same diagnostic steps.
5) Photo-First Field Documentation (Nameplates, Installs, Conditions)
Entegrity uses photo attachments heavily. They capture nameplate tags, installation photos, and surrounding conditions—particularly in existing buildings—so that later, if a warranty call arrives, they can verify what was true at a specific time. Bluerithm’s timestamps as valuable for these moments.
“We use Bluerithm as a recordkeeping tool—photos, issues, and documentation all in one place—so we can troubleshoot and respond to warranty calls with timestamped history.” – Tracey Caldwell
Why that matters: photos reduce ambiguity, accelerate communication with contractors, and provide defensible records when timelines and accountability are in question.
6) Long-Term Solar O&M for SSAs (18+ Years)
On solar service agreements (SSAs), Entegrity treats Bluerithm as an “in perpetuity” system. Each year, they create a new work item for each piece of equipment, fill out the checklist, and attach photos. Over time, this produces an annual condition history that captures differences, repairs, and trends. A specific example is Entegrity’s solar array project for Subiaco Abbey and Academy, where this year-over-year checklist approach is already in use even though none of these long contracts have reached their endpoint yet.
“For long-term solar service agreements, we add annual work items in Bluerithm so we can track condition changes and repairs over time.” – Tracey Caldwell
Why that matters: long-term O&M success depends on longitudinal data, not just a snapshot at commissioning. Yearly work items make the asset history explicit and easy to navigate.
Project Example
Entegrity’s portfolio in Bluerithm spans many projects and sectors: ~60 solar projects and ~280 other projects.
Subiaco Abbey and Academy Solar Array Project: Multi-Scope Work and Long-Term Tracking
Subiaco Abbey and Academy is highlighted in two ways:
1) Solar SSA O&M Tracking
Annual work items per equipment, photos over time, condition differences, and repairs captured year to year.
2) Existing-Building Controls Troubleshooting
Linking issues to equipment and location provides a history of what’s been found before and what was updated, supporting faster troubleshooting.
This is a strong illustration of Bluerithm’s dual role for Entegrity:
(a) commissioning/project delivery and
(b) ongoing asset management and service documentation.
By the Numbers:
Solar Modules: 2,784
Inverters: 8
Project Footprint: 6.45 acres
Subiaco Abbey and Academy
Subiaco Abbey and Academy Solar Array During Construction
Subiaco Abbey and Academy Solar Array
Outcomes and Results
Entegrity describes several concrete outcomes from their Bluerithm implementation:
1) Reduced Reporting Burden and Less Rework
Entegrity has saved a significant amount of time on reporting. Reporting is integrated with project buildout and work tracking, reducing duplicate efforts and end-of-project scrambling.
2) Stronger Troubleshooting and Warranty Response
Entegrity consistently uses Bluerithm as the first stop when troubleshooting project issues or warranty calls. Linked issue histories, asset-based documentation, and timestamped photo evidence help teams quickly determine what was known at turnover and what may have changed afterward.
3) Centralized Recordkeeping Across Solar and Commissioning
By migrating contractor test information, inverter programming configurations, and general documentation into Bluerithm, Entegrity reduces tool sprawl and creates a single system of record.
4) Positive Support Experience
Finally, Entegrity reports that Bluerithm’s support responsiveness has been strong: when issues arise, they can reach someone quickly.
A Compelling Example of How Solar Operations Can Scale
Entegrity’s case is compelling because it reflects real-world commissioning and solar operations at scale—where the core pain points aren’t theoretical:
- Teams need standardized templates that keep quality consistent across many project types.
- Contractors need structured workflows that make checklist completion realistic (and enforceable).
- Evidence matters, especially photos and timestamped histories.
- The work doesn’t stop at closeout—solar O&M and warranty support require continuity over years.
Entegrity demonstrates a mature adoption pattern: they didn’t implement Bluerithm as a “nice-to-have” afterthought. They embedded it into the lifecycle—project setup, reporting, kickoff onboarding, field execution, issue management, closeout, and multi-decade O&M.
Tracey Caldwell
Entegrity Team Members Onsite at Projects
Learn More About Bluerithm
Read real success stories from organizations using Bluerithm and learn more about how Bluerithm supports solar projects
Energy
See how Bluerithm supports commissioning for energy projects including solar, oil and gas, nuclear, geothermal, green hydrogen, hydropower, BESS, wind, fusion, and energy storage
Solar and BESS Projects
How Renewable Energy Integration Group Standardized and Scaled Operations with Bluerithm