ECI M1 + private AI
AI for ECI M1, grounded in your job, quoting, and purchasing data
Short answer
ECI M1 runs make-to-order and mixed-mode manufacturers on job costing, MRP, and shop-floor scheduling, but most shops still answer 'what's my WIP right now' by exporting a report to Excel. A private AI layer grounded on M1's job, quoting, and purchasing data answers those questions directly, drafts quotes from similar past jobs, and flags purchasing exceptions before they hit a job's delivery date, without changing how M1 itself runs.
- ERP
- ECI M1
- Industries
- Metal Fabrication, Machine Shops, Industrial Equipment Manufacturing, Make-to-Order Manufacturing
- Written for
- Owner
M1 shops are usually lean: an owner or general manager, an estimator, a few schedulers, and no dedicated IT or BI staff. That lean structure is exactly what makes M1 a good fit for metal fabrication, machine shops, and make-to-order manufacturers, but it also means nobody has time to build a custom dashboard, and nobody is going to write SQL to answer a quick question about a job's status.
The result is that basic operational questions, what's the WIP total right now, which jobs are behind schedule, which POs are overdue, get answered by opening M1, running a report, and exporting to Excel, over and over, several times a day. It works, but it is slow, and it means the owner or GM is the bottleneck for anything that isn't a canned report.
Estimating is the other pressure point. A new make-to-order quote depends heavily on what a similar job actually cost last time, but that knowledge usually lives in one estimator's head rather than in a searchable system, which makes quoting slower and less consistent than it should be, especially as experienced estimators retire.
None of this needs a new ERP. A private model grounded read-only on the existing M1 database, running on infrastructure the shop controls, can answer job and WIP questions on demand, surface comparable past jobs for quoting, and flag purchasing problems early, all while keeping competitive pricing and job-cost data inside the shop.
What usually gets in the way
The problems we hear most from owner teams running ECI M1.
Job and WIP status requires an export, not a question
Owners and GMs run canned reports and pivot in Excel to answer questions M1 already has the data to answer directly, several times a day.
Quoting depends on one estimator's memory, not searchable history
Pricing a new make-to-order job leans on the estimator recalling a similar past job. That knowledge does not transfer easily, and it walks out the door when the estimator retires.
Multi-shop or multi-division owners can't see a combined view
Shops running more than one M1 instance or division have no easy rollup, so combined numbers get built by hand once a month.
No IT or BI staff to build custom reporting
Typical M1 shops have zero dedicated data or BI headcount, so any question outside the standard report library goes unanswered or waits for a consultant.
Order-status and PO follow-up eats staff time
Customer emails asking 'where's my order' and vendor follow-ups on late POs are handled manually by staff looking things up in M1 one at a time.
Where AI earns its place in ECI M1
Each use case names the ERP objects it reads or writes, so your ERP team can judge the integration effort before anyone commits budget.
Natural-language job and WIP status queries
Owners and schedulers ask directly for WIP by job, jobs behind schedule, or capacity by work center, without opening a report.
Touches: Job/work order records, routing and operation status, work center scheduling data
Outcome: Answers in seconds instead of a daily Excel export routine
Quote-from-history copilot
Searches past jobs with similar materials, routings, and quantities to surface comparable pricing and lead time for a new quote.
Touches: Job costing history, bill of materials/routing, sales order and quote records
Outcome: Faster, more consistent quotes that do not depend on one estimator's memory
Job cost variance explainer
Explains why a job's actual cost is running over estimate, tying the variance to specific operations, material, or labor postings.
Touches: Job costing actuals vs. estimate, labor and material transactions
Outcome: Owners see the real driver of a cost overrun instead of just the total variance
Purchasing exception assistant
Flags POs at risk of arriving late against the jobs that depend on them, and drafts the vendor follow-up email.
Touches: Purchase order records, vendor confirmations, job material requirements
Outcome: Late-material problems surface days earlier, before they threaten a ship date
Customer order-status email drafting
Drafts a plain-language order-status reply from current job and shipping data when a customer emails asking where their order stands.
Touches: Sales order status, job scheduling, shipping records
Outcome: Customer service replies go out in minutes instead of requiring a manual M1 lookup
Inventory and reorder point copilot
Answers stock-level and reorder questions directly and flags items trending toward a stockout against open job demand.
Touches: Inventory on-hand and reorder point data, open job material requirements
Outcome: Fewer surprise material shortages discovered mid-job
Cross-shop consolidation for multi-location owners
Rolls up WIP, backlog, and job cost across multiple M1 instances or divisions into a single answer.
Touches: Job and financial data across multiple M1 environments
Outcome: A same-day combined view instead of a manual month-end rollup
Reference architecture
The model reads from a reporting copy of M1's hosted database, maps job, routing, and quoting vocabulary into plain language, and answers through retrieval and text-to-SQL rather than free-form guessing about job data.
- 1
ERP connectors
Read access to M1's hosted database via a reporting export or replica arranged with ECI, kept separate from the production system.
- 2
Data and semantic layer
Maps job, routing, and quoting terminology into plain business language so questions do not require knowing M1's field names.
- 3
Model serving
An open-weight model served privately, either on shop-owned hardware or in a single-tenant private cloud beside M1's hosted environment.
- 4
Retrieval and agents
Text-to-SQL over job and purchasing data, plus retrieval over past job history for quoting comparisons.
- 5
Governance and audit
Read-only by default, with job-cost and pricing data access limited to the roles that already see it in M1.
Integration notes for your ERP team
- M1 is hosted by ECI as a cloud service, so access typically comes through a reporting export or database connection arranged with ECI rather than a local network tap.
- Field names and customization vary by shop; expect a short mapping pass to translate M1's schema into plain business terms.
- Write-back, such as updating a job note or drafting a PO follow-up, should go through M1's existing UI or supported integration path, not a direct database write.
- Multi-instance or multi-division shops need a federation layer, since each M1 environment is typically its own hosted database.
- ECI continues to add its own reporting and automation features to M1; scope custom AI use cases to genuine gaps rather than duplicating what ships natively.
- Because M1 is multi-tenant hosted, agree explicitly with ECI on the data access path before building, to avoid surprises around export limits or API availability.
Deployment options
Private / sovereign cloud
Shops that want a single-tenant environment beside M1's hosted cloud without owning GPU hardware
Data is synced from M1 into a customer-controlled private tenancy where the model runs, never a shared multi-tenant service.
On-prem
Owners who want the model and job-cost data physically on site, particularly where quoting data is highly competitive
Model runs on shop-owned hardware, with a scheduled sync pulling data from the hosted M1 database.
Hybrid
Multi-location owners wanting local answers per site plus a central rollup
Local inference handles day-to-day questions; a central private tier handles cross-shop consolidation.
Compliance and data control
How the architecture supports your obligations. Certification and accountability stay with your organisation; the design keeps the evidence straightforward.
ITAR / EAR
Fabricators and machine shops touching defense-related parts keep job and drawing data inside a private or on-prem boundary rather than a shared cloud AI service.
CMMC readiness
Shops moving toward DoD subcontract work can point to a controlled, logged AI deployment as part of their broader CMMC posture.
ISO 9001
Read-only access and human review of any drafted communication keep the AI inside existing quality and traceability controls.
Quoting and pricing confidentiality
Keeping job-cost and quoting data inside a private deployment protects competitive pricing information that owners are understandably protective of.
Where Netray fits
ERPray
M1 is not a listed connector today; natural-language question-answering over job and WIP data is built on ERPray's ERP-agnostic connector architecture.
Custom build
Quote-from-history and purchasing-exception agents are specific enough to M1's job costing model to warrant purpose-built retrieval and agent logic.
How an engagement runs
Phase 1 . 2 weeks
Discovery
- -M1 data access path agreed with ECI
- -job and quoting data model review
- -prioritized use-case list
- -hardware/hosting decision
Phase 2 . 6 weeks
Pilot
- -private model stood up
- -connector to M1 reporting data
- -2-3 use cases live (job status, quote-from-history)
- -owner/estimator feedback loop
Phase 3 . 3-4 weeks
Production
- -governance and access logging hardened
- -purchasing exception assistant rolled out
- -staff training
- -role mapping to M1 permissions
Phase 4 . ongoing
Scale
- -additional shops/divisions connected
- -cross-shop rollup agent
- -cost variance and inventory use cases
- -quarterly use-case review
Questions to ask any vendor, including us
A short list that separates real ECI M1 AI work from a chatbot demo.
- What is the actual data access path into our hosted M1 environment, and did ECI sign off on it?
- Does the AI ever write into M1, or is it strictly read-only?
- Can this run fully on our own hardware, or does it require a third-party cloud dependency?
- Who keeps job cost and quoting data confidential from the vendor building this?
- How does it handle multiple M1 instances if we run more than one shop or division?
- Who audits what the AI queried and what answer it gave?
- What happens to the deployment if we later upgrade or change M1 configuration?
Frequently asked questions
Can AI be added to ECI M1 without ECI building it themselves?
Yes. A private AI layer can be built on top of M1's hosted data through a reporting export or database connection, independent of ECI's own product roadmap. It requires agreeing a data access path with ECI, but the AI itself is deployed and controlled separately.
What is the fastest AI win for an M1 shop?
Natural-language job and WIP status queries are usually fastest to stand up, since that data is already well structured in M1. Most shops see a working pilot within six weeks, answering questions that previously required a report export.
Can AI help with quoting in M1?
Yes. By indexing past job costing, routing, and quote history, a private model can surface comparable past jobs when a new quote is being built, giving estimators a consistent starting point instead of relying purely on memory.
Is this safe for a shop working on defense-related parts?
Yes, when deployed on-prem or in a private single-tenant environment with no data sent to a shared external service. That keeps job, drawing, and pricing data inside the same boundary ITAR and CMMC-conscious shops already maintain for the rest of their systems.
Does M1 have a native AI feature already?
ECI has been adding automation and reporting improvements across its product lines, but a broad natural-language AI layer grounded on job, quoting, and purchasing data is not a standard out-of-the-box M1 feature as of this writing, which is why shops add a private layer.
How does this work if we run more than one M1 instance?
A federation layer sits above each M1 environment's data connection, so a single question, such as combined WIP across two shops, can be answered without manually merging spreadsheets from each instance.
What does it cost to add AI to an M1 environment?
For a single-shop pilot covering two or three use cases, expect a cost in line with a focused mid-size integration project. Multi-shop rollups and deeper quoting-history retrieval add to that as scope grows.
Related guides
Natural 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.
Agents + approval gatesAI Agents for ERP, Running On-Prem
A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.
ERP AI Buyer GuideHow to Choose an ERP AI Implementation Partner
A CIO checklist for picking an ERP AI implementation partner: the architecture questions to ask, red flags, pricing models, and what to demand in the SOW.
ERP AI Cost GuideWhat ERP AI Actually Costs: A CFO's Guide
A CFO's guide to what ERP AI actually costs: GPU hardware, model licensing, integration and connector work, and realistic ongoing run-rate ranges.
QAD + on-prem AIAI for QAD Adaptive ERP in automotive and industrial manufacturing
Add AI to QAD Adaptive ERP or Enterprise Edition for automotive and industrial manufacturing, grounded on QXtend and QAD's API layer, on-prem or private cloud.
Plan it with numbers
Job Shop ERP Fit Assessment
Score how well your ERP handles high-mix, low-volume and make-to-order manufacturing across quoting, one-off routings, WIP visibility, subcontract tracking, and job-level cost variance.
Free ToolERP AI Maturity Assessment
Benchmark how deeply AI and automation are embedded in your ERP operations, from data foundations to autonomous agents, across four maturity levels.
Free ToolManufacturing AI Readiness Assessment
Score your manufacturing operation's readiness for AI across data, systems, people, and governance, and get a prioritized roadmap for closing the gaps.
GuideERP RFP Template for Discrete Manufacturers
A complete ERP RFP template for discrete manufacturing: requirements matrix, CMMC and ITAR questions, weighted scoring model, and vendor demo scripts.
GuideAI-Powered Demand Forecasting for Manufacturing
Improve manufacturing demand forecasts by 30-50% with AI. Combine ERP history, external signals, and ensemble ML models for accurate production planning.
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.
Talk it through with an engineer who knows ECI M1
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.