A

Project Report on
“Web-Based Laboratory Management
Application”
Submitted in partial fulfilment
for the award of the Degree
of

Bachelor of Technology
in Department of Computer Science & Engineering

Engineering College Bikaner

(A Constituent College of)

Bikaner Technical University

(2025 – 26)

Supervisor: Submitted By:

Mrs. Charu Jain Varun Sharma (22EEBCS121)
Assistant Professor Rahul Sharma (22EEBCS101)
(CSE Department) Peeyush Agarwal (22EEBCS094)
Laveena (22EEBCS052)
 ENGINEERING COLLEGE BIKANER
SESSION 2025-2026

CANDIDATE’S DECLARATION
We hereby declare that the project entitled “Laboratory Management Application” submitted
to Engineering College Bikaner, a constituent college of Bikaner Technical University,
Bikaner, in partial fulfilment of the requirement for the award of the degree of Bachelor of
Technology in Computer Science and Engineering, is our original work.
We further declare that:
• The work presented in this project report is carried out by us under the guidance of the
project supervisor.
• The content of this report has not been submitted to any other institute or university for the
award of any degree, diploma, or certification.
• Any materials, data, figures, or concepts taken from other sources have been duly
acknowledged and referenced.
We take full responsibility for the authenticity and originality of the content presented in this
project.

Varun Sharma (22EEBCS121)

Rahul Sharma (22EEBCS101)

Peeyush Agarwal (22EEBCS094)

Laveena (22EEBCS052)
 ENGINEERING COLLEGE BIKANER
SESSION 2025-2026

CERTIFICATE
This is to certified that the project entitled “Laboratory Management Application” has been
submitted to the Engineering College Bikaner, constituent college of Bikaner Technical
University Bikaner, fulfillment of the requirement for the award of the degree of Bachelor of
Technology in “Computer Science and Engineering” by following student of final year B.Tech.

Varun Sharma (22EEBCS121)

Rahul Sharma (22EEBCS101)
Peeyush Agarwal (22EEBCS094)
Laveena (22EEBCS052)

Mrs. Charu Jain Dr. Rituraj Soni

(HOD, CSE Dept.)
 ACKNOWLEDGEMENT

We are very thankful to everyone who all supported us, for completing our project effectively
and, moreover, on time.

We are equally grateful to our teacher Mrs. Charu Jain. She gave us moral support and guided
us in different matters regarding the topic. She had been very kind and patient while suggesting
us the outlines of this project and correcting our doubts. We thank her for her overall support.

Last but not the least, We would like to thank our parents who helped us a lot in gathering
different information, collecting data and guiding us from time to time in making this project.
Despite their busy schedules, they gave us different ideas in making this project unique.

Place: Bikaner, Rajasthan Thank You,

Date: 27 – November – 2025 Varun Sharma (22EEBCS121)

Rahul Sharma (22EEBCS101)
Peeyush Agarwal (22EEBCS094)
Laveena (22EEBCS052)
 ABSTRACT

Effective management of laboratory activities has become essential in academic and research
environments. Labs often deal with a variety of resources, including equipment, and project-
related data, along with maintaining records of students and faculty members. To address
these needs, our project presents a Web-Based Laboratory Management Application
that serves as a centralized platform for managing lab operations.

The application not only handles resource and user management but also introduces a
dedicated project management module to track ongoing projects, store details of
completed projects, and plan future research initiatives, making it a comprehensive solution
for academic and research laboratories.

Traditional laboratory management practices usually use manual record-keeping or isolated

digital systems, leading to various inefficiencies such as:
• Difficulty in maintaining up-to-date information on laboratory resources and their
availability.
• Lack of a centralized system to track students, their projects, and assigned mentors.
• No structured platform for managing project updates, including ideation, execution,
and completion stages.
• Poor accessibility of information, making collaboration and decision-making time-
consuming.

This project aims to eliminate these challenges by providing a streamlined, web-based

application that integrates all key functionalities into a single platform.

The Laboratory Management Application is developed as a web-based system ensuring

platform independence and easy accessibility. The frontend of the application is built using
HTML, CSS and JavaScript, providing a clean, responsive, and user-friendly interface. The
backend is powered by JavaScript, which handles server-side operations and integration
with the database. The application uses SupaBase as its database solution for secure,
scalable and real-time data storage and retrieval. Key functionalities include:
• Resource Management: Adding, updating, and tracking the availability of lab
equipment.
• Student Management: Registering students with details of their ongoing or
completed projects.
• Faculty Database: Storing mentors profiles along with their areas of expertise to
facilitate mentorship and guidance.
• Project Management: Managing the lifecycle of projects, including idea submission,
roadmap planning, tracking progress of ongoing projects and archiving completed
projects with production links for future reference.
 LIST OF CONTENTS
