1 CP Business Process Page ii

One Cutting Permit over the Community Forest Area

Business Process Guide

Table of Contents

1. Preamble

2. Objectives

3. Process

3.1 Client Process:

3.1.1 Initial FTA submission

3.1.2 CP Application Completion

3.2 Ministry of Forests, Lands & Natural Resource Operations Approval Process

3.3 Process for Adding Second and Subsequent Cut Blocks

3.3.1 Overview

3.3.2 New Block Addition Process Details

4. Appendix 1

5. Appendix 2 – Notice of Commencement (NoC) Form

6. Appendix 3 – Sample XML of 1 CP Application

1 CP Business Process Page | 1

One Cutting Permit (CP) over the Community Forest Agreement(CFA) Area– Business Process Guide

1. Preamble

The following conditions MUST be in place for the one CP over a CFA to be available:

  • An approved Forest Stewardship Plan (FSP) is in place over the whole CFA.
  • Tabular rates are applicable for the CP.
  • The District Manager is satisfied that First Nations consultation is adequate for the entire area under the FSP.

It is recognised that there will be differences across the province due to differences between licensees, districts, and First Nations. It is expected that because of these differences there will be different approaches across the province.

  • The boundary/area of the Community Forest has been cleared of any overlapping tenure conflicts at licence issuance/replacement.

Notes:

  • The expectation is that the area under the FSP and the area under the single CP will be identical andwill cover the whole community forest area. There may be some instances where the area under a FSP is less than the whole community forest. In these cases,
  • an electronic map in pdf format of the area to be covered by the CP will be submitted by the Licensee to the District.
  • enter the following text exactly in the application description (fta:applicationDescription) field of the FTA submission:

"FSP and 1 CP do not cover entire CFA area. Map has been supplied to District."

  • The FSP is the operational plan that defines the area of the community forest where timber harvesting and road construction, maintenance and deactivation will take place during the term of the CP. Section 3 (1)FRPA states that a cutting permit or road permit must be consistent with a forest stewardship plan. For the purposes of a one CP application, consistency is defined as:
  1. the CP covers the area of the community forest that is included in the FSP (and no other areas); and
  2. the locations of the cutblocks“not being in significant conflict “ with areas identified in the FSP as areas where harvesting will be avoided.

Areas where harvesting will be avoided will take three forms:

  • Stand-alone areas identified in the FSP such as private land, separate blocks of Crown land, unstable terrain areas, etc.;
  • Riparian reserve zones, spatially identified wildlife tree patches, etc.
  • Areas excluded or “save and excepted” as identified on the Exhibit A from the licence document and carried forward to the Cutting Permit.

The CP can cover these areas but cut blocks must be located outside of these no harvest areas or be in non-compliance with the performance requirements of the FPPR or licence document.

  • To avoid unnecessary work, licensees should ensure that there is available volume in the Licence’s cut control position

2. Objectives

Simplify the process for Ministry staff and CFA holders by issuing a CP that covers all or most of the entire community forestarea for a 4 year period.

3. Process

3.1 Client Process:

3.1.1Initial FTA submission

  • Prepare xml/gml for CP as per current FTA schema.
  • Include one block only for crown portion of CFA:
  • Designate as ‘SSS’ in salvageTypeCode field.
  • In Application Description (fta:applicationDescription) include text:

CFA 1 CP Application -not a SSS Application

  • Name the block using cutBlockID field as desired. Block name set at this point will be permanent block name.
  • Set net area and gross area to 0.6 ha.
  • In Block Description (fta:blockDescription), enter following phrase exactly:

SSS indicates CFA 1 CP CL

This phrase is case sensitive, and contains no leading or trailing blanks.

  • Spatial for application is a 0.6 ha triangle positioned within the CFAboundaries, preferably not overlapping active tenure permits. (An equilateral triangle with 118 meter sides has a suitable area.)

3.1.2CP Application Completion

The complete CP Application includes the following emailed to the District FTA inbox or to the district person who processes CFA CP applications:

  • Short form appraisal sheet.
  • Letter of application stipulating that the application is for a CFA One CP andproviding the FTA submission number.

3.2 Ministry of Forests, Lands & Natural Resource Operations Approval Process

  • Once the ESF and additional information have been submitted by the CFA holder, District staff can perform the status/clearance adjudication reports and approve the CP in FTA. No map outputs are required at this stage.
  • CP must have SSS designation to enable adding additional harvest blocks over life of permit.
  • District will prepare the hardcopy or e-copy CP document. The Exhibit ‘A’ that is attached to the document will be the entire area under the FSP(copied/taken from the Exhibit ‘A’ of the licence document (including the significant constraints (exclusions and save & excepts from the adjudication report))).
  • Upon issuance of CP documents, the Licensee has legal authority to harvestin the community forest, subject to the constraints identified in the FSPand the adjudication report.
  • Prior to harvesting the licensee must notify the District office through a Notice of Commencement (NoC) as required by Section 85 of FPPR. A NoC is required for each spatially discrete cut block.
  • The date stipulated in the NOC(the commencement date) usually means the date on which timber harvesting, other than on road rights of way or landings, begins on the cutblock. This commencement date starts the silviculture clock for this cutblock.

