Skip to content

Latest commit

 

History

History
105 lines (65 loc) · 5.44 KB

README.md

File metadata and controls

105 lines (65 loc) · 5.44 KB
Raw

Landing Page: https://repairnet.netlify.app

Insta: https://www.instagram.com/repairnet101/

Screenshot 2024-11-13 at 12 16 55 PM

Product Summary:

RepairNet is a facilities request tracker designed for Brandeis University students. It allows students to submit and monitor their maintenance requests seamlessly through the university’s housing portal, using their Brandeis login credentials. This tool aims to improve the efficiency of facilities management by providing students with real-time updates on their requests and scheduled maintenance visits in order to enhance student life experience for all the college students living on campus.

Problem Solved:

Students currently experience frustration with the lack of transparency and communication in the facilities request process. Many encounter delays, miscommunications, and the inconvenience of multiple platforms. RepairNet addresses these pain points by centralizing the request process, providing timely notifications, and improving communication between students and facilities teams.

Vision:

To create an efficient and transparent process for managing and tracking maintenance requests, allowing students to stay informed and plan their schedules around scheduled repairs. RepairNet streamlines interaction between students and the facilities department by leveraging the university’s existing infrastructure.

SOCIALS:

Presentation:

https://docs.google.com/presentation/d/1p7RaAJvlhozaiZNgnl1EAkxvTi9vuVQrDb1tgnXi__M/edit?usp=sharing

Features:

1. Brandeis Single Sign-On Integration

  • Description:
    Allows students to use their existing Brandeis credentials to log into RepairNet, eliminating the need for separate logins and reducing friction in the user experience.

  • Value Proposition:
    Saves time, provides ease of access, and increases adoption rates due to convenience.

  • Mockup Visual:
    Request Tracking Dashboard Mockup

2. Facilities Request Submission

  • Description:
    Students can submit requests directly through the platform, detailing the issue they need fixed (e.g., plumbing, electrical, HVAC).

  • Value Proposition:
    Simplifies the process of reporting issues, ensuring requests are accurately documented and submitted.

  • Mockup Visual:
    Facilities Request Submission Mockup

3. Request Tracking Dashboard

  • Description:
    A user-friendly dashboard where students can monitor the status of their requests, including whether they’ve been assigned to maintenance staff, are in progress, or completed. It includes fields for request ID, category, status, priority, description, arrival date, location, and the facilities management person in charge.

  • Value Proposition:
    Provides transparency, reduces uncertainty, and allows students to plan around maintenance schedules.

  • Mockup Visual:
    Request Tracking Dashboard Mockup

4. Notifications and Alerts

  • Description:
    Automated notifications sent to students when their requests have been updated, including when a maintenance visit has been scheduled.

  • Value Proposition:
    Keeps students informed and allows them to plan their day around upcoming maintenance visits, reducing interruptions.

  • Mockup Visual:
    Notifications and Alerts Mockup

5. Feedback Mechanism

  • Description:
    After a request has been resolved, students can provide feedback on the service they received, allowing facilities teams to improve based on student input.

  • Value Proposition:
    Enables continuous improvement of the service by incorporating user feedback and ensuring quality maintenance experiences.

  • Mockup Visual:
    Feedback Mechanism Mockup

6. Admin Portal for Facilities Team

  • Description:
    A backend portal for the facilities team to manage requests, assign tasks, and communicate with students.

  • Value Proposition:
    Streamlines workflow for facilities staff, allowing them to manage and prioritize requests efficiently.

Testing and Results

We will use these mockups and test them with Brandeis students to gather feedback on usability, intuitiveness, and layout. Testing would include one-on-one usability sessions where users perform tasks such as submitting a request and tracking it on the dashboard. Insights gained would inform design refinements as we move forward.

Key Testing Goals:

Usability Testing: Essentially we will measure how easily students can navigate the system, submit a request, and track its status. Assess whether the dashboard is intuitive and clear. Feedback Collection: We plan to use a combination of surveys and interviews to gather feedback on the most useful features, desired improvements, and any areas of confusion.

Early Results: Based on initial feedback from students, and their response to our product we will analyze the demand. We believe notifications and the tracking dashboard were identified as the most critical features. Some excited users of the current system suggested additional notification types, such as text message alerts.