+49 231 935015 0 info@plm-planet.com
Select Page

Search results keywords:

 

Retain revision history when withdrawing a revision

Retain revision history when withdrawing a revision

Message from: September 2021

In order to evaluate revisions that have been withdrawn and thus ensure traceability, a functionality has been created with which the revisions that have been withdrawn and their working copies can be displayed in DC Document Controlling.

 

 

 

Our customers had the problem that documents created by DMS, which were manually entered into the model via the AutoCAD reference manager, could no longer be found by the DMS functions. To solve this problem, a function was implemented that searches for the document in the system path, reloads it into the DMS and can thus rewrite the ACAD reference.

Furthermore, a new topic ADT (AutoCAD Architectural Desktop) was introduced for the use of Navisworks for controlled application editing in DMS.

Navisworks revision in DMS

Navisworks revision in DMS

Message from: May 2021

The development of a new Planet Plugin for Navisworks provides an extension of the functionalities in the DMS revision process with regard to the use of PLM NAV. This makes it possible to display different trades with different revision statuses.

 

Until now, only the Navisworks NWF work files were available in DMS. With the help of the new Navisworks plugin, a current NWD file is now created in the DMS revision procedure and stored in the revision directory. This is done via an external control from DMS with the help of a special revision dialogue.

Type assignment of the ToDo procedure with storage of the reports for revision or version

Type assignment of the ToDo procedure with storage of the reports for revision or version

Message from: November 2020

As part of the ToDo procedure for the administration of L & L reports, the possibility was created to file reports in DMS for existing versions or revisions without having to go through a revision procedure in DMS.

 

 

 

For this purpose, the template for the ToDo procedure has been extended in such a way that a type assignment can now be made for the ToDo (0 = no function; 1= must be a revision or version; 2= revision procedure). E.g. if Type = 1 is set, it is only possible to select a version or revision pdf. The prerequisite for this is the corresponding rights for the administration of L & L reports.

PLM Office Post from DMS

PLM Office Post from DMS

Meldung vom: July 2020

A direct connection from DMS to PLM Office Post has been created, so it is possible to exchange documents between DMS and Office in a controlled manner, both inbound and outbound.

 

 

 

DMS is a system for the revision and versioning of technical documentation as well as management via DCC and various search functionalities (e.g. according to KKS). For correspondence, Office Post's transaction processing is optimised; recipient and sender data can be managed via Office Variables. For ease of use, a Post Wizard has been created for the controlled transfer of documents via DCI from DMS to Office Post and vice versa. Controlled means that before sending, a revision is created in DMS and further processing is blocked in Office.

PLM DMS can now insert analogue stamps into PDF documents right-controlled

PLM DMS can now insert analogue stamps into PDF documents right-controlled

Meldung vom: November 2019

The project phases (e.g. basic engineering, construction, detail engineering) available in the Document Control Module for controlling the project execution, through which the revision procedure is controlled, offer extensive configuration options for a project.

To reduce configuration work when creating new projects, this module has been extended with a selectable copy function.
Now DC phase configurations can also be transferred to other projects and systems in a dialogue-driven manner.

PLM DMS - DC Phasen Controlling combines document phase and document purpose

PLM DMS - DC Phasen Controlling combines document phase and document purpose

Meldung vom: November 2019

Project processing (revision procedures) can be divided into a fixed sequence in DocWorkState, such as basic engineering, detail engineering, etc. Subordinate document purposes, such as "for review", "for approval" or "for attestation", etc., describe what is to happen to the document, also in a fixed order.

Within the framework of DC Phase Controlling, the DocWorkState now becomes the "DC Phase" and the document purpose becomes the "Action" package. For each "Action" package there is a ToDo template that controls the revision process. This is assigned to the action package.

The combination of a DC phase with the different "action" packages results in a DC structure tree.
The DC phases link the individual steps in the project flow with the PLM project management and ensure that the stored documentation has passed through the individual processing steps of the revision procedure in a controlled manner during the project flow.

PLM DMS - archiving of correction processes in the revision-release procedure

PLM DMS - archiving of correction processes in the revision-release procedure

Meldung vom: October 2019

The revision procedure in PLM DMS can now archive the completed correction processes.
All audit steps passed in the revision procedure can generate correction processes with the corresponding information such as comments and / or redlining.
After the document has been released, all files created in this context are combined in a PDF. This PDF also contains bookmarks for the to-dos associated with the correction process.

Each todo is accompanied by a text file containing further information on the history such as date, signature, comments etc. This text file is used as header for the individual redlining files in the overall PDF.

PLM DMS - Extension of the DMS revision release procedure

PLM DMS - Extension of the DMS revision release procedure

Meldung vom: October 2019

The PLM DMS revision release procedure has been enhanced with additional functionalities such as project processing phases and the document purpose.

This ensures a controlled workflow in the processing and testing of documents along the project processing phases. The testing and verification run is stored in a redlining ....RL.PDF document in DMS.

A PLM ToDo regulates the process of document testing in a template.

  • A - Accepted
  • B - Accepted with remark
  • C - Refusals
  • Sign
  • lRedlining
With these new possibilities, testing processes can be documented in terms of what and who triggered them.
en_GBEnglish (UK)
Powered by TranslatePress »