IQMS / DELMIAworks data: exports, history and licensing

What DELMIAworks data can a molder export and license?#

A plastics molder running DELMIAworks, the ERP many molders still call IQMS, can typically export production, quality, scheduling and maintenance history, then consider licensing the parts that record its own decisions: downtime and scrap reasons, schedule changes, inspection outcomes and mold maintenance. Customer part designs stay out.

Molders often keep the same system through many upgrades, so the history can be deep: cycle times and shot counts from presses, inspection results, work order schedules and preventive maintenance on molds and machines. Which modules hold that history depends on what your plant licensed and actually turned on.

The moment to look is usually an upgrade, a hosting change, a sale of the business or a plant consolidation. Each can trigger purges or leave older history behind in a database nobody plans to open again.

Module value table for molders#

The module value table rates the main areas of a molder's DELMIAworks installation by what each record family can teach an AI developer. The ratings are qualitative starting points; real value is judged per package and is known only once a buyer engages.

Linkage lifts every row. A downtime event that joins to the mold in the press, the work order being run and the scrap reported on that shift says far more than the same event on its own, because it ties a stop to its cause and its cost.

How to export DELMIAworks history#

Exporting DELMIAworks history works best as a set of keyed extracts, one per record family, rather than a stack of reports. Work order, mold, press, item and lot numbers must survive in every file so production, quality and maintenance records can be joined later.

Hosted deployments depend on the provider's export options and your agreement. Request the scope, format and any fees in writing, and confirm how long you keep access after notice, before relying on a hosted export for an upgrade or exit.

• 1Confirm which modules the plant used, and from when, before scoping anything.
• 2For on-premises systems, take a full database backup first, then build extracts from a copy rather than the live system.
• 3Pull process monitoring history separately; it is often the largest data set and may have been summarized or purged on a schedule.
• 4Export downtime and scrap reason code lists with their descriptions and any changes over time.
• 5Export mold records with their maintenance history, keyed by mold number.
• 6Write down every custom field, report and reason code your plant added.

Customer molds, part designs and process settings#

Customer molds and part designs raise the main rights question for molders, because many molds are customer-owned tooling and the part geometry is the customer's design. A license can cover how the molder ran a mold, such as cycle times, scrap and maintenance, while excluding part drawings, CAD files and the customer's specifications.

Process settings deserve care. A molder's setup sheets reflect its own know-how, but some supply and tooling agreements treat process parameters for a customer's parts as that customer's confidential information, so counsel reads those agreements before process data is included.

Illustrative: a custom molder snapshots history before an upgrade#

Illustrative: Pinebrook Molding is a fictional custom injection molder serving appliance, industrial and consumer product customers. It has run the system since it was branded IQMS, with press monitoring on the floor, inspections recorded in the quality module and mold maintenance tracked by mold number.

Before a major upgrade, the IT director took a full backup and extracted process monitoring summaries, scrap and downtime events, work order schedules, nonconformances and mold maintenance, all keyed by work order and mold. Reason codes had changed several times over the years, so the team built a mapping table from old codes to current ones.

Customer-owned molds were flagged from the tooling records, and part drawings were excluded from the start. The archive supported the upgrade's data checks and became the basis for a metadata-only fit check on the plant's own operating records.

What lowers the value of molding records#

Molding records lose value when reasons are missing or inconsistent. A downtime log where most stops are coded as other, or a scrap log with no reason at all, shows that problems happened but not why.

Other frequent problems include reason code lists changed without a mapping, process monitoring data purged to save space, mold numbers reused for different tools and work orders closed without scrap reporting. Each can be documented, and some can be partly repaired by mapping old codes to new ones.

Records also lose value when they cannot be separated from customer identity. Masking a customer name is simple; masking a part that only one customer makes needs a coarser product description, such as a product category and resin family.

How SourceX approaches DELMIAworks history#

SourceX approaches DELMIAworks history through the SourceX five-step transaction. The fit check collects metadata only: modules in use, years of history, plants, approximate record volumes and known customer restrictions, with no extracts requested at that stage.

Rights review covers tooling and supply agreements, Preparation removes customer identifiers and employee names, and the molder approves the final manifest and the release. The SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and the release authorization. The records are licensed, not sold outright, and the molder keeps ownership.