Acquire Fresh Skills
Remain Current with the Latest Trends
Elevate your Expertise

One thing is always certain in projects: Changes. In AutoCAD® Plant 3D, changes are normally easy, even with existing entities. The exception to this lies with Tags. Tags are unique within the software, and changing Tags on existing entities can be quite frustrating. Fortunately, Autodesk has provided a free tool called The Tag Rebuilder to address this issue.

A prime example for the use of this tool and the one we will use in this article is the result of making changes to Pipe Line Numbers to an existing project, as described in another Hagerman article entitled AutoCAD Plant 3D/P&ID: Pipe Line Numbers. In that article, the Pipe Line Numbers are redefined in the project so that they use the same format in the P&ID’s, Models, Orthos and Isometric drawings. However, if those changes are made in a project that already has existing drawings, there are additional steps that need to be taken in order to rebuild the tags within the project, and that is where The Tag Rebuilder comes into play, working in conjunction with the Data Manager.

I have already made all the changes to the Pipe Line Numbers per the aforementioned article to an existing out-of-the-box project that contains two P&ID’s and two Piping Models. Now I want to update my drawings so that they will have the correct format. Each existing Plant 3D Project will need to be updated in this same manner. However, there is no guarantee that this will work in every scenario since I cannot test every project created that has been customized. Results may vary based on the complexity of the customization as well as the amount of data that has been applied. For instance, if I were to perform these steps on the Sample Project that comes with Plant 3D, I would get mixed results because not all the Services have been defined in the Model, and when validating the Sample Project, there are a lot of errors with Services and Line Numbers between the P&ID’s and the Model. In the event these steps do not work, the only solution is to manually fix the Line Number Tags one at a time.

Downloading the Tad Builder

Autodesk provides a great tool for updating the Plant 3D Tags, and it is supposed to work on both the Plant 3D side as well as the P&ID side. I have found that it works every time on the Plant side, and so far, it is the only method I have found that will work on the Plant 3D side. However, I have yet to have a successful result on the P&ID side in any version or any project that I have personally tried to use it on. Fortunately, I have found another method on the P&ID side that works.

Here is a link to the Autodesk Technical Support instructions and download. Once you have downloaded it, I will walk you through the instructions with screenshots for the Plant 3D update. Here is the link to the document: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-update-the-tags-after-changing-the-tag-format.html

Updating the Plant3D Line Number Tags

For the Plant Side, I will walk you through the aforementioned document from Autodesk. After you click on the link above, download the Zip file PnPTagRebuilder 2017-2027.zip to your hard drive. It should be in your Downloads folder, but I suggest moving it to a location where you can find it more easily. For me, that is my S Drive on my network. The file name will most likely change in future versions, but so far that has been just changing to the latest version (ie: PnPTagRebuilder 2017-2024.zip to PnPTagRebuilder 2017-2027.zip).

Right-click on the zip file and select Extract All.

I want mine to have a shorter path, so I changed the location to the root of my S Drive and then selected Extract.

PLEASE NOTE: I have left instructions and screenshots for the PnPTagRebuilder 2017-2024.zip because the 2027 version only includes a single DLL file, which will only work with 2027. I assume that this will be corrected by Autodesk in the near future, but I have yet to hear from Autodesk regarding this. The DLL file must match the version, which is why the previous zip files contain DLL files for every version since 2017. I will remove this note once this file has been updated. Until that time, it will only work with 2027.

Once extracted, you will see several different versions. You must use the correct version in Plant 3D.

On the Source Files tab of the Project Manager, Open any Plant 3D Drawing. You must be in a Plant 3D Model with Piping to proceed.

First is an image showing the out-of-the-box Data Manager Pipe Run Component Line Number Tags.

At the Command Prompt, enter NETLOAD.

In the Choose .NET Assembly dialog box, locate the correct version of the PnPTagRebuilder.dll that you extracted above and open it. In my case, I am working in AutoCAD Plant 3D 2024, so I need the 2024 version of the routine.

In the Utility Warning dialog box, select OK.

At the command prompt, enter UpdateP3dTagValues.

You can do them all if you like by entering 0, but the more you do and the larger the project, the longer it will take. All you need for the sake of this article is Option 4 for Line Number.

