Excision Process - Functional Breakdown¶
NOTE Review along with full FRS
1. Overview¶
Excision refers to the process of removing a portion of land from an existing property for allocation or other purposes. This process involves validation, approval, and updates to both alphanumeric and spatial data.
2. Actors Involved¶
- Maintenance Manager: Reviews and assigns tasks.
- Officer: Captures request details and validates documents.
- Scrutinizer: Performs quality assurance and final checks.
- Land Surveyor: Updates diagrams and plans.
- System: Handles workflow routing, notifications, and data updates.
3. Inputs¶
- Request letter from applicant.
- Consent from relevant authorities.
- Proof of payment.
- Supporting documents (e.g., survey diagrams, title deeds).
4. Preconditions¶
- Applicant must have submitted all required documents.
- Payment verification completed.
- Existing property details available in the system.
5. Process Flow¶
- Capture Request
- Officer logs into the system.
- Selects "Excision" process type.
- Uploads required documents.
-
Completes mandatory fields (e.g., property ID, portion details).
-
Validation
-
System checks:
- Mandatory fields completed.
- Document formats correct.
- Payment verified.
-
Workflow Routing
- Task moves to Maintenance Manager for review.
- Manager assigns to Officer for processing.
- Officer completes data entry and submits for QA.
-
Scrutinizer reviews and approves/rejects.
-
System Actions
- Reserve new portion number.
- Update property description in database.
- Trigger GIS update for spatial data.
-
Generate notification letters.
-
Outputs
- Updated property record.
- Endorsement on diagrams and general plans.
- Notification letters sent to applicant and stakeholders.
6. Business Rules¶
- Portion number must be unique and reserved before approval.
- All documents must be linked to the property record.
- Audit trail must capture every status change and user action.
7. Integration Points¶
- Deeds Office API: For transfer number verification.
- GIS Service: For spatial data updates.
8. Exceptions¶
- Missing documents → Request returned to applicant.
- Invalid payment → Process halted until resolved.
- GIS update failure → Escalate to technical support.
9. Estimated Effort for Implementation¶
| Component | Effort Points (EP) |
|---|---|
| UI Form + Validation | 6 EP |
| Workflow Routing | 4 EP |
| Backend Logic | 8 EP |
| Integration (Deeds/GIS) | 6 EP |
| Document Upload & Output | 4 EP |
| Testing (Unit + UAT) | 6 EP |
| Total | 34 EP |
10. Key Screens¶
- Capture Request Screen: Dynamic fields for Excision.
- Maintenance Tab: Displays process status and linked documents.
- QA Checklist Screen: For Scrutinizer validation.
11. Notifications¶
- Email and system inbox alerts for:
- Task assignment.
- Approval/rejection.
- Completion of process.
12. Audit Trail¶
- Log every action:
- User ID.
- Timestamp.
- Status change.
- Comments.