Communiqués

Administrative Boundaries Project & Business Applications - January 2014

• Unit Table
• District & Region Changes
• Current to New Transition Diagram

On March 3rd, 2014 an Order in Council to change the structure of the current FLNRO regional and district organizational model will be put into effect.  This includes a transformation from a 3 region/29 district model to an 8 region/24 district model.  As part of this transition, changes will include district amalgamations, as well as the conversation of the current Coast, Southern Interior and Northern Interior regions into 8 new regions.

High level changes:

• 6 districts will be expired
• 1 new district will be added
• 3 existing regions will be expired
• 8 new regions will be added
• 4 districts will conduct name changes

Please refer to the attached Current to New Transition Document for a high level overview of changes.

As you may be aware, each region and district is assigned a 3-letter code value. To help minimize the number of impacts, any pre-existing district code values will be kept as-is; with the exception of Selkirk District, which is net new, as well as the 8 new regions. A listing of code values can be found in any of the attached documents. Also note that any district undergoing a name change will continue to use the existing code. For example; DKA - Kamloops Forest District will now be DKA - Thompson Rivers Natural Resource District.

How this affects FLNRO Applications:

The Information Management Branch within the NRS manages the FLNRO region/district code values and names in a centralized database table called ORG_UNIT. This table is utilized by approximately 40 FLNRO business applications (including, FTA, RESULTS, ECAS, HBS, etc). On March 3rd, 2014 this table will be updated to reflect the new structure and this will have many downstream affects within the Ministry applications as well as external processes, such as electronic data submissions. The IMB is undergoing a major project to align the affected business applications for the upcoming changes.

Please refer to the attached TO BE ORG UNIT SPREADSHEET for a comprehensive view of what changes will be made to this database table.

What does this all mean to you?

Any FLNRO electronic data submissions where a district or region code is identified may be impacted (specifically where an existing code value is being expired or a new code is added). Please be aware of the upcoming changes and what that means to your submission process. As of March 3rd, 2014 any region/district values that are not part of the new FLNRO structure will no longer be accepted in your submissions.

Questions?

If you have any questions, please contact your existing FLNRO business support channels, who will provide you with further information and/or routing to an appropriate resource. Or submit a question here:  https://www.for.gov.bc.ca/his/efm/abp-ba-sub.htm

Supplemental documents:

Current to New Transition Document - A high level visual representation of the transition from 3 regions 29 district model into the new 8 region 24 district model.

District and Region Changes Spreadsheet - Another look at the transition from the 3 region 29 District model into the new 8 region 24 district mode. Notable changes are in red font.

TO BE ORG UNIT spreadsheet - For more technical folks, a mock-up of what our FLNRO database table (called ORG_UNIT) will look like once the changes are applied on March 3rd, 2014. Note that all changes are in red font. ORG_UNIT table is the one table in the FLNRO database that contains the district and region code values and names. This table is used internally by many FLNRO applications. The org unit code values are used externally to the FLNRO applications in various ways (such as ESF submissions).

For more information please contact:  Dave.Andersen@gov.bc.ca

October 2, 2013 - RESULTS Online Training Sessions - Fall 2013

There will be six RESULTS on-line training sessions offered for the Fall 2013. Online registration can be accessed via: https://attendee.gototraining.com/49x6s/catalog/3931598846459390464

• Oct 29, 2013 10:00-11:00 am Core Module 1: Obligation Reporting: Policy and Business Context
• Oct 30, 2013 1:00-2:00 pm Core Module 2: Obligation Reporting: Online Entry and Mandatory ESF Conditions
• Oct 31, 2013 10:00-11:00 am Core Module 3: Obligation Reporting: Submitting by ESF
• Nov 5, 2013 1:00-2:00 pm Core Module 4: SU Modifications-Overview
• Nov 6, 2013 10:00-11:00 am Core Module 5: SU Modifications-ESF Set-up
• Nov 7, 2013 1:00-2:00 pm Core Module 6: SU Modifications-Online Capabilities

RELEASE New Results SU Legislative View available in the BC Geographic Warehouse (BCGW) for Ministry internal use 

There is a new RESULTS attribute-only layer in IDWPROD1 called WHSE_FOREST_VEGETATION.RSLT_STNDS_UNIT_LEGISLATIVE available for internal Ministry use.

