01.2021 - 12.2022

Airport Resource Management System.
Timeliner

About project
The Airport Resource Management System (RMS) is being developed to improve airport operations due to more passengers and strict requirements from airlines and the government.
Users:
4,000 employees

with different access levels

Future plan:
Expansion

More departments and users

Project objective

The aim is to improve airport operations and transparency. The system will help the airport plan and manage its resources better.

The team

1 Solo Designer, 6 Engineers, 8 Analysts, 2 Project Managers, and other professionals from internal and external sources.

MY role

I joined the team a year into the project's development. My role was to dive into the project, establish design processes, enhance user interaction, and address issues. I also contributed to developing new system sections.

Research

I base my work on personal experience. Recognizing the need for specific expertise in airport dispatching product development, I conducted comparative analysis. After convincing stakeholders, I gained access to direct users of the timeliner: dispatchers of technical units and human resources. They manage equipment units and personnel, providing insights into their work conditions, current tools, conveniences, and decision-making processes. This Field research yielded valuable information and formed key hypotheses.

Initially, dispatchers used multiple systems, resulting in multitasking across numerous screens. Yet, they operate in an information-rich environment, accessing tooltips, receiving information via radio and phone, and collaborating with peers. Engaging them without disrupting workflow was crucial. Factors like screen characteristics and room lighting also influenced the process.

Half-Low-Fidelity Designs

The developers had already incorporated the Bulma component library, shaping most user scenario screens, like tables or pop-up windows, from the outset. However, the timeliner began with a simplified design, presenting minimal information. The forthcoming chapter showcases the final timeline screens, portraying a more realistic amount of displayed information.

High-Fidelity Designs

The business aimed to maximize information display on the timeliner and admired the solution our Turkish colleagues implemented. However, it wasn't suitable for Pulkovo even with customization. Still, we used their approach as a reference for information display.

Furthermore, the timeliner acts like a traffic light: red signals a problem, yellow suggests attention, and green indicates everything is fine. Additionally, elements and tasks currently in focus are highlighted, while those needing less immediate attention appear semi-transparent.

Timeline customization

The timeliner offers customization settings, granting users options like choosing a dark theme or adjusting the zoom level. These settings provide flexibility and enable users to personalize their experience with the timeliner.

Other states and screens

Drag and drop a task to another employee

Shift planning. Light theme

Shift planning. Dark theme

Right drawer with flight information.

Details

My role in the project was diverse, as the system was extensive in scope. However, the most significant and interesting work was done on the timeliner, as it is one of the primary tools used for managing the airport. Other sections were also designed for detailed scenario development, but many of them presented as tables, so I will not delve into them extensively in this case.

Certainly, we didn't design all the states directly on the timeliner. Instead, various states were created separately, and documentation was prepared collaboratively with analysts using these components. This method facilitated a more systematic and comprehensive understanding of the different states and their interactions within the timeliner.

Reflections

Collaboration and Communication are vital: Close collaboration with team members, analysts, developers, and airport staff ensured a shared understanding and successful project outcomes. Clear communication and documentation were crucial throughout the process, enabling us to reach project goals and allowing me to find approaches for conducting field research.

Valuable lessons learned: The project provided valuable insights into complex project and software development for the airport, emphasizing the importance of adaptability, communication, and documentation for future projects. Additionally, involving stakeholders early on and sharing insights with them and the team facilitated a deeper understanding of the project. Moreover, it helped increase user loyalty because they were involved in our process.

Kiitos!*

*Thanks