# Engineering change metadata packet template | SourceX

Canonical: https://refer.sourcex.si/resources/engineering-change-to-effectivity-metadata-packet
Last updated: 2026-11-04

A referral partner can collect everything needed to describe engineering change records without reading any of them: the systems involved, the object types each holds, the years covered, volumes in ranges, which identifiers link one system to the next, who owns each system and link, known gaps, unknowns and rights flags. Drawings, BOMs, part numbers, customer names, screenshots and exports never go into the packet.

This template is part of the guide on [engineering change order process records](/data-types/engineering-change-order-process). Fill it in during one conversation with the company's engineering operations head, then attach it to your introduction.

## What goes in the packet and what never does

The rule is simple: describe the container, never the contents. A field passes if it would still be safe to read aloud in a meeting with a competitor of the company.

| Allowed in the packet | Never in the packet |
|---|---|
| System names, such as Jira, PTC Windchill, the ERP | Logins, URLs, database names or exports |
| Record types, such as change requests and notices | Any actual change request or notice |
| Year ranges and approximate counts | Part numbers, drawing numbers, serials |
| Which key links two systems | Example key values from real records |
| Role titles of owners | Customer names or program names |
| Rights flags, such as "customer-owned designs exist" | The customer agreements themselves |

Rights flags deserve a note. Under the ITAR, technical data includes information required for the design, production, manufacture, repair, testing or modification of defense articles, including drawings, plans and instructions. A partner does not decide whether any record is export-controlled. Writing "possible defense programs, counsel to confirm" is enough.

## The packet, field by field

Copy this table. The middle column says how to get each answer without anyone opening a record.

| Field | What to write | How to get it at metadata level | Usually supplied by |
|---|---|---|---|
| 1. Systems | Tool name per stage: requirements, change, BOM, orders, quality | Ask which tool each team works in | Engineering systems lead |
| 2. Object types | Requirements, design reviews, change requests, notices, tasks, BOM versions, orders, rework orders | Ask which object types exist, not their fields' values | Engineering systems lead |
| 3. Date ranges | Go-live year per system; what came before | Ask when each tool was introduced | Document control |
| 4. Volumes | Ranges, such as "low thousands of notices" | Ask for an order of magnitude from a report count | Engineering operations head |
| 5. Linking keys | Which identifier joins each pair of systems, and whether it is typed or system-generated | Ask how a change is traced from requirement to order | Engineering systems lead |
| 6. Owners | Role title per system and per link | Ask who approves access to each system | Engineering operations head |
| 7. Known gaps | Periods or links that are missing or manual | Ask where traces usually fail | IT integration lead |
| 8. Unknowns | Questions nobody could answer yet | Note what was left open | Partner, from the conversation |
| 9. Rights flags | Customer-owned designs, defense programs, supplier drawings | Ask whether such programs exist, not which | Company counsel |
| 10. Sponsor | Executive who can authorize a licensing discussion | Ask who signs data agreements | Engineering operations head |

PTC documents that Windchill change management runs from optional problem reports through change requests and change notices to change tasks, which gives a ready list for field 2 when the company uses that tool. Atlassian documents that Jira Cloud exports run up to 10,000 work items at a time, which is useful context for field 4: a company with a very large tracker will know its history comes out in batches. Neither fact needs anyone to open a record.

## Illustrative filled packet: a 300-person control panel builder

Invented for this page. A builder of industrial control panels and motor control centers, with engineering in one plant and assembly in two.

| Field | Illustrative entry |
|---|---|
| 1. Systems | Jira for customer requirements; Windchill for change and effectivity; ERP for BOMs and orders; a separate quality database |
| 2. Object types | Requirements, design reviews, change requests, change notices, change tasks, BOM versions, production orders, nonconformance reports |
| 3. Date ranges | Jira since 2017; Windchill since 2019; ERP since 2012; changes before 2019 as scanned forms on a file share |
| 4. Volumes | Change notices in the low thousands; production orders in the tens of thousands; requirements in the high thousands |
| 5. Linking keys | Requirement key typed into the change request since 2021; change number carried to the ERP by interface since 2022, by hand before |
| 6. Owners | Engineering owns Jira and Windchill; IT owns the interface; operations owns the ERP; quality owns nonconformance records |
| 7. Known gaps | 2019 to 2022: ERP effectivity keyed by hand, often days late |
| 8. Unknowns | Whether closed orders keep the BOM version used; whether nonconformance reports cite change numbers |
| 9. Rights flags | Some panels built to customer designs; a few utility and defense-adjacent programs; counsel to confirm |
| 10. Sponsor | COO; engineering operations head as working contact |

Notice what the packet tells SourceX without a single record: roughly four years of joinable history, an earlier stretch with a manual link, two open questions and a rights review that will need counsel. That is enough to start a conversation.

## Three fields partners most often get wrong

- **Volumes as exact numbers.** "2,847 notices" suggests someone ran a query for you. Use a range.
- **Linking keys with example values.** "Keys look like CR-0457" is a record fragment. Write "change request number, system-generated".
- **Owners as names.** Use role titles until the company chooses to make an introduction.

For a broader inventory across all systems, see [how to prepare a metadata-only inventory of business systems](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems) and the [Jira metadata inventory template](/resources/a-metadata-only-jira-inventory-template-for-company-introductions). To test whether the history is complete enough to discuss, run the [completeness checklist](/resources/engineering-change-to-effectivity-completeness-checklist); to understand fields 5 and 7, read the [record chain](/guides/engineering-change-to-effectivity-record-linkage).

## Handing the packet over

Send the packet to the sponsor with a two-line note, and let the sponsor decide whether to apply. Before you submit any introduction you must sign the Channel Partner Agreement. The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. What stays unknown until SourceX reviews it: the rights result, buyer interest and any offer. The [engineering and design screening worksheet](/resources/a-referral-screening-worksheet-for-engineering-and-design-businesses) covers size and rights screening in more depth.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If you can fill in most of the ten fields for a manufacturer in one conversation, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before sending the packet with your introduction.

## Sources

- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/CCMOviewChangeMgmtIntro.html
- https://www.ecfr.gov/current/title-22/chapter-I/subchapter-M/part-120/subpart-C/section-120.33
- https://support.atlassian.com/jira/kb/export-over-10-000-work-items-in-jira-cloud/
- https://refer.sourcex.si/terms