This view indicates the legislative framework each standards units is managed under along with a number of derived data that relates to SU modifications. It contains a Forest Stewardship Plan (FSP) reference if the standard unit contains a standards regime ID which is also included in a FSP. Due to the use of Ministry Defaults standards regime ID in FSPs, and in some cases multiple FSPs, it is not possible to systematically identify which FSP the SU reference, so up to three FSPs are identified and the user would have to manually identify which one. The view also contains tenure, client, biogeoclimatic ecosystem classification and milestone information.

This view is an attempt to assist in bulk reporting basis but will not achieve 100% accuracy. The logic used to assign legislation reference code is based on preset assumptions based on legal dates and data coding practices. Transitional legal framework periods, special circumstances, usage related to MOF Defaults standard regimes and poor data coding practices may cause incorrect legislative reference code assignment and would require manual verification.  The derived data in this view requires care in interpretation and use. Important decisions should be referring to the RESULTS source data, if required.

The key data elements in this view that is of interest are as follows:

FIELD	NOTES
LEGISLATION_REF_CODE	WL-Woodlot; CFA-Community Forest Agreement; NONLEG-Non- Legislated; FRPA-FRPA; FPCFDP –Forest Practices Code with Stocking Standards; FPCPRES-Forest Practices Code; PFPC-Pre-Forest Practices Code; UNKN-Unknown
FSP_ID (1,2,3)	While a SU can be associated to one FSP, when there is MOF Defaults SS IDs, they maybe associated to multiple FSPs which will not enable a one-to-one linkage.
FSP_NUMBER	Provides number of FSP found using the same SS ID (caused by MOF Defaults existing in FSPs).
FSP_AMENDMENT_NUMBER (1,2,3)	Provides the most recent FSP amendment number that is either APP (Approved) or INE (In Effect).
FSP_PLAN_NAME (1,2,3)
FSP_STATUS_CODE (1,2,3)
FSP_PLAN_START_DATE (1,2,3)
FSP_PLAN_END_DATE (1,2,3)
MOF_DEFAULT_STANDARD_IND	Indicates if the SS ID (Standards Regime ID) is a MOF Default
PLAN_TYPE	Shows whether SU is a Silv Prescription (no SS ID) or Site Plan (has SS ID).
FSP_PRESC_TO_PLAN_IND	Set to “Y” when a SU underwent amendment changing from silv prescription to site plan.
APPROVED_VARIATION_IND	Set to “Y”when there is an Approved Variation tracked for the opening under SU History.
OPEN_AMENDMENT_REQ_APP_IND	Set to “Y”  if the opening underwent a silviculture prescription amendment
OPEN_AMENDMENT_REQ_APP_NO	Number of silv prescription amendments tracked for the opening
MIN_PREF_STOCK_EXIST_IND	Set to “Y” if the SU that has a minimum preferred stocking value
OPENING_FRPA_S197_IND	Set to “Y” if the opening that had a s197 rollover tracked under SU History
FSP_FRPA_S197_IND	Set to “Y”, if the FSP associated with the SU has a s197 Election (for any of the FSP APP or INE amendments)

 Data dictionary for RSLT_STNDS_UNIT_LEGISLATIVE is located at:  https://www.for.gov.bc.ca/his/results/RSLT_STNDS_UNIT_LEGISLATIVE_VW.pdf

General Requirements document that highlights how the view is built with assumption, limitations, and logic is located at:  https://www.for.gov.bc.ca/his/results/General Business Requirements SU Leg View-May 16 2012 v6.pdf

At this point, known issues for this view are as follows:

• PFC_PRESC_TO_PLAN: Indicator is not currently working as intended. There are null values and records that are not showing up as "Y" where expected.
• FSP_ID: Not all FSP IDs are showing up as expected. There are null values when there should be FSP IDs.
• LEGISLATION_REF_CODE: UNKN - Unknown has a larger than expected amount that ended up in this category that would likely benefit from future enhancement to improve classification.

Any questions regarding the SU Legislation View should be directed to Matt LeRoy.

Please note RESULTS 4.8.12 is being deployed to production.  The release will address the following items:

• Opening View fixed to include latest Client;
• Duplicate Opening Numbers during add new opening and opening definition submissions are no longer allowed;
• Woodlot Exhibit A spatial map rendering for first time forest cover entries fixed;
• Site Index is now mandatory for polygons with Stocking Status = IMM, NSR or MAT unless it is a Reserve;
• WSS now optional for layers 1, 1S, 2, and 2S for polygons with Stocking Status = IMM;
• Explicit error message generated when trying to delete an opening that has a SPAR sowing request.

