<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Compas Q&A - Crew Management]]></title>
		<link>https://rogde.org/compasqa/</link>
		<description><![CDATA[Compas Q&A - https://rogde.org/compasqa]]></description>
		<pubDate>Thu, 16 Apr 2026 15:16:22 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Future Movements not being deleted automatically]]></title>
			<link>https://rogde.org/compasqa/showthread.php?tid=11</link>
			<pubDate>Thu, 18 Apr 2024 12:09:27 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://rogde.org/compasqa/member.php?action=profile&uid=2">torro</a>]]></dc:creator>
			<guid isPermaLink="false">https://rogde.org/compasqa/showthread.php?tid=11</guid>
			<description><![CDATA[If a CREW is changed to a different vessel during the planning process, the future movement is not deleted automatically.<br />
<ul class="mycode_list"><li>A Planning Movement is created when a crew members' nomination to relieve another crew member, has been approved under Planned changes &gt; Approving Crew - Approved Crew in Planned Changes . A crew member can be approved to join multiple vessels or the same vessel at different times. Each approved nomination will show under planning in ascending date order based on the Change Date. The nomination will have to be cancelled from Planned Changes in order to remove the entry from Planning Movements.<br />
</li>
<li>A crew member can have multiple Future Movements in ascending date order based on start date, and they an be created in two ways:<br />
</li>
</ul>
<ol type="1" class="mycode_list"><li>Via Planned events - once a crew change has been added to a Planned Event a Future Movement is automatically created. The start date of the Future movement will depend on the start date of the Planned Event. The end date will be the due date of the crew member being relieved. The Future movement can be edited, however, editing will not change the  information in Planned Events or Planned Changes.<br />
</li>
<li>From Crew Profile - by selecting the blue Future_events icon you can create a Future Movement directly, the Add future Movement box will open; The start date of the movement will be one day after the due date of current movement or if there is already a Future Movement, one day after the due date of that movement. <br />
<br />
Committing a Future Movement, a new note will open to confirm the movement. Once the OK button is pressed, the Future movement becomes the current movement.   <br />
</li>
</ol>
<br />
Future Movements can be Committed, Edited or Deleted, pending real situation.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">These movements are not automatically deleted. </span>]]></description>
			<content:encoded><![CDATA[If a CREW is changed to a different vessel during the planning process, the future movement is not deleted automatically.<br />
<ul class="mycode_list"><li>A Planning Movement is created when a crew members' nomination to relieve another crew member, has been approved under Planned changes &gt; Approving Crew - Approved Crew in Planned Changes . A crew member can be approved to join multiple vessels or the same vessel at different times. Each approved nomination will show under planning in ascending date order based on the Change Date. The nomination will have to be cancelled from Planned Changes in order to remove the entry from Planning Movements.<br />
</li>
<li>A crew member can have multiple Future Movements in ascending date order based on start date, and they an be created in two ways:<br />
</li>
</ul>
<ol type="1" class="mycode_list"><li>Via Planned events - once a crew change has been added to a Planned Event a Future Movement is automatically created. The start date of the Future movement will depend on the start date of the Planned Event. The end date will be the due date of the crew member being relieved. The Future movement can be edited, however, editing will not change the  information in Planned Events or Planned Changes.<br />
</li>
<li>From Crew Profile - by selecting the blue Future_events icon you can create a Future Movement directly, the Add future Movement box will open; The start date of the movement will be one day after the due date of current movement or if there is already a Future Movement, one day after the due date of that movement. <br />
<br />
Committing a Future Movement, a new note will open to confirm the movement. Once the OK button is pressed, the Future movement becomes the current movement.   <br />
</li>
</ol>
<br />
Future Movements can be Committed, Edited or Deleted, pending real situation.<br />
<br />
<span style="font-weight: bold;" class="mycode_b">These movements are not automatically deleted. </span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Old planning events being left in the movement view]]></title>
			<link>https://rogde.org/compasqa/showthread.php?tid=10</link>
			<pubDate>Mon, 15 Apr 2024 13:48:11 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://rogde.org/compasqa/member.php?action=profile&uid=2">torro</a>]]></dc:creator>
			<guid isPermaLink="false">https://rogde.org/compasqa/showthread.php?tid=10</guid>
			<description><![CDATA[Have experienced old planning events being left in the system, and struggled to find a way to get them away. Solution was to:<ul class="mycode_list"><li>on the crew's page<br />
</li>
<li>select <span style="font-weight: bold;" class="mycode_b">Service</span><br />
</li>
<li>Select <span style="font-weight: bold;" class="mycode_b">Assignments</span><br />
</li>
<li>Delete the unwanted <br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[Have experienced old planning events being left in the system, and struggled to find a way to get them away. Solution was to:<ul class="mycode_list"><li>on the crew's page<br />
</li>
<li>select <span style="font-weight: bold;" class="mycode_b">Service</span><br />
</li>
<li>Select <span style="font-weight: bold;" class="mycode_b">Assignments</span><br />
</li>
<li>Delete the unwanted <br />
</li>
</ul>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Crew Self Service - CSS]]></title>
			<link>https://rogde.org/compasqa/showthread.php?tid=6</link>
			<pubDate>Mon, 05 Feb 2024 12:41:07 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://rogde.org/compasqa/member.php?action=profile&uid=3">VIO</a>]]></dc:creator>
			<guid isPermaLink="false">https://rogde.org/compasqa/showthread.php?tid=6</guid>
			<description><![CDATA[<!-- start: postbit_attachments_attachment -->
<div class="row mb-2">
	<div class="col-auto align-self-center">

<!-- start: attachment_icon -->
<img src="https://rogde.org/compasqa/images/attachtypes/image.png" title="PNG Image" style="height: 16px; width: 16px" border="0" alt=".png" />
<!-- end: attachment_icon -->
		
	</div>
	<div class="col align-self-center">
		<a href="attachment.php?aid=1" target="_blank" title="">Image.png</a> <br />
		<span class="text-muted" style="font-size: 12px">Size: 410.74 KB / Downloads: 3</span>
	</div>
</div>
<!-- end: postbit_attachments_attachment --><br />
Is anyone using Crew Self Service and if yes, do you have any feedback from crew ?<br />
<br />
As we understand, currently it is not an app, it's a browser with an app feeling and OTG is working to make it an app but they cannot say when it will be ready.]]></description>
			<content:encoded><![CDATA[<!-- start: postbit_attachments_attachment -->
<div class="row mb-2">
	<div class="col-auto align-self-center">

<!-- start: attachment_icon -->
<img src="https://rogde.org/compasqa/images/attachtypes/image.png" title="PNG Image" style="height: 16px; width: 16px" border="0" alt=".png" />
<!-- end: attachment_icon -->
		
	</div>
	<div class="col align-self-center">
		<a href="attachment.php?aid=1" target="_blank" title="">Image.png</a> <br />
		<span class="text-muted" style="font-size: 12px">Size: 410.74 KB / Downloads: 3</span>
	</div>
</div>
<!-- end: postbit_attachments_attachment --><br />
Is anyone using Crew Self Service and if yes, do you have any feedback from crew ?<br />
<br />
As we understand, currently it is not an app, it's a browser with an app feeling and OTG is working to make it an app but they cannot say when it will be ready.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Crew lists - onboard module]]></title>
			<link>https://rogde.org/compasqa/showthread.php?tid=5</link>
			<pubDate>Fri, 26 Jan 2024 08:12:39 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://rogde.org/compasqa/member.php?action=profile&uid=2">torro</a>]]></dc:creator>
			<guid isPermaLink="false">https://rogde.org/compasqa/showthread.php?tid=5</guid>
			<description><![CDATA[We have detected an error in crew list onboard module where individuals are duplicated.<br />
Release: 36.6.4<br />
Module: onboard<br />
 <br />
Probable cause: Individuals registered with multiple Next of Kin in Family tab.<br />
 <br />
Additional: <ul class="mycode_list"><li>The crew list appears correct in the office module, indicating that the queries for the two modules are catching data from different fields<br />
</li>
<li>Enforcing single NOK in the system would possibly solve the problem, however in some areas alternative NOK is required<br />
</li>
</ul>
]]></description>
			<content:encoded><![CDATA[We have detected an error in crew list onboard module where individuals are duplicated.<br />
Release: 36.6.4<br />
Module: onboard<br />
 <br />
Probable cause: Individuals registered with multiple Next of Kin in Family tab.<br />
 <br />
Additional: <ul class="mycode_list"><li>The crew list appears correct in the office module, indicating that the queries for the two modules are catching data from different fields<br />
</li>
<li>Enforcing single NOK in the system would possibly solve the problem, however in some areas alternative NOK is required<br />
</li>
</ul>
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Visual Planner Best Practice]]></title>
			<link>https://rogde.org/compasqa/showthread.php?tid=2</link>
			<pubDate>Mon, 15 Jan 2024 16:33:14 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://rogde.org/compasqa/member.php?action=profile&uid=1">admin</a>]]></dc:creator>
			<guid isPermaLink="false">https://rogde.org/compasqa/showthread.php?tid=2</guid>
			<description><![CDATA[There are diff]]></description>
			<content:encoded><![CDATA[There are diff]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Visual Planner Best Practice]]></title>
			<link>https://rogde.org/compasqa/showthread.php?tid=1</link>
			<pubDate>Mon, 15 Jan 2024 16:33:14 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://rogde.org/compasqa/member.php?action=profile&uid=1">admin</a>]]></dc:creator>
			<guid isPermaLink="false">https://rogde.org/compasqa/showthread.php?tid=1</guid>
			<description><![CDATA[There are diff]]></description>
			<content:encoded><![CDATA[There are diff]]></content:encoded>
		</item>
	</channel>
</rss>