Are You Getting The Permission Artefacts Manually? Really?
DGCA (Director General of Civil Aviation) has defined NPNT i.e. No Permission No Take-off as mandatory compliance for all RPA’s in India. One of the fantastic architectural concepts of NPNT framework is the capability of RPA to take permission in digital format using digital certificate keys. This permission is called as Permission Artefact (PA). Digital certificate is used for securing data between Digital Sky and RPA. The digital certificate is used to sign the data and then encrypt/decrypt the data. This end to end secure communication of data is meant to avoid any kind of man in middle attack. As per NPNT process, each flight requires permission from Digital Sky platform. The permission comes as part of software process, where client software sends request to Digital Sky platform and then gets PA (Permission Artefact) as response from Digital Sky platform after successful exchange of digital keys. There are couple of options available for getting the Permission Artefact from Digital Sky, either manually or automated. Manual Process The detailed process of getting Permission Artefact manually is described here:
- A Pilot must first create a mission plan in GCS.
- Then download the mission plan from GCS software to local drive.
- He must then login to Digital Sky Platform,
- Upload the downloaded mission plan to Digital Sky platform.
- Enter details of aircraft including UIN number on Digital Sky Platform.
- Upload the digital Certificate on Digital Sky Platform
- Then download the Permission Artefact from Digital Sky platform.
- Login to the NPNT software which you have taken from other RFM provider
- Upload the Permission Artefact to the NPNT software.
- Then connect the NPNT Software to the RPA
- Then upload the Permission Artefact to the RPA.
- A pilot must create a mission in the GCS
- The GCS automatically takes care of all the other things as listed in the manual process above.