October 2, 2012 – Update – FIXED - ISSUE with geoprocessing using RESULTS business views inside the BCGW warehouse (LRDW)

All of the RESULTS business views in the BCGW warehouse should now function properly in geoprocessing operations. RESULTS business views in the BCGW warehouse include:

• WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_INV_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_SILV_SVW
• WHSE_FOREST_VEGETATION.RSLT_PLANTING_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW
• WHSE_FOREST_VEGETATION.RSLT_ACTIVITY_TREATMENT_SVW
• WHSE_FOREST_VEGETATION.RSLT_STANDARDS_UNIT_SVW

Please report any RESULTS specific geoprocessing issues to Application Help

July 20th, 2012 – Update - ISSUE with geoprocessing using RESULTS business views inside the BCGW warehouse (LRDW)

The following RESULTS business views in the BCGW warehouse should now function properly in geoprocessing operations:

• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_INV_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_SILV_SVW
• WHSE_FOREST_VEGETATION.RSLT_PLANTING_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW
• WHSE_FOREST_VEGETATION.RSLT_ACTIVITY_TREATMENT_SVW
• WHSE_FOREST_VEGETATION.RSLT_STANDARDS_UNIT_SVW

Please note, WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW is currently under repair and should not be used directly in the BCGW without first exporting from the warehouse.  Once it has been exported from the BCGW warehouse WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW does not appear to yield inaccurate or incomplete outputs in geoprocessing operations. Please report any inconsistent geoprocessing outputs.

To speed things up, WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW has also been exported from the BCGW warehouse and is posted to the FLNR FTP site.  

Please be advised that we have not experienced any difficulties using the non business view (svw) RESULTS featureclasses, these appear to be functioning as expected when run directly in the GEOBC warehouse.

Please contact Application Help if additional help is required.

June 14, 2012 – ISSUE with geoprocessing using RESULTS business views inside the GEOBC warehouse (LRDW)

It has come to our attention that when running geoprocessing operations using the RESULTS business views in the GEOBC warehouse incomplete and potentially inaccurate outputs may result.

The RESULTS business views include:

• WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_INV_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_SILV_SVW
• WHSE_FOREST_VEGETATION.RSLT_PLANTING_SVW
• WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW
• WHSE_FOREST_VEGETATION.RSLT_ACTIVITY_TREATMENT_SVW
• WHSE_FOREST_VEGETATION.RSLT_STANDARDS_UNIT_SVW

Prior to geoprocessing please first export the RESULTS business view(s) of interest from the GEOBC warehouse.

Geoprocessing using RESULTS business views that have first been exported from the GEOBC warehouse does not appear to yield inaccurate or incomplete outputs.

A set of RESULTS Business views has been exported from the GEOBC warehouse and is posted to the FLNRO ftp site at:
https://www.for.gov.bc.ca/ftp/HFP/external/!publish/RESULTS_Business_Views_exports/
These exports will be updated every week until the issue is remedied.

Please be advised that we have not experienced any difficulties using the non business view (svw) RESULTS featureclasses, these appear to be functioning as expected when run directly in the GEOBC warehouse.

Please contact Application Help at nrsenquiries@gov.bc.ca if additional help is required.

March 15, 2012 – ESF Submissions to RESULTS

Please be advised that when making ESF submissions to RESULTS using a BCEID  that has both client and org unit authorities the client authority will take precedence.

For example, a BCEID associated with a client name of ACME Ltd. and an org unit of DCK making an ESF submission on behalf of DCK will receive an error message that their submission has been rejected.  The same BCEID making a submission on behalf of ACME Ltd. will not experience any difficulties.

Please note that BCEID’s with multiple client authorities and no org unit authorities, or BCEID’s with multiple org unit authorities and no client authorities will not experience this problem.

The new protocol for the scenario where a BCEID has both client and org unit authorities is that you need to use 2 separate BCEIDS:

• one for all your Client Number access(es), and
• one for all your District Access(es).

We are encouraging a consistent naming convention for this 2nd BCEID:

BCEID\LastNameDA, where DA stands for District access, i.e.  BCEID\JohnsonDA.

Please contact Cher Mckittrick, RESULTS access coordinator for help with new BCEID’s or NRS Enquiries if additional clarity on this issue is required.

March 13, 2012 – Stocking Standard Id’s (SSID’s)

Stocking Standard Id’s (SSID’s) are associated with a specific forest stewardship plan (FSP) and are authorized for usage by licensees and districts identified in the FSP in the Forest Stewardship Plan Tracking System (FSPTS).

