01/05 · wizard
Request
REQ-1042 · SUBMITTED
Wizard intake — every request lands a complete, reviewable record.
PRYYSM · Built for mixed FDM/SLA/SLS job shops
The MES for FDM, SLA & SLS job shops. Print request to QC-checked part — one system.
Built for job shops and internal print farms running mixed FDM/SLA/SLS fleets — request, review, schedule, QC, close.
or email info@3d-prodigy.com
feasibility vs real stock — verified before one gram prints
a working product, not a mockup · production management · not AI · not a slicer
02Proof
Why production runs AM on PRYYSM
Feasibility vs real stock.
Live, not batch.
Quality gates built in.
Multi-site by default.
STACK · React · FastAPI · PostgreSQL (RLS) · WebSockets · Docker · REST API + OpenAPI
Every claim above is a product behavior in PRYYSM today — no invented numbers.
4step request wizard
7lifecycle states
6platform pillars
13real modules
3technologies
5role seats
counts of the workflow shown on this page.
03ProblemInformal
Requests were never meant to live in chat, email, and spreadsheets.
BEFORE — THE FLOOR RUNS ON TRUST
requests scattered
jobs committed blind
printers idle + double-booked
material runs out mid-job
QC improvised at the end
"where is my part?"
What's missing isn't better printers. It's the operations layer around them.
04SolutionStructured
PRYYSM is that layer — between your machines and your deadlines.
AFTER — ONE DISCIPLINED PATH
wizard intake, structured
AM Review — verified before promising
work order issued, one click
one live data thread for schedule, stock, QC
full lifecycle archived
PRYYSM is not a slicer and not an STL viewer. It is the production-management layer around your print machines.
05How it works
Every job, one disciplined path.
01REQUEST
02VERIFY
03PLAN
04PRODUCE
05PROVE
02/05 · AM review
Verify
feas: verified
Material, spares, printer, deadline vs real data — QC scope set here.
03/05 · work order
Plan
WO-2411-007 · READY
One click issues the work order on a passing readiness check.
04/05 · print + post-process
Produce
PRINTER-03 · PRINTINGauto-deduct on
Allotted on the live Gantt — confirmed material auto-deducts once.
05/05 · qa + close
Prove
QC · PASSNCR-0031 · 5-WHYSCLOSED
Nothing closes un-checked — NCR, 5-Whys, rework stay on record.
RUN THE LOOP AT YOUR PACE
Submitted
Review
Planning
Printing
Post-Process
QA
Closed
— two jobs on the board — click a request to advance it
Interactive preview · same workflow logic as the live app.
06PlatformLive
Six pillars carry the work from request to archive.
Six pillars — 13 real modules.
Request intake & wizard
P1 / 06nothing arrives half-specified
General Info→
Items & Tech→
Files & Notes→
Review
NEWREVIEWPLANNINGCLOSED
AM Review feasibility
P2 / 06
material ✔ in stock
spare ✔ in stores
printer ✔ on schedule
deadline ✔ holds
WO-2411-007 · ISSUEDREADY
Gantt & printer fleet
P3 / 06IDLEPRINTINGMAINTENANCEOFFLINE
Materials & spares
P4 / 06Post-processing & QC
P5 / 06
support removal
sanding
washing/curing
powder removal
PASS
Factory overview & multi-site
P6 / 06one facility or many, isolated end to end
WIP · stage limits
exception alerts
tenants · isolated
flow & tasks
Modules live in PRYYSM under their real names — Print RequestsAM ReviewProjects & Work OrdersPrint Schedule GanttPrinter FleetRaw Material InventorySpares & StoresPost-ProcessingQCRepositoryFlow & TasksConfigurationAdmin & Security
07TechnologiesFDM/SLA/SLS
One system for FDM, SLA, and SLS.
One schedule, one inventory, one quality record across all three technologies.
TECH · FDM fused deposition
FDM
PLA-MATTE · IN STOCK
support removal
sanding
Bambu Lab — fleet example
TECH · SLA resin
SLA
RESIN-FORM4 · IN STOCK
washing/curing
Formlabs Form 4 — fleet example
TECH · SLS powder
SLS
POWDER-MJF · LOW
powder removal
HP MJF 1200-class — fleet example
machine names = typical fleet registry entries · no machine photos — data, not a gallery
PRYYSM is not a slicer or an STL viewer. It schedules, inventories, and quality-checks the machines that print — the production-management layer, not the toolpath.
08RolesSEATS · 5
Built for every role on the floor.
REQ · REQUESTOR
Requestor
submit via wizard
upload models & files
set priority & due date
track Submitted → Closed
LIVES INPrint Requests
OP · OPERATOR
Operator
run the live schedule
set fleet status
log stock
auto-deduct material
find spares
LIVES INPrinter FleetRaw Material InventorySpares & StoresPost-Processing
QA · QUALITY
QA
inspect required/recommended/optional
log defects
open NCRs
5-Whys
record cost impact
LIVES INQCRepository
COORD · PRODUCTION CONTROL
Coordinator / Plant Manager
own AM Review
verify vs stock & schedule
issue WOs
master Gantt
trigger reorders
LIVES INAM ReviewPrint Schedule GanttRaw Material InventoryConfiguration
ADMIN · SYSTEM OWNERS
Admin / Super Admin
team & roles
per-tab access
tenants
workflow
PP / QC / notifications
LIVES INAdmin & SecurityConfiguration
09Quality
Quality is a step in the workflow — not a surprise at the end.
01 · GATES
Gates, not guesswork
QC levels defined at review — nothing closes un-checked.
02 · NCR
NCR with root cause
NCR logs it — 5-Whys, rework stay on record.
03 · RECORD
A record that survives audits
Full lifecycle history in the Repository — audit-ready.
Full lifecycle history on record — who requested, reviewed, printed, checked, closed.
Data isolated at the database level (PostgreSQL RLS); role-based, per-tab access. No third-party quality certifications are claimed — the workflow produces the evidence your own audits require.
lifecycle 7 states · recorded
10FAQ
Frequently asked questions.
The operations platform for 3D-printing production: request intake, feasibility review, scheduling, inventory, and QC — every job on one recorded lifecycle.
FDM, SLA, and SLS. The fleet registry tracks any printer you run — Bambu Lab, Form 4, MJF-class — in one schedule, stock, and QC record.
AM Review checks material, spares, machine, and deadline against real data before a work order exists. Not ready? No order.
Neither. No AI, no toolpaths. PRYYSM is the production-management layer that schedules, inventories, and quality-checks real machines.
Yes. Multi-tenant, multi-site: one deployment, many facilities, data isolated by PostgreSQL row-level security.
11CTAREQUEST → CLOSED
See your factory on the schedule.
One request walked through review, schedule, QC, close — on your fleet, in a working product, not a mockup.