MVP Integration Workflow for Partner Setup
- Eric Niday
Overview
This document outlines the ideal Minimum Viable Product (MVP) workflow for integrating with e-PlanREVIEW and PDFScout. The integration process involves connecting various systems and validating applications/plans through several steps.
Workflow Steps
1. Applicant Portal
New Application/Record/Permit:
Submit Application/Plans: The applicant submits their application/plans via the Applicant Portal.
Scout API Validation: The application/plans are sent to the Scout API for validation.
Validation Results:
If the application fails validation, the applicant resubmits plans.
If the application passes validation, it moves to the Permit System for further processing.
Plans Resubmitted:
Resubmit Plans: The applicant resubmits plans.
Scout API Validation: The resubmitted plans are sent to the Scout API for validation.
Validation Results:
If the application fails validation, the applicant resubmits plans.
If the application passes validation, it moves to the Permit System for further processing.
Approved Plans:
Generate Approval Deliverables: Approval deliverables are provided to the Applicant.
2. EPR Scout API
New Application/Record/Permit:
Validate Application/Plans: The Scout API validates the submitted application/plans.
Validation Results:
If the application passes validation, it moves to the Permit System.
If the documents fail validation, the reason for failure is returned to the Applicant Portal.
Plans Resubmitted:
Validate Resubmitted Plans: The Scout API validates the resubmitted plans.
Validation Results:
If the application passes validation, it moves to the Permit System.
If the documents fail validation, the reason for failure is returned to the Applicant Portal.
3. Permit System
New Application/Record/Permit:
Check Plan Review Requirement: The system checks if the application requires a plan review.
If no plan review is required, no integration occurs.
If a plan review is required, a project is created and moves to the Intake Process.
Plans Resubmitted:
Documents Checked for Resubmittals: Permitting Solution validates receiving all required documents for the next plan review cycle.
Review Complete:
Process Corrections Deliverables: The system processes corrections deliverables if corrections are needed.
Process Approved Plans: The system processes and creates approved deliverables.
4. Intake - EPR
New Application/Record/Permit:
Upload Documents and Complete Intake: Documents are uploaded, and intake is completed.
Plans Resubmitted:
Create Corrections Deliverables: Corrections deliverables are created if corrections are needed and returned to the permitting solution.
5. Reviewer - EPR
New Application/Record/Permit:
Complete Reviews: Reviews are completed.
Integration Points
Applicant Portal to EPR Scout API
Integration Point: Application/Plans submission and validation.
Purpose: To ensure submitted plans meet validation criteria.
Permit System to EPR
Integration Point: Plan review requirement check and project creation.
Purpose: To determine if the application requires a plan review and to create a project if necessary.
Reviewer - EPR to Permit System
Integration Point: Document/Task Statuses
Purpose: Communication of plan review program.
Permit Staff - EPR to Permit System
Integration Point: Review completion and deliverable creation.
Purpose: Return deliverables to the applicant upon completion of the review cycle.
Conclusion
This document provides a detailed outline of the ideal MVP workflow for integrating with [Your Software]. These steps ensure a seamless connection and validation process, leading to efficient and effective plan approval.
This workflow visualization helps understand the sequence of events and the integration points across different systems involved in the plan review and approval process.
Need Help?
For support and inquiries, reach out to:
Channel Partner - Scott Garner sgartner@eplansoft.com
Integration Manager - Eric Niday eniday@eplansoft.com
General Support - support@eplansoft.com
Related articles