Etihad Portal Phase1 Srs v5.4 RF Final

[The National Airline of the United Arab Emirates Etihad Airways]
Etihad Airways - Implementation of Cargo Website Portal Requirements Specification Document

Version 3.0

Document Status Draft Final Release Signed Off/Baseline Document Author Ahmed Elbaz - Senior Systems Analyst Ahmed Ashraf system analyst Table 1: Document Versions Document Version V 1.0 V 2.0 V 3.0 Distribution List Action Modified By Date & Time Section, Page(s) / Text Revised
Create Create Create
Ahmed Elbaz Ahmed Ashraf Ahmed Ashraf
09/04/2012 20/05/2012 13/06/2012
Table 2: Distribution List Affiliation External External External External Name Rory David Fidler Sheron Fernando Jeremy Krisnamur Etihad IT team Role SME - Etihad Cargo, Business owner SME - Etihad Cargo Etihad Cargo, Branding representative Etihad Cargo, Existing systems representative Etihad Cargo Etihad Cargo, Head of Product & Distribution Etihad Cargo , Manager, Cargo Product Development Service Delivery Manager
External External
Pricing & Planning Team Sam O.E. Okpro
External
Rabih BouHussien
Internal
Ahmed Magdy
Etihad Airways - Implementation of Cargo Website Portal Requirements Specification Document Version 3.0 ITWorx Inc. 2012 Page 2 of 89
Internal Internal Internal Internal Sign Off
Hossam Eloraby Ahmed Elbaz Ahmed Ashraf Mohamed Rashad
Engagement Manager Systems Analyst Systems Analyst Onsite Team Leader
Table 3: Sign Off Entities Etihad Cargo ITWorx Name Signature
Contents
1 About the Document .......................................................................................................... 8
1.1 1.2 1.3 Document Purpose and Scope .................................................................................................................8 Document Context ....................................................................................................................................8 Document Conventions ............................................................................................................................ 8 Mandating Verbs .............................................................................................................................. 8
1.3.1
About the Project................................................................................................................. 9

1.4 1.5 Business Background ................................................................................................................................ 9 Platform Portals Purpose and Scope .................................................................................................... 10 In Scope ............................................................................................................................................ 10 Out of Scope .................................................................................................................................... 11
1.5.1 1.5.2 1.6
Facts, Assumptions, Dependencies, Constraints, Risks ..................................................................... 12
Portal Overview................................................................................................................. 14
3.1 3.2 Logical architecture ................................................................................................................................. 14 Graphical Design ..................................................................................................................................... 14 Look and Feel .................................................................................................................................. 14 Public area Home Page (Internet) ................................................................................................ 15
3.2.1 3.2.2
4 5 6
Glossary of Terms ............................................................................................................. 16 Portal User Profiles ........................................................................................................... 17 Portal Functional Requirements .................................................................................... 18
6.1 Public Area (Internet) ............................................................................................................................. 20 Flights Schedule .............................................................................................................................. 20 Track Shipments ............................................................................................................................. 23 SMS Express ................................................................................................................................ 2423 Flight Status ..................................................................................................................................... 24 Route Map ....................................................................................................................................... 27 About Us .......................................................................................................................................... 27 Mission & Vision ........................................................................................................................ 2827 Our Offices .................................................................................................................................. 2827 Cargo Team (Contact us) ........................................................................................................... 2928 Revenue Management ............................................................................................................... 2928 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.1.6 6.1.7 6.1.8 6.1.9 6.1.10

6.1.11 6.1.12 6.1.13 6.1.14 6.1.15 6.1.16 6.1.16.1 6.1.16.2 6.1.16.3 6.1.16.4 6.1.17 6.1.18 6.1.19 6.2 Cargo Products ........................................................................................................................... 3029 Charter Service ............................................................................................................................ 3130 Sales Team (Cargo Commercial) .............................................................................................. 3231 Freight documents ...................................................................................................................... 3331 RSS ................................................................................................................................................ 3332 Media Center ............................................................................................................................... 3432 Photo Gallery .......................................................................................................................... 3432 Media Electronic marketing.................................................................................................. 3534 Video Libraries ....................................................................................................................... 3534 News ........................................................................................................................................ 3735 Useful links .................................................................................................................................. 3937 Link to Web docs ........................................................................................................................ 3937 Social networks links.................................................................................................................. 3937
Secured Area (Extranet) ..................................................................................................................... 4038 Registration & Login .................................................................................................................. 4038 Register & update profile (Agents) ...................................................................................... 4038 Login ........................................................................................................................................ 4239 Change password ................................................................................................................... 4240 Forgot password ..................................................................................................................... 4240 How can I help you? .................................................................................................................. 4441 Basic requests .......................................................................................................................... 4542 Complicated requests ............................................................................................................ 6056 Invoice verification process ....................................................................................................... 7267 Cargo Service Manual ................................................................................................................ 7468
6.2.1 6.2.1.1 6.2.1.2 6.2.1.3 6.2.1.4 6.2.2 6.2.2.1 6.2.2.2 6.2.3 6.2.4 6.3
General Features .................................................................................................................................. 7670 Portal Content Management ..................................................................................................... 7670 Portal Document Management ................................................................................................. 7872 Document Libraries .................................................................................................................... 7872 Portal Search ................................................................................................................................ 7973 Portal Site Map ............................................................................................................................ 7973
6.3.1 6.3.2 6.3.3 6.3.4 6.3.5
Integration/Interfaces ................................................................................................... 8074

7.1 7.2 Hardware Interfaces ........................................................................................................................... 8175 Software Interfaces .............................................................................................................................. 8175

7.3 Communication Interfaces ................................................................................................................. 8175
Logging Requirements ................................................................................................. 8276

8.1 8.2 Hardware requirement ....................................................................................................................... 8276 Software Requirements ...................................................................................................................... 8276 Communication Requirements ......................................................................................................... 8276 Database Requirements ...................................................................................................................... 8276 Operations Requirements .................................................................................................................. 8276 Regulatory Requirements .................................................................................................................. 8276 Security ................................................................................................................................................. 8276 Exception Handling ............................................................................................................................ 8377 Usability................................................................................................................................................ 8377 Capacity and Performance ................................................................................................................. 8377
3.8
8.4 8.5 8.6 8.7 8.8 8.9 8.10
Other Requirements ..................................................................................................... 8478

9.1 9.2 9.3 9.4 9.5 Technology Requirements ................................................................................................................. 8478 Data Migration ..................................................................................................................................... 8478 System archiving concept ................................................................................................................... 8478 Availability ........................................................................................................................................... 8478 Documentation Requirements ........................................................................................................... 8478
10 11
Appendix II: Clients Wish List for Future Releases ............................................. 8579 Appendix V: Open Issues ............................................................................................ 8680
List of Tables
Table 1: Document Versions ......................................................................................................................................2 Table 2: Distribution List ...........................................................................................................................................2 Table 3: Sign Off .......................................................................................................................................................... 3 Table 4: Document Context .......................................................................................................................................8 Table 5 Glossary of Terms ................................................................................................................................... 1615 Table 6 User Profiles ............................................................................................................................................. 1716 Table 8 Revenue Management documents ....................................................................................................... 2927 Table 9 Cargo Products documents ................................................................................................................... 3028 Table 10 inquiries fields ....................................................................................................................................... 3130 Table 11 Freight documents .............................................................................. Error! Bookmark not defined.31 Table 14 Albums Fields ..................................................................................................................................... 3532 Table 15 Photos Fields ....................................................................................................................................... 3532 Table 16 Video Categories Fields ..................................................................................................................... 3734 Table 17 Video Fields ........................................................................................................................................ 3734 Table 18 - News Fields ......................................................................................................................................... 3835 Table 19 Useful Links Fields................................................................................................................................ 3936 Table 20: Agent registration form fields ............................................................................................................ 4037 Table 21 - Login ..................................................................................................................................................... 4238 Table 22 - Change Password ............................................................................................................................... 4239 Table 23 - Forgot Password ................................................................................................................................. 4239 Table 24 Cargo service documents ..................................................................................................................... 7464 Table 25 Open/Closed Issues............................................................................................................................... 8676
About the Document
The Software Requirements Specifications (SRS) document is the result of the refinement of the business requirement functions, analysis of individual requirement, system process modeling and frontend design (user experience) activities. The document is submitted to Etihad for review and signoff, prior to execution.
1.1 Document Purpose and Scope

The goals of the software requirements specifications document is as follows: To establish and maintain agreement with Etihad and other stakeholders on what the system should do To provide developers with a better understanding of the system requirements To define the boundaries of to delimit the system To provide a basis for planning the technical specs. of each iteration To provide a basis for estimating cost and time to develop the system To define a user interface for the system, focusing on the needs of the users
1.2 Document Context

Table 4: Document Context Reference EY-RFP-Cargo Website.docx Etihad_Cargo Portal Implementation_ITWorx Proposal_Final.docx Location
1.3 Document Conventions

1.3.1 Mandating Verbs
The keywords SHALL, MUST, SHOULD, and MAY in this document are to be interpreted as follows: SHALL: Mandatory requirement; the system/component will be useless without it (most requirements are written with shall) MUST: Mandatory constraint; a rule that the system must apply SHOULD: Suggestive requirement; the system will not be useless without it MAY: An optional (nice-to-have) requirement that can be skipped
About the Project

1.4 Business Background
Etihad Airways is the National Airline of the United Arab Emirates and is based at Abu Dhabi Airport. Etihad has been in operation since 2003 and was awarded the World's Leading Airline in 2009 and 2010 by the World Travel Awards. In addition to its core activity for passenger transportation, Etihad also operates Etihad Holidays and Etihad Crystal Cargo.
Etihad Crystal Cargo is the fast growing cargo division of Etihad Airways. Etihad Crystal Cargo operates to 27 cargo freighter destinations in the Middle East and Africa and 76 destinations across the globe.
Etihad Crystal Cargo current public portal is outdated in terms of technological base, and branding and styling which are not up to the current standards. Etihad is seeking an operational enterprise portal, upgrading Etihad Cargo portal to the latest technologies, and positioning Etihad Cargo portal in its e-Commerce strategy.
1.5 Platform Portals Purpose and Scope

1.5.1 In Scope
Analysis, design, development, testing and deployment of Etihad Cargo Portal Implementation based on SharePoint 2010 Gather requirements for Etihad Cargo Portal Implementation Phase 2 and Phase 3 during Phase 1 implementation and after completion of Phase 1 requirements gathering and signoff System interface will be English only Providing branding and user interface design for Etihad Cargo Portal based on Etihad standards and guidelines Backend Administration: SharePoint 2010 out-of-the-box management module will be used to handle content management, user groups' definition, user rights and permissions Browser Support The browsers supported by SharePoint 2010 are the browsers that will be supported in the solution: IE 8 and 9 FireFox 13 Chrome 19 Etihad Cargo Portal Implementation Phase 1 Etihad Cargo Portal Implementation Phase 1 scope is to provide the following: Please refer to section 6.1 Integration with the following systems: Scheduling System to retrieve flights schedule information Cargospot System to retrieve shipment status and history (AWB) Etihad will provide ITWorx with the XML script to be allowed to access the Cargospot reservation system. Dispatch Departure Control System to retrieve flight status information The system will provide a hyperlink to allow the portal users to open the freight forwarders site (Webdocs) in a new window Hosting Innovate Route Map by providing a page including a place to display the Etihad Cargo Innovata map as it is, while Innovata map are hosted outside the system, but the system will only avail the page and the space to display this map. RSS feeds will be provided for announcements with a dedicated link on the navigation menu or separate icon Announcements will be displayed at the home page as a news bar and it will be handled by SharePoint lists Quick links will be provided as links to external websites. Site Map will be provided by applying the SharePoint out of the box functionality and using Etihad branding and guidelines. Enterprise Content Management for managing Web Content and Document Libraries will be provided based on SharePoint 2010 out-of-the-box functionality. Enterprise Search will be provided and configured in the solution. Assign different passwords for migrated users. Enterprise Search and SharePoint Search will be provided and configured in the solution Following requests forms and workflows: Request information. Request a booking. Ship personal goods. Ship perishable goods. Ship art and precious goods. Ship valuable and vulnerable Cargo. Ship dangerous goods and sporting weapons. Book a charter. Make a fast track booking.

