Advancing AEC and Project-based Teams with Panzura Nexus

AEC Firms Have Decades of Project Data in Panzura CloudFS That Microsoft 365 Copilot Cannot See — Panzura Nexus Bridges the Gap Maintaining Files, Permissions, and Compliance

Key Takeaways:

• AEC firms spend on average 5.5 hours per week searching for project data across decades of drawings, specs, and files that Microsoft 365 Copilot can't see—costing the industry $177.5B annually in wasted labor.
• Panzura Nexus bridges Panzura CloudFS to Copilot without migrating files or changing permissions, enabling conversational interactions and intelligent retrieval while preserving client contract compliance and existing access controls.
• Queries that took hours of manual folder searching now take seconds: precedent research, proposal language retrieval, field team support, and institutional knowledge preservation all through natural-language Copilot prompts.

Every AEC firm has the same problem.

They have decades of project work. Drawings, specifications, calculations, field reports, change orders, correspondence, cost estimates, and more. The data lives across network shares, archive systems, cloud storage, and if they've moved to a global file system like Panzura CloudFS, that history is a firm’s most valuable asset. It’s also effectively invisible to the people who need it.

A senior engineer starting a new water treatment project wants to know how the firm has approached similar jobs. In theory, that information exists. In practice, finding it means calling three colleagues, hoping someone remembers a relevant job number, digging through project folders, and opening files to see what’s inside. This takes hours, sometimes days

Often it doesn’t happen at all, because the cost of the search is higher than the expected value of the information. So the firm re-invents work it has already done, at billable expense, because the institutional memory is locked in a format nobody can easily query.

Construction professionals spend an average of 5.5 hours per week looking for project data and information. Time spent on non-optimal activities (searching for data, resolving conflicts, fixing rework) costs the U.S. construction industry an estimated $177.5 billion annually in labor.

That’s the problem AEC leaders are trying to solve. And it’s exactly what Panzura Nexus addresses.

The Copilot Gap in AEC

Most AEC firms that have committed to Microsoft 365 and by now are trying to leverage Microsoft 365 Copilot. It was an easy decision when it started because it offers the per-seat licenses a firm already owns, now with AI assistance layered on top. What has become clear in practice is that Copilot cannot see the most valuable data. It sees SharePoint, Teams chats and Outlook. It does not see the project folders, archive shares, and decades of drawings. In short, it does not see most of the firm’s critical document corpus.

For an AEC firm, the gap between “AI that works on my meeting notes” and “AI that works on my actual project history” is enormous. It’s the difference between Copilot being a nice-to-have that helps with email triage and Copilot being a tool that changes how the firm operates.

The obvious way to close that gap, which is to move the project files to SharePoint, is a non-starter in AEC. Folder structures typically match the project organization. Access controls match project teams and disciplines. Compliance policies were written against existing architecture. Migrating all of that to SharePoint would ostensibly take months or even years, break relationships, and likely violate client contracts that specify where and how project data must be stored.

Panzura Nexus takes a different approach. Files stay on CloudFS. Permissions stay in Active Directory. Panzura Nexus reads the data, translates the identities, and makes it all searchable through Copilot without moving a single file.

Table 1. AEC Retrieval Questions — Before and After Nexus

What This Looks Like in Practice

“Bad data” — data that is inaccurate, incomplete, inaccessible, inconsistent, or untimely — cost the global construction industry an estimated $1.85 trillion in 2020 according to an Autodesk report. Bad-data-driven decisions account for $88.69 billion in rework specifically, or 14% of all rework performed industry-wide. Thirty percent of surveyed firms reported that more than half of their project data is “bad” and leads to poor decision-making more than half the time.

The AEC-specific patterns we’ve seen in production map to familiar workflows.

• Precedent search. The question “have we done a project like this before” becomes a Copilot prompt rather than a chain of phone calls. The engineer asks naturally, “Show me our past hospital projects in seismic zones over two hundred thousand square feet,” and Copilot returns relevant project files, names, and a synthesized overview. What used to be two hours of manual searching is thirty seconds of conversation.
• Proposal and RFP response. Firms that respond to RFPs typically have hundreds of gigabytes of past proposals scattered across project folders. When a new RFP comes in, teams tend to start from scratch rather than search through years of old material. With Copilot connected to the full proposal history, teams can pull winning language from prior bids, reuse technical approaches, and cite past project performance with specific project numbers. Beta customers have reported meaningful time savings on proposal assembly.
• Field team support. Engineers and superintendents in the field don't have time to dig through cloud storage on a phone. A Copilot prompt from a job site, “What's the current revision of the steel erection drawings for the north building,” is a direct path to the answer. The mobile productivity gain here is larger than it looks, because the alternative is usually “call the office.”

In terms of institutional knowledge preservation, firms with senior staff approaching retirement are using Panzura Nexus as part of succession planning. Making historical project data AI-searchable means that technical judgment embedded in old drawings, specifications, and correspondence remains accessible after the people who authored it retire. This is a use case none of us anticipated when designing Nexus. It’s also one of the most meaningful use cases now.

The File Type Question

