How to add the new Position to Requirements Profile

This Position view is commonly used to set up requirements based on a crew member's position.

Step 1: Add Position

Open

1. On the left, you see the position tree with all added positions.
   Stand on the top row, please.

2. The right-side displays a list of existing ranks that are defined as active in the General Codes table.
   Please tag the position(s) you want to set up required documents for and move them to the Positions Selected section using add buttons:
   
   

   Open

   

   move tagged to the Positions Selected section;
   
   

   move all positions to the Positions Selected section.

3. Click Apply and all selected positions will be moved to the Positions tree to begin setup.

Step 2: Define required documents for the position

1. Then you should select a position on the left to which you want to define requirements.

2. The list of all competence documents that are defined in General Codes is displayed in the right part of the screen.
   The Dropdown menu above the list can help you to narrow the list. It displays all the competence views & will result in the display of only those competence that belongs to the selected view.
   Please tag required certificates & add them to a position using add buttons:

   move tagged competencies to the Documents Required section;

   move all docs in the list to the Documents Required section. 
   To return the records use the remove buttons: 

   move tagged competence(s) from the Documents Required section back; 

   move all docs from the Documents Required section back.
   
   

3. Click Apply button to save. 

Now you see these required certificates under position in the tree on the left:

Expand any position to see required documents.

Step 3: Define criteria for document
Now, when you have defined what documents are needed for a certain position(s), you are ready to choose criteria for every requirement.

1. In this screen, it is needed to click on each required document in the left part and select criteria in the right part of the screen.

2. The criteria can be:

   Vessel – proposes the list of vessels defined in your Organization Structure;
   Vessel Type – displays the vessel types (codes defined in General Codes);
   Principal – shows the list of contacts of Principal types;
   Flag (Vessel Flag) – list of countries.
   You can define any criteria you want on one or several tabs.

   Select one or several items and click add button. 

   You can create complex logic for requirements:
   e.g. if you add Vessel Type = Ocean & Flag = France - the current competence will be required only for this position for Ocean vessels under the French flag. Ocean vessels with another flag will not require this competence. 

   Vessel criteria ignores any other criteria. 

   E.g. if vessel Rima Mari is selected - the competence is required for this position only on this vessel despite the flag/vessel type/principal that you set on other tabs.
   
   

3. Click Apply to save your setup.

Once the criteria are set, you need to click Activate Profile button, and the certificate will appear as Requirements for all the positions, that you've set up.

After activation, all required documents will appear in Org. Structure > Position Properties > Requirements for corresponding Position/Vessel per defined criteria:

All changes done in the Profile module after activation will be reflected in Org. Structure.
If earlier, for example, you defined some certificates, and they are not required for a certain position any longer, you do not have to delete it manually position by position here.
You just do not define this certificate for that position in the profile, only correct certificates.
After profile activation, all the 'previous' certificates will be removed from the org requirements list, and only the listed in the profile will appear.
In other words, you need to define the correct list of certificates in the profile module before activating it.

Note: you should not add required competencies directly in Organization settings only in the Requirements Profile module.