000010704 001__ 10704 000010704 005__ 20241024114737.0 000010704 0247_ $$2doi$$a10.24868/10704 000010704 245__ $$aIntegrated Platform Management Systems and Ships staff – How to keep them working together 000010704 269__ $$a2022-08-26 000010704 336__ $$aConference Proceedings 000010704 520__ $$aThe trend in recent years has been to increase the boundary’s in IPMS capabilities making them more and more complicated with more and more Inputs & Outputs (IO) being monitored and controlled. This is all well and good if the system is a really good one, which has been well engineered, well installed, commissioned even better and then maintained to a high level – then the ships staff could be confident that the system is telling them the truth and will do what is asked of it (in regard to Automatic functions) and what they ask of it. If the system is lacking in any way, then trust will be replaced with mistrust and the IPMS will become an expensive liability. This paper will explore the boundary’s of an IPMS system and make reasoned recommendations for how a system should in the opinion of the author be designed, built, tested and maintained. This will include discussing the following aspects: What is the detailed Aim/Purpose of the system – what is the system needed to do, so that we can decide what is essential and what is possibly ‘nice to have’ Inputs and Outputs to be included – more is not necessarily best and how are they to be brought into the system Equipment Selection – Commercial off the Shelf or Bespoke Visualisation software – COTS or Bespoke Control software – how should this be written/created Building and Testing standards Installation standards Commissioning Through Life Maintenance – the aim is to be able to keep the existing system working though the life of the ship with simple upgrades and exchanges. 000010704 542__ $$fCC-BY 000010704 6531_ $$aIntegrated Platform Management System 000010704 6531_ $$aAutomatic Control 000010704 6531_ $$aCommercial off the Shelf 000010704 6531_ $$aSurveillance Control and Data Acquisition 000010704 6531_ $$aEtherNet/IP 000010704 7001_ $$aEdwards, P$$uP and S Automation 000010704 773__ $$tConference Proceedings of iSCSS 000010704 773__ $$jiSCSS 2022 000010704 8564_ $$9dd63ea2e-c024-44a3-b37f-e607a18aea49$$s2204371$$uhttps://library.imarest.org/record/10704/files/10704.pdf 000010704 980__ $$aConference Proceedings