Live animal queries. Ship a car. Human remains. Online feedback. o Make a complaint o Send a compliment o Register a comment Raise a claim
1.5.2 Out of Scope

Online payment Content entry, translation and review Content maintenance and administration after deployment Building a new route map Fixing any issues either loading and performance ones related to Innovata map although transfer of and integration of the map will be deemed as being in scope User migration from the existing portal to the new portal are out of scope, but Etihad may provide about (750 ~ 1000) cleansed and identical to the accounts information spreadsheet of the existing users accounts, then ITWorx will support the creation of these account. Existing users accounts will be created manually from scratch by Etihad staff on the new proposed portal. Content migration from the existing portal to the new portal. The RFP stated that the content is likely to change; so Etihad will provide ITWorx with the new content and will be added from scratch to the new portal for static web pages only. Upgrading of existing portal. The new portal will be developed from scratch on a new environment and no tools will be developed or provided to migrate any of existing portal functionality and content to the new proposed portal. Fix any known issues or limitations in standard SharePoint 2010 Fix any issues in Etihad's current infrastructure Creating additional subpages or sub sites other than the ones in the portal's structure agreed upon Development of custom workflows (Only out of the box workflows will be provided) Integration with back-end applications not mentioned in this document Any requests forms or workflows not mentioned at in scope section. Any custom reports. Single sign on for WebDocs application with new website. Integration with SMS gateways/interface. Integration into corporate common news items from current intranet Schedule amendments. Force registered users to change passwords at first login time. Notifying migrated users with new access credentials, this will be handled/communicated via Cargo team. No delegation or escalation in the provided business processes/workflows Business processes/workflows will have no additional approval steps. No vacation planning provided for workflows No dynamic forms in the workflows No automatic load balancing in the workflows Only the provided notifications will be available for each business process/workflow and no custom notifications.
1.6 Facts, Assumptions, Dependencies, Constraints, Risks

It is assumed that the portal page should load in 5-9 seconds The content format and specific pages will be signed off by Etihad during the wireframes wall work in order to minimize change and increase the delivery timescale The portal shall be available in English language only All the Provisioned sub-sites "Front End" will use the same Look and Feel in the whole portals Portal back end will use the default SharePoint OOB Look and Feel. Etihad's current Active Directory will be used to authenticate the portals administrators Etihad's current Active Directory is well organized and filled with the proper data about the users The system error messages will be handled as per SharePoint 2010 out of the box (no custom error messages handling) Software licenses to be provided by Etihad Cargo before deployment phase. Cargo team will provide complete VPN access control to the staging and production environments for "offshore" remote testing. Cargo team will provide multiple VPN users access accounts to allow multiple assigned quality engineers to test the portal. No single sign on for WebDocs application with new website, the forwarder will go onto a link on new website only http://www.tradevision.net/Apps/webDOC/Secure/Login.aspx?ReturnUrl=%2fapps%2fwebDOC%2fcreat e_AWB.aspx%3fSystem%3dEY&System=EY The innovate map can be displayed in a iframe using the HTML below o <Iframe o src="http://etihadcargo.innosked.com/default.aspx?show=MAP" o scrolling="no" o frameborder="0" o width="100%" o height="500"> o </Iframe> Flight Schedule integration (freights & trucks) fo r the flight schedule one file (CTI_New.txt) will be uploaded onto \\eyapps2\fltschedule and Etihad Airways Cargo team will provide full control/access on shared directory. An example of the file provided by Cargo team and the definition is identified in the table sent by cargo team interface specifications document o For the schedule will need fields,2,19,3,4,5,6,7,8,16,17,34,35 Flight Status integration For the flight schedule one file (CTI_New.txt) will be up loaded onto \\eyapps2\fltschedule and Etihad Airways Cargo team will provide full control/access on shared directory. An example of the of the file provided by Cargo team and the definition is identified in the table sent by cargo team interface specifications document o For the schedule you will need fields,3,4,5,6,7,8,9,10,15,18,19,20,21,34,35 Shipment Tracking : Cargosport integration When the AWB is entered into the website and track button is triggered it executes an event the below URLS is hit along with the airway bill number o This is the Cargo tracking URL: http://10.200.200.22:8080?/CargoTrack/servlet/trackHandler SMS interface will be an instruction/content and informational page only. Cargo team will provide the technical team with ready VMs operating system. The following features still have pending requirements from the client side, these requirements should be finalized before the start of the development and they might have cost implications. o Contracts database library and workflow, and this will be a complex workflow o Processing of Ground Handling (GHA) Invoices workflow, and this is a complex workflow (more details in section 6.2.3)

o A workflow to allow for amendments to the CMS manuals to be sent out and confirmation to then be received and tracked that GSAs have received and read the amendments , this workflow will have three follow ups and escalation feature Workflows data will be saved in SharePoint lists. Viewing the different requests will be based on SharePoint out of the box provided features such as creating list views and so on. No special data storage or data structure is assumed for future reporting phase. Integration with Microsoft lync to provide the logged in user with: Check who are the online users Online chatting with the available users Sharing documents Office integration which allows logged in users to view MS office documents on their browsers Both Micrososft lync and office integration would require hardware support and licenses which are out of the project scope
Formatted: Font: +Body (Calibri) Formatted: Justified, Indent: Left: 0.5", Space Before: 6 pt, After: 6 pt, Don't add space between paragraphs of the same style, No bullets or numbering, Tab stops: Not at 0.5"
Formatted: Font: +Body (Calibri) Formatted: Tab stops: Not at 0.5"
o o
Portal Overview
3.1 Logical architecture
3.2 Graphical Design

For best demonstration of the look-and-feel for Etihad portal, ITWorx Artwork & User Experience team created sample screenshots with different designs for the portals homepage and inner pages in English. These designs are just Preliminary Demo as conceptual designs, and all the proposed sections, links, graphical components or look and feel styles are just used as proof of concept and subject to any changes or totally redesign based on information architecture and usability activities upon project start-up.
3.2.1 Look and Feel

For best demonstration of the look-and-feel for Etihad, ITWorx graphics design team created a sample screenshot for home pages and inner pages. This design is just Preliminary Demo as conceptual design, and all the proposed sections, links, graphical components or look and feel styles are just used as proof of concept and subject to any changes or totally redesign based on information architecture and usability activities upon project start-up. Through customizing master pages and page layouts, ITWorx defines a consistent look and feel for intranet portal to allow Content Editors to easily create new pages following the same site style. The "Page Template" figure illustrates how master and page layouts are used to create new pages.
Figure 1: Page Template
3.2.2 Public area Home Page (Internet)

The system should be delivered with the home page branded relying on the Etihad Cargo visualization guidelines reflecting the (5 stars services & Luxury) of Etihad airways The home page should contain the following sections: Banner Left menu Services (Tabbed) web part o Shipment Tracking (direct interactivity) o Flight Schedule (direct interactivity) o Flight Status (direct interactivity) News web part (to display latest news) Announcements RSS feeds Section with 4 sections o Members Area o Route Map o How can I help you? o Our offices Footer
Glossary of Terms
Table 5 Glossary of Terms Term Web Part SharePoint List OOB CMS RTF Definition A modular unit of information that consists of a title bar, a frame, and content. Web Parts are the basic building blocks of a Web Part Page Are tables of data which stores columns and rows and are like miniapplications in SharePoint Out Of the Box (Features that do not require development) Content Management System Rich text format (this is a field allow users to add a text in a custom colors, fonts, underline and using tables) It also allow users to add photos and links to the text All RTF field function are easy like in Microsoft word LOV AWB List of values Air way bill
Portal User Profiles
Table 6 User Profiles User Group Backend Users Content Editors Add and edit their content, upload images, and change style (fonts, colors, etc.) of the content they are editing without having to install any client application Submit content to Content Approver for reviewing View list of contents returned from Approver and add Approver feedback Content Approver Browse submitted contents from content editors Approve contents or reject and return them to content editors Communication between content editors and Approver is logged where each submission or rejection is recorded separately with comment to clarify transaction (default SharePoint behavior) Content Publisher Portal Administrators Review the Content and publish. Have full access to all site functionalities and assign various roles to users, such as Content Editors and Approvers. Access all portal administrative functions. Public users Browse all the website content except the secure area (members area and How can I help you section). Users who can access the secured area in the website; browsing the members area and use How can I help you section. Extranet users are (GKAs (Global key accounts), GSAs (Global sales accounts), GHAs (Global handling accounts) and stations). Extranet users will have a separate registration form with approval process. Roles/Access
Extranet users
Portal Functional Requirements
The following is the list of the modules which will be delivered in the Public Portal: Public area: (Internet) This area is fully dedicated for the contents which Etihad aims to share with the public world, thus all of its contents will be available for all portal visitors, and also some integrated services will be available to be used by the public users with no need to login e.g. (Track shipment, Flight Status), these services will be detailed later in this document The following is the list of the modules which will be delivered in the public area: # 1Module Flights Schedule Description It will be an integration with the existing system of Flight Schedules, this is to allow the portal visitor to search for a flight schedule using the defined search criteria (Origin & Destination / Arrival date/ Departure date) and get the results listed on the portal with the option to print and download the schedule as an xslx (2007 2010) It will be an integration with the existing system of Track Shipments Just instruction information about SMS service It will be an integration with the existing system of Flight Status A place on the portal to display the Innovata map Content page Content page SharePoint List to display information about the offices, the visitors will be able to view the offices via the visualized editable bing map and through the provided offices list as well Contact page to display cargo team information like in contact us pages Content page + Document library Content pages + Document library Content pages + Inquiry form Like Feedback forms Content page + contact details
2-
Track Shipments
34-
SMS Express Flight Status
5678-
Route Map About Us Vision and Mission Our Offices
9-
Cargo Team
10- Revenue Management 11- Cargo Products 12- Charter Service 13- Sales Team (Cargo Commercial)
14- Freight documents 15- RSS
Document library A bar to display RSS feeds, while Etihad Cargo will provide the RSS sources To present the public Photos, videos and News To present the useful links listed and categorized Hyperlink to open Web Docs external system in a new window Forms for requesting services through a workflow
16- Media center 17- Useful links 18- Link to Web docs
19- Requests forms
Secured area: (Extranet) This area is fully dedicated for the contents which Etihad aims to share with the authenticated extranet users (GHAs & GSAs), thus all of its contents will be available only for the registered and logged in users The following is the list of the modules which will be delivered in the secured area: # 1Module Registration & Login Description The portal will include a registration module that saves users information. This will include a registration form, manage profile form, change password, forgot password, and login. Content pages + Document library
2-
Cargo Service Manual
6.1 Public Area (Internet)