S. No. Topics Page No.
1. Certificate i

2. Acknowledgement ii

3. Abstract iii

4. List of Contents iv

5. List of Tables v

6. List of Figures v

Chapter 1: Introduction
1.1 Background of the Problem
6. 1.2 Problem Statement 6-7
1.3 Objectives of the Project
1.4 Scope of the Project
1.5 Expected Outcomes

Chapter 2: Literature Review

2.1 Review of Existing Work
7. 2.2 Comparative Analysis 8-9
2.3 Research Gap Identified
2.4 Relevance to the Current Project

Chapter 3: Methodology & Design

3.1 Proposed Methodology / Approach
8. 3.2 System Architecture / Flowchart / Block Diagram 10 - 13
3.3 Tools, Technologies & Resources Required
3.4 Work Division among Group Members

Chapter 4: Progress in Phase I

4.1 Tasks Completed
9. 4.2 Preliminary Implementation 14 - 15
4.3 Challenges/Problems Encountered
4.4 Plan for Remaining Work

Chapter 5: Conclusion & Future Work

10. 5.1 Summary of Phase–I Work 16 - 17
5.2 Pending Work to be Completed in Phase–II
5.3 Expected Final Deliverables

11. Result 18

12. Conclusion 19

13. References 20
 LIST OF TABLES
S. No. Topics Page No.
1. Comparison Between Traditional System and Our Solution 6-7

2. Competitor Analysis & Feature Comparison 8

3. Technology Stack Specifications 10

4. Work Division Among Team Members 13

5. Project’s Phase 1 Status 14

6. Implemented Functional Modules Summary 16

LIST OF FIGURES

S. No. Topics Page No.

1. Flow Chart of the Project 11

2. ER Diagram of Database Schema 12

 Chapter 1: Introduction

1.1 Background of the Problem

As engineering students, we spend a lot of time in labs. During that time we have observed that the
current method of managing lab components is outdated and human dependent. Everything is
recorded manually in physical registers or offline Excel sheets. This manual method makes data
management highly inefficient and prone to human error and also makes it very difficult to search for
a specific component or check if it is available or not. Furthermore, tracking student attendance or
project progress is a very time-consuming task.

1.2 Problem Statement

The challenges faced by current system are:

• Data Fragmentation: All lab information - including equipment stocks, attendance, and
projects - are stored in different Excel sheets or registers and is not stored in a single digital
system.

• Loss of Assets: Components often go missing due to the lack of proper tracking of the
component and which student was assigned that particular component.

• Lack of Maintenance: Damaged and consumable items are not reported or replaced
systematically, leading to shortages.

• Attendance Issues: Attendance is maintained on paper or Excel, which is time-consuming

and prone to manipulation or errors.

• Project Management Gaps: There is no structured platform for managing project updates.
Stages like ideation, execution, and completion are not tracked digitally.

Traditional System
S.No. Parameter Proposed Web-Based Application
(Manual/Excel)

Physical registers or offline Centralized Cloud Database

1. Data Storage
Excel files. (Supabase).

Manual counting; no real-time Real-time updates; auto-

2. Stock Tracking
visibility. calculation of available stock.

Handwritten entries; prone to Digital logging; "Smart Return"

3. Issue/Return
errors. logic with audit logs.

Automated via RFID/Biometric

4. Attendance Registers or paper signatures.
inputs.

6
 Traditional System
S.No. Parameter Proposed Web-Based Application
(Manual/Excel)

Restricted to physical lab

5. Accessibility Accessible anywhere via Web.
location.

Automated "Low Stock" and

6. Alerts No warnings for low stock.
"Damaged Items" alerts.

Manual compilation takes Instant export of CSV reports

7. Reports
hours. (Members, Items, History).

Table 1: Comparison Between Traditional System and Our Proposed Solution

1.3 Objectives of the Project

Our main primary objective is to build an all in one web-based platform that combines Inventory,
Project Management, and Attendance. Specific objectives include:

• Smart Inventory: Storing components category-wise with unique IDs for accurate tracking.
• Real-time Monitoring: Providing a centralized dashboard to view component issue, return,
and stock levels.

• Automated Attendance: Eliminating manual input by using RFID, Face Recognition, and
Fingerprint scanning.

• Project Oversight: Creating dedicated dashboards for project teams to manage tasks and
deadlines efficiently.

1.4 Scope of the Project