Enter 4 for the Tag Format to rebuild and press ENTER. Once it has been completed, you will receive a message of how many tags were processed, letting you know it was successful.

You may need to select the Refresh button in the Data Manager, but you can see the results in the Data Manager under Pipe Run Component. This image shows a variety of components that have been updated on multiple drawings.

The Plant 3D Drawings should be updated and ready to go. Save and Exit your drawings and move on to the P&ID’s.

Updating the P&ID Line Number Tags

On the Source Files tab of the Project Manager, Open any P&ID Drawing. You must be in a P&ID Drawing to proceed.

First is an image showing the out-of-the-box Data Manager Pipe Line Group Tags.

As stated earlier, I have never gotten successful results from the Autodesk PnPTagRebuilder.dll with the P&ID’s. However, I still suggest you give it a go before moving on with the instructions below. Who knows? You may get different results than I have, or maybe the routine will be improved at some point and actually work on the Line Number Tags. It does appear to work on everything else. The only difference in the above instructions is the command for P&ID’s is UpdatePIDTagValues, and the option for Line Numbers is 5. If you try this and do not receive a message regarding the number of tags processed, then move on to the steps below.

In the Data Manager, set it to P&ID Project Data and select Pipe Line Group, and then select the Export Button.

In the Export Data dialog box, set it to Active node only. Enter the file name and location that you would like to save the Excel file to, then select OK. I am taking the default into My Documents.

Using Windows File Explorer, locate the Excel file you just created, right-click on it and Copy, then right-click and Paste so that you have two copies of the file.

Since I am doing this exactly like this article, the Pipe Line Group Tag Format was set up with two Sub-Parts, which equals ?-?. Modify one line in the Tag column to ?-? and then use Copy and Paste to modify every line in the Tag column to ?-?. Then save and exit Excel.

Back in the Data Manager in Plant 3D, still set to P&ID Project Data and Pipe Line Group, select the Import Button.

In the Import From dialog box, select the Excel file that you modified. Now select Open.

In the Import Data dialog box, select OK.

In the Data Manager, the entire Tag column is highlighted in yellow. Select the Accept All button.

In the Plant 3D – Excel Import dialog box, Select Update.

Once Successful, select Close.

Note that the Tag has been changed as well as the Line Number and Service. If the Tag does not equal ?-? then something went wrong, and you will need to Import the Excel file again. Some versions require that you open every P&ID drawing in the Project for this to work, but it will not work if the Tag is not ?-?.

Now follow the same procedure to Import the Excel file that you Copied – but Do Not Jump ahead without reading the next steps.

This time in the Data Manager, Select every entry in the Tag column and Reject just the Tag column. You can use your Shift key to select them all from top to bottom.

Now with Line Number and Service still highlighted in Yellow, but not Tag, Select Accept All. Then, in the Plant 3D – Excel Import dialog box,  select Update followed by Close once it is successful.

The P&ID Pipe Line Group Tags have now been updated to the new format in the entire project.

The P&ID’s are now updated.

Next Steps:

Want to get more out of AutoCAD Plant 3D and P&ID? Our hands-on training goes beyond the basics to help you work more efficiently and avoid common pitfalls. Browse upcoming classes or contact us to find the right training for your team.

Whether you're an architect, engineer, or BIM manager, working with Revit® cloud models on Autodesk Forma® Cloud (formally ACC) offers tremendous advantages — real-time collaboration, centralized data, and streamlined project delivery. But cloud-based worksharing also introduces new ways for things to go wrong. Even experienced Revit users can fall into habits that cause slow performance, synchronization failures, and worst of all, model corruption.

At Hagerman & Company, we work with AEC teams every day and see the same pitfalls come up time and again. Here's a rundown of the most common Revit cloud model mistakes — and what you can do to avoid them.

1. Opening Cloud Models the Wrong Way

The Mistake: Clicking File > Open to open an AFC workshared model — just like you'd open a local file.

Why It's a Problem: When you open a cloud model using the standard Open button, you bypass the proper AFC workflow entirely. This can lead to synchronization errors, detached local copies, and coordination breakdowns across your team.

The Fix: Always open AFC workshared models from the Home screen by selecting Autodesk Projects. This is the only supported method for cloud worksharing and ensures your local copy stays properly connected to the cloud central model.

