gcaa atc srs - general civil aviation authority epublicaton documents... · web viewsql server:...

GCAA eServices Part II Development

ANS eServices

Software Requirements and Specifications Document (SRS)

VERSION: 1.0 REVISION DATE: September 24th, 2008

Approval of the software requirements specifications document (SRS) indicates an understanding of the purpose and content described in this document. By signing this document, each individual agrees work should be initiated on this project and necessary resources should be committed as described herein.

Approver Name Department, Title Signature DateMr. Stanly Facey CNS , Inspector Mr. Michael Hays Aerodrome InspectorMr. Mohammed Al Shehhi I.T. , I.T. Manager M. Khurram Majed I.T. , Project Manager

Customer General Civil Aviation (GCAA) - Abu Dhabi, UAEDate 9th September 2008 Version 1.0Reference Number SRS080921_GCAA_PartII_CATv1.0

Role Name Date

Prepared by Mr.Mahdi Al Bourini , Mr.Mohammed Sbeeh 26th -Aug-08

Reviewed by Mr.Jamal Al Jeetawy 16th –Sep - 08

Authorized by Mr. Rami Abu Hayah 18th –Sep - 08

DETAILS OF BUSINESS CONTACT

Name & Designation Phone Fax EmailRami Abu Hayah 02 / 6262092 02/ 6262763 [email protected]

REVISION HISTORY

Revision Date Remarks / Changes

0.8 14- Sep-08 Initial version- Draft

0.9 17-Sep-08 Clarifications to be Addressed

1.0 BETA 18-Sep-08 Reviewed

1.0 25th –Sep-08 First Release

[Project Name]Project Charter [Version Number] | [Publication Date] ii

mailto:[email protected]

Document Details: System Requirements Specifications SRS

Project : GCAA eServices Part II

Client Name: General Civil Aviation Authority (GCAA)

Ref No.: SRS080811_GCAA_PartII_CAT

SRS Updates Log No.: 1.0

Table of Contents

1. Introduction..................................................................................................................51.1 Purpose................................................................................................................51.2 Intended audience................................................................................................51.3 Product Acronym Definitions (TBD)..................................................................61.4 Product Scope......................................................................................................6

2 Overall description.......................................................................................................72.1 Product Dependencies.........................................................................................72.2 Product Help Module...........................................................................................72.3 Product Error Handling........................................................................................82.4 Training & Documentation..................................................................................92.5 Performance Constraints......................................................................................92.6 Design Constraints...............................................................................................92.7 Product Perspective...........................................................................................102.8 System Environment..........................................................................................122.9 Hardware Interfaces...........................................................................................142.10 Software Interfaces............................................................................................142.11 Communication Interfaces.................................................................................14

3 ANS eServices Functional requirements...................................................................163.1 Users Authentication.........................................................................................16

3.1.1 Process to grant UNIT Administrator Credentials.....................................163.1.2 Process to Grant Credentials to Unit’s User..............................................21

3.2 Frequency Spectrum Approval Form (Letter of No Objection):.......................253.2.1 Overview:..................................................................................................263.2.2 The applicant registration:.........................................................................263.2.3 The applicant process:...............................................................................303.2.4 The business process workflow:................................................................333.2.5 Frequency Spectrum approval workflow and business process (Letter of no Objection):............................................................................................................42

3.3 Harmful Interference Report:............................................................................433.3.1 Overview:..................................................................................................433.3.2 The unit’s user process:.............................................................................433.3.3 The business process workflow:................................................................463.3.4 the Figure blow illustrates the work flow of the Harmful Interference Report (HIR) process workflow:...............................................................................54

3.4 Equipment Registration Form............................................................................56

of 141






3.4.1 Overview:..................................................................................................563.4.2 The unit’s user process:.............................................................................563.4.3 The business process workflow:................................................................62

3.5 Depositing Equipment Outage Report:..............................................................713.5.1 Overview:..................................................................................................713.5.2 The unit’s user process:.............................................................................713.5.3 The business process workflow:................................................................75

3.6 24 Bit Aircraft ID:.............................................................................................843.6.1 Overview:..................................................................................................843.6.2 The unit’s user process:.............................................................................843.6.3 The business process workflow:................................................................88

3.7 SAC/ SIC Code Allocation Process and workflow...........................................973.7.1 Overview:..................................................................................................973.7.2 The unit’s user process:.............................................................................973.7.3 The business process workflow:..............................................................1013.7.4 the Figure blow illustrates the work flow of the SAC/SIC process workflow:.................................................................................................................109

3.8 Aerodrome Licensing Forms:..........................................................................1103.8.1 Overview:................................................................................................1103.8.2 The unit’s user 1st process:.......................................................................1103.8.3 The unit’s user 2nd process:......................................................................1153.8.4 The requests business process workflow:................................................1193.8.1 The applications business process workflow:..........................................1273.8.2 Aerodrome Licensing Registration workflow and business process:......137

4 Non-functional Requirements..................................................................................1384.1 Performance Requirements..............................................................................1384.2 Security Requirements.....................................................................................139

5 Technical Assumptions............................................................................................139

of 141






1. Introduction

The software requirement specification (SRS) document consists of the product perspective, product functions and functional requirements of the application.

1.1 Purpose

The purpose of this document is to present a detailed description of the general civil aviation (henceforth referred by its acronym, GCAA) Communication and navigation surveillance (CNS) electronic services portal. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the stakeholders and the developers of the system and will be proposed to the GCAA for its approval.

1.2 Intended audience

This document should be read by the following persons and agreed upon:Name DesignationMr. Stanly Facey GCAA – ANS Aerodrome InspectorMr. Michael Hays GCAA – ANS Inspector .Mr. Mohammed Al Shehhi GCAA – IT. ManagerM. Khurram Majed GCAA – IT. eServices Project ManagerRami Abu Hayah Cubic Art - Development Team Business lead Jamal Ibrahim Cubic Art - Development Team Project Manager

of 141






1.3 Product Acronym Definitions (TBD)CNS License RatingsAcronym DefinitionADC Aerodrome Control RatingGMC Ground Movement Control RatingAPP Approach Procedural Control RatingAPP (R) Approach Radar Control RatingArea Area Radar Control RatingTBD To be Determind by the systeme user

1.4 Product Scope

The ANS eservices will consist of the following main modules Frequency spectrum approval Harmful interference report Equipment registration form Depositing equipment outage report form and workflow 24 bit aircraft ID SAC/SIC Codes Aerodrome Licensing forms and workflow

of 141






2 Overall description

This section presents a high-level overview of the product being specified and the environment in which it will be used, the anticipated users of the product, and the known constraints, assumptions, and dependencies.

2.1 Product DependenciesThe system depends on the availability of the following services, software and hardware.

1) Active directory: user authentication module dependency.2) SQL server: database management system as entire system dependency.3) SMS gateway: SMS notification system.4) Exchange server: mail notification system.5) Jupiter’s: document management system.6) Ultimus: extended workflow management system.7) E-Payment gateway: financial payment module.8) Network infrastructure: system dependency.9) Internet connection: external users module.

2.2 Product Help Module

The user and system administration level help will be presented as a set of HTML documents and as printed manuals.

Help indexes will be linked to each page of system.

The HTML files will be readable by internet explorer, Netscape, and most other web browsers.

of 141






2.3 Product Error Handling

Errors which the system may encounter can be classified into the following three types:

1. Fatal environment errora) System error -- e.g. no memory, no processes.b) Unable to read a system source file.c) Unable to open the specified display.d) Insufficient disk space available.

Action 1.This type of error will be handled by terminating the system and, if possible, informing the user of the nature of the error that occurred.

2. Non fatala) An animation sequence requires more memory than is available.

Action 1.Error messages will be outputted to a log file or the user will be notified.

3. User input errorsa) The user attempts to upload an existing but invalid data file.b) Attempt to open non-existent file, or a file to which the user does not

have sufficient access permissions.c) Invalid input eg. out of range in numerical field

Action 1.Inform the user of the error via a textual status widget, and allow the user to correct the error.Action 2.Pop up a dialogue box detailing the error and wait for the user to acknowledge the message before continuing. Either the user's request will be ignored, or the user will be given the opportunity to try an alternate command.

of 141






2.4 Training & DocumentationTraining One of our success factors for this project is for GCAA staff to be able to adopt and use the system effectively and in a short time. Accordingly, development team will provide the following training sessions:Functional Training: This training is geared for the users of the system; it will take the users through interactive sessions on how to effectively use the systems sessions will be conducted for one day.Technical Training: This training is geared for the technical administrators of the system, it will cover administrative functionalities and technical details of the farm configuration only and there will not be any development/code training.

Documentation Software Technical Specification document for ANS service will be handed over with the source code.Administration manual will be provided along with training user Manual with related snapshots and flowcharts need to be provided.Dataflow Diagrams (DFD’s) will be prepared with all procedures.

2.5 Performance Constraints

The system must respond to all commands within 5 seconds on a for a normal A4 content page with a load average less than 5 seconds on 256 kbps connection.

2.6 Design Constraints

1. Given that the system is event driven, the design for the system must conform to an event-driven model. The design is also constrained by the choice of implementation language.

of 141






2.7 Product PerspectiveThe GCAA ANS eservices is part of a larger system being developed by Cubic Art for GCAA. The whole system includes internet and extranet sub-systems which come together to form one whole. GCAA requirement was to evolve the existing environment into an integrated platform which addresses all their business needs such as collaboration, communication and services. It required a web-enabled solution that addresses virtually all aspects of customers/ operators communication in an elegant, simple and highly effective way.

Cubic Art Technologies proposed a complete integrated solution that helps and assists GCAA to leverage their business processes and reflecting the image of the new environment for GCAA.

Cubic Art Technologies’ proposal was equipped with Microsoft latest technologies on building the web portal or public-facing web site and the eservices sub sites which will be connected directly to the Internet and will have both GCAA customer side interface and interaction, and internal workflow automation for GCAA staff members. The subject of this SRS is the ANS eservices, however to understand this eservices in its perspective it is important to look at the entire system in its entirety. The solution proposed is presented diagrammatically here:

of 141






Figure 1: Solution Architecture

This system will be developed and implemented using the Microsoft Office SharePoint Server 2007 (MOSS 2007) and .Net Technology. As a part (sub System) of the GCAA online e-services, this section of the document is concerned with interrelation of this system with other sub systems in GCAA e-services, the following diagram shows a high level illustration, of the interrelations between ANS system and the GCAA e-services

of 141






Figure 2: Block Perspective Diagram of Interrelations of ANS & eServices

The Relations between the ANS and Other Modules of GCAA eServices can Be Defined as follows (TBD)

No. Description Input Usage Output

2.8 System Environment

The following diagram illustrates the SharePoint system environment. Please note that it is of illustrative purpose only, as the number of servers to be used may change.There are two major components of the system.

a) Client System - All users that connect to the web site are clients. This includes end users, administrators and content authors. They connect to

