You can access the Period Rules through this button:
Note: This function will also be used for crew requests in the future.
Once the rules have been created, the periods can be quickly and easily added in the Periods dialogue.
You can optionally create different period definitions using the filter option. Please check the Period Rules article in the N-OC Web Help.
Field | Description |
| Name | Enter the name of the Period Rule. This is a mandatory field. |
| Period Type | The options are Roster, Request, and Operation. |
| DataType | This is normally set to HumanResources. |
| Filter | Enter HR Filter. |
| Time Mode | The options are UTC, Local, Base, and Station. |
| Sorting | The sort order of the rule if you have several rules with different time modes. |
| Type | The frequency of the rule. The options are Monthly, Rolling, and Halfmonthly. |
| Value | Calendar month= 1 Halfmonthly=15 Rolling= number of days |
| Increment Rolling | Number of days the rolling period will move. |
| Release | This option is no longer available. |
| Time Mode | Options are UTC and Station. Station states in which time mode the periods for Open time and trade settings should be in. Station PHX and SAP start time 12 means that SAP is opened 12:00 PHX time on the SAP start date. |
| SAP (Schedule Adjustment Period) | Start Date: Date in period which SAP is released. Start Time: Time of start date which SAP is released. Duration in hours: From the date and time of Fixed start hours an onward the SAP is open. First come first served and by seniority. Defines which method to process SAP requests. By Seniority will run all requests through an algorithm by seniority then by time of request. First come first served is instant, the first one who request it will get it. |
| Temp Closed Period | Start Day: Date in period where the closed period starts. Start time: Start time of start day. Duration: Duration of the closed period from start day and time. Closing time span before end of period: The actual time span in where pairings / activities may not be altered. Calculated from the end of the period minus the entered timespan. Example Start Day - 7/1 Start time - 12:00 Duration - 168 Closing time span before end of period - 72 Between 7/1 12:00 and 14/1 12:00 (168hrs = 7 days), the three last days in the period (72/24=3), the crewmember cannot alter their schedule by dropping, swapping, pick up, etc. |
| Open Time Closes | Time when crew is no longer allowed to alter schedule. Example If “Activity Calendar Day” is selected in the dropdown:
Date of activity is 22/1 so from 20/1 00:00, the crewmember cannot alter that activity by dropping, swapping, pickup, etc. (22/1 00:00 – 48hrs = 20/1 00:00). But if the crew is allowed to split pairings, it is possible to alter coming activities in the pairing that is not within the closed period. If “Pairing Check In” is selected:
From 20/1 12:05, the crew is not allowed to manipulate anything in the pairing. |
| Trade Closes | How many hours before check in the trade board is closed for the crewmember.
Example Currently “Activity Check In ” the only item in the dropdown:
Trade board closes 09:00 for this activity and no trade can be done after this time. But if the crew is allowed to split pairings, it is possible to alter coming activities in the pairing that is not within the closed period. |
| Aggressive Pickup Period | Period where only a specified group of crew member can pick up a pairing.
Example Activity start 22/1 12:00
Date of activity is 22/1 so the aggressive pickup period for that duty is 19/1 08:00 – 18:00. |
| Archive | This option is no longer available. |
| Active | Activate the rule by clicking the checkbox. |
| Default | Check this box if this is the default rule if a crew doesn't fit into the filter. |
| Automation | This option is no longer available. |