💡 Pro Tip: Another recommendation if you have been in the model for a few days, refresh the model before opening it. Make this a standard part of your team's onboarding checklist, so no one defaults to old habits.

2. Not Syncing Frequently Enough

The Mistake: Going hours — or entire days — without synchronizing with the central model.

Why It's a Problem: Infrequent syncing means your local copy drifts further from the rest of the team's work. When you finally do sync, you're more likely to encounter conflicts, errors, or lost work. It also means other team members can't see your progress.

The Fix: Sync with Central regularly — at a minimum, every few hours, and always before stepping away from your workstation. Before leaving for lunch or ending your day, sync and relinquish your worksets so teammates can access those elements.

💡 Pro Tip: Use the Worksharing Monitor to keep an eye on who's syncing and how often.

3. Ignoring Workset Management

The Mistake: Leaving worksets disorganized, borrowing elements without purpose, or failing to relinquish worksets when done.

Why It's a Problem: Poor workset management creates bottlenecks. If team members hold onto worksets they're no longer actively editing, others are locked out. This kills productivity and creates unnecessary friction in collaborative workflows. Also, opening all worksets all the time can affect performance.

The Fix:

• Organize worksets logically at the start of the project (by discipline, floor, or system — whatever fits your workflow).
• Relinquish all worksets and elements when taking a break or ending your session.
• Avoid opening worksets that aren't needed for your current task.
• Open workset in views as needed.

4. Using Detached Mode for Collaboration Tasks

The Mistake: Opening the model in Detach from Central mode when you actually need to be working in the live cloud model.

Why It's a Problem: Detached mode prevents synchronization entirely. Any work done in this mode exists in isolation and cannot be pushed back to the cloud central model. It's appropriate for archiving or troubleshooting — not active collaboration.

The Fix: Reserve Detach mode for specific scenarios like model auditing, creating backups, or investigating issues. For all active project work, always open directly from Autodesk Projects on the Home screen.

5. Working Across Different Revit Versions

The Mistake: Some team members upgrade to a new Revit version mid-project while others remain on the previous version.

Why It's a Problem: Revit is not backward compatible. If even one person upgrades the cloud model to a newer version, everyone else must follow — or be locked out. This can cause serious disruption for ongoing projects with multiple collaborators.

The Fix: Establish a clear version policy before the project begins. All team members and external collaborators must use the same Revit version. Plan version upgrades carefully, ensuring all active project work is complete before making the switch. Use the AFC Home screen to confirm version alignment across your team.

6. Neglecting Model Health — Warnings, Bloat, and Corruption

The Mistake: Ignoring Revit warnings, stuffing the model with high-detail families, or failing to regularly purge and audit.

Why It's a Problem: A bloated, warning-riddled model slows everything down — opening, syncing, navigating. As errors accumulate, Revit becomes increasingly unstable and may eventually be unable to recover. According to Autodesk's own guidance, corruption can be introduced during editing sessions and silently compound with every save.

The Fix:

• Audit the model periodically — at least once a week, or more often on fast-moving projects. The Audit function clears problematic data and serves as an early warning system.
• Purge unused families and elements to keep file sizes manageable.
• Use Level of Development (LOD) standards so families are only as detailed as the current project phase requires.
• Review and resolve Revit warnings regularly rather than letting them stack up.
• Ensure at least 5 GB of free hard disk space is available on local machines — Revit needs room to write temporary files during sync operations.

7. Linking Models Incorrectly

The Mistake: Linking reference models through incorrect methods, or not understanding how AFC handles linked files.

Why It's a Problem: Linked models behave differently in a cloud worksharing environment than in a traditional file-based setup. Using the wrong linking method can result in broken links, coordination failures, or models that teammates can't resolve.

The Fix: Understand the specific linking workflows that AFC supports. When linking a Revit model hosted in AFC, use the proper AFC path rather than a local or network path. Assign linked models to dedicated worksets for easier management and troubleshooting. If a linked file causes issues, isolate it by closing its workset and reloading links one at a time.

8. Publishing Too Many Sheets at Once

The Mistake: Attempting to publish a large number of sheets simultaneously when printing or exporting from a cloud model.

Why It's a Problem: Publishing an excessive number of sheets in a single operation can significantly slow the process and cause errors — sometimes requiring you to start over entirely.

