Name of Work: Development of new AAI Website and Mobile APPs

Document Title: Scope of Work

ABBREVIATIONS

Sr. No. Acronym Definition

1. AAI Airports Authority of India

2. DC Data Centre, New Delhi

3. DR Data Recovery Centre, Hyderabad

4. AAI Website 1.0 Existing AAI Website (Corporate AAI Website and it’s all subdomains)

5. AAI Website 2.0 New AAI Website (Corporate AAI Website, employee’s portal and it’s all
subdomains including Airports subdomains)

6. AAI Website AAI Website 2.0 including features developed during O&M.

7. Mobile APP Mobile Application

8. AMC Annual Maintenance Contract

9. API Application Programming Interface

10. CHQ Corporate Headquarter, New Delhi

11. DB Database

12. PM Project Manager

13. CERT‐IN Computer Emergency Response Team ‐ India

14. EMD Earnest Money Deposit

15. GIGW Guidelines for Indian Government Websites

16. GUI Graphic User Interface

17. H/W Hardware

18. HTTP Hyper Text Transfer Protocol

19. HTTPS Hyper Text Transfer Protocol Secure

20. ISO International Organization for Standardization

21. JSON JavaScript Object Notation

22. JV Joint Venture

23. LDAP Lightweight Directory Access Protocol

24. MEITY Ministry of Electronics and Information Technology

25. MSME Micro, Small & Medium Enterprises

1|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Sr. No. Acronym Definition

26. O&M Operation & Maintenance

27. OEM Original Equipment Manufacturer

28. OS Operating System

29. OWASP Open Web Application Security Project

30. PBG Performance Bank Guarantee

31. PDF Portable Document Format

32. RCA Root Cause Analysis

33. REST Representational State Transfer

34. RTO Recovery Time Objective

35. RPO Recovery Point Objective

36. SAN Storage Area Network

37. SLA Service Level Agreement

38. SMS Short Message Service

39. SSL Secure Sockets Layer

40. STQC Standardisation Testing and Quality Certification

41. UAT User Acceptance Testing

42. UI User Interface

43. UI/UX User Interface/User Experience

44. VM Virtual Machine

45. VPN Virtual Private Network

46. W3C World Wide Web Consortium

47. SAP‐ESS SAP‐ Employee Self Service

48. PWA Progressive Web Apps

49. OCR Optical character recognition

50. URL Uniform Resource Locator

51. SSO Single Sign‐On

2|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Sr. No. Acronym Definition

52. OSS Open Source Software

53. CRM Customer relationship management

54. ICT Information and Communication Technology

55. BOQ Bill of Quantity

56. O& M Warranty & AMC period

57. Complete Solution AAI Website 2.0 & Mobile APPs

58. All platforms AAI Website 2.0 & Mobile APPs

59. STQC Standardisation Testing and Quality Certification

60. SOW Scope of Work

3|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Scope of work

Airports Authority of India (AAI) intends to advance its digital journey in alignment with the Digital India program of Govt.
of India by transforming the existing AAI Website to one of the world‐class aviation websites. AAI’s digital program aims
to enhance the user experiences of general public, air travellers, employee and other stakeholders. AAI is envisaging that
the digital transformation of Website shall bring an improved experience for users.

AAI desires to improve upon the existing AAI website (AAI website 1.0) and enhance the services. AAI wants to develop
AAI website 2.0 and mobile APPs with addition of new features to AAI website 1.0 as outlined in the below scope of work.
The focus of AAI website 2.0 and mobile APPs would be to provide an upgraded platform to all stakeholders of AAI.

AAI website 2.0 and mobile APPs shall make good use of the latest state of the art ICT solutions, hosting technologies,
development technologies, deployment technologies, location technologies, UI/UX technologies and other related
technologies to provide a comprehensive digital platform to provide various desired features and functionalities needed
for a delightful user experience.

The key objective of project are as follows:

 Development of AAI Website 2.0 for general public and employees.

 Development of Website/Microsites/Subdomains for all AAI Airports
 Development of Mobile APPs for Android & iOS, for employees and other stakeholders
 Deployment of Enterprise based search capability
 Data Migration from AAI website 1.0 to AAI website 2.0 and mobile APPs
 Operation & Maintenance of AAI website 2.0 and Mobile APPs
 Deployment of Manpower in AAI premise
 Training and Capacity Building of AAI officials and end users
 Development of Single Sign‐On and signup system across all the platforms (AAI Website 2.0 & Mobile APPs)
 Development of Integrated Dashboard for different stakeholders
 On‐premise Setup of DevOps Environment for automation of CI/ CD/ CT
 Optimization, backup and Performance Monitoring using various tools
 Integration with third party/AAI services using APIs.
 Audits and Compliances

4|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

1. Design, Development, Testing, Integration, Deployment and Go‐live of new AAI website in the latest technology
1.1. Responsibilities of the Contractor
1.1.1. Design, Development, testing, Integration, Implementation and rollout of the developed AAI Website
2.0 as per requirement mentioned in the RFP and thereafter.
1.1.2. Development of two separate websites:
1.1.2.1. Corporate Website for general public use
1.1.2.2. Web portal for serving and retired employees
1.1.3. Development of separate websites/microsites/subdomains for all AAI Airports.
1.1.4. All the features of AAI website 1.0 to be made available in AAI website 2.0. Please refer Annexure‐D for
list of features of AAI website 1.0. However, the list of features is not exhaustive, contractor may prepare
their own list at the time of SRS, FRS & design with the help of AAI.
1.1.5. To provide the Nodal Officer Dashboard and customized user dashboard in AAI Website 2.0. Please refer
clause 20 for more details.
1.1.6. The request intended for general public information shall not hit internal AAI data.
1.1.7. Development of Single Sign‐On (SSO) and signup system across all platforms. Please refer clause 19 for
more details.
1.1.8. Contractor shall provide customized user Dashboard in AAI Website 2.0 as per clause 20.
1.1.9. On‐premise Setup of DevOps Environment for automation of CI/ CD/ CT. Please refer clause 21 for more
details.
1.1.10. Optimization, backup and Performance Monitoring using various tools. Please refer clause 22 for more
details.
1.1.11. Integration with third party/AAI services using APIs. Please refer clause 23 for more details.
1.1.12. Audits and Compliances. Please refer clause 24 for more details.
1.1.13. Please refer Annexure‐A for scope of work ‐ Common Requirements for Website & Mobile APPs.
1.1.14. Please refer Annexure‐C for scope of work ‐ Guiding Principles for on Premise Deployment.
1.2. Functionality of Website
1.2.1. Front‐end and backend of the AAI website 2.0 shall be integrated but independent of each other
allowing modifications in one without affecting the other.
1.3. Features of Website
1.3.1. AAI Website 2.0 shall support all major internet browsers e.g. Chrome, Firefox, Safari, Edge and other
browsers, including mobile device browsers.
1.3.2. Back end platform shall have in‐built DMS Capability.
1.3.3. AAI Website 2.0 shall be running on SSL i.e. http request should automatically get redirected to https.
1.3.4. AAI website 2.0 shall be designed in a responsive manner so that the rendering of the website is
independent of device screen resolution and aspect ratio.

2. Design, Development, Testing, Integration Deployment and Go‐live of Mobile Apps for Android & iOS in the latest
cross‐platform technology
2.1. Responsibilities of the Contractor
2.1.1. Design, Development, testing, Integration, Implementation and rollout of the developed mobile APP as
per requirement mentioned in the RFP and thereafter.
2.1.2. Development of two separate Mobile APPs
2.1.2.1. Corporate Mobile APP for general public use
2.1.2.2. Mobile APP for serving and retired employees
2.1.3. Launch, install, integrate, scale‐up, test and maintain mobile applications on Android, iOS Platform and
any other prevalent platform with same codebase.
2.1.4. Develop and manage the app with all the appropriate security features as per industry standards.
2.1.5. Shall Ensure regular updating of Mobile APPs to keep it abreast with latest operating system Changes.
2.1.6. Product Delivery should be in the form of a published mobile application on each platform in the market

5|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

place (Google Play store, Apple App store, Mobile Seva App Store) and will be under the AAI accounts of
these stores. No additional payments shall be made to Contractor for publishing of mobile application.
2.1.7. Provide App Design Documentation, App Installation guide, App Administration guide and App User
Operation document to AAI.
2.1.8. Ensure that all interface / license required to connect to iOS, Android etc. will be procured by the
Contractor in the name of AAI without any additional financial implication.
2.1.9. Contractor shall follow cross‐platform development for mobile APP.
2.1.10. Contractor shall ensure that mobile applications shall support the last two measure OS versions (N‐2)
for the respective platforms. N is the current version.
2.1.11. Contractor shall make all efforts to keep the APP as light as possible to ensure fast and responsive design.
2.1.12. Contractor shall ensure that users have access to the latest features, enhancements, and security
patches, maintaining a consistent and secure user experience.
2.1.13. Guidelines for the development of e‐Governance applications (GuDApps) as developed by NIC shall be
followed for the development.
2.1.14. Development of Single Sign‐On (SSO) and signup system across all platforms. Please refer clause 19 for
more details.
2.1.15. Contractor shall provide customized user Dashboard in Mobile APPs as per clause 20.
2.1.16. Front‐end of mobile APPs shall be integrated with the same back‐end services as the AAI Website 2.0.
However, the front‐end of the Mobile APP must be loosely coupled with the back‐end services so that
future changes in either can be implemented with minimum efforts.
2.1.17. On‐premise Setup of DevOps Environment for automation of CI/ CD/ CT. Please refer clause 21 for more
details.
2.1.18. Optimization, backup and Performance Monitoring using various tools. Please refer clause 22 for more
details.
2.1.19. Integration with third party/AAI services using APIs. Please refer clause 23 for more details.
2.1.20. Audits and Compliances. Please refer clause 24 for more details.
2.1.21. Please refer Annexure‐A for scope of work ‐ Common Requirements for Website & Mobile APPs.
2.1.22. Please refer Annexure‐C for scope of work ‐ Guiding Principles for on Premise Deployment.
2.2. Functionality of Mobile APPs
2.2.1. Mobile APPs shall have provision to use the real time information via GPS availability.
2.2.2. Offline Functionality for specified features must be available in Mobile APP. Such list of specified features
will be finalized at the time of design Phase after approval of AAI.
2.2.3. Mobile APP shall be designed in a responsive manner so that the rendering of the APP is independent
of device screen resolution and aspect ratio.
2.2.4. Superfluous permissions asked while downloading the mobile App to be removed.
2.3. Features of Mobile APPs
2.3.1. The applications must include a feature to prompt users to update to the latest version in the event of
a newly published version of the applications. All apps shall be kept updated in terms of
changes/updates undertaken.
2.3.2. Mobile APPs shall support Asynchronous processing, Custom Reporting, analytic services‐ display and
download capabilities, Offline data retention on mobile and Sync to database.
2.3.3. Mobile APPs must be able to send push notifications to respective registered user in order to make
aware about the relevant information.
2.3.4. Mobile APPs shall have provision to conduct selective survey at Airports/CHQ/Regions. The form shall
be customizable according to the need of user. Provision to make geo‐location mandatory for such
surveys shall be made available.

6|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

2.3.5. All applicable features of AAI Website 2.0 to be made available in mobile APPs. However, features of
mobile APPs will be finalized at Design Phase after approval of AAI.
2.3.6. APP design complies with each platform’s advocated, documented design principles. The app shall
comply with Platform’s Human Interface Guidelines, while the Android version follows Material Design
principles.

3. Data Migration from AAI website 1.0 to AAI website 2.0 and mobile APPs
3.1. Contractor shall share execution plan mentioning the detailed data and functionalities to be migrated including
historical data, time variant data, user accounts, content, images, documents (text content, pdf, word, excel
etc.), and any other relevant information from AAI website 1.0 from AAI website 2.0 & Mobile APPs.
3.2. Contractor shall ensure compatibility with new requirements and functionalities while migrating existing data
and functionalities.
3.3. Contractor shall create a comprehensive map of data relationships, structures, and dependencies between the
AAI website 1.0 and AAI website 2.0.
3.4. Contractor shall ensure the quality, accuracy, integrity, completeness and consistency of data by identifying
and cleaning up inconsistencies, errors, and duplicates in the old data.
3.5. Before initiating the migration, perform a complete backup of the data of AAI Website 1.0 to ensure that there
is a fallback option in case of issues.
3.6. Develop a data recovery plan outlining steps to revert to the AAI Website 1.0 in case of unexpected problems.
3.7. Choose appropriate data migration tools or scripts based on the nature of the data and the systems involved.
3.8. Test the migration tools in a controlled environment to ensure they work as expected.
3.9. If the data formats or structures differ between the AAI website 1.0 and AAI website 2.0, develop
transformation scripts to convert data appropriately.
3.10. Plan for parallel operations, allowing both AAI website 1.0 and AAI website 2.0.to coexist during the migration.
3.11. After migration, conduct post‐migration validation checks to identify and address any issues that may have
arisen during the process.
3.12. Monitor the performance of the AAI Website 2.0 after migration to detect and address any performance‐
related issues.
3.13. Ensure compliance with data privacy regulations and policies during the migration process.
3.14. Set the data ownership and access rights in the AAI Website 2.0.
3.15. The overall responsibility of content and Data migration/ porting from the AAI Website 1.0 to the AAI Website
2.0 and mobile APPs is the responsibility of the Contractor.

4. Deployment of Enterprise based search capability through automatic indexing, hashing, meta‐tagging and
versioning including OCR for AAI Website 2.0 and Mobile APPs
4.1. Responsibilities of the Contractor
4.1.1. Shall provide a functionality for full text and document search for all the contents.
4.1.2. Contractor shall implement the Optical character recognition (OCR) in search of content inside scanned
PDF, images, PDF, word and any other uploaded documents. OCR shall be included in each search result.
4.1.3. Contractor shall make provisions to allow users to modify tags if desired, providing flexibility and
customization options to enhance document categorization and organization.
4.1.4. Contractor should provide software based meta‐tagging, auto indexing, hashing and versioning in search
capability.
4.1.5. Contractor shall ensure that the indexing, hashing, tagging and versioning processes are scalable to
handle large volumes of uploaded documents efficiently. Consider optimizing algorithms and
infrastructure for performance and responsiveness. Design the system to handle increased load as the
database grows.
4.2. Functionality of Enterprise Based Search
7|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

4.2.1. In case of global search, it shall be able to search in all the links, sub‐links and shall provide links where
the searched word or phrase is present. On clicking the link, the content shall be displayed.
4.2.2. Shall support for multiple languages (i.e. Hindi, English and other regional languages at Airports
Microsite) in voice recognition and searching. Ensure quick and responsive voice search results to
enhance the user experience.
4.2.3. Integration of search functionality with advanced filters and autocomplete suggestions.
4.2.4. Generate a cryptographic hash (e.g., SHA‐256) of the documents at the time of upload. This hash value
uniquely represents the contents of the document and can be used to verify the document's integrity
and detect any unauthorized modifications.
4.2.5. Compare the generated hash value with existing hashes in the database to identify duplicate documents
or versions. This helps prevent redundant storage and improves data management efficiency.
4.2.6. Conduct comprehensive testing of the integrated OCR and voice search functionalities.
4.2.7. It should have auto completion and auto correction of search words feature along with search facets for
better search functionality.
4.2.8. Should supports synonyms and result rankings. The search engine should be capable of fuzzy search.
4.2.9. The search will ‘intelligently’ guess the intent of the user (through the key word typed in) even when the
key word may not exactly match the one in content. The ‘intelligence’ will be ‘Learned’ by the system
from past uses.
4.2.10. Search result for logged‐in users should be personalized according to their assigned roles and access
privileges.
4.2.11. OCR should also be used to validate the submitted data in the forms as and when required.
4.3. Features of Enterprise Based Search
4.3.1. AAI Website 2.0 & mobile APPs should be capable to display list of links based on the user search.
4.3.2. Implement appropriate security measures to protect sensitive information during document processing
and indexing. This includes encryption of data in transit and at rest, access controls, and adherence to
data privacy regulations.
4.3.3. Incorporate mechanisms for user feedback and quality assurance to validate the accuracy and
effectiveness of automatic indexing, hashing, versioning and tagging algorithms.
4.3.4. Implement pre‐processing, learning and training techniques to enhance OCR accuracy, such as image
cleanup, noise reduction, contrast adjustment, training on AAI data set.
4.3.5. Ensure that voice search is compatible with various devices, including smartphones, tablets, and smart
speakers. Ensure compatibility of voice search across different web browsers. Implement secure
transmission and storage practices for voice data.

5. Supply of SMS gateway for transactional message (for OTP & bulk messages)
5.1. Contractor shall supply SMS gateway for transactional message for sending OTP and bulk messages to users
with total count of 2 lakhs messages.
5.2. In case of third‐party integration, Contractor shall assist AAI team without any financial implication to AAI.
5.3. Additional SMS may be procured as per the quoted rate with same Terms and Conditions, in case AAI desires
to procure additional SMS.
5.4. SMS Gateway shall be available and fully operational as per SLA defined. A dashboard shall be provided to
monitor the same.
5.5. Contractor shall ensure that messages can be sent to user on 24x7 basis.
5.6. There shall be provision to deliver automated messages to users.
5.7. Same Business Day (SBD) customer support from Contractor shall be available to fix the issues.
5.8. SMS Services Application/Module/Gateway to be fully integrate with the application by the Contractor at no
extra cost.
5.9. Validity of SMS shall be life time. No expiry date shall be in place.
5.10. SMS gateway shall be integrated with AAI Website 2.0 and mobile Apps seamlessly.
5.11. SMS gateway shall be able to send SMS in Hindi and English.
5.12. SMS gateway shall be able to provide delivery report.
5.13. SMS gateway shall be compliant with the Government of India Telecom regulation.
5.14. Contractor shall ensure necessary security measure to protect the message data.
8|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

6. Safe to Host Certification from Cert‐in empanelled auditor as per latest GIGW guidelines
6.1. The Contractor is required to provide “Safe to Host” certificate as per latest GIGW guidelines before go‐live of
complete solution.
6.2. Contractor shall get the “Safe to Host” certificate by 3rd party CERT‐IN empanelled auditors.
6.3. Please refer to Annexure‐A Clause 8 for more details on Cyber security and compliance.

