TDMS Farvater

TDMS Farvater is built on the TDMS 5 platform. TDMS Farvater implements the requirements for design and working documentation according to GOST R 21.1101-2013 and the project management requirements according to GOST R 54869-2011. The TDMS Farvater package includes templates for the design documentation development processes, as defined by Russian Government Resolution No. 87 of February 16, 2008 (as amended on December 13, 2017).

The Farvater TDMS contains preconfigured templates for deploying capital construction projects for industrial and non-industrial purposes, as well as linear facilities. These templates include over 100 template assignments from the Chief Project Engineer, over 800 templates for tasks to develop required documents, and over 800 standard document titles required for development according to Resolution No. 87.

TDMS Farvater is fully operational and requires no code modifications, while offering a number of advantages of the TDMS 5 platform, such as a standard interface designed in the style of the Microsoft Windows Explorer file manager, dynamic context menus, dynamic customizable selections, runs on the modern Microsoft SQL Server DBMS, works with TDMS File Server, and interacts with interfaces to Microsoft Office, AutoCAD, and nanoCAD.

TDMS Farvater is a customized user workstation that provides:

• fast and secure access to data and files stored in the system;
• unique tools for searching and filtering data;
• exchange of information within the system via the built-in mail module;
• collective work of users in a system with differentiation of access rights;
• blocking editable information objects, preventing simultaneous modification of the same data by different users;
• compliance with established data entry rules, preventing user errors when entering identifiers, codes, inventory numbers and other information;
• development and application of templates for entire projects, parts of projects, assignments from the Chief Project Engineer, assignments between subcontractors, documents in accordance with Resolution 87 and in accordance with enterprise standards;
• Individually configurable user workstations that improve the system's ergonomics and reduce training time.

TDMS modules Fairway

Organizational structure management module

Staff units:

• a staff unit is created by the administrator when setting up the system or when announcing a vacancy in a department;
• the user is assigned to a staff position, only after this the user is able to work in the system;
• one user can occupy several staff positions;
• a staff unit can be either separate or part of a division;
• For each staff position, a history of interactions with organizations and external recipients is recorded.

System users:

• Each user of the system has a personal profile, which stores the following settings: folders and selections (standard or developed for a given user) of the TDMS Farvater desktop;
• available commands;
• available toolbars;
• types of objects that can be used by the user;
• Profile settings are managed by the administrator.

Staff units can be entered into TDMS Farvater via an *.xls file obtained by downloading from 1C Personnel or other HR programs, or created manually.

Organizational and administrative document flow

External document flow:

• incoming correspondence;
• outgoing documents;
• contracts.

Internal document flow:

• orders;
• orders;
• memos;
• reports;
• explanatory notes;
• minutes of the technical meeting;
• general protocols;
• leave applications;
• work plans.

Working with contracts.

Engineering document flow

Project creation:

• placement in the project file of the design assignment and other initial permitting documents required by the project working group: the Chief Project Engineer and assistants to the Chief Project Engineer can create and update documents in the initial data section;
• The Chief Inspector and assistants may issue permission to work with the source data to any other employees;
• support for the versioning of original permitting documents, ensuring that work is carried out only with current versions of such documents;
• defining the project team – chief project engineers, assistant chief project engineers;
• definition of design objects within one project.

Project planning:

• defining the composition of the project: entering sections, subsections, parts, and books of the project for stage P, both using templates and without them;
• creation of parts and kits for stage R;
• creation of additional stages, such as preliminary study, research;
• creating your own stages to manage the design process;
• Project deadlines: setting planned deadlines for the completion of each part of the project;
• control to ensure that the deadlines for the work of lower-level parts and subtasks do not exceed the deadlines for the work of the tasks and parts of the upper level, and, ultimately, the contractual deadlines;
• calendar schedule, project schedule: using the Gantt Chart graphical tool to adjust the project schedule;
• Determining the critical path of a project using a Gantt chart;
• tracking the completion of tasks using the same Gantt chart;
• assignment of responsible departments and employees: a person responsible is appointed for each part of the project - the head of the department developing this part and an assistant to the person responsible;
• If necessary, the responsible employee and department can be changed at any stage of the work, while all statistics from previous work on the part and task are preserved;
• determining the sequence of work execution: establishing connections between tasks of different types: “Start-Start”, “Finish-Start”, “Finish-Finish”;
• automatic alignment of tasks taking into account connections;
• Transfer of work on parts of a project to subcontractors; for a part of the project, it is possible to specify a subcontractor if a subcontracting agreement has been concluded with it.

Organization of project implementation:

• assignment of performers to work, tasks, and project objectives: the person responsible for the section creates tasks for performers to create project documents;
• the person in charge can change the performers of tasks;
• the task to the contractor has an issue date and an actual start date of the work;
• development of documentation: performers can create documents within the framework of their tasks accepted for work;
• documents have a flag “Add to album”, which determines whether all document files should be included in volumes submitted for release, to the customer, etc.;
• documents can contain any number of any files;
• each project document is automatically assigned a designation;
• working with current versions of documents;
• organizing work on comments from both internal and external experts;
• Responding to changes through corrective actions (reassigning tasks, allocating additional resources, working with subcontractors, working with tasks according to the minutes of technical meetings).

Project/project portfolio execution control:

• monitoring progress on assignments and tasks;
• monitoring the workload of performers;
• forecasting the completion of project stages based on the current progress of work;
• generating reports suitable for analysis by external business intelligence applications.

Project Completion Processes:

• transfer of the project to the electronic archive;
• project closure.

Supporting processes:

• management of directories of contractors, subcontractors, and customers;
• management of project templates, project parts, assignments, tasks;
• document template management.

Electronic archive

• completed parts of projects are transferred to the electronic archive;
• Only employees who have received the appropriate permission to do so may work with parts and projects located in the archive;
• it is impossible to change the information stored in the archive;
• Changes to the documentation are made in accordance with GOST R 21.1101-2013, with the registration of permission to make changes;
• When changes are made, part of the project is removed from the archive and transferred to the “Under revision” status.

Receiving reports in TDMS Farvater

Standard reports:

• reports on the composition of design documentation, lists of sets of working drawings;
• resource workload reports: individual employee/department/group of departments (by project, over a period of time);
• reports on the progress of work on the Project Portfolio/Project/Part of the Project/Assignment/Task;
• schedules for completing work on the Project Portfolio/Project/Part of the Project.

User-configurable reports

• Using the standard TDMS Sample tool, the result can be exported in *.xlsx format.

TDMS Farvater Add-ons

TDMS Farvater fully supports TDMS File Server, an application that allows for efficient file management across a virtually unlimited number of storage devices. TDMS File Server optimizes file storage based on access frequency and storage device speed. TDMS File Servers can be linked to user workstations, allowing files to be stored directly on the network segment where they are most frequently accessed.

TDMS File Server is purchased in addition to TDMS Farvater. The number of file servers is determined by the size of the organization, its structure, and the volume of information involved in document flow.

Software interfaces to Microsoft Office, AutoCAD, and nanoCAD enhance the capabilities of TDMS Farvater with a number of specific functions, such as synchronization of project attributes with fields of text and graphic documents, and accelerated processing of external links.

Software interfaces to Microsoft Office, AutoCAD and nanoCAD are purchased additionally to TDMS Farvater.