This decision tree is part of engineering change order process records. It answers one question for PLM integrators and other partners: who can say yes.
Start at the records: who owns each part
Engineering change history is spread across systems, and each has a different keeper. None of them is the decider by virtue of the system they run.
| Record set | Who keeps it day to day | What they can tell you | Authority to license? |
|---|---|---|---|
| Requirements and design reviews in Jira | Applications or systems engineering | Projects, years, whether issue keys reach change requests | No |
| Change requests, notices and tasks in Windchill | Change analyst, configuration manager | Volumes, tracks used, board practice | No |
| PLM-to-ERP integration | IT or engineering systems lead | How changes and effectivity reach the ERP | No; administrator rights are not authority |
| BOM versions and production orders in the ERP | Manufacturing engineering, planning | Whether orders keep the BOM version used | No |
| The change process as a whole | Head of engineering operations | Where every link lives, and the gaps | Sponsor; rarely the final decider |
| Company records as an asset | CEO or owner | Whether the company will discuss licensing at all | Yes |
PTC documents that complex changes in Windchill take a full track through a change review board. Board members approve engineering changes. That is a different authority from approving the use of change records in a data agreement, and it is easy to confuse the two.
Who can authorize a licensing discussion: the yes path
Work through four questions in order. Stop at the first "yes" in question 3.
- Does this person administer a system? If yes, they describe the records. Ask them who runs the process, and move on.
- Does this person run the change process across products? If yes, this is usually the head of engineering operations. Ask them to sponsor the conversation and to bring in the CEO.
- Can this person commit company information to an agreement? If yes, this is your introduction: the CEO, or the owner where the owner runs the company.
- Does anyone above them need to consent? A parent company, a board or a private equity owner may. Note it; SourceX will ask.
The tree is short on purpose. The common mistake is stopping at question 1 or 2 because that person is helpful and knowledgeable.
The counsel branch: customer designs, supplier drawings and export controls
Some change records carry other parties' rights or legal restrictions. A partner flags these and stops. Counsel and SourceX's rights review decide.
| Situation | Why it matters | Who decides | Typical outcome |
|---|---|---|---|
| Customer-specified or customer-owned designs | The customer contract may own or restrict the design and its changes | Company counsel | Excluded, or included only with consent |
| Supplier drawings attached to changes | The supplier usually authored them | Company counsel | Usually excluded |
| Export-controlled programs | Release of controlled technology can require a license | Trade compliance and counsel | Excluded |
| Defense or regulated programs | Contracts may add handling terms | Counsel and contracts | Usually excluded |
| Open warranty claims or disputes | Records may be on hold | Counsel | Left alone |
Two public rules explain why. The U.S. Bureau of Industry and Security explains that releasing controlled technology or source code to a foreign person in the United States is a "deemed export" to that person's most recent country of citizenship or permanent residency and may need a license. Engineering change records can contain that kind of technical data, so controlled programs stay out unless counsel says otherwise. Separately, the U.S. Copyright Office notes that technical drawings are protected as drawings, so drawings from suppliers or customers are not the manufacturer's to license by default. Why data rights matter explains how these checks shape what is licensable, and contract review workflows covers how companies track the agreements that carry these terms.
What stays unknown until SourceX's rights review
Even after the CEO agrees to talk, four things remain open:
- Rights: which record classes the company can license, given its customer and supplier agreements.
- Scope: which products, programs and years are included.
- Demand: whether any buyer wants this data when SourceX reviews it. Programs can change; see what happens if a SourceX pauses data sourcing.
- Terms: any offer, payout and schedule.
A partner predicts none of these. The system map and the worked exception case help a partner describe the records accurately without promising anything about them.
The company baseline and the partner's paperwork
The manufacturer needs 50+ full-time employees at peak (contractors excluded), 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. Partners sign the Channel Partner Agreement before submitting introductions. Credit goes to the first valid introduction within the 90-day window, recorded when the company submits a verified application, and one partner is credited per company. More manufacturing context is in the industries hub.
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.
When the head of engineering operations has agreed to bring in the CEO, who can say yes, and flagged any controlled programs, register as a partner, confirm the company on who qualifies and read the program terms before making the introduction.