Bosch Parking Lot Management

Bosch Active Parking Lot Management user interface is displayed on a laptop computer.
Title
Active Parking Lot Management (APLM)
My role
Developer (Frontend, Backend), UI Designer and UX Designer
Time
2015 - 2018
My tools
Jira, Confluence, Miro, Affinity Designer, Affinity Photo, Balsamiq, MS Forms
Team
Product Owner, Software Architect, Scrum Master, Developers, UI Designer, UX Designer
Foreword

This document serves to illustrate my activities and services for the Bosch Group working as UX/UI-Designer and software engineer. Confidential information, including technical details, customer data, and personal data, has been removed to the best of my knowledge and has not been disclosed. If names should be found, they are fictional and used as an example. Please understand that I am unable to share any project-specific details, even upon request.

The project
[2] Bosch Active Parking Lot Management dashboard

Bosch Active Parking Lot Management (APLM) is a smart, end-to-end solution designed to optimize the operation and efficiency of parking facilities. Utilizing a combination of sensors, IoT technology, and software, APLM provides real-time information on the occupancy and usage of individual parking spaces. The core value proposition of APLM lies in its ability to significantly reduce the time drivers spend searching for parking by providing accurate, live guidance.

For operators, APLM offers operational advantages through detailed analytics on facility utilization, allowing for optimized pricing strategies, efficient maintenance planning, and improved revenue management. Ultimately, Bosch APLM enhances the overall parking experience for customers while simultaneously improving the profitability and efficiency of the parking lot for the operator. It represents a key component of modern Smart City and Connected Mobility concepts.

The problem

While car drivers are often stressed searching for a vacant parking space, parking lot managers need exact and reliable information about the parking spaces for improving profitability and the parking experience. Furthermore, technicians and caretakers need tools to locate and fix technical issues.

As a UI designer and software engineer, I want to create a user-friendly solution that addresses all the needs of these different users.

The goal
[3] Designed for parking lot management and operation

The goal is to design and develop an easy to use user interfaces to operate and manage parking lots equipped with Active Parking Lot Management from Bosch in order to make parking easier for car drivers.

My role

In this project, I served as both a UI Designer and a Software Engineer. My responsibilities spanned the entire engineering lifecycle, including: gathering user requirements, ideating potential solutions, creating wireframes, mockups, and interactive prototypes, and finally collecting user feedback. As software engineer I also supported the implementation of the user interface using Angular and other web technologies.

The outcome

By applying UX methods, I was not only able to create an intuitive user interface, but I also gained a deep understanding of user needs in the parking domain. This allowed me to create a small design system that enables scalability for future extensions and adaptations.

Together with my engineering team, the designed solution is implemented and continuously expanded with new functionalities in an iterative process.

I successfully achieved …

  • Usability: I designed web application that really helps service technicians and operators by providing the information and functionalities needed for their daily tasks. Examples are error location, sensor replacement and making new parking lots ready form APLM. For managers I designed customizable dashboard and report views.
  • User experience: I got very positive feedback for the user experience during user tests for creating views and aligning them to the way the users are working.
  • Established a design process and product design system: I started from scratch in a company that had no design system or brand guide for desktop, web and mobile applications.
My way to reach the goal
[4] Applied iterative and agile design process

We followed a typical agile software development process using SCRUM that works in cycles. As the only team member with a UX and UI design background I integrated a design process and performed UX methods and design tasks as SCRUM tasks.

Understand - Users and their tasks

Through interviews and competitor analysis I identified and set focused on four core users and I created personas for them. The goal of my personas is to remind us who we are designing our product for. That's why I kept the personas simple and easy to remember.

