Orders
Buyer, style, quantity, value, ship date, planned start, and risk notes.
Simple Version
G3CT turns factory data into the next management decision.
It reads orders, readiness, capacity rules, cash rules, and editable assumptions. Then it calculates future risk, explains why the risk exists, and creates a ranked action queue with due dates and owners.
Input
Plan data
Process
Engines
Output
Actions
Operating Relationship
1
Orders
2
Full Kit
3
Capacity
4
Cash
5
Actions
Inputs
What The System Reads
Inputs are source facts and editable assumptions. They are not all equally mature yet: Orders and Full Kit currently come from the approved Base Plan, while Cash, Capacity, and Action assumptions can be edited in Settings.
Full Kit
Fabric, trim, packaging, readiness %, expected ready date, and blocker.
Factory
Sewing lines, combos, working days, output rate, and OE scenario.
Cash Rules
Opening cash, vendor credit, buyer terms, TVC %, factoring, and buffers.
Settings
Editable assumptions used by Cash, Capacity, and Action Engines.
Process
How The Engines Work Together
Each engine creates one part of the management picture. The point is not only to calculate a number, but to explain what caused the number and what action follows.
Full Kit View
Shows whether orders are ready, partial, or critical. Current build reads the approved dataset.
Capacity Engine
Compares planned load with generated available capacity to find idle time or overload.
Cash Engine
Turns order values and payment rules into generated cash events and cash balances.
Action Engine
Ranks actions by business priority. Cash always outranks Capacity.
1. Read the plan
Bring together orders, readiness, factory model, cash rules, and settings.
2. Calculate risk
Generate cash dates, capacity gaps, readiness blockers, and order exposure.
3. Explain the driver
Connect every red or amber signal to the order, week, cash event, or material blocker.
4. Rank the action
Create the queue. Cash comes before Capacity, then owner and due date make it executable.
Outputs
What The User Gets
Outputs are generated views that help management decide. They are designed to be traceable back to the inputs and assumptions.
Dashboard KPIs
Idle capacity, cash risk date, ready orders, and order risk.
Detail Tables
Orders, Full Kit, Capacity, Cash events, and generated exception queues.
Exceptions
The weeks, orders, and cash dates that need management attention.
Actions
Owner, due date, reason, impact, and the suggested next move.
Status Logic
Traffic-Light Meaning
The same color language appears across the app so users can scan faster.
Healthy
No immediate management action.
Watch
Needs follow-up before it becomes a blocker.
Action Required
Needs management action now.
Formulas
Core Logic In Plain English
These are the formulas behind the current engines. Settings change the assumptions; the formulas recalculate the outputs.
Weekly Capacity
combos x pcs per combo day x working days x OE factor
15 x 1,100 x 6 x 1 = 99,000 pcs/week
Utilization
planned load / available capacity x 100
62,370 / 99,000 x 100 = 63%
Idle Capacity
max(0, available capacity - planned load)
99,000 - 62,370 = 36,630 pcs idle in W32
Overload
max(0, planned load - available capacity)
If load is 84,000 and capacity is 77,220, overload is 6,780 pcs
Cash Balance
opening cash + inflows - outflows
Generated events find first negative date and lowest cash point
Working Capital Required
cash gap + minimum buffer + timing buffer
Lowest negative cash plus operating cushion
Action Rank
area priority, then severity, then due date
Cash rank 1 comes before Capacity rank 3
Action Due Date
risk date - configured buffer days
14-Aug negative cash minus 4 days = 10-Aug due date
Output Rules
What Changes When Settings Change
Submitted Settings values are saved in the browser and used by the engines on the next calculation.
Cash Engine changes cash dates and cover
Opening cash, TVC, payment terms, factoring, and buffers change generated cash events, first negative date, lowest cash, and working capital required.
Capacity Engine changes utilization and gaps
Combos, output rate, working days, thresholds, and OE mode change available capacity, utilization, idle exposure, overload, and the heatmap.
Action Engine changes queue order and due dates
Area ranks, buffers, thresholds, owners, and order-value rules change the generated Exception Queue. Cash is validated above Capacity.
Boundaries
What G3CT Does Not Do Yet
These boundaries keep the prototype honest. The system supports planning decisions; it does not pretend to be the transaction system.
It is not an ERP replacement. It sits above ERP and planning sheets.
It does not write generated Cash, Capacity, or Action outputs to Supabase yet.
It does not move orders automatically. Pull-forward remains a management decision.
It is not a full accounting ledger, bank reconciliation, payroll, or tax engine.
It does not yet run a live Full Kit Engine from uploaded material transactions.
It uses the approved Base Plan dataset until live source migration is approved.
Meaning Of Terms
Plain-Language Glossary
These are the words users see across the app.
Full Kit
Enough fabric, trims, and packaging are ready for an order to safely start.
Combo
A production group of sewing lines used for capacity planning.
OE
Operating efficiency. In G3CT it can optionally adjust generated capacity.
TVC
Total variable cost used to estimate production cash commitments.
Idle Capacity
Available production capacity that is not loaded with runnable work.
Overload
Planned load that is higher than available capacity.
Pull Forward
Move a ready future order into an earlier week to recover open capacity.
Working Capital
Cash cover needed to avoid a production stop or material release delay.
Exception
A signal that needs management attention because it can affect throughput.
Action
A ranked next step with owner, due date, reason, impact, and suggestion.