PLC and HMI source with change history, packaging machinery maker

Summary

Controls source from one maker of case packers, tray formers and palletizers: structured text, ladder logic exported as text, HMI screen and alarm definitions and servo motion profiles, with the full commit history and the Jira issues behind each change. Fixes made during customer startups are tagged, so models see how machine logic changes when it meets a real line. Customer names, site network details and license keys are removed, and vendor library blocks under third-party license are left out.

Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.

Pricing on request

Request scope and pricing

At a glance

Planned scope. Volume, sources and timing are confirmed in writing before you sign.

Records: 156Ksource files, commits, issues and wiki pages
Size: 5 GB
Tokens, estimated: 1.2B
Years: 2014 to 2026
Firms: 1

Owner profile: One US packaging machinery manufacturer, 50 to 150 staff
Industry: Manufacturing
Data type: Code and engineering
Headcount: 50 to 150 staff
Region: United States
Languages: English
Formats: Source tree, JSONL
Updated: 2026-10-11

Sources

System	Kind	Records
GitLab	Code	48 repositories, 92K files, 31K commits
Jira	Projects and wiki	27K issues
Confluence	Projects and wiki	6.4K pages of FAT, SAT and commissioning notes

Good for

training code models on IEC 61131-3 structured text and ladder logic with real change history
evaluating fault diagnosis from alarm text, logic and commissioning notes
generating HMI alarm and screen definitions from a machine specification
reviewing PLC diffs for interlock and sequencing regressions

Fields

Field	Type	Description
repo	string	Repository name
path	string	File path in the source tree
language	enum	structured text, ladder export, HMI definition, motion profile or C#
machine_family	enum	case packer, tray former or palletizer
commit	string	Commit hash
committed_at	timestamp	Commit time
author_code	string	Placeholder for the engineer
message	string	Commit message
issue_keys	array<string>	Linked Jira issues
changed_symbols	array<string>	Function blocks, tags and variables touched
lines_added	int	Lines added in this file
lines_removed	int	Lines removed in this file

Example record

{
  "repo": "case-packer-std",
  "path": "Logic/Infeed/FB_InfeedJamDetect.st",
  "language": "structured text",
  "machine_family": "case packer",
  "commit": "a41f9c2e",
  "committed_at": "2023-05-16T21:07:44-05:00",
  "author_code": "[PERSON_15]",
  "message": "Infeed jam detect: debounce PE3 and ignore gaps under 40 ms while indexing. Field fix from [SITE_9] startup, false jams on shrink-wrapped trays.",
  "issue_keys": [
    "CP-2291"
  ],
  "changed_symbols": [
    "FB_InfeedJamDetect.tGap",
    "FB_InfeedJamDetect.bJam",
    "GVL_Infeed.tJamDebounce"
  ],
  "lines_added": 14,
  "lines_removed": 5
}

One record, de-identified. Placeholders such as [PERSON_12] and [COMPANY_4] stay the same across the whole dataset, so threads still read correctly.

Licenses available

Exclusive
One buyer. Nobody else can license it during the exclusive term, usually 2 years.
Non-exclusive
Licensed to more than one buyer.
First look
One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.

What ships with it

Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
Manifest with a hash for every file.
QC report and de-identification report.
Your own copy, with unique canary records.

How it is de-identified

Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.

The full method