7. Certified Quality Website (CQW) Certificate from STQC/3rd party audit agency for the compliance of latest GIGW
7.1. The Contractor shall engage STQC/third‐party audit agency for auditing and certification on GIGW compliance
for quality of AAI Website & Mobile APPs. Contractor shall obtain the Certified Quality Website (CQW)
Certificate before go‐live of complete solution.
7.2. The Contractor shall ensure that AAI Website and mobile APPs are certified with latest GIGW standard,
wherever required, and are in compliance with the GIGW standard throughout the duration of the contract.
7.3. The Contractor is required to address and resolve the errors/non‐conformities if any rose during the
audit/annual surveillance activities by any government agencies/AAI.
7.4. The Contractor is required to conduct milestone‐wise third‐party audit of the developed Solution for
compliance with GIGW for the Quality of Milestone item.
7.5. The Contractor is required to prepare an Audit Plan milestone‐wise and subsequently update on need basis.
Due approval on the Audit Plan is required from AAI for commencement of the Audit activities.
7.6. The Contractor should close all observations & recommendations of such an audit and the cost of closure of all
such audit observations & recommendations to be borne by Contractor.
7.7. Upon rectification based on the recommendations, the Auditor will be required to re‐audit the system to ensure
that all recommendations accepted for inclusion are complied with.
7.8. The final report is to be submitted immediately upon completion of the activity before go‐live of such milestone
item. Presentations on the report, its findings, conclusions and recommendations need to be made to AAI.
7.9. Contractor shall get audited with AAI Cybersecurity team for compliance with GIGW before hosting of new
features, websites/microsites/subdomains, Mobile APPs in production environment during warranty & AMC.

