The Photometric function is released in version 2020.3 and rolled out end of 2020. The function consists of or uses the following parts
In-field Photometric measurements is a standard maintenance action that is performed on runways at set times. Since the results of these Photometric measurements often lead to a recitation of certain failed fittings, it is a good method to use the results of the Photometric measurement as a parameter input in the ALIS System.
The current implementation has the ability to import one or multiple FBtechnology measurement exports ( In the FBtech software: File> Export for AirSide ) . It is also possible to create a ALIS custom format in Excel or CSV file that is build with a pre-defined structure to allow import from any in-field Photometric measurement equipment. The function supports the association and storage of Photometric images with the measurement.
The Photometric function is located under Settings → Photometric. If that function is not available on your instance, contact your ALIS support.
Importing Photometric data
The Data files
The files that can be imported can be from FBtech or a ALIS custom format in Excel or CSV - we cover them both here.
An FBTech Photometric run is exported into a folder with multiple images and one CSV file.
The CSV file contains all lights which were tested in that run - below is an example.
19:18;03/09/2020;L-862 4;L-862 5;;;FBT_00_Sp;PACV5;
Header (First Line - transposed):
(local) Time of run
Date of Run
Additional Data 1
Additional Data 2
Additional Data 3
Additional Data 4
Explanation of each data line (transposed):
Percentage of target candela
Color of the light (one side)
Filename with light distribution
You can drag the CSV file and image separate into the Drop-zone of the import page or you can drag the complete folder above into it. You can even drop a folder that contains multiple Photometric measurements into the drop zone.
ALIS Custom format
Spreadsheet (*.xls, *.xlsx, *.csv) with a defined structured.
When creating the ALIS custom format in Excel - upon handling the timestamp, make sure your cell properties are set to "Text" otherwise excel will transform the date to an excel date format which is not a iso-timestamp format!
Column A: Name (Name of run)
Column B: timestamp (ISO-timestamp|millisecondsSince1970)
Column C: Operator
Column D: System
from Column E: additional data
Isodates can be in the following formats
Date and time in UTC
Header Row for measurements - possible headers see below
Order of the headers doesn't count
from third row: measurement data according to the headers from row 2
if not present, the run-timestamp will be used
Latitude in decimal degrees (e.g. 74.47894)
Longitude in decimal degrees (e.g. -81.4781)
(0-100 -... )
Remark: either the "assetName" field or the location fields need to be filled to be able to identify an asset
Contact your ALIS support if you are having issues creating the ALIS custom format.
Here you can download an Example import sheet - Unzip the sheet and modify the details accordingly.
Photometric Measurement task and work order association.
To start importing Photometric data into ALIS, navigate to your Settings→Photometric→ Import Photometric data.
You can Drag & Drop complete folders (advised - works for multiple runs ) or the individual files ( DATA + images) ( only for 1 run) separately into the dropbox.
For every Photometric run dropped in ALIS it will show up in the "Selected for import" section.
Here you can review the imported runs and reference each of them to a maintenance task or corresponding work-order.
This setting will define to which assets in ALIS your measurements will be associated. You have the following options:
Asset identification is done by name first - on none or multiple matches, the location is used
Asset identification is only done by the name
The name in the data-file thus needs to match with the names used in ALIS.
Asset identification is only based on the asset locations
This option can be used of the measurements include the location of the measurement ( Need for GPS module in your in-field Photometric measurement equipment)
ALIS will look at which asset is in the proximity of your measurement location and match the two together.
Asset identification is done by a mapping table (entity mapping)
When you are retrieving data from an external system where your assets are named differently than within ALIS - With a one-time effort the ALIS team can create a mapping table that will translate the names from the external system to the internal ALIS names. This way you prevent to always having to change the names manually for every measurement run. Ask your ALIS support in order to setup a mapping table if this is your preferred method of matching the measurements to the assets.
When the mapping tables are created in the system , you can enter the Internal Entity Name system and Foreign System. (ie: ALIS and FBtech)
When the Photometric runs have been uploaded, maintenance task referenced and matching behaviour set ; ALIS can start analysing the Files.
Hit the "Analyse File" Button to to start the magic! If you wonder if you did something wrong? Don't worry , you can always go back - cancel the import or delete the Photometric run from ALIS .
ALIS will now have a good look at your data and try and match your measurements to the existing assets in ALIS .
You'll get a
Green (Yay! Everything Ok)
Yellow ( Some data missing but it will do! )
Red Summary ( i'm sorry, we can't do this , some things are missing or wrong)
When you have a green or yellow message you can now preview the result before importing it into ALIS. ( Do do so, hit the "Preview" tab next to the "Messages" tab.
Upon the feedback provided you can choose to continue and Execute the import or go back and rework your input.
Example a Yellow - import feedback message -
Gives you a visual overview of you import data. It allows you to get a quick look to what is going to happen into ALIS upon excecuting the import.
You can still go back and rework your import data or cancel the import completely.
ALIS will now register the maintenance performed to the assets involved with the tasks selected.
Well done! The import process is now completed. Go and grab yourself a coffee!
Upon completion you can navigate to the map to then review and create the neccesary work orders where needed on assets that have measurements below the required illumination percentage.
Details of the Photometric measurements per asset
After we have imported Photometric data, we can review the work performed and put the data to good use.
Selecting an asset that has Photometric data will show the Photometric details in it's properties. Have a look at the example below.
The following information or function is shown:
The evolution of the Photometric illumination % ( compared to the standard) of each side over time.
The measuring points are selectable in the graph.
We can toggle between the different measurement runs in the past to see how our assets Photometric has evolved and what the details are
We can re-open the measurement run as whole in a pop to see how the rest of the assets performed in that run.
We can review the individual measurement parameters per side - per run in the table and see how those values compared to the standards as set in the system.
There is a miniature image of the Photometric measurement per side.
The images of the Photometric measurements are selectable - they will enlarge to have a better view on them.
You can choose to ignore a measurement if you know that this measurement was incorrectly taken and would not give the desired end-result.
In the history of the asset there will be a record to show when the Photometric data was imported.
Exercise! Try for yourself if you can find the different functions described above!
Settings on Photometric
Before we can start using our filters to find our faulty lights from the measurement, we need to set the reference illumination onto what we define as faulty or to which level the lights need to be maintained.
Navigate to the Settings- Photometric - Settings
It allows us to set our Aviation Authority which will already help to see which lights are compliant and not.
Next to the Authority default setting you can also set your own maintenance threshold by which you define that lights should be maintained.
eg: ICAO considers a light to be faulty when its illumination is less than 50% but your local airport authority wants to have the illumination to a minimum of 85% .
The percentages set above can then be used in the filters later on.
Have a look at the other default settings that help you to speed up the import proces.
Using Photometric filters to find assets that need to be maintained
Now that we have defined our maintenance level in the Photometric settings , we can now filter out the assets that match certain conditions.
As in the example below - We are filtering out the assets that have a Photometric status that is below 85%. You see in the selected asset details that the Side 1 has <75% and is therefore in the filtered list.
You can now simple take the asset selector on top to select all the assets you want to have maintained and created the necessary workorder.
What about assets that where already maintained but no new Photometric run was done, will this asset be filtered out because of the "old" Photometric data?
We have incorporated a filter that allows you to ignore assets where maintenance was performed after the Photometric measurement! This prevents that maintenance would unnecessarily be performed again on an asset.
There is also a orange warning sign in the Photometric properties if ALIS suspects that you are looking at outdated Photometric data.
Advisories on Photometrics
If Advisories is new to you? Make sure to check out our ALIS - Advisories support page before continuing here.
We have added some Photometric Advisories into the system to give you better awareness of issues around your airfield.
The following rules are implemented and can be chosen to be shown or ignored. Feel free to modify our default settings to what you find fitting for your airport.
There are X% of assets in the same subarea that show sign of insufficient illumination output.
More than X% of your assets have an illumination that is less than X% and have thus failed!
The illumination degradation per day for xx assets is above x.x .
By using the settings button per rule you can modify the parameters for the Rule