Fusion and Project Based Workflow

[O.Tan]

Hi,
So as Fusion functions slowly come in and improve, I would like to know if AD has any plans or solutions for the given mockup situation below.

As a simple recap, in a larger companies, a single project will be split up across multiple users who are specialised in their own field. Right now, Fusion project allows those invited into the project, full access to the files, the only way to limit this behaviour for now is by having the other party to view the relevant project via live review or a special link.

However in a larger environment, this is not good enough, mainly cause of situations like:
1. Intellectual Property - Contract Designer and Intern Designer shouldn’t be able to see parts of the project where it’s confidential and they’ll only be able to access what they’re given to accomplish.
2. File permission level - To prevent other irresponsible parties from copying the whole design, only people of certain level (like the Project Manager) is allowed to export (to Fusion archive or any files like STEP), Designer probably is only allowed to import and delete but not export files and other users is only able to import files into the project.
3. Unneeded Information - For people who will do Visualisation aspect of the project, they’ll only need access to the part of the project that’ll be visible, they don’t really need access or authority to modify or edit the part.
4. Only relevant data needed - For those doing Fabrication, they only need to know the components, material, drawings and quantity needed to be manufactured, most of the time they don’t need access to the full assembly and even if they did, they’ll likely require the designer to be present to clarify few things hence they can use existing solution (live review and such)

So those are some examples I can think of, there’s probably more so for those reading this, feel free to add your case scenarios.

Best Regards.

[Mike.Grau]

Hi @O.Tan,

Thank you for pointing out to that.

Yes, this is a really important topic on the list. Especially when it comes to international distributed projects.

Have you may tried to set up a hierarchy like the chart within Fusion 360 Team = A360 Team ?

https://fusionteam.autodesk.com/

It just came to my mind if we may could set up a chart like that with multiple team hubs.

Every project group would have his own hub and every Sub-Team would have his own hub as well?

It would be great if you could share this within our IDEA station.

Thanks,

[TrippyLighting]

http://www.autodeskfusionlifecycle.com/

There will be a panel discussion about Systems Integration at AU.

If @anewenergy will be a panel member I am almost certain that's what he'll be talking about (you beat me over he head, Pat, if that's not true 😉 .

In other words, the need is clearly there and is also recognized by he Fusion 360 team.

[O.Tan]

Apologies for the late reply, 2 weeks passed by so quickly.

I checked both links and what's the difference between the two? Though Autodesk Fusion Lifecycle looks more comprehensive and do both of them work with Fusion 360 out of the box? As it looks more like for users who use Inventor and such.

I guess this wont be part of Fusion Ultimate subscribers features? I wouldn't mind setting up an IdeaStation post, but is it going to be about what I posted or about the multiple hubs that you mentioned? 

And I wont be able to attend AU as I'm living in Malaysia, will there be any video links once it's done?

[charegb]

Hi Omar,

Great question. Apologies for missing it on answer day!

You already got a couple of answers around Fusion Lifecycle and Fusion Team so I wanted to bring it all together.

Our intention is that if your using Fusion for anything other than a hobby, you should be working in a Fusion Team hub because it allows a central admin (or team of admins) a way to manage permissions and own the data for the company, and not in any individual user's account. 

We have just introduced a new viewer role in Fusion Team this week that allows you to give a new user read only access to a project so that they can observe and comment but not edit or export and data. We will continue to add more roles in the future and eventually plan to allow admins to create custom roles where you can define exactly what that role can and can't do. We are also going to let admins define if users create public share links in a project or if they should be blocked all together.

Our teams are also working on cross project distributed designs. This will allow you create projects that you can invite the contractors or interns to and let them work on certain parts of a design and then reference those designs in to assemblies in other projects with a more restrictive set of permissions. Of course this could lead to a lot of projects being created. To help manage those projects we are also going to introduce the ability to organize projects in a hierarchy using tags. 

Next year we are also planning on a more granular view of the data in a design (model, CAM, Sim, Renders etc.) and potentially roles could tie in here to let you define another user's ability to only work on CAM etc.

All of this is still part of work in process data management. The next step is Lifecycle management. FLC (Fusion Lifecycle) can use Fusion Team hubs to manage the life cycles of the designs. You can track product data, revisions and releases, Bill of Materials, change requests etc.

Additionally I appreciate the feedback we are getting from early previewers of branch/merge like you, so as we bring some of this new functionality online, we will definitely be reaching out to have you try it and give feedback.

Thanks,

Bankim