forest development standards 2012 revision · forest development standards 1.1. objectives the...

46
Forest Development Standards 2012 Revision

Upload: others

Post on 20-Jun-2020

2 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

Forest Development Standards

2012 Revision

Page 2: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 2 -

TABLE OF CONTENTS

1. FOREST DEVELOPMENT STANDARDS ....................................................................................... 4

1.1. OBJECTIVES .................................................................................................................................... 4 1.1.1. Qualified Personnel ................................................................................................................... 4 1.1.2. Environmental Management Systems ........................................................................................ 4 1.1.3. Safety ......................................................................................................................................... 4

1.2. REPORT SUBMISSIONS ................................................................................................................. 5 1.3. DEVELOPMENT MEETINGS .......................................................................................................... 5 1.4. EQUIPMENT STANDARD .............................................................................................................. 5

2. RECONNAISSANCE FIELD WORK ................................................................................................ 6

2.1. RECONNAISSANCE - INTENT ................................................................................................................ 6 2.2. FIELD PROCEDURES ............................................................................................................................ 6 2.3. RECONNAISSANCE REPORT ................................................................................................................. 7

3. ROAD LAYOUT .................................................................................................................................. 8

3.1. ROAD GRADES .................................................................................................................................... 8 3.2. SWITCHBACKS..................................................................................................................................... 8 3.3. LANDINGS ........................................................................................................................................... 8 3.4. ROAD TRAVERSE INFORMATION ......................................................................................................... 9

3.4.1. General ...................................................................................................................................... 9 3.4.2. Normal Road (Tabular Road Costs) .......................................................................................... 9 3.4.3. Engineered Road (ECE – Detailed Engineered Cost Estimates) ............................................. 10

3.5. ROAD MARKING................................................................................................................................ 10 3.6. ENGINEERED DESIGNS ...................................................................................................................... 11

3.6.1. Roads ....................................................................................................................................... 11 3.6.2. Bridges ..................................................................................................................................... 12

4. CUTBLOCK LAYOUT ..................................................................................................................... 12

4.1. GENERAL CONDITIONS ...................................................................................................................... 12 4.2. BOUNDARY TRAVERSING .................................................................................................................. 13 4.3. GROUND SKIDDING DISTANCES ........................................................................................................ 13

4.3.1. General Guidelines .................................................................................................................. 13 4.4. CABLE HARVESTING ......................................................................................................................... 14

5. RIPARIAN CLASSIFICATION ....................................................................................................... 16

5.1. FISH STREAM CLASSIFICATION / FISH BARRIERS .............................................................................. 17 5.2. NON-CLASSIFIED DRAINAGES ............................................................................................................ 17 5.3. WETLANDS........................................................................................................................................ 17 5.4. LAKES ............................................................................................................................................... 17 5.5. RIPARIAN CLASSIFICATION REPORT .................................................................................................. 18

6. WILDLIFE TREE PATCHES .......................................................................................................... 19

7. FOREST HEALTH ............................................................................................................................ 19

7.1. ROOT DISEASES ................................................................................................................................ 19 7.2. BARK BEETLES ................................................................................................................................. 20 7.3. INVASIVE PLANTS ............................................................................................................................. 21

8. FIELD MARKING – GENERAL ..................................................................................................... 22

8.1. CUTBLOCK BOUNDARY ..................................................................................................................... 22 8.2. WILDLIFE TREE PATCHES – INTERNAL TO CB ................................................................................... 22 8.3. WILDLIFE TREE PATCHES – EXTERNAL TO CB.................................................................................. 22 8.4. INDIVIDUAL WILDLIFE TREES- WITHIN CB ...................................................................................... 22 8.5. WETLANDS........................................................................................................................................ 23 8.6. STREAMS ........................................................................................................................................... 23 8.7. RIPARIAN RESERVE ZONES (RRZ) .................................................................................................... 23 8.8. ROAD MARKING BETWEEN CPS ........................................................................................................ 23 8.9. FIELD MARKINGS - RIBBON AND PAINT COLOR AND PURPOSE ......................................................... 24

Page 3: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 3 -

9. SITE PLAN DATA COLLECTION AND SUMMARY ................................................................. 25

9.1. SITE PLAN DATA COLLECTION .......................................................................................................... 25 9.2. SITE PLAN DATA SUMMARY ............................................................................................................. 26

9.2.1. Area Summary ......................................................................................................................... 26 9.2.2. Site Plan Summary ................................................................................................................... 26

10. DEVELOPMENT REPORT WRITE-UP .................................................................................... 26

10.1. GENERAL BLOCK DESCRIPTIONS ...................................................................................................... 26 10.2. HARVESTING ..................................................................................................................................... 27 10.3. ROAD BUILDING AND HAULING CONSIDERATIONS ........................................................................... 27 10.4. ASSESSMENTS AND SUPPORTING INFORMATION ............................................................................... 27 10.5. RIPARIAN CLASSIFICATION REPORT .................................................................................................. 28 10.6. APPRAISAL INFORMATION ................................................................................................................. 28 10.7. DEVELOPMENT REPORT SUBMISSION PACKAGE ............................................................................... 29

11. MAPPING STANDARDS.............................................................................................................. 30

11.1. OPERATIONAL MAPS ......................................................................................................................... 30 11.2. 2011 MAPPING STANDARDS .............................................................................................................. 30 11.3. MAPPING ERRORS ............................................................................................................................. 31

12. APPENDICES ................................................................................................................................ 32

WILDLIFE TREE RETENTION TARGETS ........................................................................................................... 32 CFP’S INTERPRETATION FOR TRAILS AND LANDINGS .................................................................................... 34 CP AND BLOCK SUMMARY ............................................................................................................................. 35 KAMLOOPS FOREST REGION / BCE SOUTHERN INTERIOR REGION LOCAL AREA AGREEMENT (LAA) DECEMBER 2001. ........................................................................................................................................... 36 FCL FISH BARRIER GUIDLINES ...................................................................................................................... 39 VERNON FOREST DISTRICT ROOT DISEASE POLICY 1998. ............................................................................. 41

Page 4: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 4 -

1. FOREST DEVELOPMENT STANDARDS

1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”) is to consistently produce high quality permits that are realistic to develop with available harvesting and road building equipment; and provide the necessary timber to meet Canoe Forest Products Ltd’s (CFP) needs. Success is a built road or a harvested block that does not materially adversely impact other interests and provides CFP with a positive contribution.

1.1.1. Qualified Personnel Consultants shall ensure their employees or approved subcontractors involved in implementing these Standards are qualified to carry out the specific tasks assigned to them.

Supervisory people responsible for development work must be registered members of the Association of BC Forest Professionals or Professional Engineers and Geoscientists of BC.

1.1.2. Environmental Management Systems Canoe Forest Product’s Ltd. has an ISO 14001 Certified Environmental Management System and is certified under the Sustainable Forest Initiative® Program (SFI®):

• All development workers must have General Awareness Training for the EMS and SFI programs and be knowledgeable of Canoe’s EMS including Noxious Weeds and Species at Risk. Training records are to be maintained and available on site.

• Best Management Practices as laid out in the applicable Environmental Field Procedures (EFP’s) - General, Supervision, and Development and Planning - must be adhered to.

• An Emergency Response Plan (ERP) for each new project must be completed.

• Pre-work Conferences must be completed for each project. All project workers are to sign the Pre-work Inspection form.

• Inspections are likely to occur on most projects.

• If incidents such as landslides, fires, spills are observed or occur an Incident Report Form (IRF) is to be filled out and provided to Canoe – see the ERP for further details.

1.1.3. Safety If work is not safe to complete then don’t do it. CFP requires Annual Safety Reviews and monthly audits. CFP also requires the consultant to be in compliance with Worksafe BC Acts and Regulations.

Page 5: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 5 -