of 141






the system through a software interface (most commonly a web browser through HTTP) and receive data back from the server in the form of pages.

b) Server System – This where the web site is hosted. All the processing related to the system happens here. The server is configured as web server and accepts requests from clients and sends back data (HTML Pages). It also stores data in the database server.

Figure 3: System Environment

of 141






2.9 Hardware InterfacesFrom figure 1, the architecture diagram, the hardware interfaces of the system can be deduced. The system will use the database and the file system to store data and information.External interfaces of the system include active directory, e-services, the etisalat e-payment gateway and the e-jobs system.Active directory will be configured locally. The profiles will be imported locally into SharePoint. The latter three interfaces will be implemented using web services.The basic Web services platform is XML + HTTP.The HTTP protocol is the most used Internet protocol.XML provides a language which can be used between different platforms and programming languages and still express complex messages and functions.Web services platform elements

SOAP (Simple object access protocol)

UDDI (Universal description, discovery and integration)

WSDL (Web services description language)

2.10 Software InterfacesFrom figure 6, the architecture diagram, the software interfaces of the system can be deduced. The most commonly used software interface will be the web browser (indicated as internet explorer in the diagram, but could be any supported browser). All types of user classes will be able to communicate through this software interface. The other software interfaces will mostly be used by site administrators and site authors. These include Microsoft Office, Windows Explorer and SharePoint Designer.

2.11 Communication InterfacesMicrosoft has released protocol documentation for SharePoint recently. The entire list of communication protocols used by SharePoint to communicate with internal and external systems is too large and involved and beyond the scope of the SRS. The protocols are divided into Front-End protocols (SharePoint internal communication) and Back-End protocols (talking to SQL Server, Exchange, etc). Excel services calls, active directory communication and office/outlook protocols are also included.

of 141






The web portal will use a small subset of this extensive communication protocol library. Some of the major protocols the system will use have been mentioned in Figure 2. They are:

a) HTTP Protocol – used by web browsers.b) SOAP – use of this protocol will be limited. SOAP is a simple XML based protocol

to let applications exchange information over HTTP. SOAP is a protocol for accessing a web service. The e-services will use this protocol for back-and-forth communication.

c) FP RPC, WebDAV and FTP – certain features of Microsoft Office use these protocols to implement certain features. For instance, office SharePoint Designer 2007 can publish through the HTTP protocol to web servers running SharePoint, and publish through FTP, WebDAV, or the file system to any web server supporting those protocols

of 141






3 ANS eServices Functional requirements

3.1 Users AuthenticationTo access the ANS eServices the system users (Mentioned below) must have login credentials the following section describes the process of obtaining credentials (user name & password) to login to the system

The users will have deferent privileges based on their roles. The system has 3 main roles as described in user’s roles table below

User Type Role DescriptionUNIT Administrators Mange the Units Users Add, Edit , Grant Privileges

to ANS UNITUSERSUNIT Users Business process users Submit and Modify

ApplicationsGCAA ANS Department Staff

GCAA Business Process Approvers and/or Inspectors

Review , Approve and /or Deny the Application

Table 1: Users Roles and Description

3.1.1 Process to grant UNIT Administrator CredentialsThe system will provide the UNIT administrator with a “User Management Panel” to

manage their UNIT User. The UNIT Administrator will have the privileges to add, modify UNIT user profiles.

To obtain these privileges the UNIT Administrator will have to complete the following steps:

UNIT Administrator Registration Process (Front End) 1) Navigate to GCAA, ANS eServices web site and click Request to Register UNIT

Administrator2) Fill in the online request form for UNIT Administrator. The form will have the

following fields:

Field Name Type Required NotesUnit Code Drop Down Yes The ANS, ANS admin will have the

of 141






List : default values are: OMAAOMAEOMALOMDBOMFJOMRKOMSJ

option to Add/ Modify the units code

Unit’s Admin Name

Text Field YesFamily Name, First Name and Other names

Phone Alphanumeric Field

No

Fax Alphanumeric Field

No

Mobile Alphanumeric Field

Yes To be used in any SMS notification

Admin e-Mail Text field Yes The e-mail must comply with the following

i. Must contain only one “@” signii. Must contain at least one dot

“.”iii. Must contain one of the

Internet site prefixes (.com,.net.gov.ae, etc)

iv. Must have at least one character to the left of the @ sign

Must not contain any of the mathematical signs (+, -, *, etc...)

Confirm e-Mail address

Text field Yes this field must be verified to be Identical to the generic e-mail address described above

Generic Unit e-Mail address

Text field Yes A generic unit e-mail address is an e-mail address that is shared between all unit administrator users, any communication and/or notifications

of 141






between ANS and the unit will be directed to this e-mail. The e-mail must comply with the followingv. Must contain only one “@” sign

vi. Must contain at least one dot “.”

vii. Must contain one of the Internet site prefixes (.com,.net.gov.ae, etc)

viii. Must have at least one character to the left of the @ sign

ix. Must not contain any of the mathematical signs (+, -, *, etc...)

Confirm Generic e-Mail address

Text field Yes this field must be verified to be Identical to the generic e-mail address described above

Login Name Text field Yes This is unique name used by the Unit’s user to login.

Password Password text field

Yes Password must comply with the following

i. Minimum length of password is 8 characters

ii. Password must contain at least one special character

iii. A Password must contain Capital and small (Mixed) letters

iv. A password must contain at least one numeric character

v. Must not contain or be identical to the user name

The system will indicate the strength of the entered password based on compliance with the above mentioned criteria’s

Human Text field Yes The system will generate an image

of 141






Verification Image Field

containing characters understandable only by the humans, this field is for security reasons to prevent automated attacks.

Upload Proof Documents

File Uploaded No (TBD) The user can upload 0-n documents to support their application.

Table 2: Unit Admin Registration Request Form

3) After filling the above detailed form, the unit’s admin will have the option, to submit or cancel the form.

4) If the unit’s admin decides to cancel the operation, the system will delete any values that were stored and redirect the unit’s admin to the ANS eServices home page.

5) If the unit’s admin click on submit a summery page displaying all the information entered by the unit’s admin, the unit’s admin will have 2 options:

a. Confirm: If the unit’s admin confirm the form, a notification will be sent telling that their request has been forwarded to the concerned ANS department staff.

b. Back: by clicking on back button the registration page will appear containing all the form fields (editable) with the entered information inserted by the unit’s admin, allowing the unit’s admin to change any field and submit it again or just cancel the form.

UNIT Administrator Registration Process (GCAA ANS Staff End)To approve/reject a new request for a UNIT administrator the ANS staff will have to complete the following steps:

1) Navigate to the ANS eServices admin login page on the GCAA ANS eServices web site

2) Enter user name and password 3) The ANS department staff (based on their privileges) will have a link of “UNIT

Administrators control panel [1]” where [1] Indicates the presences of a new application

of 141






4) By clicking on the “UNIT Administrators applications [1]” the system will display the following list in FIFO order (oldest request on top)

Unit Application Type

Date Submitted

Status Action

User Name New Admin Request

Date of Form submission

Pending View

Table 3: Units Administrator Access Applications List

Where the columns are as followsa) Unit: will display the user name entered by the user in the applicationb) Application type: may have one of two values:

1) New admin request 2) Modify admin info request

c) Date submitted : the date of the form submission d) Action : view

If the ANS inspector clicks on the action (View) the application will be displayed with all the fields set to read only and the attached documents list containing the following

1) Document description2) Documents file type (Jpg, PDF, etc…)3) “View attachment option”

If the user clicks on view attached document, a document viewer (for images and PDF/A only, otherwise the document will be downloaded) showing the actual document will be displayed The ANS inspector will have two options

1) Comments : multi line text area where the ANS staff member can enter text comments

2) Approve the request: In this case the user name and password are stored into the system and a notification e-Mail will be sent to the UNIT Administrator e-Mail with the credentials (user name and password) and the instruction on how to login to the system.

3) Deny the request: In this case the system will save the application in the “rejected applications list” and send a notification e-Mail to the UNIT Administrator e-Mail with the rejection and any comments added by the ATS# unit staff

of 141






3.1.2 Process to Grant Credentials to Unit’s UserThis section is concerned in the process of granting access privileges and credentials (user name and password) to the UNIT User:It is assumed that the UNIT Administrator has already obtained credentials as described aboveThe UNIT Administrator will have to complete the following steps to grant the ANS unit user access to the ANS eServices

1. Navigate to the GCAA web site using any common web browser (preferably IE7 or later).

2. on the web site home page the unit’s user will find the login section (username & password)

3. After successful login the system will redirect the unit’s user to the ANS admin panel home page

4. The ANS inspector panel will have the options and attributesa) List of registered users this list will contain the following fields

I. User name : The unit’s user login credentials user nameII. Last logged In : The date The unit’s user last logged in to the system

III. Status: this Item will have one of two values i. Active: the user can log in to the systemii. Suspended: this user have no access to the system.

IV. Add user : To add a new unit’s userV. New user info panel, This panel will contain the following fields

Field Name Type Required NotesUnit user full name Text Field Yes Family Name, First Name and Other

names.Login Name Text Field Yes The ANS UNIT user will have the

option to check for the availability of the user name (unique username)

Mobile Alphanumeric Field

Yes To be used in any SMS notification

e-Mail address Text field Yes The e-Mail must comply with the following

i. Must contain only one “@” signii. Must contain at least one dot

“.”iii. Must contain one of the

of 141






Internet site prefixes (.com,.net.gov.ae, etc)

iv. Must have at least one character to the left of the @ sign

v. Must not contain any of the mathematical signs (+, -, *, etc..)

Password Password text field

Yes Password must comply with the following

vi. Minimum length of password is 8 characters

vii. Password Must contain at least one special character

viii. A password must contain capital and small (Mixed) letters

ix. A password must contain at least one numeric character

x. Must not contain or be identical to the user name

The system will indicate the strength of the entered password based on compliance with the above mentioned criteria’s

Privileges Tree View Yes The unit’s admin must select at least one of the e-services provided by the ANS eServices System , All ANS e-services will be listed in the tree view

Table 4 Unit’s User Registration Panel

5. After The unit’s admin enters all the required data and clicks save the user profile is created and an e-Mail notification is sent to the user containing the user credentials (user name & password) and how to login to the system.

6. The figure below illustrates the unit admin control panel

of 141






Figure 4: UNIT’s Administrators User Management Panel

of 141






7. The following flow chart illustrates the unit’s user authentication process

Figure 5: the flow chart of unit’s user authentication

of 141






3.2 Frequency Spectrum Approval Form (Letter of No Objection):

of 141






The system will provide the following features and functionalities:

3.2.1 Overview:This section will discuss in details the attributes, functionalities and workflow concerned with the automation of the spectrum approval request process

3.2.2 The applicant registration:

- This process will be available for the public (Government, Private Sector, Individuals) here in-after referred to as the applicants.