The Fix: Batch your sheet publishing into smaller, manageable sets. Prioritize and publish only what's actively needed, rather than bulk-exporting the full sheet set in one go.

9. Skipping Regular Revit Updates

The Mistake: Running an outdated version of Revit without the latest updates and fixes applied.

Why It's a Problem: Autodesk regularly releases updates that address known corruption triggers and stability issues. Skipping these updates means you're working with known vulnerabilities that Autodesk has already fixed.

The Fix: Keep Revit up to date by installing the latest available updates for your version. Check Autodesk Access for a list of the current updates recommended for your software, security, and licensing. This is one of the simplest steps you can take to protect model integrity.

10. Skipping Team Training on Cloud Workflows

The Mistake: Assuming that because team members know Revit, they automatically know how to work in a cloud worksharing environment.

Why It's a Problem: Cloud worksharing introduces workflows, tools, and behaviors that are distinctly different from traditional local or network-based models. Without proper training, even skilled Revit users will make the mistakes listed above — often repeatedly.

The Fix: Invest in targeted training for your team on AFC and Revit cloud workflows. Understanding why the rules matter — not just what they are — is what makes the difference between a team that struggles and one that collaborates efficiently.

At Hagerman & Company, we offer Revit and Autodesk Construction Cloud training designed for real-world AEC workflows. Our Solutions Engineers work alongside your team to implement best practices, troubleshoot issues, and help you get the most from your Autodesk investment.

Final Thoughts

Cloud-based Revit workflows are powerful, but they reward teams that are disciplined and well-trained. Most of the mistakes above aren't the result of carelessness — they're the result of habit, assumptions carried over from older workflows, and a lack of formal guidance.

The good news? Every one of them is preventable.

If your team is struggling with performance issues, sync errors, or model corruption in your cloud Revit projects, Hagerman & Company is here to help. From custom training and project model support to BIM Workflow Process Assessments, we help AEC firms build better habits and better outcomes.

Contact Hagerman & Company to learn how we can support your Revit cloud workflows.

AutoCAD® Plant 3D ships with a companion utility that many users either never notice or quickly set aside after a frustrating first attempt: the Report Creator. This webcast is dedicated entirely to that tool — showing what it can actually do, why the out-of-box experience undersells it, and how custom reports can eliminate hours of manual work in spreadsheets.

Why Not Just Use the Data Manager?

The Data Manager is built for entering and viewing project data. You can export it to a spreadsheet — but the result is raw, unformatted data with no layout control, no grouping, and no calculations. Every time, you're back in the spreadsheet setting up formulas and columns from scratch.

The Report Creator takes the same data and turns it into a finished deliverable: a formatted bill of materials, parts list, specification sheet, drawing list, etc. You configure the layout once, then run it in two clicks. Output can be exported to PDF or Excel among other file formats and shared with anyone — project managers, estimators, vendors, customers — no Plant 3D license required.

What the Out-of-Box Reports Get Right (and Where They Fall Short)

Plant 3D ships with a set of preconfigured reports: equipment list, valve list, instrument list, weight reports by line number and by object, center-of-gravity reports, a 3D parts report, and a drawing list. They're a reasonable starting point — but each has real limitations worth knowing before you write the tool off:

• The equipment list shows blank weight fields even when weights are filled in the Data Manager. The report is simply mapped to the wrong property.
• Weight reports have inconsistent decimal formatting and excessive whitespace — a modest dataset can balloon to 30+ pages.
• The 3D parts report counts bolt sets, not individual bolts. Estimators still have to do that math themselves.
• The drawing list's Revision column never populates — a known gap with no workaround in the off-the-shelf report.
• An equipment list that correctly maps to weight properties, pulling data that was always there.
• A 3D parts / BOM report with tighter formatting and a calculated bolt count — no post-processing needed.
• A drawing register that pulls revision data by mapping to an alternate property, solving the blank revision column issue.
• A line number report with an optional runtime filter, so users can run it for the full project or select specific lines.

These aren't reasons to abandon the tool. They're reasons to move past the defaults.

Custom Reports: What's Actually Possible

The bulk of the webcast demonstrates custom reports built to address these gaps directly. Starting from an existing report — or from scratch — you can control column layout, grouping, subtotals, decimal precision, and even inline calculations. A few examples from the session:

A Few Limitations to Know

