Cloning Items: Playing the Game with Additional Owners

Additional Owners MarkupIn a previous post, we covered how to set up your Autodesk PLM 360 tenant to clone an item to a specific state in a workflow. If your organization makes use of the Additional Owners field and requires cloning it as well, you’ll need to do further configuration & scripting. Watch this video to understand the steps for cloning Additional Owners!
Continue Reading

Multiple Project Tracking in Autodesk PLM 360

Autodesk PLM 360 LogoAutodesk 360 Graph of Projects - Tiny

If your company manages high-volume, high-turnover projects, you may need a better method to keep track of all the projects; especially when it comes to knowing which ones are blocked or impeded. We recently helped a company configure Autodesk PLM 360 to store and manage their project data by:

  • Leveraging a custom-built workflow
  • Graphing the data to track the status of multiple (40+) projects in a single view

Continue Reading

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.
Continue Reading

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.  Continue Reading

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.
Continue Reading

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.
Continue Reading

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!
Continue Reading