Practical tips and insights for engineers, CAD managers and work preparation, on exporting, bills of materials, model management, standardization and saving time.
Three weeks of lead time, four days of actual drafting: where do the other days go? We follow an order from quote to production drawing and show where the time leaks away: waiting, handovers, searching and exporting. Plus a six-step plan to measurably shorten the chain.
Read more →
The shop wants PDF, the laser cutter DXF, the customer STEP. Which format belongs to which recipient, and how do you deliver one package from one revision, with no loose ends? Includes an overview table, a completeness checklist and a fixed approach to handling changes.
Read more →
Eight brackets on the list, twelve in the model: BOM errors stay invisible until a fitter is standing right next to them. These are the five errors that slip through most often, with the cause, the damage and the source-level check for each one, so you catch them before release.
Read more →
A slipped error costs hours, a self-check five minutes. This tick-off checklist covers six blocks: title block, dimensioning, views, parts list, scale and standards. Plus tricks for looking at your own work critically, because you tend to read what you meant to draw.
Read more →
A PDF, a DWG, a DXF and a STEP for every drawing: exporting manually in Inventor is twelve steps you repeat over and over. With Batch Publish you write out your entire set in 1 click, including together with Vault. Read how to save time and avoid errors.
Read more →
Getting the bill of materials out of Inventor and into Excel is often an error-prone quarter-hour of cutting and pasting. Read why that goes wrong and how you solve it with an export where you set the columns and order yourself, fed by iProperties that are correct.
Read more →
Leftover sketches, suppressed parts and an unreadable browser are invisible on your screen, but show up in the bill of materials and on the shop floor. Run through this 8-point checklist before you release an Inventor model, and read how Model Cleaner takes the detective work off your hands.
Read more →
One incorrectly filled iProperty field multiplies through your entire chain: bill of materials, title block, PDFs and ERP. Here is how to structure metadata at the source and enforce consistency with Thundercad's iProperty Menu.
Read more →
Exporting, retyping bills of materials, cleaning up models: each task seems like nothing on its own, but together, repetitive work in Inventor is a cost that appears nowhere on your dashboard. We make those costs measurable with a transparent calculation example.
Read more →
Standardization sounds like something for large departments with a CAD manager and a thick manual. Nonsense. With a small team in particular, you capture agreements smartly by putting the standard into your Inventor tools instead of into a document nobody reads.
Read more →
iLogic is powerful, but building scripts yourself has hidden costs: maintenance, Inventor updates and dependency on a single script hero. A sober comparison between building it yourself and a maintained toolbox such as Thundercad, including a rule of thumb for when to choose what.
Read more →
Vault keeps your data tidy, but it does not publish PDFs and does not fill in iProperties. Read how Thundercad removes the repetitive manual work in your Inventor Vault workflow: from Batch Publish to consistent metadata.
Read more →
A wrong material code costs engineering ten seconds, but costs purchasing a wrong order. Here is how you catch errors at the source, in the Inventor model, not on the purchase order, with Model Cleaner, the iProperty Menu, BOM Export and Batch Publish.
Read more →
Exporting, retyping BOMs, filling in metadata, getting files ready: routine work that adds nothing to your design. We walk through five concrete time-wasters in Inventor and show for each one which Thundercad tool takes the work off your hands.
Read more →
Should we get Vault? Every growing engineering office asks the question sooner or later. Vault solves real problems around versions, collaboration and findability, but asks for administration and discipline in return. An honest decision model with five signals shows when Vault pays off for your team, and when folders with solid agreements still do.
Read more →
The drawing says S235JR, the model says stainless steel: fill in the title block by hand and sooner or later it lags behind reality. Bind every stamp to iProperties, test the template with a smart test part, and the typing checks at every release disappear.
Read more →
"So how much does that save per week?" If you cannot answer that question, your proposal ends up at the bottom of the pile. Build a business case that holds up: a measurement from your own practice, the hourly rate from finance, a sensitivity check in three scenarios and a seven-line outline for the meeting with management.
Read more →
Staring at a progress bar for ten minutes every morning, then waiting for the next file all day long. The real problem is not the load time but the moment. Open your complete working session in one action, park your work when a rush job lands and close everything in a controlled way at the end of the day.
Read more →
Seventeen broken references when opening a single assembly? Usually the culprit is not Inventor but the folder structure underneath. Here is how to set up your workspace, libraries and project file, with an example layout you can copy right away.
Read more →
Between retyping BOM lines and fully automatic synchronization sits a ladder with four rungs. We look at the setup effort and the payoff per level, so you can start small with a structured export and only climb when the current rung really pinches.
Read more →
The product changes with every order, that is exactly what your customer pays for. But structure, metadata, release and issuing are the same each time. Which parts of the process to pin down, which to leave alone, and how to start with a single trial order.
Read more →
On screen every drawing looks fine, on the print next to the saw it suddenly does not. Faint colored lines, clogged hatching and cryptic file names share one cause: export choices nobody ever made deliberately. Set them right once, for every PDF that enters the shop floor.
Read more →
Purchasing wants everything flat, assembly wants to see the build-up and planning orders per module. Three departments, three lists, and Inventor can produce all three. How structured, parts only and first-level differ, who gets which list and how to export them without manual work.
Read more →
Too small and the dimensions fight for space, too big and the fitter stands folding paper next to the machine. Practical rules for sheet size and scale per part type, and the fastest way to fix a wrong choice afterwards without rebuilding the drawing.
Read more →
One checked-out file can bring work preparation to a standstill, yet many Vault environments hold work that has been on someone's name for weeks. Three habits keep the vault reliable: daily check-ins, small batches and one line of comment per version. Plus: finding stragglers and having the right conversation.
Read more →
Every custom field takes thirty seconds to create and years to get rid of. Three test questions tell you which fields deserve to exist, how to clean up existing sprawl and why one managed field list per document type keeps things workable. Including examples that do pass the test.
Read more →
Months of half productivity and a senior who gets interrupted all day: onboarding is the biggest hidden cost of growth. With a prepared first day, standards that live inside the tools, a fixed buddy and jobs that rise in difficulty, a new engineer handles routine work independently within weeks.
Read more →
A rush job in between normally means closing twenty files and hunting them all down again two days later. Quick save parks your complete working session in one go; Quick load brings it back exactly as you left it. Four situations where that is worth gold, from rush orders to Friday afternoon.
Read more →
Before you request a faster PC: the slowness often sits in the model itself. Five usual suspects, from heavy STEP purchased parts to leftover sketches, plus a coarse-to-fine diagnosis order that finds the offender in half an hour instead of an afternoon.
Read more →
Every item exists twice: as a model in Inventor and as a record in the ERP system, and the two drift apart as soon as somebody changes one side. Learn how to give every field one owner, place items without retyping and keep new items from appearing by accident.
Read more →
The change itself takes ten minutes, the aftermath a week: outdated drawings, a lagging BOM and exports already sitting at your supplier. With a fixed sequence of five steps you push a late change through completely and prove that nothing was left behind.
Read more →
The laser cutter asks for DXF, the customer wants DWG, and both mean something slightly different than you think. What really separates the two formats, who needs which file, and why versions and scale cause most of the trouble. After this article you deliver the right file first time.
Read more →
Balloon 14 points at a bearing housing, but item 14 in the list is a retaining ring. Mid-project additions, dropped positions and overridden numbers push the BOM, balloons and ERP out of step. A few hard numbering rules and a quick final check make everything point at the same state again.
Read more →
One model change easily touches four drawings, and the forgotten sheet keeps telling the old truth for months. Here is how to find the complete set of sheets for a changed model, check each one for detached dimensions, views and quantities, and reissue everything in one go.
Read more →
The structure you build in Vault on day one stays with you for years. Choose deliberately between project and product folders, keep libraries separate, keep the tree shallow and pick a naming convention that prevents endless searching. Includes a compact six-branch starter structure as a concrete starting point.
Read more →
The project number changes and suddenly one hundred and forty files need the same new value. Opening them one by one is hopeless. Here is how to update iProperties across a complete assembly in bulk: the right fields, the right selection and a solid check afterwards.
Read more →
Inside your senior engineer's head sits an archive that exists nowhere else: design decisions, customer preferences and the places where the bodies are buried. This notice-period playbook helps you choose what to secure, captures knowledge in the systems themselves and hands over live projects in person.
Read more →
Ten mouse trips per hour to the ribbon feels like nothing, yet adds up to hours every month. This article lists the shortcuts that truly pay off, shows how to arrange the marking menu around your own work and how to build the habit: one key per week.
Read more →
Copying a previous project is the fastest start, and the fastest way to spread old mistakes. A fixed routine keeps your copies clean: know what to take along and what never, clean up right after copying, and update metadata in bulk.
Read more →
The same M12 bolt exists five times in the ERP, each number with its own stock and its own orders. Read how duplicate items arise, what they really cost and how to prevent them for good: enforce search first, make reuse the easiest route and dedupe on a fixed rhythm.
Read more →
The customer's line is down, sales has already said yes and you are in the middle of another project. With a fixed playbook you deliver a rush order fast and right: park current work, scope it tightly, keep a minimum set of checks and issue the package in one run.
Read more →
Everyone asks for a STEP, but that export also hands over your design. What does and does not travel along in such a file, when do you share the complete machine and when only interface dimensions, and what do you agree with the recipient? A practical guide without legal jargon.
Read more →
Purchasing orders buy parts, the workshop makes make parts and standard parts come from bin stock. If that distinction is missing from your BOM, someone ends up sorting with a highlighter at every revision. Record the classification once in Inventor and hand every department its own list.
Read more →
Detailing often eats half the total drawing time, and most of the loss is rework: dimensions jumping, views shifting. With a fixed work sequence, reuse of styles and sheets, and the nerve to stop at what the shop floor actually reads, you take that loss out.
Read more →
Seven states on the whiteboard, three in actual use and files stuck for days: that is how Vault lifecycles often end up. This article describes a minimal setup that covers nearly any small team, assigns each transition to the right people and lists five signals of over-engineering.
Read more →
Encoding material and type in the item number sounds handy, until a design change makes the number lie. This article puts meaningful and meaningless numbering side by side, sorts out issuing without duplicates and offers a migration path that does not start with renumbering everything.
Read more →
Keep recruiting, but waiting for that one candidate is not a plan. Three levers are in your own hands: winning back wasted click hours through automation, putting tasks in the right chair and outsourcing selectively. Including the maths that shows how much capacity is hiding in click work.
Read more →
From the open part to its folder on disk, and to the five folders you visit every day: right now that is a click route through the file explorer every time. Two habits turn it into a reflex, with the maths showing what that saves at dozens of jumps a day.
Read more →
The machine has shipped, but the dataset is still in working state. A fixed closing checklist captures final exports, metadata and revisions, then freezes the lot. That way a service question five years from now is a ten minute phone call, not an afternoon of digging.
Read more →
Wherever systems do not talk to each other, a spreadsheet grows. Handy and flexible, until nobody knows which version is right. The honest story: where Excel is a perfectly good link, where it quietly stacks up risk, and a sober framework for deciding when an integration should take over.
Read more →
Which revision is this, is item 14 make or buy, where is that one drawing? Questions like these point to a missing agreement. Here is how to turn the handover to work preparation into a fixed package with a clear definition of done, so orders stop waiting for answers.
Read more →
Next to the PDF folder sits PDF_old, and next to that PDF_final. Everyone knows it, nobody wants it. With one fixed tree per order and a hard split between work exports and sent packages, everyone can find every file, even a year later and without the author sitting next to them.
Read more →
Every retyped BOM line risks creating a second truth. Follow the route from engineering BOM to purchasing list and ERP order: which fields must travel, where manual work creeps in and what that demands from your model. With concrete release rules that stop import errors early.
Read more →
The same fixes on every drawing: text height, layers, title block. The cause is almost always a thin template. Read what belongs in a good drawing template, how to clean up the sprawl of old templates and how to make sure the whole team works from the same version.
Read more →
Three minutes of scrolling through the folder tree, then calling a colleague anyway: that is Vault as an expensive network drive. Set up the search side and you find any file in seconds. Here is how to use quick search, property queries and saved searches, and why metadata powers it all.
Read more →
The title block says B, the file name says C: so which revision applies? A minimal way of working that lasts: revisions only after release, the iProperty as single source, clear rules for assemblies versus parts and one sentence per change for production and purchasing.
Read more →
Full timesheets, but does all that busyness deliver? Four KPIs that actually show it: lead time from order to release, first-time-right of drawings, share of rework and routine versus design work. For each one you read how to measure it without a registration circus, using data you largely already have.
Read more →
Exporting something twelve times a day means rebuilding your focus twelve times. Batching flips that around: collect similar chores and clear them at two fixed moments in one go. This article shows how to pick those moments, what can wait and what cannot, and which tooling clears the pile in minutes.
Read more →
A feature tree full of Extrusion47 and Fillet112 reads like a log of mouse clicks. With a handful of renamed features, folders per functional block and clear component names, any model becomes readable in minutes. So your colleague, or you three months from now, finds the right feature straight away.
Read more →
Every vendor puts its own box at the center, and meanwhile nobody remembers what PDM, PLM and ERP actually do. This article lines up the concepts calmly, shows where they meet and offers the order that usually works for smaller manufacturers: CAD data first, systems second.
Read more →
The first delivery from an external drafting agency rarely fits your environment out of the box: different title block, empty iProperties, their own naming habits. With a solid intake package, clear metadata agreements and a fixed delivery checklist you prevent that rework and keep a grip on quality, even at a distance.
Read more →
Nobody can work with 'plate_final_v2(1).pdf'. A good naming convention puts drawing number, revision and description in every file name, with iProperties as the single source. This article helps you choose a convention, anchor the source properly and give exports the right name automatically from now on.
Read more →
Two base plates on the wrong material and a motor without mass: together good for hundreds of kilos of difference on the lifting plan. Where weight deviations come from in Inventor, how to get material and density structurally right, and how to sweep a whole assembly in bulk before the BOM goes out the door.
Read more →
Nine views, three sections, and still the welder works out dimensions himself with a marker on the steel. The clearest drawing is rarely the most complete one. Seen from the workbench: what a welder, saw operator and machinist actually read, what distracts, and three before/after examples to make your own sheets more readable.
Read more →
Installing Vault is a manageable job; the move itself is won or lost in the weeks around it. A phased migration plan from practice: clean up and agree on conventions first, then move project by project with a real pilot, and put the old drive on read-only as soon as you can.
Read more →
Only the colleague who did the project still knows where it lives, and that colleague is not always around. How to shift from folder knowledge to finding by properties: the four fields that must be filled, helpers that speed up browsing while folders still rule, and the step towards real search.
Read more →
The saw operator cuts exactly what the list says, but the list came from an outdated revision. Many failure costs on the shop floor start as data errors in engineering. With a simple log and cause codes you trace them back to the source and fix each cause for good.
Read more →
Gut feeling almost always points at the wrong time sink. Tally your click work in Inventor for one week and you see exactly where the hours go: searching, waiting, exporting or rework. Then pick your top three automation candidates based on numbers instead of annoyance.
Read more →
Officially there are three versions of your machine; the server holds eleven. Sprawl grows copy by copy, without anyone ever deciding it. A few ground rules about article numbers, ownership and a strong base keep variants and customer specials manageable.
Read more →
Estimating on gut feeling loses the sharp orders and wins the loss-making ones. The numbers for a better quote are already in your model: weight, material, dimensions and the BOM. Here is how to build an estimate on them that you can verify against actual hours.
Read more →
Two engineers, one machine, one deadline: without ground rules, the last one to save wins. With work areas, fixed owners and a shared folder structure you work on one assembly in parallel without overwriting each other. Even without Vault you can get remarkably far.
Read more →
The shop floor, inspections and assembly crews still ask for paper. Complete packages are exactly where printing goes wrong: half sets, hidden shrinking, forgotten sheets. Here is how to print a drawing package in one run, complete, to scale and in the right order.
Read more →
Inventor does not invent a BOM: it reads your assembly out loud. Every subassembly becomes a line, every level a floor in the list. These guidelines help you build a tree that matches how the machine is built and bought, so purchasing and assembly can use your list straight away.
Read more →
One forgotten drawing stops a press brake or delays a subcontractor. This article gives a fixed working order from large to small, shows where the gaps in a drawing set come from and how to verify, before anything ships, that every manufactured part has its sheet.
Read more →
Files checked out for months, working copies left behind by departed colleagues, projects that were never closed: every vault silts up. This playbook shows how to run a single cleanup day: what to inventory beforehand, the order to clean up in, and the agreements that keep the vault clean afterwards.
Read more →
S235, S235JR and 'steel' are three different materials to Inventor, and it shows in BOMs, weights and purchase orders. This article shows how to clean up the material library, agree on one managed list of names and convert existing models to the right materials in bulk.
Read more →
Over the years every department collects macros, spreadsheets full of formulas and downloaded utilities, each with its own maker and nobody with an overview. This article shows how to take stock of what is running, decide per item between adopting, replacing or retiring, and prevent new sprawl with a lightweight intake process.
Read more →
Friday's five-to-five export is Monday's complaint from the shop floor. Mistakes do not spread evenly across the week: they cluster on moments of haste. This article exposes the mechanism and offers three guardrails that hold under pressure: seconds-long checklists, automation that forgets nothing and firm team agreements.
Read more →
What started with fifty parts has grown into eight hundred in one flat level. Opening takes minutes and nobody dares to drag anything. This article gives you the signals that it is time to split, three logical places to cut, and a step-by-step plan to restructure without wrecking references and drawings.
Read more →
Between the model and the machine there is often a person retyping: cutting lists, drilling files, bending programs. Map the data streams from CAD to the shop floor and see where file formats and a little automation replace the retyping. The sheet cutter is the best-known example, but far from the only one.
Read more →
Daily starts, kanban, shadow boards: the shop floor went lean long ago. In engineering, waste is simply called being busy. Translate the seven classic wastes to CAD work, from waiting for release to unrequested variants, and learn to make them visible and remove them one at a time.
Read more →
One line from the customer and your whole drawing package is in doubt: 'I think you sent the old version'. Seven export mistakes that keep coming back: wrong revision, yesterday's PDF, a DXF at the wrong scale, an empty title block field. For each one the cause, the remedy and a thirty-second last look.
Read more →
A field engineer gains nothing from 'plate left' or a phantom assembly. A service list needs orderable units, marked wear parts and descriptions free of CAD jargon. Here is how to build it from the same Inventor source as your production BOM, and keep it current without maintaining anything twice.
Read more →
The laser cutter calls: bend lines on the cutting layer and a mirrored engraving. Prevent that with a fixed route, from flat pattern checks and bend tables to layer setup, engravings and delivery per material thickness. Every part through nesting in one go.
Read more →
Vault is running, yet everything feels sluggish: documents hang in vague states, everyone has admin rights and people work "just quickly" around the vault. Five pitfalls almost every new team runs into, each with its concrete consequence and the simple way around it.
Read more →
The folder says P8317, the ERP says order 4126 and the title block settles on something else again. Pull one number as a common thread through folders, iProperties, title blocks and export names, and catch up existing work without losing weeks on it.
Read more →
Building a script is fun, but not every task deserves one. With three thresholds, frequency, duration and cost of failure, you decide per task whether automating pays off. Three practical examples show when to build, when to simply do it by hand and when to measure for a week first.
Read more →
Every project starts with the same setup work: creating folders, copying the project file, hunting down standard parts. Capture it once in three starting points: a ready-made folder set, a starter assembly per product type and a short kickoff checklist. Every project then starts ahead.
Read more →
A suppressed feature does nothing, so it draws no attention. But it is not gone: it may or may not count in your BOM, and it likes to break right before a release. Here is how to track down suppressed features and broken references systematically, and how to choose between repairing and deleting for good.
Read more →
Engineering thinks in dimensions and materials, purchasing in articles and lead times. As long as the BOM arrives late and specifications are incomplete, the conversation stays strained. With shared, reliable data purchasing joins earlier and supplier knowledge returns to the design. Four fixed moments make it practical.
Read more →
Discipline is scarce in busy weeks, so quality should not depend on it. A fixed day start sets up your session in one go, a fixed delivery moment closes it down in control. Two quarter-hour routines that make your workday predictable, including the clicking you can automate.
Read more →
Somewhere there is always one more print of revision A: in a drawer, on a clipboard, in a mailbox. Until someone starts cutting from it. Here is how to clean up stale exports and keep things clean: one place to look, overwriting on every export, and firm agreements for packages already out the door.
Read more →
Is frame 4021 in or not? The cut parts arrived a week ago, the welded frame sits by the straightening table and the coated frame is still at the coater. Three stages of the same part each need an identity of their own. Here is how to capture production stages in structure and metadata so purchasing and planning can steer each step.
Read more →
A missing dimension looks harmless, until the press brake stops and the machinist picks up the phone. This article covers the four dimensioning errors that stall production most often, shows how haste, copy work and changed models cause them, and gives you the checking habits that catch them before the drawing goes out the door.
Read more →
Vault runs for years without trouble, and that is exactly why ownership evaporates: backups that fail silently, permissions of colleagues who left, a clogged job server. This article makes the admin role concrete: four responsibilities, a fixed rhythm from weekly to yearly, the hours it realistically takes and what is better left to your Autodesk partner.
Read more →
Everyone has an opinion about data quality, nobody has a number. With a sample of three projects, an export to Excel and three counts you build a baseline in one afternoon: empty fields, spelling variants and duplicates. After that you know which three gaps to close first and you can see whether your measures actually work.
Read more →
The same intern who leaves behind a permanently cleaner dataset with good preparation will quietly wreck your folder structure without it. The difference comes down to three things: tasks that are well-defined, checkable and reversible, permissions that fit a beginner, and templates that shrink the gap between junior and senior work. That way an internship pays off for both sides.
Read more →
Ten minutes a day sounds like nothing, yet over a year it becomes a full working week. Those minutes hide in navigating, exporting, opening and looking things up. Four micro-improvements of a few minutes each collect them for you, and you start today with one simple habit.
Read more →
The same bolt three times in the system and copies quietly drifting apart: library chaos creeps in. Here is how to put standard and company parts in one managed location, read-only for everyone except the administrator, with a clean route for new families and a plan for when someone edits a part anyway.
Read more →
The paper order binder is a snapshot that ages while you watch. Going fully digital does not have to happen in one leap: start with one digital location per order, put screens only where they help, deliberately keep some paper and secure freshness with one hard rule: the digital set is always the current one.
Read more →
Retyping BOM lines into Excel, looking up item numbers in your ERP, hunting for files in Explorer: every switch is a chance for errors. Map the data flows between your systems and let information flow straight from Inventor instead of through the keyboard.
Read more →
The laser cutter wants DXF per sheet thickness, the machinist STEP plus PDF, the coater only a dimensioned sketch. Pin down one fixed delivery profile per subcontractor and build the package in a single run. The question emails stop, and the lead time starts running right away.
Read more →
Walking through the BOM one last time before release feels redundant, until the saw stands still. This fixed five-minute check covers quantities, units, empty fields, duplicate article numbers and balloons, and shows which part you can hand over to your Excel export template.
Read more →
You can no longer see your own mistakes, but a colleague can. Fifteen minutes of reading catches what self-checking misses. This article offers a light review routine: when four eyes are needed, what the reviewer checks, how to record feedback and what to do when there really is nobody.
Read more →
final-v2-REAL is not version control. Even without Vault you can keep a grip on versions: one fixed project structure, tight naming, a read-only release folder and hard rules about copies. Plus an honest answer to where folders stop and PDM begins.
Read more →
Every new part starts with the same empty fields, and empty stays empty until someone complains. Set up your part, assembly and drawing templates once: pre-filled iProperties, default values where possible and visibly open fields where needed. Every new document is complete from minute one.
Read more →
Three requests at once, then two quiet weeks: waves are part of the make-to-order business. Overtime does not have to be the default answer. Learn how to shrink the peak with automation, use quiet weeks to get ahead and agree in advance what can wait when things fill up.
Read more →
Two minutes of startup, a few minutes of loading, several times a day: waiting for Inventor quietly adds up to hours every month. This article covers the levers on the system side: add-ins, templates, your workspace and the habit of opening your whole day in one action.
Read more →
Every model is opened by someone else eventually: through illness, a departure or simply the next revision. Modeling with that successor in mind saves hours of archaeology. On feature order that tells the story, named parameters instead of magic numbers, and the test question that sums it all up.
Read more →
That one ERP, the home-grown planning tool, the customer portal: sometimes custom work is the only route. Such a project does not have to become a permanent headache. Start from the dataset that is already right, define one clear handover, build on a maintained base and agree who manages the integration.
Read more →Try Thundercad free for 30 days and see for yourself how much faster you work, no credit card required.
€30 per user/month or €300 per year (2 months free) · excl. VAT
