ILIAS Deployed design allows users to synchronize important transactions whenever communications bearers are available.​ The operational requirements and security considerations are at the forefront of the messaging design.​ An utterly scalable set of transactions performed in ILIAS ES can be added to the standard collection as needed.​ The chosen required transactions, limited by a mission and user-based configurations, trigger the generation and transference of an encrypted XML message from the Deployed instance and the Main Operating Base. The communication constraints, limited by operational silence, bandwidth availability, or communications quality, will activate a backlog management system that will resume the transmission once available.​ A straightforward transfer log and status are available to keep track of the transmissions.​ The standard communication messages include the more important and used transactions, including asset readings and operational status.​ The Deployed instances and Main Operating Base communication is bi-directional and includes reception confirmation.​ ​

A2M is connected with the central fleet system where the S1000D documentation from DAMEN is consolidated and is used to feed each A2M with the Bill of material and the related maintenance procedures for all embarked assets.​

In order to build on our configuration and add to the interconnection on the ship we integrate the sensors in our system. This allows us to make the link between asset and sensor. Here we are also able to have direct sensor data and enable management of the sensor information.​

While registering the usage of the assets on the vessel (automatically or manually), asset counters are getting updated. For each preventive maintenance plan received from Manufacturer and pre-loaded in A2M, the system keeps track of the remaining potential of related assets on-board. When due date is approaching or when counter is reaching its limit, A2M activates automatically the next preventive maintenance iteration and work order appears automatically on the maintenance planner board to be scheduled.

For the purpose of simplifying documentation we acknowledge that during a work order there might be new scenarios or activities occurring. Therefore we have made it possible through ILIAS Guide to add a discrepancy to the work order. This is both to enhance documentation but also give a better insight into the activities within a work order. As in the example below the technician is easily adding a discrepancy, describing it and documenting a photo of the issue.

There are a variety of sensors on ship but a lack in seeing combined sensor data for deeper insight to operations. With condition based maintenance we are drawing on a real-time collection of sensor data and visualising it to identify issues before they can interrupt production. Furthermore we are able to combine sensor data input and run predefined algorithms on the data within a 10 sec interval of showing in the visualization. In the below example we are able to simulate engine sensor data, run the algorithm and present it in our visualisation tool immediately. 

Through our visualisation tool we are able to give an overview of the Vessel readiness. The vision is to get an immediate overview of status of all key operational abilities to support various mission capabilities of a ship till operational level of each individual main sub-systems. Which allow the user to assess what exactly the vessel can perform. Furthermore if any abilities are hindered the WO section describes what work orders that needs to be concluded in order to regain the abilities.

Planning should be an easy and manageable task. In our calendar view we provide an overview of work order planning. The chief can see when and who should be working on a work order. Activities within the work order can be assigned automatically or manually to the chosen technician.

The drag and drop function allows the user to add unplanned work orders to the calendar.

The color indicator asseses across our configuration if there is the right resources to perform the work order in that given time period.

There is an automatic connection between the planning and technician. The technician will immediately see the work order in their view and the start to end date.

Here we present the technician view. This is the main view where the technician has an overview of their assigned work orders. This view provides a clear overview of all executable tasks. Here the technician can start, pause, resume or sign off their work orders. The detailed view provides the details from asset information to uploaded manuals or even the personnel working on it.

Furthermore, if there is a reason for pausing a work order the technician can easily document the reason as a part of the steps. This provides detailed insights into the work process on board. 

A2M is based on smart issuing of material on board. When material is required for maintenance, it is automatically reserved in the right warehouse.​ The responsible for the warehouse will prepare requested material and is confirming issue of all prepared material. The right material is ready to be picked by the technician.​ A2M will exchange automatically the stock levels with the shore to enhance situational awareness

With A2M you can activate the automatic requisition (Pull) for each material needed on ship. When the resupply is activated, then A2M takes cares of the resupply to get stock level on the right level on ship. Depending on material priority for the maintenance task, the requisition is inheriting this priority and, when ready, a message is sent to the shore to organize the resupply. Priority is linked to the mission Action will be related to this priority: immediate, next re-supply at sea, next period alongside, or on completion of the mission.