Document Workflow Types

Meridian offers different types of workflows that can be used for various purposes. Users can decide to use one or more of the workflow types depending on the organization’s business processes and needs. The workflow types are divided into two major categories, document workflow and project workflow. Within each category are different workflow types that can be used either alone or together with any other workflow type. The relationships of these workflow types to one another can be seen in the following list:

• Document workflow for the change control of individual documents
  • Working copies (simple check-out/check-in)
  • Document type workflow (basic workflows configured in document types)
  • Workflow definitions (advanced workflows configured in workflow definitions)

• Project workflow for the change control of multiple related documents in groups
  • Project folders (configurable folders assigned to project definitions provided by the Advanced Project Workflow Module.

In the document workflow category are the workflow types document type workflow, workflow definitions, and working copies. Document type workflow andis working copies are easy to configure and meet the requirements of the majority of change control processes. Workflow definitions are flexible and powerful enough to meet the most demanding change control process requirements.

The document workflow types control the change of individual documents. Document workflows ensure that the steps required to produce a new revision of a document are executed in the correct order by the correct people. For example, a simple document type workflow might require that a new document revision be reviewed before it can be released. Document revisions can also occur within the prescribed steps of a project workflow that controls the change of an entire set of documents, such as for a project, assembly, subassembly, and so on.

Project workflow controls the change of groups of related documents through the life cycle of a project. They ensure that the steps of a project are executed in the correct order by the right people. The documents within a project are revised individually using one of the document workflow types. For example, a simple project workflow might require that all documents revised for a project be reviewed as a completed set before they can be released for construction or manufacture. Users can create project folders only with the installation of the Meridian Advanced Project Workflow Module. A typical scenario of combining workflow types is document type workflow for master documents together with document type workflow and workflow definitions in project folders. In this scenario, non-critical, non-project-oriented document types use Quick Change to produce new revisions made only by authorized users. Non-critical, project-oriented document types use the basic steps of document type workflow in project folders. Critical, project-oriented document types use the configurable steps of workflow definitions in project folders to update master documents.

Document workflows are described in more detail in the following topics.