NEO Production View

Many sources.
One operational view.

A production display backed by a separate collection pipeline, designed to make work in process and data status visible together.

FOCUS: Operational visibility
FORMAT: Python · SQL · CSV · pygame
PROJECT STANDING: Production-display project

NEO Production View application showing throughput, active parts, five process areas, machine uptime, and capacity status — Actual application interface · Portfolio demo with synthetic data

The actual NEO Production View application interface in portfolio-demo mode. The supplied image uses synthetic data and has no live connection.

01 / THE PROBLEM

The work
behind the interface.

A production team needs to understand what is happening across multiple cells. A display can become misleading if missing records, old data, and an empty process all look the same.

The approach

Collect records from five SQL cell sources, prepare CSV data, and render a dedicated full-screen display. Keep collection separate from presentation and make freshness and source identity part of the design.

Inside the project.

CAPABILITIES & DESIGN DECISIONS

Separate collection from display.

The collector writes CSV records. The display reads those files, without requiring a direct SQL connection from the display host.

Make source health visible.

An identified data source and explicit freshness signals help distinguish a quiet process from an unavailable feed.

Preserve meaningful counts.

Part identity and exit evidence govern what appears. A delayed part can be flagged rather than removed simply because time has passed.

Support operational continuity.

The project includes process controls, daily archives, and recorded totals. Live configuration and operating conditions still determine deployment behavior.

THE PRACTICAL PRINCIPLE

A dashboard needs to show how much it knows, as well as what it knows.

A similar challenge?

Let’s talk about your workflow.

Start a conversation