- The applicant can explore the GCAA website and create profile by registering their information and get confirmation email with the username and password.

- The registration process for the public users will not move on approval cycle, any user can do the registration and once he/she fills the form and pays the required fees (if any) through the online payment gateway.

As part of the profile management module, the following sections will be included:

Create/Update user profile: The system will provide the user with the needed pages to register in the system. It is assumed that the registration form will consist of fields mentioned below in Table 1.

Change password: A page that will enable to user to change his/her password.

Forgot Password: A page that will enable the user to provide his email address in order for the system to send him/her the password.

Login: A page that the user will use to login to the system.

The current registration process (e-subscription) will be replaced with the new developed profile management module and the current user profiles will be migrated to the new system, GCAA will be responsible to provide all the required documents and access to information in the current system including the database and any other related module.

of 141






A list of eServices is maintained on the web site. Then users are added to each list upon registration. The following table gives the details of the metadata that will be associated with each eService and Registered User:

E-ServiceColumn Name

Column Type Description Required (Yes/No)

Additional Settings

Name Single Line of Text

Title of the E-Service

Yes Use Defaults

Description Multiple Lines of Text

Description of the E-Service

No Use Defaults

Registered UserColumn Name Column Type Description Required

(Yes/No)Additional Settings

Name of subscriber

Single Line of Text

Name of the subscriber

Yes Use Defaults

Title Single Line of Text

Subscriber designation

Yes Use Defaults

Organization Single Line of Text

Name of the organization

Yes Use Defaults

Address Multiple Line of Text

Subscriber street address

Yes Use Defaults

P.O.Box Numerical text field

Post office box number

Yes Use Defaults

Mobile Numerical text field

To be used for SMS

notifications

Yes Use Defaults

Email Address Single Line of Text

Email Address of the

Registered User

Yes Use Defaults

Telephone Numerical text field

Business Telephone

number include

country & area

Yes Use Defaults

of 141






codeFax Numerical text

field Business Fax

number include

country & area code

Yes Use Defaults

Password Single Line of Text

Password of the Registered

UserHuman Verification Image Field

Text field The system will generate an image containing characters understandable only by the humans, this field is for security reasons to prevent automated attacks.

Yes Human Verification Image Field

eService Lookup (information already on this site)

eService the user is

Registered to

Yes Use Defaults

Active Yes/No (Checkbox)

Weather the user should be

active

No Use Defaults

Date of registration

Date/time field The date and time of

registration

Auto filled (User cannot modify)

Format: DD/MM/YYYY

Method of payment

Drop down list Method of payment

values are: Cash, Cheque,

Yes

of 141






Bank Draft, Wire Transfer

and credit card Total Amount Nomadic# text

fieldTo display the total amount

of the selected services fees

Auto calculated (User cannot modify)

Table(1): The applicant registration form

Note: the Registration module subject to restriction based on different sections of the website and e-Services, after the requirements gathering phase a single user management specification document will be submitted in coordination with EMITAC for approval.

- The applicant will have the ability to register applications online via GCAA website; the applicant will be responsible to make sure that all the documents provided are valid.

Note: types and usage of documents will be discussed later in this document.

Login Screen:

- The applicant will login to the system with the login name & password.- After authentication of the applicant and successful login the applicant will have the following e-services available from ANS e-processing:

Service Name DescriptionInitial registration To add new applicationUpdate or review pending approval To update the application data and/or

view the status of the application, view the comments and notes added by the ANS inspector. Update or review pending approvals. (Application which was submitted but in process or pending state only).

of 141






Table(2): ANS Frequency Spectrum Approval Form

3.2.3 The applicant process:

- After a successful login the e-services home page will appear and by clicking on the “Frequency Spectrum Approval” link the “Frequency Spectrum Approval” e-service page will appear.

- The Applicant may view the pre-requisites information page (the pre-requisites entered and modified by the ANS inspector through the control panel, also it can be downloaded as PDF/A file) to this e-service then clicks on “Next” button to view the form.

- The Applicant can apply for the “letter of no objection” application (Frequency Spectrum Approval form) online by filling the following fields:

Application Fields:Column Name

Column Type

Description Required (Yes/No)

Additional Settings

Application Date

date/time field

the time of submitting the form


Format: DD/MM/YYYY

Application ID

Alphanumeric

every application submitted will assigned an ID


Format:(The ID format required from GCAA)

Attach documents

Attachment fieldsCheck table(4)

To attach multi documents No Check table(4)

Notes & comments

Multiline text box

to add any notes or comments

No

Other fields --- (other fields required from GCAA)

Table(3): Frequency Spectrum Approval Form Fields

of 141






Files Attachment Fields:Column Name

Column Type


Additional Settings

Attachment path

Disabled text box field

To insert the path after choosing the file.


Browse Button to select file YesUpload Button Only if the Attach path

contain a real file type. Otherwise shoot a warning message

Yes

Add More files

Link To add another file attachment s fields, for attaching another file

No

Table(4): Attach document fields

- After submitting the form, a confirmation page will appear displaying (only) all the data filled by the applicant, to review them and to make sure that all the data entered is all right.

- The confirmation page contains 2 buttons:

a) Confirm button: to confirm the entered data and submit it complete the process.

b) Beck# button: to go back to the previous page with all the fields that contains the data entered by the unit’s admin to modify it and submit it or to cancel the application.

- The application will be listed in a pending applications queue with FIFO order (oldest request on top) as follows:

Applicant Application Type

Date Submitted

Status Action

User Name New Request Date of Form submission

Pending View

of 141






Table(5): The application list- The applicant may view and follow up with the submitted application by visiting the “Frequency Spectrum Approval” e-service page and check the application queue, each record of the list contain the application with the status, which can be as follows:

a. Pending: not been viewed yet.

b. In-process: it’s under reviewing by the ANS inspector.

c. Partially rejected (more information required): for missing or required documents or information, the application will not processed until it’s resubmitted by the applicant with filling the required documents or information.

When the applicant opens the application details page the information entered and the attached documents fields will be in the edit mode so the applicant is allowed to update any or all of the fields with the new information and upload documents as needed depending on the ANS inspector notes and documents, the old information and documents will be saved for future reference.

A notification email (the notification template text for partially reject can be inserted and updated from the ANS inspector control panel) will be sent to the applicant email telling that the application must be updated with information or documents required as mentioned in the pre-requisites with the notes written by the ANS inspector and the application will be sent back to the queue.

The application status will turn into “information required”.

d. Rejected: this status for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, the applicant may only view the reason (with notes and documents) of rejection and if the applicant get new information or documents to support the case, a new application must be submitted, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the applicant email.

of 141






The application status will turn into “rejected”.

e. Accepted: a certificate will be generated by the system this is after the process is electronically signed and approved by the ANS inspector and the higher management, the applicant can print the PDF/A certificate file after download it, which will be available at application details page, also a notification (the notification template text for approval can be inserted and updated from the ANS inspector control panel) of approval will be emailed to the applicant email and TRA email (note that the ANS inspector can add as many cc emails with notes and attach documents to be sent as required).

The certificate format will be as following:(The certificate template required from GCAA) (TBD)

The application status will turn into “Approved”.

- If there is any update on the application the “Frequency Spectrum Approval” link on the e-services home page will turn into bold until it’s been viewed by the applicant.

3.2.4 The business process workflow:

- Each ANS inspector have an access (with username and password) to the ANS inspector control panel on the GCAA e-services admin panel, after logging in to the ANS inspector e-services control panel a list of e-services will appears depending on the privileges assigned to the ANS inspector.

- In the ANS inspector e-services home page a “Frequency Spectrum Approval” link will be available, it will turn into bold indicating that there is new or updated application.

- By clicking on the “Frequency Spectrum Approval” link a list of available pending application will be shown, also the ANS inspector can navigate

of 141






the in-process, approved, partially rejected or rejected applications by clicking on the tab named as the status name.

- The applications listed in a queue with FIFO order (oldest request on top) as follows:


Submitted Date

Status Coordinator Assigned to

Action

Full Name

New Request


Pending None None View

Table(5): The application list

- Also searching tools (simple and advance search) will be available to allow the search within the applications.

- The moment the ANS inspector opens an application, the status of that application will be changed to “in-process”.

- Application details page: when the ANS inspector opens the application details page, the following details will appear:

i. Application ID: display text field containing the application ID.

ii. Applicant information details: this will display the applicant full name and ID and by clicking on it the user information page will appears containing the applicant information details.

iii. Application information details: (fields required from the GCAA)

iv. Application date: the information submitted date.

v. Attached documents: list of attached documents (data grid field), for each record the document can be downloaded, add notes or comments to it.

vi. Notes and comments: The ANS inspector have the ability to add notes, comments or attach documents to the application:

of 141






- The notes and the attached documents added by the ANS inspector will be available in a list (data grid field) with date/time of creation and the creator name displayed beside it for each record.

- The notes and documents can be added by clicking on the “add notes and documents” button on the application details page, a new small window will appear containing the following fields:

1. Date and time: displayed date/time text field filled by the system.

2. Application ID: displayed text field filled by the system.

3. Notes & comments: multiline text box field.

4. Upload documents: this field will include:

a. Disabled text box field: for the path of the fileb. “Browse” button: to browse the files in the

computer.c. “Upload file” button: to upload the selected file.d. “Add another document” button or link: to add

another “File Attachment” fields to attach another file.

5. Confidential: this is a check box field, default case is on, the notes and/or documents are confidential most of the time and can be viewed only by the ANS inspector, unless the ANS inspector change the check box to off, then the notes or data entered are not confidential and can be viewed by the applicant.

6. “Add” button: this will save all the entered data, in case of empty fields and attachments nothing will be saved.

of 141






7. “Cancel” button: this is will close the small window, with no changes on the application.

vii. “Assign” button: this button used by the ANS inspector to:

1. Assign coordinator: this is to assign the responsible ANS inspector for this application, which he will follow up and assure the completion of the workflow for this application.

Any ANS inspector can open an application and assign himself or any of his colleagues to be the coordinator of this application, even if the application is already assigned to another ANS inspector.

After clicking on the assign button a list of ANS inspectors (including the person who clicks on the assign button) will appear, by clicking on any one and click on submit button the selected ANS inspector will assigned as the coordinator of the application.

This can be changed later (using the same way as mentioned before) by any ANS inspector.

2. Assign assistant: The coordinator ANS inspector can click on “assign” button and then choose “assign assistant” that will open a list of the ANS inspectors exclude himself and including the ANS manager, and by selecting a one or more ANS inspectors the ANS coordinator must write notes and or attach documents (for telling the reason of assistance) and then click on submit button.

After submitting the assigning a notification will be sent to the selected ANS inspectors, which they can view the application with the notes and attached document by the coordinator.

of 141






viii. “Save and close” button: the application details page will close and save all the changes done on it, with no changes on the application status.

