What’s new in PTW 1.6.4.4 Release

ptw feature, ptw release, PTW-Update

The following is a full list of features that were implemented in the Pisys PTW 1.6.4.4 release.

 1.1.1. Introduce User-Specific Default Filters

We have added functionality to allow users to store their default filter settings on several screens throughout PTW so that it initially opens with their preferred selections when they login. We have added this functionality to the screens listed below:

  • Screens:
    • Permit List
    • Isolation List
    • Permit Board
    • Plot Plan
  • New “Search Filters” row added, containing buttons for “Save” and “Load”
    • Save
      • This button is available at all times and allows the User to do a manual save of the currently selected filters.
      • These are stored in the database and will be available for reload/recall any time, even after logging-out/in.
    • Load
      • This button is only available once the User has clicked “Save” i.e. they have a manually saved filter for their User.
  • In addition to the manual save/load process above, the screen has been updated to store ‘in-session’ filters for the logged-in User.
    • This works by saving the selected filters against the User whenever a filter is applied e.g. changing a dropdown, clicking ‘Search’, etc.
    • When opening the screen again after previously having selected filters and navigating away e.g. editing a Permit, viewing the Permit Board, etc, the previous filters will automatically be reapplied.
    • The user can then click the “Reset” button to clear the ‘in-session’ filters and see the standard view.
    • ‘In-Session’ filters remain in place until the User logs in again, at which point the filters are cleared and they see the default view.

NOTE: The ‘in-session’ auto-saving has been made an optional setting per User, accessed by clicking the ‘User’ icon at the top-right of the browser window and clicking the “Enable/Disable Search AutoSave” option.

 1.1.2 Isolation Version Changes and Improvements

We have improved the Isolation Version screen to make it clear to the user and also bring it in line with how Permits work in the system.

Admin -> Isolation Version -> Equipment Settings -> Column Edit

  • The existing ‘Workflow Step’ and ‘Lock Afterwards’ functionality has been replaced with ‘Workflow Status’ and ‘Editable’.
    • This should take away the ambiguity of what ‘Lock Afterwards’ actually does as well as making the editability of columns more configurable i.e. a column can be editable at 2 specific Statuses but read-only otherwise.
  • This allows the User to configure whether a Column is Editable (and Required) when the Isolation is currently at the defined Status. For example,
    • Suppose Editable is OFF for “Created” and ON for “Approval Requested”
      • That Column will not be editable until the Isolation reaches the Status “Approval Requested”.
      • In addition, if the Column is flagged as “Required” ON at “Approval Requested”, the Isolation will not progress to the next Status until that Column has been assigned a value.

Admin -> Isolation Version -> Equipment Settings -> List

  • This screen has been updated to accommodate the increased number of possible “Workflow Status” columns by using a unique abbreviation for each Status.
    • If the Version only uses 6 or fewer statutes, the full description will be displayed.
    • If there are more than 6 statuses, the abbreviation will be shown.

TechnipFMC STT Workflow

  • The only difference when this is enabled/disabled is that when enabled, the following Statuses will be listed under the Columns “Workflow Status” and can be assigned as Editable/Required:
    • Sanction To Test Pre-Approve
    • Sanction To Test Complete

NOTE: In the non-TechnipFMC Workflow, completion of STT reverts the Isolation Status to “In Place”, hence why “Sanction To Test Complete” is not used in the standard workflow.

 1.1.3 System Generated Emails (no-reply@pisys.co.uk) Improvements

It’s becoming common for PTW clients to allow their contractors direct access to the PTW system. Emails generated from PTW come from no-reply@pisys.co.uk. This is confusing as often contractors want to query the content of an email but don’t know who to respond to.

We have therefore updated the system generated emails with the following changes:

  • User Company Name included in the banner and footer text i.e. “…on behalf of XYZ”.
  • Contact email(s) added below banner and in footer text:
    • User Name and User Email always included.
    • User’s Company Email is also included but only if the new setting is switched on for “Admin -> Company Edit -> Include Contact in Permit Emails”.

NOTE: Setting “Include Contact in Permit Emails” has been enabled by default for all existing Customers/Companies, but we can switch it off if any Customers raise it as an issue. Please contact support@pisys.co.uk for any changes regarding this item.

 1.1.4 Change all password related emails to include instructions on how to reset your password.

Support has been receiving numerous emails from users who need to set a password after the initial 24-hour period following the receipt of their welcome email. To streamline the process, we have included a note instructing users to visit the login screen and request a new password instead of contacting Support and awaiting resolution.

 1.1.5 Add More View Options to Permit Board

