Plantek

Each project in COS contains one Plantek object. The object has one attachment, a zip file containing the content of the Plantek directory in the project. The Plantek directory contains all models used in any of the blocks in the project.

When you add a Plantek model to one of the blocks, it will be copied from the central Plantek directory (part of the hull centre) to the project.

• If the file does not exist in the project yet, it will be added as a new file.

• If the file already exists in the project and it is equal to the file in the library, the file is not replaced.

• If the file already exists but the content of the file is different from the file in the library, the project file is replaced.

Multiple users at different sites are able to add Plantek data at the same time and work offline on Plantek, because you can add a Plantek model in the central Plantek directory without having to check out the block. Therefore, only Get and Save are available for Plantek in the Check Out/In dialog. However, when you want to use the Plantek model in a project, the block needs to have been be checked out previously.

Hull keeps track of new models added to the project, and shows the status in the Data State column in the Check Out/In dialog. Every time a new model is copied to the planteksymbols directory inside the project directory, the data state for Plantek shows either Local changes or Local and remote changes. The latter means that in addition to your local changes that need to be saved to the COS server, there are also changes waiting to be downloaded from the COS server. The data state shows Up-to-date when there are no changes and Out-of-date when there are changes on the COS server.

When saving the data to the COS server or getting the latest data from the COS server, the contents of the project Plantek directory are merged with the files included in the attachment for the Plantek object in COS. In case of a conflict, the file with the most recent timestamp prevails. For more information on saving and getting the data via the Check Out/In dialog, see Check out and check in operations.