ix. “Partially rejected” button: by clicking on this button a new window will appear with the following fields:



3. Notes & comments: large multiline text box field, this mandatory field for this process.


a. Disabled text box field: for the path of the fileb. “Browse” button: to brows the files in the



5. “Submit” button: this will save all the entered data and the application status will be changed to “information required”

The notes field is required to be filled by the ANS inspector but the attaching documents are optional.

6. “Cancel” button: this is will close the small window.

After submitting, a notification email (the notification template text for “information required” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant email telling that the application must be

of 141






updated with information or documents required as mentioned in the pre-requisites with the notes written by the ANS inspector and the application will be sent back to the queue.

Note that when the applicant open the application details page the information entered and the attached documents fields will be in the edit mode so the applicant is allowed to update any or all of the fields with the new information and upload documents as needed depending on the ANS inspector notes and documents.

Note that the old information and documents will be stored for future reference.

x. “Approve” button: by clicking on this button a new window will appear with the following fields:



3. Notes & comments: large multiline text box field.





5. “Approve” button: this will save all the entered data (if available) (all the fields are optional, and if left empty the

of 141






process will complete) and the application will be approved as follows:

a. Electronically signed and approved finally by the ANS inspector.

b. Electronically signed and approved by the ANS inspector and sent to the direct manager for final approval with electronic signature.

c. Electronically signed and approved by the ANS inspector and sent to the direct manager for approval with electronic signature then sent to the General Director for final approval with electronic signature.

Note: If the application rejected by any of the managers it will be rejected with the notes and documents (if any) entered by the managers and a notification (the notification template text for “approval” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).

After the final approval the application status will be changed to “approved” and a notification (the notification template text for “approved” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant email, and a certificate (The certificate template required from GCAA) will be generated by the system, the applicant can print the PDF/A certificate file by download it from the application details page, also a copy of the certificate (the notification template text for “approved” can be inserted and updated from the ANS inspector control panel) will be sent to the TRA email (note that the ANS inspector can add as many cc emails with attach documents to be sent as he want).


of 141






xi. “Reject” button: by clicking on this button a new window will appear with the following fields:



3. Notes & comments (rejection reasons): large multiline text box field, this mandatory field for this process.





5. “Reject” button: this will save all the entered data (the notes field is mandatory) and the application status will be changed to “rejected”, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).


- The ANS inspector or manager may simple or advance search on the applications wither it’s on pending, in-process, rejected or accepted.

of 141






- The ANS inspector or manager may use a detailed query to generate reports from the applications, this will include the under status of pending, in-process, rejected or accepted applications.

- The ANS inspector or manager may generate charts and add notes and attach documents to it then email it.

of 141






3.2.5 Frequency Spectrum approval workflow and business process (Letter of no Objection):

Figure 6: Frequency Spectrum Approval workflow (Letter of No Objection)

of 141






3.3 Harmful Interference Report:

3.3.1 Overview:This section will discuss in details the attributes, functionalities and workflow concerned with the automation of the Harmful Interference Report process

3.3.2 The unit’s user process:

- The username and password will be provided by the unit’s admin who will get the ANS inspector login information through the GCAA IT administrators as mentioned in the Users Authentication section 3.1 .

- After a successful login, the e-services home page will appear with the e-services menu that the unit’s user has the privilege to see and by clicking on the “Harmful Interference Report” link the “Harmful Interference Report” e-service page will appear.

- The unit user may view the pre-requisites information to this e-service before submitting the form (the pre-requisites entered and modified by the ANS inspector through the control panel, also it can be downloaded as PDF/A file).

- After the unit user pass the pre-requisites page by clicking on “next” button the details of “Harmful Interference Report” e-service page will appears with the list of fields to be filled, as the following:


Column Type


Additional Settings

Application Date

date/time field



Format: DD/MM/YYYY

Application ID

Alphanumeric



Format:(The ID format required from

of 141






GCAA)Attach documents



Notes & comments

Multiline text box


No


Table(3): Harmful Interference Report


Column Type


Additional Settings

Attachment path






Yes

Add More files


No


- After submitting the form, a confirmation page will appear displaying (only) all the data filled by the unit’s user, to review them and to make sure that all the data entered is all right.



of 141






b) Beck button: to go back to the previous page with all the fields that contains the data entered by the unit’s admin to modify it and submit it or to cancel the application.



Date Submitted

Status Action


Pending View


- The status of the application will be shown as one of the following:

1) Pending: not been viewed yet.

2) In-process: it’s under reviewing by the ANS inspector.

3) Partially rejected (more information required): for missing or required documents or information. The application process holds until it’s resubmitted by the unit’s user with filling the required documents or information.

When the unit’s user opens the application details page the information entered and the attached documents fields will be in the edit mode so the unit’s user is allowed to update any or all of the fields with the new information and upload documents as needed depending on the ANS inspector notes and documents, the old information and documents will be saved for future reference.

A notification email (the notification template text for partially reject can be inserted and updated from the ANS inspector control panel) will be sent to the unit’s user email telling that the application must be updated with information or documents required as mentioned in the pre-requisites with the notes written by the ANS inspector and the application will be sent back to the queue.

of 141







f. Rejected: this status for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, the unit’s user may only view the reason (with notes and documents) of rejection and if the unit’s user get new information or documents to support the case, a new application must be submitted, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the unit’s user email.


4) Accepted: all the data and documents attached to the application will be stored in the data base, and the application status will be converted to “accepted”.

- If there is any update to the status of the application the “Harmful Interference Report” link will turn into bold until it’s been viewed by the unit’s user



- In the ANS inspector e-services home page a “Harmful Interference Report” link will be available, it will turn into bold indicating that there is new or updated application.

- By clicking on the “Harmful Interference Report” link a list of available pending application will be shown, also the ANS inspector can navigate the in-process, approved, partially rejected or rejected applications by clicking on the tab named as the status name.

of 141







Unit’s user

Application Type

Submitted Date


Action

Full Name

New Request






- Application details page: By clicking on the details link of a specific application record the application details page will open and show the following details:

i. Application ID: display text field, this field will be filled by the system automatically.

ii. Unit’s user information details: this will display the unit’s user full name and ID and by clicking on it the user information page will appears containing the applicant information details.

iii. Application information details: (fields required from the GCAA).

iv. List of attached documents: data grid field for each record the document can be downloaded, add notes or comments to it.

v. Application date: the information submitted date.


of 141








a) Date and time: displayed date/time text field filled by the system automatically.

b) Application ID: displayed text field filled by the system automatically.

c) Notes & comments: large multiline text box field.

d) Upload documents: this field will include:

1. Disabled text box field: for the path of the file2. “Browse” button: to browse the files in the computer.3. “Upload file” button: to upload the selected file.4. “Add another document” button or link: to add another “File

Attachment” fields to attach another file.

e) Confidential: this is a check box field, default case is on, the notes and/or documents are confidential most of the time and can be viewed only by the ANS inspector’s, unless the ANS inspector make the check box off, then the notes or data entered are not confidential and can be viewed by the unit’s user.

f) “Add” button: this will save all the entered data, in case of empty fields and attachments nothing will be saved.

g) “Cancel” button: this is will close the small window

of 141






vii. “Assign” button: this button used by the ANS inspector to:

a) Assign coordinator: this is to assign the responsible ANS inspector for this application, which he will follow up and assure the completion of the workflow for this application.

- Any ANS inspector can open an application and assign himself or any of his colleagues to be the coordinator of this application, even if the application is already assigned to another ANS inspector.

- After clicking on the assign button a list of ANS inspectors (including the person who clicks on the assign button) will appear, by clicking on any one and click on submit button the selected ANS inspector will assigned as the coordinator of the application.

- This can be changed later (using the same way as mentioned before) by any ANS inspector.

b) Assign assistant: The coordinator ANS inspector can click on “assign” button and then choose “assign assistant” that will open a list of the ANS inspectors exclude himself and including the ANS manager, and by selecting a one or more ANS inspectors the ANS coordinator must write notes and or attach documents (for telling the reason of assistance) and then click on submit button.

- After submitting the assigning a notification will be sent to the selected ANS inspectors, which they can view the application with the notes and attached document by the coordinator.

of 141






viii. “Save and close” button: the application details page will close and save all the changes done on it, with no changes on the application status.

ix. “Partially rejected” button: by clicking on this button a new window will appear with the following fields:

a) Date and time: displayed date/time text field filled by the system.

b) Application ID: displayed text field filled by the system.

c) Notes & comments: large multiline text box field, this mandatory field for this process.


1. Disabled text box field: for the path of the file2. “Browse” button: to brows the files in the computer.3. “Upload file” button: to upload the selected file.4. “Add another document” button or link: to add another “File


e) “Submit” button: this will save all the entered data and the application status will be changed to “information required”


f) “Cancel” button: this is will close the small window.

- After submitting, a notification email (the notification template text for “information required” can be inserted and updated from the ANS inspector control panel) will be sent to the units’ user email telling that the application must be updated with information or documents required as mentioned in the pre-requisites with the notes written by the admin and the application will be sent back to the queue.

of 141






- Note that when the applicant open the application details page the information entered and the attached documents fields will be in the edit mode so the unit’s user is allowed to update any or all of the fields with the new information and upload documents as needed depending on the ANS inspector notes and documents.

- Note that the old information and documents will be stored for future reference.






1. Disabled text box field: for the path of the file.2. “Browse” button: to brows the files in the computer.3. “Upload file” button: to upload the selected file.4. “Add another document” button or link: to add another “File


e) “Approve” button: this will save all the entered data (if available) (all the fields are optional, and if left empty the process will complete) the application will be stored in the data base and approved as follows:


of 141








Note: If the application rejected by any of the managers it will be rejected with the notes and documents (if any) entered by the manager and a notification (the notification template text for “information required” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).

The ANS inspector may send the application details to TRA through email, the application details will be attached to the email as PDF/A file, and the ANS inspector may include any notes or/and documents to the email.

After the final approval, the application status will be changed to “approved”.


xi. “Reject” button: by clicking on this button a new window will appear with the following fields:



of 141






c) Notes & comments (rejection reasons): large multiline text box field, this mandatory field for this process.


d. Disabled text box field: for the path of the filee. “Browse” button: to brows the files in the

computer.f. “Upload file” button: to upload the selected file.g. “Add another document” button or link: to add


e) “Reject” button: this will save all the entered data (the notes field is mandatory) and the application status will be changed to “rejected”, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).





of 141






3.3.4 the Figure blow illustrates the work flow of the Harmful Interference Report (HIR) process workflow:

of 141






Figure 7: Harmful Interference Report

of 141






3.4 Equipment Registration Form

3.4.1 Overview:This section will discuss in details the attributes, functionalities and workflow concerned with the automation, requirements and specifications of the “Equipment Registration Form”.


The username and password will be provided by the unit’s admin who will get the ANS inspector login information through the GCAA IT administrators as mentioned in the Users Authentication section 3.1 .

