Plantation Manager

PM 6.0.12 [18-Feb-2022]

• Maintenance Release.

EDI 3.1.2 [27-Jan-2022]

• [Enhancement] Handle any additional tree attributes (e.g. TreeType)

PM 6.0.11 [27-Jan-2022]

• [Enhancement] Compartments - Fell Status

  Added (O)wn or (C)ontractor indicator in Compt Fell Status Grid and Edit Dialog.

PM 6.0.10 [26-Nov-2021]

• [Enhancement] Enumeration - Tree Type Alternative Buckspec

  A new 'Tree Type' tree attribute has been introduced with a pre-defined list of user-selectable values (may be modified on request). This attribute may be added to certain enumeration types on request. Additionally and optionally an alternative bucking specification per tree type may be specified by the user. Every tree classified as a specific tree type with an alternative buckspec will be bucked accordingly.

  A new 'Alt Buckspec' tab on the Enumeration window allows the user to specify alternative buckspecs for selected tree types. By default the compartment buckspec will be used if no alternative is specified or no tree type is assigned to a tree.

  The default bucking wil still be used for the normal enumeration statistics, but the volumes produced by the alternative bucking may be viewed using applicable report(s).

PM 6.0.9 [15-Nov-2021]

• [Enhancement] SI Matrix

  The SI Matrix enhancement enables you to have a pre-defined setup for SI values that is dependent on the management unit, species, and 'Site Quality' and 'Mean Altitude' compartment general attributes.

  • New System Table added for 'SI Matrix' setup
    • Select any level of Munit, the lower level will override the higher level.
    • Min and Max altitude are optional.
    • SI SQ1-5 is the value that will be used depending on the selected 'Site Quality' class on each compartment general attribute.

  • Advanced Procedure 'SI - Update from SI Matrix'.

    This procedure will update all compartments matching the selected munits, working circles, species (optional) and SI Sources with the following options:

    • Where the compartment is planted, with an optional age range
    • Where the compartment is TUP
    • The next rotation SI, optionally only if the species are different.

  • Option added to update SI when compartment species changes.

    If enabled and a matching SI Matrix setup is found, a confirmation message will be presented to use or ignore the SI lookup value.

    Enabled/disabled upon request

  • Option added to update SI for next rotation when species changes.

    This works similar to the compartment species update above, just for the next rotation. There will also be a confirmation message with the options yes, no and cancel.

    Enabled/disabled upon request

  • Option added to update SI when the compartment is planted.

    Update compartment SI if current species and new species are different and if SI Matrix setup value found.

    Enabled/disabled upon request

  The following application logic applies:

  • Search the SI Matrix table on the lowest Munit level for the compartment.
  • Use the compartment species and if not found, the species' model species.
  • If available and in SI Matrix setup, get the 'Mean Altitude' general attribute value and check if it is in the min and max altitude specified in the SI Matrix setup.
  • If a match for this compartment is found in the SI Matrix setup, get the 'Site Quality' general attribute and use the attribute class to determine which 'SI SQn' value to use.

  Batch processing

  Any current or future batch species update process will not trigger an SI update from the SI Matrix table.

PM 6.0.8 [10-Aug-2021]

• [Enhancement] Compartment Filter – Enumerations
  • Change existing 'Enum Status' filter from 'Processed, not authorised yet' to 'Processed, not authorised or declined yet'.
  • Apply all enumeration filters as ‘and’ instead of ‘or’ conditions.

PM 6.0.7 [12-Jul-2021]

• [Enhancement] Software update notification - the system will now show you a notification after login if you had a system upgrade.

EDI 3.1.1 [12-Jul-2021]

• [Enhancement] Software update notification - the system will now show you a notification after login if you had a system upgrade.

PM 6.0.6 [28-Jun-2021]

• [Enhancement] Compartment View - Activities tab: Store ‘Show activity level column’ default value.
• [Bug Fix] Fixed bug on tree view where selection was lost on tab change.
• [Bug Fix] System Tables – Regime Link: Fix bug that did not show correct ‘Coppice Regime’, was always 0.

PM 6.0.5 [31-May-2021]

• [Enhancement] Added grid search to new reporting tool selection grid and fixed some minor display bugs, including cases where the tree view selection indicator not always selected all children when their parent has been selected.

PM 6.0.4 [07-Apr-2021]

• [Enhancement] Activity system tables: The functionality of the existing valuation module has been enhanced to allow a user with valuation user rights to flag specific activities as valuation-only activities. These activities may only be used in valuation features (e.g. valuation prescriptions), and are not available for general use purposes, e.g. APO.

PM 6.0.3 [11-Mar-2021]

• [Enhancement] Grid search – a filter button has been added to some identified grids. This will filter the grid on any cell matching the filter text. Min of 3 characters is required.
• [Enhancement] Pinnable Tabs – Remember the last pinned state of the notes tab.

PM 6.0.2 [15-Feb-2021]

• [Enhancement] Session handling

  We have changed the way that sessions are handled, especially when it has expired (timed out) or gets interrupted in any way. In the past, you were presented with an error message and were forced to logout, losing your current progress.

  With this change, the application will be locked, and when you login with the same username and password, the current state/opened windows will be restored, allowing you to continue where you left off. If a different user logs in, all windows will be closed, and the previous state will be discarded.

  The following application logic applies:

  • The PM application is launched and the user logs in as usual. The session is started as usual.
  • Any interaction with the application will reset the session timeout, as usual. Inactivity will cause the session to expire as usual.
  • If the session expires, the system will, without warning, 'lock' the system and open the normal Login window. The title will indicate that the session expired.
  • The Login window will be populated with the user's username and the keyboard focus will be set to the empty password text box.
  • To unlock the system, the user must type in his/her password and press <Enter> or click OK. If the password validates successfully, the system will continue in the state it was before the lockout/session expiry.
  • If a different user wishes to login, the new user's username and password may be specified. In this case, the previous user will be logged out and the new user logged in. The state prior to the lockout will be lost, i.e. open windows will be closed, etc.

  There is also a new menu item to "lock" the system, this will save the state and allow it to be restored after logon. So, if you leave your desk, it is now possible to lock the application without losing the state.

PM 6.0.1 [20-Jan-2021]

• [Enhancement] Pinnable Tabs.

  We have changed the behavior of the additional information tabs (e.g. Notes, Regime, Volumes) on windows like the Compartment View. Tabs are no longer 'pinned' by default when opened. When opening another tab, only pinned tabs will remain open and unpinned tab(s) will be replaced by the new tab.

  A tab is pinned by double-clicking on its button, or single click on the pin icon in the top right corner of the tab.

  Additionally, the Notes tab will open automatically in a pinned state when an item is viewed.

PM 6.0.0 [11-Jan-2021]

• Maintenance Release.

PM 5.7.3 [25-Nov-2020]

• [Enhancement] Damages – Allow damage modifications on archive compartments.
• [Enhancement] Enumerations
  • Allow enumerations on archive compartments.
  • Decline enumeration functionality.
• [Enhancement] TPS – Split TPS Supply layer into TPS Supply (Fell) and TPS Supply (Thin).

PM 5.7.2 [12-Nov-2020]

• Maintenance Release.

PM 5.7.1 [15-Oct-2020]

• [Enhancement] Damages – Add new 'Verification Status' attribute.

PM 5.7.0 [09-Sep-2020]

• [Enhancement] Operations – Allow Archive Compartments on any Activity

  Previously archive compartments could only be added to harvesting activities for the purposes of volume capturing - only BP and AP quantities were editable.

  Now archive compartments may also be added to activities in the 'Maintenance' and 'Other' groups, but BW and AW are still only editable on non-harvesting type activities.

PM 5.6.21 [05-Sep-2020]

• [Enhancement] Damage Assessment

  The damage assessment for open areas will now work the same as for compartments. Incidents are now sharable between compartments and open areas.

PM 5.6.20 [02-Sep-2020]

• [Enhancement] Fire Risk Rating

  When updating the'fire risk rating' for compartments and open areas, a reason for the change is now forced. This will change the status from "Loaded" to "Manual". When importing, the status will change back to "Manual".

PM 5.6.19 [05-Aug-2020]

• [Enhancement] Open Area Primary and Secondary Types

  Previously Primary and Secondary Types used the same lookup values with no interdependency. This has been changed to use separate lists with an optional parent-child relationship between the primary and secondary types, i.e. a primary type (parent) may be defined with a list of secondary types (children) belonging to it, similar to the vegetation class and type mechanism. If a secondary type has no defined parent then it is available for selection irrespective of the selected primary type. These types can now also be defined on the "System Tables" window.

• [Enhancement] Compartment Damage

  • Assessments are now using effective area and not the area.
  • Planted TPH will be used instead of current/survival TPH when the damage is recorded before the survival age has been reached.

PM 5.6.18 [01-Jun-2020]

• [Enhancement] Document Management

  The Microforest Mobile Application introduced recently provides the ability to add documents and images to various entities, e.g. compartments, damages, business suite tickets, etc.

  This enhancement allows users to manage documents (view, add, edit, delete), including those added by the mobile application. Available on request.

  The following functionality is currently available in Plantation Manager:

  • Documents user rights.
  • New 'Documents' main toolbar button.
  • New 'Documents' tab in Compartment View
  • New 'Documents' button on compartment Damages tab and Damage view/edit window.
  • New 'Documents' button on Assessments tab in Roads View.

PM 5.6.17 [20-May-2020]

• [Enhancement] Advanced Processing - New 'Import (update) open area attributes' option
• [Enhancement] Open Area Filter – Added 'Secondary Type' filter option

PM 5.6.16 [09-Apr-2020]

• [Enhancement] Advanced Processing - New 'Import Survival Assessment' option.

PM 5.6.15 [27-Mar-2020]

• [Enhancement] Advanced Processing – MAI Calculation
  • Combined two MAI calculation menu options into one with separate 'All' or 'Only where zero' selection.
  • Option to use or ignore volume loss during calculation.

PM 5.6.14 [13-Feb-2020]

• [Enhancement] Weed Assessment Date and Time
  • In addition to the assessment date, the time of day can now be specified. This is only necessary if more than one weed assessment is captured on the same day for a specific compartment or open area.

PM 5.6.13 [23-Jan-2020]

• [Enhancement] Changing Enumeration Type
  • Before this update, all existing measurements were removed then the enumeration type was changed. With this update, the 'common' measurements are kept.
    • You will be prompted with a message indicating which measurement columns will be removed. If you agree to proceed, the captured data in those columns will be deleted, but the remaining columns' existing data will be retained.

PM 5.6.12 [12-Dec-2019]

• [Enhancement] User Access Templates
  • All user access templates now behave the same as the 'Application Permission' templates. The template is now associated with the user when applied. When the template changes, so will the access rights of users associated with the template.

PM 5.6.11 [26-Nov-2019]

• [Enhancement] Spatial Synchronisation – External Open Area
  • Provision for flag on spatial layer that indicates an open area as external. Business logic is client specific.

PM 5.6.10 [10-Nov-2019]

• [Enhancement] Advanced Processing
  • Calculate Actual vs. Planned Volumes: Instead of recalculating all archive volumes each time, calculate only additional volumes of compartment archived since last run. Instead of using age at start of fell interval, use the weighted age of all fell periods.

PM 5.6.9 [18-Oct-2019]

• [Enhancement] Prescriptions

  Info

  Prescription related functionality only impacts on clients with a Weed Prescriptions license.

  • Prescriptions and Prescription Links setup windows have been moved from the Administration - System Tables window to a new File - Prescription Tools menu.
  • New application rights have been created to manage view and edit Prescriptions and Prescriptions link items.
  • New settings added to prescriptions:
    • New triggers
    • Min and Max Quantity to activities

• [Enhancement] Operation View

  • Detail Activities: 'Effa' column renamed to 'Size' to cater for other landuse type sizes (road lengths, etc).

