This week at LuminaTech felt like a turning point.

What started as separate pieces, data, models, UI mockups, backend functions is slowly becoming a connected system. Our whiteboard says “LuminaTech,” but behind that name is real architectural progress.

From Idea to Baseline Model

We began the week by locking down something fundamental: clarity. We finalized our input features, confirmed our target definition, and built a baseline ensemble model to establish our first true performance benchmark. Instead of experimenting in multiple directions, we now have a clear reference point, a measurable starting line.

This baseline gives us something powerful:
a way to prove improvement, not just assume it.

Next step? Hyperparameter tuning. We’ll be running structured search strategies and comparing performance carefully, ensuring that any gain is meaningful and reproducible.

Strengthening the Backbone: Backend Progress

While modeling took shape, the backend architecture matured as well. We implemented and organized Supabase Edge Functions to better support workflow logic. Endpoints were structured more cleanly, making communication between the model layer and frontend more predictable and stable.

This is the invisible work that makes everything else possible, the difference between a demo and a system.

Bringing the Floor Plan to Life

On the frontend side, integration continued steadily.

We advanced our React interface and deepened the interaction between the floor plan and fixture-level views. Clicking on a fixture now feels less like navigating static UI and more like interacting with a living system. With updated code pushed to GitHub, collaboration is smoother and version control remains clean as multiple components evolve in parallel.

What’s Next: Moving Toward Full Integration

The upcoming week is focused on refinement and connection.

We’ll:

• Tune the model and compare baseline vs optimized configurations
• Stabilize backend responses for UI integration
• Connect prediction outputs into the frontend flow
• Begin validating the full pipeline

Data → Model → API → UI

Questions for Alignment

As we move toward deeper integration, we’re seeking clarification from our liaison engineer on two key areas:

• What format should model outputs take for sponsor visibility?
  Risk score? Category? Time-to-failure?
• Do we have sufficiently reliable maintenance/failure history to support stronger validation?

These answers will guide how we design both evaluation and user display.

Where We Stand

Hyperparameter tuning is defined.
UI integration is advancing.
Backend endpoints are taking shape.

LuminaTech is transitioning from isolated development into a cohesive predictive maintenance platform.

This week wasn’t just about code, it was about convergence.

As the semester drew to a close, Team 14 brought months of collaboration, learning, and innovation together for our System Level Design Review (SLDR) presentation, a major milestone in the development of L.A.A.R.K: AI-Enabled Lighting Asset Management & Digital Twin Platform.

Bringing It All Together

Over the semester, our focus shifted from exploring possibilities to building structure, defining how our platform will manage lighting assets, predict maintenance needs, and support energy-efficient decisions. The SLDR gave us the space to reflect on this progress and demonstrate how our design is ready to move into development.

During the presentation, we walked our sponsor and faculty through our goals, progress, and lessons learned. The feedback we received highlighted our strong organization, clear communication, and forward-thinking approach to sustainability and smart-building innovation.

Lessons and Reflections

This semester was about more than just creating a product, it was about learning how to think like a team of engineers. From weekly meetings to planning sessions, we learned how to translate complex challenges into actionable steps and how to keep momentum even when data or direction was still evolving.

The SLDR was a proud moment that reminded us how much collaboration, adaptability, and perseverance can achieve. We closed the semester feeling confident in our vision and ready to bring our ideas to life in the spring.

Looking Ahead

Next semester, Team 14 will shift gears into implementation and testing, turning our design into a working prototype that facility managers can interact with and evaluate. We’re excited to take everything we’ve learned and continue building toward a system that makes lighting management smarter, simpler, and more sustainable.