My personas for APLM are:

  • Parking lot manager (called Parking Paladin
  • Parking lot caretaker (called Facility Hero)
  • Service technician (called Tech Titan)
  • Service Operator for remote support (called Cloud Champion)
I have intentionally omitted personas with confidential data here

I created the information architecture to determine how complex the GUI would be and to be able to design the navigation. In addition I created for every page a sheet documenting the purpose, important information for users, navigation elements, functionalities and design decisions.

[5] Information architecture for Bosch APLM

For each screen I created a sheet that describes purpose, important information, layout, navigation and interaction items and design decisions. When it comes to implementation I used theme to create wireframes and linked them to Jira stories and tasks.

To get a better understanding of user tasks I used user journey maps. User journey maps are very good to get a common understanding in the team and with stakeholders.

I have intentionally omitted detailed customer journey maps and user journey maps with confidential data here

I consider wireframes to be a quick and cost-effective way to communicate design ideas. To support ideation, user testing, and development, I created numerous screen wireframes, visualizing views in different variants and states. Furthermore, I developed prototypes using these wireframes to map out all major user journeys and key features.

[6] Some wireframes created during ideation phase of project

Beside wireframes my design concept also contains user flows. I used the user flow to communicate and documentate ideas and to describe the way a user takes to perform a task. Therefore I created flow charts and used wireframes to gather feedback in this early phase.

I have intentionally omitted detailed flow charts with confidential data here
The design

When I joined the Bosch Group in 2015, I found myself in a situation where there was no standardized corporate design, no brand guidelines and no company-wide UI library for software applications or apps. Each development team created and implemented its own style. That's why I designed all the components myself and organized them in a design system, adapting and expanding them again and again.

[7] UI components from the product design system

To retain the typical Bosch design I used the Bosch Sans font as described in the Bosch style guide for websites.

Bosch Sans is used in all font levels, from headlines to body text. The two typefaces Bosch Sans Regular and Bosch Sans Bold form the design basis for all kinds of texts, including software applications and user interfaces.

I chose colors that fit the current style guide for websites and extended them for additional variants used for states. Regarding colors, I selected a palette that aligns with the existing Bosch style guide for websites and then extended these colors to create additional variants required for different UI states (e.g., pressed, active, hover, error, success, warning).

In addition to designing UI components and interactions, I also created application icons, product logos, illustrations, and other visual artifacts as needed and in cases where elements were missing. In doing so, I always followed the current company brand guidelines and requirements.

[8] App logos used for different devices and situations
Desktop application

Looking at the outcomes of the performed interviews with parking lot managers, parking lot owners, colleagues working in operation department and technicians we were sure that we need a software application for desktop and laptop computers that covers all of the use cases. Therefore an operating system-independent web application with a simple flat design style was designed by me and developed in our team.

[9] APLM web application - Parking lot overview

For management tasks the application includes several dashboards and reporting views. These views are customizable and allow the creation of user defined dashboards and reports.

For operators and technicians there are views that provide the status of the system and its component, list events like warnings and errors or display detail of hardware components like sensors or traffic guidance signs. Furthermore there are views that guide the user through installation of hardware like sensors or traffic guidance signs or setting up a connection to integrate APLM into other systems.

[10] Parking lot status screen
[11] Parking spaces status screen
[12] APLM Dashboard configuration screen
[13] Parking lot overview map visualization
Learnings
  • Parking: Parking lot management can sound boring, but there are so many different use cases, stakeholders and possible functionalities.
  • Agile working: Working agile is not the fastest way to deliver value. But it has the possibility to change and adapt way of working and product strategy.
  • Roles: Working as UX-designer, UI designer and Software Engineer allows deep understanding. But it limits the time for each topic, creativity and possibilities.
  • Incomplete team: Without team members responsible for user research, UX design and UI design a team has not all capabilities to create good products and services.
Related projects
Sources
[1]: Photo: unsplash.com - MacBook Pro @howardbouchevereau, UI Mockup: Created by Jens Merkel [2]: Photo: unsplash.com - Luke Thorn, UI Mockup: Created by Jens Merkel [3]: Illustration: Created by Jens Merkel [4]: Illustration and icons: Created by Jens Merkel [5]: Information architecture: Created by Jens Merkel [6]: Wireframes: Created by Jens Merkel [7]: UI components: Created by Jens Merkel, Icons: By Bosch and Jens Merkel [8]: APLM logo: Created by Jens Merkel, Bosch logo: By Bosch [9]: Photo: unsplash.com - @amyhirschi, UI Mockup: Created by Jens Merkel [10]: Screen designed by Jens Merkel [11]: Screen designed by Jens Merkel [12]: Screen designed by Jens Merkel [13]: Screen designed by Jens Merkel
Tags
IoT
Operations
Parking
User Interface
User Experience
Web Portal
Prototyping
Wireframes
Mockups