Authorized licensees may use the FSP’s SSIDs for new site plans or to modify an existing site plan.  Please be advised that when a licensee is removed from the FSP in FSPTS, they can no longer use the FSP’s SSIDs to assign SSIDs in a new opening or to modify any existing openings that had used the FSP’s SSIDs.

Work around:

In RESULTS:

In cases where clients have been removed from FSPs  as a plan holder (because they no longer have any licences under the FSP) and are needing to add SSID’s from the FSP in question to a site plan, NRS Enquiries with approval from the business lead for RESULTS, can add a client for the particular SSID.  Alternatively, clients can copy the existing SSID into a new SSID.  Be advised that new SSID’s require district approval before use.

In FSPTS:

A separate option through FSPTS is to remove the applicable licences from the FDU tab (FSP600 screen) only and leave the client number under the Agreement Holder on the Information tab (FSP300 screen).  Maintaining the Agreement Holder Client number will continue to provide the license holder with access to the SSID under the FSP, and provide a workaround for inactive licensees wishing to retain the ability to amend SSIDs for the FSP in question.

January 27, 2012 – RESULTS Live Meeting Training Sessions in Feb and March 2012

Please be advised that three RESULTS Live Meeting sessions will be offered to interested licensees, contractors and government staff. Session description and registration can be accessed using the following links:

• Obligation Reporting – February 27, 2012 from 10:30 to 12:00pm
• SU Modifications/Amendments & Updates – March 6, 2012 from 1:30 to 3:00pm
• Using RESULTS Reports - Corporate Reporting System (CRS) – March 7, 2012 from 1:30 to 3:00

  All courses will be recorded for subsequent viewing opportunities.

January 16, 2011 – Ministry eziLink™ Training Recordings available for viewing

Please be advised that Live Meeting recordings are available for Using eziLink™ to Submit to RESULTS. This training was offered to Ministry staff who are involved with reporting into RESULTS.

First module provided high level overview on eziLink™ functionalities. Second module provided a “hands-on” approach to enable users to create their own ESF submissions and attaching spatial to their submission components.

EziLink™ Training/a

December 19th, 2011 – RESULTS spatial data update.

It has come to our attention that one opening and one forest cover polygon are causing geometry exceptions and resulting in the failure of RESULTS openings, reserves and forest cover polygons from being exported successfully from the GEOBC LRDW. For users with IDIR access to the GEOBC LRDW please exclude the following features from any export or geoprocessing operations using RESULTS spatial data.

From WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW, please exclude opening_id 58036 (opening_id <> 58036)

From WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_INV_SVW, please exclude forest_cover_id 2268565 (forest_cover_id <> 2268565)

From WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_POLY, please exclude forest_cover_id 2268565 (forest_cover_id <> 2268565)

From WHSE_FOREST_VEGETATION.RSLT_OPENING_POLY, please exclude opening id 1114761 (opening_id <> 1114761)

From WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW, please exclude opening id 1114761 (opening_id <> 1114761)

We are working to correct the issue. Users with BCEID access only will have to wait until the issue is rectified before being able to successfully download these feature classes from the GEOBC LRDW.

December 15, 2011 – RESULTS DATA Guidelines for entering BWBS BEC codes into RESULTS, Direction on stocking standards and amendment submissions

December 5, 2011 – RESULTS reserves are once again SUCCESSFULLY replicating to the LRDW.

Please be advised that reserves information uploaded to RESULTS via the Electronic Submission Framework (ESF) is once again successfully replicating to the LRDW (GeoBC Geographic Warehouse). As a result the following layers are now up to date:

1. WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW

Please do not attempt to re-submit reserves information previously uploaded to RESULTS via ESF that had not replicated properly between mid-2009 and December 3,2011 as these reserves were queued for processing and should now be contained within the WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW layer currently in the warehouse.

Live Meeting EziLink Training for RESULTS ESF Submissions for Ministry Staff 2011/12 – Dec 6 and Dec 7, 2011

EziLink™ is an e-submission tool for development and submission of XML/GML files to MFLNR through the Electronic Submission Framework (ESF). The training course will cover the use of EziLink™ to create RESULTS submissions.

Suggested audience:

District staff interested in making spatial submissions to RESULTS should consider taking EziLink™ training. District staff not using EziLink™ will be limited to online edits in the RESULTS application.