AEC data is not uniform. Most firms have a mixture of native Microsoft documents, PDFs, CAD files, images, and many other proprietary and non-proprietary formats. A common question from IT directors is how Panzura Nexus handles file types that Copilot doesn’t natively understand.

The answer is that full content indexing is available for the file types Microsoft's Graph Connector can process. That includes Office documents, PDFs, plain text, and increasingly others as Microsoft expands native support. For binary formats like design files, Panzura Nexus indexes the metadata including file name, path, revision, dates, author, and title block information where extractable. That metadata is often what matters for search. “Find me the current revision of the structural drawings for the Dallas hospital” is answered by metadata, not by interpretation of the drawing itself.

Table 2. AEC File Types and Panzura Nexus Coverage

Security and Client Contracts

A particular AEC sensitivity, often more acute than in other markets, is client contract compliance. Project data for a government client, a healthcare client, or an infrastructure owner frequently comes with handling requirements written into the contract such as residency, retention, access control, and audit trail expectations.

Panzura Nexus was designed for this. CloudFS access controls remain the source of truth. Files don’t move from where contracts specify they must live. Audit trails are maintained, and compliance teams can produce a complete record of what was indexed. Where data residency matters — particularly for firms with EU offices — Panzura Nexus runs on the specific infrastructure in a region, and the Microsoft 365 tenant geographic configuration governs where the Copilot-side data lives.

Panzura Nexus is generally available to Panzura CloudFS customers. The beta program included AEC firms across different disciplines and sizes, and the deployment patterns we’ve developed over the last several months reflect AEC-specific needs.

If your firm has made the Copilot investment and you’re trying to extract more value from it — or if your engineers and project managers are telling you Copilot is useful for email but not for their real work — the conversation is worth having now

The AEC gap between AI as a novelty and AI as a working tool is closed with a comprehensive CloudFS=integrated Microsoft 365 Copilot solution, not with the prompts. To learn more about Panzura Nexus for AEC, visit panzura.com/demo or contact your Customer Success Manager.

Microsoft, Microsoft 365, Microsoft 365 Copilot, Microsoft Copilot Studio, Microsoft Azure, and Microsoft Graph are trademarks of the Microsoft group of companies. All product and company names are trademarks or registered® trademarks of their respective holders. Use of those names does not imply any affiliation with or endorsement by their owners. The opinions expressed above are solely those of Panzura LLC as of April 29, 2026, and Panzura LLC makes no commitment to update these opinions after such date.

Frequently Asked Questions

• How does Panzura Nexus make CloudFS data searchable in Microsoft 365 Copilot without moving files?

  Panzura Nexus deploys as software on the same LAN as your Panzura CloudFS nodes. It reads file content and metadata over SMB, subscribes to CloudFS audit events for real-time change detection, and pushes the data into Microsoft 365 Copilot through Microsoft's Graph Connector API. Files remain on CloudFS, permissions remain in Active Directory, and Copilot gains a governed window into enterprise file data. 

• Does Panzura Nexus index design files?
  

  Panzura Nexus indexes metadata for design file formats, including file name, path, revision, author, dates, and extractable title block fields. Full content indexing is not available for these binary formats, but metadata search typically answers most AEC retrieval questions — such as identifying the current revision of a specific drawing set. 

• Why not just migrate project files from a file system to SharePoint to use Copilot?

  SharePoint migration typically breaks existing AEC workflows: folder structures matched to project organization, access controls aligned to project teams, and compliance policies written against current architecture would all need to be rebuilt. Client contracts often specify where and how project data must be stored, and migration timelines run months to years. Panzura Nexus preserves existing architecture while extending Copilot's reach. 

• How does Panzura Nexus handle permissions when a user is removed from a project team?

  When an Active Directory group membership changes, Panzura CloudFS emits an audit event, and Panzura Nexus propagates the permission change to Microsoft 365 Copilot within seconds. Users removed from a project team lose AI access to that project's data in near real-time, not on a next-crawl basis.

• Can Panzura Nexus be deployed for AEC firms with EU data residency requirements?

  Yes. Panzura Nexus runs on the customer's own infrastructure in the customer's chosen region. Your Microsoft 365 tenant's geographic configuration governs where Microsoft 365 Copilot-indexed data resides. For an EU-based AEC firm with an EU-configured M365 tenant, both the Panzura Nexus-side file data and the Copilot-side indexed data remain within the EU throughout the ingestion pipeline.

• How is Panzura Nexus different from building a custom Microsoft Graph Connector in-house?

  A custom Graph Connector is a 12-18 month services engagement plus ongoing maintenance as Microsoft updates APIs, CloudFS evolves, or Active Directory changes. Panzura Nexus is a supported Panzura product built specifically for Panzura CloudFS, with pre-built identity mapping, event-driven ingestion, policy-based governance, and a dashboard included. It's deployed in days rather than months and maintained by Panzura.

• What is a typical Panzura Nexus deployment timeline for an AEC firm?

  Most AEC customers move from kickoff to active ingestion within one week. Infrastructure provisioning takes approximately half a day, Panzura Nexus deployment and initial setup takes hours, plugin configuration with a Panzura expert takes half a day, and the first policy is validated in dry-run mode before activation. No end-user training is required.