This repository was archived by the owner on Jun 18, 2026. It is now read-only.
Proposed architecture
Current Architecture image for comparison
Detailed Proposed Architecture image
The main focus of the to-be state is bypassing the TIM / FMMI and TIM / FPFS connections, and having OpenForest make use of a new REST API in FPFS.
REST APIs are the modern standard and are simpler to use than SOAP APIs. This new API is already being developed and is ready for OpenForest to prototype against.
- Handles a single permit, simplifying the current batch process and the underlying API technology
- Once fully functional should allow for the deprecation of firewood permitting functionality in:
- NRM Automated SFTP process
- NRM owned SOAP API
- FPFS owned SOAP API
- Additionally, FPFS data will continue to flow to FMMI as usual, so downstream data consumers should be unaffected.
- CDW and EDW reporting systems fetch data from TIMs Staging Tables.
- We will work with the EDW program manager to change their data sources from TIM to a more modern system.
- We think it makes sense for the new EDW data sources to be a combination of OpenForest and POSS, using REST APIs when possible.