1.2. REPORT SUBMISSIONS Where reports and assessments are requested they must be complete and error free and contain only the information pertinent to the CP or RP.

Any reports and / or assessments that are completed as part of any CFP timber development work must be signed, sealed, and certified by the individual who completed the work or signed off by the appropriate supervisor if the individual is not an RFT / RPF. The report is to include the following certification statement “I certify that the work described herein fulfills the standards expected of a member of the Association of British Columbia Forest Professionals and that I did personally supervise the work.”

1.3. DEVELOPMENT MEETINGS It is expected that meetings will be held regularly when development is active (at least bimonthly). During these meetings it is important to advise CFP of the issues related to CP development. Any variance from the Standards must be discussed and approved by CFP.

These meetings will also serve to bring forth any new business items or other topics that require discussion or comment.

1.4. EQUIPMENT STANDARD Consultants are to keep and maintain in good working order all equipment necessary to perform timber development work. The intent is to avoid lost time and the associated costs with vehicle or equipment breakdowns. This includes, but is not limited to:

• ATVs and snowmobiles are to be in good working condition.

• All trucks must have good winter quality (or equivalent tires) and chains.

• All trucks are to have two way radios in good working condition (antennas, receive / transmit clearly), with CFP road channels on them.

• GPS receivers and data loggers must be recent models in good working condition (cables, batteries, memory). Data loggers must support GPS road traversing.

Page 6: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 6 -

2. RECONNAISSANCE FIELD WORK

2.1. Reconnaissance - Intent For Cutting Permits where a recce is requested, CFP will provide maps detailing the scope of the recce area to be looked at including general

It is expected that the consultant will assign an individual that is responsible for implementing the recce from start to finish and that person shall be the one who is responsible for communicating with CFP’s staff.

block and road locations. For each Cutting Permit proposal CFP is to provide the consultant with a pre-development checklist (See Appendix) to ensure that CFP’s FSP results and strategies are being considered; and to ensure that CFP’s SFI commitments are being addressed as the development progresses.

A preliminary field review should be conducted with a CFP representative within the first week or two (or sooner) of the initial recce (depending upon the size of the area) to help clarify any initial development concerns (i.e. timber quality, volume, access). This initial field trip is intended to help avoid wasting time and effort looking at areas or routes that shouldn’t be looked at and to help clarify any additional planning issues that have arisen out of the initial recce. Development meetings will also be used to bring forward questions or concerns that may arise out of the recce process.

Once the consultant has completed the recce of the development area and there is a firm strategy for managing the intended area then a final field review will be planned with CFP. Final field approval of the field recce is required before the submission of the recce report and before the permit progresses to the development stage.

2.2. Field Procedures At all times the consultant will conduct field actives in a productive and cost efficient manner that meets the intent of the recce. This includes, but is not limited to:

• Using hand held GPS units for mapping timber types, road locations, streams, terrain features, etc.

• Planning D/L and S/L locations so as to avoid duplication or excessive overlap of areas or running unnecessary S/L’s where a walk through with an handheld GPS would suffice.

• Identifying controls (crossings, landings, yarding breaks, timber quality, etc.) before running G/Ls to avoid unnecessary grade-lines.

• Planning works appropriate for the time of season / rescheduling work when conditions are not conducive to good productivity (i.e. poor snow conditions – snow mobile access)

• Using of baselines (B/Ls) or stripe lines (S/Ls) only where appropriate. i.e. (where large permit areas or group selection are proposed and more detailed forest typing (vol / spp / terrain) is required)

Page 7: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 7 -

2.3. Reconnaissance Report When a Recce Report is requested by CFP it is to be brief and to the point and address the key issues.

The intent of the recce report is to collect enough information so that future development can be rationalized and so that future work can be planned for including assessments (VIA, TSA, AIA, etc.).

The recce report and map are to:

• Accurately (plus or minus10%) outline the size and shape of the CB's and proposed road location(s), major streams, terrain features. Use handheld GPS points wherever possible.

• A digital map will be submitted (at a relevant scale) with digitized block shapes, including WTPs and other internal reserves areas / leave areas, as well as road and trail locations. Other notations or descriptions (logging plan, beetle hazard, 2nd/3rd pass blocks, root rot, etc.) should be hand colored and are not required to be digitized.

• Detail the volume (net live), by harvest system and by silviculture system.

• Identify any portions of the original CFP recce plan that does not work or will not meet the intent / objective of the recce. Within the report state the reasons why and / or provide alternatives to the original proposal where practicable. CFP will file that information for future reference.

• Relate to the pre-development checklist (results and strategies, etc)

• Logging Plan – This includes issues that should be identified before any development occurs so that solutions can be provided early on and that doesn’t become a surprise later. This includes, but is not limited to, issues around landings (too small, not enough), tail holds / back guys (none), border line conventional / cable ground, long skids / forwards, etc.

• CFP must review any engineering work during the recce phase (bridges, oversized culverts, designed road).

• Identify issues and assessments required. If there are no concerns identified or assessments required - explicitly state it. Note whether or not a return visit to a site may be required due to snow cover. The following should be considered within the report:

1. Terrain Stability Assessments (TSA) – note if any areas of instability are observed on the recce map and described within the recce report.

2. Engineering – where practicable, identify all sections of proposed road that may require engineered designs or have engineered costs associated with them. This includes (but is not limited to) bridge crossings, culverts >= 2000 mm, fish stream crossings, side slopes > 60%, large gully / draw crossings or sections of potential instability.

3. Green-up - Ensure all adjacent openings have greened-up or will have greened-up by the scheduled year of harvest. This includes checking with Canoe files and / or conducting field checks. Within the appendix include a copy of the supporting information (survey maps, silviculture labels, and inventory labels, leader heights). Any issues

Page 8: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 8 -

related to green-up (i.e. missing info, or info that does not support block development) must be discussed directly with Canoe.

4. Age - Ensure that the stand meets the age requirements to justify harvest. On the Timber Licence stands must be > 75 years old on January 1, 1975. For all other stands the minimum age is 100 years, with the exception of lodgepole pine and hemlock which is 80 years. For Douglas fir and cedar <100 years, proof of culmination must be provided. Species mix must also be provided for the stand in question.

5. Riparian - Note all streams, wetlands and lake classifications where conditions permit. For fish stream classification note whether sampling or a Fisheries Biologist will be required. Note any downstream concerns. Include information on riparian areas in close proximity to blocks, along proposed roads and / or any roads requiring modification.

3. ROAD LAYOUT

3.1. Road Grades The following are recommendations with respect to road grades. Any deviations from these recommendations must be reviewed by an Canoe representative.

• Maximum favourable grade is 15% with pitches up to 18% ( for < 100m) so long as the road is straight through the steep pitch.

• Maximum adverse grades are 8%.

• Grades through the landing area must be less than 2% for 50m. Grades off a landing area should not exceed 6% for the first 20m.

• Switchback grades not to exceed 15%. Maximum adverse switchback grades are 5%.

3.2. Switchbacks • Switchbacks must have a minimum turning radius of 20 meters and

on be on ground slopes less than 40%.

• Switchback cuts and fills at centerline are to be calculated and recorded such that they balance out. This will require entering the switchback at a level grade and leaving the switchback at a level at a distance long enough for the grade to catch ground level (or the desired cut level at centerline).

3.3. Landings • Landings should be located on suitable ground slopes (0-25%) that

will allow for the construction of a 50m x 60m (0.3ha) area and service up to 10.0 ha area.

• There must be a minimum 25m cleared harvest area from the bottom a landing (including debris pile) to the timber harvest boundary edge. This is to facilitate burning of the debris pile while not burning adjacent timber or regenerated stands.

Page 9: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 9 -

• Locate landings on the town side of the block (within or external to the block boundaries). Where this is not possible, the landing location must be reviewed with CFP.

• Skidded and forwarded wood must flow into the back (bush side) of the landing to facilitate the processing of logs and flow of wood through the landing and on to the logging truck. Where this is not possible, the landing must be reviewed with CFP.

• Landings must be clearly marked with 3 pink ribbons and blaze indicating CP, Block, and Landing #.

• Where the center of the landing is offset, it should be clearly marked and referenced from the road centerline.

• A diagram will be produced for landings that have been identified as having special construction and / or landing layout requirements that are considered critical to harvesting.

• The landing diagram will be mapped at an appropriate scale (1:1000 or 1:2,000) and will show landing shape and orientation, processor and skid trail location as well as debris piles. The diagram will inset on the logging plan map and must be approved by CFP.

3.4. Road Traverse Information

3.4.1. General • Traversing of roads is not to proceed until CFP has given the

permission to go ahead.

• Prior to traversing, a sketched road map must be reviewed by a CFP representative to indicate road numbering.

3.4.2. Normal Road (Tabular Road Costs) The following guidelines are to be adhered to when carrying out the road traverse for normal (tabular road costs):

• GPS traversed to an accepted standard. End product will consist of road traverse notes in a digital Road Eng format.

• All road traverse stations (GPS/tight-chain) must be no more than 30m apart on road centerline

• The following features must be captured:

• Terrain - gullies, draws, ridges, benches

• Block boundaries, trail / road junctions, and landings. • All classified streams and non-classified drainages.

• Side slope information 15m either side of the road. Collect multiple side slopes wherever the terrain presents itself, survey crews are not to average side slope information in the field.

• Record % Rock (Interior Appraisal Manual method). Include assessment of any rock - rippable or blastable and probable ballasting. Rock includes large boulders (greater than 1.5m in diameter). Look at existing roads nearby to establish a baseline.

Page 10: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 10 -

• Calculate and record culvert sizes using culvert cards. Culvert cards are to include stream measurements, channel gradient and angle (skew) to the road. These cards are to be included with the road traverse notes. Remember that natural drainage patterns are to be maintained.

• Roads which require sub-grade modifications or the replacement of bridges or large culverts must be traversed. All streams within this type of road (outside of block) will require stream classifications (supporting information must be provided to CFP). Any roads of this nature should be reviewed by CFP to determine required work.

• The road traverse information is to be summarized in a tabular form as per the Interior Appraisal Manual. The road sections should be in multiples of 0.1 km. It is expected that the information can be derived from the road notes - it is not a requirement to spend extra time gathering this information. The appraisal is based on the best estimate.

• A hand drawn sketch map needs to be included for all roads, which join onto a Forest Service Road. This sketch should include the size of culvert at the junction, the distance of line of sight and the angle at which the 2 roads join.

3.4.3. Engineered Road (ECE – Detailed Engineered Cost Estimates)

More detailed traverse information is required for Engineered Road sections. This includes ground that is: terrain class IV and V, uphill side slopes greater than 50 percent, Rock % greater than 50% (IAM method), end haul construction areas, overland construction areas (i.e. extensive filling), bridge crossings, and forwarding roads.

• All engineered sections are to be tight chain traversed. Stations are to be 10 to 15 meters apart.

• End haul spoil site locations must be identified on the town side of section where spoil material is being created. Spoil sites are to be reviewed by CFP.

• Clearly identify any slope breaks or terrain features which may benefit the design of these roads. Ensure that side slope data extends out to at least 30m (or further where necessary) so that all relevant features are collected (breaks, benches, rock outcroppings, bluffs, etc.).

3.5. Road Marking • Road centerlines are to be marked in pink ‘Road Location’ ribbon with

the ribbon hung as high as practicable. Traverse stations will be marked with lime green ribbon. R/Ws are generally logged in the winter, for this reason all ribbon must be hung as high as possible and be easily identified in any weather conditions wherever possible. All ribbons are to be hung on the stems of trees and not on brush or branches where possible.

• Landings are marked three pink ribbons, blazed and numbered on the centerline of the road. If the center of the landing is offset from the

Page 11: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 11 -

road location the blaze on the centerline must reference the actual center of the landing and the center is to be marked with 3 pink ribbon and blazed.

• All culverts are marked with a double pink ‘Road Location’ ribbon with the actual culvert size marked on the ribbon and recorded in the traverse notes.

• Stations are to be blazed no further than 200m apart. Blaze both sides of the tree and include the road #, traverse station and cumulative HD. Station blazes are also required at the following: POC / POT of all roads, POC / POT of rock >50% (IAM calculation), POC of all switchbacks, at classified stream crossings, POC / POT of slopes > 55% uphill side slope, all road / trail junctions, block boundaries.

• Reference Trees will be marked every 500m. RTs are required at the following: POC / POT of all roads, POC / POT of rock >50% (IAM calculation), POC of all switchbacks, at classified stream crossings, POC / POT of slopes > 55% uphill side slope, all road / forwarding road junctions, and block boundaries. RTs will be marked minimum of 15m horizontal distance from the center of the road location and always on the uphill side of the road. RT will always be blazed at Breast Height on the tree and show the RT number, HD and bearing from the tie point to the road stations below (note that the field notes will show the bearing and HD from the road station to the RT number). Toe blaze RT and at centerline with RT#, distance and bearing. Reference trees will be blazed and lightly spray painted in glow orange. Road stations will be blazed, in both directions and lightly sprayed in orange.

3.6. Engineered Designs

3.6.1. Roads • Direction for designs will be given to the engineer by CFP and may

involve a field review. Design work must comply with the recommendations of any relevant TSA final report.

• Type of road must be determined prior to traversing and design (Long term or Short term). Most of CFP roads are long term.

• Minimum clearing widths are 20m for slopes under 25%, slopes of 25-50% are 25m and slopes over 50% have a minimum width is 30m unless otherwise designed.

• Ditches are not required on all permanent roads and can be minimized where it may benefit the plan. Our main concern is to maintain natural drainage. This can be done by in-sloping or out-sloping the roads (rock or steep sections).

• Road running surface widths are a minimum of 5m unless they are designed.

• Each page of plan view drawings must include an overview map of all of the roads for that project. In the overview, the section, which is designed, must be highlighted for that individual page. This should be displayed in the top right hand corner.

Page 12: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 12 -

• On every plan view there must be a direction arrow indicating the direction to town.

• Drawings for roads are to be on 11”x17” sheets. 2 copies are required.

• Detailed cost estimation must be included in the final package: Engineering cost of office and field work, mob and de-mob of all equipment to the site and rehabilitation of the road after construction if designed as a short term road with a life span less than 7 years.

• Right-of-way boundaries are to be marked in the field once the final design has been submitted and approved by CFP. Stations are to be painted on the topside of the R/W in blue paint, blue ribbon and marked with one painted vertical blue stripe.

• Culverts sizes are to be painted on a tree on both the top and bottom of the R/W indicating the angle which the culvert should be skewed to the road.

• All field stations / index numbers must match the cross sections and plan view.

3.6.2. Bridges • Field site reviews for bridges will be planned with the Engineer and

CFP prior to design work. All sites must be reviewed prior to final road location and traversing.

• Type of bridge must be determined prior to design (type of cribbing, perm, temp, steel string, concrete slab and type of decking).

• All bridges must have an L-75 load rating and 16 ft running width.

• Detailed cost estimation must be included in the final package, which will include mob and de-mob of all equipment and bridges to the site if designed as a short term road.

• 2 copies are required for bridges and are to be on 11”x17” sheets.

4. CUTBLOCK LAYOUT

4.1. General Conditions The following standards are with respect to cutblock layout. Deviations from these standards must be reviewed by a CFP representative and the consultant should provide sufficient rationale as to the deviation.

Layout personnel are to make themselves aware of the requirements for Forestry Operations under the Occupational and Health Safety Regulations (OHSR) (Part 26). Any issues related to safety are to be brought to the attention of CFP.