• General maintenance and bug fixes.

PM 5.6.8 [26-Sep-2019]

• [Enhancement] Attribute Change Log (Regime Option)

  The intention of this enhancement is to provide generic future functionality to capture change notes when specified attributes' values change. Currently it will prompt for a note/comment only when a user changes a compartment's regime option. A new read-only 'Attribute Change Log' tab is available on the Compartment View.

  This option is switched off by default and can be activated on request, but currently only for compartment regime option as mentioned.

PM 5.6.7 [12-Sep-2019]

• Maintenance Release.

PM 5.6.6 [31-Jul-2019]

• [Enhancement] Survival Assessment

  In addition to the standard summary Survival Assessment enumeration type, make provision for detail Survival Assessments:

  • Block separate dbh/height pairs specification.
  • Update survival age and tph during authorization.
  • Calculate standard arithmetic mean height if tree heights are available, but no dbh/height pairs are available for height regression.

PM 5.6.5 [25-Jun-2019]

• [Bugfix] Yield Table Generator Output Files.

  Fix a bug that, in certain circumstances, could allocate incorrect volumes to some products in the yield table output files. Totals were always correct.

PM 5.6.4 [20-May-2019]

• [Enhancement] Enumeration 'Irregular Rectangle' Plot Type
  • This new plot type allows a user to specify four side lengths, their slopes and two diagonals of an 'irregular rectangle' (general quadrilateral) plot shape. The area calculation uses these values to calculate the area. Certain assumptions have been made in this area calculation, thus it is important to confirm with Microforest before this is used.
  • The enhanced area input controls (for the additional dimensions) are only displayed when a 'remeasure/successive' type enumeration (e.g. PSP) or 'Irregular Rectangle' plot type is specified.

PM 5.6.3 [12-Apr-2019]

• [Enhancement] Delineation

  • You can now override the status of a compartment's delineation with two new states.

    • Completed - Partially Implemented Infield
    • Completed - Management Override

    As it is now, if you start capturing data (per section), then you must complete that section. When overriding the status to complete, you should always specify a "reason" from above if the status is not originally one of the existing complete statuses, but you can always change from a complete status to any of the above-mentioned new states.

  • A new process under Advanced Processing has been added, that allows you to import compartment delineation information using a ".csv" file. The same business rules will be applied as when capturing within "Plantation Manager". You can then update/replace delineation data at any time. An Excel template is available on request.

PM 5.6.2 [01-Apr-2019]

• [Enhancement] PV50 Uniformity Index was added for Enumeration - Summary Report and Enumeration - DBH Analysis.
  • This is a stand uniformity index, defined in Hakamada et al. (2015). It's the accumulated total stand volume for the bottom 50% of the stand table, expressed as a percentage of the accumulated total stand volume.

EDI 3.1.0 [03-Apr-2019]

• [Enhancement] EDI-1 (Haglof) Format: Previously all DBHHGT pairs were assigned to the first plot. This enhancement makes provision for the change Haglof made to allocate DBHHGT pairs to specific plots.

PM 5.6.1 [07-Mar-2019]

• [Enhancement] Open Areas and Compartments - Ownership and Owner
  • Open Area's 'Owner' attribute is now available and editable (similar to compartments).
  • Both compartment and open area can now be filtered on ownership and owner.
  • Both compartment and open area result lists include the ownership and owner columns.

PM 5.6.0 [01-Feb-2019]

• [Enhancement] ALS 'HD Only' Enumeration Processing
  • Previously the ALS 'HD Only' enumeration processing used the site index calibration model to predict basal area. Processing enhanced to project the basal area from a previously approved enumeration, if available.

PM 5.5.10 [06-Dec-2018]

• [Enhancement] Advanced Processing
  • When running the "Generate compartment yield tables" process, you can now specify an output directory where the files will be stored on your local system.

EDI 3.0.6 [06-Dec-2018]

• [Enhancement] Support for custom defined enumerations using configuration file

PM 5.5.9 [09-Nov-2018]

• [Bug fix] Fix bug that caused the Volume Loss on a damage incident to be reset to zero on edit.
• [Change] When calculating damage Volume Loss, do not take compartment volume loss percentage into consideration.

PM 5.5.8 [01-Nov-2018]

• [Enhancement] Seedstock

  • A compartment can now have multiple seedstock numbers defined, optionally with the number of seedlings per seedstock. An additional compartment tab has been added for this purpose.
  • When there is more than one seedstock on a compartment, the dominant seedstock must be selected.
    • The seedstock with the highest number of seedlings, will be automatically selected as the dominant seedstock. User will not be able to change this.
    • When no obvious dominant seedstock can be determined, thus if all seedstock seedlings are the same or none is specified, then the dominant seedstock must be selected. The dominant seedstock can be selected either by using the checkboxes in the seedstock control or selecting on the compartment info window as before.
    • If there is more than one seedstock defined, then the seedstock drop down on the compartment info window will only contain the seedstock numbers defined in the seedstock tab. If none or only one is specified, then it will work as it did before, containing all the active seedstock numbers.
    • The seedstock drop down on the compartment window will only be enabled if the seedstock control is not in edit mode.
  • The same rights and rules as before are also enforced on the new seedstock control.

• [Enhancement] APO Budget Product (BP) Editable and APO Import

  • BP values in APO periods are now editable, enabling the ability to override the default BW-based proportional phasing.
  • New comma separated values 'Import APO' advanced processing option. Please read notes in the template file 'APO Import.xlsx' which is available on request.

PM 5.5.7 [19-Oct-2018]

• [Enhancement] General Attributes
  • Previously all available attributes were displayed in the general attribute tab's grid, whether their values were assigned or not. This was changed to allow a user to select applicable attributes and supply their values.
  • An attribute 'Class' classification field can be pre-configured on specific attributes, which allows different classes to be assigned to an attribute, each with their own values.

PM 5.5.6 [26-Sep-2018]

• Maintenance Release - Various small bugfixes

PM 5.5.5 [19-Sep-2018]

• [Enhancement] Compartment Volume Loss Percentage (%V)

  • The compartment %V functionality has been enhanced to use damage volume loss if enabled. Damage volume loss is disabled by default (always 0), but can be enabled on request.
  • If enabled, the damage volume loss is automatically calculated when damages are added, updated or deleted on a compartment. Effective %V will then default to this value, but it can still be overridden by the user.
  • The damage volume loss is displayed in a read-only text box followed by a 'D' indicator, while the %V override text box functions as always.

PM 5.5.4 [08-Aug-2018]

• [Enhancement] Compartment Contact

  • New feature added to link contacts to a compartment with the primary contact marked.
  • New Contact Manager accessible from the View – Contacts menu.

• [Enhancement] Compartment Owner

  • New field added to compartment to specify the owner (similar editing logic as seed stock).

PM 5.5.3 [17-Aug-2018]

• Maintenance Release

PM 5.5.2 [29-Jun-2018]

• [Enhancement] Brashing and Coppice Reduction Regime Operations

  • New Brashing regime operation. Brashing is considered to be a type of pruning. Brashing height must be specified and all brashing and/or pruning operations in a regime must increase with age.

    The earliest pending brashing regime operation will be set to completed when an APO activity of class 'Brashing' is completed.

  • New Coppice Reduction regime operation. The quantity indicates the target stems/tree. It has no influence on the TPH of the compartment.

    The earliest pending coppice reduction regime operation will be set to completed when an APO activity of class 'Coppice Reduction is completed.

• [Enhancement] Brashing and Coppice Reduction Activities

  Brashing and Coppice Reduction activities may be defined as follows:

  • Brashing: Sub Class: Compartment, Activity Class: 'Brashing', Activity Group: 'Pruning'
  • Coppice Reduction: Sub Class: Compartment, Activity Class: 'Coppice Reduction, Activity Group: 'Other'

PM 5.5.1 [17-May-2018]

• [Enhancement] Fell Status – Add 'Opened On' and 'Closed On' dates.

  These additional fields save the system date when a compartment is opened or closed.

• [Enhancement] Fire Risk Rating – Add fire risk rating update date.

  This additional field saves the system date when the fire risk rating of a compartment or open area is updated.

• [Enhancement] Plantation Selection – Replace list view row selection with new check box selection column and add right-click popup context menu to select/unselect all or selected rows.

PM 5.5.0 [23-Mar-2018]

• [Enhancement] ALS Inventory Enhancements (also refer to PM 5.3.7 - 'ALS Inventory')

  • A new 'ALS HD Inventory' summary enumeration type that only requires compartment id, date and dominant height (HD) for SI calculation, is now available.
  • The 'ALS HD Inventory' may also be imported - similar to the 'ALS Inventory' import.
  • Both enumeration types are now automatically processed when imported or manually created.
  • In addition to the SI, the UMAI, Dbh and UVolume are now also calculated:
    • These additional results are shown in the enumeration tab on the compartment view.
    • 'ALS Inventory': The input data of the inventory is used to calculate these values.
    • 'ALS HD Inventory': The calculated SI (from HD) and current compartment values are used in the calculation.

• [Enhancement] Various enumeration enhancements:

  • Previously the detail and summary enumeration windows listed all the enumeration types, some of which were not always applicable. Enumeration types are now classified as detail, summary or both.
  • Previously only one set of reports applied to all enumeration types. This has been changed so that an appropriate report set can be applied to individual types and summary/detail level enumerations (e.g. summary level reports for summary enumerations).

PM 5.4.15 [23-Feb-2018]

• [Enhancement] Spatial Processing, Synchronise spatial changes – List APO Impact.

  The Spatial Processing – Synchronise spatial changes functionality has been enhanced to indicate possible APO impact of the spatially modified features (compartments, open areas and roads):

  • An additional 'On APO/Budget' check box column indicates whether the changed feature appears in any APO, Works Order and/or Works Order ticket. The current operational plan and all budget plans that have start dates from the start of current plan start date until six months after the current plan ends, are searched.

  • Only modified features are checked, i.e. an unchecked 'On APO/Budget' check box on a feature with a blank 'Change' column value, does not necessarily mean that is not on the mentioned APOs for some activity.

  • A new grid below the features grid displays the selected feature's impact information, if any. It is left to the user to investigate whether the spatial change and required synchronise action would have any impact on the listed items. If so, these must be manually handled.

  • The 'Quantity' column is normally empty for silviculture work, but will indicate the production quantity (e.g. m3) for a production activity (e.g. felling), or alternatively the resource quantity (e.g. liter) on a Works Order resource ticket.

• [Bugfix] Weeds – Fix weed edit bug introduced during Damage Incident finalisation in PM 5.4.14.

PM 5.4.14 [24-Jan-2018]

• [Enhancement] Damage Incident – Finalisation of features implemented in PM 5.4.12. Please see PM 5.4.12 for a full description of the new damage incident functionality, specifically taking notice of the following:

  Previously 100% area and 100% intensity had to be specified for specific damage class(es)/type(s) (e.g. fire) to indicate stop growth conditions, … now 100% effective area loss for the same damage class(es)/type(s) is sufficient.

• [Bug Fix] Spatial Processing: Area reconciliation reason required for split but cannot be specified.

  Under certain circumstances, due to rounding issues, the PM 'Split Information' user interface would not allow an area reconciliation reason to be specified when it was required, resulting in an error when the split was attempted.

PM 5.4.13 [23-Jan-2018]

• [Enhancement] Enumeration: A tree which is specified as completely dead by choosing the 'Dead-A' option of the tree condition (stem type) attribute may be configured to influence volume, TPH, etc. in a predetermined way. The default is that it has no influence (as if it is not present).

EDI 3.0.3 [17-Jan-2018]

