Who can authorize licensing engineering change records? A who-can-say-yes tree for PLM integrators

Short answer

Introduce the person who can authorize a licensing discussion, the CEO (in an owner-run manufacturer, usually the owner), with the head of engineering operations as sponsor and working contact. The engineering operations head runs the change process and knows where every record lives. The systems lead and change analysts can describe the records but cannot approve their use. Counsel must weigh customer designs, supplier drawings and export controls. What can be licensed stays unknown until SourceX's rights review.

Visual briefFull-size diagram
A left-to-right approval tree: from the change records, a branch to the systems lead ends at describe only, a branch to counsel checks customer designs and export controls, and the lit path runs through the engineering operations head to the CEO or owner who can authorize the discussion.
The path from record owner to authorized signer. Job titles below the CEO differ between manufacturers; the CEO authorizes.

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 setWho keeps it day to dayWhat they can tell youAuthority to license?
Requirements and design reviews in JiraApplications or systems engineeringProjects, years, whether issue keys reach change requestsNo
Change requests, notices and tasks in WindchillChange analyst, configuration managerVolumes, tracks used, board practiceNo
PLM-to-ERP integrationIT or engineering systems leadHow changes and effectivity reach the ERPNo; administrator rights are not authority
BOM versions and production orders in the ERPManufacturing engineering, planningWhether orders keep the BOM version usedNo
The change process as a wholeHead of engineering operationsWhere every link lives, and the gapsSponsor; rarely the final decider
Company records as an assetCEO or ownerWhether the company will discuss licensing at allYes

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.

  1. Does this person administer a system? If yes, they describe the records. Ask them who runs the process, and move on.
  2. 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.
  3. 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.
  4. 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.

SituationWhy it mattersWho decidesTypical outcome
Customer-specified or customer-owned designsThe customer contract may own or restrict the design and its changesCompany counselExcluded, or included only with consent
Supplier drawings attached to changesThe supplier usually authored themCompany counselUsually excluded
Export-controlled programsRelease of controlled technology can require a licenseTrade compliance and counselExcluded
Defense or regulated programsContracts may add handling termsCounsel and contractsUsually excluded
Open warranty claims or disputesRecords may be on holdCounselLeft 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.

  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

The engineering operations head is enthusiastic. Is that enough?

It is a good start, not a decision. Ask them to bring in the CEO, who signs agreements that involve company information, and introduce the CEO with the engineering operations head as sponsor.

Should a partner check whether parts are export-controlled?

No. Classification is the company's job, done by its trade compliance team or counsel. A partner only notes that the company has controlled programs, if the company says so, so the review can plan around them.

What happens if the company is owned by a private equity fund?

Note it. The CEO may still decide, but some funds require consent for agreements involving company data. SourceX asks about ownership during its review.

Sources

  1. bis.gov/learn-support/deemed-exports/what-deemed-export
  2. support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_…
  3. copyright.gov/circs/circ41.pdf
  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