This article provides information about how eplansoft REVIEW (EPR) manages projects, plan review documents, supporting attachments and the plan review cycle.Additionally, information about how EPR typically integrates to other back-office applications is described below. on a high-level overview of the project and plan review lifecycle and typical integration scenarios for connecting e-PlanREVIEW® (EPR) to an external application using our Connect API toolkit.

In this article:

...

...

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 Contactnecessary as a container to upload files.
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.Each assignment is given a pass/fail status by the reviewers.Upload files via the Upload API
   1. Upload files
   2. Trigger assignment creation for plan files to be reviewed
5. Conduct plan review and Complete assignments.
   1. Reviewer will give a status upon completion of assignment (completed, cancelled, approved, etc)
6. A 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 via 3rd party upload api or pull from EPR api.
7. 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.Repeat steps 3 and 4
      • The process repeats until all noted issues are resolved .
   The
   1. • and project is closed or archived.

...

Integrated Environments

Variations on the process described above include the following scenarios when EPR is integrated to another application using our Connect API toolkit:

Integration Option 1

...

The integrated application pushes project data, documents and plan review assignments to EPR. The integrated application manages document versioning.

No manual data entry of projects, upload of documents or creating plan review assignments is necessary in EPR.

Plan review is conducted in EPR.

Plan review deliverables are checked in to :

1. creates a project via project create API
2. uploads file to EPR
3. manually creates plan review assignments in EPR thus not using EPR's API
4. return final PDF files to the integrated application using API calls provided to EPR.

Integration Option 2

...

The integrated application pushes project data and documents to EPR using API calls.

EPR manages document versioning.

EPR's Workflow Distribution module is configured and enabled to auto-create assignments.

Plan review is conducted in EPR.

...

1. creates a project via project create API
2. uploads file to EPR
3. creates plan review assignments in EPR using EPR's assignment API
4. during plan review, based on some event trigger a callback to 3rd party application
5. return final PDF files to the integrated application using API calls

...

Integration Option 3:

EPR is connected to the e-PlanSoft goPost Customer Portal.

goPost pushes new project data and documents created by the customer to EPR using Connect API.

goPost manages document versioning.

Manual data entry of projects/contacts and uploading documents to EPR is unnecessary.

Plan review is conducted in EPR.

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.

...

...

1. provided to EPR.

Related articles

...