Checking if crew have all valid requirements is one of the most important steps.
This article is aimed to look at it as a process rather than set up description.
Set up
Of course, the set up needs to be done first.
Position Requirements set up. Check this article, to find out how it can be done.
Add travel and medical documents as required to organizations properties:
3. Competence replacement set up is done in General Codes
Once the above is completed, the user processes can be implemented around the following possibilities.
Missing requirements crew list view
The view displays persons with their onboard contract information - vessel, department, position, contract dates and the certificates that have expired or missing. The person will be displayed as many times as many requirements are missing.
Pros:
The view is dynamic, meaning it will display updated info every day, based on updates in the system or based on new certificates that got expired.
It is convenient to use and get a good overview. Open a vessel as a current client to receive info on missing requirements for that vessel only. Sort by date to get a sorted list of planned onsigners in the future. Or filter by document name to find all the persons who need certain certificates.
It is possible to export the view using Export Grid in right-click menu, but you will not influence layout much. A piece of advice: hide all columns you do not need in export first, make the sorting, filtering etc and then export it.
You can contact Adonis support if you do not need this view. We really recommend it as a best practice.
Check missing requirements in Rotation
Displaying missing documents in Rotation is based on the Position Requirements set up anyway. So, if we are talking about certificates - then the whole system logic of checking missing certificates is based on Position Requirements set up. For customized reports, standard reports, Rotation, crew list views. Of course customized reports and customized crew list views can be built using any logic. But the best practices Adonis recommends, including the view I shared with you, this is based on the set up in the Position Requirements module.
For all the ways above, when checking upon validity of existing or missing requirements, the following checks are performed:
a) does the person have an onboard activity on certain vessel, holding certain position, on certain date? (checking activities record)
b) if so, is there a requirement for that vessel for that very position? (checking requirements in Requirements module)
c) if so, does the person hold these requirements in his profile? (checking Datagroup > Competence)
d) if so, are these requirements valid within this onboard activity? (checking competence dates, replacing competence)
In case if the crew list view, report, Rotation does not give you an expected result, e.g you do not see a missing requirement, or vice versa, a requirement is displayed as missing while should not be - you can go through the above points and check if corresponding info in Adonis is updated correctly.