Manufacturing
Can I license Epicor Kinetic data to AI companies?
By SourceX Editorial · Updated
Short answer
Yes, a manufacturer can usually license the records it keeps in Epicor Kinetic to AI developers, provided it controls those records, carves out customer-owned designs and export-controlled jobs, and approves each release. The value sits in linked chains, where a quote connects to the job, the quality decision and the field service outcome, not in isolated tables.
Key takeaways
- Business records you enter into Epicor Kinetic are generally yours, but your Epicor agreement governs how you access and export them.
- Quote, job, quality and field service records are most useful when they link to one another through order, job and part references.
- Customer drawings, export-controlled jobs, employee details and confidential pricing come out before any package is scoped.
- Closed history left in an older Epicor database after an upgrade can be the deepest part of the archive, so back it up before the server is retired.
- A first fit check needs metadata only: modules in use, years of history, deployment model and known restrictions.
Who controls the records inside Epicor Kinetic?#
A manufacturer generally controls the business records it creates in Epicor Kinetic, such as quotes, jobs, inspection results and service calls, while Epicor licenses the software that stores them. That split matters because the real question is not whether Epicor owns your data but whether your agreements let you extract it and let someone else use it.
Three sets of documents shape the answer. Your Epicor license or cloud subscription terms set the rules for access and export, and may limit bulk or automated extraction. Your customer contracts and quality agreements may restrict how you use customer part numbers, specifications and drawings. Your employee notices and policies decide how operator and inspector names can be handled.
Read those documents before anyone runs an export. A short memo listing each restriction, and the record families it touches, becomes the starting point for a rights review instead of a hurdle discovered late.
Which Kinetic modules hold the most useful records?#
The Kinetic areas that hold the most useful records are quoting, job management, quality and field service, because together they show how the business turns a request into a part and how it handles what goes wrong. General ledger postings and master files add context but rarely carry decisions on their own.
| Kinetic area | What it records | Why AI developers care | Watch for |
|---|---|---|---|
| Quote | Quote lines, quantity breaks, estimated operations and materials, revisions, won or lost status | Shows how estimators price risk and trade off lead time, material and setup | Customer pricing under confidentiality terms |
| Job | Job operations, labor and machine time, material issues, scrap, rework jobs | Connects the plan to what actually happened on the floor | Operator names in labor entries |
| Quality | Inspection results, nonconformances, material review dispositions such as rework, scrap or return to supplier, corrective actions | Captures diagnosis and decisions when parts fail to conform | Customer part references and attached drawings |
| Field Service | Service calls, equipment serial numbers, service contracts and warranty status, technician comments | Links problems in the field back to how parts were built | Customer site contacts and addresses |
| Returns (RMA) | Return authorizations, inspection of returned parts, credit or replacement decisions | Shows which shipped parts came back and how the company responded | Customer contacts and credit terms |
| Engineering | Bill of materials and routing revisions, engineering changes | Explains why designs and processes changed | Customer-owned designs and export-controlled data |
What does a linked Kinetic record chain look like?#
A linked Kinetic record chain follows one piece of work from the quote through the sales order, the job, any nonconformance and corrective action, and finally the service call or return. Each step carries a reference to the one before it, so an extract can rebuild the full story instead of a pile of disconnected rows.
Free-text fields hold much of the reasoning. Quote comments explain assumptions, job notes record setup problems, nonconformance descriptions say what was wrong and why, and service call comments say what the technician found. Most companies also add user-defined fields over the years, and each one needs a line in a data dictionary so a buyer knows what it means.
- Do quote numbers carry through to sales orders and jobs, or were orders often keyed in fresh?
- Do nonconformances reference the job and part revision they came from?
- Do corrective actions point back to the nonconformances that triggered them?
- Do service calls and returns reference the original order or serial number?
- Are free-text comments used consistently, or only by a few people?
What should be carved out before anything is exported?#
The carve-out list for an Epicor Kinetic package starts with anything the company does not control or should not share: customer designs, export-controlled work, personal details and confidential commercial terms. Removing them is part of scoping, not a cleanup step once files exist.
Customer names and part numbers often stay in coded form, so the links between quotes, jobs and nonconformances survive while the identities do not. Whether coding is enough depends on the wording of each customer contract, which is why the rights review comes before preparation rather than after it.
- Customer-supplied drawings, CAD models and specifications stored as attachments or in linked document folders.
- Jobs, parts and quotes for export-controlled programs, removed in full rather than redacted.
- Employee names and IDs in labor entries, inspection records and approvals, replaced with role codes.
- Customer contacts, addresses and email threads attached to quotes or service calls.
- Price lists and terms that a customer or supplier agreement treats as confidential.
- Payroll, HR and banking records, which have no place in an operational package.
How do older Epicor versions affect the history you have?#
Older Epicor versions can hold the deepest history. Some manufacturers that moved to Kinetic from Vantage, Vista or Epicor 9 (E9) converted only open orders, master data and a short window of history, so closed jobs, old quotes and past nonconformances may still sit in a legacy database on a server nobody has switched off yet.
Treat that legacy database as an asset to inventory before it is retired. Record the version, the date range it covers and whether it can still be opened. If an upgrade, a move from on-premises to cloud deployment or a hardware refresh is planned, take a full backup and test that it restores; once a server is wiped, the history is usually gone for good.
Who does the work inside the company?#
A Kinetic review needs a small group rather than a project team: the Epicor administrator or IT lead, the quality manager, the controller and counsel, with the CEO deciding scope. Most early effort goes into answering metadata questions and reading contracts; extraction starts only once a package is scoped.
For a CFO weighing staff time, the useful split is between questions people can answer from memory and work that needs system access. The first group comes first and takes little time. The second waits until the company has decided a package is worth pursuing.
| Role | What they answer | Stage |
|---|---|---|
| Epicor administrator or IT lead | Modules in use, version history, cloud or on premises, custom fields, export route | Fit check |
| Quality manager | Whether nonconformances and corrective actions reference jobs and part revisions | Fit check |
| Controller or CFO | Confidential pricing, customer and lender terms, internal effort budget | Rights review |
| Counsel | Epicor agreement, customer contracts, export-controlled programs | Rights review |
| CEO or owner | Final scope and the decision to release | Approval |
Illustrative: a hydraulic cylinder maker reviews its Kinetic history#
Illustrative: a fictional maker of hydraulic cylinders and power units runs Kinetic as a cloud subscription and still keeps an Epicor 9 database on an on-premises server due for retirement. The CEO wants to know whether the records deserve a closer look, and the CFO wants to know what the effort would involve before committing staff time.
The team finds that quotes convert to sales orders and jobs inside the system, nonconformances reference jobs and part revisions, and field service calls tie back to serial numbers. One block of jobs for a defense customer is export-controlled, and several equipment customers supply their own drawings under confidentiality terms.
The company scopes quote-to-job and nonconformance history for its catalog cylinders, excludes the defense jobs and every customer drawing, and replaces operator names with role codes. For the cloud system, IT confirms the export route against the subscription terms. For the old server, it takes a full backup and test-restores it, so the closed Epicor 9 jobs remain available for a later review.
How SourceX approaches an Epicor Kinetic review#
SourceX starts an Epicor Kinetic review with a metadata-only fit check: which Kinetic modules are in use, how far back quote, job and quality history reaches in Kinetic and in any legacy Epicor database, whether the system runs in the cloud or on premises, and which customers or programs carry restrictions. No tables, extracts or files change hands at that stage.
The work then follows the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Module chains are weighed with the SourceX Enterprise Data Value Framework, so a quote-to-job-to-nonconformance chain ranks above isolated master files. Each approved package carries a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization. Large extracts stay on the manufacturer's servers or ship on encrypted drives, and the company licenses use of the records while keeping ownership.
Frequently asked questions
Do we need Epicor's permission to license our Kinetic records?
Usually the records are yours, but read your Epicor license or cloud subscription terms for limits on extraction, third-party access and use of vendor-supplied content. Those terms shape the export route more than the ownership question. If a clause is unclear, counsel reviews it before a package is scoped.
Does it matter whether we run Kinetic in the cloud or on premises?
It changes the export route more than the answer. On premises, IT can often extract from a restored database copy. In a cloud deployment you rely on the export tools, APIs and limits in your plan, so check the vendor's documentation before estimating the effort.
Will an AI developer want our raw Epicor tables?
Rarely. Buyers want a documented extract: the tables that matter, the keys that join them, a data dictionary for custom fields and a note on what was removed. Raw tables full of system columns and unexplained user-defined fields add work without adding meaning.
Can exporting data slow down our production system?
Large queries against a live ERP can affect performance during working hours. Extracting from a restored copy or a test environment avoids that, and it keeps the production system untouched while the scope is still being decided.
Can a buyer ask for exclusive rights to our Kinetic history?
A buyer can ask, and exclusivity is a negotiated term. It narrows your future options, so weigh it against the scope, field of use and term of the license. Without exclusivity, the same Kinetic history can be licensed again to other developers.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.