After a successful login, the e-services home page will appear with the e-services menu that the unit’s user has the privilege to see and by clicking on the “Equipment Registration Form” link the “Equipment Registration Form” e-service page will appear.

The unit user may view the pre-requisites information to this e-service before Submitting the form (the pre-requisites entered and modified by the ANS inspector through the control panel, also it can be downloaded as PDF/A file).

After the unit user pass the pre-requisites page by clicking on “next” button the details of “Equipment Registration Form” e-service page will appears with the list of fields to be filled, as the following:


Column Type


Additional Settings

Application Date

date/time field



Format: DD/MM/YYYY

Application Alphanum every application submitted Auto filled Format:

of 141






ID eric will assigned an ID (User cannot modify)

(The ID format required from GCAA)

Attach documents



Notes & comments

Multiline text box


No

Location Drop down list


Equipment Classification

Drop down list

this will retrieve the data from the database, which the ANS inspector have the ability to add, update delete records on it through a special page located at his control panel.

Yes

Equipment Type

Drop down list


Yes

Serial No Text box field

Yes

Supplier Drop down list


Yes

Status Drop this will retrieve the data Yes

of 141






down list from the database, which the ANS inspector have the ability to add, update delete records on it through a special page located at his control panel.

Calibration Date box field

Yes

Date Calibration Due

Date box field

Yes

Frequency Text box field

Yes

Identification

Text box field

Yes

WGS-84 2 Text boxes fields

Yes One for W (west) and the other for E (east).

AIP Published

Check box field

Yes

LONO Check box field

Yes

CNS Manual Published

Check box field

Yes

Operational Approval

Check box field

Yes

Unit’s Name Text box field


Table(3): Equipment Registration Form


Column Type


Additional Settings

Attachment Disabled To insert the path after Auto filled

of 141






path text box field

choosing the file. (User cannot modify)



Yes

Add More files


No


After submitting the form, a confirmation page will appear displaying (only) all the data filled by the unit’s user, to review them and to make sure that all the data entered is all right.

The confirmation page contains 2 buttons:



c) There is 3 types of application the unit’s user may apply to:

1) Add new equipment:2) Change equipment data request: if the unit’s user sees that there is

some missing or wrong information on the registered equipment details.

3) Equipment out of service request

For the applications type of “change equipment data request” and “equipment out of service request” the unit’s admin should first finds an equipment, and click on it and when the equipment details page

of 141






appears, there will be a button for “update” and “Remove (out of service)” an equipment, and by clicking on one of them the request form will appear as follows:

For the “update” button: When clicking on the “update” button a copy of editable equipment details page for the same equipment will appear and the unit’s user has the ability to add and/or update the information or attached files and then submit the application.

The unit’s user may insert notes and attach document to the application as needed.

For the “remove” button: When the unit’s user finds the required equipment and clicking on “View Details” link or button, the equipment details page appears with “remove” button (make it out of service button) on it.

The equipment will not be removed from the data base it will only be assigned as inactive, and all the history information related to it will be kept for reference.

The unit’s user may insert notes and attach document to the application as needed.

The application will be listed in a pending applications queue with FIFO order (oldest request on top) as follows:


Date Submitted

Status Action


Pending View


The unit’s user might follow up with the requested application by visiting the unit’s user “Equipment Registration” queue list and view the status of it, the status could be as follows:

of 141






Pending: not been viewed yet.

In-process: under reviewing by the ANS inspector.

Partially rejected (request for more information): for missing or required documents or information. The application process holds until it’s resubmitted by the unit’s user with filling the required documents or information.




Rejected: this status for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, the unit’s user may only view the reason (with notes and documents) of rejection and if the unit’s user get new information or documents to support the case, a new application must be submitted, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the unit’s user email.

The application status will convert to “rejected”

of 141






Accepted: all the data and documents attached to the application will be stored in the data base, and the application status will be converted to “accepted”.

After acceptance of the application the data of the equipment will be saved depending on the application type as follows:

1) Adding new equipment: an equipment ID will be generated automatically by the following format:(The equipment ID format required from GCAA)

All the equipment details will be stored on the database, and any unit’s user from the same organization may view it later on

2) Change equipment data request: all the updated equipment data details will be updated and stored on the database, the old equipment data will be saved for future reference and can be viewed only by the ANS inspector.

3) Equipment out of service request: the equipment will be assigned as inactive equipment and the unit’s user will not be able to view it or to view any detail about it.



- In the ANS inspector e-services home page a “Equipment Registration” link will be available, it will turn into bold indicating that there is new or updated application.

of 141






- By clicking on the “Equipment Registration” link a list of available pending application will be shown, also the ANS inspector can navigate the in-process, approved, partially rejected or rejected applications by clicking on the tab named as the status name.


Unit’s user

Application Type

Submitted Date


Action

Full Name

New Request







1) Application ID: display text field this will be filled by the system.2) Unit’s user information details: will be automatically attached by the

system.3) Application information details (those fields will be provided by the

GCAA).4) List of attached documents: data grid field for each record the document

can be downloaded, add notes or comments to it.5) Notes and comments: The ANS inspector have the ability to add notes,

comments or attach documents to the application:

ii. The notes and the attached documents added by the ANS inspector will be available in a list (data grid field) with date/time of creation and the creator name displayed beside it for each record.

of 141






iii. The notes and documents can be added by clicking on the “add notes and documents” button on the application details page, a new small window will appear containing the following fields:

1. Date and time: displayed date/time text field filled by the system automatically.

2. Application ID: displayed text field filled by the system automatically.

3. Equipment ID: this will be attached with the application automatically for the applications type of “change equipment data request” and “Equipment out of service request”.

4. Notes & comments: large multiline text box field.5. Upload documents: this field will include:

a. Disabled text box field: for the path of the file.b. “Browse” button: to browse the files in the



6. Confidential: this is a check box field, default case is on, the notes and/or documents are confidential most of the time and can be viewed only by the ANS inspector’s, unless the ANS inspector make the check box off, then the notes or data entered are not confidential and can be viewed by the unit’s users.



6) “Assign” button: this button used by the ANS inspector to:


of 141











7) “Save and close” button: the application details page will close and save all the changes done on it, with no changes on the application status.

8) “Partially rejected” button: by clicking on this button a new window will appear with the following fields:

a. Date and time: displayed date/time text field filled by the system automatically.

b. Application ID: displayed text field filled by the system automatically.

of 141






c. Equipment ID: this will be attached with the application automatically for the applications type of “change equipment data request” and “Equipment out of service request”.

d. Notes & comments: large multiline text box field, this is mandatory field for this process.

e. Upload documents: this field will include:i. Disabled text box field: for the path of the fileii. “Browse” button: to brows the files in the computer.

iii. “Upload file” button: to upload the selected file.iv. “Add another document” button or link: to add another “File

Attachment” fields to attach another file.f. “Submit” button: this will save all the entered data and the

application status will be changed to “information required”.The notes field is required to be filled by the ANS inspector but the attaching documents are optional.

g. “Cancel” button: this is will close the small window.




9) “Approve” button: by clicking on this button a new window will appear with the following fields:

of 141






h. Date and time: displayed date/time text field filled by the system.i. Application ID: displayed text field filled by the system.j. Equipment ID: this will be attached with the application

automatically for the applications type of “change equipment data request” and “Equipment out of service request”.

k. Notes & comments: large multiline text box field.l. Upload documents: this field will include:

i. Disabled text box field: for the path of the file.ii. “Browse” button: to brows the files in the computer.

iii. “Upload file” button: to upload the selected file.iv. “Add another document” button or link: to add another “File

Attachment” fields to attach another file.m. “Approve” button: this will save all the entered data (if available)

(all the fields are optional, and if left empty the process will complete) and the application will be stored in the data base, the approval will be as follows:




The following action will be taken after approval depend on the application action:

1. Add new equipment: the equipment data will be stored in the database and the equipment will assign a unique ID with the following format:

of 141






(The format of the equipment ID is required from GCAA).

2. Change equipment data request: the equipment will be updated with the new data.

3. Equipment out of service request: the equipment will set to inactive.

All the notes or documents added to the equipment from the moment of starting the registration process will be saved with the document for reference.

When an equipment approved and inserted into the database it will assign as active equipment until the ANS inspector approve for the “out of service” for this equipment it will set as inactive and the date&time of this action will be saved.

After the final approval the application status will be changed to “approved”.

n. “Cancel” button: this is will close the small window.

10) “Reject” button: by clicking on this button a new window will appear with the following fields:

i. Date and time: displayed date/time text field filled by the system automatically.

ii. Application ID: displayed text field filled by the system automatically.

iii. Equipment ID: this will be attached with the application automatically for the applications type of “change equipment data request” and “Equipment out of service request”.

iv. Notes & comments (rejection reasons): large multiline text box field, this is a mandatory field for this process.

v. Upload documents: this field will include:

of 141






1. Disabled text box field: for the path of the file2. “Browse” button: to brows the files in the computer.3. “Upload file” button: to upload the selected file.4. “Add another document” button or link: to add another

“File Attachment” fields to attach another file.

vi. “Reject” button: this will save all the entered data (the notes field is mandatory) and the application status will be changed to “rejected”, if the unit’s user get more documents or information to support the case he/she must start new application, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the unit’s user with the notes and documents (if any).

vii. “Cancel” button: this is will close the small window.

- The ANS inspector or manager may simple or advance search on the applications and the equipments wither it’s on pending, in-process, rejected or accepted.

- The ANS inspector or manager may use a detailed query to generate reports from the applications or the equipments, this will include the under status of pending, in-process, rejected or accepted applications.


of 141






The Figure blow illustrates the work flow of the Equipment Registration process workflow:

Figure 8: Register Equipment Process & Workflow

of 141






3.5 Depositing Equipment Outage Report:

3.5.1 Overview:This section will discuss in details the attributes, functionalities and workflow concerned with the automation, requirements and specifications of the “Deposit Equipment Outage”.



After a successful login, the e-services home page will appear with the e-services menu that the unit’s user has the privilege to see and by clicking on the “Registered Equipments” link a list of equipments will appear.

The list of registered equipments (only the equipments related to this unit organization are visible) will be available, the unit’s user may search through the database of equipments by submitting a query of the equipments fields.

When the unit’s user chooses equipment, the equipment details page will appear.

On the equipment details page a “Deposit Equipment Outage” button will be available.

By clicking on the “Deposit Equipment Outage” button a “Deposit Equipment Outage” page will appear the pre-requisites information to this e-service before Submitting the form (the pre-requisites entered and modified by the ANS inspector through the control panel, also it can be downloaded as PDF/A file).

of 141






After the unit user pass the pre-requisites page by clicking on “next” button the details of “Deposit Equipment Outage” e-service page will appears with the list of fields to be filled, as the following:


Column Type


Additional Settings

Application Date

date/time field



Format: DD/MM/YYYY

