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

Management Framework

PLM Management Framework

PLM i4.0 organises the management framework process

The project management framework (PM framework) is a subset of tasks, processes, tools and templates used in combination by the management team to gain insight into the key structural elements of the project in order to initiate, plan, execute, control, monitor and manage the project. Accompany project activities throughout the management life cycle.

In the organisation section you will find all modules that support the engineering process. In addition to the technical project management, the process-relevant data are supplemented here. Supported by defined processes, a room-oriented allocation can be carried out via facility management. All documents relating to the project are recorded either in document management or, if digital documents are not yet available, in file management.

PMS Project Management / Lots and interfaces / Claim Management

PLM-PMS stands for successfully completed projects, which must be smoothly coordinated, especially from the technical side, in order to be profitable. The PLM PMS module is the heart of technical project management, where the framework parameters for successful project management are defined. All project-relevant information can be managed and controlled centrally here.

  • P.Claim management, QM board, DC controlling, trend analysis
  • P.Sub-projects, work packages, tasks, to-dos, lots, delivery limits
  • P.Cost centres, cost units, cost trend, target/actual milestones
  • P.Deadline monitoring, project status report, status report, compressed change & approval procedure (PCS file) converge here

A project is much bigger than the sum of its technical documentation. Why has the release been delayed? Why was a change made? Who initiated this? When was this decision taken? And based on what information? What status did the change request refer to?

  • P.Structuring and monitoring of the project in lots, work packages, delivery limits and interfaces
  • P.Assign contact persons and responsibilities
  • P.Define the logos, project keys, cover and tag sheets to be used
  • P.Release standards, components and catalogues, pipe classes for use in the project
  • P.Cost estimation already in basic engineering for piping, equipment and MSR components
  • P.Define standards for your lists and commissioning protocols
  • P.Purchasing Requisitions (BANF) through the connection to the process engineering database
  • P.Avoid duplicate orders and unnecessary costs.
  • P.Monitoring the status between orders and deliveries
  • P.Keep an eye on possible claims
  • P.Organising the life cycle of project documentation from the very beginning
  • P.With PMS it is already known today which approvals will be needed tomorrow and even the day after tomorrow
  • P.Analyses of the current status, simply by pressing a button, the database will answer your questions at any time
DMS - Document requirement

The consistent application of the DMS functionalities allows a compilation of the required documents to be derived from other, similar projects when planning new projects. The implementation of documentation guidelines also generates an extensive need for documents. In PLM DMS, there are various ways of declaring the document requirement, either via similar units (sub-units), similar projects or simply via DMS templates in the form of Excel-based document requirement lists. Document requirement lists can also be used to automatically assign number ranges of different units to specific documents.

Documents from another project can be created in DMS as document requirements in the new project or the documents can be copied directly. The drawing transitions are preserved intelligently as far as possible. Documents from this pool, including virtual ones, are created in DMS and the designations from the pool are transferred in several languages if required.

This approach results in considerable time savings during project execution.

Via a PCS exchange, databases and documents in different formats (dwg, pdf etc.) with their metadata and the possibly linked PDE objects (TAG-No. / KKS / RDS-PP etc.) and their metadata can be transferred.

  • P.EXCEL transfer: A supplier registers his document number requirement via Excel. You read in this Excel file and create the corresponding virtual document set in your document requirement. You send the document numbers generated in the DMS back to the supplier to create the documents.
  • P.Structured PCS transfer: A supplier registers his document number requirement via Excel. After reading in this Excel list, a corresponding document record is created in DMS as a structured PCS data container (Planet Control System) for transferring documents & database. The PCS file containing the created document numbers is sent back to the supplier. The supplier's documents can now be entered there and linked within the PCS file if required. The PCS file is then returned and the data is automatically read into the leading PLM-PLANET project in a structured way.

Via a PCS exchange, databases and documents in different formats (dwg, pdf etc.) with their metadata and the possibly linked PDE objects (TAG-No. / KKS / RDS-PP etc.) and their metadata can be transferred.

DMS - Document Controlling

DC phases:
In order not to lose the overview of the progress of the individual documents as a project manager, all DMS documents of a project are managed in a controlled manner over a project sequence. The project execution (revision procedure) is controlled via the project phases.
The tree for the Document controlling phases is generated from the DocWorkState and the document purpose, the numbering results from this and determines the sequence.

The following elements are available

DC phases

  • P.P = phase (stands for a project phase)
  • P.A = Action (stands for processing / checking step)


  • P.Basic engineering
  • P.Construction
  • P.Detail engineering

Document purpose

  • P.Internal audit
  • P.Preliminary examination
  • P.VP attestation

In the examples you can see how DC phase controlling creates this connection.

Example of a phase:

  • P.Composition: DC phases + DocWorkState
  • P.Result: P DC phases + 1. Basic engineering = P-1. Basic engineering