• [Enhancement] Masser Excaliper import format: Option to add tree measurements where heights are measured as normal trees that are counted as part of the plot (influencing TPH, etc.), or as separate dbh/height pairs (influencing only height regression).

  All the original enumeration types (Working Plan, Thinning Control, etc.) defaults to the option where separate dbh/height pairs are added.

  All the 'new' enumeration types, if applicable ('PSP', 'Trial', etc.) defaults to the option where normal trees are added, not dbh/height pairs.

  This option was added to make provision for the following two scenarios:

  1. Trees' dbhs and other attributes, including some or all heights, are measured once.
  2. Trees' dbhs and other attributes are measured without heights, and then some of the same trees are chosen and their dbhs and heights are measured.

  In case 1, all trees, those with and without heights should be added as normal trees that is part of the plot, none as separate dbh/height pairs.

  In case 2, all trees with height measurements should be added only as dbh/height pairs, not as normal trees also (otherwise duplication).

  • As always, trees with heights and separate dbh/height pairs are combined for height regression.
  • This option may be specified on an enumeration type basis.
  • This is only applicable to the 'new' enumeration definition types (new user interface with flexible attribute definitions). Legacy enumeration types always add height measurements only as dbh/height pairs.

PM 5.4.12 [22-Nov-2017]

• [Enhancement] Damage Incident

  The concept of a compartment damage incident has been introduced. A damage incident may affect multiple compartments and has the following common attributes, which must be the same on all its damages:

  • Incident code
  • Incident boundary (where damage originated and ended)
  • Damage date
  • Damage class and type

  If any one of the above is changed on one compartment damage, then all the other damages of the incident will be updated with the new values.

  Rehabilitation actions may be performed on an incident. An action may be performed on just the current damage or on all the damages of the incident. The last action performed on a damage becomes its status. If the special action 'Closed' is specified, then the damage is closed and the closed date recorded. If the 'Closed' action is applicable to all damages, the entire incident is closed. Closed incidents will not appear in the incident lookup list (see below).

  Rehabilitation actions may be added/edited/deleted/made obsolete at File - Administration – System Tables - Other - Damage Rehabilitation Actions. This is user access controlled.

  The Damage edit window presents a dropdown of open (not closed yet) incident codes.

  • The user may select an existing incident which will populate the incident attributes mentioned above.
  • A selected incident may be renamed by typing a new name in the supplied text edit and pressing the 'Rename' button.
  • A new incident may be created by typing in a new unique incident code and pressing the <Enter> key or the 'New' button. If a closed incident with the specified code already exists, it will be loaded, added to the dropdown list and selected.

  If all damages of an incident are deleted or unlinked from the incident, then the incident will be deleted.

  If no incident code is specified, then the damage is not part of an incident and the following attributes are not available/applicable anymore:

  • Incident Code
  • Incident boundary
  • Volume Loss
  • Status
  • Close Date
  • Incident Rehabilitation Log

  The following additional damage attributes have been added, irrespective of whether it is part of an incident or not:

  • Damage originated here. Flag to indicate if damage originated in this compartment or not.
  • Damage Certainty (mandatory). Existing data defaults to 'Definite'
  • Damage UoM (mandatory). Existing data defaults to 'Percentage'
  • Affected Area (mandatory). In selected UoM. Existing data defaults to % Area Loss
  • Lost Area (mandatory, zero accepted). In selected UoM (100% intensity)
  • Partially Lost Area (read only). Calculated from Affected and Lost Area
  • Effective Area Loss %. Calculated as indicated below. Replaces original 'Area %'
  • Volume Loss (read only). See above
  • Capture By/Date (read-only). Automatically set to last user who updated the damage
  • Comment

  If an incident is recorded, the volume loss will also be automatically calculated when the damage is added/updated:

  Volume Loss = % Effective Area Loss * Standing (CUR) volume as on damage date.

  The original compartment damage module had simplistic Area % and Intensity % attributes, i.e. a percentage of the area was damaged at a certain intensity. This enhancement allows for the specification of an affected area consisting of a lost portion (fully damaged at 100% intensity) and a remaining partially lost portion (affected area – lost area) with a specific user-specified intensity less than 100%.

  Effective Area Loss %, which is a combination of the two damaged portions, replaces the original simplistic 'Area %' value:

  Effective Area Loss % = Lost Area % + Partially Lost % * Intensity %

  For example, if Compartment Area= 10ha, Standing Volume = 1500m3, Affected Area = 7ha, Lost Area = 5ha and intensity of partially lost area = 50%, then:

  Partially Affected = Affected Area - Lost Area
                     = 7ha – 5h
                     = 2ha
  
  Effective Area Loss = Lost Area + Partially Lost Area \* Intensity %
                      = 5ha + 2ha \* 50%
                      = 6ha
  
  Effective Area Loss % = 100 \* 6ha/10ha = 60%
  
  Volume Loss = Effective Area Loss % \* standing/CUR volume
              = 60% \* 1500 m3
              = 900 m3
  

  The original Area % values are migrated as follows during this upgrade:

  If intensity = 100% then

  • Affected Area % = Area%, Lost Area % = Area%, Partially Lost Area % = 0
  • Effective Area % = Area% (unchanged)

  Note

  Intensity stays 100%, no influence because partially lost = 0. It could have been set to 0, but left as is.

  If intensity < 100% then

  • Affected Area % = Area%, Lost Area % = 0, Partially Lost Area % = Area%
  • Effective Area % = Intensity% * Area% / 100 (intensity incorporated)

  IMPORTANT

  Previously 100% area and 100% intensity had to be specified for specific damage class(es)/type(s) (e.g. fire) to indicate stop growth conditions, from the above it follows that now 100% effective area loss for the same damage class(es)/type(s) is sufficient.

EDI 3.0.2 [27-Oct-2017]

• [Enhancement] The Masser Excaliper format now has the ability to create any specified enumeration type during import, not just the standard Stocktake (Working Plan) or Thinning Control types.
• [Enhancement] Handle Excaliper file with new StemType, Height1 and Height2 tree condition related QA properties.

PM 5.4.11 [27-Oct-2017]

• [Enhancement] Advance Process: Calculate Simulation Criteria (optimal MAI and DBH ages)

  HSS 3 has two new sorting algorithms in addition to the default 'oldest first' sort: Optimum MAI age and DBH target age.

  This process calculates the values used in HSS for these sorting algorithms:

  • Age where the optimal MAI is found.
  • Age where a specified target DBH is found.

  The target DBH may be specified by management unit and WC. The default is 20 for all management units and WCs. These can be modified on request.

  The calculated values are initially stored in a 'New' set. Current values, if any, are only overwritten when the 'Apply Changes' button is used. This allows the user to verify newly calculated values before they are applied and used in HSS. The current values become the previous values when replaced by the new values, and new values are cleared to indicate that the new values have been applied.

  These values may be viewed in a new 'Rotation Simulation Criteria' tab on the Compartments View.

• [Enhancement] Advance Process: Calculate Annual Production Potential

  Previously the Annual Production Potential (APP) had to be calculated by configuring and executing three very specific HSS jobs. This process now automates this calculation. A new APP job name may be specified for every run, or the default job which defaults to the current year (e.g. 2017) may be repeatedly overwritten.

  NVol volumes use WC's 'Min Regime Age'. If a compartment is older than WC's Max Regime Age, then 'Max Regime Age' is used, not the compartment's age.

  Dedicated APP reports will be made available soon.

PM 5.4.10 [18-Aug-2017]

• [Enhancement] Modeling: Tree quality/grade bucking enhancements. Switched off by default; still in testing/evaluation phase.

EDI 3.0.1 [23-Aug-2017]

• [Bug Fix] Recordings for compartments with identical names but from different management units were all incorrectly assigned to the first compartment encountered.

PM 5.4.9 [21-Jul-2017]

• [Enhancement] Report Viewer now has two buttons to generate Excel and PDF reports.

PM 5.4.8 [23-Jun-2017]

• [Bug Fix] Fixed a bug on the compartment volume tab that incorrectly flagged the total utilisable volume column (Util) as having an error (displayed in red) when bark is one of the products (bark is not included in total utilisable volume).

PM 5.4.7 [14-Feb-2017]

• [Enhancement] Automatic Weed Assessment on Activity Completion [Weed Module Only]

  PM 5.4.5 introduced automatic weed assessment creation at the start of a fell or thin operation. Similarly, this enhancement enables the user to specify the weed assessment that should be created on completion of any chosen activity.

  • Two new columns are now available in System Tables Administration – Activity: 'Weed Phase' and 'Next Weed Phase'. The latter is specified if completion of an activity should result in the creation of a new weed assessment for the compartment, effectively moving the compartment into the specified weed phase. An assessment will always be created, even if the compartment is already in the specified 'Next Weed Phase'. The 'Weed Phase' value is required only if this action should happen if the compartment is currently in the specified phase; normally left blank.
  • The newly created assessment's Recorded By is set to 'Plan:<Plan Name>', and the Document Reference is set to 'Act:<Activity Code'.

PM 5.4.6 [16-Jan-2017]

• [Bug Fix] Fixed unhandled exception when editing activity summary totals in Operations View while Harvesting APO editing is disabled for the current user.

PM 5.4.5 [11-Nov-2016]

• [Enhancement] Weeds

  Some of the following enhancements are only applicable if the new Weed Management Module is enabled – also refer to PM 5.4.3 below.

  Weed Assessment

  • The 'Phase' selection is disabled as it is automatically selected based on the selected 'Density'.
  • [Weed Module Only] If 'Prescription' is not specified by the user, the system automatically calculates it immediately. Thus, the 'Assign weed prescriptions' advanced process only has to be executed initially (or again after weeds were imported), thereafter the compartments' or open areas' effective weed phases and associated prescriptions are maintained automatically.

  [Weed Module Only] Automatic Weed Assessment on Fell/Thin

  • When a compartment is felled or thinned, the current compartment weed phase's 'Next phase if felled' or 'Next phase if thinned' setting is used to create a new weed assessment for the compartment, effectively moving the compartment into the specified weed phase.
  • This assessment's 'Recorded By' field is set to 'Fell APO' or 'Thin APO'.
  • If the compartment has not been assessed, the system assumes that its current phase is the lowest intensity level (e.g. Maintenance) and uses that to determine the next phase.
  • Any phase's 'Next phase if thinned' or 'Next phase if felled' setting may be intentionally unspecified in which case no assessment will be created.

• [Enhancement] Compartment View - New Activity Tab

  This new tab lists all activities that have occurred during the current rotation and those that are planned in future.

  • For activities in previous plans, only those with actual work are listed, no budget-only activities are included.
  • All activities in the current or future plans are listed, i.e. those with or without actual work.
  • The 'Done' column indicates if any actual work has been done; it is not an indication that work has been completed.
  • The 'Weed Phase' column indicates the weed phase during the activity. Only the first activity that was performed after the current weed phase was started will display the current weed phase.
  • The 'Regime' column displays the regime record associated with the activity, if any. If the associated activity of a specified regime entry is not present or cannot be identified, the activity detail will be blank.
  • The age is calculated at the end of the last interval that work was reported/planned.

PM 5.4.4 [07-Oct-2016]

• [Enhancement] Effective area calculation and synchronization

  The spatial processing module can now be configured to use an additional 'effective area' feature class as the source for commercial compartments' effective area. Normal compartment area calculation (coordinate system projection (if applicable) and road buffering) remains unchanged.

  • Similar to the original/base feature class, the new feature class must contain fields for the management unit code, landuse name and land type fields, as these are used to identify compartments.
  • Additionally, fields to store the calculated area and assigned LID must also be available.
  • All compartments that appear in the base feature class must also appear in the 'effective area' feature class and vice versa (number of polygons may differ if multiple polygons per landuse are used). An error will be generated if this is not the case.
  • Except for projection (if applicable), no additional processing (e.g. road buffering) will be applied to the 'effective area' feature class during area calculation, i.e. the polygons already represent the final effective areas of the compartments.
  • The spatial synchronisation process detects and synchronises area and LID changes using both these feature classes simultaneously.