8. Perpetual Enterprise support/ License cost for provided tools/software/Middleware/platform as required for the
project, as per SOW. (List of such tools/software/Middleware/platform to be provided by Bidder. Must be
mutually exclusive with such tools /software/Middleware/platform provided under BOQ line‐item No. 1.09.
8.1. Contractor shall supply the tools/software/Middleware/platform with enterprise support license to be used
during entire duration of the contract for all the environments.
8.2. All the licenses shall be procured in the name of AAI.
8.3. For hosting of the solution, Contractor shall provide software tools and solutions for load balancer, CI/CD/CT
pipeline, clustering, cache implementation, solution deployment, SLA monitoring, ticketing, alert mechanism
tools for the deployed applications etc.
8.4. Indicative List of tools/software/Middleware/platform include, but not limited to, the following:

 Database with enterprise support license

 OCR engine with enterprise support license
 Document compressor tool with enterprise support license (Image, Audio, Video, Pdf etc.)
 Speech recognition engine with enterprise support license
 Containerization tool with enterprise support license
 Container Orchestration Tool with enterprise support license
 Design Tool with enterprise support license
 Development tool with enterprise support license
 Testing tool with enterprise support license
9|Page60
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

 Deployment and Hosting Tool with enterprise support license

 Version control tool with enterprise support license
 Build Automation Tool with enterprise support license
 Error and Bug Tracking Tool with enterprise support license
 Backup and monitoring tool with enterprise support license
 Compliant Management/ Ticket tracking tool with enterprise support license
 SLA Monitoring Tool with enterprise support license
 Translation tool to translate one language to another
 Licensed Off the shelf third party APIs for Flight Status or schedule information
8.5. The list of tools/software/Middleware/platform mentioned above is only indicative and may vary depending
on technology adopted by Contractor for development, warranty and AMC. The Contractor shall submit the
details of tools/software/Middleware/platform to be delivered to AAI based on the technology stacks chosen
for AAI.
8.6. Contractor shall ensure the Enterprise support license for deployed tools/software/Middleware/platform
delivered during the entire duration of the contract.
8.7. The bidder shall provide Enterprise support license of Open Source Software (OSS) for such tools/ software/
middleware for all environments. If Enterprise Support license for such OSS tools/ software/ middleware is not
available, then the bidder shall provide the proposed list of commercial‐off‐the‐shelf (COTS) tools/ software/
middleware with justification.
8.8. If neither Enterprise support license for Open Source Software (OSS) nor Commercial Licenses for COTS are
available for any particular tools/ software/ middleware required for the project, only then OSS with
community support may be considered for the project as an exception. Clear justification for selecting such
tools/ software/ middleware with Community Support for OSS must be provided by the bidder in their
response.
8.9. Contractor shall provide the access of all the tools to AAI.

9. Subscription ‐based Enterprise support/ License cost for provided tools/software/Middleware/platform as

required for the project, as per SOW, for the development & stabilization period. (List of such tools
/software/Middleware/platform to be provided by Bidder. Must be mutually exclusive with such tools
/software/Middleware/platform provided under BOQ line‐item 1.08.
9.1. The Contractor shall be responsible for arranging annual support for the OEM products (if applicable) provided
by respective OEMs during the entire O&M phase.
9.2. It is mandatory for the Contractor to take enterprise level annual support over the entire contract duration
from the date of installation of licenses.
9.3. The Contractor shall provide supported document for procurement of the licenses and patches for the update/
upgrade as and when required.

10. Deployment of onsite Administrator for AAI website and Mobile APPs
To achieve the key objective of the project, Administrator is required to be deploy in AAI office to lead the
development, warranty, AMC of AAI Website 2.0 & mobile APPs and any new requirement comes across contract
duration. Contractor shall deploy an Administrator for entire duration of contract as per BOQ.
The roles and responsibility of Administrator are mentioned as below:
10.1. Administrator shall be the single point of contact for AAI.
10.2. Administrator will look after the development, warranty and AMC of AAI Website 2.0 and mobile APPs.
10.3. Should have experience in Website Administrator to oversee the management and maintenance of the AAI
website and Mobile APPs.
10.4. should have a deep understanding of web technologies, excellent troubleshooting skills, and the ability to

10 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

ensure the smooth operation of the AAI website and Mobile APPs.
10.5. This role requires a proactive approach for managing the website & APP’s functionality security and user
experience.
10.6. Oversee the day to day management of the AAI website & Mobile APPs, ensuring availability, uptime, and
speed. Monitor website functionality, resolve any issues promptly, and implement necessary updates.
10.7. Identify, diagnose, and resolve technical issues related to the website & Mobile APP, including broken links,
content errors, and server issues.
10.8. Should be able to Manage backup and disaster recovery processes.
10.9. Should be able to Install, configure, and update tool/software/Middleware if required.
10.10. Should be able to Manage network configurations and ensure connectivity to AAI Website & Mobile APP
server.
10.11. Should be able to Manage user accounts and access permissions on the AAI Website & Mobile APP server.
10.12. Ensure databases are up‐to‐date, secure, and performing optimally.
10.13. Diagnose and resolve database‐related issues.
10.14. Perform routine checks to ensure the AAI website 2.0 and Mobile APP's proper functioning.
10.15. Monitor AAI website and mobile APPs on a day‐to‐day basis to ensure that it functions reliably.
10.16. Monitor Website and mobile APPs proactively to ensure lag free and a seamless user experience i.e.
application does not suspend, hang etc.
10.17. Monitor components, including but not limited to, Application servers, Web Servers, Middleware and other
Servers on an ongoing basis to ensure smooth functioning of the AAI Website and mobile APPs.
10.18. He will also look after the new requirement related to AAI Website and Mobile APPs throughout the entire
duration of the contract.
10.19. He/ She will also act as Business Analyst and Solution Architect for new requirements during the warranty
and AMC period.
10.20. Administrator shall involve in requirement gathering, shall co‐ordinate with the various
Directorates/Airports/Regions for requirement gathering, approvals/sign‐offs. The requirement gathering will
also involve discussions with all concerned, and other stakeholders as per requirements.
10.21. He/ She shall also be able to develop high‐level and low‐level designs for AAI Website 2.0 and mobile APPs
and also for the new development during Warranty and AMC.
10.22. He/ She shall also be able to identify technical risks and challenges early in the project lifecycle, develop
mitigation strategies and contingency plans to address potential issues.
10.23. It will be Administrator’s responsibility to ensure compliance of various security audit reports/observations
received from AAI Cyber Security Team and other govt. agencies.
10.24. It will be Administrator’s responsibility to submit the claims with all the deliverables to AAI.
10.25. Administrator shall get the necessary deliverables approved from time to time as per project management
plan.
10.26. It will be Administrator’s responsibility to develop a comprehensive project plans, outlining the tasks and give
the timelines for the same.
10.27. Assist in designing solutions that meet business requirements. Collaborate with the development team to
translate business needs into technical specifications.
10.28. Collaborate with testing teams and users to validate that delivered solutions meet business requirements.
10.29. Administrator shall review quality of project deliverable to ensure compliance with agreed quality measures
and standards.
10.30. Provide regular project updates, addressing concerns and ensuring alignment with business goals.
10.31. Facilitate communication between team members, stakeholders, and AAI project team. Coordinate with DC
and DR team in case of any issue.

11 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

10.32. Administrator shall be responsible for SOPs and Manuals (Text, Video) updation during Warranty and AMC
period.
10.33. Administrator shall conduct trainings and Demo for the AAI personnel whenever there is any change in the
system functionality and after go‐live of new requirement/features/microsite/website during AMC and
Warranty. All Training and Demo plans have to be mutually agreed on with the AAI team.
10.34. Administrator would contact with offsite manpower (Technical Architect, DevOps Engineer, non‐functional
tester etc.) or call them in AAI premise if need arises and escalating issues to offsite resource in case deployed
manpower is unable to resolve.
10.35. Periodic Progress Reports to be submitted indicating the activities remaining / completed as against the
scheduled tasks / activities.
10.36. Above responsibility are not exhaustive. AAI reserves the right to assign any other work related to AAI website
and Mobile APPs.

11. Deployment of onsite UI/UX Designer for AAI Website and Mobile Apps
Role and responsibility of UI/UX Designer is mentioned as below:
11.1. The UI/UX Designer focuses on designing interfaces that are visually appealing, easy to navigate, and align
with user expectations and brand identity.
11.2. Conduct research to understand the target audience, their preferences, and behaviors.
11.3. Gather insights through surveys, interviews, and usability testing to inform design decisions.
11.4. Develop the information architecture to create a logical and intuitive structure for the AAI website and
Mobile APPs.
11.5. Design site maps and user flows to outline the navigation and user journey.
11.6. Create wireframes to outline the basic structure and layout of each page or screen.
11.7. Design logos, banners, branding materials, advertisements and other marketing collateral.
11.8. Develop interactive prototypes to demonstrate user interactions and flow.
11.9. Choose color schemes, typography, and imagery to create a cohesive and engaging visual experience.
11.10. Ensure designs are responsive and adaptable to various screen sizes and devices.
11.11. Produce high‐quality artwork and layouts that meet technical specifications and design standards.
11.12. Optimize layouts for both desktop and mobile experiences.
11.13. Work closely with developers to ensure the feasibility and implementation of design concepts.
11.14. Provide design assets and specifications for a seamless development process.
11.15. Design animations and interactive elements to enhance user engagement.
11.16. Ensure smooth transitions and interactions for a delightful user experience.
11.17. Consider accessibility standards and design interfaces that are inclusive for users with disabilities.
11.18. Implement features like alt text for images and ensure a focus on keyboard navigation.
11.19. Integrate user feedback into the design process to continuously improve the user experience.
11.20. Use analytics and user data to inform design decisions and enhancements.
11.21. Create design documentation, including style guides, design principles, and component libraries.
11.22. Ensure consistency in design elements across the AAI website and Mobile APPs.
11.23. Stay abreast of the latest design trends, tools, and technologies.
11.24. Apply innovative and industry‐relevant design solutions.
11.25. Be adaptable to changing project requirements and evolving user needs.
11.26. Iterate designs based on feedback and emerging trends.
11.27. To coordinate with on‐call manpower and Administrator to get the support for AAI website and Mobile APPs.
11.28. Ensure adherence to office policies and office timing of AAI.
11.29. Maintain the confidentiality of sensitive information and records.

12 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

11.30. Shall attend the phone call of users of Departments/Regions/Airports in case any issue falls under above
mentioned points.
11.31. Above responsibility are not exhaustive. AAI reserves the right to assign any other work related to AAI website
and Mobile APPs.

12. Deployment of onsite Back‐end developer for AAI Website and Mobile Apps
Role and responsibility of back‐end developer is mentioned as below:
12.1. Collaborate with front‐end developers, UI/UX designers, and other team members to deliver a cohesive and
efficient end‐to‐end solution.
12.2. Develop server‐side logic to handle the business logic and processes of the AAI website and Mobile APPs.
Implement algorithms and functionalities required for data processing and manipulation.
12.3. Design, implement, and maintain databases to store and retrieve data efficiently. Optimize database queries
and ensure data consistency and integrity.
12.4. Create and maintain APIs (Application Programming Interfaces) for seamless communication between the
front end and back end, between the servers & between the server and external system. Also, may ensure
RESTful or GraphQL API standards and proper documentation.
12.5. Ensure smooth communication between the front‐end and back‐end components.
12.6. Implement security measures to protect the application from common vulnerabilities, such as SQL injection
and cross‐site scripting (XSS).
12.7. Set up and manage user authentication and authorization processes.
12.8. Optimize server‐side performance to ensure fast response times. Implement caching mechanisms and other
performance enhancement strategies.
12.9. Design the back‐end architecture to be scalable, accommodating potential increases in user traffic and data
volume. Implement load balancing and other scalability strategies.
12.10. Plan and execute data migration processes when transitioning between database versions or migration to
AAI Website. Also, ensure data integrity during migration.
12.11. Configure and manage web servers, application servers, and databases.
12.12. Work closely with DevOps teams to automate deployment processes and ensure continuous integration and
delivery (CI/CD).
12.13. Implement infrastructure as code (IaC) practices.
12.14. Implement robust error handling mechanisms to identify and address issues proactively.
12.15. Set up logging systems to track and analyze errors for debugging.
12.16. Ensure compliance with data protection regulations and industry standards. Implement necessary measures
for data privacy and security.
12.17. Collaborate with other developers through version control workflows.
12.18. Conduct unit testing and debugging to identify and fix issues in the back‐end code.
12.19. Document the back‐end codebase, including API documentation, database schema, and architecture
diagrams.
12.20. Facilitate knowledge transfer within the development team.
12.21. To coordinate with on‐call manpower and Administrator to get the support for AAI website and Mobile APPs.
12.22. Ensure adherence to office policies and office timing of AAI.
12.23. Maintain the confidentiality of sensitive information and records.
12.24. Shall attend the phone call of users of Departments/Regions/Airports in case any issue falls under above
mentioned points.
12.25. Above responsibility are not exhaustive. AAI reserves the right to assign any other work related to AAI website
and Mobile APPs.

13 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

13. Deployment of onsite Front‐end developer for AAI Website & Mobile APPs
Role and responsibility of front‐end developer is mentioned as below:
13.1. Implement responsive and visually appealing user interfaces based on design specifications. ensuring a
seamless and engaging user experience.
13.2. Translate design wireframes or prototypes into functional and interactive web pages.
13.3. Write clean, semantic front‐end code for the structure of web pages. Style web pages to create attractive
and consistent layouts.
13.4. Develop interactive and dynamic features using front‐end frameworks and Libraries.
13.5. Ensure that AAI website functions correctly and looks consistent across various web browsers.
13.6. Address browser‐specific quirks and issues to achieve cross‐browser compatibility.
13.7. Design and implement layouts that adapt to different screen sizes and devices for a mobile‐friendly
experience.
13.8. Optimize website performance by minimizing page load times and optimizing assets.
13.9. Provide feedback on design feasibility and contribute to design discussions.
13.10. Integrate with back‐end APIs to fetch and display dynamic content on the front end.
13.11. Ensure smooth communication between the front‐end and back‐end components.
13.12. Conduct testing and debugging of front‐end code to identify and fix issues.
13.13. Implement accessibility best practices to ensure that the AAI website is usable for people with disabilities.
13.14. Use ARIA (Accessible Rich Internet Applications) attributes and follow WCAG guidelines.
13.15. Implement secure coding practices to prevent common vulnerabilities, such as cross‐site scripting (XSS) and
cross‐site request forgery (CSRF).
13.16. Document front‐end code, including comments and documentation files, for the benefit of other developers
and future maintenance.
13.17. Implement client‐side performance monitoring tools to track and analyze user interactions and experiences.
13.18. Be adaptable to changing project requirements.
13.19. Iterate on designs and functionalities based on feedback and evolving needs.
13.20. Design and implement the user interface of mobile applications based on design specifications.
13.21. Utilize mobile development frameworks and technologies to build cross‐platform Mobile APPs.
13.22. Implement responsive design principles to ensure optimal user experience on various screen sizes and
resolutions. Test and optimize layouts for smartphones, tablets and also for different platforms.
13.23. Implement interactive features and user interface elements using mobile‐specific technologies.
13.24. Incorporate gestures, animations, and transitions to enhance user engagement.
13.25. Ensure that the mobile app functions consistently and looks coherent across different mobile platforms (iOS
and Android), screen sizes, and resolutions.
13.26. Address platform‐specific design guidelines and requirements.
13.27. Optimize mobile app performance by minimizing load times and optimizing assets.
13.28. Implement caching strategies and optimize data fetching for efficient mobile usage.
13.29. Integrate mobile apps with back‐end APIs to fetch and display dynamic content.
13.30. Ensure seamless communication between the front‐end and back‐end components.
13.31. Collaborate closely with back‐end developers, UI/UX designers and other team to understand design
requirements and implement them effectively in the Mobile APPs.
13.32. Provide feedback on design feasibility and contribute to design discussions.
13.33. Implement secure user authentication mechanisms and sensitive data communication, considering mobile‐
specific security concerns.
13.34. Follow best practices for securing data storage and transmission.

14 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

13.35. Implement offline functionality when required, allowing users to access certain features or content without
an active internet connection.
13.36. Integrate push notification functionality to keep users informed about updates and relevant information on
both iOS and Android.
13.37. Conduct testing and debugging of mobile app front‐end code to identify and fix issues.
13.38. Document mobile app front‐end code, including comments and documentation files, for the benefit of other
developers and future maintenance.
13.39. Be adaptable to change project requirements, emerging technologies, and updates to mobile platforms.
13.40. Collaborate closely with back‐end developers, UI/UX designers and other team to understand design
requirements and implement them effectively. Also, collaborate with other developers using version control
workflows.
13.41. To coordinate with on‐call manpower and Administrator to get the support for AAI website and Mobile APPs.
13.42. Ensure adherence to office policies and office timing of AAI.
13.43. Maintain the confidentiality of sensitive information and records.
13.44. Shall attend the phone call of users of Departments/Regions/Airports in case any issue falls under above
mentioned points.
13.45. Above responsibility are not exhaustive. AAI reserves the right to assign any other work related to AAI website
2.0.

14. Deployment of onsite Functional Tester (Manual and Automation) for AAI Website and Mobile Apps
Role and responsibility of functional tester is mentioned as below:
14.1. Thoroughly understand the project requirements, including functional specifications, user stories, and
acceptance criteria.
14.2. Develop test plans outlining the testing approach, scope, resources, schedule, and deliverables.
14.3. Collaborate with stakeholders to ensure alignment with project goals.
14.4. Create detailed test cases based on requirements, covering positive and negative scenarios.
14.5. Ensure that test cases are traceable to requirements for comprehensive coverage. Define test scenarios and
criteria for UAT.
14.6. Execute manual test cases to validate the functionality of AAI Website and Mobile APPs.
14.7. Identify, document, and prioritize defects, and work with the development team to ensure timely resolution.
14.8. Perform regression testing to verify that new changes do not adversely impact existing functionality.
14.9. Automate repetitive and critical test cases for efficient regression testing.
14.10. Conduct exploratory testing to discover defects and potential issues that may not be covered by existing test
cases.
14.11. Verify mobile‐specific functionalities such as gestures, responsiveness, and device compatibility.
14.12. Develop and maintain automated test scripts using testing frameworks (e.g., Selenium, Appium etc.) for AAI
Website and Mobile APPs. Execute automated tests to increase test coverage and efficiency.
14.13. Conduct performance testing to assess the responsiveness, adaptability, stability, and scalability of AAI
Website and Mobile APPs. Identify and resolve performance bottlenecks. Perform security testing to identify
vulnerabilities and ensure that sensitive data is adequately protected.
14.14. Evaluate the user interface and experience to ensure that AAI website and Mobile APPs are user‐friendly and
intuitive.
14.15. Collaborate with developers to understand the root cause of defects and verify fixes.
14.16. Maintain detailed test documentation, including test cases, test scripts, test data, and defect reports.
14.17. Provide test summary reports and other relevant documentation to stakeholders.
14.18. Propose and implement improvements to the testing process for enhanced efficiency.

15 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

14.19. Provide clear and constructive feedback on the quality of the software to the development team.
14.20. Communicate testing progress, issues, and results to relevant stakeholders.
14.21. Ensure adherence to testing standards, processes, and methodologies defined by the organization.
14.22. To coordinate with on‐call manpower and Administrator to get the support for AAI website and Mobile APPs.
14.23. Ensure adherence to office policies and office timing of AAI.
14.24. Maintain the confidentiality of sensitive information and records.
14.25. Shall attend the phone call of users of Departments/Regions/Airports in case any issue falls under above
mentioned points.
14.26. Above responsibility are not exhaustive. AAI reserves the right to assign any other work related to AAI website
and Mobile APPs.

15. Deployment of onsite Content uploader for AAI Website and Mobile Apps
Role and responsibility of each Web content uploader is mentioned as below:
15.1. Shall upload the document at AAI website 2.0 & Mobile APPs on approval of competent authority.
15.2. Shall edit/update/delete the content of AAI website 2.0 & Mobile APPs on approval of competent authority.
15.3. Shall raise the tickets and track the ticket on Ticket Management system.
15.4. Shall cater the request coming on ticket Management tool, email and provide reply after resolution.
15.5. Shall check the status of server health, performance, resource usage and application availability on daily
basis.
15.6. Shall support Administrator in Monitoring of the AAI website 2.0 and Mobile APPs working on daily basis and
ensuring that they run smoothly and are secure.
15.7. Ensure adherence to office policies and office timing.
15.8. Maintain the confidentiality of sensitive information and records.
15.9. Shall attend the phone call of users (helpdesk support) at 1st level from Departments/Regions/Airports in
case any issue if not resolvable then forward to developer.
15.10. Above responsibility are not exhaustive. AAI reserves the right to assign any other work related to AAI website
and Mobile APPs.

16. Deployment of Wildcard SSL Certificate with latest version for all the platforms
16.1. All the applications should be hosted in SSL environment (https). The platform should support predefined
security configuration to protect AAI website 2.0 and mobile APPs resources against any kind of attacks.
16.2. Contractor shall provide the valid Wildcard SSL Certificate in latest version for entire duration of contract as
per BOQ.
16.3. Choose a reputable SSL certificate provider that offers Wildcard SSL certificates with support for the latest
encryption protocols and security standards.
16.4. Configure server redirects to ensure that all HTTP requests are automatically redirected to the HTTPS version
of the AAI website 2.0.
16.5. Update the network security configuration within the mobile APPs to enforce SSL/TLS encryption and trust
the Wildcard SSL Certificate for all API endpoints and server communications.
16.6. Set up monitoring and alerting mechanisms to notify AAI officials of SSL certificate expiration or potential
security vulnerabilities.
16.7. Proactively renew the SSL certificate before the expiration date to avoid service disruptions. Automate the
certificate renewal process if possible.
16.8. Keep the SSL/TLS libraries and dependencies up to date to address any security vulnerabilities or weaknesses
identified in the latest versions.
16.9. Conduct thorough testing to ensure that the SSL/TLS configuration is correctly implemented and functioning

16 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

as expected across all platforms.

16.10. Verify that the Wildcard SSL Certificate is compatible with various web browsers and mobile devices to ensure
a consistent and secure user experience.

17. Operation and Maintenance (O&M) of new AAI website and mobile APPs after Go‐Live
Salient requirements are described as:
17.1. O&M includes, but not limited to, troubleshooting, performance optimization, addressing
functionality/availability and performance issues. Focus should be on preventive/proactive maintenance.
17.2. All tickets related to any issue/complaint/observation about the solution & request for uploading, updating
& new feature/microsite/subdomain development shall be maintained in comprehensive ticketing solution.
17.3. Contractor has to ensure the AAI website 2.0 and Mobile APPs is well maintained, up‐and‐running 24x7.
17.4. The overall responsibility of the AAI website 2.0 and Mobile APPs maintenance lies with the Contractor.
17.5. Contractor shall provide the AMC of the AAI Website 2.0 and Mobile APPs for the duration of three (3) years
after One (1) year of Warranty. Warranty Period of AAI Website 2.0 and Mobile APPs will commence after
completion of stabilization period.
17.6. The contractor will deploy the resources on‐site/ off‐site depending on the nature of activity apart from
permanently deployed manpower in AAI corporate office as per BOQ. Deployed manpower shall work under
guidance of AAI Project Manager/ Project In‐charge.
17.7. Update software, plugins, and components to the latest versions to address security vulnerabilities and
improve performance.
17.8. Identify and fix any errors/bugs/gaps or issues that may arise during the operation and maintenance period
after Go‐Live.
17.9. Provide timely resolutions to reported problems, ensuring minimal disruption to AAI website and Mobile
APPs services.
17.10. Contractor shall coordinate with AAI cyber security team for security audits and vulnerability assessments.
17.11. Contractor shall prevent the AAI Website and Mobile APPs from security threat and proactively address
security concerns.
17.12. Contractor shall improve the performance of AAI Website and Mobile APPs. Improve logic and design
whenever requires in order to enhance performance of AAI website and Mobile APPs.
17.13. Contractor shall manage AAI website and Mobile APPs servers at AAI, DC & DR. Contractor shall perform DC‐
DR drill as per frequency set under SLAs.
17.14. The Contractor will have to include version upgrade and enhancements in services on account of industry
dynamics as a part of the O&M. Any development work of such type will be carried out by the deployed team
by Contractor at no extra cost.
17.15. Contractor shall perform accessibility, load testing of Applications, Database and Load balancer.
17.16. Contractor shall ensure that DC‐DR replication is happening round the clock.
17.17. Contractor shall share Contingency Plans for application and data recovery.
17.18. Contractor shall develop and implement a robust disaster recovery plan to ensure data integrity and rapid
recovery in case of system failures.
17.19. Contractor shall monitor AAI website & Mobile APPs performance and address any issues related to speed,
responsiveness, or resource utilization. Optimize AAI website & Mobile APPs components to enhance overall
performance. Contractor may procure or utilize additional software to enhancement the performance of
website.
17.20. Contractor shall ensure compliance of security issues / GIGW compliance time to time. It is the responsibility
of Contractor to rectify the security issues/ GIGW compliance raised by AAI or any government agencies
17.21. Contractor shall ensure provision to send the alert in case of AAI website or Mobile APPs go down.

17 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

17.22. Contractor shall keep record of Software Change and Version Control. Contractor may utilize the enterprise
edition of tools to monitor the same.
17.23. The Contractor shall maintain the solution related documentations such as High‐level design of whole system,
Low level design for whole system/module design level, System Requirements Specifications (SRS) etc.
17.24. The Contractor shall also ensure that any software system documentation is updated with regard to the
following:
17.24.1. Source code is documented
17.24.2. Functional specifications are documented
17.24.3. Application documentation is updated to reflect on‐going maintenance and enhancements
including FRS and SRS in accordance with the defined standards
17.24.4. User manuals and training manuals are updated to reflect on‐going changes/enhancements
17.24.5. Standard practices of version control and management are adopted and followed
17.25. All project documents need to follow a proper version control mechanism. The Contractor will be required
to keep all project documentation updated and ensure the updated project documents are submitted to the
AAI by the end of next quarter in case of any change.
17.26. Application monitoring and Compliance to Service Level Agreements, it is the responsibility of the Contractor
to:
17.26.1. Ensure compliance with SLAs as indicated in the RFP and any upgrades/updates/any changes to the
solution shall be planned by the Contractor while ensuring that the SLA requirements are met at no
additional cost to the AAI.
17.26.2. The Contractor shall ensure compliance to uptime and performance requirements of solution as
indicated in the SLA and any major changes to the software shall be planned accordingly by the
Contractor for ensuring the SLA requirements.
17.26.3. Ensure the accuracy and timeliness of data uploaded as received.
17.26.4. Resolve and report the data discrepancies to the designated AAI Officials.
17.26.5. The Contractor shall submit a document on the performance of the Software application against
the desired SLA on a Quarterly basis/as required.
17.26.6. Contractor shall ensure the password policy for application and servers.
17.26.7. Contractor need to submit a report based on user login, location, last update, visits etc. whenever
required.

18. Training and Capacity Building

18.1. User Training for features & management of AAI Website 2.0 & mobile APPs after go‐live
18.1.1. The Administrator shall conduct training on AAI Website 2.0 & mobile APPs features & management
and draw up a systematic training plan in line with the overall project plan in consultation with AAI.
18.1.2. The trainings shall be provided at AAI premises, New Delhi. Remote locations of AAI would join
through virtual meeting or they will be called by AAI to New Delhi for training.
18.1.3. The Training program would be split into series of sessions for different user groups and across
functional areas of the AAI Website 2.0 and mobile APPs.
18.1.4. The Administrator shall conduct comprehensive training (classroom + practical) for System
Administration, Technical, Web Administrator and End user.
18.2. Administrator shall be responsible for the following activities as part of the End User and Train the Trainer
Training:
18.2.1. Develop overall training plan including formation of user groups and classifications.
18.2.2. The Administrator shall prepare Training materials for successful usage, implementation,
updation and maintenance of the developed AAI website 2.0 and mobile APPs.
18.2.3. All the training material should be available on the AAI Website 2.0 and mobile APPs for users’
reference.
18.2.4. Administrator shall get the approval of AAI for Location, Training Schedule, Curriculum, feedback
form, and Training Material for AAI Staff.

18 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

18.2.5. Administrator will be responsible for training the department, region, Airport users in the areas of
parameterization, operations, management, error handling etc. with respect to Content
Management.
18.2.6. Training to the content managers (nodal officers) on the content management and tools used in AAI
website 2.0 and mobile APPs.
18.2.7. After each training session, feedback will be sought from each of the attendees on either printed
feedback forms or through a link available on the web portal. The feedback received would be
reported to the AAI for each training session.

19. Development of Single Sign‐On (SSO) and signup system across all platforms
19.1. Contractor shall develop a Single Sign‐On (SSO) and signup system across all platforms such as AAI Website
2.0, Mobile APPs, subdomains, and microsites of Airports for external users (Passengers, Visitors etc.) which
will enable them to access the services provided by AAI.
19.2. Contractor shall provide a user registration mechanism for new users to sign up for an account at
aforementioned platforms. User registration includes fields for capturing essential user information (Mobile
No., email ID etc.) and preferences. The system should have the ability to verify the accounts through e‐mail
verification, mobile OTP etc.
19.3. Contractor shall allow users to manage their profiles, including updating personal information, preferences,
and security settings.
19.4. User login at AAI Website 2.0 and mobile APPs shall be happed in encrypted mode.
19.5. Contractor shall implement password policies, such as complexity requirements, expiration periods, and
password recovery mechanisms, to ensure secure user authentication.
19.6. Contractor shall ensure that user profiles and preferences are synchronized between the platforms, providing
a consistent user experience across platforms.
19.7. Contractor shall implement robust security measures, such as encryption, session management, and threat
detection, to safeguard user credentials and data across all platforms.
19.8. Contractor shall ensure compliance with relevant regulations and standards governing user authentication,
data privacy, and security, such as India Govt. Data Protection Law & regulations, and OWASP guidelines.
19.9. Contractor shall design the SSO and signup system to accommodate future growth and scalability
requirements, including increased user traffic and expanded platform functionality.
19.10. AAI serving employees shall be authenticated through AAI LDAP system. Contractor shall provide required
mechanism to authenticate AAI serving employees through LDAP.
19.11. AAI retired employees shall be authenticated through unique Mobile Number. Contractor shall provide
required mechanism to authenticate AAI retired employees using SMS gateway.
19.12. Contractor shall develop required mechanism to fetch Real‐time retired and serving employee profile data
from AAI SAP system.
19.13. Single Sign‐On service will centrally maintain user session thus preventing user from multiple login when
trying to access multiple applications.

20. Development of Integrated Dashboard at different levels for employees

Contractor shall develop a comprehensive Dashboard specific to End User, Serving Employee, Retired Employee,
AAI Website Admin, Directorates, Regions and Airports based on role and access privileges.
20.1. Customized User Dashboard:
20.1.1. Implement a secure login mechanism to authenticate end users (serving/retired employees,
passenger, visitors etc.) and grant access to their personalized dashboards upon successful
authentication.
20.1.2. End user Dashboard shall be highly customizable according to their needs. Contractor shall provide
the options for selection of widgets/modules/Features/Menu/Submenu that users can choose from

19 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

to populate their dashboard. Widgets may include latest updates, status, notifications, weather
updates, calendar events, recent activity logs, and more.
20.1.3. Allow users to customize their dashboard layout by arranging and rearranging widgets using a drag‐
and‐drop interface. This enables users to prioritize content based on their preferences.
20.1.4. Enable users to configure individual widgets by adjusting settings, preferences, and content sources.
For example, users may customize the circulars widget by selecting preferred circulars categories or
sources.
20.1.5. Display personalized content on the dashboard based on user preferences, behavior, and historical
data. This may include recommendations, personalized messages, and relevant notifications.
20.1.6. Enable users to access their dashboard and view cached content even when offline in Mobile APPs.
This ensures continuous usability and engagement, especially in areas with limited or no internet
connectivity.
20.1.7. Integrate push notification functionality to notify users of important updates, reminders, or events
directly on their dashboard.
20.2. Nodal Officer Dashboard:
20.2.1. Dashboard should have provision to showcase the analytics of uploaded and updated information in
respect to their Directorates, Regions and Airports. All the activities performed on AAI website 2.0
and mobile APPs by AAI Website Admin, Directorates, Regions and Airports shall be recorded on
dashboard. Nodal officers will handle the dashboard. Some of activities may be like number of
document uploaded from his/her directorate, No. of Hindi doc missing, date of expiry of contents
etc.
20.2.2. Contractor shall provision to Departments, Regions and Airports to upload and update the content
on AAI website 2.0 and Mobile APPs through Dashboard. However, any content deletion provision
shall only be available with AAI website team. There should be provision to upload data using excel
sheet. System shall also maintain the revision of uploaded contents.
20.2.3. Different role shall be given to more than one user of Departments/Regions/Airports to view
Dashboard content if required.
20.2.4. Platform shall be capable of de‐centralized content contribution (Department/Regions/Airports
based) and content management. It also caters to multiple authenticated customers beyond
organizational boundaries.
20.2.5. The Applications must be able to send mail alert and push notifications to the concerned nodal officer
on expiry of content and Hindi doc missing of corresponding English upload.
20.2.6. The system shall provide a trigger facility to send a reminder notifying about the expiry date of the
content and once the notification is sent, it shall be ensured that either the content is placed in the
archive section or the expiry date is extended. Each workflow will be associated with dashboard of
nodal officer.
20.2.7. Contractor shall represent data through graphs and bar charts etc. under dashboard view.
20.2.8. Contractor may embed the analytics tool in Dashboard if required.
20.2.9. Develop various MIS reports as required by AAI. The application shall provide option to AAI Admin,
Directorates, regions and airport to generate MIS reports.
20.3. Analytics Dashboard:
20.3.1. The system should facilitate the view of hits separately for multi‐lingual website and mobile APPs.
Analysis of visitor hits on the AAI website 2.0 and Mobile APPs should be possible by filtering the data
based on certain parameters such as date range, specific page hit. The administrator shall be able to
view the number of hits, traffic coming from a specific search engine, keywords used on search
engine, repeat and unique visitors and visitor's state and countries. It shall also generate analytics on
peak usage time during a particular day/week/month/year.
20 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

20.3.2. The system shall also give a facility to generate dashboards on the website and Mobile APPs visitor's
behaviour pattern on a weekly, monthly, quarterly and annual basis. It shall also be capable of
generating detailed reports which shall be downloadable in multiple formats.
20.3.3. Contractor should provide monitoring facility, creation of metric and choice of visualization as per
AAI Admin, Directorates, regions and airport requirement. There should be provision to attach
document with planned events and dates. There should be a provision to upload excel/pdf/Doc and
download report in .xls /.pdf/Doc file formats or any other format as desired by AAI.
20.3.4. AAI website 2.0 and Mobile APPs should be capable of Omni enablement and analytics. Analytics
should be user selectable and generate reports (like number of clicks from particular IP address,
downloads, etc).
20.3.5. Solution shall provide a custom report builder for the Web portal UI.
20.3.6. MIS report should be auto generated periodically or need basis.
20.4. SLA monitoring Dashboard:
20.4.1. Contract shall provide SLA monitoring Dashboard.

21. On‐premise Setup of DevOps Environment for automation of CI/ CD/ CT

21.1. AAI is embarking on the DevOps journey and wishes to setup a scalable platform (preferable enterprise Open‐
Source tools) for automation of CI/ CD/ CT (Continuous Integration/ Continuous Development/ Continuous
Testing) activities as a centralized DevOps implementation.
21.2. Contractor shall provide platform that would be able to provide orchestration layer for the end‐to‐end
DevOps pipeline.
21.3. The Contractor shall ensure that for application and infrastructure release deployment DevOps framework
should be utilized.
21.4. Tools for Continuous integration of changes, Continuous Deployment, Automated testing of the deployed
changes, and ensuring zero or minimal downtime, code versioning should be utilized wherever necessary.
21.5. End‐to‐end CI/CD/CT pipeline spanning across multiple development environments and multiple network
regions but not limited to these only as detailed below:

DevOps Major Areas DevOps Minor Areas

Demand / Project Mgmt.
Continuous Planning
Planning Mgmt.
Source Control
Continuous Development Coding
Unit Test
Manage Artefacts
Secure Code Analysis
Continuous Integration Static Code Analysis
CI
Build
Deploy
Continuous Deployment
Configuration
Functional
Continuous Testing Non‐Functional
Security
API Testing
Application
Continuous Monitoring Infrastructure
Logs

21 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

21.6. The platform should help automate the release and delivery of applications, shortening the delivery lifecycle,
streamlining manual processes, and accelerating team velocity.
21.7. The platform to support source code management which enables coordination, sharing and collaboration
across the development teams. It should also track and merge branches, audit changes and enable
concurrent work, to accelerate software delivery.
21.8. The platform should enable teams to package their applications and dependencies and build artifacts with
ease to ensure DevOps acceleration with automated software pipelines.
21.9. The platform should be able to automate unit testing, functional testing and non‐functional testing (e.g.
performance test, security test) and integrate them into the pipeline.
21.10. The platform should be able to orchestrate and manage development and test environments.
21.11. The platform should be able to provide a common comprehensive reporting dashboard as part of
“continuous measurement”.

22. Optimization, backup and Performance Monitoring using various tools

22.1. Search Engine Optimization: (SEO) plays a crucial role in the functionality of AAI website 2.0 by enhancing its
visibility and accessibility to online users, ultimately driving more traffic to the site.
22.1.1. Contractor shall re‐write the URL's that are search engine friendly. The re‐written URL's shall be
shorter and more relevant looking links to web pages.
22.1.2. The AAI website 2.0 shall be search engine friendly and the contractor shall optimize the website for
search engine positioning using keywords relevant to stakeholders such as airport information, flight
schedules, parking facilities, travel guides etc.
22.1.3. Contractor shall submit the website to the top Four (4) search engines including Google, Bing and
Yahoo. It is the responsibility of the contractor to rank websites/microsites/sub‐domains in the top
two results on search engines mentioned when searched with relevant keywords.
22.1.4. Implementing SEO related inputs (Keywords, Meta tags, Description tags, Doctype declaration,
Character encoding, URL structure, Robots.txt, Canonical link element, XML and HTML sitemaps,
custom 404, Redirects, HTTP headers, HTML code, iFrame etc.) for the websites/microsites/sub‐
domains.
22.1.5. Improving organic traffic for the websites/microsites/sub‐domains.
22.1.6. Through SEO strategies, Contractor may target specific demographics, geographic locations, or user
interests. For example, by optimizing for keywords like “best airport for business travellers” or
“family‐friendly airports”, the website can attract relevant audiences seeking such services or
amenities.
22.1.7. Contractor shall optimize each page of the AAI website with appropriate title tags, meta descriptions,
and headings containing the chosen keywords. Ensure that URLs are descriptive and include relevant
keywords where possible.
22.1.8. Contractor shall optimize images and videos on the AAI website with descriptive filenames, alt tags,
and captions to improve accessibility and enhance SEO. Image and video content can also improve
user engagement and time spent on the website.
22.1.9. Contractor shall continuously monitor the AAI website’s performance in search results using tools.
Analyse traffic, rankings and use behaviour to identify areas for improvement and adjust the SEO
strategy accordingly.
22.2. Web Page Load/response Optimization
22.2.1. Contractor shall ensure that the web pages’ load quickly is paramount to delivering a seamless user
experience.
22.2.2. Contractor shall optimize performance for mobile devices and also optimize website performance by
22 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

minimizing page load times and optimizing assets.

22.2.3. Graphics used in modernizing the websites and portals should not be very large in size and the
contractor shall ensure that the graphics do not slow down the page load time.
22.2.4. Contractor shall provide Loading Message/progress indicator, clearly indicate to users that the page
is loading.
22.2.5. Estimated Load Time shall also be recorded on AAI Admin Dashboard.
22.2.6. The developed Mobile application should optimize the performance measures in terms of memory,
CPU consumption, installed image size, network bandwidth requirement.
22.2.7. List out the assumptions related to load & infrastructure (such as mobile specifications, internet
bandwidth etc.) so that response time and load time of AAI Website 2.0 and mobile APPs shall always
within the limit set in SLA.
22.2.8. Contractor shall implement techniques such as lazy loading, single page application, partial loading
of page and document & media optimization for faster rendering.
22.2.9. The contractor shall also ensure that the AAI website 2.0 and Mobile APPs shall have an acceptable
performance on different type of internet connection such as Broadband and High‐speed internet.
22.3. Solution Monitoring and Logging
22.3.1. The services to be provided by the Contractor for Application Monitoring which includes following
but not limited to: Web services, Application server, Database server, Middleware etc.
22.3.2. The Solution shall log all system transactions and keep them easily retrievable and sortable.
22.3.3. The Solution shall detect major errors related to one or more components including loss of network
connectivity, a database server going off line, or the application suffers an out‐of memory situation.
22.3.4. The Solution shall have safeguards designed to ensure that configuration variables affecting the
application and the back‐end resources remain at some predetermined configuration settings.
22.3.5. The Solution shall monitor bandwidth, memory, CPU, storage, backup etc as finalized by AAI Team.
22.3.6. The Solution shall monitor AAI Website and mobile APPs on 24x7 basis and send system generated
uptime and response time reports periodically.
22.3.7. The Solution shall provide information on the bottleneck in the system and generate alert.
22.3.8. The Solution shall allow AAI Team to perform admin activities through an intuitive user interface.
22.3.9. The Solution shall allow for Report generation and analysis for application troubleshooting and
capacity planning.
22.3.10. The Solution shall allow for different roles for Users including Operators, Administrators etc. for
department, region and Airport to monitor the Solution if required.
22.3.11. Contractor should test performance of AAI Website and Mobile APPs for remote locations in India
and outside India like USA, UK, Japan etc. using tool.
22.3.12. There should be mechanism with reporting and analytics to see website & Mobile APP stats,
average time spent, most accessed pages, etc. Contractor should provide periodic MIS report with
the above statistics along with hardware usage and performance indexes.
22.4. Backup and Restoration services
22.4.1. Monitoring and enhancing the performance of scheduled backups, schedule regular testing of
backups and ensuring adherence to related retention policies as defined by AAI.
22.4.2. Prompt execution of on‐demand backups of volumes and files whenever required or in case of
upgrades and configuration changes to the system. Contractor shall provide Data Backup and Data
Dump whenever required by AAI.
22.4.3. Real‐time monitoring, log maintenance and reporting of backup status on a regular basis.
22.4.4. Taking Backup of AAI website 2.0 & Mobile APPs (Application & Database) is the responsibility of
Contractor. It shall be scheduled on daily basis and the confirmation mail shall be triggered to

23 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

specified email Ids after completion of backup. Contractor may procure or utilize additional software
for the same.
22.4.5. 7x24 support for file and volume restoration requests at the DC & DR.
22.4.6. Contractor shall also provision for automatic restoration of backup as per backup policy to be
designed by Contractor with the help of AAI.
22.4.7. Contractor shall take incremental and full Back up as backup policy.
22.4.8. Contractor shall keep Backup files encrypted.
22.4.9. In case a Govt. department ex. IB, CERT‐IN needs dump of application and database, Contractor shall
provide the same information without any delay.
22.5. Contingency Plans for Application & Data Recovery
22.5.1. The DR site would work as the failover site in case the datacenter (DC) goes down. This includes
application crash, database crash, network crash or any other issues rendering the datacenter
unresponsive. In case of Application Crash, effort will be made to bring back the application to
working state through the most recent application state & configuration files from the DR site and if
required the backup / restore and reinstallation procedure would be used if the same is available in
the backup set or as a last resort if the DR site also fails. It will be taken up on a high criticality basis
with round the clock support to ensure the application state is reverted to the most recent state.
22.5.2. In case of Database Crash ‐ Effort must be made to retrieves much data as possible from the dataset
of the DR site with the most recent copy of the data. If the last backup set also includes the most
recent copy of the data then that can also be used for restoration of the database. If required,
previous backups will be used to ensure restoration. However, the Contractor needs to honor the
RPO (Recovery Point Objective) & RTO (Recovery Time Objective). Contractor should be on this job
round the clock to restore availability.
22.6. Bugs / Fixes Management
22.6.1. Bugs or Fixes Management is an important activity and based on the severity level, it becomes highly
critical.
22.6.2. Contractor shall use standard bug management tools like Bugzilla, JIRA etc. to log and track the
reported issues. Weekly bug reports shall be shared with AAI for the bug reported and fixed bug
trends which shall include severity, bug root cause, fix provided etc.
22.6.3. Contractor commits involvement in resolution on ‘best of efforts’ basis as per requirements.
Following are the steps involved:
22.6.3.1. Problem definition
22.6.3.2. Context definition (through functional teams as per requirements)
22.6.3.3. Request Analysis
22.6.3.4. Priority Categorization
22.6.3.5. Logging with OEM (if applicable) and tracking to resolution
22.6.4. The Contractor shall address all the errors/bugs/gaps in the functionality offered by the AAI website
2.0 and mobile APPs (vis‐à‐vis the FR the FRS, BRD and SRS signed off) at no additional cost during
the operations & maintenance period.
22.6.5. The Contractor shall identify and resolve application problems like system malfunctions,
performance problems, data corruption etc. due to which the software solution is not able to give
the desired performance. The Contractor shall be responsible for the following:
22.6.5.1. Updating all available patch/ updates to the AAI Website 2.0 & mobile APPs.
22.6.5.2. providing handholding support to end users.
22.6.5.3. Ensuring proactive and timely support in identification and provision of solutions including
OEM (if applicable) Support for resolution.
22.6.5.4. Timely logging of Bugs/Problems.
22.6.5.5. Periodic Reports to AAI & other Project Stakeholders.
22.6.6. An Issue log shall be maintained by the Contractor for the errors and bugs identified in the solution
24 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

as well as any changes implemented in the solution.

22.7. Software Change and Version Control
22.7.1. The Contractor shall maintain version control and configuration information for any system
documentation, AAI Website 2.0 and Mobile APPs.
22.7.2. The Contractor will inform the AAI (at least on a monthly basis) about any new updates/upgrades
available for all software components of the solution along with a detailed action report. In case of
critical security patches/alerts, the Contractor shall inform the AAI immediately along with any
relevant recommendations. The report shall also contain the Contractor’s recommendations on
update/upgrade, benefits, impact analysis etc.
22.7.3. During the operation & maintenance period, the contractor shall submit a quarterly undertaking
stating that the tools & software version is current version and all system patches/upgrades have
been deployed. Security patches can be updated on immediate basis.
22.7.4. Each release comes with a risk of system stabilization and hence periodic updates with full testing
needs to be done to mitigate the risk.
22.7.5. All configuration/features changes or any customizations to the AAI Website 2.0 and mobile APPs
identified, during development phase and the stabilization period of two (2) months, hence are to be
carried out by the Contractor at no extra cost.
22.7.6. All changes during the stabilization or support & maintenance phase shall be subjected to the
comprehensive & integrated testing by the Contractor to ensure that the changes implemented in
the AAI Website 2.0 and Mobile Apps meets the desired and specified requirements of AAI and
doesn’t impact any other function of the system.
22.7.7. All planned changes to AAI Website 2.0 and Mobile apps shall be coordinated within established
Change Control processes to ensure that:
22.7.7.1. Detailed impact analysis is conducted
22.7.7.2. Appropriate communication on change required has taken place
22.7.7.3. Proper approvals have been received
22.7.7.4. Schedules have been adjusted to minimize impact on the production environment
22.7.7.5. All Change plans are backed by Roll back plans
22.7.7.6. All associated documentation is updated post stabilization of the implemented change
22.7.7.7. Version control is maintained for all software changes
22.7.8. For any changes to the AAI Website 2.0 and Mobile Apps, Contractor shall submit a document
indicating proposed changes, impact to the system in terms of functional outcomes/additional
features added to the system etc.
22.7.9. The Contractor is required to keep all such documentation up to date to reflect the latest
enhancements/modifications made to the application. All documentation should be prepared as per
latest industry standards and STQC guidelines and should incorporate necessary version control
mechanism.
22.7.10. Contractor may use version control systems (e.g., Git) to manage and track changes to the
codebase.
22.7.11. The Contractor shall ensure that software version control is carried out for the entire contract
duration.
22.7.12. All software used in development of AAI website 2.0 and mobile APPs should be latest released
version at the time of execution of the contract.
22.8. System Administration & Management Services
The objective of this service is to support and maintain all the Systems provided as a part of this project by
AAI, and shall include:
22.8.1. Regular monitoring of all the applications hosted.
22.8.2. Operating System administration, including but not limited to management of users, processes,
25 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

resource contention, preventive maintenance and management of servers including updates,

upgrades and patches to ensure that the system is properly updated.
22.8.3. Installation and Re‐installation of the applications and other tools/software in the event of system
crash/failures.
22.8.4. Regular analysis of events and logs generated in all the sub‐systems including but not limited to
operating systems, security devices, etc. to identify vulnerabilities. Necessary Action shall be taken
by the Contractor in accordance with the results of the log analysis.
22.8.5. Suitable mechanism has to be maintained for security and forensic related logs or as per requirement
of IT Act and that of other government regulations issued from time to time.
22.8.6. Adoption of policies and procedure, compliances, guideline or international standard as defined by
the AAI.
22.8.7. Troubleshoot problems with web services, applications software and overall aspects of a solution
environment.
22.8.8. Problems shall be logged in at the Help Desk and resolved as per the SLAs defined.
22.8.9. Manage and monitor VM configuration, performance and activity of all VMs. Performance
optimization and reporting ‐ Process and Memory Management, Monitoring CPU performance,
Monitoring Memory performance, Monitoring Input / Output performance, Monitoring Ethernet
Traffic, etc.
22.8.10. Prepare and keep up to date document containing configurations of all VMs etc.
22.8.11. Hardening OS in line with security policies (ISO 27001 information security control).
22.8.12. Periodic health check of the systems, troubleshooting problems, analyzing and implementing
rectification measures.
22.9. Root Cause Analysis
22.9.1. Contractor will be required to provide root cause analysis for all performance and availability
problems that occur.
22.9.2. Formal root cause analysis will be delivered within limit set by AAI of problem occurrence, including
 Explanation of the root cause
 Actions taken to resolve the problem
22.9.3. Action plan to prevent reoccurrence, with project plan/tasks required and timing for each major
milestone of the correction effort, and identification of AAI responsibilities in the correction process.

23. Integration with third party/AAI services using APIs.

23.1. Contractor shall integrate the AAI Website & Mobile APPs with internal services such as AAI LDAP, AAI SAP,
AAI Email etc.
23.2. Contractor shall integrate the AAI Website & Mobile APPs with external services using APIs such as Social
media for fetching live feeds (only for posts published by AAI), SMS Gateway, off the shelf third party for
Flight Status & schedule information etc.
23.3. Contractor shall procure necessary API services for integration if required. Cost of integration will be borne
by Contractor without extra cost to AAI.
23.4. Contractor shall do integration with stakeholders’ database or any other database or using API as per
requirement of AAI.
23.5. Contractor shall integrate the solution through SOA (service‐oriented architecture) – Web services, API, JSON,
Social Media platform etc. whenever required.

24. Auditability and Compliance

24.1. A history and audit trail must be maintained for uploaded contents and any other activities on website and
APPs.
26 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

24.2. The Solution shall maintain a record (e.g. audit trail) of all additions, changes and deletions made to data in
the system. This should be readily searchable by user ID.
24.3. This must include but is not limited to:
24.3.1. The User ID of the person who made the change
24.3.2. The date and time of the change
24.3.3. The physical, software/hardware and/or network location of the person while making the change.
24.3.4. The information that was changed.
24.3.5. The outcome of the event.
24.3.6. The data before and after it was changed, and which screens were accessed and used
24.4. Contractor shall ensure compliance with GIGW 3.0, WCAG 2.0 guidelines etc.
24.5. New AAI Website and mobile APPs should ensure compliance with ISO and W3C and should be compatible
with the international standard for physically challenged persons.
24.6. The AAI website 2.0 and mobile APPs shall be OWASP compliant. Specifically, top ten threats should not be
present in the web and mobile applications.

27 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

ANNEXURE‐A

Scope of Work – Common Requirements for Website & Mobile APPs

1. Essential Requirement of the Project

The key responsibilities of the Contractor with regard to AAI website 2.0 and Mobile APPs include:
1.1. Contractor shall provide support for enhancements in AAI Website 2.0 and Mobile APPs w.r.t latest
advancements and troubleshooting during the contract period.
1.2. The contractor shall continue the development of the new features, functionalities, microsites, subdomains
etc. for the entire duration of the project.
1.3. Data consistency shall be maintained among all platforms i.e. Website and APPs.
1.4. Contractor shall include all the new features/modules/microsites/subdomains implemented in AAI Website
1.0 till the go‐live of the project in updated SRS and FRS document.
1.5. Contractor shall finalize the Mock‐ups for UI/UX for different screens of the software with help of AAI.
1.6. It is the responsibility of Contractor to create Text Manual and Video Manual of developed features developed
till the go‐live of the project.
1.7. AAI website & Mobile Apps shall be bilingual (Hindi and English) with Unicode compliance as per Government
of India guidelines for websites/APPs time to time. Provision of regional language shall be incorporated at all
AAI Airport subdomain/microsites/website. The application shall allow user to input the data in Hindi, English
& Regional language.
1.8. In case AAI finds any work executed by the Contractor is not meeting defined standards or not being state of
the art, AAI reserves the right to reject the same and the Contractor will be given one opportunity to execute
the work meeting the defined standards without any cost to AAI or change in timelines.
1.9. Contractor shall implement Auto archival/search mechanism to maintain the archived documents with proper
classification. The archival mechanism would allow creating the repository of the old documents in archive
mode on expiry of document and so that it could be retrieved as and when required for reference. A central
achieve sections shall also be available to see the all archival documents.
1.10. AAI website 2.0 and Mobile APPs source code and documents will be the property of AAI.
1.11. Contractor is responsible for designing the dynamic sitemap. The sitemap shall be designed in a hierarchical
visual model.
1.12. Contractor shall ensure the provision to reduce the size of the uploaded content (image, video, pdf etc.) at AAI
Website 2.0 and Mobile APPs upon uploading. Contractor may use the tool for it.
1.13. Contractor shall use bullet points and lists wherever possible and avoid the use of long paragraphs of text. The
contractor shall also provide headings and sub‐headings of any written material and the material written by
the contractor shall be professional, avoiding jargon and technical terms.
1.14. Contractor shall ensure that the font used across the AAI website 2.0 and mobile APPs should be consistent.
1.15. Contractor shall provide alternate text for non‐text elements such as images, audio/video clips and multimedia
presentation.
1.16. Contractor shall provide a mechanism to control audio, video, multimedia presentation that starts
automatically.
1.17. Contractor shall standardize the buttons and navigation graphics for all the pages, where appropriate for the
design.
1.18. Contractor shall understand that the text can be quite longer or smaller in different language and therefore
the website designed will need to take this into account.
1.19. Contractor shall ensure the provision of traveler centric general information section with information like
rights and responsibilities, Baggage, Health etc. is available at websites/subdomains/microsites of AAI Airport.
1.20. The Contractor should provide insight and advice for a digital publishing software that allows converting a pdf
to flash flip book and HTML5. The content can then be delivered on the website in the form of a real book on
several devices like desktop, laptop, tablet and smartphones. The Contractor will also be responsible to
integrate the digital publishing software/content with the website.
1.21. Continuity Measures, risk management plan for the continuity of services, application & data backup policy,
business continuity plan needs to be ensured by Contractor.

28 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

1.22. Contractor shall ensure that all the features/modules/microsites/subdomains developed in AAI Website 1.0
till the milestone‐2 shall be included in AAI Website 2.0 and mobile APPs.
1.23. Contractor shall ensure that DC‐DR replication is happening round the clock.

2. Basic Features of AAI Website & Mobile APPs

2.1. AAI Website 2.0 and mobile APPs shall support Geo mapping, Geo tagging, and time stamping as and when
required.
2.2. Visitor count shall be shown in both Hindi and English. Frequently visited section for both Hindi and English.
2.3. Look and feel of AAI website 2.0 and Mobile APPs shall be as per the latest trends in website and mobile APP
design.
2.4. AAI website 2.0 and mobile APPs should have the provision to remove/deactivate/add the existing/new
Airports, Directorates and Regions along with their respective content.
2.5. AAI website and mobile APPs shall support the segmentation of users to enable push notifications to targeted
segment of the passengers / users.
2.6. The platform should provide the means to manage subscriptions of push and pull notification services.
2.7. Latest design features such as Parallax scroll animations, multimedia experiences, dynamic scrolling etc. and
other design features expected of a high‐end user experiential website & Mobile APP shall be employed.
2.8. Zero dependency on system settings like java run time, pop up settings, plugins, add‐ons installations etc. AAI
Website & Mobile APPs should be user friendly for non‐technical persons also.
2.9. Analytical tool should be able to provide all insights of the activities done by the user in AAI Website and Mobile
APPs like page visited, time spent on page, assets in the page visited, time spent on each field on a form etc.
2.10. Comments section should be interactive using thread‐based replies. Section for initiating new thread‐based
forum/blogs for users.
2.11. All the features of AAI website 2.0 and mobile APPs has to be universally accessible to all irrespective of
technology, platforms, devices or disabilities of any kind.
2.12. Application shall support deep‐linking.

3. Cyber Security Audit & Compliances

3.1. AAI conducts Cyber Security Audit of AAI IT Applications with a frequency at every six months (i.e. Bi‐Annually).
Audit observations are shared with respective teams to close the vulnerabilities, if any. Contractor of respective
application(s) shall resolve all the observations within a specific timeframe as per SLA defined in the current
tender.
3.2. As and when new development is carried out during the warranty and AMC period, the development team has
to raise a request for Vulnerability Assessment (VA) to AAI IT Cyber security team. AAI IT Cyber security team
post completion of VA Activity will share the report to AAI Website team for closure of vulnerabilities if any
within the time limit defined in SLA.
3.3. The Contractor shall adhere to guidelines/advisories/ vulnerability notes/observations issued by Government
Security Agency & AAI IT Cyber security team from time to time. Contractor shall resolve all the vulnerabilities
within a specific timeframe as per SLA defined.
3.4. Contractor shall follow the AAI secure coding guidelines issued time to time for development of AAI Website &
Mobile APPs.
3.5. The Contractor is required to conduct milestone‐wise Information Security Audit of the developed Solution. For
the same, Contractor will get the system audited by 3rd party CERT‐IN empanelled auditors/NICSI empanelled
auditor without any additional cost to AAI.
3.6. The Contractor is required to prepare an Audit Plan milestone‐wise and subsequently update on need basis in
coordination with AAI Project Manager. Due approval on the Audit Plan is required from AAI for
commencement of the Audit activities.
3.7. The audits are to cover at least the following:
3.7.1. Vulnerability assessment
3.7.2. Internal and external network penetration testing
3.7.3. Password cracking
3.7.4. Log review, incident response and forensic auditing
3.7.5. Malware/Virus detection
29 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

3.7.6. Application security assessment (both Black Box and Grey Box testing)
3.7.7. Source Code assessment
3.8. Functional audit should cover at least the following (but not be limited to):
3.8.1. Review of User Account Management
3.8.2. Privilege Management and Access Restrictions User ID Scrutiny and Evaluation
3.8.3. Segregation of Duties
3.8.4. Evaluating Access Controls
3.8.5. Review of logs and integration with security monitoring solutions, if any.
3.8.6. Critical Access Review
3.8.7. Recording of security events for future investigations and access control
3.8.8. Modifications done to the programs and the configurations
3.8.9. Segregation between the development and production
3.8.10. Testing process
3.8.11. Quality assurance
3.8.12. Configuration Management
3.8.13. Verification and evaluation of configurations relating to business processes
3.9. The Audit Report should include (but not limited to):
3.9.1. Dates and Location(s) of audit
3.9.2. Audit components, including benchmarks for assessment
3.9.3. Summary of audit findings including identification tests, tools used and results of tests performed
3.9.4. Analysis of vulnerabilities and issues of concern
3.9.5. Plan for inclusion / rectifications needs to be prepared by the Contractor
3.9.6. Recommendations for action
3.10. The Contractor should close all vulnerabilities, observations & recommendations of such an audit and the
cost of closure of all such audit vulnerabilities, observations & recommendations to be borne by Contractor.
Upon rectification based on the recommendations, the Auditor will be required to re‐audit the system to
ensure that all recommendations accepted for inclusion are complied with.
3.11. The final report is to be submitted immediately upon completion of the activity before moving the code into
production environment or go‐live of such milestone item, as the case may be. Presentations on the report, its
findings, conclusions and recommendations need to be made to AAI.
3.12. Scope of work also covers evaluating the confidentiality, safety & security of the data & strengthen the
security posture of solution and protection against external threats.
3.13. All documents, information and reports relating to the assignment would be handled and kept strictly
confidential and not shared/published/supplied or disseminated in any manner whatsoever to any third party.
3.14. Contractor shall ensure to maintain data security at the application, database, messaging and middleware
level.
3.15. Contractor shall ensure security when the applications are accessed from outside the network or accessing
resources outside the network and shall maintain such history of logs for further review with AAI Security Team
3.16. AAI Website & Mobile APPs should be highly secure without vulnerabilities like duplicate login session and
should be SSL supported and encrypted.
3.17. The application should enforce network level security. All the traffics (client‐server, load balancer‐
application, application‐database, between micro services etc.) to be encrypted using secured connectivity.
3.18. Contract shall escalate any untoward incidents to AAI on an immediate basis either for reporting purposes /
action from AAI.
3.19. Contractor shall provide solution support availability 24x7 via phone, email, or online support portal.

4. Manpower Requirements
4.1. Contract shall deploy the manpower during the development phases as per need of the project.
4.2. The Airport Authority of India (AAI) reserves the right to conduct interviews with the specified personnel
deployed for the project during development period. Additionally, AAI may verify and cross‐check the
credentials and qualifications of other team members working offshore to ensure compliance with project
requirements and standards.
4.3. Contract shall deploy the manpower in AAI premise during Warranty and AMC as per BOQ.
30 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

4.4. In the event of absent of any deployed manpower in AAI premise, Contractor shall provide the replacement of
said manpower as per Annexure‐B. Contractor shall maintain the count of manpower.
4.5. In the event of absent of deployed manpower, the penalty will be calculated as per SLA.
4.6. Deployed manpower except content uploader shall be available at AAI Corporate Headquarter (CHQ), New
Delhi office from 0930 hrs to 1800 hrs on all working days (Monday‐Friday). If required, all the deployed
manpower may be required to provide support services from their respective locations or AAI New Delhi office
on weekends/Public Holidays or after office hours on need basis. Contractor will provide the resource with the
necessary infrastructure to carry out on‐call support. In case of non‐compliance of office timing, penalty will be
imposed as per SLA.
4.7. Content uploaders shall be available at AAI Corporate Headquarter (CHQ), New Delhi office in two (2) shift in
six (6) days of a week.
4.7.1. Monday to Friday – one from 7:00 AM to 3:30 PM & other from 1:30 PM to 10:00 PM
4.7.2. Saturday and Sunday – One in each day from 9:30 AM to 6:00 PM
4.8. Both Content uploaders shall provide support to AAI internal users as well as external users of the solution such
as customers, passengers, and visitors etc.
4.9. In addition to deployed permanent manpower requirement mentioned in BOQ, AAI may call Content Creator,
Technical Architect, non‐functional tester, devOps Engineer and any other manpower which are related to
project, in case the need arises. No any additional costs will be borne by AAI for the same, including TA/DA for
travel. In case of non‐compliance of such on‐call manpower, penalty will be imposed as per SLA.
4.10. Contractor shall take consent of AAI before deployment of manpower in AAI premise as per BOQ and all the
manpower would be interviewed by AAI before deployed in AAI premise.
4.11. AAI may, at its discretion, request the Contractor to deploy additional onsite manpower in AAI premise on a
regular basis, on top of the manpower capacity mentioned in the BOQ. Deployment of such manpower shall be
dealt as per provision of person‐month mentioned in BoQ.
4.12. If the performance of any deployed manpower is found unsatisfactory, the Contractor will be required to
replace the individual within one week. During this period:
4.12.1. If the replacement is provided within the specified week, no penalty will be applied.
4.12.2. If the replacement is not provided within one week, the individual will be considered absent, and
penalties will be calculated as per the SLA from the day the replacement was requested.
4.13. Please refer to Annexure – B for manpower qualifications requirements to be deputed onsite.
4.14. Functional requirement such as development of new features/subdomain/microsite/microservice shall be
carried out by deployed manpower without any financial implication on AAI.

5. Business Support Help Desk Solution

5.1. The AAI support cell will handle technical queries and provide guidance for queries related to using the AAI
website or its subdomains and mobile apps (for both internal and external stakeholders).
5.2. Any complaints or request to upload/update received to the helpdesk over email or phone shall be registered
as a ticket in the ticket monitoring tool.
5.3. The proposed helpdesk solution must provide flexibility of logging, viewing, updating and closing the
incident/request for upload or update.
5.4. The proposed solution should include a ticket monitoring tool for raising tickets by end user, ticket assignment
to the resolution team.
5.5. The proposed helpdesk solution must provide seamless integration to log incident & request automatically.
5.6. The proposed helpdesk solution must provide classification to differentiate request basis priority/severity to
address the most critical ones first.
5.7. Each escalation policy must allow easy definition on multiple escalation levels and notification to different
personnel via window GUI.
5.8. The proposed helpdesk solution must provide web‐based knowledge database to store useful history incident
resolution. A menu structure shall be created for callers in order to allow knowledgeable users to access
information more quickly.
5.9. The proposed helpdesk solution must integrate with monitoring, event management and support automatic
problem registration, based on predefined policies.

31 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

5.10. The proposed helpdesk solution must be able to log and escalate user interactions and requests. All
interactions with users will be assigned a ticket number.
5.11. The proposed helpdesk solution must have an updateable knowledge base for technical analysis and further
help end‐users to search solutions for previously solved issues.
5.12. The proposed helpdesk solution must have the ability to track work history of calls to facilitate troubleshooting.
5.13. The proposed helpdesk solution must support tracking of SLA (service level agreements) for call requests within
the help desk through service types.
5.14. Receiving incidents/requests through email or ticketing system. Incident management tool should be
integrated with email received from the end users and a ticket should be auto created by the tool once the
email is received.
5.15. The proposed helpdesk solution shall integrate its systems in such a way that if a grievance or a query is posted
at any of the communication channels (Portal, mobile apps, help desk centre etc.) the same are registered at
one database and resolved in similar fashion so that unified or an integrated view of the communications is
viewed by the stakeholders.
5.16. The proposed helpdesk solution must be capable of assigning call requests to technical staff manually as well
as automatically based on predefined rules, and should support notification and escalation over email, web etc.
5.17. Knowledge tools and Configuration Management Data Base (CMDB) should be integral built‐in components of
Helpdesk and should be accessible from the same login window to enable seamless access.
5.18. The proposed helpdesk solution must allow the IT team to see the Configuration Items (CI) relationships in
pictorial format, with a specified number of relationships on single window.
5.19. The proposed helpdesk solution must have a top management dashboard for viewing the helpdesk KPI in graph
& chart formats.
5.20. The proposed helpdesk solution must support remote management for end‐user & allow analysts to do the
desktop sharing for any system located anywhere, just connected to internet/intranet.

6. Flight Status & Schedule Information:

6.1. User has an option to check the flight status as well as flight schedules between a pair of airports.
6.2. User can search for flight status based on flight number or for a specific Airport.
6.3. When searching for flight status by flight, user will select the departure/arrival indicator, flight number, airport
and date of arrival/departure. The flight status of the flight would be displaying the scheduled and
estimated/arrival time. As well as flight status, Gate, Counters, Belt information if applicable.
6.4. When searching for flight status based on Airport, the user will enter the departure/arrival indicator, airport,
date and an airline filter. The flight status of the flight would be displaying the scheduled and estimated/arrival
time. As well as flight status, Gate, Counters, Belt information if applicable. Users will also have an option to
filter the results based on the time slots of the flight, airlines and source/destination airports.
6.5. The flight schedule will be showing scheduled flights along with the scheduled times between a pair of airports
at a particular date which are selected by the users. Users will also have an option to filter the results based on
the time slots of the flight, airlines and source/destination airports.
6.6. User shall be able to track a flight and shall get notifications via email, SMS, App notification, if there is update
about a particular flight.
6.7. Flight Status & schedule information can be fetched from the various sources e.g. Airport Operator AoDB/AoCC,
Airlines, off the shelf third party APIs etc.
6.8. For flight schedule there should be provision to upload data using excel sheet.

7. Project Planning, requirement Gathering & Designing

The following sections provides details as below:
7.1. Planning
7.1.1. The Contractor needs to prepare an Integrated Project Plan for the entire project. Project plan should
provide a detailed drill down of all activities to be undertaken. This includes details of tasks, assigned
teams for undertaking responsibilities for the task, schedule of deliverables and milestones, key
assumptions and dependencies, associated risks and mitigation plans.

32 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

7.1.2. The Contractor’s program of work should be synchronized with the staff deployment plan proposed;
the deployment plan shall clearly define onsite and offsite deployment plan and personals under each
deployment category.
7.1.3. The prepared project plan should allow teams to track the progress of various deliverables and
milestones, through the scheduled review mechanisms.
7.1.4. Approval by AAI of the proposed plan shall not relieve the Contractor of any of his duties or
responsibilities under the Contract. However, if the Contractor’s work plans necessitate a
disruption/shutdown in AAI Website’s operation, the plan shall be mutually discussed and developed
so as to keep such disruption/shutdown to the barest unavoidable minimum.
7.1.5. The program so submitted by the Contractor shall conform to the requirements and timelines specified
in the RFP.
7.1.6. Any time and cost arising due to failure of the Contractor to develop/adhere such a work plan shall be
to his account.
7.1.7. Please note that the deliverables are indicative in terms of enlistment; kindly refer the entire section
for comprehensive view on the deliverable’s requirements.
7.1.8. Deliverable(s):
7.1.8.1. Integrated Project Plan including:
a. Milestones
b. Resource deployment
c. Risks and their mitigation plan
d. Dependencies
e. Responsibility matrix
7.1.8.2. Submission of Project Charter to include:
a. Risk Management and Mitigation plan
b. Information Security Plan
c. Communication Plan
d. Data Migration plan
e. SLA Monitoring and reporting plan
f. Exit Management Plan including transition management
7.2. System Requirement Elicitation and System Design
7.2.1. Requirement Gathering & Analysis
7.2.1.1. Detailed functional requirements and process flow is provided in this RFP. Contractor is required
to validate the same and fill gaps (that may be identified at this stage). Further, the Contractor is to
further elaborate the functional requirements and process flow, based on discussion with AAI, from
a systems perspective.
7.2.1.2. The requirement gathering should cover (but not be limited to) workflows, business rules,
validations, regulatory / legal requirements/security requirements etc. On basis of the requirements
gathered, the Contractor is required to prepare an SRS document.
7.2.1.3. The Contractor is also required to prepare a Requirements Traceability Matrix (RTM) to establish
the design, development, testing and roll‐out of various functionalities and non‐functional (and
Technical) requirements. It should include mapping of: SRS, LLD, DFD, and other relevant
documents (as per need).
7.2.1.4. Deliverable(s):
a. Data Flow Diagram (DFD)
b. Software Requirement Specifications (SRS)
c. Requirements Traceability Matrix (RTM)
7.2.2.Solution Design
7.2.2.1. The Contractor shall design the solution architecture and specifications to meet the functional
and technical requirements mentioned as part of this RFP. The Contractor shall be entirely
responsible for the design and architecture of the proposed ‘Websites and Mobile APPs’ and its
successful operations for the period defined in the RFP.
33 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

7.2.2.2. Contractor would need to appropriately size the solution (including the bandwidth) for successful
operations, meeting the SLAs, for the contract period.
7.2.2.3. The system architecture for the integrated solution shall be designed, developed & delivered as
per following:
1. The solution design should be n‐tier services‐based architecture for all environments.
2. The solution design should focus on developing workflow and business transaction, rules
management, configuration management.
3. The solution design should be done in such a manner that components are loosely coupled;
ensuring that the application components are treated individually and dependencies are
reduced. The Contractor should ensure that addition, removal, failure or update of one
component has a minimum impact on other components.
4. The Contractor should ensure that services should be written in such a way that they can be
automated for testing. Test automation is necessary to ensure services can be upgraded, re‐
factored, etc. without breaking other services that use them. The Contractor should ensure that
all services should be inherently versioned and all invocations must specify the version of service.
5. The solutions design should provide for service abstraction, to control what part of the service
logic of a particular application needs to be private (hidden) and which parts need to be made
public (consumable).
6. The solution should not only be modular in nature, but be adaptive to converse with other
technology components such as platforms and databases, complete with management suites or
with the induction of adaptors and interfaces or even smaller bespoke solutions to support the
same.
7. All Websites & Mobile APPs must take into account appropriate security, performance, efficiency and
maintainability issues based on the functional, technical and non‐functional requirements and
the defined SLAs.
8. The solution must be supported by at least ‘N‐2’ versions of any underlying products. This will be
required in case some / other functionalities become non‐functional upon deployment on the
latest version, or in case a roll‐back is required.
9. Products must be supported in terms of upgrades, bug fixes, functionality enhancements and
patches to cater to changes to statutory requirements by their respective OEM for the entire
duration of the contract plus 6 months after end of contract. OEM support should be made
available on all deployed versions for the contract period.
10. The Contractor shall provision for following hosting environments –
 Development Environment
 UAT environment
 Production Environment
 Staging Environment
 DR Environment
11. Data will be owned, shared, controlled and protected as a corporate asset of AAI.
12. Data should only be accessed through application / interfaces for create, update and delete.
There should not be any direct access to the data layer for users.
13. The Contractor shall provide the details of data synchronization strategy both in batch mode and
in real time. AAI, in consultation with Contractor, shall decide on the methodology of data
synchronization based on service requirements

34 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

7.2.2.4. Deliverable(s):
7.2.2.4.1. High Level Design (HLD) should include Solution Architecture, including:
a. Business Architecture
b. Application Architecture
c. Integration Architecture
d. Technology Architecture
e. Security architecture
f. Deployment Architecture
7.2.2.4.2. Low Level Design (LLD)

8. Solution Development, Testing and Go‐Live of solution

8.1. Development of AAI Website 2.0 & Mobile APPs
8.1.1.Based on the approved design and requirements finalized, the Contractor will undertake development
of solution
8.1.2.The Contractor will be responsible for supplying the application, licenses, database and related
software, integration tools and installing the same so as to meet the requirements mentioned in various
sections of this RFP.
8.1.3.The Contractor needs to provide configuration, customization and installation reports to AAI. In case of
any COTS products, the Contractor should follow disciplined approach (as per the best practice defined
by the OEM) for configuration and customization which should not restrict AAI for any future upgrades
to its solution.
8.1.4.The Contractor should ensure solution sustainability to meet all RFP requirements, any additional
procurement required will have to be taken by the Contractor with no additional cost to AAI
8.1.5.The Contractor shall also supply any other tools & accessories required to complete the integrated
solution per requirements. For the integrated solution, the Contractor shall supply:
8.1.5.1. Software & licenses
8.1.5.2. Tools, accessories, documentation and prepare a list of items supplied. Tools and accessories
shall be part of the solution. Contractor should provide technologies matrix.
8.1.5.3. Supply latest supported version of all software to support the solution and any other software,
tools and bolt‐on/add‐on application.
8.1.5.4. System Documentation: System Documentation both in hard copy and soft copy.
8.2. Solution Testing
8.2.1. Planning for Testing
8.2.1.1. Once the SRS is approved and design has started, the Contractor would prepare all necessary
Test Plans (including test cases), i.e., plans for Unit Testing, Integration and System Testing and User
Acceptance Testing.
8.2.1.2. Test cases for UAT would be developed by Contractor.
8.2.1.3. The Test Plans also include planning for the testing to demonstrate the ability to integrate with
3rd party solutions. The Test Plans should also specify any assistance required from AAI and should
be followed upon by the Contractor.
8.2.1.4. The Contractor is required to get approval on the Test Deliverables (Strategy, Plan, Designs
and Specifications etc.) in order to commence the testing for the proposed solution.
8.2.1.5. The Contractor is required to make all necessary arrangements for testing (integration,
system, functional and user acceptance) including the preparation of test data, scripts where
necessary; and procurement and setup of test environments and shall be the responsibility of the
Contractor.
8.2.1.6. Deliverable(s):
a. Test Plan

35 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

b. Test Case Specification

8.2.2. Unit Testing, Integration Testing, UAT
8.2.2.1. Contractor shall perform the testing of the solution based on the approved test plan, document
the results and shall fix the bugs found during the testing.
8.2.2.2. It is the responsibility of Contractor to ensure that the end product delivered meets all the
requirements (including functional and technical requirements) of the project processes specified
in the RFP.
8.2.2.3. Contractor shall carry out the unit testing of the application in accordance with the approved
test plans.
8.2.2.4. After successful unit testing of all components, Contractor shall conduct integration testing in
accordance with the approved test plans. This shall include exhaustive testing including functional
testing and security testing. Functional testing will be led by the Contractor’s domain experts.
8.2.2.5. Contractor will plan all aspects of UAT (including the preparation of test data) and obtain
required assistance from AAI to ensure its success. AAI will assemble representatives from different
user groups based on inputs from Contractor and shall facilitate UAT. Contractor shall make the
necessary changes to the application to ensure that ‘Website and Mobile APPs’ successfully goes
through UAT.
8.2.2.6. Contractor shall be required to make necessary changes in the SRS as well as other necessary
documents based on the changes made during UAT.
8.2.2.7. It is the responsibility of the Contractor to ensure that all required infrastructure to conduct
the User Acceptance Testing are installed at required locations.
8.2.2.8. For the purposes of this RFP, User Acceptance will include successful service provisioning to
stakeholders on the proposed solution to the satisfaction of the AAI.
8.2.2.9. Deliverable(s):
a. Test Logs
b. Test Data
c. User Acceptance Report
8.2.3. Performance Testing
8.2.3.1. Performance testing of the solution would be carried out using the envisaged peak load with a
multiplier, to monitor the application response times and other performance parameters. Non‐
functional Performance testing would be carried out every 6 months to ensure the application
performance is as per requirement. Any additional hardware, software and any other components
required to meet the performance SLAs, would be provided by the Contractor.
8.2.3.2. Contractor is required to submit the report for the performance testing. The testing will be
monitored by AAI.
8.2.3.3. Performance testing would include load / stress testing. This would need to be carried out on
the exact architecture as would be used in the production environment (solution architecture as
well as computing capacity). All necessary tools to carry out testing would be provided by
Contractor.
8.2.3.4. Contractor shall test the performance of the deployed solution against certain key parameters
defined in requirements and the service level metrics described in this RFP. Such parameters
include request load time, response time, transaction time, work‐flow processing time, volume,
concurrent sessions supported by the system, Time for recovery from failure, Disaster Recovery
drill etc.
8.2.3.5. The performance/load testing also includes verification of scalability provisioned for catering to
the requirements of application volume growth in future.
8.2.3.6. The solution should be designed to remove all single point failures.
8.2.3.7. Appropriate redundancy shall be built into all the components to provide the ability to recover
from failures.

36 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

8.2.3.8. The Contractor shall perform various tests including security, load balancing, Active‐active
testing, DC/DR failover tests to verify the availability of the services in case of component/location
failures.
8.2.3.9. Deliverable(s):
a. Performance Test Reports
b. Load Test Report
8.3. Go‐Live Criteria
8.3.1. 'Go‐Live' of the project is defined as the date on which all services/modules specified in the milestones
are fully operational, and a subsequent two‐month observation period has been successfully
completed. The below describe the criteria of Go‐live:
Requirement Criteria of Go‐live

• AAI Website 2.0 and Mobile APPs are up and running as per the defined
Up and running scope of work.

Signed‐off UAT • Signed‐off UAT report, ensuring all issues raised during UAT have been
report resolved.
Safe to Host • Security Audit has been conducted by a CERT‐In empaneled agency and
Certificate corresponding findings have been mitigated in the solution, without any
additional financial implication to AAI.
 The software developed for AAI Website 2.0 & Mobile APPs shall be audited
by the CERT‐In empaneled agency from a security and controls perspective.
Following are the broad activities to be performed by the Agency as part of
Security Audit. The security review shall include the following activities:
1. Audit of Application security mechanisms
2. Assessment of authentication mechanism provided in the application
/components/modules
3. Assessment of data encryption mechanisms implemented for the
solution
4. Assessment of data access privileges, retention periods and archival
mechanisms
5. Application security features incorporated etc.
 The Contractor is required to provide “Safe to Host” certificate as per latest
GIGW guidelines before go‐live of complete solution. Contractor shall get the
“Safe to Host” certificate by 3rd party CERT‐IN empaneled auditors prior to
Go‐live.

Compliance to  The Contractor shall provide compliance to various guideline mentioned in

latest WCAG, this RFP.
GuDApps etc.

Certified Qualified  Quality Audit has been conducted by STQC/3rd party audit agency as per
Website (CQW) latest GIGW guideline and corresponding findings have been mitigated in the
Certificate solution, without any additional financial implication to AAI.
 Contractor shall provide Certified Qualified Website (CQW) Certificate from
STQC/3rd party audit agency for the compliance of latest GIGW

37 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Data migration &  Contractor shall migrate the entire data from AAI website 1.0 to AAI website
Quality 2.0 and mobile APPs as per SOW
 The Contractor shall perform the Data Quality Assessment for the entire data
 The errors/gaps identified during the Data Quality Assessment shall be
addressed by Contactor before moving the data into production
environment.

8.3.2.3rd Party Audit: The entire solution is designed, developed, tested, integrated, Deployed and made Go‐
live in accordance to the defined scope of work and project deliverable documents submitted by the
contractor.
8.3.2.1. For this purpose, the contractor must engage a 3rd party agency to audit the entire solution,
post approval of AAI.
8.3.2.2. Project deliverable document that have been submitted by the contractor must be audited
by the appointed 3rd party agency.
8.3.2.3. Appointed 3rd party agency must audit the entire solutions to validate if the solution comply
all the points mentioned in SOW.
8.3.2.4. Appointed 3rd party agency must audit the entire solutions to validate if the solution is
designed to remove all single point failures and appropriate redundancy is built into all the
components to provide the ability to recover from failures.
8.3.2.5. Appointed 3rd party agency must audit the manageability requirements such as remote
monitoring, administration, configuration, inventory management, fault identification etc.
8.3.2.6. The contractor needs to prepare and provide all requisite information/documents to third
party auditor and ensure that there is no delay in overall schedule.
8.3.2.7. The Agency shall verify the accuracy and completeness of the information captured by the
Service Levels monitoring system implemented by the Contractor.
8.3.2.8. The aforesaid auditing activity must be taken up by the contractor without any additional
financial obligation to AAI.
8.3.3.Deliverable(s):
a. Defect Reports
b. Post Go‐Live:

i. Updated system design documents, specifications,

ii. Latest source code, application deployment files, configuration files for entire solution
iii. Updated user manuals, administration manuals, training manuals etc.
iv. Software change logs etc.

38 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

9. Exit and transition management

The responsibilities of the Contractor pertaining to exit management after the end of the contract or in‐between
the contract is as follows: ‐
9.1. The Contractor shall submit its structured and detailed Transition and Exit Management plan before 1 year
of expiry of contract or within 6 months from date of request to exit from the current contract.
9.2. The Contractor needs to update the Transition and Exit management plan one year before the contract
expiration and submit the same to AAI for approval and sign‐off which shall supersede the initial plan
9.3. All risk during transition stage shall be properly documented by the Contractor and mitigation measures
shall be planned in advance so as to ensure a smooth transition without any service disruption.
9.4. Replacement of key resources during exit management shall be subject to AAI approval.
9.5. Service Level ownership, during exit, shall belong to the Contractor.
9.6. Immediately prior to the initiation of the exit, the Contractor shall provide for an updated plan for approval
of the AAI.
9.7. At the end of the contract period or during the contract period, if any other agency is identified or selected
for providing services related to the Contractor’s scope of work, the Contractor shall ensure that a proper
and satisfactory handover is made to the other agency. This shall include transfer of all assets (Software,
tools and all the documents) in working conditions with warranty after inspection and approval of AAI. If
any upgrade, repair, replacement is required Contractor will carry out the same at no extra cost to the AAI.
9.8. The Contractor shall adhere and align itself with the transition and knowledge transfer plan of the new
Contractor.
9.9. The Contractor shall ensure business continuity i.e. business as usual of complete solution during exit
management. The Contractor shall be in complete ownership of all scope related items.
9.10. The Contractor must ensure that no end of support products (software/tools) exist at time of transition for
up to 12 months from the end of contract (including any extensions) and should ensure equivalent or better
replacement/refresh.
9.11. The transition and exit management period will start 6 months before the expiration of the contract. The
Contractor will provide shadow support for at least three months and secondary support for an additional
three months before the end of the O&M period or termination of the contract, as applicable at no
additional cost to AAI during the period of secondary support. In case of termination, the exit management
period will start from effective date of termination or such other date as may be decided by the AAI but not
later than 6 months from effective date of termination.
9.12. Closing off all critical open issues as on date of exit. All other open issues as on date of Exit shall be listed
and provided to AAI.
9.13. The Contractor shall provide necessary knowledge transfer and transition support to the incoming
Contractor. The deliverables are indicated below:
9.13.1. Updated transition plan on periodic basis
9.13.2. Complete documentation for the entire system handed over to the AAI/new Contractor.
9.13.3. Handover of all AMC support related documents, credentials etc. for all OEM products
supplied/maintained in the system.
9.13.4. Handover of the list of complete inventories of all assets created for the project.
9.13.5. Assisting the new Contractor /AAI with the complete audit of the system including licenses and
assets.
9.13.6. Detailed walk‐throughs and demos for the solution.
9.13.7. Hand‐over of the entire software including source code, program files, configuration files, setup
files, project documentation, user IDs, passwords, security policies, scripts etc.
9.13.8. Hand‐over of the user IDs, passwords, security policies, scripts etc.
9.14. Knowledge transfer of the system to the incoming Contractor to the satisfaction of the AAI per the specified
timelines.

39 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

9.15. The Contractor shall be released from the project once successful transition is completed by meeting the
parameters defined for successful transition
9.16. In case the Contractor fails to observe any of the above points, the Contractor shall not be released and all
the pending payments shall be put on hold till the successful completion of the exit management to the
satisfaction of the AAI.
9.17. Key artefacts (not limited to) required to be prepared for the purpose of exit include:
9.17.1. Software Documentation
 Design Documents
 Software Requirement Specifications
 Requirements Traceability Matrix
 Source Code
 Approved Versions
 User Manual
 Search Tool Manual
 Test Plan & Cases
 DC / DR Documentation
9.17.2. Asset (DC / DR), if any
 Asset Register
 S/w End‐of‐Life Details (s/w: for COTS)
 S/w End‐of‐Shelf Details (s/w: for COTS)
 S/w Licenses details (in case of COTS & Enterprise tools)
9.18. Operations Documentation
 Updated Runbook if any
 Incidents list with RCA
 Computer Based Training Manual
 SLA compliance reports
 Training Presentation
 ToT‐ Training Manual
 User Training Manual
9.18.1. Project Governance Documentation
 Pending Action Items List
 Activities, Dates, Responsibility

10. Solution Documentation

10.1. The Contractor shall document all the installation and commissioning procedures and provide the same to
the AAI within one week of the completion of the go‐live.
10.2. The Contractor shall be responsible for preparing process documentation relating to operation and
maintenance of the solution.
10.3. All documentation will be supplied both in Hardcopy and Softcopy format.
10.4. Each process document shall clearly define the roles and responsibilities, detailed steps for execution the
defined task, detailed configuration steps etc.
10.5. AAI expects the Contractor to document the operations and management processes as per standards
defined in “Compliance to Standards and Certifications”.

40 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Annexure ‐ B
Scope of Work – Manpower experience & qualification

Title Exp. Qualification Project Experience

Administrator Minimum BE/B.Tech degree in • Experience in managing complex projects, expertise
Administrator Computer Science/IT or in Agile methodologies, and proficiency with
experience 6 equivalent field. project management tracking tools.
years • Utilize Agile methodologies to manage workflows
and deliverables.
• Proven experience in managing large‐scale projects.
• Excellent organizational and communication skills.
• Track progress using Project Management tools and
adjust plans as necessary manage end‐to‐end
project lifecycle
• Manage backup and disaster recovery processes.
• Experience in Install, configure, and update
tool/software/Middleware
• Experience in Manage network configurations and
ensure connectivity to servers.
• Experience in Manage user accounts and access
permissions on servers.
• Experience in Manage database
• Experience in up‐keeping of website & Mobile APP
Back‐end Minimum BE/B.Tech degree in • Candidate should have specific hands‐on experience
Developer Computer Science/IT or as the Architect of a large‐scale software system
Back‐end equivalent field. using open source stack.
Developer • The candidate must also have hands on experience in
experienc designing, developing, testing and deploying high
e performance and throughput systems.
4 years • The candidate must have strong expertise in the core
technologies for the profile. Experience with the
specific tools in the technology stack (or
equivalents) is preferred.
• Experience in automated builds, deployments,
debugging, and other open source tools are
required.
• Familiarity in working with Agile/Scrum
methodologies.
Front‐end Minimum BE/B.Tech degree in • Work on developing and maintaining a major project
Developer Computer Science/IT or encompassing both mobile and web platforms.
Front‐end • Collaborate with designers and backend developers
equivalent field.
Developer to integrate features.
experienc • Optimize applications for maximum speed and
e scalability.
3 years • Proficiency in HTML, CSS, JavaScript, and modern
front‐end frameworks (React, Angular).
• Familiarity with RESTful APIs and version control
systems like Git.
• Familiarity in working with Agile/Scrum
methodologies.
• Nice to have: Experience with mobile development
frameworks (React Native, Flutter).

41 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Functional Minimum BE/B.Tech degree in • Develop and execute functional test plans and test
Tester Computer Science/IT or cases.
Functional • Proficiency in test automation frameworks and tools
equivalent field.
Tester (e.g., Selenium, Testing, JUnit).
• Knowledge of SQL for database testing and data
experienc
validation.
e
• Basic scripting skills in languages such as Python or
3 years
JavaScript for creating automated test scripts.
• Understanding of API testing tools like Postman or
SoapUI.
• Familiarity with mobile testing tools and frameworks
(e.g., Appium).
• Familiarity in working with Agile/Scrum
methodologies.
UX/UI Expert Minimum BE/B.Tech degree in • Proficient skills in design software like Adobe
Computer Science/IT or Photoshop/ wireframe tools (e.g., Adobe XD)
UX/UI Expert • Proficiency in HTML, CSS, and JavaScript for rapid
equivalent field
experienc prototyping, working knowledge of front‐end
e OR development technologies.
4 years • UI/UX Designer with experience in designing
BS/MS in Human‐ Computer
websites for public sector undertakings (PSUs)
Interaction, Interaction
(Good to have).
Design or equivalent field • Design intuitive and user‐friendly interfaces for web
OR and mobile.
• *Strong portfolio, excellent design skills in design
Certifications in UI/UX design tools like Adobe XD, Sketch, or Figma.
(optional) • Familiarity in working with Agile/Scrum
methodologies.
Content Min 2 years Graduate with proficiency • Good Knowledge of English and Hindi Language
Uploader in Computer Application  Experience in data entry operations/Content
editing.
 The role involves uploading, managing, and
organizing content to ensure accuracy and
compliance with standards.
 Upload and update content on the website.
 Ensure content accuracy, formatting, and
compliance with guidelines.
 Maintain content organization and manage
content schedules.
 Experience in content management and
uploading.

42 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Annexure ‐ C
Scope of Work – Guiding Principles for on Premise Deployment

The proposed solution should adhere to the following principles

1. Solution provisioning & Commissioning

1.1. The complete solution (AAI Website 2.0 and Mobile APPs) shall be hosted in AAI, DC&DR premises and AAI
shall provide the resources such as VMs, OS, network & storage. All other components of the solution,
including any middleware, tools, any software etc. are to be provided by contractor.
1.2. Contractor shall assess and recommend the infrastructure requirements (including VM, Memory, Storage
Disk space, backup space, CPU, Network Bandwidth, Networking etc.) for hosting and maintaining all
required applications/ services at design stage of project keeping high availability, scalability, load
management, security, upgrade and continuous monitoring of solution.
1.3. The Contractor is required to prepare and submit along with their technical proposal, the details of
methodologies & computations for sizing & capacity of storage, compute, backup, network and security.
1.4. There should be sufficient capacity (compute, network and storage capacity offered) available for near real
time provisioning (as per the SLA requirement of the Contract) during any unanticipated spikes in the user
load.
1.5. The Contractor will be responsible for adequately sizing the necessary compute, memory, and storage
required, building the redundancy into the architecture (including storage) and load balancing to meet the
service levels mentioned in the RFP.
1.6. The bidder shall provide Enterprise support license of Open Source Software (OSS) for such tools/
software/ middleware for all environments. If Enterprise Support license for such OSS tools/ software/
middleware is not available, then the bidder shall provide the proposed list of commercial‐off‐the‐shelf
(COTS) tools/ software/ middleware with justification.
1.7. If neither Enterprise support license for Open Source Software (OSS) nor Commercial Licenses for COTS are
available for any particular tools/ software/ middleware required for the project, only then OSS with
community support may be considered for the project as an exception. Clear justification for selecting such
tools/ software/ middleware with Community Support for OSS must be provided by the bidder in their
response.

2. Stateless vs Stateful
2.1. While designing the application, contractor should make sure that the application built are stateless
application. While contractor should ensure that only stateless application are present but if there is a need
to have a stateful component for storing of session details the state should be stored in a NoSQL/SQL/In‐
Memory database.
2.2. The storing of state on HTTP cookies should be prevented as HTTP cookies can be tampered with at the
client side and these are required to be transmitted with every request which can increase the size of
the payload and result in unnecessary latency. For storing large state components other shared storage
layer should be used.
2.3. If at all, there is a requirement for client devices to be connected to a single compute (the design should
prevent this), sticky sessions,” session affinity” should be utilized at the load balancer level.

43 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

3. Stability, Scalability and Extensibility

3.1. The solution (Application & Database) shall be constructed in high availability mode with Synchronous
replication. It must have proven scalability credentials to cater to any system load. The solution must
support Failover Clustering and disaster recovery solutions.
3.2. A scalable system is one that can handle increasing numbers of requests without adversely affecting the
response time and throughput of the system. To the extent possible for Web and App, scale out or scale
horizontal architecture should be utilized, where, depending upon the increase of load another instance
should be spawned at run‐time.
3.3. AAI website 2.0 and mobile APPs shall be developed in a such way that it could handle the suddenly
increased traffic.
3.4. Contractor has to decide and explain whether they would be deploying the application on a container or an
OS instance and accordingly should handle the scalability.
3.5. The Solution shall be designed for ease of maintenance and readily allow future functional enhancements.
This shall be accomplished through use of modem design principles like applying principles of modularity,
interface abstraction, and loose coupling.
3.6. The Solution shall be scalable and adaptable to meet future growth and expansion/contraction needs such
that the AAI Website 2.0 and mobile APPs can be expanded on demand and be capable of retaining its
performance levels when adding additional users, functions, and data.
3.7. The webpages & Mobile pages shall be highly re‐configurable, providing ability to reposition and rename
field labels / data fields, remove or "tum‐off' unused fields, maintain data, and allow addition of custom‐
defined fields.
3.8. The Solution shall be adequately flexible to keep up with the changing technology.
3.9. The Solution should also make use of a distributed cache to enhance the scalability of the system.
3.10. Caches can be implemented at various levels including DB cache, server cache, application cache etc.

4. Microservices Architecture
4.1. Contractor is recommended to follow the microservices and serverless underlying Architecture in
development of AAI Website 2.0 and Mobile APP.
4.2. Micro services architecture is an architecture style that structures an application as a collection of loosely
coupled services which enables continuous delivery/deployment of large complex application.IT should be
designed to reduce interdependencies so that failure in one component of the system should not affect
other components and each and every component should be independently deployable in case of change
without deploying the entire application.
4.3. Use of technology agnostic services like REST/ GraphQL for the communication between various
components.
4.4. IP addresses should not be hardcoded and should be discovered using a service discovery service.
4.5. Wherever it is deemed fit use of asynchronous integration services.
4.6. The component failure should be handled in a graceful way

5. Backup & Disaster Recovery

5.1. The solution should be designed with redundancy in mind to ensure NIL impact by failure of one or more
components/services/microservices/ servers or software.
5.2. Data and information are resources that are extremely valuable for the organization; hence data
management processes must be in place to maintain the data.
5.3. While it is important to transform Storage, it is also more important to ensure all the services are getting
properly backed up. For the same, it is important to establish proper policies, by assessing and analyzing
44 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

the environment and ensuring that the data for which backup is not required is either purged or archived
depending upon criticality of data. Contractor should ensure Backup Software deployed on VMs managed
by Contractor that services are backed up.
5.4. It is important to have a DR site where the services can failover in case of a disaster and business can
continue. Keeping in mind that the application is to be built which has to be future ready and at the same
time should ensure that at time of disaster all the services fail over within RTOs and RPOs defined.
Contractor should make sure that storage replication is taken care by Software Deployed on VM managed
by Contractor. For the compute, depending on the RTO, criticality and architecture instances should be sized
on the DR site.

6. Database
6.1. Sensitive data should be in encrypted form in database.
6.2. Contractor should also do a detailed study and advice on the type of databases to be used for each
component (SQL or NoSQL). Each of the database has a specific use case and accordingly each might be
utilized. The database instances can be provisioned as a Database as a Service. In case of SQL, it should be
provisioned preferably in two separate zones/fault domains/update domains/PODS with synchronous
replication to ensure that in case of failure of even a zone/fault domain/update domains/PODS, there is no
Data loss and service can be provisioned instantly from the other zones/fault domains/PODS.
6.3. For SQL (Relational) databases, Contractor should also design the data model of the application with
partitioning where the logical data elements should breakup into multiple entities to have more availability,
performance and maintainability.
6.4. Contractor should ensure Database sync Software deployed on VMs managed by Contractor that services
are synched properly.
6.5. The solution should be database independent and should allow deployment on multiple databases. The
solution should allow integration with other heterogeneous databases irrespective of the choice of
database.

7. High Availability
7.1. As the complete solution, Contract shall provision following environments for hosting– Production,
Staging, Development and UAT at both DC & DR. Production at DC & DR shall be sized at 100% as per
requirement of the project and are required to be highly available in active‐active mode.
7.2. Staging environment shall be sized at 70% as per requirement of the project and are required to be highly
available in active‐active mode.
7.3. All UAT instances should be sized at 40% of the production instance and should be in High availability. All
Development instance should be sized at 20% of the Production instance size and are not required to be
in High Availability.
7.4. Staging environment shall be used as Non‐Functional Test Environment for Stress and Performance testing.
Post Go‐Live, the Production environment must not be used for testing and training purpose.
7.5. For sizing of DR, Contractor should ensure that the DR should be available at time of disaster at DC within
defined RTOs and RPOs. In case of failover to DR site (once disaster is declared) within the defined RTO,
the SLA would not be applicable for RTO period only. Post the RTO period, SLA would start to apply and
should be measured accordingly.
7.6. The solution should be resilient in nature with high availability, disaster recovery and backup & restore
capabilities.
7.7. The speed and efficiency of the solution should not be affected with growing volumes, especially during
search operations, reporting, MIS, online processes and batch processes.

45 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Annexure ‐ D
Scope of Work‐ Features of AAI Website 1.0

Table of Content

Table of Content......................................................................................................................................... 46
1) Corporate Website ............................................................................................................................. 47
1.1) Guest House ............................................................................................................................... 48
1.2) Chairman Corner ........................................................................................................................ 50
1.3) Lost & Found Portal ................................................................................................................... 51
2) Aeronautical Information Management India .................................................................................. 51
3) Retired Employee Portal .................................................................................................................... 52
4) Land Requisition................................................................................................................................. 53
5) Flight Training Organisation No Objection Certificate...................................................................... 54
6) IAP Forum ........................................................................................................................................... 54
7) Civil Aviation Research Organization (CARO) ................................................................................... 55
8) Civil Aviation Training Centre Prayagraj............................................................................................ 56
9) Fire Service Training Centre, Kolkata ................................................................................................ 56
10) Fire Training Centre New Delhi...................................................................................................... 57
11) Kalyanmayee Portal ....................................................................................................................... 59
12) Vigilance Complaint Management System Portal ........................................................................ 59