3.3 Process for Adding Second and Subsequent Cut Blocks

3.3.1Overview

  • Per Section 85 of FPPR, the Licensee will submit, normally by email, a Notice of Commencement to the District using the form attached in Appendix 2 prior to commencement of each spatially discrete harvest block.
  • NoC willgo to a person in the District with ‘District Senior Admin Authority’. This person will choose one of three options:
  1. If the Cut Block ID specified in the NoC already exists in the SSS permit in FTA and the NoC specifies "DO NOT addnew block entry", change the status of the identified block from PP (Proposed) to HB (Approved).
  2. If the Cut Block ID specified in the NoC does not exist in the SSS permit in FTA and the NoC specifies "Add new block entry", add the block named in the NoC to the SSS permit in FTA with a status of HB (Approved).
  3. If existing information in FTA and instructions in NoC are inconsistent, request clarification from Licencee.
  • Note that spatial data is not a part of this FTA business process. Addition of the block to the SSS permit in FTA will enable subsequent full spatial reporting in RESULTS.
  • The NoC starts the silviculture clock for this harvest unit.

3.3.2New Block Addition Process Details

  • In FTA, bring up the licence and CP and go to the block tab - FTA 903 screen.
  • Click the tab that says “Add Block” It will bring up the FTA 904 cut block detail screen, where you will fill in:
  • The exact name of the block that was supplied by the licensee’s NoC.
  • The planned gross and net area. Regardless of actual areas, use 0.6 ha.
  • The start date identified on the NoC,
  • Click the save button.
  • The block will be now in the block listing at a PP stage. Change the status from PP to HB and click save.

4. Appendix 1