The scope of this application extends beyond just our college labs. It is designed to be useful for:
• Colleges & Universities, handling inventory for labs or tracking multiple student records.
• Training Centers & Small Industries, managing tools and hardware.
• Startups & Innovation Hubs, tracking their component stocks and updates of the projects.

1.5 Expected Outcomes

By implementing this system, we expect to see reduced loss of components and a good boost in
operational efficiency. It will allow instant reporting of damaged items, making quick replacements
possible. For students, it means a smoother process for components issuing and submitting project
updates. For faculty, it means having a clear view of what is happening in the lab at any given
moment also they will time, who now currently spend hours on manual audits and loggings.

7
 Chapter 2: Literature Review

2.1 Review of Existing Work

Before starting our project, we looked at several software solutions that currently exist and addresses
individual aspects of management, available in the market. We studied tools like Asana and ClickUp,
which are famous for project management. We also looked at Zoho Inventory and Odoo for
managing stocks and resources.

2.2 Comparative Analysis

We got to know that while these tools are powerful enough, they don't fit our needs:
• Asana & ClickUp: These cost around ₹700-₹900 per month per user. They are great for
managing tasks but they only focus on software tasks. They have no feature to track physical
lab inventory or student attendance.
• Zoho Inventory: This is designed for shops selling products (retailers). It doesn't handle the
"Issue and Return" logic that labs need (where students borrow items and return them not
purchase them).
• Odoo: This is a full ERP solution. It is very expensive and too complex to set up for a simple
college lab or any academic setting.

Asana /
Feature Zoho Inventory Odoo ERP Our Solution
ClickUp

Project Retail/Sales Enterprise Academic Lab

Primary Focus
Management Inventory Management Operations

Project
Excellent No Yes Yes (Student Focused)
Tracking

Component Yes (Sales Yes (Issue/Return

No Yes
Tracking based) based)

Attendance
No No Complex Setup Yes (IoT Integrated)
System

High
Cost High (Recurring) Very High Low (One-time Setup)
(Recurring)

Business Simple/Student
User Interface Complex Complex
Oriented Friendly

Hardware
No Barcode only Complex Yes (RFID/Biometric)
Integration

Table 2: Competitor Analysis & Feature Comparison

8
2.3 Research Gap Identified
Our analysis showed that most existing softwares are "Industry-Oriented" and not "Lab-Focused".
There is no affordable system that combines component tracking, student attendance, and academic
project management in one place.

2.4 Relevance to the Current Project

This gap is exactly where our Web-Base Laboratory Management Application fits. We are
building a system specifically for the academic workflow - integrating hardware sensors (RFID) with
software to manage the specific problems of a student lab. The system that also understands the
academic lifecycle: a student joins a lab, gets a mentor, borrows components (Inventory), works on a
timeline (Project Management), and attends sessions (Attendance).

9
 Chapter 3: Methodology & Design

3.1 Proposed Methodology / Approach

We are developing this concept as a Web-Based System to ensure it can be accessed from anywhere,
whether on a lab computer or a student's laptop. The system is divided into key modules:

1. Smart Inventory Management: Uses unique IDs for components and provides real-time
monitoring of stock levels and track records for issuing of the components to students.

2. Project Management Dashboard: Allows supervisor to monitor project progress in real-

time while teams have individual separate dashboard for maintaining updates of project
progress.

3. Attendance System: Supports multiple authentication modes (RFID, Face, Fingerprint) to

record attendance data without manual input.

3.2 System Architecture

The application is built on a modern, scalable architecture:
• Frontend: We are using HTML, CSS, and JavaScript React for creating a clean, responsive,
and user-friendly interface.
• Backend: Powered by Node.js with Express.js (JavaScript Frameworks), handling server-side
operations.
• Database: We are using Supabase for secure, scalable, and real-time data storage.
• IoT Integration: For the attendance system, we will be integrating hardware components
like ESP32 and RFID readers to communicate with our backend.

3.3 Tools, Technologies & Resources Required

Component Technology / Tool Purpose in Project

Building the responsive user interface and

Frontend HTML5, Tailwind CSS,
dashboard.

Backend JavaScript (ES6+),

Handling calculations and logic.
Logic Node.js

Storing user data, inventory records, and audit

Database Supabase (PostgreSQL)
logs.

Icons/UI Lucide Icons Visual elements for the dashboard interface.

IoT Hardware ESP32, RC522 RFID Scanning student ID cards for attendance.

Table 3: Technology Stack Specifications

10
Figure 1: Flow Chart / Work Flow of the Project