46 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

1) Corporate Website
Majorly Corporate AAI website features and contents are covered under three sections, namely Corporate section,
Employee section and Airports section.

a) Corporate section:
 Menu and submenu items ‐ All information about the entity and their respective departments, useful for the
citizens and other stakeholders, present in the menu and submenu and mechanism is in place to keep the
information up to date. This also includes the history of the AAI, its structure and other basic details.
 Corporate Banner ‐ It's a bilingual banner which is used to flash the very important messages to the first fold
of AAI Web Portal through the banner and it's having linked pdf file.
 AAI important notice ‐ It's the publicly visible section where we can publish the important information and also
pin the particular information. The concerned title may have linked pdf file or external URL.
 AAI latest tender – Latest tender shows in this section and it's also linked to main tender search page. The
particular tender can be pinned in "Latest Tender" block.
 Photo gallery ‐ It's a corporate photo gallery which are organised in event wise.
 Social media feeds ‐ Latest YouTube videos, latest Twitter feeds and latest Instagram photos/videos are
provisioned for this section. For more feeds the individual visits concerned application.
 Quick link bar – Most of the major and important section is incorporated in Quick Links section like Lost &
Found, RCS Udan, Career, AIM India, Retired Employee Portal, etc. Its purpose is to easily access to major and
important section of the portal.
 Important link ‐ It's also having important links to navigate quickly but not a major part of the website.
 AAI Media ‐ All the PR related content like Press Release, AIBM, Photo Gallery, Electronic and Print media
