Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article provides information about how eplansoft REVIEW (EPR) manages projects, plan review documents, supporting attachments and the plan review cycle.

...

Table of Contents


...

High Level Overview

A typical plan review Project undergoes this basic process:

  1. Create a Project: A project record is created that includes at minimum, one primary Contact.
  2. Conduct Intake on the new plan review documents.
    1. Plan review documents (in PDF format) are uploaded to the project.
    2. Supporting attachments (any file type) are uploaded to the project.
    3. Trigger Distribution Workflows to create group and/or named-user assignments.
    4. Multiple assignments are created for each plan review document.
  3. Conduct plan review.
  4. Complete assignments.
    1. Each assignment is given a pass/fail status by the reviewers.
  5. deliverable package with the marked up documents is prepared, this completes the 1st submittal cycle.
    1. Return the deliverable package to the customer for corrections.
  6. Corrected documents are provided by the customer as the next submittal. Repeat from step 2.
    1. Existing assignments are reopened with a Not Started status and markups are carried forward to the latest version.
    2. Comments found to be resolved are marked ‘closed’.
    3. Plan Review Assignments are completed.
      • The process repeats until all noted issues are resolved.
  7. The project is closed.

...

Info
titleBest Practices

In some cases, a project may need to be reopened for plan review of revised drawings after a project has been closed. For instructions on how to handle documents submitted as revisions, see: XXXXX

The Project Status Workflow

Project statuses are configured by your site administrator and mapped to an internal project status workflow.

The example below demonstrates how custom statuses have been entered for each internal workflow process.

...

EPR automatically changes the project status from Open status to Cycle Complete status when all plan review assignment statuses are marked complete.

...

This internal status is used to indicate the project is completed, but some plan review assignments were not accepted/approved.

For permitting projects, a Fail status would infer that a permit cannot be issued.

...

Use this workflow status to halt plan review temporarily. EPR then restricts editing of the reviewer comments and project data except to allow the project Status to be modified.

Document upload/intake is disabled as well.

...

Use this workflow status for projects that will not be completed. EPR restricts editing of the reviewer comments and project data.

Document upload/intake is disabled as well. The project is essentially closed.

...



Info
titleBest Practices

For stand alone deployments, email notifications should be configured to alert the appropriate project team members when a project cycle is set to Cycle Complete so that a deliverable package can be prepared.

...