Our Permit Board was updated to closely match how our Plot Plans worked.

We have replaced the single-selection Site dropdown with a multi-select.

If a single Site is selected, the Permit Board will look just as before with details of the Areas/Permits for that Site.

If multiple Sites are selected, the Permit Board will include all Areas/Permits for those Sites.

  • The Area ‘header’ will be updated to include the Site name e.g. “Site 1 – Area 1”.
  • Permit boxes are ordered by Site then Area Descriptions.

The sub-tabs below the Board are currently set up as follows:

  • If a single Site is selected, the tabs will reflect the results, Permit-counts, etc. for that specific Site.
  • However, if multiple Sites are selected, the tabs will reflect the results across ALL Sites i.e. not just the subset of selected Sites.

 1.1.6 PTW/TRMS Sites and Areas Mapping

When we connect our TRMS (Task Risk Assessment) to a PTW instance we have to go through the process of creating a site in PTW, then creating the same site in TRMS to then go back to PTW and map it. The same happens for Areas/Locations between the two systems.

We have now streamlined this process.

Sites

  • New “TRMS Mappings” button added to the “Sites and Areas” list screen in PTW (only available for instances using TRMS).
  • Clicking this opens the “Site Mappings” screen with sections for “PTW” and “TRMS”.
  • PTW Sites – A list of the existing PTW Sites alongside any existing TRMS mappings with columns for:
    • PTW Site (read-only label)
    • TRMS Site
      • Each row will have a dropdown populated with the TRMS Sites.
      • For any PTW Site already mapped, the dropdown will have that TRMS Site selected.
      • NOTES:
        • If the PTW Site is mapped and HAS mapped child Areas/Locations, the dropdown will be read-only (i.e. like the existing dropdown on the Site Edit screen).
        • When a TRMS Site is selected for mapping, both the “Create TRMS Site” and “Create PTW Site” checkboxes are unchecked and made read-only (i.e. cannot map existing and create new at the same time).
        • If the same TRMS Site is selected for mapping against multiple PTW Sites, a “Duplicate” message is displayed upon clicking “Save”.
    • Create TRMS Site
      • Each row will have a checkbox allowing the User to flag existing PTW Sites which are to be replicated in TRMS.
      • NOTES:
        • If the PTW Site is mapped and HAS mapped child Areas/Locations, no checkbox will be provided since the mapping is effectively ‘locked’.
        • If the PTW Site is mapped and HAS NO mapped child Areas/Locations, the checkbox will be read-only (i.e. no need to create a TRMS site since a mapping already exists).
        • If a checkbox is selected against a PTW Site which already has a matching named Site in TRMS, an ‘Existing TRMS Site’ message is displayed upon clicking “Save”.
        • When successfully creating a TRMS Site based on the original PTW one, the Areas for that PTW Site are automatically created as Locations against the TRMS Site and mapped back to the respective PTW Areas.
    • Areas
      • Each row will have a button labelled “Areas” which opens the TRMS Area/Location mappings for the Site.
      • NOTES:
        • Only mapped PTW/TRMS Sites will have a button displayed.
        • The button will display in either Green or Orange:
          • Green – all Areas/Locations fully mapped between PTW/TRMS for the Site.
          • Orange – there are either:
            • PTW Areas not mapped to a TRMS Location.
            • TRMS Locations not mapped to a PTW Area.
  • TRMS Sites – A list of the TRMS Sites which have not been mapped with columns for:
    • TRMS Site (read-only label)
    • PTW Site (read-only label)
    • Create PTW Site
      • Each row will have a checkbox allowing the User to flag existing TRMS Sites which are to be replicated in PTW.
      • NOTES:
        • If the TRMS Site is mapped and HAS mapped child Areas/Locations, no checkbox will be provided since the mapping is effectively ‘locked’.
        • If the TRMS Site is mapped and HAS NO mapped child Areas/Locations, the checkbox will be read-only (i.e. no need to create a PTW site since a mapping already exists).
        • If a checkbox is selected against a TRMS Site which already has a matching named Site in PTW, an ‘Existing PTW Site’ message is displayed upon clicking “Save”.
        • When successfully creating a PTW Site based on the original TRMS one, the Locations for that TRMS Site are automatically created as Areas against the PTW Site and mapped back to the respective TRMS Locations.
    • Areas (button as described under “PTW Sites” above).

