User Manuals
- Additional Counters User Manual - Running Hours Module
- Additional Incident Information
- All Details on Signing Out a Job
- Certificate Module
- Circulating Components
- Component Form Details
- Connecting and Removing Spare Parts To Components
- Create/Re-create a Forecast
- Details for the Pro forma Invoice Form
- Document Handling User Manual
- Due Jobs in Transit
- Forecast User Manual
- Holding Bay
- How Can a User Assigned an Action Find it and Sign it out
- How Does the Movable Assets Module Work
- How to add a cargo?
- How to add a port to a voyage?
- How to add a port/sailing event (to current voyage)
- How to add a port/sailing event template?
- How to Add Actions to an Observation
- How to Add Additional Suppliers to a Spare Part
- How to Add and Withdraw an Amount of Items to Stock, Directly in the Item Form
- How to add cargo figures?
- How to add Incident consequences
- How to Add Stock Items (spare parts and catalogue items) to a Location?
- How to Add Stock Locations and Sub Locations
- How to approve a voyage?
- How to calculate consumption in the voyage log
- How to Cancel an Observation
- How to change the scale in the timeline view
How Does the Movable Assets Module Work
The Movable Assets module will allow you to move components and spare parts between units. Component relevant information (Jobs, History, Spare parts, Running hours, documents), will be available to the receiving unit, once it has been received onboard. A Transfer document (Pro forma invoice) is used to perform the transfer process and can be printed as part of the physical documentation.
Once a component has been received on a vessel, it will behave as any other component on board, adding its jobs to the vessels due list, and its job history to the vessel’s job history. Changes made to the component in TM Master V2 (Job signed out, changes made to its attributes or spare part list etc.) are as for all other components replicated back to the office system.
The difference with the movable components in regards to system behaviour, is that once the office system receives updates to it, these changes are then also replicated to the other vessels in your fleet (those which are configured to be able to receive the appropriate movable component data). This way, when a movable component is actually transferred between units, all information belonging to the component is already on board the receiving unit, and only needs to be “Activated” in that system. The alternative to this solution is to replicate all the information at the time of the actual transfer. This would result in one big replication file every time the component is moved. This would cause problems for vessels with lower bandwidth.
Depending on your fleet size and diversity, it will not be likely that all vessels will receive all the movable components. (Tanker vessels will not receive Seismic equipment for example). To avoid unnecessary replication to vessels that will never receive the component, you can categorize movable components and decide which units receive which categories. Any updates made to a movable component of one category are only distributed to units designated to receive that category. A Unit can receive none, one or several categories. A component can only be added to one of the categories.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article