SYSPRO + WIP job costing
AI for SYSPRO production and job costing
Short answer
AI on SYSPRO reads work-in-progress jobs, operations, labor and material postings, and compares them with the routing and bill of materials so a plant manager can ask why a job is over cost or late and get an answer tied to specific postings. It runs read-only against the SYSPRO SQL Server database or its business objects and can be hosted on-prem.
- ERP
- SYSPRO
- Industries
- Discrete manufacturing, Machinery, Electronics
- Written for
- Production Manager and Cost Accountant
Most SYSPRO plants know their job costing is only as good as the data entered at the shop floor. A job closes, the actual cost lands in WIP, and the variance against standard shows up in a report weeks after the decision that caused it. The accountant then spends a morning working out whether the overrun was scrap, a substituted component, extra setup, or labor booked to the wrong operation.
SYSPRO stores that story in a SQL Server database: the job header, the operations on the routing, the material allocated and issued, the labor and machine time posted, and the inventory movements behind them. The information exists. The problem is that answering a single question usually means a custom report, a saved query, or an export to Excel that only one person knows how to build.
An AI layer does not replace SYSPRO job costing. It reads the same data, shows the query it ran, and lets a production manager, a cost accountant, or a supervisor ask in plain language: which open jobs are running over material cost, which operations take longer than the routing says, which jobs have issued more than they should have.
This page describes what that looks like on SYSPRO specifically, where it helps, where the standard SYSPRO tools are already enough, and how to keep it safe: read-only by default, scoped to the operator roles you already have, and hosted where your data policy requires.
What usually gets in the way
The problems we hear most from production manager and cost accountant teams running SYSPRO.
Variances found after the job closes
Standard versus actual cost is reviewed at or after job completion. By then the scrap, the overtime, or the substituted material has already shipped and the customer price is fixed.
Labor posted against the wrong operation
Operators book time to a job but not always to the right operation, so the routing looks cheap on one step and expensive on another. Cleaning this up is manual and happens at month end.
Material over-issue is hard to see
Backflushed or manually issued material that exceeds the bill of materials quantity hides in totals. Finding the one job that consumed three times the stock needs a query most supervisors cannot write.
Reports owned by one person
Job cost reports built in SYSPRO Reporting Services or Excel depend on a single analyst. When that person is out, nobody can answer an unusual question about a job in under an hour.
Routing and BOM drift
Standards in the routing and bill of materials age as processes change. The gap between what SYSPRO expects and what the floor does shows up as chronic variance, but nobody has a list of which parts are the worst offenders.
Where AI earns its place in SYSPRO
Each use case names the ERP objects it reads or writes, so your ERP team can judge the integration effort before anyone commits budget.
Ask why a job is over cost
The user names a job and asks for the cost breakdown against the routing and bill of materials. The assistant lists material, labor, and any outside operation, flags the largest variances, and cites the postings behind each number.
Touches: WIP job master, job operations, WIP material and labor posting tables, routing and BOM, inventory movements
Outcome: A variance explanation that used to need an analyst for an hour is available in a minute, with the postings listed so it can be checked.
Open job health scan
Each morning the assistant lists open jobs where cost to date is running ahead of percent complete, or where an operation has more hours than its planned run time. The supervisor reviews a short ranked list.
Touches: Open WIP jobs, operation status, posted hours versus planned hours, material issued versus required
Outcome: Problem jobs surface while they can still be corrected, not at close. The size of the benefit depends on how current your floor postings are.
Labor posting anomaly review
The assistant looks for time postings that are outliers: very long single entries, time on completed operations, or hours on operations out of sequence, and proposes a list for correction.
Touches: Labor postings by employee, work center, and operation; job operation sequence
Outcome: Cleaner labor data feeds cleaner job cost. Humans decide on every correction; nothing is changed automatically.
Standard cost refresh candidates
Across closed jobs, the assistant groups parts whose actual run time or material yield consistently differs from the routing and BOM, and ranks them by volume and cost impact.
Touches: Closed job history, routing standards, BOM component quantities, scrap and yield data
Outcome: A short worklist for engineering to revisit standards, rather than a gut-feel list. Updates still go through your normal change process.
Late job explanation and recovery options
For a job behind schedule, the assistant shows which operation is holding it, whether material is short, and which later operations can be overlapped, based on SYSPRO data.
Touches: Job operations, work center load, purchase order receipts due dates, inventory availability
Outcome: Planners spend time choosing a recovery action instead of collecting facts from four screens.
Quote-to-actual comparison
For repeat parts, the assistant compares the cost estimated at quote time with actuals from the last several jobs and suggests where the next quote should move.
Touches: Sales order lines, job costs, quoted cost, closed job actuals by stock code
Outcome: Estimators see their own history without building a report, which supports more accurate repeat quotes.
Month-end WIP reconciliation helper
The assistant lists jobs whose WIP value differs from the sum of their postings, or jobs with activity but no recent movement, to focus the reconciliation.
Touches: WIP ledger balances, job postings, general ledger WIP control account
Outcome: Finance starts reconciliation with a prioritized list instead of a full sweep. The accountant still signs off the entries.
Reference architecture
The AI sits beside SYSPRO, not inside it. It reads through an approved path, builds answers from curated queries and documents, and shows what it ran. Any write goes through SYSPRO business objects with a human approval step.
- 1
Source access
A read-only SQL Server login scoped to approved WIP, inventory, and routing views, or read calls through SYSPRO e.Net business objects. Full database access is not given to the model.
- 2
Curated query layer
Parameterized queries and views for the common job costing questions, so the model chooses a tested query and fills parameters instead of writing arbitrary SQL against production.
- 3
Retrieval over documents
Routing notes, work instructions, and costing policies are indexed so the assistant can cite a procedure beside the numbers.
- 4
Model serving
Open-weight model served with vLLM or Ollama on your GPU or in your private cloud. No job data goes to a shared public AI API.
- 5
Controls and audit
Role mapping to SYSPRO operators, logging of every question and query, and approval gates for any proposed correction.
Integration notes for your ERP team
- SYSPRO runs on Microsoft SQL Server, so the simplest read path is a read-only login on approved views. Confirm table and column names against your version before writing queries.
- For anything that should respect SYSPRO's own business logic, use the e.Net business objects or SYSPRO's web services layer instead of direct SQL.
- Operator security in SYSPRO is separate from database logins. Map AI users to SYSPRO operators and role groups so the assistant exposes only what each person is allowed to see.
- Job costing numbers depend on posting discipline. Check that labor and material postings are timely before blaming the AI for a confusing answer.
- Custom form fields and user-defined fields (UDFs) often hold the useful context, such as customer special instructions. Include them in the data map deliberately.
- SYSPRO Reporting Services reports you already trust are good test cases. The assistant should reproduce their numbers before anyone uses a new answer.
Deployment options
On-prem or private server beside the SYSPRO database
Shops that will not let job, customer, or drawing data leave the building, including ITAR and CUI work.
An open-weight model (Qwen, Llama, Mistral, or gpt-oss class) is served with vLLM or Ollama on a single GPU server on the plant network. Retrieval and query tools run on the same box. SYSPRO itself can stay on its current server; only a read path to SQL Server is needed.
Sovereign or private cloud tenant
Multi-site manufacturers that want managed GPUs without sending data to a shared public AI API.
The model and the vector index run in a private cloud account or a regional sovereign provider, reached from the plant over a private link. Data stays in a tenant you control and you choose the region.
Read-only pilot against a replica
Teams that want to prove value on real data before committing hardware or touching production.
A nightly restore or replica of the SYSPRO data feeds a small model and a handful of approved questions. Nothing writes back. Most of the learning is about data quality and which questions people actually ask.
Compliance and data control
How the architecture supports your obligations. Certification and accountability stay with your organisation; the design keeps the evidence straightforward.
ITAR and export-controlled data
Hosting on-prem or in a US-only private tenant lets the customer keep controlled job data inside its own boundary. The customer remains responsible for its registration and controls.
CUI and NIST SP 800-171
Where job data includes CUI, the AI stack is placed inside the same enclave and access controls as SYSPRO, with logging that supports the customer's own assessment.
Financial controls (SOX style review)
Read-only access means the assistant cannot post or alter WIP entries. Any proposed correction is reviewed and entered by an authorized accountant.
Customer data and contract confidentiality
Customer pricing and part data are scoped by role. The model is not trained on your jobs unless you explicitly agree to a fine-tune on your own hardware.
Where Netray fits
How an engagement runs
Phase 1 . 1 to 2 weeks
Discovery and data map
- -Inventory of the SYSPRO tables, views, and reports behind production and job costing
- -Ranked list of 15 to 25 real questions from the people who do the work
- -Decision on hosting, access method, and which roles may see which data
- -Written read-only boundary and approval rules for any later write-back
Phase 2 . 2 to 4 weeks
Grounding and retrieval build
- -Read-only connection with a service account scoped to the approved objects
- -Curated query layer and document index for production and job costing
- -Evaluation set of questions with checked answers from your own data
- -Visible query or source citation on every answer
Phase 3 . 3 to 4 weeks
Pilot with a small group
- -Pilot with 5 to 15 estimators, planners, supervisors, or quality staff
- -Weekly review of wrong or unhelpful answers and fixes
- -Usage log showing which questions were asked and which saved time
Phase 4 . 2 to 3 weeks
Harden and hand over
- -Role mapping, audit logging, and backup of the AI stack
- -Runbook for model updates and index refresh after SYSPRO upgrades
- -Go or no-go note on any gated write-back actions
Questions to ask any vendor, including us
A short list that separates real SYSPRO AI work from a chatbot demo.
- Which SYSPRO version and database do we run, and is the data model for WIP jobs the same across all companies and sites?
- Does the assistant use views, business objects, or raw SQL, and can we see every query it runs?
- How are SYSPRO operator permissions mapped to AI users?
- Can the assistant reproduce an existing job cost report exactly before we use new answers?
- What happens when an upgrade changes a table or business object we depend on?
- Is anything written back to SYSPRO, and who approves it?
- Where is the model hosted and does any job data leave our network?
- How do we measure whether answers are correct on our own jobs?
Frequently asked questions
Does SYSPRO already have AI or analytics for job costing?
SYSPRO offers reporting and analytics tools, and for many plants the standard job cost reports are enough. An AI layer helps when people keep asking one-off questions that need a custom report each time, or when you want a daily exception list rather than a report someone has to open.
Will the AI change our job costs or WIP?
No. The default is read-only. The assistant can point out a suspicious posting or a likely correction, but an authorized user makes the change in SYSPRO. If you later enable a write-back, it goes through business objects with a named approver.
Can it run without sending data to the cloud?
Yes. An open-weight model runs on a GPU server in your plant or private cloud and reads SYSPRO through a scoped read-only path. That keeps job, customer, and pricing data inside your boundary.
How accurate are the answers?
Accuracy comes from grounding. The assistant uses tested queries and cites postings, and we measure it on a set of your own questions with known answers. It can still be wrong where your data is incomplete, so the cited source is always shown.
How long does a pilot take?
A typical pilot is eight to twelve weeks from data mapping to a small group of users, depending on how clean the postings are and how quickly access is approved. A read-only replica makes it faster.
Do we need clean data first?
No, but the assistant will expose problems. Late labor postings or missing operation numbers show up quickly. Many teams treat the first pilot as a data quality review as much as an AI project.
Who should use it?
Production managers, cost accountants, estimators, and shop supervisors. Each sees only what their SYSPRO role allows. Executives usually use the dashboards rather than the question box.
Related guides
AI for SYSPRO, Grounded in Your Own Manufacturing Data
Add AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.
SYSPRO shop floor + AIAI for SYSPRO Manufacturing Operations: From Work Centers to Answers
SYSPRO Manufacturing Operations generates data on work centers, routings, and WIP - see how private AI turns it into shop floor answers on-prem.
SYSPRO + food safety AIAI for SYSPRO in Food and Beverage: Lot Trace, Expiry and Yield Answers Without Leaving Your Network
Private AI on SYSPRO for food and beverage plants: ask lot trace, expiry, FEFO and yield questions in plain English, query shown, on-prem or private cloud.
RFQ-to-quote + on-prem AIAI for quote-to-cash in manufacturing and job shop ERPs
AI reads incoming RFQs, drafts quotes from your ERP's own cost and pricing history, and flags parts your shop has never quoted before, keeping the estimator in control.
Ask your ERP anythingNatural Language Query for ERP Data: Ask SAP, Infor, or Oracle a Question in Plain English
See how natural language query over SAP, Infor, Oracle, and NetSuite data works: grounded text-to-SQL, role-based permissions, and a visible audit trail.
RAG + SQL + permissionsA Private LLM Grounded on Your ERP Data
How a private LLM answers questions on your ERP data: RAG plus text-to-SQL, role-based permissions inherited from the ERP, and where each fits.
Plan it with numbers
On-Prem LLM Total Cost of Ownership Calculator
Model the full multi-year cost of running LLMs on your own hardware, including GPU capex, power, cooling, support contracts, and operations staffing.
Free ToolOpen-Weight Model Selector
A 10-question assessment that matches your hardware budget, workload complexity, and operational maturity to the right open-weight model size class.
Free ToolAS9100 Audit Readiness Checklist
A 30-point checklist for AS9100 Rev D certification and surveillance audits, weighted toward the aerospace-specific requirements where auditors write the most findings.
GuideAI Agents for ERP: The Complete Guide
Everything you need to know about AI agents for ERP systems. How they work, ROI expectations, implementation approaches, and real-world results.
GuideERP Integration Patterns with AI Middleware
Modern ERP integration patterns using AI middleware. Event-driven architecture, API orchestration, and intelligent data synchronization for Infor and Salesforce.
GuideManufacturing AI Readiness Assessment
Assess your manufacturing organization's readiness for AI. Data quality, process maturity, infrastructure, and cultural readiness evaluation framework.
Talk it through with an engineer who knows SYSPRO
Bring one real question your team cannot answer from the ERP today. We will map the data path, the model, and where it runs, and tell you honestly if AI is the wrong tool for it.