PMS 5.0 Release Notes¶
Released 04/02/2021
Key changes:
Works are now referred to as Projects and include both paving and non-paving projects
Projects and Programmes and LA Programmes are both now managed through the new UI
You now need to login when accessing the new UI. You can log in with your existing PMS username and password. If you do not have a user account please contact the RMO
75,000 Works have been migrated to the new Projects schema.
Both user interfaces use the same database and web services, although there are two sets of mapping services. The new WFS/WMS services can be accessed via URLs such as those below, replacing the LA name as necessary.
Introductory Screencasts¶
Introduction to PMS 5.0¶
Works to Projects Migration¶
Mobile App Changes¶
Works Application¶
The existing Works application should no longer be used. A new Works application has been developed to work with Projects. Please contact the RMO for details on how to install the new application.
PSCI Application¶
The application remains unchanged. Surface Surveys can still be carried out, however the materials that can be selected are currently unchanged, so new surface material in PMS 5.0 options are unavailable until the application is updated.
The new PMS 5.0 unavailable materials are:
Slurry Surfacing
Stone Mastic Asphalt
Paving
Asphalt Concrete
The following surface materials are still available in the PSCI application but not available in PMS 5.0 as a surface course material:
SMA - Modified Stone Asphalt
Modular Paving
Microsurfacing - Slurry Seal
Surface Course Asphalt Concrete
High Friction Surfacing
Miscellaneous Updates¶
User Role Changes¶
Please contact the RMO for queries and requests for user role changes.
All LA administrator accounts have been removed
Admins have the new Unlocker Role applied.
MapServer¶
DATE_STRING field removed from the VisualCR (PSCI Visual Condition Ratings) layer
Existing PMS UI Changes¶
Surface Inventory Layer removed (this is available in the new system under Surveys > Surface Surveys)
Server Changes¶
Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows using MicrosoftEasyFix51044.msi