Many engineering teams eventually face the same request:
“Can we make the BOM and related files available to procurement, production, or service?”
The simplest solution is to publish the results of design: drawings, PDFs, STEP files, and often the BOM itself. These files are typically placed in a shared folder or a SharePoint site so that other departments can access them.
From the perspective of the design team, the problem is solved. The information is available and easy to distribute.
For the teams that need to work with that information, however, this is often where new challenges begin.
A BOM shared as an Excel file is easy to read, but difficult to connect to purchasing decisions. Drawings and STEP files provide context, but they don’t allow project leads, procurement, or service teams to contribute information back into the product definition. The data is accessible, yet collaboration still happens through meetings, emails, and repeated clarification between teams.
Publishing engineering data makes it visible.
But it does not necessarily make it collaborative.
This is where Fusion Manage changes the picture. Instead of exporting product information as files, the underlying items and BOM structures can be introduced into Fusion Manage as structured data that remains connected and usable by different roles across the organization.
In the following sections, we explore why simply publishing engineering data often creates new challenges and how using Fusion Manage as a collaboration platform allows product information to remain structured, shared, and actively used across teams.
When engineering data is shared as files, the intent is clear: other teams should be able to access the information they need.
But access alone rarely solves the underlying problem.
Procurement may need to attach supplier information.
Project leads may need to define required components for a specific project.
Service teams may need documentation and context that evolves over time.
When the shared information exists only as documents, these interactions typically happen somewhere else like spreadsheets, emails, or meetings. The product information itself remains static while the real discussions happen around it.
Over time a familiar pattern emerges: engineering publishes information, other departments request changes or clarifications, and engineering republishes updated files.
The information is shared. But the process still revolves around engineering producing and redistributing documents.
Once engineering data becomes visible beyond the design team, another question naturally appears: when does the product definition actually start?
In many organizations, engineering work begins before the full scope of a project is completely defined. Project leads or sales teams may already know which equipment must be used, which suppliers are required, or which configurations the customer expects. Yet this information often lives in conversations rather than in the product data itself.
When product information is introduced into Fusion Manage, the process can start earlier.
Instead of beginning every project directly in CAD, teams can first define the top-level product and its key constraints in Fusion Manage. Project leads capture the scope, identify required components, and provide engineering with a clearer starting point.
Engineering still performs the detailed design work in CAD and Vault. But instead of starting with a blank structure, they begin with a defined product context.
This small shift reduces ambiguity and helps ensure that engineering effort focuses on the right solution from the start.
Another issue that often becomes visible is consistency.
When product data mainly lives inside design files, small variations in naming and descriptions are almost inevitable. Something as simple as a bracket may appear under several slightly different names depending on who created it.
Over time, this makes searching and reuse difficult. Even when a suitable component already exists, it may not be easy to find.
By introducing classification and structured product data in Fusion Manage, teams can standardize how components are described. Titles and descriptions are generated consistently, ensuring that similar components are identified the same way across projects.
This may seem like a small improvement, but it has an important effect: once product information becomes consistent and searchable, it becomes much easier to build on existing work instead of starting from scratch.
One of the most interesting changes appears in the way engineers approach product variants.
In many environments, certain assemblies are recreated for each new configuration. For example, when building pump stations, engineers may design a new frame for every variant, even when the differences are relatively small.
Once product information becomes easier to search and reuse, teams begin questioning this approach. Instead of designing slightly different frames for each project, they start designing frames that support multiple configurations.
In other words, the design philosophy shifts from creating variants to designing for reuse.
This shift can have a noticeable impact. Preparing a new variant that once required days of engineering work can often be reduced to hours.
What makes this dynamic interesting is that none of these improvements are the original goal.
The initial request is usually simple: others need access to the data.
But once product information lives in Fusion Manage as structured data, the organization gains something more valuable than access: a shared foundation for working around the same product definition.
Product definitions can start earlier.
Information becomes easier to find and reuse.
Teams spend less time clarifying requirements and more time building on what already exists.
Sharing engineering data is the trigger. Keeping that data structured and connected is what allows the real improvements to happen.
Publishing engineering artifacts will always remain an important part of the design process. Drawings, PDFs, and models are essential for manufacturing, procurement, and documentation.
But when those artifacts become the only way product information is shared, collaboration remains limited.
By keeping items and BOM structures alive in Fusion Manage, engineering data becomes more than a set of files. It becomes a shared product definition that multiple roles can work around.
The difference may appear subtle at first.
But over time it determines whether sharing marks the end of the data journey or the beginning of a more connected way of developing products.