Lilee had launched several autonomous/self-driving public transportation projects from Taiwan to the U.S., but the current operational control center (OCC) software we use is an unqualified tool from the laboratory. At first, the requests are vague and changing - nobody knows how to start and have no experience on this type of product. What we have to do is to quickly converge the requirement by MVP process. After benchmark & competitor analysis, I found the monitoring environment and the level of the monitoring object (from route/intersection/to vehicle) are two main topics we have to focus on. So we propose several monitoring & layout strategies to limit our using scenarios - According to MVP spirit, we start from a normal web application under only one single monitor environment, but still prepare for the environmental setting process to save room for the future multi-monitor scenario. After the layout & environmental strategy is confirmed, we started to intensively discuss with the front-end developers on how to create a “canvas” like experience to let user resize their widgets by simply drag and drop, and try to apply most of the UI components from what we already had in current products (ex: chart, form, navigation) to reduce development loading, but we also introduced several new tricks to adopt the monitoring user experience (ex: rViz view/ track monitoring) This project is still ongoing.