Maximum clear-cut opening size is 40.0 ha (this includes adjacent non-greened up openings). Deviations from this are acceptable only if the situation has been identified early in the recce stage and direction has been given by CFP. Reserve widths - direction will be given by CFP. The intent is to avoid aggregate cutblock openings and / or contiguous openings > 40.0 ha.

Page 13: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 13 -

4.2. Boundary Traversing • Traversing of block boundaries is not to proceed until CFP has given the

permission to go ahead.

• All block boundaries are to be GPS traversed where practicable. Where the GPS is not practicable default to tight chain traversing.

• Block boundaries adjacent to existing openings are, generally, not to be GPS traversed. Ortho images are be used to map these edges. Exceptions are when the GPS person must walk the boundary edge to get to a feature that has to be GPS traversed.

• Falling Corners will be blazed and metal tagged with FC, CP and block number. See Sect. 7.0 Field Marking.

• For tight chain traverses the closing error must be < 1.0%

• Hand traverse notes will be submitted with the Development package.

4.3. Ground Skidding Distances

4.3.1. General Guidelines Maximum skid distances for conventional skidders on various slopes:

Continuous Slope Skid Distance -15% to -10% 100 to 150 m -10% to 0% 150 to 200 m 0% to +20% 400 meters

+20% to +35% 350 meters

• See section 26.16 - OHSR Forestry Operations for maximum slope operability for logging equipment. In brief, rubber tire skidders are restricted to 35%; Feller bunchers, hoes, and bulldozers are restricted to 40%; and specially designed equipment is restricted to 50%. Where these slopes are exceeded trails are required.

• Winter blocks developed for skidders should have very little adverse skidding. Any such areas that will require adverse skidding, are to be noted on the map for possible return trail construction in poor snow conditions.

• Bladed or excavated skid trails are to be indicated on the LP and SP map.

• Where a skid trail/yarding road junctions another road from below; ensure that the steepness of the upper road’s fill side is considered. It must be practicable to create a skid trail connecting to the road location.

• For shorter slope lengths (40 –70m) between 35% and 50%, block layout for hoe chucking must be considered.

• Areas within blocks that have portions of hoe chucking or cat ground (hand felling) must be identified as such. These areas have to be identified on the log plan map.

• If possible, consider forwarding trails for RT skidders to be used in conjunction with bulldozer or hoe chucking.

4.3.1.1. Marking Skid and Forwarding Trails Marking and traversing skid / forwarding trails are required when:

Page 14: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 14 -

• 2 blocks are joined together by a specific forwarding trail location.

• A trail is used rather than a road.

• Specific trail locations are required for cable harvesting.

• A trail is required through some type of reserve area.

• The trails will be used as a permanent structure within a group selection.

• A trail will be used outside the block to access timber within the harvest unit.

• Mobile tail holds can be used inside or outside of the block.

• Trails that will be used for the yarder should be identified and discussed with a CFP representative.

4.4. Cable Harvesting The following guidance should help reduce the number of complications that arise.

• CFP requires experienced cable layout contractor personnel.

• It is important that deflection lines represent reality and not unlikely chances. The consultant’s person responsible for layout must field review deflection lines and hang the boundary to ensure that deflection is realistic.

• Cable yarding should be a minimum of 4.0 ha if there are other cable blocks on the same road system.

• Stand alone cable blocks must have a minimum of 3,000 m3.

• CFP’s cable contractor uses a Madill 120 swing yarder with a 15 meter tower height.

• All D/Ls must show adequate deflection that generates sufficient payloads (>1,000kg) to landings.

• Run appropriate D/Ls (point settings or yarding roads)

• Mobile backspars and mobile backguys are to be utilized wherever practicable. This is necessary to gain yarding efficiencies and keep costs down.

• No Intermediate Supports are to be used in CFP’s cable layout.

• Deflection lines (D/L) must be numbered and match any mapping. If deflection is obvious 1 D/L should be run and the entire area described in the block summary.

• Any D/Ls in close proximity of a road or trail must have a D/L station outside of the R/W clearing width so that it can be easily identified after road or trail construction. All D/Ls are to be in blue / white striped ribbon with yellow ribbon stations.

• Where steep ground exists in the permit area, roads and landings should be positioned for present or future cable yarding efficiency. Backguys should be identified where first pass will remove all stumps. For example, defer harvest patches containing trees that can be used as anchors.

Page 15: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 15 -

• If the area is laid out for continuous settings, deflection has to be ensured along the entire area for swing yarders. If deflection is critical for a swing yarder in a specific location, that location must be marked in the field.

• Yarding roads must be traversed and have appraisal information collected. Yarding roads are to be summarized in the Road Appraisal Information Sheet.

• Where applicable, yarding roads and back-spar trails are to be extended to cutblock edges (i.e. don’t stop short of the cutblock boundary as this creates more work for yarding set up).

• D/L stations must show all relevant terrain features and slope breaks and should be no further than 30 meters apart.

• Minimum yarding distance should not be less than 100 meters - unless it is a corner of a block or a small portion of a larger block. If a specific circumstance arises a CFP representative should be notified. If mobile tail-holds for a swing yarder can be utilized then shorter yarding distances are acceptable. These situations must be discussed prior to layout. Mobile tail-spars should be utilized in all swing yarder blocks where possible. All mobile trails must be flagged.

• The maximum grade for back-spar trails is +/- 30%

• The maximum grade of a yarding road is +/- 15%. Where yarding to occur 5%.

• A brief description should appear in CB summary detailing:

• Trees for possible tail-holds / back-guys / intermediates (ie. dbh, rooting depth, species, health, number). Sound Fd, Sx, Hw > 40 cm dbh are preferred for back guys.

• Tail trees /must be large diameter (>50cm dbh) and of good form and quality (Fd, Sx, Hw) with enough room and adequate stumps to guy back to. This is especially critical along existing opening edges where timber has been removed and / or stumps have degraded.

• Tail trees, when suitable and available, cannot exceed 5 m in height. Use of tail trees should be the exception and not the rule. I.E. Use sparingly.

• If a CB has no or poor quality tail-holds, describe the situation and explain the process required to use a mobile tail spar or deadmen (if required). All guy stumps must be described in the block summary.

• All areas of poor or marginal deflection should be described in your block summary. Things to be considered - chokers rather than grapple and a description of tail trees so that the rigging can be lifted higher.

• Yarder locations must have adequate tie-backs and tail-holds and safe guy angles of 450 or less by WCB standards. Guy-line clearances must be identified in the field and included into the harvest boundary.

• Tail trees, back-guy stumps that are critical to cable logging must be marked. These trees must be marked with a horizontal green band @ 70cm on the tree with a ‘BG’ painted on two sides above the line. Back guy stumps must be marked, where required, around landings and along R/Ws to ensure that the conventional harvesting does not remove these options.

• Width of area for possible yarder settings - considering road or trail cut. Describe the terrain where the yarder settings are to be located in order to

Page 16: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 16 -

ensure that wood can be adequately and safely landed in front of the yarder. Describe the cut, which may be caused from the construction of the yarder road. This area maybe able to be used as a right-of-way landing. The road cut or landing cut must be accounted for when using Logger PC to do payload analyses.

• Cable harvesting must be split out in the area summaries in our final reports from other harvest systems.

• All landings are to be on the town or dump side of the yarding so as not to impede truck traffic and landing production.

• Shorten the forward distance as much as possible. Distances over 400 meters must be brought to the attention of a CFP representative during layout.

