Articles in this section

TMv2 July 2025 | Fleet Maintenance | (Minor) Release Notes

TM VERSION NUMBER: 2.666/665/666.9354

Disclaimer:

  • All developments and fixes contained in this release have a stated minimum version number (2.664, 2.665 or 2.666).
  • Current supported versions are 2.664 and higher.
  • Developments and fixes are relevant to minimum version and higher.
  • Developments are TMv2 module specific and may not be available under your current subscription.
  • Developments may be configurable, so may not be automatically applied upon upgrade.

🎉Enhancements and New Features

[NEW FEATURE] [USER RIGHTS MODIFIED]

  • In the 'Jobs' module and the 'Components' module, some existing user rights have been added as additional specific rights.
  • This provides more granular control to the editing of codes and critical fields.
  • The new User Rights allow rights to be granted specifically to the following functions:
    • Assigned To
    • Pre-Warning
    • Serial Number & Consequence/Risk Evaluation
  • The following existing Rights are unchanged.
    • Components Module > EditCriticalFields2
    • Jobs Module > EditCriticalFields
    • Jobs Module > EditCodeFields

Administrators can assign 3 (new) user rights to any user or user group. The user rights are:

  • Components > EditSerialNumber&Consequence/RiskEvaluation
    • Hover your mouse over the user right to see the description: ‘Can add or edit a serial number. Can add or edit consequence and risk assessment’.
  • Jobs > EditPrewarning
    • Hover your mouse over the user right to see the description: ‘Can add and edit prewarning’.
  • Jobs > CanAssignTo
    • Hover your mouse over the user right to see the description: ‘Can use ‘Assign to’ field’.

Preconditions:

  1. Open TM2.
  2. Select the database version.
  3. Click OK.

Reproduction steps:

  1. Log into TM2.
  2. Click Administration.
  3. Click User Groups.
  4. Double click and open a user group.
  5. Click Components
  6. Click to check the EditSerialNumber&Consequence/RiskEvaluation checkbox.
  7. Click Save.
  8. Click Jobs.
  9. Click to check the EditPrewarning checkbox.
  10. Click to check the CanAssignTo checkbox.
  11. Click Save and close.

[ENHANCEMENT] [LOCATOR LOCK AUTHORISATION EXTENSION TO STOCK MOVEMENT]

  • In the Stock module, a new user right has been created to allow users to lock or unlock stock movements for a folder.
    • The right is CanLockStockMovement.
    • You can check the ‘Stock Locked’ checkbox for the folder.
    • The existing ‘Locked’ folder check box has been repositioned and has a new label titled ‘Location Locked’. There is no change to the existing ‘Locked’ functionality (only a label change).
    • The ‘Location Locked’ and ‘Stock Locked’ function independently.
    • When upgrading, folders with the ‘Locked’ status will automatically assume ‘Location Locked’ status.
  • When dragging stock from a locked folder, an alert appears instead of the stock movement window. You must click Okay to accept the restriction.

Preconditions:

  1. Open TM2.
  2. Select the database version.
  3. Click OK.

Reproduction steps:

  1. Log into TM2.
  2. Click Administration.
  3. Click User Groups.
  4. Double click and open a user group (that should be able to lock/unlock folders).
  5. Scroll down to click on the Stock module listed in General tab.
  6. Click to check the ‘CanLockStockMovement’ right.
  7. Save and close.
  8. Click on the Inventory dropdown menu.
  9. Right click on a folder and select Open.
  10. Click the Stock Locked checkbox.
  11. Save and close.

[ENHANCEMENT] [ABILITY TO ADD FILE TO UNIT SPECIFIC SPARE PART]

  • The ability to add a document to a unit specific spart part (item) on Vessel and in Office has been added.

Preconditions:

  1. Open TM2.
  2. Select the database version.
  3. Click OK.

Reproduction steps:

Vessel Workflow

  1. Click Items.
  2. Double click the item (within the tree directory) and double click the listed item.
  3. Select the spare part item.
  4. Click the Documents tab. (The horizontal split appears with the tool bar and grid for the 'Item Unit Documents' (upper) and the 'Item Documents' (lower).)
  5. On the 'Item Unit Documents' toolbar, click Add File. (The file selector window opens allow selection of the file.)
  6. Add a description and click Okay.

The unit specific spare part document is displayed within the grid.

Office Workflow

  1. Select Unit.
  2. Click Items.
  3. Double click the item (within tree directory) and double click the listed item.
  4. Select the spare part item.
  5. Click the Documents tab. (The horizontal split appears with the tool bar and grid for the 'Item Unit Documents' (upper) and the 'Item Documents' (lower).)
  6. On the 'Item Unit Documents' toolbar, click Add File.
  7. Select the unit and click Continue or Cancel.*
  8. Click Continue. The pop-up window closes and the 'Add File' interface appears.
  9. The window opens allowing you to select the file.
  10. Add a description and click Okay.

The unit specific spare part document is displayed within the grid.


[ENHANCEMENT] [ITEM AND CATALOGUE IMPORT TEMPLATE UPDATE]

  • The Item and catalogue import template has been updated to include a Price and Estimated Delivery Date column.
  • The Estimated Delivery date column must have an integer value. If the estimated lead-time is not known the column should receive a ‘0’ value. This work around will be rectified in our August release.
  • The following templates have been updated and added to the report pack for this July 2025 release:
    • SparePartItemList_Layout 1.xlsx
    • CatalogItemList_Layout 1.xlsx 

Preconditions:

  • The updated July_2025 release All_Reports.v2Reports file can be found in the install path \v2Data\Reports.
  • It can be imported in TMv2 by logging in with an Admin account, then clicking "File"->"Import"->"Import Reports" and selecting the All_Reports file.

 

🛠️Bug Fixes

[TMITEMNO ASSIGNMENTS WERE DUPLICATED]

  • Issue:
    • Previously, when creating items in the database, the TmItemNo did not apply correctly, and items were created with duplicate TmItemNo values.
    • This was due to the running number being pulled from TmSystem.SparePartNo instead of TmNumberFormatUnits.
  • Affected Users:
    • This is applicable for all users.
  • Outcome:
    • This issue has been fixed.

Summary

We appreciate your continued partnership and welcome any feedback you have on this latest update. If you have any questions or need further assistance, please feel free to reach out to our support team.

Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.