Suffolk Uses Contech Stack on Gilead California Research Center

Suffolk Uses Contech Stack on Gilead California Research Center
Photo by C Dustin on Unsplash

General contractor Suffolk is using a set of construction technology (contech) tools on Gilead's new research center in California. The project, reported by Construction Dive on November 18, 2026, shows Suffolk combining four vendors to handle layout, progress tracking, procurement and sequencing on one lab job.

  • Layout: Dusty Robotics
  • Progress tracking: OpenSpace
  • Procurement management: Kaya AI
  • Sequencing: Alice Technologies, maker of Alice
  • Client and project: Gilead's new research center in California

Which contech tools Suffolk used at Gilead

Each tool covers a separate stage of delivery. Dusty Robotics builds the FieldPrinter, a robot that prints BIM and CAD layouts straight onto the slab, replacing much of the manual chalk-line work crews usually do before framing and MEP rough-in.

OpenSpace captures 360-degree imagery as teams walk the site and turns it into a visual record that can be compared against plans over time. Alice generates and optimizes construction schedules, letting planners test different sequences before committing crews and equipment. Kaya AI handled procurement management on the project.

Why lab projects suit a multi-tool contech approach

Research facilities tend to carry dense mechanical, electrical and plumbing systems and long-lead equipment. That makes accurate layout, tight sequencing and close tracking of material deliveries more valuable than on a typical office build.

Suffolk's choice to cover four functions with four point solutions, rather than one platform, reflects how many large contractors now work. Specialist tools often go deeper in their niche, but they have to be stitched together by the project team.

What to check before copying this contech stack

Several details have not been made public. Suffolk has not shared, in the coverage available to aec+tech, measured outcomes such as schedule days saved, layout rework avoided or procurement delays prevented. Contractors weighing a similar setup should ask vendors for project-level results, not just pilot anecdotes.

Other questions worth raising before adopting a comparable stack:

  • Data flow: does the sequence produced in Alice feed progress tracking in OpenSpace, or do teams compare them by hand?
  • Model readiness: robotic layout depends on a coordinated, field-ready model. Who owns that model and when is it frozen for printing?
  • Procurement links: how does procurement status connect back to the schedule so that a late delivery triggers a resequence?
  • Field adoption: who on site runs each tool, and how much training do superintendents and trades need?
  • Owner access: does Gilead, as owner, see the same data the contractor sees?

Integration between these products has not been detailed for this project, so firms should not assume the four tools share data automatically.

What it means for AEC teams

The Gilead project is another sign that large general contractors are treating contech as a stack, with a dedicated tool for each workflow rather than a single system. For BIM managers, that raises the bar on model quality, since the same model now drives robotic layout, schedule simulation and progress comparison.

For smaller contractors, the practical lesson is to start with the workflow that causes the most rework on complex jobs, prove the value there and then add tools. Without published results from Suffolk, the strongest takeaway is the structure of the stack, not its return on investment.

Ask Ace