This webpage provides common tips and issues faced by users submitting FSPs to the FSP Tracking System. More information on these tips and techniques can be found in the Submitting an FSP User Guide.
- Submit via ESF
The easiest and most efficient way for licensees/BCTS to submit their FSP is through the Electronic Submission Framework (e.g., by using your internal applications to generate the XML/GML file). If you don't have the resources to generate an XML/GML file, you can submit the non-spatial portion of your FSP via the FSP Tracking System. You will need to contact your District Manager to address the submission of the spatial portion. See the Submitting an FSP User Guide or Amending an FSP User Guide for more information on both these options.
- FSP Stocking Standards
Stocking standards for FSPs should be submitted with the FSP by entering into the FSP Tracking System or including in the XML file and submitting via the Electronic Submission Framework (ESF). Stocking standards for FSPs are no longer entered into RESULTS. They will be automatically approved and passed to the RESULTS application once the corresponding FSP is marked as approved in the FSP Tracking System.
If entering your stocking standards directly into the FSP Tracking System (via the Stocking Standards tab), retain the plan in "draft" status until all the stocking standards are entered (e.g., do no submit the FSP until all stocking standards are entered). Once the FSP is submitted, you will not be able to make any further changes/additions to it.
- Forest Development Unit (FDU) boundaries
FDU boundaries submitted to the FSP Tracking System as an XML/ GML file via ESF will be stored in the Land and Resource Data Warehouse (LRDW) and linked to the corresponding FSP in the FSP Tracking System. The spatial information submitted by the Licensee/BCTS should meet the mapping standards specified in the Submitting an FSP User Guide. The boundaries should not be changed by MFR personnel.
- FSP Legal Document
The FSP legal document must be submitted by the Licensee/BCTS for storage in the FSP Tracking System. It must be a full, legal copy of the plan, complete with signatures of those required to prepare the plan as per the requirements of the FRPA. More information on signatures to an FSP can be found in Section 3.10.15 of Volume I of the AGFSP ("Who is responsible for signing-off on the FSP?").
The legal document must be submitted under the FSP legal document section of the Attachments tab in the FSPTS. This is the document containing the legal requirements for the FSP defined in section 5 of the FRPA. Non-legal information should be submitted under the supporting documents section of the Attachments tab.
The FSP legal document can be in a Microsoft Word or pdf format. A pdf format is preferred from the reader's perspective – this avoids formatting issues when viewing the document on another computer as well as avoids any issues with dates in the document that display the current date vs. the date the document was written.
- Submit complete version of amended FSP
An amendment must contain an FSP legal document. This can be a fully consolidated version containing the original FSP plus the amended sections, or it could be a "1-page" document listing just the changed information. If multiple "1-page" amendments have been submitted in a row, licensees/BCTS are encouraged to submit a fully consolidated FSP on their next amendment. This will make it easier for all those who need to view the approved FSP (and amendments) if the FSP is up-to-date and contains all the amendments (vs. having to look through multiple "1-page" amendments to see what has changed in the plan).
The amended FSP legal document must be complete with signatures of those required to prepare the amendment as per the requirements of the FRPA. More information on signatures to an FSP can be found in Section 3.10.15 of Volume I of the AGFSP ("Who is responsible for signing-off on the FSP?").
- Amendment description
Amendments should include a description of the changes in the amended plan to assist those reviewing the amendment identify the changes. This can be the covering letter for the amendment.
- Use data fix to correct data entry errors
Amendments should only be used by licensees/BCTS to change their plan – not correct data entry errors. Data fixes should be used to correct any errors that occurred when entering information into the FSPTS.
- Submitting the FSP covering letter
The covering letter for the FSP can either be included in the FSP and attached in the FSP legal document section of the Attachments tab or attached in the supporting documents section of the Attachments tab.
- Use meaningful naming conventions
Licensees/BCTS are encouraged to use meaningful names to describe the information in their submission. For example, forest development units could be named by their geographic location versus "FDU1". This will make it easier to understand the labels on the map. Names of files attached in the Attachment tab could also be named to reflect the content (e.g., "Big creek FDU.zip", "Licensee X FSP").
- Use email distribution lists for contact email address
On the FSP300 (FSP Information Tab), Licensees/BCTS are encouraged to set up and enter an email distribution list for the contact email address instead of a single email address. This will enable the FSP Tracking System to send notice(s) to several recipients and minimize issues with invalid email accounts and mailbox full errors.