Application ID

Alphanumeric




Unit’s user ID

Display text


Equipment ID

Display text

This field is the equipment that the unit’s user wants to deposit as an equipment outage


Attach documents



Notes & comments

Multiline text box


No


Table(3): Deposit Equipment Outage

Files Attachment Fields:Column Column Description Required Additional

of 141






Name Type (Yes/No) SettingsAttachment path






Yes

Add More files


No




1) Confirm button: to confirm the entered data and submit it complete the process.

2) Beck button: to go back to the previous page with all the fields that contains the data entered by the unit’s admin to modify it and submit it or to cancel the application.



Date Submitted

Status Action


Pending View


of 141






The unit’s user might follow up with the requested application by visiting the unit’s user “Deposit Equipment Outage” queue list and view the status of it, the status could be as follows:







g. Rejected: this status for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, the unit’s user may only view the reason (with notes and documents) of rejection and if the unit’s user get new information or documents to support the case, a new application must be submitted, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the unit’s user email.

of 141








- If there is any update to the status of the application the “Deposit Equipment Outage” link will turn into bold until it’s been viewed by the unit’s user



- In the ANS inspector e-services home page a “Deposit Equipment Outage” link will be available, it will turn into bold indicating that there is new or updated application.

- By clicking on the “Deposit Equipment Outage” link a list of available pending application will be shown, also the ANS inspector can navigate the in-process, approved, partially rejected or rejected applications by clicking on the tab named as the status name.


Unit’s user

Application Type

Submitted Date


Action

Full Name

New Request





of 141










iii. Application information details: (fields required from the GCAA).

iv. List of attached documents: data grid field for each record the document can be downloaded, add notes or comments to it.

v. Application date: the information submitted date.





of 141







c) Equipment ID: this will be attached with the application automatically.

d) Notes & comments: large multiline text box field.

e) Upload documents: this field will include:



f) Confidential: this is a check box field, default case is on, the notes and/or documents are confidential most of the time and can be viewed only by the ANS inspector’s, unless the ANS inspector make the check box off, then the notes or data entered are not confidential and can be viewed by the unit’s user.

g) “Add” button: this will save all the entered data, in case of empty fields and attachments nothing will be saved.

h) “Cancel” button: this is will close the small window

xii. “Assign” button: this button used by the ANS inspector to:


of 141











xiii. “Save and close” button: the application details page will close and save all the changes done on it, with no changes on the application status.

xiv. “Partially rejected” button: by clicking on this button a new window will appear with the following fields:



of 141
















of 141






xv. “Reject” button: by clicking on this button a new window will appear with the following fields:

g) Date and time: displayed date/time text field filled by the system.

h) Application ID: displayed text field filled by the system.

i) Notes & comments (rejection reasons): large multiline text box field, this mandatory field for this process.

j) Upload documents: this field will include:

a. Disabled text box field: for the path of the fileb. “Browse” button: to brows the files in the computer.c. “Upload file” button: to upload the selected file.d. “Add another document” button or link: to add another “File


k) “Reject” button: this will save all the entered data (the notes field is mandatory) and the application status will be changed to “rejected”, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).

l) “Cancel” button: this is will close the small window.

xvi. “Approve” button: by clicking on this button a new window will appear with the following fields:




of 141









e) “Approve” button: this will save all the entered data (all the fields are optional, and if left empty the process will complete the application will be stored in the data base and approved as follows:

e. Electronically signed and approved finally by the ANS inspector.

f. Electronically signed and approved by the ANS inspector and sent to the direct manager for final approval with electronic signature.

g. Electronically signed and approved by the ANS inspector and sent to the direct manager for approval with electronic signature then sent to the General Director for final approval with electronic signature.


All the notes or documents added to the equipment from the moment of starting the registration process will be saved for reference.


of 141










of 141






The Figure blow illustrates the work flow of the Equipment Registration process workflow:

Figure 9: Depositing Equipment Outage Report

of 141






3.6 24 Bit Aircraft ID:

3.6.1 Overview:This section will discuss in details the attributes, functionalities and workflow concerned with the automation, requirements and specifications of the “24 Bit Aircraft ID”.






On the equipment details page a “24 Bit Aircraft ID” button will be available.

By clicking on the “24 Bit Aircraft ID” button a “24 Bit Aircraft ID form” page will appear the pre-requisites information to this e-service before Submitting the form (the pre-requisites entered and modified by the ANS inspector through the control panel, also it can be downloaded as PDF/A file).

of 141






After the unit user pass the pre-requisites page by clicking on “next” button the details of “24 Bit Aircraft ID” e-service page will appears with the list of fields to be filled, as the following:


Column Type


Additional Settings

Application Date

date/time field



Format: DD/MM/YYYY

Application ID

Alphanumeric




Unit’s user ID

Display text


Equipment ID

Display text



Attach documents



Notes & comments

Multiline text box


No


Table(3): 24 Bit Aircraft ID


of 141












Yes

Add More files


No








Date Submitted

Status Action


Pending View


of 141






The unit’s user might follow up with the requested application by visiting the unit’s user “24 Bit Aircraft ID” queue list and view the status of it, the status could be as follows:







h. Rejected: this status for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, the unit’s user may only view the reason (with notes and documents) of rejection and if the unit’s user get new information or documents to support the case, a new application must be submitted, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the unit’s user email.

of 141







8) Accepted: all the data and documents attached to the application will be stored in the data base, and the equipment will be assigned a “24 bit aircraft ID” automatically.

The application status will be converted to “accepted”, the unit’s user may view the “24 bit aircraft ID”.




- In the ANS inspector e-services home page a “24 Bit Aircraft ID” link will be available, it will turn into bold indicating that there is new or updated application.

- By clicking on the “24 Bit Aircraft ID” link a list of available pending application will be shown, also the ANS inspector can navigate the in-process, approved, partially rejected or rejected applications by clicking on the tab named as the status name.


Unit’s user

Application Type

Submitted Date


Action

Full New Date of Form Pending None None View

of 141






Name Request submission Table(5): The application list




vii. Application ID: display text field, this field will be filled by the system automatically.

viii. Unit’s user information details: this will display the unit’s user full name and ID and by clicking on it the user information page will appears containing the applicant information details.

ix. Application information details: (fields required from the GCAA).

x. List of attached documents: data grid field for each record the document can be downloaded, add notes or comments to it.

xi. Application date: the information submitted date.

xii. Notes and comments: The ANS inspector have the ability to add notes, comments or attach documents to the application:



of 141
















xvii. “Assign” button: this button used by the ANS inspector to:

of 141












xviii. “Save and close” button: the application details page will close and save all the changes done on it, with no changes on the application status.

xix. “Partially rejected” button: by clicking on this button a new window will appear with the following fields:


of 141
















of 141







xx. “Reject” button: by clicking on this button a new window will appear with the following fields:

m) Date and time: displayed date/time text field filled by the system.

n) Application ID: displayed text field filled by the system.

o) Notes & comments (rejection reasons): large multiline text box field, this mandatory field for this process.

p) Upload documents: this field will include:



q) “Reject” button: this will save all the entered data (the notes field is mandatory) and the application status will be changed to “rejected”, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).

r) “Cancel” button: this is will close the small window.

xxi. “Approve” button: by clicking on this button a new window will appear with the following fields:



of 141















The equipment will be assigned a “4 bit aircraft ID” automatically by the system, the ANS inspector will insert a range of two hex numbers in the ANS inspector control panel, the system will generate a sequence hex number between the two numbers inserted by the ANS inspector and assign it to the equipment.

of 141






In case of available number before of the sequence number (like some equipment get out of service and assigned as inactive) the system will assign it to this equipment if approved by the ANS inspector.


After the final approval the application status will be changed to “approved”, and the unit’s user may view the assigned 4 bit aircraft ID





of 141






The Figure blow illustrates the work flow of the 24 Bit Aircraft ID process workflow:

Figure 10: 24 Bit Aircraft ID Registration Process

of 141






3.7 SAC/ SIC Code Allocation Process and workflow

3.7.1 Overview:This section will discuss in details the attributes, functionalities and workflow concerned with the automation, requirements and specifications of the “SAC*/SIC* ”.

* SAC: system allocation code.* SIC: system identification code.






On the equipment details page a “SAC/SIC” button will be available.

By clicking on the “SAC/SIC” button a “SAC/SIC form” page will appear the pre-requisites information to this e-service before Submitting the form (the pre-requisites entered and modified by the ANS inspector through the control panel, also it can be downloaded as PDF/A file).

of 141






After the unit user pass the pre-requisites page by clicking on “next” button the details of “SAC/SIC” e-service page will appears with the list of fields to be filled, as the following:


Column Type


Additional Settings

Application Date

date/time field



Format: DD/MM/YYYY

Application ID

Alphanumeric




Unit’s user ID

Display text


Equipment ID

Display text



Attach documents



Notes & comments

Multiline text box


No


Table(3): SAC/SIC


of 141












Yes

Add More files


No








Date Submitted

Status Action


Pending View


of 141






The unit’s user might follow up with the requested application by visiting the unit’s user “SAC/SIC” queue list and view the status of it, the status could be as follows:







i. Rejected: this status for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, the unit’s user may only view the reason (with notes and documents) of rejection and if the unit’s user get new information or documents to support the case, a new application must be submitted, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the unit’s user email.

of 141







12) Accepted: all the data and documents attached to the application will be stored in the data base, and the equipment will be assigned a “SAC/SIC” automatically.

The application status will be converted to “accepted”, the unit’s user may view the “SAC/SIC”.




- In the ANS inspector e-services home page a “SAC/SIC” link will be available, it will turn into bold indicating that there is new or updated application.

- By clicking on the “SAC/SIC” link a list of available pending application will be shown, also the ANS inspector can navigate the in-process, approved, partially rejected or rejected applications by clicking on the tab named as the status name.


Unit’s user

Application Type

Submitted Date


Action

Full Name

New Request



of 141










xiii. Application ID: display text field, this field will be filled by the system automatically.

xiv. Unit’s user information details: this will display the unit’s user full name and ID and by clicking on it the user information page will appears containing the applicant information details.

xv. Application information details: (fields required from the GCAA).

xvi. List of attached documents: data grid field for each record the document can be downloaded, add notes or comments to it.

xvii. Application date: the information submitted date.

xviii. Notes and comments: The ANS inspector have the ability to add notes, comments or attach documents to the application:



of 141
















xxii. “Assign” button: this button used by the ANS inspector to:

of 141












xxiii. “Save and close” button: the application details page will close and save all the changes done on it, with no changes on the application status.

xxiv. “Partially rejected” button: by clicking on this button a new window will appear with the following fields:


of 141
















of 141







xxv. “Reject” button: by clicking on this button a new window will appear with the following fields:

s) Date and time: displayed date/time text field filled by the system.

t) Application ID: displayed text field filled by the system.

u) Notes & comments (rejection reasons): large multiline text box field, this mandatory field for this process.