5. RIPARIAN CLASSIFICATION All watercourses (streams, wetlands and lakes) within and in close proximity to CP blocks must be classified for purposes of the Site Plan. All watercourses that are crossed by roads (proposed / modification) and that will be used to access CP blocks must be classified for Road Permit purposes. Consultants are required to provide a riparian classification report, which clearly and defensibly details how the watercourses were classified. The riparian classification report will provide a breakdown of the watercourses in the CP by block or road and will contain the necessary information used to classify the reach. The riparian classification report will also include any wetland or lake classification and supporting information. The consultant will provide an experienced and competent (RFT, FIT, RPF, RP Bio) assessor to conduct riparian assessments and classifications. It is expected that these individuals will be familiar with fish sampling procedures and the reference material listed below. This person will be responsible for preparing the riparian classification report as well. For CFP’s purposes, the minimum necessary information for stream classification includes:

• average channel / wetted widths / average depth / gradient • reach length • description of channel / bed morphology / CWD • RMA vegetation (for streamside retention prescription purposes,

Basal Area retention) • description of any barriers to fish passage • description / rationale for non-classified drainage sections

Stream classification’s are to be made in conjunction with the stream information collected in the field and the LAA flow chart, as well as the following:

• Kamloops Forest Region/BCE Southern Interior Region Local Area

Agreement (LAA) December 2001 • CFP’s FSP Sect 3.4 Water, Fish, Wildlife and Biodiversity within Riparian

Areas. - Results • FCL's Fish Barriers Guidelines written by Jason Kurtz, RP Bio.

Page 17: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 17 -

• Part 4: Division 3 – Riparian Areas - FPPR

For purposes of the definition of a ‘larger S6’ stream, the stream must:

• Maintain a water surface width of at least 1.5m throughout the year.

Large S6 streams in question should be assessed throughout the year, where practicable (i.e. recce, layout, assessments, etc.) in order to determine if the year round flow width is met. Estimates are okay as long as some rationale is provided.

5.1. Fish Stream Classification / Fish Barriers The LAA, in conjunction with Fish Barrier Guidelines will be used wherever practicable to classify stream reaches as non-fish bearing. It is important for the consultant to identify sections of low gradient (<20%) streams that cannot be written off by the LAA so that the appropriate stream sampling assessments can be completed.

Individuals conducting stream assessments must understand the difference between “obstructions” and “barriers to” fish passage. The assessor must also collect sufficient stream information when assessing potential fish stream reaches and collect that information with the LAA in mind.

Where there is doubt as to the fish habitat potential of a stream or to possible barriers then the consultant needs to convey to Canoe Forestry staff the need for other professional opinion (i.e. fish biologist).

5.2. Non-classified drainages Non - classified drainages are those flow areas that do not meet the definition of a stream. Unclassified drainages will be operationally treated as follows:

1. No field marking but mapped and identified accurately on SP and LP map (NC’s are not to be GPS traversed)

2. Operational strategy: • Fall and yard away • Treat as “No Machine Zone” - limit any traffic and do not skid

down (subject to site disturbance guidelines) • If encountered, control any ground water

5.3. Wetlands Wetlands within or in close proximity to block boundaries require assessment and classification. The stream report must contain sufficient information to justify the classification. The management strategies will be outlined as per the Riparian Management Area Guidebook. In addition, W3 wetlands have additional FSP Results.

5.4. Lakes Lakes in close proximity to block boundaries require assessment and classification. The stream report must contain sufficient information to justify the classification. The management strategies will be outlined in the Riparian Management Area Guidebook.

Page 18: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 18 -

5.5. Riparian Classification Report • To be included within the Development Report.

• Stream classification is to be summarized in a tabular format by block and / or road.