• Course 1 - Dec 6: Overview of the EziLink™ program, outline of EziLink™ features, spatial manipulation, modifying XML.
• Course 2 - Dec 7: Create XMLs for recently disturbed areas and recently surveyed areas.

Participants are not required to attend both sessions but are strongly encouraged to do so as the sessions will build on previous learnings.

Following this course, attendees will have a basic understanding of the capabilities of EziLink™ and how to utilize it to create RESULTS Submissions.

Course delivery will be via Live Meeting. Registration is done via the following website: https://www106.livemeeting.com/lrs/8002144422/PublicEvents.aspx

October 26th, 2011 – Openings, silviculture activities, standards units, planting, and forest cover information is once again SUCCESSFULLY replicating to the LRDW.

Please be advised that new openings, silviculture activities, standards units, planting, and forest cover information uploaded to RESULTS via the Electronic Submission Framework (ESF) is once again successfully replicating to the LRDW (GeoBC Geographic Warehouse). As a result the following layers are now up to date:

1. WHSE_FOREST_VEGETATION.RSLT_OPENING_POLY
2. WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW
3. WHSE_FOREST_VEGETATION.RSLT_OPENING_VW
4. WHSE_FOREST_VEGETATION.RSLT_STANDARD_UNIT_SVW
5. WHSE_FOREST_VEGETATION.RSLT_ACTIVITY_TREATMENT_SVW
6. WHSE_FOREST_VEGETATION.RSLT_PLANTING_SVW
7. WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_INV_SVW
8. WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_SILV_SVW

It is important to note that new forest reserves uploaded to RESULTS via the Electronic Submission Framework (ESF) are currently not replicating properly to the GeoBC Geographic Warehouse (LRDW). As a result the WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW layer is not up to date.

A fix is currently being implemented and the situation is anticipated to be rectified by November 4th. Further communication will be issued when the replication functionality for the Reserves layer is fully restored.

Openings, reserves, silviculture activities, standards units, planting, and forest cover information is failing to replicate to the LRDW – October 3, 2011

Please be advised that new openings, silviculture activities, standards units, planting, and forest cover information uploaded to RESULTS via the Electronic Submission Framework (ESF) are currently not replicating properly to the LRDW (GeoBC Geographic Warehouse).  This affects the following RESULTS opening layers in the LRDW:

1. WHSE_FOREST_VEGETATION.RSLT_OPENING_POLY
2. WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW
3. WHSE_FOREST_VEGETATION.RSLT_OPENING_VW
4. WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW
5. WHSE_FOREST_VEGETATION.RSLT_STANDARD_UNIT_SVW
6. WHSE_FOREST_VEGETATION.RSLT_ACTIVITY_TREATMENT_SVW
7. WHSE_FOREST_VEGETATION.RSLT_PLANTING_SVW
8. WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_INV_SVW
9. WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_SILV_SVW

As a result, these layer are not up to date.  Openings, silviculture activities, standards units, planting, and forest cover information uploaded to RESULTS via ESF to RESULTS will not appear in the LRDW until this issue is fixed.

It is important to note that all spatial and tabular data within the RESULTS database is up to date and the tabular data in the RESULTS LRDW tables are also up-to-date.

These issues have been flagged as a priority and further communication will be issued when the replication functionality is fully restored.  A fix is currently being implemented and the situation is anticipated to be rectified by October 15th.

Please do not attempt to re-submit openings, silviculture activities, standards units, planting, and forest cover information uploaded to RESULTS via ESFor reserves that have not replicated as they are queued for processing.

Recording is available Interim Measure for Identifying Reserves in the Forest Clearance Process held on September 20, 2011.

This session will provide an overview of the interim strategies and procedures for checking treed reserve encumbrances, that reflect the current RESULTS forest cover submission using the July 2009 procedures and previously submitted reserves, during the forest clearance process.

• https://www106.livemeeting.com/lrs/8002144422/Registration.aspx?pageName=g8vt0bfjspkhlm5xicUrl=1

Openings and Reserves failing to replicate to the LRDW

Please be advised that new openings uploaded to RESULTS via the Electronic Submission Framework (ESF) are currently not replicating properly.  This affects the following RESULTS opening layers in the GeoBC Geographic Warehouse (LRDW): WHSE_FOREST_VEGETATION.RSLT_OPENING_POLY and WHSE_FOREST_VEGETATION.RSLT_OPENING_SVW and WHSE_FOREST_VEGETATION.RSLT_OPENING_VW.  As a result, this layer is not up to date, openings uploaded via ESF to RESULTS since the end of May will not appear in the LRDW until this issue is fixed.

