Product Tour Pricing Integrations Get started
Back to Use Cases
Infrastructure Consulting

How StructureWorks Group
Stopped Solving the Same Problems Twice

520+ engineers. 9 offices across 4 continents. 35 major infrastructure projects per year — and 60% of solved technical challenges re-investigated from scratch because the knowledge walked out the door when teams disbanded.

0 Engineers
0 Global Offices
0 Projects / Year
60% Rework Rate
01

The Company

StructureWorks Group is a multinational infrastructure consulting firm headquartered in Zurich, Switzerland, with offices in Dubai, Singapore, Toronto, São Paulo, London, Mumbai, Sydney, and Cape Town. They design and oversee construction of bridges, tunnels, highways, and transit systems — projects that typically span 18 to 36 months and involve cross-functional teams of structural, geotechnical, and transportation engineers.

Each project is a temporary organization: a team assembles, solves complex engineering challenges, delivers the project, and disbands. The knowledge stays with the people — until those people move to a different project, a different office, or a different company.

02

The Challenge

StructureWorks was bleeding expertise at every project close-out:

The Rework Cycle

An internal analysis revealed that 60% of technical challenges encountered on new projects had already been solved on previous ones. A soil stabilization technique perfected on the Dubai Metro Extension was re-investigated from scratch 14 months later by a different team on the Mumbai Coastal Road. The solution existed — nobody knew where to find it.

Team Disbandment

When a project closes out, the team scatters. Engineers return to their home offices, move to other projects, or leave the company. The project's close-out report — typically a 200-page PDF — captures formal deliverables but misses the tacit knowledge: which subcontractors to avoid, what regulatory shortcuts exist, and which design approaches were tried and abandoned.

9 Document Silos

Each office ran its own document management system. Zurich used SharePoint, Dubai had a custom solution, Singapore used Google Drive, and Toronto was still on a legacy file server. Cross-office knowledge sharing meant booking a call with someone who might remember something from 3 years ago.

03

The Implementation

Chief Knowledge Officer Maria Santos led the rollout, starting with the three most active offices:

Month 1 — Pilot

Three Offices, Three Systems

Wissenswerk connected to SharePoint (Zurich), Google Drive (Singapore), and the custom DMS (Dubai) simultaneously. 12,000 project documents were indexed in the first week — structural calculations, geotechnical reports, design review notes, and close-out reports from 8 years of projects.

Month 2–3 — Close-Out Debriefs

Capturing What Reports Miss

Wissenswerk's AI conducted debrief sessions with engineers from 6 recently completed projects. Each 5-minute session captured the lessons that never make it into formal reports: vendor reliability issues, regulatory workarounds, design alternatives that were considered but not chosen, and client communication strategies. 420 sessions produced 2,600+ structured knowledge entries.

Month 3–4 — Visual Knowledge

Making Diagrams Searchable

StructureWorks' document archive contained thousands of engineering diagrams — structural cross-sections, load distribution charts, and geotechnical profiles. Wissenswerk's visual knowledge extraction processed 4,800 diagrams, making their content queryable. An engineer could now ask "show me pile foundation designs for soft clay conditions" and find relevant diagrams from projects in Singapore, Mumbai, and São Paulo.

Month 4–6 — Full Scale

All 9 Offices Connected

The remaining 6 offices were onboarded over 8 weeks. A new project kickoff workflow was introduced: before starting any design work, teams now query Astra for relevant precedents from past projects. The "Solved Before?" check became a mandatory step in the project initiation process.

04

Turning Points

Two stories that showed the organization what was possible:

Month 3

The Cape Town Bridge Shortcut

A geotechnical team in Cape Town was bidding on a bridge retrofit over a tidal estuary. During the "Solved Before?" check, Astra surfaced a detailed soil stabilization report from a Sydney project 4 years earlier — same geological conditions, same saltwater exposure. The Cape Town team adapted the Sydney approach instead of starting from scratch, cutting the design phase by 11 weeks and saving an estimated €340,000 in engineering hours.

Solved Before? Check
soil stabilization techniques for tidal estuary bridge foundations

Found 3 relevant precedents. The Sydney Harbour Connector (2020) used jet grouting with saltwater-resistant additives for identical conditions. The technique reduced settlement by 78% and was completed 3 weeks ahead of schedule.

Source: Sydney Harbour Connector — Geotechnical Close-Out Report, Section 4.3
Month 5

The Departing Expert

StructureWorks' most experienced tunnel engineer, with 28 years at the firm, announced his retirement. In the past, this would have meant months of frantic knowledge transfer meetings. Instead, he participated in 24 AI debrief sessions over 6 weeks. Wissenswerk captured his expertise on tunnel boring machine selection, ground settlement prediction, and emergency protocol design — knowledge that had only existed in his head. Three months after his retirement, a junior engineer in Toronto solved a tunnel ventilation problem using insights from his debriefs.

05

The Results

12 months after full deployment across all 9 offices:

60% → 18% Rework rate reduced from 60% to 18%
€4.2M Saved in avoided duplicate engineering work
38K+ Project documents searchable across all offices
11 wks Average design phase reduction per project

"We used to joke that every project started from zero. It wasn't funny — it was costing us millions. Now when a team starts a new bridge or tunnel project, they ask Astra 'has this been solved before?' and nine times out of ten, the answer is yes. That single workflow change has transformed how we operate."

The New Project Knowledge Flow

Every project at StructureWorks now follows a knowledge-driven lifecycle:

1

Solved Before? Check

Before any design work begins, the team queries Astra for relevant precedents from past projects across all 9 offices.

2

Continuous Capture

Weekly AI debrief sessions capture decisions, challenges, and solutions as the project progresses — not just at close-out.

3

Knowledge-Rich Close-Out

When the project ends, all documents, debriefs, and diagrams are already indexed. The team disbands, but the knowledge stays forever.

Start Your Story

Teams that disband don't have to
take the knowledge with them.

Whether it's project-based work, consulting, or construction — we've helped organizations like StructureWorks keep knowledge alive long after the team moves on.