• This report must state the assumptions (Reg's, LAAs, etc.) used to make the classifications.

• A map, which shows stream classifications, fish sampling, etc., must also be provided (1:10000).

Page 19: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 19 -

6. WILDLIFE TREE PATCHES

Wildlife tree Patches (WTPs) are to be retained at the percentage specified under Section 3.8 Wildlife and Biodiversity – Stand Level of CFP’s approved FSP. These percentages are based upon FDU / Landscape unit BEC subzones within OSFD (Table 5 – Appendix 11.1). The area of WTP retained within the cut block will be calculated using the NAR of the cutblock. Each individual cutblock within the CP must contain a minimum of 50% of the requirement listed in Table 5, with the remaining balance met over the CP.

In most cases the results and strategies of the FSP dictate where a portion of the WTP is placed (e.g. marten and fisher). Where practicable, WTPs are to be distributed throughout the cutblock based on the 500m rule and may be internal or external (or both) to the cutblock boundary. Where practicable, WTPs are to be placed in areas that are constrained from the timber harvesting land base and may include, but are not limited to, OGMAs, riparian reserve zones (FPC and OSLRMP), inoperable or NP areas. WTP areas are should be representative of the stand being harvested and at a minimum contain a component of mature conifer or deciduous stems (i.e. not 100% alder patch). Where WTPs contain wetlands or wetland complexes, the wetland area must be netted out of the WTP area.

External WTPs are to be marked with ‘Wildlife’ ribbon and blue paint along the cut block edge. The area outside of the block is not be marked or traversed, but should use logical boundaries such as streams, draws, ridges, roads, etc. that are easy to define and map.

WTPs are to be numbered by block in the field. For example, CP 400 has 3 blocks and 1 WTP in each block. Number the WTPs 1-1, 2-1 and 3-1.

7. FOREST HEALTH

The initial assessment of forest health factors or disease incidence should be identified during the recce phase. Root rots (A.ostoyae and P.weirii) and bark beetles are the primary forest health factors that CFP manages for. Forest health assessments should be integrated with general prescription assessments as much as possible. Specific forest health surveys should be carried out only where an initial assessment indicates they are necessary.

7.1. Root Diseases The SP walkthrough is an essential step in the root disease management process and provides an opportunity to evaluate stand hazard and risk as well as the general incidence of damaging agents.

The Vernon Forest District Root Disease Policy Dec 1998 is to be used (See Appendix). If applicable, Blocks may be stratified into three differing root disease incidence levels: Low, Moderate, or High. Sketch maps are to be provided for moderate and high incidence areas. Only High incidence stratums will be stumped.

Page 20: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 20 -

Root Rot Treatment Maps (i.e. stumping) - hand sketch maps are appropriate. Use logical boundaries (roads, streams, slope breaks etc.) to map treatment areas that will be easy for equipment operators to identify in the field. The minimum treatment unit is 1.0 ha.

7.2. Bark Beetles The decision to survey for bark beetles (IBM, IBD, IBS IBB) is dependent on the threshold levels as identified in the initial assessment and will be directed by CFP staff. Ground survey methods change with the bark beetles being assessed. Two survey methods used are walkthroughs and probes. Walkthroughs are non-systematic, ground reconnaissance surveys, usually done prior to full probes. Full probes are generally not recommended unless there is uncertainty about the population within the CB. Formal beetle probes will be directed by CFP staff.

Page 21: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 21 -

7.3. Invasive Plants

Under Section 5.1 Measures, within CFP’s approved FSP. To prevent the introduction or spread of species of plants that are invasive plants under the Invasive Plant Regulation, if the introduction or spread is likely to be the result of CFP’s forest practices (see field guide to Noxious Weeds). In the course of carrying out forest development work consultants will note the occurrence and location of any of the noxious weeds that are listed in the table titled “Habitat Susceptibility to Invasive Plants by BEC Zones (LCP FDUs)” under Section 5.1 of the FSP.

A detailed field survey is not required

A comment is to be made within the recce report stating which noxious weeds, if any were found with there general location sketched on the recce map with the proper notation (IAP Code Index).

-observations while driving through areas and / or through the course of development work will suffice. Areas to check are generally associated with disturbed sites – existing roads, trails, landings and existing openings. The area we are concerned about is within 500m of any proposed cutblock or proposed road under development. Identification of most noxious weeds will be easiest when the plants are flowering (May – August), however some weeds (Bull / Canada Thistle) are still identifiable after the plant is dead.

The following websites contain more information on species identification: http://www.weedsbc.ca/

http://www.for.gov.bc.ca/hra/Plants/application.htm

Page 22: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 22 -

8. FIELD MARKING – GENERAL

8.1. Cutblock Boundary • Orange “Timber Harvesting Boundary” ribbon to be used. Lime green

stations. • Boundary ribbon must be hung as high as possible, facing the block, and on

trees that can be easily seen in any season of harvest. • Boundaries are to be painted with 2 blue horizontal painted strips – as high

as possible. • Proposed boundaries that follow existing opening edges are not to be marked

(flagged / painted). • Falling Corners (FC)

• FCs are to be metal tagged and tree blazed (3 sides) and lightly painted with orange

• Mark the blaze with the FC #, CP # and block # only • Hang with 2 “Timber Harvesting Boundary” ribbons and 1 lime green

ribbon • WTP FCs are to be different from boundary FC’s (don’t repeat numbers).

• Falling corners are to be marked in the following instances: • Classified streams on the boundary (existing opening edges included) • Major block corners • On the topside of any road where the road enters a cutblock (Blazed

outside of the R/W). • Start / end of WTPs • Approximately every 200 m in the absence of the above

8.2. Wildlife Tree Patches – Internal to CB • Marked with orange “Wildlife” ribbon and painted with blue paint. • FCs are to be numbered, metal tagged and tree blazed with WTP number.

8.3. Wildlife Tree Patches – External to CB • Marked on external cutblock boundaries using orange "Wildlife" ribbon. • Falling corners must be at the start and end of the WTP. FCs are to be

numbered, metal tagged and tree blazed with WTP number. • WTP boundaries outside of cutblock (excluding actual cutblock boundary) are

a mapping exercise and are not to be marked in the field. • Use logical boundaries such as streams, draws, ridges, roads, etc. that are

easy to map.

8.4. Individual Wildlife Trees- Within CB • Orange “Wildlife” ribbon to be used.

Page 23: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 23 -

• Trees are to be marked with an orange paint “W” on 3 sides for easy identification.

8.5. Wetlands • To be excluded from the timber harvest area with either Wildlife ribbon or

Timber Harvest Boundary. • The RMZ is to be clearly marked with orange ribbon “Stream Protection

Zone” parallel to the wetland edge. • W3 wetlands have additional FSP results and strategies – see Canoe’s FSP.

8.6. Streams • Centerlines of classified streams are to be clearly marked with a horizontal

band of red paint. Trees are to be marked on all sides for easy identification. • Stream must be numbered and marked in the field with a FC at the top and

bottom of the cutblock. Where the stream begins or terminates within the block and not at a boundary a single blaze with the stream number is required.

• S-class streams are to be traversed and mapped. • The Riparian Management Zone (RMZ) is to be clearly marked with orange

“Stream Protection Zone” ribbon at the specified RMZ distance. • Ribbon has to be “closed” if creek ends or begins within CB and along

boundaries and roads. Ribbon is to be clearly visible from road. • Stream number and classification is to be painted in red paint at road

intersection and or CB boundary or at beginning and end of stream if ending and or beginning within CB.

8.7. Riparian Reserve Zones (RRZ) • RRZ boundaries are to marked with Timber Harvest Boundary or Wildlife

ribbon and painted with blue paint.

8.8. Road Marking between CPs Where a proposed road within an existing CP (that will be harvested first) will extend ahead into another CP, the road is to be marked as follows. • Mark the new proposed road in yellow up to the original CP cutblock edge. • Toe blaze and paint traverse stations (below 30cm on tree) along the

proposed centerline. • Outside of the original CP cutblock use pink road location ribbon. • The intent is to prevent R/W crews from continuing on into the new cutting

permit without approval.

Page 24: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 24 -

8.9. Field Markings - Ribbon and Paint Color and Purpose Purpose - To Mark: Ribbon

Color Paint Color Wording on Ribbon

Boundary; Metal Tags at Falling Corners (FCs)

Orange Blue: 2 horizontal

lines

Timber Harvest Boundary

Split Lines – SU’s (only as directed)

Orange Special Management

Riparian Management Area (RMA)

Orange Red Creek Centerline

Stream Protection Zone

Wildlife Tree Patch (WTP) Orange Blue – Inside Of CB

Boundary

Wildlife

Individual Wildlife Trees Orange Orange W

Wildlife

Final Road Location, Final Landing Location; Metal Tags and Blazes at Stations

Pink Orange blazes

Road Location

Bladed Skid Trail Location Only mark when: - yarder / forward roads - mobile backspar trails - trail outside the confines of

the block - permanent access - trails required between

blocks - through a WTP

Red Orange blazes

Skid Trail

All recce work - winter weight – final grade - Summer weight – recce

grade

Yellow

Cruise Strips, , Baselines, Beetle Probes

Blue/Yellow Stations

Yellow (cruise plots)

Forest Health; Trap Trees Pink

Forest Health

Deflection lines: -Station must be outside of clearing width of Forward trail or road. - D-lines are to be numbered and all references must match what is in the field

Blue/white stripped with

yellow stations

Station Markers (Roads, Trails, Boundary)

Lime green

Back Guy / Tailspar Green BG

1 horizontal band

R/W Station # / Index # painted on tree

Blue Blue: 1 vertical line

Page 25: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 25 -

9. SITE PLAN DATA COLLECTION AND SUMMARY The consultant will be responsible for the collection of Site Plan data and summary of information but will not be required to fill out or submit the Site Plan document. Consultants will provide an area summary worksheet.

The consultant will provide experienced and competent (RFT, FIT, RPF) individuals to collect and summarize site plan information. It is expected that these individuals will be familiar with BEC principles, forest health factors, riparian classification and silviculture regeneration principles and will have experience collecting SP field data within CFP’s operating area.

9.1. Site Plan Data Collection The following Site Plan information is to be collected for all cutblocks:

• Site Plan information is to be collected on FS 39A SP plot cards

• Fill SP plot card out to the extent necessary to describe the site SU

• Use scratch pits, root wads to check variability of soils in a block. Brief notes written as part of the walkthrough assessment which describe variability of sites within a block are more useful than a bunch of plots thrown into a block. Generally, 1 plot per SU / 20.0 ha is sufficient – it is not necessary to sample each site series with a SP plot. SP plots should be used to confirm what the assessor sees on his/her walkthrough.

• Where a site series is of a minor component or there is variability in the sites within the SU label the SU with the leading site series and lump the remainder (i.e. 01700530). Describe the label – ‘01 sites on dry slopes and ridges and 05 sites along seepages and depressions’. The intent is to avoid unnecessary SU stratification and / or duplication of SUs that could be combined into 1 unit.

• Describe understory pole / sapling layers with regards to the quality / distribution for streamside or visual retention.

• In high value Grizzly bear habitat (OSLRMP) – important berry producing site series – ensure that the required amount of Vaccinium spp. by site series are present within the block.

• Forest Health – see section 6 Forest Health – Stand Level Surveys

• Soil hazard assessment – fill out soil compaction, displacement, erosion only.

• Sample tree data – not necessary to collect data. Information regarding tree ages, heights, dbh, etc. should be collected within the recce phase.

• Photographs of SP plot soil pits are not

• The SP data collection plots shall be marked and identified in the field. The plot will be marked with the plot number, 2 yellow ribbons, the date, and crew names. .

required.

Page 26: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 26 -

9.2. Site Plan Data Summary The following Site Plan data summary is required:

9.2.1. Area Summary • An area summary map that shows all gross block shapes including external /

internal WTPs / leave areas and all external / internal landings, yarding roads, trails is to be produced. Preference is to have block shapes (any shape with an area) to be produced as an Arc shape file. Block shapes are to have areas attached to them.

• An area summary worksheet that summarizes each block. Area summary worksheet will be provided by CFP (Appendix).

• For purposes of calculating TAS and PAS consider CFP interpretation sheet provided by Greg Hislop, February 2001 (Appendix).

• WTPs – see Section 5 Wildlife Tree Patches and Appendix.

9.2.2. Site Plan Summary • CFP Site Plan document is not to be filled out.

• A Site Plan map (digital) will be produced as previously provided by the consultant – no changes.

• A brief write up (point form letter) that identifies any additional site sensitivities such as wind throw, stocking issues, riparian, forest health issues, etc. that should be brought to the attention of CFP’s Foresters.

• Submit original SP cards – do not submit any photocopies.

• SP Plot photos are optional – digital copies (not film) are preferred.

The consultant must meet with the appropriate CFP forester, well in advance of any submission, to review SP areas, final SP maps and summaries.

10. DEVELOPMENT REPORT WRITE-UP The function of the development report is to convey what the blocks are comprised of (spp / vol) and how the blocks will be developed. Constraints or anticipated difficulties to harvesting and development are also identified within this report. The development report also functions as place to tie in the other block assessments and supporting information (i.e. Site Plan, Stream Report, D/L’s, etc.).

10.1. General Block Descriptions • For the cutting permit provide a general overview description and volume

break down by block for the entire CP.

• The CP block summary will include a tabular breakdown that shows the Gross Area, NAR, WTP / Other area, Timber Type (%), Average Ht and Dbh, Harvest and Silviculture system (see Appendix).

Page 27: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 27 -

10.2. Harvesting • For each block include a tabular breakdown that shows the NAR and

Volume by Harvest System, Season of Harvest, Max. Skid / Yarding Distance, landings, etc. (see Appendix).

• Be brief and to the point. The purpose of this section is to provide a brief description of the block and the general harvest plan. Any special consideration or items that need attention drawn to them should be identified here.

• A summary of field marking must be presented.

• This section of the Development Report should be a stand-alone document, which can be copied and given to the appropriate staff.

10.3. Road Building and Hauling Considerations • A tabular summary of road requirements is required. The summary must

include landings required (existing or proposed), proposed road requirements, yarding roads, culverts <1000mm, culverts > 1800 mm and specific comments.

• Be brief and to the point. The purpose of this section is to provide a brief description of the roads and road construction required. Any special consideration or items that need attention drawn to them should be identified here.

• This section of the Development Report should be a stand-alone document, which can be copied and given to the appropriate staff.

10.4. Assessments and Supporting Information • Green-up summary is to be provided as it relates to specific blocks (i.e.

creates the formation of non-green up aggregate openings). If green-up information was collected as part of the recce do not include it as part of the development report (do not duplicate information).

• In order for a block to be classified as “greened up” it must meet the following:

• Min. 700 sph > 1.3m over 75% of the NAR of the existing block

• Average height of the tallest 10% of trees over 75% of the NAR of the existing block is > 2.0m

• A summary of LRMP and other resource issues (Visuals, Range, etc.). Related to the Pre-development checklist.

• A summary of field reviews and assessments – in progress, required, completed, N/A.

• Original road traverse field notes are to be included. A copy of the RoadEng road notes is only required for engineered sections.

• D/L analysis – plotted at mappable scale. Must include profile, payload and tensions as well as rigging lengths. Back spar rig up heights should also be shown on the deflection line plots.

• Stumping maps if applicable (with digital polygons)

• Slope maps are no longer required.

Page 28: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 28 -

• Logging Plan Maps. Copies of logging plans and comments must be provided to CFP for review well in the advance of plotting final maps and the Development Report submission.

10.5. Riparian Classification Report • The Riparian Classification Report is a stand-alone document that can be

placed on our legal files (double sided and not bound).

• Stream data is summarized in a tabular format by block and / or road.

• This report must state the assumptions Reg's, LAAs, etc used to make the classifications.

• A map, which summarizes the findings, must also be provided (1:10000).

• Submit original filed cards (no photocopies required).

• Stream photos are only required where the assessor feels they are necessary to support a stream classification. Digital images are preferred if submitted.

10.6. Appraisal information The information is required to provide an estimation of conditions that will be incorporated into the CP application. See the Interior appraisal manual for specific detail required for Cutting Permit appraisals.

Appraisal information is to be gathered during final road location traverse.

• Road appraisal information is to be by section - a section is a minimum of 100 m - sections are to be kept as long as possible and averaged over the length of road which has similar terrain.

• As a section is completed, rock content is to be estimated. Use roads nearby to form a baseline.

The Interior Appraisal Manual method of calculating % rock is:

Rock Ht2 /Cut Bank Ht2 = Percentage Rock

32 / 62 = 9/36 = .25 x 100% = 25% Rock

if a cut bank is 6 m high with 3 m of rock

Page 29: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 29 -

Road appraisal data information is to be summarized as follows:

Road Appraisal Data Information for CP 948 Canoe Forest Products Ltd. F.L. A18670

BCG Zone Identification Table

Section Identity BCG Zone Length (km) 130.001 IDFmw2 0.461 130.101 IDFmw2 0.276 130.140 IDFmw2 1.695 130.150 IDFmw2 0.718

Appraisal Data Table

Section Identity

Road Type (LT,S,Snow/ Ice)

Section Length (km)

Uphill Side Slope (%)

Rock (%) IAM Method

130.001 0+000 – 0+115 LT 0.1 25 25 0+115 – 0+287 LT 0.2 15 20 0+287 - 0+353 LT 0.1 35 20 0+353 – 0+461 S 0.1 20 15

Road Type LT– Long term S – Short term Snow/Ice Road

10.7. Development Report Submission Package • Double sided copies where practical

• Plastic map sleeves are not required as these are usually discarded after the maps are taken out of the report (cost savings to consultant).

• RoadEng road notes (engineered roads only)

• All original filed cards and notes are to be submitted – no photocopies are required.

• All report information is to be put on archival quality CD’s. This information includes, but is not limited to the following:

• Recce report and maps

• Riparian Classification Report, maps and photos

• Development Report

• RoadEng road notes and maps

• LoggerPC deflection line analysis

• All Arc files

• SP area summary work sheets

• SP summary letter

• Photos

Page 30: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 30 -

• Any scanned information (hand sketched maps - .pdf)

Not required in the development binder submission

• Exhibit A maps

• GPS Traverse maps

• RoadEng road traverse notes and plans (non-engineered road)

11. MAPPING STANDARDS

11.1. Operational Maps Operational maps include:

• Cutting Permit,

• Road Permit, Cruise,

• Site Plan, Logging Plan, and Stumping.

Operational maps are to be submitted as part of the Development submission (including digital information) with the exception of cruise maps, which will be produced at a later date. In some cases CFP will conduct the Operational mapping; therefore prior to completing any mapping the consultant must ensure who will be conducting the mapping.

11.2. 2012 Mapping Standards

Contact Patti Schmidt for new logos and digital information associated with Canoe Forest Products Ltd. All data will be supplied to CFP in an ArcGIS file geodatbase or in shape file format Please include the Licence, CP and Block fields for all feature classes or shape files to enable selective map display of detail. Note the fields (hi-lighted) as short integers (from old microstation levels) to be imported into CFP’'s geodatabase. These codes are used in symbolizing features. Digital data of feature classes indicated as 'Base', is not required as a deliverable. Symbology and/or labels may be altered or substituted where space is limited or to enhance clarity. Symbology for 'cruise' and 'stream class' maps is not included - consultants’ discretion.

Page 31: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 31 -

Mxd templates of the map surrounds will be provided. These surrounds include title blocks, legends and tables. Please adhere to these templates as much as possible – standard sizes of 11”X17” and 8½”x11” A style file of distinct CFP symbols will be provided.

Any questions related to mapping standards are to be directed to Patti Schmidt – [email protected] – Ph: 250-833-1232

11.3. Mapping Errors Mapping errors account for a large percentage of additional administrative cost to CFP. As with reports, the individual who is responsible for signing off on the report will also be responsible for signing off on the technical quality and completeness of the mapping. Where avoidable and unnecessary mapping errors and omissions are made by the consultant, corrective measures will be made at no cost to CFP.

Page 32: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 32 -

12. APPENDICES

Wildlife Tree Retention Targets

Table # 5 Wildlife Tree Retention Area Percentage Requirements FDU LU BEC

Subzone

Retention % (percentage of the

Net Area to Reforest)

South Shuswap

Salmon Arm ESSFdc 11

South Shuswap

Salmon Arm ICHmk 7

South Shuswap

Salmon Arm ICHmw 7

South Shuswap

Salmon Arm IDFmw 7

South Shuswap

Salmon Arm MSdm 8

South Shuswap

Eagle ESSFvc 4

South Shuswap

Eagle ESSFwc 9

South Shuswap

Eagle ICHmw 6

South Shuswap

Eagle ICHvk 7

South Shuswap

Eagle ICHwk 7

White Lake White ESSFwc 9 White Lake White ICHmw 7 White Lake White ICHwk 9 White Lake White IDFmw 4 Three Valley Eagle ESSFvc 4 Three Valley Eagle ESSFwc 9 Three Valley Eagle ICHvk 7 Three Valley Eagle ICHwk 7 Three Valley Kingfisher ICHwk 7 Three Valley Kingfisher ICHvk 6 Three Valley Kingfisher ESSFvc 4 Three Valley Kingfisher ESSFwc 9 Pukeashun Pukeashun ESSFwc 8 Pukeashun Pukeashun ICHmk 7 Pukeashun Pukeashun ICHmw 7 Pukeashun Pukeashun ICHwk 10 Pukeashun Pukeashun IDFmw 5 Crowfoot Crowfoot ESSFwc 10 Crowfoot Crowfoot ICHmw 9 Crowfoot Crowfoot ICHwk 11 Crowfoot Crowfoot IDFmw 4

Page 33: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 33 -

TFL33 Anstey TFL ESSFwc 9 TFL33 Anstey TFL ICHmw 8 TFL33 Anstey TFL ICHwk 10 Anstey Anstey ESSFwc 5 Anstey Anstey ICHmw 3 Anstey Anstey ICHvk 7 Anstey Anstey ICHwk 7 Seymour Seymour ESSFvc 4 Seymour Seymour ESSFwc 7 Seymour Seymour ICHmw 7 Seymour Seymour ICHvk 6 Seymour Seymour ICHwk 8 Table 5 is consistent with the draft wildlife retention targets provided by a letter from the District Manager, Okanagan Shuswap Forest District, May 12, 2005.

Page 34: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 34 -

CFP’s Interpretation for Trails and Landings

Trail Accounting: Area of

NPR TAS NAR SP Location

Proposed trail within block No Yes Yes NAR Existing trail within a block Yes No No Other Existing trail outside block Yes No No Other Proposed trail outside the block in timber

No Yes Yes NAR

Proposed trail that will be used to access subsequent passes of timber.

Yes No No PAS

Proposed trail outside block in an existing cutblock that isn't free growing.

No Yes Yes NAR

Landing Accounting: Area of

NPR PAS NAR SP Location

Existing Landings in the block Yes Yes No PAS Proposed Landings in the block Yes Yes No PAS Existing Landings outside block Yes No No Other Proposed Landings outside block Yes Yes No PAS

For maximum allowable soil disturbances on a cutblock we will follow the SAFD's DM Policy 195-30. Therefore, Wildlife Tree Patches on, or outside, the block boundary will not be considered part of the gross area of the block (not including peninsular type patches).

Page 35: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 35 -

CP and Block Summary

CP Summary Block # Gross

Area *Net Area WTP

Area Species (by %) Avg

Ht Avg Dbh

Harvest System

Silv. System

1

2

3

4

TOTAL

*Net Area = Gross area minus existing and proposed roads and right-of-way, existing landings (not proposed landings), WTP, NP, or other noted deductions

Block Summary Harvest System Net Area Net Live m3 Harvest

Season Max. Skid Distance

# of landings

Net Live R/W wood volume m3 inside

block

Net Live R/W wood volume m3 outside

block

Conventional

Swing yarder

Skyline

Hoechuck

LGP

Helicopter

TOTALS

Page 36: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 36 -

Kamloops Forest Region / BCE Southern Interior Region Local Area Agreement (LAA) December 2001.

Page 37: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 37 -

Page 38: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 38 -

Page 39: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 39 -

FCL Fish Barrier Guidlines

Page 40: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 40 -

Page 41: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 41 -

Vernon Forest District Root Disease Policy 1998.

Page 42: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 42 -

Page 43: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 43 -

Page 44: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 44 -

Canoe Forest Products - Pre Development Checklist

Federated Co-operatives Limited

CP Block Associated Roads

must be filled in

Checklist for full FRPA Blocks and Roads Check Check Detail or Comments

(Intent is to review GIS information to see what Attach maps where clarity is applies to block and roads) Yes No required 3.3.1.2 Great Basin Spadefoot Habitat 3.3.1.3 "Great Basin" Gopher Snake Habitat 3.3.1.4 Flammulated Owl 3.3.1.5 Fringed Myotis 3.6 Community Watershed 3.9 OGMA Conflict 4.1 Lakeshore Management Zone 4.2 Recreation Site 4.2 Recreation Trail 4.3 Scenic Areas Zone 1 5.1 Basic CWD 5.2 Basic and Enhanced CWD High BEO Grizzly MH to High Habitat Marten High Capability Habitat Marten - Habitat Fly Hills Fisher Moderate Habitat 5.3 Intensive Recreation Shared Use (all season) Shared Use (summer) Summer Non-motorized Snowmobile Winter Non-motorized X country Skiing/ Non-motorized 5.5 Tourism Areas Back Country Dispersed Use Tourism Use Out of Zone 1 but in Tourism Area 5.7 Marten Areas General Resource Management High Capability Habitat Marten Habitat - Fly Hills 5.8 Fisher Areas General Resource Management Moderate Habitat 5.9 Big Horn Sheep Area 5.10 Objectives

Page 45: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 45 -

Community / Crown Interface Grizzly MH to High Habitat Moose Winter Range and MMU Mountain Goat Mule Deer Winter Range Walk-in Lakes 5.11 Williamson's Sapsucker 6.1 FSW - Okanagan Region 6.2 FSW - Thompson Region 7.2 Range land GAR Orders U-8-001 Mule Deer U-8-004 Mountain Caribou U-8-005 Mountain Goat U-8-006 Moose WHA Caribou Joss Mtn South 8-226 Caribou Joss Mtn 8-227 Caribou Joss Mtn Corridor 8-228 Caribou Specified Area 8-233 Grizzly Specified Area 8-232 SFI SAR Animals Caribou Western Grebe Great Basin Spadefoot Mormon Fritillary Plants Bearded sedge Brown beak-rush Satinflower Yellow widelip orchid Ecological Communities Red-osier dogwood/sedges Few-flowered spike-rush/hook-mosses Three-way sedge SFI - Birds with potected nests Bald eagle, Osprey, Burrowing owl Peregrine falcon, Gryfalcon, heron Other Species (in use) SFI - Special Sites Ecological Archaeological Site

Page 46: Forest Development Standards 2012 Revision · FOREST DEVELOPMENT STANDARDS 1.1. OBJECTIVES The objective of having Forest Development Standards (hereafter called “Standards”)

SOP–2012 REVISION

- 46 -

Cultural Geological Summary:

Note: If "Yes" is indicated items will need to be addressed consistent with the FSP prior to the Site Plans being signed.

Checklist Completed by: Date: