I developed CAE Job Dairy as a side project to help me stay organized in my former day job as a CAE simulation and development engineer for automotive safety.
Simulation jobs added to the solver server cluster are polled and the submission information is automatically added to the web app. Changes to the jobs status are automatically update in the web app and you can leave a result summary after you analyzed your job. The web interface allows you to add summary notes and categorize the outcome of the simulation. You can also use the web app to search and filter jobs (by project and/or user).
CAE Job Dairy is probably the most complex app I have developed thus far (2020). Not because of the web app frontend. The frontend is extremely simple and does not even have user authentication (it was a feature idea but not necessary for the tiny user base at first). The complexities come in because of the different data files it has to parse, the events and conditions and connected race conditions on the file system it has to deal with. It was also my first larger app and I have learned a great deal about how to structure software since then. I probably would not build it like this again. Especially the coupling between the backend parsing processes and the Django web app have shown some significant down sides.