Runtime filter parameters — where users choose specific values each time they run a report — don't persist when the report definition is saved and reopened. Autodesk has this in the development pipeline; the webcast covers a workaround in the meantime.

Data flow is also one-directional. Reports pull from Plant 3D — you can't push data back from a report into the drawing database. Anything that needs to appear in a report has to be entered in the project first.

Watch the Recording

The full webcast walks through each report live, including the build process behind the custom examples. If you're ready to get more out of the data already in your Plant 3D projects, it's worth an hour of your time.

PLC documentation, schematics, and panel layouts are tightly connected—but in many controls workflows, they’re created and maintained separately. That separation forces engineers to manually coordinate tags, addresses, and references across drawings, increasing the risk of errors and making revisions harder than they need to be.

AutoCAD® Electrical approaches this differently. By embedding electrical intelligence into the design environment, it automates many of the relationships between schematics, PLC I/O, and panel layouts. Instead of relying on manual updates, the software keeps related information synchronized as designs evolve.

This article looks at AutoCAD Electrical automation for these core controls engineering tasks and why it matters as projects grow in complexity.

Automating PLC I/O Documentation from the Start

Documenting PLC I/O is one of the most time-consuming and error-prone parts of controls design. In plain CAD workflows, engineers often track I/O assignments in spreadsheets or manually enter addresses into drawings, then update multiple documents when changes occur.

AutoCAD Electrical reduces this effort by treating PLC I/O as structured data rather than static text. Engineers can define PLC modules, addresses, and signals once, then generate documentation automatically. As I/O points are added, removed, or modified, related drawings update with them.

This approach helps teams:

• Reduce manual data entry across schematics
• Maintain consistency between PLC data and drawings
• Make late-stage I/O changes without cascading errors

Because PLC information is stored as data, not disconnected notes, AutoCAD Electrical supports a more reliable and flexible documentation process.

Keeping Schematics Intelligent and Connected

Schematics are the backbone of controls design, but their value depends on how well information is maintained across revisions. In generic CAD environments, relationships between coils, contacts, and devices must be tracked manually, which becomes increasingly difficult as drawings multiply.

AutoCAD Electrical automates many of these relationships. Parent-child connections, cross-references, and wire numbers are managed by the software, not the user. When a change is made in one location, related references update automatically across the project.

This intelligence allows controls teams to:

• Copy and modify circuits without retagging everything by hand
• Maintain accurate cross-references across large drawing sets
• Reduce time spent checking drawings after revisions

The result is a schematic workflow that supports change instead of resisting it.

Linking Panel Layouts to Schematic Data

Panel layouts are where electrical designs become physical, and mismatches between schematics and layouts often surface late (during fabrication or installation). When layouts are created independently, keeping component tags, wiring, and terminal information aligned requires constant manual effort.

AutoCAD Electrical for control panel design helps reduce these risks by linking panel layout documentation to schematic data. Components placed in schematics can be represented in panel layouts with consistent tags and descriptions, helping ensure alignment between logical and physical design.

By maintaining this connection, teams can:

• Catch layout conflicts earlier in the design process
• Reduce rework during panel build
• Confidently revise designs knowing related data stays aligned

This integration is especially valuable on projects with frequent revisions or tight fabrication timelines.

Why Automation Matters as Projects Scale

Automation isn’t just about saving time on individual tasks—it’s about maintaining control as complexity increases. As drawing counts grow and changes become more frequent, manual coordination quickly becomes a bottleneck.

By automating PLC documentation, schematic relationships, and panel layout alignment, AutoCAD Electrical reduces the cumulative effort required to manage revisions. Engineers spend less time reconciling information and more time designing systems that meet functional requirements.

This shift becomes critical for teams delivering larger, more complex controls projects on tight schedules.

How Hagerman & Company Helps Teams Apply Automation Effectively

While AutoCAD Electrical provides powerful automation capabilities, realizing their full value depends on how they’re implemented. Without proper setup, standards, and training, many teams underutilize PLC tools, schematic intelligence, or layout workflows.

Hagerman & Company helps controls engineering teams apply AutoCAD Electrical automation in practical, scalable ways. From configuring PLC libraries and schematic standards to aligning panel layout workflows and training teams, Hagerman focuses on turning built-in capabilities into measurable improvements.

If your organization is looking to reduce manual PLC documentation, improve schematic accuracy, or better connect panel layouts to design data, Hagerman can help you build an AutoCAD Electrical workflow that supports automation from start to finish!

Many controls engineering teams still rely on plain AutoCAD®  for electrical design—not because it’s ideal, but because it’s familiar. Over time, that familiarity can mask inefficiencies that quietly slow projects down, increase error risk, and make revisions harder than they need to be.

To better understand the real impact of tool choice, an independent productivity study was conducted comparing plain AutoCAD and AutoCAD Electrical’s productivity across common controls design tasks. The results were striking. When performing the same electrical design activities, Autodesk users completed tasks 80–95% faster on average using AutoCAD Electrical. These weren’t edge cases or advanced workflows—they were everyday tasks that controls engineers perform on nearly every project.

This article breaks down what the study measured, why the productivity gap exists, and what the findings mean for controls teams evaluating whether AutoCAD Electrical is worth the investment.

How the Productivity Study Was Conducted

The Autodesk productivity study was designed to compare plain AutoCAD and AutoCAD Electrical as fairly as possible. An independent consultant performed a series of tests using the same hardware, the same user, and the same sample projects. The goal was not to showcase advanced features, but to measure how efficiently each tool handled common electrical design work.

The study evaluated 10 typical controls engineering tasks, including:

• Inserting and modifying electrical symbols
• Retagging circuits and wire numbers
• Managing cross-references across drawings
• Creating PLC I/O documentation
• Generating bills of materials and reports
• Symbol insertion and wiring, where smart symbols automatically connect, align, and break wires
• Wire numbering and component tagging, which update automatically across drawings
• Cross-referencing, where parent-child relationships between coils and contacts are maintained without manual tracking

For each task, the study tracked the number of commands used, the number of user interactions (clicks and keystrokes), and the total time required to complete the work in both environments. By holding variables constant, the results highlighted differences caused by the software itself—not user skill or workflow choices.

Where the Biggest Productivity Gains Came From

The study consistently showed that AutoCAD Electrical outperformed plain AutoCAD because it eliminates manual coordination work. In a generic CAD environment, electrical intelligence has to live in the engineer’s head. Tags, wire numbers, and relationships must be tracked, updated, and verified by hand.

AutoCAD Electrical automates much of that coordination. Productivity gains were especially strong in areas such as:

In one example from the study, retagging a copied circuit required dozens of manual edits in plain AutoCAD. The same task in AutoCAD Electrical was completed with a fraction of the interactions, resulting in time savings of more than 80%. Across the full set of tasks, the reduction in manual commands directly translated into faster completion times and fewer opportunities for error.

Why Plain AutoCAD Falls Behind at Scale

Plain AutoCAD can handle basic drafting, but it was never designed to manage electrical relationships across large, evolving projects. As drawing counts increase and revisions become more frequent, the effort required to keep everything aligned grows exponentially.

The study highlighted a key difference: AutoCAD Electrical reduced the total number of commands used by roughly two-thirds across tasks. Fewer commands mean fewer chances to miss a step, mislabel a component, or forget an update. Over the life of a project—or across dozens of projects—that difference adds up quickly.

This is why many teams feel fine using plain AutoCAD on small jobs but struggle as project complexity increases. The tools simply aren’t built to scale with modern controls engineering demands.

What the Study Means for Controls Engineering Teams

The takeaway from the productivity study is not that plain AutoCAD is “bad,” but that it places an increasing burden on engineers as projects grow. AutoCAD Electrical shifts that burden to the software, allowing engineers to focus on design intent rather than manual coordination.

For teams evaluating AutoCAD Electrical, the 80–95% productivity range provides a realistic benchmark—an indication of where time savings come from when electrical intelligence and automation are fully utilized.

How Hagerman & Company Helps Teams Apply These Findings

Understanding the potential of AutoCAD Electrical’s ROI is only the first step. Real-world results depend on how the software is implemented, standardized, and adopted by your team. Without the right setup and workflows, it’s easy to underutilize the very features that drive the biggest gains.

Hagerman & Company helps controls engineering teams bridge that gap. As an Autodesk Platinum Partner, Hagerman works with organizations to evaluate current workflows, implement AutoCAD Electrical effectively, migrate legacy data, and establish standards that support long-term efficiency. The goal isn’t just faster drawing, it’s a controls engineering environment that scales with your business.

