Who can say yes to licensing production schedule recovery records? A decision tree for partners

Short answer

Introduce the CEO, who can authorize a licensing discussion, with the plant operations director as working contact. Start the conversation with the operations director, who knows how recoveries are decided and where each record is kept, and let them bring in the CEO. System administrators, planners and maintenance managers own records day to day but cannot approve their use. Customer agreements, a parent group and employee data can each add a required sign-off, and SourceX's rights review settles what remains open.

Visual briefFull-size diagram
An approval tree starts at the record owners, MES administrator, planning manager and maintenance manager, rises to the plant operations director, branches to counsel review for customer, group and export questions, and lights a path to the CEO as the authorized signer.
The highlighted path is the usual route; the side branches stay open until SourceX's rights review.

This decision tree is part of the guide on production schedule change logs. The worked hard case shows which records a recovery leaves; this page shows who can say yes to discussing them.

Who holds which records

Recovery records are spread across roles. Each holder can describe their part, and none of them alone can approve a licensing discussion.

RecordDay-to-day holderCan describe itCan approve licensing
Downtime events and piece counts in the MESManufacturing systems lead or MES administratorYesNo
Rescheduled dates and sequence changesPlanning managerYesNo
Maintenance work orders and failure codesMaintenance managerYesNo
Confirmations with yield and scrapPlant controllerYesNo
Quality holds and dispositionsQuality managerYesNo
Approval emails and planner chatIndividual mailboxes, governed by IT policyPartlyNo
All of the above, as a company assetExecutive teamThrough the operations directorYes, the CEO

SAP documents that confirmations can be partial or final and carry yield and scrap, and ISA-95 Part 4 defines object models for scheduling, performance and work-record data exchanged between business and plant systems. Those standards describe how data moves, not who owns it. Technical access is never authority.

The tree: from record owner to authorized signer

Work down the tree in a conversation. Each answer sends you to the next question.

  1. Does the company have 50+ full-time employees at peak (contractors excluded), a documented operating history and records it believes it has rights to license? If no, stop; the company does not meet the baseline. If yes, go to 2.
  2. Is the plant operations director, or an equivalent operations head, willing to describe how recoveries are recorded? If no, ask who runs scheduling and maintenance decisions and start there. If yes, go to 3.
  3. Is the plant part of a larger group? If yes, the parent may need to approve; note the parent's decision-maker and go to 4. If no, go to 4.
  4. Do orders contain customer drawings, part numbers or specifications covered by supply agreements? If yes, flag customer sign-off for counsel. Either way, go to 5.
  5. Do any programs involve defense articles or other export-controlled work? If yes, flag it for counsel. Either way, go to 6.
  6. Do approvals, overtime notes or chat contain employee names and personal details? If yes, flag a policy and privacy check. Either way, go to 7.
  7. Will the CEO agree to a licensing discussion? If yes, introduce the CEO, with the operations director as working contact. If not yet, wait; the partner does not push past the CEO.

Under the ITAR, technical data includes information required for the design, production, manufacture, repair, testing or modification of defense articles, including drawings and plans. A partner never decides whether that applies. Step 5 only records that the question exists.

BranchWhy it mattersWho resolves itWhat the partner writes
Customer drawings and specs inside ordersSupply agreements may restrict useCompany counsel, then SourceX rights review"Customer-owned designs present"
Parent or group ownershipThe plant may not own its systems or dataGroup legal or the parent's executive"Part of a group; parent approval may be needed"
Export-controlled programsTechnical data may be restrictedCompany counsel and export compliance"Possible controlled programs; counsel to confirm"
Employee data in approvals and chatPrivacy policy and local law applyHR and counsel"Personal data in email; policy check needed"
Assets sold or in an insolvency processAuthority may sit with a trustee or assigneeThe appointed officer"Authority sits outside management"

The last row is rare but real: when a plant closes or its assets pass to an assignee, the person who can say yes changes; see ABC assignee intangible asset recovery. Why ownership is checked before anything else is explained in why data rights matter, and who owns customer drawings at a contract manufacturer covers the most common branch.

What stays unknown until SourceX's rights review

A partner should be comfortable leaving these open:

  • Whether customer agreements permit licensing any part of the records.
  • Whether controlled or confidential programs must be excluded.
  • Whether employee data needs removal or de-identification.
  • Whether there is SourceX's current data needs for the records and what any offer would be.

The geography rule is also SourceX's to apply: 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. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company.

Making the introduction

Once step 7 is a yes, send a short note to the executive with the operations director copied, and attach a metadata-only summary; the referral brief template gives the fields. Partners must sign the Channel Partner Agreement before submitting introductions. More plant record types are on the manufacturing industry page.

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 tree ends at a CEO who agrees to talk, register as a partner, check the company against who qualifies, and read the program terms before you make 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

Can the MES administrator agree to a licensing discussion?

No. The administrator can describe what the system holds and since when. Agreeing to discuss licensing company records is the CEO's decision.

What if the plant manager is enthusiastic but the CEO has not heard of it?

Treat the plant manager as the working contact and ask them to bring the idea to the CEO. Do not submit the company as if the CEO had agreed.

Does a partner need to resolve the customer and export questions first?

No. Flag that they exist. SourceX's rights review and the company's counsel resolve them.

Sources

  1. help.sap.com/docs/s4hana-cloud-best-practices/quality-man…
  2. isa.org/products/ansi-isa-95-00-04-2018-enterprise-c…
  3. ecfr.gov/current/title-22/chapter-I/subchapter-M/part…
  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