Skip to main content
Skip table of contents

Location List

The Location List in YMS is a fully customizable self-referencing hierarchy that allows each vessel to define the physical Decks, Rooms & Storage Locations onboard in a well structured list. The following best practices will help ensure your Location List is logical, efficient, and easy for all crew to navigate.

Hierarchy Design

  • Use Decks as Root-Level Locations: Begin with the vessel's decks as your top-level locations.
    Example: 00 Tank Deck, 01 Lower Deck, 02 Main Deck, 03 Bridge Deck, 04 Sun Deck

  • Add Rooms/Spaces as Sub-Locations: Under each deck, list all the rooms & compartments as individual sub-locations.
    Example: 01 Lower Deck >> Engine Room

  • Add Storage Units as Lowest-Level Locations: Beneath each room, include specific lockers or containers.
    Example: 01 Lower Deck >> Engine Room >> Stbd Gen Space >> Box D34

  • Use a Numbering System: As with categories, prefix location names to control display order across the application.

  • Unique Names for Storage Boxes: Assign unique identifiers to all movable containers or boxes & print matching labels to be fixed to these containers and boxes.
    Example: Box D34 should retain a unique name even if it is moved to another location.

  • Keep Names Short but Clear
    Use concise labels that still convey meaning. Abbreviate common terms consistently to improve readability and save space.
    Example: Use Stbd instead of Starboard, so it matches the length of Port.


Access Control

  • Restrict Editing Rights: Only YMS Administrators and possibly Heads of Department (HoDs) should have permissions to create or modify locations.


Shoreside Storage

  • Create a Dedicated Root Location: Add a top-level location named Shoreside Storage.

  • Add Sub-Locations by Facility: List each external facility as a sub-location where inventory is stored off-vessel.


Planning and Alignment

  • Use Official Names from Build Documentation: Reference the names of rooms and spaces from the official build documentation and encourage crew to use these names when referring to locations. This promotes consistency and removes ambiguity across the system.

  • Refer to the General Arrangement (GA): Use the GA to identify all decks and systematically add each room and space to ensure all locations exist in YMS.

  • Collaborate with Departments: Confirm all departments' needs are considered in the Location List design.


Final Notes

Implementing a well-structured Location List helps:

  • Improve search and filter accuracy

  • Reduce user confusion

  • Maintain consistent data entry across departments

Planning your Location List methodically ensures that all physical spaces are accounted for and the system remains intuitive for long-term use.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.