UniPM

Maintenance records move from inspection to review and searchable history.

Status: Academic capstone MVP, 2026-present
Scope: University preventive-maintenance forms and maintenance-history search.
Team and role: Team capstone. I worked on the backend maintenance flow and retrieval system.

Context

Draft and unacknowledged maintenance forms should not appear in official history or search results.

Built policy-protected ASP.NET Core workflows for assets, schedules, inspections, and the maintenance-form lifecycle.
Implemented history retrieval with SQL Server Full-Text Search, serialized embeddings, bounded candidates, application cosine similarity, and Reciprocal Rank Fusion.

React and TypeScript client requests are served by an ASP.NET Core API backed by SQL Server.
Policy-protected API paths cover assets, schedules, inspections, and maintenance review records.
Retrieval combines SQL Server Full-Text Search candidates with serialized embedding metadata, application cosine similarity, and Reciprocal Rank Fusion.
Only acknowledged maintenance rows enter official history and retrieval.
Candidate retrieval is bounded before semantic scoring, with an explicit lexical fallback when semantic services are unavailable.
Query vectors are transient and are not stored as user history.

The repository documents JWT authentication and policy-based authorization across five roles.
Fictional users and synthetic maintenance records keep the capstone data separate from institutional production data.
The repository includes migrations, health checks, CI, and a command that rebuilds retrieval data.
Running the rebuild command again produces the same retrieval records.
Tests use deterministic fixtures, including the 84 maintenance records described in my CV.

Academic MVP using fictional maintenance records. It has not been deployed at MSEUF.
It does not diagnose faults or predict maintenance needs. Corrected-action handoff is outside the current scope.