Situation

The client is a digital infrastructure and smart buildings firm founded in 2007. They plan, design, and build data centers, smart buildings, and mission-critical technology infrastructure for clients across higher education, healthcare, life sciences, financial services, and government. Their work ranges from hyperscale data center development and AI-ready computing environments to smart building integration for commercial real estate. Projects are complex, multi-phase, and often run concurrently across multiple sectors and regions.

With that kind of project mix, knowing how time is allocated across the team is not just a reporting exercise. It directly affects how leadership manages capacity, staffs engagements, and tracks utilization against available hours. The client tracks project time through Harvest, but getting a timely picture of that data required manual steps. Without a connected reporting layer, reviewing utilization across projects meant pulling exports and working with raw data rather than a structured view built for the team’s needs.

The client wanted a Power BI solution that could connect directly to their Harvest data and surface the most useful information without requiring manual intervention each time.

Solution

ProsperSpark built a Power BI dashboard connected to Harvest through Coupler, a data integration tool that pulls Harvest time records on a scheduled basis. This gave the team a live data connection that updated automatically rather than requiring manual exports or file management.

The dashboard was built around labor utilization, with views sliced across four dimensions:

• • Time period (month, quarter, and week)
  • Project
  • Task
  • Employee and employee type (Market Leaders vs. Project Team)

A key feature was the available capacity vs. utilization view, which showed both hours and percentage, giving leadership a quick read on how the team was allocated at any point in time.

Formatting and formulas were refined across all tabs after an initial review call with the client, and a revision was returned based on that feedback. The final connection setup was verified on a call with the client team, confirming the data was pulling correctly and that the team could refresh and access the dashboard independently through a desktop shortcut.

The engagement was structured as a block of hours, which kept the work practical and focused. The goal was a working, maintainable dashboard—not an over-engineered solution.

Results

The team ended the project with a dashboard that connected directly to their Harvest data and required no manual prep to use. Instead of pulling exports and working with raw time records, the client now had a structured view of labor utilization that could be refreshed on demand.

The Coupler connection was verified live with the team and confirmed to be pulling current data. The dashboard was accessible from a desktop shortcut, and the data connection was set up under the primary account so it would remain stable without depending on individual team members’ credentials.

For a project delivered in eight hours, the outcome was a reliable, self-service reporting tool the team could continue using without outside support.