If you’re considering AutoCAD Electrical or want to better understand how these productivity gains apply to your organization, Hagerman’s controls engineering team can help you turn study results into measurable improvements. Contact us today!

If you have ever opened an Autodesk Fusion® design only to find a timeline cluttered with hundreds of unnamed features all stacked under the top-level browser node, you have already felt the pain that Rule #1 is designed to prevent.

In this clip from our webcast, Inside Autodesk Fusion's New Intent-Driven Design Workflow, we break down one of the most fundamental and most frequently skipped best practices in Fusion: always start a new component before you start designing.

What Is Rule #1?

Rule #1 is simple to state and transformative in practice: as soon as you start a new design, create a new component first, then do your work inside that component.

That means every sketch, extrusion, revolve, hole, and feature you create belongs to a specific component rather than the top-level design file. Once that component is complete, you step back up to the appropriate level in the browser, create another component, and repeat.

Why Does It Matter?

Without Rule #1, all of your features from every part in your assembly pile up under the top-level browser node. The result is a single, undifferentiated timeline that becomes nearly impossible to navigate as your design grows in complexity.

When you follow Rule #1, each component owns its own timeline. Need to edit a hole? Activate the component where that hole lives, and its isolated timeline appears, showing only the features that matter. This makes editing faster, troubleshooting cleaner, and collaboration far more manageable.

The practical payoff includes:

• Focused timelines: Activating a component shows only its features, reducing noise
• Easier edits: You always know exactly where a feature lives
• Cleaner assemblies: Internal and external (linked) components stay clearly separated
• Scalable designs: The workflow holds up whether you have 5 components or 50
• Make component creation your first click on any new design, before you open a sketch
• Name your components as you go. Unnamed components are almost as hard to navigate as no components at all
• Before adding any new geometry, check the browser to confirm the right component is active (bold text = active)
• Review the timeline color. Purple means you are inside a component

Internal vs. External Components

Rule #1 applies equally to internal components (built directly within your design file) and external components (linked in from separate Fusion files). In the chair example shown in the clip, the chair base and cylinder are internal components, while the swivel casters are linked in from external files. Keeping these clearly organized at the component level ensures your overall design file stays readable and maintainable.

This also unlocks one of Fusion's most powerful capabilities: reusable external components. When you link in a component from an external file, any updates made to that source file propagate through every design that references it, which is a significant advantage in iterative or multi-project workflows.

The Purple Timeline: Your Visual Cue That Rule #1 Is Working

One useful indicator mentioned in the clip: when you have a component activated and are working inside it, Fusion shows a purple-tinted timeline rather than the full design timeline. That color shift confirms that new features will be owned by the active component and not the top level. If you are ever unsure whether you are working in the right context, check the timeline color before you start sketching.

Building the Habit

Like most best practices, Rule #1 is easy to understand and easy to forget, especially when you are in the middle of a design and just want to get something modeled quickly. A few habits that help:

Watch the Full Recording

This clip is just one piece of a much larger conversation. In the full recording of Inside Autodesk Fusion's New Intent-Driven Design Workflow, we dig into how Fusion's newest workflow tools are changing the way engineers and designers approach their work.

Whether you are new to Fusion or looking to level up your workflow, the full webcast is packed with practical guidance you can apply right away.

Artificial Intelligence is rapidly transforming how manufacturers design, build, and deliver products. But while the promise of AI is compelling—automation, predictive insights, and faster decision-making—its success depends entirely on the quality and structure of your underlying data. If your product information is incomplete, inconsistent, or siloed across disconnected systems, AI initiatives will struggle to deliver meaningful value.

To fully leverage AI, manufacturers must first establish a strong data foundation. This is where Vault ™ PLM plays a critical role—connecting engineering data, standardizing processes, and creating the structured environment AI requires to perform effectively.

AI Is Only as Powerful as Your Data

AI tools rely on accurate, accessible, and well-structured data to generate insights and automate workflows. In many organizations, however, product data is fragmented across CAD files, spreadsheets, emails, and disconnected systems. This creates significant barriers to AI adoption, including:

• Inconsistent or duplicated data
• Limited visibility across departments
• Manual processes that introduce errors
• Lack of lifecycle and change tracking