11
Figure 2: ER Diagram of Database Schema

12
3.4 Work Division Among Group Members

To ensure the timely completion of the Project, the development work was distributed among the
team members based on technical strengths. The specific roles and responsibilities are defined
below:

Team
S.No. Role Key Responsibilities
Member

• Designing the User Interface (UI) and Dashboard

layouts.
• Implementing the Sidebar Navigation and main
Frontend structure.
1. Laveena
Development
• Ensuring consistent styling using Tailwind CSS.
• Creating visual components like Stats Cards and
Tables.

• Developing interactive Modals & Dialogs (Add

Item, Issue Item forms).

Rahul Frontend • Implementing Search & Filter functionalities.

2.
Sharma Development • Ensuring Mobile Responsiveness for the PWA.
• Handling form validations and user feedback
(Toast notifications).

• Writing core JavaScript Logic for data fetching and

updates.
• Implementing complex algorithms like "Smart
Varun Backend Return" and "Auto-Fix Calculations".
3.
Sharma Development
• Setting up Real-time Subscriptions for live
dashboard updates.
• Handling IoT (RFID) integration logic.

• Designing the Database Schema (ER Diagram).

• Setting up Supabase tables (Members, Items,
Peeyush Database Categories).
4.
Agarwal Management • Implementing Audit Logs to track user actions.
• Managing data security and relationships
between tables.

Table 4: Work Division Among Team Members

13
 Chapter 4: Progress in Phase 1

4.1 Tasks Completed

In this first phase, our focus was on planning and designing the system. But in addition to that, we
have completed one of our modules. List of things we have completed:

• Requirement Gathering: We listed out all the types of components (Consumable vs. Non-
Consumable) and the specific data we need to track for them, like Voltage, Current, and RPM.

• UI/UX Design: We have designed the layouts for the Admin Dashboard. This includes the
"Cards" view for Total Items, Issued Quantity, and Low Stock alerts.

• Database Schema: We have planned how to store member details and component
properties in the database.

• Tech Stack Finalization: We decided to go with the MERN stack (MongoDB/MySQL, Express,
React, Node) because it is efficient for real-time updates.

• Smart Inventory Management Module: We have completed the Inventory Management

Module.

S. No. Task Description Status

1 Problem Identification & Literature Review Completed

2 Requirement Analysis & Feasibility Study Completed

3 UI/UX Design (Dashboard & Layouts) Completed

4 System Architecture & Database Design Completed

5 Frontend Development (HTML/CSS/JS) Completed

6 Database Integration (Supabase) Completed

7 Testing & Debugging (Phase 1) In Progress

8 Configuration of ESP32 for Module 2 In Progress

Table 5: Project’s Phase 1 Status

4.2 Preliminary Implementation

We have finalized the design concept for the dashboard interface where admins can view
components categorized by type (e.g., Consumable vs. Non-Consumable), see real-time stats like
"Issued Quantity" vs "Available" and properties of components like "Voltage" or "RPM" for motors. We
have coded the “Smart Inventory Management Module” for the Phase 1 of the project lifecycle and its testing
is still in progress.

14
4.3 Challenges Encountered
One of the main challenges we faced was designing a database that can handle different types of
components. For example, a "Motor" has RPM and Voltage, but a "Resistor" has Resistance and
Power. Creating a flexible category system was difficult. We are also working on figuring out how to
securely connect the IoT devices (ESP32) to the web server without lagging.

4.4 Plan for Remaining Work

In Phase II, our focus will be:
• Designing and developing the remaining modules (Attendance System and Project
Management).
• Once the remaining modules are developed, integrating all the three modules into a one
single application.
• Physically wire the RFID reader to the ESP32 and write the code to send scan data to the
database, for detection and recognition logic, important for Attendance System Module.

15
 Chapter 5: Conclusion and Future Work

5.1 Summary of Phase 1 Work

In Phase I, we successfully analysed the limitations of existing manual lab systems with also analysing
the solutions already present in market, which according to our research weren’t according to out
needs and were more like “Industry Focused” after that defined a scope for a comprehensive digital
solution. We selected a robust technology stack which involves React.js, Express.js and SupaBase. The
system architecture has been designed to unify scattered information into a single "Smart Solution".
Also developed one module of the project i.e. “Smart Inventory Management”.

Module Features Implemented Function Name in Code

Real-time stats, Low stock alerts, Quick

Dashboard updateStats()
actions.

Add/Edit items, Dynamic properties,

Inventory populateItems(), addItem()
Category sorting.

Issue Assign items to students, check

issueItemWithType()
System availability.