PM 5.4.3 [20-Sep-2016]

• [Enhancement] Weed Management Module

  Please note that this is a licensed module; weed module functionality will either be hidden or disabled if a license is not available. Please contact Microforest for more information.

  Weed Assessment

  • Previously dominant weed selection was a precondition for weed density selection. Weed density is now always available, has moved to the top of the input controls and is linked to a default weed phase. When a density class is selected, the default phase is automatically selected. This auto-selected phase may be changed/overridden by the user.

  • The following table lists the default weed densities and linked phases:

    Weed Densities	Linked Weed Phase
    None	Maintenance
    Very Low	Maintenance
    Low	2nd Follow-up
    Medium	1st Follow-up
    High	Initial

    Note

    During the implementation of this functionality the weed phases of all existing weed assessments with a density but without a specified weed phase will be setup using the table above.

  • The Prescription selection box lists the 'Weeding' type prescriptions as configured in the System Table – Prescriptions window (see next). The user may select a value or leave it empty to be populated by the 'Assign weed prescriptions' advanced process (see later).

    Note

    It is important to execute the 'Assign weed prescriptions' advanced process after weed assessments were added, deleted or updated to allocate all 'missing' prescriptions and set the compartments' or open areas' effective weed phases and associated prescriptions. This data is used by the TPS weed plan process.

• Administration – System Tables: Prescriptions

  • Any number of prescriptions may be defined, each with one or more scheduled activities to execute. Currently the only type of prescriptions that may be created are weeding prescriptions, but a prescription definition is generic and will later be expanded to include other prescription types.

  • Any activity may be selected for a prescription; it is up to the user to choose only appropriate activities.

  • The following attributes may be assigned to a prescription activity:

    • After Event [Months]: The number of months after the trigger event to start executing the activity. Default = zero, i.e. immediately.
    • Number of Repeats: How many times the activity should be repeated during each application, e.g. #Repeats = 2 on a 10ha compartment would result in 20ha work.
    • #Cycles: The number of times the work should be repeated after the first application. Default = zero, i.e. not done again after the first application.
    • Cycle Length [Months]: If #Cycles is greater than zero, the length of the cycle in months before the next application.

  • Trigger Events:

    • The user may specify the trigger or combination of triggers that cause a prescription to be executed. It may be the age of a commercial compartment and/or the execution of specific activities or activities in specified activity groups.

      Note

      The trigger events are provided for future expansion and is not currently used. Prescription scheduling in the Tactical Planning System is based on weed phases, not these trigger events. The user may ignore this for now.**

  • Links

    • This grid displays a read-only list of prescription's weed phase links as defined in the Weed Prescription Link system table (next)

• Administration – System Tables: Weed Prescription Link

  • This is where weed phases are linked to prescriptions, i.e. which prescription will be executed for each weed phase in a specific management unit and WC.
  • Management units must be specified on the highest level possible with only exceptions (if any) on the lower levels. A link on a lower management unit level overrides those at higher levels.
  • WC must be left blank to specify a link for open areas.
  • It is important that all weed phase, M.Unit and WC combinations are covered, otherwise the 'Assign weed prescriptions' advanced process and TPS weed plan processes will generate errors.

• Advanced Processing - Assign weed prescriptions

  • This process assigns prescriptions to weed assessments and sets the compartments' and open areas' effective weed phases and associated prescriptions. This data is a prerequisite to generate the TPS weed plan.