v) Upload documents: this field will include:



w) “Reject” button: this will save all the entered data (the notes field is mandatory) and the application status will be changed to “rejected”, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).

x) “Cancel” button: this is will close the small window.

xxvi. “Approve” button: by clicking on this button a new window will appear with the following fields:



of 141















The equipment will assigned a SAC/SIC automatically by the system after the ANS inspector choose the type of SAC/SIC.

The ANS inspector through the control panel create types of SAC/SIC and for each type he will add a range of two numbers, so when

of 141






assigning a SAC/SIC it will be a combination of the SAC/SIC type’s name (which may contain 3 letters or more) and the sequence number between the two number range that entered by the ANS inspector.

In case of available number before of the sequence number (like some equipment get out of service and assigned as inactive) the system will assign it to this equipment if approved by the ANS inspector.


After the final approval the application status will be changed to “approved”, and the unit’s user may view the assigned SAC/SIC.





of 141






3.7.4 the Figure blow illustrates the work flow of the SAC/SIC process workflow:

Figure 11: SIC / SAC Allocation Process and workflow

of 141






3.8 Aerodrome Licensing Forms:

3.8.1 Overview:This section will discuss in details the attributes, functionalities and workflow concerned with the automation of the Harmful Interference Report process

3.8.2 The unit’s user 1st process:- The username and password will be provided by the unit’s admin who will get the ANS inspector login information through the GCAA IT administrators as mentioned in the Users Authentication section 3.1 .

- After a successful login, the e-services home page will appear with the e-services menu that the unit’s user has the privilege to see and by clicking on the “Aerodrome Licensing Registration” link the “Aerodrome Licensing Registration” e-service page will appear.

- The unit user may view the pre-requisites information to this e-service before submitting the form (the pre-requisites entered and modified by the ANS inspector through the control panel, also it can be downloaded as PDF/A file).

- After the unit’s user pass the pre-requisites page by clicking on “next” button a list of option (to what type of request the unit’s user applying) will appears, the unit’s user must choose one of these options:

a) New or updated operational equipments.b) New or updated manuals.c) New or updated operational procedures.d) New or updated unit facilities.

- Depend on the option that the unit’s user chooses the details of “Aerodrome Licensing Registration” e-service page will appears with the list of to be filled, as follows:

of 141







Column Type


Additional Settings

Request Date

date/time field



Format: DD/MM/YYYY

Request ID Alphanumeric




Unit’s user ID

Display text


Option name

Dropdown list field

a) New or updated operational equipments.

b) New or updated manuals.

c) New or updated operational procedures.

d) New or updated unit facilities.

Yes

Attach documents



Notes & comments

Multiline text box


No


Table(3): Aerodrome Licensing Registration

of 141







Column Type


Additional Settings

Attachment path






Yes

Add More files


No


- After submitting the form, a confirmation page will appear displaying (only) all the data filled by the unit’s user, to review them and to make sure that all the data entered is all right.






Date Submitted

Status Action


Pending View


of 141






- The status of the application will be shown as one of the following:







of 141






j. Rejected: this status for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, the unit’s user may only view the reason (with notes and documents) of rejection and if the unit’s user get new information or documents to support the case, a new application must be submitted, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the unit’s user email.



After the request acceptance the second phase will start, the ANS inspector will submit a list of required documents and/or projects, this list will prepared by the ANS inspector and sent back to the unit’s user to start filling it.

- If there is any update to the status of the application the “Harmful Interference Report” link will turn into bold until it’s been viewed by the unit’s user.

of 141






3.8.3 The unit’s user 2nd process:

- The ANS inspector will send a list of required documents and projects so the unit’s user has to fill it all to get the whole application approval.

- The application contains a list of documents and/or projects as follows:

i. The document’s fields:

a) The document’s information details and any attached documents related to it.

b) Uploading fields: mandatory field to upload the documents as follows



c) Notes and comments as follows:

1. Date and time: displayed date/time text field filled by the system automatically.2. Application ID: displayed text field filled by the system automatically.3. Notes & comments: large multiline text box field.4. Upload documents: this field will include:

A. Disabled text box field: for the path of the fileB. “Browse” button: to browse the files in the computer.C. “Upload file” button: to upload the selected file.D. “Add another document” button or link: to add another “File Attachment”

fields to attach another file.


6. “Cancel” button: this is will close the small window

of 141






d) Submitted Date/time: display only box generated automatically by the system on the submission time.

ii. The projects fields:

a) The document’s information details and any attached documents related to it.

b) The project application ID: mandatory Text box field to enter the application ID for the project so it will be attached to the application.

c) Uploading fields: optional field to upload documents as follows



d) Notes and comments as follows:

1. Date and time: displayed date/time text field filled by the system automatically.2. Application ID: displayed text field filled by the system automatically.3. Notes & comments: large multiline text box field.4. Upload documents: this field will include:

A. Disabled text box field: for the path of the fileB. “Browse” button: to browse the files in the computer.C. “Upload file” button: to upload the selected file.D. “Add another document” button or link: to add another “File Attachment”

fields to attach another file.


6. “Cancel” button: this is will close the small window

e) Submitted Date/time: display only box generated automatically by the system on the submission time.

of 141






- Each time the unit’s user uploads a document from the list it will be forwarded separately to the ANS inspector as a new request for acceptance with the following expected status:




When the unit’s admin opens the list of requirements page the attached documents fields will be in the edit mode so the unit’s admin is allowed to add or update any or all of the documents with new documents as needed depending on the ANS inspector’s notes and/or documents, the old information and documents will be stored for future reference.

A notification email (the notification template text for partially reject can be inserted and updated from the ANS inspector control panel) will be sent to the unit’s admin email telling that the request must be updated with new documents required as mentioned in the pre-requisites with the notes written by the ANS inspector and the request will be sent back to the queue.

This record status will be converted to “information required”

k. Rejected: this is for final rejection with explanation by the ANS inspector, the process will be terminated and disabled, with the ability from the ANS inspector to allow for starting new process for this part of the list only, the unit’s user may only view the reason (notes and documents) of rejection and if the unit’s admin get new information or documents to support the case, a new request must to be submitted (within this part of the application record list) if allowed by the ANS inspector, and if not this process will be finally rejected this could result for a rejection for the whole application, also a notification (the notification template text for

of 141






rejection can be inserted and updated from the ANS inspector control panel ) of rejection will be sent to the unit’s user email.



- Each time the unit’s user assigns a project to the application from the list it will be reflect to the application record as follows:

1) Accepted: if the project has been accepted this will result of automatic acceptance of this record.

2) Rejected: if the project rejected, this record of the application is rejected and the unit’s user must resubmit a new project through putting the project application ID in the text box field for the same record as an update to it and pending status will assign to it with new process.

- After submitting all the required documents and projects to the application, the whole application might:

1) Rejected: this status for final rejection with explanation by admin, the process will be terminated and disabled, the unit’s admin may only view the reason (notes and documents) of rejection and if the unit’s admin get new information or documents to support the case, the unit’s admin must start the process from the beginning with new request, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel) of rejection will be sent to the unit’s admin email.The whole application status will be converted to “rejected”

of 141






2) Approval: all the data and documents attached to the application will be stored in the data base, and the application status will be converted to “accepted”.

After approval a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel) of approval will be sent to the unit’s user email.

A certificate (the certificate template required from GCAA) will be generated by the system this is after the process is electronically signed and approved by the ANS inspector and the ANS manager, the unit’s user can print the certificate by clicking on the application details and download the PDF/A file, also a notification (the notification template text for rejection can be inserted and updated from the ANS inspector control panel) of approval will be emailed to the unit’s user email (note that the ANS inspector can add as many cc emails with attach documents to be sent as needed).

- If there is any update to the status of the application the “Aerodrome Licensing Registration” link will turn into bold until it’s been viewed by the unit’s admin.

3.8.4 The requests business process workflow:


- In the ANS inspector e-services home page a “Aerodrome Licensing Registration” link will be available, it will turn into bold indicating that there is new or updated applications or requests.

- By clicking on the “Aerodrome Licensing Registration” link a list of available pending requests will be shown, also the ANS inspector can navigate the in-

of 141






process, approved, partially rejected or rejected requists by clicking on the tab named as the status name.

- The requests listed in a queue with FIFO order (oldest request on top) as follows:

Unit’s user

Application Type

Submitted Date


Action

Full Name

New Request




- The moment the ANS inspector opens a request, the status of that request will be changed to “in-process”.

- Also searching tools (simple and advance search) will be available to allow the search within the applications and requests.

- Request details page: By clicking on the details link of a specific request record the request details page will open and show the following details:

a) Request ID: display text field, this field will be filled by the system automatically.

b) Unit’s user information details: this will display the unit’s user full name and ID and by clicking on it the user information page will appears containing the applicant information details.

c) Request information details: (fields required from the GCAA).

d) List of attached documents: data grid field for each record the document can be downloaded, add notes or comments to it.

e) Request date: the information submitted date.

f) Notes and comments: The ANS inspector have the ability to add notes, comments or attach documents to the request:

of 141







- The notes and documents can be added by clicking on the “add notes and documents” button on the request details page, a new small window will appear containing the following fields:









g) “Cancel” button: this is will close the small window

of 141






g) “Assign” button: this button used by the ANS inspector to:

a) Assign coordinator: this is to assign the responsible ANS inspector for this “application”, which he will follow up and assure the completion of the workflow for this “application”.

- Any ANS inspector can open an application and assign himself or any of his colleagues to be the coordinator of this “application”, even if the “application” is already assigned to another ANS inspector.

- After clicking on the assign button a list of ANS inspectors (including the person who clicks on the assign button) will appear, by clicking on any one and click on submit button the selected ANS inspector will assigned as the coordinator of the “application.”



- After submitting the assigning a notification will be sent to the selected ANS inspectors, which they can view the “application” with the notes and attached document by the coordinator.

of 141






h) “Save and close” button: the request details page will close and save all the changes done on it, with no changes on the request status.

i) “Partially rejected” button: by clicking on this button a new window will appear with the following fields:


h) Request ID: displayed text field filled by the system.

i) Notes & comments: large multiline text box field, this mandatory field for this process.




k) “Submit” button: this will save all the entered data and the application status will be changed to “information required”



- After submitting, a notification email (the notification template text for “information required” can be inserted and updated from the ANS inspector control panel) will be sent to the units’ user email telling that the request must be updated with information or documents required as mentioned in the pre-requisites with the notes written by the admin and the request will be sent back to the queue.

of 141






- Note that when the request open the request details page the information entered and the attached documents fields will be in the edit mode so the unit’s user is allowed to update any or all of the fields with the new information and upload documents as needed depending on the ANS inspector notes and documents.


j) “Reject” button: by clicking on this button a new window will appear with the following fields:


b) Request ID: displayed text field filled by the system.





