TeamCraft (rudalabs) errors

5 recurring problems engineers report in TeamCraft (rudalabs), ranked by impact.

#107 by errors trackedPLMMCADPDM

Recurring TeamCraft (rudalabs) errors, by impact

  1. 1Assemblies uploaded through the web UI or API get no BOM even though the server already scans and matches their part references.PLM · Agent failure · 1 report74
  2. 2In TeamCraft, a revision with no file chosen gets geometry by format rank. On the NIST test assembly with 21 files on one revision, NX ranks first, so the page shows one hex nut's mass, CG and inertia as the whole assembly's, with nothing saying a choice was made. A plausible but wrong number can end up in a mass budget or a flight simulation.MCAD · Agent failure · 1 report74
  3. 3TeamCraft's CAD folder import writes quantity 1 on every BOM line, even when an Inventor assembly places a bolt four times. The reference scan records which files an assembly references and not how often, so the new graph view shows x1 everywhere. SOLIDWORKS, NX and STEP files carry instance counts the server already reads for previews, but the BOM import never used them, and Inventor .iam occurrence data is not decoded at all.PDM · Agent failure · 1 report74
  4. 4For teams like student racing, rocketry and satellite groups that replace a third of 60 members each year, deactivating a leaver leaves their check-outs, draft change orders, pending reviews and manager flag in place, and mostly only an admin can clear them, one object at a time.PDM · Agent failure · 1 report66
  5. 5TeamCraft freezes revisions under a change order and needs every reviewer to approve, but the four-eyes check looks only at the person who created the change order, not at the people who changed the data, an admin can be author and reviewer, and obsoleting or superseding skips review.PDM · Agent failure · 1 report66

How it fails

  1. Agent failure5

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.