hyperlynx

We set out to solve the often ineffective ticket-to-response systems present in data centers. Our journey took us through the night to innovate a platform that works within Jira to streamline processes.

This choice was solution-oriented: we learned that Jira is not just industry standard but also the platform used by NMC^2. We wanted to optimize manager and respondent ticket responses, both of which are large issues across industries.

We created a React Web App utilizing Django and Vultr for our backend server. We also created our own Jira to most accurately use API calls to simulate real life data center work orders through tickets. On the frontend we used HTMS, CSS, and bootstrap with react.

There's much scalability with our project. The gap within data centers is one that costed AWS over $500M last week. And, as server racks become more complex, technicians will be tasked with more and more tickets. Our technology ensures that technicians can have the maximum amount of context required to solve problems, not being forced to deal with the tediousness of Jira. Meanwhile, managers benefit from minimized errors, creating a higher bar of corporate compliance.

Additionally, our market research highlighted that other similar industries may be able to benefit from this technology as well. Emergency response units, currently using computer assisted dispatches (CADs), similarly face efficiency and context issues. This market is underserved yet bears great impact on response time and consequently thousands of lives each year.

Furthermore, Auth0 and enhanced security measures allow our ticketing system to stay in line with industry norms. A cohesive marketing package, complete with various logos, graphics, colors, and fonts (including a hand-drawn custom one), works seemlessly to make an experience that is best for the user.

Slide deck: https://1drv.ms/p/c/94d0c7094038a788/ERD2QmJoK2RJi9SEbdDRLUcB_xeQu3EhM7PKPdkGUQWVNw?e=acvyVE