Employee profiles
Structured employee records with departments, teams, job positions, and reporting relationships.
02OPERATIONS & RESOURCE MANAGEMENT
HR & Logistics Management Platform.
A centralized operational platform for employee records, organizational structure, assets, and resource coordination.
01 / OVERVIEW
People. Assets. One system.
An operational application that brings personnel and resource information into a shared system. The public hrmsams codebase includes HR records, organizational relationships, asset custody, locations, movement history, and maintenance records.
My contribution
Full-stack development, bringing the interface, business workflow, and data layer together.
02 / THE BUSINESS REQUIREMENT
The problem to solve.
People and physical resources are closely connected in day-to-day operations. Separate records make it harder to understand who holds an asset, where it is located, and how the organization’s structure relates to those responsibilities.
03 / THE APPLICATION
What the system does.
Asset custody
Connect assets to their current custodian and location.
Movement history
Record asset assignments, transfers, returns, and maintenance movements.
Domain-specific roles
A role model distinguishes general users, managers, HR staff, and asset administration.
04 / TECHNICAL ARCHITECTURE
How the layers connect.
01
Presentation
Next.js · Tailwind CSS
Dedicated HR and asset management areas with shared interface components.
02
Application
Server actions · Prisma
Domain actions for employees, departments, assets, categories, and locations.
03
Persistence
MySQL
Related employee, organization, asset, custody, and movement records.
05 / ENGINEERING DECISIONS
Deliberate choices.
Separate current state from history
An asset stores its current location and custodian. AssetMovement records separately preserve the movement between people and locations.
Represent hierarchy explicitly
Self-referential relationships model employee reporting lines and nested locations, instead of flattening them into descriptive text.
Organize around the domain
HR and asset management have dedicated routes and action modules while sharing a common user and data model.
06 / THE TECHNICAL CHALLENGE
Connecting people and resources without losing context.
A single asset can move between locations, custodians, and maintenance states. A current-state record alone cannot explain that journey.
THE APPROACH
The schema separates the asset master record from movement and maintenance records, with relationships for the sending and receiving locations, custodians, and approving user.
07 / THE RESULT
A connected application.
A shared relational foundation connects employee administration with asset custody, movement, and maintenance. Dedicated HR and asset areas make these related operational responsibilities accessible through one application.
About this case study’s sources
The Next.js, Prisma, and MySQL stack and HR/asset architecture were checked against hrmsams. The screenshot comes from the existing portfolio and may reflect an earlier version.