Smart Bulk return, Mark as damaged, Auto-stock

smartReturn(), processSmartReturn()
Return update.

Reporting CSV Export for audits, items, and history. exportAllData(), downloadCSV()

checkAuthAndShowApp(),
Security User authentication, Audit logging.
addAuditEntry()

Table 5: Functional Modules Summary that’s implemented so far

5.2 Pending Work to be Completed in Phase-II

• Design and develop the rest two modules.
• Integration of all the three modules into a single Web Application.
• Full development of the backend API using Node.js and Express.js.
• Physical integration of the ESP32 RFID reader and biometric modules with the web application.
• Testing of the "Issue-Return" logic to ensure accurate stock updates.

16
5.3 Expected Final Deliverables
The final deliverable will be a fully functional web application connected to hardware sensors,
featuring a dashboard that manages members, tracks components in real-time, manages student
attendance and manages project timelines and updates. It will significantly enhance operational
efficiency, collaboration, and productivity in college labs. What users will be able to do:
• Students can log in and view available components, manage their projects and view their
attendance.
• Faculty can view project updates, real-time availability of components and attendance
insights.
• The system automatically alerts the admin when stock is low for the components.

17
 RESULT
In Phase I of the Web-Based Laboratory Management Application, we successfully transitioned from
the planning stage to the actual development of the core software module (Smart Inventory
Management). The following results have been achieved:

1. User Interface (UI) Implementation

We have developed a responsive and clean user interface using HTML and Tailwind CSS.

• Dashboard: The main dashboard is fully functional. It correctly displays real-time statistics
such as "Total Members," "Total Items," and "Issued Quantity".

• Smart Alerts: The system successfully identifies items with low quantity (≤ 5 units) and
displays them in a dedicated "Low Stock" card.

• Visual Feedback: We implemented toast notifications (pop-ups) that give instant feedback
(e.g., "Item Added Successfully" or "Error: Duplicate ID") to improve the user experience.

2. Functional Inventory Logic

We wrote the core JavaScript logic to handle the complex "Issue and Return" cycle.

• Smart Return: The code successfully handles the logic where a student can return multiple
items at once. The system automatically updates the database, increasing the "Available"
count instantly.

• Damage Tracking: We successfully added a feature to mark items as "Damaged." These

items are removed from the active stock but kept in the database history for accountability,
solving the problem of missing components.

3. Database Connectivity
We connected our frontend to Supabase.

• The application can now Create, Read, Update, and Delete (CRUD) records for Members and
Categories.

• Real-time Updates: We used Supabase subscriptions in our code, which means if one admin
adds an item, it instantly appears on another admin's screen without refreshing the page.

4. Audit Logging
To ensure security, we implemented an Audit Log in the code. Every time an item is issued, returned,
or deleted, the system records who did it and when. This result specifically addresses the problem of
lack of accountability in the manual system.

18
 CONCLUSION
The traditional method of managing laboratory resources using paper registers and isolated Excel
sheets has proven to be inefficient and error-prone. Through Phase I of this project, we have
successfully laid the foundation for a digital solution that addresses these challenges head-on.

Key Takeaways from Phase I:

1. Centralization Works: By bringing Inventory, Project Management, and Attendance into
one platform, we have eliminated the need for scattered records.

2. Automation Saves Time: The logic we wrote for auto-calculating stock levels proves that
software can handle in milliseconds what takes minutes to do manually.

3. Accountability is Improved: With features like the Audit Log and Member Issue History,
we can now track exactly where every component is, significantly reducing the chance of theft
or loss.

Future Scope (Phase II):

While the software side is shaping up well, the next phase will focus on bridging the gap between the
digital and physical worlds.

• IoT Integration: We will connect the ESP32 and RFID readers to our Node.js backend to
automate attendance.

• Biometric Security: We plan to implement fingerprint scanning for issuing expensive

equipment.

• Mobile App: We will refine the features to ensure the app works smoothly on faculty
smartphones.

In conclusion, the Laboratory Management Application is on track to becoming a vital tool for
our college, promising a smarter, more efficient, and paperless laboratory environment.

19
 REFERENCES

1. React Documentation. Getting Started with React. https://react.dev/

2. Supabase. Supabase Database & Realtime Documentation. https://supabase.com/docs

3. Asana. Project Management Software Features. https://asana.com/

4. Zoho Corp. Zoho Inventory Management System. https://www.zoho.com/inventory/

5. Espressif Systems. ESP32 Technical Reference Manual.

6. Mozilla Developer Network (MDN). Service Worker API (PWA).

https://developer.mozilla.org/

20