Comments:

  • All blocks will be identified/captured in FTA.
  • No new front end ESF.
  • CIMS reporting and risk ranking will work.
  • Residue and Waste reporting will work.
  • Full RESULTS reporting both attribute and spatial as per usual. LRDW spatial will be captured here.
  • Simpler process for licensee.
  • Allows blocks to be added in RESULTS as FTML.
  • Licensee FTA submission is simplified and should be reduced in cost.
  • LRDW will show only one small triangular block until spatial is captured by RESULTS reporting.
  • Performing clearance on triangle shaped 0.6 ha “fictitious block” - it will be unknown if there any conflicts outside the 0.6ha fictitious block. Therefore the constraints (exclusions & save and excepts) from the adjudication of the licence document need to be copied/carried forward to the CP document.
  • CP will be SSS designation when it is not really. Prescribed inclusion of a CFA 1 CP code in the(fta:blockDescription field, will allow for sorting and reporting, thus reducing potential inaccuracies in provincial statistics
  • FTA will only accept blocks of < 1 ha, due to this SSS designation. Using a standard size of 0.6 ha improves data integrity and assists in sorting of cutblocks under a one CP
  • If crown land is added or subtracted from the CFA, the FSP will need to be amended andthe 1 CP Exhibit A will need to be amended
  • An XML/GML ESF upload will be required for RESULTS entries requiring spatial.
  • If MFLNRO issues a CP over the entire CFA there could be tenure over tenure if there are existing issued CP’s. Early closure of all other valid CP’s is required before the new 1 CP can be issued. CP closure will be as per the current processes (note only existing CPs that have had either no harvest or all harvest completed can be easily closed. Any existing CPs that are only partially harvested may be problematic to close (take or pay issue) and need to be carefully considered and discussed with the licensee before closing).

5. Appendix 2–Notice of Commencement (NoC) Form

The NoC form is required under Section 85 [Notification of timber harvesting and road construction] of the Forest Planning and Practices Regulation (FPPR).

The NoC is to be submitted to the District Manager (or the approved representative) before beginning timber harvesting or road construction. Submission is usually in the form of an email with an attached map. It may also be submitted by fax, mail or in person. The NoCcontent is as follows:

(Some forest districts have a form on their district website which can be filled in and emailed. This can be suitable if it captures the following information.)

CFA Number: / Name of Holder:
Phone: / e-Mail:
Contractor Name:
Harvest
Timber Mark: / Cut Block ID:
(Block ID/name set at this point will be permanent block name used to reference block throughout reporting cycle.)
Add New Block Entry to FTA:  / DO NOT Add New Block Entry to FTA: 
Roads
Road Permit Number: / Road Section ID:
Start up Date:
Enter the date when the activity will begin(yyyy-mm-dd).
The date that felling will begin in the cutblock will also be the date that the silviculture obligation begins / or / Re-start Date:
Enter the date when the activity will begin again after an inactive period of 3 months or more (yyyy-mm-dd)
Site Location: Describe the location of the cutblock or road construction

Site Location Notes:

It is strongly recommended that this is a pdf copy of thesite plan map required by FPPR Section 34attached to an email. (Note: This map is provided to communicate general location of harvest, and is not intended to show block boundaries.)

Other ways of describing the site location are:

  • GPS coordinates(latitude and longitude values)
  • UTM values (zone and easting and northing coordinates)
  • PDF of a map showing the approximate location of the block or road in the woodlot and associated roads
  • Written description of travel directions

6. Appendix 3 – Sample XML of 1 CP Application

<?xml version="1.0" encoding="UTF-8"?<esf:ESFSubmissionxmlns:esf=" xmlns:gml=" xmlns:mof=" xmlns:fta=" xmlns:xsi=" xsi:schemaLocation="

esf:submissionMetadata

<esf:emailAddress>mailto:</esf:emailAddress

<esf:telephoneNumber>2502267792</esf:telephoneNumber

</esf:submissionMetadata

esf:submissionContent

<fta:FTASubmission

<gml:boundedBy

<gml:null>inapplicable</gml:null

</gml:boundedBy

<fta:submissionMetadataProperty

<fta:SubmissionMetadata

<fta:districtCode>DAB</fta:districtCode

<fta:clientCode>00142700</fta:clientCode

<fta:clientLocationCode>00</fta:clientLocationCode

</fta:SubmissionMetadata

</fta:submissionMetadataProperty

<fta:submissionItem

<fta:HarvestApplicationWithCP

<gml:boundedBygml:null>inapplicable</gml:null</gml:boundedBy

<fta:forestFileID>W1832</fta:forestFileID

<fta:applicationDescription> Woodlot 1 CP Application -not a SSS Application

</fta:applicationDescription

<fta:district>DAB</fta:district

<fta:applicationPurpose>N</fta:applicationPurpose

<fta:cuttingPermitID>D</fta:cuttingPermitID

<fta:location>W1832</fta:location

<fta:markingInstrumentCode>H</fta:markingInstrumentCode

<fta:markingMethodCode>S</fta:markingMethodCode

<fta:deciduousIndicator>false</fta:deciduousIndicator

<fta:catastrophicIndicator>false</fta:catastrophicIndicator

<fta:cruiseBasedIndicator>false</fta:cruiseBasedIndicator

<fta:crownGrantedIndicator>false</fta:crownGrantedIndicator

<fta:salvageTypeCode>SSS</fta:salvageTypeCode

<fta:cutblockMember

<fta:CutBlockWithCP

<fta:cutBlockID>1</fta:cutBlockID

<fta:applicationPurpose>N</fta:applicationPurpose

<fta:blockDescriptionsss indicates wl 1 cp</fta:blockDescription

<fta:plannedGrossArea>0.6</fta:plannedGrossArea

<fta:plannedNetArea>0.6</fta:plannedNetArea

<fta:cruiseVolume>999</fta:cruiseVolume

<fta:plannedHarvestDate>2011-01-01</fta:plannedHarvestDate

<fta:extentOf

<gml:PolygonsrsName="EPSG:26911">

<gml:outerBoundaryIs

<gml:LinearRing

<gml:coordinates

459099.38,5497490.56 458981.14,5497491.45 459041.03,5497593.12 459099.38,5497490.56

</gml:coordinates

</gml:LinearRing

</gml:outerBoundaryIs

</gml:Polygon

</fta:extentOf

</fta:CutBlockWithCP

</fta:cutblockMember

<fta:cutblockMember

<fta:CutBlockWithCP

<fta:cutBlockID>2</fta:cutBlockID

<fta:applicationPurpose>N</fta:applicationPurpose

<fta:blockDescriptionsss indicates wl 1 cp</fta:blockDescription

<fta:plannedGrossArea>0.6</fta:plannedGrossArea

<fta:plannedNetArea>0.6</fta:plannedNetArea

<fta:cruiseVolume>999</fta:cruiseVolume

<fta:plannedHarvestDate>2011-01-01</fta:plannedHarvestDate

<fta:extentOf

<gml:PolygonsrsName="EPSG:26911">

<gml:outerBoundaryIs

<gml:LinearRing

<gml:coordinates

463726.42,5496190 463608.18,5496190.89 463668.07,5496292.56 463726.42,5496190

</gml:coordinates

</gml:LinearRing

</gml:outerBoundaryIs

</gml:Polygon

</fta:extentOf

</fta:CutBlockWithCP

</fta:cutblockMember

</fta:HarvestApplicationWithCP

</fta:submissionItem

</fta:FTASubmission

</esf:submissionContent

</esf:ESFSubmission