In addition, new forest reserves uploaded to RESULTS via the Electronic Submission Framework (ESF) are currently not replicating properly to the GeoBC Geographic Warehouse (LRDW), specifically the WHSE_FOREST_VEGETATION.RSLT_FOREST_COVER_RESERVE_SVW layer.  As a result, this layer is not up to date.

These issues have been flagged as a priority and further communication will be issued when the replication functionality is fully restored.  Please do not attempt to re-submit openings or reserves that have not replicated as they are queued for processing.

RESULTS FFT 2011/2012 Training - New Recording, Training Slides and Sept 15 Session

Please be advised that FFT RESULTS Training Live Meeting Recording and training slides are now available on the RESULTS Training website: https://www.for.gov.bc.ca/his/results/training/FFT.htm.  The training covers topics related to FFT Reporting into RESULTS.

Another Live Meeting session will be held on September 15, 2011 10:30 to 12:00.  If you are interested in attending the session, please register at: https://www106.livemeeting.com/lrs/8002144422/Registration.aspx?pageName=487rrsdj3gdnnct3=1.

RESULTS – Obligation Reporting Training – May 2011

There will be two Live Meeting sessions for RESULTS Obligation Reporting in May 2011.  Dates and times are:

• May 17 (Tuesday) 10:30–12:00
• May 24 (Tuesday) 10:30–12:00

Please go to the following link to register for the these sessions:
https://www106.livemeeting.com/lrs/8002144422/Registration.aspx?pageName=bbz5z26f221n6v99icUrl=1

RESULTS Layers Now Available in Data Distribution Service – January 18, 2011

Please be advised that the following RESULTS Layers are now available in the Data Distribution Service: https://apps.gov.bc.ca/pub/dwds/

• RESULTS – Activity Treatment Units
• RESULTS – Forest Cover Inventory
• RESULTS – Forest Cover Silviculture

RESULTS Training Offerings for Fall 2010

Fall RESULTS Training sessions have been delivered for the following themes:

• Forest For Tomorrow – Reporting into RESULTS High Level Overview and Data Issues
• FRPA s.108 – Using RESULTS to complete s.108 Application
• Obligation Reporting

Powerpoint presentations and recordings may be accessed through RESULTS training website by Theme at the following address:
https://www.for.gov.bc.ca/his/results/training/index.htm

Live Meeting recordings are listed and available through the following address:
https://www.for.gov.bc.ca/his/results/training/live-meeting.htm

Presentations

• RESULTS – a key business tool for integrated MFR and licensee operations

Communiqués

The following documents provide information about RESULTS, e.g. release notes, upcoming release and training schedules, changes to policies and procedures and data cleanup strategies.

• Release 4.8 August 2012 MCT
• New Modifications to Standards Units Detailed Report & Data Download Reports – November 2010
• Process for Addressing Outstanding Data Integrity Issues in FLNRO Corporate Database – March 2010
• RESULTS Operational Issue Forum QA Training Communication Session 2 – March 4-10 Session
• RESULTS Operational Issue Forum QA Training Communication Session 1 – February 18-23 Session
• Submitting Forest Cover to RESULTS for Openings with Treed Retention – Interim Procedures Training Feb 2010 — Responses to Questions from the Live Meeting Sessions
• Submitting Forest Cover to RESULTS for Openings with Treed Retention – Interim Procedures Training Feb 2010
• FRPA Administrative Bulletin (Number 13)
• RESULTS Release 4.1 - Detailed User Summary
• RESULTS Training – Live Meeting Recordings Available – November 2009
• RESULTS Species Monitoring Report Training Fall/Winter 2009
• Submitting Forest Cover to RESULTS for OPENINGS with TREED Retention
• Summer 2008
• Status Report - Strategic Cleanup of Key Corporate Information in RESULTS
• Chief foresters woodlot e-business update
• Release 3.1 March 2008
• Summer 2007
• Release 3.00.12 - May 2007
• Release 3.0 Spatial Tolerances - April 2007
• Release 3.0 fixes - April 2007
• Emergency Release - January 2007
• January 2007
• April 2006
• November 2005
• Release 2.1 - October 2005
• September 2005
• June 2005
• April 2005
• January 2005
• November 2004
• July 2004
• Release 1.3 - July 2004
• Release 1.2 - April 2004
• March 2004