Engineering change to effectivity metadata packet: a fill-in template for introductions

Short answer

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.

Visual briefFull-size diagram
A packet card fills in eight fields, systems, object types, date ranges, volumes, linking keys, owners, gaps and rights flags, while a stack of raw records beside it stays closed under a lock.
Illustrative packet. Every field describes the records; none of them contains one.

This template is part of the guide on engineering change order process records. 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 packetNever in the packet
System names, such as Jira, PTC Windchill, the ERPLogins, URLs, database names or exports
Record types, such as change requests and noticesAny actual change request or notice
Year ranges and approximate countsPart numbers, drawing numbers, serials
Which key links two systemsExample key values from real records
Role titles of ownersCustomer 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.

FieldWhat to writeHow to get it at metadata levelUsually supplied by
1. SystemsTool name per stage: requirements, change, BOM, orders, qualityAsk which tool each team works inEngineering systems lead
2. Object typesRequirements, design reviews, change requests, notices, tasks, BOM versions, orders, rework ordersAsk which object types exist, not their fields' valuesEngineering systems lead
3. Date rangesGo-live year per system; what came beforeAsk when each tool was introducedDocument control
4. VolumesRanges, such as "low thousands of notices"Ask for an order of magnitude from a report countEngineering operations head
5. Linking keysWhich identifier joins each pair of systems, and whether it is typed or system-generatedAsk how a change is traced from requirement to orderEngineering systems lead
6. OwnersRole title per system and per linkAsk who approves access to each systemEngineering operations head
7. Known gapsPeriods or links that are missing or manualAsk where traces usually failIT integration lead
8. UnknownsQuestions nobody could answer yetNote what was left openPartner, from the conversation
9. Rights flagsCustomer-owned designs, defense programs, supplier drawingsAsk whether such programs exist, not whichCompany counsel
10. SponsorExecutive who can authorize a licensing discussionAsk who signs data agreementsEngineering 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.

FieldIllustrative entry
1. SystemsJira for customer requirements; Windchill for change and effectivity; ERP for BOMs and orders; a separate quality database
2. Object typesRequirements, design reviews, change requests, change notices, change tasks, BOM versions, production orders, nonconformance reports
3. Date rangesJira since 2017; Windchill since 2019; ERP since 2012; changes before 2019 as scanned forms on a file share
4. VolumesChange notices in the low thousands; production orders in the tens of thousands; requirements in the high thousands
5. Linking keysRequirement key typed into the change request since 2021; change number carried to the ERP by interface since 2022, by hand before
6. OwnersEngineering owns Jira and Windchill; IT owns the interface; operations owns the ERP; quality owns nonconformance records
7. Known gaps2019 to 2022: ERP effectivity keyed by hand, often days late
8. UnknownsWhether closed orders keep the BOM version used; whether nonconformance reports cite change numbers
9. Rights flagsSome panels built to customer designs; a few utility and defense-adjacent programs; counsel to confirm
10. SponsorCOO; 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 and the Jira metadata inventory template. To test whether the history is complete enough to discuss, run the completeness checklist; to understand fields 5 and 7, read the record chain.

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 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, check the company against who qualifies, and read the program terms before sending the packet with your introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the packet include a sample change notice to show what the records look like?

No. Even one notice can contain part numbers, drawings or customer names. Describe the record type and its fields in words instead.

What if the company cannot give counts?

Write a range or 'unknown'. An honest unknown is more useful than a precise guess, and SourceX confirms volumes with the company later.

Who should fill in the packet?

The company's own people, with the partner asking the questions. The partner writes down answers; it does not query systems.

Sources

  1. support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_…
  2. ecfr.gov/current/title-22/chapter-I/subchapter-M/part…
  3. support.atlassian.com/jira/kb/export-over-10-000-work-items-in-jir…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment