In the fast-paced and quickly-growing energy field, efficiency and accuracy mean everything. But when essential equipment break down, large scale operations can fall apart. Provided with Chevron's work order data, we sought to optimize the equipment repair process from work order request to repair completion, all while making the detailed process appear simple and elegant.

What it does

ChevRep provides a easy-to-understand platform to submit or receive work order requests that prioritizes time efficiency in matching qualified technicians to work orders. With our focus on user experience and attention to detail on front end, we hope to help Chevron employees and technicians avoid facing the difficulties of the intricate tracking and scheduling process.

How we built it

We built a full-stack web application around our work scheduling system that supports dynamically adding new work orders. The front-end of the web application was built with Vue.js, a progressive Javascript framework designed for easy UI development. The back-end of the web application had two services, a NodeJS server that handled most of the authentication and data manipulation and a Flask server that called the algorithm that we wrote in Python. We also maintained 3 databases: one for technicians, one for work orders, and one for facilities. The NodeJS server also supported sending SMS notifications to technicians, which we implemented using Twilio's NodeJS library.

Challenges we ran into while building it

One of the biggest design challenges was constructing our algorithm. We had to carefully consider what we considered was important for the repair queue and how we delegated them to the workers. In algorithm design, one has many choices to use for an algorithm; we selected urgency over speed. We went through the process of weighing the pros of cons with each algorithmic choice we made, which really fueled our discussions throughout our project.

Accomplishments that we're proud of

One thing that we were definitely proud of was seeing everything come together. We were amazed to see the progress that we were able to make especially in such a short period of time. We all definitely enjoyed this multi-faceted problem; and especially enjoyed going through the design process and watching things grow as we came together with a solution.

Our Takeaways from this Experience

There's something special about being up at 3 AM on a Discord call with your friends building something really neat. Hackathons, especially at Rice, really show the power of the CS community; how we can design and create ideas from basically scratch. These problems and challenges allow us to tackle exciting and relevant problems that can really make an impact in the world.

ChevRep's Next Steps

Creating more interactive features and avenues for communication are in store for ChevRep. We want to create a more engaging experience for users so that ChevRep can become a hub for technicians and employees to communicate. Afterwards, we want to further improve our algorithm, expanding it cross with several more constraints and tailor the experience to the user, the worker. One idea that we came by is the idea of having multiple people tag in to speed up the process. This not only decreases the idle time of the workers, but also fosters a collaborative environment in which ChevRep thrives on.

Share this project: