Workflows

Definition

A workflow is the flexible traverse of drawings and documents which maps the automated or formalised business processes. Not only project members but also external service providers can be integrated into these workflows. Workflows are used to organise and coordinate collaboration in a project.

  • Sequential and parallel checking
  • Powerful Redlining functions
  • Automatic merging of redlinings after a parallel check
  • Integration of external project members by e-mail
  • Automatic print requests
  • Dynamic workflows on basis of various document parameters
  • Support of QR-Codes as a connection to hardcopies
  • Electronic signatures and individual stamps on every document

Organized Processes

  • Workflows are the organizational basis for most EPLASS projects. The processes and assigned participants are defined together with the EPLASS project managers. Subsequent workflow diagrams are drawn out to visualise the processes. With the help of EPLASS, various project members or departments can carry out reviewing the documents sequentially and/or simultaneously.
  • In order to process the workflow tasks, various groups are defined. Hence allowing the differentiation between users who are or are not authorized to view, edit, or sign a document. Further options, such as the requirement for a "dual control" by two checkers before a document can be forwarded is also possible.
  • The document and drawing review is carried out online and digitally using the integrated viewer in EPLASS without the need for a download to a local computer. Furthermore, EPLASS automatically combines the comments and review entries at the end of a parallel check.
  • The due dates for processing the individual tasks and milestones can also be defined in the workflow.
  • It is also possible to grant read access rights at different positions in the workflow. For example certain groups can be given access rights to documents from a particular status such as “Issued for Construction” onwards in the workflow.

Flexibility

  • No workflows without exceptions: the explicit traverse of documents can be influenced by any given specific parameters, such as the assigned editor may be read from the document ID. Another classic example, is the selection of the checking engineer based on lots, or block numbers. Furthermore, many other parameters can automatically be set to execution such as adjustment of review periods, distribution of e-mail notifications, or the send out of print requests.
  • To add to the pre-defined automated flexibilities, a specific group of users may be given privileged access as power users to move a document manually in the workflow.

Documentation

  • Complete protocol of all review tasks is logged as documents traverse through the workflows. All review comments, e-mails, for infos, rejections, approvals, revision increases, deadline overruns and so on are logged into EPLASS. As a result, it is always possible to see who approved which plan or document, and when.
  • Even manual adjustments by the so-called power users are logged into EPLASS. This has a significant influence on the quality of the review and documentation.