Migrate the Few or Migrate the Masses: Import What You Need, How You Need to Autodesk PLM 360

wild-geese-589983_1280 SubsetAnother request we hear often is to migrate existing items to Autodesk PLM 360, bringing them in at whatever workflow state they are at—which more often than not is further down the line than the initial state. This is common when you want to migrate existing Change Orders, for example.
Read the rest of this entry »

DriveWorks 12 Calculation Tables: It’s Like Excel, Only Better

Calculation Tables ImageA long time ago, in an automation far, far away… It is a period of engineering calculations under the flag of Microsoft Excel. Microsoft Excel has enjoyed many years of use and continues to be a weapon of choice for automators and engineers alike. Read the rest of this entry »

Cloning Items: Getting the Right STATE of Mind

yoga-clip-art-1729876Well, we may not be able to help you get to any particular meditation state, but today we’ll delve into getting to certain workflow states. Do you ever find yourself in this scenario in your Autodesk PLM 360 tenant? You might have an item at a particular state in a workflow (say, state 3 out of 9) and you need to clone the item and make a very small change. When the change is of a type that previous workflow states do not need visited, you want the new item to pop to the same workflow state as the original item.  Read the rest of this entry »

Import Legacy Items & BOMs into Autodesk PLM 360 with Revisions

Autodesk PLM 360 LogoImporting data from your legacy system into your cloud-based Autodesk PLM 360 tenant is a request we hear often. If, for example, you have existing items and bills of materials (BOMs) that are released in the legacy system at certain revisions, you will most likely need them replicated in Autodesk PLM 360. There is a built-in import tool to do just that (among other things). However, there are several ways this tool can be used, and not every way will get you all your desired results. In this video we will guide you through the best approach and usage of the tool for importing legacy data.
Read the rest of this entry »

Highlights from Accelerate 2015 with Autodesk PLM 360


From Autodesk veeps to customer stories and open-air networking, Accelerate 2015 on Sept 1-2 inspired, catalyzed, and educated. Highlights included stunning images from Autodesk PLM 360 customer BAC, PLM analysts trying to avoid fraught buzzwords in the panel discussion, and a sneak peek at Autodesk cloud PDM and “evented web” integration for Autodesk PLM 360.
Read the rest of this entry »

SOLIDWORKS Add-ins and Macros affected by Windows Update

Logo_SolidWorks_LogoIf you have installed the Microsoft Windows Update KB3072630 released on July 15, 2015, you may find some issues with SOLIDWORKS 2015 macros and add-ins. Several groups within Razorleaf have found issues with SOLIDWORKS 2015 macros and add-ins as a result of installing this update. This affects add-ins from SOLIDWORKS Toolbox to SOLIDWORKS Simulation to DriveWorks and potentially SOLIDWORKS EPDM and ENOVIA SmarTeam. Read the rest of this entry »

A Close Look at Non-Released Statuses in Autodesk PLM 360

Autodesk PLM 360 LogoWorking Versions, the Working Revision Identifier, the WIP Revision, and the Unreleased Lifecycle…Do you know what these non-released statuses are, when they occur, how to differentiate between them, and how to manage them in Autodesk PLM 360? We are often asked to clear up confusion that users and administrators have on this subject. So an explanation of the “what”, “when”, and “how” of the non-released statuses, and more, is what we are covering today!
Read the rest of this entry »