coverage are published here.
 Training Corner ‐ It's a training corner of AAI Web Portal from where we can navigate to training institutes or
get information about particular training institute.
 Scroll bar ‐ It's the very important section on the top of the portal where we can publish the important
information for a particular time period. The concerned title may have linked pdf file or external URL. We can
scroll the message URL wise also.
 Footer bar ‐ It's having some generic links like contact us, RTI, Official Language, FAQs, T&C, Privacy Policy, etc.
 Quick navigation bar ‐ The following links are available in quick link bar such as Careers, Media, Medical, AIM‐
India, AirSewa, Lost & Found, OPAAS, PromoteAAI, CPP Portal, BDP, Nocas, Cargo, RCS UDAN, Retired Emp
Portal, MoCA Website.
 Careers
 Current Vacancies
 Display recruitment results
 On‐line recruitment

b) Airport Section:
 Home: Serves as a landing page for the respective airport. Also contains links to the airport facilities like ATMs,
Eat and Dine, Accommodation, and so on.
 Airport Information:
 About Airport
 Domestic and international Terminals
 The Management Team, Our Organization, Values & Beliefs, Quality, Environment, CSR, Business Awards etc.
 Media including News & Events, Fact Sheet, Photo Gallery and Milestones
 Flight Schedule: Displays a detailed schedule for all the flights departing from, or destined to, the respective
