Continuous distribution of PMS documents and other information will be a key part of the PMS Service Request. Think of continuous distribution as a constant update of material. Today, the Surface fleet only receives bulk PMS updates semi-annually due to the administrative burden associated with making changes through the Force Revision process that deletes and re-installs the electronic PMS library aboard ships. The Future of PMS will maintain a continuous distribution of PMS changes automatically updated within the electronic PMS deck through Equipment Maintenance Plans.
While this will greatly reduce or eliminate the administrative burden for Force Revisions, it will also eliminate the need for ACN processes and other paper-based PMS document work-around solutions. If a PSR results in a change to PMS documents, those updated documents will be automatically distributed to all hull/activities using the same systems and equipment. This means, you can expect approved changes to be finalized on the maintenance requirements distributed to your command within days, not months after the changes are authorized. So if it was a monthly PMS check you were working on and you submitted a PSR, there is a good chance you will be working on the revised document the next time that PMS check comes due. How great is that?
By making the PSRs more versatile than the current FBR system, work center supervisors can view any PSR fleet-wide, whether it is opened or closed. Automatic indicators will be available from the scheduling software to highlight issues or concerns from their peers who use and
perform maintenance on the same systems or equipment. If the supervisor sees a common issue they may be able to select a "thumbs up" or a "+1" indicator to add their name and command to the existing PSR and add more information or comments.
In contrast, if the user disagrees with a PSR request, they may select the "thumbs down" or a "-1" indicator to show their disagreement and provide a conflicting viewpoint. In this manner, the Fleet maintenance community will have a greater ability to influence how PMS documents, tools, processes, and policies evolve. This process can only be successful if the information is easy to find and their opinions can be captured in just a few clicks of a mouse, rather than the current practice of making an entirely new (and independent) feedback document.
In order to implement the PMS Service Request in the Future, there are several technical challenges to overcome. The primary obstacle is the ability to continuously send and receive PMS data from the ship. To leap this hurdle, the Future of PMS infrastructure will be designed to work primarily in an off-line mode, with transactions being passed between the ship and the shore as bandwidth is made available.
This approach will allow commands to continue to utilize their maintenance system when the system does not have active communications with shore support infrastructure. Other potential barriers include the limited computer resources at the ship level, shore-based hosting infrastructure shortfalls, and the need for all PMS to be tied to configuration records. As these barriers are overcome, the PMS Service Requests will be implemented to give you a quicker response to all of your feedback and be a key feature in the Future of PMS Project.