& Construction

Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
& Manufacturing

Professional CAD/CAM tools built on Inventor and AutoCAD
Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
In this lesson, we’ll introduce you to projects in Upchain, including the information you can access within a project, the workflow of a project and the difference between public and private projects.
In this video we will discuss projects in Upchain, the information available in a project and the difference between public and private projects.
Transcript
00:08
What is a project in Upchain?
00:10
Well, a project in Upchain contains all the work, effort, assignments, members, and materials, such as your bill of materials,
00:18
business processes, documents, project plans, and project and team members related to your product.
00:27
Essentially, all of the data connected to your product will be contained within the project.
00:33
None of the objects we discussed can exist without being tied to a project.
00:38
Projects are the foundation of your product development process in Upchain.
00:43
Once a project is created, you can organize all of the information related to your product.
00:49
A unique feature of projects in Upchain is the Workflow.
00:53
The Workflow dictates the lifecycle of the project. When a project is first created, it is placed in a draft state.
00:60
When a project is in a draft state, only the creator of the project can see it.
01:04
It should also be noted that creator can only see the project in the web app at this point.
01:10
They will not be able to see it in any of the plugins.
01:13
Once the project is activated and the workflow started, the project moves into an active status.
01:19
In this state, the project is now visible to project members or teams that have been added.
01:24
The project can also be added to the Favorites list and have it show on the main dashboard.
01:30
The next step in the Project Workflow is Closed or Archived.
01:34
This step in the workflow is selected when the project is finished or paused for an extended period of time.
01:40
When the project is in this state, everything connected to the project is in a "read only" state. No changes can be made to the project.
01:48
From there, you can either select Finish Workflow, which moves the project to a completed state and therefore cannot be reopened,
01:55
or reopen the project and move it back into an Active state.
02:00
Therefore, you can work on the project once again.
02:08
Once a project has been created, you need to determine if it will be a Public project or a Private project.
02:15
A Private project is only visible to the project team members or teams,
02:20
while a Public project is available to all registered users in your tenant.
02:25
Any project that you have been given access to will be visible through the web app and any of the plugins that you're using.
02:31
So now that we know what a project is, our next step is to go ahead and create one.
Video transcript
00:08
What is a project in Upchain?
00:10
Well, a project in Upchain contains all the work, effort, assignments, members, and materials, such as your bill of materials,
00:18
business processes, documents, project plans, and project and team members related to your product.
00:27
Essentially, all of the data connected to your product will be contained within the project.
00:33
None of the objects we discussed can exist without being tied to a project.
00:38
Projects are the foundation of your product development process in Upchain.
00:43
Once a project is created, you can organize all of the information related to your product.
00:49
A unique feature of projects in Upchain is the Workflow.
00:53
The Workflow dictates the lifecycle of the project. When a project is first created, it is placed in a draft state.
00:60
When a project is in a draft state, only the creator of the project can see it.
01:04
It should also be noted that creator can only see the project in the web app at this point.
01:10
They will not be able to see it in any of the plugins.
01:13
Once the project is activated and the workflow started, the project moves into an active status.
01:19
In this state, the project is now visible to project members or teams that have been added.
01:24
The project can also be added to the Favorites list and have it show on the main dashboard.
01:30
The next step in the Project Workflow is Closed or Archived.
01:34
This step in the workflow is selected when the project is finished or paused for an extended period of time.
01:40
When the project is in this state, everything connected to the project is in a "read only" state. No changes can be made to the project.
01:48
From there, you can either select Finish Workflow, which moves the project to a completed state and therefore cannot be reopened,
01:55
or reopen the project and move it back into an Active state.
02:00
Therefore, you can work on the project once again.
02:08
Once a project has been created, you need to determine if it will be a Public project or a Private project.
02:15
A Private project is only visible to the project team members or teams,
02:20
while a Public project is available to all registered users in your tenant.
02:25
Any project that you have been given access to will be visible through the web app and any of the plugins that you're using.
02:31
So now that we know what a project is, our next step is to go ahead and create one.
In this video we will discuss some of the different ways you can use projects in Upchain and how they can be time based or open ended.
Transcript
00:08
Projects, as you may recall, can have a lot of information contained within them.
00:14
This information can be things like the bill of materials, business processes, documents, project plans, and team members.
00:21
Not every project in Upchain will contain all of these things.
00:25
While many of the projects you create in Upchain will be focused on product development,
00:30
projects can be used for more than just product development.
00:34
The best way to think about projects in Upchain is like a container.
00:38
It is a central repository of information. All of the things listed here can be part of any project.
00:46
So, let's take a closer look.
00:57
The first example we are going to look at is a Standard Parts Library.
01:01
The purpose of this project is to provide a list of standard parts,
01:05
that can be easily accessed when building out specific products in a project.
01:11
This project is a public project, meaning it is available to every registered tenant user.
01:19
Let's start by looking at the BOM.
01:21
We can see here there's a list of parts organized by different types including washers, anchors, and nuts.
01:29
Since this is a public project, these items will appear in the Advanced Search for all registered tenant users.
01:37
Looking at this list of items, we can see this is not a typical BOM structure you would see as part of a product driven project.
01:47
This is one of the benefits of projects in Upchain is you can use them to store whatever information you may need.
01:55
If we navigate over to the Project Management section for this project,
02:01
we can see there are no tasks and no Gantt chart created.
02:06
This is because this particular project does not require this information since, again, it is a standard parts library.
02:14
One thing to note about this project is that the workflow is used to place it in an active state.
02:20
This particular project will stay in this active state indefinitely.
02:30
This is just one example of how to use projects in Upchain.
02:34
Another way would be using the same concept to create a document library as we see here.
02:40
This would provide all tenant users access to documents approved by your company to be used in product driven projects.
02:50
You can see here a list of documents that have been published and available for tenant users.
02:58
So, now that we have taken a look at a couple different ways we can use projects in Upchain,
03:04
let's take a closer look at a project with a product driven example.
03:11
The main way you will use projects, of course, in Upchain is to develop products.
03:16
These projects will be set to Private and only project team members will have access.
03:24
So, we're going to take a closer look at this drone project that we've recently started working on,
03:29
to see how it differs from the standard parts library.
03:33
We can see in our drone project there is a project plan.
03:38
This was used by the project manager to help assign tasks to the project team and keep the project on track.
03:45
This is useful for this particular project, but as we saw would not be useful for the standard parts library.
03:52
As we navigate through the project, we can see the BOM structure is very different from the one in the standard parts library.
04:00
Again, this BOM structure is product specific.
04:04
We see all of the items required to create a finished product which is expected for this kind of project.
04:11
The same can be seen under the Documents section.
04:18
The documents listed here are specific to the project and support the development of the drone.
04:32
The business processes will contain more than just a change request to move the items into a released state.
04:42
We can see here there are investigation requests as well.
04:47
One other difference between our drone project and the standard parts library project is the team members.
04:56
Each team member provides a specific set of skills to help develop this particular product.
05:06
Also, by only having specific team members, this project is only accessible to them since this is a private project.
05:15
The project manager can also assign specific tasks to each team member or the team as a whole.
05:23
Lastly, this project will utilize the entire workflow associated with it.
05:29
Once this project is released and completed, the project manager will move the project into a closed state.
05:37
This indicates that work has been completed on this project and no further changes or updates are required.
05:44
Another difference between our drone project and the standard library of parts is the timeline.
05:51
The drone project has a specific timeline associated with it as we see again in the project plan,
05:57
while the standard parts library did not have a project plan and will remain available over time.
06:04
So we have seen some examples of what we can do with projects in Upchain. I would encourage you to think about how you can use projects.
Video transcript
00:08
Projects, as you may recall, can have a lot of information contained within them.
00:14
This information can be things like the bill of materials, business processes, documents, project plans, and team members.
00:21
Not every project in Upchain will contain all of these things.
00:25
While many of the projects you create in Upchain will be focused on product development,
00:30
projects can be used for more than just product development.
00:34
The best way to think about projects in Upchain is like a container.
00:38
It is a central repository of information. All of the things listed here can be part of any project.
00:46
So, let's take a closer look.
00:57
The first example we are going to look at is a Standard Parts Library.
01:01
The purpose of this project is to provide a list of standard parts,
01:05
that can be easily accessed when building out specific products in a project.
01:11
This project is a public project, meaning it is available to every registered tenant user.
01:19
Let's start by looking at the BOM.
01:21
We can see here there's a list of parts organized by different types including washers, anchors, and nuts.
01:29
Since this is a public project, these items will appear in the Advanced Search for all registered tenant users.
01:37
Looking at this list of items, we can see this is not a typical BOM structure you would see as part of a product driven project.
01:47
This is one of the benefits of projects in Upchain is you can use them to store whatever information you may need.
01:55
If we navigate over to the Project Management section for this project,
02:01
we can see there are no tasks and no Gantt chart created.
02:06
This is because this particular project does not require this information since, again, it is a standard parts library.
02:14
One thing to note about this project is that the workflow is used to place it in an active state.
02:20
This particular project will stay in this active state indefinitely.
02:30
This is just one example of how to use projects in Upchain.
02:34
Another way would be using the same concept to create a document library as we see here.
02:40
This would provide all tenant users access to documents approved by your company to be used in product driven projects.
02:50
You can see here a list of documents that have been published and available for tenant users.
02:58
So, now that we have taken a look at a couple different ways we can use projects in Upchain,
03:04
let's take a closer look at a project with a product driven example.
03:11
The main way you will use projects, of course, in Upchain is to develop products.
03:16
These projects will be set to Private and only project team members will have access.
03:24
So, we're going to take a closer look at this drone project that we've recently started working on,
03:29
to see how it differs from the standard parts library.
03:33
We can see in our drone project there is a project plan.
03:38
This was used by the project manager to help assign tasks to the project team and keep the project on track.
03:45
This is useful for this particular project, but as we saw would not be useful for the standard parts library.
03:52
As we navigate through the project, we can see the BOM structure is very different from the one in the standard parts library.
04:00
Again, this BOM structure is product specific.
04:04
We see all of the items required to create a finished product which is expected for this kind of project.
04:11
The same can be seen under the Documents section.
04:18
The documents listed here are specific to the project and support the development of the drone.
04:32
The business processes will contain more than just a change request to move the items into a released state.
04:42
We can see here there are investigation requests as well.
04:47
One other difference between our drone project and the standard parts library project is the team members.
04:56
Each team member provides a specific set of skills to help develop this particular product.
05:06
Also, by only having specific team members, this project is only accessible to them since this is a private project.
05:15
The project manager can also assign specific tasks to each team member or the team as a whole.
05:23
Lastly, this project will utilize the entire workflow associated with it.
05:29
Once this project is released and completed, the project manager will move the project into a closed state.
05:37
This indicates that work has been completed on this project and no further changes or updates are required.
05:44
Another difference between our drone project and the standard library of parts is the timeline.
05:51
The drone project has a specific timeline associated with it as we see again in the project plan,
05:57
while the standard parts library did not have a project plan and will remain available over time.
06:04
So we have seen some examples of what we can do with projects in Upchain. I would encourage you to think about how you can use projects.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement.May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.