airport.
 Passenger Info: All information relevant to facilitation of passengers, like parking, medical facilities, baggage
facilities, Free Wi‐Fi, Mobile Charging Point, Smoker Lounge, Vending Machines, Prayer Room Parents Room,
47 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Currency Exchange facilities, Business & VIP facilities, Disability Access and facilities for Disabled Access
Information etc. are listed here.
 Transport: Contains info regarding the transport facilities available at the airport thereby enabling last mile
connectivity such as Parking, Car Rental, Bus, Train, Passenger pickup Area (Bus/Car) etc.
 City Info: All info related to tourism can be found here such as Cruise, theme parks, Religious/heritage sites,
tours, Zoos etc.
 Security Info: This tab consists of security related information like various do’s and don’ts, prohibited items,
lost and found baggage, Unattended Items, Emergency Contacts including Embassies information, Emergency
Numbers and other info relevant to the subject.
 AAI Airports: This tab contains links to all AAI owned airports.
 Navigation Pane: Every page on the respective airport website contains a quick navigation pane which provides
links to the facilities available at the airport.
 Footer: Contains useful links like Lost & Found items, Airsewa grievances, PGO details, FAQs, Cargo, Contact
details, Map and so on.
 Cargo Handling Facilities including Clearance Procedure, Schedule of Charges etc.
 Any other statutory or general information helpful to the passengers.

