Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

This team will oversee the feasibility regarding the development of the system,

Electronic Personnel Licensing Initiative (EPLI) (aka E-Licensing)

Initiative de Licences électroniques du personnel.

The goal is to replace passport-like aviation credentials with an electronic (QR code) substitute.

Links :

Confluence

Team Members

Team Multipass

DevOps

Azure DevOps Board

Sharepoint

ELECTRONIC PERSONNEL LICENSING INITIATIVE - documentation

Teams Channel

Team Multipass - Daily Standup

Team Calendar

Team Multipass Calendar

#####

Other :

EPL Inbox/Generic EMail
<to be determined>

Sign-in Canada
https://canada-ca.github.io/sign-in-canada_authenti-canada/en/index.html

Miro
https://miro.com/app/board/uXjVPXfe5aw=

ICAO (International Civil Aviation Organization)
https://www.icao.int/Pages/default.aspx

CASA (Civil Aviation Safety Authority - Australia)
https://www.casa.gov.au/
Github - casaux - Overview

DAPLS (Distributed Air Personnel Licensing System)
DAPLS - SDLPA
DAPLS-MPDIS - SDLPA-SDDPM

CAMIS (Civil Aviation Medical Information System)
CAMIS

#####

suggested working agreement only - 2022-11-01 - KM

Working Agreement

  1. Be Respectful: Always be respectful and courteous.

  2. All team members will be available during the core working hours from 0930 - 1445

  3. Keeping Team Calendar Up to date:

    1. Put key dates and milestones on team calendar

    2. Give advance notice (when possible) of leave

    3. Team Calendar can be found here: Team Multipass Calendar

    4. Set your “Out of Office” notification within Outlook.

  4. Daily stand-up will be at 9:30 every morning. If you are unable to make it, notify the team in advance through the MS teams chat (with your updates for the day).

  5. Ask For Help:

    1. Ask for help when you need it and offer help if you see someone struggling.

  6. All important information should be documented in Confluence.

    • e.g. reoccurring blockers , environment setup information

    • any protected material to be linked in Confluence, and stored in Sharepoint

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.