Areas

  • The Area Mappings screen is very similar in look and functionality to Site Mappings, with the only real difference being that there is a selectable list of Sites on the left.
  • Sites are colour-coded based on their mapping-status i.e.
    • Green – all Areas/Locations fully mapped between PTW/TRMS for the Site.
    • Orange – there are either:
      • PTW Areas not mapped to a TRMS Location.
      • TRMS Locations not mapped to a PTW Area.
    • Red – either:
      • Site is not mapped to a TRMS Site.
      • Site is mapped to a TRMS Site, but there are no child PTW Areas or TRMS Locations.

 1.1.7 Add a Today button to the Date Picker in PTW

Since the redesign of Contractor Management, we now have to deal with a lot of documents that have expiry dates and start dates etc.

If you set up your company or recipient requirements last year and they are about to expire, you may need to update the date. Currently, the date picker does not offer a quick way to select today’s date; you have to navigate through the year selector, then the month selector, and finally the day selector.

A “Today” button has been added to all date pickers to make the above easier.

 1.1.8 “Add New” button when Work Party is used but Contractor Management is not.

This change was a result of recent changes made to the Contractor and Work Party selection screens.

The Work Party screen has been updated to allow adding of new Recipients i.e.

  • On the Work Party “Add Member” screen, add a button for “Create New Member”.
    • Clicking this will open a new screen allowing input of:
      • First Name
      • Last Name
      • Email
    • Clicking Save on this screen does the following.
      • Creates the Recipient in the DB.
      • Returns to the Work Party “Add Member” screen.
      • “Member” dropdown has the new person pre-selected, displaying their CM Status icon, but not yet added to the Work Party.
    • User will then need to click “Save” to confirm adding them to the Work Party.
      • Having this extra step of not automatically adding to the Work Party means that any Recipient Site checks will be done and need to be satisfied first.

The Work Party screen will also be updated to display the existing list of people selected (i.e. currently only shown under the Permit Edit -> Work Party tab).

Additionally, the Issue & Reissue screens will also be updated with access to the Work Party:

  • If the setting “Use Contractor Management with Permits” is not used, the Recipient “Add New” button continues to function as at present.
  • If CM is used, the “Add New” button is replaced with a button for “Edit Work Party”.
    • Clicking this will open the Work Party “Add Member” screen, displaying the existing Work Party Members and allowing Add/Edit/Create New functionality, exactly as if accessed via Permit Edit.
    • Once the Work Party has been configured as required, clicking “Return” will take the User back to the Issue/Reissue screen and allow selection of the Responsible Person via the list containing the newly defined Work Party.

Also removed the “Cannot Issue Permit without Work Party Members being assigned” check/message when clicking the “Issue” button on Pemit Edit i.e. User can now rectify any missing Work Party problems once they’re in the Issue/Reissue screen.

 1.1.9 Request Approval changes

At the “Request Approval” step of the permit, the permit can be saved without any approver being selected. This results in a status change of the permit with no approver having been notified. We have created the option to make at least one approver mandatory.

If enabled and no Approver is selected, a message will be given to the User.

Bug Fixes

The following is a list of bug fixes that were implemented in Pisys PTW 1.6.4.4 patch release.

  • PTW-1710 – Browser Autofill
  • PTW-1722 – Deleting an Inspection Type redirects to the “Inspection Type Edit” screen
  • PTW-1694 – Cached JavaScript Files Issue
  • PTW-1713 – Emails Being Sent in Disabled Instances
  • PTW-1724 – When validating the Proposed Issued/Expiry CM Dates, the workflow buttons disappear, leaving only the save button
  • PTW-1711 – CM – PTW Reviews List is not showing all Company Reviews
  • PTW-1719 – User approval list for permits did not consider panel type controls.
  • PTW-1716 – Proposed Issued/Expiry CM Dates are validating when a permit is Rejected
  • PTW-1718 – Delete of Inspection Question takes the user back to the Inspection Types screen
  • PTW-1712 – Spot Checks
  • PTW-1715 – Inspections Question Copy when In-Use
  • PTW-1698 – Management Screen Terminologies
  • PTW-1655 – Permit Question Copy Bug
  • PTW-1654 – Alignment Issue for Permit Questions.

The following list of Security Updates was identified and were also fixed in this release:

  • PTW-1726 – Firewall error when exporting.

For an overview of our update process, please click here: https://pisys.co.uk/our-update-process/

Scroll to top