• Tactical Planning System – Weed Plan

  The tactical planning system uses the assigned weed phases and prescriptions of assessments on compartments and open areas as a starting point. Thereafter it simulates the progression of phases using a combination of preset phase time periods and thin/fell operations in the plan. This is configured by Microforest on request, the defaults being:

  Phase	Management Unit	WC	Months to stay in phase before next	Next phase if period expired	Next phase if thinned	Next phase if felled
  Initial	All – Company	All	12	1st Follow-up	No Change	No Change
  1st Follow-up	All – Company	All	12	2nd Follow-up	No Change	Initial
  2nd Follow-up	All - Company	All	12	Maintenance	2nd Follow-up	Initial
  Maintenance	All - Company	All	Forever	N/A	2nd Follow-up	Initial

  The last weed assessment date is assumed to the start date of the weed phase for the compartment or open area. This is also the trigger event and start date for the prescription after which the prescription activities will be scheduled based on their configuration (After Event [Months], #Cycles, Cycle Length [Months], etc.)

  • Plan Group Admin
    • New option 'Use Weed Prescriptions' to enable/disable the weed plan functionality for all plans in the group.

  • TPS Detail Windows

    • New 'Weed Plan' tab that displays weed phases and prescription activities grouped per management unit, WC and weed phase.

  • TPS Summary Windows

    • New 'Weed Plan Summary' that displays a summary of total activity work and compartment/open area weed phase areas per plan period. The weed phase of a compartment/open area in the middle of the period is used.
  • TPS Map
    • New 'TPS <Period> Weed Phases' map layers for every <Period> in the plan.
  • Refresh Plan
    • Option to refresh the weed plan individually. Alternatively, it will also be refreshed if a full refresh is done.
  • Update Compartment Tables
    • New 'Weed Apo (to selected plans)' option.
    • New 'Plan (Weed Activities)' column on period selection grid. The user has to select a budget APO that corresponds to each TPS plan period (matching start/end dates). If no APO is selected, the weed plan for that period will not be written back to, or deleted from, any APO. The weed plan cannot be written back to an operational plan.
    • 'Delete Previous Plan' also deletes the activities of the TPS Plan from the specified APO plan(s).
    • The weeding activities are written to the selected APO in the month that it occurs with the specified budget work quantity.

PM 5.4.2 [24-Aug-2016]

• [Enhancement] Compartment Stop Growth Date

  • New 'Stop Growth Date' compartment attribute. User access controlled – off by default.

  • The stop growth dates' initial values have been set according to the applicable existing 100% intensity and 100% area (fire) damages, if any. Thereafter it will be automatically adjusted if an applicable damage is added, updated or deleted and the user has not overridden it. It means that the stop growth date will only be updated if:

    • The previous stop growth date was equal to the previous fire damage date, or
    • The stop growth date field is empty

  • The stop growth date is used to stop growth in the following processes/modules:

    • Modeling Tool – New 'Use stop growth age' option to use/ignore the compartment's stop growth date.
    • Advanced Processing – Calculate current (CUR) volumes – new 'Use stop growth date' option to use/ignore.
    • Advanced Processing – Calculate compartment volumes (APO) – new 'Use compartment stop growth date' option to use/ignore.
    • TPS – New 'Use compartment stop growth date' attribute on plan group level. If changed on a group with existing plans, all the group's plans will have to be refreshed or manually edited. If the option is switched on and thin supply is not refreshed (refresh entire plan or refresh thin compartments) to remove ineligible thin supply records after the stop growth dates, then errors will be reported for these supply records during volume recalculation.

    Note

    • None of the MAI related processes, nor the yield table generation process in Advanced Processing use the compartments' stop growth dates.
    • All thin operations after the stop growth date/age are ignored during modeling in the above mentioned processes.

PM 5.4.1 [16-Aug-2016]

• [Enhancement] New 'Next Conv 2' factor to use for TPS alternative units quantity calculation (refer to TPS enhancements in PM 3.7.2)
  • A new 'Next Conv 2' Buck Spec attribute has been added for this purpose (System Tables Administration). Its default value is set to the 'Conv 2' value.
  • A new 'Use Next Conv' attribute on TPS Plan Group periods. If switched on, the system will use the 'Next Conv 2' value to calculate the alternative quantity for the period.
  • When the 'Use Next Conv' option is changed, the TPS plan needs to be refreshed (Recalculate volumes and product allocation) to calculate the alternative quantities using the different factor.

PM 5.4.0 [13-Jul-2016]

• [Enhancement] Stand Table Projection – Thinning Control Enumerations & Thin Operations

  Previously stand table projection was stopped as soon as a thin operation was encountered.

  Instead of generating only a single calibration stand table, three stand tables are now generated during thinning control enumeration processing and the growth model will use the appropriate one during modeling:

  • Before Thin – Used for stand table projection from enumeration age to thin age.
  • Thin – Used for stand table projection for the thin operation.
  • After Thin – Used for stand table projection after the thin operation.

  Working plan enumeration calibration stand table generation and projection are unchanged, i.e. only one calibration stand table is generated and stand table projection is stopped if a thin operation is encountered.

  Coeff11 of function dminhwk has always been used to indicate the maximum period in years after enumeration that the stand table projection may be used (Max1). The above changes introduce the need for a second variable, i.e. the maximum period in years between enumeration and thinning (Max2). If this period is exceeded, stand table projection is not performed.

  Coeff11 is now used for both variables as follows: Max1.Max2, e.g.:

  Max1 = 10 years, Max2 = 2 years: Coeff11 = 10.2
  Max1 = 8 years, Max2 = 0.5 year: Coeff11 = 8.05
  Max1 = 8 years, Max2 = 2.5 years: Coeff11 = 8.25
  

  As before, if stand table projection must be performed during modeling, but no stand table is available, then an error is generated.

  The Modeling Tool lists all available calibration stand tables and indicates the type of stand table (Before/Thin/After). The output Stand Table now also indicates the type of stand table used, if any.

  Existing thinning control enumerations do not have the Before Thin and Thin stand tables and will have to be reprocessed to generate them. The Process button on the Enumeration Management window can now be used to process authorised enumerations (without first unauthorising and authorising them again afterwards) Only the last authorised enumeration can be reprocessed, others will be automatically skipped. The user will be prompted whether the compartment's SI and UMAI should also be updated. No regime changes will be done.

  Note

  The enhanced calibration stand table generation is only available in the 'new' enumeration functionality. This means that thinning control enumerations must be setup to use the new enumeration functionality, otherwise all the required stand tables will not be generated resulting in errors during modeling/volume calculation processes.

PM 5.3.9 [30-Jun-2016]

• Changed all "Plantation" references to "MUnit" or "Management Unit"

PM 5.3.8 [02-Jun-2016]

• Maintenance Release

PM 5.3.7 [26-Apr-2016]

• [Enhancement] – New Summary Enumeration Type

  • Enumeration type 'ALS Inventory' makes provision for the following variables: TPH, BA, HD, HM, DBH min, DBH StdDev
  • A new 'Process' button allows the SI to be calculated based on Cruise Date and HD. Process Date is also set.
  • If Cruise Date or HD is changed, SI and Process Date is cleared until processed again.
  • The enumeration may be authorised which will have the same impact as authorising a 'Working Plan' enumeration.

  • Advanced Processing provides a new 'Import Airborne Laser Scanning (ALS) inventory data' process that allows batch import of enumeration data.

    • The format of the comma delimited data in the import file must be as follows:

      Compt_Id, Inventory Date (yyyy/mm/dd or dd/mm/yyyy), TPH, BA, HD, HM,Dmin, Dsdev
      

    • ALS inventory data will replace existing ALS inventory records in PM with corresponding Compt_id and Inventory Date. However existing ALS inventory records that are authorised cannot be replaced, and in these cases the data import process will be aborted.

PM 5.3.6 [07-Apr-2016]

• [Enhancement] – Variable Plot Sizes (New Inventory System Only). Prior to this enhancement plot sizes where the same for all plots in the enumeration. Now a new 'Variable plot sizes' option can be switched on which allows different plot dimensions to be specified for each plot.

• [Enhancement] – Custom Plot Type (New Inventory System Only). A new 'Custom' plot type is now available (in addition to 'Circular' and 'Rectangular'). This allows the user to specify the actual areas of the plots in m2. An area specified in this way is not further influenced by the plot's slope, i.e. it should already take slope into consideration.

PM 5.3.5 [09-Mar-2016]

• [Enhancement] – New User Access Rights for Harvesting APO.

  • New application right: Operations - 'Edit Harvesting APO'. The user has harvesting APO edit access only if this item is selected, with full rights still determined by the other rights (Delete, Phase, etc.).

  • The following is disabled for harvesting APO's when this application right is not assigned:

    • New Activity – No harvesting activities will be listed, but can still be used as based-on.
    • Delete Activity
    • Edit Harvesting APO (summary and detail)
    • Add/Delete compartment
    • Un/Authorise
    • Tag & Phase
    • Move landuse to another activity.
    • Update activity category.
    • Reset unallocated.

PM 5.3.4 [02-Dec-2015]

• [Maintenance Release]

PM 5.3.3 [21-Oct-2015]

• [Enhancement] Model function BA1CR4M3 added to the model library.

PM 5.3.2 [08-Jul-2015]

• [Enhancement] Weeds – Work in progress, additional attributes on the weeds assessment window may be ignored for now.

PM 5.3.1 [08-Jul-2015]

• [Enhancement] Recalculate APO volume when opening a compartment for thin or fell. A new 'APO Volume' button is available on the Fell Status window when opening a compartment. It presents the user with a newly calculated volume record for the selected regime with the option to replace the existing volume record (if any).

• [Enhancement] Manually recalculate individual compartment volumes (APO and CUR). Similar to the APO and CUR volume calculation on the Advanced Processing window, but for a specific compartment. A new 'Recalculate' button is available on the compartment volume tab to achieve this.

• [Enhancement] Seedstock.

  • A seedstock item can now be made inactive. Inactive items will no longer appear in selection controls.
  • Additional optional attributes: Species, Type, Source, Generation 0, Generation 1 and Clonal Cycle.
  • If seedstock species is specified then the seedstock may only be used on compartments with the same species.
  • Seedstock attribute lookup values may be defined on the System Tables – Other window.

PM 5.3.0 [19-Jun-2015]

• [Enhancement] Added activity as criteria item on landuse filter for compartment, open area, road and infrastructure views and on APO selection windows. On the APO selection windows it effectively enables based-on APO creation.

• [Enhancement] New 'Task Unit' activity attribute (in addition to existing Work Unit and Prod Unit). If specified (Administration - System Tables – Activity) allows labour resources to be task based – see Business Suite 5.4.4.

PM 5.2.9 [05-Jun-2015]

• [Enhancement] Edit Archive Compartment's %V

• [Enhancement] Assign Supplier(s) to APO. Business Suite clients only.

  One or more suppliers may be assigned to APO activities in the Operations View. The assigned suppliers are used during Business Suite budget generation and works order activity selection (refer to Business Suite 5.4.3 release notes).

  A new Supplier column has been added to the activity detail grid. This column may be toggled on or off using the new 'Display Supplier' check box. Its default state (on or off) may be configured by Syndicate on customer request.

  A new 'Assign Supplier(s)' menu item is available on the right-click detail activity popup menu; only if the Supplier column is visible, the Budget Work (BW) type is selected, and the current user has the 'Assign APO Supplier(s)' application privilege.

  The new menu item opens the Apo Supplier(s) window. Available suppliers are limited by the current user's supplier access rights. Supplier assignment may be made for one or more landuses (compartments, etc); behaviour depends on whether only one landuse or multiple are selected:

  One landuse:

  • Its current supplier(s) with budget work allocations are displayed.
  • Budget work (BW) must be specified in the unit of measure of the activity (ha, etc.)

  Multiple landuses:

  • No previous supplier assignments are displayed.
  • Budget work percentages must be provided. Proportionally applied to all selected landuses on completion.

Tip

If required, press Ctrl-A to select all the landuses in the activity.

The system automatically assigns 100% of the BW to the first selected supplier. If a second supplier is added and the first supplier is still 100% allocated, then the system automatically assigns the work on a 50/50 basis. User may change as required. Full allocation of work is required.

PM 5.2.8 [08-May-2015]

• [Enhancement] Thin/Fell APO – Link to Regime when Compartment opened for Activity.

  • User to select the appropriate regime when the compartment is opened for an activity.

  • This enables the system to

    • Accurately allocate volumes and work to the correct regime.
    • Prevent over-allocation of work from multiple activities to the same regime.
    • Always correctly complete the regime when multiple activities are involved.
    • Automatically assign the correct TPH to thin activities on the PM Operations View and Business Suite works orders.

  • Existing APO records already opened will not have this link. In these cases, the system will determine the regime based on the last pending regime as was previously done. The users may also opt to close and reopen the compartment in order to explicitly establish the link.

PM 5.2.7 [26-Feb-2015]

• [Enhancement] APO – Select Compartment/Road/Open Area/Infrastructure

  Previously these selection windows allowed the user to select multiple items by using Ctrl/Shift while clicking on the row headers. If a mistake was made, the entire selection was lost.

  The selection mechanism on these windows has been enhanced as follows:

  • A new 'Sel' checkbox column now controls the selection.
  • The checkbox of a row is toggled on or off by clicking on any cell in the row.
  • Multiple rows may be highlighted (not yet selected) by clicking on the row header and dragging the mouse up or down or using Ctrl/Shift as appropriate.

  • Right-click opens a popup menu that allows the selection or un-selection of all rows or only of the highlighted rows.

    • Also, these selection grids have all been enhanced by adding multi-column sort functionality.

• [Bug Fix] Enumeration processor could sometimes use wrong product age range's waste percentages if more than one age range defined in buckspec table.

• [Bug Fix] Compartment List – Weed assessment fix

PM 5.2.6 [29-Sep-2014]

• [Enhancement] Compartment Delineation

  • Manage Delineation Independent of Delineation APO.

    The compartment delineation workflow process has always been driven by the three delineation APO activities, i.e. 'Delineation Assessment', 'Delineation' and 'Delineation Post-Establishment GPS'. The appropriate tab on the compartment Delineation Control is enabled as the corresponding delineation APO entry is completed during the process. Without following the APO-based workflow it was not possible to manually manage the delineation on the delineation user interface. See the 'Delineation Notes' in PM Documentation.

    Another option is now available whereby the delineation process may be purely user interface driven with no delineation APO dependency:

    Option 1 [Existing]: Apo driven as always. This is the current setting if delineation functionality has been enabled.

    Option 2 [New]: User interface driven with no delineation APO dependency. This is the current setting if delineation functionality has not been enabled.

    When a compartment is added to the fell APO:

    • With Option 1 a 'Delineation Assessment' APO is created and the compartment's delineation status is set to 'Assessment Scheduled' (as always).
    • With Option 2 this does not happen, except if the 'Use Delineation Plant Restriction' setting is enabled; if which case the compartment's delineation status is set to 'Assessment Scheduled' (but no APO created). This is done to still force delineation assessment before planting occurs.

  • Copy Delineation Information and Compartment Delineation Status to Next Rotation.

    Prior to this change, when a compartment was felled, delineation information was only available on the archive, not on the new compartment. Delineation information is now copied to the new compartment. If the new compartment's delineation information is changed, the archives still contains the history of the previous delineation(s).

    A side-effect of this with Option 1 [Existing]: Adding a compartment to the fell Apo will not generate a 'Delineation Assessment' APO if it has already been assessed. To reassess/repeat the delineation process if required, the user must add a 'Delineation Assessment' APO manually. This action resets the compartment's delineation status and deletes the old delineation information.

• [Enhancement] Edit and Process Archive Compartment Enumerations

  • Authorise and unauthorise now also allowed under this user access right setting.

PM 5.2.5 [30-Sep-2014]

• [Enhancement] Stand Table Projection – Mean Height and Dbh-Height Distribution Calibration and Projection

  • Calibrate and project mean height in function hm2hd2:

    Hmean2 = Hdom2 \* (Hmean1/Hdom1)
    
    Where:
    
        Xxxx2 = Value at projected age.
    
        Xxxx1 = Value at calibration (enumeration) age.
    

  • Calibrate and project the Dbh-Height Distribution

    • During enumeration processing, fit the Htdbh_dd (non-linear) function to the line represented by the normal (linear) dbh-height function.
    • Use calculated Htdbh_dd coefficients above for future projections.

  • The Modeling Tool has been enhanced to show the calculated Htdbh_dd coefficients on the 'Calibration Stand Table' tab.

  • This functionality is disabled by default, but may be enabled on request.

PM 5.2.4 [18-Sep-2014]

• [Enhancement] Successive Enumerations/Re-measurements (New Inventory System Only)

  • Copy 'Project' attribute to new successive measurement.
  • User interface prevents dead trees from becoming alive again in new successive measurement.
  • Copy dead tree DBH and height to new successive measurement.
  • Processing warning if DBH or Height reduction on new successive measurement (live trees only).

• [Enhancement] Edit and Process Archive Compartment Enumerations

  • New user access right setting to allow archived enumeration editing and processing. (Authorise and unauthorise still blocked)
  • Include enumerations of archived compartments in Enumeration Management window if archives included in compartment view filter.

PM 5.2.3 [04-Sep-2014]

• [Enhancement] Combobox/Dropdown Selection Improvement.

  It is sometimes laborious to find and select a specific item in a dropdown selection control with a very long list of items. When a user opens a single selection or multi-selection dropdown list and types a series of characters, the default Windows behavior is to select the first or next item that starts with each single character as it is typed.

  The following improvements are introduced to enhance the user experience:

  • Single selection combo boxes: The user may type the first few characters of a search item. The first item that starts with these characters will be selected. Previously the item that started with the last typed character would have been selected; parts of words could not be searched for. For this to work, the user must type each character within a time delay of approximately 1.5 seconds after the previous one, otherwise only the last character is used.

  • Multi-selection dropdown lists: Same as the above, except that there is no time delay constraint, the search string is displayed in grey italics and the user may search for text inside the items' text. The backspace key can be used to modify the search string. The first item that starts with the search string is highlighted, if none is found and the search string is at least three characters long, the first item that contains the search string in any position is highlighted. Once an item is highlighted, the user may select the item by pressing the space bar or with a mouse click. The search is case insensitive and spaces are ignored. For example, in the 'Activity' multi-selection dropdown on the 'Operations View' window, the user can search for 'P - Act 2' in the following list of activities by typing pact2 or ct2-: 'E Act 1 ***, E Act 2 ***, …. , P Act 1 ***, P Act 2-1 *** , P Act 3 ***…'

  Additionally, the Escape key (Esc) can now be used to close this list.

• [Bug fix] The Apply and Cancel buttons stay active on the Compartment, Open Area, Infrastructure & Road Views after editing mode cancelled.

PM 5.2.2 [25-Jul-2014]

• [Enhancement] Compartment & Open Area Summary Info – The Info/Statistics button (blue i button next to the reports button) now displays summary information for these two views (WC, Fire Risk, Ownership, etc.)
• [Bug fix] Error on TPS Plan Create – Avoid error if any selected higher level management unit(s) do not have any plantations.

PM 5.2.1 [18-Jun-2014]

• [Bug fix] Consolidate Open Areas – Move ASI's to master. Delete general attributes of non-master. Update confirmation/warning message to show all actions that will be performed.

PM 5.2.0 [05-Jun-2014]

• [Enhancement] Model Enhancement
  • No changes to the base model, but changes were made to the stand table procedures that may result in small volume variations for enumerated compartments. Calibration of DbhMin and DbhStdDev introduced to improve model projections after enumeration.
• [Enhancement] Modeling Tool - DbhMin and DbhStdDev columns are now included when the 'Yield Table' tab's 'Show Detailed Results' is enabled.
• [Bug fix] Handle Bark Volumes correctly.
  • Volume Tab - Previously erroneously indicated total volume vs summed product volume mismatch (red cell) because bark was also incorrectly included in summed product volume.
  • 'Add Volumes' – Assign correct bark log id of 99.
• [Bug fix] Removed not applicable/empty product columns and volume input controls from Volume Tab grid and 'Add Volumes' window respectively.

PM 5.1.12 [02-May-2014]

• [Enhancement] Change compartment fell authority during felling – An optional 'TUP Fell Authority' attribute may be specified on any existing fell authority. This attribute, if set on the fell authority of a compartment, will determine the new fell authority of the resulting felled TUP compartment.

  Please contact Syndicate if there are any fell authorities that you would like to setup like this, e.g. Research -> Management.

• [Enhancement] New enumeration 'Project' attribute.

  • This optional attribute is available on the summary and detail enumerations (new Inventory System only).
  • Enumeration Type and Project attributes have also been added as new compartment filter options.
  • Enumeration Project values may be edited using the 'System Tables', 'Other…' administration functionality. One or more Project values may be assigned to every enumeration type. User access needs to be granted for the 'Enumeration Project' option to be available here.
  • [Change] Compartment Enumeration Sort Order – Enumeration sort order changed back to descending enumeration date (newest topmost) irrespective of enumeration type (as it was before the change introduced in PM 5.1.6 – Successive Enumerations/Re-measurements).

PM 5.1.11 [25-Apr-2014]

• [Enhancement] Advanced Processing - Apo & Cur Volume Calculation. Improved performance, up to 2-5 times faster depending on network utilisation.
• [Enhancement] Plan Admin – New Revision. Now also available for Business Suite Clients.

PM 5.1.10 [17-Apr-2014]

• [Enhancement/Bugfix] New Area Recon Types & Area Recon Errors.

  Area recon always reconciles compartment area, not effective area. Previously when a compartment with an effective area smaller than its area was felled or planted, area recon errors were introduced. Two new area recon types have now been added that indicate this difference and eliminate these errors:

  • Fell Area/Effa Diff
  • Plant Area/Effa Diff

  Previously when a compartment was partially felled, the newly created #2 TUP compartment received the area/effa difference. This has been changed so that the area/effa difference remains with the #1 compartment and the #2 compartment's effa is equal to its area. Only when the compartment is fully felled, does the resulting live or #2 compartment receive the additional area difference which makes its area larger than effa.

  At this point, if the 'Reset Effa to Full Area during clearfell' setting is enabled (refer to PM 5.1.8 below), the compartment's effa is reset/increased to be equal to the area. Please contact Syndicate if you would like to enable this setting.

PM 5.1.9 [07-Apr-2014]

• [Enhancement] Species Admin - Add Report & Area Recon Species Group fields. Both mandatory.
• [Bugfix] Seedstock Admin - Error when adding seedstock item after having added one or more with an empty description.
• [Bugfix] Operations View - Fix summary grid's activity column sort order.

PM 5.1.8 [10-Mar-2014]

• [Enhancement] Roads – Added 'Ownership' attribute. Shows the ownership of the selected road. If the road comprises of multiple segments and their ownership types are different, '(Various)' is displayed. If the ownership is changed, all the segments in the road will be assigned the new ownership. If the user selects '(Various)' no update is performed.
• [Enhancement] Enumeration – Add 'Authorised By' attribute.
• [Enhancement] Utilisable TPH – Added TPH, Utilisable TPH and AvUTreeVol (see PM 5.1.6) to the TPS Detail Compartment Supply window.
• [Enhancement] Reset Effa to full Area during clearfell. E.g. if 2ha of compartment A1 (Area = 10, Effa = 9) is partially felled, then A1#1 (Area = 7, Effa = 7) and A1#2 (Area = 3, Effa = 3 (previously Effa would have been 2)) are created. Currently disabled pending investigation into area recon bug related to effa/area.
• [Enhancement] Added 'Src' (Source) and 'Created' (Date Created) columns to compartment volume tab. Only applicable to non-actual (e.g. APO, CUR, etc) type volumes. Source can be one of 'Proc' (advanced processing functions used), 'TPS' or 'HSS' (write back functions). All volumes created before this upgrade will have blank values for these attributes.

PM 5.1.7 [19-Feb-2014]

• [Change] Do not generate model execution error during UMAI or APO volume calculation (Advanced Processing) if a thin operation yields zero volume.

PM 5.1.6 [10-Jan-2014]

• [Enhancement] Utilisable TPH: The full TPH has historically been used for calculation of Utilisable Tree Volume (Average Utilisable Tree Volume = U.Vol / TPH). This is not necessarily correct, and can cause errors especially in modeling of younger stands and processing of inventories where small diameter trees are measured. A new variable Utilisable TPH was introduced on Mondi's request, defined as: the number of trees per hectare that produce utilisable timber (products as defined in buckspec).

  • Added to all volume calculations and modeling processes (Enumerations, Modeling Tool, Advanced processing, TPS, HSS)
  • Enumeration: Summary Report: 'Util TPH' added and used in tree vol calcs
  • Report Tool: Enumeration Report (export) 'Util TPH' added and used for calc of AvUTreeVol column
  • Modeling Tool: 'TphU' column added to Yield Table screen
  • Modeling Tool: Diameter Distribution report: 'Bucked frequency' added and used for calc of Vol Util (m3/tree) column
  • Report Tool: Volume Reports / Compartment Volumes – WP (export): 'Util TPH' added and used in calc of AvTree column
  • Report Tool: HSS Reports / 'TPH Util' added and used in calc of AvTree column

• [Enhancement] Enumeration - Summary Report

  • Util TPH mentioned above plus: Dbh min, Establishment method, %V, Buckspec table, Stump height, Cut allowance.

• [Enhancement] Enumeration – Chart DBH Analysis

  • New Diameter Distribution table including columns for Basal area, Bucked frequency, and Tree volume.

• [Enhancement] Modeling Tool – Diameter Distribution Report

  • New Diameter Distribution table including columns for Basal area, Bucked frequency, and Tree volume.

• [Enhancement] Successive Enumerations/Re-measurements (New Inventory System Only)

  • Clients may request Syndicate to enable successive measurements/re-measurements on selected enumeration types (PSPs, etc)
  • A new column 'M.Seq' in the compartment enumeration tab indicates the sequence of the re-measurements. Even if no re-measurements have been done a '1' in this column indicates that it is a re-measurement type, blank otherwise.
  • A re-measurement is done by selecting an existing eligible enumeration and using the new 'Successive' button.
  • Any number of re-measurements can be done, their sequence in the group indicated by a new 'M.Seq' column on the enumeration grid.
  • All measurements in a re-measurement group must be authorised before a next measurement can be done.
  • A new re-measurement is always copied from the last measurement (with largest sequence number), becomes the last measurement, and:
    • Only the 'Cruise Date', 'Cruised By' and enumeration & plot notes may be edited, the rest (type, plot type, input type and plot dimensions) are read-only.
    • All attribute values in the enumeration 'Attributes' tab are cleared; to be edited by user.
    • All plot attribute values in the plot 'Attributes' tab are cleared; to be edited by user.
    • Tree data is copied (including custom tree attributes) but all their dbh & height values are cleared; to be edited by user.
    • No dbh/height pairs are copied or allowed to be added in re-measurements. If required, height should be specified on the tree data itself.
    • Only the GPS data of the first enumeration is used by all measurements.
    • New trees may be added, but existing ones may not be deleted.
    • If a tree is no longer present, its 'Tree Condition' attribute should be set to 'Dead'. It will then be ignored during processing if the 'Dead' option's Volume/TPH influence is properly configured. Please consult with Syndicate in this regard.
    • Plots cannot not be added or deleted.
  • Only the first and the last measurement in a group can be deleted. If the first one is deleted, all the measurements in the group are deleted.
  • While any enumeration in a measurement group is viewed/edited, the others may be viewed by changing the new 'M.Seq' up/down control's value.
  • Although not recommended, any enumeration in a re-measurement group can be un-authorised and edited (e.g. to edit GPS coordinates), but then the above restrictions regarding read-only attributes and plot/tree add/delete apply.

• [Enhancement] Compartment TUP Date – Set to start or end of fell activity period.

  Historically a compartment's TUP Date was always set to the date when a fell operation was first applied/started. The option now exists to set the TUP Date to the date when the fell operation was last applied/ended. Note that the date is always the start date of the start or end period (depending on setting). Optionally, historic data of live compartments can be updated. Please contact Syndicate if you would like this option to be activated.

• [Enhancement] Next rotation – Add Espacement

  Espacement added to next rotation data set; optional, empty by default. If specified, used as default for APO plant information.

• [Bug fix] Year-end Area Reconciliation - Fix error during year-end area reconciliation process when more than one budget plan exist. The user is now required to select the next plan when doing the reconciliation, not only when doing the actual year-end.

PM 5.1.5 [27-Nov-2013]

• [Enhancement] System Tables Administration – Activity Codes: New Activity Level Hierarchy

  The Activity Codes administration window has been redesigned to allow for the definition of a four level activity classification hierarchy. Existing and new activity codes may be assigned to the lowest (fourth) level nodes in this hierarchy.

  This classification allows for enhanced reporting functionality if required. Its definition and use is optional. The activity selection mechanism throughout the system is unchanged.

  Default names and abbreviations have been assigned to the activity levels ('Activity Level 1' & 'Level 1', etc.). Syndicate will change these names and abbreviations on request.

  • An activity edit session is started by pressing the main 'Edit button; as usual and protected by user rights. While in an edit session:
    • New activity rows are added by typing in the last new empty row. A new activity is automatically assigned to the selected fourth level hierarchy node, if any.
    • Existing activities may be deleted (if not used in the system) by selecting the activity row and pressing the 'Del' button.
    • All activity updates must be submitted to the server or cancelled by pressing the main 'Apply' or 'Cancel' button which ends the editing session.
    • Activity hierarchy edit sessions are started and ended independently within a main edit session with its dedicated Apply and Cancel buttons.
  • The user may define an activity hierarchy of up to four levels below the default 'All Activities' node in a tree view. This is done by using a right-click context menu on any tree view hierarchy node to Add, Edit and Delete nodes. A hierarchy node edit session may also be started by simply typing in the Name, Abbreviation or Code text edits.
  • A right-click context menu on the activity grid allows selected activities to be assigned to the currently selected fourth level activity hierarchy node. Activity rows are selected by clicking in the leftmost grey row header cell. Following normal Windows practices, row selection can be extended by click-and-drag over the row header cell or by simultaneously using the shift or control keys.
  • The activity grid has four new columns indicating the activities' assigned activity hierarchy branch (abbreviations of all four levels). The user may hide these columns if required.
  • The 'All Activities' node always displays all the activities, assigned and unassigned. Lower level nodes display only the activities in that specific branch. A user option allows all unassigned activities also to be shown; this allows assignment.

PM 5.1.4 [08-Nov-2013]

• [Enhancement] Enumeration Plot ID – New 'Plot ID' business attribute. Ability to toggle plot tab control labels between 'Plot n' and 'Plot ID' value by right-click and 'Toggle Plot Label' menu item.

PM 5.1.3 [21-Oct-2013]

• [Bug fix] Enumeration Authorisation – Update compartment display with new Site Index after authorisation.

PM 5.1.2 [17-Oct-2013]

• [Enhancement] Enumeration (New Inventory System)
  • Delete plot in middle of range with right-click and 'Delete Plot' menu item.
  • Allow enumerations with zero utilisable volume (e.g. young compartment) to be authorised - warning only.
  • In addition to boolean 'Volume Loss' attribute, add 'Tree Condition' attribute with choices 'Normal', 'Damaged' (loss applicable – see PM 3.7.8) and 'Dead'. 'Dead' option's volume & TPH influence configurable by Syndicate.
  • Compartment name added to Enumeration window label.

PM 5.1.1 [20-Sep-2013]

• [Enhancement] Enumeration (New Inventory System) – Provide ability to implement custom height function if height regression is not available/possible. Available on request only. T&C apply.

PM 5.1.0 [09-Sep-2013]

• [Enhancement] Management Unit Code
  • The management unit code replaces the original management unit id ('MU_Id') on all Microforest user interface elements, maps, file and device interfaces/imports and reports.
  • Management Units Admin
    • 'Management Unit Id' (MU_Id) removed, replaced by 'Management Unit Code' (previously 'User Code').
    • Management Unit Code is a numeric only field, initially set to the value of MU_Id.
    • Users may change the Management Unit Code as required, but have to manually update all related spatial management unit ids/codes to be the same as the Management Unit Code.
    • 'Short Name' has been renamed to 'Abbreviation'.

PM 5.0.3 [28-Aug-2013]

• NEW Inventory System including:
  • Quality Control (QC) sampling and assessments
  • Permanent Sampling Plot (PSP) assessments
  • Various enhancements to the Working Plan and Thinning Control methods

Available on request only. T&C apply.

• [Bug Fix] ASI View mode - Prescription & Notes text boxes were previously disabled, preventing view of all text, changed to enabled but read-only to enable scrolling.
• [Bug Fix] Spatial Processing, Area/Length calculation – User interface sometimes updated wrong process's status (user name and date) immediately after length or area calculated (always stored correctly on database).

PM 5.0.2 [29-Jul-2013]

• [Change] Enumeration – Where empty plots allowed and present in an enumeration, include in enumeration statistical analysis (previously ignored).

PM 5.0.1 [21-Jul-2013]

• [Enhancement] Enumeration – Add plot level volume and height statistics.
• [Bug fix] TPS - During write back if 'Delete Previous Plan' is selected, clear only TPS locks, not non-TPS locks.
• [Bug fix] Spatial Processing - Area Sync: Date & user status update omitted during ArcGIS 10.1 migration, corrected.

PM 5.0.0 [02-Jul-2013]

• PM and BS versions changed to use same major release number (5)
• [Enhancement] TPS
  • Allow compartments younger than four years to be added to plan.
  • During write back volumes will not be written back for records where volume errors already exist (red records); only the fell date will be updated if applicable. Additional volume errors discovered during write back will result in write back failure.

PM 3.7.10 [15-May-2013]

• [Enhancement] Multi-Column Data Grid Sort

  • The data grids in the System Tables Administration module have been enhanced to allow sorting by multiple columns. A grid with this capability is identifiable by a ^ symbol in the top left corner cell. When sorted, the ^ symbol is replaced by '…' and this cell's tooltip text displays the current active sort column names. The column sort order is determined by the order in which the columns were selected. If the Shift key is pressed when a column header is clicked, the column is added to the sort column list. If Shift is not pressed, the sort column list is cleared and the column is added to the sort column list as the first and only column. If an existing sort column is clicked (with or without pressing Shift), the column's sort order is changed from ascending to descending and vice versa.

• [Enhancement] %V Implementation in HSS Reports: HSS applies %V (volume loss/gain) to compartment volumes if the 'Use compartment volume loss percentage' is selected in the Options page. If this flag is not selected, users have the option to apply %V when printing the following HSS reports: Compartment Output, Summarised Output. This release includes the following changes to these reports:

  • %V values are read from the HSS Input table, not from the compartment register as previously.
  • The report cannot re-apply %V if it has already been applied during the HSS run.
  • The report prints the %V value (red in PDF) ONLY if it has been applied in either the HSS run or the report.

PM 3.7.9 [25-Apr-2013]

• [Enhancement] Map Viewer –Google Earth KMZ generation facility
  • A new button on the Map Viewer window that allows a user to generate a kmz file (zipped kml) for a selected layer and the current extent. The kmz file can be opened in Google Earth (must be pre-installed), or its location opened in the Windows file explorer.
• [Enhancement] Enumeration View/Edit
  • When an enumeration is saved/applied, projected GPS plot coordinates are automatically converted to geographic and inserted into the enumeration spatial layer. No need to do manually for each plot.
  • When any cell of a plot column is selected/clicked and GPS coordinates exist for the plot, the "Plot x GPS" tab is automatically activated.

EDI 1.8.0 [25-Apr-2013]

• [Enhancement] EDI 1 Enumeration Input File Format – GPS points .This file format has been enhanced to optionally include plot GPS information. If the data in the geodatabase is in the geographic WGS1984 format, the coordinates may be specified in WGS1984 or in any appropriate projected coordinate system (PCS) format. However, if the data is stored in a PCS format, then the GPS coordinates may only be specified using the same PCS.

PM 3.7.8 [12-Apr-2013]

• [Enhancement] Enumeration – New 'Working Plan with Loss Assessment' enumeration type.
  • The DBHs of trees with loss can be marked with an asterisk (*), similar to marking trees for thinning in a 'Thinning Control' enumeration.
  • Marked trees are handled identically to other trees (as if not marked), not influencing the enumeration growth model and statistical analysis, but an average loss percentage setting (configured by Syndicate) is used to calculate the utilisable volume loss for each marked tree.
  • When calculating the UMAI, the total utilisable volume loss is subtracted from the total utilisable volume.
  • UMAI is used in certain spesialised growth model configurations. For this reason, provision has also been made for UMAI capturing on the Modeling Tool. These values are ignored in the standard growth models.

PM 3.7.7 [10-Apr-2013]

• [Enhancement] Enumeration - Projected GPS Plot Coordinates.
  • Added ability to specify GPS projected coordinate system on PM Enumeration window.
  • Plot coordinates can be specified in projected units (e.g. meter) and converted to decimal degrees using the specified projected coordinate system.
• [Enhancement] Enumeration – Null/Empty Plots.
  • Previously all plots were required to have DBH values. If some were left empty (i.e. no DBH values specified), the system automatically removed these plots.
  • A new setting (configured by Syndicate on client request) is now available that allows empty or Null plots to be present.
  • Null plots are ignored by the enumeration growth model and statistical analysis but can proportionally reduce the compartment effective area during authorization if so configured.

PM 3.7.6 [26-Feb-2013]

• [Enhancement] Yield Table Generator – Ability to optionally include Archive compartments.

PM 3.7.5 [13-Feb-2013]

• [Enhancements & Bug Fixes] Tactical Planning
  • Do not include bark (buck spec log id = 99) in total product value.
  • Prevent a bark volume calculation error under certain circumstances when enumerations are present.
  • Added units of measure to Area, Age and DBH.
• [Reports]
  • Compartment List – General: CFLock field added to export
  • TPS Detail – Supply: enhanced for bark quantities

PM 3.7.4 [21-Jan-2013]

• [Enhancement] Tactical Planning – System Matrix by Establishment. A system matrix can be defined for any establishment type which will override the default system matrix.
• [Bug fix] Compartment User Access – Fixed user access for CF lock type selection and added user access for fire risk rating.

PM 3.7.3 [30-Nov-2012]

• [Enhancement] Yield Table Generator – Add ability to specify alternative bucking specification.

PM 3.7.2 [16-Nov-2012]

• [Enhancement] Compartments
  • Fell Lock – Replaced 'Locked' flag with lock type selection (Not Locked, General and Lease).
  • New predefined 'General' attributes: Erosion Hazard, Compaction Hazard, Wet/Dry Road Access, Dominant Aspect, Ext Primary Transport Distance, Secondary Transport Distance.
• [Enhancement] Tactical Planning
  • All volumes are now calculated. Previously volumes were only calculated if no existing APO volumes (from HSS or volume calculation processes) were available to reuse.
  • Ability to lock compartments with 'TPS Lock' type during write back from TPS.
  • Option to show volumes or converted/alternative units (see next) with or without % Volume Loss at any time.
  • Option to show volumes (m3) or converted/alternative units (e.g. ton) at any time. The Buck Spec 'Conv 2' factors are used for this conversion (see System Tables Administration).
  • The % Volume Loss and Volume vs. Alternative Unit default settings may be specified on plan group and plan level.
  • In addition to the Thin/Fell and WC filter, a new 'Regime (Option)' multiple selection filter.
  • A new 'Use Filters' option on the 'Composition Summary' tab specifies whether the current WC, Thin/Fell and Regime filters should be used when calculating the summary.
  • A new 'Total' row on the Composition Summary tab.
  • New columns added: Regime, Establishment, Lock Type, %V, Vol/ha, UMAI, TVol/Tree
  • Various bug fixes:
    • Display proper error message during plan load if no applicable compartments in plan..
    • Replaced multiple "One or more management units are already defined in other plans: x,y,z...!" errors with single error message.
    • Don't repeat WC in multiple "No products/commodities defined for XX working circle" errors.
    • Always check locks also when writing back, compartments might have been locked after plan setup.
    • Always reload plan when re-opened from Open 'Plan button' - to see updated compartment info, if any.
    • On plan load, display proper warning message when plan group WCs removed.
    • On plan load, display proper warning message when systems changed.
    • Etc.

PM 3.7.1 [27-Sep-2012]

• [Enhancement] ASI: Make provision for ASIs to be added to 'Maintained' (infrastructure) 'sub-class' activities on the APO. Allow ASIs to be deleted from the Infrastructure View.

HSS 5.10.6 [19-Sep-2012]

[Enhancement] Stump height & Cut Allowance: Add stump height and cut allowance growth model attributes as user configurable attributes to the buck class.

PM 3.7.0 [05-Sep-2012]

• [Enhancement] Advance Processing – Import compartment/open area weeds and/or fire risk data.
  • Imports compartment/open area weed and/or fire risk data from a comma-delimited text file (use 'Save-As' to 'CSV (Comma Delimited)' in Excel).
  • If a compartment name without part identifiers (#1, etc.) is specified, and only part compartments exist, then the first compartment found is used, in order: #1, #2, #3.
  • If the compartment/open area has an existing weed record on the same date, then the existing weed record is updated, else a new record is added.
  • It is possible to load both the compartment/open area fire risk rating and weed information in one record, or each separately by leaving either the fire risk rating attribute or weed attributes blank. Leaving both sets blank will result in a delete – see next point.
  • It is possible to delete weed attributes by leaving the fire risk rating and the otherwise mandatory 'Rec By' attribute blank: If a date is specified then all weed records for the compartment/open area on the specific date are deleted, if no date is specified then all weed records for the compartment/open area are deleted.
  • Identical weed attribute validation rules apply as when manually adding/updating weed records through the user interface.
  • Any failure will result in no updates being applied to the database (all or nothing).

PM 3.6.9 [15-Aug-2012]

• [Enhancement] System Table Administration - Activities: Add ability to edit GL and HR system interface codes.
• [Enhancement] New compartment fire rating attribute.
• [Enhancement] New 'General' tab for additional compartment and open area attributes. Depending on the configuration, attribute values are optional or mandatory, and values can be selected from a predefined lookup list or a text value can be supplied. No other associated business logic. Please contact Syndicate to configure if required.
• [Enhancement] New Weeds tab for compartments, similar to the Open Area Weeds tab. Additional optional weed rating attribute, if supplied validated according to the intensity: 0 – 10%: Low ratings, 10 – 50%: Medium ratings, 50 – 100%: High ratings.

PM 3.6.8 [13-Aug-2012]

• [Enhancement] Stump height & Cut Allowance: Add stump height and cut allowance growth model attributes as user configurable attributes to the buck class. Enhance System Tables Administration to allow editing of these attributes.
• [Enhancement] Modeling Tool: Display bucking specification 'Conversion' attribute on Bucking tab. Allow cut allowance user override (in addition to existing stump height). Display correct UVol unit of measure (if not default 'm3').

PM 3.6.7 [13-Jul-2012]

• [Change] System Tables Administration – Activity: Increase 'Code' field length to 20 characters.

PM 3.6.6 [29-Feb-2012]

• [Bugfix] Compartment Fell Status Control – Fix access control bug.

PM 3.6.5 [16-Jan-2012]

• [Enhancement] Volume – Add 'Excl. AvsP' volume flag to exclude selected volume records from Actual vs Predicted reports. This flag can be set/cleared on the compartment volume tab. Only available if enabled via global setting – Syndicate to configure if required.
• [Enhancement] Advanced Processing – Import Compt/OA Damage
  • Imports compartment and open area damage information from a comma-delimited text file (use 'Save-As' to 'CSV (Comma Delimited)' in Excel).
  • All damages except open area weeds can be imported.
  • If a compartment name without part identifiers (#1, etc.) is specified, and only part compartments exist, then the first compartment found is used, in order: #1, #2, #3.
  • If the compartment has an existing damage for the same damage class, type and date, then the existing damage record is updated, else a new record is added.
  • If both area and intensity percentage = 0 then matching compartment damages are deleted. If the date is empty then all compartment damages with the same class and type are deleted.
  • Any failure will result in no updates being applied to the database (all or nothing).
• [Bugfix] Road selection for APO - Error when 'Blocks' filter used to search for roads.

PM 3.6.4 [20-Nov-2011]

• [Enhancement] BA Override Functionality

PM 3.6.3 [25-Oct-2011]

• [Enhancement] Roads & Infrastructure Views – New button to move selected items to a different plantation (MF only, GIS to be handled separately).

PM 3.6.2 [29-Aug-2011]

• [Enhancement] User Management
  • Add right-click popup menu to logistics data access tabs for un/select all/selected functionality.
  • Add 'auto assign access to new entities' flags to logistics data access tabs.
• [Change] Compartment View
  • Exclude 'Legacy' enumerations from 'not processed yet' filter (does not get processed).
  • 'Age/Fell Status' - show age also if closed, previously displayed only "Closed"
• [Enhancement] Enumeration Defaults – No longer cached, updated values available immediately. Improved certain enumeration error messages by displaying values/and or range limits.
• [Enhancement] Enumeration Statistics – Increase Dbh/Hgt regression F value's maximum value from 999 to 99,999 to make provision for large number of Dbh/Hgt pairs.
• [Enhancement] Spatial Synchronisation – Make provision for optionally utilising ArcSDE multi-versioned views thereby enabling synchronisation to a specific spatial version.
• [Enhancement] System Table Administration, 'Other' – Added Activity Categories.
• [Enhancement] Main Application Window – Change dark grey background to white and make provision for simple image or html page display when logged out, or after logged in and before any other windows opened.
• [Enhancement] Modeling Tool – Added 'BA Override' which allows user specified BA value to override growth model calculated value. Not persisted yet.
• [Bug fix] Operations View – Some confirmation & error messages displayed activity id instead of activity code & abbreviation.
• [Bug fix] Compartment View – Incorrectly used the Open Area damage user rights instead of the Compartment damage user access rights for Add. Edit, Delete of damages.
• [Bug fix] Fixed error that occurred when user attempted to copy selected rows by pressing <Ctrl>-C or <Ctrl>-<Insert> on some data grids (e.g. compartment list on Compartment view, etc.).

PM 3.6.1 [29-Jul-2011]

• [Change] System Tables – In order to preserve data integrity, disable editing of the id and name attributes of existing buck classes, and disable editing of the class, log id, and name attributes of existing buck spec records.

PM 3.6.0 [17-Jun-2011]

• [Enhancement] Spatial road synchronisation – Option to specify GIS as master (vs. default MF master). Optional feature which requires client specific script enhancements.

PM 3.5.6 [10-Jun-2011]

• [Change] NS1ME2 survival model changed to utilise the survival TPH correctly during calibration. This function is mainly used in P.ell models at this stage.

• [Enhancement] New Crop Failure Functionality

  Provides functionality to flag crop failure compartments and report crop failure fell and replant activities.

  A new compartment 'crop failure' attribute indicates crop failures. Authorised users may toggle this flag on the compartment edit window. No activity validation is performed at this point.

  Two new activity classes 'Crop Fail – Fell' and 'Crop Fail – Replant' operate on crop failed compartments. Users may add any number of activities belonging to these classes: Besides using the new classes, activities are to be defined with exactly the same attributes as normal 'Fell' and 'Plant' class activities.

  Felling and (re-)planting crop failure compartments may only be performed using abovementioned activities; normal fell/plant activities are not allowed. These activities may not be used on non-crop failure compartments. This is checked when compartments are added to the APO and when actual work is performed.

  The crop failure fell and plant activities validations are identical to that of their non-crop failure counterparts, except that a crop failure compartment does not have to be on the fell plan, but still has to be open for actual work and volumes.

  Once felled, the crop failure flag is carried over to the TUP compartment. This flag is cleared when the compartment is planted.

  The crop-failure activities results in two new area reconciliation type being reported: 'Crop Fail – Fell' and 'Crop Fail – Replant'.

PM 3.5.5 [15-Apr-2011]

• [Enhancement] Added activity category column to the detail activity grid on the Operations View, with the ability to edit the activity category of selected records using the detail activity pop-up context menu.

PM 3.5.4 [15-Apr-2011]

• [Enhancement] New attributes on users, currently only used by the works orders functionality in the Business Suite:
  • Designation – New user attribute, and new system table editable on 'System Tables – Other'. .
  • Stand-in – New user attribute, and new user admin tab to list all the users a user is standing in for. This makes provision for user specific tasks to be performed by a user's stand-in if the user is not available
  • Authorisation list – New tab on user admin window. All users in a user's authorisation list must authorise certain actions initiated by the user.
• [Bug Fix] Regime update validation - fix bug on check during single-statement multi-compt regime update (bulk load).
• [Change] Enumeration EDI changed to recalculate plot 'trees per hectare' in all cases, using the number of diameters measured per plot.

PM 3.5.3 [30-Mar-2011]

• [Enhancement] Advanced Processing – Calculate compartment volumes:
  • Make provision for additional volume type (contact Syndicate if required).
  • Add option to exclude compartment percentage volume loss.
  • Replace minimum date only with date range and available for live compartments also.
• [Bug fix] Unrealistic TPH values corrected in Modelling Tool and Yield Table processing, specifically in early years (before 1^st thin) and when felled on thinning age.

PM 3.5.2 [01-Mar-2011]

• [Enhancement] Added 'Moisture Deduction Species' to Species. This is used for moisture deduction functionality on the Weighbridge Business Suite application. It allows you to group species with similar moisture characteristics together, reducing the number of moisture deduction sets required (defined in the Business Suite).

PM 3.5.1 [20-Jan-2011]

• [Enhancement] Added 'Min Enumeration Age' to WC, replacing the previous single global setting. Used in growth modelling to instruct the model to ignore any (possibly unrealistic) enumerations done before the predefined minimum age (if set to 0, no enumerations are ignored). If the enumeration is ignored, the default compartment SI is used.
• [Enhancement] Compartment – Change archive's information display colour from dark grey to blue.
• [Bug Fix] TPS – Fix null-pointer error during plan opening if no demand defined on plan.

PM 3.5.0 [03-Jan-2011]

• [Enhancement] Compartment volumes - allow volumes from different species and/or product set (bucking specification) to be recorded against a compartment.

  • Controlled by compartment level attribute. Disallowed by default. Editable on archive compartments.
  • PM Compartment Add Actual Volume – Allow different species and/or bucking specification selection.
  • PM Compartment Volume Tab – Species column added and additional product volume set columns displayed if applicable.

• [Enhancement] Compartment Open/Close for felling/thinning - allow compartments to be open against multiple activities if required.

  • Controlled by global setting. Disallowed by default.
  • Activation depends on compatibility with external volume interfaces.
  • PM Compartment Add Actual Volume - User chooses applicable open activity.
  • PM Compartment Fell Status Tab - User may open compartments for multiple activities. Full open/close history is kept.

• [Enhancement] Split TPS attribute view and edit rights, i.e. can be separately controlled.

• [Bug Fix] Quick Search - Fix error that occurred if * is part of search string.

PM 3.4.1 [08-Nov-2010]

• [Bug Fix] Manage Enumerations - Fix duplicate item error when more than one enumeration from a compartment authorized.
• [Enhancement] Manage Enumerations - Sort enumerations by date when authorizing so that most recent enumeration (if more than one) is authorized last.
• [Enhancement] Enumeration Processing – Check individual enumeration statistics for possible database size overflow.

PM 3.4.0 [01-Nov-2010]

• [New] Stand Table Projection functionality (Nepal-Somers). This model enhancement, when switched on, increases the product estimation accuracy of enumerated compartments (especially for saw log regimes).
• [Enhancement] Modeling Tool – Function coefficient reference & description, SaveAs functionality, calibration stand table display/edit, and output stand table display.
• [Bug fix] Map View - Transparency of selected polygon features increased to avoid other non-selected features (e.g. roads) being hidden by selection.

PM 3.3.0 [11-Oct-2010]

• [New] Yield table generation functionality – Advanced Processing. Yield Table Generation is an optional licensed item. It is used specifically by clients utilising external planning components, e.g. optimisation modules. It generates output similar to that of the modelling tool, for the current and next rotation.

PM 3.2.17 [16-Jul-2010]

• [Bug fix] Generic system tables editing ('Other…') – Row 'Del' key deletion (as opposed to 'Delete' button) did not function properly.
• [Bug fix] Compartment seedstock edit - incorrectly used e.g. 123123 if both 123123 and 123-123 are in lookup list and 123-123 is selected.

PM 3.2.16 [15-Jun-2010]

• [Enhancement] Small changes to activity code display from 3.2.15.

PM 3.2.15 [07-Jun-2010]

• [New] Additional system tables editing functionality. See File->Administration->System Tables->Other…
• [Enhancement] Display activity 'Code – Abbreviation' (and/or description) not Id. Code may be edited, enabling users to modify activity display value (system tables). Also fully internationalised.
• [New] Modeling Tool Reports.

PM 3.2.14 [17-May-2010]

• [New] Species recommendation. See species recommendation notes.
• [New] Delineation - Additional post-plant GPS functionality. See delineation notes.
• [New] Selected documentation made available from PM Help menu item.
• [Enhancement] Actual volumes - include additional compartment information (WC, Species, Regime Option, Effa, Rotation, Activity Date)

PM 3.2.13 [20-Apr-2010]

• [Enhancement] Allow hierarchical management unit regime link definition with lower level unit setting overriding more generic settings.
• [Bug fix] Under some circumstances plant and coppice operations did not use defined default survival & EC ages and % Volume loss.

PM 3.2.12 [08-Dec-2010]

• [Bug fix] Implement workaround to avoid materialized view error during APO/CUR volume calculation process.
• [Enhancement] Thinning control enumeration authorisation – set pending regime's age to age on authorisation date.

PM 3.2.11 [19-Feb-2010]

• [Enhancement] Spatial synchronisation – add ownership filter.
• [Bug fix] Compartment view - fix next rotation control resize bug.

PM 3.2.10 [21-Jan-2010]

• [Enhancement] Interval name internationalization.
• [Bug fix] Under certain circumstances the map icon & menu item would be incorrectly disabled.

PM 3.2.9 [11-Jan-2009]

• [New] New Cur/Apo volume recalculation & removal of obsolete volume types.

  • Please do not use until go-ahead given, in final testing phase. User access removed ("Advanced Processing").

• [New] "Overhead" activity sub-class (for plantation level activity).

  • When defining new overhead activities in system tables, specify the 'Overhead' sub-class
  • On Operations window, user cannot add landuses (compartments, open areas, etc.) to this activity.

• [Enhancement] Allow compartment volume loss percentage (%V) to be less than zero, i.e. increase volume.

• [Bug fix] Under certain circumstances during compartment edit, the compartment buck spec id (non-editable) would be lost.
• [Enhancement] Report internationalization.