c) Employee Section:
 Circulars & Orders ‐ The employee can see related information like circulars, policy, reports, manuals, etc.
 Events ‐ The documents/images of events organized by AAI are updated here.
 Awards ‐ The awards received by AAI employees can be seen here.
 Employee Search ‐ To search employee and creator/publisher by department, region, airport, etc.
 Tender ‐ It's used to create new tender and contract award.
 Others ‐ This menu contains Employee Responsibilities, Gender Equalities, National Register and New Features.
 Help ‐ It contains text and video manuals helps in uploading and updating files.
 Banner ‐ It's a bilingual banner which is used to flash the very important messages to the first fold of AAI Web
Portal through the banner and it's having linked pdf file.
 Photo Gallery ‐ It's a photo gallery which is organized in event wise for AAI Employees.
 Announcements ‐ It contains important announcements/messages can be seen or downloaded through the
link.
 Important Link ‐ It's also having important links to navigate quickly on the linked page or other website i.e. IAP
discussion forum, Guest House Booking, AAI Ideation, AAI Blog, AAI Holiday calendar, IAA Training nomination
form.
 Scroll bar ‐ It's the very important section on the top of the portal where we can publish the important
information for a particular time period. The concerned title may have linked pdf file or external URL.
 Quick Navigation bar – The following links are available in quick link bar such as Media, Medical, AAI‐Mail,
Parivartan, Eoffice, Biometric Attendance, CPP Portal, GeM, AIM‐ India, AAI Survey, Safar, AAI Ideation, Gagan,
IAP Forum Discussion, RCDU.
 Reminder Section‐ Employee may configure reminder in future date.
 Role based access has been provided for following features‐ Airport Master plan, Airport Infrastructure details,
RESA maintenance, RCDU ,etc.
 Survey forms may be created as per need of User Directorate.
 Ideation – employees can publish their ideas and other employees can comment on the same.

1.1) Guest House

Airports Authority of India manages guest houses in different location of the country. This system is offering to
book the guest house for all the employees of AAI.

These features are available only for employees after login

48 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

Users: There are three types of user in this system

 AAI Employees: These users can book guest house subject to availability.
 Guest House Admin: This user will be responsible to manage all guest house related details i.e. Rooms
available, Location details, Facilities available, etc. This will be an AAI Employee.
 Guest House Supervisor: This user will be able to see bookings for the guest house.