6.1.1 Flights Schedule
The system will integrate with the existing system of Flight Schedules, to get the flight schedule information; this is to allow the visitors to get information about flights relying on updated information The system should allow the portal visitor to search for a flight schedule using the defined search criteria (Origin & Destination / Departure date / Arrival date) and get the results listed on the portal with the option to print and download the schedule as an xslx (2007 2010)
The existing Flight Schedules system will generate a nd upload an excel file including the flight schedule every day onto \\eyapps2\fltschedule; the definition of the file is identified in the table below. Fields mapping 1. Scheduled Departure date - dd/mm/yyyy UTC [Should be the original date, even the flight is rescheduled to another date] 2. Scheduled Departure date - dd/mm/yyyy local station [Should be the original date, even the flight is rescheduled to another date] 3. Carrier code 2-3 letter code 4. Flight number - 901 (only numeric no reschedule indicator) 5. Departure station - 3 letter code 6. Arrival station - 3 letter code 7. Scheduled time of departure - local station 8. Scheduled time of arrival - local station 9. Actual time of departure - local station 10.Actual time of arrival - local station 11.Scheduled time of departure UTC 12.Scheduled time of arrival UTC 13.Actual time of departure UTC 14.Actual time of arrival UTC 15.Flight status - Arrived / Departed / Delayed / Ontime / Rescheduled /Diverted/Cancelled 16.Aircraft registration ID
17.Aircraft type 18.Scheduled Departure Date - Local Station 19. Scheduled Arrival Date - Local Station 20. Actual Departure Date - Local Station 21 Actual Arrival Date - Local Station 22.Scheduled Departure Date - UTC 23. Scheduled Arrival Date UTC 24. Actual Departure Date UTC 25 Actual Arrival Date - UTC 26. Estimated Date of Departure UTC 27. Estimated Date of Departure Local Station 28. Estimated Date of Arrival UTC 29. Estimated Date of Arrival Local Station 30. Estimated Time of Departure UTC 31. Estimated Time of Departure Local Station 32. Estimated Time of Arrival UTC 33. Estimated Time of Arrival Local Station 34. Flight Indicator To identify Cargo , Cargo Charter , Passenger , Passenger Charter , Truck 35. Scheduled Route 36. Arrival Flight No 37. Diverted Station 38. Rescheduled Flight Nr (with reschedule indicator) 39. Rescheduled Departure Date - UTC 40. Reschedule Arrival Date - UTC
41. Rescheduled Departure Time - UTC 42. Reschedule Arrival Time - UTC Notes: The above schedule is the mapped fields in the excel file to the fields For the schedule you will need fields,2,19,3,4,5,6,7,8,16,17,34,35 Users will need to filter out passenger flights with field 34.
Flight schedule functionalities Search Flight Schedule The system should allow the visitors to search the flight schedule The visitor will enter the following search criteria: Type/Length LOV Data Validations Mandatory: Y Updateable: Y Business Rules Single Select from predefined Origins Mapped station Destination LOV Mandatory: N Updateable: Y to: the
Element Label Origin
Departure
Single Select from predefined Destination
the
Mapped to: Arrival station Departure date Date Mandatory: Y Updateable: Y Calendar Should be today or greater Mapped to: Actual time of departure - local station Arrival date Date Mandatory: Y Updateable: Y Calendar, should be greater than departure date Mapped to: Actual time of arrival - local station Type of flight Check box Mandatory: N Updateable: N It will have three options: Scheduled Freight Charter to:
Formatted: Normal, No bullets or numbering Formatted: Font: +Body (Calibri)
mapped Aircraft type
View Flight Schedule

The system will search in the generated file The system should display the results in a table with the following columns sorted by departure date: o Origin o Destination o o o o Flight # (mapped to Flight number - 901 (only numeric no reschedule indicator) field) Departure time Arrival time Scheduled date (mapped to Scheduled time of arrival - local station field)
Formatted: Font: (Default) +Body (Calibri), 11 pt, Not Bold
Note: the above fields are the same fields mapped in the table of fields The following note will be displayed at the top of the results table the following results are sorted by departure date If no results, The system will display an appropriate message to the user The system should allow the visitor to open the results in a printable format view to be able to print it The system should allow the visitor to download the results as an xslx file (2007 2010) Flight schedule section will have a document library, where the user should be able to upload flight schedule file (PDF) and update it regularly and the site users will be able to view and download it
6.1.2 Track Shipments

The system will integrate with the existing system of track shipments, to get the current shipment information; this willthis will allow the visitors to get information about their shipments relying on updated information The system should allow the portal visitor to search for a shipment using the shipment serial number (AWB) and get the results listed on the portal The existing Track Shipment system (Cargospot System) will allow the system to use a web service to send the AWB number, and then the Cargospot System will retrieve the results accordingly
Track shipments functionalities Track Shipment The system should allow the visitors to search for a specific shipment The visitor will enter one or more the shipment serial number (AWB) separated by , AWB will be divided to two fields: o The prefix serial which is a drop-down list o The AWB number which is a text field
View Shipment tracking information The system will integrate with the Cargospot System web service and send the AWB number Cargospot System web service will retrieve the data related to the defined AWBs The system should display the results sorted by flight date in a table with the following columns: o Segment (mapped to: segment field) o Flight # (mapped to: flight number)
o
o o o
Flight Date (mapped to: planned flight date)

Arrival Date (mapped to: actual arrival date) Arrival Time (mapped to: actual arrival date) Pieces (mapped to: no. of pieces)

o Weight (mapped to: weight (pending client)) o Status (mapped to: flight status) User will be able to print the displayed results. A note will be displayed at the bottom of the table illustrating each different status in the table; this note will be fixed.
6.1.3 SMS Express

The system will provide a content page to illustrate the SMS shipment tracking service which will be available for the shipment owners to track their shipments by SMS express service The instructions will include the steps to allow the visitors to subscribe to this service The system will not integrate with any system regarding to this service, but the system will only provide the instructions content page
6.1.4 Flight Status