Without a centralized and reliable data source, AI cannot deliver trustworthy results. Establishing a single source of truth is the first—and most critical—step.

Moving from File Management to Data Management

Traditional data management approaches often focus on files—where they are stored and how they are versioned. While this is important, AI requires a deeper level of structure. It needs data that is organized, contextualized, and connected.

Vault PLM enables organizations to move beyond file-based workflows to item-centric processes. Instead of managing files in isolation, teams can manage products as structured items with associated properties, relationships, and lifecycle states.

This shift allows organizations to:

• Standardize product definitions
• Track changes with full traceability
• Link engineering data to business systems
• Enable consistent data reuse across projects

Connecting Engineering to the Business

One of the biggest challenges in preparing for AI is bridging the gap between engineering and the rest of the organization. Engineering data often exists in isolation, making it difficult for operations, procurement, and leadership teams to access and use it effectively.

Vault PLM connects engineering data to broader business processes by integrating with ERP and other enterprise systems. This ensures that product information flows seamlessly across departments, creating a unified data environment.

With this level of connectivity, organizations can:

• Improve collaboration between teams
• Reduce manual data handoffs
• Ensure consistency across systems
• Enable better decision-making with complete information

Standardizing Lifecycle and Change Management

AI thrives on structured processes. When workflows are inconsistent or undocumented, it becomes difficult for AI to interpret and act on data.

Vault PLM introduces standardized lifecycle and change management processes, ensuring that product data is governed, traceable, and reliable.

By implementing controlled workflows for releases, revisions, and change orders, organizations can:

• Maintain data integrity over time
• Reduce errors and rework
• Capture valuable historical insights
• Provide a clear audit trail for AI analysis

Building a Foundation for AI-Driven Workflows

Once data is structured, connected, and governed, organizations can begin to unlock the true potential of AI. With Vault PLM as the foundation, AI can be applied to a wide range of use cases, including:

• Predictive analytics for product performance
• Automated classification and data enrichment
• Intelligent search and knowledge discovery
• Process optimization and workflow automation

Rather than struggling with disconnected data, teams can focus on leveraging AI to drive innovation and efficiency.

Start with the Data, Not the Technology

While AI continues to evolve, the organizations that will benefit most are those that prioritize their data foundation today. Investing in structured, connected, and lifecycle-aware data is not just a prerequisite for AI—it is a strategic advantage.

Vault PLM provides the framework needed to prepare your business for AI, enabling you to move from fragmented information to a cohesive, intelligent data environment.

Watch the Full Recording

To explore these concepts in more detail and see how Vault PLM supports AI-ready workflows in practice, watch the full webcast recording.

The Challenge: Fragmented Facility Information

For many campus facilities teams, document management remains a fragmented process—spread across shared drives, legacy systems, paper archives, and institutional knowledge. The result is familiar: difficulty locating accurate drawings, inconsistent standards, and valuable time lost searching for information instead of acting on it.

A Purpose-Built Approach for Facilities Teams

RedEye provides a purpose-built, cloud-based platform designed specifically for facilities document control and drawing management. Unlike traditional systems that were adapted for facilities use, RedEye is engineered around real-world workflows—prioritizing accessibility, usability, and data integrity for both technical and non-technical users.

Establishing a Single Source of Truth

A modernized approach enables organizations to establish a single, reliable source of truth for facility documentation. Drawings and documents are centralized, version-controlled, and easily searchable, allowing teams—from engineers to maintenance staff—to quickly access the most current information. This reduces risk, improves coordination, and ensures decisions are based on accurate data.

Operational Impact and Long-Term Value

Organizations that have modernized their document management strategies are seeing measurable benefits, including improved operational efficiency, faster response times, and greater confidence in their data. By removing friction from how information is stored, accessed, and maintained, facilities teams are better equipped to support ongoing campus operations and long-term planning.

Building a Scalable Foundation

As campuses continue to evolve, implementing a scalable and user-friendly document management solution is no longer optional—it’s foundational. Platforms like RedEye help transform document management from a persistent challenge into a strategic asset, enabling teams to work more efficiently and make better-informed decisions.

Watch the Full Webcast

See how RedEye works in practice and hear real-world perspectives from organizations that have modernized their facilities' document management approach.