TIER IV PEOPLE shines a light on the people and teams whose unique experiences, backgrounds, and stories bring our mission to life. In this installment members of the FMS, Drive and Maps teams gathered to discuss their roles, challenges, and visions for the future of autonomous driving.

Yutaro Uramoto, the Maps team leader, earned a degree in mechanical systems engineering from Tokyo University of Agriculture and Technology. Previous experience includes the development of search systems for a real estate business and travel agency, handling everything from frontend to backend development. With a passion for fast cars, Yutaro enjoys road trips and sports such as baseball, basketball, and soccer.

Akira Saso is a backend developer on the Drive team, specializing in remote monitoring systems. He graduated from Waseda University's Graduate School of Fundamental Science and Engineering. Previously, he worked as a security engineer for a mobile game developer, focusing on vulnerability assessments and improving internal security. In his free time, Akira enjoys playing mobile games, traveling, and going to the gym.

Yu Nakata, a member of the FMS team, graduated from Osaka University with a Ph.D. in Information Science. He currently develops the backend of the Fleet Management System. Previously, he worked in research and development at a major manufacturer, specializing in networking and edge computing. Yu moved to Osaka six months ago and is currently on the lookout for the perfect cabinet to display his liquor collection.

— How did you arrive at TIER IV?

Yutaro: In my previous job, I developed search systems for real estate and travel businesses, handling everything from frontend to backend and from requirements definition to operations and maintenance. With a background in mechanical engineering, I wanted to work on things that actually move. That’s when I came across TIER IV and was drawn to the challenge of working with cutting-edge technology that is unlike anything else out there. I’ve always loved cars, and my interest in autonomous driving was a major reason for joining the company.

Akira: I previously worked as a security engineer at a mobile game developer, focusing on vulnerability assessments to identify and address security gaps. I also worked on initiatives to enhance internal security practices. My connection to TIER IV came via an employee who was a former colleague. He reached out to me, and after hearing more about the company, I decided to make the move. The work I do now is quite different from what I did at my previous job. Currently, I mainly focus on development. I was drawn to TIER IV because of the opportunity to tackle new challenges and work with advanced technology.

Yu: I develop the backend of the Fleet Management System (FMS). Previously, I spent about six years in the research lab of a major Japanese manufacturer, working on networking and edge computing. I joined TIER IV because I had been doing R&D for a long time, and I wanted to put my knowledge and experience to practical use. Given my background in edge computing, when I learned about TIER IV's Fleet Management System, which integrates edge and cloud technologies, it closely aligned with what I had been working on. Edge computing is about visualizing information from the field. With TIER IV's system, it involves tasks like sending commands from the cloud to vehicles, and bidirectional communication that is real-time and always available. I was motivated by the prospect of tackling such challenges.

— What do the FMS, Drive, and Maps teams do?

Yu: My team is responsible for the Fleet Management System, which is used to manage vehicle operations, scheduling and the maps used by vehicles. For example, we can access information such as the current location of vehicles and battery levels. The system also features functionalities similar to a taxi app, allowing us to send instructions to autonomous vehicles about where they should travel from and to.

My team designs and develops new features in response to issues identified during tests and actual operations. Since our system heavily relies on functionalities from products like Autoware and Web.Auto, I collaborate closely with related teams to discuss and define specifications.

Yutaro: The Maps team develops services to create, edit, and manage maps. We’re responsible for the map creation and editing application, Vector Map Builder. My team also works on the FMS, which is the backend of the map management system that Yu is in charge of. Essentially, I’m responsible for overseeing and developing web services related to maps. Data collection is often done by teams out in the field.

In Autoware, maps use both Point Cloud Data (PCD) maps for self-localization and vector maps that define drivable areas, signals, and signs on the map. Our teams handle both types of maps.

Akira: The Drive team is responsible for the remote monitoring system. We develop tools that allow operators in a remote monitoring room to check live footage from cameras mounted on vehicles to ensure smooth operations. The software for transmitting footage from the vehicle is based on open-source software. We also handle the operation of servers that distribute this footage and the development of applications that allow users to view the footage in a browser.

— Where are the remote monitoring rooms located?

Akira: It depends on the project. For the 2023 project at Narita Airport, personnel monitored operations from a room at the airport. From the monitoring screen, operators can perform actions like emergency stops, issue commands, or even communicate with people in the vehicle. Currently, vehicles have operators on board, but in the future, the plan is for remote personnel to oversee unmanned vehicle operations via video feeds.

— Your teams work remotely. How do you communicate with each other?

Yu: Basically, Slack. Within the team, there is an atmosphere where we can openly discuss things frankly. The FMS, Maps, and Drive teams have a joint 15-minute call every morning, where we share what we worked on the previous day and our plans for today. After that, we often have quick calls with other stakeholders.

Yutaro: The Maps team has a team meeting twice a week where we discuss everything from work-related topics to casual chat. Although the team is small, we communicate a lot. Team members actively share their insights and suggestions for improvement, which leads to lively discussions and enhances our work.

Akira: The Drive team comprises individuals from diverse backgrounds. I’m originally a security engineer with a background in backend development. Another member came from a research university specializing in communications, while another has previously worked for a media streaming company, focusing more on audio media than visual media. We are all working on the same challenges, but with each of us having different specialisms, discussions are often in-depth and the feedback is from various perspectives. We don't have that many meetings, but we do tend to have extended discussions when we’re tackling a challenge.

— What is the most interesting aspect of your job?

Yutaro: Maps are essential in the current version of Autoware. I find it meaningful that many people use the services we develop to work on and advance autonomous driving. Seeing vehicles running on maps I’ve personally edited gives me a sense of accomplishment and makes me feel more connected to the product.

A map created in Vector Map Builder. The point cloud data (shown in white) serves as a base for creating various features such as lanes and signals.

Akira: It’s fascinating to see the video streaming features we’ve developed with multiple organizations actually deployed in vehicles. I feel a sense of accomplishment knowing that the products I’ve worked on are contributing to autonomous driving and advancing the technology.

Yu: Autonomous driving systems like Autoware and FMS involve highly complex technologies. However, from the perspective of passengers or users, autonomous vehicles are simple to comprehend. Riding an autonomous bus is not that different from riding a regular bus. One of the appealing aspects of the job is being involved in products and services of the future, which is an easy way to impress family and friends. Autonomous driving has been attracting a lot of attention, and TIER IV is getting more media coverage. I feel a sense of satisfaction whenever I see things I’ve worked on in TV or YouTube footage.

— Can you share some recent challenges?

Yutaro: Operational areas are expanding rapidly, and the maps are getting significantly larger. So, we're working on procedures to create and edit large maps, manage uploads and ensure they're ready for operation. We’re also developing a system to inspect the safety of the maps. There's a lot to handle, from small improvements to significant adjustments. We're addressing the challenges step by step. Detecting changes in the map is also quite crucial. We need a system where Autoware detects changes while the vehicle is running, and automatically updates the maps on the web.

Akira: We need to meet the requirements for remote monitoring as specified by traffic laws and regulations, and address the increasing requests for remote monitoring systems due to a rise in users. It’s a challenge to handle the increased load. We also need a system that ensures stable operation of video streaming software and supports updates, while broadly addressing the needs of remote vehicle monitoring.

We’re conducting field tests with local 5G services, checking communication and video quality, and fine-tuning the system to ensure optimal video streaming for remote monitoring. This aspect is technically demanding and involves significant difficulties.

Yu: The more users and customers there are, the more the system becomes an indispensable resource. If customers want to use the system in the middle of the night or overseas, the system needs to operate 24 hours a day, 365 days a year. The current challenge is to increase reliability by re-architecting the FMS and the system. Currently, FMS releases occur every two weeks, managed by the entire web team.

We’ve been working on making it possible to release the system without downtime and this has involved re-architecting various components. It has been a collaborative effort involving different teams, not only FMS. Each member of the development team has been involved in considerations of architecture, technology selection, risk analysis, and testing – not just application development. Sharing insights and organizing study sessions has been part of the process. It's been a valuable experience.

— The FMS and Drive teams are currently hiring. What kind of candidates would you like to see?

Akira: We're looking for people with a strong technical interest and the ability to take ownership of their work. Right now, we’re hiring a video specialist, as well as frontend and backend web system engineers. We especially welcome candidates with expertise in streaming and 3D graphics.

Yu: Most of us are mid-career hires, and our backgrounds are quite diverse. Some have experience in large corporations or companies involved in system integration, while others come from web-related backgrounds. In terms of team atmosphere, rather than a leader making all decisions and giving instructions, when someone wants to make a proposal, people offer comments from different perspectives with the aim of improving the product.

In the engineering community, there is a topic known as psychological safety, where everyone feels safe to speak up without fear of being judged, and conversations are conducted with respect. Many people here seem to be conscious of this, and as a result, discussions are conducted in a way that everyone feels comfortable.

— Lastly, any industry predictions?

Yu: As autonomous driving becomes more common, there will be more opportunities to ride in autonomous vehicles. We’re approaching a point where concerns and anxieties about autonomous driving will gradually disappear. During a recent trip to the Hokuriku region with my family, we used an autonomous bus at Komatsu Airport. The passengers, including me, were looking at their smartphones and treated the autonomous bus just like a regular one.

Currently, various locations are conducting tests and valuable insights are being gained. Overcoming technological challenges will bring us closer to autonomous driving on public roads. If profitable use cases like autonomous trucking on highways are established first, I imagine we’ll start seeing more and more autonomous vehicles on public roads.

・・・

TIER IV is always on the lookout for passionate individuals to join our journey. If you share our vision of making autonomous driving accessible to all, get in touch.

We’re currently hiring for the following related positions:

Discover more related job openings on our careers page.

If you’re uncertain about which roles align best with your experience, or if the current job openings don’t quite match your preferences, register your interest here. We’ll get in touch if a role that matches your experience becomes available, and schedule an informal interview.

Media contact

pr@tier4.jp

Business inquiries

sales@tier4.jp

Social Media

X (Japan/Global) | LinkedIn | Facebook | Instagram | YouTube

More

Insights from FMS, Drive and Maps teams

FMS／Drive／Maps エンジニア座談会