The system will integrate with the existing system of Flight Status, to get the flight status information; this is to allow the visitors to get information about flights relying on updated information The system should allow the portal visitor to search for a flight status using the defined search criteria (Flight# / Origin & Destination / Departure date / type of flight / type of plane) and get the results listed on the portal The existing Flight status system will generate a text file called CTI_New including all flight statues every 5 minutes, and the generated file will be located at a specific reachable directory, the portal will always use the latest version of the file. Fields mapping 1. Scheduled Departure date - dd/mm/yyyy UTC [Should be the original date, even the flight is rescheduled to another date] 2. Scheduled Departure date - dd/mm/yyyy local station [Should be the original date, even the flight is rescheduled to another date] 3. Carrier code 2-3 letter code 4. Flight number - 901 (only numeric no reschedule indicator) 5. Departure station - 3 letter code 6. Arrival station - 3 letter code 7. Scheduled time of departure - local station 8. Scheduled time of arrival - local station 9. Actual time of departure - local station 10.Actual time of arrival - local station
11.Scheduled time of departure UTC 12.Scheduled time of arrival UTC 13.Actual time of departure UTC 14.Actual time of arrival UTC 15.Flight status - Arrived / Departed / Delayed / Ontime / Rescheduled /Diverted/Cancelled 16.Aircraft registration ID 17.Aircraft type 18.Scheduled Departure Date - Local Station
19. Scheduled Arrival Date - Local Station 20. Actual Departure Date - Local Station 21 Actual Arrival Date - Local Station 22.Scheduled Departure Date - UTC 23. Scheduled Arrival Date UTC 24. Actual Departure Date UTC 25 Actual Arrival Date - UTC 26. Estimated Date of Departure UTC 27. Estimated Date of Departure Local Station 28. Estimated Date of Arrival UTC 29. Estimated Date of Arrival Local Station 30. Estimated Time of Departure UTC 31. Estimated Time of Departure Local Station 32. Estimated Time of Arrival UTC 33. Estimated Time of Arrival Local Station 34. Flight Indicator To identify Cargo , Cargo Charter , Passenger , Passenger Charter , Truck expected to be a drop-down list) (the client will check if they are static values or not) (this field is
35. Scheduled Route 36. Arrival Flight No 37. Diverted Station 38. Rescheduled Flight Nr (with reschedule indicator) 39. Rescheduled Departure Date - UTC 40. Reschedule Arrival Date UTC 41. Rescheduled Departure Time - UTC 42. Reschedule Arrival Time - UTC The above schedule is the mapped fields in the excel file to the fields For the schedule you will need fields,3,4,5,6,9,10,15,18,19,20,21,34,35 Users will need to filter out passenger flights with field 34.
Flight status functionalities Search Flight status The system should allow the visitors to search the flight status The visitor will enter the following search criteria: Type/Length Text Data Validations Mandatory: Y Updateable: Y Origin LOV Mandatory: Y Updateable: Y Business Rules 50 char Mapped to: Flight number Single Select from predefined Origins Mapped station Destination LOV Mandatory: N Updateable: Y to: the
Element Label Flight#
Departure
Single Select from predefined Destination
the
Mapped to: arrival station Departure date LOV Mandatory: N Updateable: Y Single select The system should avail 5 values (current date and 2 days before and 3 days after) Mapped to: Actual time of departure Type of flight LOV Mandatory: N Updateable: Y Single select from the defined types (Scheduled /

Freight / Charter) Mapped to: Aircraft type Type of plane LOV Mandatory: N Updateable: Y Single select The system should generate the list values using the data defined in the CTI_New file for the planes types Pending client
View Flight Status The system will search the in the generate CTI_New text file The system should display the results in a table with the following columns: o Flight # o Origin o Destination o Departure time Scheduled Time of Departure (STD) Estimated or actual Time according to the flight status (EST/ACT) o Arrival time Scheduled Time of Arrival (STA) Estimated or actual Time according to the flight status (EST/ACT) o Status
Formatted
o User should be able to print and download the populated results
6.1.5 Route Map

Innovata map is an already existing tool available from the current cargo portal The system should provide a page including a place to display the Etihad Cargo Innovata map as it is The Innovata map are hosted outside the system, but the system will only avail the page and the space to display this map via provided iframe HTML tag The system will not be responsible for any of the retrieved data on the Innovata map, but this will be Etihad Cargo responsibility
6.1.6 About Us
This will provide the Etihad Cargo visitors with information about Etihad in general and the Cargo Division in more details. This page will be managed by the content editor as an information page For more details about the information page specs and management, please refer to section General Features Information pages
6.1.7 Mission & Vision

This will provide the Etihad Cargo visitors with the vision and mission of Etihad in addition to an overview page. This page will be managed by the content editor as an information page For more details about the information page specs and management, please refer to section General Features Information pages
6.1.8 Our Offices

Through this page the portal visitors will be able to view a list of the offices and service providers addresses in a well presented and easy to find section which will surely get the charm of the visiting public users. In addition to the address information listing, the system will visually represent the locations of the listed facilities on the bing map which is interactive map to make the task of finding the location even more pleasing for the public users. Given that the geo locations will be provided by the Etihad Cargo through implementation phase The system will allow the content editors to define the offices data (please refer to offices fields table) The system will display the offices in a list in addition to the map of locations ( bing Map) This page will be managed by the content editor as a SharePoint List For more details about the SharePoint Li sts specs and management, please refer to section General Features SharePoint Lists Element Label Office Title Type/Length Text Data Validations Mandatory: Y Updateable: Y Country LOV Mandatory: Y Updateable: Y City LOVText field Mandatory: Y Updateable: Y Office TitleAddress TextText Mandatory: Y Updateable: YMandatory: Y Updateable: Y Office telephone Text Mandatory: Y Updateable: Y Fax Text Mandatory: N Updateable: Y Contact Details Text Mandatory: Y Updateable: Y Accepts numbers only 20 Char Accepts numbers only 20 Char 255 Char Select from Cities Lookup (according to the selected country)255 Char 255 Char255 Char Select from countries Lookup Business Rules 255 Char
Description
Text
Mandatory: Y Updateable: Y
1K char
Office telephone
Text
Accepts numbers only
Offices fields
6.1.9 Cargo Team (Contact us)

This will provide the Etihad Cargo visitors with information about different Cargo Teams, and the information about how to communicate these teams This page will be managed by the content editor as an information page For more details about the information page specs and management, please refer to section General Features Information pages
6.1.10 Revenue Management

This will provide the Etihad Cargo visitors with information about Revenue Management Through this page the content editor will have 2 sections to manage its contents: 1- General information about the Revenue Management 2- Revenue Management Documents listing The document listing will be a dedicated document library to display the document related to Revenue Management With each document the system will allow the content editor to add the following fields:
Table 78 Revenue Management documents

Element Label Document Title Type/Length Text Data Validations Mandatory: Y Updateable: Y Document Photo Image Mandatory: N Updateable: Y Description Textopen text Mandatory: N Updateable: Y Meta Data Text Mandatory: N Updateable: Y Document File File Mandatory: Y Please refer to Document 255 Char Select from photos defined in SharePoint 1K char list Business Rules 255 Char

Updateable: Y management section
The system will display the general information section and the document list to the portal visitors in a presentable page This page will be managed by the content editor as an information page and a document library For more details about the information page specs and management, please refer to sections General Features Information pages Document Management & Document library
6.1.11 Cargo Products

This will provide the Etihad Cargo visitors with information about Cargo Products Through this page the content editor will have 2 sections to manage its contents: 1- General information about Cargo Products a. Which can include information about the new destinations, interline News and interline bulletin divisions, also the content editor will be able to add an internal reference (Hyperlink) to Video library(s) and Photo Gallery(s) 2- Cargo Products Documents listing The document listing will be a dedicated document library to display the document related to Revenue Management With each document the system will allow the content editor to add the following fields: Table 89 Cargo Products documents Element Label Document Title Type/Length Text Data Validations Mandatory: Y Updateable: Y Document Photo Image Mandatory: N Updateable: Y Description Textopen text Mandatory: N Updateable: Y Meta Data Text Mandatory: N Updateable: Y Document File File Mandatory: Y Updateable: Y Please refer to Document management section 255 Char Select from photos defined in SharePoint 1K char list Business Rules 255 Char
The system will display the general information section and the document list to the portal visitors in a presentable page This page will be managed by the content editor as an information page and a document library For more details about the information page specs and management, please refer to sections General Features Information pages Document Management & Document library
6.1.12 Charter Service

This will provide the Etihad Cargo visitors with information regarding Charter Service (an offering from Etihad Airways Cargo Division). It will also provide the ability to send an inquiry to the designated person. Through this page the content editor will have the ability to manage the general information about Charter Service, and provide the information about the aircrafts characteristics, aircrafts dimensions, Main deck dimensions and Volume capacity; this will be through providing text and images The system will display the general information section to the portal visitors in a presentable page This page will be managed by the content editor as an information page For more details about the information page specs, please refer to sections General Features Information pages The page will include a document library in addition to the charter service informatio n, please refer to document libraries section for the details. Also the system will allow the visitors to send an enquiry to the designated person An assigned Employee(s) will view these feedback comments and respond to them accordingly through the appropriate channels. Inquiry functionality: Submit inquiry Visitors will be able to enter their inquiries data by filling the appropriate fields and submitting the form (please refer to inquiries fields table) The system will send an email to the dedicated follower informing him that there is a new inquiry submitted; containing link to the inquiry item. The system will forward the inquiry to the follower group, and any user of this group will be able to check the inquiry and deal with it Follow-up The system should allow the administrator to assign a group of followers with the Charter Service inquiries The follower will have the ability to view the submitted inquiries The system will list all sent inquiries in a table showing (sender name, Charter Service Inquiry, status) The list of inquiries should have the paging option to display every (20 configurable) inquiries in a separate page By default the system will sort the inquiries by date (ASC.) The follower will be able to filter the inquiries by (Sender Name / Status) The inquiry item is clickable to open the inquiry in a separate page The system will not archive any reply, but the follower should only be able to change the inquiry status (by changing the value of Status field) The system will not provide the option to allow the followers to reply through the system, but it will be the responsibility of the follower to find the way of communication between him and the sender inquiries statuses are: Checked / Not Checked the default value will be unchecked
Table 910 inquiries fields
Element Label Name
Type/Length Text
Data Validations Mandatory: According to configuration Updateable: According to configuration
Business Rules 255 Char
Email
Email
Mandatory: According to configuration Updateable: According to configuration
255 Char
Charter Inquiry
Service
Text
1K char
6.1.13 Sales Teams page (Cargo Commercial)

This web page presents contact details of the worldwide sales team and their associated offices This page will be managed by the content editor by filling a contacts form for each location and it will be saved in a SharePoint list.as an information page The sales page will be grouped by location (i.e. Middle East sales team), accordingly the user should define all the countries under this location with the contacts information. The following field should be entered for each sales team. Table 1011 Freight documents Element Label Region name Type/Length LOV Data Validations Mandatory: Y Updateable: Y Telephone Text Mandatory: Y Updateable: Y Fax Text Mandatory: N Updateable: Y Address Text Mandatory: Y Updateable: Y Element Label Office Title Type/Length Text Data Validations Mandatory: Y Updateable: Y Business Rules 255 Char 255 Char Accepts numbers only Accepts numbers only Business Rules 255 Char
Country
LOV
Select from countries Lookup
City
Text field
255 Char
Address
Text
255 Char
Office telephone
Text
Fax
Text
Mandatory: N Updateable: Y
Contact Details
Text
255 Char
Description
Text
1K char
This page will include the information related to Global Key Accounts (GKAs) , which will be displayed as a logo listing of all GKAs, and each logo can be linked to an external URL to allow the visitors to open the web site of each GKA For more details about the information page specs and management, please refer to section General Features Information pages
6.1.14 Freight documents

This will provide the Etihad Cargo visitors with a library of specific documents required for specific and/or general cargo shipments. The document listing will be a dedicated document library to display the freight documents The system will display the document grouped by categories With each document the system will allow the content editor to add the following fields: This page will be managed by the content editor as a document library For more details about the document management, please refer to sections General Features Document Management & Document library
Formatted: Font: +Body (Calibri) Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5"
Formatted: Font: +Body (Calibri) Formatted: Font: +Body (Calibri)
6.1.15 RSS
RSS feeds deliver new content and information to users on the topics in which they are interested. The system should be delivered with a bar on the home page to display the RSS feed from the different News providers The news sources will be provided by Etihad Cargo to configure the RSS feeds bar with them.The system should provide RSS control web part that can be configured to load RSS feeds from multiple sources
Formatted: Left Formatted: Font: +Body (Calibri)

The news sources will be provided by Etihad Cargo to configure the RSS feeds bar with them. RSS feed will display the following information: o Title (clickable and redirects to the news item) o A part of the news body (the length is configurable) RSS Feed can be configured with number of news items to retrieve from different RSS sources RSS page sorts news feeds by date
Formatted: Font: +Body (Calibri) Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5" Formatted: Font: +Body (Calibri) Formatted: Font: +Body (Calibri) Formatted: List Paragraph, Bulleted + Level: 2 + Aligned at: 0.75" + Indent at: 1" Formatted: Font: +Body (Calibri)
6.1.16 Media Center

6.1.16.1 Photo Gallery
Etihad Cargo portal administrators will be able to share photos through having an online media gallery available in the portal. The system will be delivered with a ready-made component for the photo gallery, where user will be able to view photos related to Etihad Cargo in a presented photo albums The following are the main functionalities: Manage Album
Formatted: Font: +Body (Calibri) Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5" Formatted: Font: +Body (Calibri) Formatted: Font: +Body (Calibri)
The system should allow the content editor to add / update / delete photo albums (please refer to the album fields table) The system will allow the content editor to set the album cover by selecting the album cover photo The system will allow the content editor to re-assign the album cover image The system should allow the content editor to manage the photos by add / update / delete photos (please refer to the photos fields table) Photos will be classified by album. User should determine the album The photos sizes should be less than 5 MB (the size is configurable in SharePoint) Extensions supported: bmp, gif, jpg, and tiff. The system should allow the end users to browse the albums and view the photos The landing page of the photo gallery will have a listing of all available albums. Each album will be displayed with its thumbnail cover When click on any album it will open the photos viewer page with all the album pictures. By default the viewer will display the first photo of the album The system should display the total number of photos under the opened album If the album has no photos, the system will display a message to the user stating that "No photos in the selected album" The system will list all photos in a thumbnail mode and allow the user to choose the photo to be displayed in the preview mode Additionally, in the preview mode the system will display a set of arrows to allow the user to scroll through album photos. With each photo the system will display its related data (title, description)
Manage Photos
View Photo gallery
Request a photo
[The National Airline of the United Arab Emirates Etihad Airways] The system should allow the end users to request a photo with high resolution. End user will fill the request form with the following fields: Name: text field (mandatory, 255 Char) Email: text field (mandatory, mail validation) Reason: text area (mandatory, 1K) The system will automatically send an email to the marketing department (configured email address) with the request. The email notification will include the form information filled by the requester in addition to the image name. The marketing team will handle the requests manually outside the system.
Formatted: Indent: Left: 0.44", Tab stops: 0.69", List tab + Not at 0.44"
Table 1114 Albums Fields Element Label Album Name Type/Length Text Data Validations Mandatory: Y Updateable: Y Album Photo Cover Browse Mandatory: NY Updateable: Y NA Business Rules 255 Char
Table 1215 Photos Fields Element Label Album Type/Length Select Data Validations Mandatory: Y Updateable: Y Photo Browse Mandatory: Y Updateable: Y Title Text Mandatory: Y Updateable: Y Description Text Mandatory: N Updateable: Y 1K char From the uploaded images on SharePoint lists 255 Char Business Rules From defined albums
6.1.16.2 Media Electronic marketing

This section will be the same as photo gallery section but for displaying the marketing content like brochures and flyers for the public users.
6.1.16.3 Electronic Data Marketing EDMs

This section should allow the user to send marketing materials online through the portal
Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5"

User should be able to upload a document to the site and select user groups to send them the email Additionally user should be able to add the email body and title System will send automatically the email notification to the selected users
Formatted: No bullets or numbering
Table 1316 EDMs Fields Element Label Document name Type/Length Text Data Validations Mandatory: Y Updateable: Y Document File upload Mandatory: Y Updateable: Y Description Text area Mandatory: N Updateable: Y Formatted: Font: 10 pt Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5"
NA
NA
6.1.16.36.1.16.4 Video Libraries

Etihad Cargo portal administrators will be able to share videos through having an online video library available in the portal. The system will be delivered with a ready-made component for the video library, where user will be able to play videos related to Etihad Cargo The following are the main functionalities: Manage categories
The system should allow the content editor to manage the videos categories by add / update / delete the categories (please refer to the categories fields table) The system should allow the content editor to manage the videos by add / update / delete videos (please refer to the videos fields table) Videos will be classified by category. The video size should be less than 50 MB (50 MB is the default size at SharePoint Asset Library Which can be configured to max size 2047MB) Extensions supported: WMV (WMV is the only supported extension for SharePoint OOB Media Player Web Part.) Videos will be stored in SharePoint 2010 "Asset Library" The system should allow the end users to browse the video library and play the videos The landing page of the video library will have a listing of all available videos categories. The system should display the total number of videos under each category When click on any category it will open the video player page with a list of all videos under the selected category. By default the player will play the first video in the selected category
Manage Videos
Browse & Play Videos
[The National Airline of the United Arab Emirates Etihad Airways] Additionally, the system will display a set of arrows allowing the user to scroll through categorys videos. If the category has no videos defined, the system will display a message to the user stating that "No videos in the selected category" End users will be able to select a specific video to play it With each video the system will display its related data (title, description)
Table 1416 Video Categories Fields Element Label Category Name Type/Length Text Data Validations Mandatory: Y Updateable: Y Description Text Mandatory: Y Updateable: Y Category Photo Cover Browse Mandatory: Y Updateable: Y NA 255 Char Business Rules 255 Char
Table 1517 Video Fields Element Label Category Type/Length Select Data Validations Mandatory: Y Updateable: Y Videos Browse Mandatory: Y Updateable: Y Title Text Mandatory: Y Updateable: Y Description Text Mandatory: Y Updateable: Y 1K char From the uploaded videos on SharePoint lists 255 Char Business Rules From defined categories
6.1.16.46.1.16.5 News
The portal content editors should be able to post news on the Etihad Cargo portal. This gives the end user the ability to View the latest Etihad Cargo news By clicking on the news title, the user will be able to View the news details. The news will be added and maintained by Etihad Cargo news content editor from the SharePoint administration site
News supported Functions: Manage News Important news can be marked to be featured in the Portal homepage highlights and rest of news can be viewed as well in case the user selects view all news. The content editor will have the ability to manage the news through SharePoint; through viewing a list of all already published News items. The editor can add new item, update any of the already published news, and also choose a certain news item to delete.
News highlights on Homepage The system will allow the content editors to define the items to be displayed on the highlights on Homepage section, the most recent published and marked as "Featured news items will be displayed in the portal homepage spotlights area. Selected item titles are displayed in the highlights web-part. When the title is clicked the item details are displayed. Highlights on Homepage dynamically show items in a graphically attractive way. The user can cycle through various items and see more than the few ones shown at the page load. Each item has a details page to show more information about it.
View News details The system will allow the end user to view a list of all defined news The news landing page will have the option to display the featured news (marked as: featured) in a film strip view with arrows to display next and previous news The news landing page will have the option to display a list of all other defined news With each news item in the list, the system will display date, title, image and summary User can access the details of every published news item by open the news title. The system will display the news details in a separate view
Table 1618 - News Fields Element Label News title Type/Length Text Data Validations Mandatory: Y Updateable: Y News summary Text Mandatory: Y Updateable: Y News image Image Picker Mandatory: N Updateable: Y Select from photos defined in SharePoint list 255 Char Business Rules 255 Char
News date
Date
Mandatory: Y Updateable: Y Gregorian, (dd/mm/yyyy)
N/A
News Details Content Featured
RTF
N/A
Boolean
NA
6.1.17 Useful links

The "Useful Links" section will display a hyperlinks list container web part, which is used to allow portal users to open other URL's. It allows the users to reach relevant sub sites and pages, or even external websites of government or private entities easily. The portal will allow the content editor to manage these links by add/update/delete them. This is done through the Portal administration website. For each of the useful links displayed, contents editor user should input the following information:
Table 1719 Useful Links Fields

Element Label Category Type/Length Lookup Data Validations Mandatory: Y Updateable: Y URL HyperLink hyperlink Mandatory: Y Updateable: Y 255 char Business Rules NA
6.1.18 Link to Web docs

The link to Web docs will be in the form of Hyperlink to open Web Docs external system in a new window This will be represented by an appropriate icon
6.1.19 Social networks links

The Social networks links will be in the form of Hyperlinks to open in a new window the pages of (Twitter Facebook - Youtube) channels of Etihad Cargo, and Etihad will provide the URLs This will be represented by an appropriate icon
6.2 Secured Area (Extranet)

This area is fully dedicated for the contents which Etihad aims to share with authenticated extranet users (GHAs & GSAs), thus all of its contents will be available only for the registered and logged in users
6.2.1 Registration & Login

The Portal will include a registration module that saves users information. This will include a registration form, update profile, change password, forgot password, and login.
6.2.1.1

Register & update profile (Agents)
The system should allow the agents to register their account The system should request from the agent users to fill in the registration form After agents register their account, the system should consider the account as inactive account The system should forward the registration form to a predefined approver (Etihad Employee) to review the registered data and approve it The request status will be pending approval and it will be displayed for the user in a list with the requester information (title, name, IATA/CASS #, mail and country) Also the system will send an email to the approver telling him that there is a new registration request pending his approval Approver will be able to take two actions: Reject the request: accordingly this will send to the requester an email notifying him that his request has been rejected. Approve the request: Once the registration form approved by the approver, the system will consider the account as authorized agent and the system will activate the account The system will notify the agent via email that his account has been activated The agent will be able to login the system to access sections available for registered agents only The system should allow the agent to update their profiles according to the data validations in the registration form User should add his Crystal cargo ID in the registration form, to identify him later in the reports and the workflows Table 1820: Agent registration form fields Element Label Contact Details Agent Title LOV Mandatory: Y Updateable: Y Agent Name Text Mandatory: Y Updateable: Y Contact Person Text Mandatory: Y Updateable: Y Crystal ID cargo Text Mandatory: Y Updateable: Y Not defined yet from the client side 255 Char From a list of agents types (Agent GSSA/GSA/CSA GHA) 255 Char Type/Length Data Validations Business Rules
IATA/CASS number Country
Text
255 Char
LOV
Select from countries Lookup
City
LOV
Select from Cities Lookup (according to the selected country) Separated to 3 fields Country code (3 digits) Area code (5 digits) Number (10 digits) The user should be able to add one or more phone or mobile number
Phone Number
Numeric
Fax Number
Numeric
Separated to 3 fields Country code (3 digits) Area code (5 digits) Number (10 digits)
Mobile Number
Numeric
Separated to 3 fields Country code (3 digits) Area code (5 digits) Number (10 digits)
Email
email
Mandatory: Y Updateable: N Unique: Y
N/A
Address
Text
255 Char
E-booking Contact Name/Number Password
Text
14 char
password
Mandatory: Y Updateable: N
Eight characters password with strength check Should be same the previous "password"
Confirm
password
Mandatory: Y

password Updateable: N field
6.2.1.2

Login
Agents will have the ability to login to the portal using the email and password When login, the agents will be able to access the portal secured area (Extranet)
Table 1921 - Login Element Label Email Type/Length email Data Validations Mandatory: Y Updateable: Y Password password Mandatory: Y Updateable: Y At least Eight characters password with strength check Business Rules N/A
6.2.1.3

Change password
System should allow agents to change the password. Agents will be able to enter the "change password" form The system will save the new password Agents will use the new password for the next login
Table 2022 - Change Password Element Label Password Type/Length password Data Validations Mandatory: Y Updateable: Y New password password Mandatory: Y Updateable: Y Confirm password password Mandatory: Y Updateable: Y Business Rules Eight characters password with strength check Eight characters password with strength check Should be same the previous "new password" field
6.2.1.4

Forgot password
The agents will have the ability to request from the system to send him an email with his password System requests from the agent to enter his email System sends an email to the agent with the password that match the email entered System inform the user that his password has been sent to him, this will be via appropriate message
Table 2123 - Forgot Password Element Label Type/Length Data Validations Business Rules
Email
Email
N/A
6.2.2 How can I help you?

The portal will include an area for the registered users for requesting services from Etihad cargo; these requests will start automated workflows for delivering and processing the requests. Requests will be divided to two sections: Basic requests: these requests will be one step workflow and it basically requires from the user to fill a form with the needed information and submit it; accordingly it will be sent to the responsible department/user Complicated requests: these requests will be two or more steps and it requires more interaction between the user and the reviewers/approvers.
The following are the shapes definition that will be used in modeling the system workflows: Shape Definition Shows a process, task, action, or operation. It shows something that has to be done or an action that has to be taken. Note: system or email notifications are considered as a process or an activity performed by the system. This shape tells you where the workflow starts.
Start
Workflow has only one start point. This shape tells you where the workflow ends. Workflow could have many end points. Refers to an external process that is defined elsewhere.
No
Yes
This shape refers to decision asks a question. The answer to the question determines which arrow you follow out of the decision.
The lines with arrows determine the flow through the workflow process (workflow processes will be numbered for traceability). This line indicates that the step is optional. P N S Refers to process Refers to a notification or message sent by the system Refers to the status of the strategy item at each action
[The National Airline of the United Arab Emirates Etihad Airways] 6.2.2.1 Basic requests
The following workflow steps will be applied on the following requests, but each request will have a different form to be submitted at the beginning of the workflow (forms are defined below in requests data entry forms section after the workflow steps). Request a booking o General goods o Dangerous goods o Perishable goods o Art and precious goods o Make a fast track booking Request information Provide feedback: o Raise a claim o Send a compliment o Register a comment Send a complaint Ship valuable and vulnerable goods Book a charter
Basic Workflow Requester/User Portal Backend Approver (Department/User)
Start
Fill the request information P1
Submit the form for processing P2 Send notification to receiver N1 Receive notification P3
Send notification to requester N2
Yes
Appro ve No
Add comments and submit P4
This diagram shows the basic workflow

Basic workflow steps are as follows: P1 The requester/user will add the request information to the data entry form. P2 The requester/user will send the request form by clicking submit button (the request status
Yes will be pending approval).
N1 The system will automatically send an email notification to the approver (department/user) to notify him with the new request. P3 Approver will receive the notifications in his tasks list in the system in addition to his Email account added in the system. Approver will view the request details by clicking it in his tasks list. N2 If the approver approved the request then the system will automatically send an email notification to the requester notifying him that his request has been approved (the request status will turn to approved)

P4 If the approver rejected the request then he will be able to add some comments (Feedback) to the request screen and send it to the requester (the request status will turn to rejected) N3 The system will automatically send an email notification to the requester notifying him that his request has been rejected.
6.2.2.1.1 General business rules

Basic workflows have only one approval step. Workflow doesnt support escalation or delegation Notifications are fixed and cant be configured. All notifications will be through email. The approver will be configurable for each request type. Approvers tasks will be assigned in SharePoint task lists Approver should add a comment/feedback in case of rejection.
6.2.2.1.2 Workflow notifications

ID N1 Condition Requester submitted the request Notification type Email notification Notification A new request request type/name + request number has been submitted for approval Link to access the request directly from the email N2 Approver clicked Approve option Approver clicked reject option Email notification Your request request type/name + request number has been approved Your request request type/name + request number has been rejected Display the approver comments
N3
Email notification
6.2.2.1.3 Requests data entry forms

6.2.2.1.3.1 Request a booking form
The information inserted in this form will be generated in FFR extension and sent to cargo spot system email accordingly cargo spot will handle all the next steps even the notifications that will be sent to the requester. Cargo spot email and the FFR file format will be specified by the client. Element Label Type/Length Data Validations Business Rules
AWB
Drop-down list + text field
- Drop-down list will have the carrier code of the AWB (3 characters) - Text area for one or more AWB up to 10 max numeric separated with semi-colons - A note will be displayed under the field please add AWBs with semicolons separated Drop-down list will have the prefix of the AWB (3 characters) Text field will have the rest of the 14 characters
Formatted: Indent: Left: 0", Hanging: 0.16", Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5"
Shipment Details Section Shipment type Drop-down list Mandatory: Y Updateable: Y Drop-down list values: General Dangerous goods Perishable goods Art and precious goods Make a fast track booking
According to the selected option, shipment details section will display different information General and art and precious goods options fields in shipment type drop-down Commodity Text field Mandatory: Y Updateable: Y No. of pieces Text field Mandatory: Y Updateable: Y Total weight Text field + drop-down list Mandatory: Y Updateable: Y Max: 4 characters Accepts number only Text field: Max: 4 characters Accepts numbers only 255 Char
Drop-down list: displays a

look-up with the available measurements Dimensions (Length (L), width (W) and height (H)) 3 text fields Mandatory: Y Updateable: Y Max: 4 characters Accepts number only User will have the option to add another dimension (up to 20 records) Label (calculated field) NA Will be calculated according to the supported weight and dimensions (formula to be supported by the client)
Volume
Dangerous goods fields SHC 9 text fields Mandatory: Y Updateable: Y - Each text field can take up to 3 characters - When clicking the field name; a pop-up with SHCs list will be displayed (SHC name and code with check box beside each row) - When the user checks one of the SHCs, its code will be populated directly to one of the 9 text fields - The populated text fields will be disabled with the mapped values Dangerous goods class UN number Drop-down list Mandatory: Y Updateable: Y Text field Mandatory: N Updateable: Y Perishable goods fields SHC 9 text fields Mandatory: Y Updateable: Y - Each text field can take up to 3 characters - When clicking the field name; a pop-up with SHCs list will be displayed (SHC name and code with check box beside each row) - When the user checks one of the SHCs, its code will be The drop-down list will display values from 1 to 9 100 Char

populated directly to one of the 9 text fields The populated text fields will be disabled with the mapped values Temperature requirements (From - To) Two text fields Mandatory: Y Updateable: Y - Display inside from field min text -o Accepts 2 characters - Display inside to field max text -o Accepts 2 characters - Display Celsius sign as a label beside the fields Make a fast track booking fields XPS Text field Mandatory: Y Updateable: Y - Text field can take up to 3 characters - When clicking the field name; a pop-up with XPSs list will be displayed (XPS name and code with check box beside each row) - When the user checks one of the XPSs, its code will be populated directly to the text field - The populated text fields will be disabled with the mapped values - A link will be displayed beside the field; on clicking it a list with all the stations that provide this service will be populated and the user will have the option to print it. Transport Details Section Origin Drop-down list Mandatory: Y Updateable: Y Destination Drop-down list Mandatory: Y Display a look-up with all countries Display a look-up with all
Formatted: Indent: Left: 0.25", Hanging: 0.25" Formatted: Indent: Left: 0.25", Hanging: 0.25"

Updateable: Y Preferred date Date Mandatory: Y Updateable: Y Preferred flight Text field Mandatory: N Updateable: Y Shipper details section Name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Address Text field Mandatory: Y Updateable: Y City Text field Mandatory: Y Updateable: Y Zip code Text field Mandatory: Y Updateable: Y Country code Text field Mandatory: Y Updateable: Y Consignee Details Section Name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Address Text field Mandatory: Y Updateable: Y Accepts numbers only 20 Char 100 Char Email validation 255 Char 255 Char 100 Char Accepts numbers only 100 Char Accepts numbers only 255 Char Accepts numbers only 20 Char 255 Char Email validation 255 Char 255 Char NA255 Char countries NA
City
Text field
255 Char
Zip code
Text field
Accepts numbers only 100 Char Accepts numbers only 100 Char
Country code
Text field
6.2.2.1.3.2 Request information form

The information inserted in this form will be sent to the customer service team email. Note: email of the approver will be configurable. Element Label Name Type/Length Text field Data Validations Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Request Text area Mandatory: Y Updateable: Y Accepts numbers only 20 Char Email validation 100 Char 1K Char Text area will display the following text inside it with grey color; when the user clicks it the text will disappear Id like to Business Rules 255 Char
6.2.2.1.3.3 Provide feedback form

This form will have the following three categories Raise a claim: will be sent to cargo claim department email Send a compliment: will be sent to customer service department Register a comment: will be sent to customer service department
Raise a claim form

Element Label AWB
Type/Length Drop-down list + text field
Data Validations Mandatory: Y Updateable: Y
Business Rules - Drop-down list will have the carrier code of the AWB (3 characters) - Text area for one or more AWB up to 10 max numeric separated with semi-colons - A note will be displayed under the field please add AWBs with semicolons separated Drop-down list will have the prefix of the AWB (3 characters) Text field will have the rest of the 14 characters
Customer Information Claimant name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Brief description Text area Mandatory: Y Updateable: Y Supporting documents File browsing button + text field Mandatory: N Updateable: Y - User can upload one or more file and describe it using the text field - Max. file size 2M
255 Char
Accepts numbers only 20 Char Email validation 100 Char 255 Char
Send a compliment and register a comment forms

Element Label AWB Type/Length Drop-down list + text field Data Validations Mandatory: Y Updateable: Y Business Rules - Drop-down list will have the carrier code of the AWB (3 characters)

Text box Drop-down list will have the prefix of the AWB (3 characters) Text field will have the rest of the 14 characters Customer Information Claimant name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Compliment/Comment Text area Mandatory: Y Updateable: Y Accepts numbers only 20 Char Email validation 100 Char 1K Char 255 Char
Formatted: List Paragraph, Indent: Left: 0", Hanging: 0.16", Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5"
6.2.2.1.3.4 Make a complaint form

This form will have the following categories: Didnt fly as booked Missing cargo Missing documents Split shipment Cargo damaged Cargo pilfered Shipment perished Delayed shipment
Didnt fly as booked form

Element Label AWB Type/Length Drop-down list + text field Data Validations Mandatory: Y Updateable: Y Business Rules - Drop-down list will have the carrier code of the AWB (3 characters) - Text box Drop-down list will have the prefix of the AWB (3 characters) Text field will have the rest

of the 14 characters Booked flight & date Text field + date Mandatory: Y Updateable: Y Text field accepts numbers only 100 Char Comments Text area Mandatory: Y Updateable: Y Customer Information Name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Address Text field Mandatory: Y Updateable: Y Country Drop-down list Mandatory: Y Updateable: Y City Text field Mandatory: Y Updateable: Y Zip code Text field Mandatory: Y Updateable: Y Accepts numbers only 100 Char 255 Char Accepts numbers only 20 Char Email validation 100 Char NA 255 Char Look-up with all countries 255 Char 1K Char
Missing cargo form

Element Label AWB Type/Length Drop-down list + text field Data Validations Mandatory: Y Updateable: Y Business Rules - Drop-down list will have the carrier code of the AWB (3 characters) Text box Drop-down list will have the prefix of the AWB (3 characters)
Text field will have the rest of the 14 characters Total no. pieces Gross weight of Text field Mandatory: Y Updateable: Y Text field + drop-down list Mandatory: Y Updateable: Y Max: 4 characters Accepts number only Text field: Max: 4 characters Accepts numbers only
Drop-down list: displays a look-up with the available measurements No. of missing pieces HAWB (hause airway bill) Provide description for the missing pieces Comments Text field Mandatory: Y Updateable: Y Text field Mandatory: Y Updateable: Y Text area Mandatory: Y Updateable: Y 1K Char Max: 4 characters Accepts number only 100 Char
Text area
1K char
Customer Information (the same like didnt fly as booked form)
Cargo damaged form

Element Label AWB Type/Length Drop-down list + text field Data Validations Mandatory: Y Updateable: Y Business Rules - Drop-down list will have the carrier code of the AWB (3 characters) Text box Drop-down list will have the prefix of the AWB (3 characters) Text field will have the rest of the 14 characters Total no. of Text field Mandatory: Y Max: 4 characters

pieces No. of damaged pieces Extent damage of Text field Updateable: Y Mandatory: Y Updateable: Y Drop-down list Mandatory: Y Updateable: Y Accepts number only Max: 4 characters Accepts number only Look-up table with the following values: Comments Text area Mandatory: Y Updateable: Y Supporting evidence File browsing button + text field Mandatory: N Updateable: Y - User can upload one or more file and describe it using the text field - Max. file size 2M Customer Information (the same like didnt fly as booked form)
Inner packing damage Outer packing damage Crushed Wet
1K Char
Cargo pilfered form

Element Label AWB Type/Length Drop-down list + text field Data Validations Mandatory: Y Updateable: Y Business Rules - Drop-down list will have the carrier code of the AWB (3 characters) Text box Drop-down list will have the prefix of the AWB (3 characters) Text field will have the rest of the 14 characters Description Text area Mandatory: Y Updateable: Y Supporting evidence File browsing button + text field Mandatory: N Updateable: Y - User can upload one or more file and describe it using the text field Max. file size 2MUser can upload one or more file and 1K Char

describe it using the text field Customer Information (the same like didnt fly as booked form)
Shipment perished, missing documents, split shipments and delayed shipments form
Element Label AWB Type/Length Drop-down list + text field Data Validations Mandatory: Y Updateable: Y Business Rules - Drop-down list will have the carrier code of the AWB (3 characters) Text box Drop-down list will have the prefix of the AWB (3 characters) Text field will have the rest of the 14 characters Origin Drop-down list Mandatory: Y Updateable: Y Destination Drop-down list Mandatory: Y Updateable: Y Total no. pieces Gross weight of Text field Mandatory: Y Updateable: Y Text field + drop-down list Mandatory: Y Updateable: Y Display a look-up with all countries Display a look-up with all countries Max: 4 characters Accepts number only Text field: Max: 4 characters Accepts numbers only
Drop-down list: displays a look-up with the available measurements Comments Text area Mandatory: Y Updateable: Y Customer Information (the same like didnt fly as booked form) 1K Char
6.2.2.1.3.5 Ship valuable and vulnerable form

This request will be sent to customer service team
Element Label Name
Type/Length Text field
Telephone
Text field
Accepts numbers only 20 Char Display a look-up with all countries Display a look-up with all countries 1K Char
Origin
Drop-down list
Destination
Drop-down list
Description goods Station
of
Text area
Text field
255 Char
6.2.2.1.3.6 Book a charter form

The information inserted in this form will be sent to the customer service team email. Element Label Name Type/Length Text field Data Validations Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Origin Drop-down list Mandatory: Y Updateable: Y Destination Drop-down list Mandatory: Y Updateable: Y Description Text area Mandatory: Y Updateable: Y Accepts numbers only 20 Char Email validation 100 Char Display a look-up with all countries Display a look-up with all countries 1K Char Business Rules 255 Char
6.2.2.2
Complicated requests
The following workflow steps will be applied on the following requests, but each request will have a different form to be submitted at the beginning of the workflow (forms are defined below in requests data entry forms section after the workflow steps). Ship an animal o Pet o Animals o Horse o Falcons Ship a car Ship human remains
Complicated requests Requester/User Portal Backend Customer service Network
Start
Fill the request information P1
Send notification to Network N2

No
Submit the form for processing P2
Origin country=
Abudhabi Yes
The same steps applied for the customer service will be applied for the network P8
Send notification to customer service N1
Receive notification P3
Check documents manually P4

Yes Validate and complete quote No
Receive notification P6
Yes Appro ve No
Send notification to Customer service N5

Send notification to Customer service N5
This diagram shows the complicated workflow

Complicated workflow steps are as follows: P1 The requester/user will add the request information to the data entry form.

P2 The requester/user will send the request form by clicking submit button (the request status will be pending approval). The system will check the origin field; if the origin is Abudhabi then the request will be directed to customer service team email, but if the origin is any other country then the request will be directed to network department email. N1 The system will automatically send an email notification to the customer service team (department/user) to notify him with the new request. N2 The system will automatically send an email notification to the network team (department/user) to notify him with the new request. P3 Customer service team will receive the notifications in his tasks list in the system in addition to his Email account added in the system. P4 Customer service team will prepare the needed documents and the verifications manually outside the system Customer service will have three options: o o o Approve the request and prepared the quote Reject the request Send back to requester
N3 If the customer service approved the request then the system will automatically send an email notification to the requester notifying him that his request has been approved (the request status will turn to approved)
P5 If the customer service rejected the request then he will be able to add some comments (Feedback) to the request screen and send it to the requester (the request status will turn to rejected)
N4 The system will automatically send an email notification to the requester notifying him that his request has been rejected. If the customer service send back the request to requester for more details, the system will send a mail notification to the requester with the needed information where he can open the same form and add the information needed (the request status will be pending approval)
P6 the requester will view the notification send to him where he will be able to approve or rejact the quote N5 if the requester approved the quote, an email notification will be sent to the customer service notifying them that the request has been approved (request status will turn to customer approved)
N6 if the requester rejected the quote, he will be able to add comments and an email notification will be sent to the customer service (request status will turn to customer rejected) P7 The same process will be applied if the request sent to network Note: customer service will be able to add comments at any action (i.e: on approving the request, he should add the quotation details for the customer)
6.2.2.2.1 General business rules

Customer service/network can request information from the customer one or more time without closing the workflow The requester will be able to edit the request when new information requested from him (the form will be opened in the edit mode) The requester will be able to view/list his requests Workflow doesnt support escalation or delegation Notifications are fixed and cant be configured. All notifications will be through email. The approver will be configurable. Approvers tasks will be assigned in SharePoint task lists Approver should add a comment/feedback in case of rejection.
6.2.2.2.2 Workflow notifications

ID N1 Condition Requester submitted the request and the origin = Abudhabi Notification type Email notification to customer service Notification A new request request type/name + request number has been submitted for approval Link to access the request directly from the email N2 Requester submitted the request and the origin not equal abudhabi Email notification to network A new request request type/name + request number has been submitted for approval Link to access the request directly from the email N3 Customer service clicked Approve option Customer service clicked reject option Email notification Your request request type/name + request number has been approved Your request request type/name + request number has been rejected Display the approver comments N4 requester clicked approve option Email notification request type/name + request number has been approved by the requester Display the requester comments N5 requester clicked reject option Email notification request type/name + request number has been rejected by the requester Display the requester comments
N4
Email notification
6.2.2.2.3 Requests data entry forms

6.2.2.2.3.1 Ship an animal form
Element Label Type/Length Data Validations Business Rules
A note will be displayed at the top of the form with the difference between the types of the animals shipped (the note to be provided by the client ) Animal type Drop-down list Mandatory: Y Updateable: Y Drop-down list values: Pets Animal Horse Falcon
According to the selected option, the animal information section will be populated Pet option fields Pet type Drop-down list Mandatory: Y Updateable: Y Drop-down list values: Dog Cat
According to the selected option, pet type and breed fields will be populated Breed Drop-down list Mandatory: Y Updateable: Y Drop-down list values will be populated according to the selected pet type Breeds of dogs and cats will be sent by the client Drop- down will have other option, when the user selects it, the form will populate a text field to add the breed type Age Text field Mandatory: Y Updateable: Y weight Text field + drop-down list Mandatory: Y Updateable: Y Accepts numbers only 4 Char Text field: Max: 4 characters

Drop-down list: displays a look-up with the available measurements Animals options: the same as pet but the following fields will change to: Pet type Animal type Breed Specious A note will be displayed if the selected option is animal shipment should take place between two zoological entities Is this animal controlled by CITIES? Combo boxRadio button Mandatory: Y Updateable: Y - Yes or no option - If the user selected yes, a text filed labeled certificate number will be displayed and it will be mandatory - 100 Char Needed documents File browsing button + text field Mandatory: N Updateable: Y - User can upload one or more file and describe it using the text field - A help note will be displayed beside the field - Max file size 2 M Horses and falcon form will be the same as animal form, but a notification email with the request details will be sent to general manager ground operations Booking information Section Origin Drop-down list Mandatory: Y Updateable: Y Display a look-up with all countries Will have other option, when selecting it a text field will be populated to add the other option Destination Drop-down list Mandatory: Y Updateable: Y Display a look-up with all countries Will have other option, when selecting it a text field will be populated to add the other option Preferred date of Date Mandatory: Y NA

departure Will be accompanying your pet? Combo box Updateable: Y Mandatory: N Updateable: Y Options will be yes and No The field will have a help note beside it when clicking it a pop-up with the help information
Cage information weight Text field + drop-down list Mandatory: Y Updateable: Y Text field: Max: 4 characters Accepts numbers only
Drop-down list: displays a look-up with the available measurements Dimensions (Length (L), width (W) and height (H)) 3 text fields Mandatory: Y Updateable: Y Max: 4 characters Accepts number only User will have the option to add another dimension (up to 20 records) Shipper details section Name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Address Text field Mandatory: Y Updateable: Y City Text field Mandatory: Y Updateable: Y Zip code Text field Mandatory: Y Updateable: Y Country code Text field Mandatory: Y Accepts numbers only 100 Char Accepts numbers only 255 Char Accepts numbers only 20 Char Email validation 100 Char 255 Char 255 Char

Updateable: Y Consignee Details Section Name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Address Text field Mandatory: Y Updateable: Y City Text field Mandatory: Y Updateable: Y Zip code Text field Mandatory: Y Updateable: Y Country code Text field Mandatory: Y Updateable: Y Request a quote option Request quote? a Combo box Mandatory: N Updateable: Y Two options Request a quote Submit for booking Accepts numbers only 20 Char Email validation 100 Char NA 255 Char NA 255 Char Accepts numbers only 100 Char Accepts numbers only 100 Char 255 Char 100 Char
If the user selected request for quote the system will automatically calculate a quote for the requester according to some inputs (inputs and formula to be supported by the client) If the user selected submit for booking user can submit the form directly
6.2.2.2.3.2 Ship human remains form

Element Label Type/Length Data Validations Human remain details Name of the deceased Nationality Text field Mandatory: Y Updateable: Y Drop-down list Mandatory: Y Updateable: Y weight Text field + dropdown list Mandatory: Y Updateable: Y Text field: Max: 4 characters Accepts numbers only Lookup with all nationalities 255 Char Business Rules
Drop-down list: displays a look-up with the available measurements Booking information Section Origin Drop-down list Mandatory: Y Updateable: Y Display a look-up with all countries Will have other option, when selecting it a text field will be populated to add the other option Display a look-up with all countries Will have other option, when selecting it a text field will be populated to add the other option NA
Destination
Drop-down list
Preferred date of departure Flight number
Date
Text field
100 Char
Is the deceased will be accompanied?
Combo box
- Options will be yes and No - The field will have a help note beside it when clicking it a pop-up with the help information - If the user selected yes, the following fields will be displayed to define the accompanying person information o Passenger name (text

field (255 Char and mandatory)) o Ticket number (text field (100 Char and optional)) Local contact number (text field (100 Char and optional with add another option))
Needed documents
File browsing button + text field
- User can upload one or more file and describe it using the text field - A help note will be displayed beside the field - Max file size 2 M
Shipper details section Name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Updateable: Y Email Text field Mandatory: Y Updateable: Y Address Text field Mandatory: Y Updateable: Y City Text field Mandatory: Y Updateable: Y Zip code Text field Mandatory: Y Updateable: Y Country code Text field Mandatory: Y Updateable: Y Consignee Details Section Name Text field Mandatory: Y Updateable: Y Telephone Text field Mandatory: Y Accepts numbers only 255 Char Accepts numbers only 100 Char Accepts numbers only 100 Char 255 Char Accepts numbers only 20 Char Email validation 100 Char 255 Char 255 Char

Updateable: Y Email Text field Mandatory: Y Updateable: Y Address Text field Mandatory: Y Updateable: Y City Text field Mandatory: Y Updateable: Y Zip code Text field Mandatory: Y Updateable: Y Country code Text field Mandatory: Y Updateable: Y 20 Char Email validation 100 Char NA 255 Char NA 255 Char Accepts numbers only 100 Char Accepts numbers only 100 Char
6.2.2.2.3.3 Ship a car form

Element Label Type Type/Length Drop-down list Data Validations Mandatory: Y Updateable: Y Name Text field Mandatory: Y Updateable: Y Model Text field Mandatory: Y Updateable: Y weight Text field + drop-down list Mandatory: Y Updateable: Y Text field: Max: 4 characters Accepts numbers only 255 Char Business Rules Drop-down list values will be supported by the client 255 Char
Drop-down list: displays a look-up with the available measurements Dimensions (Length (L), width (W) and height (H)) 3 text fields Mandatory: Y Updateable: Y Max: 4 characters Accepts number only User will have the option to add another dimension (up to 20 records) Supported with help note
The following sections will be same as ship an animal form Shipper information Consignee information Booking details Request a quote
6.2.3 CMS manuals workflow

Cargo service manual section will have four main libraries o CSM o ECB o CSA o CSF CSM is the main document while the rest are amendments for this document Admin should be able to upload the file and name it Admin should be able to overwrite the file by uploading a new file; the system shouldnt save the old files Admin should be able after uploading a new document to notify the users with it through the following steps: o Select the users he want to notify (public users will be managed in groups (GHAs, GSAs, GKAs, etc) where admin should select the users he want to notify) o Click save button An email notification will be sent to all the selected users with a link with the new document Users should confirm receiving the notification by clicking received link If user didnt confirm receiving the mail within 3 days (configured number of days) he will be reported to a configured user (notification will be through an email) Admin will have a report to list all the users with the status (notified or not notified) Table 2216 CMS Fields Element Label Document library Type/Length LOV Data Validations Mandatory: Y Updateable: Y Business Rules The available values are: o o o o CSM ECB CSA CSF
Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5" Formatted: List Paragraph, Bulleted + Level: 2 + Aligned at: 0.75" + Indent at: 1"
Formatted: List Paragraph, Bulleted + Level: 2 + Aligned at: 0.75" + Indent at: 1"
Formatted: Indent: Left: 0.25", No bullets or numbering
Document name
Text
255 Char
Document
File upload
NA
Description
Text area
NA
Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5" Formatted: List Paragraph
6.2.36.2.4
Invoice verification process
This workflow take place between the suppliers and the finance team, automating this process would help the finance team to control and monitor the invoice verification process in addition to facilitating the process and eliminating the paper work The below diagram will show the process but this is not the final process as its still pending the integration with ARPS system that would affect the workflow steps and information inserted.
Invoice verification process Supplier Accounts Payable (ARPS) Cargo business Cargo finance
Start
Fill invoice information P1
No
Submit the form for processing P2
Dart
Yes No
Log invoice in cargo finance P4
No
ARPS
Verif
Yes
A.P payment P4
Yes
Yes Appro ve No
Send notification to supplier N1
This diagram shows the invoice verification process
6.2.46.2.5
Cargo Service Manual
This will provide the Etihad Cargo registered agents with the ability to download the Cargo service manual in PDF format The Cargo Service Manual will be located in a predefined document library, where authorized content editors will be able to check-in and check-out updating the PDF version. And the system will have an approval workflow configured for publishing the document(s) Through this page the content editor will have 2 sections to manage its contents: 1- General information about Cargo service 2- Cargo service manual Documents listing With each document the system will allow the content editor to add the following fields: Table 2324 Cargo service documents
Element Label Document Title
Type/Length Text
Document Photo
Image
Select from photos defined in SharePoint 1000 char
list
Description
Textopen text
Meta Data
Text
500 char
Document File
File
Please refer to Document management section
The system will display the general information section and the document list to the agents in a presentable page This page will be managed by the content editor as an information page and a document library For more details about the information page specs and management, please refer to sections General Features Information pages Document Management & Document library
6.3 General Features

The following sections will detail the system out of the box features and components
6.3.1 Portal Content Management

The portal is organized in a tree structure. A site collection is the main container for the portal and all content is kept as pages or sub-sites under the same collection. The top-level site provides the global site frame and the pointers to its sub-sites. The site structure characteristics include: The galleries, libraries, master pages, page layouts, images and Cascading Style Sheets under a site collection make consistent branding and navigation for all its sub-sites. Web parts, page layouts, and workflows in a site collection enable consistent authoring experience. A site collection provides unified administration. Sub-sites are ideal for creating unique branding experiences within different sections of the site. SharePoint variations shall be used to created label hierarchies to support different versions of pages and content for different languages or layouts. The portal administration shall be available in English language only
Content approval is a core SharePoint process which is used for publishing documents and content. This process provides the ability to limit the visibility of a document and contents to approvers until the document or content is approved to be published. This will change the security of the document such that all users who have access to the list will be able to view it. When content approval is required for content, a document or content that was changed remains in a pending state until it is approved or rejected by someone who has permission to approve it. If the file is approved, it is

assigned an Approved status in the library, and it is displayed to anyone with permission to view the library. If the file is rejected, its status is updated to Rejected and it remains visible only to the document author and to people with permission to manage lists. A pending document or content is visible only to its author and to the people with permission to manage lists. Each content type has a specific access right, an attribute that makes users edit, review and publish content according to their access rights (default SharePoint behavior) The default SharePoint content publishing workflow will be enabled for all content created on the portal. Content Management System entitles content editor, content approver, and publisher with the following capabilities: Content Editor: Add and edit their content, upload images, and change style (fonts, colors, etc.) of the content they are editing without having to install any client application Submit content to Content Approver for reviewing View list of contents returned from Approver and add Approver feedback
Approver: Browse submitted contents from content editors Approve contents or reject and return them to content editors Communication between content editors and Approver is logged where each submission or rejection is recorded separately with comment to clarify transaction (default SharePoint behavior)
Publisher: Review the Content and publish
All activities related to creating, updating, publishing, and eventually rendering content to end users makes up the publishing process. The end-to-end steps involved with publishing include: Check out content (if editing existing content). Edit and save content. Check in content. Publish content. Approve content via workflow. Deploy content (if necessary). Content goes live based on content scheduling. Content expires based on content scheduling. Update content as needed, beginning this process again at Step 1. Purge or archive content as necessary.
Publishing is the process of creating or editing content, approving content, and publishing content to a production environment. The publishing environment supports advanced editing tools within SharePoint and externally through tools such as Microsoft Office client applications, document versioning and history, scheduling of content, and workflows to manage approvals. The content approval and publishing life cycle will be managed using SharePoint out of the box content approval workflows. Approval workflows will be applied on SharePoint lists and document libraries. Content must be approved by the content approvers or portal administrators prior to being published on the portal. Editing is supported on both public-facing and hidden front-end Web servers that are removed from the load balancer. Editors maintain data, publish updates, and ultimately approve content updates. Prior to the final

approval, all edits are local and not available to the general public. Live rendering of content is governed by the publishing start and expiration dates associated with the content.
6.3.2 Portal Document Management

ITWorx shall implement the SharePoint as document management system, based on SharePoint 2010, key features include creating and browsing secure document repositories; document version control, alerts on documents, searching documents, document approval workflows, managing permissions on document repositories; simplifying, standardizing, and exposing processes by which these documents are created, modified, published, and finally disposed of or retained; searching using Metadata; distribution and alerts automation; checkingin/checking-out policies; documents versioning Document Workflow The document circulates using 3 levels workflow between different users. No validation will be done; the flow is for approval or rejection only.
Accepted Document Types By this feature the portal administrator can configure accepted types of documents such as Excel doc, word doc, Power Point, PDF, Visio, Images and videos to be imported, exported or attached on the portal.
Accepted Document Size The default maximum file size is 50 MB; which is can be increased up to 2 GB, and the maximum number of documents is 30,000,000 per library.
Versioning Support SharePoint document management out of the box features will allow users to keep track the needed version control via checking-in/checking-out policies and document history.
Archiving support SharePoint 2010 out of the box archiving process will be used to implement the needed document a rchiving operations to satisfy users needs.
Document Level Security Authorized users or department will have the capability of controlling access at item level (document, file, etc.) inside the document repository in addition to the folder level.
6.3.3 Document Libraries

The document library in SharePoint is where admin or any appropriate user upload their main or core documents. Document Library is consist of a row and column view with links to the documents, when the document is updated and so is the link is created on the portal. Users can also track metadata of the documents. Meta data in SharePoint is consisting of document properties. The solution will be delivered with the option of publishing the multiple document libraries, with archive of previous issues stored in an out-of-the-box SharePoint document library. Each issue can be downloaded in the form of its type. The system will list the published files in a list with the image of the document, title, brief description and a link to download the document file The system should allow the content editor to upload the files to the researches document library The system will allow the content editors to manage the researches under one level of categorization
Formatted: Normal
6.3.4 Portal Search

The portal enables basic and advanced search through conducting a full text search on all the portal content. The search features are as follows: Support for Arabic and English The administrator is able to define Search Scopes. Search scopes is used to categorize data to make search faster and simple SharePoint search automatically omits all items that the current user performing the search doesnt have access to, and they dont appear in the search results. Portal Homepage contains a simple search text box. The advanced search page link is available from search results page, to help user refine search results if needed.
Simple Search Basic search enables user to search for a word or phrase Search for content from the Search box near the top of the pages on a SharePoint site. The search box is limited to a maximum of 255 characters. The search service automatically ignores common words (Noise/Stop Words) such as the, it, and by, as well as single-digit numbers.
Advanced Search User can choose to display or exclude results by refinements that include certain words, filter search results by scope, and search on content metadata.
Search Results
The search results page displays the number of results that were returned for your search query and the amount of time it took to perform the search query. The system support the paging option when display the results as it will display a configured number of results per page By default, search results are displayed by relevance To sort the list of results by the date when the items were last modified, click View by Modified Date. Each result contains the following data (Linkable result title - Description)
Formatted: Normal - Bullet - Indent - No Space After
6.3.5 Portal Site Map

The site structure will allow for easy navigation of the portal, facilitating the process of finding information for the users. The site hierarchy will have the flexibility of adding/updating any sections when needed. The following are the main functionalities for proposed SharePoint 2010 out of the box portal site map: The portal enables front-end users to view a listing of all sections of the portal, represented in a graphical and hierarchical way; each listing in the site map is a hyperlink to its main page The sitemap displays the site structure as a group of folders containing links. Each folder represents a sub-site and each link is a page or a sub-site inside this sub-site Dynamic sitemap: The sitemap structure is auto generated. The generated sitemap depends on the configured parameters like depth (which can be 3 levels), pages or sites
Integration/Interfaces
The system will integrate with the following systems: System Existing system Schedules of Flight Initiation The existing Flight Schedules system will generate an Excel file including the flight schedule every day, and the generated file will be located at a specific reachable directory Input/output Input: Search criteria (Origin & Destination / Departure date / Arrival date) Output: The system should display the results in a table with the following columns: Origin Destination Flight # Departure time Arrival time
Track Shipment (Cargospot System) system The existing Track Shipment system (Cargospot System) will allow the system to use a web service to send the AWB number, and then the Cargospot System will retrieve the results accordingly
Scheduled date
Input: The visitor will enter the shipment serial number (AWB)
Output: The system should display the

results in a table with the following columns:
Segment Flight # Flight Date Arrival Date Arrival Time Pieces Weight Status
The existing system
Flight
status
The existing Flight status system will generate a text file called CTI_New including all flight statues every 5 minutes, and the generated file will be located at a specific reachable directory The system will search in the latest generated CTI_New file
Input: search criteria (Flight# / Origin & Destination / Departure date / type of flight / type of plane)
Output: The system should display the

results in a table with the following columns:
Flight # Origin Destination Departure time

o o Scheduled Time of Departure (STD) Estimated or actual Time according to the flight status (EST/ACT) Scheduled Time of Arrival (STA) Estimated or actual Time according to the flight status (EST/ACT)
Arrival time
o o
Status
7.1 Hardware Interfaces

N/A
7.2 Software Interfaces

N/A
7.3 Communication Interfaces

HTTP, FTP, SMTP
Logging Requirements
8.1 Hardware requirement
N/A
8.2 Software Requirements

N/A
8.3 Communication Requirements

The above H/W and S/W requirements must be connected and configured within the same network.
8.4 Database Requirements

N/A
8.5 Operations Requirements

N/A
8.6 Regulatory Requirements

This project should comply with the following regulatory requirements: Protection against unauthorized access Following the software development procedures Following the software testing procedures
8.7 Security
ITWorx actively evaluates system's security measures to fortify developed applications against potential threats. This is done through two methodologies; Source Code Analysis and Penetration Testing.
Source Code Analysis entails scanning of the application's code to check for any pieces of code that may introduce system vulnerabilities. On the other hand, Penetration Testing simulates malicious attacks to reveal and resolve an application's potential vulnerabilities by identifying vulnerabilities, defining their associated complexity and business risks, setting priorities, and suggesting mitigation actions.
ITWorx applies Source Code Analysis in the System Implementation phase to make sure the code itself is secure, and detect vulnerabilities early enough in the Software Development Life Cycle to reduce the cost of rework.
ITWorx applies Penetration Testing in the System Testing phase to strengthen system's security through a robust testing methodology, recognized tools and techniques, and a comprehensive set of Penetration Test Categories.
Together, Source Code Analysis and Penetration Testing complement each other to discover a comprehensive set of vulnerabilities to ensure the application's security and reliability.
8.8 Exception Handling

A centralized exception management strategy will be enabled in developed application for consistent handling of exceptions. Implement Exception handling layer will not result in application reliability issues or exposure of sensitive application information.
8.9 Usability
As per wireframes
8.10 Capacity and Performance

ITWorx will be responsible for avail performance testing on developed applications to: Follow SharePoint best practices. Web pages should load in an acceptable amount of time. Optimize the data transfer between the system and the interface as much as possible as the system will be accessed from the internet. Optimize the data storage and attachments.
Other Requirements
9.1 Technology Requirements
Microsoft SharePoint 2010
9.2 Data Migration

N/A
9.3 System archiving concept

N/A
9.4 Availability
The portals shall be available 24/7 and should be functioning at all times.
9.5 Documentation Requirements

N/A
10
Appendix II: Clients Wish List for Future Releases
(Out of Scope Requirements)
11
N/A
Appendix V: Open Issues
Table 2425 Open/Closed Issues Open Issue Justification Decision Maker Date to close
12
Appendix VI: Change Requests

Formatted: Heading 2,Heading 2 Char Char Char Char Char Char Char,Heading 2 Char2,Heading 2 Char1 Char,Heading 2 Char Char Char Char Char Char Char Char Char Char,Second Level Topic,h2,Second Level Topic Char,h2 Char,Sub-heading,sl2,Section 1.1,1.1 Heading 2,H2,l2, No bullets or numbering Formatted: Table Caption, No bullets or numbering
9.6 Registration form changes

The following requirements have been added to the registration requirements (refer to registration and login section 6.2.1) The registration form should include the following fields: Registration form Element Label Agent code Type/Length Text field Data Validations Mandatory: Y Updateable: Y Agent type Drop-drown list Mandatory: Y Updateable: Y The values Region Text field Mandatory: N Updateable: Y First name Text field Mandatory: Y Updateable: Y First name Text field Mandatory: Y Updateable: Y Job Text field Mandatory: N Updateable: Y Department Text field Mandatory: N Updateable: Y Responsibility Drop-down list Mandatory: N Updateable: Y The listed values are: E-booking ACI filling Procurement ECB distribution EDM distribution 255 Char 255 Char 255 Char 255 Char GSA GSSA CSA GHA Business Rules Max: 10 characters
Formatted: Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5"
255 Char
Formatted: Bulleted + Level: 1 + Aligned at: 0.25" + Indent at: 0.5"

Remarks Text area Mandatory: N Updateable: Y The following tables are just look-up tables sent by the client in customer database: o Agent_types mapped to Agent_type field in (agent general sales and agents ground handlers tables) o Cities mapped to city_name field in (agent general sales, agents ground handlers tables and personnel) o Countries mapped to country_name field in (agent general sales, agents ground handlers tables and personnel) o Responsibility mapped to responsibility in (personnel table) Responsibility table in cusromer database will have the following values, and find below the specification for each option: o E-booking: when the user selects this option, he should be able to access request booking form or not Users who dont have this option shouldnt be able to access the form, accordingly it will not be displayed in the requests list in how can we help you section o ACI filling: when the user selects this option, he should add an email address (the system will automatically display a text field), this email address should be sent to cargo spot system (this point is pending on technical details from Etihad) o PINS: when the user selects this option, the system should open a text field for the user to add his PINS ID o Procurement: No action o ECB distribution: to check whether the user should be able to receive ECB and updates or not o EDM distribution: to check whether the user should be able to receive EDM and updates or not o CSA distribution: to check whether the user should be able to receive EDM and updates or not o VPN: when the user selects this option he should add his VPN ID in a text box displayed automatically by the system o Citrix: when the user selects this option he should add his Citrix ID in a text box displayed automatically by the system o Cargospot: when the user selects this option he should add his cargospot ID in a text box displayed automatically by the system User should be able to select one or more responsibility
Formatted: Normal, Indent: Left: 0.25", No bullets or numbering
CSA distribution VPN Citrix Cargospot PINs
1K Char
Formatted: Normal, Indent: Left: 1", No bullets or numbering
Formatted: Indent: Left: 1", No bullets or numbering Formatted: Normal
9.7 Request a booking form changes

The forwarder table in customer database, only the following fields Forwarder_code & Forwarder_Name should be inserted in request booking form Accordingly the data entry form of request booking will add the following fields Forwarder table will not be managed by the system

Etihad Portal Phase1 Srs v5.4 RF Final

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Etihad Portal Phase1 Srs v5.4 RF Final

Загружено:

Авторское право:

Доступные форматы

[The National Airline of the United Arab Emirates Etihad Airways]

Etihad Airways - Implementation of Cargo Website Portal Requirements Specification Document

[The National Airline of the United Arab Emirates Etihad Airways]

Create Create Create

Ahmed Elbaz Ahmed Ashraf Ahmed Ashraf

09/04/2012 20/05/2012 13/06/2012

Pricing & Planning Team Sam O.E. Okpro

[The National Airline of the United Arab Emirates Etihad Airways]

Internal Internal Internal Internal Sign Off

Hossam Eloraby Ahmed Elbaz Ahmed Ashraf Mohamed Rashad

Engagement Manager Systems Analyst Systems Analyst Onsite Team Leader

Table 3: Sign Off Entities Etihad Cargo ITWorx Name Signature

[The National Airline of the United Arab Emirates Etihad Airways]

About the Project................................................................................................................. 9

1.5.1 1.5.2 1.6

Facts, Assumptions, Dependencies, Constraints, Risks ..................................................................... 12

[The National Airline of the United Arab Emirates Etihad Airways]

6.3.1 6.3.2 6.3.3 6.3.4 6.3.5

Integration/Interfaces ................................................................................................... 8074

[The National Airline of the United Arab Emirates Etihad Airways]

Logging Requirements ................................................................................................. 8276

Other Requirements ..................................................................................................... 8478

[The National Airline of the United Arab Emirates Etihad Airways]

[The National Airline of the United Arab Emirates Etihad Airways]

About the Document

1.1 Document Purpose and Scope

1.2 Document Context

1.3 Document Conventions

[The National Airline of the United Arab Emirates Etihad Airways]

About the Project

[The National Airline of the United Arab Emirates Etihad Airways]

1.5 Platform Portals Purpose and Scope

[The National Airline of the United Arab Emirates Etihad Airways]

1.5.2 Out of Scope

[The National Airline of the United Arab Emirates Etihad Airways]

1.6 Facts, Assumptions, Dependencies, Constraints, Risks

[The National Airline of the United Arab Emirates Etihad Airways]

Formatted: Font: +Body (Calibri) Formatted: Tab stops: Not at 0.5"

[The National Airline of the United Arab Emirates Etihad Airways]

3.2 Graphical Design

3.2.1 Look and Feel

Figure 1: Page Template

[The National Airline of the United Arab Emirates Etihad Airways]

3.2.2 Public area Home Page (Internet)

[The National Airline of the United Arab Emirates Etihad Airways]

[The National Airline of the United Arab Emirates Etihad Airways]

Portal User Profiles

[The National Airline of the United Arab Emirates Etihad Airways]

Portal Functional Requirements

SMS Express Flight Status

Route Map About Us Vision and Mission Our Offices

[The National Airline of the United Arab Emirates Etihad Airways]

14- Freight documents 15- RSS

19- Requests forms

Cargo Service Manual

[The National Airline of the United Arab Emirates Etihad Airways]

6.1 Public Area (Internet)

[The National Airline of the United Arab Emirates Etihad Airways]

[The National Airline of the United Arab Emirates Etihad Airways]

Element Label Origin

Single Select from predefined Destination

mapped Aircraft type

View Flight Schedule