Marg Autodesk Fusion Lifecycle PLM

everything worked..I guess? You can add functionality, which is really nice. I went to a PLM meeting in Novi, MI which i thought was really helpful.

Its confusing, slow, non-intuitive. When I would search for one upper level SKU, I would get everything related to it, all the old revisions, packaging-everything. It was terrible. I get that filters help, but no way should it be that crazy

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

Once you get used to it, it is fairly easy to navigate. It allows the company to have all product information in one location instead of scattered through our shared drive.

When the sales pitch is that you can do everything yourself - you don't need to be in IT or need IT's help. Its not true. We needed help, lots of it, which ends up costing a lot of money. Might have well have invested the money up front to have it set up the way you wanted. However, that is not what was presented to us.

What problems are you solving with the product? What benefits have you realized?

The high level of customization and 'you can pretty much do anything you want' vibe of the whole application. For instance, the way in which any team's workflows can be directly translated to a block diagram is very powerful, and the scripting engine allows for some pretty deep add-on customization.

The robust API makes custom integrations easy for even an untrained programmer like myself.

The admin module (workflow editor, item details editor, etc.) is very easy to use and overall a great user experience. This is often overlooked in systems like these.

The concept behind workspaces and items and their relationships is easy to explain to just about any user, allowing them to cook up their own workspaces if they request them.

The entire document/attachment system. There's no bulk file imports, and everything is limited to a one-to-one item to file relationship. Large workarounds and scripts must be created to accommodate some very simple document management operations. Support has indicated that this is changing, but I've seen nothing in the last year.

The sourcing tab is very limited, and bulk import/export are not easy to accomplish (e.g. BOM scrubbing).

While attractive, the classification module is completely useless - the data cannot be exported, reported on, or displayed in BOMs.

Generally, although the scripting module powerful, it's clear that it's being used overused (out of the box) to write in features that ought to be easier to administrate (e.g. workflow approvals, custom part numbering)

It's also lacking out of the box integration with other Autodesk tools, even ones explicitly named Fusion!

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

The support from the AD team. FLC has a great potential to drive a majority of company business processes as the de-facto business process engine, but the application really needs to be stable.

The modern UI version is buggy and unstable. The incorporation of cPDM with FLC is extremely flawed in security and relationships. The interfaces between cPDM, Autodesk Drive, and FLC are not consistent. The document viewer has multiple bugs and the UX can be cleaned up. The UI/UX while better than the classic can be much more intuitive. Why does it take so many clicks??? The mobile app does not allow you to view attachments so it is almost worthless. System speed is also an issue. Using the system in China and Europe can be challenging. Browser compatibility is limited.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

All the information for a program is located centrally and dependent relationships can be created to link critical items.

It is slow and my group (certification) is not fit as well by the templates as engineering is - apparently updating the code for our group is not easy enough to make it worth while (mainly document flow types).

.

What problems are you solving with the product? What benefits have you realized?