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.
| Record | Day-to-day holder | Can describe it | Can approve licensing |
|---|---|---|---|
| Downtime events and piece counts in the MES | Manufacturing systems lead or MES administrator | Yes | No |
| Rescheduled dates and sequence changes | Planning manager | Yes | No |
| Maintenance work orders and failure codes | Maintenance manager | Yes | No |
| Confirmations with yield and scrap | Plant controller | Yes | No |
| Quality holds and dispositions | Quality manager | Yes | No |
| Approval emails and planner chat | Individual mailboxes, governed by IT policy | Partly | No |
| All of the above, as a company asset | Executive team | Through the operations director | Yes, 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.
- 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.
- 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.
- 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.
- 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.
- Do any programs involve defense articles or other export-controlled work? If yes, flag it for counsel. Either way, go to 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.
- 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.
Branches that need legal, customer or group sign-off
| Branch | Why it matters | Who resolves it | What the partner writes |
|---|---|---|---|
| Customer drawings and specs inside orders | Supply agreements may restrict use | Company counsel, then SourceX rights review | "Customer-owned designs present" |
| Parent or group ownership | The plant may not own its systems or data | Group legal or the parent's executive | "Part of a group; parent approval may be needed" |
| Export-controlled programs | Technical data may be restricted | Company counsel and export compliance | "Possible controlled programs; counsel to confirm" |
| Employee data in approvals and chat | Privacy policy and local law apply | HR and counsel | "Personal data in email; policy check needed" |
| Assets sold or in an insolvency process | Authority may sit with a trustee or assignee | The 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.