A. AAI Employee Section

 Book Guest House
 My Bookings
 Room Occupancy History

B. Guest House Admin Section

Guest house admin is responsible to manage all guest house related details i.e. Rooms available, Location details,
Facilities available, etc.

 Book Guest House: The admin can book a guest house for self and others. Quota Booking Guest house admin
can book a room on behalf of other employee/dependent, in that case room/s will be booked from Quota
Rooms. If rooms are not available, then system gives error accordingly.
 List of Guest House: Admin will see a list of all guest houses assigned to handle after clicking ‘List of Guest
House’.
 Room Occupancy History: Admin can check the room reservation as per the guest houses assigned.
 Admin can view the guest house room occupancy history month wise.
 Manage the guest house for room availability, advance booking time, adults/children limit etc.

49 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

 Admin can cancel the booking if found anything wrong or as per requested by the guest house supervisor.
 Admin can do the early checkout if guests leave the room before checkout time.

C. Guest House Supervisor

Booking Cancellation Process

Booking History:
 Request to the guest house admin for a booking cancellation if found anything wrong.
 Check all the bookings done by AAI employees under this section.
 Extent the room booking during the guests stays as requested by them.
 Do the early checkout if guests leave the room before checkout time.

Book Guest House:

 Book a guest house for others.
 Request to the guest house admin for a booking cancellation if found anything wrong.
 Extent the room booking during the guests stays as requested by them.
 Do the early checkout if guests leave the room before checkout time.

1.2) Chairman Corner

The Chairman corner is an exclusive portal designed for the internal employees of the Airports Authority of India.
This is accessible only after login, this portal serves as a platform where employees can directly communicate their
suggestions and constructive feedback to the top management.

URL: https://www.aai.aero/

Login with the registered username and password (Only internal employees of AAI can Login)

50 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

User Roles:

1. Employee Dashboard
2. Chairman Office Dashboard
3. Department Dashboard

1.3) Lost & Found Portal

URL: https://www.aai.aero/

The Lost and Found portal of the Airports Authority of India (AAI) is designed to assist the passengers who have
misplaced personal belongings within airport premises, service aims to enhance passenger experience by ensuring
that lost items are efficiently managed and returned to their owners whenever possible.

1. Process for Adding Lost/Found Item Detail

 Log in: Use admin's credentials.
 Fill Form: Fill the required information of the received item (lost item) and publish the same.

2. Lost and Found Section (Public Access)

In the Lost and Found Section the passenger who has lost an item logs into the AAI website.

 Go to the Lost and Found section on AAI Website.

 Search for Item: Select airport, terminal, category, and date Click "Search."
 View Results: System displays a list with: Serial No, Item Code, Category, Airport, Description, Date Item Found,
Contact Details, Operation (e.g., Initiate Claim).
 Initiate Claim: Fill in email, mobile number, and description and Submit the claim. Once the user initiates a
claim, email notification is sent to Admin of respective Airport.

3. Claim Process

 Claim Received: It shows the list of claims initiated by the user. Admin verifies the item and description provided
by the user. In case of match, Admin sends verification link.
 Claim Link Sent: Verification link sent to user.
 Claim Docs Received: Admin can view documents uploaded by user via verification link. Admin can review the
documents.
 Claim Docs Partially Accepted: User re‐uploads required documents.
 Claim Docs Accepted: Admin approves documents.
 Item marked as “Settlement in Process.”
 Claimant Didn't Turn Up: Status updates if user doesn't claim item in time.
 Claim Settled: Admin settles claim, item removed from catalogue.
 Declined: Admin declines claim with reason.

4. Adding Terminal‐Specific Contact Person Detail for Lost/Found

Log in with admin's credentials.

Fill Form: Fill the required information of the contact person. One contact details per airport.

Duplicate attempts show an error with an Edit link.

2) Aeronautical Information Management India

URL: https://aim‐india.aai.aero/

51 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

The Aeronautical Information Management includes the following details:

• Banner: Banner on the home page.

• Home: Brief introduction to Aeronautical Information Management.
• eAIP India AIRAC AMDT 04/2023
• AIP Supplements: Aeronautical information publication supplements with linked PDFs or external URLs.
• Monthly NOTAMs Summaries: Month‐wise A and C series NOTAMs.
• Aeronautical Information Circulars (AIC): Linked to an external URL.
• eTOD (Electronic Terrain and Obstacle Data): Digital representation of terrain and obstacles.
• Airspace Use Plans (AUP): Listed for Delhi and Chennai.
• Operational Hours of ATS, COM & MET Units: Displayed for all airports.
• Cost/Subscription Charges for AIS Products 2023: Includes subscription charges and linked PDFs.
• QMS Implementation: QMS certificates for Aeronautical Information Services (AIS).
• Service Level Agreements: SLAs help improve communication, set mutually agreed standards, and measure
service effectiveness between AIS (Aeronautical Service Provider) AAI and data originators at various airports.
• Subscribe for E‐mail Notification: Sign‐up for email notifications on new publications.
• Documents: Public Documents, Restricted Documents, AIS Workspace
• Feedback: Submit user feedback.
• Aviation Links: Useful links including Airports Authority of India, Bureau of Immigration, IATA, Pawan Hans
Helicopters Ltd., ICAO, Ministry of Civil Aviation, DGCA, and Airports Council International.
• Contact Us: Contact information.
• Disclaimer: Standard site disclaimer.

3) Retired Employee Portal

URL: https://rep.aai.aero/

Retired employee portal (REP) of AAI is a web portal to facilitate medical reimbursement online claimed by
retired/separated employee of AAI.

Retired employee portal is broadly classified into four sections:

 Retired employee section

 Reviewer section
 Approver section
 HR verifier section

52 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

4) Land Requisition
URL: https://landmngt.aai.aero/

The AAI Land Requisition Portal provides a structured and streamlined process for users and managers to handle
land requisitions and lease renewals.

Types of Roles:

There are two types of roles:

 Users can register, apply for land, track application status, and respond to clarifications.
 Managers have a dashboard to oversee applications, request clarifications, and make decisions on acceptance
or rejection of applications.

1) Public Access (Registration and Login)

 Users can register and login to the portal to access various features.
 Menu and Submenu items: Information about land requisitions for citizens and stakeholders.
 Banner: Banner is displayed on the home page for general announcements or information.

2) User Access (Post Login)

Fresh Applications:
 My Information: Users can view and manage their profile information.
 Apply for Land: Users can submit new land requisition applications.
 Draft Applications: Users can track, modify, or delete draft applications.
 Submitted Application: Users can view all their submitted applications.
 Clarification Submission: Users can respond to clarification request from managers.
 Application Status: Users can track the status of their applications.

Renewal Applications:

 Renewal of Lease: Users can submit applications for lease renewal.

 Submitted Renewal Applications: Users can view all their submitted renewal applications.
 Renewal Application Status: Users can track the status of their renewal applications.

3) Manager Access (Post‐Login)

Manager Dashboard:
 My Information: Managers can view and manage their profile information.
 Received Application: Managers can track details of all received applications and update their status.
 Seek Clarification: Managers can request additional information or clarification from users.
 Under Review: Managers can view applications under review and either accept or reject them.
 Accepted/Rejected Application: Managers can track all accepted or rejected applications.

Manager Renewal Application:

 Received Lease Renewal: Managers can track details of all received lease renewal applications and update
their status to under review.
 Under Review Lease Renewal: Managers can view lease renewal applications under review and either accept
or reject them.

53 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

 Accepted/Rejected Lease Renewal: Managers can track all accepted or rejected lease renewal applications.

5)Flight Training Organization No Objection Certificate

URL: https://atm‐ftonoc.aai.aero/

Flight Training Organisation No Objection Certificate Application System is an initiative to streamline and expedite
process of obtaining No Objection Certificate (NOC) from Air Traffic Management Point of View from Airports
Authority of India.

1) Registration (Public Access)

 Users can register and login to the portal with the registered email id.
 Menu and Submenu Items: It contains all the necessary information about the Flight Training Organisation No
Objection Control Portal.
 Banner: Banner is displayed on the home page.

2) User Access Features (Post Login)

 My Information: User can view their profile information.
 Apply for FTO NOC: User can apply for FTO NOC through this section.
 Draft Form: Users can track, modify, edit, delete, draft applications.
 Submitted Form: Users can check all their submitted applications.
 Sought Clarification: Users can respond to requests for clarification from the manager.
 Accepted/Rejected Form: Users can track the status of their applications, whether accepted or rejected.

3) Manager Access Features (Post‐Login):

 My Information: Managers can view their profile information.
 Received Form: Managers can track details of all received applications and change their status.
 Seek Clarification: Managers can request clarifications from users for any submitted applications.
 Accepted Forms: Managers can view details of accepted forms.
 Rejected Forms: Managers can view details of all rejected forms.

6) IAP Forum
Url : https://iapforum.aai.aero/

The IAP Forum is a platform utilized by Airports Authority of India members to create groups, add members, share
content, and contribute comments in various sections.

Navigation and User Actions:

54 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

 Discussion List: Users can view a list of discussions. The list includes: Discussion Title, Last Updated On.
 User Account Management: Users can access their account details via "My Account."

IAP Community @AAI: Admin can view, create and edit community information.

 Users can see the list of members in the community.

 Users can search for members or topics within the community.
 There is an option to leave the community.

Adding Content and Comments:

 Users can add new content and comments to discussions.

 Users can attach files to their comments or content.
 User can reply to the comments

Group Management:

 Adding Groups: Admin can create new groups.

 Admin can manage: Groups, Group Types, Group Roles, Group Members.

7) Civil Aviation Research Organization (CARO)

URL: https://caro.aai.aero/

Civil Aviation Research Organization (CARO) is a collaborative research platform catering to R&D requirements
projected by both Air Navigation Services (ANS) and Airport/engineering fields under one roof.

 Menu and Submenu Items: Contains comprehensive information about CARO Hyderabad.
 Banner Description: A corporate banner used for displaying very important messages prominently on the
homepage.
 Useful Links: Quick navigation links to essential pages/Websites.

1) Registration (Public Access)

2) Admin Access (Post Login)

 Dashboard: It shows the number of Total Applications, Pending Applications, Accepted Applications, Declined
Applications.

55 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

 Pending Applications: It shows the list of applications awaiting action (reject or accept).
 Accepted Applications: It shows the list of accepted applications. The user can export the list in excel and pdf
format.
 Visa Invitations: It shows the list and visa details of those applicants who have applied for visa.
 Declined Applications: It shows the list of those applications which are rejected by the admin. The user can
export the list in excel sheet and pdf format.
 Archived Applications: List of applications where the event has expired.

8) Civil Aviation Training Centre Prayagraj

URL : https://catc.aai.aero/

The CATC, Prayagraj subdomain includes detailed menus, an attention‐grabbing banner, regularly updated news
and announcements, an organized photo gallery, and quick access to important links.

 Menu and Submenu Items: Contains comprehensive information about CATC Prayagraj. Details about various
courses available at CATC, Prayagraj.
 Banner Description: A corporate banner used for displaying very important messages prominently on the
homepage.
 News and Announcements: Section for important announcements and news updates. Viewable and
downloadable content
 Photo Gallery: A visual representation of events organized by CATC. Event‐wise categorization for easy
navigation.
 Important Links: Quick navigation links to essential pages.
 Footer: It contains following features: Image Gallery, Contact Us, Disclaimer, Terms and Conditions

9) Fire Service Training Centre, Kolkata

URL: https://fstc.aai.aero/

User Registration Flow

User Registration:

Private:

 Fill personal details such as Name, Gender, Email, Address, Mobile, Aadhar Upload, Math question.
 Validate details (email format, Aadhaar, mobile).
 Email confirmation and verification link sent, One‐time login to set password.
 Password setup with security requirements and Account creation confirmation.

Organization:

56 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

 Fill official details such as Email, Nodal Officer Name/Designation, Department, Organization, Location,
Management Level, Address, Mobile, Email, Authorization Letter Upload (up to 20 MB), Math question.
 Validate details (email format, Aadhaar, mobile). Email confirmation and verification link sent.
 One‐time login to set password. Password setup with security requirements. Account creation confirmation.

Login as Private User

 Personal Profile: Displays and allows editing of‐ User name, Gender, Mobile number,
 Join Course: Here, user can apply for active training course.
 Submitted Application: View submitted applications.
 Application Process and Selection Criteria: Content for SOP for Online Application Process for Admission
in BTC Course for Private Candidates
 Download Form Format: Download different forms such as: Indemnity Bond (PDF), Physical Standard
Form (PDF)

Login as Organization User

 Nodal Officer Profile: Displays and allows editing of: Name, Organization, Designation, Department, Mobile
Number
 Apply for Course Options: Here, user can apply for active training course.
 Submitted Application: View submitted applications.
 Application Process & Selection Criteria: Details for BTC Course admission.
 Download Form Format: Download various forms such as Indemnity Bond (PDF), Medical Fitness Certificate
(PDF)

Login as Admin

Private Application Nodal Action:

 Registered User: List of registered users with details

 Course Setting: Edit course settings.
 Application Received: View active applications
 Download Report: View reports for 7 day’s post‐course completion. Reports are downloaded on merit basis of
candidates.
 Archive Application: Archive applications after 7 days

Sponsorship Application Nodal Action:

 Course Setting: View and edit National, International, ICMS courses and dates
 Application Received: View active course applications
 Download Report: View reports for 7 days’ post‐course completion
 Archive Application: Archive applications after 7 days

10) Fire Training Centre New Delhi

URL: https://ftc.aai.aero/

 User Registration:

57 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

User Registration Flow

Private:

 Fill personal details such as Name, Gender, Email, Address, Mobile, Aadhar Upload, Math question.
 Validate details (email format, Aadhaar, mobile).
 Email confirmation and verification link sent, One‐time login to set password.
 Password setup with security requirements and Account creation confirmation.

Organization:

 Fill official details such as Email, Nodal Officer Name/Designation, Department, Organization, Location,
Management Level, Address, Mobile, Email, Authorization Letter Upload (up to 20 MB), Math question.
 Validate details (email format, Aadhaar, mobile). Email confirmation and verification link sent.
 One‐time login to set password. Password setup with security requirements. Account creation confirmation.

Login as Private User

 Personal Profile: Displays and allows editing of‐ User name, Gender, Mobile number,
 Join Course: Here, user can apply for active training course.
 Submitted Application: View submitted applications.
 Application Process and Selection Criteria: Content for SOP for Online Application Process for Admission in BTC
Course for Private Candidates
 Download Form Format: Download different forms such as: Indemnity Bond (PDF), Physical Standard Form
(PDF)

Login as Organization

 Nodal Officer Profile: Displays and allows editing of: Name, Organization, Designation, Department, Mobile
Number
 Apply for Course Options: Here, user can apply for active training course.
 Submitted Application: View submitted applications.
 Application Process & Selection Criteria: Details for BTC Course admission.
 Download Form Format: Download various forms such as Indemnity Bond (PDF), Medical Fitness Certificate
(PDF)

Login as Admin

Private Application Nodal Action:

• Registered User: List of registered users with details

• Course Setting: Edit course settings.
• Application Received: View active applications
• Download Report: View reports for 7 day’s post‐course completion. Reports are downloaded on merit basis of
candidates.
58 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

• Archive Application: Archive applications after 7 days

Sponsorship Application Nodal Action:

• Course Setting: View and edit National, International, ICMS courses and dates
• Application Received: View active course applications
• Download Report: View reports for 7 days’ post‐course completion
• Archive Application: Archive applications after 7 days

11) Kalyanmayee Portal

Url: https://kalyanmayee.aai.aero/

The portal for Kalyanmayee, the Airports Authority of India Women Welfare Association. The site likely includes
information on various welfare activities, initiatives, events, and resources aimed at supporting women and their
families in the AAI community.

• Home: Brief Information about Kalyanmayee: Banner, Photo Gallery, Our Network (Region‐wise details of
Kalyanmayee committee’s activities and the projects they’ve undertaken)
• About Us: Information about the Kalyanmayee portal, as it is a CSR (Corporate Social Responsibility) portal of
the Airports Authority of India. This section includes: details of Management, details of Committees, Vision.
• Projects: Details about various case stories of Kalyanmayee’ s CSR initiatives.
• Events: Images and descriptions of various events organized by Kalyanmayee, such as Women's Day
celebrations.
• Media: This shows a list of CSR activities. This section includes:
• A list of activities sorted by serial number and title.
• Download options for PDF files containing images of CSR activities.
• Pagination to navigate through the list of activities.
• News: A section that displays a list of activities in serial order with titles and download options, including
pagination for easy navigation.

12) Vigilance Complaint Management System Portal

URL: https://cmsvig.aai.aero/

This platform is for lodging vigilance complaints under the jurisdiction of the Chief Vigilance Officer (CVO) of AAI.

a) Citizen Login
1) New User Registration
 Click on “Register new account”.
 Fill out the registration form.

59 | P a g e 6 0
 Name of Work: Development of new AAI Website and Mobile APPs
Document Title: Scope of Work

 Click the “Register new account” button.

2) Existing User Login
 Fill in the Username, Password, and Math question.
 Click the “Login” button.
 Note: If you have forgotten your password, click on "reset password".
3) Lodge a Complaint
 Login to Citizen Login.
 Click on “Lodge a complaint”.
 Fill out the complaint form.
 Click the “Submit” button.
4) Know Your Complaint Status
 Login to the Citizen Login.
 Click on “Know your Complaint Status”.
 View the list of complaints or search for your lodged complaints using your Complaint Number (e.g.,
7|2024).
 Click on the “view” link to see the details.
 Print your complaint by clicking on the “Print” button.
5) Compliant Handling Policy
It includes the compliant handling policies (SOPS) procedures to manage and resolve complaints.

b) CVO Login

Upload Complaint

 Login to CVO Portal.

 Click on "Upload Complaint": Once logged in, click on the "Upload Complaint" button to submit a new
complaint.

Complaint Handling Policy : It includes the compliant handling policies procedures to manage and resolve
complaints.

List of Complaints: Click on "List of Complaints" to view the dashboard.

 Alternatively, click on "My Dashboard" located just before the "User Manual" button.
 View Dashboard: The dashboard displays the number of complaints categorized as Received, In‐Process,
Downloaded, and Closed.

MIS Report: Click on "MIS Report" Tab.

60 | P a g e 6 0