Emergency Lock State

In the event of an emergency, you may want to hide the flight and crew to prevent non-authorized users from viewing the flight and it’s details. This is called an Emergency Lock. 

This article shows you how to configure the Emergency Lock State in N-OC.

Navigate to Projects

Projects

We will use the project to tag the flight. 

To create a new Project:

1. Click the NEW button. This will open a new dialogue box to fill out (below).
   
   
   • Name this project Emergency Lock.
   • Set the Shortcode to LOCK.
   • Leave both Cost Centers and Company as blank. We do not have multiples of either in our example airline. Note: If you have multiple Cost Centers and Company contracts, you can select these here. However, if you want to apply the Project to all Companies your airline manages, you can leave this selection blank to apply to all.  
   • Select the Active checkbox.
2. Click the SAVE button to ensure that the Project is committed to the Database and it is ready for use. 

Leg Filter

Let's create a Leg Filter. This will find the legs within the project ‘LOCK’. 

1. Click the NEW button to open a new dialogue.
2. Add a name. In this example, we have used Emergency Lock.
3. Select the dates you would like the filter to be valid from and to.
4. You can choose between Public, Protected, and Private. 
   • Note: We suggest Protected as this Leg Filter cannot be edited by all users.
5. Click the SAVE button.

Adding Qualifiers

Let's add qualifiers, which will assist in locating the flights that are within the project.

1. The filter is set to Project Short Codes (String Array) not equal (!=) to LOCK.
2. Use the "ProjectShortCodes" and set it to "not qual" to "LOCK".
   
   
3. Click the TEST RUN button to ensure the script is working as expected. If so, you can click save and you have successfully created a Leg Filter.

Special Role

Now, create a Special Role for Crew Members. This allows us to lock crew members information in the event of an emergency.

1. Navigate to Special Roles then click the NEW button to enter Special Role information.
   
   
2. In this example, we have entered the name as Emergency Lock and the shortcode as LOCK. We want this to apply to ALL rosters, role types, and equipment qualification so we have left the options as ‘None’.
   
   
3. Set the Special Role to Active and click the SAVE button.

HR Filter

Let's create an HR filter for the Special Role. This is similar to the Leg Filter process. 

1. Navigate to Human Resource Filters.                          
2. Click the NEW button Add a name for the HR Filter. Note: For the example, we have used Emergency Lock.
   
   
3. Select the dates that you would like the filter to be Valid From and To.
   
   
4. Choose between Public, Protected, and Private. Note: We suggest Protected so this HR Filter cannot be edited by all users.
   
   
5. Click the SAVE button.
   
   
   
6. Add qualifiers to assist in locating the flights that are within the project.
   
   
7. Set the filter to Special Role Short Codes and set it to does not equal (!=)  to ".*LOCK".
   
   
8. The .* will do that crew with multiple Special roles will be included in the filter. If you remove the .* only crew with one special role will be found.                                                                              
   
   
9. Click TEST RUN button to ensure the script is working as expected. After, click the SAVE button and you have successfully created an HR Filter.

User Groups

Let's link the project to a usergroup.

1. In this example, we have added the permissions to the NAVBLUE Admin Group. 
   • Note: You can also create a group called View Only if you want to only allow viewing for a specific user group.
     
2. Select ALL on the dropdown list and search for Schedules and Station Operations.
   
3. Set the Filter to Emergency Lock. This displays the LOCK project.
    
4. Additionally, we have done the same for the Human Resource filters, we have selected full permissions for the CrewGantt and HumanResources as well as set both filters to Emergency Lock.  
   
   
5. Click the SAVE button to save your work.

Scenario

In this scenario, we will outline what actions an administrator (or any user in a user group that has permissions) can do during the event of an emergency.                                        

1. Lock the flight data and crew. This hides the flight and the respective data, as well as protect such data from being changed, viewed, or otherwise tampered with.  

   
   

      
2. Navigate to the ScheduleGantt and right-click the affected flight. Select AdHoc Edit.
   
   
3. Select the Project "LOCK". Select Refresh - Next then click Save.
   
   
4. In the tool tip, you can see that the flight belong to the Project "Emergency Lock". 
   • Note: Because you have the rights, you can still see the flight.
     
     
5. In the roster Gantt, you can bring the crew to the top.
   
   
6. Assign the Special role to all the crew. The easiest way is to use the Mass HRdata Inserter.
   
   
   
7. Select the Special role type and the Emergency Lock subtype.                  
   
   
8. Select From Test field, and enter the employee numbers.      
   
   
9. The period should be a large period on both sides of the current date.
   
   
10. If we now log in to the VIEW only group and open the Schedule Gantt, we can't see the flight. In the Crew Gantt, the crew are hidden.