> For the complete documentation index, see [llms.txt](https://help.auxalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.auxalia.com/plant-tools/white-papers/not-placed-objects-npo-with-pdm-and-psd-for-bim360acc-or-vault.md).

# Not-Placed Objects (NPO) with PDM and PSD for BIM360/ACC or Vault

This chapter describes if and how Not-Place Objects (NPOs) can be used with PlantDataManager and PlantSpecDriven.

### <mark style="color:blue;">What are Not-Placed Objects (NPOs)</mark>

NPOs are objects which do not exist in a drawing. NPOs can be created by PlantSpecDriven or PlantDataManager. PlantReporter can use them in a report/list/data sheet.

Details about NPOs can be found under [Not-Placed Objects](/plant-tools/plantdatamanager/how-to-use/plantdatamanager/not-placed-objects.md).

### <mark style="color:blue;">Where are they stored</mark>

Up to released PDM 4.3.0.1971 and PSD 4.3.0.1971 the NPOs were stored in the ACPProcessPower.dcf database in your project under the ACPlantTools folder. Or in the \[Project]\_ACPProcessPower database when using SQL-Server.

Essentially the ACPProcessPower.dcf is a copy of the structure of the ProcessPower.dcf (P\&ID Database). In addition there are some tables needed for the NPOs.

With the introduction of PlantTools 5.0.0.x the ACPProcessPower.dcf is integrated into the ProcessPower.dcf. Existing ACPProcessPower.dcf databases will be migrated when opening a project in a PlantTools or Plant 3D.

### <mark style="color:blue;">Using NPOs with PlantSpecDriven</mark>

NPOs are used in PlantSpecDriven to add typically fasteners like gasket or stub-ends to the flanges or valves in you P\&ID drawing. The NPOs can be seen in the PSD panel.

![](/files/msTWpkahsXi2ZzU0NxA1)

In PDM those NPOs appear in blue.

![](/files/nmfDOBcP6ghVIqfRqliE)

### <mark style="color:blue;">Using NPOs with PlantDataManager</mark>

If you are working on a Vault or BIM360/ACC project with PlantDataManager, we had to disable the NPO functions. The reason for this is, that we currently cannot check in the NPOs you create in PDM.

![](/files/EndYVwpuyRFTHjCtbK3l)

We will check if Plant 3D 2023 has any improvements for that or if we can find a work around.

Restrictions do NOT apply for regular projects (not using Vault or BIM360/ACC).

### <mark style="color:blue;">Using AUDITPROJECT on NPOs</mark>

NPOs created by PlantSpecDriven will not be removed by AUDITPROJECT.

Up until PDM 4.3.0.1971 you could create NPOs and how them related to a drawing or not. During the migration of previous projects to PlantTools 5.0.0.x, all NPOs will be migrated.

However, NPOs with no relation ship to a drawing will be removed when you execute AUDITPROJECT.