Example of an action:

  • P.Composition: DC phases + DocWorkState + document purpose
  • P.Result: A DC phases + 1st basic engineering + 1st internal test = A-1.1 internal test
DMS document management system

PLM-DMS manages the work processes and documents to optimise the efficiency and quality improvement processes of your projects in the process industry. Use the specialised optimisation potential of this document management system.
All data of complex plants and their planning processes are available at the push of a button in the current planning status. Regardless of whether you are planning small compact plants or large power plants, PLM-DMS equips you perfectly for the fast-moving future markets.

  • P.Supply and Logistics
  • P.Commercial Project Management
  • P.Technical Project Management
  • P.Construction and Assembly
  • P.Quality Management
FAD Document Organization

The demands on plant documentation are constantly increasing. In addition, systems within the framework of Industry 4.0 must provide more and more detailed information in ever more complex structures and formats. One of the greatest challenges is to be able to provide uniform documentation that meets the constantly increasing demands.
This is where FAD comes in. Not only are you able to manage your paper documentation, you are also able to manage PLM documentation as well as any external documentation with just one single tool

  • P.Do not just combine your paper documentation and your electronic documentation, integrate any third-party documentation.
  • P.Your supplier has only provided you with a file system? Simply integrate it into your documentation. FAD automatically shows you new files, changed files or even duplicates.
  • P.Create a uniform appearance for your documentation. Use the options to generate spines, tables of contents and cover pages in a uniform way.
  • P.Keep track of the content, storage locations and loan status of your paper documentation.
  • P.Do you have a question about a specific technical component? If you are not looking for a key, code or structure of a DMS system, you can simply find everything about this component.
  • P.Is your documentation complete? Is every component and assembly sufficiently documented? FAD shows you possible gaps in the documentation at the push of a button.
  • P.Keep an overview of open redlines and to-dos. Stay up to date on which changes have been made, when and by whom in your documentation.
  • P.Make use of synergies. Integrate your maintenance and operations directly. Release the necessary documentation in an FAD portal. Changes and conversions are incorporated directly into your documentation.
  • P.Use the integration of your process engineering database
FLM Facility Management

PLM-FLM is a facility management tool for the organisation of infrastructural information. The advantage of this solution lies in the possibility of using identification systems from the plant construction industry, such as KKS or RDS-PP.
PLM-FLM closes the gap that usually exists between location-based and process-related plant identification, data, procedures and documents of entire production plants.

  • P.Group and sites, rooms and storage locations
  • P.Inventory management, job description
  • P.Room and installation location Marking
  • P.consumption billing, effective land use
  • P.High resource utilisation

The PLM FLM module helps you to manage your rooms, facilities and inventory. You receive a fault message, you know in which technical area of an installation the fault is located. But where is the component physically located? In which building and at what altitude is it installed? Use FLM to increase the value of your 3D model even further.

  • P.Manage your buildings, rooms and storage locations across the entire group.
  • P.Use the possibilities of your licence plate system (e.g. KKS, RDS-PP etc.) and experience the advantages and synergies of a 3D system with fully integrated database.
  • P.Connect your documentation to FLM. Find components not only through your documents, but also through their installation locations.
  • P.Use the connection to your process engineering database to discover completely new possibilities. Identify details where others are still in the basic planning stage.
PMC Project Monitoring and Controlling

The basis is the delimitation of the requirements from the requirements in the project, whereby the offer, order, contract, lots, award of contract, engineering, assembly, commissioning, handover and final documentation are defined as milestones. Essentially, documents are created which are to be monitored according to their category, according to their target fulfilment according to the project phases. During the recording, generation and transfer of project activities, the metadata leave traces that can be used for project monitoring. If the movement profiles of the metadata are linked with algorithms, the activity can be mapped in the project development phase. Since all activities in PLM are stored in the PLM database, documentation and controlling can be realised particularly easily via SQL statements.

  • P.Project monitoring
  • P.Monitoring communication
  • P.Monitoring of documents
  • P.Monitoring process data and EMSR data
  • P.Definition of the target conditions
  • P.Test procedure
  • P.Transfer procedures
  • P.QM
  • P.Start-up cold and warm
  • P.Handover and final documentation

The PLM 4.0 software family offers an electronic monitoring system for consultants, planners, installers and operators based on the metadata, which logs and monitors the process. Due to the lot structure in PMS, further subdivisions of the project are possible. As in the project the subsystems for construction, assembly, commissioning, documentation and assessment etc. are a basis for the subdivision, the lot structure should take this fact into account.
This eliminates the need for multiple assignments and minimises the workload for the workflow and controlling. Milestones for controlling should be assigned to the lots (and thus also to the subsystems). Various sets of rules, regulations, standards and the contract with the customer form the checklist for project controlling.


en_GBEnglish (UK)
Powered by TranslatePress »