Project centered workflow
Creates one managed workspace for project details, QA content, inspection records, generated documents, and recovery files.
Flagship application
F.A.T.
Factory Acceptance Testing managed as one controlled project workflow.
I designed and built F.A.T. to replace scattered forms, folders, and manual document assembly. The system keeps project setup, QA content, inspection records, PDFs, backups, permissions, and activity history together.
ROLEProduct design and engineering
PLATFORMDesktop and browser application
DELIVERYWindows Server and tablet use
FOCUSQA records and document control
01 · The problem
Critical QA records were spread across disconnected files.
Factory acceptance work requires project details, repeatable checks, signoff fields, review copies, final records, and reliable storage. Managing those pieces separately increases rework and makes the current record harder to identify.
F.A.T. gives each project one managed workspace and one consistent path from setup through inspection and document output.
02 · The solution
A practical application built around the work itself.
The interface follows the actual process instead of forcing the work into a generic form system.
Reusable QA package builder
Lets users select approved QA items, organize them into sections, set quantities and locations, and control document order.
Inspection and activity records
Tracks initials, dates, notes, completion progress, saved revisions, and project activity in one workflow.
Controlled documents and recovery
Generates structured PDFs, separates drafts from final records, preserves backups, and uses audited deletion instead of permanent removal.
03 · System design
Clear inputs. Controlled work. Reliable records.
The Python desktop application established the product model. The web version moved that workflow into a shared internal application for workstations and tablets.
Projects and QA catalog
Project data, approved QA items, sections, quantities, and notes.
Build, inspect, and review
Validation, saving, roles, progress, revision checks, and history.
Documents and records
PDF packages, project history, backups, and recoverable archives.
04 · Engineering and delivery
Built for use outside the development machine.
Deployment, access, storage, recovery, and support documentation were treated as product requirements, not cleanup work.
- Shared access
- The browser version supports internal workstations and tablets without installing the application on every device.
- Operational deployment
- The desktop version is packaged for Windows with its Python, PyQt6, and ReportLab dependencies included.
- Separated application data
- Application files and writable project data use separate locations so updates do not overwrite active records.
- Access and recovery
- Role controls, Windows permissions, backups, audit history, and soft deletion support normal administration and recovery.
Full product ownership
I took F.A.T. from an operational problem to a supportable application.
The work covered requirements discovery, interface design, data modeling, PDF generation, packaging, server deployment, permissions, recovery, testing, user documentation, and support planning.
05 · Operational readiness
Designed for deployment, administration, and continued support.
F.A.T. is more than a user interface. The project includes the application, deployment model, storage rules, access controls, recovery paths, and the documentation needed to operate it.
Complete project lifecycle
Project creation, QA package setup, inspection, saving, reopening, PDF review, and retained history work as one connected process.
Built for an internal environment
The application supports shared Windows deployment, browser access, tablet use, and controlled storage outside the source code.
Documented for handoff
User guidance, deployment instructions, validation steps, permissions, known limits, and recovery procedures are documented.
06 · Product evidence
Real application screens and generated output.
Public examples use synthetic records. The generated document is redacted to protect internal project and QA content.
The larger takeaway