e) “Reject” button: this will save all the entered data (the notes field is mandatory) and the request status will be changed to “rejected”, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).


of 141






xxvii. “Approve” button: by clicking on this button a new window will appear with the following fields:


b) Request ID: displayed text field filled by the system.





e) “Approve” button: this will save all the entered data (all the fields are optional, and if left empty the process will complete) the request will be stored in the data base and approved as follows:




Note: If the request rejected by any of the managers it will be rejected with the notes and documents (if any) entered by the manager and a notification (the notification template text for

of 141






“information required” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).

After the final approval, the request status will be changed to “approved”.

The ANS inspector now may choose a list of required documents or projects and send this list to the unit’s admin to fill it all to get the approval for the application.

The ANS inspector choose the list of requirement from a stored requirement in the database, the ANS inspector can update or add new requirement for future use, by submitting the following fields:

a. Requirement type: document or project, this is drop down list field.

b. Requirement name: text box field.c. Requirement details: multiline text box field to insert the

details of this requirement.


- The ANS inspector or ANS manager may simple or advance search on the requests wither it’s on pending, in-process, rejected or accepted.

- The ANS inspector or ANS manager may use a detailed query to generate reports from the requests, this will include the under status of pending, in-process, rejected or accepted applications.

- The ANS inspector or ANS manager may generate charts and add notes and attachment documents to it then email it.

of 141






3.8.1 The applications business process workflow:

- After the ANS inspector submit the list of requirements to the unit’s user, the request will turn into accepted and the new application will turn into “pending”.

- The unit’s admin start to fill the list of requirements, for each record in the list he submit either document or project.

- In case of submitting a request for a project the record’s status of the list will be related to the project status, if it’s accepted the records list will be accepted and if it’s rejected the rejected.

- In case of submitting a request for a document, the request of approval for this document will be sent to the ANS inspector for approval as part of the application approval workflow, the ANS inspector may view the request by clicking on the records field details, and a request detailed page will appear as follows:



iii. List of attached documents: data grid field for each record the document can be downloaded, add notes or comments to it.

iv. Application date: the information submitted date.

v. Notes and comments: The ANS inspector have the ability to add notes, comments or attach documents to the application:


of 141















g) “Cancel” button: this is will close the small windowvi. “Assign” button: this button used by the ANS inspector to:

of 141












vii. “Save and close” button: the application details page will close and save all the changes done on it, with no changes on the application status.

viii. “Partially rejected” button: by clicking on this button a new window will appear with the following fields:


of 141






h) Application ID: displayed text field filled by the system.

i) Notes & comments: large multiline text box field, this mandatory field for this process.




k) “Submit” button: this will save all the entered data and the application status will be changed to “information required”





of 141







ix. “Reject” button: by clicking on this button a new window will appear with the following fields:





h. Disabled text box field: for the path of the filei. “Browse” button: to brows the files in the computer.j. “Upload file” button: to upload the selected file.k. “Add another document” button or link: to add another “File


e) “Reject” button: this will save all the entered data (the notes field is mandatory) and the application status will be changed to “rejected”, and a notification (the notification template text for “reject” can be inserted and updated from the ANS inspector control panel) will be sent to the applicant with the notes and documents (if any).





of 141










e) “Approve” button: this will save all the entered data (all the fields are optional, and if left empty the process will complete) the application will be stored in the data base and approved as follows:

l. Electronically signed and approved finally by the ANS inspector.

m. Electronically signed and approved by the ANS inspector and sent to the direct manager for final approval with electronic signature.

n. Electronically signed and approved by the ANS inspector and sent to the direct manager for approval with electronic signature then sent to the General Director for final approval with electronic signature.




of 141






- After reviewing each record on the list the ANS inspector can do one of the following actions:

i. Notes and comments: The ANS inspector have the ability to add notes, comments or attach documents to the request:


- The notes and documents can be added by pressing on the “add notes and documents” button on the request details page, a new small window will appear containing the following fields:

i. Date and time: displayed date/time text field filled by the system automatically.

ii. Application ID: displayed text field filled by the system automatically.

iii. Notes & comments: large multiline text box field.

iv. Upload documents: this field will include:

1. Disabled text box field: for the path of the file

2. “Browse” button: to browse the files in the computer.

3. “Upload file” button: to upload the selected file.

4. “Add another document” button or link: to add another “File Attachment” fields to attach another file.

v. Confidential: this is a check box field, default case is on, the notes and/or documents are confidential most of the time and can be

of 141






viewed only by the ANS inspector’s, unless the ANS inspector make the check box off, then the notes or data entered are not confidential and can be viewed by the unit’s admin.

vi. “Add” button: this will save all the entered data, in case of empty fields and attachments nothing will be saved.

vii. “Cancel” button: this is will close the small window

ii. Reject the application: by pressing on this button a new window will appear with the following fields:


2. Application ID: displayed text field filled by the system automatically.

3. Notes & comments (rejection reasons): large multiline text box field, this is a mandatory field for this process.


a. Disabled text box field: for the path of the file

b. “Browse” button: to brows the files in the computer.

c. “Upload file” button: to upload the selected file.

d. “Add another document” button or link: to add another “File Attachment” fields to attach another file.

5. “Reject” button: this will save all the entered data (the notes field is mandatory) and the request status will be changed to

of 141






“rejected”, and a notification (the text template of the notification will be provided by GCAA, also it can be modified from the ANS inspector control panel) will be sent to the unit’s admin with the notes and documents (if available).


iii. Accept the application: by pressing on this button a new window will appear with the following fields:


8. Request ID: displayed text field filled by the system automatically.

9. Notes & comments: large multiline text box field.


a. Disabled text box field: for the path of the file.

b. “Browse” button: to brows the files in the computer.

c. “Upload file” button: to upload the selected file.

d. “Add another document” button or link: to add another “File Attachment” fields to attach another file.


12. “Approve” button: this will save all the entered data (all the fields are optional, and if left empty the process will complete) and the request status will be turned into “approved”.After the final approval the application status will be changed to “approved” and a notification (the notification template text for

of 141






“approved” can be inserted and updated from the ANS inspector control panel) will be sent to the unit’s user email, and a certificate (The certificate template required from GCAA) will be generated by the system, the applicant can print the PDF/A certificate file by download it from the application details page, also a copy of the certificate can be emailed and cc with attach documents to anyone the ANS inspector or manager decide.

b. The ANS inspector or ANS manager may simple or advance search on the application or requests wither it’s on pending, in-process, rejected or accepted.

c. The ANS inspector or ANS manager may use a detailed query to generate reports from the applications or requests, this will include the under status of pending, in-process, rejected or accepted applications.

d. The ANS inspector or ANS manager may generate charts and add notes and attachment documents to it then email it.

of 141






3.8.2 Aerodrome Licensing Registration workflow and business process:

Figure 12: The Aerodrome Licensing Process and work flow

of 141






4 Non-functional Requirements

4.1 Performance Requirements

The application should be fast in processing the data entry and a high level of accuracy

has to be maintained. However the performance will depend to a great extent on the

hardware resources of the web server.

1. Compatibilitya) GCAA software should run compatibly (i.e. under the same operating

system, database and networking capabilities) with the other subsystems software it works together with.

b) System will allow administrator to enroll new users and grant access rights required by their duties.

2. Reliability and Availabilitya) System will permit 1 hour per day for maintenance and backup activities

with minimal disruption to users.b) Any failure should cause no more than 10-minute downtime, with the

average not exceding 2 minutes.c) Backup should spot-tested to ensure they are reliable.

3. Performancea) System will allow up multiable users to login and use the system at the

same time, the response time of the system will depend on the speed of the connection both for the server and client machine and on the number of loggedin users at the same time .

of 141






4.2 Security RequirementsThe portal will manage, deliver and receive sensitive information. Security is a prime

requirement of the portal system.

The portal will provide access for authorized users while screening out those who do not

need to view confidential data.

The Development team may choose one of the security methods below:

a) Forms authentication:

It a system by which unauthenticated requests is redirected to an HTML form using

HTTP client-side redirection. The user provides credentials and submits the form. If the

application authenticates the request, the system issues a cookie that contains the

credentials or a key for reacquiring the identity. Subsequent requests are issued with

the cookie in the request headers; they are authenticated and authorized by an ASP.NET

event handler using whatever validation method the application developer specifies. All

users account saved in separated data base.

b) Windows authentication:

Authentication is performed by IIS in one of three ways: basic, digest, or Integrated

Windows Authentication. When IIS authentication is complete, ASP.NET uses the

authenticated identity to authorize access. Integrated with active directory

authentications

5 Technical Assumptions MS Exchange and active directory are already in place and running before

project kickoff.

Active directory integration within this project will only be the default integration provided by SharePoint. No extra work or customization will be done for active directory.

of 141






The server hosting the solution will be set up in the same domain in the corporate network.

Infrastructure efforts and configurations will be done for SharePoint needs only.

The look and feel proposed will be simple with no complex graphics involved (Complex graphics are defined as navigation, flashes, and site structure, while non-complex graphics includes color and logos of the portal)

It's highly recommended to install MS Office 2007 on all clients’ machines. THE DEVELOPMENT will not hold responsibility for any missing functionality due to using old versions of office.

It's assumed that the content validation and data entry for the new portal site will be GCAA’s responsibility.

The development TEAM will brand GCAA eServices based on the selected theme however the ANS administration sites that will be created during the installation and the configuration to SharePoint farm like the central administration site and the shared service provider will not be branded and will use out of the box themes.

The development TEAM will not customize any administration pages for the SharePoint 2007.

THE DEVELOPMENT TEAM will integrate the MOSS 2007 with Ultimus Workflow system to be used as a workflow engine as per, under the limitations of share point and Ultimus softwares cabapility and integration v.

Its assumed that all the required licensing for Integration with Utltimus will be provided by GCAA including API integration

It’s assumed that the portal will authenticate the users against the active directory.

It's assumed that THE DEVELOPMENT TEAM will integrate the systems with the existing DMS provided by GCAA to build the required administration pages for uploading content.

It's assumed that the internet users’ profiles will be stored in the database.

of 141






It is assumed that THE DEVELOPMENT TEAM will utilize an existing payment gateway to enable payment transaction over the internet portal. However, THE DEVELOPMENT will not be responsible for any extra charges or fees due to implementing this feature. Also, it is assumed that GCAA will provide all the needed standard interfaces (SDK, XML Web Services, HTTP …) and credentials for THE DEVELOPMENT TEAM to be able to connect to this payment gateway.

It is assumed that THE DEVELOPMENT TEAM will utilize an existing SMS gateway to enable SMS transaction over the internet portal. However, THE DEVELOPMENT TEAM will not be responsible for any extra charges or fees due to implementing this feature. Also, it is assumed that GCAA will provide all the needed standard interfaces (SDK, XML Web Services, HTTP …) and credentials for THE DEVELOPMENT TEAM to be able to connect to this SMS gateway.

of 141