Shop-Floor Execution, Native to NetSuite
FactoryBridge puts work order execution in the operators' hands — setup and run timed to the second, components issued against lot and bin, yield recorded as it happens, and every action written back to NetSuite.
Key Features
Scoped Operator Console
Location, work center and module — operators only ever see the jobs at their station.
Timed Setup & Run
Two independent timed phases per operation, each pausable against a coded reason.
BatchWizard Campaigns
Group work orders into a campaign and run them in planned sequence.
Lot & Bin Issue
Components issued against a cascading lot, bin and inventory-status selection.
CoYield
Co-products and by-products captured at completion, with lot and expiry.
YieldCraft
Input variance — planned against actual — allocated back to inventory.
Sync Center
A device-scoped queue so the floor keeps running when the network does not.
Admin Console
Users, roles, locations, work centers, feature toggles and a full audit log.
The shared sign-in — operators and administrators start at the same screen; role decides which console opens
How it fits together
FactoryBridge is an execution layer, not a second system of record. Operators work against NetSuite work orders in real time; completions, component issues and yield entries are written back as they happen. The console is deliberately narrow — an operator signs in, picks their location and work center, and sees only what runs there.
The scoping chain
- Location — the NetSuite location the operator is working at.
- Work center — the station within that location.
- Module — Work Orders, BatchWizard, CoYield or YieldCraft.
Documentation
Each part of the console, on its own page.
The Operator Console
Everything an operator touches lives behind three choices: which site they are at, which work center they are standing at, and which kind of work they are doing.
Location, work center, module
The console does not open onto a list of everything. It narrows deliberately, so that an operator at a single machine sees only the work that belongs to that machine.
Step 2 — work center. The work centers configured for the chosen location.
Step 3 — module. Work Orders for direct execution, BatchWizard for campaigns, CoYield and YieldCraft for recording.
The chain is reflected in the URL — /operator/{location}/{workCentre}/{module} — so a
tablet can be bookmarked directly to a station and will reopen there.
Why the module choice matters
Work Orders and BatchWizard are two routes to the same execution screen. Work Orders lists individual work orders routed to this work center; BatchWizard lists batch work orders, each grouping several work orders that run as a campaign. CoYield and YieldCraft are not execution — they are recording modules that act on completions that already exist.
The four modules
Work Orders
Every work order whose current operation sits at this work center, with planned, completed and remaining quantities and accumulated time.
Read the docs →BatchWizard
Batch work orders, each expanding into its member work orders with a sequence number.
Read the docs →CoYield
Records co-products produced alongside the main item, against a specific completion.
Read the docs →YieldCraft
Records actual component usage against planned, and allocates the resulting variance to inventory.
Read the docs →The account menu
The avatar at the top right carries the operator's utilities. Two of them matter day to day.
Operator account menu. Change password, Sync Center, My Activity, Log Out.
My Activity. The operator's own audit trail, including Work order lock acquired and Completion recorded in NetSuite.
Sync Center holds submissions made while the tablet was offline, ready to sync when it reconnects. My Activity is the operator's own history — useful when someone needs to prove what they recorded and when.
Concurrency is handled with locks
The activity trail includes Work order lock acquired events. Starting an operation takes a
lock on that work order, which prevents two operators at the same work center from running the same job
simultaneously.
Scanning
Scan controls appear next to every identifier field — items, lots, bins — and as a global work-order scan on list screens. They are governed by the Enable Scanning toggle in admin settings.
No separate scanner hardware is required
Scanning uses the device camera through the browser, with an on-screen framing overlay and an Upload photo fallback for long barcodes that will not focus. On a shop-floor tablet the built-in camera is the scanner. A dedicated USB or Bluetooth scanner that emulates a keyboard will also work, since the underlying fields accept typed input.
Frequently asked questions
Why can an operator not see a work order they know exists?
The list is filtered to work orders whose current routing operation is at the selected work center. If the work order is still sitting at an earlier operation it will not appear here. Open any work order's operation details to see where it currently sits.
What happens if the previous operation has not been completed?
The execution screen refuses to start and explains why: "Previous operation has not been started. Complete or partially complete the previous operation before starting this operation." The routing is enforced rather than advisory.
Can one tablet be shared between work centers?
Yes. The location and work center are chosen per session rather than fixed to the device. Sync Center belongs to the tablet rather than to the account, so anything it has queued while offline stays with that tablet until it is back on the network.
Work Orders — execution at the work center
The Work Orders module is where an operation is actually run: setup timed, run timed, pauses coded to a reason, and a completion quantity entered against the work order.
The work order list
Every work order whose current routing operation sits at the selected work center, with planned, completed and remaining quantities, accumulated time and status. The list can be searched, sorted on any column, filtered to Partially Completion, and its columns can be shown or hidden.
Work Orders. Planned quantity, completed against planned, remaining, accumulated time and status, with search and a column picker.
Seeing the whole routing
The eye icon on any row opens the operation details — the full routing across every work center, with the current operation marked. This is how an operator answers "where is this job actually up to?" without leaving the console.
Operation details. Each work center in routing order, its operation status, quantity completed and remaining. The current operation carries a Current badge.
The routing gate
Operations cannot be run out of order. If the preceding operation has not been started, the execution screen refuses and says so plainly.
Routing enforced. "Previous operation has not been started. Complete or partially complete the previous operation before starting this operation."
Two timed phases
Each operation is timed in two independent phases — setup and run. They are recorded separately, which is what makes changeover cost visible rather than buried inside total production time.
- Start Setup Time. The timer runs and the work order moves to In Progress.
- Pause, with a reason. Pausing requires a coded reason, so downtime is categorized at the moment it happens rather than reconstructed later.
- Complete setup. A confirmation states the elapsed time that will be recorded and warns that it cannot be undone. The work order moves to Setup Completed.
- Start Run time. The same controls, timed separately. Issue Components becomes available during this phase.
- Complete run. Again confirmed with the elapsed time. The work order moves to Runtime Complete and the batch time summary appears.
- Enter Completion. Quantity completed, validated against what remains.
Setup running. Pause and Complete, with the phase badge showing Setup time.
Setup complete. The phase badge switches to Run time and the action becomes Start Run time.
Pause reasons
A pause cannot be recorded without selecting a reason. The list is the tenant's downtime taxonomy — on the documented tenant it includes Machine Breakdown, Machine Maintenance, Material Quality Issue and Material Shortage, among others.
Pause requires a reason. Confirm Pause stays disabled until one is chosen.
The reason list. Machine Breakdown, Machine Maintenance, Material Quality Issue, Material Shortage and more.
This is the most valuable data the system collects
Coded pause reasons captured at the moment of stoppage are what turn a timer into downtime analysis. Getting the reason list right for the plant matters more than almost any other configuration decision.
Irreversible steps are confirmed
Completing a phase states the exact elapsed time that will be written and warns that the action cannot be undone.
Complete Setup Time? The elapsed time to be recorded is stated explicitly.
Current Batch Time. Setup, run and total, shown once the run phase closes.
Recording the completion
The completion dialog shows the completion time, the quantity entered so far in this segment and the quantity remaining. Partial completions are supported — enter less than the balance and the work order moves to Partially Built, retaining the remainder.
Record Completion. Quantity completed, with "Entered this segment" and "Remaining" shown beneath the field.
Partially Built. A completion of 1 against a planned 2 leaves the work order open with the balance outstanding.
Once a completion exists it becomes a record in its own right — labelled WO1614-1 for the
first completion of that work order — carrying its own setup time, run time and total, and its own
CoYield and YieldCraft entries.
A completed work order. Completion record, time breakdown and the optional follow-ups for co-yield and yield variance.
Behavior worth knowing
| Observation | Detail |
|---|---|
| Over-production is blocked by default | Completion is refused once cumulative completed quantity reaches the planned quantity, unless Allow Over Production is enabled in admin settings. |
| Locks prevent double-running | Starting an operation acquires a work order lock, recorded in the audit log. |
| Timers survive navigation | Leaving the screen and returning shows the operation still running with accumulated time intact. |
Frequently asked questions
Can setup and run be recorded by different operators?
Each action is attributed individually in the audit log, so a shift change mid-operation is recorded accurately. The work order lock is what governs simultaneous access, not the phase.
What happens to a pause that is never resumed?
The operation stays in Paused with the timer stopped. It does not accrue time and it does not auto-resume; an operator must resume or complete it explicitly.
Can a completion be corrected after submission?
Not from the operator console. Completion dialogs state that the action cannot be undone, and the correction belongs in NetSuite. This is deliberate — the console is an execution record, not an editing surface.
Why does the run phase briefly show the setup elapsed time?
After completing setup, the timer continues to display the setup total under a Run time badge until Start Run time is pressed, at which point it resets to zero. Cosmetic, but it reads as though run time has already accrued.
BatchWizard — running a campaign
BatchWizard groups work orders into a batch work order and runs them as a sequenced campaign, so a production run that spans a dozen orders is planned and executed as one unit.
Batch work orders
The module opens on the batch work orders available at this work center, each showing how many work orders it contains. Opening one lists its members with their sequence number, planned and completed quantities, accumulated time and status.
Batch Work Orders. Each batch with its work order count.
Inside a batch. Sequence, work order, item, planned, completed, remaining, time and status.
From here the execution screen is identical to the one reached through Work Orders — the same two timed phases, the same coded pauses, the same completion dialog. What BatchWizard adds is the campaign grouping and the sequence.
Execution inside a batch. The header carries both identifiers — batch and work order — so the operator can see which campaign they are running.
Sequence
Sequence numbers express the intended order of a campaign — grouping similar items so the line changes over as little as possible. On the documented tenant sequences were not contiguous (1, 2, 4), so the number expresses order rather than position.
Time is tracked per completion
Each completion inside a batch carries its own setup, run and total time. A batch that produced two completions has two independent time records, not an aggregate.
Completion inside a batch. Setup, run and total time for that completion, with co-yield and yield variance available as follow-ups.
Frequently asked questions
Does a batch have to be run in sequence order?
The sequence is displayed and sortable, and it expresses the planned order. Routing enforcement operates per work order rather than across the batch, so the sequence is planning guidance rather than a hard gate.
Can a batch be partially completed?
Yes. Each member work order completes independently, and each can itself be partially completed. A batch in progress will commonly show a mix of Completed, Partially Built and Pending members.
Where do batch work orders come from?
They originate in NetSuite — typically from ProShop's BatchWizard module, which creates formula-based work orders in bulk. FactoryBridge reads and executes them; it does not create them.
Issue Components — consuming material with traceability
Component issue is available during the run phase. It records which lot, from which bin, in which inventory status, was consumed against the operation — the backbone of downstream traceability.
Opening the dialog
The Issue Components action appears beneath the timer once the run phase has started. It lists the components the work order expects, each collapsible.
Issue Components. The components expected by this work order.
Expanded. Required quantity is stated, with Add to create an issue row and a scan control alongside.
The cascade
Issue rows resolve in order, each field narrowing the next. This is what prevents an operator from issuing a lot that is not actually in the bin they selected.
- Lot. Chosen from the lots available for that component.
- Bin. Narrowed to bins that hold the chosen lot.
- Inventory status. Resolved from the lot and bin combination — often auto-selected when only one status applies.
- Available quantity. Displayed, not entered — the operator sees what is actually there.
- Quantity to issue. Entered against that availability.
The cascade. Bin and status stay disabled until a lot is chosen — "Enter lot first", "Select lot first".
Ready to submit. Available quantity resolved, quantity to issue entered.
Non-lot components skip straight to bin, status and quantity. Components with neither lot nor bin tracking take a quantity alone.
After submission
The action changes to View Issued Components, which shows what was consumed — component line, issued quantity, lot, bin and status.
Issued Components. The audit view: component line, issued quantity, lot, bin and inventory status.
Partial issues are permitted
Where required quantity exceeds what a single lot or bin holds, the operator can issue what is available and the system accepts it without objection. Add further rows to draw from additional lots or bins. If your process requires the full required quantity to be issued before completion, that control does not exist today and would need to be enforced procedurally.
Frequently asked questions
Can components be issued after the run phase is complete?
Yes — Issue Components remains available on the post-run action list alongside Enter Completion, so material can be reconciled after the fact.
What if the lot needed is not in the list?
The list is populated from NetSuite inventory for that component. A missing lot means it is not on hand in a bin visible to this location, which is an inventory question rather than a FactoryBridge one.
Is issuing the same as consuming in NetSuite?
The issue is posted to NetSuite against the work order. The audit log records it as
Issue under the relevant module.
CoYield — recording co-products
Formula-based production rarely yields one output. CoYield records the co-products and by-products that came off the line alongside the main item, tied to a specific completion.
Two ways in
Co-yield can be recorded at the moment of completion or picked up later. Both write the same record.
Inline, at the completion
Immediately after a completion is recorded, CoYield appears as an optional follow-up on the work order screen.
From the CoYield module
A list of completions awaiting co-yield, in Work Orders and Batch Work Orders tabs, each showing Pending or Success.
The CoYield module. Completions with their co-yield status — Pending until recorded.
After recording. The row flips to Success. Status describes the co-yield record, not the work order.
Reading the Status column correctly
A completion can show Pending here while the work order itself is fully complete. The column describes whether co-yield has been recorded for that completion — not the state of production.
Recording co-products
The dialog is headed with the work order and completion number and carries the full completion ID and quantity, so there is no ambiguity about which output the co-products belong to.
Where the work order defines co-products, they are pre-populated. Where it does not, the operator adds them from a searchable picker over the item master.
Pre-populated co-products. A lot-managed co-product and a bin-managed one, each with its own entry grid.
Added manually. An empty item row with a scan control, for work orders that define no co-products.
Entry mirrors the tracking of the item. Lot-managed co-products take a lot number, inventory status, expiry date and quantity. Bin-managed co-products take a bin, status and quantity.
Lot-managed entry. Lot, status, expiry date and quantity.
Bin-managed entry. Bin chosen from a searchable list, status and quantity.
Validation is explicit
Rather than disabling the submit button silently, the dialog lists what is still missing and keeps listing it until each item is resolved.
Cannot submit yet. Each unmet requirement is named — here a quantity greater than zero and a required expiry date.
Expiry date is a tenant setting
Whether expiry is mandatory is controlled by Require Expiry Date in admin settings. When disabled the field still appears but is optional.
History
Once recorded, the inline action becomes View Co-Yield History, listing what was submitted against that completion.
Co-Yield History. Item, quantity, lot, bin and status for each submitted line.
Frequently asked questions
Can co-yield be recorded for a partial completion?
Yes. Co-yield attaches to a completion, and a partial completion is a completion. A work order that produced two partial completions can carry separate co-yield records against each.
What is the difference between CoYield and YieldCraft?
CoYield records additional outputs — what else came off the line. YieldCraft reconciles inputs — how much component material was actually consumed against plan. Outputs and inputs, recorded separately.
Is co-yield mandatory?
No. It is presented as an optional follow-up and completions can be left with co-yield Pending indefinitely. If it matters for your costing, the module list is where you see what has been missed.
YieldCraft — reconciling planned against actual
YieldCraft captures what a completion actually consumed against what it was planned to consume, and requires the resulting difference to be accounted for in inventory rather than written off silently.
Entering actual usage
The dialog lists each component with its planned quantity and an editable actual usage field. Variance is calculated as you type.
Issue Yield Variance. Component, planned, actual usage, variance and an inventory link per row.
Variance calculated. Planned 50 against actual 52 gives −2; planned 20 against actual 19 gives +1.
Read the sign convention carefully
Variance is calculated as planned minus actual. Using more than planned produces a negative variance; using less produces a positive one. This is the accounting convention — positive means material was saved — but it is the opposite of what many operators assume. Worth covering explicitly in floor training.
Variance must be allocated
A variance cannot simply be declared. Each one has to be allocated against real inventory before the form will submit, so the difference lands somewhere accountable.
Negative variance. Target variance and issued total, with inventory status, available quantity and quantity to issue.
Positive variance. Bin and status for material returning to stock, with allocated total tracked against target.
The allocation panel tracks issued or allocated total against the target and turns it green on a match. Until the two agree, the parent dialog continues to refuse submission.
Allocation matched. Issued total equals target variance, with available quantity resolved from the chosen status.
Zero variance
Where actual equals planned there is nothing to allocate and the form submits immediately — the common case, and it stays out of the way.
Zero variance. Actual matches planned, so no allocation is required and submission is immediate.
Yield Variance History. Component, required, actual, variance and the allocation detail.
Frequently asked questions
Why does the allocation dialog say "negative variance −2" but "Target variance: 2"?
The heading restates the signed variance; the target is the absolute quantity to allocate. The two refer to the same difference. It reads inconsistently and is worth aligning, but the arithmetic is correct.
Can yield variance be recorded without issuing components first?
Yes. Planned quantities come from the work order's component requirements rather than from what was issued, so YieldCraft can be completed independently of Issue Components.
What happens to the allocated material?
It is posted against the chosen inventory status and bin — extra consumption issued out of stock, savings
returned to it. The audit log records the submission as YieldCraft · Submit.
Sync Center — when the network drops
Factory wifi is not office wifi. Sync Center is where submissions made while a tablet is offline are held, so they can be synced once it is back on the network.
What it holds
Sync Center is scoped to the device. If a tablet drops off the network, the submissions made on it are held there and can be synced once it is back online — nothing is lost and nothing has to be re-entered. Four kinds of submission are queued: component issues, completions, co-yield and yield variance.
Sync Center. Pending, Synced and Failed counters, with Refresh and Retry all.
The queue is counted as Pending, Synced and Failed, so an operator can see at a glance what has gone through and what has not. Retry all re-attempts the queue and Refresh updates the counts.
Nothing to sync. The empty state names exactly which submission types queue here, which is the clearest statement of the offline model in the product.
The offline model
FactoryBridge is online-first. Reading work orders requires a connection, because the data lives in NetSuite. What is protected is the write path: an operator who has already started work and loses connectivity mid-shift does not lose the record of what they did.
Set expectations accordingly
This is resilience, not offline operation. An operator cannot pick up a new work order on a disconnected tablet. They can finish, and record, the one they are on.
Related: connection quality
Because every action is a NetSuite round trip, connection quality shows up as waiting rather than as failure. The API Latency Dashboard is where an administrator sees whether the floor is slow because of the network or because of NetSuite.
Frequently asked questions
How long do queued submissions survive?
They stay on the device until they are synced. Because the queue belongs to the device rather than to the account, an operator who moves to a different tablet does not carry it with them — the original tablet has to come back online for its queue to clear.
Can an administrator see another device's queue?
Sync Center reflects the device it is opened on, so it is not a tenant-wide view. The admin audit log shows what has successfully reached the server, so a submission sitting on a tablet but absent from the audit log has not synced yet.
What happens if a queued submission is rejected on retry?
It is counted under Failed rather than disappearing, and stays in the queue so it can be retried once the tablet is back on the network.
The Admin Console
The customer administrator manages who can sign in, sees how locations and work centers map to NetSuite, controls the feature toggles that change what operators see, and reads the audit log and latency dashboard.
Users and roles
The console opens on the user list — name, email, role and status, with edit and delete per row.
Admin Console — User. Every user in the tenant with their role and status.
Two roles are assignable, and the picker states plainly what each grants.
Role options. customer-manager — delegated customer admin with full tenant permissions. operator — all permissions except user management and invitations.
| Role | Grants | Assignable |
|---|---|---|
customer-admin | The tenant owner account. Full administration. | No |
customer-manager | Delegated customer admin with full tenant permissions. | Yes |
operator | All permissions except user management and invitations. | Yes |
Administrators cannot edit themselves
Edit and delete are disabled on customer-admin rows, with the tooltip "Customer-admin users cannot edit other customer-admin accounts or their own account." This prevents an administrator locking themselves or a peer out. A separate Clear active session action releases a session so the user can sign in elsewhere — which implies a single-active-session policy per account.
Add New User. Name, email, role and status.
Locations and work centers
The second tab lists every NetSuite location, expanding to the work centers beneath it with their NetSuite internal IDs. This is read-only — the structure is maintained in NetSuite — but it is the fastest way to confirm what an operator will see.
Locations. Every NetSuite location available to the tenant, including sub-locations.
Work centers. Expanded with internal IDs — Cooking & Stirring is #3325, matching the operator console URL.
Feature toggles
Settings → Features controls operator-panel behavior for the whole tenant. Changes apply immediately. These four toggles explain more operator-facing behavior than any other screen in the product.
Features. Four tenant-wide toggles governing scanning, expiry dates, over-production and custom lot/serial fields.
| Toggle | Effect when enabled | Operator symptom when disabled |
|---|---|---|
| Enable Scanning | Barcode and QR scan controls appear throughout the operator panel. | Scan buttons disappear; identifiers must be selected or typed. |
| Require Expiry Date | Expiry is mandatory for lot items on completion, co-yield and positive yield variance. | The field still shows but submission no longer blocks on it. |
| Allow Over Production | Operators may record quantities exceeding the planned quantity. | Completion is refused once cumulative completed quantity reaches planned — the source of the "more than remaining" message. |
| Enable Lot & Serial Custom Field Configuration | Administrators can configure custom fields for lot and serial entry, which then appear in operator transactions. | The configuration table is hidden and no custom fields appear. |
Diagnostic shortcut
When an operator reports that the system "won't let them" do something, check this tab first. Three of the four toggles produce exactly that class of complaint.
Profile and branding
Settings → Profile carries the account name and a company logo upload that replaces the header mark for the administrator and every user they have invited.
Settings — Profile. Account name and company logo, shown in the header for invited users.
API Latency Dashboard
A live view of gateway performance with the NetSuite portion isolated — average, P95, max and error rate over a selectable window, then a per-endpoint table split into PULL and PUSH.
API Latency Dashboard. Headline figures, gateway-to-NetSuite latency, then per-endpoint detail with request counts and error rates.
What the numbers said on the documented tenant
Over one hour of genuine use: average 1176 ms, NetSuite average 1168 ms. The gateway contributes roughly eight milliseconds. P95 was 2440 ms and the slowest call 5411 ms, with a 0% error rate. Read plainly: the platform is reliable and the latency is NetSuite's. Front-end optimization will not move these numbers — reducing the number of round trips, or not blocking the operator on them, would.
Audit Log
Every operator action across the tenant, filterable by module, action type, operator, work order number and date range, exportable to CSV.
Audit Log. Time, operator, module, action, work order reference and result, with filters and CSV export.
Two naming inconsistencies worth aligning
The audit log labels the Work Orders module "Classic WO", a name that appears nowhere in the
operator interface. And Lock rows show a raw internal identifier
(cmtk4tbhn0001l504isqhq8il) in the WO Ref column rather than the work order number, which makes
lock events hard to correlate with the job they belong to.
Frequently asked questions
Can an administrator create locations or work centers?
No. Both are read from NetSuite. The Locations & Work Centers tab is a mirror, useful for confirming what an operator will be offered.
What does "Clear active session" do?
It releases the account's active session so the user can sign in on another device. Its presence implies accounts are limited to one active session, which is a sensible default for shared shop-floor hardware.
How far back does the audit log go?
The documented tenant held 94 entries spanning several weeks, paginated. The date range filter and CSV export are the tools for anything longer than a browse.
Does changing a feature toggle require operators to sign out?
The screen states that changes apply immediately. Have an operator refresh their console if they are mid-session when a toggle changes.
Product Roadmap
FactoryBridge is actively developed. What follows is what we are building next — shaped by what manufacturers actually hit on the floor, not by a feature checklist.
Q3 2026 — Quality, Instructions & Projects
The next release takes FactoryBridge beyond timing and quantity: what good looks like, how the job is done, what to do when it is wrong, and project work alongside standard production.
Q3 2026: Quality, Instructions & Projects
Today FactoryBridge records what was made, by whom, from which lot, and how long it took. This release adds the quality and instruction layer around that record, and opens execution to project-based work.
Quality Check
Inspection steps presented on the operator console as part of the operation, with results recorded against the completion rather than on paper. Because the check happens where the work happens, the quality record and the production record share the same operator, timestamp and lot.
Work Instructions
The current operation’s instructions shown on the terminal — text, images and attached documents — so an operator sees what to do without leaving the console or hunting for a printed traveler. Revision controlled, so the floor is never working from a superseded sheet.
Non-Conformance Reports
Raise an NCR from the console at the moment something fails, capturing the work order, operation, quantity affected and reason at the point of discovery — then route it into NetSuite for disposition instead of letting it live in a notebook until the end of the shift.
NetSuite Projects Integration
Project-based work executed alongside standard work orders, so operations tied to a NetSuite project carry their project context through timing, component issue and completion. The natural pairing for engineer- and make-to-order manufacturers already using Project2Prod.
Q4 2026: Machine Data & LumberSuite
The fourth quarter turns the execution record into machine-level insight, and brings lumber-specific quantities into the operator console.
Machine OEE
Availability, performance and quality per machine and per work center — derived from data FactoryBridge already captures: separately timed setup and run phases, coded pause reasons, completion quantities and quality results. The coded pause reason is what makes the availability half of OEE meaningful rather than a guess.
LumberSuite Integration
Board-foot quantities, tally detail and species and grade attributes handled natively on the operator console, so a lumber operation records what it actually produced rather than an approximation in eaches. Connects the shop-floor record to LumberSuite.
Release Timeline
| Quarter | Theme | Key Features | Status |
|---|---|---|---|
| Q3 2026 | Quality, Instructions & Projects | Quality check, work instructions, non-conformance reports, NetSuite Projects integration | PLANNED |
| Q4 2026 | Machine Data & LumberSuite | Machine OEE, LumberSuite integration | PLANNED |