> 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/plantspecdriven/collaboration-workflows/general-workflow.md).
# General Workflow
This chapter describes the general workflows when using PlantSpecDriven with Collaboration project.
Configurations Files of PlantSpecDriven
These are the files used by PlantSpecDriven 1.**PlantSpecDriven.xml** These files exist locally (%PROGRAMDATA%\ACPlant Consult\PlantTools\PlantSpecDriven\PlantSpecDriven.xml) and in each project (\[PROJCTFOLDER]\ACPlantTools\PlantSpecDriven\PlantSpecDriven.xml). Locally the status of the toggle buttons of the PlantSpecDriven Palette are stored.
In the project, all settings from the Settings dialog are stored.
2.**PaletteSettings.xml** The \[PROJCTFOLDER]\ACPlantTools\PlantSpecDriven\PaletteSettings stores the setup of the PlantSpecDriven tree which are defined in the **Tree Settings** dialog.
3.**SpecDrivenLinkConfiguration.Collection.xml** The \[PROJCTFOLDER]\ACPlantTools\PlantSpecDriven\SpecDrivenLinkConfiguration.Collection.xml holds a list of available sdc files in the project. 4.**\*.sdc files** The \[PROJCTFOLDER]\ACPlantTools\PlantSpecDriven\\\*.sdc files are the configuration files of PlantSpecdriven in your project. 5.**Spec Template File** The Spec Template file is set in the spec-driven configuration and is typically pointing to a pipe spec in the project. In this case the Spec Template file will not be handled, because it is already in the project.
6.**AttributeFlowTaskList.xml** The \[PROJCTFOLDER]\ACPlantTools\PlantSpecDriven\AttributeFlowTaskList stores the pending AttributeFlow tasks. 7.**Files in Project Manager**
Opening/Downloading an existing Collaboration project
This is handled if the project doesn't exist in the work folder yet and everything needs to be downloaded from scratch. 1.PlantSpecDriven.xml => DOWNLOADED 2.PaletteSettings.xml => DOWNLOADED 3.SpecDrivenLinkConfiguration.Collection.xml => DOWNLOADED 4.\*.sdc files => DOWNLOADED 5.Spec Template file => DOWNLOADED 6.AttributeFlowTaskList.xml => DOWNLOADED
Sharing an existing project (which is already setup for PlantSpecDriven) to ACC
When sharing a project with PlantSpecDriven files the following files are handled: 1.PlantSpecDriven.xml => CHECKED IN 2.PaletteSettings.xml => CHECKED IN 3.SpecDrivenLinkConfiguration.Collection.xml => CHECKED IN 4.\*.sdc files => CHECKED IN 5.Spec Template file => CHECKED IN
Opening Main Dialog
If you open the Main Dialog of PlantSpecDriven the following files are handled: 1.SpecDrivenLinkConfiguration.Collection.xml => CHECKED OUT
Closing Main Dialog
If you close the Main Dialog of PlantSpecDriven the following files are handled: 1.SpecDrivenLinkConfiguration.xml => CHECKED IN Deleted \*.sdc files will be removed from the SpecDrivenLinkConfiguration.Collection.xml. Added or imported \*.sdc files will be added to the SpecDrivenLinkConfiguration.Collection.xml.
Opening Settings Dialog
If you open the settings dialog of PlantSpecDriven the following files are handled: 1.PlantSpecDriven.xml => CHECKED OUT
Closing Settings Dialog
If you close the settings dialog of PlantSpecDriven the following files are handled: 1.PlantSpecDriven.xml => CHECKED IN
Opening Tree Settings Dialog
If you open the Tree Setting dialog of PlantSpecDriven the following files are handled: 1.PaletteSettings.xml => CHECKED OUT
Closing Tree Settings Dialog
If you close the Tree Setting of PlantSpecDriven the following files are handled: 1.PaletteSettings.xml => CHECKED IN
Deleting a Link Configuration
If you delete a link configuration the following files are handled: 1.\*.sdc file => DELETED This includes the removal of the \*.sdc file from the work folder as well as the removal on BIM360. 2.The \*.sdc file name will be removed from the SpecDrivenLinkConfiguration.Collection.xml But the file will be checked in only when the Main Dialog will be closed. If all \*.sdc files are deleted, then the SpecDrivenLinkConfiguration.Collection.xml will be deleted when the Main Dialog will be closed. 3.Spec Template file => UNLINKED The file will only be removed from the MISC.dcf to not appear anymore under \Related Files\Spec Sheets.
Creating a new Link Configuration
If you add a new link configuration the following files are handled: 1.\*.sdc file => CHECKED IN 2.Spec Template file => CHECKED IN 3.SpecDrivenLinkConfiguration.Collection.xml => COMMITTED
Editing an existing Link Configuration
If you edit (not renaming) a link configuration the following files are handled: 1.\*.sdc file => CHECKED OUT
Closing Wizard
If you edit a link configuration the following files are handled: 1.If link configuration was renamed then Old \*.sdc => DELETED New \*.sdc => CHECKED IN Rename file name in SpecDrivenLinkConfiguration.Collection.xml 2.The SpecDrivenLinkConfiguration.Collection.xml will later be checked in when closing the Main Dialog
Adding a Link Configuration without using the PlantSpecDriven Wizard
Sometimes it is more convenient to just add existing \*.sdc file(s) from another project without using the Wizard. This is how you do this: 1.Open your collaboration project in AutoCAD Plant 3D 2.Open the PlantSpecDriven Main Dialog This checks out the SpecDrivenLinkConfiguration.Collection.xml. 3.Copy the \*.sdc file into the \[PROJECTFOLDER]\ACPlantTools\PlantSpecDriven folder Maybe you need to adapt the path to the spec template file. 4.Open the SpecDrivenLinkConfiguration.Collection.xml with a text editor 5.Add the \*.sdc file name to the SpecDrivenLinkConfiguration.Collection.xml file 6.Save and Close the SpecDrivenLinkConfiguration.Collection.xml file 7.Click on **Refresh** in the Main Dialog This will read the SpecDrivenLinkConfiguration.Collection.xml and the newly added \*.sdc file again so you see if there are any error in the file. 8.Close the Main Dialog This checks in the SpecDrivenLinkConfiguration.Collection.xml and the newly added \*.sdc file.
Adapting a Link Configuration without using PlantSpecDriven Wizard
Sometimes it is more convenient to adapt the configuration directly in the \*sdc file without using the Wizard. This is how you do this: 1.Open your collaboration project in AutoCAD Plant 3D 2.Open the PlantSpecDriven Main Dialog 3.Select the configuration you want to modify 4.Click on the **Edit** button to open the Wizard This checks out the \*.sdc file. 5.Click on **Cancel** to close the Wizard The \*.sdc file will still be checked out. Do not close the Main Dialog yet. 6.Open the \*.sdc file under \[PROJECTFOLDER]\ACPlantTools\PlantSpecDriven in a text editor 7.Make your modifications in the file and save and close it 8.Click on **Refresh** in the Main Dialog This will read the \*.sdc file again so you see if there are any error in the file. 9.Close the Main Dialog This checks in the \*.sdc file.
Double-Clicking or Open DWG in PlantSpecDriven Tree
If you **double-click** or use **Open** in the PlantSpecDriven Tree the following files are handled: 1.\*.dwg file => CHECKED OUT
Open DWG Read-Only in PlantSpecDriven Tree
If you use **Open Read-only** in the PlantSpecDriven Tree the following files are handled: 1.\*.dwg file => DOWNLOADED
Double-Clicking on P&ID Line Segment, Inline Assets, Inline Instrument, Equipment, Nozzle in PlantSpecDriven Tree
If you **double-click** on a P\&ID Line Segment, Inline Asset, Equipment or Nozzle in the PlantSpecDriven Tree the following files are handled: 1.\*.dwg file => DOWNLOADED
Using Route/Insert in PlantSpecDriven Tree
If you use **Route/Insert** in the PlantSpecDriven Tree the following files are handled: 1.\*.dwg file => DOWNLOADED
Using Zoom onto P&ID/3D Object in PlantSpecDriven Tree
If you double-click or use **Zoom onto P\&ID/3D object** in the PlantSpecDriven Tree the following files are handled: 1.\*.dwg file => DOWNLOADED
Using Zoom onto P&ID/3D Object in Inconsistency Palette
If you use **Zoom onto P\&ID/3D object** in the PlantSpecDriven Inconsistency Palette the following files are handled: 1.\*.dwg file => DOWNLOADED
Copy values through Inconsistency Palette
If you use **Copy P\&ID to 3D** or **Copy 3D to P\&ID** in the PlantSpecDriven Inconsistency Palette the following files are handled: 1.\*.dwg file => CHECKED OUT
Executing AttributeFlow Task List
If you use Execute Task in AttributeFlow Task List dialog the following files are handled: 1.\*.dwg file => CHECKED OUT
Executing AttributeFlow from Propagation Dialog
If you execute AttributeFlow from propagation dialog the following files are handled: 1.\*.dwg file => CHECKED OUT