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:
- Create a Project: A project record is created that includes at minimum, one primary Contact.
Conduct Intake on the new plan review documents.- Plan review documents (in PDF format) are uploaded to the project.
- Supporting attachments (any file type) are uploaded to the project.
- Trigger Distribution Workflows to create group and/or named-user assignments.
- Multiple assignments are created for each plan review document.
- Conduct plan review.
- Complete assignments.
- Each assignment is given a pass/fail status by the reviewers.
- A deliverable package with the marked up documents is prepared, this completes the 1st submittal cycle.
- Return the deliverable package to the customer for corrections.
- Corrected documents are provided by the customer as the next submittal. Repeat from step 2.
- Existing assignments are reopened with a Not Started status and markups are carried forward to the latest version.
- Comments found to be resolved are marked ‘closed’.
- Plan Review Assignments are completed.
- The process repeats until all noted issues are resolved.
- The project is closed.
...
Plan review deliverables are sent back to goPost. The customer logs into goPost to download the reviewed plans, etc. and can optionally be downloaded to another network location.
...
| title | Best Practices |
|---|
...
.
...
| Info | ||
|---|---|---|
| ||
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. |
...