ETDMS


ETDMS®

 

The flexibility of our solutions to boost your business needs and procedural specifications of each customer!

B

Few or maybe no electronic management document solution (EDM) meets totally the needs or specific management modalities, applied to specific procedures of a company for the control of the document control management (DCRM: Document Control and Record Management).

There is an undeniable limit of available solutions to satisfy the workflow management required by the procedures of DCRM, within the framework of workflows validation- specific to a company- while complying with constraints: procedural, technical, site construction or budget..

Based on these specific needs, in each sector and often in each company, SOFTIC designed ETDMS®. SOFTIC - ETDMS ® is a complete suite of fully integrated software adaptable to different areas of activity.

SOFTIC-ETDM®  is a complete suite of fully integrated software adaptable to different areas of activity.

Reduce the risks related to various projects, increase your margins, and optimal use of your resources with the software SOFTIC -ETDMS® for engineering. SOFTIC - ETDMS®, an all –in –one software :

  • Integration of conception and construction plans.
  • Management of the technical documents through the creation, the review, the validation and all tasks that obstruct a company during the management process, the control, and the monitoring of the technical conception documents.
  • Management of the statements of MTO (Material take off) for pricing, distribution and placing orders.
Text/HTML

MORE ON ETDMS®

 

SOFTIC - ETDMS® ensures functionalities like:

The need or requirement for a new documentation may be incorporated into the management system by managers and project managers, employees, or even recommendations or norms from external third parties. The requirements necessary for creating documents can be based on minimum criteria, but which are not limited. In a non-exhaustive way, we can enumerate the following criteria:

  • The legislation
  • the Standards
  • the results of internal / external evaluations
  • The suggestion of the third parties involved in one or more projects
  • The different changes in terms of activities, sectoral or organizational structure.

All controlled documentation systems, require a regular examination to meet effectively the needs in terms of company procedures. The review of process or adjustment may consider the following non-exhaustive elements:

  • The aptitude and the pertinence in relation to the workplace, the industry or the company,
  • Effectiveness in achieving the desired results,
  • Compliance with legislative requirements...

The goal of files management is to ensure that quality documents are created, managed and eliminated in accordance with technical, legal or procedural requirements. Files may include simultaneously, documents with types (paper or electronic) and from different sources (internal or external documents).

Documents (new, intermediate or final) of projects are approved by any authorized and defined person in the business task or the specific project. According to the importance of the impact on the business process, the project or the task nature, the board of directors can determine the need to resend the project documents to any authorized entity for validation within the procedure. Once approved, the final controlled document is made available to the concerned staff to enable its application.

Consultations and revisions of the system documents are necessary before finalizing. The applied method for this involves at least the workflow or process below:

  1. Draft documents: The draft documents are communicated to the concerned parties and posted on the solution to invite those who are concerned to insert comments. They will be posted for a defined period of time, during which feedbacks can be shared (all this is done in accordance with the instructions given by the internal procedure for example).
  2. The final draft is pending approval: the feedbacks are examined and incorporated into the draft documents. A final draft is prepared by senior consultants for the final approval.

A master register of document control is maintained for all the documentation of the created or modified system. All documentations locally developed or modified by the firm, the business divisions and the departments are saved in a control register of local and regularly maintained documents. The document control register of master or local ones generally includes the following elements: document title, version number, creation date, revision date, creation reasons, creation comments, version revision, the one who submitted it, links to consultations, tenders, or any source behind the creation of the document, feedbacks, etc.

 

The documents are considered obsolete if they are no longer required in the daily procedures. They are hence archived as defined by the prerequisites of the document management system, in an appropriate manner to prevent any unintentional usage and remain accessible if needed, for the system evaluation within the requirements of the company procedures.

All documentation, used or introduced through the solution is a part of the integrated system. This documentation is maintained in an electronic format. In some cases, it is possible that only the latest versions of the documentation are available on the Front Office. Revisions and other modifications are available for certain user groups only. In practical terms, in this first case or others, the different revisions and updates are well preserved. The visualization of versions and save is done based on the procedural constraints of the company in the first place, or according to other more specific constraints on business processes within the company.

Do not hesitate to consult the various cases by clicking on the different case studies.

Every document created, modified or controlled on the management system requires the following minimum properties or attributes in the description:

  • Document identification: the Document title:the team and / or the authorization zone of the document, the version, etc.;
  • The date of publication or release: the month and year of publication of the document;
  • The number of pages: the page and the number of pages in the document;

Locally developed or modified, the documentation included in the system according to the local needs have to meet the following minimum requirements of the document properties. In practice, this is mirrored by the case below:

When a modification occurred on the system documentation, the document publisher must mention at least the following elements in the document:
  • The concerned operational zone
  • The publisher of the document
  • The words " locally modified"
  • The month and year of modification